Data guide

109 data fields: what is needed, who provides it and why

This list covers electricity production, hydropower project condition, reservoir condition, flood coordination and the EDL and government data needed for useful analysis.

The proposed reporting times are for the pilot. Lao institutions must approve the final requirements, deadlines and warning limits.

Operators have two equal ways to provide readings: send them automatically from SCADA or telemetry, or enter them manually in the web form. Both methods use the same database, data checks, operator review and supervisor confirmation.

Data owner

Every field has an owner

Every value shows who provides it, why it is needed, its unit, when it is updated and who may see it.

Time

Keep four timestamps

Store when the value was observed, received, submitted and confirmed.

Data quality

Zero is not missing

Show if a value was measured, estimated, replaced, missing because of a sensor fault or not needed.

History

Keep every version

A correction creates a new confirmed version. Keep the earlier value, reason, person and time.

Information saved with every value

This helps operators, EDL and government teams see who provided each value, when it applies and whether it is confirmed.

Provider · provider_orgSource system · source_systemRecord type · record_typeHow entered · methodReading time · observation_timeForecast issued · issue_timeTime covered · valid_timeReceived time · received_atQuality · quality_codePossible range · uncertaintyVersion · revisionConfirmed by · certified_byConfirmation time · certified_atWho may see it · classification

Energy · current power and unit statusOperator web form or automatic SCADA / telemetry feed12 fields

Data field	Unit / type	When updated	Required / owner	Why it is needed
Generating unit status	status	Automatic feed or important change	Required	Online, standby, outage, maintenance, condensing
Power made before project use (gross)	MW	Automatic feed	When relevant	Power made before the project uses some of it
Power sent to the grid (net)	MW	Automatic feed	Required	Power measured at the agreed grid meter
Energy made / energy sent to the grid	MWh per interval	15–60 min	Required	Compare energy made with energy sent to the grid
Energy used inside the project	MW, MWh	15–60 min	Required	Show how much energy the project uses itself
Reactive power / voltage / frequency	MVAr, kV, Hz	Automatic feed	When relevant	Automatic grid-support readings; do not type by hand
Power available now	MW	Hourly / change	Required	Power the operator says the project can safely provide
Power that is reduced or unavailable	MW	Event	Required	How much power is unavailable and why
Ability to increase or reduce output	MW	15–60 min	Required	How much output can go up or down now
Water through turbines / usable water height	m³/s, m	Automatic feed	Required	Connect water use with electricity production
Start, stop, synchronization, trip	timestamp	Event	Required	Project start, stop and trip history
Energy not produced and the reason	MW, MWh, code	Event / interval	Required when used	Separate grid, water, environment and equipment causes

Energy · available power, next-day plan and fast responseOperator enters and confirms this in the web form12 fields

Data field	Unit / type	When updated	Required / owner	Why it is needed
Installed and net maximum capacity	MW	Set once; update when changed	Required	Approved project and unit capability
Reliable power in wet / dry season	MW	Seasonal	Required	Season-specific firm contribution
Lowest safe output / safe output range	MW	Set once; update when changed	Required	Feasible dispatch envelope
Lowest / highest available power by time	MW	Next-day plan / update	Required	Day-ahead supply declaration
Planned power by time	MW, MWh	Next-day plan / update	Required	24–48 h expected production
Domestic commitment / export commitment	MW, MWh	Next-day plan / contract	When relevant	Purpose-limited; contract owner validates
Energy available if EDL changes the plan	MWh	Daily	Required	EDL operational flexibility
How fast output can increase or decrease	MW/min	Hourly / change	Required	Current feasible ramp
Startup time / minimum up-down time	min, h	Set once; update when changed	Required / conditional	Commitment feasibility
Backup power available and for how long	MW, min or h	Next-day plan / intraday	When relevant	Only where applicable by arrangement
Black-start / synchronous condenser	status, MW/MVAr	Daily / test	When relevant	Restoration and voltage support
Reason for a limit, its effect and confidence	code, MW, level	Each plan	Required	Reason and quality of declaration

Energy · outages, reliability and maintenanceOperator web form plus system calculations12 fields

Data field	Unit / type	When updated	Required / owner	Why it is needed
Outage or reduced-power event ID	Unique ID	Event	Required	Persistent event identity
Type of event	planned / maintenance / forced / grid	Event	Required	Standard attribution
Start and actual / expected end	timestamp	Event / update	Required	Duration and return forecast
Affected unit and capacity lost	ID, MW	Event	Required	Supply impact
Cause and responsible party	code + text	Event	Required	Fair responsibility attribution
Expected return time and confidence	timestamp, level	On change	Required	Future supply planning
12-month outage calendar	start, end, MW	Monthly / change	Required	12-month coordination
Service / reserve-shutdown / available hours	hours	Calculated monthly	Required	Reliability basis
Planned / forced outage hours	hours	Calculated monthly	Required	Availability metrics
Derating MW-hours	MW-h	Calculated monthly	Required	Equivalent capacity loss
Attempted / successful starts	count	Event / monthly	Required	Start reliability
Trips, MTBF and MTTR	count, hours	Calculated monthly	Required	Reliability trend

