Probabilistic Boundary Assessment.
The most power each boundary can carry, with every credible N-1 checked.
PBA pushes power across a boundary step by step until the first credible fault would overload something. At every step it re-optimises quad-boosters and HVDC links, so the limit you get is the real one, with the binding contingency named.
Why it matters nowProjects are queuing behind the same transmission corridors, so the first question is how much a boundary can carry before it needs reinforcing. Get it wrong and an offer is either undeliverable or capped for no reason. PBA finds the real limit.
How PBA works.
- 01
Boundary definition
Zone-to-zone map, monitored circuits and the monitored contingency set per boundary.
- 02
Step transfer up
Transfer is walked up incrementally until the first credible N-1 contingency binds.
- 03
Asset optimisation
Nearby quad-boosters and HVDC set-points are optimally re-dispatched at every step.
- 04
Capability output
The secure capability at the first binding contingency, base and optimised, with that contingency named.
Transfer capability, before and after optimisation.
Each boundary's secure transfer limit, before and after optimal dispatch of quad-boosters and HVDCs. Hover a bar for the binding detail.
Figures from an example run on a test network.
Boundary D is the bottleneck. Optimisation lifts it +21%, but it still misses the planning target. PBA puts a number on the gap that the next reinforcement, HVDC bootstrap or storage has to close.