Use Case: <Planned Outage Reporting to EMS Use Case Number: <EMS-003>

Use Case:003>: <Planned Outage Reporting to EMS

Summary:

The outage data exists in Outage Request System (ORS) application. All approved new, rescheduled and cancelledoutages will be published to Enterprise Integration bus in CIM XML format.

Actor(s):

Name / Role description
ORS / Publish planned outages in CIM XML format to Enterprise Interation bus.
Enterprise Integration Bus / Enterprise provides data correlation for Equipment Id and publishes to EMS.
EMS / Subscribe to planned outage data and updates scheduled outage database.
Tech support / Receive and respond to alarm after unsuccessful update of EMS schedule outage database.

Participating Business Functions/Systems:

Acronym / Business Function
/Abstract Component / System / Services or Information Provided
ORS / Lotus notes Outage Request System /
  • Extract all approved new,rescheduled,and cancelled outages from ORS database.
  • Converts outage data to CIM based XML message.
  • Publishes to Enterprise Integration Bus.

Integration BUS / Integration bus /
  • Provides message bus functionality for publilsh/subscribe.
  • Provides data correlation for equipment Id.

EMS / ABC Energy Management System /
  • Subscribe to CIM based XML message for planned outage data.
  • Processes the data and updates scheduled outage database.
  • Sends confirmation back to integration bus.

Assumptions / Design Considerations:

  • Published data from ORS application will contain new,rescheduled as well as cancelled outages.
  • The action of creation, reschedule or cancellation is conveyed via the verb phrase in the message header.
  • EMS euipment id is the name of the equipment instance and not the pseudo SCADA point.
  • Generation outages are for individual generating units as opposed to the whole plant and there is no ramping in the schedule. There is no derating of the generator.
  • Frequency: Real time, approximately 40-50 average per day to a maximum of 65 per day. “As per Karl, all the outages for future should be extracted at the end of day”.
  • One outage per message

Pre-conditions:

  • All the published outages have been approved either internally or by ISO.
  • Approved outage is rescheduled.
  • Approved outage is cancelled.

Normal Sequence: Create Planned outage

Use Case Step / Event / Description Of Process / Information To Be Exchanged / ProducerTo Receiver Abstract Component/
System / Message Type (Verb/Noun)
Step1 / Approval of planned outage / Extract the approved planned outage and convert to CIM based XML message. / The information to be exchanged is the schedule for the planned outage. Refer to information model table below. / ORS-INTEGRATION BUS / Create Planned Outage
Step2 / INTEGRATION BUS receives Outage message / Enterprisesuccessully correlates the ORS equipment id to EMS equipment id.
Publish message to EMS. / Same as previous step, with EMS equipment id. / INTEGRATION BUS-EMS / Create Planned Outage
Step3 / INTEGRATION BUS receives Outage message / Enterprise cannot correlate ORS equipment id to EMS equipment id raises exception.
INTEGRATION BUS sends alarm to INTEGRATION BUS support. / Error message; Equipment id, status “Cannot correlate”. / INTEGRATION BUS-Support Staff / Error Message
Step4 / EMS receives Outage message / EMS receives CIM based XML planned outage message.
EMS process the message. / Same as previous step, with EMS equipment id. / INTEGRATION BUS-EMS / Create Planned Outage
Step5 / EMS accepts planned outage / EMS updates scheduled outage database.
Step6 / EMS update successful / EMS Sends update confirmation message “Success” back to INTEGRATION BUS. / Outage id, Euipment id, Status “success”. / EMS-INTEGRATION BUS / Update Confirmation

Alternate Sequence: Create Planned outage

Use Case Step / Event / Description Of Process / Information To Be Exchanged / ProducerTo Receiver Abstract Component/
System / Message Type (Verb/Noun)
Step 1-4 / Same as Normal sequesnce
Step5 / EMS rejects planned outage / Exception because of error in message.
Exception because of operational reasons.
Step6 / EMS update unsuccessful / EMS Sends update confirmation “Error” or “Reject” message back to INTEGRATION BUS. / Outage id, Euipment id, Status “Error”, error description.
Outage id, Euipment id, Status “Rejects”, error description. / EMS-INTEGRATION BUS / Update Confirmation
Step7 / INTEGRATION BUS receive unsuccessful confirmation / INTEGRATION BUS send alarm to INTEGRATION BUS support. / Outage id, Euipment id, Status “Error”.
Outage id, Euipment id, Status “Rejects”. / INTEGRATION BUS-Support Staff / Planned outage unsuccessful alarm

Normal Sequence: Reschedule Approved Planned outage

Use Case Step / Event / Description Of Process / Information To Be Exchanged / ProducerTo Receiver Abstract Component/
System / Message Type (Verb/Noun)
Step1 / Reschedule of approved of planned outage / Extract the previously approved planned outage which is being rescheduled and convert to CIM based XML message. / The information to be exchanged is the schedule for the planned outage. Refer to information model table below. / ORS-INTEGRATION BUS / Reschedule Planned Outage
Step2 / INTEGRATION BUS receives Outage message / Enterprisesuccessfully correlates the ORS equipment id to EMS equipment id.
Publish message to EMS. / Same as previous step, with EMS equipment id. / INTEGRATION BUS-EMS / Create Planned Outage
Step3 / INTEGRATION BUS receives Outage message / Enterprise cannot correlate ORS equipment id to EMS equipment id raises exception.
INTEGRATION BUS sends alarm to INTEGRATION BUS support. / Error message; Equipment id, status “Cannot correlate”. / INTEGRATION BUS-Support Staff / Error Message
Step4 / EMS receives rescedule Outage message / EMS receives CIM based XML reschedule planned outage message.
EMS process the message. / Same as previous step, with EMS equipment id. / INTEGRATION BUS-EMS / Create Planned Outage
Step5 / EMS accepts reschedule planned outage / EMS updates scheduled outage database.
Step6 / EMS update successful / EMS Sends update confirmation message “Success” back to INTEGRATION BUS. / Outage id, Euipment id, Status “success”. / EMS-INTEGRATION BUS / Update Confirmation

