Part I - BRIEF PROJECT DESCRIPTION

1.0.1 In recent year, Bandung has been facing a number of flood which dealing a
significant damage and loss. Its morphological condition as surrounded by mountains, population
growth, drainage is issues, waste management issues, green space reduction contribute a higher
chance of flood occurrence. This leads the Government Bandung City to take initiative looking
for solutions that meet the flood problems.
1.0.2 Respecting to the project requirement of A Research Grant for Bandung Data
Innovation Program, we propose comprehensive solutions which fulfill the necessity of real-time
insight for disaster preparedness and flood forecasting.
1.0.3 This project will cover all the needs from capturing, manage, and training data from
the sensors and CCTV provided and compile all of it to give insights in helping Bandung
government in order to prevent and minimize the probability of loss caused by any upcoming
flood.
1.0.4 One motive of building flood warning systems of rivers is reducing the damages of
flood through warning the residents of flood areas and determining the real-time exploitation of
constructed dams on the rivers. The insights built up from captured data would help government
in taking emergency actions and providing progressed information about flood.
1.0.5 The proposed system prototype will be developed using agile methodology by the
project team with continuous improvement in each cycle.

Part II- PROPOSED APPROACH

2.0.1 We understand that the scattered and out-of-date data and information in different
government units are the main problem that drive the need to conduct flood preparedness in
Bandung. Therefore, Bandung government needs new insights to help them in achieving their
target of Bandung free flood in 2020.
2.0.2 Below are some strength and resources provided to support the project.
1. Strong collaboration with Diskominfo (Dinas Komunikasi dan Informatika) Bandung
2. 357 CCTV in 97 locations and 27 new weather sensors will soon be installed in sub-
district offices
3. USD 15,000 as the supporting budget for the researcher team
4. Team member with expertise on image analysis and censor
 With all of the capabilities mentioned above, below are the proposed approaches that we
offer to solve the problem.
2.1. Predicting Flood

2.1.1 Flood usually occurs at rainy seasons, especially in a basin terrain or in a

riverside area. If it occurs in an urban area, it may cause significant damages such as the
damages of infrastructure, crippled citizens activity, spread diseases which is caused by
unhealthy environment, and loss of valuables or even lives.
2.1.2 To predict a flood occurrence probability in a region, there are at least two
kinds of data involved: topological information over the region and water volume.

2.2. Patterns & Considerations

2.2.1 Water flows from the higher ground water source to the lower ground. Flood
usually occurs at rainy seasons, especially in a basin terrain or in a riverside area.
Therefore, below are the possible approaches to predict the flood probability.

Statistical prediction from previous data

2.2.2 This approach is fully dependent to the previous year data to conduct a simple
simulation and prediction on which dates may be potential for a flood to occurs. The
predicted data is gained from observing the frequency of flood occurrence in the previous
year on the same date and calculate the probability by combining the water level data
captured by the devices sensors.

Topological model + water source data

2.2.3 This is a more complex and complicated method and may cause invalid
prediction if there are some errors in determining the boundary value and assumptions.
This method calculates the probability by comparing the altitude of the highest point of the
river and the other points where the devices are located. By processing the water
flow/discharge and the area of the river, the system can predict how is the water level
would be in the future and can predict the potential area of flood occurrence.

2.2.4 Figure 1 shows the sketch of a single river which is equipped with some
devices to capture real-time data.
 Figure 1 Sketch of Device Implemented River

2.2.5 From the above explanation, here is the water flowing model expression in a
node:

Vwaterinasurface = Vwaterin Vwaterout

Figure 2 Equation to Calculate Water Level

Therefore, some conditions that may be the result of the calculation are:

If result is zero or negative then no flood

If it positive then it is most likely a flood to happen

2.2.6 In applying this model, we apply the assumption of water flow without friction,
acceleration and turbulence, so that all of the external factors are not included in the
calculation.
 Figure 3 Assumption of Water Flow from An Area

2.2.7 Figure 3 explains the assumption of water flows from region to region which is
like moving more likely from pixel to pixel. It has a possibility to move into 8 neighboring
regions if the neighboring regions (blue) are lower in height than the origin (green).

Part III- DATA USED, TECHNOLOGY AND OUTCOME

3.0.1 Below is the problem-to-solution mapping diagram that escalate some problems that
occurred in the current situation of Bandung. The detailed problems are derived from the main
problems that is happening in Bandung such as the high amount of waste production combined
with the scattered and unused past data. These things lead Bandung to worse circumstances and
longer time needed to achieve the main goal of Bandung Free Flood in 2020.
 Figure 4 Problem-to-Solution Mapping Diagram

