Grid Control & Balancing Management

BC-3830 Level 1 Power & Water Utilities 3 providers 24 API surfaces

System-operator function for the bulk power system — real-time balancing of generation and demand, frequency and voltage control, reserves and ancillary services, operational planning, cross-border coordination, and black-start preparedness.

Grid Control & Balancing Management (BC-3830) is a level-1 business capability in the Power & Water Utilities model. The catalog holds 24 API surface(s) from 3 provider(s) that can perform some part of it. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Real-Time System Operations BC-3830.10

Continuous real-time supervision and control of system generation, demand, and interchange to maintain secure operation.

1 provider, 9 API surfaces

Frequency & Voltage Control BC-3830.20

Active frequency and voltage regulation through automatic generation control and reactive-power dispatch.

no catalog coverage

Operational Planning BC-3830.30

Day-ahead and intraday system security analysis, outage assessment, and operating-margin planning.

1 provider, 3 API surfaces

Reserves & Ancillary Services BC-3830.40

Procurement and activation of operating reserves and ancillary services including frequency, voltage, and inertia products.

3 providers, 10 API surfaces

Imbalance Settlement Operations BC-3830.50

System-operator-side calculation and notification of imbalance volumes and prices for balancing-responsible parties.

no catalog coverage

Cross-Border Coordination BC-3830.60

Coordination of interconnector flows, redispatch, and security with neighbouring TSOs and regional security coordinators.

no catalog coverage

Black Start & Restoration Planning BC-3830.70

Maintenance of black-start contracts, restoration plans, and restoration drills for total or partial system collapse scenarios.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Developing 3 Usable, with meaningful gaps to close
AEMOBalancing Reports v2.5LFAS Reports v2LFAS Submission v2System Management Reports v2.25 APIs53.7ISO New Englandactualinterchangedayaheadconstraintsdayaheadhourlyoperatingreservefifteenminuteinterchange15 APIs49.4ERCOTNP3-911-ERNP3-990-EXNP4-179-CDNP4-33-CD4 APIs49.1

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Grid Control & Balancing Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →