Power-system Data Orchestrator.
One pipeline. Every source. A single canonical model every other engine inherits.
The data pipeline under every other module. It cleans market and network feeds, ties each asset to its busbar, reduces a year of operation to representative scenarios and hands one checked dataset to the rest of the suite.
Why it matters nowFast tools on messy data just give you wrong answers sooner. Every study is only as good as the model underneath it, so PDO gives every module one version-controlled dataset.
How PDO works.
- 01
Normalise
Every source mapped to a Parquet schema with consistent units and conventions.
- 02
Node-merge
Topology reconciliation: duplicate and split nodes resolved against the network model.
- 03
Asset → busbar
Each economic asset bound to its physical node, so market and grid speak the same language.
- 04
Reduce & validate
A year of hours reduced to representative scenarios at <1% reconstruction error, then validated.
Five feeds in. One canonical model out.
Market and network data from different sources is normalised, matched to the topology and reduced, then handed to every module as one shared input.
Figures from an example run on a test network.
PDO turns five incompatible feeds into one reference model, so every module downstream works from exactly the same picture of the system.