Mahaweli Authority of Sri Lanka

Sri Lanka decision proposal

Tell us what to change or add.

Archived decisions

1. Check a decision

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

2. Try the inputs

Use Change example to try different values. Use Data needed to check the fields and sources. 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. Review cropping plans against calculated water requirementsDEC-DP06-001 · Seasonal cropping
Try this decision

Compare crop-water requirements with the records supporting a seasonal system plan.

Verified published component · Crop evapotranspiration ETc component

Fictional default example · 2025.

Fictional case / areaGross daily irrigation requirement [m³/day]Net field requirement [mm/day]Next check
Laggala Pallegama — seasonal cropping / 20256,687.55.35Review weather, crop, water-availability and operating evidence
Rattota — seasonal cropping / 20256,687.55.35Review weather, crop, water-availability and operating evidence
Panvila — seasonal cropping / 20256,687.55.35Review weather, crop, water-availability and operating evidence

What the selected record shows. Gross daily irrigation requirement: 6,687.5 m³/day.

Next step. Review weather, crop, water-availability and operating evidence. Prepare water-needs scenario in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Calculated crop need is not an approved cropping or release plan.

Inputs, method and sources
Supplied inputValueUnit
Irrigated crop area85ha
Reference evapotranspiration4.5mm/day
Crop coefficient1.1ratio
Rainfall reaching the field after runoff1.6mm/day
Deep percolation and paddy allowance2mm/day
Capillary contribution0mm/day
Desired change in stored soil water0mm/day
Field application efficiency0.68fraction

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

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.

Other required records: System; crop hectares; crop coefficients; rainfall; soil storage; efficiency.

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.

Calculation appendix

  • 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.
Your checks for this decision
2. Correct system-level water-delivery shortfallsDEC-DP06-002 · Water delivery
Try this decision

Compare system delivery targets and measured water supplied in the same period.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [m³]Relative change [%]Next check
Laggala Pallegama — water delivery / 2025-16,000-18.824Check the matching records and reasons for the difference
Rattota — water delivery / 2025-2,000-2.353Check the matching records and reasons for the difference
Panvila — water delivery / 2025-5,000-5.882Check the matching records and reasons for the difference

What the selected record shows. Difference: -16,000 m³.

Next step. Check the matching records and reasons for the difference. Prepare difference review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A volume shortfall does not establish its cause or authorise a new allocation.

Example chart
Difference — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Planned system delivery in the stated period85,000m³
Measured system delivery in the same period69,000m³

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

Other required records: System ID; approved allocation; actual delivery; season; command hectares.

Calculation appendix

  • 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.
Your checks for this decision
3. Review linked-reservoir storage and transfer scenariosDEC-DP06-003 · Reservoir networks
Try this decision

Reconcile storage and transfer records within a defined control volume.

Validation required

Fictional default example · 2025.

Fictional case / areaCalculated closing storage [m³]Observed minus calculated closing [m³]Next check
Laggala Pallegama — reservoir networks / 2025164,000-500Reconcile closing balance
Rattota — reservoir networks / 2025164,000-500Reconcile closing balance
Panvila — reservoir networks / 2025164,000-500Reconcile closing balance

What the selected record shows. Calculated closing storage are 164,000 m³. The recorded closing observation is 163,500 m³; recorded minus calculated is -500 m³. Check the component records before explaining that difference.

Next step. Reconcile closing balance. Prepare balance review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Internal transfers must not be counted as both new system inflow and outflow.

Inputs, method and sources
Supplied inputValueUnit
Opening storage160,000m³
All measured inflows and transfers in48,000m³
Releases and transfers out35,000m³
Evaporation and other outflows9,000m³
Independently observed closing storage163,500m³

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

Use the same physical boundary, period and units. A residual is a reconciliation issue, not automatically a measured loss. For a combined reservoir boundary, eliminate transfers wholly inside that boundary. The example is a single stated control volume, not the total Mahaweli system.

