V10 · Organization Market Bidding

1. This volume — your seat at the market

This volume is the organisation’s working desk with two counterparties you never meet in person: the Market Operator and the System Operator.

You already know how to run a book, make a deal, and settle a PPA. Those are conversations with your counterparties — an IPP, an off-taker, a trader. This volume is the other conversation: the one with the people who run the shared marketplace. You do not telephone them. You file paper, you send bids, you acknowledge instructions, you read statements, and you pay (or get paid) through accounts they hold in trust.

Think of a produce market that opens the day before the stalls do.

You are a farmer, a grocer, or a wholesaler. You do not set the crate price. You write a sealed note: how many crates you can sell, or how many you will take, and the worst price you will accept. The Market Operator opens every note, fills demand from cheapest supply, and announces one crate price for that hour. The System Operator is not in the hall at all. It is the traffic officer on the road to the market: it decides which trucks may actually roll, and it can tell you to dump crates if the road is blocked.

That picture is enough to use the five rooms in the organisation sidebar. The rest of this volume is that picture, screen by screen.

1.1 Who this is for

You log into the organisation app. You are an IPP, an off-taker, a trader, or a seat that wears more than one of those hats. Once you register as a Balance Responsible Party (BRP), the Market Operator treats you as one party — one membership card, one set of financial security, one inbox. The plants, sites and pools under that card are Trading Units. The market schedules and settles units, not your internal books.

You do not sit in the Market Operator console (/mo) or the System Operator console (/so). Those chairs are V11 and V12. This volume is what you press from /org.

Follow along. Seat: a seeded organisation, for example OffTaker C (offtaker_c@webill.net) or a trader (offtaker_c is the Organisation door on /; traders such as trader_1@webill.net work the same password). Password: supersecret (dev/demo only). Path: / → Organization. In the left sidebar, open the TRADING module: Market, Bid Desk, Month (the Market Month; its page is titled After Delivery), and Accounts. This volume covers those, plus Billing, which sits in the MONEY module beside the Room. Cross-border pool trading is not a sidebar room in this release.

1.2 What “dealing with” them actually means

Dealing with the Market Operator is mostly paper, prices and money:

1. You join. You file an accession application. They issue an MPID, two agreements, and an effective date. Until they Activate, you cannot bid.
2. You declare what you own. Trading Units, Points of Delivery, standing data. They keep the register the whole market can trust.
3. You bid. Day-ahead by 10:00 on D−1; intraday as the day unfolds. They clear, they publish one System Marginal Price per hour, they write your schedule.
4. You settle. After the meters come in they write a statement. Weeks later they invoice. You pay, or they pay you, through accounts they hold at the Market Bank.

Dealing with the System Operator is mostly physics and instructions:

1. You read the map. Zones, corridors, how much can actually flow.
2. You acknowledge instructions. Dispatch, curtailment, outage, reserve. An instruction you ignore is not “pending” — it is a missed operational order.
3. You tell them when the plant changed. Availability revisions and constraint declarations, so they do not dispatch a machine that is already down.
4. You dispute instructed energy when their published trace is wrong, because that trace is what imbalance will be measured against.

The two offices sit next to each other. They are not the same job. The Market Operator never throws a switch. The System Operator never writes your invoice.

1.3 The five rooms, in one sentence each

The sidebar’s TRADING module is this volume, plus Billing from the MONEY module. Five rooms, in the order the work actually runs (the sidebar rows are shorter — Month, Room — because the module says the rest):

Market is complete in this volume. Every tab, every card, every table, every operational button on Info, Account/Cover, Notices, SO, Registry, Standing Data and API is named. Bid Desk, Market Month and Accounts are written at the same grain — every tab, card, table, graph and operational button. Billing is still mapped tab by tab; the arithmetic those rooms run is taught in V9 and V15. Billing at Market grain is still open — see V22 §10.

1.4 How to read this volume

If you have twenty minutes, read this chapter, §2 and §3. That is the story: two offices, five rooms, one membership card.

If you are joining for the first time, start at §5 and walk the application board until the seat is ACTIVE. Then §6 (cover), §9 (units) and §10 (what the plant can do). You cannot usefully open Bid Desk until those four are green.

If an instruction arrived and you do not know whether to press Acknowledge, go to §8 and §7.

If someone asks “why was I charged this?”, start at Bid Desk › Settlement (§12.6) for the day, §13 for the month, and §14 for cash, then the statement arithmetic in V9 §13–§15.

Where this is taught. The SAWEM primer — what a BRP is, what the Market Operator auctions, what the System Operator dispatches — is V9 §1. This volume does not re-teach that. It teaches your screens. The Market Operator’s chair is V11. The System Operator’s chair is V12. The HTTP contract is V13.

1.5 Time, money, and the words on the badges

Every clock in this volume is SAST, a fixed UTC+02:00 with no daylight saving. D is the Trading Day — the calendar day the energy is actually produced or consumed. D−1 is the day before. A Trading Period is one hour, written as its start: 18:00 means 18:00–19:00. A Billing Period is a calendar month. They are not synonyms. Daily work picks a day; month work picks a month.

Money sign on market statements. Positive means the Market Operator pays you. Negative means you pay the Market Operator. Energy sign: positive means produced, negative means consumed.

Three status words you will see on Info, and they are not the same question:

The application board is the source of truth. The other two are projections. §5.4 walks the fifteen states from your chair.

1.6 A day in four pictures

Yesterday you bid. Today the energy flows. Next month the money moves. The rooms you live in change with that clock.

%%{init: {"themeVariables": {"fontSize": "18px"}, "flowchart": {"nodeSpacing": 28, "rankSpacing": 52, "padding": 18, "subGraphTitleMargin": {"top": 12, "bottom": 56}}}}%%
flowchart TB
  subgraph join ["Before you ever bid"]
    A["Market › Info<br/>file the application"] --> B["Market › Account/Cover<br/>notify the two accounts"]
    B --> C["Market › Registry + Standing Data<br/>units the market can schedule"]
  end
  subgraph dminus1 ["Yesterday · D−1"]
    D["Bid Desk › Submissions<br/>by 10:00"] --> E["MO clears and publishes<br/>by 14:00"]
  end
  subgraph d ["Today · Trading Day D"]
    F["Bid Desk › IDM<br/>five smaller auctions"] --> G["Market › SO / Notices<br/>acknowledge instructions"]
  end
  subgraph later ["Market Month"]
    H["Market Month<br/>wallet · file-join"] --> I["Accounts + Billing<br/>cover, cash, documents"]
  end
  C --> D
  E --> F
  G --> H

Nothing in that picture is optional once you are ACTIVE. Skip Registry and the meter cannot settle. Skip Account/Cover and accession never completes. Skip Acknowledge and the instruction still happened — you just did not admit you saw it.

The next chapter is the two counterparties, in ordinary language, with the metaphors you will need when a new colleague asks “who do I call?” The answer is: you do not call. You open the right room.

2. Two counterparties — Market Operator and System Operator

The organisation app talks to two offices that share a building and do not share a job. Mixing them up is the most expensive confusion on this desk: you will send a bid to the people who throw switches, or wait for an invoice from the people who dispatch plant.

2.1 The airport metaphor

Picture an airport.

The Market Operator is the ticketing hall, the published timetable, and the airport bank. It decides who may fly (your accession). It runs the auction that fills tomorrow’s seats (the day-ahead market). It publishes one price for a crate of energy that hour (the System Marginal Price). It holds your deposit so other passengers are not left paying your bill (credit cover). Weeks later it issues the invoice.

The System Operator is air-traffic control. It does not sell tickets. It keeps the sky from colliding. It draws the map of runways and corridors (network zones). When weather closes a runway it tells a specific aircraft to hold or divert (dispatch, curtailment, outage). You acknowledge the instruction so the tower knows the cockpit heard it.

You buy a ticket from ticketing. You take orders from the tower. You do not argue a delay with the cashier, and you do not pay an invoice to air-traffic control.

2.2 What the Market Operator is, in this app

The Market Operator (MO) is the independent party that runs SAWEM. From your chair that means five verbs:

They do not write the prices on your bid. They do not throw a switch. They do not settle your bilateral PPA — that is V8.

Where this is taught. The MO’s own chair — every /mo room — is V11. When this volume says “the Market Operator will Activate”, the button they press is on V11 §21.

2.3 What the System Operator is, in this app

The System Operator (SO) keeps the physical system secure. From your chair that means four verbs:

They do not set the energy price. Zones limit flow; they do not mint a local SMP. An instruction changes what “good delivery” means for imbalance. It does not quietly rewrite yesterday’s day-ahead price.

Where this is taught. The SO’s own chair — Dispatch Desk, Network Model, Registry — is V12. When this volume says “acknowledge the instruction”, the tower that issued it is V12 §4.

2.4 A worked hour — one crate, two offices

Data. Teaching numbers, not a sealed statement line. Pattern to expect on any ACTIVE demo seat. The golden fixture used across V7/V9 is Trading Day 2026-07-15, hour 18:00.

Yesterday (D−1). Your solar unit offered 20 MWh at a reservation of R 400/MWh. The Market Operator cleared the hour at an SMP of R 520/MWh. You were scheduled for 18 MWh. That is a ticket: 18 crates sold at R 520, not at R 400. The note only got you into the market.

Today 17:40. A corridor constraint appears. The System Operator issues a Curtailment instruction: hold 12 MWh for the hour, not 18. The instruction lands on Market › Notices (and the same row’s effects). You press Acknowledge. The Market Operator does not re-run yesterday’s auction. The 6 MWh you can no longer deliver is instructed. Imbalance will not treat it as a broken promise in the same way as a silent miss.

Tonight. Meters say you delivered 12.1 MWh. Bid Desk › Imbalance shows scheduled 18, instructed 12, actual 12.1. The small leftover is ordinary metering noise inside the band. Accounts later show the day-ahead energy pot (18 MWh at SMP) and a separate instructed/curtailment treatment — two offices, two lines, one hour.

Conservation of the story, not of a particular rand:

ticket (MO)     = 18 MWh scheduled at SMP
tower (SO)      = 12 MWh instructed
meter           = 12.1 MWh actual
imbalance story = actual − instructed, not actual − yesterday’s ticket

That is why Acknowledge is not politeness. It is how you admit the tower spoke, so the cashier can use the right measuring stick.

2.5 What you send, what you get

A pocket card for a new colleague.

To the Market Operator you send

• the accession application and any further information they ask for
• signed Market Participation Agreement and Balancing Agreement
• written notice that the two settlement accounts exist
• Trading Units, Points of Delivery, standing data
• day-ahead submissions and intraday re-declarations
• credit cover (cash into Collateral Reserve, in this console)
• queries against a statement

From the Market Operator you receive

• an MPID and an effective date
• the two agreements, signed by them first
• published prices, schedules, notices
• Default Notices, Credit Cover Increase Notices, Warning Notices
• statements, invoices, self-billing invoices
• accession on the public register (so counterparties can see you exist)

To the System Operator you send

• acknowledgements of instructions
• availability revisions (“the plant is down from 14:00”)
• constraint declarations (“do not dispatch me above X MW”)
• reserve certification requests
• Instructed Energy disputes
• optional event-subscription callback

From the System Operator you receive

• the constrained scheduling model (zones, corridors, headroom)
• dispatch, curtailment, outage, reserve, system-condition instructions
• Instructed Energy traces
• certification decisions (on the SO Registry; you see the result on Standing Data)

There is no “call the MO” button and no “call the SO” button. Every verb above is a control on a screen in this volume, or an API operation on the API page you open from Market › Info.

2.6 Three facts that stop most arguments

1. One price for the country, per hour. The day-ahead SMP is not per zone. Zones belong to the System Operator. They cap flow. They do not mint a Johannesburg price and a Cape Town price.
2. Clearing is not paying. Schedules and prices publish at 14:00 on D−1. Cash leaves bank accounts on the Settlement Calendar, weeks later. Daily numbers on Market Month are a preview, not a payment.
3. An instruction does not rewrite the bid. The IDM re-uses the day-ahead curve and moves volume for hours that have not started. A curtailment moves what you must physically do. The original crate price stays.

The next chapter is the map of the five rooms — which sidebar item, which tabs, which office you are talking to when you press it.

3. The five rooms

The organisation sidebar is Configuration, a row of its own at the top, and four collapsible modules — the lives the platform actually has:

The rows are short because the module says the rest. TRADING › Month is the room this volume calls the Market Month (its page is titled After Delivery); MONEY › Room is the Money Room; CARBON › Tax and Market are the carbon tax and the carbon venue. Two rows read Market — SAWEM’s and carbon’s — and the module above each one tells them apart.

Each module is a row with an icon tile and a chevron, and the row is a button: click it to open or close that module. Its rooms are indented beneath it, and the room you are in is a solid amber chip. The module holding your room opens itself, so the chip is never hidden. A closed module still shows an amber number — the sum of what is waiting inside it — so a life you have folded away can still wave. Your open/closed shape is remembered per organisation in this browser.

The action bar sits under the brand: Sign out, and the chevron that narrows the sidebar. Under it, your organisation chip. Under that, Quick jump — type and the sidebar filters as you go: matching rooms, or every room of a module whose name matches, with the matching modules opened for you. Esc or the × clears it.

Collapse the whole sidebar with the chevron and the module rows disappear: an 80 px rail of room icons with hover tooltips.

Learn the chrome once. Every market room reuses it: organisation header, page title, one-sentence description, flash (green info or red error), and the tab bar belonging to that room.

3.1 Why the menu is in this order

The sidebar is not an alphabet. Inside a group it follows the operating clock.

1. Market — may you be here at all? Membership, cover, inbox, register.
2. Bid Desk — what are you doing about tomorrow and today?
3. Month (the Market Month; the room is titled After Delivery) — what actually happened this month?
4. Accounts — where is the cash and the cover?

Cross-border pool trading is not a Trading room in this release.

Billing is the fifth room of this volume — what document do I show finance? — and it sits one module down, in MONEY, beside the Room: the document lives with the picture of how you are doing.

A badge in the sidebar means attention, not inventory. Deals counts proposals waiting, negotiations live and disputes needing you; Certificates counts batches to review. How many sites or pools you own is written on the room label itself, in brackets — OffTaker Sites (n), IPP Sites (n), Trader Pools (n) — and it counts every site or pool the organisation holds, whatever its status: the same number as the N sites or N pools chip in that room’s top bar (and, on IPP Sites, its Sites (n) tab).

3.2 Shared chrome

A Trading Day picker is a calendar day. A month picker is a Billing Period. Default trading date: before 10:00 SAST the picker often offers tomorrow (you are still in D−1); from 10:00 it offers today. Default billing month: usually the previous calendar month once the current one is still open.

3.3 The sidebar, item by item

Path prefix: /org. Module: TRADING, except Billing, which is in MONEY. The room column is the page title where it differs from the sidebar row.

