Irrigation Department

Tell us what to change or add.

Your name (optional)Your roleReview date

Continue a saved review

1. Check a decision

Open a decision below. Check the area, period, inputs, result and proposed next step.

2. Try the inputs

Use Example input to change a sample. Use Source input to check the fields and source details. The land-use change decision has its own comparison views.

Record your corrections below, then download your answers or print them.

3. Check each decision

1. Prepare additional irrigation allocation proposals 2. Restore stale river and reservoir observations 3. Choose what to handle first: canals with delivery shortfalls 4. Review storage consequences of proposed releases 5. Escalate dam inspection defects requiring engineering action 6. Prepare response options from authorized hydrological evidence 7. Compare feasible drought water-allocation alternatives 8. Choose what to handle first: bathymetric surveys and desilting appraisal 9. Choose what to handle first: repair packages within engineering and budget limits 10. Select drainage improvements for persistently waterlogged areas 11. Check saline intrusion affecting irrigated land 12. Schedule approved gate operations without conflicts 13. Target schemes with low crop output per water delivered 14. Flag proposed releases inconsistent with reviewed flow conditions 15. Require reproducible calibration before model use 16. Compare energy performance of lift-irrigation stations 17. Appraise reservoir rehabilitation cash-flow alternatives 18. Check delayed irrigation construction milestones 19. Prevent shortages of critical irrigation equipment spares 20. Correct missing metadata in published reservoir information

1. Prepare additional irrigation allocation proposalsDEC-DP05-001 · Command water demand · Suggested priority: High

Try this decision

Prepare additional irrigation allocation proposals.

Verified published component · Crop evapotranspiration ETc component

Method. ETc = ETo × Kc. Net = max(0, ETc + percolation + desired storage increase − rainfall after runoff − capillary contribution). Gross = net × hectares ×10 / application efficiency.

Next step. Review evidence. Propose crop demand, scheduling or allocation alternatives for authorized review.

Inputs, example and sources

Food and Agriculture Organization of the United Nations · FAO Irrigation and Drainage Paper 56 Crop Evapotranspiration
Institution publication · Chapter 5, Crop coefficient approach, equation 56

This verifies the ETc component only. Local water-balance allowances, coefficients and operating decisions still need confirmation.

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Irrigated crop area [ha]; Reference evapotranspiration [mm/day]; Crop coefficient [ratio]; Rainfall reaching the field after runoff [mm/day]; Deep percolation and paddy allowance [mm/day]; Capillary contribution [mm/day]; Desired change in stored soil water [mm/day]; Field application efficiency [fraction]

Other required evidence. Command hectares; crop stage; evapotranspiration; rainfall; percolation; efficiency.

Fictional worked example · 2025

Laggala Pallegama — command water demand · Laggala Pallegama

Input or result	Value	Unit
Irrigated crop area	85	ha
Reference evapotranspiration	4.5	mm/day
Crop coefficient	1.1	ratio
Rainfall reaching the field after runoff	1.6	mm/day
Deep percolation and paddy allowance	2	mm/day
Capillary contribution	0	mm/day
Desired change in stored soil water	0	mm/day
Field application efficiency	0.68	fraction
Gross daily irrigation requirement	6,687.5	m³/day
Net field requirement	5.35	mm/day

The full local balance, rooting depth, stress, crop stage and operating constraints still matter. The paddy allowance is explicit and must be zero where inapplicable. This is not an authorized reservoir release.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Delivered water, crop stress, unmet demand and downstream conditions.

FAO 56: crop evapotranspiration — Institution publication. FAO 56 Chapter 5 equation 56; ETc = Kc × ETo. Institutional context; does not establish the calculation or local approval.
FAO56 root-zone water balance — Institution publication. Chapter8 equation85 and ETc = Kc ETo. Daily water balance components; local coefficients and operating assumptions still need review.
FAO Irrigation Water Management Training Manual 3 — Institution publication. Chapter 4.4 Irrigation water need of rice; steps 1 to 8. Institutional context; does not establish the calculation or local approval.
SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decisionDoes this decision belong to your institution?Is the required data list complete?Are the sources, places and time periods suitable?Can staff use the proposed entry or upload steps?Are the calculation, units and limits correct?Do the chart and result help you decide?Are the checking officer and decision authority correct?Are the access and sharing limits suitable?

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

2. Restore stale river and reservoir observationsDEC-DP05-002 · Gauge operations · Suggested priority: High

Try this decision

Restore stale river and reservoir observations.

Validation required

Method. Completeness = 100 × valid / expected. Age = assessment date − latest valid observation; compare with the explicitly supplied interval.

Next step. Check overdue observation. Repair missed observations, contact the owner, or suspend stale evidence from current decisions.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Expected observations in the window [observations]; Distinct valid observations [observations]; Latest valid observation; Assessment date; Required observation interval [days]

Other required evidence. Gauge ID; observation schedule; last valid reading; outage duration; calibration.

Fictional worked example · 2025

Laggala Pallegama — gauge operations · Laggala Pallegama

Input or result	Value	Unit
Expected observations in the window	30	observations
Distinct valid observations	24	observations
Latest valid observation	2025-06-28
Assessment date	2025-06-30
Required observation interval	1	days
Completeness	80	%
Age of latest observation	2	days
Missing observations	6	observations

A recent observation does not fill earlier gaps. Unknown schedule or observation time cannot establish freshness.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Valid observations received on time and recurring gaps.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

3. Choose what to handle first: canals with delivery shortfallsDEC-DP05-003 · Canal performance · Suggested priority: High

Try this decision

Prioritize canals with delivery shortfalls.

Validation required

Method. Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive.

Next step. Review evidence. Investigate a material deviation, assign correction, or propose a target revision.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Planned value [m³]; Observed value [m³]

Other required evidence. Canal outlet; planned cubic metres; delivered cubic metres; period; command area.

Fictional worked example · 2025

Laggala Pallegama — canal performance · Laggala Pallegama

Input or result	Value	Unit
Planned value	100	m³
Observed value	90	m³
Difference	-10	m³
Relative change	-10	%

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Subsequent variance with original and revised targets retained.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

4. Review storage consequences of proposed releasesDEC-DP05-004 · Reservoir operation · Suggested priority: High

Try this decision

Review storage consequences of proposed releases.

Validation required

Method. Calculated closing = opening + inflows − releases/transfers − other outflows. Residual = independently observed closing − calculated closing.

Next step. Reconcile closing balance. Investigate unexplained balances and propose revised measurement or operating action.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Opening storage [m³]; All measured inflows and transfers in [m³]; Releases and transfers out [m³]; Evaporation and other outflows [m³]; Independently observed closing storage [m³]

