Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
topics:operator [2026/03/19 14:25] – ↷ Page name changed from topics:utility to topics:operator admintopics:operator [2026/04/13 11:02] (current) – o.sachs
Line 1: Line 1:
-<WRAP catbadge blue>General Topics</WRAP>+<WRAP catbadge>Actors & stakeholders</WRAP>
  
 ====== Operator ====== ====== Operator ======
Line 5: Line 5:
 <WRAP meta> <WRAP meta>
 lead-authors: Klaus Kubeczko lead-authors: Klaus Kubeczko
-contributors: [Names] +contributors: 
-reviewers: [Names]+reviewers:
 version: 3.0 version: 3.0
 updated: 17 March 2026 updated: 17 March 2026
 sensitivity: low sensitivity: low
-ai-disclosure: Claude Sonnet 4.6 (Anthropic) assisted with topic structuring, editorial revision, reference verification, and formatting; reviewed by Vitaliy Soloviy, 17.03.2026+ai-use: Claude Sonnet 4.6 (Anthropic) was used for topic structuring, editorial revision, reference verification, and formatting; reviewed by Vitaliy Soloviy, 17 March 2026 
 +status: in-review
 </WRAP> </WRAP>
  
Line 16: Line 17:
 Grid operators hold mandates to manage the technical functioning and long-term adequacy of electricity networks at transmission, distribution, or local level. Smart grid transitions expand what they coordinate: bidirectional flows, distributed storage, and advanced metering data require new capabilities and coordination architectures. Grid operators hold mandates to manage the technical functioning and long-term adequacy of electricity networks at transmission, distribution, or local level. Smart grid transitions expand what they coordinate: bidirectional flows, distributed storage, and advanced metering data require new capabilities and coordination architectures.
 </WRAP> </WRAP>
 +
  
 ===== Why this matters ===== ===== Why this matters =====
Line 25: Line 27:
 </WRAP> </WRAP>
  
-===== A shared definition =====+===== Shared definitions =====
  
 An operator is an entity with a mandate or licence to manage the technical functioning, stability, and adequacy of part of an electricity system. System operation may be separated from asset ownership under unbundling rules, and a single entity may fulfil several roles depending on local regulatory design. An operator is an entity with a mandate or licence to manage the technical functioning, stability, and adequacy of part of an electricity system. System operation may be separated from asset ownership under unbundling rules, and a single entity may fulfil several roles depending on local regulatory design.
 +
 +<WRAP tablecap>
 +**Table 1.** Operator categories, typical scope, and mandates.
 +</WRAP>
  
 ^ Category ^ Scope and typical mandate ^ ^ Category ^ Scope and typical mandate ^
Line 57: Line 63:
 Operators rely on SCADA, energy management systems, and distributed energy resource management platforms. As resources multiply at the grid edge, operators need real-time visibility into low-voltage networks and the ability to process data at scale. Effective integration requires interoperability across technical, informational, and organisational levels — as described in the GridWise Architecture Council framework.((GridWise Architecture Council. (2008). //GridWise® interoperability context-setting framework//. GWAC. https://gridwiseac.org/pdfs/interopframework_v1_1.pdf)) Operators rely on SCADA, energy management systems, and distributed energy resource management platforms. As resources multiply at the grid edge, operators need real-time visibility into low-voltage networks and the ability to process data at scale. Effective integration requires interoperability across technical, informational, and organisational levels — as described in the GridWise Architecture Council framework.((GridWise Architecture Council. (2008). //GridWise® interoperability context-setting framework//. GWAC. https://gridwiseac.org/pdfs/interopframework_v1_1.pdf))
  
 +<WRAP figure>
 {{:operator:gwac_interoperability_framework.png|GridWise Interoperability Framework Categories (GWAC, 2008)}} {{:operator:gwac_interoperability_framework.png|GridWise Interoperability Framework Categories (GWAC, 2008)}}
 +
 +**Figure 1.** GridWise interoperability framework categories. //Source: GridWise Architecture Council (2008).//
 +</WRAP>
 +
 +<WRAP tablecap>
 +**Table 2.** GridWise interoperability framework levels, grouped by domain. //Source: GridWise Architecture Council (2008).//
 +</WRAP>
  
 ^ Category ^ Levels ^ ^ Category ^ Levels ^
Line 85: Line 99:
 <WRAP case> <WRAP case>
 **Nigeria -- Transmission Company of Nigeria** \\ **Nigeria -- Transmission Company of Nigeria** \\
-TCN manages the national grid while eleven distribution companies handle regional delivery — a separation that creates coordination challenges at the transmission-distribution boundary.+TCN manages the national grid while eleven distribution companies handle regional delivery, a separation that creates coordination challenges at the transmission-distribution boundary.
 </WRAP> </WRAP>
  
 </WRAP> </WRAP>
 +
 +===== Distinctions and overlaps =====
 +
 +@@GAP@@ No distinctions content present in source. Suggested pairings for the next editorial pass: TSO vs DSO (scope and mandate); operator vs owner (unbundling); system operator vs balancing responsible party (role and liability).
  
 ===== Related topics ===== ===== Related topics =====
  
-{{tag>network_-_grid grid_edge integrated_system sector_coupling_-_sector_integration architectural_frameworks_-_sgam_et_al Operability Interoperability Markets Flexibility Resilience}}+[[topics:grid|Grid]] · [[topics:grid_edge|Grid edge]] · [[topics:sector_coupling|Sector coupling]] · [[topics:operability|Operability]] · [[topics:markets|Markets]] · [[topics:flexibility|Flexibility]] · [[topics:resilience|Resilience]]
  
 +===== Topic notes =====
  
  
-===== References =====+Source flag: Nigeria -- TCN case has no footnote or source. Add a verifiable reference before publication or remove the case.