Datasets:
The dataset viewer is not available for this split.
Error code: StreamingRowsError
Exception: CastError
Message: Couldn't cast
observation_window_id: int32
minutes: double
seconds_observed: double
data_coverage_pct: double
seconds_reliable: double
reliable_coverage_pct: double
is_reliable_window: int32
to
{'asset_id': Value('string'), 'asset_type': Value('string'), 'em_manufacturer': Value('string'), 'em_model': Value('string'), 'em_communication_protocol': Value('string'), 'em_acquisition_pathway': Value('string'), 'stream_start_utc': Value('timestamp[us]'), 'stream_end_utc': Value('timestamp[us]'), 'is_submeter': Value('bool')}
because column names don't match
Traceback: Traceback (most recent call last):
File "/src/services/worker/src/worker/utils.py", line 149, in get_rows_or_raise
return get_rows(
dataset=dataset,
...<4 lines>...
column_names=column_names,
)
File "/src/libs/libcommon/src/libcommon/utils.py", line 272, in decorator
return func(*args, **kwargs)
File "/src/services/worker/src/worker/utils.py", line 129, in get_rows
rows_plus_one = list(itertools.islice(safe_iter(ds, dataset=dataset), rows_max_number + 1))
File "/src/services/worker/src/worker/utils.py", line 489, in safe_iter
yield from ds.decode(False) if ds.features else ds
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2818, in __iter__
for key, example in ex_iterable:
^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2355, in __iter__
for key, pa_table in self._iter_arrow():
~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2380, in _iter_arrow
for key, pa_table in self.ex_iterable._iter_arrow():
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 536, in _iter_arrow
for key, pa_table in iterator:
^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 419, in _iter_arrow
for key, pa_table in self.generate_tables_fn(**gen_kwags):
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/parquet/parquet.py", line 220, in _generate_tables
yield Key(file_idx, batch_idx), self._cast_table(pa_table)
~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/parquet/parquet.py", line 156, in _cast_table
pa_table = table_cast(pa_table, self.info.features.arrow_schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2369, in table_cast
return cast_table_to_schema(table, schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2297, in cast_table_to_schema
raise CastError(
...<3 lines>...
)
datasets.table.CastError: Couldn't cast
observation_window_id: int32
minutes: double
seconds_observed: double
data_coverage_pct: double
seconds_reliable: double
reliable_coverage_pct: double
is_reliable_window: int32
to
{'asset_id': Value('string'), 'asset_type': Value('string'), 'em_manufacturer': Value('string'), 'em_model': Value('string'), 'em_communication_protocol': Value('string'), 'em_acquisition_pathway': Value('string'), 'stream_start_utc': Value('timestamp[us]'), 'stream_end_utc': Value('timestamp[us]'), 'is_submeter': Value('bool')}
because column names don't matchNeed help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
Open Energy Dataset β Star Schema
1. Overview
This star schema models the Gold-layer 15-minute energy aggregates from an industrial manufacturing facility in Ireland. The source dataset covers 43 monitored assets over ~12 months (2024-12-31 to 2025-12-31), with 1,039,873 ALL-phase windows totalling 2.96 GWh of measured electrical energy.
The facility employs ~150 personnel under continuous production. Monitored loads include hydraulic presses, air compressors, AHUs, heat pumps, mixers, material handling, and utilities. Metering was deployed progressively (staged commissioning), so individual assets have different temporal coverage within the observation window.
Source: Flynn et al., Data 2026, 11, 101 β doi:10.3390/data11050101 Dataset: doi:10.5281/zenodo.19180972
2. Tables
| Table | Role | Rows | Description |
|---|---|---|---|
| fact_energy_15m | fact | 12,076,111 | Unpivoted 15-min energy measurements (3 signals x 4 phases) |
| dim_asset | dimension | 43 | Monitored asset metadata (meter type, protocol, stream dates) |
| dim_signal_info | dimension | 12 | Signal catalogue (metric name + phase + unit) |
| dim_observation_window | dimension | 1,554 | Deduplicated per-window coverage and reliability profiles |
| fact_data_quality_event | fact | 24 | Documented instrumentation fault events |
File inventory
result/
βββ README.md (this file)
βββ build_star_schema.py (ETL script)
βββ fact_energy_15m.md (table concept)
βββ dim_asset.md (table concept)
βββ dim_signal_info.md (table concept)
βββ dim_observation_window.md (table concept)
βββ fact_data_quality_event.md (table concept)
βββ dim/
β βββ dim_asset.parquet (43 rows, <1 KB)
β βββ dim_signal_info.parquet (12 rows, <1 KB)
β βββ dim_observation_window.parquet (1,554 rows, 14 KB)
βββ fact/
βββ fact_energy_15m.parquet (12,076,111 rows, 75.8 MB)
βββ fact_data_quality_event.parquet (24 rows, <1 KB)
All parquet files use ZSTD compression. The fact table is a single file (not partitioned).
3. Schema Diagram
erDiagram
dim_asset {
VARCHAR asset_id PK
VARCHAR asset_type
VARCHAR em_manufacturer
VARCHAR em_model
VARCHAR em_communication_protocol
VARCHAR em_acquisition_pathway
TIMESTAMP stream_start_utc
TIMESTAMP stream_end_utc
BOOLEAN is_submeter
}
dim_signal_info {
INTEGER signal_id PK
VARCHAR signal_name
VARCHAR phase
VARCHAR unit
VARCHAR description
}
fact_energy_15m {
VARCHAR asset_id FK
INTEGER signal_id FK
TIMESTAMP time
DOUBLE value_float
INTEGER observation_window_id FK
}
dim_observation_window {
INTEGER observation_window_id PK
DOUBLE minutes
DOUBLE seconds_observed
DOUBLE data_coverage_pct
DOUBLE seconds_reliable
DOUBLE reliable_coverage_pct
INTEGER is_reliable_window
}
fact_data_quality_event {
INTEGER event_id PK
VARCHAR asset_id FK
VARCHAR issue_type
VARCHAR issue_detail
TIMESTAMP asset_stream_start
TIMESTAMP asset_stream_end
TIMESTAMP issue_start
TIMESTAMP issue_end
BOOLEAN issue_persisted_to_stream_end
}
dim_asset ||--o{ fact_energy_15m : "asset_id"
dim_asset ||--o{ fact_data_quality_event : "asset_id"
dim_signal_info ||--o{ fact_energy_15m : "signal_id"
dim_observation_window ||--o{ fact_energy_15m : "observation_window_id"
4. Design Principles
- Grain of
fact_energy_15m: one row per (asset_id,signal_id,time). The three source measures (energy, demand, avg power) and four phases (L1, L2, L3, ALL) are unpivoted into rows with a singlevalue_floatcolumn. - Signals as a dimension:
dim_signal_infoencodes both the signal name and the electrical phase, enabling flexible filtering and pivoting without hard-coded column names. - Coverage as a deduplicated dimension:
dim_observation_windowholds a surrogateobservation_window_idPK plus the six coverage/reliability value columns. Only 1,554 distinct profiles exist across 4.1M source rows, so each fact row carries a compact FK instead of duplicating coverage columns. - Data quality events as a separate fact: instrumentation faults are modelled as time-bounded events referencing the asset dimension, enabling temporal overlap analysis with energy facts.
5. Source Mapping
| Star Schema Table | Source File(s) | Transform |
|---|---|---|
fact_energy_15m |
Gold-layer Parquet partitions (data_parquet/asset_id=*/dt_utc=*/*.parquet) |
Unpivot Energy_kWh_15m, Demand_kW, AvgPower_kW_15m x Phase into rows; rename window_start_utc -> time; assign signal_id and observation_window_id FKs |
dim_asset |
metadata/AssetList.csv |
Direct load |
dim_signal_info |
Static catalogue (12 rows) | Generated from the 3 signal names x 4 phases |
dim_observation_window |
Gold-layer Parquet partitions | DISTINCT on 6 coverage columns; assign surrogate observation_window_id |
fact_data_quality_event |
metadata/meter_data_quality_log.csv |
Direct load with surrogate event_id |
6. Typical Questions
Questions an analyst might ask of this dataset, with expected answers derived from the published validation summaries.
Energy totals
Q: What is the total measured energy across all assets (ALL phase)?
A: 2,958,571 kWh (2.96 GWh). This is the sum of energy_kwh_15m for the ALL phase across all assets and windows.
Q: How much energy did the grid connection (mi_a) import over the observation period? A: 1,228,639 kWh. This is the single largest energy contributor in the dataset.
Q: Which asset type consumes the most energy? A: Electrical_GridImport (1,228,639 kWh via mi_a), but among consumer loads: HVAC_AirExtraction (206,329 kWh, driven by ex_b at 191,771 kWh), followed by Press_Main (525,161 kWh across 9 presses) and CompressedAir (144,771 kWh from 2 compressors).
Q: What is the total energy measured across all rows including per-phase breakdowns? A: 5,917,142 kWh across all 4,103,703 rows (L1 + L2 + L3 + ALL phases combined).
Temporal coverage
Q: What is the time span of the dataset? A: 2024-12-31 07:30 UTC to 2025-12-31 23:45 UTC (approximately 12 months).
Q: How many 15-minute windows are in the ALL-phase dataset? A: 1,039,873 windows across 43 assets.
Q: Which month had the highest energy consumption? A: October 2025 with 418,908 kWh (36-37 active assets), followed by November 2025 at 403,469 kWh (40 active assets).
Q: How did the number of active assets change over time? A: From 14 assets in January 2025 to 43 assets in December 2025, reflecting staged commissioning. The jump from 14 to 18 occurred in February, then 22 in March, 26 in April, and 36 in May when supply/distribution meters came online.
Data quality
Q: What is the mean data coverage across the dataset? A: 99.99% mean data coverage (ALL phase). Median is 100.00%.
Q: What percentage of ALL-phase windows are reliable? A: 97.72% (1,016,182 out of 1,039,873 windows satisfy IsReliableWindow = 1).
Q: Which asset has the lowest reliable window percentage? A: p_f (Press_IntegratedAutomationCell) at 70.64%, followed by sb_c (Electrical_Distribution) at 63.40%. Both have documented instrumentation issues.
Q: How many data quality events are there and what types? A: 24 events across 18 assets. Types include reversed CT polarity (most common), phase reference misalignment (single/multi/all phases), tag misconfiguration, and CT ratio misconfiguration.
Q: Which assets have unresolved faults (persisted to stream end)? A: ahu_a (L3 tag misconfiguration) and mix_b (L3 tag misconfiguration) β both had SCADA tag issues that were never corrected during the observation period.
Asset comparisons
Q: How many assets use Modbus RTU vs Modbus TCP/IP? A: 4 assets use Modbus RTU (hp_a, hp_b, sb_c, mi_b β all Rayleigh meters via gateway). The remaining 39 use Modbus TCP/IP (Weidmuller EM220 meters).
Q: Which individual press consumes the most energy? A: p_k (Press Main and Robot) at 207,445 kWh, followed by p_f (Press IntegratedAutomationCell) at 111,980 kWh and p_b (Press Main) at 88,014 kWh.
Q: What is the energy consumption of the two air compressors combined? A: 144,771 kWh (comp_a: 68,392 kWh, comp_b: 76,379 kWh).
Load profiles
Q: Do the heat pumps consume significant energy? A: No. hp_a consumed 69 kWh and hp_b consumed 12 kWh over the observation period β negligible compared to other loads.
Q: What fraction of total grid import is captured by sub-metered assets? A: The dataset is not a closed energy system β partial sub-metering means summing all consumer meters will not equal grid import (mi_a). This is a documented limitation of the retrofit monitoring deployment.
- Downloads last month
- 29