3.1. Overview Project

This project is aimed to improve the effort in preventing flood disaster in Bandung. The
main features that will be implemented in the designed system are listed below:
3.1.1. Infrastructure Mapping
3.1.1 This feature will be implemented as a visual map that show the river
water level in real-time, the construction of building surrounding the area, and
generate useful insight for government. These data will be generated from sensors
located in some vulnerable points of the river and Dinas Pekerjaan Umums website.
3.1.2. Flood Simulation Modelling
3.1.2 This feature allows us to do simulation and prediction through the
possibility of flood disaster in certain area. With this feature, we can prepare the
possibility of flood disaster quickly and prepare nearest safety evacuation location
from that area. The prediction is done by processing data from previous annual
recorded data added by recent data derived from sensors.
3.1.3. Early Warning System (EWS)
After the implementation of sensors and flood simulation, then we can do
preparation for early prevention with the implementation of early warning system.
 This system integrated with sensors that attached in crucial point of flood. At some
level, system will send a warning signal that informed the possibility of flood in that
area.
3.2. Project Components

This project consists of some supporting components to form main system. Data,
application, and technology that used in this project will explained below:
3.1.1. Data
Data collected from sensors that attached in some area and from annual data record
about flood disaster in Bandung. Those Data will be grouped into three main group. They
are Topology Data, Water Volume Data, and Region Data. Topology Data talk about the
condition of land/ground and building visualization around vulnerable point of flood in
Bandung. Those data will give us insight about how to manage evacuation method in
emergency. Water Volume Data give information about river condition that will be the
main information to determine next required action. Region data give information about
external river environment that also give effect to river condition. Those three main groups
of data will be processed and simulated in making simulation model to give information
about flood potential in certain surrounding area. The Data can be obtained from:

Figure 5 Data Use Visualisation of Early Warning System

3.1.1.1. Dinas Pekerjaan Umum

Data derived from this source talk about environment condition around flood
vulnerable area. Those data include land contour and building visualization in surrounding
area.
Land Countour

Building Visualization

3.1.1.2. Badan Meteorologi Klimatologi Geofisika

Data derived from this source talk about weather condition around vulnerable point.
Those data include weather condition, temperature, time, humidity, wind velocity, and
wind direction.

Weather Condition

Temperature

Time

Humidity

Wind Velocity

Wind Direction

3.1.1.3. Balai Besar Wilayah Sungai Citarum

The Data that derived from this source are talking about rivers condition, water
building, water drainage system, and another thing related to water condition in Bandung.
Data classes that will used commonly listed below:
Data of River
River Code
River Name
River Order
Passed Area
River Status
Estuary

Data of Upstream and Downstream

Altitude Position
Latitude Position
Technical Data
River Drainage Area Data
Maximum Width
Mean Width
Minimum Width
Minimum Depth
Maximum Capacity
Mean Slope
River Length
Debit Mainstay

Debit of Flood
3.1.2. Application
The Application that developed is a dashboard that can give information, data
visualization, modelling, and simulation about condition of specific vulnerable area. It also
gives a prediction about the possibility of flood disaster and its mitigation plan.

Data
Application Integration
Interface Analytics Devices
Platform Services
and Model

Weather Sensor
HTML SOA
Java, ME
CCTV (Surveillance
Devices)

CSS JSON
Vector Image
Detector
Decision Support
Android
System
Moving Object
ArcGIS XML Detector

Water Debit
Detector
iOS
Mobile IDE REST API Moving Object
Identifier

Figure 6 Technology Stack of Early Warning System

From that picture, we get information that this system will be developed in some
layers. Those are,
a. Interface Layer: This layer will provide visual content that shows many information
needed about flood prediction, simulation, warning system, etc.
b. Application Platform: This layer shows in which device this system can be
accessed. This system may be accessed in some platform such as android, iOS, and
web browsers.
c. Data Analytics and Model: This layer shows technology concept (Decision Support
System) that will be used to do some prediction and simulation based on data that
collected. Those data will be processed by Artificial Neural Network so we can
predict the next situation based on some input data.
d. Integration Services: This layer will provide how to transfer the information and the
mechanism of communication between devices and server.
e. Devices: This layer shows what kind of devices that will be implemented and support
to this project.

These are some example of data visualization that developed in this project. This
visualization located in application-level.
a. Water Level Data by Region
This visualization gives us information about water level in specific area that
monitored by sensor and surveillance unit. It also gives information about predicted
upcoming floods so everyone can prepare for evacuation.

