One report moves through clear steps
Operators prepare and confirm their own hydropower project data. EDL and NWMC receive only the fields they are allowed to use. They may mark the report as received or ask a question, but they cannot change the operator’s values.
How data enters and moves through the system
A hydropower project may send readings automatically from SCADA or telemetry, or an operator may enter them manually in the web form. Both methods follow the same checks and confirmation.
1. Hydropower project sends or enters data
SCADA and control systems stay inside the project. The website only receives information.
- Automatic: SCADA, meters and sensors send readings
- Manual: operator enters readings in the web form or uploads a file
- The website cannot control turbines, gates or project equipment
2. Check and confirm
New data stays private while the system checks it and an authorized operator reviews it.
- Errors must be fixed; warnings must be checked
- A supervisor confirms the report with secure sign-in
- The confirmed report is locked; corrections create a new version
3. Use approved dashboards
EDL and NWMC receive different views and add information owned by their own organizations.
- EDL adds demand, grid, contract and backup-power data
- NWMC adds official forecasts and downstream warning levels
- Questions, receipt confirmations and actions are recorded
Routine reporting workflow
Normally, one person prepares the report and another authorized person confirms it. A small hydropower project should combine these roles only when this is formally approved.
Four separate progress labels
Do not use one word such as “approved” for four different processes.
| Progress type | Steps | Plain meaning |
|---|---|---|
| Operator report | New task → draft → waiting for confirmation → confirmed → replaced by newer version | How far the operator report has moved |
| Data check | Not checked → error → warning → passed | Whether the data quality checks are complete |
| Delivery | Not shared → shared → received → receipt confirmed | Whether the approved user received it |
| Coordination | No case → request → response → agreed/not agreed → complete | What action the organizations took |
Short emergency form
Urgent release information must not wait for the routine report.
Send urgent notice
Enter the planned release, start time, reason, confidence and duty contact.
Confirm receipt and coordinate
The system saves the case, sends notices and supports downstream checks.
Complete the report
The operator records the decision and action, then sends the full confirmed report.
How often to send data
These are proposed times for the pilot. EDL, NWMC and operators must agree the final deadlines and warning limits.
| Data | If entered manually | If connected automatically | Used for |
|---|---|---|---|
| Electricity readings | Enter or confirm a summary twice daily; hourly when required | Send every 5–15 minutes | Current available power and production |
| Reservoir and flow readings | Enter twice daily during normal conditions | Send every 5–15 minutes with the original time | Reservoir condition and space for floodwater |
| Available power and unit status | Daily and whenever an important change happens | Send when status changes | Check if power supply is enough |
| Next-day energy and release plan | Enter daily by the agreed deadline | Send hourly values for the next 24–72 hours | Energy and water planning |
| Next 7 days | Update daily | Update after each forecast | Outage and risk planning |
| Wet / dry season | Monthly; weekly in watch conditions | Update when the forecast changes | Seasonal energy and water security |
| Unexpected outage or major release | Enter immediately | Send when the event happens; receipt must be confirmed | Urgent action |
How the one database is organized
All information stays in one PostgreSQL database. Separate protected areas keep incoming data, confirmed operator reports, EDL and NWMC data, dashboard results and history under the right access rules.
| Database area | Main records | Why it exists | Who can access it |
|---|---|---|---|
| master — Project reference data | companies, projects, reservoirs, units, stations, curves, limits | Keeps approved project names, equipment and safe limits | Approved users can read; data manager can change |
| intake — Incoming data | new messages, SCADA batches, manual form entries, import errors | Receives SCADA/telemetry, file uploads and manual web forms before checks | Private; system services only |
| operations — Project reports | reports, readings, unit status, water records, versions | Stores operator-owned readings and every confirmed version | Limited by organization, project and allowed use |
| planning — Plans and events | available power, energy plans, release plans, outages | Stores future plans, limits and events | Limited by role and data type |
| institutional — EDL and authority data | EDL demand, grid limits, forecasts, warning levels | Stores data owned by EDL and government authorities | Owner can change; approved users can read |
| workflow — Questions and action | cases, decisions, notices, receipt confirmations | Keeps the full coordination record | Approved duty staff |
| analytics — Secure dashboards | approved views, summaries, calculated indicators | Powers the EDL and water dashboards | Users see only their approved view |
| audit — History | activity, data checks, access history | Keeps changes and responsibility clear | Private; data manager and auditor |
Only the right people see each report
Database permissions limit access by organization, project, job and data type. Powerful system passwords stay on the server. Confirmation and administrator work require secure sign-in.
Important notices are saved and tracked
Every important notice is stored, tried again if delivery fails and kept open until the responsible user confirms receipt. This protects the record during network problems.
Corrections never erase the old record
Every report keeps its owner, source, reading time, receipt time, quality, version, preparer, supervisor and reason for a change.