Other required evidence. Opening storage; inflow; irrigation release; spill; evaporation; closing survey.

Fictional worked example · 2025

Laggala Pallegama — reservoir operation · Laggala Pallegama

Input or result	Value	Unit
Opening storage	160,000	m³
All measured inflows and transfers in	48,000	m³
Releases and transfers out	35,000	m³
Evaporation and other outflows	9,000	m³
Independently observed closing storage	163,500	m³
Calculated closing storage	164,000	m³
Observed minus calculated closing	-500	m³

Use the same physical boundary, period and units. A residual is a reconciliation issue, not automatically a measured loss.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Reconciled balance residuals and verified operating results.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

5. Escalate dam inspection defects requiring engineering actionDEC-DP05-005 · Dam safety · Suggested priority: High

Try this decision

Escalate dam inspection defects requiring engineering action.

Validation required

Method. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.

Next step. Complete the evidence. Request correction, refer mandatory failures, or accept the inspected item with conditions.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Dam ID; Dam ID evidence reference; seepage; seepage evidence reference; deformation; deformation evidence reference; inspection findings; inspection findings evidence reference; approved limits; approved limits evidence reference; responsible engineer; responsible engineer evidence reference

Other required evidence. Dam ID; seepage; deformation; inspection findings; approved limits; responsible engineer.

Fictional worked example · 2025

Laggala Pallegama — dam safety · Laggala Pallegama

Input or result	Value	Unit
Dam ID	Missing
Dam ID evidence reference
seepage	Documented
seepage evidence reference	Sample Laggala Pallegama field register / 2025
deformation	Documented
deformation evidence reference	Sample Laggala Pallegama field register / 2025
inspection findings	Documented
inspection findings evidence reference	Sample Laggala Pallegama field register / 2025
approved limits	Documented
approved limits evidence reference	Sample Laggala Pallegama field register / 2025
responsible engineer	Documented
responsible engineer evidence reference	Sample Laggala Pallegama field register / 2025
Evidence gaps	1	items

Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Evidence-backed corrective closure and recurring nonconformances.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

6. Prepare response options from authorized hydrological evidenceDEC-DP05-006 · Flood readiness · Suggested priority: High

Try this decision

Prepare response options from authorized hydrological evidence.

Validation required

Method. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.

Next step. Complete the evidence. Select a feasible control, escalate beyond authority, or seek technical inspection.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. River levels; River levels evidence reference; official forecast; official forecast evidence reference; flood exposure; flood exposure evidence reference; warning protocol; warning protocol evidence reference; evacuation constraints; evacuation constraints evidence reference; Documented unresolved critical condition; Evidence observation date; Existing control and its evidence; Competent recipient

Other required evidence. River levels; official forecast; flood exposure; warning protocol; evacuation constraints.

Fictional worked example · 2025

Laggala Pallegama — flood readiness · Laggala Pallegama

Input or result	Value	Unit
River levels	Missing
River levels evidence reference
official forecast	Documented
official forecast evidence reference	Sample Laggala Pallegama field register / 2025
flood exposure	Documented
flood exposure evidence reference	Sample Laggala Pallegama field register / 2025
warning protocol	Documented
warning protocol evidence reference	Sample Laggala Pallegama field register / 2025
evacuation constraints	Documented
evacuation constraints evidence reference	Sample Laggala Pallegama field register / 2025
Documented unresolved critical condition	Unknown
Evidence observation date	2025-06-30
Existing control and its evidence	Sample documented control
Competent recipient	Responsible specialist / duty authority
Evidence gaps	1	items

Show the hazard, exposure and verified controls separately. No generic score, probability, diagnosis, site clearance or official warning is derived from a count.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Verified control effectiveness and residual risk with evidence.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

7. Compare feasible drought water-allocation alternativesDEC-DP05-007 · Drought allocation · Suggested priority: High

Try this decision

Compare feasible drought water-allocation alternatives.

Validation required

Method. Budget minus option cost. Compare benefits, adverse effects and mandatory constraints separately; no weighted score or automatic best option.

Next step. Compare feasible trade-offs. Choose a feasible alternative with rationale and conditions, commission evidence, or defer.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Expected benefit and its evidence; Resource needs and adverse effects

Other required evidence. Dependable storage; sector demand; environmental requirements; allocation rules; uncertainty.

Fictional worked example · 2025

Canal repair · Laggala Pallegama

Input or result	Value	Unit
Option cost	1,500,000	LKR
Available budget	1,800,000	LKR
Mandatory constraints	Met
Expected benefit and its evidence	Compare feasible drought water-allocation alternatives; Dependable storage and sector demand evidence needed
Resource needs and adverse effects	Sample water, labour, access and safeguard trade-offs
Budget remaining after option	300,000	LKR

Affordability does not prove feasibility or scientific suitability. A missing mandatory condition keeps an option unresolved.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Verified benefits, costs and adverse effects versus the agreed baseline.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

8. Choose what to handle first: bathymetric surveys and desilting appraisalDEC-DP05-008 · Reservoir sedimentation · Suggested priority: High

Try this decision

Prioritize bathymetric surveys and desilting appraisal.

Validation required

Method. Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive.

Next step. Review evidence. Accept a genuine change for planning review, investigate a discontinuity, or defer comparison.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Earlier/source value [m³]; Later/comparison value [m³]

Other required evidence. Storage survey editions; sediment volume; usable capacity; survey accuracy; dates.

Fictional worked example · 2025

Laggala Pallegama — reservoir sedimentation · Laggala Pallegama

Input or result	Value	Unit
Earlier/source value	100	m³
Later/comparison value	90	m³
Difference	-10	m³
Relative change	-10	%

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Comparable change after the chosen action and unresolved discrepancies.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

9. Choose what to handle first: repair packages within engineering and budget limitsDEC-DP05-009 · Canal rehabilitation · Suggested priority: High

Try this decision

Prioritize repair packages within engineering and budget limits.

Validation required

Method. Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately.

Next step. Follow up overdue case. Authorize feasible repair through the proper work process, inspect further, or restrict unsafe use.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed

Other required evidence. Asset condition; defects; service criticality; repair options; costs; inspection date.

Fictional worked example · 2025

Laggala Pallegama — canal rehabilitation · Laggala Pallegama

Input or result	Value	Unit
Received or defect observed	2025-04-01
Recorded due date	2025-06-01
Assessment date	2025-06-30
Case/work closed	No
Documented critical unresolved condition	Unknown
Responsible office or maintainer	Proposed responsible office
Actual closure date when closed
Open days past due	29	days
Calendar age	90	days