Figure 7 Water Level Data by Region Visualization

b. Device Location
It gives information about location of all sensory devices and all information about
river condition ranked by its flood possibility risk. It also shows a clickable icon that will
show us about water debit and water level of area around the device.
 Figure 8 Device Location Visualization

3.1.3. Technology
This section will explain the detailed technologies used in this project. It also informs
how those technologies communicate and connected.

Figure 9 Technology Block Diagram of Early Warning System

3.1.3.1. Data Retrieval Infrastructure

This section shows the requirements that needed in building the data retrieval
devices which will be placed in some area on the river.
Component Description Minimum
 Specification
Water-level These sensors will be placed in - Resistant to
sensors some prone area along the river. It waterflow or having a
will give us information about the high durability
level of water in the river so we can - Rapid sensing
do some prediction with those data. - Accurate
measurement
Microcontrollers It will be used to process data - Highly processing
gained from sensors and prepare it ability
to be sent to server through the - Economical
communication modules - Having high
durability of any
condition
LCDs LCD will be used to visualize the - Clear visualization
information that has been processed - Easy customization
by the administrator. It will give
information to people along those
river about the condition of river.
So, they can prepare early if an
unwanted situation occurs.
Light Indicators Light indicator also used to give - Can be seen from
information about the condition of 100m away
river. This light indicator is the - Common color sign
simplest sign that can be understand
by people around it.

3.1.3.2. Communication Module

This section shows the requirements that needed in building a good
administrative system to accommodate this whole system.
Component Description Minimum
Specification
Access Point This device will connect some of - Can support at least
data retrieval devices 10 devices connection
VPN It will provide a secure and private - Use privilege access
connection among devices and system
administrator. It used to protect the
data flow so it wont be distracted
by someone. It also will rise the
efficiency of the data transfer.
Wireless This connection used to bridge the - Using WAN to
Connection communication between device and accommodate some
administrator that locate in remote devices along the
 area. river
- Minimum Bandwidth
10 GB
- Data Transfer
25Mbps

3.1.3.3. Server Side

This section shows the requirements that needed in building a good
administrative system to accommodate this whole system.
Component Description Minimum
Specification
Databases It used to store all data and - Contain of
information processed from devices Operational Database,
and Analytical tools. Analytical Database
and Data Warehouse
- Using MSSQL,
Oracle, PostgreSQL,
or IBM DB2 (high
performance
databases)
Processor It used as the brain for analytical - Support High
work. Calculation and Data
Processing ~3.4Ghz
Monitoring It used to show all information - Support all
System gained from this system. It also information that
used to help in making decision for required to be shown
the next right step.

Figure 6 show the scheme of technology used in this system.

Figure 10 Technology Block Diagram
Part IV POTENTIAL RISK AND ISSUE

This section is made to explain risk and issue that can be happened in doing this project. Table below shows the issue, impact,
and recommended action to handle it. Its made by Failure Mode Effect Analysis (FMEA) method.
Potential
Current
Potential Potential Effect(s) Cause(s)/ Det Recommended
No Risk/Issue Sev. Prob. Design RPN
Failure Model of Failure Mechanism(s) of . Action(s)
Control
Failure
Gathering Hard to obtain Long term 9 Miss 1 Availability of Gather all of the
information or gaining development communication TOR potential data sources
false destruction or and wrong from the trusted
1. information scope creeping information 1 9 government agencies,
source such as: BBWS
Citarum, Diskominfo,
BandungGov
Revision Capital unit as In the end of 5 Lack of 1 Keep in touch with
from capital a supervisor project there will communication capital unit
unit have a be a lot of revision between
2. 1 5
different developer and
perspective capital
with developer
Sensor Damaged Get wrong data 8 Sensor not 1 Do a regular check
internal thread calibrated yet and maintenance to
3. 3 24 ensure that the device
can capture data
properly
Sensor Damaged Sensor broken 6 Sensor doesnt fit 2 Do some adjustment
4. external thread down with the 1 12 in implementing the
environment device
Procurement Procurement Less or over 5 Mistaken in 3 Use expert Increase the
hardware budgeting making the service unexpected cost in the
5. budget plan 1 15 budget plan with some
consideration of the
risks that may occur
 Member Uncommitted Distracted work 7 There is no work 1 Use expert Make a contract