Trading Units and Balancing Groups no longer have a sidebar row of their own; the live list they become is Market › Registry, and the planner is taught with them in V9 §3.3 · V9 §3.6.

Former Bid Desk paths /org/brp/bid-desk/settlement and the old /org/brp/imbalance redirect to Bid Desk › Settlement and Imbalance. /org/brp/bid-desk/month and /org/brp/reconciliation land on Market Month. Bookmarks still work.

3.4 Which office you are talking to

Not every room talks to both offices.

3.5 A week on the clock

Use this as a standing rhythm, not a legal timetable. Gates and business-day counts live in V9 and V1.

Monday–Friday, before you are ACTIVE. Live on Market › Info. Answer information requests. Sign agreements. Notify accounts. Do not open Bid Desk expecting a submit that will stick.

Every D−1. Bid Desk › Submissions by 10:00. Then Daily to watch publication. Notices if something broadcast.

Every Trading Day. Bid Desk › IDM for the hours still left. Notices and SO for instructions. Acknowledge the same day.

Every morning after delivery. Bid Desk › Settlement for yesterday. Imbalance if the hour looks wrong. Market Month as the days accumulate, and when the monthly file arrives.

Every 17:00 assessment, and at month-end. Accounts for cover and cash. Billing for the document finance will file.

The next seven chapters are Market — the membership desk — tab by tab.

4. Market — the membership desk

Screen: Market (/org/brp). Sidebar icon: building-library. You land on the Info tab.

Market is one sidebar item with six tabs. Bid Desk and After Delivery used to share this neighbourhood; they are now their own sidebar items. The published interface for machines used to be a seventh tab; it is now a link on Info. Everything that answers who you are, whether you may trade, and what the two operators have told you still lives here.

Think of Market as the club reception. Info is the membership application. Account/Cover is the deposit the club holds. Notices is the pigeon-hole. SO is the sports-ground steward. Registry is the list of which lockers you hold. Standing Data is the medical certificate for each player. The letterbox for systems that do not use the front door is API, opened from Info — it is not a desk you work every morning.

You cannot skip reception and go straight to the trading floor. A Bid Desk without an ACTIVE registration is a desk that will not submit.

4.1 The tab bar

Nav #market-nav, aria-label Market. Each tab is #market-tab-{id} with an icon and a label.

API is not on this bar. On Info, link #market-api-link (label API, code-bracket icon) sits to the right of the tabs and opens /org/brp/api. Old bookmarks to that address still open the same page. While you are there, the six tabs stay visible and none of them is current. The sticky bar reads API. Taught in §11.

The page shell is #market-page. Title Market. Description changes slightly with the tab; Info’s is Balance-responsible-party registration, the books it balances and SAWEM compliance.

4.2 Empty, loading, and “not yet a party”

Several tabs refuse to work until a BRP registration exists. They all say so in the same voice: a dashed empty card, a short reason, a Register link back to Info.

Async sections show a compact navy spinner (section_loading) with a label such as Loading registry stats…. Wait for the card. Clicking again does not hurry the Market Operator.

4.3 The membership-card metaphor

One organisation, one BRP registration. That card is the legal container. Trading Units are what the market schedules. Strategy books (trader / IPP / off-taker) are how you organise work. A book that is not attached to the registration is a book the Bid Desk cannot submit for.

%%{init: {"themeVariables": {"fontSize": "18px"}, "flowchart": {"nodeSpacing": 32, "rankSpacing": 40, "padding": 12}}}%%
flowchart LR
  O["Organisation"] --> R["BRP registration<br/>one card"]
  R --> TU["Trading Units<br/>what the market schedules"]
  R --> BK["Books<br/>how you plan"]
  TU --> POD["Points of Delivery<br/>meters, pairing"]
  TU --> SD["Standing data<br/>what the plant can do"]

Info creates the card. Registry and Standing Data fill it. Account/Cover proves there is money behind it. Notices and SO are how the two offices talk to the card once it exists. API is how a machine talks as the card. You open that letterbox from Info; it is not one of the six desks.

Follow along. Seat: any seeded org that already has a BRP (most full_demo organisations do). Path: Market. You should see six tabs and, on Info, an API link to the right of them, plus a header with a BRP code, a status badge, and a View Registration button. If you see Register as a Balance Responsible Party instead, you are on a seat that has not filed yet — §5.1.

The next chapter is Info, field by field and button by button.

5. Market · Info

Screen: Market → Info (/org/brp). Tab #market-tab-info. This is the membership application, the membership card, and the day-to-day answer to may this seat bid today?

The Market Operator sits on the other side of every button on this tab. The System Operator does not.

To the right of the tab bar, link #market-api-link (API) opens the machine letterbox at /org/brp/api. It is on Info only. Account/Cover does not show it. A person working the membership card can ignore it. A system that bids without a browser starts there — §11.

Follow along. Seat: an organisation without a BRP if you want the empty CTA; or OffTaker C / a trader if you want a live card. Path: Market → Info.

5.1 No registration yet

When @registration is missing, Info is a single dashed card #brp-register-cta.

That click opens the create wizard (§5.8). Nothing is sent to the Market Operator until you press Register as BRP on a complete application.

5.2 The stats strip

When a registration exists, six cards sit in #info-registry-strip. They are a dashboard, not buttons — each is a reading of work that lives on another tab.

Loading placeholder: #market-info-stats-loading — Loading registry stats….

5.3 The registration header

Card #brp-registration-header. This is the membership card as worn on the jacket.

5.3.1 Top band

Operational buttons on the band

When status is SUSPENDED, a note #suspension-lift-is-section-six explains: Lift of this suspension is a clause 6 Market Governance Committee action — not an applicant self-service. There is no “unsuspend myself” button. That is the Market Operator’s (and the Committee’s).

5.3.2 Details grid

Block #brp-registration-details. Read-only facts, plus one editable limit.

5.4 The application board

Section #brp-application-status. When: a registration exists and application_state is not ACTIVE. Once you are a trading Party the board hides: the header badge is enough.

Title: Your application. The badge is the fifteen-state machine. The explainer #brp-application-explainer is the exact sentence the Code-facing enum shows the applicant — not a paraphrase. Clock #brp-application-clock: Due + date; overdue or N business days left; yours or with the Market Operator.

5.4.1 What you see in each state

5.4.2 Information request — files and response

Shown when the MO has asked for further information (INFO_REQUESTED).

Clarification correspondence #brp-clarification-correspondence. Heading Information request. Each round: Question, Response, or empty Awaiting the applicant.

Supporting files #brp-application-files. Heading Supporting files. Each row #brp-application-file-{id}: title, filename, description. Links View and Download. Remove #brp-application-file-remove-{id} (remove_information_file) while you are still attaching.

Attach form #brp-info-attach-form (only in INFO_REQUESTED):

Response form #brp-info-response-form:

Flash after submit: Information submitted. The Market Operator has ten business days to review it.

5.4.3 Agreements list

Block #brp-application-agreements when agreements exist. Heading Your agreements. Each row #brp-agreement-{id}:

• Title: Market Participation Agreement or Balancing Agreement
• Reference · clause
• Signed-by copy when present
• Status badge ISSUED / SIGNED
• Eye button #brp-agreement-view-{id} — view (view_participation_agreement)

That opens the PDF modal (§5.9).

5.4.4 Action buttons

Each visible applicant action is #brp-application-action-{TARGET} with phx-click="move_application" and phx-value-target. Labels come from ApplicationFlow.action_label/1. Submit information is the form above, not a second button in this row.

Flash after Sign contracts: Both agreements signed. The Market Operator will approve them. After Withdraw: Application withdrawn. You may ask the Market Operator to reinstate it.

You cannot press Activate, Approve, Issue contracts, Request information, Decline, Suspend, or Revoke. Those labels exist on the Market Operator’s Participants board (V11 §21). The applicant LiveView refuses any other target with :not_permitted.

5.4.5 More time

When the clock is yours (INFO_REQUESTED or CONTRACTS_ISSUED) and you have not already asked:

Flash: Extension requested for N business days. The Market Operator must decide before the deadline moves.

#brp-extension-pending: An extension request is with the Market Operator. Your deadline has not moved until it is granted.

#brp-extension-refused: the request was declined; you cannot ask again for this clock.

5.4.6 History

Collapsible #brp-application-history, summary History (N). Timeline #brp-application-history-list. Each item is a transition: PENDING → INFO_REQUESTED on {date} by {name} (applicant|Market Operator) (N business days, due {date}). Automatic rows are worded by the daily clock / no one acted; the period lapsed.

5.5 Compliance card

Component compliance_view, root #org-compliance. Heading Market Code compliance (§6, §15). Loading: #market-compliance-loading.

This is not Account/Cover. It is the outstanding work and the two agreements, plus Default Notices.

There is no Notify Market Operator button here. That button lives on Account/Cover (§6.3).

5.6 Books balanced

Card #brp-books-balanced. Title Books balanced ({N}). Badge Unallocated when none attached. Note #brp-books-balanced-note explains Trading Units versus strategy books.

A book is how you plan (trader pool, IPP site, off-taker site). The registration is the market seat. Attach the book so Bid Desk has something to submit from.

Loading: #market-covered-books-loading.

5.7 What you cannot do on Info

Honesty is a feature:

• You cannot Activate yourself.
• You cannot lift a SUSPENDED seat.
• You cannot edit the filed wizard answers (view is read-only). Change standing data and units on their own tabs; change cover on Account/Cover and Accounts.
• You cannot notify the two settlement accounts from this tab.

5.8 The registration wizard

Modal #brp-registration-wizard (create) or #brp-registration-view (view). Eyebrow SAWEM §6 accession / BRP registration. Title Register as a Balance Responsible Party / Balance Responsible Party.

Think of six short rooms in a corridor. Click any step button #brp-wizard-step-{0..5}. Incomplete rooms show a warning; hover Still needed lists missing fields. Green means that step has what it needs.

Successful submit flashes BRP registration created. and closes. The seat lands PENDING / APPLICANT. The Market Operator still has to Activate.

5.8.1 Step 1 — Identity

Panel #brp-wizard-panel-identity. Heading Identity & roles.

5.8.2 Step 2 — Party

Panel #brp-wizard-panel-party. Heading Party classification.

Party-type cards #brp-party-type-*: Generator, Trader, Distributor, Transmission, Network Operator, Import/Export, Consumer, Reseller. A Retailer is not admitted on this path.

Qualifying criterion #registration-qualifying-criterion is derived from the type — the Annexure 1 doorway. Two toggles:

• Market participant (§2.1(135) — trades in DAM / IDM)
• Balance responsible (§2.1(14) — accountable through balancing)

A party can be balance-responsible without ever bidding. That is why there are two switches.

Where this is taught. Every field’s Code meaning is V9 §3.1. This chapter names the controls as built.

5.8.3 Step 3 — Trading

Panel #brp-wizard-panel-trading.

• Safety margin (R/MWh) — a cushion on your reservation prices
• Price taker (offers at the floor / accept the clearing price)

5.8.4 Step 4 — Security

Panel #brp-wizard-panel-security.

• Guarantee type — required if you are a market participant. Bank guarantee / Letter of credit / Cash (and None if you are not a market participant)
• Guarantee amount (R)
• Use recommended (R …) (use_recommended_guarantee)
• Warning Limit (R) (§2.1(225))

Letters of credit are modelled. This console’s enabled posted instrument today is cash in Collateral Reserve ([S28]). The wizard still records the legal form you intend.

5.8.5 Step 5 — Agreements

Panel #brp-wizard-panel-agreements.

5.8.6 Step 6 — Review

Panel #brp-wizard-panel-review. A definition list of the key fields. Create copy reminds you the seat will be PENDING. View copy is the same list, frozen.

In view mode every input is disabled. Register as BRP is hidden. Cancel reads Close.

5.9 The agreement PDF modal

Root #brp-participation-agreement-pdf-modal. Opens from the application board or the compliance View buttons.

You read. You do not edit the PDF here. Signing is Sign contracts on the board.

5.10 Info — operational button index

Every write on this tab, in one place.

Loading placeholders on the tab: #market-info-stats-loading, #brp-application-status-loading, #market-compliance-loading, #market-covered-books-loading.

6. Market · Account/Cover

Screen: Market → Account/Cover (/org/brp/account-cover). Tab #market-tab-account-cover. Icon: banknotes.

This tab is the deposit the club holds, not the wallet you spend from. The wallet — add funds, pay invoices, request a withdrawal — is Accounts (§14). Here you read the published 17:00 assessment, respond to notices, record replenishment arrangements and notify the Market Operator that the two settlement accounts exist.

Metaphor: the airport bank has already opened two accounts in the Market Operator’s name, on trust. This tab is the letter that says “yes, those accounts are ours, please record it” plus the nightly printout of how much cover they require.

Follow along. Seat: an ACTIVE demo BRP. Path: Market → Account/Cover. You should see the Required / Posted / Headroom strip, two account-balance cards, then Accounts and credit cover with a Notify Market Operator button per un-notified account.

6.1 Loading

Info-tab content (wizard, application board, books) is hidden on this tab. If you still see it, you are on Info.

6.2 Credit cover dashboard

Root #credit-cover. Read it in order: 1. Published cover position, 2. What needs attention, then 3. Settlement accounts. The publication date and daily 17:00 SAST label distinguish the assessment from current balances.

6.2.1 Stat cards #credit-cover-stats

The four compact cards are Required cover, Posted cover, Headroom and Warning limit. Each belongs to the dated assessment. Later deposits, payments and warning-limit changes appear in the next assessment.

How cover is calculated opens the method dialog, including its parameters and instrument restrictions. The notices below explain what needs attention; warning-limit changes use their own dialog. Cash is the enabled instrument today; modelled letters of credit remain disabled until enabled by the relevant market rules.

6.2.2 Account balance cards #cover-account-cards

Note the extra “and” in Trading and Clearing Account on these cards. The list below uses Trading Clearing Account. Same pot.

6.2.3 Empty assessment

#credit-cover-empty: No published credit-cover assessment yet. The figure on this page is the one the daily job wrote at 17:00 — not a live recompute.

6.2.4 Breakdown table #cover-components

Shown when an assessment exists.

Amounts are rands, monospace.

6.2.5 Notices on the assessment

Credit Cover Increase Notice #increase-notice (kind == CREDIT_COVER_INCREASE_NOTICE):

There is no button on the notice. Posting cash and paying an invoice are Accounts (§14). This card is how you know the clock started.

Warning Notice #notice-WARNING_NOTICE:

• Warning Notice — headroom {amount}
• {notice.note}
• Warning Limit {amount} ({clause}).

History table #cover-history (columns Business day, Required, Posted, Headroom, Notices) is wired in the component. This tab does not pass history today, so the table stays empty here. The same component on Accounts can show a trail.

6.3 Accounts and credit cover

Root #org-compliance-accounts. Heading Accounts and credit cover with a mono span §15.2, §15.10.

6.3.1 Per-account card

Each account: #org-compliance-account-{kind} where kind is TRADING_CLEARING or COLLATERAL_RESERVE.