Example due dates are not legal service standards. Do not alter statutory deadlines by silently subtracting pauses, or infer severity from age alone.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Verified defect closure, service availability and repeat failures.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

10. Select drainage improvements for persistently waterlogged areasDEC-DP05-010 · Drainage · Suggested priority: High

Try this decision

Select drainage improvements for persistently waterlogged areas.

Validation required

Method. Budget minus option cost. Compare benefits, adverse effects and mandatory constraints separately; no weighted score or automatic best option.

Next step. Compare feasible trade-offs. Choose a feasible alternative with rationale and conditions, commission evidence, or defer.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Expected benefit and its evidence; Resource needs and adverse effects

Other required evidence. Flood duration; drainage network; outlet capacity; affected hectares; engineering options.

Fictional worked example · 2025

Canal repair · Laggala Pallegama

Input or result	Value	Unit
Option cost	1,500,000	LKR
Available budget	1,800,000	LKR
Mandatory constraints	Met
Expected benefit and its evidence	Select drainage improvements for persistently waterlogged areas; Flood duration and drainage network evidence needed
Resource needs and adverse effects	Sample water, labour, access and safeguard trade-offs
Budget remaining after option	300,000	LKR

Affordability does not prove feasibility or scientific suitability. A missing mandatory condition keeps an option unresolved.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Verified benefits, costs and adverse effects versus the agreed baseline.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

11. Check saline intrusion affecting irrigated landDEC-DP05-011 · Salinity exclusion · Suggested priority: High

Try this decision

Investigate saline intrusion affecting irrigated land.

Validation required

Method. Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status.

Next step. Outside example comparison bounds. Refer a confirmed nonconformance for authorized response, resample, or investigate the method.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Parameter and applicable use; Measured result [µS/cm]; Example lower comparison bound [µS/cm]; Example upper comparison bound [µS/cm]; Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis

Other required evidence. Water conductivity; tide stage; gate status; crop use; reviewed salinity limits.

Fictional worked example · 2025

Laggala Pallegama — salinity exclusion · Laggala Pallegama

Input or result	Value	Unit
Parameter and applicable use	Irrigation-water electrical conductivity
Measured result	2,500	µS/cm
Example lower comparison bound	0	µS/cm
Example upper comparison bound	2,000	µS/cm
Original and limit unit	µS/cm
Sampling and analytical method/version	Sample laboratory method
Limit source, version and use	Fictional comparison bounds; not a regulatory limit
Parameter, unit, use and averaging period match	Yes
Result is below a reporting/detection limit	No
Averaging interval, sampling depth or process basis	Sample stated sampling/averaging basis
Measured value	2,500	µS/cm

Example bounds establish no compliance or diagnosis. Ambient, drinking-water, effluent, crop, food, air and noise standards are not interchangeable. A censored result is not an exact zero.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Follow-up compliance, exposure/service condition and corrective closure.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

12. Schedule approved gate operations without conflictsDEC-DP05-012 · Gate scheduling · Suggested priority: High

Try this decision

Schedule approved gate operations without conflicts.

Validation required

Method. Check start/end order, operating window, effort, predecessor completion and overlapping bookings for the same resource. A conflict is flagged; no optimal schedule is invented.

Next step. Resolve overlapping resource bookings. Assign a feasible timetable, redistribute resources, or escalate the blocked dependency.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites

Other required evidence. Release approval; gate capacity; operator availability; downstream constraints; operating windows.

Fictional worked example · 2025

Laggala Pallegama — gate scheduling · Laggala Pallegama

Input or result	Value	Unit
Required resource	Watershed field team
Task start	2025-06-01
Task end	2025-06-04
Earliest permitted start	2025-05-28
Latest permitted finish	2025-06-08
Required resource effort	16	hours
Available resource effort	24	hours
Predecessor task reference	None
Mandatory permits and prerequisites	Met
Planned duration	3	days
Resource hours remaining	8	hours

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. On-time completion with verified outputs and resource use.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

13. Target schemes with low crop output per water deliveredDEC-DP05-013 · Water productivity · Suggested priority: Medium

Try this decision

Target schemes with low crop output per water delivered.

Validation required

Method. Saleable crop output / Matching irrigation water input, for the same product, process and period.

Next step. Review evidence. Investigate low productivity, compare practices, or improve the input/output measurements.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Saleable crop output [kg]; Matching irrigation water input [m³]

Other required evidence. Crop output kg; delivered cubic metres; command hectares; crop; season.

Fictional worked example · 2025

Laggala Pallegama — water productivity · Laggala Pallegama

Input or result	Value	Unit
Saleable crop output	19,780	kg
Matching irrigation water input	7,200	m³
Crop water productivity	2.747	kg/m³

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Output per relevant input alongside quality and resource impacts.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

14. Flag proposed releases inconsistent with reviewed flow conditionsDEC-DP05-014 · Environmental flows · Suggested priority: High

Try this decision

Flag proposed releases inconsistent with reviewed flow conditions.

Validation required

Method. Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive.

Next step. Review evidence. Investigate a material deviation, assign correction, or propose a target revision.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Planned value [m³/s]; Observed value [m³/s]

Other required evidence. Release proposal; flow obligation; dates; monitoring point; measured flow.

Fictional worked example · 2025

Laggala Pallegama — environmental flows · Laggala Pallegama

Input or result	Value	Unit
Planned value	100	m³/s
Observed value	90	m³/s
Difference	-10	m³/s
Relative change	-10	%

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Subsequent variance with original and revised targets retained.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

15. Require reproducible calibration before model useDEC-DP05-015 · Hydrological models · Suggested priority: Medium

Try this decision

Require reproducible calibration before model use.

Validation required

Method. Reproduced minus expected result, within an explicitly supplied absolute tolerance, using the same exact input/method versions and a separate checker. Retain originals, code, parameters and environment evidence.

Next step. Investigate reproduction difference. Accept reproducible evidence for review, investigate differences, or withhold an unsupported result.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Earlier/source value [m³/s]; Independently reproduced value [m³/s]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [m³/s]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer

Other required evidence. Model version; rainfall; flow; calibration period; validation period; performance criteria.

Fictional worked example · 2025

Laggala Pallegama — hydrological models · Laggala Pallegama

