Outage Management Replacement Phase 1
Contents
1. oo SU eges eT D E Ea i LIST OT PIQUICS MEME UT ii List of Tables 5e n cna viens m onec mnanaa iii Table of Chariges crei iit tir t EU iv 1 lntroducti n 4 eere eee eee itrerere E Na rtr lia cere eerte eene 1 1 1 PUrpOSO et i ode alit e Nee Cl eset 1 1 2 roo m St Q ORE 1 1 3 Who Should Read This Document M 9 Rss 1 2 xOutage PIOGBSS imiinien VN se Gore co De didiu eu cid tera Rc iaaah an 2 3 Functional Overview 2M0 3 3 1 OMR Phase 1 Electronic Outage Request Form sesssssssssss 3 3 1 1 Purpose amp 298 0 3 3 1 2 User Gjaups Mf ERR 3 A13 Dom ER eoo M ooo oo diee Pro ertet ee sac 3 3 1 4 EMO NS A Nee nn eher ne nnns 4 3 4 5 Rules E eese eene nnne 5 3 2 Documentation WEE MERE een 7 3 3 General Requirements VNNRENCNNRRER A 7 4 Availability and Reliability eeeeeeeeeeeeeeeee eere eren nennen 8 4 1 RP Willlability 99k 5er 8 4 2 it NC ODIO DOE 8 4 3 SS CUNY MN REN dec tc Mq IE 8 5 Appendiks Dr T 9 5 1 Request Screen RP ea EE E densakasstnenywuglolaatstaecolewdeienateeben 9 5 1 1 x isgaistzoglenre c EC 10 5 2 Search SGre oec ted od Deep prb xe o e ES v reda La A Eu Ra A E e od 13 5 2 12. CP Station Kapuskasing Eqp Information Voltage 115 kV MW Max Cap 247 MX 434 Can be recalled URS a me NEN I MB LI REL C LM Rap XWhite Line Wapustasna Outage Y Oms 9o o 9 jeee Gen 2 Generator Whteshel ims N WA 9 15 9 esos Outage request screen mock up Issue 1 0 July 24 2009 Public 5 Appendix 5 Appendix IESO REQ 0152 10 5 1 1 Field descriptions Single Point of Contact Organization The organization this outage request pertains to This is a drop down field for all market participants the user is eligible to submit on behalf of Contact The name of the contact person defaults to the user who creates the request but can be overridden Phone The phone of the contact person defaults to the user who creates the request but can be overridden Fax The fax of the contact person defaults to the user who creates the request but can be overridden eMail The eMail of the contact person defaults to the user who creates the request but can be overridden Submitter The user who ast submitted the form Outage Request Draft ID The id for this draft outage request This field is only generated on an outage request being saved as a draft Outage ID The record id of any request following its submission to IOMS This field replaces any assigned Draft ID Status The state of the outage draft submitted confir
3. EXTERNAL REQUIREMENTS IESO REQ 0152 o leso Power to Ontario On Demand Outage Management Replacement Project Phase 1 Functional Requirements Draft Issue 1 0 edo cument details the functional requirements of phase 1 of the B Oude Man oe nt Replacement Project Document ID Document Name Issue Reason for Issue Effective Date IESO REQ 0152 Outage Management Replacement Phase 1 Issue 1 0 Initial Release July 24 2009 2009 Independent Electricity System Operator Outage Management Replacement Phase 1 Document Change History Document Change History Issue Reason for Issue Date 0 1 Initial Release April 24 2009 0 2 Modified with requirements updates July 16 2009 0 3 Modified outage request state flow to include forced July 24 2009 outages Related Documents Document ID Document Title Issue 1 0 July 24 2009 Public Document Control Document Control IESO REQ 0152 Authorities Prepared by Role Signed amp Dated Reviewed by Role Signed amp Dated Approved by Role Signed amp Dated Distribution List Name Organization Public Issue 1 0 July 24 2009 Outage Management Replacement Phase 1 Table of Contents Table of Contents Table of Conlerils 0 02202520 2 2 6202 20226202 8 2 62 2 90 2 9202 99 9 02 2 0 2 0005
4. MS database to receive and store outage data submitted via the electronic form 6 The IESO portal shall be used to authenticate users and to provide a secure environment to submit outage requests 1 3 Who Should Read This Document 7 This document is for the use of business and or systems analysts in preparing specifications for the OMR project 8 This document will also be used to communicate the scope of the project to the Steering Committee and as such will be modified if the scope changes throughout the project 9 In this document you and your refer to market participants i e external users while we us and our refer to the IESO End of Section Issue 1 0 July 24 2009 Public 1 2 Outage Process IESO REQ 0152 2 Outage Process 10 Under the market rules you are required to report any changes to the normal status of your equipment that would affect the reliability of the IESO controlled grid ICG Refer to Market Manual 7 3 Appendix B for outage reporting requirements For the purpose of this document these changes will be referred to as outages 2 Public Issue 1 0 July 24 2009 Outage Management Replacement Phase 1 3 Functional Overview 3 Functional Overview 3 1 OMR Phase 1 Electronic Outage Request Form 3 1 1 Purpose 11 The electronic outage request form will be developed for the purpose of automating the transfer of outage information to the existin
5. NNEN a NEP NND EE UIS The outage search screen mock up 5 2 1 Field detail e All fields with the exception of the Status either Draft or Submitted are optional e The Equipment column of the search results contains a bulleted list of the equipment which is contained in the outage request Issue 1 0 July 24 2009 Public 13 5 Appendix IESO REQ 0152 5 3 Outage request state flow Request state flow green is an MP ariven state purple is an IESO ariven state and orange is dependent on the preceding state 14 Public Issue 1 0 July 24 2009 Outage Management Replacement Phase 1 5 Appendix 5 4 Request type ECP type matrix Below is a matrix of which ECP types are available for each outage request type Request ECP Outage Derate In service Hold off Planned WY ww ww Forced WY W Y x X Test XK Y Information XK 3 w w Y Issue 1 0 July 24 2009 Public 15 6 References IESO REQ 0152 6 References Document Name Document ID End of Document 16 Public Issue 1 0 July 24 2009
6. an about 4 hours per year as a result of unplanned outages 4 2 Reliability 50 There should be no more than 4 service breaks or unplanned outages that exceed 30 minutes per year 4 3 Security 5 Only authorized users of the OMR will be able to use the system Users will be authenticated through the IESO Identity Management System 52 All data transmitted on the public internet and will not be encrypted 53 The functions delivered by the OMR project shall conform to the IESO security standards which includes user authentication for each individual user Each user will be required to use their account and password End of Section 8 Public Issue 1 0 July 24 2009 Outage Management Replacement Phase 1 5 Appendix 5 1 Request Screen Outage Request Form Single Point of Contact Organization Power 4 U v Contact Doe John Phone 999 9999 ext 234 Submitter Doe John eMail john doeQ power4u com Fax 999 9999 ext 222 Outage Request Outage ID Status N A Draft Submit date time Last saved 2009 Jun 12 14 23 2009 Jun 12 14 23 Type Purpose Planned a My Description Start date time End date time Cycle Includes weekends Confirm on submission 7j pay Cancellation Deferral hr Recall Cost comments Cost comments Please confir Draft 2039 created Are you sure you want to au Lua Draft outage request 2039 created Equipment Condition Plans E
7. draft format before it has been submitted creating a Draft ID on the request No validations are performed Submit Submits the outage request to IOMS following data validation This action replaces the Draft ID if present with an Outage ID Delete A user is able to delete a draft which had previously been saved but not submitted to IOMS Public Issue 1 0 July 24 2009 Outage Management Replacement Phase 1 3 Functional Overview Forced Pending 40 Submit Resubmits the outage request to IOMS following data validation 4 Cancel Cancels the outage Forced In progress 42 Submit Resubmits the outage request to IOMS following data validation 3 2 Documentation 43 Auser manual shall be produced 44 A process document shall be produced 3 3 General Requirements 45 Regular database maintenance functions shall not affect the performance of the OMR Phase 1 functions 46 All user interfaces shall be integrated into the IESO web portal 47 All times are in EST 48 Upgrades shall be done with minimal interruptions to the users End of Section Issue 1 0 July 24 2009 Public 7 4 Availability and Reliability IESO REQ 0152 4 Availability and Reliability 4 1 Availability 49 The OMR electronic form shall be available 24 hours a day seven days a week 365 days a year 99 95 of the time excluding planned outages to the system or the OMR electronic form shall be unavailable no more th
8. g IOMS system 3 1 2 User Groups 12 The outage submission electronic form is designed for external participants thus the only users expected to interact with it are market participants 3 1 3 Design 13 We will design the new electronic form so that it provides a similar look and feel as the existing Outage Request form IMO FORM 1360 The new electronic form will allow you to submit outage data more efficiently consistent with what is expected in using an electronic submittal process 14 Itshould be noted that there are some market participants that have developed their own outage systems that use the existing API to submit outage data This capability will remain in place and will not be enhanced in this phase of the project 15 Screen mock ups and field descriptions are included in the appendix Issue 1 0 July 24 2009 Public 3 3 Functional Overview IESO REQ 0152 3 1 4 Functions 16 17 18 19 20 21 22 You will be able to use the electronic form to create submit and update outage information within the IOMS based on permissions You will have the ability to view a summary report of your outage submissions You will have the ability to search from amongst your submitted outages based upon search criteria that you can specify To increase efficiency the search operation might potentially only retrieve a specific number of outages with any given query When submitting outages you will ch
9. gi oe 13 5 3 Outage request state flOw eite eS RR Eie e e a Ee e a dag 14 5 4 Request type ECP type matrix ios coe tete et mess te Ro eee donee 15 XM ReferenC S eT M 16 Issue 1 0 July 24 2009 Public i List of Figures IESO REQ 0152 List of Figures None ii Public Issue 1 0 July 24 2009 Outage Management Replacement Phase 1 List of Tables List of Tables None Issue 1 0 July 24 2009 Public iii Table of Changes iv Table of Changes IESO REQ 0152 Reference Section and Paragraph Description of Change Public Issue 1 0 July 24 2009 Outage Management Replacement Phase 1 Introduction 1 Introduction 1 1 Purpose 1 This document defines the functional requirements for the first phase of the Outage Management Replacement OMR project Phase 1 of the OMR project is to provide users with the ability to submit outage requests via an electronic outage request form 1 2 Scope 2 The in scope items for phase 1 of the OMR project are as follows 3 Provide you with the ability to submit outage requests via an electronic form The electronic outage request form shall be designed so that it is similar to the existing outage request form IMO FORM 1360 4 Provide the necessary business logic in the electronic outage request form to improve the data entry process 5 Phase 1 of the OMR project will use the existing IO
10. lect a piece of equipment Eqp type Informational used in conjunction with station to help select a piece of equipment Equipment The equipment this ECP is referring to only selectable after station and eqp type have been selected Protection only Yes no if only the protection sections of the equipment are relevant to the ECP Eqp Information Any relevant information for the equipment selected this includes Second station lines only Voltage MW Max Cap generators only MX Max Cap generators only Can be recalled Yes no if this ECP can be recalled Recall time Number and units minutes hours or days Type Derating outage in service or hold off Derate to MW MW derating always 0 for outages Derate to MX in MX in derating Derate to MX out MX out derating 12 Public Issue 1 0 July 24 2009 Outage Management Replacement Phase 1 5 Appendix 5 2 Search Screen Outage search Criteria ID Organization Status OPG w ODreft Confirmed i i Submitted Start date i r c Station Equip type Equipment Kapuskasing s Generator s GENI2B Results Purpose ID Equip Gen1B Gen2C 1 Sog pm Lorem ipsum dolor sit amet consectetur adipiscing elit LineS a hh hr orate E 0 0 00E o 0 ooo o o o submit 0 0 0 0 0 0 0 o o 1 confirm 0L 0 0 0 o 1 1 gun 1 ILL I senim 0 0 0 0 05 0 S E CDOHM NE
11. med etc Submit date time When the outage was last submitted Last saved When the outage was last saved all user initiated state changes are considered to be saves as well Public Issue 1 0 July 24 2009 Outage Management Replacement Phase 1 5 Appendix Type Planned forced test or information Purpose A brief description of the outage also used for searching later Start date time When the outage is proposed to start End date time When the outage is proposed to end Cycle Daily or continuous Includes weekends Whether the outage duration is to include weekends or not Cancellation Cost to cancel the outage Deferral hr Hourly cost to defer the outage Recall Cost to recall the outage Cost comments Justification comments for costs provided MP comments Any comments the MP has regarding the outage This section is to be used to provide the IESO with any pertinent information that will assist the IESO in performing an assessment The IESO cannot edit this field Refer to Market Manual 7 3 section 1 3 5 1 for details IESO comments Any notification comments the IESO has made regarding this outage This data will need to be pulled from IOMS when the form is loaded MPs cannot edit this field Issue 1 0 July 24 2009 Public 11 5 Appendix IESO REQ 0152 Equipment Condition Plans Station Informational used in conjunction with eqp type to help se
12. oose equipment from a pre defined list stored within IOMS This will allow us to more easily maintain the IOMS equipment list We will maximise the number of outage properties that are explicitly defined via pick lists in order to minimize input data errors facilitate error checking standardize the data and to facilitate automated tasks The electronic form shall report data validity errors to you Any outages that you might continue to submit via fax or e mail for example in an emergency if the Portal was not available will not be accessible through any of the functions added through Phase 1 of the OMR project Public Issue 1 0 July 24 2009 Outage Management Replacement Phase 1 3 Functional Overview 3 1 5 Rules Planned Outages Draft Form behavior 23 The confirm on submission check box is only available and defaulted to checked when the outage start date is less than 33 calendar days from commencement User actions 24 Save draft Saves the outage request in a draft format before it has been submitted creating a Draft ID on the request No validations are performed 25 Submit Submits the outage request to IOMS following data validation This action replaces the Draft ID if present with an Outage ID If the confirm on submission box is checked request is placed in confirmed state otherwise it is placed in the unconfirmed state 26 Delete A user is able to delete a draft which had previo
13. usly been saved but not submitted to IOMS Unconfirmed confirmed Form behavior 27 The confirm on submission check box is only available and defaulted to checked when the outage start date is less than 33 calendar days out and the outage is in the unconfirmed state User actions 28 Submit Submits the outage request to IOMS following data validation On submission a previously assigned timestamp can potentially be overridden with a new timestamp as described in Chapter 5 section 6 4 13 6 4 18 of the Market Rules 29 Cancel Cancels the outage Issue 1 0 July 24 2009 Public 3 3 Functional Overview IESO REQ 0152 Rejected User actions 30 31 Force Sets the outage type to forced Cancel Cancels the outage Advance Approved User actions 32 Cancel Cancels the outage Revoked User actions 33 34 Force Sets the outage type to forced Cancel Cancels the outage Final Approved User actions 35 36 Request planned extension Creates a new draft based on the current request with the start time of the new request set to the end time of the current request and the comments pre filled with the text Extension to outage with being the ID of the current outage Add forced extension The user is able to submit a new end time and the outage type is set to forced Forced outages Draft User actions 37 38 39 Save draft Saves the outage request in a
Download Pdf Manuals
Related Search