HomeGB EnergyCross-cuttingElectricityGasOil and upstreamHydrogenHeatNuclearCCUSInterconnectors

Governance scenario

Code Modification Conflict

A BSC modification conflicts with a simultaneous DCUSA modification. Cross-code coordination is needed. RECCO must facilitate resolution amongst competing governance bodies.

Back to scenarios

This is a fictionalised teaching scenario grounded in real institutional roles, published reforms, and current public-source context.

Scenario player

Work through the decision path below. Each choice changes the route, the institutional trade-offs, and the metrics the scenario tracks.

Code Modification Conflict

Step 1 of 2

Elexon

Conflicting modifications advance in parallel

A BSC modification proposes a change to settlement metering principles. Simultaneously, a DCUSA modification proposes related metering requirements. The two changes are technically compatible but have conflicting commercial implications. If both pass, suppliers face contradictory obligations. RECCO (Regulatory Coordination Committee) must be asked to facilitate.

What is at stake

  • -If both modifications proceed separately, implementation will be chaotic.
  • -If one is delayed, its sponsors lose momentum and support.
  • -If implementation is unified, responsibility for failure is unclear.

How do you coordinate the modifications?

Current Metrics

Operational Efficiency55
Stakeholder Trust60
System Security70
Affordability62
Customer Protection62
Net Zero Progress62

Actors Involved

ElexonRECCoOfgemSuppliersNGED

Regulatory Context

BSC Code Modification Procedure and DCUSA

Governance relationship map

View mode

Operating loop breadcrumb

Governance→Planning→Operations→Outcomes→Evidence

Current focus: Rules and accountability

Legend

Governance and policy

Rules, remits, and accountability

Planning and investment

Connections, queue progression, and delivery planning

System operations

Real-time balancing and network operation

Market and consumer outcomes

Prices, settlement, reliability, affordability

Evidence and learning

Telemetry, assurance, and continuous improvement

Glossary

  • Dispatch

    Real-time instructions to increase or reduce generation or demand so supply stays in balance.

  • Balancing

    The continuous process of matching electricity supply to demand while maintaining system frequency.

  • Constraint

    A technical limit in the network that restricts how power can flow under current conditions.

  • Industry code

    A formal rulebook that defines obligations and processes for specific market and network activities.

  • Connection agreement

    The formal agreement setting technical and milestone conditions for connecting a project to the network.

  • Settlement

    The process that turns metered and contractual positions into final market cashflow outcomes.

  • Conformance gate

    A quality checkpoint that verifies whether data or implementation meets agreed standards.

  • LTDS

    Long Term Development Statement publication requirements for distribution network data.

Guided tour

Step 1 of 8

Who sets the rules?

Start with governance: policy direction, regulatory oversight, licences, and code obligations.

Why it matters: Newcomers should first understand where authority sits before interpreting operational decisions.

Open Ofgem licence and code guidance

Preparing system graph…

Use this map to keep scenario decisions anchored to policy, coordination, operational delivery, and evidence feedback relationships.

Sources and methodology

How this page was assembled

Scenarios are designed as regulator-safe teaching runs. Institutional roles, programme context, and cited reform pathways stay grounded in current public sources, while event details and numbers inside the run remain fictionalised unless explicitly evidenced elsewhere. This scenario is framed against BSC Code Modification Procedure and DCUSA.

Last reviewed 18 March 2026

Primary sources

Ransford's Notes