6. project contract service 1 7 before hiring
member employee
Timeline The ongoing Project wont 7 Unstructured 3 Use expert Make contingency
project complete on time timeline service plan to prevent the
timeline is not exceeded timeline
7. 1 21
in accordance
with the
original plan
Government A structural New responsible 4 The need to 3 Involve Preparing the
structure change in person and manage the government transition process
government is administrator implemented earlier by
8. needed due to system 1 12 communicating the
the needed changes with
implementatio the government
n of the system
Government Disaster Policy needs to be 3 A proper policy 2 Involve Communicate with
policy handling and change should be made to government relevant government
9. evacuation support the 1 6 agencies
policy changes implementation
may occur of the system

Sev =Severity
Prob = Probability
Det = Detection
RPN = Risk Priority Number
RPN = Sev x Prob x Det
Part V DEVELOPMENT METHODOLOGY

In working this project, the most suitable methodology is agile development combined
with scrum in the implementation.

No Aspects Agile Waterfall

1 Customer High Low (only at the beginning and

Involvement the end)

2 Scope & Continually changed and Defined once only in the initial
Requirements updated planning phase

3 Time Management Effective regular boxed High possibilities of delayed

duration (sprint) process

4 Teamwork & frequent communication and Less-frequent communication

Communication face-to-face interactions between team members and
customers

5 Process Iteration (more effective) One-way only, cant return to the

previous stage

6 Testing Consist of unit/part and Only performed at the end

integration testing in every
sprint/cycle

From the table above, we can see that agile methodology brings up many benefits more
than the waterfall methodology. Below are some possible gained benefits of agile methodology
in performing this data innovation project:
1. produce prototypes quickly that the user can evaluate and use to refine requirement
2. provide high degree of collaboration between the client and project team
3. increasing government satisfaction due to high quality product
4. Reduce lost cost and probability
5. More productive team
Hence, we believe that agile development methodology is the most suitable for this project
to gain the best work products and performance.
The project development is divided into phases in six months starting from October 2017
and will be finished on March 2018. Below is the general timeline of the whole development
process.
 Figure 11 Project Timeline

In order to ensure that the system has meets all of the requirement, we will conduct a few
tests during the whole development process. Here is some general test case that will be included
in the test.

1. Hardware testing
The test will be performed on the real-environment to gain the real data directly from
the hardware/device and to ensure that the device could suit in the real environment.
2. Server testing
This test is performed to ensure that the back-end could run and support the whole
system architecture while operating and conducting insights from the raw data.
3. Software testing
The test is performed to see how far the software has meet the functional and non-
functional requirements as stated in the agreement.
 4. Communication & data transfer testing
The test is performed to ensure the data transfer from the device to the server could
be proceed without any error.
5. Integration testing
This test combines and involves all of the hardware, software, and communication
protocol to operate simultaneously.

Figure 12 Test Scheme

Beside all of the tests mentioned above, we also will perform User Acceptance Test (UAT)
in the end of the project development to ensure that the product could successfully operate and
be the suitable answer for the government needs.

The development process starts from defining requirements, design, development (coding),
quality analysis, until user acceptance test to gain the client feedback. This process iterates
continuously to ensure every feature and requirement is fully implemented in the system. Below
is the table of all the project team members and their qualifications that involved directly the
development process.

No Role Qualifications Total

1 Project Manager Certified as a professional in project management (PMP, 1

CAPM, Associate in Project Management)

2 System Analyst Experienced and proficient in conducting report & requirement 1

document

3 UI/UX Designer Experienced and familiar with adobe photoshop or other similar 1
application

4 Database Can operate one of listed database (MySql, Oracle,IBM2) 1

Administrator
5 Hardware Graduated as a bachelor of engineering from a certified 2
Engineer educational institution, familiar and have passions in creating
devices from sensors.

6 Software Graduated from a certified educational institution majored in 3

Engineer computer science and have experience in conducting some
related projects.

7 Architecture Certified as a TOGAF professional, has a wide knowledge in 1

Specialist integrating all business, data, technology, and application
sector.

8 Legal & Familiar in conducting documentation, have a good 1

Administration communication and sense in building relation, have
experienced in some previous government projects.

9 Environment Graduated from a certified educational institution majored in 1

Specialist environmental engineering and have experience in conducting
some related projects.

Total Project Team Members 12

All of the project team members are fully committed during the development time and will
provide the best performance in producing the solution in order to meet the government needs.
All of the development process will be documented and combined to make some progress
reports and a final presentation that will be delivered to the government as the real evidence of
the whole development process. All of the documentation will also be published as a certified
paper in IEEE and indexed as one publication in Scopus and Thomson Reuter.