Trading Integration
Trading integration in ODS-E focuses on one core problem: multiple market actors can only settle, bill, and scale participation if they exchange data with a shared contract.
Context
In South Africa’s transition to a multi-participant electricity market, utilities, municipalities, traders, and private generators are active at the same time but do not consistently operate with a shared machine-readable data layer.
Common friction points:
- municipal and utility process differences across jurisdictions
- inconsistent wheeling and billing reconciliation practices
- party identity ambiguity across bilateral contracts
- tariff version drift between documents and operations
What ODS-E Adds
ODS-E provides a neutral interoperability layer for:
- interval energy records (
energy-timeseries) - settlement party context (
seller_party_id,buyer_party_id,network_operator_id) - tariff context (
tariff_schedule_id,tariff_period, version-effective timestamps) - municipal/grid topology (
municipality_id, feeder, zone, voltage metadata)
Market Reform Extensions
Aligned with the SAETA “Policy to Power” report (February 2026), ODS-E adds optional fields for 7 reform areas:
- Wheeling Transaction Envelope – traditional, virtual, and portfolio wheeling with reconciliation status
- Tariff Component Granularity – unbundled generation, transmission, distribution, and ancillary charges
- Curtailment Event Tracking – curtailment flags, causes, lost generation, and dispatch instruction references
- BRP / Imbalance Settlement – BRP context, forecasts, and imbalance calculations for the SAWEM
- Municipal Reconciliation – billing cycles, metered vs. billed quantities, and DAA references
- Green Attribute / Certificate Tracking – I-REC and other certificate references with carbon intensity
- Grid Capacity / Connection Status – GCAR milestones and grid access lifecycle (asset-metadata fields)
All extensions are additive and optional. Existing valid payloads remain valid.
Runtime Helpers
- Post-Transform Enrichment – inject settlement, tariff, and topology context into transformed rows
- Conformance Profile Validation – enforce required-field sets per trading context (bilateral, wheeling, SAWEM, municipal)
Why It Matters
With a common data contract:
- Traders can settle faster with fewer disputes.
- Utilities can onboard counterparties without custom data pipelines.
- Municipal processes can standardize reconciliation even when commercial models differ.
- LLM and analytics applications can return scoped, auditable answers.