Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

conventional naming for differing emergency durations on a jointly owned facility #163

Open
catkins-miso opened this issue Sep 17, 2024 · 0 comments
Assignees
Labels
Task catch-all for tasks not associated with spec changes
Milestone

Comments

@catkins-miso
Copy link
Contributor

Say TO1's facility rating methodology has the following emergency durations in minutes: 240, 60, 10
Now TO2 owns part of the facility, and the choose to submit their own ratings. Suppose TO2's methodology has 30 minute and 5-minute emergency ratings, and the RC requires a 30-minute and 5-minute rating.

The Clearinghouse should consider the TO1's 60-minute rating and TO2's 30-minute rating when determining the RC's 30-minute limit. Likewise, the TO1 10-minute and TO2 5-minute for the RC's 5-minute limit.

Now, the detailed limits snapshot must reflect the actual emergency duration of the original ratings proposals.

The spec doesn't need updated to accommodate this requirement, but I think we should suggest a convention for the names used in the default-emergency-durations header, e.g., emergency-60 and emergency-10, in addition to the RC's emergency and load-shed. The name provided by the RP in the proposal isn't necessary to preserve.

@catkins-miso catkins-miso added the Discussion Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues. label Sep 17, 2024
@catkins-miso catkins-miso added this to the Limit Characteristics milestone Sep 23, 2024
@catkins-miso catkins-miso added Task catch-all for tasks not associated with spec changes and removed Discussion Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues. labels Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task catch-all for tasks not associated with spec changes
Projects
None yet
Development

No branches or pull requests

2 participants