Other required records: Reservoir storage; inter-basin transfers; inflow; releases; evaporation; spill.

Calculation appendix

  • 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.
Your checks for this decision
4. Check land requests before Mahaweli reviewDEC-DP06-007 · Land allocation
Try this decision

Check land-request and rights evidence before a Mahaweli land referral.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — land allocation / Laggala PallegamaParcel ID: MissingObtain the missing evidence listed below
Rattota — land allocation / Rattotaapplicant evidence: MissingObtain the missing evidence listed below
Panvila — land allocation / Panvilapermitted purpose: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this land allocation case. The items below identify what must be obtained or reconciled.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Parcel ID: Missing

Complete paperwork does not grant agricultural or commercial use permission.

Inputs, method and sources
Supplied inputValueUnit
Parcel IDMissing
Parcel ID evidence referenceNot provided
applicant evidenceDocumented
applicant evidence evidence referenceSample Laggala Pallegama field register / 2025
permitted purposeDocumented
permitted purpose evidence referenceSample Laggala Pallegama field register / 2025
plan editionDocumented
plan edition evidence referenceSample Laggala Pallegama field register / 2025
current rulesDocumented
current rules evidence referenceSample Laggala Pallegama field register / 2025

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

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

Other required records: Parcel ID; applicant evidence; permitted purpose; plan edition; current rules.

Calculation appendix

  • 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.
Your checks for this decision
5. Check activities reported inside tank or canal reservationsDEC-DP06-009 · Reservation protection
Try this decision

Review the reported reservation overlap, inspection, permission and maintenance access before preparing a case referral.

Validation required

Fictional example records. Geographic context is separate from an exact site and the applicable Mahaweli system. Supplied hectares are not measured from the reference image.

Fictional case / contextObserved activityReported overlapNext check
Inspection 1 / 2025 — fictional / Laggala PallegamaTemporary material storage — fictional observation0.15 ha of 0.6 ha; 25%Obtain the exact site and applicable system-office evidence
Inspection 2 / 2025 — fictional / RattotaSeasonal cultivation — fictional observation0.08 ha of 0.4 ha; 20%Review the activity against the documented permission
Inspection 3 / 2025 — fictional / PanvilaAccess-path works — fictional observation0 ha of 0.2 ha; 0%Obtain the missing case evidence

What the first case shows. 0.15 ha of the 0.6 ha observed activity is reported inside the reservation (25.0%). A matching permission is missing or disputed. This does not establish unlawful occupation. Still needed: Exact site or asset reference; Applicable system jurisdiction and source for the responsible system office; Matching permission record and conditions; Inspection evidence about maintenance access. The figures describe the supplied example records; they do not settle these gaps.

Next step. Obtain the exact site and applicable system-office evidence. Use the prototype to prepare a visible evidence request or case-review draft; it remains unassigned and is not sent.

Inputs, method and sources

Reported overlap share = 100 × reported activity overlap / total observed activity area. Count common overlapping parts once in the supplied survey record. No map intersection is performed.

A reported overlap is not a finding of unlawful occupation. Confirm the applicable survey, reservation basis, permissions and inspection evidence. No fixed reservation width, eviction, penalty or safety determination is inferred.

Required evidence: Exact site or asset reference; Applicable system jurisdiction and responsible system-office source; Reservoir or canal case identity; Applicable reservation survey and basis; Observed activity and inspection date; Activity area and reported overlap; Permission reference and maintenance access evidence.

Calculation appendix

  • 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.
Your checks for this decision
6. Compare agricultural water productivityDEC-DP06-011 · System productivity
Try this decision

Compare matching agricultural output and water volume by system.

Validation required

Fictional default example · 2025.

Fictional case / areaCrop water productivity [kg/m³]Next check
Laggala Pallegama — system productivity / 20252.747Check matching outputs, denominators and operating conditions
Rattota — system productivity / 20253.344Check matching outputs, denominators and operating conditions
Panvila — system productivity / 20253.076Check matching outputs, denominators and operating conditions