Input or result	Value	Unit
Earlier/source value	100	m³/s
Independently reproduced value	90	m³/s
Original measurement unit	Sample matching unit
Comparison measurement unit	Sample matching unit
Compared measure and definition	Sample comparable m³/s measure; same input scope
Documented absolute comparison tolerance	0.01	m³/s
Expected input/method version	Sample input1 /method1
Reproduced input/method version	Sample input1 /method1
Original result creator	Preparation officer
Independent reproducer	Independent checking officer
Difference	-10	m³/s
Relative change	-10	%

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Independent reproduction within the approved tolerance.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

16. Compare energy performance of lift-irrigation stationsDEC-DP05-016 · Pumping systems · Suggested priority: Medium

Try this decision

Compare energy performance of lift-irrigation stations.

Validation required

Method. Electric energy consumed / Water pumped, for the same product, process and period.

Next step. Review evidence. Investigate low productivity, compare practices, or improve the input/output measurements.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Electric energy consumed [kWh]; Water pumped [m³]

Other required evidence. Delivered cubic metres; energy kWh; pumping head; operating hours; station ID.

Fictional worked example · 2025

Laggala Pallegama — pumping systems · Laggala Pallegama

Input or result	Value	Unit
Electric energy consumed	3,128	kWh
Water pumped	18,000	m³
Specific energy use	0.174	kWh/m³

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Output per relevant input alongside quality and resource impacts.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

17. Appraise reservoir rehabilitation cash-flow alternativesDEC-DP05-017 · Rehabilitation investment · Suggested priority: High

Try this decision

Appraise reservoir rehabilitation cash-flow alternatives.

Verified published formula · Discounted cash-flow NPV

Method. NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5.

Next step. Review evidence. Compare feasible investments, adjust the scope, or defer pending finance/evidence.

Inputs, example and sources

Food and Agriculture Organization of the United Nations · Guidelines for defining financial economic environmental and social information
Institution publication · Sections 2.2.2 and 2.2.3, discounting and Net Present Value

The five-year horizon, discount rate and cash assumptions are local settings. Verification does not approve an investment or loan.

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%]

Other required evidence. Capital cost; maintenance; avoided losses; benefits; discount rate; project life.

Fictional worked example · 2025

Laggala Pallegama — rehabilitation investment · Laggala Pallegama

Input or result	Value	Unit
Initial investment	2,400,000	LKR
Net cash flow year1	400,000	LKR
Net cash flow year2	550,000	LKR
Net cash flow year3	680,000	LKR
Net cash flow year4	720,000	LKR
Net cash flow year5	760,000	LKR
Residual value at end of year5	120,000	LKR
Example discount rate	8	%
Five-year net present value	109,847.353	LKR

Match currency, price year, real/nominal basis and cash-flow timing. The example rate and five-year horizon are assumptions, not institutional financing terms; no credit approval follows.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Realized cash flows, benefits and costs versus the approved appraisal.

FAO Guidelines for financial economic environmental and social information — Institution publication. Section2 discounted cash-flow analysis and NPV. Published discounted cash-flow method; local rate, horizon and cash assumptions are separate.
SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

18. Check delayed irrigation construction milestonesDEC-DP05-018 · Construction delivery · Suggested priority: Medium

Try this decision

Investigate delayed irrigation construction milestones.

Validation required

Method. Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar.

Next step. Review evidence. Investigate a material deviation, assign correction, or propose a target revision.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Planned milestone/sowing date; Observed completion/sowing date

Other required evidence. Approved milestone dates; actual dates; dependencies; contract progress; completion evidence.

Fictional worked example · 2025

Laggala Pallegama — construction delivery · Laggala Pallegama

Input or result	Value	Unit
Planned milestone/sowing date	2025-06-01
Observed completion/sowing date	2025-06-09
Calendar date difference	8	days

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Subsequent variance with original and revised targets retained.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

19. Prevent shortages of critical irrigation equipment sparesDEC-DP05-019 · Spare parts · Suggested priority: Medium

Try this decision

Prevent shortages of critical irrigation equipment spares.

Validation required

Method. Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available).

Next step. Review replenishment gap. Reorder approved quantities, redistribute stock, or quarantine affected lots.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Physical stock [spares]; Quarantined stock [spares]; Expired stock [spares]; Committed usable stock [spares]; Additional demand [spares]; Supplier lead time [days]; Remaining shelf life of usable stock [days]

Other required evidence. Part ID; usable stock; asset compatibility; lead time; approved demand; expiry.

Fictional worked example · 2025

Laggala Pallegama — spare parts · Laggala Pallegama

Input or result	Value	Unit
Physical stock	1,200	spares
Quarantined stock	100	spares
Expired stock	50	spares
Committed usable stock	740	spares
Additional demand	500	spares
Supplier lead time	14	days
Remaining shelf life of usable stock	30	days
Uncommitted usable stock	310	spares
Additional demand gap	190	spares

Stock must be compatible by item, lot, condition, expiry and delivery window. Do not allocate quarantined/expired stock or silently erase overcommitment.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Stockouts, expiry, losses and verified lot traceability.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

20. Correct missing metadata in published reservoir informationDEC-DP05-020 · Public information · Suggested priority: Lower

Try this decision

Correct missing metadata in published reservoir information.

Validation required

Method. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.

Next step. Complete the evidence. Accept a fit source for a defined use, restrict it, or request metadata/schema correction.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Reservoir ID; Reservoir ID evidence reference; reading time; reading time evidence reference; unit; unit evidence reference; datum; datum evidence reference; source; source evidence reference; review state; review state evidence reference; update schedule; update schedule evidence reference

Other required evidence. Reservoir ID; reading time; unit; datum; source; review state; update schedule.

Fictional worked example · 2025

Laggala Pallegama — public information · Laggala Pallegama

Input or result	Value	Unit
Reservoir ID	Missing
Reservoir ID evidence reference
reading time	Documented
reading time evidence reference	Sample Laggala Pallegama field register / 2025
unit	Documented
unit evidence reference	Sample Laggala Pallegama field register / 2025
datum	Documented
datum evidence reference	Sample Laggala Pallegama field register / 2025
source	Documented
source evidence reference	Sample Laggala Pallegama field register / 2025
review state	Documented
review state evidence reference	Sample Laggala Pallegama field register / 2025
update schedule	Documented
update schedule evidence reference	Sample Laggala Pallegama field register / 2025
Evidence gaps	1	items

Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.

Proposed checking role. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions.

After the action. Resolved interoperability issues and current verified metadata.

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Institution and data context

Irrigation Department public information — Government publication. Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information. Institutional context; does not establish the calculation or local approval.
Irrigation Department overview and functions — Government publication. Overview: Objectives and Functions. Institutional context; does not establish the calculation or local approval.
FAO crop evapotranspiration 56 — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

4. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

Reservoir · Water and irrigation

Existing form reference: 4c16fb03e60a6df6

Field	Unit	Required
Source record ID	Confirm if needed	No
Tank Code	Confirm if needed	No
Reservoir name	Confirm if needed	No
Range Code	Confirm if needed	No
Range	Confirm if needed	No
Division Code	Confirm if needed	No
Division	Confirm if needed	No
Type	Confirm if needed	No
River basin	Confirm if needed	No
Scheme	Confirm if needed	No
HFL m MSL	m MSL	No
FSL m MSL	m MSL	No
BTL m MSL	m MSL	No
Catchment Area (ha)	ha	No
Capacity at FSL (MCM)	million m³	No
Dead Storage (MCM)	million m³	No
Live Storage (MCM)	million m³	No
Area at FSL (ha)	ha	No
Capacity at FSL(Acft)	acre-ft	No
Dead Storage (Acft)	acre-ft	No
Live Storage (Acft)	acre-ft	No
Remarks	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Irrigable Area · Water and irrigation

Existing form reference: c16bd1e4f59a2a05

Field	Unit	Required
Source record ID	Confirm if needed	No
Scheme	Confirm if needed	No
Type	Confirm if needed	No
Division	Confirm if needed	No
Range	Confirm if needed	No
Res An Uni	Confirm if needed	No
Code	Confirm if needed	No
Response Officer	Confirm if needed	No
Irrigable Area - Scheme Register (ha)	ha	No
Remarks	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Canal System · Water and irrigation

Existing form reference: 21d2e28388872fa1

Field	Unit	Required
Source record ID	Confirm if needed	No
Scheme	Confirm if needed	No
Subsystem	Confirm if needed	No
Division	Confirm if needed	No
Range	Confirm if needed	No
Canal Type	Confirm if needed	No
Code	Confirm if needed	No
Res An Uni	Confirm if needed	No
Scheme Type	Confirm if needed	No
Source geometry length	Confirm if needed	No

Bund · Water and irrigation

Existing form reference: a834d8c98d70c0a1

Field	Unit	Required
OBJECTID 1	Confirm if needed	No
Reservoir name	Confirm if needed	No
Division	Confirm if needed	No
Type	Confirm if needed	No
Range	Confirm if needed	No
Tank Code	Confirm if needed	No
Division Code	Confirm if needed	No
Bund Top Width (m)	Confirm if needed	No
Maximum Height of Bund (m)	Confirm if needed	No
Length of Bund (m)	Confirm if needed	No
Up Stream Slope	Confirm if needed	No
Down Stream Slope	Confirm if needed	No
Range Code	Confirm if needed	No
Source geometry length	Confirm if needed	No

Tank Coordinate · Water and irrigation

Existing form reference: 1c6cf855f1769bc7

Field	Unit	Required
Source record ID	Confirm if needed	No
X Coordinate (Em)	Confirm if needed	No
Y Coordinate (Nm)	Confirm if needed	No
Reservoir name	Confirm if needed	No
Division	Confirm if needed	No
Type	Confirm if needed	No
Range	Confirm if needed	No
Tank Code	Confirm if needed	No
Division Code	Confirm if needed	No
Range Code	Confirm if needed	No
SLD99 Xm	Confirm if needed	No
SLD99 Ym	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No

Sluice · Water and irrigation

Existing form reference: a4b6d5793605c038

Field	Unit	Required
Location	Confirm if needed	No
Reservoir name	Confirm if needed	No
Reservoir Type	Confirm if needed	No
Range	Confirm if needed	No
Tank Code	Confirm if needed	No
Division Code	Confirm if needed	No
Range Code	Confirm if needed	No
Division	Confirm if needed	No
SLD99 Xm	Confirm if needed	No
SLD99 Ym	Confirm if needed	No
Latitiude	Confirm if needed	No
Longitude	Confirm if needed	No
Chinage Location	Confirm if needed	No
Sluice Sill Level	Confirm if needed	No
Number of Baral	Confirm if needed	No
Size of Baral	Confirm if needed	No
Remarks	Confirm if needed	No

Spill · Water and irrigation

Existing form reference: 52df99673ebef8ff

Field	Unit	Required
OBJECTID 12	Confirm if needed	No
Location	Confirm if needed	No
Division	Confirm if needed	No
Tank Code	Confirm if needed	No
Reservoir name	Confirm if needed	No
Range	Confirm if needed	No
Type	Confirm if needed	No
Range Code	Confirm if needed	No
Division Code	Confirm if needed	No
SLD99 Xm	Confirm if needed	No
SLD99 Ym	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Spill Location in Chainage(km+m)	Confirm if needed	No
Spill Type	Confirm if needed	No
Spill Length m	Confirm if needed	No
No of Gates	Confirm if needed	No
Type of Gate	Confirm if needed	No
Size of Gate m (W x H)	Confirm if needed	No
Spill Crest Level mMSL	Confirm if needed	No
Remarks	Confirm if needed	No
Comments	Confirm if needed	No

river basins · Water and irrigation

Existing form reference: d2774621c4b33eb3

Field	Unit	Required
OID	Confirm if needed	No
Name	Confirm if needed	No
FolderPath	Confirm if needed	No
SymbolID	Confirm if needed	No
AltMode	Confirm if needed	No
Base	Confirm if needed	No
Clamped	Confirm if needed	No
Extruded	Confirm if needed	No
Snippet	Confirm if needed	No
PopupInfo	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Attanagalu Oya Flood 2018; Deduru Oya Flood 2018; Gal Oya Flood 2016 · Flood Inundation DSD · Water and irrigation

Existing form reference: 0971c8cf24efd19e

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Yan Oya Flood 2016 · Flood Inundation GND · Water and irrigation

Existing form reference: b2ee7829c7cfc34b

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Yan Oya Flood 2016 · Flood Inundation DSD · Water and irrigation

Existing form reference: 71692320f67c8770

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Yan Oya Flood 2016 · Flood Inundation Area · Water and irrigation

Existing form reference: 9d90cd9c5c84a7ba

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 81 · Water and irrigation

Existing form reference: 8ba4ffbddb26f7b5

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Nilwala Ganga Flood 2017 · Flood Inundation GND · Water and irrigation

Existing form reference: cd20f9bf8d1487c0

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Nilwala Ganga Flood 2017 · Flood Inundation DSD · Water and irrigation

Existing form reference: d6e8e9a429825b57

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Nilwala Ganga Flood 2017 · Flood Inundation Area · Water and irrigation

