This is a simple fix but technically breaks anyone using segment to filter seasonal overrides and/or temporary AAR exceptions.
It's true that a temporary AAR exception only applies to the logical segment, and the same could probably be said regarding all seasonal overrides. However, we early on adopted the "everything is a power system resource" view, and I think it should have applied in this case.
In addition to reading as an inconsistency, some clearinghouse providers may wish to accept seasonal overrides on facilities that have an AAR exemption and so may not have had a rating obligation or segment id. Additionally, some clearinghouse providers might prefer the use of facility ids for solely owned facilities instead of creating a segment. In the end the "resource-id as mailbox address for ratings" model is violated by the current name.
This is a simple fix but technically breaks anyone using
segmentto filter seasonal overrides and/or temporary AAR exceptions.It's true that a temporary AAR exception only applies to the logical segment, and the same could probably be said regarding all seasonal overrides. However, we early on adopted the "everything is a power system resource" view, and I think it should have applied in this case.
In addition to reading as an inconsistency, some clearinghouse providers may wish to accept seasonal overrides on facilities that have an AAR exemption and so may not have had a rating obligation or segment id. Additionally, some clearinghouse providers might prefer the use of facility ids for solely owned facilities instead of creating a segment. In the end the "resource-id as mailbox address for ratings" model is violated by the current name.