What the selected record shows. Saleable crop output: 19,780 kg; Matching irrigation water input: 7,200 m³. This gives 2.747 kg/m³.

Next step. Check matching outputs, denominators and operating conditions. Prepare performance comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Productivity ratios do not establish the cause of a difference.

Example chart
Crop water productivity — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Saleable crop output19,780kg
Matching irrigation water input7,200m³

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

Other required records: Harvest kg; delivered cubic metres; cropped hectares; season; crop type.

Calculation appendix

  • 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.
Your checks for this decision
7. Review overdue Mahaweli maintenance casesDEC-DP06-013 · Irrigation assets
Try this decision

Identify overdue maintenance cases and inspect their engineering evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaOpen days past due [days]Calendar age [days]Next check
Laggala Pallegama — irrigation assets / 20252990Follow up overdue case; confirm the missing condition evidence
Rattota — irrigation assets / 20252990Follow up overdue case; confirm the missing condition evidence
Panvila — irrigation assets / 20252990Follow up overdue case; confirm the missing condition evidence

What the selected record shows. Open days past due: 29 days. Follow up overdue case.

Next step. Follow up overdue case; confirm the missing condition evidence. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Documented critical unresolved condition: Unknown

Case age alone is not engineering severity or repair priority.

Inputs, method and sources
Supplied inputValueUnit
Received or defect observed2025-04-01
Recorded due date2025-06-01
Assessment date2025-06-30
Case/work closedNo
Documented critical unresolved conditionUnknown
Responsible office or maintainerProposed responsible office
Actual closure date when closedNot provided

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

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

Other required records: Asset ID; condition; defects; criticality; inspection date; repair estimates.

Calculation appendix

  • 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.
Reference map image
Matale District location in Sri Lanka — published static reference map
Reference map image — not live. Matale District location in Sri Lanka. Map date: 2012-07-30. Uwe Dedering; uploaded by BishkekRocks · CC BY-SA 3.0. Detail crop only; no features added. The example areas are supplied records, not measurements from this image.
Your checks for this decision
8. Plan service capacity for settlement growthDEC-DP06-014 · Settlement services
Try this decision

Compare settlement-service demand with usable service capacity.

Validation required

Fictional default example · 2025.

Fictional case / areaUsable capacity minus demand [m³/day]Usable capacity [m³/day]Next check
Laggala Pallegama — settlement services / 2025-15135Review capacity shortfall
Rattota — settlement services / 2025-15135Review capacity shortfall
Panvila — settlement services / 2025-15135Review capacity shortfall

What the selected record shows. Usable capacity minus demand: -15 m³/day. Review capacity shortfall.

Next step. Review capacity shortfall. Prepare capacity review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A capacity gap does not select or authorise an infrastructure expansion.

Inputs, method and sources
Supplied inputValueUnit
Demand in the selected period150m³/day
Rated capacity for that period180m³/day
Unavailable or restricted capacity45m³/day

Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand.

Match peak/average basis, time window, skill, staffing, accessibility and other binding constraints. One aggregate capacity does not override a safety constraint.

Other required records: Household demand; water and road capacity; service locations; projected occupancy.

Calculation appendix

  • 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.
Your checks for this decision
9. Select riparian and catchment restoration alternativesDEC-DP06-015 · Environmental restoration
Try this decision

Compare restoration choices using catchment, riparian, rights and resource evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Riparian natural regeneration / Laggala PallegamaAllow suitable riparian vegetation to recover.Needs the applicable boundary, seed sources, protection and landholder agreement.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Native buffer planting / Laggala PallegamaEstablish a specified native buffer.Needs species/site evidence, planting resources, access and maintenance.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Slope and stream restoration / Laggala PallegamaCoordinate upper-slope and stream restoration.Needs joint agreements, sequencing, erosion evidence and outcome monitoring.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing

What the selected record shows. There is not enough information to choose this option. Obtain the records and evidence about conditions listed below. The supplied budget less cost is 300,000 LKR.

Next step. Obtain the missing records before choosing. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Records needed: Site condition; land rights; restoration costs; biodiversity; watershed benefit evidence
  • Applicable conditions, what was checked and the supporting reference

Predicted benefits remain assumptions until supported by local evidence.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionAllow suitable riparian vegetation to recover.
Resource needs and adverse effectsNeeds the applicable boundary, seed sources, protection and landholder agreement.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

Compare each alternative's stated benefit, adverse effects, domain evidence and mandatory constraints. Where cost and budget are supplied, budget balance = budget − option cost. A budget balance alone does not determine domain feasibility or select an option.

Predicted benefits remain assumptions until supported by local evidence.

Other required records: Site condition; land rights; restoration costs; biodiversity; watershed benefit evidence.

Calculation appendix

  • 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.
Your checks for this decision
10. Check delayed system-development milestonesDEC-DP06-018 · Investment delivery
Try this decision

Compare planned and recorded system-development milestone dates.

Validation required

Fictional default example · 2025.

Fictional case / areaCalendar date difference [days]Next check
Laggala Pallegama — investment delivery / 20258Check the matching records and reasons for the difference
Rattota — investment delivery / 20258Check the matching records and reasons for the difference
Panvila — investment delivery / 20258Check the matching records and reasons for the difference

What the selected record shows. Calendar date difference: 8 days.

Next step. Check the matching records and reasons for the difference. Prepare difference review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Delay alone does not establish cause, liability or an escalation level.

Inputs, method and sources
Supplied inputValueUnit
Planned milestone/sowing date2025-06-01
Observed completion/sowing date2025-06-09

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

Other required records: Project milestones; actual progress; contracts; budget; dependencies; verification.

Calculation appendix

  • 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.
Your checks for this decision
11. Reconcile inconsistent land and water system codesDEC-DP06-020 · System reporting
Try this decision

Find land and water-system codes whose definitions or source references need reconciliation.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — system reporting / Laggala PallegamaSource system labels: MissingObtain the missing evidence listed below
Rattota — system reporting / Rattotaofficial system registry: MissingObtain the missing evidence listed below
Panvila — system reporting / Panvilageometry edition: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this system reporting case. The items below identify what must be obtained or reconciled.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Source system labels: Missing

A completed mapping checklist does not authorise overwriting the source codes.

Inputs, method and sources
Supplied inputValueUnit
Source system labelsMissing
Source system labels evidence referenceNot provided
official system registryDocumented
official system registry evidence referenceSample Laggala Pallegama field register / 2025
geometry editionDocumented
geometry edition evidence referenceSample Laggala Pallegama field register / 2025
steward decisionsDocumented
steward decisions evidence referenceSample Laggala Pallegama field register / 2025

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

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

Other required records: Source system labels; official system registry; geometry edition; steward decisions.

Calculation appendix

  • 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.
Your checks for this decision
12. Check which Mahaweli blocks need a revised paddy production estimateDEC-DP06-021 · Published method
Try this decision

Source. Sri Lanka publication.

Data needed. System and block, season, expected net harvested hectares and a comparable yield estimate.

Method. Apply the DCS paddy production relationship to each matched block and season. Compare revised estimates with the approved planning figures.

Worked example. A Mahaweli block expects 65 ha to be harvested at 4.2 t/ha. The estimate is 273 t, which is 17 t below its 290 t plan. Ask the block officer what changed.

Next step. Ask the block officer to investigate a material difference in harvested area or expected yield.

Department of Census and Statistics, Paddy Statistics Yala 2023. Introduction and Mahaweli block-level area, yield and production tables.

Confirm comparable seasons, net area, yield source and the review threshold.

Your checks for this decision

4. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

Irrigation Schemes · Land Suitability

Existing form reference: 648a6f28a711dfa9