Existing form reference: ce6e0b46bd0534b9

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 76 · Water and irrigation

Existing form reference: 4d62429a56f1e52b

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mundani Aru Flood 2014 · Flood Inundation GND · Water and irrigation

Existing form reference: 54b17c1b976d7b7c

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mundani Aru Flood 2014 · Flood Inundation DSD · Water and irrigation

Existing form reference: de66a3c339d43cc1

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mundani Aru Flood 2014 · Flood Inundation Area · Water and irrigation

Existing form reference: ebc817056ae98de6

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 71 · Water and irrigation

Existing form reference: 7df34748f8dc7a71

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mee Oya Flood 2019 · Flood Inundation GND · Water and irrigation

Existing form reference: 336909700eb1e807

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mee Oya Flood 2019 · Flood Inundation DSD · Water and irrigation

Existing form reference: 977273349cc89bef

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mee Oya Flood 2019 · Flood Inundation Area · Water and irrigation

Existing form reference: 3c769ddf1cd69ffa

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 66 · Water and irrigation

Existing form reference: d6db0e029cc9024f

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Malwathu Oya Flood 2011 · Flood Inundation GND · Water and irrigation

Existing form reference: 17b96434d3bdc3d8

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Malwathu Oya Flood 2011 · Flood Inundation DSD · Water and irrigation

Existing form reference: fa2f19c86d129c30

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Malwathu Oya Flood 2011 · Flood Inundation Area · Water and irrigation

Existing form reference: 785418aca242c75f

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 61 · Water and irrigation

Existing form reference: 75f475250456de4c

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mahaweli Ganga Flood 2012 · Flood Inundation GND · Water and irrigation

Existing form reference: 3d03fbdf1f36a8b0

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mahaweli Ganga Flood 2012 · Flood Inundation DSD · Water and irrigation

Existing form reference: 562d7edfae1efc39

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mahaweli Ganga Flood 2012 · Flood Inundation Area · Water and irrigation

Existing form reference: 5a3f22d6db739d31

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 56 · Water and irrigation

Existing form reference: bbc4c12de68b1c87

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Maha Oya (102) Flood 2016 · Flood Inundation GND · Water and irrigation

Existing form reference: ccd8becff516f214

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Maha Oya (102) Flood 2016 · Flood Inundation DSD · Water and irrigation

Existing form reference: 388a6af26afd09cc

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Maha Oya (102) Flood 2016 · Flood Inundation Area · Water and irrigation

Existing form reference: 9edb436b9dd89dbd

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 51 · Water and irrigation

Existing form reference: e86ead836ff90dea

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kirama Oya Flood 2017 · Flood Inundation GND · Water and irrigation

Existing form reference: f589bf96735f0d23

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kirama Oya Flood 2017 · Flood Inundation DSD · Water and irrigation

Existing form reference: ab1ef79575b445fa

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kirama Oya Flood 2017 · Flood Inundation Area · Water and irrigation

Existing form reference: 5d056dd558b67b64

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 46 · Water and irrigation

Existing form reference: aa5a1be4d7f874a7

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kalu Ganga Flood 2017 · Flood Inundation GND · Water and irrigation

Existing form reference: 23a2949aee5a9a33

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kalu Ganga Flood 2017 · Flood Inundation DSD · Water and irrigation

Existing form reference: 6adfb4fb98a8707e

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kalu Ganga Flood 2017 · Flood Inundation Area · Water and irrigation

Existing form reference: 0082696b49d69c10

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 41 · Water and irrigation

Existing form reference: 03a72f044ebae238

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganag Flood 2016 Major · Flood Inundation DSD · Water and irrigation

Existing form reference: fb02e7976de33449

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganag Flood 2016 Major · Flood Inundation GND · Water and irrigation

Existing form reference: 03ee84fbf008e604

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganag Flood 2016 Major · Flood Inundation Area · Water and irrigation

Existing form reference: 271b1d2b0a139a64

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 36 · Water and irrigation

Existing form reference: 7a5174dfa55bfd27

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganga Flood 2012 Minor · Flood Inundation GND · Water and irrigation

Existing form reference: cc5d99dd2a1894a4

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganag Flood 2016 Minor · Flood Inundation DSD · Water and irrigation

Existing form reference: 620e0dab3654a548

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganga Flood 2012 Minor · Flood Inundation Area · Water and irrigation

Existing form reference: 7f5d382712c12acf

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 31 · Water and irrigation

Existing form reference: 05802ebbb2056902

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganga Flood 1989 Critical · Flood Inundation GND · Water and irrigation

Existing form reference: 317acf986c000ec2

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganga Flood 1989 Critical · Flood Inundation DSD · Water and irrigation

Existing form reference: a8bf89973a928788

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganga Flood 1989 Critical · Flood Inundation Area · Water and irrigation

Existing form reference: 741b82a1161a09af

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 26 · Water and irrigation

Existing form reference: 3a83818903f3f37d

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kala Oya Flood 2016 · Flood Inundation GND · Water and irrigation

Existing form reference: 49c3db841a10343f

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kala Oya Flood 2016 · Flood Inundation DSD · Water and irrigation

Existing form reference: 991636cb328c0e85

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kala Oya Flood 2016 · Flood Inundation Area · Water and irrigation

Existing form reference: b22dc6c49a5a6c32

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 21 · Water and irrigation

Existing form reference: 5aefbeaa988c678e

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gin Ganga Flood 2017 · Flood Inundation GND · Water and irrigation

Existing form reference: aacfac87f71565b1

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gin Ganga Flood 2017 · Flood Inundation DSD · Water and irrigation

Existing form reference: 29a6fdf392f24335

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gin Ganga Flood 2017 · Flood Inundation Area · Water and irrigation

Existing form reference: a0692e188c7ae78c

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 16 · Water and irrigation

Existing form reference: 9f0e3d9806f9372e

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gal Oya Flood 2016 · Flood Inundation GND · Water and irrigation

Existing form reference: 0896be503f933851

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gal Oya Flood 2016 · Flood Inundation DSD · Water and irrigation

Existing form reference: edc275f80f311458

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gal Oya Flood 2016 · Flood Inundation Area · Water and irrigation

Existing form reference: 621723d9774991dd

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 11 · Water and irrigation

Existing form reference: 66a5f593af6cf0f5

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Deduru Oya Flood 2018 · Flood Inundation DSD · Water and irrigation

Existing form reference: 7babdebde5c3a59f

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Deduru Oya Flood 2018 · Flood Inundation GND · Water and irrigation

