OMS Phase 3 - Generation

Transcription

1 OMS Phase 3 - Generation User Checkpoint Meeting (2 of 2) Business Requirements Phase November 15, 2011

2 Agenda Meeting Objectives Rod Wheeler OMS Generation Project Rod Wheeler Review requests received as of October 31 Reminder to submit final requests/comments by COB today Q&A: Business Rod Wheeler IT - Travis Robinson Page 2

3 Stakeholder Participation Consistent with our standard process, provide input on publicly available project documents. Participants can submit comments to First User Checkpoint was held September 14 Requests and comments have been solicited in two rounds (2 nd round ends today) Business Requirements Specification (BRS) walkthrough scheduled for December 13 January reviews of user interface prototypes and sequence diagrams for B2B integration Page 3

4 MP Scope Requests 69 requests received as of October 31: 43 in scope (pending executive approval) 7 in analysis 4 need more detail/supporting example from MP 10 out of scope 5 duplicate Current list is posted on OMS public site: sses/outagemanagementsystemproject.aspx Page 4

5 Requests In Analysis Not in Scope for Phase 3 The ISO is performing business analysis on these items. Feasibility and approval from executive management is still to be determined. More information regarding this request will be provided at the BRS walkthrough. Req # OMSREQ8 Description Allow SC to identify units out due to line outage OMSREQ9 Prevent ADS from dispatching a unit that is unavailable due to a line outage OMSREQ13 Push notifications of status changes on outage cards OMSREQ33 OMSREQ45 OMSREQ52 Forced Outage Report - When submitting a Forced Outage Report, once selecting the Add Information / Forced Outage Report, auto populate the 4 lines of info that are needed to report. Enable submission of cards that temporarily exceed master file data, for example test generation below Pmin All outage card data completely communicated to/from PCI (including new cards created directly in SLIC) Page 5

6 Requests Awaiting MP Response The ISO has requested more detail and/or supporting examples in order to evaluate these requests. Req # OMSREQ9 Description Prevent ADS from dispatching a unit that is unavailable due to a line outage OMSREQ10 Provide NRS-RA resource availability display OMSREQ31 OMSREQ51 Pmin P-min cards created from zero IFM schedules (currently can't create a P-min card unless a resource has an IFM award above 0 as this time) Quick link to all cards affecting a resource on the display screen for a single card OMSREQ55 Establish a response time deadline (or target) OMSREQ63 Correct Rules for Availability Reporting. If there are multiple SLIC tickets, the most limiting curtailment should determine availability. Currently, if there are multiple active outages/derates for the same period, then each time one ticket is changed, the user must conform changes to all the other tickets that apply during the same period. Page 6

7 Requests Out of Scope (Slide 1 of 2) Req # Description ISO Response OMSREQ18 Make Exceptional Dispatches viewable in OMS This is an ADS real-time dispatchable function. This is not an outage function. OMSREQ21 OMSREQ22 OMSREQ23 Provide cause codes connected with "Ambient not due to temp" rather than checking an additional box. (exempt from SCP charges) Provide cause code connected with Transmission outages showing unit being fully available and not dispatchable. (exempt from SCP charges) Use displays should highlight SCP Assessment hours. The check box in question is necessary to support SCP. Any change requests to this policy should be submitted to an ISO client representative. A new OMS attribute to support this situation can be implemented. However, it would require changes to SCP to recognize and use the new attribute. Any change requests to this policy should be submitted to an ISO client representative. This would be a new SCP function and is out of scope for OMS. OMSREQ32 Normal card. Currently only one hourly curtailment value can be entered for Normal cards. Should allow for an entry for all 24 values. Availability data can be submitted as hourly data that is used by the market. The hourly curtailment functionality in SLIC is not used by the market and will not be implemented in OMS. Page 7

8 Requests Out of Scope (Slide 2 of 2) Req # Description ISO Response OMSREQ53 Enable more flexible management of read/write access by certificate by resource. OMS follows ISO certificate security policy. Changes to certificate access are out of scope for OMS. OMSREQ54 Change request deadline time from 3 business days to 3 calendar days. This would require a change in ISO policy and tariff requirements. OMSREQ62 Include SLIC Outages in SIBR. Availability de-rates entered in SLIC aren t shown in SIBR. {We} must consult other data sources to avoid entering unavailable capacity. If visible in SIBR, the user could more efficiently submit feasible bids in SIBR. The CAISO should also assure that OMS information is synchronized across SIBR, ADS and CMRI. This would require an upgrade in SIBR functionality. No additional functionality is necessary in OMS. Page 8

9 Duplicate Requests Req # Description ISO Response OMSREQ25 OMSREQ40 Copy/Paste feature available for items such as availability, or any other entry with multiple fields to enter. Provide Web services for cause codes. Some sort of API call to get the latest cause codes See OMSREQ15 See OMSREQ5 OMSREQ49 Provide notifications / alerts for missing Forced Outage Reports See OMSREQ28 OMSREQ56 More transparency in approval process, e.g. more detailed status information See OMSREQ28 for the amount of approval detail that is in scope OMSREQ68 Integration with ADS would be very helpful. This would prevent ADS from dispatching a unit that is unavailable due to a line outage. See OMSREQ9 Page 9

10 Last Call for Requests and Comments MPs submit final input by COB today, November 15 to ISO will post responses by November 28 Page 10

11 Next Steps ISO responses posted by November 28 BRS walkthrough on December 13 Requirements and status will be posted to CAISO.COM > Stay Informed > Stakeholder Processes > Outage Management System Project Contact Rod Wheeler at Questions? or (916) Page 11