FieldUnitRequired
System NameConfirm if neededNo
SystemsConfirm if neededNo
IDConfirm if neededNo
ID_SystemsConfirm if neededNo
MASL_SystemConfirm if neededNo
DSD_NameConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Ground Water Prospect · Water Systems

Existing form reference: ce5ed1b99bb3102f

FieldUnitRequired
IDConfirm if neededNo
AquifierConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Ground Water · Water Systems

Existing form reference: 8d60801843516765

FieldUnitRequired
IDConfirm if neededNo
AquifierConfirm if neededNo
Original FIDConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Village Tank · Water Systems

Existing form reference: ba56f4a118b8defb

FieldUnitRequired
NumberConfirm if neededNo
IDConfirm if neededNo
DataConfirm if neededNo
SheetConfirm if neededNo
XConfirm if neededNo
YConfirm if neededNo
XCOORDConfirm if neededNo
YCOORDConfirm if neededNo
Sheet NumberConfirm if neededNo
QuantityConfirm if neededNo
DescriptionConfirm if neededNo
Village Anicut · Water Systems

Existing form reference: f173e69599dc5331

FieldUnitRequired
Serial NumberConfirm if neededNo
XCOORDConfirm if neededNo
YCOORDConfirm if neededNo
CodeConfirm if neededNo
DescriptionConfirm if neededNo
Basin · Water Systems

Existing form reference: aab19eb1fe26e99f

FieldUnitRequired
Basin NameConfirm if neededNo
NumberConfirm if neededNo
BoundaryConfirm if neededNo
River BasinConfirm if neededNo
areaConfirm if neededNo
PerimeterConfirm if neededNo
WatershedConfirm if neededNo
IDConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Water Shed · Water Systems

Existing form reference: f0192290b75919c0

FieldUnitRequired
Watershed_TypeConfirm if neededNo
Watershed_NameConfirm if neededNo
Catchment_NameConfirm if neededNo
Basin_NameConfirm if neededNo
Region_NameConfirm if neededNo
DescriptionConfirm if neededNo
PerimeterConfirm if neededNo
areaConfirm if neededNo
Watershed_NumberConfirm if neededNo
HectaresConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Dam · Water Systems

Existing form reference: ccd11935ddd740eb

FieldUnitRequired
Dam NameConfirm if neededNo
Dam_TypeConfirm if neededNo
Dam Storage CapacityConfirm if neededNo
Hydraulic Head Size meterConfirm if neededNo
Dam SizeConfirm if neededNo
Dam Construction TypeConfirm if neededNo
Dam Construction MaterialConfirm if neededNo
Dam Structural BehaviourConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
Hydro Point IDConfirm if neededNo
DescriptionConfirm if neededNo
st_length(shape)Confirm if neededNo
River Mouth Locations · Water Systems

Existing form reference: 8123426118305c93

FieldUnitRequired
NameConfirm if neededNo
Capture_TypeConfirm if neededNo
WB_NumberConfirm if neededNo
Point_XConfirm if neededNo
Point_YConfirm if neededNo
Zone_NameConfirm if neededNo
Stream · Water Systems

Existing form reference: 46072ad6caa5f83d

FieldUnitRequired
Stream TypeConfirm if neededNo
Stream NameConfirm if neededNo
Length In KmConfirm if neededNo
Width In MetersConfirm if neededNo
Hydro Line IDConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_length(shape)Confirm if neededNo
Pond · Water Systems

Existing form reference: 66361481a1066277

FieldUnitRequired
Pond_TypeConfirm if neededNo
Pond_NameConfirm if neededNo
Capacity_Acre_Per_FeetConfirm if neededNo
Perimeter_kmConfirm if neededNo
Area_In_sqkmConfirm if neededNo
Depth_In_MetersConfirm if neededNo
Spill_Level_MLSConfirm if neededNo
Catchment_AreaConfirm if neededNo
Hydro_Area_IDConfirm if neededNo
Creation_MethodConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision_MethodConfirm if neededNo
Year_of_RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Canal · Water Systems

