Spaces:
Running
Running
File size: 15,475 Bytes
fd0bd3b 2f1129f fd0bd3b 9f09117 fd0bd3b 2f1129f fd0bd3b 0d542b0 fd0bd3b d31601b fd0bd3b d31601b fd0bd3b 2f1129f 134bb77 43cb5cc 0d542b0 134bb77 43cb5cc 0d542b0 134bb77 2f1129f fd0bd3b 12d7321 fd0bd3b 2f1129f 3af727f 2f1129f 1b5231e 0d542b0 1b5231e 2f1129f 1b5231e 2f1129f fd0bd3b 2f1129f fd0bd3b 2f1129f 0d542b0 fd0bd3b 0d542b0 2f1129f 0d542b0 fd0bd3b 12d7321 2f1129f 12d7321 2f1129f 12d7321 fd0bd3b 43cb5cc 9f09117 fd0bd3b | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 | <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>NEM Battery SCADA & Energy Data Explorer</title>
<link rel="preconnect" href="https://fonts.googleapis.com" />
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet" />
<link rel="stylesheet" href="/static/css/style.css?v=__VERSION__" />
<script src="https://cdn.plot.ly/plotly-2.27.0.min.js" defer></script>
</head>
<body>
<!-- ── Header ── -->
<header>
<div>
<h1>🔋 NEM Battery SCADA & Energy Data Explorer</h1>
<p>4-second SCADA power output and 5-minute dispatch energy storage data for BESS units in Australia's NEM</p>
</div>
</header>
<main>
<!-- ── BESS list staleness banner (shown only when /api/bess returns a non-live source) ── -->
<div id="bess-list-banner" class="alert alert-warning hidden" role="status"></div>
<!-- ── Control panel ── -->
<section class="panel">
<h2>Select Data</h2>
<div class="controls">
<div class="form-group">
<label for="sel-state">State / Region</label>
<select id="sel-state" disabled>
<option value="">— Loading… —</option>
</select>
</div>
<div class="form-group">
<label for="sel-bess">BESS Unit</label>
<select id="sel-bess" disabled>
<option value="">— Select a state first —</option>
</select>
</div>
<div class="form-group">
<label for="inp-date">Date <span style="color:var(--text-muted);font-weight:400">(max 1 day)</span></label>
<input type="date" id="inp-date" disabled />
</div>
<div class="form-group">
<label>Data Types</label>
<div class="data-type-group">
<div class="check-row-header" style="margin-bottom:0">
<label class="check-label">
<input type="checkbox" id="chk-scada" checked />
4-second SCADA
</label>
<button class="about-toggle" data-tip="4-sec power output & quality flags · PUBLIC_NEXT_DAY_FPPMW · from 29 Apr 2025" data-about="scada">▶ About</button>
</div>
<div class="check-row-header">
<label class="check-label">
<input type="checkbox" id="chk-energy" checked />
5-minute Dispatch
</label>
<button class="about-toggle" data-tip="5-min energy storage & dispatch MW · DISPATCH_UNIT_SOLUTION · from 1 Apr 2025" data-about="energy">▶ About</button>
</div>
</div>
</div>
<div class="form-group">
<label> </label>
<button class="btn btn-primary" id="btn-load" disabled>Load Data</button>
</div>
</div>
</section>
<!-- ── Error ── -->
<div id="error-box" class="alert alert-error hidden" role="alert">
⚠️ <span id="error-msg"></span>
</div>
<!-- ── Loading ── -->
<div id="loading-box" class="hidden">
<div class="spinner-wrap">
<div class="spinner"></div>
<p id="loading-msg">Fetching data from AEMO NEMWEB…</p>
</div>
</div>
<!-- ── Results ── -->
<div id="results-box" class="hidden">
<!-- ── SCADA section ── -->
<div id="scada-results" class="hidden">
<section class="panel">
<h2>SCADA — Summary Statistics</h2>
<details class="dataset-info">
<summary>About this dataset — PUBLIC_NEXT_DAY_FPPMW</summary>
<div class="dataset-info-body">
<p>
In the <strong>PUBLIC_NEXT_DAY_FPPMW</strong> (FPP Daily) data files, these four
columns define the exact timing and status of the 4-second SCADA power measurements
for batteries and generators.
</p>
<p style="margin-bottom:0.5rem"><strong style="color:var(--text);font-size:0.85rem">Column Descriptions</strong></p>
<div class="col-defs">
<div class="col-def">
<span class="col-name">INTERVAL_DATETIME</span>
<span class="col-desc">The <strong>target timestamp</strong> for the 4-second interval. Follows the format <code>YYYY/MM/DD HH:MM:SS</code> and represents the standard grid slot (e.g., :00, :04, :08) the measurement is assigned to.</span>
</div>
<div class="col-def">
<span class="col-name">MEASUREMENT_DATETIME</span>
<span class="col-desc">The <strong>actual timestamp</strong> when the SCADA reading was recorded by AEMO's systems. May differ slightly from <code>INTERVAL_DATETIME</code> due to communication latency or jitter; AEMO snaps each reading to the nearest 4-second slot.</span>
</div>
<div class="col-def">
<span class="col-name">MEASURED_MW</span>
<span class="col-desc">The <strong>instantaneous power output</strong> of the asset in Megawatts (MW) at that specific time. For batteries, positive values denote discharging (generation) and negative values denote charging (load).</span>
</div>
<div class="col-def">
<span class="col-name">MW_QUALITY_FLAG</span>
<span class="col-desc">A <strong>numeric code</strong> indicating data health. Tells you whether <code>MEASURED_MW</code> is a live reading or a substitute inserted because the real data was missing or erroneous (see below).</span>
</div>
</div>
<p style="margin-top:1rem;margin-bottom:0.5rem"><strong style="color:var(--text);font-size:0.85rem">MW_QUALITY_FLAG Values</strong></p>
<p>The quality flag is critical for ensuring you aren't analysing "frozen" or "bad" data.
According to the <strong>AEMO FPP Factor Calculation Guide</strong>, the digits translate as follows:</p>
<div class="col-defs" style="margin-top:0.65rem">
<div class="col-def">
<span class="col-name" style="color:var(--good)">0 — Good</span>
<span class="col-desc">Data is valid and received directly from the site telemetry.</span>
</div>
<div class="col-def">
<span class="col-name" style="color:var(--suspect)">1 — Substituted / Estimated</span>
<span class="col-desc">The raw data was missing. AEMO has "held" the previous known-good value or interpolated a value to fill the gap.</span>
</div>
<div class="col-def">
<span class="col-name" style="color:var(--bad)">2 — Bad</span>
<span class="col-desc">Telemetry is flagged as bad (e.g., communication failure, hardware fault). These points are typically excluded from high-fidelity performance analysis.</span>
</div>
<div class="col-def">
<span class="col-name" style="color:var(--na)">3 — Manual Override</span>
<span class="col-desc">An AEMO operator has manually adjusted the value to correct for a known system-wide error.</span>
</div>
</div>
</div>
</details>
<div id="stats-grid" class="stats-grid"></div>
<h2 style="margin-bottom:0.6rem">Data Quality</h2>
<div id="quality-strip" class="quality-strip"></div>
<p style="font-size:0.78rem;color:var(--text-muted)">
Quality flags are sourced directly from the AEMO FPP dataset.
<strong style="color:var(--good)">Good (0)</strong> = reliable measurement;
<strong style="color:var(--suspect)">Suspect (1)</strong> = possible communication issue;
<strong style="color:var(--bad)">Bad (2)</strong> = sustained failure or substituted value.
</p>
</section>
<section class="panel">
<h2>4-Second Power Output (MW)</h2>
<div id="scada-chart-container"></div>
</section>
<section class="panel">
<h2>Download SCADA Dataset</h2>
<div class="download-bar" style="margin-bottom:0.75rem">
<span>4-second SCADA data for the selected BESS and date:</span>
<a id="btn-csv" class="btn btn-outline" href="#" download>⬇ CSV</a>
<a id="btn-parquet" class="btn btn-outline" href="#" download>⬇ Parquet</a>
</div>
<p style="font-size:0.78rem;color:var(--text-muted)">
<strong>Parquet</strong> is recommended for Python users — 5–10× smaller than CSV,
loads natively with <code>pandas.read_parquet()</code> or <code>polars.read_parquet()</code>.
</p>
</section>
</div><!-- /scada-results -->
<!-- ── Energy section ── -->
<div id="energy-results" class="hidden">
<section class="panel">
<h2>Dispatch Energy — Summary Statistics</h2>
<details class="dataset-info">
<summary>About this dataset — DISPATCH_UNIT_SOLUTION</summary>
<div class="dataset-info-body">
<p>
Extracted from AEMO's <strong>DISPATCH_UNIT_SOLUTION</strong> table and published
the following day via NEMWEB. Data is fetched live from:
<a href="https://nemweb.com.au/Reports/Current/Next_Day_Dispatch/" target="_blank" rel="noopener">Current directory</a>
(individual daily files, recent months) or the
<a href="https://www.nemweb.com.au/REPORTS/ARCHIVE/Next_Day_Dispatch/" target="_blank" rel="noopener">Archive directory</a>
(monthly bundles for older dates, accessed via HTTP Range requests).
</p>
<div class="col-defs">
<div class="col-def">
<span class="col-name">INITIALMW</span>
<span class="col-desc">Actual power output (MW) at the exact start of the 5-minute dispatch interval. Used as the baseline for the next dispatch instruction.</span>
</div>
<div class="col-def">
<span class="col-name">INITIAL_ENERGY_STORAGE</span>
<span class="col-desc">State of Energy (SoE) at the start of the interval (MWh). Represents how much energy was physically available in the battery before the current interval's dispatch began.</span>
</div>
<div class="col-def">
<span class="col-name">ENERGY_STORAGE</span>
<span class="col-desc">Target or projected energy level at the end of the interval (MWh). Accounts for the expected charging or discharging activity scheduled during that 5-minute block.</span>
</div>
</div>
</div>
</details>
<div id="energy-stats-grid" class="stats-grid"></div>
</section>
<section class="panel">
<h2>5-Minute Initial Energy Storage (MWh) & Dispatch MW</h2>
<div id="energy-chart-container"></div>
</section>
<section class="panel">
<h2>Download Energy Dataset</h2>
<div class="download-bar" style="margin-bottom:0.75rem">
<span>5-minute dispatch energy data for the selected BESS and date:</span>
<a id="btn-energy-csv" class="btn btn-outline" href="#" download>⬇ CSV</a>
<a id="btn-energy-parquet" class="btn btn-outline" href="#" download>⬇ Parquet</a>
</div>
<p style="font-size:0.78rem;color:var(--text-muted)">
Columns: <code>SETTLEMENTDATE</code>,
<code>INITIALMW</code><span class="info-icon" data-tip="Actual MW output at interval start. Used as the dispatch baseline.">ⓘ</span>,
<code>INITIAL_ENERGY_STORAGE</code><span class="info-icon" data-tip="State of Energy (SoE) at interval start (MWh) — energy physically available in the battery before dispatch began.">ⓘ</span>,
<code>ENERGY_STORAGE</code><span class="info-icon" data-tip="Target energy level at interval end (MWh) — accounts for scheduled charging or discharging during the 5-minute block.">ⓘ</span>.
<strong>Parquet</strong> recommended for programmatic use.
</p>
</section>
</div><!-- /energy-results -->
</div><!-- /results-box -->
<!-- ── Info ── -->
<section class="panel">
<h2>About This App</h2>
<p style="font-size:0.875rem;color:var(--text-muted);line-height:1.7">
This tool provides access to two datasets published by the
<a href="https://www.aemo.com.au" target="_blank" rel="noopener">Australian Energy Market Operator (AEMO)</a>
via NEMWEB:<br/><br/>
<strong>4-second SCADA data</strong> — from
<a href="https://www.nemweb.com.au/REPORTS/Current/FPPDAILY/" target="_blank" rel="noopener">NEMWEB FPPDAILY</a>,
published as part of the
<a href="https://aemo.com.au/initiatives/major-programs/frequency-performance-payments-project" target="_blank" rel="noopener">Frequency Performance Payments (FPP)</a>
scheme (commenced 28 February 2025). Currently fetchable from <strong>29 April 2025</strong>;
earlier daily bundles have been rolled off the AEMO archive.<br/><br/>
<strong>5-minute dispatch energy data</strong> — from
<a href="https://nemweb.com.au/Reports/Current/Next_Day_Dispatch/" target="_blank" rel="noopener">NEMWEB Next_Day_Dispatch</a>,
with the <code>INITIAL_ENERGY_STORAGE</code> column added on 11 February 2025.
Currently fetchable from <strong>1 April 2025</strong>; earlier monthly bundles have been rolled off.<br/><br/>
Data is fetched live from AEMO on each request — no data is stored on this server.
Maximum request window: <strong>1 day</strong> per query.
</p>
</section>
</main>
<footer>
<div>
SCADA data: <a href="https://www.nemweb.com.au/REPORTS/Current/FPPDAILY/" target="_blank">AEMO NEMWEB FPPDAILY</a>
|
Energy data: <a href="https://nemweb.com.au/Reports/Current/Next_Day_Dispatch/" target="_blank">AEMO Next_Day_Dispatch</a>
|
BESS list: <a href="https://www.aemo.com.au/energy-systems/electricity/national-electricity-market-nem/planning_and_forecasting/generation-information" target="_blank">AEMO NEM Generation Information</a>
|
Not affiliated with AEMO.
</div>
<div style="margin-top:0.6rem">
This tool is provided for informational and research purposes only. Data is retrieved as-is from
AEMO NEMWEB and is subject to change, correction, or unavailability without notice. No warranty —
express or implied — is made regarding the accuracy, completeness, timeliness, or fitness for any
particular purpose of the data presented. The authors accept no liability for any loss, damage, or
decision made in reliance on this information. Always verify critical data directly with
<a href="https://www.aemo.com.au" target="_blank" rel="noopener">AEMO</a>.
</div>
</footer>
<!-- ── About modal ── -->
<div id="about-modal" class="modal-overlay hidden" role="dialog" aria-modal="true" aria-labelledby="modal-title">
<div class="modal-card">
<div class="modal-header">
<h3 id="modal-title"></h3>
<button id="modal-close" class="modal-close" aria-label="Close">✕</button>
</div>
<div class="modal-body" id="modal-body"></div>
</div>
</div>
<script src="/static/js/app.js?v=__VERSION__"></script>
</body>
</html>
|