Existing form reference: 8ef6df7ed78bd257

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Deduru Oya Flood 2018 · Flood Inundation Area · Water and irrigation

Existing form reference: 6e945531b3cfca82

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 6 · Water and irrigation

Existing form reference: ad60f9303374d50c

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Attanagalu Oya Flood 2018 · Flood Inundation GND · Water and irrigation

Existing form reference: f1156d2a9872139a

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Attanagalu Oya Flood 2018 · Flood Inundation DSD · Water and irrigation

Existing form reference: 64d7a48f5360398d

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Attanagalu Oya Flood 2018 · Flood Inundation Area · Water and irrigation

Existing form reference: 23c4010edccc9e62

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 1 · Water and irrigation

Existing form reference: 9cee3fab75edb4bf

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

rivers · Water and irrigation

Existing form reference: bddcc1162ffe3b29

Field	Unit	Required
OID	Confirm if needed	No
Name	Confirm if needed	No
FolderPath	Confirm if needed	No
SymbolID	Confirm if needed	No
AltMode	Confirm if needed	No
Base	Confirm if needed	No
Clamped	Confirm if needed	No
Extruded	Confirm if needed	No
Snippet	Confirm if needed	No
PopupInfo	Confirm if needed	No
Source geometry length	Confirm if needed	No

Buffer of hydrostations · Water and irrigation

Existing form reference: a0f586c57ced7d89

Field	Unit	Required
Source record ID	Confirm if needed	No
no	Confirm if needed	No
station	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No
basin	Confirm if needed	No
Buffer distance in Meters	Confirm if needed	No
ORIG FID	Confirm if needed	No
Area in Square Kilometers	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

gauges · Water and irrigation

Existing form reference: 10375802bd0f4154

Field	Unit	Required
Source record ID	Confirm if needed	No
River Basin	Confirm if needed	No
Gauge	Confirm if needed	No
Water Level	station unit; select a station	No
Rain Fall	mm	No
Source record created	Confirm if needed	No
Source record edited	Confirm if needed	No
alertpull	station unit; select a station	No
minorpull	station unit; select a station	No
majorpull	station unit; select a station	No

stations · Water and irrigation

Existing form reference: c0d33ca136364cb4

Field	Unit	Required
Source record ID	Confirm if needed	No
no	Confirm if needed	No
station	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No
basin	Confirm if needed	No
Tributory	Confirm if needed	No
Alert Level	Confirm if needed	No
Minor Flood Level	Confirm if needed	No
Major Flood Level	Confirm if needed	No
Unit	Confirm if needed	No
Elivation m MSL	m MSL	No

groupbySummary · Water and irrigation

Existing form reference: 6a3ee4ad7513e95e

Field	Unit	Required
Source record ID	Confirm if needed	No
Join ID	Confirm if needed	No
gauge	Confirm if needed	No
Sum Rain Fall	mm	No
Count of Points	Confirm if needed	No

Irrigable Area · Water and irrigation

Existing form reference: ec64c51bcb7a13ab

Field	Unit	Required

Reservoir · Water and irrigation

Existing form reference: a4a0cc679fd52fa5

Field	Unit	Required

Bund · Water and irrigation

Existing form reference: 1f490c8006777e68

Field	Unit	Required

Sluice · Water and irrigation

Existing form reference: 1799548d75c1577b

Field	Unit	Required

Spill · Water and irrigation

Existing form reference: 092220ad7d168ad3

Field	Unit	Required

Canal System · Water and irrigation

Existing form reference: 018e6b3de43e55a7

Field	Unit	Required

Flood 30Nov2025 · source layer 0 · Water and irrigation

Existing form reference: d7be90171f7bd605

Field	Unit	Required
OBJECTID 1	Confirm if needed	No
RiverBasin	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Major reservoirs · current readings · Water and irrigation

Existing form reference: 2942a78ac9121012

Field	Unit	Required
Publisher reservoir ID	Confirm if needed	No
Week No	Confirm if needed	No
Update Date	Confirm if needed	No
Reservoir	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Range	Confirm if needed	No
Division	Confirm if needed	No
Irrigable area	acres	No
Full supply depth	ft	No
Gross Capacity Acft	acre-ft	No
Dead Storage Acft	acre-ft	No
Active Storage Acft	acre-ft	No
Date	Confirm if needed	No
Water Depth ft	ft	No
Gross Storage Acft	acre-ft	No
Effective Storage Acft	acre-ft	No
Effective storage percentage	%	No
Preceding-day rainfall	mm	No
Spilling	Confirm if needed	No
Remarks	Confirm if needed	No
Downstream impact	Confirm if needed	No
Spill discharge	cusec (publisher)	No
Remaining storage (publisher)	acre-ft	No

Major reservoirs · Maha seasonal history · Water and irrigation

Existing form reference: 620e4a73d4ea0be0

Field	Unit	Required
Publisher reservoir ID	Confirm if needed	No
UPDATED DATE	Confirm if needed	No
RESERVOIR	Confirm if needed	No
LATITUDE	Confirm if needed	No
LONGITUDE	Confirm if needed	No
RANGE	Confirm if needed	No
Division	Confirm if needed	No
Active Storage (Acft)	acre-ft	No
Long-term average	acre-ft	No
ES 20 21 Acft	acre-ft	No
ES 21 22 Acft	acre-ft	No
ES 22 23 Acft	acre-ft	No
ES 23 24 Acft	acre-ft	No
ES 24 25 Acft	acre-ft	No
ES 25 26 Acft	acre-ft	No
ES 26 27 Acft	acre-ft	No

Major reservoirs · Yala seasonal history · Water and irrigation

Existing form reference: 560087607361a247

Field	Unit	Required
ID	Confirm if needed	No
Publisher reservoir ID	Confirm if needed	No
UPDATED DATE	Confirm if needed	No
RESERVOIR	Confirm if needed	No
LATITUDE	Confirm if needed	No
LONGITUDE	Confirm if needed	No
RANGE	Confirm if needed	No
Division	Confirm if needed	No
Active Storage (Acft)	acre-ft	No
Long-term average	acre-ft	No
EFFECTIVE STORAGE (Acft) 2022	acre-ft	No
EFFECTIVE STORAGE (Acft) 2023	acre-ft	No
EFFECTIVE STORAGE (Acft) 2024	acre-ft	No
EFFECTIVE STORAGE (Acft) 2025	acre-ft	No
EFFECTIVE STORAGE (Acft) 2026	acre-ft	No

Medium reservoirs · Yala seasonal history · Water and irrigation

Existing form reference: c349e5c98d02782a