Energy · wet/dry supply, efficiency and sustainabilityOperator web form plus water data and system calculations13 fields

Data field	Unit / type	When updated	Required / owner	Why it is needed
7-day generation forecast	MWh/day	Daily	Required	Near-term supply outlook
1–3 month generation scenarios	GWh/week or month	Weekly / monthly	Required	Low, central and high cases
Dry-season firm energy	GWh	Monthly / seasonal	Required	Energy security at agreed confidence
Wet-season expected energy	GWh	Monthly / seasonal	Required	Absorption, spill and export planning
Energy that can be made from stored water	MWh / GWh	Calculated daily	Required	Reservoir water expressed as energy
Planned reservoir use and filling by season	level, storage, energy	Weekly	Required	Water-energy operating plan
Water or river-flow limit on energy	MW, MWh	Weekly / change	Required	Forecast impact by cause
Water through turbines and spillway	m³	Calculated daily	Required	Water use and opportunity analysis
Water used for each unit of energy	m³/MWh	Calculated daily	Required	Efficiency indicator within the project
Share of water energy changed into electricity	%	Interval / monthly	When relevant	Requires calibrated head, flow and power
Auxiliary-load ratio / renewable delivery	%, MWh	Daily / monthly	Required	Net productivity
Minimum river-flow requirement met	status / %	Daily / event	When relevant	Operational sustainability
Site GHG intensity / certification	gCO₂e/kWh, status	Annual / study	Optional	Use recognized site-specific method

Water · reservoir design and safe limitsApproved reference data from the operator or authority13 fields

Data field	Unit / type	When updated	Required / owner	Why it is needed
Reservoir type, catchment and cascade order	code, km², sequence	Set once; update when changed	Required	Storage, pondage or run-of-river logic
Location and water-level reference	GIS, datum/version	Set once; update when changed	Required	Spatial and vertical consistency
Table linking water level, area and storage	versioned tables	Set once; update when changed	Required	Never replace with one capacity number
Dead / minimum / normal / maximum levels	m MSL, Mm³	Set once; update when changed	Required	Approved operating bounds
Seasonal target water level	date–level/storage	Set once; update when changed	Required	Target operating trajectory
Flood-control water-level limits	m MSL, Mm³	Seasonal / change	When relevant	Required for storage reservoirs
Turbine / spillway / outlet capacity curves	m³/s vs head/gate	Set once; update after a test	Required	Physical release envelope
Table linking gate opening and water flow	position–flow table	Set once; update after a test	Required	Convert gate state to flow
Environmental minimum flow	m³/s, seasonal	Set once; update when changed	Required	Ecological operating constraint
Limits on how fast water release may change	m³/s/h, m/h	Set once; update when changed	Required	Safety and environmental constraint
Downstream river stations and warning levels	IDs, m, m³/s	Set once; update when changed	Required	Alert, alarm and danger context
Model of water movement and travel time	model/version	Calibrate / change	Required for cascade	Flow-dependent; not one fixed travel time
Operating manual / emergency-plan version	document IDs	Set once; update when changed	Required	Legal and procedural traceability

Water · current reservoir condition and releasesOperator web form or automatic SCADA / telemetry feed16 fields

Data field	Unit / type	When updated	Required / owner	Why it is needed
Reading time and how old the sensor data is	timestamp, age	Automatic feed	Required	Separate observation from receipt time
Reservoir level / river level below the dam	m above named datum	Automatic feed or web-form reading	Required	Reservoir state and head
Reservoir storage / surface area	Mm³, km²	Automatic or manual; system calculated	Required / optional	Approved curve result
Measured or calculated water entering the reservoir	m³/s	Automatic feed or web-form reading	Required	Method must be stated
Local rainfall / tributary inflows	mm, m³/s	Automatic feed	When relevant	Operator-observed contributions
Evaporation / seepage / withdrawals	Mm³/day, m³/s	Daily	When relevant	Water-balance components
Turbine release	m³/s	Automatic feed or web-form reading	Required	Energy and release balance
Spillway release	m³/s	Automatic feed or web-form reading	Required	Flood and energy impact
Water through the bottom outlet or bypass	m³/s	Automatic feed or web-form reading	Required	Complete outflow
Environmental / fish passage release	m³/s	Automatic feed or web-form reading	When relevant	Compliance
Total release	m³/s	Automatic or manual; system checked	Required	Sum of all release components
Gate status and opening	status, % or m	Automatic feed or important change	Required restricted	Operational state, purpose limited
Release equipment and turbine availability	status	Automatic feed or important change	Required	Maximum feasible release
Current limit or emergency level	code + text	Event	Required	Normal, watch, warning, emergency
Water quality / sediment	°C, DO, NTU, mg/L	Hourly / daily	When relevant	Licence and sustainability monitoring
Data quality, possible range and reason for a change	codes / ± value	Every value	Required	Traceability and confidence