The only operational button on this tab

After notice: #org-compliance-notified-{id} — Notified in writing on {date} — clause 6.2(11).

That is the letter to ticketing. Without it, accession cannot complete. Press it once per account.

6.3.2 Provider, windows, surviving obligations

6.3.3 Open a replenishment window

When you have permission to replenish by an agreed date, record that arrangement here. Replenishment arrangements sits beside the existing windows under What needs attention. The form has moved from Accounts.

flowchart LR
  A[Open replenishment window] --> B[Enter permitted dates]
  B --> C[Record the arrangement]
  C --> D[Review the refreshed window]

1. Choose Open replenishment window. The branded dialog opens over the page.
2. Supply Opened on and Closes on. You may also enter Reason and Reference. Use the permitted closing date; this workflow does not choose a duration for you.
3. Choose Open window. Missing required dates are refused. A backend refusal remains in the dialog so you can correct the fields. Cancel, the close button or Escape dismisses it without opening a window.
4. On success, Replenishment window opened confirms the record and the compliance details refresh. A currently open window appears in Credit-cover arrangement in progress.

Opening the window does not transfer money, post collateral or rewrite the published assessment. Clause 6.4(4) concerns suspension solely for absent cover during the permitted period; other obligations remain.

6.4 What this tab is not

Cash funding and payments are in Accounts. Statements & transactions opens Accounts → Statements. The replenishment form here records permitted dates; it is a compliance arrangement, not a payment.

Where this is taught. Why three pots exist, and which money is yours, is V9 §3.16. How a cover call is satisfied in cash is §14.

7. Market · Notices

Screen: Market → Notices (/org/brp/notices). Tab #market-tab-notices. Icon: megaphone.

Page description: Every notice issued to this BRP — Market Operator broadcasts, defaults, credit-cover calls, application updates and SO instructions for the selected month.

This is the pigeon-hole. Both offices drop paper here. The Market Operator drops broadcasts, defaults, cover calls, application updates. The System Operator drops dispatch, curtailment and outage instructions. You read the first kind. You Acknowledge the second.

Metaphor: a hotel front desk. Letters from accounts go in the same pigeon-hole as a note from the fire marshal. You may ignore a marketing flyer. You may not ignore the fire marshal.

Follow along. Seat: an ACTIVE BRP in a month that has been traded (full_demo). Path: Market → Notices. You should see a month picker and two cards: Notices (the table) and SO instructions.

7.1 Unregistered

Card #org-brp-notices-unregistered.

• Heading No BRP registration
• Body: Register as a Balance Responsible Party to receive market notices.
• Link Register → /org/brp

No pigeon-hole without a room number.

7.2 Month chrome

Panel #org-brp-notices-panel when registered. Heading Notices. Subtitle: Chronological inbox for {month}. Times are UTC.

Bar #org-brp-notices-month:

Deep-link with ?month=2026-07.

7.3 The notices table