Alternate Sequence: Rescedule Approved Planned outage

Use Case Step / Event / Description Of Process / Information To Be Exchanged / ProducerTo Receiver Abstract Component/
System / Message Type (Verb/Noun)
Step 1-4 / Same as Normal sequesnce
Step5 / EMS rejects rescedule planned outage / Exception because of error in message.
Exception because of operational reasons.
Step6 / EMS update unsuccessful / EMS Sends update confirmation message “Error” or “Reject” back to INTEGRATION BUS. / Outage id, Euipment id, Status “Error”, error description.
Outage id, Euipment id, Status “Rejects”, error description. / EMS-INTEGRATION BUS / Update Confirmation
Step7 / INTEGRATION BUS receive unsuccessful confirmation / INTEGRATION BUS send alarm to INTEGRATION BUS support. / Outage id, Euipment id, Status “Error”.
Outage id, Euipment id, Status “Rejects”. / INTEGRATION BUS-Support Staff / Planned outage unsuccessful alarm

Normal Sequence: Cancel Planned outage

Use Case Step / Event / Description Of Process / Information To Be Exchanged / ProducerTo Receiver Abstract Component/
System / Message Type (Verb/Noun)
Step1 / Cancellation of approved planned outage / Extract cancelled planned outage previously approved and convert to CIM based XML message. / The information to be exchanged is the schedule for the planned outage. Refer to information model table below. / ORS-INTEGRATION BUS / Cancel Planned Outage
Step2 / INTEGRATION BUS receives cancel Outage message / Enterprisesuccessfully correlates the ORS equipment id to EMS equipment id.
Publish message to EMS. / Same as previous step, with EMS equipment id. / INTEGRATION BUS-EMS / Cancel Planned Outage
Step3 / INTEGRATION BUS receives Outage message / Enterprise cannot correlate ORS equipment id to EMS equipment id raises exception.
INTEGRATION BUS sends alarm to INTEGRATION BUS support. / Error message; Equipment id, status “Cannot correlate”. / INTEGRATION BUS-Support Staff / Error Message
Step4 / EMS receives Outage message / EMS recdeives CIM based XML cancel planned outage message.
EMS process the message. / Same as previous step, with EMS equipment id. / INTEGRATION BUS-EMS / Cancel Planned Outage
Step5 / EMS accepts cancellation of planned outage / EMS updates scheduled outage database with cancellation of planned outage.
Step6 / EMS update successful / EMS Sends update confirmation “Success” message back to INTEGRATION BUS. / Outage id, Euipment id, Status “success”. / EMS-INTEGRATION BUS / Update Confirmation

Alternate Sequence: Cancel Planned outage

Use Case Step / Event / Description Of Process / Information To Be Exchanged / ProducerTo Receiver Abstract Component/
System / Message Type (Verb/Noun)
Step 1-4 / Same as Normal sequesnce
Step5 / EMS rejects cancellation of planned outage / Exception because of error in cancel message.
Exception because of operational reasons.
Step6 / EMS update unsuccessful / EMS Sends update confirmation message “Error” or “Reject” back to INTEGRATION BUS. / Outage id, Euipment id, Status “Error”, error description.
Outage id, Euipment id, Status “Rejects”, error description. / EMS-INTEGRATION BUS / Update Confirmation
Step7 / INTEGRATION BUS receive unsuccessful confirmation / INTEGRATION BUS send alarm to INTEGRATION BUS support. / Outage id, Euipment id, Status “Error”.
Outage id, Euipment id, Status “Rejects”. / INTEGRATION BUS-Support Staff / Planned outage unsuccessful alarm

Integration Scenarios

Information Model for normal sequence:

Native Data Name / Description / Native Data Type / CIM Class / CIM Class Attributes / CIM Attribute Type
SWITCHCENTER / Switching Center Id
ITEMNUM / Outage Id / OutageRecord / Name / String
STATIONLOCATION / Station Location / Either concatenate Station/Voltage and Id and data correlation resolves it later
VOLTAGE / Voltage of Device
EQUIPMENT / Device Id
OUTAGEDATE / Start Date of Outage
RETURNDATE / End date of Outage
STATUS / Create, cancel, Approved / Status
(This is a message header field. to identify if this is a create or a cancel outage.)
SCHEDULED / Scheduled time, start and end time

Exceptions

None

Post-conditions:

  • Message is persisted in Enterprise only till it receives confirmation with “Success”, after that its deleted from INTEGRATION BUS.
  • If the confirmation is “Error” or “Reject”, message needs to be reprocessed after manual intervention.

Message Type Table:

Message Type Identifier / Message Type (Verb/Noun) / Message Type Content
(Class.Attribute) / Revision Number

Create Planned Outage

Cancel Planned Outage

Reschedule Planned Outage

Error message

Update Confirmation
Planned outage unsuccessful alarm

References:

None

Issues:

ID / Description / Status
1 / Verify if we need to get real time equipment outages to EMS. / NO
2 / What about other non-transmission outages like generation outages etc. / Yes, the same interface will handle Generation outages.

Revision History:

No / Date / Author / Description
1. / 12/01/05 / Project team / Original.
2 / 12/15/06 / Project team / Updated and baselined after requirements meeting