Water · forecast, release plan and coordinationOperator web form, official forecast and system calculations17 fields

Data field	Unit / type	When updated	Required / owner	Why it is needed
Forecast provider and model version	IDs	Each cycle	Required	Operator and official forecasts stay distinct
When the forecast was made and the time it covers	timestamps, hours	Each cycle	Required	Which forecast was used
Forecast inflow series / peak / volume	m³/s, Mm³	Each cycle	Required	P10/P50/P90 or ensemble
Official rainfall forecast	mm, probability	Each cycle	Required	Authority-owned input
Upstream release plan and expected arrival	m³/s, timestamp range	Plan / event	Required for cascade	Routed cascade coordination
Target level / storage	m MSL, Mm³	Plan / event	Required	Operator end-of-horizon target
Planned turbine / spill / bypass profile	m³/s by time	Plan / event	Required	Release intent
Plan start / end / ramp rate	timestamps, m³/s/h	Plan / event	Required	Execution envelope
Reason for an early release	code + text	Event	Required during event	Reason for proposal
Extra water in the early release	Mm³	Event	Required during event	Plan above baseline
No-change case and other choices	versioned IDs	Event	Required during event	Transparent comparison
Expected storage / space for floodwater	Mm³, %	Cycle / plan	Calculated	Forward reservoir condition
Downstream flow, water level and arrival time	m³/s, m, time range	Event	Calculated	Calibrated routing/hydraulic model
Chance of passing a warning level	%	Event	Calculated	Chance of passing a warning level
Energy consequence	MW, MWh	Event	Calculated	Imported from energy module
Plan, decision and notice status	workflow states	Event	Required	Versioned accountability
Actual release compared with approved plan	m³/s deviation	Automatic feed during an event	Required	Execution monitoring

Data from EDL and government agencies · not entered by the operatorEDL and water-authority data14 fields

Data field	Unit / type	When updated	Required / owner	Why it is needed
Current and expected electricity demand	MW, MWh	Hourly / Next-day plan	EDL	Supply-demand balance
Peak demand and uncertainty	MW, timestamp, range	Daily / seasonal	EDL	Adequacy and scenario analysis
Available power from all energy sources	MW, MWh	Hourly / daily	EDL	National system—not hydro alone
EDL generation plans and instructions	MW by interval	Next-day plan / intraday	EDL	Plan-performance attribution
Backup power needed and available	MW	Automatic feed / hourly	EDL	Operational security
Imports, exports and transfer limits	MW, MWh	Hourly / change	EDL	Net balance and deliverability
Power-line outages and limits	equipment, MW	Event	EDL	Grid constraint attribution
Losses, load shedding and unserved energy	%, MWh	Daily / event	EDL	Reliability outcome
Power available to EDL under contracts	MW / MWh	Next-day plan / contract	EDL / contract owner	Separate from technical availability
Official rainfall / river forecast	series + uncertainty	Forecast cycle	Authorized authority	National forecast remains official
National and MRC gauge observations	m, m³/s	Automatic feed / cycle	Authorized authority	Basin and transboundary context
Downstream warning levels and places at risk	m, m³/s, GIS	Set once; update when changed	Water authority	Impact assessment
Official event level / coordination rules	status / protocol	Event / change	Designated authority	Actions and legal basis
Dry-season allocation / flow objective	m³/s, volume	Seasonal	Designated authority	Water-security target

Recommended first version for operators

Start with the information needed for the pilot. More advanced fields can be added later.

1Operators enter and confirm available power, the next-day plan, outages, limits and expected return dates in the web form.

2Actual MW, MWh, unit status and water readings may also arrive automatically from SCADA or telemetry.

3Collect reservoir level and storage, inflow, turbine water, spillway water, other releases and the planned release.

4Keep the data source, time, quality, confidence, confirmation, version and full change history.

Main calculated indicators

Use the official NERC and IEEE definitions for formal hydropower project availability and reliability reports.

Power left after demandUsable supply − demand − required backup

Share of possible energy producedNet MWh ÷ (maximum MW × hours)

Water used for each unit of energyWater through turbines ÷ net MWh

Total releaseTurbine + spill + bypass + other

Space for floodwaterApproved flood target − current storage

Difference from release planActual release − approved release

Standards and reference sources

International standards guide the design. Lao institutions must approve local definitions, limits and responsibilities.

109 data fields: what is needed, who provides it and why

Every field has an owner

Keep four timestamps

Zero is not missing

Keep every version

Information saved with every value

Recommended first version for operators

Main calculated indicators

Standards and reference sources

IEA · electricity security

IEA · hydropower flexibility

NERC · generator capability

IEEE 762 · unit reliability

MRC · hydrology guidance

MRC · data sharing

WMO · hydrology publications

IHA · sustainability standard