Columns: Date, Kind, Notice (#org-brp-notices-col-*). Each row #org-brp-notice-{id}: timestamp, a kind badge (notice.label), body text (notice.body).

There is no Acknowledge on this table. Market Operator broadcasts are read, not signed for. Credit-cover calls still need action — that action is on Account/Cover and Accounts, not a stamp here.

7.4 SO instructions card

Same month as the table above. Loading: #org-brp-so-instructions-loading — Loading SO instructions….

Card #org-brp-so-instructions. Heading SO instructions. Subtitle: Dispatch, curtailment and outage instructions issued in {month}. Same month as the notices table.

Each row #so-instruction-{id}.

Kind badges: Curtailment · Planned outage · Unplanned outage · Dispatch constraint · Reserve · System condition.

Reason #instruction-reason-{id}: labelled reason, or reason not stated.

Effects (curtailment pattern): {MWh} MWh curtailed · deemed R {…} · imbalance excused R {…}. Otherwise —.

Status / actions

Acknowledge is a round-trip to the System Operator, not a local tick. Success flash: Instruction acknowledged. Failure flash: Acknowledge failed (…). Retry — the local stamp is only a projection of a round-trip.

Press it. The tower needs to know the cockpit heard. An archived instruction is end-of-day history; you cannot ack it after archive.

Where this is taught. What an instruction is, and why missing one under SO-controlled is a breach, is V12 §3. The map those instructions are issued against is §8. The Bid Desk also shows a system condition banner; that is context, not this table.

7.5 Notices — operational button index

8. Market · SO

Screen: Market → SO (/org/brp/so). Tab #market-tab-so. Icon: signal.

Page description: Constrained scheduling model, instructed energy and dispatch control. SO instructions live on Notices.

This is the tower radio and the wall map. Instructions you must sign for live on Notices (§7.4). This tab is the map those instructions are issued against, the Instructed Energy trace, whether a unit is under SO control, and the forms you use to tell the tower the plant changed.

Follow along. Seat: an ACTIVE BRP with Trading Units in named zones. Path: Market → SO. You should see Constrained scheduling model, then a metrics row of three cards: Instructed Energy, Dispatch Control, Instructions Reasons.

8.1 Unregistered

The same empty pattern: No BRP registration. plus Register. Instructed Energy still renders an empty card so the layout does not collapse.

8.2 Constrained scheduling model

Section #so-network-model-panel. Heading Constrained scheduling model. The body explains §3.3(4) and the two-month revision notice: the System Operator publishes a coming model so you can check your units against a boundary change before it invalidates a registration.

Loading: #so-network-model-loading — Loading network model….

A provisional banner [data-role=model-provisional-banner]: Not an SO declaration — do not plan against these figures. plus the blockers. Treat it as a sketch, not a clearance.

Empty [data-role=model-empty]: No zone model is loaded, so the System Operator’s network model cannot be shown.

If none of your units declares a zone: [data-role=no-zones-of-mine] — None of your Trading Units declares a Network Zone yet… Open the map to inspect the full System Operator model.

8.2.1 Action bar #so-action-bar

View all zones shows when you are a BRP, the model is loaded, and zones exist.

8.2.2 Zone tabs and the featured card

Nav #so-zone-nav. Label Select Zone:. Chip Active Model: N-1 Derated. Each tab #so-zone-tab-{code} (select_featured_zone).

The featured card #network-zone-{code}:

• Zone name; badges Your zone and Provisional when they apply
• Tiles: Export Capability, Import Capability, Net Trading Headroom, Corridors Active
• Sections Corridors / SAPP Interconnectors
• Empties: No active corridors for this zone. / No interconnectors present.
• Isolated: Not represented in any corridor in this model…

Basis chips: declared / assumed / no data. Hub labels: Deficit Hub / Surplus Hub / Balanced.

Footer counts: Corridors: · Interconnectors: · optional Not represented in any corridor:.

8.3 Metrics row

Row #so-metrics-row when registered.

8.3.1 Instructed Energy #instructed-energy-view

Heading Instructed Energy. This is the path the tower published for the unit in the period. Imbalance will be measured against it.

Flash on dispute: Instructed Energy dispute {id} filed (clause 13.4.1(3)). Failure: Could not file the Instructed Energy dispute.

Press it when the published trace is wrong. Do not press it because you dislike the instruction — that is a different argument.

8.3.2 Dispatch Control #so-control-state

Loading: #so-control-state-loading — Loading control….

Heading Dispatch Control plus badge STAND-IN when the intraday schedule is standing in (clause 11.4(9)).

Footer Status: Automated dispatch loop inactive. or Units listed above are under System Operator control.

When the tower has taken the stick, the schedule is no longer the whole story. Instructed Energy is.

8.3.3 Instructions Reasons #instruction-reasons

A catalogue, not a live feed. Heading Instructions Reasons. Each row #instruction-reason-{code}:

Each carries its clause. Use the same codes on the revision and constraint forms.

8.4 Missing-instruction breach

Alert #missing-instruction-breach when breaches exist. Title Missing instruction under so_controlled (clause 11.4(10)). Body: the standing schedule is not a fallback once the unit is under SO control — the tower must keep instructing. This is the expensive silence.

Availability revisions that have been lodged list as #availability-revision-{id}: {tuid} · {clause} · {id}.

If you subscribed to events, #event-subscription-id shows the id.

8.5 Consolidated dispatch report

Section #dispatch-report when a report exists and you expanded it (View Consolidated Report). Heading Consolidated dispatch report (clause 14.2(1)).

Columns: Trading Unit, Control State, SO Instructions, Reasons, Status. Empty: No dispatch report rows for this trading date. Reason chip NONE. Footer Showing N trading unit(s) and a reference. Rows #dispatch-report-{unit_key}.

Collapse #dispatch-report-collapse (toggle_dispatch_report).

8.6 Event Subscription modal

@so_modal == :event_subscription. Dialog #so-event_subscription-modal (dom #event-subscription). Backdrop / Escape / Close / Cancel all close_so_modal.

Help #event-subscription-fallback: Poll-by-refresh is the §16(2)(f) fallback — GET /events?since= remains the system of record.

Form #event-subscription-form (subscribe_events):

This is how a machine listens. A browser tab that you refresh is the fallback, not a second truth.

8.7 Constraint declaration modal

Opened by Constraint Deletion (the control’s label; the form declares a constrained MW). Dialog around #constraint-declaration.

Form #constraint-declaration-form (submit_constraint_declaration):

Tell the tower a cap. Do not wait for them to discover the line is short.

8.8 Availability revision modal

Revision submission. Form #availability-revision-form (submit_availability_revision):

The plant is down. Say so before the tower dispatches it.

8.9 Zones map modal

When View all zones is pressed and the model is ok.

On this seat the compact cards are not a second selector (selectable? defaults false). The featured-zone tabs on the page are.

8.10 SO — operational button index

Handlers set_tab / search_archived still exist on the LiveView. The active/archive feed UI moved to Notices. Do not look for those tabs here.

Where this is taught. The SO console that issues these artefacts is V12. Zones as a concept: V12 §2.

9. Market · Registry

Screen: Market → Registry (/org/brp/registry). Tab #market-tab-registry. Icon: identification.

Page description: Trading Units, Points of Delivery and the counterparty inbox.

This is the locker list. The Market Operator keeps the register the whole market trusts. You declare units and meters. The other party must confirm that a meter you named is actually theirs. Until they do, that energy cannot settle.

Metaphor: two neighbours sharing a garden tap. You file “the tap on the fence is also theirs.” They must sign “yes, that’s ours.” An unsigned tap is water nobody can bill.

Follow along. Seat: a demo BRP that has Trading Units. Path: Market → Registry. You should see Counterparty inbox, Trading Units table, and Points that cannot settle yet.

9.1 No party

#registry-no-party: This organization has no Balance Responsible Party registration, so it has no market registry yet. A Trading Unit belongs to a party, not to a site. Link Register.

9.2 Counterparty inbox

Card #registry-counterparty-inbox. Loading: #registry-counterparty-inbox-loading — Loading counterparty inbox….

Heading Counterparty inbox — plus count #registry-inbox-count and §7.1(6). The Market Operator must inform the other party when a Point of Delivery is added or removed. This inbox is how they answer. Without it every point would sit at PENDING_RECIPROCITY forever.

Empty: Nothing waiting on you.

Each notification #registry-inbox-{id}:

• Electrical node
• Badge added or removed
• … names you as the counterparty, effective {date}.

Flash on confirm: Declaration confirmed — the Point of Delivery is now paired. Failure: Could not confirm that declaration.

Confirm is the neighbour signing. Dispute is “that tap is not ours” with a reason. Leaving it sitting is how settlement incidents are born.

9.3 Trading Units table

Card #registry-trading-units. Loading: #registry-trading-units-loading. Heading Trading Units — plus #registry-unit-count.

Empty: None registered yet. Trading Units says how many you need. (That planner is Units/Groups in the sidebar.)

Table #registry-trading-units-table. Columns (#registry-trading-units-col-*): TUID, Name, Zone, Status, Class, MCR, Standing data, Counterparty, Actions.

Each row #registry-unit-{tuid}. MCR as {n} MW. Counterparty — if none.

9.4 Points that cannot settle yet

Card #registry-exceptions. Loading: #registry-exceptions-loading. Heading Points that cannot settle yet.

Two subsections, always rendered:

Energy through an unpaired meter cannot be settled. The market does not stop the rest of the day for one tap; it reports the incident. Your job is to drive both lists to None.

9.5 Trading Unit drawer

Opens from View. Root #registry-tu-drawer-root.

9.5.1 Points of Delivery tab

Section #tu-pod-pairing-{tuid}. Heading Points of Delivery plus §7.1(6) · §12.3(1).

Add fields: Electrical node, Meter device number, Meter remote access id, Site (location) prompt — pick a site for GPS —, Counterparty (optional) prompt — pair later —.

Flash on add: Point of Delivery added. or Point of Delivery added. Pairing is still pending.

9.5.2 Effective Modification tab

Section #tu-modification-{tuid}. Heading Effective-dated modification plus §7.1(5). Cutoff copy #tu-modification-cutoff-{tuid}: changes after 08:00 SAST on D−1 do not make tomorrow’s schedule.

Form #tu-modification-form-{tuid} (submit_modification):

Flash: Modification dated {ISO date} — a new row, not an in-place edit. A cutoff error returns the message from the domain. This is a new version, like issuing a new locker key dated next Monday — you do not engrave over yesterday’s key.

9.6 Registry — operational button index

Balancing Groups are not on this page. They live on Units/Groups.

Where this is taught. Why a Trading Unit is not your book, and how Balancing Groups net, is V9 §3.3–§3.6. The Market Operator’s register board is V11 §22.

10. Market · Standing Data

Screen: Market → Standing Data (/org/brp/standing-data). Tab #market-tab-standing-data. Icon: clipboard-document-check.

Page description: What each Trading Unit can physically do — and who has to answer for the parts nobody has.

This is the medical certificate for each player. About thirty facts per plant. Most of them are not in any database. The screen’s job is not to shout “invalid”. It is a work list: what is missing, which clause requires it, and who supplies it — plant engineer, System Operator, or finance. Those three work on different clocks. The System Operator’s is the longest.

A zero that is true and a zero that is a placeholder are different numbers. Every field shows its clause and its provenance so you can tell them apart.

Follow along. Seat: a generator BRP in full_demo. Path: Market → Standing Data. You should see metric cards, an IPPs table, Register generator site / Register off-taker site, Fleet CSV, and zone-gap desk.

10.1 No party

#standing-data-no-party: no BRP, so no standing data. Register.

10.2 Fleet list (no TUID selected)

Header actions:

10.2.1 Metric cards #standing-data-metrics

10.2.2 IPPs table #standing-data-ipps

Subtitle: Registered Independent Power Producer… Search #standing-data-ipps-search / #standing-data-ipps-search-input, placeholder Search site, TUID, BRP ref… (search_ipps).

Columns: IPP / Site, Organisation, BRP Ref, TUID, MCR, Fields, Actions.

Row action View #ipp-view-{unit.id} → /org/brp/standing-data/{tuid}.

10.2.3 Fleet CSV #standing-data-csv

Heading Fleet CSV · Batch Import/Export. Drop zone: Drag & drop fleet CSV file here, or browse.

Use this when the plant engineer lives in a spreadsheet. Provenance still has to be honest after the upload.

10.2.4 Zone gaps #org-zone-gap-desk

Heading Sites the provisional map cannot place. Clause § 3.3(4)(a). Empty: All sites placed successfully.

A site the map cannot place is a unit the register cannot honestly zone. Fix GPS / site, or wait for the SO model to cover the gap.

10.3 Plant detail /org/brp/standing-data/:tuid

Section #standing-data-detail. Back #stand-data-back returns to the fleet. Title #standing-data-detail-title plus TUID chip and status (for example Grid Active).

Request Certification #request-certification-open (open_request_certification) — the System Operator must agree reserve capacity. Until certified, reserve is 0.000 and availability indicators in submissions are forced to U.

Completeness gate #standing-data-completeness / #standing-data-incomplete: {tuid} cannot be registered… until the work list is clear. This is the gate Bid Desk will feel.

Callout inside #standing-data-editor: Data Provenance Mandate · §7.2(q)–(t) Standard.

10.3.1 Detail tabs #stand-data-tabs

Query ?tab= on the TUID URL.

Group panels: #standing-data-group-{capacity|start_up|run_limits|ramp_rates|reserve|settlement|classification}.

Each field is a tile #standing-data-field-{key} with Record #…-record (supply_field). You supply a value and a provenance. The tile shows the clause. Recording flashes {label} recorded as {provenance label}.

That is the whole editor: not a red “invalid”, a work list you tick with honest provenance.

10.3.2 Certified reserve table

Rows #standing-data-reserve-{category}. Columns: Capability, Clause, Certified, Status, SO reference, Indicator.

Categories: Regulating, Instantaneous, Ten-Minute, Synchronous Condenser Operation (§7.2(q)–(t)). Not self-declared.

10.3.3 Request Certification modal

#request-certification-modal / form #reserve-cert-request. Title Request Certification Form.

The decision is made on the SO Registry queue (V12 §6). You see the result here as a certified MW and an SO reference.

10.3.4 Storage and energy-constrained profiles

When the unit is storage: #storage-profile-form, submit Record storage profile #storage-profile-submit.

When energy-constrained: #energy-constrained-profile-form, submit Record energy-constrained profile #energy-constrained-submit.

These are standing shapes, not a day’s bid. The bid still goes out through Bid Desk.

10.4 Generator onboarding wizard

Component #site-onboarding / #site-onboarding-wizard. Title Register generator site #site-onboarding-title.

Steps: Site · Identity · Zone · Delivery · Engineering · Finance. Click any step.

This files a generator site and the first cut of its Trading Unit into the register. Standing-data completeness is still the work list on the detail page.

10.5 Off-taker onboarding wizard

#offtaker-onboarding / #offtaker-onboarding-wizard. Title BRP Standing Data OffTaker Registration.

Steps: Identity · Zone · Delivery · Demand · Finance. Same button pattern: #offtaker-onboarding-{back|cancel|continue|register}, step tabs #offtaker-onboarding-tab-{step}.

10.6 Standing Data — operational button index

Where this is taught. Why thirty attributes, who supplies each, and the completeness gate as a work list is V9 §3.7–§3.8. This chapter is the controls as built.

11. Market · API

Screen: Market → Info → API (/org/brp/api). Link #market-api-link on Info. There is no API tab. Icon: code-bracket.

Page description: Published SAWEM OpenAPI for System Operator dispatch and Market Operator trading, settlement and registry.

This is the letterbox for machines. The same published document the operators read at GET /api/v1/publication/openapi, split into two cards so you open the office you mean.

If your desk is a human on these screens, you may never press this link. If your balance-responsible system submits bids and acknowledges instructions without a browser, this is the map of what that system may call. The full contract is V13.

The six membership tabs stay on the page. None of them is highlighted. The sticky bar heading is API (#org-page-heading). Use a tab to go back to a desk.

Follow along. Seat: any organisation. Path: Market → Info, then API at the right of the tab bar. Two cards: SO APIs and MO APIs. Press Open API Swagger on either.

11.1 SO APIs card

Article #org-brp-api-so. Heading SO APIs. Navy accent.

Body: Dispatch instructions, acknowledgements, Instructed Energy, availability revisions and the constrained scheduling model (§11, §13.4.1, §3.3). Tags: Dispatch, Events, Network zones, Network model.

Button #org-brp-api-so-swagger (open_swagger surface=so):

• Idle: Open API Swagger (navy)
• Open: Hide API Swagger (gold)
• aria-expanded / aria-controls="org-brp-api-swagger-panel"

11.2 MO APIs card

Article #org-brp-api-mo. Heading MO APIs. Gold accent.

Body: Party registry, standing data, day-ahead and intraday markets, metering, balancing and financial settlement (§6–§10, §12, §13, §15). Tags: Party registry, Standing data, Day-ahead market, Intraday market, Metering, Balancing, Financial settlement.

Button #org-brp-api-mo-swagger (open_swagger surface=mo): same Open / Hide API Swagger pattern. Opening MO while SO is open switches surface; pressing the open button again hides.

11.3 Swagger panel

Panel #org-brp-api-swagger-panel when a surface is open. Title #org-brp-api-swagger-title is SO APIs or MO APIs. Close #org-brp-api-swagger-close (close_swagger).

Operations are grouped by tag #org-brp-api-swagger-tag-{slug}. Each operation #org-brp-api-swagger-op-{id}:

This is in-place documentation, not a console that fires live calls with your session. Integrators still authenticate as in V13. Every write on the Market API still needs an idempotency key; every response still carries X-Sawem-Server-Time because your clock is not the gate.

11.4 API — operational button index

Section #org-brp-api is a two-column grid on large screens, stacked on small ones.

That is the last Market tab. The remaining chapters are the other four sidebar rooms, mapped tab by tab, with the arithmetic still taught in V7 and V13.

12. Bid Desk — tomorrow’s ticket and today’s patch

Screen: Bid Desk (/org/brp/bid-desk). Sidebar icon: presentation-chart-line. You land on Daily.

This is the organisation’s Bid Desk — the trading floor. Everything you tell the Market Operator about tomorrow, and everything you patch while today is still running, happens in this room. You do not telephone anyone. You do not edit the country’s price. You send a sealed note, you wait for the auction, and — if the weather or the load has moved — you send a smaller note for the hours that have not yet started.

From Daily you walk into five rooms that share a Trading Day and a Trading Unit: Submissions, IDM, Forward, Settlement and Imbalance. The month wallet lives on Market Month (sidebar: After Delivery, §13). This desk talks to the Market Operator. The System Operator appears as current system context and instructions that overlap the selected day.

Where this is taught. How a net position becomes a ladder, how 168 periods are validated, how a missed gate rolls over, and how IDM money is priced: V9 §4 and V9 §5. This chapter is the organisation screen in ordinary English — what you are looking at, why Daily, Submissions, IDM, Forward, Settlement and Imbalance are separate rooms, and which button to press.

Follow along. Seat: an ACTIVE BRP with a book attached (Market → Info → Books balanced). Path: Bid Desk (/org/brp/bid-desk). You land on Daily. There is no tab strip. You should see a navy organisation header, a white Delivery date control, a four-stage lifecycle, three connected summaries, an hourly energy chart and a row per Trading Unit.

The month wallet and the monthly file-join are not this chapter — §13.

12.0 The problem this desk solves

Your organisation has plants, customers, or both. Strategy has already worked out, hour by hour, whether you will have leftover energy (long) or a gap you still need to fill (short). That leftover or that gap is your net position.

The rest of the country does not know your book. The Market Operator runs a shared marketplace so leftover energy can find a buyer, and so a gap can be filled, at one price for everyone that hour — the System Marginal Price (SMP).

Somebody has to tell the marketplace, before tomorrow starts, what each of your Trading Units can do. And somebody has to patch that story when the forecast was wrong and the hour has not yet begun. That somebody is you, on this desk.

Think of a produce market that writes tomorrow’s crate list the night before.

You are a farmer, a grocer, or a wholesaler. You do not shout a price in the hall. You write a sealed note: how many crates you can sell (or take) in each hour, and the worst price you will accept. At a fixed time the auctioneer opens every note, fills demand from cheapest supply, and announces one crate price for that hour. After that, the list is locked — except for five smaller windows during the day where you may change remaining hours only, and changing your own mind is charged differently from being moved by the traffic officer on the road.

That night-before auction is the Day-Ahead Market (DAM). Those five smaller windows are the Intraday Market (IDM). This desk is where you write both notes.

12.0.1 What the Bid Desk does — and what it does not

It does six jobs. Daily (/org/brp/bid-desk) is the front door. Submissions, IDM, Forward, Settlement and Imbalance are the next rooms — you walk into them from Daily (or, once you are in one of those rooms, from the tab strip). Each destination room is one Trading Day and one Trading Unit.

1. Show you the day. Have your units spoken? Has the Market Operator published? Is the next IDM gate still open? That is Daily — a scoreboard. You do not type a bid here.
2. Send tomorrow’s note. Rebuild the draft from the latest strategy run, check it against the same rules the Market Operator will run, and Submit a 168-period Submission for one Trading Unit. That is Submissions (/org/brp/bid-desk/submissions) — the desk itself.
3. Patch remaining hours. Lodge a re-declaration, or change whether the Market Operator may move your day-ahead schedule in the five intraday auctions. That is IDM (/org/brp/bid-desk/idm).
4. Read what you already promised. A physical contract that was registered as a forward schedule is already on the wires. This room shows that promise and whatever the night auction still added on top. That is Forward (/org/brp/bid-desk/forward) — a scoreboard, not a register. You register the schedule from Deals (§18).
5. Read what last night’s auction did to you. After 14:00 the day before delivery, this room shows — hour by hour — how many crates cleared, at the one crate price, and which extra lines the wires or reserve added. That is Settlement (/org/brp/after-delivery). It is a receipt, not a bank transfer.
6. Compare the ticket to the meter. After the hour has run, this room asks: what did you promise, what did the System Operator tell you to do, and what did the meters actually record? You are charged on the difference, and the charge depends on who caused it. That is Imbalance (/org/brp/after-delivery/imbalance). It is a weighbridge, not last night’s receipt.

It does not post cover, pay an invoice, or edit the register. Those rooms are Accounts, Billing, and Market. The month wallet and the monthly file-join (the old Recon tab) live on Market Month (§13). It does not talk to the System Operator except to show the stress banner — you acknowledge instructions on Market › Notices. An Instructed Energy dispute on Settlement talks to the System Operator / DRB.

12.0.2 The Day-Ahead Market — booking tomorrow tonight

The Day-Ahead Market is one auction for tomorrow, run today. People say “daily DAM” because it happens every calendar day, for the next Trading Day. It is not a rolling chat. It is a deadline.

A useful picture is a theatre. Tonight you book seats for tomorrow’s show. Every hour of tomorrow is one scene. You do not book a single seat. You book a week of scenes at once — 24 hours × 7 days = 168 Trading Periods. The market wants a horizon, not a one-night stub. A 24-period body is the most common mistake and is refused as a horizon fault, not as “144 hours missing”.

You do not name the ticket price. Your curve says “I am willing to run this many megawatts at this cost.” The auctioneer stacks every offer from cheapest to dearest, fills demand, and the last offer needed sets the SMP. Everyone who cleared is paid (or pays) that SMP, not their own number. A cheap solar farm that offered R 0/MWh and a coal plant that offered R 900/MWh can both clear at R 900 in the same hour.

A worked picture — OffTaker C’s solar hour. A farm thinks it can produce 75 MW at 18:00 tomorrow. It sends that as Declared Available Capacity, with a cheap curve (renewables often offer at the floor). The market has enough demand. The unconstrained schedule gives the farm 75 MWh. The SMP that hour is R 900/MWh. The energy payment is 75 × 900 = R 67,500. That money is struck on the unconstrained number, even if the wires later cannot take it — the System Operator’s constraint is compensated separately. The arithmetic of that split is V9 §13. You need only this: Daily will later show that 75 MWh as Unconstrained, and a smaller number as DAM constrained if the wires were tight.

The gate is a door, not a hint. After 10:00 SAST on the day before delivery, the DAM will not take a first submission for tomorrow. A unit that stays silent is not left with nothing: the Market Operator rolls over yesterday’s accepted horizon — shifts it forward a day — so the country still has a number. That is a safety net, not a strategy. A rolled-over profile is a week-old guess wearing today’s date. The Submissions page tells you so, in a banner you cannot miss.

The 03:00 SAST worker on D−1 will send a draft you left sitting, if Auto DAM is on for this BRP (the default). Turn that off on Market → Info when you Submit yourself or when your own system PUTs the DAM. You do not have to sit here at three in the morning when Auto DAM is on. Submit on the screen is the same write path, for when you rebuilt after 03:00 or want the payload on the wire before the worker.

The Bid Desk tells you which way the seat is set: chip #bid-desk-auto-dam (Auto DAM · on / off) on Daily, Submissions and IDM; a sentence #org-dam-auto-submit on Daily and on Submissions; and the draft banner when a DRAFT is sitting. The chip links back to Market → Info.

12.0.3 The Intraday Market — five amendment windows, not a chat

Weather and load still move after 10:00. The Intraday Market is how you tell the marketplace that remaining hours will look different. It is not a second DAM. It does not rewrite last night’s bid, and it does not change the DAM price. It re-uses the day-ahead curve and changes volume.

A useful picture is a train timetable. Last night you published tomorrow’s trains (the DAM). During the day you may issue amendments, but only for trains that have not yet departed. A train that left at 11:00 cannot be un-run at 12:05. There is no rolling “change anything up to 60 minutes before”. There are five auctions, at times that do not move:

Iteration 5 closes at 18:00, so it can move 19:00 and cannot move 18:00 — the hour whose delivery is beginning as the gate shuts.

Changing your own mind costs money; being moved does not. If the System Operator cuts you because the wires are full, you are compensated at your own offered price — which for a renewable that offered zero is R 0.00, and you keep the day-ahead energy payment. If you cut your own Declared Available Capacity because the cloud arrived, that reduction is charged flat at the Intra-Day Price. Your own cheap offer buys you nothing. That is the whole plot of the IDM page, in one sentence.

The same solar hour, continued. Heavy cloud at 11:30. Before the 12:00 gate (iteration 4) the farm re-declares 18:00 from 75 MW down to 20 MW — a 55 MWh story in the Code worked example is 60 → 20 after a network constraint, charged 40 × R 945 = R 37,800. The DAM ticket (R 67,500 on the unconstrained 75) is not torn up. The IDM adds a separate charge for the volume you took back. You read that charge later on Market Month, not on this desk. The money walk is V9 §5.2.

Consent is a separate door. Your day-ahead submission carries a flag: may the Market Operator move your schedule in those five auctions? Willing means yes. Non-willing means hold my DAM schedule unless the System Operator imposes a new network constraint. Changing consent does not silently change volume. Two forms, two buttons, on purpose.

12.0.4 Daily is the front door — there is no tab strip

/org/brp/bid-desk is Daily. The page does not have a Daily / Submissions / IDM tab bar. Mixing “how is my day?”, “write the 168-period note”, “patch hour 18”, and “read yesterday’s chalkboard” on one scroll would bury the gate, so those jobs live on separate URLs. You start here. Summary counts filter the unit list. A labelled unit action opens the workbench directly, with its date and TUID.

You share one trading date and (when you pick one) one Trading Unit across those rooms. Changing the date on Daily is the same date on Submissions, IDM, Forward, Settlement and Imbalance. The white Trading date bar is the clock on the wall: so you do not bid the wrong day, or after the door has shut.

On those rooms a small Bid Desk link (#back-to-bid-desk) brings you home to Daily. A tab strip #bid-desk-tabs lets you walk to the other rooms without going back first. Daily itself still has no tab strip.

The Market Operator reads the same day on Bidding (/mo/bidding) — V11 §13.5. You never sit in that chair from this app.

12.1 Your trading day — choose the date, then follow its progress

You need to know which day you are preparing, what still needs attention, and where to act. Your trading day puts those questions in that order. The overview remains separate from the workbench where you build, validate and submit a bid.

When you have no BRP registration, No BRP registration yet links to Registration. When your registration has no Trading Units, the overview explains how to add one. While evidence is loading, the page says Loading your trading day…. A failed load offers Try again.

12.1.1 The organisation header

The usual organisation header and Trading sidebar stay in place. The page heading is Your trading day. On a narrow screen, use the menu button to open the sidebar; the overview and its drawers fit the window.

12.1.2 Current market context

The compact context line shows a currently effective System Operator condition for your registration, with its SAST start time. If there is none, it says so. This describes the system now, even when you are looking at another delivery date. Market notices opens Market → Notices at /org/brp/notices.

A general notice does not stop a bid or change a deadline. A formally published gate extension appears beside the day’s decisions, with its reason, authoriser and publication time. A named-unit extension appears in that unit’s drawer and changes only its action; the next deadline names the unit whose extended gate will close. An SO instruction whose effective window overlaps the selected day is listed with its reference and times. Open the notices page to inspect the instruction before acting.

12.1.3 Delivery date and market clock

Choose Delivery date, or use Today and Tomorrow. This is the day energy is delivered. The day-ahead submission gate normally falls on the preceding day, D−1. The date travels with every unit action.

The Market clock reads South African Standard Time (SAST) from the server. Beside it, the next deadline names the actual market: DAM submission closes, or IDM 1 closes, for example. A published gate extension is included. After the last intraday gate, the page says there is no remaining submission gate for this day. Evidence and timing refresh once a minute; the countdown advances between refreshes.

12.1.4 The day lifecycle

The four stops explain how the same delivery day progresses:

flowchart LR
  A["DAM submission · D−1"] --> B["Publication and energy results"]
  B --> C["Delivery and intraday · D"]
  C --> D["Metering and imbalance"]

1. DAM submission. Read the closing date and time, then prepare or review each unit’s bid before the gate.
2. Publication & energy results. A closed gate does not mean results have been published. The page keeps Awaiting publication until the stored published result arrives.
3. Delivery & intraday. Read the selected day’s delivery hours and the next actual IDM gate. Review remaining-hour differences where the forecast and published position have a matching basis.
4. Metering & imbalance. After delivery, review published results and metering coverage. Missing or incomplete metering remains visible.

The workbench retains its detailed gate, draft and validation controls. They belong to the unit you open from this overview.

12.2 Daily — understand the day, then choose the unit

Follow along. Seat: Trader 1 in the seeded demo. Path: Trading → Bid Desk → Tomorrow. You should see the lifecycle, three summaries, the hourly portfolio chart and a row for each registered Trading Unit. Counts and deadlines depend on the selected date and the current server time.

12.2.1 Readiness and automation

Start with the summaries, then read the sentence naming the next unit that needs attention. Missing submissions take priority over rolled-over ones and other evidence gaps. The unit list itself stays in TUID order when data refreshes, so rows do not move while you read them.

Auto DAM · on/off appears below the list. Trading controls opens the existing controls page. Reading this overview, changing a filter or opening a drawer never sends a bid.

12.2.2 Three connected summaries

All units clears the filter. A count never opens an empty workbench without a Trading Unit. An empty filtered list says No units match this filter. It does not mean that the organisation has no units.

Before the DAM gate, attention includes missing submissions, rollover, forecast gaps and hours capped by bid limits. After the gate and before publication, review missing or rolled-over submissions. During delivery, review schedule gaps and comparable differences for hours a remaining IDM auction can still change. After delivery, attention turns to published schedule and complete metering coverage.

12.2.3 Your portfolio through the day

The 24-hour chart uses MWh on its vertical axis and SAST hours on its horizontal axis. The colour key sits centered under the plot. Green Long bars show forecast energy left over; amber Short bars sit below zero for forecast gaps. These are shown separately so surplus at one book cannot conceal a shortage at another. Each linked book is counted once, even when two Trading Units share it.

The coverage line states how many books are represented and how many units have no unique book or share one. Missing hours remain gaps. A stored zero remains zero. Partial coverage is not a complete portfolio forecast.

Use Chart scope to inspect one unit. Where a book maps uniquely to that unit and the registration has a single book, the chart can compare its residual forecast with the DAM schedule and Latest spot schedule. Shared books and registration-wide netting use a different basis; the page explains why it does not overlay them as a unit comparison.

Click a chart hour or use Inspect hour · SAST. The reading below gives the exact quantities and, for a unit, the forecast run and schedule’s publication time. Latest spot schedule starts at the published DAM quantity. Each published IDM update replaces only the hours it contains and is labelled with its iteration. It is not a relabelled DAM daily total.

A difference invites you to review the position. The overview does not claim that redeclaration is profitable or assign a financial penalty using assumed prices.

12.2.4 Comparable Trading Unit rows

Each row gives the official name, TUID, zone, class, latest submission sequence and its full horizon. A 168-period submission is a seven-day horizon, not 168 hours of the selected delivery day.

The exception appears beside that status. Details & destinations opens all exceptions in a right-hand drawer. The main action is labelled Prepare bid, Review submission, Review intraday or View settlement, according to the day’s stage. You can open it directly; there is no selection checkbox to unlock it.

Each small hourly profile uses the same vertical scale as the other unit rows. A larger shape therefore means a larger position. Its caption gives the number of forecast hours; a flat measured zero and a missing series remain different states.

The drawer contains Bidding, IDM and Forward, followed by Settlement and Imbalance under After delivery. All five links carry the selected delivery date and that row’s TUID. A linked book is also carried into the workbench. Close with the top-right X, the backdrop or Escape to return to the same list.

12.2.5 Hourly evidence and published energy results

The unit drawer’s hourly table keeps forecast, unconstrained schedule, DAM schedule, latest spot schedule and actual metering separate. It names the latest schedule’s source and each meter value’s vintage and completion state. Actual Energy is shown on its net-import basis; it is not silently subtracted from a book residual forecast. Where multiple vintages exist, the latest available revised, verified or provisional value is shown once.

Sources and submission evidence exposes the forecast run identifiers, publication times, book, submission and rollover parent, plus meter sources. The published DAM energy payment, Energy Payment (EPM), and any congestion adjustments are read separately. EPM is one energy settlement component. It is not portfolio profit or cash received.

Market context & benchmarks, beside the context line, opens a separate read-only drawer. It compares technology capture rates with a 100% baseload reference for the last 30 days. Each technology retains its benchmark date, coverage, metered-site count and evidence labels. Stale, profile-based and demo-price observations are labelled. Detailed benchmarks & provenance retains captured and baseload R/MWh, capture, cannibalisation and floor-share percentages, and the source and policy records. These historical observations are not forecasts for your selected delivery date.

Where this is taught. The meaning of technology capture rates is in V9 §21. Bid-building controls stay in §12.3; changing intraday positions stays in §12.4.

12.3 Submissions

Submissions (/org/brp/bid-desk/submissions) is the desk. This is the only Bid Desk page that writes a day-ahead Submission to the Market Operator. Daily is a scoreboard. This page is the booking office.

Think of Daily as the arrivals board at a station: who has spoken, is the timetable up yet, is the next train still boarding. Submissions is the ticket window. You come here to write the note for one Trading Unit, check it, and hand it over. A small Bid Desk link (#back-to-bid-desk) takes you back to the arrivals board.

Why its own page: Validate, Rebuild from latest run, and Submit are expensive buttons. They belong next to the 168-period grid and the book ladder, not next to a scoreboard. One Trading Unit at a time — a Submit that silently picked “the first unit on the register” would be the worst kind of helpful. There is no dropdown that defaults to unit A. If the Trading date bar still says Select a trading unit, Submit will refuse rather than guess.

Where this is taught. Field-by-field DAM bid: V9 §4. What a Submission is: V9 §4.8.

Two layers sit on this page, and they are easy to mix up. Picture a restaurant. The kitchen has already plated tonight’s leftover portions and stuck a cost on each plate. That is your work. The waiter then writes a ticket the dining room will honour. The market clears the ticket, not the kitchen plate.

Submit turns the first into the second and PUTs it. If curve emission fails, Submit refuses and says why. There is one write path. The 03:00 worker uses that same path when Auto DAM is on.

Follow along. Seat: an ACTIVE BRP (for example OffTaker C) with a book attached. Path: Daily → TU-IPP-A-PV → Prepare bid or Review submission. You should land on /org/brp/bid-desk/submissions?date=…&tuid=TU-IPP-A-PV. A tab strip #bid-desk-tabs lets you walk to IDM, Forward, Settlement and Imbalance without going back to Daily. The Trading date bar still shows the unit as read-only.

12.3.1 How you get here

On Daily, choose Prepare bid or Review submission on the unit row. You can also open Details & destinations → Bidding. Each route carries date=YYYY-MM-DD&tuid=TU-… and the linked book where one exists. You arrive at the workbench for that unit and day, ready to review the draft and the last accepted submission.

The summary counts on Daily filter its list; they do not open an unscoped workbench. Existing bookmarked Submissions URLs still work. Without a valid owned TUID, the workbench asks you to choose a Trading Unit and does not silently select the first one.

12.3.2 Gate open, gate closed, and still unpublished

Two clocks are easy to mash into one. They are not the same event. The theatre picture from §12.0.2 helps:

Between 10:00 and 14:00 the box office is shut and the printed tickets are not up yet. That stretch is normal. It is not a fault. You are looking at the note you already handed in (or at the empty desk if you never did). You do not yet have a crate price. Daily will still say Unpublished. The kitchen ladder’s SMP / Accepted / Result columns stay — / Pending until publication fills them.

What “open and not published” looks like on this page

Typical: 09:40 on D−1. You selected TU-IPP-A-PV. You have a DRAFT in the kitchen, or nothing yet. The auction has not run.

What “closed and not published” looks like on this page

Typical: 11:30 on D−1. Same unit, same date. The door shut at 10:00. The results board is still blank until about 14:00.

Rollover, in one picture. You missed the box office. The theatre does not cancel the show. It reprints yesterday’s seating plan, shifted one day. Day 7 of a long rollover repeats the source’s day 7, because there is no day 8 to shift from — the horizon is collapsing onto a single old day. The rose escalation line on the banner says so. Submit before the next gate.

Publication is the other light. When Daily’s Market results summary shows its publication time, then — and only then — the kitchen ladder can fill SMP and Accepted, the unit evidence drawer can fill Unconstrained / DAM, and energy money exists to read. Until that flip, Submissions is a ticket window, not a results board.

12.3.3 What you see from the top — chrome, banners, pre-flight

Read the page in the order it is drawn. The organisation header remains familiar. This workbench retains its detailed market notices, date bar and banners. Then:

The Trading date bar is the same clock on the wall, with two Submissions-only facts:

• Trading Unit is still read-only (#bid-desk-selected-tuid). There is no form #submission-desk-tuid and no dropdown on this page. You picked the unit on Daily (or in the URL). If you did not, it reads Select a trading unit.
• Book dropdown #bid-desk-book-form / #bid-desk-book appears only if this BRP balances more than one strategy book. It chooses which kitchen the ladder is built from. It is not on Daily. One book: the control is absent, because there is nothing to choose.

Then the workbench’s system condition and draft banners. Then #back-to-bid-desk. Then the body.

Pre-flight #submission-preflight sits at the top of the body, not inside the day-ahead table. Shown while the DAM gate is open. Navy left hairline. Heading Pre-flight. Button Validate #submission-validate (event validate_submission). Hover: Runs the Market Operator’s full validation set on this Trading Unit’s submission for this Trading Date — the same rules as a real submit. Does not lodge the bid.

This is the same function the real PUT calls (WB.Sawem.Submission.Validation). A pretty checklist that reimplemented the rules would drift, and the drift shows up as a participant told it is clean and then rejected at 09:59.

Validate does not lodge the bid. It does not reopen a closed gate. When the gate is closed, this whole banner is gone.

Until the panel has loaded, grey placeholders sit where pre-flight, the three cards, the curve, the ladder, and the day-ahead table will be. Wait. Do not re-click.

The rest of the page, top to bottom (wide screen):

1. Three cards in one row #org-dam-submissions-row — log, draft ladder, last accepted Submission.
2. Five price curve cards #submission-curve-editor (only once a Trading Unit is selected).
3. Attach-a-book empty state, if needed.
4. Book ladder — Rebuild, Submit, net-position chart, clips, certainty-equivalent card, hourly table.
5. Day-ahead submission (§9.3) — gate clock, rollover banner, seven-day selector, 24-row period table.
6. View payload modal, only after you click that action.

On a phone the three cards stack. Nothing is hidden in a side drawer. There is no #org-submission-drawer.

12.3.4 The three top cards

Row #org-dam-submissions-row. On a wide screen it is twelve columns: the log takes five, the draft ladder three, last accepted four. They are three different objects on purpose. Putting them in one row is the whole lesson: do not mistake the kitchen for the ticket, and do not mistake “we have a draft” for “the Market Operator has a Submission”.

Worked picture — 09:40, nothing sent yet. The log still lists TU-IPP-A-PV with — in Source / Seq / Consent / Horizon. The draft card may already say DRAFT · 24 kitchen line(s) because Strategy plated leftovers. Last accepted is empty on purpose. That empty pane is the sentence “we have not handed a ticket in.” If the draft numbers leaked into last accepted, you would think the market already had them.

Card 1 — Participant submissions log

White card #org-dam-submissions-log. Heading Participant submissions log.

Under the heading, sentence #org-dam-auto-submit (the same switch as the bar chip, written out so you do not miss it):

• Auto DAM on (the word on is emerald): Auto DAM is on for this BRP — the 03:00 worker will send a draft unless you Submit first. Then Change on Market → Info.
• Auto DAM off (the word off is amber): Auto DAM is off for this BRP — the 03:00 worker will not send. Submit yourself before 10:00, or the Market Operator will roll over. Then the same link.

Caption under that: Historical sequence of bids and availability updates. This table is a diary of what was stored for this Trading Date, not an editor.

Table #org-dam-submissions-table. One row per owned Trading Unit — except when a tuid is in the URL, the list is filtered to that unit only. Row id org-dam-unit-{tuid}. There is no TUID column. There is no Open. The action is View payload.

Worked row. TU-IPP-A-PV, you Submitted at 09:12. Class GENERATING. Source Participant. Seq 1. Consent yes. Horizon 168. Book bid SUBMITTED. View payload opens the note as JSON — useful when a colleague asks “what exactly went on the wire?”

Card 2 — Draft ladder

White card #submission-desk-draft. Heading DRAFT LADDER (uppercase). Caption: Kitchen leftovers — what the book priced. This is not what the market clears.

This pane is about the book, not about one unit’s MO ticket. Strategy ran. Some hours were leftover energy (long — you can offer). Some hours were a gap (short — you still need to buy). Those leftovers were priced into rungs. That plate sits here.

Rebuild and Submit are not on this card. They live on the book ladder further down (§12.3.7). This card is the reminder: leftovers are not a ticket until Submit turns them into one.

Card 3 — Last accepted Submission

White card #submission-desk-accepted. Heading LAST ACCEPTED SUBMISSION (uppercase). This is the ticket — the 168-period object the Market Operator will clear — for the selected Trading Unit and Trading Date.

History (only when a declaration is loaded). A small HISTORY list: each previous version as seq {N} · {source} plus an eight-character id chip. That is the paper trail — seq 2 replaced seq 1; you can still see that seq 1 existed. If this version was rolled over, the parent lives on that trail.

The three-card test. If the draft says DRAFT and last accepted is empty, you have not spoken to the market yet. If last accepted says seq 1 · Participant and the log Horizon is 168, the ticket is in. Publication can still be hours away.

12.3.5 Price curve — the five stat cards

Block #submission-curve-editor. Drawn under the three top cards and above the book ladder. It appears only once a Trading Unit is selected (no unit: these five cards are absent). It is not an editor sitting under the period grid, and it is not five boxes you save from. It is five readout cards with a coloured hairline along the top.

Heading Price curve (§9.3(4)(c)). Explainer: Five blocks. The first is what you must run at; the last is emergency capacity. The market pays everyone the same hourly price regardless of which block cleared.

Picture a staircase of how hard the plant is willing to work. The bottom step is “I must run at least this much” (a coal station that cannot go to zero). The top step is “only if the lights are going out” (emergency). The three middle steps are the ordinary climb. You are not naming the crate price. You are naming megawatts at each step. The auctioneer still posts one SMP for the hour. A cheap step and an expensive step that both clear are paid the same SMP. Your steps decide whether you clear and how far up the plant is asked to go — not the number on the invoice.

Five cards in a row on a wide screen (lg:grid-cols-5), two columns on a tablet, stacked on a phone. Each card is a white tile with a 4 px coloured top border, a tiny uppercase label, and a large mono megawatt figure.

Note #submission-curve-lock-note under the row: Mingen and Elbow 3 come from the registry and cannot be edited here — they are the two most common rejections, and both are authoring errors. To change them, modify the registry under §7.1(5) before the 08:00 D−1 cutoff.

Worked picture. Registry Mingen 20 MW, MCR 100 MW. Elbow 1 might read 40, Elbow 2 70, EL1 110. You cannot type 18 into Mingen on this page. If 18 is what the plant can really do now, that is a registry change before 08:00 D−1, not a clever edit at 09:50.

The three unlocked fields are text inputs in the markup so the values can sit in a form-shaped card. There is no Save on this row. Treat them as figures. The period table’s Curve column is the per-hour pointer into this staircase (set, or to R {cost} when a cost increment is stored).

12.3.6 Attach a book / no run

#bid-desk-need-book when units exist but no book is attached: To build a DAM bid from a strategy forecast, attach a book to this registration. Link Attach a book → Info.

Inside the ladder, #org-dam-book-ladder shows a dashed empty state when there is no completed strategy run and no net position: No completed strategy run for this book yet — run a forecast to build a bid. Strategy is the kitchen. This desk does not invent megawatts.

12.3.7 Book ladder — the kitchen panel

Component #org-dam-book-ladder. This is your residual, priced the way the book already values spill and shortfall. The Market Operator never sees these rungs. Rebuild and Submit live here — not on the three top cards.

Stale-run banner. Amber: A newer strategy run exists — rebuild to bid on the latest position. Shown when the Bid’s strategy_run_id is behind the net position’s. Why: submitting last night’s leftover after this morning’s re-forecast is how you sell energy you no longer have.

Submit sits in a strip above the chart (phx-click="submit"), only while the Bid is DRAFT and the date is not in the past. Paper-plane icon. Confirm: Submit this bid to the Market Operator? Prices are anchored to the strategy’s opportunity costs. Writes the 168-period Submission through the same door the 03:00 worker uses. Flash names the TUID. Refuses if there is no draft, no TUID, validation fails, curve emission fails, or the gate/horizon is wrong. Past dates hide Submit. You cannot bid yesterday.

After a successful send, the button is replaced by an emerald chip: Submitted · MO ref … — the market’s reference. The ladder is now a receipt, not an editor.

Rebuild from latest run #bid-desk-rebuild sits in the chart header (event build), once a book exists. Pulls the latest completed strategy run into a DRAFT Bid. Flash: Draft bid built from the latest run. or The latest run is balanced — nothing to bid. It does not send anything to the Market Operator.

12.3.8 Chart — Net position (MWh by SAST hour)

Card heading Net position (MWh by SAST hour). Chart id #dam-net-position. It is a stacked area: two series, Long (offer) in one colour and Short (buy) in the other, one point per SAST hour 0–23.

How to read it. A bar (or stacked area) above the axis in the long series means “this hour we have leftover energy we can offer.” The short series means “this hour we still need to buy.” They are drawn as positive heights so a 6 MWh short does not hide under the axis. A flat night on a solar book is normal. A spike at 18:00 on an off-taker book is the evening gap.

Netting badge. When the registration balances more than one book, a pill shows gross → net MW netted. The market settles the registration, not each book. Long and short books in the same hour cancel; only the residual is bid. Caption #bid-netting-scope: Scope: registration fixture · cross-book netting or Scope: book. Expand an hour in the table to see per-book contributions. Time zone chip: SAST (UTC+2).

Price ribbon. When a System Operator reference-hour forecast exists: P10 / P50 / P90 in R/MWh. This is a weather-map of price, not a bid. P50 is the middle guess; P10 is the cheap tail; P90 is the expensive tail.

12.3.9 Bilateral vs market, clips, and the ladder table

The same leftover megawatt-hours you are about to bid into the DAM are the megawatt-hours a counterparty might still take at a fixed price. This block is the desk’s last look at that fork: keep the energy for the auction, or sign it away bilaterally. It sits under the net-position chart. It is a decision aid, not a send button. Dragging the slider never rewrites a rung, never changes the 168-period Submission, and never talks to the Market Operator.

The card headed Bilateral vs market renders only when a DAM price forecast band exists (P10 / P50 / P90). The Offer figure is the fixed bilateral price laid against that band. If the book has not stored a comparison offer, the card uses the forecast P50 so the five figures still render. A missing band hides the whole card; the ladder table then sits on its own under the chart.

The five figures

Five values in a row, all in R/MWh. Hover the information-circle on each label for the same sentence the card uses.

P10 / P50 / P90 here are price bands, not generation grades. They come from the System Operator’s trailing DAM history (28 days, bucketed by market × month × day-type × hour), refreshed at 12:30. The ribbon above the chart is the same family of numbers. A flat demo history can read 980 / 980 / 980; a real noisy history spreads them. Full clocks: V9 §9.5.

Careful. These figures never become bid prices. Ladder rungs stay opportunity-cost truthful (V9 §4.2). The forecast changes whether you still want the energy on the market, not the price the kitchen wrote on the rung.

Risk aversion λ — what the slider does

The Risk aversion λ range (set_lambda, 0.00–1.00 in steps of 0.05, default 0.50) is the book’s appetite dial. It is the λ in the CE formula. Moving it recomputes CE and the verdict badge on this card only. It does not persist onto the Bid, does not change Rebuild, and does not change Submit.

Write the formula once:

CE = P50 − λ × (P50 − P10)

(P50 − P10) is the cheap-tail gap — how far the bad DAM outcome sits below the middle guess. λ is how much of that gap you subtract from P50 before you will call the market “worth it.”

What sliding it achieves. Drag left (toward 0) and CE rises toward P50 — the market looks more attractive, so the badge is more willing to say Hold for market. Drag right (toward 1) and CE falls toward P10 — the market looks worse, so a middling Offer that lost at λ = 0 can win at λ = 1 (Sign bilateral). You are not changing the forecast. You are changing how much cheap-tail pain this desk will discount before it prefers a fixed crate.

The slider is a preview of appetite, not a new number the auction will see. If two desks disagree on a PPA vs DAM, they are usually disagreeing on λ, not on P50.

The verdict badge

The badge compares CE to Offer. Let diff = CE − Offer.

The 5% band is why Marginal exists: a CE of R 841 against an Offer of R 820 is not a ringing endorsement of the DAM. It is “almost a coin flip.” The BRP seat computes the verdict; the card is pure presentation of that decision. Strategy never reads the forecast to mint a rung.

Worked arithmetic

Take a noon band with spread — the numbers V9 §9.5 already uses: P10 R 700 / P50 R 980 / P90 R 1,400. Cheap-tail gap = 980 − 700 = R 280/MWh.

Read the middle row aloud: at the default λ, a R 900 fixed offer beats a market whose risk-adjusted value is R 840, even though the median forecast is R 980. That is the point of CE. P50 is a coin flip; the offer is a certainty. People who “know P50 is above the strike” and still see Sign bilateral are not looking at a broken card — they have not named their λ yet.

On flat demo history (P10 = P50 = P90) the gap is zero, CE equals P50 at every λ, and the slider does not move the badge. Drag it anyway to see the control; the arithmetic only bites when the band has spread.

Follow along. Seat: an org Bid Desk with a DAM band (trader_1@webill.net on the demo). Path: /org/brp/bid-desk/submissions. Under the chart, read Offer / P10 / CE / P50 / P90, then drag Risk aversion λ. Watch CE and the badge, and confirm the ladder rungs beside them do not change.

Open-position clamps

Rose card, heading Open-position clamps, when any hour was cut to the book’s OPEN_POSITION_MW risk limit. Each chip: {hour}h {direction}: clamped {from} → {to} MW. Why: the book promised risk it will not take. The cheapest rungs are kept; the rest is dropped and logged, so you can see the cut rather than wonder why the ladder is smaller than the chart. Daily’s Clips count is this list’s length.

What the ladder table is for

#org-dam-ladder-table. One row per SAST hour 00–23, under the chart — nested inside the Bilateral vs market card when that card is showing, otherwise on its own. Scroll inside the table for hours 13–23; the Hour column stays sticky.

This table is the kitchen receipt for the residual, hour by hour. Strategy already decided what is leftover (long) and what is still a gap (short). Rebuild turned that residual into price steps — opportunity-cost rungs, cheapest first on an offer, a single limit on a buy (V9 §4.2). The table is how you inspect that kitchen work before (and after) you encode it as a 168-period Submission.

It is not:

• the five-block price curve the Market Operator clears (§12.3.5)
• the day-ahead period grid (§12.3.10)
• a place to type a bid price
• the Bilateral vs market verdict (that card sits around this table when the band exists, and does not edit these rungs)

Why it lives on Submissions. Daily tells you whether tickets went in. Submissions is where you write tomorrow. You need to see, for each hour: how much residual, which way it faces, what the book thinks that energy is already worth, and — once the auction has printed — whether the market took it and at what SMP. Without this table you would Submit a curve and hope the kitchen leftover matched. With it you can catch a stale run, a clip, or a netting surprise before 10:00.

How an hour is meant to be read. Pick 12:00. Net MWh is the signed leftover from the latest run (green long, rose short). Dir says whether the rungs are an OFFER or a BID. Ladder (R/MWh) is the kitchen’s steps for that hour — what you will offer or the most you will pay — not the crate price the market will pay everyone. Until publication, SMP, Accepted, and often Result stay — / Pending. That is the unpublished stretch from §12.3.2, not a missing column. After clearing, SMP is the uniform price; Accepted is how many MW the auction took; Result is Cleared / Pending / —. SAWEM pays SMP, not your rung (V9 §4.3).

Click a row (toggle_row) to expand provenance: which strategy run minted the residual, and which components (kind, MWh, c/kWh) stacked into the rungs. That is “why this hour costs what it costs.” When the registration balances more than one book, the Netting stack shows gross, net, and per-book MWh — the market settles the registration, not each book. Empty: No provenance for this hour.

Worked feel — hour 12. Net +6.71 MWh long, Dir OFFER, Ladder 10.00 / 410.00 (firm spill at the floor-plus-margin, wind at 40 c/kWh × 10 + margin). SMP — before publication; after a R 980 print both rungs would clear and Accepted would read 6.71. Provenance names the run and the two components. Same numbers as V9 §4.1.

If Open-position clamps cut that hour 6.71 → 3.00 MW, the chart still shows the unconstrained leftover and the ladder shows the clipped volume. That mismatch is the point of the rose chips.

12.3.10 Day-ahead submission table

Section #submission-desk. This is the ticket, opened flat. Heading Day-ahead submission (§9.3). Explainer: What you submit is not a price and a volume. It is how much you can produce each hour and a price ladder for it, for the next seven days — 168 Trading Periods.

If you arrived without a unit, #submission-desk-empty: No Trading Unit selected. The gate clock may still render beside the heading; the grid does not. Pick a unit on Daily (or put tuid= in the URL) and come back.

Gate clock #submission-gate-clock sits top-right of this card. Green when open, rose when closed. This is the detailed twin of the bar chip — §12.3.2 walks both states.

Rollover banner #submission-rollover-banner. Only when the stored Submission’s source is not Participant. Amber, or rose when staleness has started to bite. This submission was rolled over under §9.3(2) — you did not send it. Names the source trading date (#submission-rollover-source) and consecutive missed gates (#submission-rollover-staleness). When it escalates: Day 7 of a rollover repeats the source’s day 7, because there is no day 8 to shift from — so your horizon is converging on a single old day. Submit before the next gate.

Day selector #submission-day-selector. Heading The seven-day horizon (§9.3(1)). Caption: 168 periods submitted together — the day below is a view, not a separate submission. Seven buttons #submission-day-{1–7}, event select_submission_day. Labels look like Thursday 16 Jul '26. The selected day is navy; the others are white.

Why seven buttons: 168 rows on one grid is unreadable. You page through the week the way you flip a wall calendar. Looking at Day 3 does not send a 24-period body. There is still one Submission. There are not seven tickets.

Worked picture. You Submit once. The market receives 168 hours: tomorrow, the day after, … through day 7. You click Day 3 because you want to check Saturday’s 18:00 DAC. You have not created a Saturday-only bid. You have turned the page.

Period grid #submission-period-grid. Heading Trading Periods — {ISO date} (the day you selected). Scroll #submission-period-grid-scroll when 24 rows do not fit.

Empty #submission-grid-empty: No submission for this Trading Date yet. That is the open-and-unpublished morning with nothing stored — and also any date you have not spoken for. The five curve cards can still show registry Mingen / MCR above; the grid stays empty until a Submission exists.

When stored, 24 rows #submission-period-{hour} (00–23). Hover a row: warm highlight. Every column header has an information-circle; hover it for the sentence in the last column below.

Footer legend under the table (always, once the desk is showing):

• F (sky) means the market may move you between Mingen and your declared capacity, and your offer can set the price.
• I (amber) means you will be scheduled at exactly your declared capacity — a commitment, not a ceiling — and you cannot set the price (§9.7.2(2)).
• A / U are reserve available / unavailable.

Worked row — 18:00 on the selected day, OffTaker C solar. Period 18:00. DAC 75. DC —. Flexible F. Inst. U, Reg. U, 10-min U (this farm is not offering reserve). Curve set. That is the 75 MW hour from §12.0.2, as the ticket records it — still not the SMP. The SMP arrives on Daily after publication.

This table does not have a Submit button. Submit is on the kitchen ladder. This table is how you read the 168-period note, one day at a time.

12.3.11 View payload

View payload on a log row opens modal #org-dam-payload-modal (backdrop #org-dam-payload-backdrop). Heading Submission payload details. Subtitle: Sequence {n} · Horizon {n}h · {source}, or No stored submission for this Trading Unit. if you opened a silent row.

Body #org-dam-payload-json is the note as pretty-printed JSON (dark panel, green type): identity, sequence, source, horizon, consent, trading date, received-at, the five curve blocks, and each period’s DAC / DC / flexible / reserves / curves. Copy JSON #org-dam-payload-copy puts that text on the clipboard. Close #org-dam-payload-dismiss (or the X #org-dam-payload-close, or the backdrop) dismisses it.

Use this when someone asks “what exactly did we send?” It is a receipt, not a second editor.

12.4 IDM

IDM (/org/brp/bid-desk/idm) is the patch desk for today. You open it when the forecast has moved and the hour has not yet started. Five smaller auctions that only move hours still left. A Bid Desk link (#back-to-bid-desk) returns you to Daily.

Redeclare #idm-open-redeclare and Consent #idm-open-consent sit on the right of the iteration chips (#org-idm-actions). They open branded modals (#idm-redeclare-modal, #idm-consent-modal). Both buttons are hidden when the IDM gate is closed. While the board is fetching, #org-idm-loading is a spinner over the actions and the desk. What each button is for, when to press it, and what happens after you click: §12.4.5.

Why its own page: the DAM submission is a week-shaped object with a 10:00 door. The IDM is five smaller doors, a carry-or-redeclare decision, and two forms that must not share a button. Mixing them with Submit is how a participant re-prices mid-day by accident. The IDM does not rewrite the DAM bid. It re-uses the day-ahead curve and changes volume.

Where this is taught. On-instruction vs against-instruction pricing, collars, and reversals: V9 §5.

The Trading date bar still shows the selected unit as read-only (#bid-desk-selected-tuid). Pick the unit on Daily (or arrive with tuid in the URL from a unit-card icon). The Redeclare and Consent buttons appear whenever the gate is open; both submits stay disabled until a TUID is selected. Lodgements then filter to that unit.

12.4.1 Iteration chips

Row #org-idm-iterations. Five pills #org-idm-iteration-{n}: Iteration N plus the gate time (for example Wed 12:00). An OPEN iteration also shows a green dot. The selected chip is navy; the others are white. Each chip is a patch with iteration= in the URL.

To the right of the chips, when the selected iteration is open: Redeclare #idm-open-redeclare and Consent #idm-open-consent (event open_idm_modal). Those two buttons are hidden while the gate is closed.

Why the chips are not cosmetic: selecting an iteration loads that iteration’s lodgements, the hours it can still move, and the carry / re-declare advice for those hours. Clicking iteration 4 at 11:50 is how you work the 12:00 gate. There is no rolling T−60 window.

12.4.2 Intraday market card

Section #intraday-desk. Heading Intraday Market. Gate badge #org-idm-gate-state sits next to the heading: GATE OPEN (green, pulsing) or GATE CLOSED (rose). Empty #intraday-desk-empty: No intraday auctions for this Trading Day. Subtitle #org-idm-subtitle: Five auctions at fixed times — non-rolling window (clause 10(1)). Countdowns relative to server time.

Auction table #idm-gates (ids #idm-gates-col-*). This is the table on the card — five rows, one per iteration, #idm-gate-{n}. It is a clock, not a price list. There is no SMP column and no Collar column here. Those belong on a later card after an auction has published (below).

Hours rem. is not the countdown. Closes in is how long you have. Hours rem. is how much of the day this auction can still touch. A re-declaration only applies to hours that have not started. Iteration 1 (gate 18:00 the day before) still has the whole Trading Day — 24. Iteration 4 (gate 12:00) has 13:00 onwards — the morning is already being delivered and cannot be patched. Iteration 5 (gate 18:00) has 19:00 onwards — five hours. The number is a property of that iteration, not a live drop as the clock ticks toward the gate. At 11:00, iteration 4 still shows the afternoon. At 12:01 that row is CLOSED: those hours are gone for this door. They do not come back on this iteration.

State is whether this door will still take a lodge.

• OPEN (amber row, amber pill) — the gate is still in the future. Redeclare and Consent are on the chip strip. You may lodge for any hour in Hours rem.
• CLEARING (pale amber pill) — the gate has shut and the result is not published yet. The door will not take another lodge. Wait.
• CLOSED (slate pill) — published, or the publication deadline has passed. This iteration is finished. Pick a later chip if one is still OPEN.

The open row is highlighted so you can see which auction you are working. Selecting a chip loads that iteration’s lodgements and the hours it can still move. Clicking iteration 4 at 11:50 is how you work the 12:00 gate.

Classification preview #idm-classification-preview (amber alert) when a re-declare is in view. Heading: the classification and clause. Body: the sentence that says whether this will be against instruction (charged/paid flat at the Intra-Day Price) or on instruction (you keep the better of your offer and that price). Footer: The classification is certain; the price is an estimate until the auction clears. Why this is the most useful thing on this page: §10(6)–(9) is deterministic from the declaration. You can know you will be charged flat before you press Lodge, while you can still change your mind.

The lodgements table and this platform’s ledger sit further down the page — §12.4.6 and §12.4.7. Carry / re-declare is the timeline in §12.4.4.

After an auction publishes

A second card, Intraday prices #idm-prices, appears under the capacity chart only when an iteration has already published a price. It is not the five-row table on this card. Until then the card above is the whole clock: Iteration, Gate, Closes in, Hours rem., State.

When that later card is present it shows both prices, always — the raw Intra-Day Price and the one the collar left. The arithmetic is V9 §5.4.

12.4.3 Capacity profile

When the selected iteration has hourly positions, a Hourly Capacity Profile card sits under the classification preview. The chart #idm-capacity-chart is a stacked area: redeclared MWh on top of baseline MWh, one column per hour still in this iteration.

Read it like a horizon line. The baseline is what the DAM left you with. The redeclared band is the patch you have already lodged. Hours you have not touched stay baseline-only. The mono chip on the right names the window (for example 13:00–24:00).

12.4.4 Carry or Re-declare Schedule

Card Carry or Re-declare Schedule #idm-positions. Subtitle: Manage hourly MW volumes and carry forward rules for Iteration N. A chip names how many hours are on the spine. This is the hour-by-hour board for the selected iteration: for each remaining hour, should you leave the DAM schedule alone or patch volume before the gate?

It is a vertical timeline #idm-positions-timeline, not a table. Amber line down the middle. One node #idm-position-{n} per hour the desk has a decision for. Read each node left → spine → right.

An empty iteration renders #idm-positions-empty: No carry or re-declare positions for this iteration. Nothing to decide.

The left of the node — time and Target Baseline

On the left of the amber spine:

• A mono chip with the hour in SAST — 18:00 SAST. That is the Trading Period this node is about.
• Target Baseline — the contracted megawatt-hours for that hour.

Target Baseline is the promise still on the books. It is this unit’s Contracted Energy for the hour: the latest intraday schedule if an earlier iteration already moved you, otherwise the day-ahead constrained schedule. Balancing will measure you against this number if you do nothing. It is not the forecast, not Declared Available Capacity, and not a price.

If the farm was scheduled for 75 MWh at 18:00 and nothing has been re-declared yet, Target Baseline is 75 MWh. After iteration 4 patches you to 20, a later iteration’s Target Baseline for that hour is 20 MWh. The left side does not change when you hover. It is the reference the right-hand card is arguing against.

The information card on the right

To the right of the spine sits a slate card. That card is the decision for this hour. From the top:

• Deviation MWh against the baseline. A large mono figure (how far the freshest forecast sits from Target Baseline), the word against, then the same contracted MWh again so you can read the gap without looking left. Signed: short is the plant will not make the baseline; long is it will overshoot.
• A carry or redeclare badge. Carry (slate) — do not patch this hour. Redeclare (amber) — the desk has an IdmDecision that says a lodge is the cheaper path. Daily’s chip is this same decision, summarised. The three reasons carry can mean, and when redeclare wins, are V9 §5.5.
• A short advice sentence #idm-position-{n}-tip. Hover the sentence (or the figures above it) for the full reason — instruction expected, inside the metering band, or imbalance cheaper than the IDM. “Carry” is one badge and three different facts; the sentence says which.

On the right edge of that card:

• A read-only MWh box #idm-position-{n}-mwh. You cannot type a new volume here. This is the deviation the decision used, not an editor. Volume is typed in the Re-declare modal.
• When the selected iteration is OPEN, a clickable icon #idm-position-{n}-redeclare (circular-arrow). When the gate is closed the icon is hidden — you cannot lodge through a shut door.

The footer of the card is #idm-positions-total: the sum of absolute deviations on the spine. It is a scan figure, not a charge.

What the icon button does

The icon does not lodge. It does not change Target Baseline. It opens the Re-declare modal (§12.4.5) with this node’s hour already filled in. That is the fastest path when you already know which hour you mean — “have I already touched 18:00?” and “open the form for 18:00” in one click.

Hover the icon: tooltip #idm-position-{n}-redeclare-tip — Re-declare this hour. Opens the form with this period filled in. Volume, not price. The tooltip is the button’s job in one breath. Clicking still needs a selected Trading Unit and an IdmDecision on screen before Lodge will enable.

Use the icon when the badge says redeclare and you agree. Do not use it to “correct” a carry hour because the forecast moved a little — that is how a free or cheap deviation becomes a flat Intra-Day Price charge. Closing the modal without lodging leaves the timeline as it was.

What redeclaring is

Think of last night’s day-ahead market as a restaurant booking. You reserved a table for eighteen people at 18:00. The kitchen planned for eighteen. This morning the dining room is smaller (the System Operator cut the wires) so the booking is now sixteen. At 11:30 the weather turns and you will only bring four. If you say nothing, eighteen (then sixteen) still sit on the reservation book, and at 18:00 the empty chairs are a problem you pay for later.

Redeclaring is ringing the restaurant before dinner and saying: I am only bringing four. You have not cancelled the booking. You have not changed the menu price. You have patched the head-count. The kitchen can still sell the empty chairs to someone else in the lunchtime (intraday) sitting.

In market words: a re-declaration is a volume patch on one hour that has not started. You send a new Declared Available Capacity. The day-ahead price curve stays. The DAM energy ticket is not torn up. The intraday market adds a separate charge (or payment) for the megawatt-hours you took back or added. You cannot re-price mid-day. If you could, you could watch the stack form and then move the price you are about to be charged at.

It is not a new bid. It is not Consent (that is a yes or no for the day). It is not typing in the read-only MWh box on the timeline. It is not free just because your day-ahead offer was R 0.00. Changing your own mind is charged flat at the Intra-Day Price. Being moved by the System Operator is not. That difference is the whole plot.

The arithmetic home is V9 §5. This section is the same hour in ordinary English, on this timeline and this form.

What the Re-declare form does

The form #idm-redeclare-form lives in modal #idm-redeclare-modal. It does one job: send the Market Operator a patch for one hour, one unit, one iteration. It does not rewrite last night’s 168-period note.

Open it from the chip-strip Redeclare button or from the node icon (the icon fills the hour for you). The page behind stays put. Three fields, then a lodge.

Justification #idm-redeclare-justification repeats the timeline badge so you can see why the desk asked. Without that decision, amber: No IdmDecision is on screen for this unit. Lodge stays off. A patch without a reason is how someone “corrects” an hour the desk said to carry.

Close without Lodge and the books are unchanged. A second lodge for the same unit, date, iteration, and hour replaces the first.

A worked hour — 18:00, start to finish

Same solar hour the chapter already opened (§12.0.3). OffTaker C. Unit TU-IPP-A-PV. Trading date 15 July 2026. Iteration 4, gate 12:00. You are at the desk at 11:30.

Step 1 — last night. You told the market this farm would be there for 75 MWh at 18:00. The market cleared. You are paid R 67,500 on that unconstrained 75, at R 900. That is the restaurant taking the deposit for eighteen seats.

Step 2 — this morning, the room shrinks. The System Operator constrains the hour. The books now expect 60 MWh. Target Baseline on the left of the 18:00 node is 60, not 75. Those 15 MWh were taken from you. You keep the R 67,500. The cut is free. You did not redeclare yet.

Step 3 — 11:30, the cloud. The nowcast says 20 MWh, not 60. If you do nothing, 18:00 still starts at 60 on the market books. After the meter, the missing 40 MWh is imbalance — often dearer than the IDM. The desk compares that path to a patch (V9 §5.5).

Step 4 — what the timeline is saying. Left: 18:00 SAST, Target Baseline 60 MWh. Right: −40 MWh against 60, badge redeclare, advice that the intraday charge is the cheaper path. The read-only box shows 40. The circular-arrow is visible because iteration 4 is still OPEN (Closes in is counting down to 12:00; Hours rem. still includes 18:00).

Step 5 — you open the form. Click the node icon. Period is pre-filled. Justification repeats redeclare. You type 20 in Declared available capacity and the cloud sentence in Reason. You have not changed a price. Lodge is enabled because the unit is selected and the decision is on screen.

Step 6 — you press Lodge. The modal closes. Flash: Re-declaration lodged for TU-IPP-A-PV. Lodgements shows 18:00 / REDECLARE / 20 MW / Logged. The capacity chart grows a redeclared band on 18:00. Classification preview says this 40 MWh is against instruction — charged flat at the Intra-Day Price, not at your offer. The classification is certain; R 945 is the estimate until the 12:00 auction clears. Target Baseline on the left does not flip to 20 until a later iteration reads the new schedule. The DAM ticket is still R 67,500.

Step 7 — the money, after the gate. The IDM adds a separate charge for the 40 MWh you took back. You read it on Market Month, not on this desk.

Σ check: 67,500 − 0 − 37,800 = 29,700 ✓. The 15 MWh the System Operator took is not in the charge. The 40 MWh you took back is. Had you redeclared the first 15 as well, you would have paid for a cut that was going to be free. That is why a carry badge on an instructed hour is not laziness.

Had the badge said carry because a further constraint was coming, the same Lodge would have been the expensive click: you would have converted a free instructed deviation into a flat R 945 bill.

Data. full_demo · seed 42 · worked delivery day 2026-07-15 · 18:00 SAST · iteration 4 · unit TU-IPP-A-PV · SMP R 900 · applied IDP R 945. The 60 → 20 / 40 MWh charge is the Code picture; the 75 is last night’s unconstrained ticket.

Follow along. Seat: OffTaker C, TU-IPP-A-PV selected. Path: Bid Desk → the bolt IDM icon. Pick an OPEN iteration. On Carry or Re-declare Schedule, read one node: SAST chip and Target Baseline on the left; on the right, deviation against that baseline, the carry / redeclare badge, and the advice. Hover the circular-arrow icon — the tooltip should say the form will open with this period filled in. Click it. The Re-declare modal opens with that hour in Trading period. Close without lodging.

12.4.5 Re-declare and consent

Two buttons sit on the right of the iteration chips. They look alike. They are not.

Redeclare tells the Market Operator: for this hour, I can no longer do what last night’s schedule said. You change volume — how many megawatts this unit will produce (or draw). You do not change the day-ahead price. The DAM ticket still stands. The IDM adds a separate patch for the megawatt-hours you took back, or added.

Consent tells the Market Operator: for the rest of today, may you move this unit in the remaining auctions? You change a permission, not a megawatt. Willing means yes. Non-willing means hold the DAM schedule unless the System Operator imposes a new network constraint. Changing consent does not silently change volume. Two forms, two buttons, on purpose.

The two forms no longer sit on the page. They open as modals so the chips, the capacity chart, and the positions timeline stay in view while you type.

Close either modal with #idm-redeclare-modal-close / #idm-consent-modal-close (or the backdrop #idm-redeclare-modal-backdrop / #idm-consent-modal-backdrop). Event: close_idm_modal. Completing the submit also closes it. Closing without submitting writes nothing.

The buttons on the chip strip are hidden when the selected iteration is closed. The closed banner is then the only action. You cannot lodge a patch through a shut door.

You still pick a Trading Unit in the chrome. The modal will open without one, but both submits stay disabled until a TUID is selected. Amber copy: Pick a Trading Unit before you re-declare / Pick a Trading Unit before you change consent. Lodgements then filter to that unit; with All units they list every owned unit’s patches for the selected iteration.

What Redeclare does

Think of last night’s DAM as a promise: this unit will be there for 75 MW at 18:00. Cloud arrives. The plant will not make 75. If you do nothing, the hour still starts at 75 on the market books, and the difference becomes imbalance after the meter.

Redeclare is how you correct that promise before the hour starts, while this iteration’s gate is still open. You send a new Declared Available Capacity for one remaining hour. Everything else on the DAM submission — the price curve, reserves, energy limits — is left alone. A re-declaration is a patch, never a replacement. You cannot re-price mid-day.

That patch costs money when you took the volume back. Being moved by the System Operator does not. The arithmetic lives in V9 §5. This page’s job is to let you see the classification before you lodge, and to refuse a lodge that cannot show why the desk asked for it.

When you should press Redeclare

Press it when all of these are true:

1. A Trading Unit is selected.
2. This iteration’s gate is OPEN.
3. The hour has not started. Iteration 4 (12:00) can still move 13:00 onwards; it cannot move 12:00.
4. The positions timeline badges the hour redeclare, and the justification on the form repeats that advice. That badge is an IdmDecision: the desk has compared an expected System Operator instruction, your Metering Accuracy Band, and the likely Intra-Day Price against imbalance, and concluded that a patch is the cheaper path (V9 §5.5).
5. You have a human reason you can write down — forecast, outage, derate — because a later query will read that sentence.

Do not press it when the badge says carry. Carry means the drift is inside the band, or an instruction is expected, or imbalance is cheaper than the IDM. Patching then converts a cheap (or free) deviation into a flat Intra-Day Price charge. If a constraint is coming anyway, re-declaring first transfers value away from you.

Do not press it to “fix” a price. There is no price field. Do not press it for an hour that has already started. That is a re-declaration of the past, and it is refused.

What happens when you click Redeclare

1. The button #idm-open-redeclare opens modal #idm-redeclare-modal. Heading Re-declare. Caption: PUTs a TUID re-declaration. A submit that cannot show the IdmDecision that justified it is refused. The page behind stays put — chips, chart, timeline.
2. Opening from a timeline node #idm-position-{n}-redeclare does the same, and pre-fills the trading period for that hour. That is the fastest path when you already know which hour you mean.
3. If no unit is selected, amber: Pick a Trading Unit before you re-declare. Lodge re-declaration stays disabled.
4. Justification #idm-redeclare-justification repeats the carry/redeclare advice. Without a decision, amber: No IdmDecision is on screen for this unit. Submit is refused until one is. The lodge button stays disabled. A patch without a reason is how a participant “corrects” an hour the desk did not ask it to touch.
5. You fill the form #idm-redeclare-form (fields below) and press Lodge re-declaration #idm-redeclare-submit (event idm_redeclare).
6. On success the modal closes. Flash: Re-declaration lodged for {tuid}. The page reloads that iteration. The hour appears on the Lodgements table as kind REDECLARE, status Logged. The capacity chart grows a redeclared band on that hour. Classification preview #idm-classification-preview states whether this will be charged flat at the Intra-Day Price (against instruction) or kept at the better of your offer and that price (on instruction). The classification is certain; the price is an estimate until the auction clears.
7. The DAM ticket is not torn up. Money for the patch arrives later on Market Month, not on this desk.
8. On refusal you stay in the modal. Flash names why: no TUID, no decision, a bad period, or Re-declaration refused: … with the server’s reason. A closed hour is refused with a sentence that names the gate that already shut.

A second lodge for the same unit, date, iteration, and hour replaces the first. Two rows for one hour would leave the clearing choosing between them.

The same 18:00 hour — 75 last night, Target Baseline 60, type 20, charge 40 × R 945 — is walked number-by-number in §12.4.4.

The form #idm-redeclare-form lives inside the modal.

There is also a declared-consumption path in the payload when the unit is a load or a battery; the visible field on this form is capacity, because that is the common renewable correction.

What Consent does

Consent is a flag for the day, not a number for an hour. It has no Trading Period. Your DAM submission already carried one: may the Market Operator move this unit in the five intraday auctions? Consent on IDM restates that flag for today.

• Willing (WILLING) — yes. The Market Operator may reschedule this unit in the remaining auctions. That is the usual setting for a plant that can still move.
• Non-willing (NON_WILLING) — hold my DAM schedule. Stay out of an ordinary re-clear.

Non-willing is not a force field. A new System Operator network constraint still moves you. You opted out of a market re-clear, not out of the wires.

Consent does not change Declared Available Capacity. It does not lodge a re-declaration. It does not appear as a REDECLARE row on the lodgements table. The flash says so on purpose: Volume was not re-declared.

When you should press Consent

Press Willing when you want the remaining auctions to be allowed to move this unit — you are flexible, or you want the Market Operator to be able to pick you up if the stack needs you.

Press Non-willing when you need the DAM schedule to hold: fuel already committed, a must-run hour, a bilateral that assumes the night-time shape. You are saying do not volunteer me. You are not saying ignore the System Operator.

Do not press Consent because the forecast moved. That is Redeclare. Do not press it hoping to cancel a lodge you already sent. Consent does not unwind volume.

You still need a selected Trading Unit and an OPEN gate. The button is hidden when the iteration is closed.

What happens when you click Consent

1. The button #idm-open-consent opens modal #idm-consent-modal. Heading Rescheduling consent. Caption: A separate control. Changing consent does not silently re-declare volume.
2. If no unit is selected, amber: Pick a Trading Unit before you change consent. Update consent stays disabled.
3. You set #idm-consent-flag to Willing or Non-willing and press Update consent #idm-consent-submit (event idm_consent).
4. On success the modal closes. Flash: Rescheduling consent updated for {tuid}. Volume was not re-declared. The page reloads. No new REDECLARE row appears. The capacity chart does not grow a band. Hours you have not patched stay on the DAM volume.
5. Closing without submitting leaves yesterday’s (or this morning’s) flag as it was.

The form #idm-consent-form lives inside the modal.

Follow along. Seat: OffTaker C, unit TU-IPP-A-PV selected. Path: Bid Desk → the bolt IDM icon (or /org/brp/bid-desk/idm?tuid=TU-IPP-A-PV). Pick an OPEN iteration. Press Redeclare. You should see the justification, the period / DAC / Reason fields, and Lodge re-declaration enabled only when an IdmDecision is on screen. Close it. Press Consent. Change nothing yet — read the caption. Willing / Non-willing does not mention megawatts. After Update consent, the flash tells you volume was not re-declared, and Lodgements is unchanged.

12.4.6 Lodgements table

Section heading Lodgements · Iteration N. Subtitle: Logged gate entries and re-declaration triggers. Body #org-idm-lodgements-table. Empty: No re-declaration was lodged.

What a lodgement is

A lodgement is the receipt for what you handed in before this auction’s door shut. You filled the Re-declare form and pressed Lodge. The platform kept a copy. That copy is the lodgement.

Think of a registered letter. You wrote a patch: this unit, this hour, this many megawatts, this reason. You handed it over the counter. The clerk stamped it Logged and gave you the slip. The letter has not been opened by the market yet. The slip is not the reply. It is proof you sent something, at this iteration, for this hour.

On this platform that receipt is a WB.Sawem.Mo.IdmLodgement of kind REDECLARATION. It is a participant input, not a market output. Iteration 4 clears from what you lodged at 11:47. Until that gate runs, the row is only your word, kept.

It is not:

• the Intra-Day Price (that arrives after the auction)
• the new Target Baseline on a later iteration (that is the revised schedule)
• a kitchen Bid (the book ladder is a different object — §12.4.7)
• Consent (that is a yes/no for the day, with no hour; this table does not list it)
• last night’s DAM Submission (that ticket still stands)

It is the patch the Market Operator will read when this iteration’s gate shuts: one Trading Unit, one Trading Period, one new Declared Available Capacity (or declared consumption), a reason code, and your note.

A second lodge for the same unit, date, iteration, and hour replaces the first. Two slips for one letter would leave the clerk choosing. Last one in is the one that clears.

Selecting a Trading Unit filters the table to that unit. All units lists every owned unit’s patches for the selected iteration. Switching the iteration chip reloads that auction’s slips — iteration 3’s 06:00 lodgements do not appear on iteration 4.

How to read a row

A worked slip — the same 18:00 hour

You already walked the form in §12.4.4. OffTaker C, TU-IPP-A-PV, 15 July 2026, iteration 4. At 11:47 you lodged 20 MW for 18:00, reason Forecast revision, note Convective cloud, 11:30 nowcast.

After Lodge, this table is no longer empty. One row:

If at 11:55 you lodge again for the same 18:00 — say 18 MW because the nowcast darkened — this row updates. You still see one line, not two. The clerk kept the latest letter.

At 12:01 iteration 4 is CLOSED. The row stays. You cannot add another slip on this door. Iteration 5 is a different table.

Empty #org-idm-lodgements-table with No re-declaration was lodged. means this iteration has no slip yet — not that the forecast matches the baseline, and not that you chose carry. Carry writes nothing here. Only Lodge does.

Follow along. After you lodge the 18:00 patch on TU-IPP-A-PV (password supersecret), stay on IDM, iteration 4. You should see one row: 18:00 · REDECLARE · 20 · FORECAST_REVISION · intra_day_price · Logged. Consent, then check again — still one row.

Data. full_demo · seed 42 · 2026-07-15 · iteration 4 · TU-IPP-A-PV. The 20 MW / 40 MWh / R 945 picture is §12.4.4.

12.4.7 This platform’s ledger

Paragraph #org-idm-book-ledger under the table, not a separate card. Body: The table above is this platform’s book-level IDM ladder — not the market stack. The Market Operator clears a re-declaration on a Trading Unit, not this ledger.

Why the warning exists: the kitchen Bid and the Code lodgement are different objects, the same way the book ladder is not the Submission. If you come here looking for “our IDM bid”, you are holding the leftover. The market cleared the TUID patch.

12.5 Forward

Forward (/org/brp/bid-desk/forward) is the contract scoreboard. You open it when you already have a physical power purchase agreement that was registered as a forward schedule, and you need to see — hour by hour — how much of tonight’s plant is already spoken for, and how much the night auction still put on top.

A Bid Desk link (#back-to-bid-desk) returns you to Daily. The tab strip #bid-desk-tabs walks you to Submission, IDM, Settlement and Imbalance without going home first.

This page does not write. You cannot register a schedule here, cannot bid, cannot patch. The write sits on Deals → Contracts (§18.1). This page only reads.

Where this is taught. What a forward schedule is, when the registration gate closes, and why the night auction only clears the leftover: V9 §20. What the Market Operator sees: V11 §27.

Follow along. Seat: an ACTIVE BRP with a Trading Unit that holds a REGISTERED forward schedule. Path: Daily → the unit’s Details & destinations → Forward. You should land on /org/brp/bid-desk/forward?date=…&tuid=…. You should see a navy Bid Desk header, a white Trading date bar, a back link, a tab strip with Forward highlighted, and a table of 24 hours.

12.5.1 What “forward” means here

Think of a greengrocer who already has a standing order with a farm: twelve crates every Wednesday at 08:00, written into a contract months ago. Tonight the produce market still runs an auction for whatever crates are left. The standing order is not in that auction. The auctioneer cannot take those twelve crates away to sell them to someone else. What the auctioneer can do is sell extra crates on top, if the farm grew more than twelve.

On this desk:

• The standing order is the forward base — megawatts already promised on a registered physical contract for that hour.
• The extra crates are the day-ahead figure — megawatts the night auction still chose for that hour, after the standing order was taken off.

Two numbers, always. Adding them is what the country will actually try to deliver. That sum is Contracted Energy — the baseline imbalance is measured against later. Collapsing the two numbers into one would hide a fact you need: sometimes the auction left nothing extra, and that zero is information, not an empty cell.