Existing form reference: f38ab955cf2f6bd4

FieldUnitRequired
Canal TypeConfirm if neededNo
Canal NameConfirm if neededNo
Length In KmConfirm if neededNo
Width In MetersConfirm if neededNo
Hydro Area IDConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Lake · Water Systems

Existing form reference: 1bb76fa1770b0049

FieldUnitRequired
Lake_TypeConfirm if neededNo
Lake_NameConfirm if neededNo
Capacity_Acre_Per_FeetConfirm if neededNo
Perimeter_kmConfirm if neededNo
Area_In_sqkmConfirm if neededNo
Depth_In_MetersConfirm if neededNo
Spill_Level_MLSConfirm if neededNo
Catchment_AreaConfirm if neededNo
Hydro_Area_IDConfirm if neededNo
Creation_MethodConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision_MethodConfirm if neededNo
Year_of_RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
River · Water Systems

Existing form reference: d15540e8ecb12c69

FieldUnitRequired
River TypeConfirm if neededNo
River NameConfirm if neededNo
Length_In_KmConfirm if neededNo
Width_In_MetersConfirm if neededNo
Hydro_Area_IDConfirm if neededNo
Creation_MethodConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision_MethodConfirm if neededNo
Year_of_RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Lagoon · Water Systems

Existing form reference: 0f0d24cef4bd6481

FieldUnitRequired
Lagoon_TypeConfirm if neededNo
Lagoon NameConfirm if neededNo
Primary InflowsConfirm if neededNo
Primary_InflowsConfirm if neededNo
Length_In_KmConfirm if neededNo
Width_In_KmConfirm if neededNo
Capacity_Acre_Per_FeetConfirm if neededNo
Area_In_sqkmConfirm if neededNo
Depth_In_MetersConfirm if neededNo
Hydro_Area_IDConfirm if neededNo
Creation_MethodConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision_MethodConfirm if neededNo
Year_of_RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Spill Point · Water Systems

Existing form reference: dd591850f1e639e2

FieldUnitRequired
TypeConfirm if neededNo
NameConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
Sluice Point · Water Systems

Existing form reference: 70efb0310e727bec

FieldUnitRequired
Type Hydro pointConfirm if neededNo
NameConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
hydro_point_idConfirm if neededNo
Cascades · Water Systems

Existing form reference: a23c11282c20ec1d

FieldUnitRequired
RiverBasin NumberConfirm if neededNo
RiverBasin NameConfirm if neededNo
SWS NumberConfirm if neededNo
SWS NameConfirm if neededNo
Tank Cascade NumberConfirm if neededNo
Tank Cascade NameConfirm if neededNo
Number of TanksConfirm if neededNo
Number of Tanks1Confirm if neededNo
Climatic ZoneConfirm if neededNo
RemarksConfirm if neededNo
areaConfirm if neededNo
PerimeterConfirm if neededNo
HectaresConfirm if neededNo
UP CodeConfirm if neededNo
Color CodeConfirm if neededNo
IDConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Sea Ports · Water Systems

Existing form reference: 7caa76b009c9aa66

FieldUnitRequired
Port NameConfirm if neededNo
IDConfirm if neededNo
Port TypeConfirm if neededNo
DescriptionConfirm if neededNo
GFCODEConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
Water Area · Water Systems

Existing form reference: d89ee67747f1e131

FieldUnitRequired
Type_ClassificationConfirm if neededNo
Water Area NameConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
Hydro_Area_ID Confirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Mahaweli authorities · Administrative & Planning Areas

Existing form reference: a928ea0c164539db

FieldUnitRequired
idConfirm if neededNo
authority IdConfirm if neededNo
descriptionConfirm if neededNo
cityConfirm if neededNo
latitudeConfirm if neededNo
longitudeConfirm if neededNo
Mahaweli systems · Administrative & Planning Areas

