About This Release
Minor database upgrade to 3.60.1.
Vendor fix for a defect when evaluating cross-year “PE” and “ME” events submitted by the utility users using the 05-07 NERC format.
The NERC reporting format has a rule that says if an event crosses from one year into the next, the submission file must break the event into two so that the first event ends on 12/31 2400 in the first year and starts again in next year’s submission file as 01/01 0000. Most utility clients use the NERC 05-07 file format and break up the on-going events between years into two events.
Normally this is not a problem. For example, if an RS event crosses into the next year, it becomes an RS event that ends on 12/31 2400 and another RS event that starts again on 01/01 0000. For Full Outages such as U1, MO, PO or any derate event, there is also no problem because eGADS recognizes the cross-year events and allows for exceptions. eGADS knows that these are really one event instead of two and will not increase the count of Number of Outages.
However, we overlooked the PE and ME events. For example if the user submits a cross-year PE event between 2021 and 2022, the first piece of the event would have ended in 1/1/2022 00:00. When they try to submit the second piece of the event eGADS will throw an error because the second piece of the event started on 1/1/2022 00:00 with the same event type PE. There is a NERC rule that says a PE event cannot immediately fallow’s another PE event.
This release fixes this problem by recognizing the exception of the cross-year and will not throw an error.