An outage is when the outage requester submits a “cancelled” Cancelled change request with a cancel action. An outage is when it is not accepted by the ISO. “disapproved” Disapproved An outage becomes OK” via a manual transition by the “in IN OK outage requester/ISO operator to indicate that an outage is about to be completed An outage becomes service editable” either via an automatic “in transition by the system or a manual transition by the outage IN Service Editable requester to indicate the actual end time of an outage An outage becomes service” after 24 hours in the service “in “in IN Service editable” state. An outage is to end” when the outage requestor has not “late Late to End submitted an OK” request before the scheduled end time. “in An outage is to start” when the outage requester has not “late Late to acted before the scheduled start time. An outage becomes recommended” when ISO OE staff “OE OE Recommended have completed review in Long Term Planning horizon and determined the outage can be accommodated. An outage becomes when the outage requester provides “out” OUT the actual time of the outage An outage becomes OK” either via a manual transition by “out OUT OK the outage requester/ISO operator or automatically via the OMS system to indicate that an outage is ready to start An outage is when ISO staff are waiting for more “pre-approved” Pre-approved detailed information prior to approval of the outage. An outage is when the outage request passes all “received” Received validation rules. An outage is in the state when ISO staff are studying an “study” Study outage. The Outage States above and the relative state transitions observed in the ISO OMS are shown in the figure below. The diagram also demonstrates the state transitions expected to occur between the ISO and Reliability Coordinator’s outage states, including state transition mapping between the two systems.
Cancelled An outage is “cancelled” when the outage requester submits a change request with a cancel action. Disapproved An outage is “disapproved” when it is not accepted by the ISO. IN OK An outage becomes “in OK” via a manual transition by the outage requester/ISO operator to indicate that an outage is about to be completed IN Service Editable An outage becomes “in service editable” either via an automatic transition by the system or a manual transition by the outage requester to indicate the actual end time of an outage IN Service An outage becomes “in service” after 24 hours in the “in service editable” state. Late to End An outage is “late to end” when the outage requestor has not submitted an “in OK” request before the scheduled end time. Late to An outage is “late to start” when the outage requester has not acted before the scheduled start time. OE Recommended An outage becomes “OE recommended” when ISO OE staff have completed review in Long Term Planning horizon and determined the outage can be accommodated. OUT An outage becomes “out” when the outage requester provides the actual time of the outage OUT OK An outage becomes “out OK” either via a manual transition by the outage requester/ISO operator or automatically via the OMS system to indicate that an outage is ready to start Pre-approved An outage is “pre-approved” when ISO staff are waiting for more detailed information prior to approval of the outage. Received An outage is “received” when the outage request passes all validation rules. Study An outage is in the “study” state when ISO staff are studying an outage. The Outage States above and the relative state transitions observed in the ISO OMS are shown in the figure below. The diagram also demonstrates the state transitions expected to occur between the ISO and Reliability Coordinator’s outage states, including state transition mapping between the two systems.
Outage%20Management%20BPM%20Version_redline.docx