Existing form reference: 8e71c080613ac3a4

FieldUnitRequired
idConfirm if neededNo
system IdConfirm if neededNo
descriptionConfirm if neededNo
mahaweli Authority DTO / idConfirm if neededNo
mahaweli Authority DTO / authority IdConfirm if neededNo
mahaweli Authority DTO / descriptionConfirm if neededNo
mahaweli Authority DTO / cityConfirm if neededNo
mahaweli Authority DTO / latitudeConfirm if neededNo
mahaweli Authority DTO / longitudeConfirm if neededNo
cityConfirm if neededNo
latitudeConfirm if neededNo
longitudeConfirm if neededNo
Mahaweli blocks · Administrative & Planning Areas

Existing form reference: 1b6608ff1b096b55

FieldUnitRequired
idConfirm if neededNo
codeConfirm if neededNo
mahaweli System DTO / idConfirm if neededNo
mahaweli System DTO / system IdConfirm if neededNo
mahaweli System DTO / descriptionConfirm if neededNo
mahaweli System DTO / mahaweli Authority DTOConfirm if neededNo
mahaweli System DTO / cityConfirm if neededNo
mahaweli System DTO / latitudeConfirm if neededNo
mahaweli System DTO / longitudeConfirm if neededNo
descriptionConfirm if neededNo
land AreaConfirm if neededNo
cultivated AreaConfirm if neededNo
irrigated AreaConfirm if neededNo
non Irrigated AreaConfirm if neededNo
created DateConfirm if neededNo
modified DateConfirm if neededNo
district DTO / idConfirm if neededNo
district DTO / nameConfirm if neededNo
district DTO / codeConfirm if neededNo
ds Division DTO / idConfirm if neededNo
ds Division DTO / codeConfirm if neededNo
ds Division DTO / nameConfirm if neededNo
ds Division DTO / created DateConfirm if neededNo
ds Division DTO / modified DateConfirm if neededNo
Mahaweli units · Administrative & Planning Areas

Existing form reference: b2dbe12695570d5c

FieldUnitRequired
idConfirm if neededNo
unit IdConfirm if neededNo
descriptionConfirm if neededNo
mahaweli Block DTO / idConfirm if neededNo
mahaweli Block DTO / descriptionConfirm if neededNo
mahaweli Block DTO / land AreaConfirm if neededNo
mahaweli Block DTO / cultivated AreaConfirm if neededNo
mahaweli Block DTO / irrigated AreaConfirm if neededNo
mahaweli Block DTO / non Irrigated AreaConfirm if neededNo

5. Documents and images

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

Mahaweli Authority of Sri Lanka Documents and images prototype screen
Mahaweli Authority of Sri Lanka. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open Documents and images. Check the institution name.
  2. Use All files, Documents or Images to find a file. Open its preview or download the original.
  3. Use a sample file to try Add file. Private is the starting choice. Public needs a source, permission to share and review.
  4. 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

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.

Mahaweli Authority of Sri Lanka Data structure management prototype screen
Mahaweli Authority of Sri Lanka. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open Data structure and choose Manage structure.
  2. 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.
  3. Give the definition a clear name, code and meaning. Reuse an existing definition when the meaning is the same.
  4. 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

7. Users and access

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

Mahaweli Authority of Sri Lanka Users and access prototype screen
Mahaweli Authority of Sri Lanka. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open User management and choose the institution. The rows are examples, not a list of your staff.
  2. Use View access to check a role. An administrator title alone does not give access to Private files.
  3. Try Preview invitation or Preview access change. Check the role, start date, optional end date and reason.
  4. 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

8. Can you share data regularly?

We currently use public data and published reports where available. Please confirm whether your institution can provide data directly, so we can avoid retyping or reading figures from PDFs.

Do not enter passwords, access keys or private account details.

9. Anything else we should change?

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.