You are on page 1of 321

Technical Assistance Consultants Report

Project Number: 37049-023


February 2012

TA 7189-INO
Institutional Strengthening for Integrated
Water Resources Management in the
6 Cis River Basin Territory

Decision Support Systems for Integrated Water Resources


Management in The Citarum River Basin

Financed by the Government of The Netherlands, Multi-Donor Trust


Fund under the Water Financing Partnership Facility, Climate
Change Fund and ADB's Technical Assistance Special Fund (TASF)

This consultants report does not necessarily reflect the views of ADB or the Government concerned, and
ADB and the Government cannot be held liable for its contents. (For project preparatory technical
assistance: All the views expressed herein may not be incorporated into the proposed projects design.
Prepared by
K-Water Institute
Korea Water Resources Corporation (K-Water)
Jeonmin-dong, Yusung-gu, Daejeon, Korea 306-711

For Directorate General of Water Resources Ministry of Public Works Republic of Indonesia
and the Asian Development Bank
NOTE

(i) The fiscal year (FY) of {the Government and its agencies} ends on {day month}.
FY before a calendar year denotes the year in which the fiscal year ends, e.g.,
FY2011 ends on 31 December 2011

(ii) In this report, "$" refers to US dollars.


Final Report
TA 7189-INO: INSTITUTIONAL STRENGTHENING FOR INTEGRATED WATER RESOURCES
MANAGEMENT (IWRM) IN THE 6 CIS RIVER BASIN TERRITORY PACKAGE D

DECISION SUPPORT SYSTEM FOR


INTEGRATED WATER RESOURCES
MANAGEMENT IN THE CITARUM
RIVER BASIN

February 2012

Korea Water Resources Corporation, Korea

i
Executive Summary

1. Introduction

The surface and ground water resources in the Citarum River Basin (CRB) are critical to
the social and economic development of Indonesia. They are essential for urban and
industrial development in the heavily urbanized Jabodetabek and Bandung areas,
especially for export industries, agricultural production through major irrigation systems,
rural water supplies, electricity generation, and fisheries. K-water and its international and
domestic consultants in collaboration with Perum Jasa Tirta II (PJT-II) under supervision
of BBWSC and ADB have developed a Decision Support System (DSS) for IWRM in the
Citarum River Basin (CRB) which is Package D of TA 7189-INO: Institutional
Strengthening for Integrated Water Resources Management (ISIWRM) in the 6 Cis River
Basin Territory, a program supported by ADB. Ultimately, the DSS is envisioned to
consist of hydrological and GIS databases; analytical models such as rainfall-runoff, water
allocation and water quality models; and optimized monitoring activities for acquisition of
hydrological and water quality data. The main tasks during the first phase included 1) data
collection and analysis, 2) hydrologic and GIS database development, 3) rainfall-runoff
model development, and 4) institutional strengthening and capacity building. This report
presents the development and results accomplished during the first phase of Package D.

2. Main Achievement and Findings

2.1. Data Collection and Analysis


Data collection and monitoring network analysis are continuous and iterative exercises,
requiring tremendous amount of time and effort. The initial large, consistent, and usable
data was obtained from PJT-II. Then, additional data were obtained from other agencies
such as BPLHD, Package C, etc. Significant analysis and re-organization efforts were
needed to bring these data into a consistent, usable format. There were large gaps in the
collected data as well as anomalous measurements. The monitoring networks for data
acquisition were analyzed for rainfall, flow, and water quality monitoring stations. Based
on international guidelines and in-depth analysis, optimized monitoring locations were
recommended to satisfy minimum densities for proper data coverage and to suit the future
perceived modeling requirements.

2.2. GIS and Hydrological Database Development


A GIS and hydrological database was developed to enhance data management and sharing
among the stakeholders in the basin and to provide essential data for analytical models.
The database and its constituent elements have emerged out of extensive consultations
conducted through a systematic framework. The database is capable of importing
information and data values from a number of different sources and formats including text
messages from mobile phones. The data import capabilities were built on the basis of
requirements for data input that started coming in from different agencies and their data

ii
flow regimes from field collection to storage. What makes the database unique is the
multifarious data import options available in the database which suit developing country
conditions where data comes from multiple means and sources and in multiple formats.
The DSS database developed in this project was populated with the collected data for
hydrological and spatial database and equipped with a data management tool named as
DSS Data Manager. They are all integrated and communicate directly with one another.
The GIS-based integrated database interacts with data management system and the users
through a convenient Graphic User Interface. The DSS Data Manager is to manage
hydrological & GIS data stored in the database and to share data among different agencies
playing various functions in managing the Citarum River Basin.

2.3. Rainfall-Runoff Forecasting System Development


A rainfall-runoff model was constructed for CRB area by employing RRFS, a long-term,
hydrologic rainfall-runoff model enabling the continuous simulation of daily, monthly and
yearly runoff. The model was built considering the three dams in the upstream area and
WTC and ETC in the downstream area. Various water usages (domestic, agricultural, and
industrial uses) were carefully taken into account. Through the land use and soil map of
CRB, the model was calibrated and verified using the observed flow data acquired during
the data collection activities. A reasonable modeling accuracy was obtained. Additionally,
an Ensemble Streamflow Prediction (ESP) method was implemented for future runoff
prediction with past rainfall scenario analyses and for improvement of runoff prediction.
The accuracy of runoff prediction with ESP was higher than the nave prediction with past
data. Besides, the accuracy was improved by applying weather forecast pretreatment.
Hence, monthly runoff prediction through ESP method was found to be appropriate. The
rainfall-runoff model developed using RRFS will provide basic input data for the water
allocation model scheduled in the later phase of this project. Additionally, RRFS- based
mid- and long-term ESP systems will play an important role in risk assessment and
probability analysis for dam operation and water allocation plan.

2.4. Institutional and Capacity Building


For successful implementation of DSS, the development was a consultative process to
bring all the stakeholders on board and to ensure that the specific needs of the stakeholders
would be addressed. Many meetings were organized throughout the project to get the
stakeholders on board. Also, several workshops and trainings were conducted including
counterpart training in Korea and inter-agency meetings for institutional strengthening and
capacity building. The project team met with all hydrological and water resources data
collection agencies operating in CRB, and identified how their existing systems and data
could cross-communicate or be integrated in a central system. In addition, the project team
met regularly with stakeholders and roadmap consultants to review ongoing and planned
IWRM activities and tried to investigate opportunities to create synergy among
stakeholder organizations.

3. Summary and Future Plan

iii
The objectives of this project are to develop an effective DSS for IWRM for CRB that can
be extended to 6 Cis River Basin Territory in the future and to strengthen the capacity of
water resources engineers for better water quantity and quality management. Once fully
developed and implemented, the DSS is expected to serve as a standardized framework on
which all current monitoring, modeling, and conservation practices can be integrated and
analyzed by the river basin managers. It is intended that the DSS be suitably
comprehensive and will provide support to all river managers without need for additional
tools.

To complete the DSS development, an additional funding of approximately US$5.0


million is required. The Government of Indonesia has submitted a requisition proposal to
Korean International Cooperation Agency (KOICA) for the required funding. If the
funding is successfully secured, several tasks such as monitoring system improvement,
development of Water Information System (WIMS), and institutional strengthening and
capacity building are to be conducted to fully develop the DSS.

iv
RINGKASAN EKSEKUTIF
I. Pendahuluan
Sumber air permukaan dan sumber air tanah di Citarum River Basin adalah sangat penting
untuk pembangunan sosial dan ekonomi Indonesia. Mereka sangat penting untuk
pembangunan perkotaan dan industri di Jabodetabek yang sangat padat dan daerah
Bandung, terutama untuk industri ekspor, produksi pertanian melalui sistem irigasi besar,
pasokan air pedesaan dan perkotaan, pembangkit listrik, dan perikanan. K-Water dan
partner konsultan internasional dan domestik bekerja sama dengan Perum Jasa Tirta II
(PJT II) di bawah pengawasan BBWSC dan ADB telah mengembangkan Sistem
Pendukung Keputusan (Decision Support System/DSS) untuk IWRM di Sungai Citarum
(CRB) dalam Paket D yang merupakan bagian dari TA 7189-INO: Institutional
Strengthening for Integrated Water Resources Management (ISIWRM) in the 6 Cis River
Basin Territory, sebuah program yang didukung oleh ADB. Pada akhirnya, DSS dibuat
terdiri dari database hidrologi dan GIS; model analitis seperti curah hujan-limpasan
(RRFS), alokasi air dan model kualitas air dll, dan kegiatan pemantauan dioptimalkan
untuk perolehan data hidrologi dan kualitas air. Tugas utama selama fase pertama adalah
1) pengumpulan data & analisis, 2) pengembangan hidrologi & database GIS, 3) curah
hujan-limpasan pengembangan/RRFS model, dan 4) penguatan kelembagaan & kapasitas
SDM. Laporan ini menyajikan pengembangan dan hasil yang dicapai selama tahap
pertama Paket D.

II. Hasil Utama dan Temuan

a. Pengumpulan Data dan Analisis


Pengumpulan data dan analisis jaringan pemantauan terus menerus dan pengulangan-
pengulangan interkasi, membutuhkan sejumlah besar waktu dan usaha. Sejumlah data
awal yang besar, konsisten, dan dapat digunakan diperoleh dari PJT-II. Kemudian, data
tambahan diperoleh dari lembaga lain seperti BPLHD, Dinas Pengairan Jabar, Paket C, dll.
Analisis yang signifikan dan upaya melakukan re-organisasi data yang diperlukan untuk
membawa data ke dalam format yang konsisten dan yang dapat digunakan cukup
melelahkan. Ada kesenjangan yang besar dalam data yang dikumpulkan serta pengukuran
yang anomali. Jaringan pemantauan untuk akuisisi data dianalisis untuk curah hujan,
aliran, dan stasiun pemantauan kualitas air. Berdasarkan pedoman internasional dan
analisis mendalam, optimalisasi lokasi monitoring direkomendasikan untuk memenuhi
kepadatan minimum untuk cakupan data yang tepat dan sesuai dengan persyaratan
pemodelan masa depan.

b. GIS dan Pengembangan Basis Data Hidrologi


Sebuah GIS dan database hidrologi dikembangkan untuk meningkatkan manajemen data
dan berbagi di antara para pemangku kepentingan dalam DAS Citarum dan untuk
menyediakan data penting bagi model analitis. Database dan elemen penyusunnya telah
disiapkan oleh konsultasi secara luas serta dilakukan melalui kerangka kerja sistematis.
Database tersebut mampu mengimpor nilai informasi dan data dari sejumlah sumber yang
berbeda format termasuk pesan teks dari ponsel. Kemampuan data impor dibangun atas
dasar persyaratan untuk input data yang mulai datang dari lembaga yang berbeda dan

v
aturan data mereka yang masuk dari petugas lapangan untuk disimpan. Apa yang
membuat database ini unik adalah tersedianya aneka pilihan jenis data dalam system
database yang sesuai kondisi negara berkembang dimana data datang dari berbagai sarana
pengiriman dan berbagai sumber data dan dalam berbagai format. Database DSS yang
dikembangkan dalam proyek ini diisi dengan data yang dikumpulkan untuk database
hidrologi dan spasial serta dilengkapi dengan alat manajemen data dinamakan sebagai
Data Manager DSS. Mereka semua terintegrasi dan berkomunikasi langsung satu sama
lain. Database berbasis GIS terpadu berinteraksi dengan sistem manajemen data dan
pengguna melalui Graphic User Interface secara nyaman. Tugas Para Data Manager DSS
adalah untuk mengelola data hidrologi & GIS yang disimpan dalam system database dan
berbagi data antar instansi yang berbeda tugas fungsinya dalam mengelola Daerah Aliran
Sungai Citarum.

c. Pengembangan Sistem Peramalan Curah Hujan-Limpasan


Sebuah model curah hujan-limpasan dibangun untuk daerah CRB menggunakan model
RRFS, jangka panjang, hidrologi curah hujan-limpasan model yang memungkinkan
simulasi limpasan harian, bulanan dan tahunan secara menerus. Model dibangun
mempertimbangkan tiga bendungan di daerah hulu dan WTC dan ETC di daerah hilir.
Penggunaan air (domesitic, pertanian, dan industri) dengan hati-hati diperhitungkan.
Melalui penggunaan lahan dan peta tanah CRB, model tersebut dikalibrasi dan diverifikasi
menggunakan data aliran yang diamati dan diperoleh selama kegiatan pengumpulan data.
Sebuah akurasi pemodelan yang wajar diperoleh. Selain itu, sebuah metode Predition
Ensamble Debit (Ensemble Stream-flow Prediction / ESP) diterapkan untuk scenario
prediksi limpasan masa depan dengan analisis curah hujan masa lalu untuk perbaikan
prediksi limpasan. Ketepatan prediksi limpasan dengan ESP lebih tinggi dari prediksi naif
dengan data masa lalu. Selain itu, akurasi ditingkatkan dengan menerapkan pretreatment
prakiraan cuaca. Oleh karena itu, limpasan prediksi bulanan melalui metode ESP
ditemukan adalah cocok/sesuai. Model curah hujan limpasan-dikembangkan
menggunakan RRFS akan memberikan masukan data dasar untuk model alokasi air yang
dijadwalkan dibuat pada tahap pengembangan selanjutnya dari proyek ini. Selain itu,
RRFS berbasis system ESP pertengahan dan jangka panjang akan memainkan peran
penting dalam penilaian risiko dan analisis probabilitas untuk operasi bendungan dan
rencana alokasi air.

d. Kelembagaan dan Peningkatan Kapasitas


Untuk keberhasilan implementasi DSS, pengembangannya merupakan suatu proses
konsultatif untuk membawa semua pemangku kepentingan terlibat dan untuk memastikan
bahwa kebutuhan khusus dari para pemangku kepentingan akan ditangani dan difasilitasi.
Banyak rapat yang diselenggarakan sepanjang proyek untuk mengajak stakeholder keatas
pentas IWRM. Juga, beberapa lokakarya dan pelatihan dilakukan termasuk training di
Korea dan rapat rapat antar badan untuk penguatan kelembagaan dan peningkatan
kapasitas SDM terutama insinyur yang akan berperan aktif dalam menjalankan DSS. Tim
proyek bertemu dengan semua instansi pengelola dan pengumpul data hidrologi yang
beroperasi di CRB, dan mengidentifikasi bagaimana sistem yang ada dan data dapat cross-
berkomunikasi atau diintegrasikan dalam sistem terpusat. Selain itu, tim proyek bertemu
secara teratur dengan para pemangku kepentingan dan konsultan ICWRMIP Roadmap

vi
untuk meninjau kegiatan IWRM yang sedang berjalan maupun dalam rencana dan
mencoba untuk menyelidiki peluang dalam menciptakan sinergi antara organisasi
pemangku kepentingan.

III. Ringkasan dan Rencana Kedepan


Tujuan dari proyek ini adalah untuk mengembangkan efektif DSS untuk pelaksanaan
IWRM di Citarum River Basin yang dapat juga digunakan oleh ke 6 Wilayah Sungai di
masa depan dan untuk memperkuat kapasitas insinyur sumber daya air dalam mengelola
kuantitas dan kualitas air yang lebih baik. Setelah sepenuhnya dikembangkan dan
diimplementasikan, DSS diharapkan dapat berfungsi sebagai kerangka kerja standar di
mana semua pengelolaan, pemodelan, dan praktek konservasi saat ini dapat diintegrasikan
dan dianalisis oleh Manajer Daerah Aliran Sungai. Hal ini dimaksudkan bahwa DSS harus
komprehensif dan akan memberikan dukungan untuk semua manajer sungai tanpa perlu
alat tambahan.

Untuk menyelesaikan pengembangan DSS, sebuah dana tambahan sekitar US $ 5,0 juta
diperlukan. Pemerintah Indonesia telah mengajukan proposal permintaan untuk Badan
Kerjasama Internasional Korea (KOICA) guna mendapat dana yang diperlukan. Jika dana
tersebut berhasil diamankan, beberapa tugas seperti perbaikan sistem moitoring,
Pengembangan Sistem Informasi Sumber Daya Air (WIMS), dan penguatan kelembagaan
serta peningkatan kapasitas SDM dapat dilakukan untuk sepenuhnya mengembangkan dan
mengoperasikan decision support system ini.

vii
Participants

Implementation Team
K-water, Korea
s Dr. Jeongkon Kim, Senior Water Management Specialist, Project Manager
s Dr. Ick Hwan Ko, Senior Water Resources Specialist, Project Advisor
s Dr. Sangyoung Park, Senior GIS & Non-point Source Specialist, On-site Team Leader
s Mr. Sanguk Lee, Reservoir Water Quality Specialist
s Dr. Sang Jin Lee, Senior Hydrologist
s Dr. Joo Cheol Kim, Hydrologist
s Dr. Seongho Cho, Water Quality Management Specialist
s Mr. Fouad Kahn, Water Quality and DB Specialist
s Dr. Eui Ho Hwang, DB & IT Systems Specialist
s Dr. Shin Uk Kang, Water Resources Systems Specialist
s Dr. Ki Uk Cha, Senior Water Resources System Specialist
s Mr. Hyun Sik Kim, Senior Water Resources Specialist
s Mr. Chul Kyun Shin, Water Resources Specialist
Consultants (Websolus), Korea
s Mr. Yoo Jin Kim, DB Development Leader
s Mr. Ho Jin Lee, Senior DB Specialist
s Mr. Shin Jae Kang, Senior GIS Specialist
Consultants, Indonesia
s Mr. Soenarto Soendjaja & Minanto, On-site Deputy Team Leader
s Dr. Arno Kuntoro & Mohammad Farid, Hydrologist
s Dr. Hadi Kardhana, Hydrological Modeling Specialist
s Dr. Marisa Ling, GIS Specialist
s Mr. Robby Maulana, Software Programmer
s Ms. Veronica Kasim & Nur Aksar Sari, Project Coordinator
Counterparts, Indonesia
s BBWSC: Raden Didi Garnida, Dani Hamdan and Riska Hilmi
s PJT-II: Reni Mayasari, Erni Murniati and Hendra Rachtono
s BPSDA: Sumarno, Indra Kurniawan, Brilian Parmawati and Adhi Kurniawan
s Bina Program: Meita Rudiahningsih, Kalmah, Arie Setyorini and Aryo Hudiotomo
s BDIJ: Nely Mulyaningsih and Adi Primadika Diaz
s BPLHD: Sofyan Hadi and Windi Dwi Windiandi
s PusAir: Rebiet Rimba Rinjani

viii
Advisory Group

s Dr. Thomas Panella, Principal Water Resources Specialist of ADB


s Mr. Eric Quincieu, ADB Consultant
s Dr. A. Hasanudin, Head of BBWSC
s Dr. Mohamad Hassan, Director-General of DGWR
s Dr. Setiawan, Head of the West Java BPLHD
s Mr. Dedi Djunaedi, Director of PSDA
s Mr. Herman Idurus, Director of Water Management, PJT-II
s Dr. Deuk Koo Koh, Executive Director of R&D, K-water
s Mr. Phyll Sun Hwang, Director of Water Resources Operations Center, K-water

ix
Table of Content

1. Introduction .....................................................................................................1
1.1 Project Background .....................................................................................1
1.2 Roadmap .......................................................................................................2
1.3 Decision Support System for IWRM (Package D) ......................................3
2. Data Collection and Monitoring Network Design .........................................6
2.1 Overview of Data Collection ........................................................................6
2.2 GIS Data ........................................................................................................7
2.2.1 Base Layers .........................................................................................7
2.2.2 Hydrological Information Layers ...........................................................9
2.2.3 Geological Information Layers ............................................................11
2.3 Hydrological Data Analysis and Monitoring Network Design .................14
2.3.1 Data Analysis .....................................................................................14
2.3.2 Monitoring Network Design ................................................................20
2.4 Water Quality Data Analysis and Monitoring Network Design ................31
2.4.1 Data Analysis .....................................................................................31
2.4.2 Design of Water Quality Monitoring Network ......................................37
3. Development of DB and GIS Database .......................................................41
3.1 Introduction ................................................................................................41
3.2 Database System Development Process for DSS ....................................42
3.3 Hydrological Database ...............................................................................44
3.3.1 Status of Existing Data Storage System .............................................45
3.3.2 Population Status ...............................................................................49
3.3.3 User Requirement Analysis ................................................................50
3.3.4 Design of DB Structure .......................................................................55
3.4 Development of GIS Database...................................................................58
3.4.1 Data Preparation and Selection for GIS Database..............................59
3.4.2 Final GIS Layers.................................................................................63
3.5 DSS Database .............................................................................................65
3.5.1 Menu Diagram....................................................................................65
3.5.2 Key Features of DSS Data Manager ..................................................66
3.5.3 Graphical User Interface.....................................................................72
3.6 Information Systems Implementation Program .......................................78
3.6.1 Introduction ........................................................................................78
3.6.2 System Configuration .........................................................................79

x
3.6.3 Database Server Configuration ..........................................................82
3.6.4 GIS Server Configuration ...................................................................83
3.6.5 Data Manager Configuration ..............................................................89
3.6.6 Issues and Recommendation .............................................................97
4. Development of Rainfall-Runoff Forecast System ................................... 100
4.1 RRFS Introduction ....................................................................................100
4.2 Model Construction ..................................................................................101
4.2.1 Sub-catchment delineation of CRB...................................................101
4.2.2 Input Data.........................................................................................106
4.3 Result of Application in CRB ...................................................................107
4.3.1 Model Calibration and Verification ....................................................107
4.3.2 Simulation in the Canals Considering Water Allocation ....................113
4.4 Application of ESP Technique with PDF Ratio Method .........................120
4.4.1 Overview of ESP Technique .............................................................120
4.4.2 Probabilistic Weather Outlooks and PDF Ratio Method ....................121
4.4.3 Case Study of ESP Technique with PDF Ratio .................................125
4.5 Results ......................................................................................................135
5. Capacity Building and Institutional Arrangement .................................... 136
5.1 Summary of Stakeholder Consultations .................................................138
5.1.1 Balai Data and Information and Balai PSDA Citarum, PWRS ...........138
5.1.2 PJT-II ...............................................................................................138
5.1.3 BPLHD .............................................................................................138
5.1.4 BMKG Bogor ....................................................................................138
5.1.5 Water Balance and Water Quality Modeling, RIBASIM .....................139
5.1.6 PusAir ..............................................................................................139
5.1.7 West Java Communication and Information Agency.........................139
5.1.8 National Development Planning Agency (BAPPENAS) ....................139
5.2 Counterpart Activity .................................................................................140
5.2.1 Counterparts Training .......................................................................140
5.2.2 Training Program at K-water............................................................140
5.3 Institutional Arrangement ........................................................................142
5.3.1 Current Status of Institutions in Water Resources Data Management in
Citarum Basin...................................................................................142
5.4 The Institutional Development of DSS Project for IWRM in Citarum Basin
.........................................................................................................145
5.4.1 Scope of Works ................................................................................145
5.4.2 Regulations ......................................................................................146
5.4.3 Human Resources............................................................................146

xi
5.4.4 Technology.......................................................................................146
5.4.5 Fund .................................................................................................146
5.4.6 Working Environment .......................................................................146
5.4.7 Recommendations on Initial Design of Institutional Setup for DSS
Implementation .................................................................................147
5.4.8 Collaboration Plan between Institutions ............................................148
5.5 The Strategic Issues of Institutional Development ................................149
5.5.1 Inter-agency Workshop on Legal Framework for DSS Implementation
(9-10 August 2011, Bandung)...........................................................150
5.5.2 Data Sharing Management Workshop (1-2 February 2012, Bandung)
.........................................................................................................150
6. Future Plan & Summary ............................................................................. 151
6.1 Proposal for Further Work .......................................................................151
6.1.1 Funding for the Future Phases .........................................................151
6.1.2 Project Description ...........................................................................151
6.1.3 Project Objective (Short Term and Long Term) ................................151
6.1.4 Scope of Works ................................................................................152
6.1.5 Outputs of each phase: ....................................................................153
6.1.6 Project Sustainability ........................................................................153
6.2 Database Extension .................................................................................154
6.3 DSS Development ....................................................................................154
6.4 Summary ...................................................................................................155
7. References .................................................................................................. 157

xii
Appendices

Appendix 1:Graphics User Interface for GIS and Hydrological Database . 159
Appendix 2:Structure Code List .................................................................... 172
Appendix 3:UCD Specification ....................................................................... 193
Appendix 4:Data Flow Diagrams ................................................................... 197
Appendix 5:GIS Maps in Database ................................................................ 206
Appendix 6:Class Diagrams........................................................................... 212
Appendix 7:ERD (Entity-Relationship Diagram) ........................................... 225
Appendix 8:Summary of Meetings ................................................................ 291

xii
List of Figures

Figure 1: Citarum River Basin...................................................................................... 1


Figure 2: Strategic Framework for Roadmap Development ...................................... 3
Figure 3: Scope of Work for Counter Part Agencies .................................................. 5
Figure 4: Location of CRB in Java Island, DEM, Administrative and Transport
Network ......................................................................................................... 8
Figure 5: Land Cover in CRB ....................................................................................... 8
Figure 6: Village Wise Population in CRB ................................................................... 9
Figure 7: Water Reservoirs, Stream and Canal Network and Stream Network
Structures in CRB ....................................................................................... 10
Figure 8: Sub-catchments, Flow Meters, Rainfall and Weather Stations and Water
Quality Sampling Locations in CRB .......................................................... 10
Figure 9: Geology in CRB .......................................................................................... 11
Figure 10: Soil Water Content in CRB ....................................................................... 12
Figure 11: Lithology in CRB ....................................................................................... 12
Figure 12: NRCS Soil Classification .......................................................................... 13
Figure 13: Soil Texture Classification ....................................................................... 13
Figure 14: Rainfall Station Locations in CRB ........................................................... 15
Figure 15: Flow Monitoring Locations from PJT-II ................................................... 15
Figure 16: Rainfall Data Availability .......................................................................... 16
Figure 17: Spatial Coverage of Rainfall Data ............................................................ 17
Figure 18: Observed Discharge Data at (a) Saguling, (b) Cirata, and (c) Juanda. .. 19
Figure 19: Stream Network Identification ................................................................. 21
Figure 20: DEM Based Sub-catchment Delineation at Different Resolutions ......... 21
Figure 21: The Selected Rainfall Stations in CRB on DEM ...................................... 23
Figure 22: The Selected Rainfall Stations in CRB against Population Density ...... 23
Figure 23: Suggested Rainfall Station Locations ..................................................... 26
Figure 24: Suggested Flow Station Locations .......................................................... 28
Figure 25: Current Water Quality Monitoring Stations ............................................. 31
Figure 26: Monthly Variation of DO, BOD, and COD ................................................ 34
Figure 27: Variation of NH3-N, NO2-N, and NO3-N ................................................... 35
Figure 28: Correlation Coefficients of BOD and COD .............................................. 36
Figure 29: Watershed Area Weighted BOD Concentration of the Major Sites........ 38
Figure 30: Suggested Water Quality Monitoring Stations ....................................... 39
Figure 31: Suggested Water Quality Monitoring Stations (Upstream of Inlet
Saguling) ..................................................................................................... 39

xiii
Figure 32: Suggested Water Quality Monitoring Stations (Saguling, Cirata and
Jatiluhur Reservoir) .................................................................................... 40
Figure 33: Suggested Water Quality Monitoring Stations (East Tarum Canal) ...... 40
Figure 34: The Purpose of Integrated Database Development ................................ 41
Figure 35: Configuration Hydrological and GIS Database System ......................... 42
Figure 36: Development Process .............................................................................. 43
Figure 37: Identification of Data for Hydrological Database Development............. 44
Figure 38: Water Information System (SISDA) Developed by PJT-II ....................... 46
Figure 39: Hydrology Information System Developed by PusAir ............................ 47
Figure 40: Procedure of Data Management in DPSDA ............................................. 48
Figure 41: Water Quality Information System (SISLING) Developed by BPLHD .... 49
Figure 42: The Gauge Station Code Structure .......................................................... 55
Figure 43: ERD of Hydrological Database................................................................. 57
Figure 44: Database Component Diagram ................................................................ 58
Figure 45: GIS Database Structure ............................................................................ 59
Figure 46: GIS Layers Applied in DSS Database ...................................................... 64
Figure 47: DSS Data Manager Main Screen .............................................................. 65
Figure 48: Menu Diagram ........................................................................................... 65
Figure 49: Data Input Wizard ..................................................................................... 66
Figure 50: Data Export to Excel Format .................................................................... 67
Figure 51: Data Validation Screen ............................................................................. 67
Figure 52: Integrated RRFS Screenshot ................................................................... 68
Figure 53: Reports ...................................................................................................... 70
Figure 54: DSS Data Manager Manuals ..................................................................... 71
Figure 55: Home Screen............................................................................................. 72
Figure 56: Result of Searched data in table and graph ............................................ 73
Figure 57: Data Import Wizard ................................................................................... 74
Figure 58: Preview of Imported Data ......................................................................... 75
Figure 59: GIS View Button ........................................................................................ 75
Figure 60: GIS Map Screen ........................................................................................ 76
Figure 61: GIS Map Icons ........................................................................................... 77
Figure 62: Progress of DSS Database Operation ..................................................... 78
Figure 63: Hardware Configuration ........................................................................... 79
Figure 64: Server Requirements ................................................................................ 80
Figure 65: Client Requirements ................................................................................. 80
Figure 66: Software Installed in DSS Server ............................................................. 81
Figure 67: SQL Server Configuration Manager ........................................................ 82
Figure 68: Context Menu of SQL Server Service ...................................................... 82

xiv
Figure 69: ArcGIS Server Manager Login Screen..................................................... 83
Figure 70: ArcGIS Server Manager Configuration Screen ....................................... 84
Figure 71: List of GIS Maps on Service ..................................................................... 84
Figure 72: Start, Stop, and Restart Function ............................................................ 85
Figure 73: Select GIS map for Detailed Information ................................................. 85
Figure 74: Parameters Menu Screen ......................................................................... 86
Figure 75: Capabilities Menu Screen......................................................................... 86
Figure 76: Pooling Screen.......................................................................................... 87
Figure 77: Caching Screen......................................................................................... 87
Figure 78: Log Files Menu Screen ............................................................................. 88
Figure 79: Location of DataManager.exe.config File .............................................. 89
Figure 80: Content of DataManager.exe.config File ............................................... 89
Figure 81: ArcGIS server IP configuration Screen ................................................... 90
Figure 82: Authentication Management Screen ....................................................... 91
Figure 83: Authentication Management Detail Button ............................................. 91
Figure 84: Changing Authority of Account ............................................................... 92
Figure 85: Adding New Account ................................................................................ 92
Figure 86: User Management Menu ........................................................................... 93
Figure 87: Filtering Tool ............................................................................................. 93
Figure 88: Result Screen of Using Filtering Tool ..................................................... 94
Figure 89: Detail Button on User Management Screen ............................................ 94
Figure 90: User Information Screen .......................................................................... 95
Figure 91: Adding New Account ................................................................................ 95
Figure 92: Setting Information for New Account ...................................................... 96
Figure 93: Network Configuration 1 .......................................................................... 97
Figure 94: Network Configuration 2 .......................................................................... 98
Figure 95: Network Configuration 3 .......................................................................... 99
Figure 96: Rainfall Runoff Forecasting System ...................................................... 100
Figure 97: Sub-Catchment Delineation ................................................................... 101
Figure 98: Final CRB Sub-catchment Division ....................................................... 102
Figure 99: Drainage Schematic in Central CRB ...................................................... 103
Figure 100: Schematic diagram of drainage system of WTC................................. 104
Figure 101: Schematic diagram of drainage system of ETC.................................. 105
Figure 102: Schematic diagram of drainage system of NTC ................................. 105
Figure 103: RRFS Modeling Calibration Results in 2002 Saguling Dam ............ 109
Figure 104: RRFS Modeling Calibration Results in 2002 Cirata Dam................. 109
Figure 105: RRFS Modeling Calibration Results in 2002 Juanda Dam .............. 110

xv
Figure 106: RRFS Modeling Verification Results in 2004 Saguling Dam ........... 110
Figure 107: RRFS Modeling Verification Results in 2004 Juanda Dam.............. 110
Figure 108: RRFS Modeling Verification Results in 2005 Saguling Dam ........... 111
Figure 109: RRFS Modeling Verification Results in 2005 Juanda Dam.............. 111
Figure 110: Yearly Histogram of Runoff Ratio in Saguling and Cirata ................. 112
Figure 111: Yearly Histogram of Runoff Ratio in Juanda ...................................... 113
Figure 112: Water Availability and Distribution Schematic in CRB....................... 113
Figure 113: WTC Simulation Schematic Diagram................................................... 114
Figure 114: Simulation Results of Bekasi Weir Inflow ........................................... 115
Figure 115: Simulation Results of Cikarang Weir Inflow ....................................... 116
Figure 116: Simulation Results of Cibeet Weir Inflow ............................................ 117
Figure 117: ETC Simulation Schematic Diagram.................................................... 118
Figure 118: Simulation Results of Barugbug Weir Inflow ...................................... 119
Figure 119: Simulation Results of Macan Weir Inflow ........................................... 119
Figure 120: Simulation Results of Salam Darma Weir Inflow ................................ 119
Figure 121: Schematic diagram of RRFS-ESP System ......................................... 120
Figure 122: Generation of ESP Scenarios............................................................... 120
Figure 123: A priori Distribution of Rainfall ............................................................ 123
Figure 124: Distribution of Rainfall with Above Forecast ...................................... 123
Figure 125: Distribution of Rainfall with Normal Forecast..................................... 124
Figure 126: Distribution of Rainfall with Below Outlook ........................................ 124
Figure 127: ESP Result of Monthly Inflow into Saguling Dam, Jan. 2005 ............. 127
Figure 128: ESP Probability of Monthly Inflow into Saguling Dam, Jan 2005 ...... 128
Figure 129: Saguling January Rainfall PDF with Normal Weather Forecast ........ 131
Figure 130: Saguling February Rainfall PDF with Above Weather Forecast ........ 131
Figure 131: Saguling April Rainfall PDF with Below Weather Forecast ................ 132

Figure 132: Cumulative Probability of ESP Scenario for


Q33.3 and Q66.7 ............... 133

Figure 133: Cumulative Probability of PDF ratio Scenario for


Q33.3 and Q66.7 ..... 133

Figure 134: Seven Trainees in Korea, 10-14 May 2011 ........................................... 141
Figure 135: Citarum River Basins Stakeholders in Administration System of
Indonesia Government .......................................................................144
Figure 136: Initial Design of Institutional Setup for DSS Implementation .............147
Figure 137: Institutional Framework for DSS Implementation ................................147
Figure 138: Anternative No.1: Collaboration between Institutions ........................148
Figure 139: Anternative No.2: Collaboration between Institutions ........................148
Figure 140: User group of Water Information Management System ......................152

xvi
List of Tables

Table 1: Data Collection and Source Summary ...........................................................6


Table 2: Recommended Minimum Densities for Rainfall Stations ...........................22
Table 3: Rainfall Station Location Suggestion for Monitoring Optimization ...........24
Table 4: Suggested Rainfall Station Locations .........................................................25
Table 5: Suggested Flow Station Locations ..............................................................28
Table 6: Monitored Water Quality Parameters from each Agency. ..........................32
Table 7: Major Water Quality Monitoring Sites of the Citarum River Mainstream ...37
Table 8: Hydrological Database Layers .....................................................................45
Table 9: Data Population Status .................................................................................49
Table 10: Program Usage ............................................................................................50
Table 11: URS (User Requirement Specification) ......................................................52
Table 12: Station Code Structure ...............................................................................56
Table 13: GIS Data Collected from PJT-II ...................................................................59
Table 14: GIS Maps Selected for Database Base Layer ............................................63
Table 15: GIS Map Icon Legend ..................................................................................77
Table 16: Hardware Explanation .................................................................................79
Table 17: Software Installed in DSS Server ...............................................................81
Table 18: Results of Model Calibration ....................................................................108
Table 19: Result of Error Analysis for Verification Period ......................................111
Table 20: Runoff Ratio of Main Control Points in CRB ...........................................112
Table 21: Example of Probability Weather Forecasting ..........................................121
Table 22: Interval Probability with respect to Weather Forecasting ......................121
Table 23: Nave Forecasting of Monthly Rainfall .....................................................125
Table 24: Nave Forecasting of Monthly Inflow .......................................................126
Table 25: Observational Rainfall by Month ..............................................................129
Table 26: Weather Forecasts by Month ....................................................................130
Table 27: Prediction Score by ESP and PDF ratio ...................................................134
Table 28: Summary of Meetings ...............................................................................136
Table 29: List of Trainee Selected from DGWR .......................................................140
Table 30: Training Agenda in Korea, K-water Headquarter, Daejeon.....................141
Table 31: Legal Mandates and Role in Water Resources Data Management ........142
Table 32: Legal Mandates and Role in Other Institutions .......................................143

xvii
Acronyms

ADB Asian Development Bank


AE Absolute Error
AWLR Automatic Water Level Recorder
AWS Automatic Weather Station
BAPPEDA Local Government Planning Board
BBWSC Balai Besar Wilayah Sungai Citarum
BFLIM Maximum Subsurface Runoff Rate
BII Baseflow Infiltration Index
BII-BFP Baseflow Infiltration Index-Baseflow Percent
BMKG Badan Meteorologi Klimatologi dan Geofisika
BPDAS Balai Pengelolaan Daerah Aliran Sungai
BPLHD Badan Pengelolaan Lingkungan Hidup Daerah
CFC Cibeet Feeder Canal
CMSS Communication Message Support System
CRB Citarum River Basin
CSO Civil Society Organization
DAMS Data Acquisition and Management System
DAS Daerah Aliran Sungai
DGWR Directorate General of Water Resources
DISKOMINFO Dinas Komunikasi Dan Informatika
DPSDA Dinas Pengelolaan Sumber Daya Air
DSS Decision Support System
ESP Ensemble Stream-flow Prediction
ETC East Tarum Canal
GIS Geographic Information System
GOI Government of Indonesia
GR4J Ge'nie Rural a' 4 parame'tres Journalier
GUI Graphic User Interface
HEC-RAS Hydrologic Engineering Centers River Analysis System
ICWRMIP Integrated Citarum Water Resources Management Investment Program
IRWMS Integrated Real-Time Basin Water Management System
ISDI Indonesian Spatial Data Infrastructure
ISIWRM Institutional Strengthening for Integrated Water Resources Management
IWRM Integrated Water Resources Management
JICA Japan International Cooperation Agency
JIS Jatiluhur Irrigation Scheme
KMA Korea Meteorological Administration
KModSim Korea Modified Simyld
KOICA Korea International Cooperation Agency
K-water Korea Water Resources Corporation
LOA Letter of Agreement
LPSE Layanan Pengadaan Secara Electronik
MODQUAL Water Quality Model
MOE Ministry of Environment
MOU Memorandum of Understanding
NGO Non-Government Organization
NSDI National Spatial Data Infrastructure

xviii
NTC North Tarum Canal
OPD Organisasi Perangkat Daerah (Offices of West Java Province)
PAS Provincial Agriculture Service
PBLZ Percent of total Baseflow going to Lower Zone routing
PIU Project Implementation Unit
PJT-II Perum Jasa Tirta II
PMO Project Management Office
PusAir Puslitbang Sumber Daya Air
PWRS Provincial Water Resources Service
RBO River Basin Organization
RBT River Basin Territory
RCMU Roadmap Coordination Management Unit
RCWR Research Center for Water Resources
RDS Reciprocal Distance Square
RIBASIM River Basin Simulation Model
RMSE Root Mean Square Error
RR Rainfall Record
RRFS Rainfall-Runoff Forecasting System
SDI Spatial Data Infrastructure
SISDA Sistem Informasi Sumber Dava Air
SMI Soil Moisture Index
SMI-ROP Soil Moisture Index-Runoff Percent
S-SS Surface-Subsurface Separation
TMA Tinggi Muka Air
TOR Terms of Reference
Ts Retention time of baseflow
VPN Virtual Private Network
WAMIS Water Management Information System
WL Water Level
WLR Water Level Recorder
WTC West Tarum Canal

xix
1. Introduction

1.1 Project Background

The surface and groundwater resources in the Citarum River Basin (CRB), Indonesia, shown
in Figure 1: are critical to social and economic development of the country. They are essential
for urban and industrial development (particularly in Jabodetabek and Bandung areas)
including export industries, agricultural production through major irrigation systems, rural
water supplies, electricity generation, and fisheries. While the water resources of the CRB are
relatively abundant, competition for these resources has increased significantly over the past
twenty years leading to a situation of acute water stress and excessive depletion of aquifers in
some places. Rapid urbanization has significantly increased the exposure to flood risk.
Environmental degradation has reached a level that compromises public health and
livelihoods, particularly for the urban and rural poor, and incurs additional economic and
financial costs related to the source of bulk water supply and its treatment.
The adoption of Integrated Water Resources Management (IWRM) principles and
sustainability of the water resource was emphasized in the 2004 Water Law. The Water Law
introduces the concept of management within the boundaries of a river basin and reflects the
principles of decentralization and devolvement of authority to local levels as promoted by the
program of regional autonomy. A Roadmap (Strategic investment plan) has been prepared
for basin-wide IWRM based on a Vision of basin stakeholder for Government and
community working together for clean, healthy, and productive catchments and rivers
bringing sustainable benefits to all people in the CRB.

Jakarta

Juanda Dam

Cirata Dam

Bandung
Saguling Dan

Figure 1: Citarum River Basin

1
1.2 Roadmap

The process for the development of a roadmap for the Citarum River Basin has followed the
basic methodology of strategic planning.
s Fundamentally, the approach has been to ask the following three questions:
Where do we want to go (with water resource management in the basin)?
Where are we now (that is, what are the existing issues/problems)?
How can we get from where we are now to where we want to go (the road we need
to take)?

Much has been written about the current issues for water resource management in the basin,
and the key issues are well documented in a variety of documents produced in the last decade.
The problems are numerous and cover a variety of areas, including severe deterioration of
water quality, deforestation and degradation of upland catchments, mining of groundwater
and degradation of water control infrastructure. These problems have severe economic and
social cost consequences to the people of the basin.

The roadmap itself is simply a set of strategies (and projects/actions to implement those
strategies) that define the path between the present situation with respect to water resources in
the basin and the desired outcomes (or vision) for the future that is, what needs to be done
to achieve the objectives.
s This has been achieved using the following vision-oriented approach:
Reaffirm and more clearly define a shared vision of stakeholders for the future of the
Citarum River Basin (to the year 2020);
Compare the present status of water resources in the basin to the vision, in order to
identify the strategic direction that needs to be taken (the road so to speak);
Formulate objectives in a number of key areas that would, if achieved, lead to the
fulfillment of the vision;
Develop a set of interventions (projects) the successful implementation of which
would achieve the objectives in each key area.

Close to seventy interventions have been identified as necessary for the achievement of the
objectives (and hence the vision) for the Citarum River Basin. These have come from a
variety of sources. The costs that have been assumed for each of these come from those
sources (factored into 2006-dollar terms) and can only be considered as indicative, and of
course must be firmed up during project preparation.

The strategic framework to arrive at the roadmap was developed in consultation with a broad
range of basin stakeholders to ensure that an integrated approach to the formulation of the
roadmap would be ensured. This is represented in the house diagram in Figure 2, where the
vision for the basin is supported by activities in a number of key areas, five of which are seen
to be pillars, with a foundation of two crosscutting key areas-the foundation. The
roadmap identified seven key areas of intervention.

2
VISION
The government and community working together
for clean, healthy and productive catchment and rivers,
bringing sustainable benefits to all people of the Citarum River Basin

Management
Main Key of Development
Areas Environmental Disaster
Institution of Water Water Share
Protection Management
(Pillars) and program Resources

Key Supporting
Areas Community Empowerment Data and Information
(Foundation)

Figure 2: Strategic Framework for Roadmap Development

The six Cis or six rivers basin territory comprises of the basins of Citarum, Ciliwung,
Cisadane, Cidanau, Ciujung and Cidurian rivers in West Java, Jakarta and Banten provinces
and includes the metropolitan conurbation of Jabodetabek. Institutional Strengthening for
Integrated Water Resources Management (ISIWRM) in the 6 Cis River Basin Territory (TA
7189) will fund a range of interventions across the water sector that relate to water and land
management and are necessary to pursue the introduction of Integrated Water Resources
Management (IWRM) in the six Cis river basins.

Information sharing is a basic principle of IWRM planning, and data, information, and
decision support are key components to the Roadmap for IWRM in the CRB. This includes
collecting, validating, archiving, managing, and disseminating relevant data covering surface
and groundwater quantity and quality, as well as other natural resource data such as soils,
geology, land cover, and ecosystems, including such socioeconomic data as population,
poverty, and land use. This information can be used to research catchment processes and
demography; developing new technologies for water conservation and environmental
protection; and developing and implementing decision-support tools, including geographic
information systems, hydrologic and hydraulic models, and other analytical tools.

1.3 Decision Support System for IWRM (Package D)

Package D is a part of key area 7 of the roadmap which focuses on data and information. The
objectives of Package D is to develop an effective Decision Support System (DSS) for
IWRM of CRB that can be extended to 6 Cis River Basin Territory in the future and to
strengthen the capacity of water resources engineers for better water quantity and quality
management. The DSS is expected to serve as a standardized framework on which all current
monitoring, modeling, and conservation practices can be integrated and analyzed by the river
basin managers. It is intended that the DSS be suitably comprehensive and will provide
support to all river managers without need for additional tools. Ultimately, the DSS is
envisioned to consist of hydrological and GIS databases; analytical models such as rainfall-
runoff, water allocation and water quality models; and optimized monitoring activities for
acquisition of hydrological and water quality data.
3
The DSS is expected to serve the following functions in the CRB;

a. Operation
s Water Resources Management
Establish short-term water supply plan
Balancing seasonal water demands between users through reservoir and streamflow
management

b. Management
s Hydrological and GIS Data Management
Data collection, archiving, management and validation
Data sharing and dissemination among agencies and stakeholders
s Water Resources Management
Quantify spatial and temporal runoff amounts
Drought contingency planning and water rights analysis
s Water Quality Management
Simulation of steady state water quality (BOD, TN, TP) in stream
Reservoir water quality management
Propose water quality improvement alternatives

c. Planning
s Monitoring, Planning and Evaluation for IWRM in CRB

Various stakeholder agencies responsible for participating in the task of DSS developed have
been grouped into three blocks, with each block being responsible for ensuring complete
compliance with K-water in DSS development, provision of local support, active
participation in capacity building and consultations. The responsible agencies with their
relative DSS components assigned are shown in Figure 3.

4
Figure 3: Scope of Work for Counter Part Agencies

The main tasks during the first phase included 1) data collection & analysis, 2) hydrologic &
GIS database development, 3) rainfall-runoff model development, and 4) institutional
strengthening & capacity building. K-water and its international and domestic consultants
have been in charge of the DSS development in collaboration with Perum Jasa Tirta II (PJT-
II) under supervision of BBWSC and ADB. This report presents the development and results
accomplished during the first phase of Package D. This report describes the details of the
database and RRFS implementation as well as presents recommendations for further
improvement of monitoring networks. The complete details of the information systems
support and capacity-building activities have also been provided. Further, scopes of work are
presented for future phases of the project to ensure continuity and sustainability of project
outputs.

5
2. Data Collection and Monitoring Network Design

Data collection and monitoring network analysis are seen as continuous and iterative
exercises, though most of the available data in the CRB has already been obtained and
compiled within the project. The following sections summarize the results of data collection
and monitoring network design processes.

2.1 Overview of Data Collection

The initial cache of large, consistent usable data was obtained from PJT-II. This data could be
organized into the following data sets: Rainfall, Water Quality, Dam Intake, Release and
Storage, River Flow Measurements, Temperature, and GIS. The second large cache of data
that progresses the modeling effort significantly was the rainfall data obtained from
Component B of the project. The complete data collection summary is shown in Table 1.

Table 1: Data Collection and Source Summary


No Data Agency Data Description
SISDA (Information System of
Water Resources)
- Working Jurisdiction Boundary GIS Database/Layer
- Administrative Boundary GIS Database/Layer
1 PJT-II
- Reservoir, Road, River GIS Database/Layer
- Catchment Area GIS Database/Layer
- Observation Station GIS Database/Layer
- Hydraulic Structures GIS Database/Layer
Hydrology Data, e.g.:
- Rainfall Data for Upper CRB c.a.: 80 stations, up to 2008
2 Package-C
- River Discharge Data 22 stations, up to 2005
- Climatology Data for Upper CRB 4 stations
3 Update of SISDA Data PJT-II Update of SISDA Database
Hydrology & Water Quality Data:
- Rainfall Data for Upper CRB 24 stations, up to 2009/2010
4 - River Discharge Data DPSDA/ BPLHD 22 stations, up to 2009
- Water Quality Data for Upper
10 stations, up to 2009
CRB
Hydrology and GIS Data
5 - Rainfall Data for 6Cis Package-B c.a.: 400 stations, up to 2009/2010
- GIS Data for 6Cis GIS Database/Layer
6 Hydrology and GIS Data BBWSC

6
Significant analysis and re-organization effort was needed to bring this data into a consistent
usable format. There were large gaps in the collected data as well as anomalous
measurements. Details about the analysis required to clean up this data will be discussed in
detail in the following sections.

2.2 GIS Data

PJT-IIs SISDA system has been the primary source of GIS data so far. The data obtained so
far contains more than 80 different layers which can broadly be categorized in the following
fifteen data types: Reservoir Locations; Structures on Tarum Canals; Administrative
Boundaries; Water Resources Infrastructure; Flow Stations; Water Flow Network (rivers,
streams, canals); Digital Elevation Model; Rainfall and Weather Stations; Transport Network
(roads, rails etc.); Water Quality Sampling Locations; Landuse; Irrigation Water Sources for
upper and lower CRB; Sub-catchment Delineation; Soil Type and Geology; Population Data
This data is shown in composite maps in the following sections.

2.2.1 Base Layers


The base layer can be presented in three different maps of Location of CRB, DEM,
Administrative and Transport Network; Landuse; Population.
Figure 4 shows the location of CRB within Java Island, the DEM obtained from USGS
Hydrosheds database, the city district boundaries and the main rail and road network. The
DEM displayed here has been the one utilized for RRFS modeling as discussed in later
sections. The Land cover as obtained from satellite imagery is shown in Figure 5. The
population distribution with respect to village boundaries is shown in Figure 6. While this
map also shows the village boundaries layers, part of the administrative divisions data
obtained, for clarity this layer is not shown in the administrative and location map.

7
Figure 4: Location of CRB in Java Island, DEM, Administrative and Transport
Network

Figure 5: Land Cover in CRB

8
Figure 6: Village Wise Population in CRB

2.2.2 Hydrological Information Layers


The hydrological information is captured in two maps here.
The first map covers location of water reservoirs, stream and canal network and civil works
structures located on that network, and the second map covers sub-catchment delineations,
flow meters, weather, rainfall station, and water quality sampling locations.
The water network map presented in Figure 7 covers the following layer groups: Water
Reservoirs; Stream and Canal Network; Bridges; Culverts and other Structures on the stream;
and canal network. The sub-catchments and hydrological instrument map shown in Figure 8
covers the following layer groups: Sub-catchment Delineation; Flow Meter Locations; Weir
Locations; Weather and Rainfall Station Locations; and Water Quality Sampling Locations.
The data from these maps will be utilized in RRFS and all future modeling.

9
Figure 7: Water Reservoirs, Stream and Canal Network and Stream Network
Structures in CRB

Figure 8: Sub-catchments, Flow Meters, Rainfall and Weather Stations and Water
Quality Sampling Locations in CRB
10
2.2.3 Geological Information Layers
The geological information is presented in five maps of Geology, Soil Water Content;
Lithology, NRCS Soil Classification, and Soil Texture Classification. Figure 9 ~ Figure 13
shows the geology, soil water content for soils less than 200 mm depth, lithology, NRCS soil
classification based on one, and soil texture classification based on one measurement. Most
of the data presented here will be used for future rainfall-runoff modeling.

Figure 9: Geology in CRB

11
Figure 10: Soil Water Content in CRB

Figure 11: Lithology in CRB

12
Figure 12: NRCS Soil Classification

Figure 13: Soil Texture Classification

13
2.3 Hydrological Data Analysis and Monitoring Network Design

2.3.1 Data Analysis


In this project, hydrological (mostly rainfall) data were used for two main purposes: 1) as
data input for Rainfall-Runoff Modeling; 2) as database for developing a Decision Support
System for CRB. For technical applications, a good hydrological measurement network is
essential to obtain high accuracy hydrology data. The location of hydrology station and data
time interval can be managed so that the network data may represent the whole hydrological
cycle in the river basin. The data analysis primarily consisted of analysis of data for usability
in incorporation in modeling and database building activity. The data analysis included
cleaning of data from null and anomalous values, identifying outliers and identifying sections
of data which continuous and congruous for further utilization.

The needs for hydrological data depend on the dominant activities and nature of regional
development. In the highly populated urban area such as DKI Jakarta, hydrology
measurements mainly conducted as part of flood mitigation system, while in the lower of
Jatiluhur, hydrology measurement mainly related to water management for irrigation. In the
past, most hydrological measurements in Indonesia were managed by Central Government
under Department of Public Works. After the policy for local autonomy was implemented,
hydrology measurements were conducted by different agencies with different purposes and
requirements. For Citarum River Basin (CRB), the hydrological measurements were mainly
conducted by BBWSC (Balai Besar Wilayah Sungan Citarum), DPSDA (Dinas
Pengembangan Sumber Daya Air), BMKG (Badan Meteorologi dan Geofisika), and Perum
Jasa Tirta II (PJT-II). In general, the availability and accuracy of hydrology data in Indonesia,
especially in CRB, varies by time and locations. A good and long time series of rainfall data
is needed to obtain a relatively accurate rainfall prediction. However, rainfall data availability
in Indonesia is still far from ideal, for the following reasons:
Number of rainfall stations is not sufficient to cover the rainfall variability in the river
basin,
Number of data available in a rainfall station is not sufficient to construct a long time
series data for more advance analysis (e.g.: data series less than 10 years), and
Many data series contain empty/error values.

The rainfall data obtained from PJT-II consisted of intermittent data between 1980 and 2010
obtained from 153 stations. The second cache of rainfall data was obtained from Component
B. Flow data was obtained from 39 flow stations and the maximum spread of data was from
1989 to 2010. This was supplemented with weir discharge data from 22 weir locations
spreading temporally from 1992 to 2007. Daily release, storage and intake data from
Saguling, Cirata, and Jatiluhur dams was obtained from PJT-II for a time-period from 1991 to
2009. Figure 14 & Figure 15 show the major monitoring locations of rainfall and
flow/discharge in CRB.

14
Figure 14: Rainfall Station Locations in CRB

Figure 15: Flow Monitoring Locations from PJT-II


15
a. Temporal Coverage of Rainfall Data
For the period of 1980-2009, from about 400 rainfall stations in CRB and its nearby area,
only about 150 stations contain of blank data less than 30%. Data availability for the period
of 1991-2000 was slightly higher, but lower for the period of 2001-2009 as shown in Figure
16.

Figure 16: Rainfall Data Availability

16
b. Spatial Coverage of Rainfall Data
After completion of data mapping to sub-watersheds, the rainfall data for each sub-watershed
was calculated. Ideal coverage of a rainfall station in mountainous area is 100-250
km2/station (WMO). Rainfall stations are not uniformly distributed in CRB. Upper CRB (e.g.
Bandung) and Lower CRB (e.g.: Karawang) have relatively sufficient number of stations,
while other areas (e.g.: Cianjur, Sumedang) seem to have only few number of stations with a
long series of data.

Figure 17: Spatial Coverage of Rainfall Data

17
c. Gap Analysis of Rainfall Data
For the period of 1980-2009, about 150 stations contain blank data less than 30%. To ensure
data quality as input for RRFS modeling, filling of empty data was conducted for stations
with small number of blank data:

For high coverage area: stations with data availability > 60% for the period of 1980-
2009 (30 years)
For low coverage area: stations with data availability > 60% for the period of 1991-
2000 (10 years) or 2001-2009 (9 years)
Data of one rainfall station which collected from different sources/agencies can be
merged into one data series

According to Box-Plot analysis of the rainfall data, fifteen out of the thirty years the ninetieth
percentile annual accumulated rainfall falls below 4000 mm. For all of the years the ninetieth
percentile is below 5000 mm. This amounts to a maximum average rainfall of less than 14
mm per day (90th percentile). The minimum rainfall instances exceeded 1000 mm for only
two out of the thirty years. The median rainfall for all years was between 1000 to 3000 mm.
No significant pattern of dry or comparatively wetter periods emerges indicating that spread
of rainfall over the last three decades has generally been fairly uniform. This result was also
confirmed by the Cluster Analysis conducted in this study.

d. Discharge Data
Discharge data at the three dams of Saguling, Jatiluhur, and Citaram from 1991 to 2007 are
shown in Figure 18. This date range was chosen for analysis of correlation between rainfall
data and observed flow data at the dams. The analysis demonstrated enough correlation
rendering further rainfall-runoff modeling, a promising prospect. Although the data of the
three dams were quite complete, many data from other locations were discontinuous and
contained null entries and zero entries which were indistinguishable. Further analysis was
performed on this data to identify usable segments. After a series of significant analysis, the
data was sorted and sectioned for inclusion in the database.

18
(a) Saguling

(b) Cirata

(c) Juanda
Figure 18: Observed Discharge Data at (a) Saguling, (b) Cirata, and (c) Juanda.

19
2.3.2 Monitoring Network Design
The first process in data analysis consisted of delineating the sub-catchments on the basis of
DEM. This is essential because DEM based placement of both, the rainfall stations and the
river flow gauges are crucial to collecting data sets adequate for rainfall-runoff modeling.
Similarly, the stream network for major flow paths affected by the topography of the area
needs to be identified.

a. Sub-catchment Delineation and Stream Network Identification


To delineate the sub-catchment and to identify the flow pattern from topography as obtained
from USGS SRTM-90 Digital Elevation Maps (DEMs), the six-step process as described
below and explained in Figure 19 was used. The ArcHydro modules for ArcGIS developed
at University of Texas were used for the following processing.

The DEM is obtained from USGS Hydrosheds and cropped to the CRB boundary.
Using DEM, the flow direction for each discrete cell is identified.
Using DEM, the stream network is defined, etched, and segmented.
The flow direction is implemented upon stream network to obtain stream
segmentation with drainage line.
Sub-catchment grid is delineated using stream segmented with drainage line and flow
direction map. At this stage, the resolution of the sub-catchment delineation and
stream network identification can be defined. The greater the resolution at which sub-
catchments are delineated, the more the no. of sub-catchments there would be in the
basin. For the purposes of this application, sub-catchment was delineated at three
different resolutions as shown in Figure 20.
The stream network is vectorized.

At this point, the sub-catchment delineation being utilized does not take into account
topographical information. The basin is divided into 48 sub-catchments. To improve further
the monitoring network, a schematic based on sub-catchment delineation b) from Figure 20
will be utilized. This delineation divides the basin into 109 sub-catchments based on DEM. It
is suggested that in the future, this delineation may be utilized for further refined modeling
and monitoring network optimization. The sub-catchment delineation and stream network so
identified takes into account the topography of the CRB.

20
Figure 19: Stream Network Identification

a) No. of sub-catchments=39 b) No. of sub-catchments=109 c) No. of sub-catchments=1163

Figure 20: DEM Based Sub-catchment Delineation at Different Resolutions

b. Rainfall Monitoring Network Design


According to WMO guidelines (Guide to Hydrological Practices, 2008), recommended
minimum densities for rainfall stations is as shown in Table 2. Non-recording gauges are for
obtaining daily data. In addition to daily depth of rainfall, the state of the weather is to be
measured at each standard rainfall station. Recording gauges are for obtaining rainfall data in
the order of minutes to hours. In developing networks, it is suggested to have at least 10% of
gauges as recording gauges, to be placed in areas subject to intense, short-duration rainfalls,
and in urban areas where the time resolution needed for rainfall measurements is of the order
minutes to hours.

21
Table 2: Recommended Minimum Densities for Rainfall Stations

Area in km2 per rainfall station


Physiographic Unit
Non-Recording Recording

Coastal 900 9 000


Mountains 250 2 500
Interior 575 5 750
Hilly/undulating 575 5 750
Small Island 25 250
Urban Area - 10-20
Polar/arid 10 000 100 000

The selected rainfall stations in CRB being utilized for modeling, together with topography
and demographical conditions, are shown in Figure 21 and Figure 22. As can be seen, 23 out
of the 48 sub-catchments require at least one additional non-recording station while two sub-
catchments require additional recording stations. Based on rainfall data availability,
topography and demographic conditions in CRB, the proposed number of rainfall stations is
shown in Table 3.

Rainfall station placement followed a simple algorithm based on the above analysis.
Based on the deficiencies identified in Table 3, additional rainfall stations were placed
in the appropriate sub-catchment.
While placing the rainfall stations, if a sub-catchment covered multiple sub-
catchments as identified in Figure 20 (b), then the rainfall station was placed in a sub-
catchment where there were minimum no. of rainfall stations. So for instance if sub-
catchment C8 (requiring 1 additional rainfall meter) covered sub-catchment 2, 3, and 4
from Figure 20 (b) and both sub-catchments 3 and 4 have one rainfall station each
already, then the additional rainfall station should be placed within sub-catchment 2.
In the second round, a rainfall station was placed in each of the 109 sub-catchments
from Figure 20 (b) which did not already have a rainfall station.

The suggested rainfall station locations based on the above algorithm are shown in Figure 23.
A total of 49 additional rainfall station locations were suggested. The latitude and longitude
for the location are shown in Table 4.

22
Figure 21: The Selected Rainfall Stations in CRB on DEM

Figure 22: The Selected Rainfall Stations in CRB against Population Density

23
Table 3: Rainfall Station Location Suggestion for Monitoring Optimization1
Numbe r of Rainfall Stations
Ge ne ral Condition
Sub-Catchme nt Are a (km2) Non Re cording Re cording
Topography De mography Navailable Nminimum Nadd Navailable
C1 1348.5 Mountainous Urban 13 6 - 2
C2 1009.3 Mountainous Urban 8 5 - -
C3 916.9 Mountainous Rural 1 4 3 -
C4 850.0 Mountainous Rural 1 4 3 -
C5 491.0 Mountainous Rural 2 2 - -
C6 72.9 Mountainous Rural 1 1 - -
C7 244.8 Mountainous Rural 2 1 - -
C8 155.7 Flat Rural 0 1 1 -
C9 244.3 Mountainous Rural 0 1 1 -
C10 224.0 Mountainous Rural 0 1 1 -
C11 55.6 Flat Rural 0 1 1 -
C12 289.2 Mountainous Rural 0 2 2 -
C13 110.2 Flat Rural 1 1 - -
C14 559.2 Flat Rural 11 1 - -
I1 82.2 Flat Rural 0 1 1 -
I2 246.8 Mountainous Rural 3 1 - -
I3 125.2 Flat Rural 0 1 1 -
I4 464.4 Flat Urban 2 1 - -
I5 420.8 Mountainous Rural 1 2 1 -
I6 111.8 Flat Urban 1 1 - -
I7 96.1 Flat Urban 0 1 1 -
I8 174.3 Flat Urban 1 1 - -
I9 134.2 Flat Rural 0 1 1 -
I10 371.3 Mountainous Rural 10 2 - -
I11 70.6 Flat Urban 1 1 - 1
J1 217.4 Flat Rural 0 1 1 -
J2 75.5 Flat Rural 2 1 - -
J3 192.0 Flat Rural 1 1 - -
J4 70.5 Flat Rural 1 1 - -
J5 942.7 Mountainous Rural 3 4 1 -
J6 220.2 Flat Rural 1 1 - -
J7 116.1 Flat Rural 0 1 1 -
J8 74.0 Flat Rural 0 1 1 -
J9 147.8 Flat Rural 0 1 1 -
J10 213.5 Flat Rural 1 1 - -
J11 119.3 Flat Rural 0 1 1 -
J12 164.4 Flat Rural 0 1 1 -
J13 132.1 Flat Rural 0 1 1 -
J14 317.3 Mountainous Rural 3 2 - -
J15 230.8 Mountainous Rural 1 1 - -
J16 103.4 Mountainous Rural 3 1 - -
J17 98.8 Flat Rural 0 1 1 -
J18 30.0 Flat Rural 0 1 1 -
J19 358.1 Flat Rural 7 1 - -
J20 264.5 Flat Rural 1 1 - -
J21 146.8 Flat Rural 2 1 - -
J22 194.6 Flat Rural 7 1 - -
J23 68.8 Flat Rural 7 1 - -
J24 231.3 Flat Rural 0 1 1 -

1
Notes:
Navailable : Number of rainfall station with sufficient number of data
Nminimum : Minimum number of rainfall station based on WMO standard
Nadd : Proposed number of additional rainfall station

24
Table 4: Suggested Rainfall Station Locations
Suggested Suggested
Latitude Longitude Latitude Longitude
Rainfall Station ID Rainfall Station ID
1 107.1979 -7.06206 26 107.8204 -6.46108
2 107.2243 -6.9451 27 107.8635 -6.39598
3 107.0749 -6.87309 28 107.8231 -6.19754
4 107.2086 -6.85603 29 107.6528 -6.47578
5 107.2247 -6.87202 30 107.6944 -6.28772
6 107.2906 -6.75532 31 107.5661 -6.47181
7 107.2962 -6.73666 32 107.4571 -6.41535
8 107.2896 -6.73161 33 107.5378 -6.42338
9 107.2815 -6.73402 34 107.2513 -6.00462
10 107.2708 -6.45745 35 107.5519 -6.94526
11 107.1097 -6.6054 36 107.5712 -6.98131
12 107.1857 -6.52207 37 107.6119 -6.98712
13 107.193 -6.4375 38 107.7098 -6.98903
14 107.1093 -6.50012 39 107.6943 -6.97135
15 107.1657 -6.40618 40 107.4144 -6.89651
16 107.1085 -6.42086 41 107.1199 -6.66287
17 107.0093 -6.31754 42 107.358 -6.51242
18 106.954 -6.55067 43 107.3607 -6.57585
19 106.8876 -6.54932 44 108.0446 -6.3447
20 106.8383 -6.53665 45 107.4432 -6.15364
21 106.947 -6.41416 46 107.3771 -6.04814
22 106.9503 -6.13196 47 107.0896 -6.11151
23 106.9006 -6.14873 48 107.0439 -6.08123
24 108.0369 -6.53474 49 106.8928 -6.39783
25 107.9119 -6.50979

25
Figure 23: Suggested Rainfall Station Locations

c. River Flow Monitoring Network Design


According to Government of Western Australia guidelines, surface water monitoring sites
should be used to determine the sites water balance including its inflow and outflow,
detention or retention of storage, and flows to or from water-dependent environments
(WDEs). This is particularly important in catchments where significant changes in flow
volumes, nutrients, and any contaminants could be expected post-development and which
would need to be managed. The proponent needs to collect sufficient data to demonstrate, as
part of the required water management documents, that the pre-development hydrologic,
hydrogeologic, and ecological characteristics of the downstream catchment and receiving
environment can be protected and maintained.

Correct site selection is critical to obtaining accurate flow data. The primary criterion is a site
where a consistent relationship between water level and flow rate is known or can be
established. This usually requires a site, which has low flow-velocity at the level recorder and
an increase in water gradient downstream of the measurement site. A site will not be
appropriate if it is;

Affected by backwater conditions from obstructions, debris, or sediment from


hundreds of meters downstream
In drains with minimal gradient (longitudinal slopes)
In tidally affected waterways
Where pumping occurs and pumping records are not available
26
All sites will need a means of converting water height to flow via rating curve development
or by using total flow and velocity loggers. The accuracy of the flow data can be improved by
manual discharge measurements (gauging) over a range of flow rates. Loggers should be set
to record water levels at five-minute intervals to ensure that peak water levels are recorded in
flash storm events. Data from data-loggers should be downloaded with a frequency that
coincides with the frequency of manual monitoring in the area. Site selection should take into
consideration, the following;

A site at the lower side or outlet of the catchment, and/or sites where flow leaves the
study area
At least one site where any significant flow enters the study area
Sites near the lower side of any sub-catchments (i.e. immediately upstream of a
waterway confluence or a wetland)
Sites should be in flowing water and not backwater affected from downstream
Sites should be unaffected by local inflows (i.e. drains/pipes discharging immediately
upstream)
Sites should have a uniform cross- and long-section, a weir structure, and rated gauge
board to enable calculation of instantaneous flows.

On the whole, the method generally practiced for stage gauge location is to locate one flow
meter at the outlet of each sub-catchment. The network density and data collection resolution
is increased by delineating sub-catchments at a finer level and by locating stage gauges at the
appropriate sites for the smaller sub-catchments. The following simple algorithm was
followed to identify locations for placing new stage gauges.

Install a stage gauge at the drainage outlet of each sub-catchment from Figure 20 (b).
If there is an existing stage gauge at the location, there is no need to install additional
stage gauge.

Based on the above methodology, the stage gauging station locations are shown in Figure 24.
A total of 103 new flow station locations are suggested. The coordinates for the locations are
given in Table 5.

27
Figure 24: Suggested Flow Station Locations

Table 5: Suggested Flow Station Locations


Suggested Suggested
Flow Station Latitude Longitude Flow Station Latitude Longitude
Number Number
1 107.7251 -6.98954 53 107.5269 -6.42864
2 107.7355 -7.02319 54 107.3897 -6.54421
3 107.7297 -7.02056 55 107.3804 -6.54283
4 107.6187 -6.99384 56 107.3668 -6.53861
5 107.5505 -6.98677 57 107.2223 -6.46289
6 107.6013 -6.98094 58 107.1471 -6.56173
7 107.6117 -6.97566 59 107.1402 -6.43826
8 107.6096 -6.98154 60 107.1316 -6.43116
9 107.4082 -6.92489 61 106.9077 -6.49059
10 107.1975 -7.01317 62 106.897 -6.48634
11 107.1933 -7.02711 63 106.8279 -6.13031
12 107.2114 -6.88676 64 106.9672 -6.30363
13 107.2034 -6.88359 65 106.9219 -6.18123
14 107.1813 -6.8521 66 106.9305 -6.18655
15 107.1856 -6.86011 67 106.9337 -6.17958

28
16 107.2294 -6.84117 68 106.9403 -6.10245
17 107.2359 -6.84382 69 106.9623 -6.10237
18 107.4049 -6.91527 70 107.0629 -6.12019
19 107.4418 -6.90277 71 107.0237 -6.07697
20 107.3155 -6.81775 72 107.0698 -6.11481
21 107.4364 -6.89637 73 107.1058 -6.1484
22 107.3252 -6.8161 74 107.1143 -6.13927
23 107.5353 -6.94457 75 107.0851 -6.18971
24 107.5395 -6.93277 76 107.0926 -6.1929
25 107.7155 -6.9912 77 107.157 -6.23119
26 107.7085 -6.98589 78 107.1645 -6.23383
27 107.7137 -6.96819 79 107.2653 -6.28059
28 107.7063 -6.98055 80 107.2725 -6.28015
29 107.6292 -6.98901 81 107.5223 -6.42353
30 107.7062 -6.96503 82 107.7045 -6.3363
31 107.2783 -6.76064 83 107.711 -6.34951
32 107.2843 -6.77132 84 107.7226 -6.34744
33 107.282 -6.74028 85 107.8326 -6.28826
34 107.2755 -6.72907 86 107.8418 -6.287
35 107.1479 -6.57439 87 107.9118 -6.25371
36 107.1388 -6.57335 88 107.8226 -6.22289
37 107.3065 -6.72357 89 107.816 -6.19042
38 107.305 -6.73429 90 107.7034 -6.23456
39 107.2948 -6.73005 91 107.6505 -6.24927
40 107.2985 -6.71986 92 107.6027 -6.19439
41 107.7915 -6.70125 93 107.4891 -6.16067
42 107.7979 -6.70389 94 107.4367 -6.17055
43 107.9136 -6.54269 95 107.4255 -6.1706
44 108.0815 -6.34962 96 107.4612 -6.14367
45 108.0447 -6.36589 97 107.4419 -6.12075
46 108.0362 -6.36487 98 107.3955 -6.0337
47 108.0546 -6.3241 99 107.3434 -5.98146
48 107.9061 -6.53952 100 107.2444 -5.97331
49 107.8974 -6.49017 101 107.2847 -6.25046
50 107.9088 -6.47941 102 107.2745 -6.24515
51 107.7348 -6.50321 103 107.0187 -5.93992
52 107.7234 -6.50256

29
d. Suggestion for Improving Monitoring Stations

1. Rainfall Measurement
In addition to the standard rain gauges from which daily precipitation data is recorded, data
must be built of at most fifteen-minute time series to conduct appropriate rainfall-runoff
modeling for storm events. This would require installation of automated weather observing
systems to record precipitation data at a higher temporal resolution as the rain event is
happening. According to World Meteorological Organization Training Material on
Automated Weather Observing Systems, It has become a necessity to obtain more reliable
and continuous meteorological data and transfer these data in due course to those who are
concerned Atmosphere is alive and it has to be observed continuously by recording all
significant changes and phenomena. This can be possible by using AWOS only. It is
impossible to make continuous observations by using un-automated systems.

There are two primary types of automated systems in current general use. The automated
Weather Observing System (AWOS) generally report data at 20-minute intervals and are not
sensitive enough to document rapidly changing weather conditions. Automated Surface
Observing System (ASOS) are the mostly widely used in USA and developed countries and
are capable of documenting rapidly changing weather conditions. While the development of a
comprehensive ASOS system should be undertaken by developing nations in the long terms,
at present the installation of such a system would be cost prohibitive. The transition should
start with installation of AWOS towards gradual replacement of manual rainfall metering
systems.

2. Flow Measurement
Hydrostatic pressure level sensors are submersible sensors used for measuring the level of
liquids (including corrosive liquids) in deep tanks or water in reservoirs. Pressure water level
loggers provide accuracy and reliability across a wide range of applications. Non-contact
ultrasonic level sensors emit ultrasonic (20 kHz to 200 kHz) acoustic waves from a
transducer which also detects and measures the reflected waves. This type of sensor is ideal
for measuring bulk solids such as sand, cement, grain, rice, and plastic pellets as well as
liquids with high viscosity such as slurries, heavy oil, grease, and latex. Often called RF due
to the radio frequency signals that are applied to the capacitance circuits, Capacitance Level
Sensors are excellent for measuring a wide range of liquids, slurries, and solids. Capacitance
Level Sensors can be used to measure media with dielectric constants between 1.1 and 90.
Capacitance level sensors are rugged, contain no moving parts, are easy to clean and simple
to use. Also known as microwave level sensors, radar level sensors are ideal for use in
environments where temperature varies and in moist, dusty, or vaporous environments. The
microwaves are able to penetrate temperature and vapor layers that can be problematic for
other types of water level sensor. Objects with high dielectric constants such as metal and
conductive water will reflect microwaves. Conversely, media with low dielectric constants
(glass, plastics, foodstuffs, paper) will absorb the microwaves by varying degrees. Radar
water level sensors are ideal for use in a vacuum as the microwaves are electromagnetic
energy and don't require air molecules to propagate.

30
2.4 Water Quality Data Analysis and Monitoring Network Design

2.4.1 Data Analysis


The information of current monitoring stations in the CRB is shown in Figure 25. In the
upper stream of the Saguling reservoir, 10 monitoring stations are in the mainstream of CRB
and 7 stations are located in the entrance of tributaries. Water quality data was obtained
exclusively from the database of PJT-II. The data spanned twenty-seven (27) years from 1993
to 2010. While in some years data was available from as many as 78 stations, in most of the
years data was obtained from 41 stations. Initially, the data consisted of 29 parameters, up
until the year 1998; from 1999 onwards the water samples were analyzed for only 16
parameters. The water quality parameters monitored by each agency in CRB is summarized
in Table 6.

Figure 25: Current Water Quality Monitoring Stations

31
Table 6: Monitored Water Quality Parameters from each Agency.
Parameters PusAir / BPLHD PJT-II
Temperature O O
Dissolved solids O O
PHYSICAL
SS O
Turbidity O
Ammonium O O
Iron O O
Boron O
Detergent O
Phenol O
Fluoride O
Total phosphate O
Cadmium O
Chloride O
BOD O O
COD O O
Chromium VI O
Manganese O O
Oil-grease O
Nickel O
Nitrate O O
Nitrite O O
CHEMICAL
DO O O
pH O O
SAR O
Zinc O O
Sulfate O O
Copper O
Lead O
Mercury O
Arsenic O
Cobalt O
Barium O
Cyanide O
Chloride O O
Sulfide O O
Selenium O
Fecal coliforms O
Total coliforms O

32
High concentration of BOD and algal bloom cause low concentration of dissolved oxygen
and negative effects on fish farming. Algal bloom is one of the most important processes in
the aquatic ecosystem and BOD - DO relationship is not sufficient to explain fate of DO in
the reservoir. In the Citarum River Basin, chlorophyll-a data is not measured and current data
is not sufficient to explain algal bloom process and its impact on water body of the reservoirs.

For preliminary data analysis, 5 stations of the Citarum River Basin were chosen such as
Nanjung, outlet of Saguling, Cirata, and Jatiluhur, and Curug weir and those data from 2005
to 2009. The results of DO, BOD, and COD at the inlet of the Saguling reservoir, Nanjung,
which corresponds to the downstream of Bandung city and three sequential reservoirs
(Saguling, Cirata, and Jatiluhur) including the Curug Weir are shown in Figure 26. Generally,
the variation of DO, BOD, and COD at the Nanjung station is greater than other ones and it
tends to decrease in downstream reservoirs. Most data exceeded the limitation by PP 82/2001
class 1 and 2, which are usable for recreational, gardening agricultural, farming, and any
other use with the similar requirements.

In Figure 27, variations of ammonia, nitrite, and nitrate was displayed and it shows a
tendency to improve water quality toward downstream. Nutrient data such as ammonia,
nitrite, and nitrate required for ecological modeling are very limited. It is necessary to
increase the number of sampling parameters and frequencies required for modeling of algae
growth. In Figure 28, it reveals that the correlation coefficient between BOD and COD is
above 0.9 which requires additional analysis to identify whether it is due to watershed
characteristics or other factors such as data sampling and analysis methodologies.

33
10
Nanjung Saguling Cirata Jatiluhur Curug
8
DO (mg/L)
6

0
J-05 J-05 J-06 J-06 J-07 J-07 J-08 J-08 J-09 J-09
Time in Days

50
Nanjung Saguling Cirata Jatiluhur Curug
40
BOD (mg/L)

30

20

10

0
J-05 J-05 J-06 J-06 J-07 J-07 J-08 J-08 J-09 J-09
Time in Days

100
Nanjung Saguling Cirata Jatiluhur Curug
80
COD (mg/L)

60

40

20

0
J-05 J-05 J-06 J-06 J-07 J-07 J-08 J-08 J-09 J-09
Time in Days

Figure 26: Monthly Variation of DO, BOD, and COD

34
5
Nanjung Saguling Cirata Jatiluhur Curug

4
NH3 -N (mg/L)
3

0
J-05 J-05 J-06 J-06 J-07 J-07 J-08 J-08 J-09 J-09
Time in Days

1.0
Nanjung Saguling Cirata Jatiluhur Curug
0.8
NO 2-N (mg/L)

0.6

0.4

0.2

0.0
J-05 J-05 J-06 J-06 J-07 J-07 J-08 J-08 J-09 J-09
Time in Days

5
Nanjung Saguling Cirata Jatiluhur Curug
4
NO3-N (mg/L)

0
J-05 J-05 J-06 J-06 J-07 J-07 J-08 J-08 J-09 J-09
Time in Days

Figure 27: Variation of NH3-N, NO2-N, and NO3-N

35
50 100
Nanjung y = 2.69 x - 1.28(R2 = 0.99) Nanjung
Saguling 90
Cirata
40 Jatiluhur 80
Curug
70
y = 2.69 x - 1.28
COD (mg/L)

COD (mg/L)
30 60
R2 = 0.99
y = 2.18 x + 1.38(R2 = 0.97) 50
y = 2.34 x + 0.39(R2 = 0.92)
20 40
y = 2.5 x + 0.1(R2 = 1.00)
30

10 20
y = 2.34 x + 0.40(R2 = 0.92)
10

0 0
0 5 10 15 20 0 5 10 15 20 25 30 35 40
BOD (mg/L) BOD (mg/L)

50 50
Saguling Cirata

40 40
COD (mg/L)

COD (mg/L)

30 30
y = 2.18 x + 1.38 y = 2.34 x + 0.39
R2 = 0.97 R2 = 0.92
20 20

10 10

0 0
0 5 10 15 20 0 5 10 15 20
BOD (mg/L) BOD (mg/L)

50 50
Jatiluhur Curug

40 40
COD (mg/L)

COD (mg/L)

30 30
y = 2.34 x + 0.40
R2 = 0.92
20 20
y = 2.5 x + 0.1
R2 = 1.00

10 10

0 0
0 5 10 15 20 0 5 10 15 20
BOD (mg/L) BOD (mg/L)

Figure 28: Correlation Coefficients of BOD and COD

36
2.4.2 Design of Water Quality Monitoring Network
The objectives of water quality monitoring are as follows;
Characterizing water resources
Identifying water quality problems and trends
Developing water quality management priorities and plans
Developing and implementing water quality management programs
Evaluating the effectiveness of management actions

To achieve these objectives, it is necessary to determine adequate monitoring location and


frequency. In the Citarum River mainstream, watershed boundary is defined distinctly only
in the restricted area between the most upstream and the Curugn Weir. Therefore, in this
study, the restricted stations are considered. The watershed areas, their relative contribution
for the major water quality monitoring sites in the mainstreams of CRB are summarized in
Table 7. In Figure 29, it shows watershed areas multiplied by average BOD values from 2005
to 2009 for the monitoring stations presented in Table 7. The results indicate that the area-
weighted BOD values changed drastically.

Table 7: Major Water Quality Monitoring Sites of the Citarum River Mainstream
Monitoring Station Watershed Area(km2) Watershed Area (%)

Margahayu 1,438.2 29.3%


Nanjung 1,754.8 35.8%
Batujajar 1,808.5 36.9%
Inlet Saguling 1,808.5 36.9%
Outlet Saguling 2,300.9 46.9%
Inlet Cirata 2,414.4 49.2%
Outlet Cirata 4,148.1 84.6%
Inlet Jatiluhur 4,292.0 87.5%
Outlet Jatiluhur 4,620.3 94.2%
Bendung Curug 4,906.1 100.0%

37
10

Average Conc. of BOD Watershed Area(%)


8

0
Majalaya

Margahayu

Batujajar

Inlet Jatiluhur

Outlet Jatiluhur
Sapan

Nanjung

Inlet Saguling

Outlet Saguling

Inlet Cirata

Outlet Cirata

Bendung Curug
Wangisagara

Figure 29: Watershed Area Weighted BOD Concentration of the Major Sites

Currently, the number of monitoring stations of West Tarum Canal is sufficient to capture
waste load changes in each watershed and tributary. However, due to most pollutant sources
from human related activities, additional water quality monitoring stations need to be
installed in other major tributaries and main reservoirs to cover the information on loading
upstream and downstream of the urbanized areas. Then, enough information of the water
quality changes between major tributaries and mainstream should be collected through the
installed water quality monitoring stations in CRB. Suggested additional water quality
monitoring stations are shown in Figure 30.

The details of the reasons for additional monitoring stations are explained. Due to radical
changes of BOD concentration by the weighted watershed area between Majalay and Sapan,
four additional stations (Cirasea, Cipamokolan, Cicadas, and Ciwidey) need to be installed in
the upstream of Sapan and Margahayu as shown in Figure 31 for proper monitoring this area.
Between Cirata and Jatiluhur reservoir, three more stations (Cisokan, Cimeta, and Cikundul)
need to be installed to monitor the changes of waste load, and in the Saguling and Cirata
reservoir additional four monitoring stations need to be installed respectively (Figure 32). In
East Tarum Canal, there are five monitoring stations, 19 additional stations (7 major
tributaries of Ciherang, Cilamaya, Cijeongol, Ciasem, Cigaung, Ciborosole, and Cipunagara
and major points of the East Tarum Canal) need to be added for proper water quality
monitoring as shown in Figure 33.

38
Figure 30: Suggested Water Quality Monitoring Stations

Figure 31: Suggested Water Quality Monitoring Stations (Upstream of Inlet Saguling)

39
Figure 32: Suggested Water Quality Monitoring Stations (Saguling, Cirata and
Jatiluhur Reservoir)

Figure 33: Suggested Water Quality Monitoring Stations (East Tarum Canal)

40
3. Development of DB and GIS Database

3.1 Introduction

The main objective for development of GIS and hydrological database is to build a central
repository of all hydrological, metrological and spatial data for archiving, analyzing, and
sharing data and for supporting the DSS. Currently there are many in-house databases
developed by stakeholder organizations in CRB. However there is no central database which
could be used to extract and update information by all organizations. An integrated and
centralized database is needed to ensure the reliability of data as well as the smooth flow of
information amongst agencies for effective river basin management. Therefore, data would
be made easily accessible and retrievable for various different classes of users from experts to
technicians. The purpose and goal of development of the integrated database is described in
Figure 34.

Figure 34: The Purpose of Integrated Database Development

The DSS database was constructed with collection of data (hydrological and spatial data) and
data management tool so called DSS Data Manager which was developed considering user
requirements. The DSS database is all integrated and communicated directly with one another
as follows:

GIS-Database: to serve as a central database for data sharing throughout the whole
basin;
Hydrological Database: to store rainfall, water level, flow, ground water level, and
water quality;
DSS Data Manager: to manage hydrological & GIS data stored in database and share
data between every agency which is managing Citarum River Basin;

41
The main function of hydrological and GIS database is shown below:

Data archiving, analysis, validation, management and support of DSS modules


Providing user interface, data analysis tools, and reports for the database
Data sharing and dissemination among the related agencies
Review the quality of information for removing any gaps
Spatial presentation of the hydrological data and meta-data

The GIS based integrated database interacts with data management system and the users
through a convenient Graphic User Interface. A hydrological database was tagged on the
spatial database to construct the integrated DSS database as shown in Figure 35.

Figure 35: Configuration Hydrological and GIS Database System

3.2 Database System Development Process for DSS

Like any other software development, there are four stages in database development as shown
in Figure 36. The first phase is reviewing the status of existing system such as database,
software, and data management tools running on the stakeholders machines. Investigation
and evaluation for existing system are important to design the target database and DSS, and
needed to make a conceptual diagram of the running system. To develop a user friendly and
sophisticated database, the software development team gathered requirements from
stakeholders and made out a User Requirement Specification (URS) document as a main
reference not only in designing use case diagrams to plan users behaviors in the software,
but also in designing database structures.

42
Figure 36: Development Process

The second phase is crucial designing database, because the design itself ensures that the
developed database needs to be fulfilled users needs and requirements. Main activities in this
phase are designing the system architecture, user screens using the Use Case Diagram and
data storage by using Entity Relationship Diagrams (ERD).

The third phase is implementing the design of the database. In this phase, the developed
design must be converted into a machine-readable format and after this process, the coding
process or the code generation process is performed. Generally, coding processes is divided
into 3 major modules: Graphical User Interface (GUI) development module as a
communication interface between user and machine, Database Manipulation (insert, update,
delete, etc.) module, and the Service module. The Service module provides interconnectivity
between Server Application and Client Application that exist as server services on server
machine. Server Application shall respond to all client applications requests using this
service. Therefore, this service is the main core in data storage, data searching, and data
manipulation activities and includes data importer and data exporter modules.

The last phase is testing database. If the database is ready for testing, it starts debugging
database. After that, the database will be applied and database developer team starts to figure
out any exceptions or errors including not only syntax errors that must be fixed but also
algorithmic errors. If an error is identified, then re-coding or fixing has to be done. Final
activities in this phase are creating user manual/documentation and delivering developed
database to stakeholders including training users how to implement developed database.
43
3.3 Hydrological Database

The objective of hydrological database development is building the hydrological data storage
system for archiving data such as rainfall, water level, discharge, water quality. All of the
acquired hydrological data from previous data collection activities are integrated into
hydrological database. After gathered from different agencies, all the data were thoroughly
investigated for accuracy, duplication, and usability following the process shown in Figure 37.
Those classified as usable data were used for constructing the integrated database. The
process for data integration and classifying available data is as follows:

Check data duplication from the gathered data schema


Investigate common data code such as basin, gauge station, and facilities by the code
comparison table such as the national guidelines for river stretches and hydro-stations
codification available in DGWR-WRM
Classify the data table by the attribute information
Check available data at the same data table
Select available data to integrate hydrological database
Metadata

Figure 37: Identification of Data for Hydrological Database Development

Basically hydrological database contain time-series data such as rainfall, water level, stream
flow, and so on. The range of database construction has been determined by considering the
data quality and availability on the DSS in Citarum River Basin. Through discussions with
each agency, the detailed ranges to be covered by hydrological database have been
determined as shown in Table 8.

44
Table 8: Hydrological Database Layers
Related
Section Contents
Agencies
Station Name, Location (Longitude, Latitude)
Gauge Station Recording Type
All
Information Recording Period and Frequency, Competent Authority
Management History
Station Name
BBWSC
Real Time Data
Rainfall DPSDA
Daily, Monthly, Yearly data
PusAir
Annual Summary Table Data
Station Name
BBWSC
Real Time Data
Water Level PJT-II
Discharge
PusAir
Daily, Monthly, Yearly data
Station List & Specification
Real Time Data
Meteorological BMKG
Daily, Monthly, Yearly data
data PJT-II
Rainfall, Temperature, Air pressure, Wind Direction &
Velocity.
Dam List & Specification
Dam Operation Information (Storage Level, Inflow,
Dam & Reservoir Outflow) PJT-II
Level-Storage Relationship
Power Generation Information
Domestic Demand
Water Demand Agricultural Demand PJT-II
Industrial Demand
Station List & Specification PJT-II
Water Quality Parameter (BOD, COD, TN, TP, ) PusAir
Water Quality
Pollutant Information BPLHD
Treatment Facility Information DPSDA

3.3.1 Status of Existing Data Storage System


Many data storage systems, analysis models and decision support systems have been
developed through several projects in the past. However currently, there is scarcely available
system for water management organization such as River Basin Organizations (RBO) in CRB,
because handover of the database and modeling systems from the project consultants to the
RBO has not been successful. Thus, those existing database systems are too complicated to
be successfully adopted for river basin management. The stakeholders interest now lies in an
effective database that is user-friendly and actually can be applied and shared amongst all
stakeholder agencies.

45
a. Existing Data Storage System in PJT-II
In early 2001, PJT-II began developing their own database system, collaborating with other
institutions, specifically with Balai Agroklimat and Hidrologi (Baliklimat), part of the
Ministry of Agriculture. In 2006, the system became operational, which is called SISDA-
PJT-II (Sistem Informasi Sumber Daya Air-PJT-II). Since 2008, PJT-II has been expanding
the database system to include the irrigation areas with the collaboration of Baliklimat.
Recently, PJT-II is working on developing the new version of SISDA with an upgraded
database and GUI in Figure 38 and integrated with hydrological database including spatial
presentation of data and meta-data.

SISDA database has 59 data tables including rainfall, water level, meteorological data, water
supply intake for Jakarta, reservoir, water quality and electricity generation data. The data is
accessible through a GIS based GUI. Mainly daily rainfall, river and weir discharge,
meteorological data and water supply data are available, while hourly and minutely data are
also stored, the records are sporadic, limited and not normally utilized for any predictive
modeling. Also reservoir data including Jatiluhur, Cirata and Saguling reservoirs are provided
daily and only monthly water quality data is available.

Figure 38: Water Information System (SISDA) Developed by PJT-II

46
b. Existing Data Storage System in PusAir
PusAir has a number of departments deals with databases and currently utilizes only two
main databases (hydrological and water quality database) in water resources management in
CRB.

Hydrological data is maintained by Experimental Station Hydrology and Water Management


department of which head is Mr. Ilfan Sudono. The Experimental Station Hydrology and
Water Management have two data processing software (HITA 1.1 and NEO-PERDAS).
HITA 1.1 converts time series graph from magnetic recording papers into digital data and
NEO-PERDAS has a function to convert river water level into river discharge. At present,
PusAir is developing a new database and data information system. For the new database
system, firstly the processed data and collected data from DPSDA, BBWSC and PJT-II are
transformed to CSV file format, stored in My-SQL database operated on a Linux server. The
information in My-SQL database is provided by users in PusAir through the web GIS based
hydrological information in-house system. This information system is accessible only to local
users in PusAir, which means PJT-II, DPSDA and BBWSC etc. located in and outside PusAir
cannot access the My-SQL database and hydrological information system in PusAir. A
screenshot of the hydrology information system with PusAir is shown in Figure 39.

Figure 39: Hydrology Information System Developed by PusAir

47
c. Existing Data Storage System in DPSDA
DPSDA maintains two types of data processing and management software (NEO-PERDAS
and PHU). NEO-PERDAS is provided by PusAir as mentioned above and PHU (Provinsi
Hydrologi Unit) operated in DOS mode was developed in-house with the assistance of a local
university using Visual and Turbo Basic. PHU handles both data entry and extreme analysis
value. They have no formal systematic database (for example Oracle or SQL) besides; data is
saved in spreadsheets as MS Excel files. Raw stream flow data from the Balai PSDA is
usually only processed once per year and entered into the database. DPSDA uses the database
to create an annual publication. This report is circulated amongst divisions of PWRS and
served to other organizations upon request. Access to raw data is not allowed for external
stakeholders. Some of the data is posted online on the Dinas Komunikasi and Informasi
(communication and Information office) website. Only a sample of the analysis results has
been posted online while the complete analysis is kept in the office. Other agencies should
request to the office if they are interested in collecting that data.

Data Data Collection and Processing Dissemination


Measurement
Observer PJT-2
(RF)
1st Screening 2nd
Screening PusAir
Observer
(WL)
Balai PSDA BMKG
Citarum
Balai Data dan Informasi
InInformasi

Figure 40: Procedure of Data Management in DPSDA

d. Existing Data Storage System in BPLHD


BPLHD has developed its own environmental information system database called SISLING.
This system is connected to a MapInfo GIS system which is capable of archiving spatial and
temporal data as shown in Figure 41. It is developed to meet the needs of integration and
interconnection of separate software between the river water, wastewater and GIS map
information. Data entry is carried out manually and there are two main categories of input
data i.e. data that has to be entered manually and data that can be exported from spreadsheets.
Two main analysis reports are available, which are developed and displayed using MapInfo
GIS 9.0; the individual index of water quality status and series of indices of water quality
status. The index is determined according to the classes of water resources status based on the
Government Regulation 82/2001. Only the analyses results are posted online, while detailed
data is provided to organizations upon request.

48
Figure 41: Water Quality Information System (SISLING) Developed by BPLHD

3.3.2 Population Status


Data population in DSS database system is completed in Table 9, however; it still needs to be
polished by the operator at each agency. Each operator has to fill out some missing data,
match data parameters between each agency such as water quality, validate the data from
each relevant agency and update latest data which are not populated by DSS developers.

Table 9: Data Population Status

Data Data Provider Total


Data Type
Interval BBWSC DPSDA PJT-II BPLHD Other Station

Rainfall Daily 1980-2009 1980-2009 - - 1980-2009 117

AWS Daily - - 1999-2011 - - 3

Dam Daily - - 1962-2011 - - 3

Dam Plan Daily - - 2011 - - 3

Weir Daily - - 2003-2011 - - 12

AWLR Daily - - 1989-2006 - - 1

Water Level Daily 1995-2010 - 1990-2002 - - 27

Water Quality Daily - - 1992-2011 2001-2011 - 95

49
3.3.3 User Requirement Analysis
The usage of planned database was analyzed by interviewing each stakeholder and reviewing
the existing software and database. The main purpose of database usage for PJT-II is
supporting storage of all the hydrological data, searching data, exporting data, creating
reports, and running RRFS model.

And it is needed that database will also contain operation plan menu of dam, weir, and water
demand. Operation plan menu is only for PJT-II, therefore only PJT-II staff will be able to
use this menu in database.

In terms of BBWSC and DPSDA, the usages is supporting storage of the hydrological data,
searching and exporting data, creating reports, and running RRFS, and publishing yearbook.
Publishing the yearbook is very important feature and it follows from user requirement
specification.

In terms of BPLHD, the usage is supporting storage of the hydrological data, searching data,
exporting data, creating reports, and running RRFS model. Based on the TOR, water quality
features will be developed in the second phase of database development.

BMKG and PusAir can only search data and export data to excel format, because they do not
have their own hydrological data.

However; if the development team has enough time, DSS will also support a new feature
which user can manage water quality of river and industry. This feature follows from the user
requirement specification (PusAir).

Table 10: Program Usage


Input End
No. Usage Remarks
Data User
- Store all of the hydrological data from station
in DB server. Water level
data
- Search & edit hydrological data.
Rainfall data
- Export hydrological data to excel format.
AWS data
- Create & Print reports.
Weir data
PJT-II - Share all of the hydrological data with other
agency. Dam data
- Support operation of Dam. Water quality
data
- Support operation of weir.
Water demand
- Support operation of water demand.
data
- Modeling tools : RRFS

50
- Store all of the hydrological data from station
in DB server.
- Search & edit hydrological data.
- Export hydrological data to excel format. Water level
BBWSC - Create & Print reports. data
- Share all of the hydrological data with other Rainfall data
agency.
- Publish Year Book of hydrological data.
- Modeling tools : RRFS
- Store all of the hydrological data from station
in DB server.
- Search & edit hydrological data.
- Export hydrological data to excel format. Water level
DPSDA - Create & Print reports. data
- Share all of the hydrological data with other Rainfall data
agency.
- Publish Year Book of hydrological data.
- Modeling tools : RRFS
- Store all of the hydrological data from station
in DB server.
- Search & edit hydrological data.
- Export hydrological data to excel format.
BPLHD - Create & Print reports. Water Quality
- Share all of the hydrological data with other
agency.
- Support management of water quality in river
& industry.
- Search hydrological data.
Water quality
PusAir - Export hydrological data to excel format.
data
- Create & Print reports.
- Search hydrological data.
Rainfall data
BMKG - Export hydrological data to excel format.
Weather data
- Create & Print reports.

a. User Requirement Specification


Without doubt, the User Requirements Specification (URS) is the most critical of documents
because all of the development process including analysis, design, coding, and testing for
planned database and system is determined by user requirements and needs.

The table below is the user requirements sorted by each stakeholder. Based on the meeting,
PJT-II really concerns about water resource management such as weir, dam, reservoir, and
water supply have been incorporated.

51
BBWSC and DPSDA are having hard time storing the data into their database. The idea is to
simplify data storage by using database software and solve the complicated method of storing
data. Another important mission for them is publishing yearbook annually. Development
team will try to create feature that can directly extract the material for publishing the
yearbook in a few simple steps.

PusAir requested feature of providing chart of water quality information for each water
quality standard parameter efficiently and succinctly (showing the maximum, minimum and
average). Development team will try to create function to select maximum, minimum, and
average water quality data in a year (chart of annual report and comparison with other water
quality sampling point). As a result, they will be able to see the trends of water quality data at
those locations.

Table 11: URS (User Requirement Specification)


No. Sources Requirements Follow up Remarks
Need to save water
Create table to store
REQ- level, water discharge
rating curve formula
G-001 information, and
(update once a year)
rating curve formula
Some of rainfall data can be
collected from AWS. Data
AWS folder (daily.xls,
hourly.xls, minutely.xls)
Create table of rainfall
REQ- Save rainfall data Some of rainfall data can be
data considering to
G-002 from ARR collected from AWLR. Data
standard format (.TXT)
AWLR folder
(dayeuhkolot_daily.TXT,
dayeuhkolot_hourly.TXT,
dayeuhkolot_yearly.TXT)
Create table of water Data AWLR folder
REQ- Save water level data level data by (dayeuhkolot_daily.TXT,
G-003 from AWLR considering to standard dayeuhkolot_hourly.TXT,
format (.TXT) dayeuhkolot_yearly.TXT)
Save Create weather table by
REQ- Data AWS folder (daily.xls,
weather/climatological considering to standard
G-004 PJT-II (Erni) hourly.xls, minutely.xls)
ly data from AWS format (.xls)
Save water discharge Unfortunately, PJT-II did not
Create water discharge
REQ- data as additional have column space on water
column in the water
G-005 parameter of water quality table to save water
quality table
quality discharge information
Observer still hold the field
Save hourly water
note document of hourly
level & water
water level & water discharge
REQ- discharge data from Create hourly water
data. In other case, the hourly
G-006 observer into level data table
water level & water discharge
database, besides the
data stored on excel
daily data
document, in division office
Save annual
operational plan of
dam (maximum Create Operational Plan Based on : file name=
REQ- threshold, minimum of Dam table based on LCD_I_Dam_Operation_201
G-007 threshold, normal annual dam operational 10223.xlsm, sheet
characteristic, wet plan name=Rencana_OP
characteristic, and dry
characteristic)

52
In manner of
comparison, PJT-II
needs to save actual Create separate table for
data (water level, each dam data, including
water discharge, water level, water
REQ- hydropower discharge, hydropower
G-008 production) from production because the
gauge stations of each member of data for each
operating dam (Cirata dams are different,
dam, Saguling dam, especially Jatiluhur dam
and Jatiluhur/
Ir.Djuanda dam)
Save water-quality
standard parameters
based on government
REQ- regulation Create wq_parameter
G-009 (SK.Governor of DKI, table
SK.Governor of West
Java and Government
Regulation
BPLHD concerns more detail
Create about the WQ parameter than
wq_standards_industry PJT-II. BBWSC separates the
table to store water WQ standard parameter based
quality standards for on the classification of
Industry industry. For example, water
Create GUI to import sampling taken from Coca
Save water quality WQ standards for Cola (soft drink) factory will
REQ- standards parameter industry be just compared with WQ
G-010 based on government Create standards for Soft drink
regulation wq_standards_river industry
table to store water Please refer to Baku Mutu
quality standards for Industri.xls
main river WQ standard for main river
Create GUI to import stream flow can be review at
WQ standards on the folder \Format Data
river Import BPLHD\Baku Mutu
Air Sungai\
Create table of water
BPLHD sampling of wastewater
disposal of industry
named
Import water sampling
water_sampling_industr Please refer to: \Format Data
REQ- of wastewater disposal
y table Import BPLHD\Format
G-011 of industry in form of
Create GUI to facilitate Industri\Data Pemantauan.xls
excel files
user to import water-
sampling data from
industrys waste water
disposal.
WQ data in form of all data in
Create table of water one format. Please refer to :
sampling of main river \Format Data Import
stream flow named BPLHD\Format Sungai\format
Import water sampling
water_sampling_river import CITARUM.xls
REQ- of main river stream
table WQ data in form of one sheet
G-012 flow in form of excel one sampling point, please
Create GUI to facilitate
files refer to : \Format Data
user to import water-
sampling data taken Import BPLHD\Format
from the main river Sungai\Data Pemantauan
Wangisagara.xls

53
Create
Import Water Quality
Water_Quality_IP table
score based on Please refer to : \Format
(IP = Index
REQ- comparison using Data Import BPLHD\Format
Pencemaran/Pollution
G-013 pollution Index Sungai\Indeks
Index)
method (WQ on river Pencemaran.xls
Create GUI to import
stream flow)
data.
Import Water Quality
Create
score based on Please refer to: \Format
Water_Quality_Storet
REQ- comparison using Data Import BPLHD\Format
table
G-014 STORET method Sungai\ Storet
Create GUI to import
(WQ on river stream Wangisagara.xls
data
flow)
Example format: ..\format
data dpsda\ P0401
Cibeureum(RAINFALL
Create GUI to import DATA).xls
REQ- Import rainfall data in rainfall data which Database of rainfall data (in
G-015 form of excel files consider to standard data form of .db files, database file
format from DPSDA of Database Desktop from
DPSDA Delphi 7) can be review at
\format data dpsda\DATA
folder and subfolder
Import daily data on
annual Create GUI to import
REQ- Daily WATER DISCHARGE
report/yearbook of water level data from
G-016 in a year.xls
water level data in DPSDA
form of excel files
Create functionality to
Import AWLR data
REQ- parse the raw data and to
(recording interval :
G-017 store AWLR data into
hourly)
AWLR table
BBWSC
Create function to parse
Standard data format of
REQ- Import Rainfall data rainfall data and to store
rainfall data is similar with
G-18 (annual report) rainfall data into rainfall
DPSDAs standard format
table
Create function to select
maximum water quality
data, minimum water
Provide chart of water quality data, and average
quality information for of water quality data in a
each water quality year (chart of annual
standard parameter report and comparison
REQ- PusAir
efficiently and with other water quality
G-19 (Mr.Iskandar)
informative (showing sampling point). E.g.
the maximum, chart of BOD of water
minimum and sampling for Majalaya,
average) Nanjung, and so on
So, they can see the
trends of water quality
data on those location

The final use case diagrams derived from user requirement analysis are presented in
Appendix 3.

54
b. Data Flow Diagrams and Importer Modules
In this phase, the sources of data are identified and then each data source is characterized
with respect to the main characteristics of the data, the fields, and the type of entry
specifications. A flow diagram is drawn for each data source and type identifying the
complete route and all the processing in between required for the data to arrive at the
database from collection at the field. Similarly, legacy datasets are analyzed for their route
into the database. This process allows for the identification of importer modules that would
be required in order to process all the data types flowing into the database. The final data
flow diagrams for all the data sources and each data type are presented in Appendix 3:

3.3.4 Design of DB Structure

a. Standardization of DB
Station codes form the basis of location identification in the GIS database being built. These
station codes has to be defined to make each station has a unique code, so we can distinguish
every station belongs to each agency and make it possible to expend the database to other
river basin in the future.

b. Gauge Station Code Structure


To distinguish between each hydrological structure, the structure needs a unique code to be
assigned to it for GIS programming as shown in Figure 42.

Figure 42: The Gauge Station Code Structure

55
Table 12 is the gauge station code specification which development team used for:

Table 12: Station Code Structure


River Territory Type Agency Reg. Number
Length 2 2 1 3
10 : Dam
0 : BBWSC
20 : Weir
1 : BPLHD
30 : Rainfall
Detail 10 : Citarum 2 : DSPDA 000 ~ 999
40 : Water Discharge
3 : PJT-II
50 : AWS
4 : PusAir
60 : Water Quality

c. Code List
This code is used only for the programming, therefore only administrators can edit it and
users can only search and see the structure information, so they cannot change the code. All
the assigned structure code is shown in Appendix 2.

d. Development of Class Diagrams


In a database, classes are elements that are a combination of variables and algorithm. As such,
a class can have different states (different values for its variables) as well as different
behaviors in response to events. Classes constitute a fundamental aspect of object-oriented
programming and definition of classes as well as the identification of relationship between
these classes is fundamental step in any database design. The complete classes identified and
their respective class diagrams are shown in Appendix 3:

e. Database ERD
In software engineering, an Entity-Relationship Model (ERM) is an abstract and conceptual
representation of data. Entity-relationship modeling is a database modeling method, used to
produce a type of conceptual schema or semantic data model of a system, often a relational
database, and its requirements in a top-down fashion. Diagrams created by this process are
called Entity-Relationship Diagrams, ER Diagrams, or ERDs.

56
class Database Schema

Contain i nformation about


region, watershed,
agency, etc...
Dam

+ DAM_DATA_Cirata
Base Info
+ DAM_DATA_Jatiluhur
Rainfall + AGENCY_INFO + DAM_OPER_PLAN
+ RF_DAT A_DAILY + CATCHM ENT_INFO + DAM_DATA_Sagul ing
+ RF_GAUGE_INFO + DIST RICT _INFO use + DAM_INFO
use
+ PROVINCE_INFO
+ RIVER_T ERRITORY_INFO
+ SUB_CAT CHMENT _INFO
+ SUB_DISTRICT_INFO
+ VILLAGE_INFO
Weir
use
use + WEIR_DAT A_Barugbug
AWS (Automatic Weather Station) + WEIR_DAT A_Bekasi
+ WEIR_DAT A_Ci karang
+ AWS_DAILY
+ WEIR_DAT A_Gadung
+ AWS_GAUGE_INFO
+ WEIR_DAT A_Jengkol
+ AWS_HOURLY
+ WEIR_DAT A_Macan
+ AWS_MINUTELY
+ WEIR_DAT A_Sal amdarma

use use + WEIR_DAT A


use use
+ WEIR_DAT A_Waduk_Cipancuh
+ WEIR_DAT A_Ci beet
+ WEIR_INFO

WaterDemand
WaterLev el WaterQuality WaterQuality (Industry)
+ WD_DAT A_DAILY
+ AWLR_DAILY + WQ_GAUGE_INFO + WQ_IND_GAUGE_INFO
+ WD_INT AKE_POINT_INFO
+ AWLR_HOURLY + RIVER_CLASS_INFO + IND_CAT _INFO
+ WD_PAM_INT AKE_PLAN
+ AWLR_MINUT ELY + WQ_DAT A + WQ_IND_DAT A_DET AIL
+ RAT ING_CURVE_FORMULA + WQ_PARAM + WQ_IND_DAT A
+ WL_DATA_MAN + WQ_STD_RIVER + WQ_STD_IND
+ WL_GAUGE_INFO

Figure 43: ERD of Hydrological Database

Entity-Relationship Diagrams establish how fields are linked or joined to each other within
tables of a database. Establishing ERDs is the first step towards development and design of
all the tables that will eventually be incorporated in the database. The ERDs for the
hydrological and GIS database is shown in Figure 43 and the ERDs for all the other data
tables are presented in Appendix 7.

f. Component Diagram
Development team has been using Model View View Model (MVVM) as common
software design pattern to develop the application. Model components are the components
that directly handle functionality of data manipulation, data searching, data recognition to
read raw data from a file, or data writer to export some data to a file.

In the Unified Modeling Language, a component diagram depicts how components are wired
together to form larger components and/or software systems. They are used to illustrate the
structure of arbitrarily complex systems.

Component diagram represent the perspective implementation of the system and reflect
grouping of the different design elements of a system, such as classes of the system.
Components are the objects that interact with each other in the system. Components connect
to each other to make an integrated system by some relation/association. Relation/association
lines are representation of a command delegation, functionality requirement, data binding, or
component dependency. The database component diagram is shown in Figure 44.

57
Figure 44: Database Component Diagram

3.4 Development of GIS Database

The main objective for development of GIS database is to build a central repository of all
hydrological, hydro-geological, metrological, land use, and groundwater data; history and
that being collected in real time. The GIS database will provide a geo referenced data
archiving solution for DSS operators and managers. The data would be made easily
accessible and retrievable for various different classes of users from experts to technicians.

GIS database are composed of three parts as shown in Figure 45:

Data Table: collection of rows, each contains the same fields;


Feature Class: table with a shape fields containing a point, line, or polygon geometries
for geographic features;
Raster dataset: contain raster which represent continuous geographic phenomena;

58
Figure 45: GIS Database Structure

3.4.1 Data Preparation and Selection for GIS Database


GIS data are mostly obtained from Water Resources Information System (Sistem Informasi
Sumber Daya Air/SISDA) of PJT-II and consists of administrative boundary, diversion and
intake structure, reservoir location, sub-catchment, discharge observation points, roads, soil
type, water quality, land-use, rainfall station, etc. The list of data collected from PJT-II is
summarized in Table 13. Some of the GIS layers are presented in the following paragraph.

Table 13: GIS Data Collected from PJT-II

No Layers Description

1 Administrative boundaries Polygon of Java island, province, district, sub-


district, village
2 Boundary of working jurisdiction Polyline of boundary
Diversion & intake structure of east
3 Point location (X, Y)
tarum canal
Diversion & intake structure of west
4 Point location (X, Y)
tarum canal
Diversion & intake structure of north
5 Point location (X, Y)
tarum canal
6 Secondary diversion & intake structure Point location (X, Y)

7 Bendung (dam) Point location (X, Y)

59
8 Das (catchment) Polygon of sub-catchment
9 Debit (discharge) Point location (X, Y)
Classification of elevation (<1200, 1200-2000,2000-
10 Elevation vegetation type
3000, >3000)
11 Planting group Polygon of planting group
12 Culvert Point location (X, Y)
13 Hydro (river network) Polyline of river network with length
14 Climate Point location (X, Y)
15 Infrastructure Point location without (X, Y) coordinate
16 Artery Road Polyline with length (meter)
17 Rail Road Polyline with length (meter)
18 Express Road Polyline with length (meter)
19 Bridge Point location (X, Y) of the center
20 Soil type Polygon of soil type
21 Slope Polygon of slope classification
Polygon of physical condition such as hills, alluvial
22 Physical condition
valleys, swamps, etc.
23 Water quality Point location (latitude, longitude)
24 Critical land Polygon of critical land
25 Landuse Polygon of landuse
26 Landuse 2007 Polygon of landuse
27 Population Polygon of population density
Point of infrastructures (bus terminal, railway
28 Transportation infrastructure
station, harbor)
29 Main canal Polyline with length (meter)
30 Secondary canal Polyline with length (meter)
31 Siltrap Point location (X, Y) of the center
32 Siphon Point location (X, Y) of the center
33 Lake dam swamp Polygon of lake_dam_swamp
34 Rainfall station Point location (X, Y) of the center
35 Aquaduct Point location (X, Y) of the center
36 Drop structure Point location (X, Y) of the center
37 Dam lake Polygon of dam_lake
38 Daker (working jurisdiction) Polygon of working jurisdiction of observers

60
All the collected and validated maps are shown in Appendix 1.

a. Administrative Boundaries
The administrative boundaries are divided into province, district, sub-district, and village.
The smallest administrative boundary in CRB is called desa/village. Fields on the attribute
table are as follows: (i) area, (ii) perimeter, (iii) provinces ID, (iv) districts ID, (v) sub-
districts ID, (vi) villages ID, (vii) province, (viii) districts name, (ix) sub-districts name,
and (x) villages name. CRB covers two provinces (West Java and DKI Jakarta), 17 districts
(kabupaten/kota), 42 sub-districts (kecamatan), and 2377 villages (desa). The smallest village
area is 1.83 km2 (Desa Pademangan Barat, Kecamatan Pademangan, Kota Jakarta Utara, DKI
Jakarta Province) and the largest area is 9.05 km2 (Desa Jatisari, Kecamatan Cileungsi, Kota
Bogor, West Java Province).

b. Diversion and Intake Structure of East Tarum Canal (ETC)


There are 62 locations of diversion and intake structure along East Tarum Canal (ETC). The
structure of ETC covers the information of X, Y coordinate, code for each structures point
and the dimension of each structure. The contribution from Curug Weir to ETC is about 88%
and ETC has supplied municipal water to Subang and Karawang Districts.

c. Diversion and Intake Structure of West Tarum Canal (WTC)


There are 43 locations of diversion and intake structure along West Tarum Canal (WTC).
WTC starts from Curug weir on the Citarum river and ends at a junction with the Ciliwung
river. The field attributes covers (i) buildings name, (ii) canals name, (iii) remarks, (iv) X, Y
coordinates of the center of the building. WTC was operated since 1968 and was conveying
raw water of the Citarum river for both irrigation water supply and domestic, municipal and
industrial water supply. The raw water is pumped up at the Curug Weir site by 17 hydraulic
pumps. WTC is also one of the key suppliers for raw water to the water treatment plants
(WTP) of PAM-Jaya in Jakarta. The WTP that receives raw water from WTC is
Pejompongan I & II, Pulogadung and Buaran I & II. In addition, WTC has supplied water to
Bekasi City through the municipal water supply agency, PDAM Bekasi.

d. Diversion and Intake Structure of North Tarum Canal (NTC)


There are 64 locations of diversion and intake structure along North Tarum Canal (NTC).
The municipality of Karawang abstracts water from the NTC for the municipal use. The field
attributes covers (i) buildings name, (ii) canals name, (iii) remarks, (iv) X, Y coordinates of
the center of the building.

e. Secondary Diversion and Intake Structure


There are 1,561 locations of secondary diversion and intake structure in the downstream of
CRB. The field attributes covers (i) buildings code, (ii) buildings name, (iii) secondary
canals name, (iv) short information on structures, and (v) X and Y coordinates of the
building.

61
f. Weirs (Bendung)
There are 56 weirs location inside Citarum River Basin. Field in attribute table covers (i) X
and Y coordinate, (ii) weirs name, (iii) rivers name, (iv) weirs type, (v) gates type, (vi)
gates dimension, (vii) maximum discharge, (viii) function of each weir, (ix) condition, (x)
operator, (xi) district. (xii) sub-district, (xiii) village, (xiv) built in year, and (xv) start of
operations year.

One of the most important weirs, called Curug Weir, is situated on the mainstream about 15
km upstream from the Walahar Weir and has, since 1965, diverted the river water to the West
and East Tarum Canals through pumped systems.

Although the diversion systems have also supplied raw water for the municipal and industrial
uses to the urbanized areas located along the canals, the most significant role thereof is to
supply to Jakarta City.

In order to cope with the increasing water demand in the water supply areas, each canal
system extracts river flow from the tributary of the Citarum river and the other nearby river at
some places where the canal crosses one of them. For instance, the 70 km long West Tarum
Canal takes water from the Cibeet river, a tributary of the Citarum river, on its way to Jakarta,
while the East Tarum Canal from the Cipunagara river at the Salamdarma Weir, which is the
nearby river discharging into Java Sea to east of the Citarum river. Thus, the water resources
of the Citarum river Basin and its neighboring basins, which cover a total catchment area of
11,000 km2, have been effectively utilized through the integrated water network in order to
meet the water demands in the previously mentioned target areas.

In the western part of the network, the West Tarum Canal (WTC) passes through the
Cikarang and Bekasi river and extracts more additional water from these two (2) rivers.
Eventually, the aggregated total catchment area of the Citarum Water Resources Network
covers a total area of 13,000 km2 and the cities of Jakarta and Bogor are the major beneficiary
areas thereof.

g. Main & Secondary Canal


Main canal is stored as poly-line in the GIS data. The information in attribute table includes
canal name, length of canal, and canal code.

h. Lake
Information of lakes in CRB is stored as polygon without (X, Y) coordinate. Field of attribute
table includes area of the lake.

62
3.4.2 Final GIS Layers
The database base map will consist of 13 essential maps. The selection of these maps has
taken into account not just data consistency but all the user requirements as discussed in later
sections. The layers are shown in Table 14. The applied GIS layers in DSS Database are
shown in Figure 46.

Table 14: GIS Maps Selected for Database Base Layer

No GIS data Name of Shape File


1 River territory information batas_wilker_pline
2 River system Hidro
3 Rainfall observe station information rainfall station_final
4 AWS information Lklim
5 Water discharge observe station information Debit
6 Water quality observe station information kualitas_air
7 Dam information waduk_srtv / waduk_situl / waduk_situz
8 Weir information Bending
9 Intake point information bagi_sadap_induk_stt / bagi_sadap_stb /
bagi_sadap_stu
10 contour information DEM CRB
11 Catchment information final_catchment10mar11
12 Sub catchment information final_catchment10mar11
13 Map of west java adm_jawa_poly_utm

63
Figure 46: GIS Layers Applied in DSS Database

64
3.5 DSS Database

DSS data manager is the software developed to manage hydrological and GIS data for
relevant operator. Figure 47 is the main screen of data manager.

Figure 47: DSS Data Manager Main Screen

3.5.1 Menu Diagram


The Menu diagram from the GUI is shown as follows;

Figure 48: Menu Diagram

65
Each agency has its own database related to Citarum River Basin. However, the database
should be integrated and expanded to cover the whole country in the future. Therefore DSS
data manager is also designed to share data between every agency which are managing
Citarum River Basin and also developed to construct integrated database in national level.

For the first step, this project is starting with CRB and the data manager is developed
considering this progress plan.
For the next step, development team should build up understanding with another
agency and make a contract and then create a new database space for them.
Each agency will populate the data manager with their own data and the populated
data will be automatically shared with other agencies.

DSS data manager can also provide a clear and reliable database by searching, comparing,
and analyzing hydrological data at one glance by sharing data between each agency.

3.5.2 Key Features of DSS Data Manager

a. Data Input
Each agency can input data by using Data Input Wizard without changing the previous format
which is used before. Through this process, agencies do not have to duplicate work to
maintain the database. User can input data directly to the data table by typing or copy & paste
manually as well.

Figure 49: Data Input Wizard

66
b. Data Output
Each agency can export their data in excel format and other agencies data as well.

Figure 50: Data Export to Excel Format

c. Data Validation
User can check the data after importing by using Data Import Wizard or manual method.
After importing the data, user can easily notice an abnormal data by cross checking the tablet
data at the chart window as well.

Figure 51: Data Validation Screen

67
d. Integrated Modeling Tools
Modeling tools can be integrated with DSS database which user does not need to input data
separately only to run the models. RRFS is developed and integrated exclusively for DSS
data manager and Citarum River Basin.

Figure 52: Integrated RRFS Screenshot

e. Create Reports
DSS data manager includes feature which can create reports based on user requirements such
as yearbook, rainfall report, dam operation report, and water quality report. These reports are
based on URS (User Requirement Specification) collected by agencies.

68
(a) Publish Year Book

(b) Annual Rainfall

69
(c) Water Quality

(d) Dam Operation


Figure 53: Reports

70
f. Manual
The DSS data manager also provides a manual for administrators and a help document for
end users. These documents and written in English and fully translated into Bahasa Indonesia
as well.

Figure 54: DSS Data Manager Manuals

71
3.5.3 Graphical User Interface
In computing, a GUI (Graphical User Interface) is a type of user interface that allows users to
interact with electronic devices with images rather than text commands. A GUI represents the
information and actions available to a user through graphical icons and visual indicators such
as secondary notation, as opposed to text-based interfaces, typed command labels or text
navigation. The actions are usually performed through direct manipulation of the graphical
element.

a. Main Screen
Basically, user can see GIS map which has geometrical data. By clicking the target point in
the map, users also get information of area, station, dam, and weir. GIS map can also be
panned, zoomed-in, and zoomed-out on with GIS map tool. On the bottom of GIS screen,
user will be able to see mini map and map scale information.

Figure 55: Main Screen

72
b. Data Search and Review Screens
User can search all kinds of hydrological data from each agency, which is composed of the
data of rainfall, AWS, water level, water quality, water demand, dam, and weir. User can
search data by agency name, date, station type, district, and sub district and the search result
will be viewable in table and graphical view.

Figure 56: Result of Searched data in table and graph

73
c. Data Import Wizard
User will be able to input data in few steps by using data import wizard. It reads the file
which user selected and stores the data to the database.

First step; user has to select agency type such as BBWSC, PJT-II, DPSDA, BPLHD
and PusAir.
Second step; user has to select data type such as AWS, rainfall, weir. etc. and also
whether it is automatic or manual station.
Third step; user has to browse for and upload excel file or text file which contains the
data.

Figure 57: Data Import Wizard

74
After all of these steps, user will be able to check the data which is imported and validate the
data before it is stored in the database as shown in Figure 58.

Figure 58: Preview of Imported Data

d. Opening GIS Map


DSS software is based on GIS map data. Most of the hydrological data collecting stations are
located on the GIS map and each location contains data from each observation station. The
GIS Map data bar is shown in Figure 59.

Step 1. after you login the DSS software, click on 'GIS View' button to see GIS map of
Citarum River Basin.

Figure 59: GIS View Button

75
Step 2. as clicking on 'GIS View' button and you will be able to adjust the GIS map using
your mouse.

Figure 60: GIS Map Screen

Step 3. You can adjust the GIS map with simple mouse operations.

Move: click and drag the GIS map in any direction.


Zoom in: wheel the mouse up to zoom in to certain area.
Zoom out: wheel the mouse down to zoom out the map.

76
e. GIS Map Icon Legends
You will see some icons on the GIS map in Figure 61 which represents observation stations
and legend of each icon in Table 15.

Figure 61: GIS Map Icons

Table 15: GIS Map Icon Legend

Icons Explanation
Rainfall station

AWS (Automatic Weather Station)

Water quality station

Weir

Water level station

77
3.6 Information Systems Implementation Program

Information systems implementation is an important component of the project involving the


deployment and setup of the hardware and configurations needed to sustainably execute the
project. In this section, it will introduce how the information systems network and hardware
will be setup and provides some details on the efforts underway to get the DSS deployed and
up and running.

3.6.1 Introduction

a. How DSS Database Works


DSS will be served as a standardized framework on which all current monitoring, modeling,
and conservation practices can be integrated and analyzed by the river basin managers. The
database is schematized in Figure 62.

Figure 62: Progress of DSS Database Operation

78
3.6.2 System Configuration

a. Hardware Configuration
DSS hardware consists of two servers; the database server and GIS server. In database server,
Microsoft SQL Server is installed which stores and manages entire hydrological data. In GIS
server, it stores and manages GIS data related to Citarum River Basin. Following is the figure
of DSS hardware configuration.

Figure 63: Hardware Configuration

A public IP should be assigned to each server for the access from outside client, and each
server uses RAID-1 method for the backup and safety of data.

Table 16: Hardware Explanation

Hardware Explanation Satisfy Requirements


UPS Uninterruptible Power Supply Stability
Modem Internet Connection Modem
Scalability, Performance,
DB Server Database Server
Stability
Scalability, Performance,
GIS Server GIS Server
Stability
Monitor For Server Management Management

79
b. System Requirements
For proper operation and performance of DSS system, DSS server and client should satisfy
following requirements.

Figure 64: Server Requirements

Figure 65: Client Requirements


80
c. Software Configuration
Development team has installed various software, which are necessary for operation. The
software list is shown in Figure 66 and Table 17.

Figure 66: Software Installed in DSS Server

Table 17: Software Installed in DSS Server

Software Explanation
Windows Server 2008 R2 Enterprise Edition Operating System for Database and GIS server
Anti-Virus Vaccine Protection of External Attack
Microsoft SQL Server 2008 R2 Enterprise Edition Storage and Management of Hydrological Data
ArcGIS Server v10 Storage and Management of GIS Data
DSS Software Hydrological Data Search and Input

81
3.6.3 Database Server Configuration

a. Start & End of Database Service


Database services can be controlled for server management. SQL Server Configuration
Manager Program which is installed in database server is needed to be run for starting the
control of database service.

Figure 67: SQL Server Configuration Manager

If server administrator makes a right-click on the SQL Server, context menu will be showed
up as below. Now Administrator can start, stop, and restart the SQL server service using this
menu.

Figure 68: Context Menu of SQL Server Service

82
3.6.4 GIS Server Configuration
The following section presents details on the GIS Server configuration.

a. ArcGIS Server Manager Connection


Administrator has to use ArcGIS Server Manager to manage ArcGIS servers data. ArcGIS
Server Manager is hosted by ArcGIS server and it is a web-based program, therefore
administrator should access by installed web browser.

Input the connection address of ArcGIS Server Manager after running web browser.
Connection address is http://GIS Server IP Address/ArcGIS/Manager.

Figure 69: ArcGIS Server Manager Login Screen

83
If you input the account and password administrator will be able to see the screen for
configuration.

Figure 70: ArcGIS Server Manager Configuration Screen

Click on Manage Services menu to check the GIS maps which are currently on service.

Figure 71: List of GIS Maps on Service

84
Administrator will be able to see list of GIS maps and administrator can also start, stop, and
restart the service of GIS maps.

Figure 72: Start, Stop, and Restart Function

If administrator wants to see more detail about the GIS map, administrator can click on the
GIS map list.

Figure 73: Select GIS map for Detailed Information

85
Now, administrator will be able to see detailed information and administrator can edit the
information and also setup GIS map address which are currently on service in the Parameters
menu screen.

Figure 74: Parameters Menu Screen

In Capabilities screen, administrator can select the map which wants to be serviced.

Figure 75: Capabilities Menu Screen


86
In pooling screen, administrator can set the minimum and maximum value of server stress.
Set the values depend on the server specification.

Figure 76: Pooling Screen


In Caching screen, administrator can set Map Cache information to increase the server
performance.

Figure 77: Caching Screen


87
After setting entire configurations, click on Save and Restart button which located on the
right-bottom of the screen to apply configuration and the ArcGIS server will be restarted.

b. ArcGIS Server Management


Administrator can check the log information of the ArcGIS servers operation status, in
purpose of observation and maintenance. Click on Log Files menu to start.

Figure 78: Log Files Menu Screen

Administrator can see the entire log and information recorded up to date in this screen.

88
3.6.5 Data Manager Configuration
Following section explains the data manager configuration in detail.

a. Database Connection Setting


Database connection information is included in the distributed DSS software. If administrator
wants to change the configuration, it can be changed by using programs such as Notepad.
DataManager.exe.config is located in the same directory which is installed DSS software.

Figure 79: Location of DataManager.exe.config File

If you open the file, you will be able to see a configure information as below which has XML
format.

Figure 80: Content of DataManager.exe.config File

89
Change the IP address in the database server and save the file. Then restart the DSS software
and the new IP address of database server will be assigned.

b. ArcGIS Server Connection Setting


DSS software contains a feature which can check and setup the ArcGIS server connection
information. If the ArcGIS server IP is changed, user has to change the connection
information to use DSS softwares GIS map and it can be done in the Management menu
screen.

Run DSS software and go to Config menu which is under Management menu, then user will
be able to see a screen as below. User can change the IP address in ArcGIS Server Rest API
Address menu. Change the address and click on the Save button which is located on the
toolbar to save the address and then DSS software will try to connect to the new IP address
and receive GIS data from the new IP address.

Figure 81: ArcGIS server IP configuration Screen

90
c. Authority Setting
Administrator can assign authority to each account in Authentication Management menu.
User can only use the menu for which he or she has authority to access. Click on
Authentication Management menu which is under Management menu.

Figure 82: Authentication Management Screen

Administrator can change which user will have authority through the menu options. If
administrator needs to change that information, then click on Detail button to start.

Figure 83: Authentication Management Detail Button


91
If administrator clicks on the Detail button, the detailed information of selected account will
appear and the authority can be changed, saved, and deleted.

Figure 84: Changing Authority of Account

Administrator has to click on Add button to add a new account for DSS software.

Figure 85: Adding New Account

After clicking on Add button, a screen will be appeared using which administrator can add
new account and then click on save button to finish adding new account for DSS software.

92
d. User Account Setting
Administrator can search and setup account which can access DSS software. For doing this,
run DSS software and go to User Management menu, which is located under Management
menu.

Figure 86: User Management Menu

First, administrator will see the list of accounts which are currently in use. On the top of the
list, there is a filtering tool which administrator can use to see only the selected parameter.
For example, if administrator wants to see certain agency, selects the agency on the filtering
tool.

Figure 87: Filtering Tool

93
Now the account only belonging to selected agency will be appeared on the screen.

Figure 88: Result Screen of Using Filtering Tool

If administrator wants to change the information of certain account, he or she can click on
Detail button, which is located on the end of the account row.

Figure 89: Detail Button on User Management Screen

94
Information screen will be appeared on the top of the list when administrator clicks on Detail
button.

Figure 90: User Information Screen

After changing information, click on save button. If administrator wants to delete account,
just click on Delete button, otherwise, to add a new account, click on Add button to start.

Figure 91: Adding New Account

95
If administrator clicks on add button, a screen will be appeared on the top of the list through
which administrator can input information for a new account. Enter the information of new
account and click on save button, then a new account will be created.

Figure 92: Setting Information for New Account

96
3.6.6 Issues and Recommendation
The DSS data manager development is completed and the software is ready to be installed in
the actual server for operation. The following section provides information on some of the
challenges that were encountered during the development phase.

a. Limitation of Network Bandwidth and Availability


Considering the current network configuration of DSS, there is an issue of minimum network
bandwidth for DSS software implementation in PJT-II. Because of this reason, we propose a
few network configurations which can solve this bandwidth problem.

Figure 93: Network Configuration 1

97
Figure 94: Network Configuration 2

98
Figure 95: Network Configuration 3

99
4. Development of Rainfall-Runoff Forecast System

One of the fundamental steps in any water basin management is rainfall-runoff analysis,
which also provides basic data for water resources allocation and water quality analyses. This
chapter describes results of development and application of the rainfall-runoff forecasting
system for CRB.

4.1 RRFS Introduction

RRFS shown in Figure 96 is a rainfall-runoff forecasting system developed by K-water based


on US Armys Stream flow Synthesis and Reservoir Regulation (SSARR) Model. RRFS is a
long-term, hydrologic rainfall-runoff model for continuous simulation of daily, monthly, and
yearly runoffs. It was designed to facilitate the conjunctional operation and control of
reservoirs by simulating runoff, serving as a base for water use management. Some of the key
advantages of RRFS over other rainfall-runoff models are: 1) Advanced GUI for intuitive and
easy use, 2) Flexible conceptual model for incorporation of more complicated calculations as
required, 3) Minimum data requirements for easy initial deployment, and 4) Ensemble stream
flow prediction for comprehensive coverage of all potential event probabilities and their
outcomes. The details of basic logic of RRFS engine, parameter estimation, and application
processes are given in the RRFS manual.

Figure 96: Rainfall Runoff Forecasting System

100
4.2 Model Construction

4.2.1 Sub-catchment delineation of CRB


After significant consultations, the existing sub-catchment delineation already in use by PJT-
II was selected as a basic scheme for initial RRFS development and implementation in line
with overall objective of synergizing the DSS development with existing practices. The
catchment delineation is shown in Figure 97, which also shows the three regions of CRB
divided for RRFS implementation. There are 14 catchments in Citarum basin, 24 catchments
in upper Jatiluhur area, and 11 catchments in Cilicis area.

Figure 97: Sub-Catchment Delineation

101
Due to the parallel distribution pattern of sub-catchment which flows from the South to the
North, the drainage system is complicated if each catchment is considered independently.
Therefore, the existing hydrologic drainage system was modified based on WTC (West
Tarum Canal), ETC (East Tarum Canal), and NTC (North Tarum Canal) which pass through
the I- and J-regions. Based on an analysis of the basin, the sub-catchments were reorganized
as Figure 98.

Figure 98: Final CRB Sub-catchment Division

102
The schematic diagram of CRB is composed of Central CRB, West Tarum Canal, East Tarum
Canal, and North Tarum Canal shown in Figure 99 to Figure 102.

Figure 99: Drainage Schematic in Central CRB

103
In RRFS, the flow network can be modeled using five types of water elements:
A basin represents a basin or sub-catchment of which essential parameters are rainfall
and flow characteristics.
A channel is essentially a transfer point that can incorporate lag or delay in the flow
and also approximates flow through parts of the stream network where
evapotranspiration and seepage is negligible.
A transfer point is a point in the network where no input or output takes place;
however the flow can be observed. Transfer points are model equivalents of flow
monitoring stations on the ground.
An intake point is essentially another transfer point with the ability to input flow into
the overall balance. These can be used to model as parts of the network where flow is
entered in the network through manmade pipelines or channels.
A dam has all the properties of channel, intake point, and transfer point. Additionally,
it can also be used as a way to divert flow away from the network. Dams can be used
to model water reservoirs, man-made or natural, in the network.

a. WTC
WTC is the artificial canal which flows to the West from the water source, Curung weir.
Runoff diagram is shown in Figure 100 and its starting point is node 17 in Figure 99. Node
17 is the intake point in CRB-RRFS described as WTC in Figure 99.

Out
17-5 17-4 WTC-4 17-3 WTC-3 17-2 WTC-2 17-1 WTC-1 17
let

I1 I6 I2 I3
CFC
26

Figure 100: Schematic diagram of drainage system of WTC

Cibeet river located in C-region flows to the WTC through the node 26, Cibeet Feeder
Canal (CFC), and Suppression from Cibeet (SFC) in Figure 99, and node 17-1 in
sequence.
After Cibeet river is formed, two main tributaries (Cikarang and Bekasi river) flow to
the WTC through the node 17-2 and 17-3. Two other tributaries (Cipinang and
Ciliwung) flow to the WTC through the 17-4 and 17-5 located at the right before
outlet node.
In this diagram, three sub-catchments (I4, I5, and I7) in southern sides of I-region are
not included because WTC is an artificial channel and some area passes through the
urban area; however, it will be added later after considering input of expert opinion.
Of the basins of WTC 2, 3, and 4 will be included in the flow diagram easily by
adding inflow node at the end of each channel.

104
I8 and I9 in the northern side of I-region are the areas which could not be expected to
have return flow. The water in this area will be used for agricultural purposes by
adding intake node.

b. ETC
ETC is the artificial canal which flows to the East from the water source, Curung weir.
Runoff diagram is shown in Figure 101 and its starting point is node 18 in Figure 99. Node
18 is the intake point in CRB-RRFS described as ETC.

Out
I8 ETC-1 18-1 18-2 ETC-2 18-3 ETC-3 18-4 18-5 ETC-4 18-6 ETC-5 18-7
let

J1+
J3 J4 J7 J5 J9 J2+ J12
J10

Figure 101: Schematic diagram of drainage system of ETC

Seven main tributaries flow in to the ETC through each node. Especially, Cipunegara
river inflows through node 18-6 to the ETC and there are three sub-catchments (J1, J2,
and J10) which contribute this river. It will be divided as it is for simulating better
analysis instead of as one merged catchment.
Three sub-catchments (J6, J8, and J11) in southern sides of J-region are not included;
however, those will be included in the diagram easily by adding inflow node at the
end of each channel.
J13, J14, J15, J16, and J17 in the northern side of J-region are the area which could
not expected to have return flow. They are also considered that the water in this area
will be used for agricultural purposes by adding intake node.

c. NTC
NTC is the canal located in downstream of CRB which flows to the east through the J14 node.
Runoff diagram is shown in Figure 102 and its starting point is node 31 in Figure 99. Node
31 is the intake point in CRB-RRFS.

Out
31 NTC
let

Figure 102: Schematic diagram of drainage system of NTC

It will be possible to add inflow and intake nodes as described in the case of WTC and
ETC.

105
4.2.2 Input Data
The input data used in the RRFS model can be largely divided into three types: physical,
hydrometeorologic, and water demand data.

a. Physical Data
To implement reservoir operation function of RRFS, three dams (Saguling, Cirata, and
Juanda) were taken into consideration. Channel routing is implemented by continuous virtual
reservoir routing method which parameters represent the number of virtual reservoir and
retention time. Basin routing in RRFS is implemented independently using flow fields such
as surface, sub-surface, base-flow, and lower zone. Each flow field assumes that there are a
lot of virtual reservoirs and each reservoir is routed. Parameters of each flow field represent
the number of virtual reservoir and retention time and each parameter is estimated with basin
area, main channel length, and travel time. Accurate flow duration curve can be estimated by
water allocation analysis for the relation between catchments and flow such as to and from
catchments for water allocation.

b. Hydrometeorologic Data
To estimate spatial variance of rainfall by elevation, area ratio by elevation is the main input
data for RRFS simulation. In this study, basin area and area ratio by elevation were calculated
by dividing a basin into several bands based on DEM. To draw the graph of one of the
parameter (SMI-ROP) in RRFS, initial value of SMI-ROP is determined by land use and soil
type. The value of SMI01 was estimated with upstream data of three dams, SMI02 using dam,
and SMI03 using downstream data of Juanda dam. Because the average basin rainfall based
on the observed rainfall and temperature data by Thiessen method was estimated with an
assumptive of flat area, it is necessary to apply rainfall weights by elevation to adjust this
assumption as real basin condition. In this study, rainfall weights by elevation is estimated as
calibrating constant, that is calculated based on 100% of rainfall weights at the average
elevation in each catchment. Calibrating constant defines the increment of rainfall (mm) by 1
m increment of elevation.

c. Water Demand Data


Water demand data for CRB can be divided into three parts: agriculture, municipal and
industrial water demands.

s Agricultural Data
In the upstream of Jatiluhur, water demand for each sub-catchment can be computed by
standard irrigation demand per ha (about 1.1 liter/ha/s) which is multiplied by the total
agriculture area in each sub-catchment. Irrigation demand is assumed constant for each
month and year. Based on this calculation, an average annual irrigation demand of about
149.8m3/s for the upstream part of Jatiluhur is distributed into sub-catchments. In the
downstream of Jatiluhur, Water demand for each sub-catchment is derived from annual water
balance data which is available from 1990 to 2009 from PJT-II and total agriculture area in
each sub-catchment. Irrigation demand of each month is assumed as constant and then total
irrigation water demand for each sub-catchment is computed by:

106
SubCatchmentIrrigationArea
SubCatchmentIrr.Demand = TotalIrr.Demand
TotalIrrigationArea

An average annual irrigation demand of about 168.6m3/s is distributed into sub-catchments


in downstream of Jatiluhur.

s Municipal and Industrial


For upstream of Jatiluhur, analysis result from the document of Integrated Water Resources
Management Project (ICWRMP), Appendix I, Water Demand, 2006, can be used. The
municipal water demand for the downstream of Jatiluhur together with water demand
prediction from PJT-II. For the period 2010-2011, water demand for municipal and industry
is estimated as:
s Total for East Tarum Canal: 0.88m3/s
s Total for West Tarum Canal: 21.44m3/s
s Total for North Tarum Canal: 2.5m3/s
These values are further distributed into sub-catchments.

s Return flow estimation


Intake amount of water usage in a basin or river is able to return to the inside or outside of its
basin or river. The return flow rate is one of the important factors to simulate water allocation
analysis; however, there is no simultaneous equipment to measure intake and flow for
estimating return flow. The return flow is estimated with the constant rate of intake in CRB.
The return flow rate for municipal and industrial water usages is set at 65% and that of
agricultural water usage is set at 35%.

4.3 Result of Application in CRB

4.3.1 Model Calibration and Verification


Parameters of the model were calibrated against observed flow data in the central region of
CRB by employing the input data described in the previous section. Then, the calibrated
model was verified using other sets of observed flow data at the same locations. The
appropriateness of the model calibration and verification was estimated using two methods of
Relative Bias (RB) and Relative Root Mean Square Error (RRMSE). RB and RRMSE are
simultaneously used to examine the result of yearly simulation and daily simulation,
respectively.
MF - MQ
RB =
MQ

1 n
( Fi - Qi )
2

n i =1
RRMSE =
MQ
Where, Fi=calculated discharge on ith day, Qi=observed discharge on ith day

107
1 n
M F = Fi
n i =1
1 n
MQ = Qi
n i =1
Where, MF=mean annual calculated discharge, MQ=mean annual observed discharge

Table 18: Results of Model Calibration


Low Flow High Flow
Dam Year
Obs(m /s)
3
Sim(m /s)
3
RB RRMS Obs(m /s)
3
Sim(m3/s) RB RRMS
) E E
1997 29.04 39.71 0.37 1.52 104.72 108.82 0.04 0.43
1998 102.98 88.25 -0.14 0.35 177.90 188.31 0.06 0.47
1999 66.22 71.70 0.08 0.54 135.63 119.18 -0.12 0.36
Saguling 2000 63.71 60.22 -0.05 0.63 111.63 117.56 0.05 0.30
2001 92.31 70.96 -0.23 0.56 144.98 138.58 -0.04 0.36
2002 37.33 49.25 0.32 1.30 157.59 178.25 0.13 0.40
2003 24.42 62.92 1.58 2.76 98.73 127.00 0.29 0.84
1997 99.36 75.66 -0.24 1.52 236.83 172.24 -0.27 0.90
1998 248.04 177.83 -0.28 1.31 412.44 282.38 -0.32 0.98
1999 208.52 145.05 -0.30 1.39 322.68 223.30 -0.31 1.20
Cirata 2000 190.63 135.65 -0.29 1.49 263.85 172.87 -0.34 1.02
2001 275.43 161.95 -0.41 2.35 346.14 249.48 -0.28 1.02
2002 141.10 92.85 -0.34 1.68 419.39 297.58 -0.29 1.04
2003 79.02 84.36 0.07 1.22 178.95 151.17 -0.16 0.85
1997 88.44 92.51 0.05 0.19 167.92 167.93 0.00 0.11
1998 203.64 225.34 0.11 0.18 229.06 246.37 0.08 0.09
1999 142.15 179.04 0.26 0.32 206.22 197.97 -0.04 0.26
Juanda 2000 162.21 173.18 0.07 0.15 159.28 171.48 0.08 0.14
2001 223.53 231.60 0.04 0.29 188.63 210.36 0.12 0.14
2002 133.56 139.34 0.04 0.24 281.49 271.48 -0.04 0.14
2003 122.49 83.66 -0.32 1.16 140.07 131.03 -0.06 0.33

108
Before model calibration, RRFS was run with selected parameters for warming-up process.
Then, the data from 1997 to 2003 are used for calibration. The calibration results using RB
and RRMSE with high flow (Jan to Apr) and low flow (May to Dec) of three dams inflow
are shown in Table 18. The calibration results in 2002 for Saguling, Cirata and Juanda dams
are shown in Figure 103, Figure 104, and Figure 105, respectively. To check veracity,
calibrated model was run with rainfall data from 2004 onwards. The results in 2004 and 2005
are shown Figure 106-Figure 109. The RB and RRMSE for high flow (Jan to Apr) and low
flow (May to Dec) of three dams inflow are shown in Table 19.

1000

100
Discharge(m /s)
3

10

Saguling OBS

Saguling COM

1
2002-01-01 2002-02-20 2002-04-11 2002-05-31 2002-07-20 2002-09-08 2002-10-28 2002-12-17

Time(day)

Figure 103: RRFS Modeling Calibration Results in 2002 Saguling Dam

10000

Cirata OBS

Cirata COM

1000
Discharge(m3/s)

100

10
2002-01-01 2002-02-20 2002-04-11 2002-05-31 2002-07-20 2002-09-08 2002-10-28 2002-12-17

Time(day)

Figure 104: RRFS Modeling Calibration Results in 2002 Cirata Dam

109
10000

Juanda OBS

Juanda COM

1000
Discharge(m /s)
3

100

10
2002-01-01 2002-02-20 2002-04-11 2002-05-31 2002-07-20 2002-09-08 2002-10-28 2002-12-17

Time(day)

Figure 105: RRFS Modeling Calibration Results in 2002 Juanda Dam

Figure 106: RRFS Modeling Verification Results in 2004 Saguling Dam

Figure 107: RRFS Modeling Verification Results in 2004 Juanda Dam

110
Figure 108: RRFS Modeling Verification Results in 2005 Saguling Dam

Figure 109: RRFS Modeling Verification Results in 2005 Juanda Dam

Table 19: Result of Error Analysis for Verification Period


Low Flow High Flow
Dam Year Low3 Flow
Obs(m3/s) Sim(m /s) RB RRMSE Obs(m3/s) Sim(m3/s) RB RRMSE

2004 36.33 51.50 0.42 1.28 125.58 138.76 0.10 0.44


Saguling
2005 49.79 55.84 0.12 0.52 164.36 154.55 -0.06 0.36
2004 138.09 96.40 -0.30 2.08 320.22 195.39 -0.39 1.25
Cirata
2005 173.61 120.37 -0.31 1.77 373.82 261.80 -0.30 1.02
2004 132.43 137.39 0.04 0.46 183.49 208.59 0.14 0.16
Juanda
2005 168.91 164.32 -0.03 0.26 256.87 240.24 -0.06 0.16

111
a. Runoff Ratio Estimation at the main Control Points
Based on the observed data and simulation results from 1997 to 2005, the runoff ratios at the
main control inflow points were estimated as shown in Table 20. The results in the form of
histogram are also presented in Figure 110 and Figure 111 for Saguling dam and Juanda dam,
respectively. In most cases, the runoff ratios of simulation results are higher than those
estimated from the observed data.

Table 20: Runoff Ratio of Main Control Points in CRB


Saguling+Cirata Juanda
Year
Observed RRFS Observed RRFS

1997 0.61 0.69 0.55 0.58


1998 0.76 0.77 0.53 0.59
1999 0.72 0.73 0.48 0.56
2000 0.74 0.74 0.66 0.72
2001 0.87 0.77 0.62 0.67
2002 0.68 0.73 0.62 0.64
2003 0.42 0.67 0.34 0.28
2004 0.68 0.72 0.48 0.53
2005 0.73 0.74 0.55 0.55
Ave 0.69 0.73 0.54 0.57

Figure 110: Yearly Histogram of Runoff Ratio in Saguling and Cirata

112
Figure 111: Yearly Histogram of Runoff Ratio in Juanda

4.3.2 Simulation in the Canals Considering Water Allocation


a. Canal Structure and Water Allocation
In Jatiluhur Dam of central CRB, Curug weir is installed to supply domestic and industrial
water for metropolitan area and agricultural water for farming fields. The West and East
Tarum Canals are connected to this structure as the water supply canals. The schematic
diagram of water availability and allocation in CRB is shown in Figure 112 and the number
in the colored box represents daily inflow and water allocation, with values at each station
being the inflow and allocation on September 2 2009 as an example. The number in yellow
box represents inflow amount into the canal from mainstream. The number in gray box near
three dams represents inflow amount of Dam while the number in blue and pink box near
canal shows water supply and water use such as domestic, industrial, agricultural, and return
flow.

Figure 112: Water Availability and Distribution Schematic in CRB


113
b. RRFS Simulation considering West and East Tarum Canals
As mentioned in previous section, the capacity of expanded RRFS runoff simulation in whole
CRB was evaluated considering the contribution of runoff to the West and East Tarum Canal.
The WTC simulation schematic diagram of I-region is shown in Figure 113 and there are
three adjacent hydraulic structures to the WTC such as Bekasi, Cikarang, and Cibeet weirs
making direct impact on the runoff of the WTC. The colored sub-basins in Figure 113
correspond to the drainage basins directly contributing to the inflow into Bekasi, Cikarang,
and Cibeet weirs. Figure 114, Figure 115, and show the simulation results of three weirs
inflow during 2001 and 2006 by hydrographs and hyetographs.

Figure 113: WTC Simulation Schematic Diagram

114
(a) 2001-2003

(b) 2004-2006

Figure 114: Simulation Results of Bekasi Weir Inflow

115
(a) 2001-2003

(b) 2004-2006

Figure 115: Simulation Results of Cikarang Weir Inflow

116
(a) 2001-2003

(b) 2004-2006

Figure 116: Simulation Results of Cibeet Weir Inflow

117
The ETC simulation schematic diagram of J-region is shown in Figure 117. There are five
adjacent hydraulic structures to the ETC such as Barugbug, Jengkol, Macan, Gadung, and
Salam Darma weir. As mentioned in previous section, Jengkol and Gadung weir located in
the northern of East Tarum Canal did not have any impact on the runoff of the ETC. Due to
this reason, the simulation was conducted focusing on the other three weirs inflows. The
colored sub-basins in Figure 117 correspond to the drainage basins directly contributing to
the inflow into Barugbug, Mancan and Salam Darma weirs. Figure 118 , Figure 119, and
Figure 120 show the simulation results of Barugbug, Macan, and Salam Darma weirs inflow
in 2004, 2005, and 2009 by hydrographs and hyetographs. The results are reasonably accurate
similar to the case of WTC with three weirs.

Figure 117: ETC Simulation Schematic Diagram


118
Figure 118: Simulation Results of Barugbug Weir Inflow

Figure 119: Simulation Results of Macan Weir Inflow

Figure 120: Simulation Results of Salam Darma Weir Inflow

119
4.4 Application of ESP Technique with PDF Ratio Method

4.4.1 Overview of ESP Technique


Ensemble Stream flow Prediction (ESP) is one of the representative probabilistic runoff
forecasting methods that generate many stream flow scenarios from all possible rainfall
scenarios using the deterministic rainfall runoff model (e.g. RRFS). In this method, the initial
conditions of a basin at the time of forecasting (e.g. soil moisture contents, water stage, etc.)
are combined with historical weather ensemble data that can be simulated in the future. That
is, this method attempts to obtain multiple runoff scenarios resulting from the application of
all possible rainfall scenarios to a deterministic rainfall-runoff model. The use of RRFS
enables the implementation of ESP quite easy through combination with probabilistic
weather forecasting. In this phase of DSS development, RRFS model including ESP has been
developed for rainfall-runoff forecasting in the CRB and calibrated and validated main
parameters using observed daily rainfall data. Schematic diagram of ESP estimating method
combined with RRFS is shown in Figure 121 and Figure 122.

Figure 121: Schematic diagram of RRFS-ESP System

Figure 122: Generation of ESP Scenarios

120
The key point of ESP method is the process for assigning a weight to each stream flow
scenario. The uncertainty of input data could be compensated through this process. One of the
simplest methods of weighting scenarios is assigning the same weight value to the all
scenarios. For instance, pre-mentioned 30 scenarios are imposed 1/30 probability per each
scenario. Advanced method of weighting data is imposing higher weight or probability to the
past year, which has similar hydrologic status with target year. If the weather outlook is given
in the form of probability forecast, two methods, Croley and PDF ratio, have been used to
estimate weighted value. Two drawbacks of Croley method are that a lot of weather
probability forecast is required to estimate weight and that all forecasted scenarios in the
same forecasting categories have the same probabilities because this method ignores the
distribution of climate variable. In other words, the method is discontinuous, which increases
or decreases the probability of scenarios equally to satisfy weather probability forecast
condition. On the other hand, in the PDF ratio method, continuous weight is estimated by
considering the distribution of climate variables. This method is also used to estimate weight
with only single weather probability forecast unlike Croley method.

4.4.2 Probabilistic Weather Outlooks and PDF Ratio Method


In the case of Korea Meteorological Agency (KMA), daily and bi-weekly probability
forecasts of 87 areas, categorized as A (Above), N (Normal), and B (Below), have been
provided through the KMA website since 2010. As an example, the A category probability
forecast in Daejeon is shown in Table 21 and the high, medium, and low probability
compared to the annual temperature and rainfall are 50%, 30%, and 20% respectively. The
result of applicable probability per category is stated in Table 22.
Table 21: Example of Probability Weather Forecasting
September, Daejeon, Korea
Temperature High
Probability Forecast 50% 30% 20%
Rainfall High
Probability Forecast 50% 30% 20%

Table 22: Interval Probability with respect to Weather Forecasting


High Medium Low Sum
A 50% 30% 20% 100%
N 30% 50% 20% 100%
B 20% 30% 50% 100%

Each of the above climate scenarios is modified through PDF ratio by applying former
climate data and used as input data of RRFS such as one probability forecast in Table 21.
Through this method, validated probability is estimated by each scenarios probability (1/N)
multiplied by weight value, and the weighted value is induced by following process.

121
If f ( y ) , f ( y ) are prior and post distributions of weather forecast, the expected value of
Y Y

function G ( y ) can be calculated as:

E[G ( y )] = G ( y ) fY ( y )dy (1)

E[G ( y )] = G ( y ) fY ( y )dy (2)

E[ ] is the expectation operator and equation (2) can be converted as:

fY ( y )
E[G ( y )] = G ( y ) fY ( y )dy (3)
fY ( y )

1 fY ( y )
qi = (4)
N fY ( y )

From equation (3), it is possible to confirm that the expected value of G ( y ) reflected by
f ( y ) (the post probability distribution) can be calculated by applying
Y

ratio f ( y ) and f ( y ) to f ( y ) (the prior distribution as shown in equation (4)). According


Y Y Y

to these results, validated probability, q can be calculated by using weighted value and the
i

ratio of f ( y ) and f ( y ) .
Y Y

For example, if the monthly rainfall follows log-normal distribution with average
m = 20.08mm and standard deviation s = 2.72mm , the prior probability distribution fY ( y ) at
any given point is shown in Figure 123. The position of quantile of accumulated probability
33.3 % and 66.7% are R33.3 = 13.0mm and R66.7 = 30.9mm , respectively, and these represent
upper limits of low and medium interval. The fY ( y ) and fY ( y ) represents of weather
forecast A, N, B, which are shown in Figure 124, Figure 125, and Figure 126, respectively.
The continuous ratios of fY ( y ) and fY ( y ) are also shown in these figures.

122
Figure 123: A priori Distribution of Rainfall

Figure 124: Distribution of Rainfall with Above Forecast

123
Figure 125: Distribution of Rainfall with Normal Forecast

Figure 126: Distribution of Rainfall with Below Outlook

124
4.4.3 Case Study of ESP Technique with PDF Ratio
In this analysis, the method of ESP-PDF ratio is applied for monthly inflow prediction at the
Saguling dam. The target period is from January to December 2005, and the rainfall scenario
during the target period is 30 years daily rainfall (1980 to 2009).

a. Nave Forecasting
After nave forecasting of meteorological characteristics such as monthly rainfall and inflow
in the target area, three intervals of high, medium, and low are set. Hydrological data used in
nave forecasting are 30 years monthly rainfall from 1980 to 2009 and 10 years monthly
inflow of dam from 1996 to 2005. The interval limit of monthly rainfall and inflow are shown
in Table 23 and Table 24, respectively. If the average rainfall is 150mm and inflow is
4000m3/sec at the Saguling dam in January, the rainfall is categorized as Low and the inflow
is categorized as Medium. In this analysis, the result of nave forecasting rainfall in Table 23
is used for combining weather forecast, and the result of nave forecasting inflow in Table 24
is used for the quantitative standard for reliability verification of forecasting system in the
ESP forecast process.

Table 23: Nave Forecasting of Monthly Rainfall

Saguling

R33.3 (mm) R66.7 (mm)

Jan 208.16 251.08


Feb 155.63 228.93
Mar 216.81 291.49
Apr 187.65 252.15
May 99.82 147.65
Jun 36.65 82.65
Jul 20.82 52.23
Aug 14.91 56.55
Sep 27.31 66.38
Oct 69.94 181.08
Nov 181.48 278.77
Dec 222.82 268.90

125
Table 24: Nave Forecasting of Monthly Inflow

Saguling

Q33.3 (m3 / sec) Q66.7 (m3 / sec)

Jan 3565.13 4224.54


Feb 3144.24 4029.50
Mar 3811.00 5055.29
Apr 3596.88 4810.65
May 1913.58 3390.13
Jun 882.23 1731.68
Jul 784.02 1196.38
Aug 255.10 523.39
Sep 291.84 846.04
Oct 337.86 1954.43
Nov 1325.72 4659.12
Dec 2275.49 3750.03

126
b. Forecasting by ESP Technique
ESP forecasting for the target period is implemented to compare with nave forecasting. The
main input for the rainfall scenario of RRFS is daily rainfall from 1980 to 2009, and the
parameters for initial conditions of the basin are set as of December 31 2004. The results of
simulated inflow scenario in Saguling in January 2005 are shown in Figure 127, and
accumulated probability of ESP forecasting scenario is shown in Figure 128. If the ESP
forecasting was not combined with any specific prior processing method, it is assumed that
the weighted values of forecasting flow per scenario in Figure 127 are the same as
accumulated probability values in Figure 128 or 50% of the values.

Figure 127: ESP Result of Monthly Inflow into Saguling Dam, Jan. 2005

127
.

Figure 128: ESP Probability of Monthly Inflow into Saguling Dam, Jan 2005

128
c. Forecasting Renewal by PDF ratio Method
To conduct the prior process of ESP forecasting flow scenario by using PDF ratio method,
weather forecast in the form of probability forecast is required. Unfortunately, this
information for the interested basin is not available. In this analysis, the probability forecast
was calculated by observed rainfall in the target month and the forecast interval as
summarized in Table 23. The observed monthly rainfall in the Saguling dam is shown in
Table 25. The weather forecast in the target month is determined by the analysis, where the
target months rainfall will fall on forecasting interval in Table 23. For instance, the observed
rainfall in January 2005 is 209 mm and it is between R33.3 (208.16mm) and R66.7 (251.08mm),
then the weather forecast in January 2005 is N (Normal). The monthly weather forecast
results are shown in Table 26.

Table 25: Observational Rainfall by Month


Month Rainfall(mm)
Jan 209.00
Feb 326.50
Mar 250.00
Apr 176.50
May 78.50
Jun 111.00
Jul 58.00
Aug 59.50
Sep 68.50
Oct 109.00
Nov 182.50
Dec 223.50

129
Table 26: Weather Forecasts by Month
Month Weather Outlook
Jan N
Feb A
Mar N
Apr B
May B
Jun A
Jul A
Aug A
Sep A
Oct N
Nov N
Dec N

Monthly probability distribution goodness of fit test for former rainfall data is required to use
PDF ratio method. However, in this analysis, goodness of fit test is not implemented as the
consistency, and the weighted value are calculated by assuming that all data are log-normally
distributed. In other words, if the verified former rainfall data distribution fY ( y ) and
fY ( y )
probability forecast distribution are the same as the log-normal distribution and only
f ( y)
average and standard deviation are changed, the ratio of fY ( y ) and Y in Figure 124 to
f ( y )
Figure 126 are calculated by equation (4). The fY ( y ) and Y in the Saguling dam, for
the months of January (Normal), February (Above), and April (Below) are shown in Figure
129 to Figure 131, respectively. The probability density function drawn by the thick line
represents weather forecast.

130
Figure 129: Saguling January Rainfall PDF with Normal Weather Forecast

Figure 130: Saguling February Rainfall PDF with Above Weather Forecast

131
Figure 131: Saguling April Rainfall PDF with Below Weather Forecast

d. Quantitative Analysis of Prediction Results


The accuracy of monthly inflow prediction was analyzed with monthly-observed inflow by
ESP and PDF ratio methods. In deterministic model, the accuracy can be evaluated by
comparing observed data and with predicted data which is provided as a single value.
However, it is impossible to evaluate the results of ESP method application of model by
comparing with observed data because ESP method in this study predicted outlooks data
based on as various scenarios forms. In this case, a Prediction score can be used to evaluate
the accuracy of prediction. Therefore, the prediction score represents prediction probability in
the interval of observed flow occurrence. If nave prediction results are used, every monthly
prediction score will be calculated as 0.333. According to this logic, the accuracy of renewed
scenario per method will can be evaluated from prediction score estimation.

The accumulated probability of Q and Q in Table 24 is drawn in Figure 132 and Figure
33.3 66.7

133, respectively. The two dashed lines represent the accumulative probability of 33.3% and
66.7%, respectively, and blue square dots represent monthly observed inflow.

Monthly prediction score per ratio estimated from the result of Figure 132 and Figure 133 are
summarized in

132
Table 27. In here, one of the remarkable point is that the predicted average score of the ESP
ratio is higher than 0.333. Overall, through this result, the accuracy of the prediction result by
ESP ratio is higher than that by nave prediction, in other words that is, the application of
ESP system developed in project this study must be reasonable. The prediction score of PDF
ratio is also higher than that of ESP ratio. As a result, it can be concluded that the accuracy of
prediction can be improved with renewed prediction result by ESP ratio using probability
weather forecast.

Figure 132: Cumulative Probability of ESP Scenario for Q and Q


33.3 66.7

Figure 133: Cumulative Probability of PDF ratio Scenario for Q and Q


33.3 66.7

133
Table 27: Prediction Score by ESP and PDF ratio
ESP PDF
Jan-05 0.14 0.14
Feb-05 0.55 0.57
Mar-05 0.67 0.68
Apr-05 0.70 0.62
May-05 0.52 0.32
Jun-05 0.25 0.07
Jul-05 0.23 0.36
Aug-05 0.46 0.55
Sep-05 0.35 0.45
Oct-05 0.40 0.65
Nov-05 0.61 0.87
Dec-05 0.18 0.24
average 0.42 0.46

134
4.5 Results

In this study project, RRFS model for the of CRB area has been was built constructed and the
application was reviewed by implementing basic probability flow forecast simulation. The
C-region connected main three dams were divided into 14 sub-catchments and schematic
diagram was developed considering the role of the three main dams, canals and water usage
(agriculture, industry, and household). Through the land use and soil map of CRB, main
parameters were calculated for each sub-catchment such as Soil Moisture Index-Runoff
Percent (SMI-ROP), Baseflow Infiltration Index- Baseflow Percent (BII-BFP), and Surface-
Subsurface Separation (S-SS) input data were prepared.

Through this conceptual model of CRB-RRFS, the relative bias and relative root mean square
error of high and low runoff in three dams and the appropriateness of runoff area was
reviewed using observed. The above data between from 1997 and 2005 was simulated for
verification and the simulated observed value was found to be appropriate. The CRB-RRFS
in C-region was expanded to West Tarum Canal and East Tarum Canal area and the
simulated results of expanded diagram showed high correlation to observations.
The appropriateness of runoff prediction is also was analyzed with ESP method, which is . It
was implemented in this project study not only for future runoff prediction with past rainfall
scenario analysis, but also for improvement of runoff prediction through comparative analysis
of ESP and PDF ratio using ESP connected to probability weather forecast provided by the
Meteorological Agency. The accuracy of runoff prediction with ESP is higher than nave
prediction with past data only. Besides, the accuracy was improved by applying weather
forecast pretreatment. Hence, monthly runoff prediction through ESP method is appropriate
and it will be necessary to conduct do further research to verify the application of ESP
method for expanded basin and for additional hydrological analysis.

The developed rainfall-runoff model developed for the CRB area using RRFS will provide
the basic input data such as runoff data for each sub-catchment and at main control points to
for water allocation model to be developed in the next phase., KModSim , such as runoff data
for each sub-catchment and main control points. Additionally, CRB-RRFS for the mid- and
long-term prediction RRFS based on the ESP-PDF system will play an important role in risk
assessment and probability analysis for dam operation and water allocation planning.

135
5. Capacity Building and Institutional Arrangement

For the successful development and implementation of the Decision Support system (DSS) in
the Citarum River Basin (CRB), consultative process that brings all the stakeholders on board
to address their specific needs is very important. The followings are the objectives of the
stakeholder consultation process which scopes out the work of capacity building and
institution development:
Identify and meet with all hydrological and water resources data collection agencies
operating in CRB
Identify how their existing systems and data can cross-communicate or be integrated
in a central system
Meet regularly with stakeholders and roadmap consultants to review ongoing and
planned IWRM activities
Investigate opportunities to create synergy among stakeholder organizations
Collect and disseminate information relevant to the ongoing roadmap activities and
DSS among stakeholders
The list of consultation meetings with stakeholders is summarized in Table 28.

Table 28: Summary of Meetings


Date/ Location Title Agenda
20 Sept 2010 / PJT-II Scope of work & objective of DSS
Kickoff Meeting
Purwakarta for IWRM in CRB
29 Sept 2010 / PJT-II Bandung Technical aspect of DSS
Technical meeting
office development
Introduction of K-water to BPLHD
30 Sept 2010 / BPLHD office Introduction of K-water DSS
West Java
19 20 Oct 2010 / Balai Data &
Information collecting for database Data collection
Information, PWRS
Explanation & presentation of
21 Oct 2010 / PJT-II Purwakarta Information collecting for database
existing DSS in PJT-II
Explanation and presentation of
22 Oct 2010 / BPLHD office Information collecting for database
existing DSS in BPLHD
26 Oct 2010 / Akmani Hotel, Review draft Memorandum of
Wrap up ADB 4th Review mission
Jakarta Understanding
Information collecting for Hydrological data collection, data
2 Nov 2010 / BMKG Bogor
hydrology database handling & database
WTC water balance & water Water quality modeling, GIS &
quality modeling spatial planning
4 Nov 2010 / Package B1 office
Information collecting for Ribasim
Information collecting for
Hydrology and water quality
9 Nov 2010 / PusAir office West hydrology, water quality & database
Java Communication & database
Information collecting for database
Informatics Services office
and publication of data & Data collection
information using electronic device

136
Discussion on Package D
14 Dec 2010 / PJT-II Purwakarta Inception Workshop
Inception Report
1 Feb 2011 / Bandung K-water Coordination meeting between JSM 2.2 model result in
PMO office Package D and B2 component D, DSS
Role of each agency in process of
2 Mar 2011 / PJT-II Bandung
Initial inter-agency meeting DSS development, mobilization of
office
counterparts
21 Mar 2011 / BBWS Citarum, Required support from counterpart
Counterpart meeting
Bandung on DSS
Required support from counterpart
1 Apr 2011 / PusAir, Bandung Counterpart meeting
on DSS
23 May 2011 / Package B office,
Coordination meeting
RCMU office
Synchronizing the hydrology
8 June 2011 / Package B office Hydrology synchronization
analysis
Progress of DB management,
21 June 2011 / Horizon Hotel,
Midterm Workshop institutional development & RRFS
Bandung
development until June 2011
Action plan for accelerating the
21 June 2011 / PMO K-water, National Policy for SIH3, business
Midterm Workshop follow-up
Bandung plan, institutional capacity survey
and rationalization of station.
22 June 2011 / PMO K-water,
DSS Software training DSS Software Training
Bandung
Synergizing the preparation of
national policy on hydrology,
22 June 2011 / DWRM Office,
National Policy on SIH3 hydrogeology, hydro-climatology
Jakarta
system information (SIH3) and
budget securing for next phase
Synergizing the preparation of
national policy on hydrology,
22 June 2011 / NWRC Office,
National Policy on SIH3 hydrogeology, and hydro-
Jakarta
climatology system information
(SIH3)
Regular meeting of Forum
5 July 2011 / PLTA Bengkok
Coordination of Water Governance Presentation of DSS Project
office, Bandung
Operation Secretariat (SPKTPA)
Instruction and demonstration on
Workshop on Data Population and
12 July 2011 / PMO K-water, data import wizard, and knowledge
Knowledge Sharing for
Bandung sharing on DSS management and
implementation of DSS
operation.
15 July 2011 / PLTA Saguling, IP-UP Saguling / Member of
Presentation of DSS Project
Cioray, Rajamandala SPKTPA
20 July 2011 / BBWS Citarum, Coordination with Head of BBWS
Brief Presentation of DSS Project
Bandung Citarum
Summary of DSS Project,
27 July 2011 / BBWS Citarum,
Coordination with BBWS Citarum Requirement for DSS operation,
Bandung
demo of user interface.
Discussion on Draft
26 October 2011 Consultation meeting with DWRM Recommendation from DGWR to
NWRC
Discussion on data base & GIS
24 November 2011 Consultation meeting with PJTII
servers locations.
Consultation meetings with Dinas
12,13,14,15 December 2011 PSDA Jabar, PusAir, BPLHD Discussion on data sharing concept
Jabar, and BBWS Citarum
Consultation meeting with BBWS Discussion on data base & GIS
February 2012
Citarum servers locations.

137
5.1 Summary of Stakeholder Consultations

Among the consultation meetings, significant consultation sessions, trainings and meetings
are summarized as follow;

5.1.1 Balai Data and Information and Balai PSDA Citarum, PWRS
Discussion about data collection and database of Balai Data & Information and Balai PSDA
Citarum and field visit conducted to see examples of river gauging and rainfall gauging
stations on 19-20 October 2010. The key points raised by the chairman during the discussion
were as follows; the software of database was provided by Sub Directorate of Hydrology and
Water Quality, DWRM-DGWR, which was modified to become Provincial Hydrology Unit
(PHU). Based on the official agreement between BBWSC and Dinas PSDA the operation and
maintenance of most hydrological stations within Citarum River Basin would be handed over
to BBWSC starting at the beginning of 2011.

5.1.2 PJT-II
Several discussions with PJT-II regarding information collection for database were held from
21 October 2010 up to November 2011 in PJT-II Jatiluhur office as well as in PMO Office in
Bandung. Remarks from the chairman of PJT-II mentioned human based communication still
being used for most equipment (telephone, fax, sms and email). Urgent development and
improvement of communication system is required. A lot of data from PJT II was being used
as basic database for DSS design format and now has been put in place as database in the
Server of Database.

5.1.3 BPLHD
Several discussions from 22 October 2010 up to January 2012 were led by Chairman of
BPLHD and Deputy Chairperson and from these discussions, produced several key points
such as sustainability of implementation of CRB DSS, which is essential, and that BPLHD
will support K-water in developing this DSS by providing staff members as counterparts. The
format of water quality data monitoring from BPLHD will be used as a standard for the water
quality database in DSS design.

5.1.4 BMKG Bogor


The meeting with BMKG Bogor regarding hydrology data collection, held on 02 November
2010, was attended by head of Bogor Climatologically Station and his staff. The whole
meeting was centred on the mission of providing forecast for rainfall, weather and
climatology to other institutions and the community. The Head of BMKG explained that
collecting data from the observers was still done through fax, email, telephone, and post mail
and that there are just 2 automatic rainfall recorders located in Geophysical Bandung and
Geophysical Lembang office. However, all data collected was stored and processed in Bogor
office. In addition, all institutions using data information from BMKG should cite the source
of data. The hydro-climatology data from BMKG has been transferred from data file of
Package B1 Consultant of 6 Cis TA-7189 to the database of the DSS.

138
5.1.5 Water Balance and Water Quality Modeling, RIBASIM
The meeting about hydrological data, water demand projection, spatial planning and satellite
images, water quality modeling, and GIS layers was held on 4 November 2010, in Package
B1 Consultant office, Jakarta. On that day, there was another discussion about collecting
RIBASIM information in Package B1 office, Jakarta. RIBASIM models main purpose is
simulating water balance within 6 Cis river basin territory for period 2010, 2010-2030,
2030-2050 for drafting POLA (mid/long term) in 6 Cis territory.

5.1.6 PusAir
Meeting was held on 9 November 2010, in PusAir office, Bandung. The Head of
Experimental Station for Hydrology and Water Allocation mentioned his concern for the
mission of PusAir, which is to collect data from hydrological data collection agencies in
Indonesia, including Balai PSDA Citarum, BBWSC and Saguling reservoir (country level).
K-water has collected all data from PusAir by official letter via the Head of PusAir. PusAir
considers web-based data sharing management to be beneficial for integrated water resources
management not only in Citarum River Basin but also in all river basins throughout Indonesia.

5.1.7 West Java Communication and Information Agency


The meeting regarding database and publication using electronic devices in West Java
Communication and Information agency was held on 9 November 2010. Head of the agency
mentioned that Diskominfo would support development of CRB DSS in line with its task to
facilitate and control communication and informatics post, telemetric and electronic data
processing.

5.1.8 National Development Planning Agency (BAPPENAS)


The intention of the meeting on 11 January 2012 was to have a discussion with Director of
Water Resources and Irrigation, BAPPNEAS regarding institutional setup and data sharing
management in DSS for Citarum River Basin. The Director of WRI has provided guidance
for the workshop in February 2012 on Data Sharing Management and has encouraged the
West Java Provincial Administration to take more active roles in Citarum integrated water
resources management through Team for Synchronizing the Planning and Optimization of
Institutions Cooperation in Integrated Citarum River Basin Management or SPOKI Team
established by Governor of West Java. (Decree No.050.05/Kep.1589-Bapp/2011 on
December 5, 2011)
A complete summary and description of all the meetings is given in Appendix 8.

139
5.2 Counterpart Activity

The following section provides details of interaction and training involving counterparts from
agencies.

5.2.1 Counterparts Training


Several workshops and a training have been conducted so far including Inception Workshop,
Midterm Workshop, Legal Framework Workshop, Data Sharing Management Workshop,
Final Workshop, counterpart training in Korea and main meeting facilitated by K-water.

5.2.2 Training Program at K-water


Training of 7 selected counterparts from various agencies was held in Korea from 10 - 14
May 2011 which focused on database and RRFS developed by K-water for DSS project. This
training was very important for DSS management in the future as it educated the operators
and staff members of each agency to commit themselves to DSS operation and maintenance.
Workshop regarding the database and DSS development on monitoring and hydrology
analysis in K-water clearly presented how sophisticated and well managed the DSS would be.

Table 29: List of Trainee Selected from DGWR


Institution Name Position
Directorate of Water Briliyan
Staff of the Sub Directorate for Hydrology &
Resources Parmawati, ST,
Water Quality, Directorate of WRM
Management MPSDA.
Staff of the Sub Directorate for Data and
Directorate of Bina
Wahyudin, ST. Information, Bina Program, Directorate of
Program
WRM
Provincial Monitoring
and Environment Computer Operator in Sub Directorate for
Windi Dwi
Pollution Monitoring & Environment Pollution,
Windiandini
Agency (BPLHD) BPLHD West Java
West Java
Reni Mayasari, Head of Division for Program, Planning
Perum Jasa Tirta II
ST, M.Si. Bureau, PJT-II
Dani Hamdan, ST, Head of Section for General Planning &
BBWS Citarum
M.Sc. Program, BBWSC
Balai Data dan Staff of Information System for Water
Adi Primadika
Informasi of West Resources, Balai Data and Information, Prof.
Diaz, S.Si.
Java Province West Java
Rebiet Rimba Staff of R&D, Experimental Station for
PusAir
Rinjani, ST Water Environment, PusAir

140
Figure 134: Seven Trainees in Korea, 10-14 May 2011

Table 30: Training Agenda in Korea, K-water Headquarter, Daejeon

Monday (May 9) Departure from Jakarta


Tuesday (May 10) Arrival at Incheon Airport
Wednesday (May 11) K-water Head Quarter tour & Workshop
Thursday (May 12) Field trip (Geumnam Weir, Daecheong dam, Water Treatment Plant)
Friday (May 13) Field trip, Kyung-in Ara Waterway, Cheong-Gye Stream
Saturday (May 14) Wrap up meeting, Departure from Korea

141
5.3 Institutional Arrangement

5.3.1 Current Status of Institutions in Water Resources Data Management in Citarum


Basin

a. Institutions and Their Mandates in Water Resources Data Management


The governmental institutions, their mandates and roles in water resources data management
are presented in Table 31.

Table 31: Legal Mandates and Role in Water Resources Data Management

Institutions Name Legal Mandates Main Role

National Water Resources Council


Law No.7-2004 on Water Resources
(Dewan Nasional Sumber Daya
Gov. Reg. No.42/2008 on Water Manager of national water
Air) is a national apex body who
Resources Management; resources management
main duty is to assist President in
Presidential Regulation No.12-08 policy development
national water resources
Presidential Decree No.6-2009
management policy
Law No. 7/2004 on Water Resources
Gov Reg. No.42/2008 on Water
Resources Management
Balai Besar Wilayah Sungai
MPW Decree:
Citarum / Citarum River Basin
No.11A/PRT/M/2006 Manager of hydrological
Organization which has its mandate
No.12/PRT/M/2006 data in the Cimanuk Basin
from Ministry of Public Works and
No.26/PRT/M/2006
DGWR
No.23/PRT/M/2008
DGWR Decree:
No.42/KPTS/D/2007
Law No.7/2004 on Water Resources
Manager of groundwater
Gov Reg No.43-2008 on Groundwater
Badan Geology/Dinas Energy and (quantity and quality) data
Gov Reg 82/2001 on Water Quality
Mineral Resources / Dinas ESDM in west java basins
Management
West Java which has its mandate including Bandung and
Min ESDM Reg No.18/2010 on
from Governor of West Java Sumedang groundwater
Organization and Governance of
basin
MESDM
Manager of meteorology,
Badan Meteorogy, Climatology and KEPPRES no.46 & 48 year 2002 on climatology, and
Geophysis Bogor which has its Position, Tasks and Organization of geophysics data in West
mandate from the President BMG Java area covering
Citarum River Basin
UU.No.23/1997 on Environment
Badan Environment Protection and Protection and Management Manager of water quality
Management West Java (BPLHD UU. No.5/1990 Biodiversity and manager in West Java
jabar) which has its mandates from Ecosystem Conservation; covering Citarum River
the Governor of West Java UU.No.32-2009 on Environment Basin
Management and Protection
UU.No.7-2004 on Water Resources;
Manager of irrigation area
Dinas Water Resources West Java UU.No.32-2004 on Regional
in West Java which is the
which has its mandates from the Government;
biggest user in Citarum
Governor of West Java PP.No.38-2007 on Distribution of
Basin
Governmental Administration Affairs

142
Water Distributor in
PJT-II the state own corporation
PP. No.7-2010 on Establishment of PJT- Citarum basin which is the
which has its mandates from the
II biggest user for water
Government of Indonesia
supply and irrigation
UU.No.24 2010 on Information
Dinas Communication and Manager of west java hub
Transparency
Information West Java has its for disseminating all data
PERPRES No.9 tahun 2005 on Position,
mandates from Governor of West and information with in
Tasks dan Organization of Cabinet of
Java West Java area
GOI
UU.No.4-2011 on Geo-Spatial
Agency for National Mapping Information Coordinator and Regulator
Coordination/BAKOSURTANAL KEPPRES No. 178-2000 on of spatial mapping with in
has its mandates from Government Organization and Governance of Non the whole Indonesia
Ministry
Manager of conservation
UU. No. 19/2004 and UU. No.41/1999
Balai of River Basin Management in Citarum River Basin has
on Forestry
has its mandates from Ministry of also collected some
UU. No.18/2004 on Plant Estate
Forestry sedimentation and surface
(Perkebunan)
erosion data
UU. No. 19/2004 and UU. No.41/1999 Manager of spring water in
State Own Company IX West Java /
on Forestry forest area in West Java
PERHUTANI has its mandates
UU. No.18/2004 on Plant Estate including in Citarum River
from Ministry of Forestry
(Perkebunan) Basin

The other institutions that have indirect relations with water resources data management is
summarized in Table 32 and these governmental institutions within Government of Indonesia
administration system could be laid out as the Figure 135.

Table 32: Legal Mandates and Role in Other Institutions


Legal
Institutions Name Main Role
Mandates
State Own Company of Java Bali
Main user of water for Cirata
Electricity has its mandates from
N/A hydro power in Citarum River
Ministry of Energy and Mineral
Basin
Resources
State Own Company of Indonesia Main user of water for Saguling
Power has its mandates from Ministry N/A hydro power in Citarum River
of Energy and Mineral Resources Basin
Water Supply District Own Company User of Citarum water
of Karawang, Purwakarta and N/A managing water quality for
Bandung their own purposes
User of Citarum water
Water Supply City Own Company of
N/A managing water quality for
Bandung
their own purposes
User of Citarum water
Water Supply Provincial Own
N/A managing water quality for
Company of DKI Jakarta
their own purposes
User of Citarum water
Some large textile industries
N/A managing water quantity and
company in Bandung District
quality for their own purposes

143
PRESIDENT OF
INDONESIA

BMKG / OTHER MIN MINISTRY OF P MINISTRY OF MINISTRY OF


METEOROLOGY, CLIMAT STATE OWN
OLOGY & GEOPHYSICAL
ISTRIES UBLICK WORK MINING & E
ENTERPRISES
INST NERGY

BOGOR CLIMATOLO DGWR PJT - II PLN / STATE ELECT


GICAL STATION RICITY COMPANY

MONTHLY BULLETIN OTHER PusAir DIRECTORATE BBWS WATER SUPPLY SAGULING & CIRATA
OF RAINFALL DIRECTORATES WRRD CENTER OF WRM CITARUM FOR VARIOUS NEEDS HYDROPOWER
FORECASTING

SUB DIRECTORAT ELECTRICITY


E OF HYDROLOG IWRM HYDROPOWER

GOVERNOR OF GOVERNOR OF
JAKARTA
JAKARTA
METROPOLITAN
10 DISTRICTS & MUNIC
WEST JAVA PROV
METROPOLITAN DRINKING WATER IPALTIES GOVERNME
NTS IN CRB
BAPPEDA BPLHD DWRS
BAPPEDA / PR BPLHD / PWRS COOMUNICATION & IN MINING PAS OTHER OF
OV PLAN BRD FORMATION OFFICE
ENV PRO OFFICE FICES

INTER-AGENCY COO WATER WATER


INTER-AGENCY COO WATER WATER FACILITATE & CONTRO GROUND ON FARM RDINATION & BUDG
POLLUTION RESOURCES
RDINATION & BUDG L OF COMMUNICATION ET ALLOCATION
POLLUTION RESOURCES WATER IRRIGATION CONTROL MANAGEMENT
ET ALLOCATION &
CONTROL MANAGEMENT INFORMATICS CONTROL SERVICE

DAS OTHER MINING


OFFICE
Agencies providing input data to development of WIMS OFFICES

ON FARM GROUND
IRRIGATION WATER
SERVICE CONTROL

Figure 135: Citarum River Basins Stakeholders in Administration System of Indonesia Government

144
b. Current Status
Currently, PJT-II, DPSDA Jabar, BPLHD Jabar, BMG Bogor and BBWS Citarum are
carrying out data and information management of hydrology (rainfall, runoff, and
climatological data) and water quality. It seems that PJT-II and DPSDA are more active in
managing data and information of hydrology.

According to Government Regulation No.7/2010 on PJT-II article 4 items 2 (f) and 2 (g), the
task of PJT-II is monitoring and evaluating water quantity and quality of water source within
their jurisdiction and also to disseminate the results to beneficiary of water resources,
community, and managers of water resources. PJT-II also has responsibility on data and
information of hydrology and water quality considering its task as operator of water resources
management.

DPSDA Jabar is a water resources management agency under Governor of West Java which
is responsible for monitoring and evaluating water quantity and quality of water resources in
their jurisdiction. Historically, DPSDA Jabar has carried out hydrology related activities in
the entire province of West Java.

According to the Water Law (UU No.7/2004 on Water Resources), BBWS Citarum has
authority from Central Governments descendant delegation to manage all aspects of water
resources management in Citarum basin. So far, it is under jurisdiction of BBWS Citarum.
Jurisdiction of PJT-II on hydrology is still useful for their operational management, while
jurisdiction of DPSDA on hydrology in Citarum has been vague. Currently, MOU of
hydrology management between DPSDA Jabar and BBWS Citarum is in place, however, not
effectively implemented.

5.4 The Institutional Development of DSS Project for IWRM in Citarum Basin

5.4.1 Scope of Works


The scopes of work for institution development inter-alia are as follow:
Review and analyze current institutional arrangements for data sharing, collaboration,
staff allocation and prepare recommendations for improvement;
Provide institutional recommendations for the long term development of the DSS;
Facilitate the implementation plan to improve the existing data collection, storage, and
sharing procedures for the agencies related to the Citarum River Basin;
Assess the past, current and projected expenditure of the data collection agencies and
assist integration, rationalization and harmonization of their future development plans
for the data collection infrastructure and programs;

145
5.4.2 Regulations
It is recommended that regulations under Government Regulation or Peraturan Pemerintah
should be provided. In these regulations, the following critical issues must be addressed:
Synergy in each agencys roles in water resources data management with overlapping
current task and function;
Sustainability of budget resources
Sustainability of staffing system in agencies;
Level of human resources skill in terms of managerial and technical skills;
Construction of wireless/man less/gateway technology infrastructure, which has
interoperability capacity for collaborating and sharing information from all different
protocols provided by different water resources data management centers.

After implementation of the regulation above, Ministerial Regulation and/or Ministerial


Decree and/or Memorandum of Understanding among the main stakeholders, which contain
implementation guidelines and/or manuals that are more technical and operational rules, shall
be developed. It is important to note that only these types of regulations would have legal
public binding.

5.4.3 Human Resources


It is recommended that human resources development in a real action plan be built based on
the existing condition. Training, exercise and comparative study, manual and guideline
provision are few of many ways of achieving human resources development. More than that,
the structure of organizations shall include the working unit with persistence rank which
looks after the entire water information management system (WIMS).

5.4.4 Technology
The technology should be improved and maintained with proper human resources and budget
allocation every year. The existing technology should be upgraded using affordable and
applicable new technology.

5.4.5 Fund
It is recommended all main stakeholders construct business plan regarding the mandates
borne by each institution for the sake of WIMS operation. To ensure that this action plan can
be sustainably maintained, it is recommended each Ministerial Regulation include the legal
document as instruction.

5.4.6 Working Environment


There is no progress under a working environment that is not supportive and encouraging.
Commitment and knowledge are the two pillars to build leadership upon. It is recommended
leadership training and exercise be provided for top and mid-level managers of each
institution that manage water data and information.
146
5.4.7 Recommendations on Initial Design of Institutional Setup for DSS
Implementation

Figure 136: Initial Design of Institutional Setup for DSS Implementation

In the implementation of DSS, currently PJT-II, BBWSC, PusAir, DPSDA, DESDM, BMKG
Bogor, Balai DAS Citarum, PERHUTANI, IP, PIJB and BPLHD are identified as data
providers and Citarum River Basin (CRB) as main end user. All agencies (data providers)
have to carry out data validation independently before input to the DSS. BBWSC and
DPSDA will utilize the DSS to publish Year book of hydrological data. PJT-II will utilize
the DSS for the operation of reservoir, weir, and water demand estimation.

Figure 137: Institutional Framework for DSS Implementation

BBWSC as the administrator has authority to read, write, and delete data in order to maintain
the integrity of the database. PJT-II has authority to read, write, and delete for operating
water resources facilities such as dam, weir and intake (Input of annual dam operation plan).
DPSDA and BPLHD have authority to read while collecting data and validating collected
data. PusAir, BMKG and other users would have a role only as an end user who can search
all of the data in DSS. This is presented in Alternative No.1 in Figure 138.
147
5.4.8 Collaboration Plan between Institutions

Synchronize Synchronize
Data Data

Use RRFS Use RRFS

Figure 138: Anternative No.1: Collaboration between Institutions

Synchronize Synchronize
Data Data

Use RRFS Use RRFS

Figure 139: Anternative No.2: Collaboration between Institutions

Considering the effectiveness of information consumption by the public, DPSDA and


BPLHD should re-arrange the data into a more easy-to-comprehend information and readable
formats (map as an image, low bandwidth consumption) for the general public. Nevertheless,
regarding data transparency, not all of the data is published for public consumption as noted
by representative of Dinas Kominfo (Mr. Purnomos) in his statement during the Technical
148
Meeting. Moreover, there is a matter of low bandwidth consumption. To accommodate this
situation, the Alternative No.2 was preferable for the Stakeholders in the Workshop that was
held on February 1, 2012.
5.5 The Strategic Issues of Institutional Development

The main current policies are:


The water resources information comprises of information on the hydrological, hydro-
meteorological, and hydro-geological information, water resources and water
resources infrastructure, water resources policies, water resources technology, the
ecology and environment of the water sources and the surrounding areas, and the
social economic and cultural activities of the community related to the water sources
of concern. The water resources data and information management is spread among
public institutions and managed by various institutions based on their legal mandates.
The water resources data and information management could be done through
collaboration among those institutions. However, accuracy and validity of the data and
information remain the responsibility of the owner of data according to the mandates.
The data and information should be accessed by all parties that are concerned with the
water resources. Therefore, the data and information sharing for a river basin is
inevitable.
The Governor of West Java has issued a decree No.050.05/Kep.1589-Bapp/2011 for
establishment of a team for Synchronizing the Planning and Optimization of
Institutions cooperation in Integrated Citarum River Basin management or SPOKI
team at 5 December 2011. This team is chaired by the Secretary of West Java
Province and the Chairman of BAPPEDA Jabar, in charge of daily Secretary Duty.
The team has several duties but among those, two are very important for the
development of cooperation between Institutions:
Coordination between the organizations of the regional and related institutions at
Central, Provincial and Regency / City Level.
Synchronizing planning and optimization of institutional cooperation in handling of
the integrated Citarum river area with good regional annual, medium term and long-
term development plans..

The strategic issues that could be derived from the collected policies above are:
Design of wireless/man-less/gateway information technology infrastructure, which has
interoperability capacity, for collaborating and sharing information from different
protocols provided by various water resources data management centers.
The discrepancies among the institutions interest should be eliminated and objectives
streamlined into one goal i.e. CITA CITARUM the vision of west java people for
Citarum river. In this case, the importance of role of West Java Provincial
Government through SPOKI team should be emphasized.
Synergy in each agencys roles in water resources data management with overlapping
current tasks and functions into integrated data sharing management;
Sustainability of budget resources and staffing system in agencies;
Level of human resources skill-set, especially managerial and technical skill;
149
For the institution to achieve optimal results, capacity study, analysis, and two inter-agencies
workshops were conducted to find and formulate the national policies on water resources data
information system management. These policies have been worked out by NWRC and
thereby accelerate and intensify the communication among the agencies who are managing
the water resources data and information. The second workshop was to agree upon the
concept of data sharing management in DSS implementation for IWRM in Citarum River
Basin. The findings of two inter-agency workshops for project (up to 29 February 2012) are
summarized below:

5.5.1 Inter-agency Workshop on Legal Framework for DSS Implementation (9-10


August 2011, Bandung)
This inter-agency workshop was aimed at developing the findings and formulations of main
national policies that have been worked out by National Water Resources Council (NWRC)
and accelerating and intensifying the communication among the agencies who are managing
the water resources data and information. All supporting platforms that are required for
representing, disseminating, and distributing data and information were opened to officials
and the public. The objective of the workshop was to assist the finalization of the legal format
of national policy framework on water resources information management as an instrument
for integrated water resources management, stipulated in Government Regulation No.42-
2008.

5.5.2 Data Sharing Management Workshop (1-2 February 2012, Bandung)


Currently, data and information in water related fields are managed in a segmented way by
sectors and regional institutions in Indonesia, which makes it difficult to utilize Decision
Support System (DSS). The most distinctive categories of dataset for water resources are
Water Quality, Hydrology, Hydrogeology and Hydrometeorology (WQH3). Their formats
should be streamlined and made uniform for practical implementation of DSS. These issues
were emphasized at the coordination meeting for DSS Project (Package D) in K-water
Bandung office on 4 May 2011, TA 7189-INO coordination meeting on 16 November 2011,
and also during consultation meeting with BAPPENAS on 11 January 2012. The provision of
data sharing agreement among the stakeholders of Citarum RBT, which is based on
regulation for operational management level, would be a solution for these issues. In addition,
it would build a commitment among the stakeholders. This kind of agreement should be
complemented with concrete Annual Works Plan (AWP) and Annual Budget Plan (ABP) for
each institution involved for the next five years. In relation, an inter-agency workshop was
conducted as a focus group discussion among the main stakeholders in West Java for building
a sense of togetherness and homogeneous understanding of the importance of water resources
data sharing in Citarum River Basin. The workshop participants agreed on the concept of data
sharing mechanism and technology in one-day workshop. After the workshop, training for the
stakeholders technical staff and counterparts was conducted to practice the Data Sharing
Management plus the RRFS.

150
6. Future Plan & Summary

6.1 Proposal for Further Work

Following section explains plans for future work on the project.

6.1.1 Funding for the Future Phases


On 14 March 2011, the MPW Secretary General has issued a funding request to Korean
International Cooperation Agency (KOICA) for the next phases of the DSS development. A
letter has been sent as well to Bappenas for inclusion of this project into the blue book.
Further discussion with KOICA and Bappenas will be needed to confirm funding for the
future phases of the project. The summary of the future project request to KOICA is
presented below.

6.1.2 Project Description


Title: Advanced Water Information Management System (WIMS) and Institutional
Capacity Building of River Basin Organization in the Citarum River Basin (CRB)
Project duration: (January 2013 December 2014)
Estimated Project cost: 5,000,000 USD

6.1.3 Project Objective (Short Term and Long Term)


Short-term objectives of the project include development, implementation and transfer of a
comprehensive Water Information Management System (WIMS) as a standard platform for
water resource management for river basin organization (RBO) including a hydrological and
GIS database and water quantity and quality modeling tools. The WIMS will help diminish
environmental and water resources degradation through advanced water resources
management by improving a) monitoring and forecasting capabilities, b) software and
hardware infrastructure for water resources management and c) institutional capacity building
of RBO and related agencies.

Long-term objectives will include a) poverty alleviation through efficient resource


management, b) more sustainable economic development, c) improvement in public health
and environment and d) climate change preparedness through development of more robust
and sustainable water management system and better forecasting.

151
6.1.4 Scope of Works

a. Monitoring System Improvement


Analyze density, location and functionality of rainfall, intake, flow stations and water
quality sampling locations in the Citarum River Basin
Recommend optimum locations for additional stations for better monitoring
Install state of the art monitoring equipment at selected stations for real-time
monitoring on a pilot basis
Provide training on operation and maintenance of equipment

b. Development and Implementation of WIMS

Develop a comprehensive WIMS including software for water allocation management


and modeling and forecasting tools for water quality and runoff connected to a
comprehensive database for integrated river basin management
Implementation of WIMS, testing, stabilization and optimization
Development of public hydrological database and web-based information
dissemination portal

c. Institutional Strengthening and Infrastructure Support


Support for network and hardware setup
Operation of information management system and on the job training
Capacity building for RBO through trainings and workshops

Figure 140: User group of Water Information Management System


152
6.1.5 Outputs of each phase:

a. Phase 1 (2012)
A comprehensive state-of-the-art water information management system
Tools for better forecast and planning of water resources and usage
A central hydrological database with current water resources information for decision
makers
Trained and qualified staff for water resource management system operations

b. Phase 2 (2013)
Implementation of water resources management system, testing, on-job training of
counterparts and stabilization
Portal for public access to hydrological database
Institutionalization of information flow management protocols, procedures and
systems for more efficient inter-agency cooperation
Enhanced water management and planning systems and procedures for agencies that
will integrate the WIMS into ongoing operations
Business plan for long-term development and sustainable management of the WIMS
using government resources

6.1.6 Project Sustainability


Extensive on-job training, classroom based training as well as training in Korea will be
provided to ensure successful operation of project using local human resource after project
completion. An important contribution towards sustainability will be working closely with
RBO and other counterparts to understand their responsibilities and processes and
demonstrate the benefits of WIMS for operations. To accompany this, the project will have a
strong institutional and management focus that will work to formalize information sharing
and mainstream use of the WIMS in planning and management. The project will work with
the government to create a business plan for long-term development and management of the
WIMS using government resources.

153
6.2 Database Extension

Currently, DSS database is not available to conserve agriculture water demand, industrial
water demand, domestic water demand data, and intake of PAM Jaya (Drinking Water
Company). This data is required to support water allocation modeling and calculate water
balance. Water demand is sophisticated data, so it needs further analysis to normalize so it
can be easily managed in the database. Besides that, it is related to discharge data in hydraulic
structure such as reservoir and weir.

In case of water quality data, current DSS database saves only water quality observations
from river water. Disposal discharge from industry is not available to be saved in DSS DB. It
has different data format, but it is crucial to measure not only water quality on the
river/stream, but also water quality in the pollutant outflow. So it is required to analyze such
data and create appropriate data table in the database.

So, in the next phase, we will add water demand data table and also industry's water quality
data table in the database.

6.3 DSS Development

In the next phase, there will be additional features added to the database to increase DSS
usability, especially in managing water quantity and water quality data:
Monitoring, Planning, and Evaluation for IWRM in Citarum River Basin to support
the basin managers and water basin council
Long-term water allocation planning
Operational Water Resources Management
Establish short-term water supply plan
Balance seasonal water demands between users through reservoir and stream flow
management
integrated river-reservoir system operational planning
Quantify spatial and temporal runoff amounts
Improve the efficiency of basin reservoir system management
Water allocation monitoring and evaluation
Trans-basin operational planning and monitoring
Water resources DB and information management

s Three Dams Operational Planning and Management for;


Dry climate
Normal climate
Wet climate
Severe climate
Emergency condition
154
6.4 Summary

The primary tasks envisioned to be completed during the inception period as per the original
scope of work for DSS development for IWRM in CRB; Package D of Institutional
Strengthening for Integrated Water Resources Management in the 6 Cis Territory, included
the following;

Data collection and analysis for DSS in CRB


Identification of data gaps and recommendations to eradicate those data gaps through
improved monitoring
GIS hydrological database development and deployment
RRFS model development and implementation for CRB
Institutional strengthening and capacity building

This report presents the findings of the above five exercises as well as a listing of identified
issues that may delay or hinder the future progress of DSS deployment and extension project.

The cynosure of project activities during the period up to final report was water quantity and
quality monitoring network, hydrological and GIS database development, RRFS development,
information support system, and capacity building and institutional strengthening. Through
site visits and several missions to Indonesia, during which extensive consultations were
conducted with all stakeholder organizations, the important stakeholder organizations were
identified. Their organization structures were studied and manpower interviewed to develop
extensive profiles of existing human resource capability. PJT-II was identified as a significant
stakeholder in terms of data availability, as they were the organization with the largest
database of centrally stored and managed coherent data in the form of SISDA database and
modeling system. For network modeling, Package B consultants were identified as the
significant partners in terms of data availability. PusAir has been identified as the
organization with the largest qualified human resource base to contribute towards capacity
building, as there is the center of water research.

Although the datasets collected on rainfall and stream flow are generally adequate to build a
base model especially for upper Citarum, there are many gaps and inconsistencies in the data.
So far, rainfalls, water demand, flow and dam operation data have been collected from PJT-II.
Further, several layers of GIS data have been collected from PJT-II system. The collected
data have been analyzed for consistency and density. Based on the recommendations in
midterm, the monitoring network optimization of rainfall, flow meter, and water quality and
optimization of data collection methodology are developed.

GIS data are mostly obtained from Water Resources Information System (Sistem Informasi
Sumber Daya Air/SISDA) of PJT-II, and consists of administrative boundary, diversion and
intake structure, reservoir location, sub-catchment, discharge observation points, roads, soil
type, water quality, land-use, rainfall station, etc. The area of Citarum River Basin is bounded
by working jurisdiction.

155
The process of development followed from user requirement analysis, specification, drawing
flow diagrams and importer modules, design UI, development of class diagrams and Entity
Resource Diagram development. As a result, the final DSS software for managing database is
fully proficient in handling requirements of all the stakeholders in the project.

While developing there were some issues and challenges such as difference of data format,
different parameters, clearance of data field attributes, and missing data. However,
development team overcame all of these issues by discussing with every agency and
collecting feedbacks.

The main features of DSS data manager are as below:

Constructed an integrated GIS based database connecting each agency.


Data input (Data Import Wizard)
Data output (Excel format)
Data validation (Using charts and alert system)
Integrated modeling tools (RRFS)
Create reports (Year book, rainfall, dam operation, and water quality report)
Support of User manual (English, Bahasa Indonesia)

Final calibration, validation and finer scaled calibration of the RRFS model and complete
deployment for CRB are finished as of February 2012. In the next phase, the developed
RRFS will provide the basic input data for water allocation model, KModSim, such as runoff
data per sub-basins and of main control points. The mid- and long-term RRFS based on ESP-
PDF system will also play an important role in risk assessment and probability analysis for
dam operation and water allocation plan.

Most phases of DSS development are seen as iterative with constant feedback from
stakeholders being incorporated into the project even during deployment. The future of DSS
development will see a continuation of this cycle of inclusive development and
implementation. In the next phase, there will be additional features to increase DSS usability,
especially in managing water quantity and water quality data: (i) Monitoring, Planning, and
Evaluation for IWRM in Citarum River Basin to support the basin managers and water basin
council, (ii) Long-term water allocation planning, (iii) Operational Water Resources
Management, and (vi) Three Dams Operational Planning and Management.

The primary finding of the project was the significance of stakeholder engagement and
consultation in making the project successful and sustainable. Accordingly, the database
design and development team was relocated to the project site to stay in direct coordination
with the stakeholders in real time. The relevant findings of the exercise were included in the
database within the design phase. It should be emphasized that stakeholder consultation and
engagement has to take main stage as the key activity in any technology implementation
project of such kind especially in the area of water resources and environment where local
knowledge incorporation is key to project success.
156
7. References

ADB Technical Assistant, Integrated Citarum Water Resources Management Program


(ICWRMP) (TA4381-INO-Phase III), ADB, (2006).

ADB Technical Assistant, Report on Data and Decision Support Systems (TA7189-REOT-002-
0), ADB, (2010).

ADB, Report and Recommendation of the President to the Board of Directors, ADB, (2008).

Jatiluhur Water Resources Management Project Preparation Study (JWRMP), NEDECO,


(1998).

K-water, Development of a Water Quality Management System for the West Tarum Canal of
Citarum River Basin in West Java Province, Indonesia, (2008).

Lee, S.U., Kim, J.K., Noh, J.W., Ko, I.H., Assessment of Selective Withdrawal Facility in the
Imha Reservoir Using CE-QUAL-W2 Model, Korea Institute of Water and Environment, Korea
Water Resources Corporation, Korean Society on Water Quality, (2007).

Rockwood, D.M., Columbia basin stream-flow routing by computer, Transactions, American


Society of Civil Engineers, No. 3119 (1961).

Rockwood, D.M., Application of stream-flow synthesis and reservoir regulation SSARR


Program to the lower Mekong river, The Use of Analog and Digital Computer in Hydrology
Symposium, International Association of Scientific Hydrology, UNESCO, pp. 329-344 (1968).

Technical Assistance, Integrated Citarum Water Resources Management Project (ICWRMP)


(TA4381-INO), Nippon Koei Co., LTD, (2006).

Teunis H. op ten Noort, Mission Report, Integrated Citarum Water Resources Management
Project (TA-4381-INO), (2006).

USACE, SSARR User manual, North Pacific Div., Portland (1991).

Ministry of Science and Technology, 21st Century Frontier R&D Program, -Sustainable Water
Resources Research Program-, (2007).

Wells, S.A., Cole, T.M., Theoretical Basis for the CE-QUAL-W2 River Basin Model, Engineer
Research and Development Center Vicksburg MS Environmental Lab, (2000).

157
Appendices

158
Appendix 1: Graphics User Interface for GIS and
Hydrological Database

Image 1: Administrative Boundaries of Java Island

Image 2: Working Jurisdiction of CRB

159
Image 3: Diversion and Intake Structure of West Tarum

Image 4: Diversion and Intake Structure of East Tarum

Image 5: Diversion and Intake Structure of North Tarum


160
Image 6: Secondary Diversion and Intake Structure

Image 7: Dam Structure

Image 8: Sub-Basins of CRB


161
Image 9: Discharge Observation Locations in CRB

Image 10: Elevation Vegetation Type in CRB

Image 11: Planting Group in CRB


162
Image 12: Culvert Location in CRB

Image 13: Hydro (River Network) in CRB

Image 14: Climate Station Location in CRB


163
Image 15: Infrastructure Location in CRB

Image 16: Artery Road in CRB

Image 17: Rail Road in CRB


164
Image 18: Express Road in CRB

Image 19: Bridge Location in CRB

Image 20: Soil Type in CRB


165
Image 21: Slope of CRB

Image 22: Physical Condition of CRB

Image 23: Water Quality Observation Location in CRB


166
Image 24: Critical Land in CRB

Image 25: Landuse of CRB

Image 26: Landuse of CRB in 2007


167
Image 27: Population in CRB

Image 28: Transportation Infrastructure Location in CRB

Image 29: Main Canal in CRB


168
Image 30: Secondary Canal in CRB

Image 31: Siltrap Location in CRB

Image 32: Siphon Location in CRB


169
Image 33: Swamp Location in CRB

Image 34: Rainfall Station Location in CRB

Image 35: Aquaduct Location in CRB


170
Image 36: Drop Structure Location in CRB

Image 37: Lake Location in CRB

Image 38: Working Jurisdiction of Observers in CRB

171
Appendix 2: Structure Code List

172
AWS (Automatic Weather Station)

Code River Territory ID Catchment ID Agency ID Station Name Station Type Sub-basin ID District ID Sub-district ID
10503001 10 1001 3 Chincona 1 100101 3204 3204040
10503002 10 1001 3 Ciparay 1 100101 3204 3204080
10503003 10 1001 3 Cicalengka 1 100101 3204 3204100
10503004 10 1001 3 Bandung 1 100101 3277 3277010
10503005 10 1001 3 Saguling 1 100101 3204 3204240
10503006 10 1001 3 Cisokan 1 100101 3203 3203150
10503007 10 1001 3 Plered 1 100101 3214 3214060
10503008 10 1001 3 Sukatani 1 100101 3214 3214090
10503009 10 1001 3 Citalang 1 100101 3214 3214100

Dam

Code River Territory ID Catchment ID Agency ID Name Type Postfix Province ID District ID Sub-district ID
Dam
10103001 10 1001 3 0 Jatiluhur 32 3214 NULL
Jatiluhur
10109002 10 1001 3 Dam Cirata 0 Cirata 32 3204 NULL
Dam
10109003 10 1001 3 0 Saguling 32 3204 NULL
Saguling

173
Rainfall

Catchment ID Agency ID Name Sub-catchment ID Province ID District ID Sub-district ID


10300003 1001 0 Ciparay 100101 32 3204 3204130
10300004 1001 0 Dago Bengkok 100101 32 3273 3273260
10300005 1001 0 Lembang 100101 32 3204 3204320
10300011 1001 0 Cisondari_1 100101 32 3204 3204020
10300014 1001 0 Cibeureum_2 100101 32 3204 3204050
10300015 1001 0 Paseh 100101 32 3204 3204080
10300016 1001 0 Cicalengka_1 100101 32 3204 3204100
10300018 1001 0 Ujung Berung 100101 32 3204 3204290
10300020 1001 0 Margahayu1 100101 32 3204 3204320
10300025 1001 0 Montaya 100101 32 3204 3204220
10300102 1001 0 Cisomang 100101 32 3204 3204390
10300110 1001 0 Ciherang_Kalijati 100101 32 3213 3213080
10300111 1001 0 Cisampih 100101 32 3213 3213080
10300117 1001 0 Jatiroke 100101 32 3211 3211010
10300120 1001 0 Kertamanah 100101 32 3204 3204050
10300121 1001 0 Cileunca 100101 32 3204 3204040
10300122 1001 0 Cipanas Pengalengan 100101 32 3204 3204040
10300123 1001 0 Cipeusing 100101 32 3204 3204340
10300124 1001 0 Tanjungsari 100101 32 3213 3213040
10300125 1001 0 Cisalak 100101 32 3213 3213030
10300126 1001 0 Ciluluk 100101 32 3204 3204080
10300127 1001 0 Rancaekek 100101 32 3211 3211030
10300201 1001 0 Cikancung 100101 32 3204 3204090
174
10300202 1001 0 Cisurupan/Cibiru 100101 32 3273 3273110
10302017 1001 2 Cicalengka_2 100101 32 3204 3204100
10302021 1001 2 Kayu Ambon 100101 32 3204 3204320
10302034 1001 2 Cianten 100101 32 3201 3201020
10302035 1001 2 Cibinong 100101 32 3276 3276040
10302042 1001 2 Panjang 100101 32 3201 3201110
10302043 1001 2 Naringgul 100101 32 3201 3201110
10302048 1001 2 Bangkir 100101 32 3212 3212150
10302049 1001 2 Cikedung 100101 32 3212 3212040
10302050 1001 2 Indramayu 100101 32 3212 3212150
10302051 1001 2 Juntinyuat 100101 32 3212 3212110
10302052 1001 2 Kertasemaya 100101 32 3212 3212080
10302053 1001 2 Krangkeng 100101 32 3212 3212090
10302054 1001 2 Losarang 100101 32 3212 3212180
10302055 1001 2 Sumurwatu 100101 32 3212 3212220
10302063 1001 2 Halim Perdanakusuma 100101 31 3172 3172040
10302064 1001 2 Tanjuk Priok 100101 31 3175 3175030
10302066 1001 2 Babakan 100101 32 3275 3275070
10302068 1001 2 Depok 9TP 100101 32 3276 3276010
10302114 1001 2 Kasso Malang 100101 32 3211 3211171
10302115 1001 2 Darmaraja 100101 32 3211 3211080
10302116 1001 2 Gudang Uyah 100101 32 3211 3211050
10302118 1001 2 Pamulihan 100101 32 3211 3211032
10302119 1001 2 Ujung Jaya 100101 32 3211 3211130
10302200 1001 2 Ciherang/Cangkuang 100101 32 3204 3204161

175
10303128 1001 3 Montaya 100101 32 3204 3204230
10303129 1001 3 Cisokan(Cirata) 100101 32 3203 3203150
10303130 1001 3 Sindanglaya 100101 32 3211 3211170
10303131 1001 3 Cipicung(Cirata) 100101 32 3214 3214020
10303132 1001 3 Ciseuti-265 100101 32 3211 3211171
10303133 1001 3 Cibukamanah 119.a 100101 32 3204 3204390
10303134 1001 3 Dam(Cirata) 100101 32 3214 3214020
10303135 1001 3 Muara 100101 32 3271 3271020
10303136 1001 3 Curugagung 312.2 100101 32 3213 3213010
10303137 1001 3 Cipeundeuy-313.3 100101 32 3213 3213080
10303138 1001 3 Cinangling-313.1 100101 32 3213 3213080
10303139 1001 3 Dangdeur 153/b 100101 32 3213 3213070
10303140 1001 3 Gantar CBN3.b 100101 32 3212 3212011
Bend.Cipamingkis-
10303141 1001 3 100101 32 3201 3201170
89.a
10303142 1001 3 Kroya-Cbn.6 100101 32 3212 3212020
10303143 1001 3 Pagaden 152 100101 32 3213 3213140
10303144 1001 3 Cipancuh-Cbn.18 100101 32 3212 3212011
10303145 1001 3 Tamiang-Cbn.29 100101 32 3212 3212020
10303146 1001 3 Cibandung 331/1 100101 32 3213 3213130
10303147 1001 3 Gabus Wetan-Cbn.5 100101 32 3212 3212030
10303148 1001 3 Pundong-115.b 100101 32 3214 3214110
10303149 1001 3 Cibarusah_85 100101 32 3201 3201170
10303150 1001 3 Cikampek-112.a 100101 32 3215 3215040
10303151 1001 3 Salamdarma-153 100101 32 3213 3213160
10303152 1001 3 Pawelutan 75 100101 32 3213 3213170
176
10303153 1001 3 Cilentah 321.2 100101 32 3214 3214101
10303154 1001 3 Dawuan-112 100101 32 3215 3215040
Leuweung Semut-
10303155 1001 3 100101 32 3212 3212030
Cbn.15
10303156 1001 3 Cigadung 153 100101 32 3213 3213160
10303157 1001 3 Barugbug-113.c 100101 32 3213 3213110
10303158 1001 3 Ciberes-323.1 100101 32 3213 3213110
10303159 1001 3 Rancabango 324/3 100101 32 3213 3213110
10303160 1001 3 wanguk-Cbn.16 100101 32 3212 3212210
10303161 1001 3 Bendung Cibeet 8.a 100101 32 3215 3215010
10303162 1001 3 Purwasari 100101 32 3215 3215050
10303163 1001 3 Jatisari-111 100101 32 3215 3215070
10303164 1001 3 Tulangkacang-Cbn.14 100101 32 3212 3212200
10303165 1001 3 Telar-110.B 100101 32 3215 3215072
10303166 1001 3 Karangtoman-824.2 100101 32 3213 3213180
10303167 1001 3 Wanasari-332.2 100101 32 3213 3213170
10303168 1001 3 Cikalong-113.b 100101 32 3215 3215070
10303169 1001 3 Ciasem 324/1 100101 32 3213 3213180
10303170 1001 3 Tambakdahan-333.3 100101 32 3213 3213190
10303171 1001 3 Anjatan-Cbn.1 100101 32 3212 3212210
10303172 1001 3 Bojongkeding 331.2 100101 32 3213 3213200
10303173 1001 3 Tanjung-111.B 100101 32 3215 3215070
10303174 1001 3 PEDES B.Tut.4 100101 32 3215 3215060
10303175 1001 3 Citapen-110.a 100101 32 3213 3213180
10303176 1001 3 Setu_Bks.13 100101 32 3216 3216010
10303177 1001 3 KARAWANG 100101 32 3215 3215112
177
10303178 1001 3 Cikeas-Dkt.26 100101 32 3275 3275020
10303179 1001 3 Bendung Cikarang_9.a 100101 32 3216 3216071
10303180 1001 3 Sukra-Cbn.21 100101 32 3212 3212220
10303181 1001 3 Cigugur 344.1 100101 32 3213 3213200
10303182 1001 3 Karanganyar-74 100101 32 3213 3213200
10303183 1001 3 Cibitung-78.c 100101 32 3216 3216071
10303184 1001 3 Pilar_82.a 100101 32 3216 3216071
10303185 1001 3 Pusakanagara-345/1 100101 32 3213 3213200
10303186 1001 3 Gempol Haji-128.a 100101 32 3215 3215081
10303187 1001 3 Pebayuran_Bks.4c 100101 32 3216 3216050
10303188 1001 3 Rawamerta 96.a 100101 32 3215 3215120
10303189 1001 3 Pamanukan 333/1 100101 32 3213 3213210
10303190 1001 3 Kranji-Dkt.25 100101 32 3275 3275060
10303191 1001 3 Sarengseng_82.c 100101 32 3216 3216062
10303192 1001 3 Gabus_Dkt.70 100101 32 3216 3216110
10303193 1001 3 Pacing-Bks.5 100101 32 3216 3216130
10303194 1001 3 Rawarorotan_Dkt.30 100101 31 3175 3175060
10303195 1001 3 Teluk Bango.Bks.7 100101 32 3216 3216130
10303196 1001 3 Teluk Bango-82.d 100101 32 3215 3215190
10303197 1001 3 Gempol Lor-94 a/c 100101 32 3215 3215170
10303198 1001 3 Pangakaran_82.a 100101 32 3215 3215200
Teluk Buyung
10303199 1001 3 100101 32 3215 3215200
78.d/Dkt
10309001 1001 9 Majalaya 100101 32 3204 3204080
10309002 1001 9 Pacet 100101 32 3204 3204060
10309006 1001 9 Bandung Telemetri 100101 32 3273 3273260
178
10309007 1001 9 Pangalengan 100101 32 3204 3204040
10309008 1001 9 Chinchona 100101 32 3204 3204040
10309009 1001 9 Ciwidey 100101 32 3204 3204020
10309010 1001 9 Gambung 100101 32 3204 3204020
10309012 1001 9 Cisondari_2 100101 32 3204 3204020
10309013 1001 9 Cibeureum_1 100101 32 3204 3204050
10309019 1001 9 Sukawana 100101 32 3204 3204330
10309022 1001 9 Batujajar 100101 32 3204 3204240
10309023 1001 9 Padalarang 100101 32 3204 3204360
10309024 1001 9 Cililin 100101 32 3204 3204200
10309026 1001 9 Saguling Dam 100101 32 3204 3204230
10309027 1001 9 Cemara 100101 32 3273 3273250
10309028 1001 9 Bendung Bekasi 100101 32 3275 3275040
10309029 1001 9 Cikarang 100101 32 3216 3216061
10309030 1001 9 Lemah Abang 100101 32 3216 3216061
10309031 1001 9 Rengas Bandung 100101 32 3216 3216050
10309032 1001 9 Tapak Serang 100101 32 3216 3216071
10309033 1001 9 Empang 100101 32 3271 3271010
10309036 1001 9 Citeko 100101 32 3201 3201110
10309037 1001 9 Darmaga 100101 32 3201 3201060
10309038 1001 9 Gadog 100101 32 3201 3201120
10309039 1001 9 Gunung Mas 100101 32 3201 3201110
10309040 1001 9 Katulampa 100101 32 3271 3271020
10309041 1001 9 Kranji 100101 32 3276 3276040
10309044 1001 9 Pasir Muncang 100101 32 3201 3201120

179
10309045 1001 9 Cimulang 100101 32 3201 3201231
10309046 1001 9 Klapa Nunggal 100101 32 3201 3201180
10309047 1001 9 Tunggilis 100101 32 3201 3201180
10309056 1001 9 Bantarhuni 100101 32 3212 3212011
10309057 1001 9 Bugel 100101 32 3212 3212190
10309058 1001 9 Bugis 100101 32 3212 3212210
10309059 1001 9 Leuweungsemut 100101 32 3212 3212030
10309060 1001 9 Karangasem 100101 32 3212 3212190
10309061 1001 9 Ponggang 100101 32 3213 3213040
10309062 1001 9 Cipayung 100101 32 3216 3216041
10309065 1001 9 Pasar Minggu 100101 31 3175 3171020
10309067 1001 9 BMG Pusat 100101 31 3173 3173020
10309069 1001 9 Depok 36a 100101 32 3276 3276010
10309070 1001 9 Batujaya 100101 32 3216 3216140
10309071 1001 9 Cibadar 100101 32 3215 3215161
10309072 1001 9 Cibuaya 100101 32 3215 3215160
10309073 1001 9 Cilamaya 100101 32 3215 3215081
10309074 1001 9 Gempol Lor 100101 32 3215 3215160
10309075 1001 9 Karawang 100101 32 3215 3215113
10309076 1001 9 Leuweung Seureuh 100101 32 3215 3215040
10309077 1001 9 Pacing_Tub16 100101 32 3215 3215150
10309078 1001 9 Pengakaran 100101 32 3216 3216140
10309079 1001 9 Pataruman 100101 32 3215 3215150
10309080 1001 9 Pedes 100101 32 3215 3215140
10309081 1001 9 Peundeuy 100101 32 3215 3215081

180
10309082 1001 9 Plawad 100101 32 3215 3215112
10309083 1001 9 Pondok Balas 100101 32 3215 3215140
10309084 1001 9 Rawamerta 100101 32 3215 3215112
10309085 1001 9 Rengas Dengklok 100101 32 3215 3215140
10309086 1001 9 Telaga Sari_2 100101 32 3215 3215040
10309087 1001 9 Rawa Gempol_1 100101 32 3215 3215081
10309088 1001 9 Rawa Gempol_2 100101 32 3215 3215081
10309089 1001 9 Teluk Bango 100101 32 3216 3216130
10309090 1001 9 Walahar_101b 100101 32 3215 3215020
10309091 1001 9 Pasirukem 100101 32 3215 3215081
10309092 1001 9 Teluk Buyung 100101 32 3215 3215200
10309093 1001 9 Ceuplik 100101 32 3215 3215040
10309094 1001 9 Tempuran_br12 100101 32 3215 3215161
10309095 1001 9 Talenpare_btp2 100101 32 3213 3213220
10309096 1001 9 Gebang Malang 100101 32 3215 3215081
10309097 1001 9 Pegadungan 100101 32 3215 3215120
10309098 1001 9 Cibukanamah 100101 32 3204 3204390
10309099 1001 9 Cikao Bandung 100101 32 3214 3214100
10309100 1001 9 Ciracas 100101 32 3214 3214081
10309101 1001 9 Cirata 100101 32 3214 3214020
10309103 1001 9 Darangdan 100101 32 3214 3214060
10309104 1001 9 Pondok Salam 100101 32 3214 3214091
10309105 1001 9 Purwakarta 100101 32 3214 3214100
10309106 1001 9 Sadang 100101 32 3214 3214112
10309107 1001 9 Wanayasa 100101 32 3214 3214080

181
10309108 1001 9 Ciherang 100101 32 3213 3213080
10309109 1001 9 Ciherang_168b 100101 32 3214 3214112
10309112 1001 9 Pamanukan 100101 32 3213 3213220
10309113 1001 9 Subang 100101 32 3213 3213070

182
Water Level (Water Discharge)

Sub-catchment
Code River Territory ID Catchment ID Agency ID Station Name District ID Sub-district ID
ID
10400001 10 1001 0 Cisangkuy-Pataruman 100101 3204 3204040
10400004 10 1001 0 Citarum-Majalaya 100101 3204 3204120
10400005 10 1001 0 Cisangkuy-Kamasan 100101 3204 3204160
10400006 10 1001 0 Citarum-Dayeuh Kolot 100101 3204 3204140
10400008 10 1001 0 Cikapundung-Pasir Luyu 100101 3273 3273060
10400009 10 1001 0 Citarum-Nanjung 100101 3204 3204250
10400010 10 1001 0 Cikeruh-Cikuda 100101 3211 3211010
10400012 10 1001 0 Cidurian-Sukapada 100101 3273 3273220
10400019 10 1001 0 Cilalawi-Cilalawi 100101 3214 3214050
Cipunagara-Kiara
10400021 10 1001 0 100101 3213 3213160
Payung
10400042 10 1001 0 Cijalupang-Peundey 100101 3204 3204100
10400043 10 1001 0 Citarik-Rancakemit 100101 3204 3204110
10400044 10 1001 0 Cikondang-Cihaur 100101 3203 3203120
Cikeruh-Babakan
10400045 10 1001 0 100101 3211 3211010
Bandung
Ciwidey-Cukang
10402002 10 1001 2 100101 3204 3204020
Genteng
10402003 10 1001 2 Cirasea-Cengkrong 100101 3204 3204130
10402007 10 1001 2 Citarik-Bd.Cangkuang 100101 3204 3204100
10402011 10 1001 2 Cipanjalu-Kepuh 100101 3204 3204300
10402013 10 1001 2 Cikapundung-Gandok 100101 3273 3273260
10402014 10 1001 2 Cikapundung-Maribaya 100101 3204 3204320

183
10402015 10 1001 2 Cigulung-Maribaya 100101 3204 3204320
10402016 10 1001 2 Cibeureum-Cihideung 100101 3204 3204320
10402017 10 1001 2 Cimahi-Cicakung 100101 3204 3204340
10402018 10 1001 2 Ciasem-Curug Agung 100101 3213 3213010
10402020 10 1001 2 Cilamaya-Cipeundeuy 100101 3214 3214111
10403022 10 1001 3 Bendung Cisomang 100101 3214 3214060
10403023 10 1001 3 Bendung Curug Agung 100101 3213 3213010
10403024 10 1001 3 Bendung Pondoksalam 100101 3214 3214091
10403025 10 1001 3 Bendung Cileuleuy 100101 3213 3213070
10403026 10 1001 3 Bendung Lalanang 100101 3212 3212020
10403027 10 1001 3 Bendung Leuwi Nangka 100101 3213 3213080
10403028 10 1001 3 Bendung Cipamingkis 100101 3201 3201170
10403029 10 1001 3 B.Pangsor 100101 3213 3213140
10403030 10 1001 3 Bendung Pedati 100101 3212 3212020
10403031 10 1001 3 Bendung Macan 100101 3213 3213130
10403032 10 1001 3 Pundong 100101 3214 3214110
10403033 10 1001 3 Bendung Salam Darma 100101 3213 3213160
10403034 10 1001 3 Barugbug 100101 3215 3215070
10403035 10 1001 3 Bendung Beet 100101 3216 3216031
10403036 10 1001 3 Bendung Walahar 100101 3215 3215020
10403037 10 1001 3 Jengkol 100101 3213 3213180
10403038 10 1001 3 Bendung Gadung 100101 3213 3213170
10403039 10 1001 3 Bendung Cikeas 100101 3201 3201190
10403040 10 1001 3 Bendung Karang 100101 3216 3216061
10403041 10 1001 3 Bendung Bekasi 100101 3275 3275050

184
10403046 10 1001 3 Sapan 100101 3204 3204280
10403047 10 1001 3 Gandok-Citarum 100101 3273 3273190
Pembuang Situ
10403048 10 1001 3 100101 3214 3214091
Wanayasa
10403049 10 1001 3 Situ Wanayasa 100101 3214 3214091
10403050 10 1001 3 Cikao AWLR 100101 3214 3214100
10403051 10 1001 3 Ciherang AWLR 100101 3214 3214112
10403052 10 1001 3 Cikao-Cipaisan 100101 3214 3214101
Sungai Cikao-Jemb.
10403053 10 1001 3 100101 3214 3214101
Kujang
10403054 10 1001 3 Waduk Cipancuh 100101 3212 3212011
10403055 10 1001 3 Bendung Curug 100101 3214 3214101
10403056 10 1001 3 Sta. Pompa STB 100101 3214 3214101
10403057 10 1001 3 SITT / ETC 100101 3214 3214101
10403058 10 1001 3 Bendung Cigentis-Waru 100101 3216 3216030
10403059 10 1001 3 Sungai Ciherang 100101 3214 3214110
10403060 10 1001 3 SS. Pangkalan 100101 3216 3216021
10403061 10 1001 3 Bendung Paweulutan 100101 3213 3213170
10403062 10 1001 3 Kedung Gede 100101 3216 3216022
10403063 10 1001 3 SITU / NTC 100101 3215 3215040
10403064 10 1001 3 Sungai Cikeas 100101 3275 3275050
10403065 10 1001 3 Intake Buaran 100101 3275 3275010
10403066 10 1001 3 SITB / WTC-Bd. Gergaji 100101 3172 3172070
10403067 10 1001 3 Intake Pejompongan 100101 3172 3172070
10403068 10 1001 3 Intake Pulogadung 100101 3172 3172070
10403069 10 1001 3 Intake Cakung 100101 3172 3172070
185
Water Quality

Code Catchment ID Agency ID District ID Station Name Interval Sub-district ID Sub-catchment ID


10601001 1001 1 3204 Wangisagara 3204070 100101
10601002 1001 1 3204 Majalaya 3204120 100101
10601003 1001 1 3204 Sapan 3204280 100101
10601004 1001 1 3204 Cijeruk 3204280 100101
10601005 1001 1 3204 Dayeuh Kolot 3204140 100101
10601006 1001 1 3204 Burujul 3204190 100101
10601007 1001 1 3204 Nanjung 3204250 100101
10601008 1001 1 3204 Curug 3204250 100101
10601009 1001 1 3215 Walahar 3215020 100101
10601010 1001 1 3216 Tanjung Pura 3216050 100101
10603001 1001 3 3273 Outlet Situ Cisanti 3273180 100101
10603002 1001 3 3204 Wangisagara 3204070 100101
10603003 1001 3 3204 Majalaya 3204120 100101
10603004 1001 3 3204 Rancaekek 3204110 100101
10603005 1001 3 3204 Sapan 3204280 100101
10603006 1001 3 3204 Sapan 3204280 100101
10603007 1001 3 3273 Sapan 3273090 100101
10603008 1001 3 3204 Sapan 3204280 100101
10603009 1001 3 3273 Buah Batu 3273080 100101
10603010 1001 3 3204 Jalan Asia Afrika 3204050 100101
10603011 1001 3 3204 Dayeuh Kolot 3204270 100101
10603012 1001 3 3204 Banjaran 3204160 100101
10603013 1001 3 3204 Dayeuh Kolot 3204270 100101
10603014 1001 3 3204 Palasari 3204270 100101
10603015 1001 3 3204 Margahayu 3204180 100101
10603016 1001 3 3204 Burujul 3204250 100101

186
10603017 1001 3 3204 Nanjung 3204250 100101
10603018 1001 3 3204 Nanjung 3204240 100101
10603019 1001 3 3204 Batujajar 3204240 100101
10603020 1001 3 3204 Inlet PLTA Saguling 3204230 100101
10603021 1001 3 3204 Outlet PLTA Saguling 3204370 100101
10603022 1001 3 3214 Inlet PLTA Cirata 3214020 100101
10603023 1001 3 3214 Outlet PLTA Cirata 3214020 100101
10603024 1001 3 3215 Cikao Bandung 3215020 100101
10603025 1001 3 3215 Sebelum PT IBR 3215020 100101
10603026 1001 3 3215 Sesudah PT IBR 3215020 100101
10603027 1001 3 3214 Bendung Curug 3214101 100101
10603028 1001 3 3215 Bendung Walahar 3215020 100101
10603029 1001 3 3215 Jalan Rumah Sakit 3215031 100101
10603030 1001 3 3216 Tanjungpura 3216050 100101
10603031 1001 3 3215 Tunggakjati 3215113 100101
10603032 1001 3 3216 Rengasdengklok 3216130 100101
10603033 1001 3 3216 Muara Gembong 3216150 100101
10603034 1001 3 3201 Leuwi Nutug 3201200 100101
10603035 1001 3 3201 Cileungsi 3201190 100101
10603036 1001 3 3201 Cibinong 3201200 100101
10603037 1001 3 3201 Bantar Gebang 3201190 100101
10603038 1001 3 3275 Bojong Kulur 3275011 100101
10603039 1001 3 3275 Bekasi Makro 3275050 100101
10603040 1001 3 3275 Bekasi PJKA 3275070 100101
10603041 1001 3 3275 Kampung Muara 3275070 100101
10603042 1001 3 3216 Kampung Muara 3216090 100101
10603043 1001 3 3216 Warung Pojok 3216071 100101
10603044 1001 3 3216 Cibitung Coca Cola 3216071 100101
10603045 1001 3 3216 Cibitung 3216071 100101
187
10603046 1001 3 3216 Setelah Muara Sadang 3216071 100101
10603047 1001 3 3216 Cilemahabang 3216061 100101
10603048 1001 3 3215 Sebelum PT Pupuk Kujang 3215050 100101
10603049 1001 3 3215 Sesudah PT Pupuk Kujang 3215050 100101
10603050 1001 3 3214 Cibungur 3214110 100101
10603051 1001 3 3214 Sesudah PT Sanfu 3214111 100101
10603052 1001 3 3215 Setelah PT ABB (Associated British Budi) 3215070 100101
10603053 1001 3 3213 Ciasem 3213220 100101
10603054 1001 3 3213 Pamanukan 3213210 100101
10603055 1001 3 3214 Cikembang 3214010 100101
10603056 1001 3 3214 Cikao Bandung 3214101 100101
10603057 1001 3 3214 Bendung Curug 3214101 100101
10603058 1001 3 3215 B.Tb. 10 3215020 100101
10603059 1001 3 3216 B.Tb. 23 3216022 100101
10603060 1001 3 3216 B.Tb. 35 3216071 100101
10603061 1001 3 3275 B.Tb. 45 3275050 100101
10603062 1001 3 3172 B.Tb. 49 3172070 100101
10603063 1001 3 3172 Intake PAM Buaran 3172070 100101
10603064 1001 3 3172 Intake PAM Pulo Gadung 3172070 100101
10603065 1001 3 3172 B.Tb. 51 3172060 100101
10603066 1001 3 3172 Intake PAM Pejompongan 3172060 100101
10603067 1001 3 3215 Karawang 3215032 100101
10603068 1001 3 3216 Cikarang 3216071 100101
10603069 1001 3 3275 Sebelum Bendung Bekasi 3275050 100101
10603070 1001 3 3215 Batujaya 3215190 100101
10603071 1001 3 3215 Rengasdengklok 3215150 100101
10603072 1001 3 3215 Warung Bambu 3215040 100101
10603073 1001 3 3215 Bendung Walahar 3215020 100101
10603074 1001 3 3215 Cikampek Utara 3215072 100101
188
10603075 1001 3 3214 Parung Kalong 3214020 100101
10603076 1001 3 3214 Sodong 3214020 100101
10603077 1001 3 3214 Bojong 3214011 100101
10603078 1001 3 3214 Jamaras 3214011 100101
10603079 1001 3 3214 Kerenceng 3214011 100101
10603080 1001 3 3214 Karamba 3214010 100101
10603081 1001 3 3214 Cilalawi 3214010 100101
10603082 1001 3 3214 PDAM 3214010 100101
10603083 1001 3 3214 Taroko 3214010 100101
10603084 1001 3 3214 Baras Barat 3214010 100101
10603085 1001 3 3214 Tailrace 3214011 100101
10603086 1001 3 3214 DAM 3214011 100101
10603087 1001 3 3214 Pasir Astana 3214011 100101
10603088 1001 3 3214 Pasir Kole 3214010 100101
10603089 1001 3 3214 Tajur Sindang 3214010 100101
10603090 1001 3 3214 Inlet PLTA Ir. H. Djuanda 3214011 100101

189
Weir

Code River Territory ID Catchment ID Agency ID Division Name Type Longitude Latitude
10203001 10 1001 3 2 Bendung Cisomang 2 0 0
10203002 10 1001 3 0 Bendung Cinangka 0 NULL NULL
10203003 10 1001 3 3 Bendung Curug Agung 4 NULL NULL
10203004 10 1001 3 2 Bendung Pondok Salam 2 NULL NULL
10203005 10 1001 3 0 Bendung Arsadipura 0 NULL NULL
10203006 10 1001 3 0 Bendung Surupan 0 NULL NULL
10203007 10 1001 3 3 Bendung Cileuleuy 4 NULL NULL
10203008 10 1001 3 0 Bendung Sukahurip 0 NULL NULL
10203009 10 1001 3 3 Bendung Cilalanang 4 NULL NULL
10203010 10 1001 3 3 Bendung Leuwinangka 4 NULL NULL
10203011 10 1001 3 0 Bendung Parakanbadak 0 NULL NULL
10203012 10 1001 3 0 Bendung Jati 0 NULL NULL
10203013 10 1001 3 0 Bendung Ranca Kando 0 NULL NULL
10203014 10 1001 3 0 Bendung Ciomas Bogor 0 NULL NULL
10203015 10 1001 3 3 Bendung Waru 2 NULL NULL
10203016 10 1001 3 0 Bendung Huni 0 NULL NULL
10203017 10 1001 3 0 Bendung Menteng 0 NULL NULL
10203018 10 1001 3 0 Bendung Gunungbubut 0 NULL NULL
10203019 10 1001 3 0 Bendung Cimanggu 0 NULL NULL
10203020 10 1001 3 0 Bendung Pagelaran 0 NULL NULL
10203021 10 1001 3 0 Bendung Cibarengkok 0 NULL NULL
10203022 10 1001 3 0 Bendung Cipicung 0 NULL NULL
10203023 10 1001 3 0 Bendung Cirawa 0 NULL NULL
190
10203024 10 1001 3 0 Bendung Cibayar 0 NULL NULL
10203025 10 1001 3 0 Bendung Ciomas Karawang 0 NULL NULL
10203026 10 1001 3 1 Bendung Cipamingkis 1 0 0
10203027 10 1001 3 0 Bendung Jungkur 0 NULL NULL
10203028 10 1001 3 3 Bendung Pedati 4 NULL NULL
10203029 10 1001 3 3 Bendung Pangsor 4 NULL NULL
10203030 10 1001 3 0 Bendung Legeh 0 NULL NULL
10203031 10 1001 3 3 Bendung Macan 3 0 0
10203032 10 1001 3 0 Bendung Cipicung 0 NULL NULL
10203033 10 1001 3 0 Bendung Curug 0 0 0
10203034 10 1001 3 0 Bendung Barasole 0 NULL NULL
10203035 10 1001 3 2 Bendung Pundong 2 0 0
10203036 10 1001 3 3 Bendung Salamdarma 3 0 0
10203037 10 1001 3 0 Bendung Pawelutan 0 NULL NULL
10203038 10 1001 3 3 Bendung Barugbug 3 0 0
10203039 10 1001 3 3 Bendung Gadung 3 0 0
10203040 10 1001 3 0 Bendung Bugis 0 NULL NULL
10203041 10 1001 3 1 Bendung Beet 0 0 0
10203042 10 1001 3 2 Bendung Walahar 2 0 0
10203043 10 1001 3 0 Bendung Rejag 0 NULL NULL
10203044 10 1001 3 0 Bendung Telar 0 NULL NULL
10203045 10 1001 3 0 Bendung Karangtoman 0 NULL NULL
10203046 10 1001 3 0 Bendung Kalong 0 NULL NULL
10203047 10 1001 3 3 Bendung Jengkol 3 0 0
10203048 10 1001 3 0 Bendung Leuweungseureuh 0 NULL NULL

191
10203049 10 1001 3 1 Bendung Cikeas 1 NULL NULL
10203050 10 1001 3 1 Bendung Cikarang 0 0 0
10203051 10 1001 3 0 Bendung Ranggon 0 NULL NULL
10203052 10 1001 3 1 Bendung Lemahabang 1 NULL NULL
10203053 10 1001 3 1 Bendung Bekasi 0 0 0
10203054 10 1001 3 0 Bendung Gergaji 0 NULL NULL
10203055 10 1001 3 0 Bendung Buana 0 NULL NULL
10203056 10 1001 3 0 Bendung Cakung 0 NULL NULL
10203057 10 1001 3 2 Situ Wanayasa 2 NULL NULL
10203058 10 1001 3 3 Waduk Cipancuh 4 NULL NULL
10203059 10 1001 3 1 Siphon Cibeet 1 2 3

192
Appendix 3: UCD Specification

UCD (Use Case Diagram)


As we know that Use Case Diagram is a type of behavioral diagram defined by and created
from a Use-case analysis. Its purpose is to present a graphical overview of the functionality
provided by a system in terms of actors, their goals (represented as use cases, in shape of
circle), and any dependencies between those use cases.

Box 1: UCD Specification

No Case Description
1 View GIS Map User views the GIS Map on main window.
User can read user manual, help feature or step-by-step procedure to
2 View User Manual
operate the software.
Manage Hydrological
3 User can manage hydrological data.
Data
Sub-case of Manage Hydrological Data (no.3) which user can search data
4 Search Data using search parameter such as agency type, station type, data type, interval
date, etc.
Sub-case of Manage Hydrological Data (no.3) which user can import data
5 Import Data
from Excel file or TXT file depends on the data type their going to import.
Sub-case of Manage Hydrological Data (no.3) which user can export data
6 Export Data
to Excel file depends on what kind of data that they are going to export.
Operational
7 User can manage the operational of water management.
Management
Sub-case of Operational Management (no.7) which user can manage dam
8 Manage Dam Operation
operational.
Sub-case of Operational Management (no.7) which user can manage weir
9 Manage Weir Operation operational, such as water discharge in weir, water level, and water
availability in weir.
Manage Water Demand Sub-case of Operational Management (no.7) which user can manage water
10 demand operation, especially for irrigation water demand evaluation &
Operation
drinking water demand evaluation.
11 Model User can use modeling tools.
Sub-case of Model (No.11) that user can simulate Rainfall Runoff
12 RRFS
modeling.
Sub-case of Model (No.11) which user can simulate other Modeling Tools
13 Other Modeling tools A
A (Proposed : Water Allocation Modeling)
Sub-case of Model (No.11) which user can simulate other Modeling Tools
14 Other Modeling tools B
B (Proposed : Water Quality Modeling)
User can create report using a wizard. E.g. : create annual report of rainfall
15 Create report wizard
data.
16 Manage Station User can manage station information.
User can search station information using search parameter such as agency
17 Search Station
type, station name, station type, etc.
18 Add Station User can add new station information.
19 Edit Station User can edit or update station information.
20 Delete Station User can delete station information.

193
UCD of PJT-II
PJT-II has rights to search, import, and export data from Hydrological Data menu. They can
also run RRFS model, create report and manage stations. DSS also includes a special menu
named Operation Plan where they can see dam, weir, and water demand information.
Operation Plan menu is only for PJT-II.

Image 39: UCD of PJT-II

194
UCD of BBWSC / DPSDA / BPLHD
In terms of usage, BBWSC, DPSDA, and BPLHD have same rights. Search, import, and
export data from Hydrological Data menu. They can also run RRFS model, create report
and manage stations.

Image 40: UCD of BBWSC / DPSDA / BPLHD

195
UCD of PusAir / BMKG
In terms of usage, PusAir and BMKG have same rights. Each agency can search and export
data from Hydrological Data menu. They can also run RRFS model, create reports from
other agency.

Image 41: UCD of PusAir / BMKG

196
Appendix 4: Data Flow Diagrams

Code Definition

Currently each observe station has a code based on the database structure, however some the
code definition is not completely assigned and almost none of the code has a unique value.
Therefore, all of the observer stations are redefined to make the code complete and unique.

Image 42: Code Definition

River Territory / Basin: Currently the development is based on Citarum basin only,
but concerning the future of the DSS program, we added a code to define which basin
it is located.
Catchment: Each agency has its own catchment definition, but for an integrated
database, we redefined the catchment definition based on RRFS model from K-water.
Gauge station type: There are many type of observe station in Citarum basin. In
purpose of distinction, this code is added as the notes below image 5.
Agency: DSS is not belonged to one institution. Therefore this code is added to define
which agency is on the management of each observe station.
Reg. Number: This is a unique number allocated to each observe station.

197
Data Flow Analysis
Hydrological data was analyzed by visiting the stakeholder and gathers some basic
information of existing system, data, and tools running on the stakeholder. Investigation and
evaluation needed to make a rough image of running system, and make a deep analysis to
maintain automation for future software. To make good software, which user friendly and has
more automation, software development team gathers some requirement from stakeholder.
There so, software development team provides some users request documentation, called
User Requirement Specification (URS) document. This document is not only a main
reference in designing use case diagram to plan user behaviors in the software but also in
designing database structures.

Each agency that collects hydrological data (PJT-II/DPSDA/BBWSC/BPLHD) has different


procedure of data collection. Following figures are description of each agencys procedure
sorted by station type.

Water Quantity
Water Level AWLR with telemetry system (PJT-II)
PJT-II has two type of AWLR with telemetry system. One is using SMS communication
method that send data automatically to HQ by SMS and another one is using dial-up
communication method that sends data manually to HQ.

Image 43: Water Level AWLR with telemetry system (PJT-II)

In the case of using SMS communication, Table grabber extracts raw data from each
observer station that is recorded in text format. And PROJEX calculates data to minutely,
hourly and daily data. This process works hourly and automatically.
The observe station using Dial-up communication method, use a software named CIMSTA
which calculates raw data to minutely, hourly and daily data. This process works manually
and the HQ staff receives the data at 7 oclock in the morning.
Even though PJT-II has six of telemetry station, only two are operating well. The details are
in Box 2.
198
Box 2: AWLR Station Status
No. Station Method Status
1 Cikao River in Gipaisan PSTN BROKEN
2 Citarum River in Majalaya PSTN BROKEN
3 Citarum River in Sapan GSM/SMS IN USE
4 Citarum River in Dayeankolot GSM/Dial-up IN USE
5 Citarum River in Kedunggede PSTN BROKEN
6 Ibeet in upstream of Siphon PSTN BROKEN

Water Level AWLR without telemetry system (PJT-II)

Image 44: Water Level AWLR without telemetry system (PJT-II)

Most of observe station which PJT-II operates, are recording water level manually. The raw
data are recorded in a cassette and each section staff collects the cassette once a month. After
collecting the cassette, PJT-II use EPROM reader that can extract data from cassette. Then
they use CIMSTA to calculate data to minutely, hourly and daily data.
Water Demand (PJT-II)
PJT-II also has an annual plan for water demand. There manage three kinds of area which is
irrigation area, industry area, and water supply company. However, PJT-II has no spatial data
for industry.

Image 45: Water Demand (PJT-II)

Each division collects the data and validates the data at the bi-weekly meeting named
TEPHASA Meeting with PJT-II HQ.
199
Water Level (DPSDA)
Not all of water level data and sets of spatial data are uploaded on official website of DPSDA
(http://dpsda.jabarprcv.go.id). It contains just only some part of whole data. DPSDA will
disseminate the annual report (yearbook) if it requested by people / other agency.

Image 46: Water Level (DPSDA)

The observe station does not record data in digital format. They have only hard (paper) copy
of data and DPSDA receives the hard copy directly from each observed station staff. DPSDA
also uses a software name PHU the input data in digital format. It can also extract data in
the excel file format.
Water Level AWLR with telemetry system (BBWSC)
BBWSC has four stations of AWLR, however there are also manual gauge at the same
location for case of emergency. This manual gauge is not in operation when AWLR is in
normal condition.

Image 47: Water Level AWLR with telemetry system (BBWSC)

Raw data from observation station are transmitted automatically with BBWSCs own
software. The software stores the data in text format and input average of hourly data as daily
data in excel format. With this excel format they publish a yearbook of hydrological data
annually.

200
Water Level Manual (BBWSC)
BBWSC has 20 stations (include the location of AWLR). Collected data is exactly same as
DPSDAs data.

Image 48: Water Level Manual (BBWSC)

Same as automatic water level station, manual water level station data are used as a data for
the yearbook of hydrological data.
Water Level Manual (PJT-II)
PJT-II considers 07:00 water level data as daily water level data.

Image 49: Water Level - Manual (PJT-II)

Usually PJT-II HQ collects data from each division bi-weekly and save the data in the SQL
database. But HQ also receives 7 a.m. data by SMS directly by the observation staff once a
day. They use this daily data to input values in the LCD excel file to keep the monitoring
system up to date.
201
Water Quality
Water Quality (PJT-II)
Most of stations location in fixed, however water quality observe stations location and
numbers of station changes every month.

Image 50: Water Quality (PJT-II)

Each division collects sample of water form targeted location. Then send the sample to the
laboratory. After analysis of the sample water, laboratory sends the result report in a carbon
copy format. Each division directly inputs the data to the database, not by the HQ office.
Water Quality (BPLHD)
BPLHD use software named SISLING to store data into the database and extract analysis
data which they can use as a report form. However, the database is secured by password and
they do not even know it. If we want to store all of previous data to DSS, they should collect
all of the excel file and input to DSS database by using data input wizard.

Image 51: Water Quality (BPLHD)

202
Climatology
Rainfall Automatic (PJT-II)
Procedure of rainfall (automatic) is exactly same as AWLR (with telemetry).

Image 52: Rainfall - Automatic (PJT-II)

Rainfall Manual (PJT-II)

Image 53: Rainfall Manual (PJT-II)

203
AWS Automatic Weather Station (PJT-II)
Procedure of rainfall (automatic) is exactly same as AWLR (without telemetry).

Image 54: AWS - Automatic Weather Station (PJT-II)

Rainfall (DPSDA)
Same as water level data in DPSDA, not all of rainfall and sets of spatial data are uploaded
on official website of DPSDA (http://dpsda.jabarprcv.go.id). It contains just only some part
of whole data. DPSDA will disseminate the annual report (yearbook) if it requested by people
/ other agency.

Image 55: Rainfall (DPSDA)

Rainfall (BBWSC)
BBWSC has 21 stations and collected data is exactly same as DPSDAs data.

Image 56: Rainfall (BBWSC)


204
Dam Operation
Dam (PJT-II)
PJT-II considers 00:00 data as daily data. PJT-II makes an annual plan for normal, dry, and
wet season to operate the dam effectively.

Image 57: Dam (PJT-II)

According from the user requirement specification, development team will try to implement
Dam Operation Plan feature which PJT-II staff can input annual plan and compare with
actual values.
Weir (PJT-II)
Procedure of data collection is exactly same as water level (manual); only the raw data is
different. PJT-II needs to store daily rainfall and discharge data to database, also the data sent
by SMS needs to be stored.

Image 58: Weir (PJT-II)


Importing weir data to DSS database was the most complicated process while developing the
data input module because the format of weir data are all different from another. Therefore,
we decided to develop an individual import module only for weir data.

205
Appendix 5: GIS Maps in Database

AWS (Automatic Weather Station)

206
Dam

207
Rainfall Station

208
Water Discharge

209
Water Quality

210
Weir

211
Appendix 6: Class Diagrams

Image 59: Data Objects

212
Image 60: Document View Model

213
Image 61: Data Export Wizard

214
Image 62: Data Import Wizard

215
Image 63: Data Search
216
Image 64: Document

217
Image 65: GIS Interaction

218
Image 66: GIS & Data Search Interaction
219
Image 67: Main
220
Image 68: Pane

221
Image 69: Station Management

222
Image 70: Enumeration
223
Image 71: Miscellaneous Models

224
Appendix 7: ERD (Entity-Relationship Diagram)

Hydrological database tables are grouped into 9 conceptual packages, as follows:


Base Info package: All of tables are the basic information in the database and
depended by all station information such as agency, catchment, district, subdistrict,
province, river territory, sub catchment and village. River_Territory_Info table
may be needed in the future for expansion, not only Citarum River Basin but also
other river basin.
Rainfall package: RF_Data_Daily table contains rainfall data that measured and
recorded every day (daily data). RF_Data_Daily table depends on
RF_Gauge_Info table that contains rainfall gauge station information. This is
because every record on RF_Data_Daily has a code of rainfall gauge station
which provided by RF_Gauge_Info table.
AWS package: BBWSC and PJT-II have AWS (Automatic Weather Station)
recording climatological data such as rainfall, humidity, temperature, etc. But,
they have different interval in data recording related to applied configuration in
the equipment. Therefore, climatological data are separately stored into 3 tables
based on its interval; there are six-minutely, hourly, and daily. AWS_Daily table
stores daily climatological data. AWS_Hourly table stores hourly climatological
data. Meanwhile, AWS_Minutely table stores six-minutely climatological data. All
of those tables are depends on AWS_Gauge_Info table which contains all
registered AWS stations from BBWSC and PJT-II.
Water Level package: Rating_Curve_Formula table contains rating curve
formulation for each registered water level gauge station. WL_Data_AWLR_Daily
table contains AWLR data that measured and recorded everyday by equipment,
meanwhile WL_Data_AWLR_Hourly table contains hourly data and
WL_Data_AWLR_Minutely table contains six-minutely data. For water level data
which measured by manual equipment, there is WL_Data_Man table which can
store all of those data. All of tables in this package are depends on
WL_Gauge_Info table which contains all water level gauge station, whether it is
automatic or manual equipment.
Water Quality package: This package stores all data which related to water quality
in the river (mainstream) including water quality sampling point information
(water quality gauge station), water quality parameter, water quality measurement
data, and water quality standard based on government regulation (Indonesia :
Baku Mutu Kualitas Air).
Water Quality (Industry) package: This package stores all data which related to
water quality in the industrys outlet including water quality gauge station
information (industry), industry classification (to implement equitable water
quality standards and rules), and water quality standard for industry.

225
Dam package: Collected data from each dam are different based on schematic or
characteristic of the dam. There so, we need to store data in separate table.
Dam_Data_Cirata table stores all collected data from Cirata dam,
Dam_Data_Saguling table stores all collected data from Saguling dam, and
Dam_Data_Jatiluhur table stores all collected data from Jatiluhur dam. As we
know that PJT-II creates annual dam operation plan for each dam, and make this
operation plan as a main indicator in water level monitoring and evaluation. There
so, this crucial information must be stores in database, we creates a
Dam_Oper_Plan table to store this information.
Weir package: As we know that there are some weir schematic and each
schematic provides different amount of data types, so we need to separate data
comes from special weir and common weir. Special weir can be identified such as
Barugbug weir, Bekasi weir, Cikarang weir, Gadung weir, Jengkol weir, Macan
weir, Salamdarma weir, and Cibeet weir. Water Demand package contains
WD_Data_Daily, WD_Intake_Point_Info, and WD_Pam_Intake_Plan table. This
package stores all collected data related to water demand especially water intake
by PAM DKI Jakarta (public water services) such as Pejompongan, Pulogadung,
and Buaran.
To implement the design of software, the design must be converted into a machine-readable
form. There so, the coding process or the code generation process performed on this phase.
Generally, coding processes are divides into 3 big modules, Graphical User Interface (GUI)
development as a communication interface between user and machine. Next module is the
database manipulation (insert, update, delete, etc.) module. Firstly, the database must be
established. Last, the Service module, this module provides interconnectivity between Server
Application and Client Application that existed as server services on server machine. Server
application shall response to all client applications request by this service. So, this service is
the main core in data storing, data searching, and data manipulation activities including data
importer and data exporter.

226
Hydrological D/B
Type: Package

Package: Data Model

Detail: Created on 05/01/2006 and last modified on 28/03/2011

Database Schema

Created By: Robbie on 09/03/2011

Last Modified: 30/01/2012, Version: 1.0

class Database Schema

DSS Software ERD(Entity Relationship Diagram)


Doc No : ERD-MAIN-01
Version : 1.0

Contain information about


region, watershed,
agency, etc...
Dam

+ DAM_DATA
Base Info
+ DAM_OPER_PLAN
Rainfall + AGENCY_INFO + DAM_INFO
+ CAT CHMENT _INFO
+ RF_DATA_DAILY
+ DISTRICT _INFO use
+ RF_GAUGE_INFO
use + PROVINCE_INFO
+ RIVER_TERRITORY_INFO
+ SUB_CAT CHMENT_INFO
+ SUB_DIST RICT_INFO
+ VILLAGE_INFO
Weir
use
+ WEIR_DAT A_Waduk_Cipancuh
use
AWS (Automatic Weather Station) + WEIR_SCHEMATIC
+ WEIR_SCHEMATIC_IMAGE
+ AWS_DAILY
+ WEIR_DAT A_Barugbug
+ AWS_GAUGE_INFO
+ WEIR_DAT A_Bekasi
+ AWS_HOURLY
+ WEIR_DAT A_Cikarang
+ AWS_MINUT ELY
+ WEIR_DAT A_Gadung
+ WEIR_DAT A_Jengkol
use
use + WEIR_DAT A_Macan
+ WEIR_DAT A_Salamdarma
+ WEIR_DAT A
+ WEIR_DAT A_Cibeet
+ WEIR_INFO

WaterLev el WaterQuality User Info Image Info


+ WL_DAT A_AWLR_DAILY + RIVER_CLASS_INFO + AUT HORITY_INFO + IMAGE_DAT A
+ WL_DAT A_AWLR_HOURLY + WQ_ST D_RIVER + USER_INFO
+ WL_DAT A_AWLR_MINUTELY + WQ_GAUGE_INFO
+ WL_DAT A_MAN + WQ_DATA
+ WL_GAUGE_INFO + WQ_PARAM
+ WL_RAT ING_CURVE

Image 72: DSS software ERD

227
AWS (Auto Weather Station)
Type: Package

Package: Hydrological D/B

Detail: Created on 05/04/2011 and last modified on 05/04/2011

AWS

Created By: zemna on 05/04/2011

Last Modified: 30/01/2012, Version: 1.0

class AWS

AWS(Automatic Weather Station) Database Structure - 1/2


Doc No : ERD-AWS-01
Versi on : 1.0

Base Info::RIVER_TERRITORY_INFO

col umn
*PK i d: i nt
nam e: varchar(50)

PK AWS_GAUGE_INFO
+ PK _RIVER_T E RRIT ORY_INFO(int)
1
col um n
*PK code: varchar(50)
ol d_stati on_i d: varchar(50)
Base Info::VILLAGE_INFO FK river_terri tory_i d: i nt
FK catchment_id: i nt
col umn FK agency_id: i nt
*PK i d: i nt 0..* FK vi ll age_i d: i nt
1
nam e: varchar(50) stati on_name: varchar(50)
stati on_type: i nt
0..* l ongi tude: fl oat
l ati tude: fl oat
el evati on: fl oat
Base Info::CATCHME NT_INFO
0..* observati on_start_ti me: datetim e
status: int
col umn
1
*PK i d: i nt
FK ri ver_terri tory_i d: i nt FK
name: varchar(50) 0..* + FK _AWS_GAUGE_INFO_AGENCY _INFO(i nt)
+ FK _AWS_GAUGE_INFO_CAT CHMENT _INFO(i nt)
+ FK _AWS_GAUGE_INFO_RIVER_T ERRIT ORY_INFO(i nt)
+ FK _AWS_GAUGE_INFO_VILLAGE_INFO(i nt)
Base Info::AGENCY _INFO P K
+ PK_AWS_GAUGE_INFO(varchar)
column
*PK id: i nt 1
name: varchar(50)

Associated Agency AWS _GAUGE_INFO


- PJT -II - S tore i nformati on about autom ati c weather stati on

AWS(Automatic Weather Station) Database Strucure - 2/2


Doc No : ERD-AWS-02
Versi on : 1.0

AWS_DAILY

col umn
*pfK code: varchar(50)
*PK date: dateti m e
T N: fl oat
T X : fl oat
T M : fl oat
IT N: varchar(50)
AWS_HOURLY
IT X: varchar(50)
UN: fl oat
col um n
UX : fl oat
*pfK code: varchar(50)
UM : fl oat
*PK date: dateti me
IUN: varchar(50)
hour: dateti me
IUX: varchar(50)
AWS_M INUTELY T : fl oat
U4: varchar(50)
U: fl oat
U6: varchar(50)
col umn U8: varchar(50)
U8: varchar(50)
*pfK code: varchar(50) U9: varchar(50)
U9: varchar(50)
*PK date: datetim e RR: fl oat
RR: fl oat
RR: fl oat RRX: float
RRX: fl oat
DRR: varchar(50)
IRRX : varchar(50)
VT : fl oat
FK DRR: varchar(50)
VX: fl oat
+ FK_AWS_MINUT ELY _AWS_GAUGE _INFO(varchar) HH: varchar(50)
VM: float
PK VN: fl oat
GV: fl oat
+ P K_A WS_MINUT ELY(varchar, dateti me) VNE: fl oat
RG: fl oat
VE : fl oat
PS: fl oat
VS E: fl oat
HH: varchar(50)
VS : fl oat
BA: fl oat
VS O: float
VO: fl oat
FK VNO: float
+ FK _AWS_HOURLY _AWS_GAUGE_INFO(varchar) GIX: fl oat
P K VT : fl oat
+ PK_AWS _HOURLY(varchar, dateti me) VX : fl oat
IVX: varchar(50)
RG: fl oat
PS : fl oat
PS X: fl oat
IPSX : varchar(50)
BA : fl oat
BA N: fl oat
BA X: fl oat
Associated Agency AWS_M INUTELY IBAN: varchar(50)
- PJT -II - 6-mi nutes weather data IBAX : varchar(50)
AWS_HOURLY
- hourl y weather data
FK
AWS_DAILY
+ FK_AWS_DAILY_AWS_GA UGE _INFO(varchar)
- dai ly weather data
PK
+ PK _AWS_DAILY(varchar, dateti me)

Image 73: AWS (Auto Weather Station)


228
AWS_DAILY

Database: SQL Server 2005, Stereotype: table, Package: AWS (Automatic Weather
Station)

Detail: Created on 18/03/2011 and last modified on 30/01/2012

Notes: Table of daily AWS data.

Columns
Not
PK Name Type Unique Len Prec Scale Init Notes
Null
True code varchar True False 50 AWS gauge station code
True date datetime True False record date
Minimum Temperature
False TN float False False
(0C)
Maximum Temperature
False TX float False False
(0C)
Average Temperature
False TM float False False
(0C)
Time of Minimum
False ITN varchar False False 50
Temperature (hh.mm)
Time of Maximum
False ITX varchar False False 50
Temperature (hh.mm)
False UN float False False Minimum Humidity (%)
Maximum Humidity
False UX float False False
(%)
False UM float False False Average Humidity (%)
Time of Minimum
False IUN varchar False False 50
Humidity (hh.mm)
Time of maximum
False IUX varchar False False 50
humidity (hh.mm)
Duration of temperature
False U4 varchar False False 50
less than 40% (hh.mm)
Duration of temperature
False U6 varchar False False 50 condition between 60%
up to 80% (in %)
Duration of temperature
False U8 varchar False False 50 condition between 80%
up to 90% (in %)
Duration of temperature
False U9 varchar False False 50 condition more than
90% (in %)
False RR float False False Rainfall (mm)
Maximum rainfall
False RRX float False False
intensity (mm)
Time of maximum
False IRRX varchar False False 50
rainfall (hh.mm)
Rainfall duration
False DRR varchar False False 50
(hh.mm)
Duration of leaf
False HH varchar False False 50 humidity equal to 1;
humid; (hh.mm)
False VN float False False Wind distance to the
229
North (Km)
Wind distance to the
False VNE float False False
North East (Km)
Wind distance to the
False VE float False False
East (Km)
Wind distance to the
False VSE float False False
South East (Km)
Wind distance to the
False VS float False False
South (Km)
Wind distance to the
False VSO float False False
South West (Km)
Wind distance to the
False VO float False False
West (Km)
Wind distance to the
False VNO float False False
North West (Km)
Wind direction of
False GIX float False False maximum wind distance
(degree or 0)
Total wind distance
False VT float False False
(Km)
False VX float False False Wind speed (m/s)
Time of maximum wind
False IVX varchar False False 50
speed (hh.mm)
Total of global radiation
False RG float False False
(J/cm2)
Total electric current on
False PS float False False
Solar Panel (mAh)
Actual electric current
False PSX float False False
from Solar Panel (mAh)
Time of maximum
False IPSX varchar False False 50
current(hh.mm)
Battery voltage at 00.00
False BA float False False
am (Volt)
Minimum battery
False BAN float False False
voltage (Volt)
Maximum battery
False BAX float False False
voltage (Volt)
Time of minimum
False IBAN varchar False False 50
battery (hh.mm)
Time of maximum
False IBAX varchar False False 50
battery (hh.mm)

Constraints
Name Type Columns Initial Code Notes
FK_AWS_DAILY_AWS_GAUGE_INFO Public code
code
PK_AWS_DAILY Public
date

Relationships
Columns Association Notes
0..* AWS_DAILY.FK_AWS_DAILY_AWS_GAUGE_INFO
(code = code)
1 AWS_GAUGE_INFO.PK_AWS_GAUGE_INFO
230
AWS_GAUGE_INFO

Database: SQL Server 2005, Stereotype: table, Package: AWS (Automatic Weather
Station)

Detail: Created on 16/03/2011 and last modified on 30/01/2012

Notes: Table of AWS gauge station information.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True code varchar True False 50 Gauge Station code
old_station
False varchar False False 50 Old Station ID
_id
river_territ
False int False False River Territory
ory_id
catchment_
False int False False Catchment ID
id
False agency_id int False False Agency ID
False village_id int False False Village ID
station_na
False varchar False False 50 Station Name
me
station_typ 0 : manual
False int False False
e 1 : automatic
False longitude float False False Longitude
False latitude float False False Latitude
False elevation float False False Elevatiaon
observation Start date of
False datetime False False
_start_time observation
0 = not operating
False status int False False
1 = operating

Constraints
Name Type Columns Initial Code Notes
FK_AWS_GAUGE_INFO_
Public agency_id
AGENCY_INFO
FK_AWS_GAUGE_INFO_
Public catchment_id
CATCHMENT_INFO
FK_AWS_GAUGE_INFO_
RIVER_TERRITORY_INF Public river_territory_id
O
FK_AWS_GAUGE_INFO_
Public village_id
VILLAGE_INFO
PK_AWS_GAUGE_INFO Public code

231
Relationships
Columns Association Notes
0..* AWS_GAUGE_INFO.FK_AWS_GAUGE_INFO_AGENCY_INFO
(agency_id = id)
1 AGENCY_INFO.PK_AGENCY_INFO
0..*
(catchment_id = id) AWS_GAUGE_INFO.FK_AWS_GAUGE_INFO_CATCHMENT_INFO
1 CATCHMENT_INFO.PK_CATCHMENT_INFO
0..* AWS_GAUGE_INFO.FK_AWS_GAUGE_INFO_VILLAGE_INFO
1 VILLAGE_INFO.PK_Village
0..* AWS_MINUTELY.FK_AWS_MINUTELY_AWS_GAUGE_INFO
(code = code)
1 AWS_GAUGE_INFO.PK_AWS_GAUGE_INFO
0..* AWS_HOURLY.FK_AWS_HOURLY_AWS_GAUGE_INFO
(code = code)
1 AWS_GAUGE_INFO.PK_AWS_GAUGE_INFO
0..*
(river_territory_id = AWS_GAUGE_INFO.FK_AWS_GAUGE_INFO_RIVER_TERRITORY_I
id) NFO
1 RIVER_TERRITORY_INFO.PK_RIVER_TERRITORY_INFO
0..* AWS_DAILY.FK_AWS_DAILY_AWS_GAUGE_INFO
(code = code)
1 AWS_GAUGE_INFO.PK_AWS_GAUGE_INFO

AWS_HOURLY

Database: SQL Server 2005, Stereotype: table, Package: AWS (Automatic Weather
Station)

Detail: Created on 18/03/2011 and last modified on 30/01/2012

Notes: Table of Hourly AWS data

Columns
Not
PK Name Type Unique Len Prec Scale Init Notes
Null
True code varchar True False 50 Station code
True date datetime True False Record date
False hour datetime False False Record hour
False T float False False Temperature (0C)
False U float False False Humidity (%)
Duration of humidity
False U8 varchar False False 50 between 80% to 90%
(hh.mm)
Duration of humidity more
False U9 varchar False False 50
than 90% (hh.mm)
False RR float False False Rainfall (mm)
False RRX float False False Maximum rainfall (mm)
False DRR varchar False False 50 Rainfall duration (hh.mm)
False VT float False False Total wind (km)
Maximum wind speed
False VX float False False
(m/s)
False VM float False False Average wind speed (m/s)
Average wind direction
False GV float False False
from last 10 minutes (0)
Total of global radiation
False RG float False False
(J/cm2)
232
Electric Current on Solar
False PS float False False
Panel (mAh)
Duration of humid; leaf
False HH varchar False False 50
humidity = 1 (hh.mm)
battery status/Voltage
False BA float False False
(Volt)

Constraints
Name Type Columns Initial Code Notes
FK_AWS_HOURLY_A
Public code
WS_GAUGE_INFO
code
PK_AWS_HOURLY Public
date

Relationships
Columns Association Notes
0..*
AWS_HOURLY.FK_AWS_HOURLY_AWS_GAUGE
(code = code)
_INFO
1 AWS_GAUGE_INFO.PK_AWS_GAUGE_INFO

AWS_MINUTELY

Database: SQL Server 2005, Stereotype: table, Package: AWS (Automatic Weather
Station)

Detail: Created on 25/03/2011 and last modified on 30/01/2012

Notes: Table of minutely AWS data. (Only rainfall data)

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True code varchar True False 50 Station code
datetim
True date True False Record Date
e
False RR float False False Rainfall (mm)

Constraints
Name Type Columns Initial Code Notes
FK_AWS_MINUTELY_AWS_GAUG
Public code
E_INFO
PK_AWS_MINUTELY Public code date

Relationships
Columns Association Notes
0..*
AWS_MINUTELY.FK_AWS_MINUTELY_AWS_GAUG
(code = code)
E_INFO
1 AWS_GAUGE_INFO.PK_AWS_GAUGE_INFO
233
Base Info
Type: Package

Package: Hydrological D/B

Detail: Created on 05/04/2011 and last modified on 06/04/2011

Base Info

Created By: zemna on 05/04/2011

Last Modified: 20/10/2011, Version: 1.0

class Base Info

Base Information Database Structure - [Region]


Doc No : ERD-BI-01
Version : 1.0

PROVINCE_INFO DISTRICT_INFO SUB_DISTRICT_INFO VILLAGE_INFO

column column column column


*PK id: int *PK id: int *PK id: int *PK id: int
name: varchar(50) name: varchar(50) name: varchar(50) name: varchar(50)
FK province_id: int FK district_id: int sub_district_id: int
1 0..* 1 0..* 1 0..*
PK
+ PK_PROVINCE_INFO(int) FK FK PK
+ FK_DISTRICT _INFO_PROVINCE_INFO(int) + FK_SUB_DISTRICT _INFO_DIST RICT_INFO(int) + PK_VILLAGE_INFO(int)
PK PK
+ PK_DIST RICT_INFO(int) + PK_SUB_DIST RICT_INFO(int)

Associated Agency PROVINCE_INFO


- ALL - Province Information
DISTRICT_INFO
- District Information
SUB_DISTRICT_INFO
- Sub District Information
VILLAGE_INFO
- Village Information

Image 74: Base Information Database Structure (Region)

234
class Base Info

Base Information Database Structure - [Watershed, Agency]


Doc No : ERD-BI-02
Version : 1.0

CATCHMENT_INFO

column
RIVER_TERRITORY_INFO *PK id: int
FK river_territory_id: int
column name: varchar(50)
*PK id: int area_km: float
name: varchar(50) area_ha: float
1 0..*
perimeter: float
PK
+ PK_RIVER_T ERRIT ORY_INFO(int) PK
+ PK_CATCHMENT_INFO(int) AGENCY_INFO
FK
+ FK_CATCHMENT_INFO_RIVER_TERRITORY(int) column
*PK id: int
1 name: varchar(50)

PK
+ PK_AGENCY_INFO(int)
0..*

SUB_CATCHMENT_INFO

column
*PK id: int
FK catchment_id: int
name: varchar(50)
area: float
area_ha: float
perimeter: float

FK
+ FK_SUB_CATCHMENT_INFO_CATCHMENT_INFO(int)
PK
+ PK_SUB_CATCHMENT_INFO(int)

Associated Agency RIVER_TERRITORY_INFO


- ALL - River Territory Information
CATCHMENT_INFO
- Catchment Information
SUB_CATCHMENT_INFO
- Sub Catchment Informaion
AGENCY_INFO
- Agency Information

Image 75: Base Information Database Structure (Watershed, Agency)

AGENCY_INFO

Database: SQL Server 2005, Stereotype: table, Package: Base Info

Detail: Created on 09/03/2011 and last modified on 30/01/2012

Notes: Table of Agency information

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True id int True False Agency ID
False name varchar False False 50 Agency's Name

Constraints
Name Type Columns Initial Code Notes
PK_AGENCY_INFO Public id

235
Relationships
Columns Association Notes
0..* WQ_GAUGE_INFO.FK_WQ_GAUGE_INFO_AGENCY_INFO
(agency_id = id)
1 AGENCY_INFO.PK_AGENCY_INFO
0..* RF_GAUGE_INFO.FK_RF_GAUGE_INFO_AGENCY_INFO
1 AGENCY_INFO.PK_agency
0..*
(agency_id = id) AWS_GAUGE_INFO.FK_AWS_GAUGE_INFO_AGENCY_INFO
1 AGENCY_INFO.PK_AGENCY_INFO
0..* WEIR_INFO.FK_WEIR_INFO_AGENCY_INFO
(agency_id = id)
1 AGENCY_INFO.PK_AGENCY_INFO
0..* DAM_INFO.FK_DAM_INFO_AGENCY_INFO
(agency_id = id)
1 AGENCY_INFO.PK_AGENCY_INFO
0..* WL_GAUGE_INFO.FK_WL_GAUGE_INFO_AGENCY_INFO
(agency_id = id)
1 AGENCY_INFO.PK_AGENCY_INFO

CATCHMENT_INFO

Database: SQL Server 2005, Stereotype: table, Package: Base Info

Detail: Created on 09/03/2011 and last modified on 30/01/2012

Notes: Table of Catchment information

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True id int True False Catchment ID
river_territory River Territory
False int False False 0 0 0
_id ID
Catchment
False name varchar False False 50
name
Total area in
False area_km float False False
KM2
False area_ha float False False Total area in ha
False perimeter float False False Perimeter

Constraints
Name Type Columns Initial Code Notes
PK_CATCHMENT_INFO Public id
FK_CATCHMENT_INFO_
Public river_territory_id
RIVER_TERRITORY

236
Relationships
Columns Association Notes
0..* RF_GAUGE_INFO.FK_RF_GAUGE_INFO_CATCHMENT_INFO
1 CATCHMENT_INFO.PK_river_basin
0..*
(catchment_id = SUB_CATCHMENT_INFO.FK_SUB_CATCHMENT_INFO_CATCHMENT_
id) INFO
1 CATCHMENT_INFO.PK_CATCHMENT_INFO
(catchment_id = 0..* WQ_GAUGE_INFO.FK_WQ_GAUGE_INFO_CATCHMENT_INFO
id) 1 CATCHMENT_INFO.PK_CATCHMENT_INFO
(catchment_id = 0..* AWS_GAUGE_INFO.FK_AWS_GAUGE_INFO_CATCHMENT_INFO
id) 1 CATCHMENT_INFO.PK_CATCHMENT_INFO
(catchment_id = 0..* DAM_INFO.FK_DAM_INFO_CATCHMENT_INFO
id) 1 CATCHMENT_INFO.PK_CATCHMENT_INFO
(catchment_id = 0..* WEIR_INFO.FK_WEIR_INFO_CATCHMENT_INFO
id) 1 CATCHMENT_INFO.PK_CATCHMENT_INFO
(river_territory_ 0..* CATCHMENT_INFO.FK_CATCHMENT_INFO_RIVER_TERRITORY
id = id) 1 RIVER_TERRITORY_INFO.PK_RIVER_TERRITORY_INFO
(catchment_id = 0..* WL_GAUGE_INFO.FK_WL_GAUGE_INFO_CATCHMENT_INFO
id) 1 CATCHMENT_INFO.PK_CATCHMENT_INFO

DISTRICT_INFO

Database: SQL Server 2005, Stereotype: table, Package: Base Info

Detail: Created on 23/03/2011 and last modified on 30/01/2012

Notes: Table of District information

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True id int True False District ID
False name varchar False False 50 District's name
False province_id int False False 0 0 0 Province ID

Constraints
Name Type Columns Initial Code Notes
FK_DISTRICT_INFO_PROVINC
Public province_id
E_INFO
PK_DISTRICT_INFO Public id

Relationships
Columns Association Notes
0..*
(district_id = id) SUB_DISTRICT_INFO.FK_SUB_DISTRICT_INFO_DISTRICT_INFO
1 DISTRICT_INFO.PK_DISTRICT_INFO
0..* WQ_GAUGE_INFO.FK_WQ_GAUGE_INFO_DISTRICT_INFO
(district_id = id) 1 DISTRICT_INFO.PK_DISTRICT_INFO
0..* DISTRICT_INFO.FK_DISTRICT_INFO_PROVINCE_INFO
(province_id = id) 1 PROVINCE_INFO.PK_PROVINCE_INFO

237
PROVINCE_INFO

Database: SQL Server 2005, Stereotype: table, Package: Base Info

Detail: Created on 23/03/2011 and last modified on 30/01/2012

Notes: Table of Province information

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True id int True False Province ID
False name varchar False False 50 Province name

Constraints
Name Type Columns Initial Code Notes
PK_PROVINCE_INFO Public id

Relationships
Columns Association Notes
0..* DISTRICT_INFO.FK_DISTRICT_INFO_PROVINCE_INFO
(province_id = id) 1 PROVINCE_INFO.PK_PROVINCE_INFO

RIVER_TERRITORY_INFO

Database: SQL Server 2005, Stereotype: table, Package: Base Info

Detail: Created on 10/03/2011 and last modified on 30/01/2012

Notes: Table of River Territory information

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True id int True False River Territory ID
False name varchar False False 50 River Territory name

Constraints
Name Type Columns Initial Code Notes
PK_RIVER_TERRITORY
Public id
_INFO

238
Relationships
Columns Association Notes
0..* WQ_GAUGE_INFO.FK_water_quality_station_river_territory
1 RIVER_TERRITORY_INFO.PK_river_territory
0..* DAM_INFO.FK_hydraulic_structure_river_territory
1 RIVER_TERRITORY_INFO.PK_river_territory
0..* WL_GAUGE_INFO.FK_gauge_station_river_territory
1 RIVER_TERRITORY_INFO.PK_river_territory
(river_territ 0..* CATCHMENT_INFO.FK_CATCHMENT_INFO_RIVER_TERRITORY
ory_id = id) 1 RIVER_TERRITORY_INFO.PK_RIVER_TERRITORY_INFO
(river_territ 0..* AWS_GAUGE_INFO.FK_AWS_GAUGE_INFO_RIVER_TERRITORY_INFO
ory_id = id) 1 RIVER_TERRITORY_INFO.PK_RIVER_TERRITORY_INFO

SUB_CATCHMENT_INFO

Database: SQL Server 2005, Stereotype: table, Package: Base Info

Detail: Created on 09/03/2011 and last modified on 30/01/2012

Notes: Table of Sub-Catchment information

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
Sub-Catchment
True id int True False
ID
catchment_
False int False False 0 0 0 Catchment ID
id
Sub-catchment
False name varchar False False 50
name
Total area in
False area float False False
Km2
False area_ha float False False Total area in ha
False perimeter float False False Perimeter

Constraints
Name Type Columns Initial Code Notes
FK_SUB_CATCHMENT_INFO_CATCHMENT_INFO Public catchment_id
PK_SUB_CATCHMENT_INFO Public id

Relationships
Columns Association Notes
0..*
(catchment_id = SUB_CATCHMENT_INFO.FK_SUB_CATCHMENT_INFO_CATCHMENT_I
id) NFO
1 CATCHMENT_INFO.PK_CATCHMENT_INFO

239
SUB_DISTRICT_INFO

Database: SQL Server 2005, Stereotype: table, Package: Base Info

Detail: Created on 23/03/2011 and last modified on 30/01/2012

Notes: Table of Sub-district information

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True id int True False Sub-district ID
Sub-district
False name varchar False False 50
name
False district_id int False False 0 0 0 District ID

Constraints
Name Type Columns Initial Code Notes
FK_SUB_DISTRICT_INFO_DISTRICT_INFO Public district_id
PK_SUB_DISTRICT_INFO Public id

Relationships
Columns Association Notes
0..* SUB_DISTRICT_INFO.FK_SUB_DISTRICT_INFO_DISTRICT_INFO
(district_id = id)
1 DISTRICT_INFO.PK_DISTRICT_INFO
0..* VILLAGE_INFO.FK_Village_Subdistrict
1 SUB_DISTRICT_INFO.PK_Subdistrict

VILLAGE_INFO

Database: SQL Server 2005, Stereotype: table, Package: Base Info

Detail: Created on 23/03/2011 and last modified on 30/01/2012

Notes: Table of village information

Columns
Not
PK Name Type Unique Len Prec Scale Init Notes
Null
True id int True False Village ID
False name varchar False False 50 Village name
False sub_district_id int False False Sub-district ID

Constraints
Name Type Columns Initial Code Notes
PK_VILLAGE_INFO Public id

240
Relationships
Columns Association Notes
0..* WL_GAUGE_INFO.FK_WL_GAUGE_INFO_VILLAGE_INFO
1 VILLAGE_INFO.PK_Village
0..* RF_GAUGE_INFO.FK_RF_GAUGE_INFO_VILLAGE_INFO
1 VILLAGE_INFO.PK_Village
0..* DAM_INFO.FK_DAM_INFO_VILLAGE_INFO
1 VILLAGE_INFO.PK_Village
0..* WQ_GAUGE_INFO.FK_WQ_GAUGE_INFO_VILLAGE_INFO
1 VILLAGE_INFO.PK_Village
0..*
AWS_GAUGE_INFO.FK_AWS_GAUGE_INFO_VILLAGE_INFO
1 VILLAGE_INFO.PK_Village
0..* WEIR_INFO.FK_WEIR_INFO_VILLAGE_INFO
(village_id = id)
1 VILLAGE_INFO.PK_VILLAGE_INFO
0..* VILLAGE_INFO.FK_Village_Subdistrict
1 SUB_DISTRICT_INFO.PK_Subdistrict

241
Dam
Type: Package

Package: Hydrological D/B

Detail: Created on 05/04/2011 and last modified on 06/04/2011.

Dam

Created B: zemna on 05/04/2011

Last Modified: 30/01/2012, Version: 1.0

class Dam

Dam Database Structure (Info, Operation Plan, Data)


Doc No : ERD-DAM-01
Version : 1.0

DAM_OPER_PLAN

column
*PK rec_id: bigint
FK code: varchar(50)
Base Info::VILLAGE_INFO date: datetime
normal: float
column DAM_INFO dry: float
*PK id: int 1 wet: float
name: varchar(50) column maks: float
*PK code: varchar(50) min: float
old_dam_id: varchar(50)
FK river_territory_id: int
FK
FK catchment_id: int
0..* + FK_DAM_OPER_PLAN_DAM_INFO(varchar)
0..* FK agency_id: int PK
FK village_id: int
name: varchar(50) + PK_DAM_OPER_PLAN(bigint)
type: int 1
Base Info::CATCHMENT_INFO
location_category: int
column longitude: float
*PK id: int latitude: float DAM_DATA
1 0..*
FK river_territory_id: int elevation: float
name: varchar(50) status: int column
postfix: varchar(50) *pfK code: varchar(8)
1 *PK date: datetime
FK T MA: float
0..* + FK_DAM_INFO_AGENCY_INFO(int) AM: float
+ FK_DAM_INFO_CAT CHMENT _INFO(int) 0..* AML: float
+ FK_DAM_INFO_VILLAGE_INFO(int) AK: float
PK AKTb: float
Base Info::AGENCY_INFO HJV: float
+ PK_DAM_INFO(varchar)
Spillway: float
column T otal: float
*PK id: int 1 power_production_kwh: float
name: varchar(50) power_production_MW: float

FK
+ FK_DAM_DAT A_DAM_INFO(varchar)
PK
+ PK_DAM_DAT A(varchar, datetime)

Associated Agency DAM_INFO


- PJT-II - Dam Information
DAM_OPER_PLAN
- Annual DAM Operational Plan.

Image 76: Dam Database Structure (Info, Operation Plan, Data)

242
DAM_DATA

Database: SQL Server 2005, Stereotype: table, Package: Dam

Detail: Created on 20/10/2011 and last modified on 30/01/2012

Notes: Table of water quantity data in DAM, including the amount of power production.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
varc
True code True False 8 Dam Code
har
datet
True date True False Record Date
ime
False TMA float False False Water level
False AM float False False Inflow
Inflow from
False AML float False False
Overflow
False AK float False False Outflow
Outflow in the
False AKTb float False False
turbine
Outflow in the
False HJV float False False
Hollow Jet
Overflow in the
False Spillway float False False
Spillway
False Total float False False Total Outflow
Amount of
power
power_production
False float False False production in
_kwh
Kilo Watt per
Hour (KWH)
Total of power
power_production production in
False float False False
_MW Mega Watt
(MW)

Constraints
Name Type Columns Initial Code Notes
FK_DAM_DATA_DAM_INFO Public code
PK_DAM_DATA Public code date

Relationships
Columns Association Notes
0..* DAM_DATA.FK_DAM_DATA_DAM_INFO
(code = code)
1 DAM_INFO.PK_DAM_INFO

243
DAM_OPER_PLAN

Database: SQL Server 2005, Stereotype: table, Package: Dam

Detail: Created on 24/03/2011 and last modified on 20/10/2011

Notes: Reservoir Operational Plan PJT-II

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True rec_id bigint True False
code of water
varcha
False code False False 50 0 0 level gauge
r
station
dateti
False date False False Planned Date
me
water level
False normal float False False estimation for
normal condition
water level
False dry float False False estimation for dry
condition
water level
False wet float False False estimation for
wet condition
maximum
False maks float False False
threshold
minimum
False min float False False
threshold

Constraints
Name Type Columns Initial Code Notes
FK_DAM_OPER_PLAN_DAM_INFO Public code
PK_DAM_OPER_PLAN Public rec_id

Relationships
Columns Association Notes
0..* DAM_OPER_PLAN.FK_DAM_OPER_PLAN_DAM_INFO
(code = code)
1 DAM_INFO.PK_DAM_INFO

244
DAM_INFO

Database: SQL Server 2005, Stereotype: table, Package: Dam

Detail: Created on 16/03/2011 and last modified on 30/01/2012

Notes: Table of DAM structure information

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
varcha
True code True False 50 Dam Code
r
varcha
False old_dam_id False False 50 Old Code
r
river_territory River Territory
False int False False
_id ID
False catchment_id int False False Catchment ID
False agency_id int False False Agency ID
False village_id int False False Village ID
varcha
False name False False 50 Dam Name
r
0 : dam
1 : weir
False type int False False 2 : syphon
3 : diversion
intake structure
0 : located in
main canal
location_categ
False int False False 1 : located in
ory
secondary canal
2 : other
False longitude float False False Longitude
False latitude float False False Latitude
False elevation float False False Elevation
0 = not
False status int False False operating
1 = operating
varcha
False postfix False False 50
r

Constraints
Name Type Columns Initial Code Notes
FK_DAM_INFO_AGENCY_INFO Public agency_id
FK_DAM_INFO_CATCHMENT_INFO Public catchment_id
FK_DAM_INFO_VILLAGE_INFO Public village_id
PK_DAM_INFO Public code

245
Relationships
Columns Association Notes
0..* DAM_DATA.FK_DAM_DATA_DAM_INFO
(code = code)
1 DAM_INFO.PK_DAM_INFO
0..* DAM_INFO.FK_DAM_INFO_VILLAGE_INFO
1 VILLAGE_INFO.PK_Village
0..* DAM_INFO.FK_hydraulic_structure_river_territory
1 RIVER_TERRITORY_INFO.PK_river_territory
0..* DAM_INFO.FK_DAM_INFO_CATCHMENT_INFO
(catchment_id = id)
1 CATCHMENT_INFO.PK_CATCHMENT_INFO
0..* DAM_INFO.FK_DAM_INFO_AGENCY_INFO
(agency_id = id)
1 AGENCY_INFO.PK_AGENCY_INFO
0..* DAM_OPER_PLAN.FK_DAM_OPER_PLAN_DAM_INFO
(code = code)
1 DAM_INFO.PK_DAM_INFO

246
Image Info
Type: Package

Package: Hydrological D/B

Detail: Created on 20/10/2011.

Image Info

Created By: HP on 20/10/2011

Last Modified: 30/01/2012, Version: 1.0

dm Image Info

Image Data (For all gauge station and hydraulic structure)

Dam::DAM_INFO

column
IMAGE_DATA 1 *PK code: varchar(50)

column
*pfK code: varchar(8) 0..*
*PK index: int
AWS (Automatic Weather Station)::AWS_GAUGE_INFO
image: image
hash: varchar(32)
column
0..* *PK code: varchar(50)
FK 1
+ FK_IMAGE_DATA_AWS_GAUGE_INFO(varchar)
+ FK_IMAGE_DATA_DAM_INFO(varchar) 0..*
+ FK_IMAGE_DATA_RF_GAUGE_INFO(varchar) Rainfall::RF_GAUGE_INFO
+ FK_IMAGE_DATA_WEIR_INFO(varchar)
+ FK_IMAGE_DATA_WL_GAUGE_INFO(varchar) column
0..* 1
+ FK_IMAGE_DATA_WQ_GAUGE_INFO(varchar) *PK code: varchar(50)
unique
+ UQ_IMAGE_DATA_code(varchar)
0..*
PK WaterLev el::WL_GAUGE_INFO
+ PK_IMAGE_DATA(varchar, int)
1 column
0..*
*PK code: varchar(50)

1
WaterQuality::WQ_GAUGE_INFO
Weir::WEIR_INFO
column
column 1
*PK code: varchar(50)
*PK code: varchar(8)

Image 77: Image Data (for all gauge station and hydraulic structure)

247
IMAGE_DATA

Database: SQL Server 2008, Stereotype: table, Package: Image Info

Detail: Created on 20/10/2011 and last modified on 30/01/2012

Notes: Table of Image data. This image includes figures or photos of each hydraulic
structure and gauge station in CRBDSS.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
gauge station codes
True code varchar True True 8 0 0 or hydraulic structure
codes
Indexing for image of
True index int True True 0 0 0
a station.
Image data in
False image image False False 0 0 0
DBImage format
Generated hash
False hash varchar False False 32 0 0 number to identify
each pictures.

Constraints
Name Type Columns Initial Code Notes
PK_IMAGE_DATA Public code index

248
Rainfall
Type: Package

Package: Hydrological D/B

Detail: Created on 05/04/2011and last modified on 30/01/2012.

Notes: Rainfall (mm)

Rainfall

Created By: zemna on 05/04/2011

Last Modified: 06/04/2011, Version: 1.0

class Rainfall

Rainfall Database Structure


Doc No : ERD-RF-01
Versi on : 1.0

Base Info::VILLAGE_INFO

column
*PK id: int
name: varchar(50) 1
RF_GAUGE_INFO

column
*PK code: varchar(50)
old_stati on_id: varchar(50)
RF_DATA_DAILY
0..* FK vil lage_id: int
FK catchment_id: i nt
column
FK agency_id: int
Base Info::CATCHMENT_INFO *pfK code: varchar(50)
name: varchar(50)
*PK date: datetime
l ongi tude: fl oat
column l atitude: float value: float
*PK id: int elevati on: float
1 0..* 1 0..*
FK river_terri tory_id: int observation_start_time: datetime FK
name: varchar(50) status: int + FK_RF_DATA_DAILY_RF_GAUGE_INFO(varchar)
PK
FK + PK_RF_DAT A_DAILY(varchar, dateti me)
+ FK_RF_GAUGE_INFO_AGENCY_INFO(int)
0..* + FK_RF_GAUGE_INFO_CATCHMENT_INFO(int)
+ FK_RF_GAUGE_INFO_VILLAGE_INFO(int)
PK
Base Info::AGENCY_INFO + PK_RF_GAUGE_INFO(varchar)

column
*PK id: int 1
name: varchar(50)

Associated Agency RF_GAUGE_INFO


- BBWSC, DPSDA, PJT-II - Store gauge informati on
RF_DATA_DAILY
- Store dail y rainfall data

Image 78: Rainfall Database Structure

249
RF_DATA_DAILY

Database: SQL Server 2005, Stereotype: table, Package: Rainfall

Detail: Created on 18/03/2011 and last modified on 30/01/2012

Notes: Table of daily Rainfall data

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
RF gauge station
True code varchar True False 50
code
True date datetime True False record date
False value float False False

Constraints
Name Type Columns Initial Code Notes
FK_RF_DATA_DAILY_RF_GAUGE_INFO Public code
PK_RF_DATA_DAILY Public code date

Relationships
Columns Association Notes
0..* RF_DATA_DAILY.FK_RF_DATA_DAILY_RF_GAUGE_INFO
(code = code)
1 RF_GAUGE_INFO.PK_RF_GAUGE_INFO

250
RF_GAUGE_INFO

Database: SQL Server 2005, Stereotype: table, Package: Rainfall

Detail: Created on 03/04/2011 and last modified on 30/01/2012

Notes: Table of Rainfall Gauge Station information

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
RF Gauge
True code varchar True False 50
Station code
False old_station_id varchar False False 50 Old Station ID
False village_id int False False Village ID
False catchment_id int False False Catchment ID
False agency_id int False False Agency ID
RF station
False name varchar False False 50
name
False longitude float False False Longitude
False latitude float False False Latitude
False elevation float False False Elevation
observation_st Start date of
False datetime False False
art_time observation
0 = not
False status int False False operating
1 = operating

Constraints
Name Type Columns Initial Code Notes
FK_RF_GAUGE_INFO_AGENCY_INFO Public agency_id
FK_RF_GAUGE_INFO_CATCHMENT_INFO Public catchment_id
FK_RF_GAUGE_INFO_VILLAGE_INFO Public village_id
PK_RF_GAUGE_INFO Public code

Relationships
Columns Association Notes
0..* RF_GAUGE_INFO.FK_RF_GAUGE_INFO_CATCHMENT_INFO
1 CATCHMENT_INFO.PK_river_basin
0..* RF_GAUGE_INFO.FK_RF_GAUGE_INFO_VILLAGE_INFO
1 VILLAGE_INFO.PK_Village
0..* RF_GAUGE_INFO.FK_RF_GAUGE_INFO_AGENCY_INFO
1 AGENCY_INFO.PK_agency
0..* RF_DATA_DAILY.FK_RF_DATA_DAILY_RF_GAUGE_INFO
(code = code)
1 RF_GAUGE_INFO.PK_RF_GAUGE_INFO

251
User Info
Type: Package

Package: Hydrological D/B

Detail: Created on 20/10/2011and last modified on 20/10/2011.

\USER_INFO

Created By: HP on 20/10/2011

Last Modified: 30/01/2012, Version: 1.0

dm USER_INFO

AUTHORITY_INFO

column
*PK No: int
* Name: varchar(100)
* DataSearch: bit
* DataModify: bit
* DamOperationPlan: bit
* WeirSchematic: bit
* DataImport: bit
* StationManagement: bit
* UserManagement: bit
1
PK
+ PK_AUTHORITY_INFO(int)

USER_INFO

column 0..*
*PK ID: varchar(20)
* Name: varchar(50)
FK Agency: int
*FK Authority: int
* Password: varchar(50)

PK
+ PK_USER_INFO(varchar)
FK
+ FK_USER_INFO_AGENCY_INFO(int)
+ FK_USER_INFO_AUTHORITY_INFO(int)

Image 79: User Info

252
AUTHORITY_INFO

Database: SQL Server 2008, Stereotype: table, Package: User Info

Detail: Created on 20/10/2011 and last modified on 30/01/2012

Notes: Table of Authority group information

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
Authority
True No int True True 0 0 0
Number
Authority
False Name varchar True False 100 0 0
Name
Allow Data
False Data Search bit True False 0 1 0
Search
Allow Data
False Data Modify bit True False 0 1 0
Modify
Dam Operation Allow Dam
False bit True False 0 1 0
Plan Operation Plan
Allow Weir
False Weir Schematic bit True False 0 1 0
Schematic
Allow Data
False Data Import bit True False 0 1 0
Import
Station Allow Station
False bit True False 0 1 0
Management Management
User Allow User
False bit True False 0 1 0
Management Management

Constraints
Name Type Columns Initial Code Notes
PK_AUTHORITY_INFO Public No

Relationships
Columns Association Notes
0..* USER_INFO.FK_USER_INFO_AUTHORITY_INFO
(Authority = No)
1 AUTHORITY_INFO.PK_AUTHORITY_INFO

253
USER_INFO

Database: SQL Server 2008, Stereotype: table, Package: User Info

Detail: Created on 20/10/2011 and last modified on 30/01/2012

Notes: Table of User Account information

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True ID varchar True True 20 0 0 User ID
False Name varchar True False 50 0 0 User Name
False Agency int False False 0 0 0 Agency ID
False Authority int True False Authority ID
False Password varchar True False 50 0 0 User Password

Constraints
Name Type Columns Initial Code Notes
PK_USER_INFO Public ID
FK_USER_INFO_AGENCY_INFO Public Agency
FK_USER_INFO_AUTHORITY_INFO Public Authority

Relationships
Columns Association Notes
0..* USER_INFO.FK_USER_INFO_AUTHORITY_INFO
(Authority = No)
1 AUTHORITY_INFO.PK_AUTHORITY_INFO

254
WaterLevel
Type Package

Package: Hydrological D/B

Detail: Created on 05/04/2011 and last modified on 05/04/2011.

WaterLevel

Created By: zemna on 05/04/2011

Last Modified: 30/01/2012, Version: 1.0

class WaterLev el

WaterLevel Database Structure - [Information]


Doc No : ERD-WL-01
Version : 1.0

Base Info::V ILLAGE _INFO

WL_GAUGE_INFO
col um n
*P K i d: int 1 col umn
name: varchar(50)
*PK code: varchar(50)
ol d_station_i d: varchar(50)
FK ri ver_terri tory_id: i nt
FK catchm ent_i d: i nt
FK agency_i d: i nt WL_RATING_CURVE
0..* FK vi l l age_i d: i nt
stati on_name: varchar(50) col umn
equi pment_type: i nt *PK rec_i d: bigi nt
Base Info::CATCHMENT_INFO l ongi tude: float FK code: varchar(50)
l atitude: fl oat year: int
col um n el evati on: fl oat RQ_formul a: varchar(50)
*P K i d: int observati on_start_ti me: dateti me
1 0..* 1 0..*
FK river_terri tory_i d: int status: i nt FK
name: varchar(50) operator_name: varchar(50) + FK_RAT ING_CURVE_FORMULA_WL_GAUGE_INFO(varchar)
operator_phone: varchar(50)
PK
+ PK _RA T ING_CURVE_FORM ULA (bi gi nt)
FK
+ FK_WL_GAUGE _INFO_AGENCY_INFO(i nt)
0..*
+ FK_WL_GAUGE _INFO_CA T CHM ENT _INFO(i nt)
+ FK_WL_GAUGE _INFO_VILLA GE _INFO(i nt)
Base Info::AGENCY_INFO PK
+ P K_WL_GAUGE_INFO(varchar)
col um n
*P K i d: int 1
name: varchar(50)

Associated Agency WL_GAUGE _INFO


- BBWSC, PJT -II - Water l evel station i nformati on
RATING_CURVE _FORMULA
- Rati ng curve formul a data

WaterLevel Database Structure - [Data] Doc No : ERD-WL-02


Version : 1.0

WL_DATA_AWLR_MINUTE LY WL_DATA_AWLR_HOURLY WL_DATA_AWLR_DAILY

col um n column col umn


*pfK code: varchar(50) *pfK code: varchar(50) *pfK code: varchar(50)
*PK dateti m e: dateti me *PK dateti me: datetim e *PK datetim e: dateti me
RR: float T : fl oat T N: fl oat
HO: fl oat RR: fl oat T X : fl oat
HON: fl oat T M : fl oat
FK HOX: fl oat IT N: varchar(50)
+ FK_WL_DAT A_AWLR_M INUT ELY_WL_GAUGE_INFO(varchar) BA: fl oat IT X: varchar(50)
RR: fl oat
P K RRX: fl oat
+ PK_WL_DAT A_AWLR_MINUT ELY (varchar, dateti me) FK IRRX : varchar(50)
+ FK_WL_DAT A_AWLR_HOURLY_WL_GAUGE_INFO(varchar) HOM : fl oat
PK HON: float
+ PK_WL_DA T A_AWLR_HOURLY(varchar, dateti me) HOX: float
IHON: varchar(50)
IHOX: varchar(50)
PS : fl oat
BA : fl oat
BA X: fl oat
BA N: fl oat

FK
WL_DATA_M AN + FK_WL_DA T A_A WLR_DAILY_WL_GA UGE_INFO(varchar)
PK
col umn + PK _WL_DAT A_AWLR_DAILY(varchar, dateti me)
*pfK code: varchar(8)
*PK date: datetim e
water_l evel : float
di scharge: fl oat

PK
+ PK _WL_DAT A_MA N(varchar, dateti me)
FK
+ FK_WL_DA T A_M AN_WL_GAUGE _INFO(varchar)

Associated Agency WL_DATA_AWLR_MINUTELY


- BBWSC, PJT -II - 6-mi nutes water level data
WL_DATA_AWLR_HOURLY
- Hourly water l evel data
WL_DATA_AWLR_DAILY
- Dai l y water l evel data
WL_DATA_MAN
- Manual l y measured water l evel data

Image 80: Water Level Database Structure


255
WL_DATA_AWLR_DAILY

Database: SQL Server 2005, Stereotype: table, Package: Water Level

Detail: Created on 24/03/2011 and last modified on 30/01/2012

Notes: Table of Water Level data in AWLR gauge station which daily recorded.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True code varchar True False 50 code of AWLR station
True datetime datetime True False
Minimum Temperature
False TN float False False
(0C)
Maximum Temperature
False TX float False False
(0C)
Average Temperature
False TM float False False
(0C)
Time when Minimum
Temperature occurred
False ITN varchar False False 50
(hh.mm)
e.g. : 12h18, 13h42
Time when Maximum
Temperature occurred
False ITX varchar False False 50
(hh.mm)
e.g. : 12h18, 13h42
False RR float False False daily rainfall (mm)
Maximum Rainfall per
False RRX float False False hour (mm/jam), jam =
hour
Time of Maximum
False IRRX varchar False False 50
Rainfall occurred
value :
False HOM float False False >>>> = ?
<<<< = ?
Minimum Water Level
False HON float False False
---- = -1111
Maximum Water Level
False HOX float False False
---- = -1111
time of minimum water
False IHON varchar False False 50 level occurred (hh.mm)
e.g. : 12h18, 13h42
Time of Maximum Water
False IHOX varchar False False 50 Level occurred (hh.mm)
e.g. : 12h18, 13h42
total electric current on
False PS float False False
sonar panel (mAh)
Battery voltage at 24.00
False BA float False False
in V (Volt)
Maximum battery
False BAX float False False
voltage in V (Volt)
Minimum battery voltage
False BAN float False False
in V (Volt)

256
Constraints
Name Type Columns Initial Code Notes
FK_WL_DATA_AWLR_DAILY_WL_GAUGE_INFO Public code
PK_WL_DATA_AWLR_DAILY Public code datetime

Relationships
Columns Association Notes
0..*
(code =
WL_DATA_AWLR_DAILY.FK_WL_DATA_AWLR_DAILY_WL_GAUGE_INFO
code)
1 WL_GAUGE_INFO.PK_WL_GAUGE_INFO

WL_DATA_AWLR_HOURLY

Database: SQL Server 2005, Stereotype: table, Package: Water Level

Detail: Created on 24/03/2011 and last modified on 30/01/2012

Notes: Table of Water Level data from AWLR gauge station, which hourly recorded.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True code varchar True False 50
Concate ("Date"
True datetime datetime True False data + "Hour"
data)
False T float False False Temperature (0C)
False RR float False False Rainfall
Minimum water
False HON float False False level
---- = -1111
Maximum water
False HOX float False False level
---- = -1111
battery
status/voltage,
False BA float False False exactly at 59
minutes and 59
seconds (Volt)

Constraints
Name Type Columns Initial Code Notes
FK_WL_DATA_AWLR_HOURLY_WL_GA
Public code
UGE_INFO
code,
PK_WL_DATA_AWLR_HOURLY Public
datetime

Relationships
Columns Association Notes
0..*
(code = WL_DATA_AWLR_HOURLY.FK_WL_DATA_AWLR_HOURLY_WL_G
code) AUGE_INFO
1 WL_GAUGE_INFO.PK_WL_GAUGE_INFO

257
WL_DATA_AWLR_MINUTELY

Database: SQL Server 2005, Stereotype: table, Package: Water Level

Detail: Created on 24/03/2011 and last modified on 30/01/2012

Notes: Table of Water Level data from AWLR gauge station which recorded every 6 minute.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True code varchar True False 50
True datetime datetime True False
Rainfall
False RR float False False
---- = -1111
Water Level
---- = -1111
False HO float False False
<<<< = -3333
>>>> = -6666

Constraints
Name Type Columns Initial Code Notes
FK_WL_DATA_AWLR_MINUTELY_WL_GAUGE_I
Public code
NFO
code,
PK_WL_DATA_AWLR_MINUTELY Public
datetime

Relationships
Columns Association Notes
0..*
(code = WL_DATA_AWLR_MINUTELY.FK_WL_DATA_AWLR_MINUTELY_
code) WL_GAUGE_INFO
1 WL_GAUGE_INFO.PK_WL_GAUGE_INFO

258
WL_DATA_MAN

Database: SQL Server 2008, Stereotype: table, Package: Water Level

Detail: Created on 20/04/2011 and last modified on 30/01/2012

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
Code of Water
True code varchar True True 8 0 0 Level Gauge
Station
datetim Date of
True date True True 0 23 3
e measurement
False water_level float False False 0 53 0 Water Level
Water
False discharge float False False 0 53 0
Discharge

Constraints
Name Type Columns Initial Code Notes
PK_WL_DATA_MAN Public code, date
FK_WL_DATA_MAN_WL_GAUGE_INFO Public code

Relationships
Columns Association Notes
0..* WL_DATA_MAN.FK_WL_DATA_MAN_WL_GAUGE_INFO
(code = code)
1 WL_GAUGE_INFO.PK_WL_GAUGE_INFO

259
WL_GAUGE_INFO

Database: SQL Server 2005, Stereotype: table, Package: Water Level

Detail: Created on 09/03/2011 and last modified on 30/01/2012

Notes: This table consist Automatic Water Level gauge station info and Manual Water Level
gauge station info.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True code varchar True False 50
False old_station_id varchar False False 50
river_territory_i
False int False False
d
False catchment_id int False False
False agency_id int False False
False village_id int False False
False station_name varchar False False 50
option :
0 = manual
False equipment_type int False False
1 = automatic
2 = telemetric
False longitude float False False
False latitude float False False
False elevation float False False
observation_star datetim
False False False
t_time e
0 = not
False status int False False operating
1 = operating
field
False operator_name varchar False False 50 operator's
name
Phone
number of
False operator_phone varchar False False 50 field
operator/obse
rver

Constraints
Name Type Columns Initial Code Notes
FK_WL_GAUGE_INFO_AGENCY_INFO Public agency_id
FK_WL_GAUGE_INFO_CATCHMENT_INFO Public catchment_id
FK_WL_GAUGE_INFO_VILLAGE_INFO Public village_id
PK_WL_GAUGE_INFO Public code

260
Relationships
Columns Association Notes
0..* WL_DATA_MAN.FK_WL_DATA_MAN_WL_GAUGE_INFO
(code = code)
1 WL_GAUGE_INFO.PK_WL_GAUGE_INFO
0..* WL_GAUGE_INFO.FK_WL_GAUGE_INFO_VILLAGE_INFO
1 VILLAGE_INFO.PK_Village
0..* WL_GAUGE_INFO.FK_gauge_station_river_territory
1 RIVER_TERRITORY_INFO.PK_river_territory
0..*
WL_RATING_CURVE.FK_RATING_CURVE_FORMULA_WL_GAUGE_INF
(code = code)
O
1 WL_GAUGE_INFO.PK_WL_GAUGE_INFO
0..*
WL_DATA_AWLR_DAILY.FK_WL_DATA_AWLR_DAILY_WL_GAUGE_I
(code = code)
NFO
1 WL_GAUGE_INFO.PK_WL_GAUGE_INFO
0..*
WL_DATA_AWLR_HOURLY.FK_WL_DATA_AWLR_HOURLY_W
(code = code)
L_GAUGE_INFO
1 WL_GAUGE_INFO.PK_WL_GAUGE_INFO
0..*
WL_DATA_AWLR_MINUTELY.FK_WL_DATA_AWLR_MINUTEL
(code = code)
Y_WL_GAUGE_INFO
1 WL_GAUGE_INFO.PK_WL_GAUGE_INFO
0..* WL_GAUGE_INFO.FK_WL_GAUGE_INFO_AGENCY_INFO
(agency_id = id)
1 AGENCY_INFO.PK_AGENCY_INFO
(catchment_id = 0..* WL_GAUGE_INFO.FK_WL_GAUGE_INFO_CATCHMENT_INFO
id) 1 CATCHMENT_INFO.PK_CATCHMENT_INFO

261
WL_RATING_CURVE

Database: SQL Server 2005, Stereotype: table, Package: Water Level

Detail: Created on 24/03/2011 and last modified on 30/01/2012

Notes: Table of Rating Curve formula for each water level gauge station. Rating Curve
formula is used in calculating Water Discharge.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True rec_id bigint True False
water level gauge
False code varchar False False 50
station code
published year of
False year int False False Rating Curve
formula
Rating Curve
Formula
Formula to
calculate Water
False RQ_formula varchar False False 50 Discharge from
Water Level data.
Just for reference,
updated once a
year.

Constraints
Name Type Columns Initial Code Notes
FK_RATING_CURVE_FORMULA_WL_GAUGE_INFO Public code
PK_RATING_CURVE_FORMULA Public rec_id

Relationships
Columns Association Notes
0..*
(code =
WL_RATING_CURVE.FK_RATING_CURVE_FORMULA_WL_GAUGE_INFO
code)
1 WL_GAUGE_INFO.PK_WL_GAUGE_INFO

262
WaterQuality
Type: Package

Package: Hydrological D/B

Detail: Created on 05/04/2011 and last modified on 05/04/2011.

WaterQuality

Created By: zemna on 05/04/2011

Last Modified: 30/01/2012, Version: 1.0

class WaterQuality

WaterQuality Database Structure


Doc No : ERD-WQ-01
Versi on : 1.0

Base Info::DISTRICT_INFO

Base Info::VILLAGE _INFO column


*P K id: i nt
WQ_GAUGE_INFO
col umn name: varchar(50)
*PK i d: i nt FK provi nce_id: i nt
1 column
name: varchar(50)
*P K code: varchar(50)
ol d_stati on_id: varchar(50) FK
FK ri ver_territory_i d: i nt + FK_DIST RICT _INFO_PROVINCE_INFO(int)
FK catchm ent_i d: i nt PK
1
FK agency_i d: int + PK_DIST RICT _INFO(i nt)
di vi si on_i d: i nt
0..* FK di stri ct_id: i nt
FK vil l age_i d: i nt
Base Info::CATCHMENT_INFO 0..*
stati on_nam e: varchar(50)
interval : varchar(50)
col umn equi pm ent_type: i nt
*PK i d: i nt longi tude: fl oat
1 0..*
FK river_terri tory_i d: int latitude: fl oat
name: varchar(50) el evation: fl oat
observati on_start_ti me: dateti me
status: i nt
operator_name: varchar(50)
0..*
FK
+ FK_WQ_GAUGE_INFO_AGENCY_INFO(int)
+ FK_WQ_GAUGE_INFO_CAT CHMENT _INFO(int)
Base Info::AGENCY_INFO + FK_WQ_GAUGE_INFO_DIST RICT _INFO(int)
+ FK_WQ_GAUGE_INFO_VILLAGE_INFO(i nt)
col umn
*PK i d: i nt 1 PK
name: varchar(50) + PK_WQ_GAUGE _INFO(varchar)

Associated Agency WQ_GAUGE_INFO


- BPLHD, PJT -II - Water Qual i ty station i nformati on

WaterQuality Database Stucture - 2/2


Doc No : ERD-WQ-02
Versi on : 1.0

Contains whol e of water


quali ty data type WQ_STD_RIVE R
i ncl udi ng water quali ty
WQ_PARAM
param eter for i ndustry. col umn
column *pfK ri ver_class_code: i nt
*PK param_code: varchar(4) *pfK param_code: varchar(4)
B PLHDnam e: varchar(50) *PK date: dateti me
category: varchar(10) val ue1: fl oat
uni t: varchar(20) val ue2: fl oat
* type: i nt = ((0)) 1
P JT IIname: varchar(50) 0..* uni que
+ UQ_WQ_ST D_RIVER_date(dateti me)
PK + UQ_WQ_ST D_RIVER_param_code(varchar)
+ P K_WQ_PARAM(varchar) + UQ_WQ_ST D_RIVER_ri ver_cl ass_code(int)
PK
1
+ PK _WQ_ST D_RIVE R(i nt, varchar, dateti m e)
0..* FK
+ FK_WQ_ST D_RIVER_RIV ER_CLASS_INFO(int)
WQ_DATA
+ FK_WQ_ST D_RIVER_WQ_PARAM (varchar)
col umn
0..*
*pfK code: varchar(8)
*pfK param_code: varchar(4) 1
*PK date: dateti me
value: float RIVE R_CLASS_INFO
*PK depth: i nt
column
*P K ri ver_cl ass_code: i nt
PK
* regul ati on_date: date
+ PK_WQ_DAT A_1(varchar, varchar, datetim e, i nt)
regul ati on_no: varchar(50)
FK name: varchar(50)
+ FK_WQ_DAT A_WQ_GAUGE_INFO(varchar) water_use: text
+ FK_WQ_DAT A_WQ_PA RAM(varchar)
uni que
+ UQ_RIVER_CLASS _INFO_ri ver_cl ass_code(int)
PK
+ PK_RIVER_CLASS_INFO(i nt)

Associated Agency RIVE R_CLASS_INFO


- BPLHD, PJT -II, PUSAIR - Ri ver cl assi fi cati on based on government regul ati on
WQ_PARAM
- Contai ns whol e of water qual i ty data type
WQ_STD_RIVER
- Annual water quali ty standard
WQ_DATA
- Water Qual i ty data

Image 81: Water Quality Database Structure


263
RIVER_CLASS_INFO

Database: SQL Server 2008, Stereotype: table, Package: Water Quality

Detail: Created on 30/01/2012 and last modified on 30/01/2012

Notes: Table of River Class information. It has includes river classification based on
government regulation in case of water quality monitoring process.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
river_class_cod
True e
int True True River Class code
False regulation_date date True False Regulation started
Government's
regulation number
of River
Classification
associated with
varch water quality
False regulation_no False False 50
ar monitoring.
e.g. : - PP 82 tahun
2001
- Keputusan
Gubernur Jawa
Barat
RiverClass name :
varch eg : Kelas I, Kelas
False name False False 50
ar II, Kelas III, Kelas
IV
Water Usage
specification. Ex:
False water_use text False False Irrigation, Industry,
Drinking Water, or
Fresh Water Resort.

Constraints
Name Type Columns Initial Code Notes
UQ_RIVER_CLASS_INFO_river_class_code Public river_class_code
PK_RIVER_CLASS_INFO Public river_class_code

Relationships
Columns Association Notes
(river_class_code = 0..* WQ_STD_RIVER.FK_WQ_STD_RIVER_RIVER_CLASS_INFO
river_class_code) 1 RIVER_CLASS_INFO.PK_RIVER_CLASS_INFO

264
WQ_STD_RIVER

Database: SQL Server 2008, Stereotype: table, Package: Water Quality

Detail: Created on 30/01/2012 and last modified on 30/01/2012

Notes: Table of Water Quality Standard for Water Quality monitoring on the river. These
Water Quality Standards are based on government regulation which associated with water
quality monitoring process. Ex: PP 82 Tahun 2001, it is includes water quality standard for
each River Class.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
river_class_c
True int True True River Class code.
ode
varc WQ Parameter
True param_code True True 4
har Code
Date of entry, date
datet
True date True True of regulation
ime
started.
Minimum
False value1 float False False Acceptable
Concentration
Maximum
False value2 float False False Acceptable
Concentration

Constraints
Name Type Columns Initial Code Notes
UQ_WQ_STD_RIVER_date Public date
UQ_WQ_STD_RIVER_param_code Public param_code
UQ_WQ_STD_RIVER_river_class_code Public river_class_code
river_class_code, param_code,
PK_WQ_STD_RIVER Public
date
FK_WQ_STD_RIVER_RIVER_CLASS
Public river_class_code
_INFO
FK_WQ_STD_RIVER_WQ_PARAM Public param_code

Relationships
Columns Association Notes
(param_code = 0..* WQ_STD_RIVER.FK_WQ_STD_RIVER_WQ_PARAM
param_code) 1 WQ_PARAM.PK_WQ_PARAM
0..*
(river_class_code =
WQ_STD_RIVER.FK_WQ_STD_RIVER_RIVER_CLASS_INFO
river_class_code)
1 RIVER_CLASS_INFO.PK_RIVER_CLASS_INFO

265
WQ_GAUGE_INFO

Database: SQL Server 2005, Stereotype: table, Package: Water Quality

Detail: Created on 16/03/2011 and last modified on 30/01/2012

Notes: Table of Water Quality gauge station. It's includes location of each gauge station and
base information related to the gauge station.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True code varchar True False 50
False old_station_id varchar False False 50
False river_territory_id int False False
False catchment_id int False False
False agency_id int False False
False division_id int False False
False district_id int False False
False village_id int False False
False station_name varchar False False 50
daily,
monthly,
False interval varchar False False 50 semi-
monthly,
annually
False equipment_type int False False 0 : manual
False longitude float False False
False latitude float False False
False elevation float False False
observation_star
False datetime False False
t_time
0 = not
False status int False False operating
1 = operating
Field
False operator_name varchar False False 50 operator
name

Constraints
Name Type Columns Initial Code Notes
FK_WQ_GAUGE_INFO_AGENCY_INFO Public agency_id
FK_WQ_GAUGE_INFO_CATCHMENT_INFO Public catchment_id
FK_WQ_GAUGE_INFO_DISTRICT_INFO Public district_id
FK_WQ_GAUGE_INFO_VILLAGE_INFO Public village_id
PK_WQ_GAUGE_INFO Public code

266
Relationships
Columns Association Notes
0..* WQ_GAUGE_INFO.FK_WQ_GAUGE_INFO_AGENCY_INFO
(agency_id = id)
1 AGENCY_INFO.PK_AGENCY_INFO
0..*
(catchment_id = id) WQ_GAUGE_INFO.FK_WQ_GAUGE_INFO_CATCHMENT_INFO
1 CATCHMENT_INFO.PK_CATCHMENT_INFO
0..* WQ_GAUGE_INFO.FK_WQ_GAUGE_INFO_VILLAGE_INFO
1 VILLAGE_INFO.PK_Village
0..* WQ_GAUGE_INFO.FK_water_quality_station_river_territory
1 RIVER_TERRITORY_INFO.PK_river_territory
0..* WQ_DATA.FK_WQ_DATA_WQ_GAUGE_INFO
(code = code)
1 WQ_GAUGE_INFO.PK_WQ_GAUGE_INFO
0..* WQ_GAUGE_INFO.FK_WQ_GAUGE_INFO_DISTRICT_INFO
(district_id = id)
1 DISTRICT_INFO.PK_DISTRICT_INFO

WQ_DATA

Database: SQL Server 2008, Stereotype: table, Package: Water Quality

Detail: Created on 18/03/2011 and last modified on 30/01/2012

Notes: Table of Water Quality measurement data.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
Code of Water
True code varchar True True 8 0 0 Quality Gauge
Station
param_co Water Quality
True varchar True True 4 0 0
de Parameter Code
Date of
True date datetime True True 0 23 3
measurement
Value of
False value float False False 0 53 0
measurement
Depth of
True depth int True True 0 0 0
measurement

Constraints
Name Type Columns Initial Code Notes
PK_WQ_DATA_1 Public code, param_code, date, depth
FK_WQ_DATA_WQ_GAUGE_I
Public code
NFO
FK_WQ_DATA_WQ_PARAM Public param_code

Relationships
Columns Association Notes
0..* WQ_DATA.FK_WQ_DATA_WQ_PARAM
(param_code = param_code)
1 WQ_PARAM.PK_WQ_PARAM
0..* WQ_DATA.FK_WQ_DATA_WQ_GAUGE_INFO
(code = code)
1 WQ_GAUGE_INFO.PK_WQ_GAUGE_INFO

267
WQ_PARAM

Database: SQL Server 2008, Stereotype: table, Package: Water Quality

Detail: Created on 18/03/2011 and last modified on 30/01/2012

Notes: Table of Water Quality Parameter, includes physical, biological and chemical
parameter for monitoring water quality in the river stream and industry's waste disposal.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True param_code varchar True True 4 0 0 Code of parameter
BPLHDnam Parameter name
False varchar False False 50
e (BPLHD's naming)
Parameter Category
False category varchar False False 10 0 0
(Chemical, Physical)
False unit varchar False False 20 0 0 Unit of parameter
Parameter type.
0 = WQ Parameter
False type int True False ((0)) for River Stream
1 = WQ Parameter
for Industry
Parameter name
False PJTIIname varchar False False 50
(PJT-II's naming)

Constraints
Name Type Columns Initial Code Notes
PK_WQ_PARAM Public param_code

Relationships
Columns Association Notes
0..* WQ_STD_RIVER.FK_WQ_STD_RIVER_WQ_PARAM
(param_code = param_code)
1 WQ_PARAM.PK_WQ_PARAM
0..* WQ_DATA.FK_WQ_DATA_WQ_PARAM
(param_code = param_code)
1 WQ_PARAM.PK_WQ_PARAM
<anonymous>. , WQ_PARAM.

268
Weir
Type: Package

Package: Hydrological D/B

Detail: Created on 05/04/2011 and last modified on 05/04/2011.

Weir

Created By: zemna on 05/04/2011

Last Modified: 30/01/2012, Version: 1.0

cla s s We ir

Weir Database Structure - [Information]


Doc No : E RD-WE -0 1
Ve rsi on : 1. 0

Ba s e I nfo::VI LLAGE _I NFO

col um n WEI R_ INFO WEI R_ SCHEM ATI C_ IM AGE


*P K id : i nt 1
na m e: varch ar(50 ) co lum n co lum n
*P K co d e: va rcha r(8 ) *P K cod e: cha r(8 )
(vill ag e_ id = id )
o ld_ weir_i d: va rcha r(5 0 ) im g : im ag e
*FK ri ve r_t errito ry_i d: in t h ash: va rcha r(3 2 )
*FK ca tchm e nt _id : in t
*FK a ge ncy_ id : i nt
P K
* d ivi sio n: in t
0.. * + P K_ WEI R_ S CHE MA T IC_I MA GE(ch ar)
*FK vi lla ge _ id: b ig in t
Bas e I nfo::CATCHM ENT_ INFO * n am e : varch ar(50 )
* type : in t
col um n lo ca tio n _cate g ory: in t
*P K id : i nt lo ng it ud e: fl oa t
FK river_t errito ry_id : in t la tit ud e: fl oa t
1
na m e: varch ar(50 ) e levat io n: fl oa t
0.. * * st atu s: i nt
p ost fix: va rch a r(5 0)
sche m at ic_ im a ge s: im a ge
*FK p rovin ce _i d: in t
*FK d istrict_i d: in t
*FK su b_ d ist rict_i d: in t
0.. *
Ba s e I nfo::AGE NCY _I NFO P K
+ P K_ WEI R_ INFO(varch ar)
col um n
FK
*P K id : i nt 1 + FK_ WEI R_ INFO_ AGE NCY _I NFO(in t)
na m e: varch ar(50 )
+ FK_ WEI R_ INFO_ CA T CHM ENT _I NFO(in t)
+ FK_ WEI R_ INFO_ DI ST RICT _ INFO(i nt)
+ FK_ WEI R_ INFO_ PROVI NCE _INFO(in t)
+ FK_ WEI R_ INFO_ RI VE R_T ERRIT ORY _I NFO(in t)
+ FK_ WEI R_ INFO_ SUB _DIS TRICT _I NFO(in t)
+ FK_ WEI R_ INFO_ VI LL AGE _I NFO(bi gi nt)

Ass oc ia te d Agency Wei r h as d iffe re nt d ata f orm a t b y its type


- PJT-II If we ir type is g en eral, d ata i s stored in WE IR_DA TA ta b le
If we ir type is sp e cia l, da ta is st ore d in WEI R_ DAT A _p ostfi x t ab le

Weir Database Stucture - [General Type]


Doc No : E RD-WE -0 2
Ve rsi on : 1. 0

WE IR_S CHE M ATIC

col um n
*P K Date : da te tim e
WEI R_ DATA B ekasi Ut ara: fl oa t
B ekasi : flo at
B ua ra n: fl oa t
co lum n
*p fK cod e: varcha r(8) P ulo g ad un g: f loa t
*P K d ate : da te tim e P ejo m po n ga n: fl oa t
K ara n g1 : flo at
Q1: fl oa t
Ove rfl ow: flo at K ara n g2 : flo at
Q2: fl oa t K ara n g3 : flo at
B ekasi 2: fl oa t
Cika ra ng : flo at
PK Cipa m in gkis: fl oa t
+ P K_ WEI R_ DAT A _1 (va rcha r, da te tim e ) Cibe e t: flo at
FK Wal ah ar: f lo at
+ FK_ WEI R_ DA T A_ WE IR_ INFO(va rch a r) S TU: flo at
S TT : flo at
S TB : flo at
CFC: flo at
Cika o: fl oa t
Ja ti luh ur: flo at
Cira ta : f lo at
S ag ul ing : flo a t
B aru g bu g1 : flo at
B aru g bu g2 : flo at
S un ga pa n : f lo at
B en gg al a: fl oa t
Je n gko l1 : flo at
Je n gko l2 : flo at
Cije ng ko l: flo a t
Gad un g1 : flo a t
Gad un g2 : flo a t
M acan : flo at
Ciasem : fl oa t
Ass oc ia te d Agency Ciga d un g: fl oa t Dev is ion I I
- PJT-II S ala m da rm a 1: fl oa t S om a ng , S T _Wa na ya sa , P u nd on g, P on do k_ Sa la m , Wa ru , Wal ah ar
S ala m da rm a 2: fl oa t
B MC: flo a t Dev is ion I II (South of Ja ti luhur Ir ri ga tion Ar ea )
Cipu n eg ara: fl oa t Curu g _A gu n g, Ci leu le uy, L e uwin an gka, P an gsor, P ed at i, La lan a ng

P K
+ P K_ WeirSche m at ic(da te tim e )

Weir Database Structure - [Devision I]


Doc No : E RD-WE -0 3
Ve rsi on : 1. 0

WE IR_DATA_Cibee t WE IR_DATA_Cik ar ang WE IR_DATA_Be ka si

co lu m n colu m n col um n
* PK d at e: d at eti m e *P K da te : da te tim e *P K da te : da te tim e
o ve rf low: flo a t su pl esi : flo at su pl esi_f rom _ B TB 45 : flo a t
sup le si: fl oa t overflo w: f loa t overflo w: f loa t
o ut flo w: f lo at ou tfl ow_o f_ flu sh _ ga te : f loa t in take_ P am _ Ja ya : flo at
Q1 : flo at ou tfl ow_o f_ weir_g at e: fl oa t in take_ B ekasi_Uta ra : flo at
Q2 : flo at used _wa ter_b y_ west _b ekasi: flo a t ou tfl ow: flo a t
se nt _to _sukat an i: flo a t Q1: fl oa t
P K used _wa ter_t o_ su ka tan i: fl oa t Q2: fl oa t
+ P K _WE IR_DA TA _Cib e et_ 1 (da te tim e ) overflo w_ o f_CB L: fl oa t
Q1 : flo a t P K
Q2 : flo a t
+ PK _ WEIR_ DA T A_ B eka si _1 (d at eti m e)

P K
+ PK _ WE IR_ DA T A_ Ci ka ra ng _1 (d at eti me )

Ass oc ia te d Agency Data wil l b e save d t o e a ch WEI R_ DAT A _p ostfi x t ab le


- PJT-II

Weir Database Structure - [Devision III]


Doc No : E RD-WE -0 4
Ve rsi on : 1. 0

Jatiluhur irrigation area South of Jatiluhur Irrigatio n Area

WE IR_DATA_ Ba rugbug WE IR_DATA_J engk ol WEI R_ DATA_ M ac a n

col um n co lu m n co lu mn
*P K da te : da te tim e * PK da te : d at et im e *P K d at e: d ate ti me
Q2 : flo a t sup le si _from _ BT T : f lo at sup le si_ fro m _B T T: fl oa t
Q1 : flo a t Q2 : flo at Q2 : f lo at
su pl esi _t o_ ST T : flo at Q1 : flo at Q1 _su p lesi_ to _S TT : flo a t
Ove rflo w: f lo at Q1 _S S : flo at Q1 _B M 8Hili r: flo a t
Overflo w: f loa t Q1 _S S: f loa t
Ove rf low: flo a t
P K WE IR_DATA_Wa duk _Cipancuh
+ PK _ WE IR_ DA T A_ Ba ru gb u g(d a tet im e) P K
+ PK _WE IR_DA TA _ Je ng ko l_ 1(d a tet im e) PK colu m n
+ P K _WE IR_DAT A _M a ca n_ 1(da te tim e ) *P K da te : da te tim e
wa te r_ leve l: flo at
Q1 : flo a t

P K
WE IR_ DATA_ Sa la mda rma WE IR_DATA_Ga dung
+ PK _ WE IR_ DA T A_ Wad uk_Cip an cu h _1 (d ate ti me )

col um n co lu m n
*P K Da te : da te tim e * PK d a te: d at et im e
Su p lesi_ ST T : f lo at sup le si_ from _ BT T : f lo at
Q2 : flo a t Q2 : flo at
Q1 _ Ind u k_ Bu gi s: flo a t Q_ Be n du ng : flo at
Q1 _ SS : flo at Q1 _S S : flo at
Fl ushin g: f loa t Overflo w: fl oa t
Ove rflo w: f lo at
P K
P K + P K _WE IR_DA TA _ Ga du n g_ 1(da te tim e )
+ PK _ WE IR_ DA T A_ Sa la m da rm a _1 (d ate ti me )

Ass oc ia te d Agency Data wil l b e save d t o e a ch WEI R_ DAT A _p ostfi x t ab le


- PJT-II

Image 82: Weir Database Structure


269
WEIR_DATA_Waduk_Cipancuh

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 20/10/2011 and last modified on 30/01/2012

Notes: Table of Water Discharge data in Cipancuh Weir

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True date datetime True True 0 23 3 Date
Water
False water_level float False False 0 53 0
Level
False Q1 float False False 0 53 0 Q1

Constraints
Name Type Columns Initial Code Notes
PK_WEIR_DATA_Waduk_Cipancuh_1 Public date

270
WEIR_SCHEMATIC

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 20/10/2011 and last modified on 30/01/2012

Notes: Table of Discharge data for each weir in form of Weir Schematic diagram.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
dateti
True Date True True 0 23 3 Date of Measurement
me
Water Discharge in
Bekasi
False Utara
float False False 0 53 0 Bekasi Utara water level
gauge station
Water Discharge in
False Bekasi float False False 0 53 0 Bekasi water level
gauge station
Water Discharge in
False Buaran float False False 0 53 0 Buaran water level
gauge station
Water Discharge in
Pulogadu
False ng
float False False 0 53 0 Pulogadung water level
gauge station
Water Discharge in
Pejompon
False gan
float False False 0 53 0 Pejompongan water
level gauge station
Water Discharge in
False Karang1 float False False 0 53 0 Karang1 water level
gauge station
Water Discharge in
False Karang2 float False False 0 53 0 Karang2 water level
gauge station
Water Discharge in
False Karang3 float False False 0 53 0 Karang3 water level
gauge station
Water Discharge in
False Bekasi2 float False False 0 53 0 Bekasi2 water level
gauge station
Water Discharge in
False Cikarang float False False 0 53 0 Cikarang water level
gauge station
Water Discharge in
Cipaming
False kis
float False False 0 53 0 Cipamingkis water level
gauge station
Water Discharge in
False Cibeet float False False 0 53 0 Cibeet water level gauge
station
Water Discharge in
False Walahar float False False 0 53 0 Walahar water level
gauge station
Water Discharge in STU
False STU float False False 0 53 0
water level gauge

271
station
Water Discharge in STT
False STT float False False 0 53 0 water level gauge
station
Water Discharge in STB
False STB float False False 0 53 0 water level gauge
station
Water Discharge in CFC
False CFC float False False 0 53 0 water level gauge
station
Water Discharge in
False Cikao float False False 0 53 0 Cikao water level gauge
station
Water Discharge in
False Jatiluhur float False False 0 53 0 Jatiluhur water level
gauge station
Water Discharge in
False Cirata float False False 0 53 0 Cirata water level gauge
station
Water Discharge in
False Saguling float False False 0 53 0 Saguling water level
gauge station
Water Discharge in
Barugbug
False 1
float False False 0 53 0 Barugbug1 water level
gauge station
Water Discharge in
Barugbug
False 2
float False False 0 53 0 Barugbug 2 water level
gauge station
Water Discharge in
False Sungapan float False False 0 53 0 Sungapan water level
gauge station
Water Discharge in
False Benggala float False False 0 53 0 Benggala water level
gauge station
Water Discharge in
False Jengkol1 float False False 0 53 0 Jengkol1 water level
gauge station
Water Discharge in
False Jengkol2 float False False 0 53 0 Jengkol2 water level
gauge station
Water Discharge in
False Cijengkol float False False 0 53 0 Cijengkol water level
gauge station
Water Discharge in
False Gadung1 float False False 0 53 0 Gadung1 water level
gauge station
Water Discharge in
False Gadung2 float False False 0 53 0 Gadung2 water level
gauge station
Water Discharge in
False Macan float False False 0 53 0 Macan water level
gauge station

272
Water Discharge in
False Ciasem float False False 0 53 0 Ciasem water level
gauge station
Water Discharge in
False Cigadung float False False 0 53 0 Cigadung water level
gauge station
Water Discharge in
Salamdar
False ma1
float False False 0 53 0 Salamdarma1 water
level gauge station
Water Discharge in
Salamdar
False ma2
float False False 0 53 0 Salamdarma2 water
level gauge station
Water Discharge in
False BMC float False False 0 53 0 BMC water level gauge
station
Water Discharge in
Cipunega
False ra
float False False 0 53 0 Cipunegara water level
gauge station

Constraints
Name Type Columns Initial Code Notes
PK_WeirSchematic Public Date

273
WEIR_SCHEMATIC_IMAGE

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 20/10/2011 and last modified on 30/01/2012

Notes: Table of Weir Schematic image for each weir structure.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True code char True True 8 0 0
weir schematic image in
False img image False False 0 0 0
DBImage format.
generated hash value for
False hash varchar False False 32 0 0 associated weir schematic
image

Constraints
Name Type Columns Initial Code Notes
PK_WEIR_SCHEMATIC_IMAGE Public code

WEIR_DATA_Barugbug

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 16/03/2011 and last modified on 30/01/2012

Notes: Table of water discharge data in Barugbug weir.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True date datetime True True 0 23 3 Date
False Q2 float False False 0 53 0 Q2
False Q1 float False False 0 53 0 Q1
suplesi_to_
False float False False 0 53 0 Supply
STT
False Overflow float False False 0 53 0 Overflow

Constraints
Name Type Columns Initial Code Notes
PK_WEIR_DATA_Barugbug Public date

274
WEIR_DATA_Bekasi

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 10/03/2011 and last modified on 30/01/2012

Notes: Table of water discharge data in Bekasi weir

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True date datetime True True 0 23 3 Date
suplesi_fro
False float False False 0 53 0 Supply water
m_BTB45
False overflow float False False 0 53 0 Overflow
Intake by PAM
Jaya
intake_Pam Ind : Penyaluran
False float False False 0 53 0
_Jaya ke PAM Jaya
Suplesi ke DKI
Jakarta
Intake by Bekasi
Utara
intake_Bek Ind : Penyaluran
False float False False 0 53 0
asi_Utara ke Bekasi Utara
Suplesi ke Bekasi
Utara
False outflow float False False 0 53 0 Bocoran bendung
False Q1 float False False 0 53 0 Q1
False Q2 float False False 0 53 0 Q2

Constraints
Name Type Columns Initial Code Notes
PK_WEIR_DATA_Bekasi_1 Public date

275
WEIR_DATA_Cikarang

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 10/03/2011 and last modified on 30/01/2012

Notes: Table of water discharge data in Cikarang weir

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True date datetime True True 0 23 3 Date
Suplesi dari
False suplesi float False False 0 53 0
Btb.34b
False overflow float False False 0 53 0 Overflow
outflow_of_flu Bocoran Pintu
False float False False 0 53 0
sh_gate Pengurasan
outflow_of_w Bocoran Pintu
False float False False 0 53 0
eir_gate Bendung
used_water_by Dimanfaatkan
False float False False 0 53 0
_west_bekasi ke Bekasi Barat
sent_to_sukata Dikirim ke
False float False False 0 53 0
ni Sukatani
used_water_to dimanfaatkan
False float False False 0 53 0
_sukatani ke sukatani
overflow_of_
False float False False 0 53 0 limpasan CBL
CBL
False Q1 float False False 0 53 0 Q1
False Q2 float False False 0 53 0 Q2

Constraints
Name Type Columns Initial Code Notes
PK_WEIR_DATA_Cikarang_1 Public date

276
WEIR_DATA_Gadung

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 16/03/2011 and last modified on 30/01/2012

Notes: Table of water discharge data in Gadung weir

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True date datetime True True 0 23 3 Date
suplesi_from_
False float False False 0 53 0 Supply
BTT
False Q2 float False False 0 53 0 Q2
False Q_Bendung float False False 0 53 0 Q_Benndug
False Q1_SS float False False 0 53 0 Q1
False Overflow float False False 0 53 0 Overflow

Constraints
Name Type Columns Initial Code Notes
PK_WEIR_DATA_Gadung_1 Public date

WEIR_DATA_Jengkol

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 16/03/2011 and last modified on 30/01/2012

Notes: Table of water discharge data in Jengkol weir

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True date datetime True True 0 23 3 Date
suplesi_from_
False float False False 0 53 0 Supply
BTT
False Q2 float False False 0 53 0 Q2
False Q1 float False False 0 53 0 Q1
False Q1_SS float False False 0 53 0 Q1_SS
False Overflow float False False 0 53 0 Overflow

Constraints
Name Type Columns Initial Code Notes
PK_WEIR_DATA_Jengkol_1 Public date

277
WEIR_DATA_Macan

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 16/03/2011 and last modified on 30/01/2012

Notes: Table of water discharge data in Macan weir

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True date datetime True True 0 23 3 Date
suplesi_from_ Supply From
False float False False 0 53 0
BTT BTT
False Q2 float False False 0 53 0 Q2
Q1_suplesi_to Q1 (Supply to
False float False False 0 53 0
_STT STT)
False Q1_BM8Hilir float False False 0 53 0 Q1 (BM8Hilir)
False Q1_SS float False False 0 53 0 Q1 (SS)
False Overflow float False False 0 53 0 Overflow

Constraints
Name Type Columns Initial Code Notes
PK_WEIR_DATA_Macan_1 Public date

WEIR_DATA_Salamdarma

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 16/03/2011 and last modified on 30/01/2012

Notes: Table of water discharge data in Salamdarma weir.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True Date datetime True True 0 23 3 Date
False Suplesi_STT float False False 0 53 0 Supply (STT)
False Q2 float False False 0 53 0 Q2
Q1_Induk_Bu Q1 (Induk
False float False False 0 53 0
gis Bugis)
False Q1_SS float False False 0 53 0 Q1 (SS)
False Flushing float False False 0 53 0 Flushing
False Overflow float False False 0 53 0 Overflow

Constraints
Name Type Columns Initial Code Notes

PK_WEIR_DATA_Salamd
Public Date
arma_1

278
WEIR_DATA

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 16/03/2011 and last modified on 30/01/2012

Notes: Table of water discharge data for each weir which have general data (Q1, Q2, and
Overflow)

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True code varchar True True 8 0 0 Weir Code
True date datetime True True 0 23 3 Date
False Q1 float False False 0 53 0 Inflow
False Overflow float False False 0 53 0 Overflow
False Q2 float False False 0 53 0 Outflow

Constraints
Name Type Columns Initial Code Notes
PK_WEIR_DATA_1 Public code, date
FK_WEIR_DATA_WEIR_INFO Public code

Relationships
Columns Association Notes
0..* WEIR_DATA.FK_WEIR_DATA_WEIR_INFO
(code = code)
1 WEIR_INFO.PK_WEIR_INFO

279
WEIR_DATA_Cibeet

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 10/03/2011 and last modified on 30/01/2012

Notes: Table of water discharge data in Cibeet weir

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True date datetime True True 0 23 3 Date
False overflow float False False 0 53 0 Overflow
False suplesi float False False 0 53 0 Supply
False outflow float False False 0 53 0 Outflow
False Q1 float False False 0 53 0 Q1
False Q2 float False False 0 53 0 Q2

Constraints
Name Type Columns Initial Code Notes
PK_WEIR_DATA_Cibeet_1 Public date

WEIR_INFO

Database: SQL Server 2008, Stereotype: table, Package: Weir

Detail: Created on 16/03/2011 and last modified on 30/01/2012

Notes: Table of Weir structure information.

Columns
PK Name Type Not Null Unique Len Prec Scale Init Notes
True code varchar True True 8 0 0 Weir Code
False old_weir_id varchar False False 50 0 0 Old Weir ID
river_territor
False int True False 0 0 0 River Territory ID
y_id
False catchment_id int True False 0 0 0 Catchment ID
False agency_id int True False 0 0 0 Agency ID
False division int True False 0 0 0 Division
False village_id bigint True False 0 19 0 Village ID
False name varchar True False 50 0 0 Weir Name
0 : General, 1 :
False type int True False 0 0 0
Special
location_cate
False int False False 0 0 0 Location Category
gory
False longitude float False False 0 53 0 Longitude
False latitude float False False 0 53 0 Latitude
False elevation float False False 0 53 0 Elevation
False status int True False 0 0 0 0 : Not Operating,

280
1 : Operating
False postfix varchar False False 50 0 0 Postfix
schematic_i
False image False False 0 0 0 Schematic Image
mages
False province_id int True False 0 0 0 Province ID
False district_id int True False 0 0 0 District ID
sub_district_i
False int True False 0 0 0 Sub-district ID
d

Constraints
Name Type Columns Initial Code Notes
PK_WEIR_INFO Public code
FK_WEIR_INFO_AGENCY_INFO Public agency_id
FK_WEIR_INFO_CATCHMENT_INFO Public catchment_id
FK_WEIR_INFO_DISTRICT_INFO Public district_id
FK_WEIR_INFO_PROVINCE_INFO Public province_id
FK_WEIR_INFO_RIVER_TERRITORY_INFO Public river_territory_id
FK_WEIR_INFO_SUB_DISTRICT_INFO Public sub_district_id
FK_WEIR_INFO_VILLAGE_INFO Public village_id

Relationships
Columns Association Notes
0..* WEIR_DATA.FK_WEIR_DATA_WEIR_INFO
(code = code)
1 WEIR_INFO.PK_WEIR_INFO
0..* WEIR_INFO.FK_WEIR_INFO_AGENCY_INFO
(agency_id = id)
1 AGENCY_INFO.PK_AGENCY_INFO
0..* WEIR_INFO.FK_WEIR_INFO_CATCHMENT_INFO
(catchment_id = id)
1 CATCHMENT_INFO.PK_CATCHMENT_INFO
0..* WEIR_INFO.FK_WEIR_INFO_VILLAGE_INFO
(village_id = id)
1 VILLAGE_INFO.PK_VILLAGE_INFO

281
Diagram Documentation
Database Schema - (Logical diagram)
class Databas e Sche ma

DSS Software ERD(Entity Relationship Diagram)


Doc No : ERD-MAIN-01
Ve rsi on : 1.0

Contai n i nforma ti on abou t


regi on, watershed,
age ncy, e tc...
Dam

+ DAM_DATA
Base Info
+ DAM_OPER_PLAN
Rainfall + AGENCY_ INFO + DAM_INFO
+ RF_DAT A_DAILY + CAT CHMENT _INFO
+ DISTRICT _INFO use
+ RF_GAUGE_INFO
u se + PROVINCE_INFO
+ RIVER_T ERRITORY_INFO
+ SUB_CAT CHMENT _INFO
+ SUB_DIST RICT_ INFO
+ VILLAGE_INFO
Weir
use
+ WEIR_DAT A_ Wa duk_Ci pancuh
use
AWS (Automatic Weather Station) + WEIR_SCHEMAT IC
+ WEIR_SCHEMAT IC_IMAGE
+ AWS_DAILY
+ WEIR_DAT A_ Barugb ug
+ AWS_GAUGE_INFO
+ WEIR_DAT A_ Bekasi
+ AWS_HOURL Y
+ WEIR_DAT A_ Ci karang
+ AWS_MINUT ELY
+ WEIR_DAT A_ Gadun g
+ WEIR_DAT A_ Jen gkol
use
use + WEIR_DAT A_ Ma can
+ WEIR_DAT A_ Sal amdarma
+ WEIR_DAT A
+ WEIR_DAT A_ Ci beet
+ WEIR_INFO

WaterLev el WaterQuality User Info Image Info


+ WL_ DAT A_AWL R_DAILY + RIVER_ CLASS_INFO + AUTHORITY_INFO + IMAGE_DAT A
+ WL_ DAT A_AWL R_HOURLY + WQ_ST D_RIVER + USER_INFO
+ WL_ DAT A_AWL R_MINUT ELY + WQ_GAUGE_INFO
+ WL_ DAT A_MAN + WQ_DATA
+ WL_ GAUGE_ INFO + WQ_PARAM
+ WL_ RAT ING_ CURVE

Image 83: DSS Software ERD

282
AWS - (Logical diagram)
class AWS

Do c No : ERD-AWS-01
AWS(Automatic Weather Station) Database Structure - 1/2 Versi on : 1.0

Base Info::RIVER_TERRITORY_INFO

col umn
*PK id: int
name: varchar(50)

PK AWS_GAUGE_INFO
+ PK_RIVER_TERRIT ORY_INFO(int)
1
col umn
*PK code: varch ar(50)
old_stati on_i d: varchar(50)
Base Info::VILLAGE_INFO FK ri ver_terri tory_id: int
FK catchment_ id: int
col umn FK agency_id: i nt
*PK id: int 0..* FK vi ll age_id: i nt
1
name: varchar(50) station_name: varchar(5 0)
station_type : i nt
0..* longi tude: float
latitude: flo at
elevati on: fl oat
Base Info::CATCHMENT_INFO
0..* observati on_start_ti me: dateti me
status: i nt
col umn
1
*PK id: int
FK ri ver_terri to ry_id: int FK
name: varchar(50) 0..* + FK_AWS_GAUGE_INFO_AGENCY_INFO(int)
+ FK_AWS_GAUGE_INFO_CAT CHMENT_INFO(int)
+ FK_AWS_GAUGE_INFO_RIVER_TERRITORY_INFO(i nt)
+ FK_AWS_GAUGE_INFO_VILLAGE_ INFO(i nt)
Base Info::AGENCY_INFO PK
+ PK_AWS_GAUGE_INFO(varchar)
col umn
*PK i d: i nt 1
name: varchar(50)

Associated Agency AWS_GAUGE_INFO


- PJT-II - Sto re informati on about automatic weather station

Image 84: AWS Database Structure 1/2

class AWS

AWS(Automatic Weather Station) Database Strucure - 2/2


Doc No : ERD-AWS-02
Version : 1.0

AWS_DAILY

col umn
*pfK co de: varcha r(50)
*PK date: d atetime
TN: fl oat
TX: fl oat
TM: fl oat
IT N: varchar(50)
AWS_HOURLY
IT X: varchar(50)
UN: fl oat
col umn
UX: fl oat
*pfK code: varch ar(50)
UM: fl oat
*PK date: dateti me
IUN: varchar(50)
hour: dateti me
IUX: varchar(50)
AWS_MINUTELY T : floa t
U4 : varchar(50)
U: floa t
U6 : varchar(50)
col umn U8: varcha r(50)
U8 : varchar(50)
*pfK cod e: varchar(50) U9: varcha r(50)
U9 : varchar(50)
*PK date : da tetime RR: fl oat
RR: fl oat
RR: fl oat RRX: fl oat
RRX: fl oat
DRR: varch ar(50)
IRRX: varchar(50)
VT: fl oat
FK DRR: varcha r(50)
VX: fl oat
+ FK_ AWS_MINUT EL Y_AWS_GAUGE_INFO(varchar) HH: varchar(50)
VM: fl oat
PK VN: fl oat
GV: fl oat
+ PK_AWS_MINUTELY(varchar, datetime) VNE: fl oat
RG: fl oat
VE: fl oat
PS: fl oat
VSE: fl oat
HH: va rchar(50)
VS: fl oat
BA: fl oat
VSO: fl oat
VO: flo at
FK VNO: fl oat
+ FK_AWS_HOURLY_AWS_GAUGE_INFO(varcha r) GIX: fl oat
PK VT : fl oat
+ PK_AWS_HOURLY(va rchar, date ti me ) VX: fl oat
IVX: varchar(50)
RG: flo at
PS: fl oat
PSX: fl oat
IPSX: varchar(50)
BA: fl oat
BAN: fl oat
BAX: fl oat
Associated Agency AWS_MINUTELY IBAN: varchar(50)
- PJT -II - 6 -min utes weath er data IBAX: varchar(50)
AWS_HOURLY
- h ourl y weather data
FK
AWS_DAILY
+ FK_AWS_DAILY_ AWS_ GAUGE_INFO(varchar)
- d ail y weath er data
PK
+ PK_AWS_DAILY(varcha r, da tetime)

Image 85: AWS Database Structure 2/2


283
Base Info - (Logical diagram)
class Base Info

Base Information Database Structure - [Region]


Doc No : ERD-BI-01
Versi on : 1.0

PROVINCE_INFO DISTRICT_INFO SUB_ DISTRICT_INFO VILLAGE_INFO

column column col umn col umn


*PK i d: int *PK i d: i nt *PK id: i nt *PK id: int
na me: varchar(50) name: varchar(5 0) name: varchar(50) name: varchar(50)
FK province_id: int FK district_i d: i nt sub_district_i d: i nt
1 0..* 1 0..* 1 0..*
PK
+ PK_PROVINCE_INFO(i nt) FK FK PK
+ FK_DISTRICT_INFO_PROVINCE_INFO(i nt) + FK_SUB_DIST RICT _INFO_DISTRICT_INFO(i nt) + PK_VILLAGE_INFO(i nt)
PK PK
+ PK_ DIST RICT _INFO(int) + PK_SUB_DIST RICT_INFO(i nt)

Associated Agency PROVINCE_INFO


- ALL - Pro vi nce Information
DISTRICT_INFO
- District Information
SUB_DISTRICT_ INFO
- Sub Di strict Information
VILLAGE_INFO
- Vil l age Informa ti on

Image 86: Base Information Database Structure


class Base Info

Base Information Database Structure - [Watershed, Agency]


Doc No : ERD-BI-02
Versi on : 1.0

CATCHMENT_INFO

col umn
RIVER_TERRITORY_INFO *PK id: i nt
FK ri ver_territory_id: i nt
col umn name: varchar(50)
*PK id: i nt area _km: fl oat
name: varchar(50) area _ha: float
1 0..*
peri meter: float
PK
+ PK_RIVER_TERRITORY_INFO(i nt) PK
+ PK_CAT CHMENT_INFO(int) AGENCY_INFO
FK
+ FK_ CATCHMENT _INFO_RIVER_TERRIT ORY(int) column
*PK i d: i nt
1
name: varchar(50)

PK
+ PK_AGENCY_INFO(i nt)
0..*

SUB_CATCHMENT_ INFO

col umn
*PK id: in t
FK catchment_id: int
name : varchar(50)
area: float
area_ ha: float
peri meter: float

FK
+ FK_SUB_CAT CHMENT_INFO_ CATCHMENT _INFO(i nt)
PK
+ PK_SUB_CATCHMENT _INFO(int)

Associated Agency RIVER_TERRITORY_INFO


- ALL - River T erritory Informati on
CATCHMENT_INFO
- Catchment Information
SUB_CATCHMENT_INFO
- Sub Catchment Informai on
AGENCY_INFO
- Agency Information

Image 87: Base Information Database Structure

284
Dam - (Logical diagram)
class Dam

Image Data (For all gauge station and hydraulic structure)


Doc No : ERD-DAM-01
Versi on : 1.0

DAM_OPER_PLAN

col umn
*PK rec_id: bigi nt
FK code: varchar(50)
Base Info::VILLAGE_INFO date: dateti me
normal : fl oat
column DAM_INFO dry: fl oat
*PK i d: i nt 1 wet: fl oat
name: varchar(50) column maks: float
*PK code: varchar(50) mi n: fl oat
ol d_dam_id: varchar(50)
FK river_terri tory_i d: int
FK
FK catchment_id: i nt
0..* + FK_DAM_OPER_PLAN_DAM_INFO(varchar)
0..* FK agency_id: i nt PK
FK vil l age_id: i nt
name: varchar(50) + PK_DAM_OPER_PLAN(bi gi nt)
type: int 1
Base Info::CATCHMENT_INFO
l ocati on_category: int
column l ongi tude: float
*PK i d: i nt 1 0..* l atitude: float DAM_DATA
FK ri ver_terri tory_i d: int el evation: fl oat
name: varchar(50) status: i nt col umn
postfi x: varchar(50) *pfK code: varchar(8)
1 *PK date: datetime
FK TMA: fl oat
0..* + FK_DAM_INFO_AGENCY_INFO(i nt) AM: float
+ FK_DAM_INFO_CAT CHMENT _INFO(i nt) AML: float
0..*
+ FK_DAM_INFO_VILLAGE_INFO(i nt) AK: float
PK AKT b: float
Base Info::AGENCY_INFO HJV: fl oat
+ PK_DAM_INFO(varchar)
Spil lway: fl oat
column Total : fl oat
*PK i d: i nt 1 power_production_kwh: fl oat
name: varchar(50) power_production_MW: float

FK
+ FK_DAM_DAT A_DAM_INFO(varchar)
PK
+ PK_DAM_DAT A(varchar, datetime)

Associated Agency DAM_INFO


- PJT -II - Dam Information
DAM_OPER_PLAN
- Annual DAM Operati onal Pl an.

Image 88: Image Data

Image Info - (Data Modeling diagram)


dm Image Info

Image Data (For all gauge station and hydraulic structure)


Doc No : ERD-IMAGE-01
Version : 1.0

Dam::DAM_INFO

col umn
IMAGE_DATA 1 *PK code: varchar(50)

col umn
*pfK code: varchar(8) 0..*
*PK i ndex: i nt
AWS (Automatic Weather Station)::AWS_GAUGE_INFO
i mage: image
hash: varchar(32)
col umn
0..* *PK code: varchar(50)
FK 1
+ FK_IMAGE_DATA_AWS_GAUGE_INFO(varchar)
+ FK_IMAGE_DATA_DAM_INFO(varchar) 0..*
+ FK_IMAGE_DATA_RF_GAUGE_INFO(varchar) Rainfall::RF_GAUGE_INFO
+ FK_IMAGE_DATA_WEIR_INFO(varchar)
+ FK_IMAGE_DATA_WL_GAUGE_INFO(varchar) col umn
0..* 1
+ FK_IMAGE_DATA_WQ_GAUGE_INFO(varchar) *PK code: varchar(50)
unique
+ UQ_IMAGE_DATA_code(varchar)
0..*
PK WaterLev el::WL_GAUGE_INFO
+ PK_IMAGE_DATA(varchar, i nt)

0..* 1 col umn


*PK code: varchar(50)

1
WaterQuality::WQ_GAUGE_INFO
Weir::WEIR_INFO
column
column 1 *PK code: varchar(50)
*PK code: varchar(8)

Image 89: Image Data

285
Rainfall - (Logical diagram)
class Rainfall

Rainfall Database Structure


Doc No : ERD-RF-01
Versi on : 1.0

Base Info::VILLAGE_INFO

column
*PK i d: i nt
name: varchar(50) 1
RF_GAUGE_INFO

col umn
*PK code: varchar(50)
ol d_station_i d: varchar(50)
RF_DATA_DAILY
0..* FK vi ll age_i d: i nt
FK catchment_id: int
col umn
FK agency_i d: i nt
Base Info::CATCHMENT_INFO *pfK code: varchar(50)
name: varchar(50)
*PK date: dateti me
l ongitude: float
column val ue: fl oat
l atitude: float
*PK i d: i nt el evati on: fl oat
1 0..* 1 0..*
FK ri ver_terri tory_i d: i nt observation_start_ti me: dateti me FK
name: varchar(50) status: int + FK_RF_DATA_DAILY_RF_GAUGE_INFO(varchar)
PK
FK + PK_RF_DATA_DAILY(varchar, dateti me)
+ FK_RF_GAUGE_INFO_AGENCY_INFO(i nt)
0..* + FK_RF_GAUGE_INFO_CATCHMENT_INFO(i nt)
+ FK_RF_GAUGE_INFO_VILLAGE_INFO(i nt)
PK
Base Info::AGENCY_INFO + PK_RF_GAUGE_INFO(varchar)

column
*PK i d: i nt 1
name: varchar(50)

Associated Agency RF_GAUGE_INFO


- BBWSC, DPSDA, PJT-II - Store gauge informati on
RF_DATA_DAILY
- Store dai ly rainfall data

Image 90: Rainfall Database Structure

USER_INFO - (Data Modeling diagram)


dm USER_INFO

Doc No : ERD-BI-02
Base Information Database Structure - [Watershed, Agency] Version : 1.0

USER_INFO AUTHORITY_INFO

col umn column


*PK ID: varchar(20) *PK No: int
* Name: varchar(50) * Name: varchar(100)
FK Agency: int * DataSearch: bi t
*FK Authori ty: int * DataModi fy: bit
* Password: varchar(50) * DamOperationPlan: bi t
0..* 1 * Wei rSchematic: bit
* DataImport: bit
PK * Stati onManagement: bit
+ PK_USER_INFO(varchar) * UserManagement: bit
FK
+ FK_USER_INFO_AGENCY_INFO(i nt)
PK
+ FK_USER_INFO_AUTHORITY_INFO(int)
+ PK_AUT HORIT Y_INFO(int)

Image 91: Base Information Database Structure

286
Water Level - (Logical diagram)
class WaterLev el

Doc No : ERD-WL-01
WaterLevel Database Structure - [Information] Versi on : 1.0

Base Info::VILLAGE_INFO
WL_GAUGE_INFO
colum n
*PK i d: int 1 column
name: varchar(50)
*PK code: varchar(50)
old_station_i d: varchar(50)
FK river_territory_i d: i nt
FK catchm ent_id: i nt
FK agency_i d: i nt WL_RATING_CURVE
0..* FK vill age_i d: i nt
station_name: varchar(50) col um n
equipm ent_type: int *PK rec_i d: bigi nt
Base Info::CATCHMENT_INFO l ongi tude: float FK code: varchar(50)
l atitude: fl oat year: int
colum n elevati on: fl oat RQ_form ula: varchar(50)
*PK i d: int observation_start_time: dateti me
1 0..* 1 0..*
FK river_terri tory_id: i nt status: int FK
name: varchar(50) operator_name: varchar(50) + FK_RAT ING_CURVE_FORM ULA_WL_GAUGE_INFO(varchar)
operator_phone: varchar(50)
PK
+ PK_RATING_CURVE_FORMULA(bi gint)
FK
+ FK_WL_GAUGE_INFO_AGENCY_INFO(i nt)
0..*
+ FK_WL_GAUGE_INFO_CATCHMENT_INFO(i nt)
+ FK_WL_GAUGE_INFO_VILLAGE_INFO(int)
Base Info::AGENCY_INFO PK
+ PK_WL_GAUGE_INFO(varchar)
colum n
*PK i d: int 1
name: varchar(50)

Associated Agency WL_GAUGE_INFO


- BBWSC, PJT -II - Water l evel station i nformati on
RATING_CURVE_FORMULA
- Rating curve formula data

Image 92: Water Level Database Structure (Information)

class WaterLev el

Doc No : ERD-WL-02
WaterLevel Database Structure - [Data] Versi on : 1.0

WL_DATA_AWLR_MINUTELY WL_DATA_AWLR_HOURLY WL_DATA_AWLR_DAILY

col umn col umn colu mn


*pfK code: varchar(50) *pfK code: varch ar(50) *pfK code: varcha r(50)
*PK dateti me: dateti me *PK datetime: d atetime *PK d atetime: da tetime
RR: fl oat T: fl oat T N: float
HO: float RR: float T X: float
HON: float T M: float
FK HOX: float IT N: varchar(50)
+ FK_WL_DAT A_AWLR_MINUTELY_WL_GAUGE_INFO(varcha r) BA: float IT X: varchar(50)
RR: float
PK RRX: fl oat
+ PK_WL_DAT A_AWLR_MINUT ELY(varchar, dateti me) FK IRRX: varchar(50)
+ FK_WL_DAT A_AWLR_HOURLY_WL_GAUGE_INFO(varchar) HOM: float
PK HON: float
+ PK_WL_DATA_AWLR_HOURLY(varchar, datetime) HOX: float
IHON: varcha r(50)
IHOX: varcha r(50)
PS: float
BA: float
BAX: fl oat
BAN: fl oat

FK
WL_DATA_ MAN + FK_WL_DATA_AWLR_DAILY_WL_GAUGE_INFO(varchar)
PK
column + PK_WL_DAT A_AWLR_DAILY(varchar, datetime)
*pfK code: varchar(8)
*PK date: datetime
water_level : float
di scharge: fl oat

PK
+ PK_WL_DAT A_MAN(varchar, dateti me)
FK
+ FK_WL_DATA_MAN_WL_GAUGE_INFO(varcha r)

Associated Agency WL_DATA_AWLR_MINUTELY


- BBWSC, PJT-II - 6-minutes wate r level data
WL_DATA_AWLR_HOURLY
- Hourly water l evel data
WL_DATA_AWLR_DAILY
- Dai ly water l eve l data
WL_DATA_MAN
- Manual ly measured water l evel data

Image 93: Water Level Database Structure (Data)


287
Water Quality - (Logical diagram)
class WaterQuality

WaterQuality Database Structure


Doc No : ERD-WQ-01
Versi on : 1.0

Base Info::DISTRICT_INFO

Base Info::VILLAGE_INFO col umn


WQ_GAUGE_INFO *PK id: int
col umn name: varchar(50)
*PK id: int FK province_i d: i nt
1 col umn
name: varchar(50)
*PK code: varchar(50)
old_station_i d: varchar(50) FK
FK ri ver_te rritory_id: in t + FK_DISTRICT _INFO_PROVINCE_INFO(int)
FK catchment_id: int 1 PK
FK agency_i d: i nt + PK_DIST RICT_INFO(in t)
divisi on_i d: i nt
0..* FK distri ct_i d: i nt
FK vi ll age_i d: i nt
Base Info::CATCHMENT_INFO 0..*
station_ name: varchar(50)
interval : varchar(50)
col umn equipment_type: i nt
*PK id: int longi tu de: float
1 0..*
FK ri ver_terri tory_id: int latitude: fl oat
name: varchar(50) elevati on: fl oat
observation_start_ti me: dateti me
status: int
operator_name: va rchar(50)
0..*
FK
+ FK_WQ_GAUGE_INFO_AGENCY_INFO(int)
+ FK_WQ_GAUGE_INFO_CAT CHMENT_INFO(i nt)
Base Info::AGENCY_INFO + FK_WQ_GAUGE_INFO_DISTRICT _INFO(i nt)
+ FK_WQ_GAUGE_INFO_VILLAGE_INFO(i nt)
col umn
*PK id: int 1 PK
name: varchar(50) + PK_WQ_GAUGE_INFO(varchar)

Associated Agency WQ_GAUGE_INFO


- BPLHD, PJT -II - Water Quali ty station information

Image 94: Water Quality Database Structure 1/2


class WaterQuality

WaterQuality Database Stucture - 2/2


Doc No : ERD-WQ-02
Versi on : 1.0

Contain s whole of water


quali ty data type WQ_STD_RIVER
includi ng water qual ity
WQ_PARAM
parameter for i ndustry. col umn
col umn *pfK ri ver_cl ass_code: i nt
*PK param_cod e: varchar(4) *pfK param_cod e: varchar(4)
BPLHDname: varchar(50) *PK date: date ti me
category: varchar(10) val ue1: flo at
unit: varchar(20) val ue2: flo at
* type: i nt = ((0)) 1
PJTIIname: varchar(50 ) 0..* u nique
+ UQ_WQ_STD_RIVER_ date(datetime)
PK + UQ_WQ_STD_RIVER_ param_code (varchar)
+ PK_WQ_PARAM(varch ar) + UQ_WQ_STD_RIVER_ ri ver_cl ass_code(i nt)
PK
1
+ PK_WQ_ST D_RIVER(i nt, varchar, dateti me)
0..* FK
+ FK_WQ_STD_RIVER_ RIVER_CLASS_INFO(i nt)
WQ_DATA
+ FK_WQ_STD_RIVER_ WQ_PARAM(varchar)
col umn 0..*
*pfK code: va rchar(8)
*pfK param_code: varchar(4) 1
*PK date: dateti me
val ue: fl oat RIVER_CLASS_INFO
*PK depth: in t
colu mn
*PK ri ver_cl ass_co de: i nt
PK
* regul ati on_date: date
+ PK_WQ_ DATA_1(varchar, varcha r, dateti me, int)
regul ati on_no: varchar(50 )
FK n ame: varcha r(50)
+ FK_WQ_DAT A_WQ_GAUGE_INFO(varchar) water_use: te xt
+ FK_WQ_DAT A_WQ_PARAM(varchar)
uni que
+ UQ_RIVER_CLASS_INFO_ri ver_cl ass_code(i nt)
PK
+ PK_RIVER_CLASS_INFO(int)

Associated Agency RIVER_CLASS_ INFO


- BPLHD, PJT -II, PUSAIR - River classi fi cati on based on governmen t regul ati on
WQ_PARAM
- Contains whol e of water qual ity data type
WQ_STD_RIVER
- Annual water q uali ty standard
WQ_DATA
- Water Quali ty d ata

Image 95: Water Quality Database Structure 2/2

288
Weir - (Logical diagram)
class Weir

Weir Database Structure - [Information]


Doc No : ERD-WE-01
Versi on : 1.0

Base Info::VILLAGE_ INFO

column WEIR_INFO WEIR_SCHEMATIC_IMAGE


*PK i d: i nt 1
name: varchar(50) col umn col umn
*PK co de: varchar(8) *pfK code: varchar(8)
(vi ll age_i d = id)
old _wei r_i d: varchar(50) img: image
*FK ri ver_territory_i d: i nt hash: varchar(32)
*FK ca tchment_id: i nt
*FK agency_i d: i nt
FK
* divi sion: int
0..* *FK vi l lage_i d: bi gi nt + FK_WEIR_SCHEMAT IC_IMAGE_WEIR_INFO(varchar)

* name: varchar(50) unique


Base Info::CATCHMENT_INFO
* type: int 0..* + UQ_WEIR_SCHEMAT IC_IMAGE_code(varchar)
column location_categ ory: i nt PK
*PK i d: i nt lon gitude: floa t + PK_WEIR_SCHEMATIC_IMAGE(varchar)
FK river_terri tory_i d: i nt lati tude: fl oat 1
1
name: varchar(50) ele vation: fl oat
0..* * sta tus: int
postfi x: varcha r(50)
sch ematic_images: image
*FK pro vi nce_i d: i nt
*FK district_i d: i nt
*FK sub_di strict_i d: int
0..*
Base Info::AGENCY_INFO PK
+ PK_WEIR_INFO(varchar)
column FK
*PK i d: i nt 1 + FK_WEIR_INFO_AGENCY_INFO(int)
name: varchar(50)
+ FK_WEIR_INFO_CAT CHMENT_INFO(in t)
+ FK_WEIR_INFO_DISTRICT _INFO(i nt)
+ FK_WEIR_INFO_PROVINCE_INFO(int)
+ FK_WEIR_INFO_RIVER_TERRITORY_INFO(i nt)
+ FK_WEIR_INFO_SUB_DIST RICT_INFO(i nt)
+ FK_WEIR_INFO_VILLAGE_ INFO(bi gint)

Associated Agency Weir has di fferen t data forma t by its type


- PJT-II If we ir type is general, data i s stored i n WEIR_DATA tabl e
If we ir type is special , data is stored in WEIR_DAT A_p ostfix table

Image 96: Weir Database Structure (Information)

class Weir

Weir Database Stucture - [General Type]


Doc No : ERD-WE-02
Versi on : 1.0

WEIR_SCHEMATIC

column
*PK Date: dateti me
Bekasi Utara: fl oat
Bekasi : float
Buara n: float
Pulog adung: floa t
Pejompongan: fl oat
WEIR_DATA
Karan g1: float
Karan g2: float
column
Karan g3: float
*pfK code: varchar(8)
Bekasi 2: float
*PK da te: datetime
Cikarang: fl oat
Q1 : float
Cipami ngkis: fl oat
Overfl ow: fl oat
Cibee t: fl oat
Q2 : float
Walah ar: fl oat
STU: fl oat
PK STT : fl oat
+ PK_WEIR_DAT A_1(varchar, dateti me) STB: fl oat
FK CFC: float
+ FK_WEIR_DAT A_WEIR_INFO(varchar) Cikao : float
Jati lu hur: fl oat
Cirata : float
Sagul ing: fl oat
Barug bug1: float
Barug bug2: float
Sungapan: fl oat Associated Agenc y
Benggal a: float - PJT -II
Jengkol 1: float
Jengkol 2: float
Cij engkol : float
Gadu ng1: float
Gadu ng2: float
Maca n: float
Ciase m: fl oat
Cigad ung: float
Salamdarma1: fl oat
Salamdarma2: fl oat
BMC: fl oat
Cipun egara: fl oat Dev ision II
Soma ng, ST _Wan ayasa, Pundong, Pondok_Salam, Wa ru, Walahar
PK
Dev ision III (South of Jatiluhur Irrigation Area)
+ PK_Wei rSchemati c(dateti me)
Curug _Agung, Cil eul euy, Leuwi nangka, Pa ngsor, Pedati, Lal anang

Image 97: Weir Database Structure (General Type)

289
Im
age 98: Weir Database Structure (Division I)

Image 99: Weir Database Structure (Division III)

290
Appendix 8: Summary of Meetings

Kick Off Meeting

The kick off meeting was held to discuss the scope, action plan and involvement of
stakeholders on 20 September 2010 at DGWR MoPW. Director of DWRM, DGWR in his
opening speech, stated that he anticipated K-waters approach of knowledge transfer and
every stakeholder should accommodate it by assigning proper level of counterpart for the
project. ADB suggested that the DSS system would be a web-based system to
accommodate every stakeholder for free access to database. To ensure long-term
sustainability and proper data sharing, a mutual agreement for data sharing was drafted
between BBWS Citarum and DPSDA. Through the discussion, the operation of DSS
would be designated to permanent agencies like PJT-II or PusAir. BBWS Citarum has
been mandated to be a River Manager by the Law No.7-2004, Government Regulation
No.42.-2008 and Decree of the Minister of Public Work. DSS should be placed in BBWS
Citarum, and considering BBWS Citarum has just established in 2007, the need for
capacity building of the staff of BBWS Citarum is urgent.

Image 100: Kick Off Meeting, 20 Sept 2010, DGWR meeting room, Jakarta

Inception Workshop
Package D inception workshop discussed the inception report, held on 14 December
2010, PJT-II Headquarter Office, Purwakarta. ADB (Dr. Thomas Panella) mentioned
that the success of DSS needs proactive participation from all stakeholders. MOU for
data sharing between BBWS Citarum and DPSDA was drafted. And clarification for
relationship between agencies in the DSS development and operation will be done by
K-water.

291
Image 101: Inception workshop, 14 Dec 2010, Purwakarta Technical Meeting

Discussion on the technical aspects of DSS development with stakeholders was held
on 29 September 2010 in PJT-II Bandung office. During this meeting, ADB stated
that a formal letter from DGWR for coordination meeting purposes should be
prepared and ADB would follow up a MOU for all agencies. K-water would consider
the needs of various stakeholders in DSS development. DGWR as an implementing
agency would assign the counterparts to Package D.

Image 102: Technical Meeting, 29 Sept 2010, PJT-II Bandung office

ADB 4th Review Mission warp up meeting


The draft Memorandum of Understanding was reviewed at the wrap up meeting on
26 October 2010, Akmani Hotel, Jakarta. Several comments on paragraphs in the
draft of MOU related to problems of each agency in implementing respected projects
were discussed during the meeting. Most comments from participant were of concern for
their projects and there was no objection or comment from other participants to the
progress of Package D.

292
Coordination Meeting between Package D and B2

The meeting about JSM (Java Spatial Model) 2.2-model result was held on 1 February
2011, PJT-II Bandung office. JSM 2.2 needs no licenses but needs metadata for
description result. Package D needs to collect JSM 2.2 model and all relevant data
from package B.

Initial inter-agency meeting

Initial inter-agency meeting held on 2 March 2011, PJT-II Bandung office discussed
objective and scope of DSS development, especially on the role, contribution and
budget of each agency. The Chairman mentioned that counterpart involvement is
essential for ensuring proper knowledge transfer and to keep sustainability of operation
and updating DSS.

Discussion with counterpart from BBWS Citarum

Discussion about required support from counterpart and introduction data


management system of BBWS C (Neoperdas) held on 21 March 2011, BBWS
Citarum, Bandung. As BBWS C and DPSDA signed joint operation (KSO) on 16
July 2010, DPSDA will not process data but solely collect them while BBWS C
processes the data. Hydrological activity in BBWS C is more advanced than expected
and they have 9 staff members in hydrology section.

Discussion with counterpart from PusAir

Discussion about counterpart required support on DSS development was held on 1


April 2011, PusAir, and Bandung. PusAir collected and maintained water quality
data in Indonesia (country level); however, the established local autonomy and each
jurisdiction level have taken over the river basin management (BPLHD and BBWS).
As research center, PusAir provides training in hydrology and water quality
management.

Coordination meeting with Package B

The coordination meeting held on 23 May 2011, Package B office, Jakarta, discussed
about some part of modeling and planning that have been done in package B quite similar
with DSS modeling and how it could be done harmoniously. And further meeting and
coordination needed to avoid duplication of works. In a meeting with RCMU, Jakarta on
the same date, discussed about progress and information about International Law Firm
providing funding for River Information System as part of their CSR program.

293
Initial inter-agency Workshops

9-10 August 2011 Workshopn on Legal Framework for DSS Implementation


The Summary
The implementation of Government Regulation (GR)/PP should not reduce the
subject that have been stipulated in GR/PP, but be able to translate into more
operational terminology. format data.
The SIH3 backbones for data collaboration/data sharing should be specifically
translated into clear policy terminology so that it can be implemented.
Data custodians are the Government institutions in charge of H3 component;
The governmental manager of data and information in each element of H3 should
be of Echelon Rank III at minimum to be able to coordinate smoothly.
The budget allocation should be clearly defined in the national program and
separated from other program budget allocation in one DIPA of each concerned
government institution.
The human resources for managing data and information should be trained
continuously and not easily moved to other posts.

Image 103: The Opening of the Workshop August 2011

294
1 February 2012 Workshop on Data Sharing Management
The Summary
The Director of DWRM-DGWR (Mr.Djajamurni WD) in Opening Speech
mentioned DGWRs continuous support for ICWRM implementation and
especially on Data Sharing Management for DSS implementation in CRB, which is
one of the important activities of TA.7189-INO. Institutional Strengthening for
Integrated Water Resources Management in the 6 Cis River Basin Territory. The
DSS is required to assist Decision Makers manage water resources in an integrated
and rational manner. Without that, it is almost impossible for technical
management tools to conduct IWRM in any river basin. The need of the DSS is due
to data which is scattered among the institutions in Central and West Java
governments, therefore, data sharing is inevitable for a sustainable and reliable
DSS. The national legal umbrella for the data sharing is now being processed in the
State Secretariat to be put under Presidential Regulation for guarantee of smooth
and consistent regional and basin wide implementation.
The Secretary of West Java Province (Mr.Lex Laksamana), in his opening remarks,
requested the stakeholder of water resources data in Citarum River Basin to
conduct their functions and tasks for their own benefits and for the Citarum vision
i.e. Cita Citarum. Therefore, the spirit of the word, sharing should be
implanted in each of activities to achieve the vision of Cita Citarum. Sharing is a
spirit of a balance of giving and taking that has to be facilitated using open
information technology that is being prepared in Decision Support System (DSS)
by DGWR with the technical assistance from ADB. The DSS should be completed
for the data sharing management could be established sustainably in achieving
integrated water resources management of Citarum River Basin. He especially
thanked DGWR and ADB that has launched the ICWRMIP and continue to support
all coordination tasks in implementation through Team SPOKI who has been
assigned to by the Governor of West Java since 5 December 2011.
The Secretary of BAPPEDA Jabar mentioned in his closing remarks that if we
could establish this data sharing management for integrated water resources
management in Citarum River Basin, and then we would be able to utilize and
manage the Citarum optimally for the people of West Java and DKI Jakarta. There
is no way to achieve the Cita Citarum without any collaboration in activities of
every stakeholder for Citarum River Basin. The BAPPEDA West Java will support
all program and budget that are required by West Java Dinas in implementing
ICWRMP, including the data sharing management. Implementation coordination
will be conducted through Team SPOKI, which has been instructed through West
Java Governor Decree No.050.05/Kep.1589-Bapp/2011 since 5 December 2011.
All participants understood and agreed that data sharing is inevitable not only for
the DSS to be used effectively but also for the nationwide sharing purposes, except
PJT II. This is because the DSS data managements open virtual data sharing
platform has not been completed yet. Only demo version is presented in the
workshop, therefore, the PJT II do not see how they can gain any benefits this,
hence not willing to participate. PJT II claimed that they already had a DSS for
their use for their own purposes and they have been collaborating with BMKG
Bogor through SPKTPA without any data sharing complexity or other difficulties.
They will participate in the data sharing after they know clearly what data can be
shared, what benefits can be gained, how these data and benefits will be shared,
295
what the level of users is, how the data security will be conducted and when this
can be started. Those could be verified for each stakeholder and agreed upon before
they sign the document of specific collaboration agreement. They support and will
participate in the process of verification.

Image 104: Opening Ceremony by the Secretary of West Java Province

Image 105: Workshop Attendees from Main Data Stakeholders in CRB

Discussion with Management of PJT II


Discussions with PJT II on Server specifications and locations have been done
several times from October 2011 to December 2011, and in the last meeting on 29
Decemeber, it was agreed that the location of Data Server and GIS Server will be
in BBWS Citarum and not in PJT II. This agreement is based on:
The internet provider in Purwakarta, where the PJT II Headquarter is, does not
provide public domain service (dedicated URL);
The PJT II can lend or transfer the assets (two servers) to BBWS Citarum because
the assets belongs to the Public Company (PERUM);
The BBWS Citarum by law and regulation has mandates to manage the water
resources within Citarum river territory (wilayah sungai).
Discussion with Management of BBWS Citarum

296
Discussions with The Head of BBWS Citarum on data sharing, server
specification and location were conducted several times during November 2011
and Janauary 2012 and some conclusions were derived:
The workshop on data sharing management should be led by the SPOKI Team that
was established by Governor of West Java, to coordinate all activities in
ICWRMIP. This Team is hired by the Secretary of West Java;
The specifications and location have been agreed upon by the BBWS Citarum,
where cheap and reliable Cloud System Fee has been used;
The technical staff that will manage the two servers which will be located within
the Internet Provider will be assigned and trained using the DSS version Feb 2012.

Discussion with the Management of BPLHD Jabar


Discussion with the Management of BPLHD Jabar on data sharing were carried
out during November 2011 and January 2012. The most important result was that
they will support the use of DSS data management as a virtual platform of data
sharing management in Citarum river with some prerequisite, i.e:
Data mapping which would verify the type of available data, data format, data
reporting format, and dissemination method;
Analysis on stakeholders available data gaps and overlaps based on their
mandates;
Several focus group discussions on the topics of mechanism of data sharing,
specific collaboration agreement and business plans. These discussions will discuss
deeply about: Goal and Purpose, scope of agreement, object of data sharing,
configuration of virtual platform base, configuration of data required for each
stakeholder, report configuration, copy right of data, level of data security,
AWP/ABP, working coverage, coordination meeting period, data custodian,
administration level of the data sharing management, dispute settlement,
mechanism of data sharing implementation, and period of the agreement.

Discussion with the Dinas PSDA Jabar


Discussion with the Management of Dinas PSDA were carried out during
November and December on the specific collaboration agreement that was made
between Dinas and BBWS Citarum. This was not working because there were no
support from the Legislative party when it came to financing. The most crucial
matter was to agree that the data and information in water resources are essenstial
for integrated water resources management, especially for water resources in West
Java ,an important source for DKI Jakarta, the Capita City of Indonesia. The
sample of agreement was given and was prepared for an initial template in data
sharing agreement among the data stakeholder in Citarum River Basin.

297
Discussion with the Management of Directorate WRI, BAPPENAS
The discussion was held on 11 January 2012. The important inputs derived from
this meeting are as follows:
Every institutions which are dealing with water resources data and information has
their legal mandates and is established for the sake of integrity of the Indonesia
Governance and Administration, therefore every institution has its own purpose;
When we discuss data sharing, we should be bear in mind that sharing means,
take and give instead of solely give or take. That is why the DSS should be
co-owned or jointly operated. This is schematically shown in figure below:

Synchronize Synchronize
Data Data

Use RRFS Use RRFS

Director of DWRI, DR. Donny Azdan, stated that DSS could be a platform for
virtual data sharing management during the developmental period. There is no
reason to not continue DSS development including the lack of funding.

ADB 6th Review Mission Meeting


The ADB 6th Mission started off with the kickoff meeting in Bandung chaired by
Director of WRI, Bappenas on 17 January 2012, followed by specific discussion
on 25 january 2012 for Package D, DSS for IWRM in Citarum RB. One of
important decisions by the ADB Mission was the DSS for IWRM in CRB Stage I
will be continued by National Experts and no International Experts inputs will be
put in place until the Proposal from GOI to KOICA is launched in March 2013
with a New Project.

298

You might also like