Implementation Specification: Vector DERMS¶
Summary¶
This implementation specification defines the project-scoped delivery for the Vector DERMS milestone.
It is an incremental delivery plan against the long-lived OSCP and microgrid system designs. It captures the Vector-specific scope, partner-profile constraints, and short-term implementation choices needed to deliver the first OSCP integration without changing the long-term system design direction.
System Design References¶
- Primary system design:
docs/system-design/oscp/spec.md - Dependent system design:
docs/system-design/microgrid/spec.md
Project Goal¶
Deliver a Vector-compatible OSCP Flexibility Provider integration that binds Vector group_id values to managed microgrid scopes, manages connection configuration and lifecycle, translates incoming forecasts into microgrid OperatingEnvelope constraints, and publishes outbound metering, adjustment, and compliance messages through the OSCP domain.
In Scope¶
- OSCP configuration entity covering group binding to a managed microgrid scope and connection profile management.
- OSCP operations visibility, registration, handshake, heartbeat, and lifecycle state.
- Protocol-agnostic
OperatingEnvelopetranslation for OSCP forecast effects, initially applied by updating legacy circuit available-capacity values associated with the mapped managed scope when that scope corresponds to a grid-connection circuit. - Forecast intake and translation into the microgrid
OperatingEnvelopeboundary. - Outbound group and asset measurement publication through the interim dispatcher.
- Manual adjustment flow and compliance-error publication.
- Vector-specific measurement profile behavior.
Story Scope¶
- All stories in
stories.mdin this folder.
Cross-Project Microgrid Dependencies¶
- Microgrid Provisioning and Management
- External Capability Status to Microgrid Card
- Microgrid Status Summary View
- Manage UI Cycle and Breach Visibility
Vector-Specific Short-Term Variations¶
- The first rollout uses the Vector partner profile on top of the generic OSCP system design.
measurement_configuration=INTERMITTENTis required for this project.- The Vector profile uses
UpdateAssetMeasurementsas a partner-profile deviation from the canonical Capacity Provider measurement path. - OAuth Client Credentials and required static header behavior are part of this project scope as partner-profile configuration concerns.
- Quarter-hour aligned metering windows and
initial_measure_timebehavior are required in this project even though the system design keeps that logic generic. - The first
OperatingEnvelopeimplementation writes through to legacy circuit available-capacity fields and uses legacy UI surfaces for operator visibility when the managed scope maps to a legacy grid-connection circuit.
Explicitly Out of Scope for This Project¶
- Generalized Capacity Optimizer support.
- Broader multi-partner OSCP profile support beyond what is needed for Vector.
- Complex multi-branch load-balancing redesign beyond the explicit
OperatingEnvelopestory and the listed cross-project dependencies. - A canonical microgrid operating-envelope history or detail view beyond what is required for the interim legacy-circuit path.
Backlog Link¶
- Future OSCP stories not assigned to this project should be tracked under
docs/artifacts/backlog/oscp/stories.md.