Field	Unit	Required
Publisher reservoir ID	Confirm if needed	No
Update Date	Confirm if needed	No
Reservoir	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Range	Confirm if needed	No
Division	Confirm if needed	No
Active Storage (Acft)	acre-ft	No
Long-term average	acre-ft	No
EFFECTIVE STORAGE (Acft) 2023	acre-ft	No
EFFECTIVE STORAGE (Acft) 2024	acre-ft	No
EFFECTIVE STORAGE (Acft) 2025	acre-ft	No
EFFECTIVE STORAGE (Acft) 2026	acre-ft	No

Medium reservoirs · Maha seasonal history · Water and irrigation

Existing form reference: ade3b5a99ab49e1d

Field	Unit	Required
Publisher reservoir ID	Confirm if needed	No
Update Date	Confirm if needed	No
Reservoir	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Range	Confirm if needed	No
Division	Confirm if needed	No
Active Storage (Acft)	acre-ft	No
Long-term average	acre-ft	No
ES 24 25 Acft	acre-ft	No
ES 25 26 Acft	acre-ft	No
ES 26 27 Acft	acre-ft	No

Medium reservoirs · current readings · Water and irrigation

Existing form reference: 78fedd1e1892ca18

Field	Unit	Required
Publisher reservoir ID	Confirm if needed	No
Week No	Confirm if needed	No
Update Date	Confirm if needed	No
Reservoir	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Range	Confirm if needed	No
Division	Confirm if needed	No
Irrigable area	acres	No
Full supply depth	ft	No
Gross Capacity Acft	acre-ft	No
Dead Storage Acft	acre-ft	No
Active Storage Acft	acre-ft	No
Date	Confirm if needed	No
Water Depth ft	ft	No
Gross Storage Acft	acre-ft	No
Effective Storage Acft	acre-ft	No
Effective storage percentage	%	No
Preceding-day rainfall	mm	No
Spilling	Confirm if needed	No
Remarks	Confirm if needed	No
Remaining storage (publisher)	acre-ft	No

Published project technical details · Water and irrigation

Existing form reference: official-projects

Field	Unit	Required
Project	Confirm if needed	No
Component	Confirm if needed	No
Parameter	Confirm if needed	No
Source page	Confirm if needed	No

Irrigation publications · Water and irrigation

Existing form reference: official-publications

Field	Unit	Required
Publication	Confirm if needed	No
Type	Confirm if needed	No
Publication period	Confirm if needed	No
Data availability	Confirm if needed	No
Publisher document	Confirm if needed	No

5. Documents and images

Your institution has its own document and image library. Use the same library for reports, photos and other evidence.

Open this screen for Irrigation Department See the presentation example

Irrigation Department Documents and images prototype screen — Irrigation Department. Prototype screen. Select the image to enlarge it.

What you can try

Open Documents and images. Check the institution name.
Use All files, Documents or Images to find a file. Open its preview or download the original.
Use a sample file to try Add file. Private is the starting choice. Public needs a source, permission to share and review.
Use Access preview to try the institution reviewer and Public visitor views.

Files added in the prototype stay in this browser. Public sharing is an access preview. Existing public reference links already work online.

What your institution needs to confirm

Does a separate library for your institution meet your needs?Should new files start as Private for the permitted institution team?Should Public access require a review of the file and sharing permission?What documents and images will you store? Give the file types, usual sizes and need for earlier versions.Which job roles may add files, read Private files and approve Public files?Which files must stay Private? What permission, licence or expiry rule is needed for Public files?What else should change in this library?

6. Data structure management

Data structure keeps the existing source tree, records, charts and map. Manage structure adds a place to propose changes to definitions.

Open this screen for Irrigation Department See the presentation example

Irrigation Department Data structure management prototype screen — Irrigation Department. Prototype screen. Select the image to enlarge it.

What you can try

Open Data structure and choose Manage structure.
Use Add base domain for a main information area. Add inside creates a subject area, a nested subject, an entity type or a field under the right parent.
Give the definition a clear name, code and meaning. Reuse an existing definition when the meaning is the same.
For a field, check the data type, unit, required value, limits and missing-value rule. Save a Draft, then try the separate reviewer view.

An entity type means a kind of thing or event, such as a reservoir or an inspection. Drafts stay in this browser. A demo approval does not change real definitions, data, chart links or sharing rights.

What your institution needs to confirm

Do the existing main topics and subject areas match your institution’s work?Should definition changes stay Draft until the responsible reviewer checks them?Is it right to reuse the same entity type or field when its meaning is the same?Which main topics, subject areas, entity types or fields should we add or change?Which units, choices, limits, decimal places and missing-value rules must each new field use?Which job roles may edit definitions and review them? Who owns each main information area?When a meaning, unit or calculation changes, what review and version history does your institution need?

7. Users and access

User management shows example profiles for each institution. People and Roles and access let you review the proposed account screens.

Open this screen for Irrigation Department See the presentation example

Irrigation Department Users and access prototype screen — Irrigation Department. Prototype screen. Select the image to enlarge it.

What you can try

Open User management and choose the institution. The rows are examples, not a list of your staff.
Use View access to check a role. An administrator title alone does not give access to Private files.
Try Preview invitation or Preview access change. Check the role, start date, optional end date and reason.
Review the example permissions and tell us which job roles should receive each one.

These are interface previews only. They create no account, send no email and change no access. Use example details in the preview. Institution verification does not grant a real permission.

What your institution needs to confirm

Do the proposed role names and responsibilities match your institution?Should access be limited to the assigned institution and the agreed dates?Should reading Private files need a separate permission, even for an administrator?Which job roles should view data, add files, review Public requests, edit definitions and manage users?Who should approve new access, set an end date or remove access when someone changes duties?Which user fields, roles or access checks are missing? Give role names rather than passwords or private account details.

9. Anything else we should change?

Which decisions or services are missing?Which forms or fields should change? Give the existing form reference where possible.What should change in the entry, checking, expert, map or report steps?Are the English, Sinhala and Tamil words clear? Give the screen name, current word and your suggested wording.Who should join the next review and what should happen next?

Use the Download answers button at the top of this page. Share the downloaded file or printed copy through your agreed review channel. Nothing is sent automatically.

Irrigation Department

1. Check a decision

2. Try the inputs

3. Check each decision

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

4. Existing data forms for your institution

5. Documents and images

What you can try

What your institution needs to confirm

6. Data structure management

What you can try

What your institution needs to confirm

7. Users and access

What you can try

What your institution needs to confirm

8. Can you share data regularly?

9. Anything else we should change?