search

carbon-data-specification / Power-Systems-Data

This repository is dedicated to the Power Systems Data Working Group
Other
10 stars 7 forks source link

[Discussion] Topology should allow for network reconfiguration #75

Open Pierre-VF opened 1 year ago

Pierre-VF commented 1 year ago

Networks (including transmission lines) topology might be reconfigured over time. This makes capacity time-variant (although variations should be few over time), which should be accounted for in the topology endpoints and descriptions.

A reconfiguration can consist in:

A way to handle this could be to provide a timestamp when querying topology, where the returned value would be the topology at the time of request.

Note : this refers to the topology described in https://github.com/carbon-data-specification/Power-Systems-Data/blob/main/specifications/cdsc-wg2-03.md

ssuffian commented 11 months ago

What if we simply put a "lastUpdated" field on topology, that way the user would know if a topology has been updated since their last pull?

Pierre-VF commented 11 months ago

That can be an option too, which would then only allow to look at the current topology. I'm wondering whether there would be use-cases where a past topology would need to be loaded (e.g., when doing carbon reconciliation at the end of the year for scope 2 accounting), and if so, whether we should not design for allowing past topology to be loaded so that they can be supported. (I would personally favour this)