Implementation Specification: Complex Circuit Load Balancing¶
Summary¶
This implementation specification defines the project-scoped delivery for the Complex Circuit Load Balancing milestone.
It is an incremental delivery plan against the long-lived microgrid system design. It focuses on using the microgrid concept to model more realistic electrical systems for load balancing, while keeping the MVP implementation pragmatic and close to existing persisted circuit, charge-point, and connector data.
System Design Reference¶
- Primary system design:
docs/system-design/microgrid/spec.md
Project Goal¶
Deliver a microgrid-backed load-balancing MVP that can represent and balance a WA-PTA-style electrical structure where one or more grid connections feed multiple charger circuits and each charger circuit feeds multiple chargers, with hierarchical limits enforced across the whole site.
In Scope¶
- Build a richer in-memory microgrid balancing structure on top of the persisted microgrid created in BBA, using the microgrid itself as the root and the persisted first-level
GRID_CONNECTIONnodes sourced from the depot's top-level circuits. - Derive downstream charger-circuit, charger, and connector relationships in memory from existing persisted site data rather than introducing new topology tables in this MVP.
- Use explicit existing rating sources as the authoritative hierarchical limits in this MVP:
- top-level grid-connection circuit default/safe operating capacities for the first electrical layer beneath the microgrid
- downstream circuit default/safe operating capacities for charger-circuit branches
- charge-point and connector maximum ratings for downstream charging assets
- Apply hierarchical rebalance behavior across grid connection, charger-circuit, and charger limits.
- Show derived structure, cycle outcome, and branch or site constraint visibility through minimal product surfaces.
- Demonstrate the behavior with seeded or simulator-backed scenarios suitable for QA and stakeholder review.
Story Scope¶
- All stories in
stories.mdin this folder.
Planned Release Slices¶
- Phase 1: Load-Balancer Package Enhancement
COR-10- Phase 2: Complex Microgrid Product Integration
COR-11- Phase 3: Customer Integration Testing
COR-14- Customer-specific integration or validation execution issues may be tracked only in Linear against this phase; they are not canonical repo stories.
- Phase 4: Microgrid Status and Breach Visibility
COR-12COR-13- Phase 5: Charger-Based Strategy Parity
COR-35
Explicitly Out of Scope for This Project¶
- Operator-authored topology editing.
- Persistent microgrid topology tables, topology versioning, or topology conflict workflows.
- Dedicated node or aggregate limit management UI.
- Legacy circuit compatibility paths and TOU migration work.
- Telemetry-fallback hardening beyond what is needed for the MVP balancing flow.
Short-Term Delivery Notes¶
- The MVP keeps the persisted
Microgridrecord as the stable site root, uses the persisted first-levelGRID_CONNECTIONnodes created in BBA, and derives the richer downstream balancing structure at read or evaluation time rather than persisting a full editable topology model. - Existing circuit, charge-point, and connector configuration remains the source of truth for physical ratings and electrical relationships in this phase.
- In the current integrated path, the derived power-node projection is consumed by connector-based load-balancing strategies. Charger-based strategies still follow the existing charger-allocation path.
- Charger-based parity for the same complex projection is tracked as a separate follow-on story in this project.
- This project provides cross-project dependencies to the Vector DERMS milestone for microgrid status and cycle-visibility surfaces.
Dependency Notes¶
- This project builds on the microgrid provisioning, persisted microgrid record, and first-level persisted
GRID_CONNECTIONnodes delivered indocs/artifacts/active/bba-microgrid-controller/. - Later
OperatingEnvelopework remains owned by the Vector DERMS project and related follow-on microgrid stories. It is not a delivery dependency forCOR-10orCOR-11.
Backlog Link¶
- Deferred microgrid stories not assigned to an active project are tracked under
docs/artifacts/backlog/microgrid/stories.md.