JOINT COOPERATION PROGRAMME

Component D2:

Flood Early Warning System

Document D2.7 Final report Jakarta Floods January 2013

April 2013

Project: 1201430.000

Client: Water Mondiaal Partners for Water Royal Netherlands Embassy in Jakarta

Period: January 2011 – March 2013

Main Report

GOI – GON

Jakarta Floods January 2013 Flood Hazard Mapping (FHM) Joint Cooperation Program (JCP)

Deltares, HKV PusAir, RHDHV

BBWS Ciliwung – Cisadane Dinas PU DKI

Integrated GOI-GON Delta approach

April 2013

FHM – Emergency Assistance – Flood January 2013 Joint Cooperation Program (JCP)

Jakarta Floods January 2013

Final Report

Prepared for: Royal Embassy of the Netherlands Ministry of Public Works, Indonesia (PU)

Jakarta Floods January 2013

Main Report

April 2013

a 1207961 Jakarta Floods January 2013 1207961 April 2013 Main Report

Contents

1 Introduction ...... 1 1.1 Jakarta Emergency assistance...... 1 1.2 Purpose of this report ...... 1 2 Description of the January 2013 floods ...... 3 2.1 Wet season 2012 – 2013 ...... 3 2.2 Wet period January 15 – 18, 2013 ...... 5 2.3 Inundation of Pluit polder ...... 5 2.3.1 January 10th till January 17th – high rainfall in the upstream Ciliwung Catchment and the city of Jakarta ...... 5 2.3.2 January 17th – Overtopping of the BKB and flooding of the City ...... 7 2.3.3 January 17th till January 24th – Inundation of pluit ...... 9 2.4 Preliminary analysis – Conditions leading to Pluit flooding ...... 12 2.4.1 Discharge of the Ciliwung ...... 12 2.4.2 Overtopping of the Banjir Kanal Barat ...... 13 2.4.3 Inundation of Melati, Cideng and Pluit polders ...... 15 3 Identification of Urgent Flood Measures ...... 18 3.1 Identification of measures ...... 18 3.2 Diverting flow from the Ciliwung ...... 18 3.2.1 Ciliwung – BKT diversion ...... 19 3.2.2 New flood strategy for the Ciliwung – BKB system ...... 20 3.2.3 Katu Lampa – Cisadane diversion ...... 21 3.3 Ciliwung-BKT diversion...... 21 3.3.1 Introduction ...... 21 3.3.2 Improvements required at the BKT and Cipinang ...... 23 3.3.3 Diversion capacities ...... 24 3.3.4 Effect of diversions on Ciliwung and Banjir Kanal Timur water levels ...... 25 3.3.5 Towards “equal distribution” ...... 28 3.3.6 Prefer ability of alternative...... 29 3.4 Katu Lampa – Cisadane diversion ...... 30 4 Flood information at BNPB and BPBD Jakarta...... 33 4.1 Pusdalops at Badan Penanggulangan Bencana Daerah (BPBD) ...... 33 4.2 Pusdalops at Badan Nasional Penanggulangan Bencana (BNPB) ...... 35 4.3 Information and coordination meetings ...... 35 4.4 Problems identified by BPBD, BNPB ...... 36 5 National FMIS for Disaster Management ...... 37 5.1 Background ...... 37

Deltares, HKV, PusAir , RHDHV i

Jakarta Floods January 2013 1207961 April 2013 Main Report

5.2 FMIS architecture ...... 37 5.3 Client applications ...... 39 5.3.1 Customized Dashboard of FMIS information ...... 39 5.3.2 Supports crowd sourcing functions ...... 40 5.3.3 Supports data entry by SMS or other web-apps ...... 40 5.3.4 Supports internal communication ...... 40 5.3.5 Produces impuls upon exceedance of thresholds ...... 40 5.3.6 Support downloads and onwards communication of FMIS information ...... 40 5.3.7 Supports registration and access management by an information manager ...... 40 5.4 Web services ...... 40 5.4.1 Data request processes ...... 40 5.4.2 Communication processes ...... 41 5.5 Webserver ...... 41 5.5.1 Data gathering processes ...... 41 5.5.2 Other server tasks ...... 41 6 Emergency Assistance Development ...... 42 6.1 Customized visualization of FMIS information: ...... 42 6.1.1 Planar Application ...... 42 6.1.2 Water Map Application ...... 43 6.1.3 Web service ...... 44 6.1.4 Webserver ...... 44 6.2 Impulse upon exceedance of threshold ...... 44 6.3 Crowd sourcing from Twitter ...... 44 6.3.1 Web service ...... 45 6.3.2 Webserver ...... 45 6.4 Data entry by SMS for Flood map ...... 45 6.4.1 BPBD expands their SMS Gateway...... 45 6.4.2 HKV receiving text messages ...... 46 7 Testing of the Twitter Map...... 47 7.1 5 February inundations ...... 47 7.2 5 March inundations ...... 48 7.3 18 April inundations ...... 50 A Generation of rainfall maps for Melati, Cideng and Pluit ...... 53 B Creating the flood depth map ...... 58 C Technical documentation ...... 64 D Meeting Minutes BNPB/ BPBD ...... 70 E Presentation Soft Soil Tunneling in Urban Areas ...... 74

Deltares, HKV, PusAir , RHDHV ii

Jakarta Floods January 2013 1207961 April 2013 Main Report

1 Introduction

1.1 Jakarta Emergency assistance During 15 till 18 January 2013 Jakarta and Bogor areas experienced heavy rain leading to several high river waves entering and flowing through Jakarta. On January 17 one of the river banks of the Western Flood Channel (Banjir Kanal Barat, BKB) could not withstand the permanent high water levels and collapsed over a length of 76 meter. As a result for about a day water from BKB entered the city with a rate of about 100 m 3/s. At the same time heavy rains (over 150 mm/day) pounded the city and this combination resulted in very heavy flooding in the Thamrin, Menteng, Pluit areas of Jakarta. The heavy rainstorm also caused overflowing of the Angke and Pesanggrahan river causing considerable flooding in the north western parts of the city. To a lesser extent also the north eastern areas experienced flooding due to local rainfall. No flooding appeared in the south eastern areas where the rain waters were safely transported to the sea through the new Eastern Flood Channel (Banjir Kanal Timur, BKT). On the 19th of January most of the floods in the central parts of Jakarta already receded, but many Northern areas remained flooded for several days. Especially the Pluit area was severely affected by the floods and remained flooded for over 10 days.

The Royal Netherlands Embassy (RNE) and the Ministry of Infrastructure and the Environment (Min I&E) of the Netherlands stayed in close contact with the Indonesian Ministry of Public Works (PU) to see if the extensive Dutch knowledge of the water system of Jakarta could be mobilized to assist Jakarta during the flood operations and with the aftermath of the floods. Already on January 18 the Government of Indonesia (GOI) and the Government of the Netherlands (GON) agreed on cooperation to assist Jakarta. Deltares and HKV were invited to identify with the experts of the Ministry of PU the principal elements of this assistance for both the short-term (till the end of the current flood season, March 2013) and the longer term. The assistance started on January 21, 2013.

For the short-term three areas of assistance were identified to assist both National and Provincial (Jakarta) governments with the flood aftermath and prepare for urgent measures and operation during the remaining of the flood season:

- Evaluate ‘what happened’ and identify ‘new lessons learnt’ - Assist with the identification of additional urgent flood measures - Assist, maintain and improve critical parts of the Jakarta Flood Early Warning System (JFEWS) for both National and Provincial: o Flood operation and management o Disaster centres

1.2 Purpose of this report This report, dated April 2, 2013, present the results and findings of the assistance based on the final Work Plan (dated February 5, 2013) and confirmation of RNE (dated February 26, 2013) for the short-term services to assist both the National and Provincial governments of Indonesia and Jakarta with the aftermath of the floods of January 2013. The report is based on intense and close communication with both GOI and GON and compiled by the Emergency Flood Team staffed by experts of Deltares (lead firm) and HKV.

Deltares, HKV, PusAir , RHDHV 1

Jakarta Floods January 2013 1207961 April 2013 Main Report

Chapter 2 provides the evaluation (‘what happened’) of the January 15 – 18, 2013 flooding. Chapter 3 provides the evaluation of urgent measures in particular new concepts for equal distribution of flood waters from the Ciliwung to BKT and BKB. Chapters 4 - 7 present the assistance provided to the National and Provincial disaster centres as well as the enhancements of Jakarta Flood Early Warning System (JFEWS) to improve the flood information for the immediate and future support to the flood and disaster operations.

Deltares, HKV, PusAir , RHDHV 2

Jakarta Floods January 2013 1207961 April 2013 Main Report

2 Description of the January 2013 floods

2.1 Wet season 2012 – 2013

The wet season 2012 – 2013 can be characterized as a ‘very wet’ wet season. Already in November 2012 the wet season started with frequent rain storms both in the upstream areas and in Jakarta. From mid December 2012 the rains intensified. Figure 2 shows the resulting measured water levels at key locations (see Figure 1) along the Ciliwung and BKB (from upstream to downstream: Katu Lampa, Depok, Manggarai and Karet) in combination with the warning (siaga) levels. From end of December onwards the water levels along the Ciliwung frequently surpass the warning levels.

Also in the west of the Jakarta catchment frequent high waters occurred (see Figure 3), while the eastern parts appeared to be drier than the other areas (see Figure 4).

Figure 1- Key water level locations in the Jakarta catchment area

Figure 2- Water levels at key locations along the Ciliwung, December 1, 2012 - February 10, 2013 (source JFEWS)

Deltares, HKV, PusAir , RHDHV 3

Jakarta Floods January 2013 1207961 April 2013 Main Report

Due to the intense flood rehabilitation and construction program, which was implemented after the severe flooding of February 2007 by the Balai Besar Wilaya Sungai Ciliwung-Cisadane (BBWSCilCis) and DKI, during most of the period the high waters were safely transported through the urban areas to the sea.

All figures also clearly show the very wet period January 15 – 18, 2013 during which many areas in Jakarta were flooded. Most of these local floods were caused by heavy rainfall on the city itself, but along the Ciliwung – BKB system heavy flooding occurred due the collapse of the revetment at Laturharhari in combination with heavy local rainfall.

Figure 3 - Water levels at key western locations, December 1, 2012 - February 10, 2013 (source JFEWS)

Figure 4 - Water levels at key eastern locations, December 1, 2012 - February 10, 2013 (source JFEWS)

Deltares, HKV, PusAir , RHDHV 4

Jakarta Floods January 2013 1207961 April 2013 Main Report

2.2 Wet period January 15 – 18, 2013

From January 15 till 18 heavy rain storms passed over the Jakarta area from the West. Figure 5 shows the rainfall on January 16 arriving from the West covering nearly the whole catchment area resulting in peak (siaga 1) water levels in Katu Lampa on January 15, 16 and 17.

Figure 5 - Rainfall arriving from the West on January 16, 2013

2.3 Inundation of Pluit polder

2.3.1 January 10th till January 17th – high rainfall in the upstream Ciliwung Catchment and the city of Jakarta Large floods in Jakarta are usually accompanied with periods of a few days with extensive rainfall prior to the event. Figure 6 shows rainfall in the upstream Ciliwung catchment (Katu Lampa, Depok) together with rainfall in the city (Manggarai and Istana). This data is collected from posko piket at DPU (also known as PU2). From the rainfall graph you can see rainfall volumes are substantial from January 12th, January 15th and January 16th are especially wet in the upstream catchment (Katulampa and Depok). January 16th and January 17th are extremely wet in the city of Jakarta. No statistics have been derived for the gauges of Istana or Manggarai. Also, both stations haven’t been checked on quality. Taking into account these facts, it is likely that the recurrence period of the rainfall in the city of Jakarta January 17th could well me > 25 years.

Deltares, HKV, PusAir , RHDHV 5

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 7 shows that the extensive rainfall in the upstream Ciliwung catchment caused increased water levels at the Ciliwung gauging stations from noon January 15th until the overtopping and collapse of the Banjir Kanal Barat (BKB) embankment in the morning of January 17th and thereafter.

Rainfall (Posko Piket DPU) 250 KATULAMPA

225 DEPOK

MANGGARAI 200 ISTANA 175 ) y a 150 d / m m (

e 125 g r a h c s

i 100 D

75

50

25

0 Jan 10th Jan 11th Jan 12th Jan 13th Jan 14th Jan 15th Jan 16th Jan 17th Jan 18th

Figure 6 – Rainfall from January 10th until January 18th

Water levels along Ciliwung 12 BKB collapse WL Katulampa WL Depok 10 WL Manggarai WL Karet

8 ) ? ?

+

m (

l

e 6 v e l

r e t a

W 4

2

0 10-1-2013 11-1-2013 12-1-2013 13-1-2013 14-1-2013 15-1-2013 16-1-2013 17-1-2013 18-1-2013 19-1-2013 20-1-2013

Figure 7 – Water levels at Ciliwung from January 10th until January 20th

Deltares, HKV, PusAir , RHDHV 6

Jakarta Floods January 2013 1207961 April 2013 Main Report

2.3.2 January 17th – Overtopping of the BKB and flooding of the City From hourly rainfall recordings and the rainfall radar it is known that the day the BKB was overtopped started with heavy rainfall. This lead to inundation at Placa Indonesia due to local rainfall. As a response the operators of pompa air Melati opened pintu air (PA) Sogo (see Figure 8), which connects Melati polder to Cideng polder. This decision was made at PU2. According to the operators this decision was made at 03.00 am at the morning of January the 17th. Via the Lower Krukut, Melati, Cideng and Pluit are now all connected. However, the connection between Cideng and Pluit at the Lower Krukut is only a very narrow underpass.

The early morning the city-side embankment of the BKB broke (see Figure 8 - Figure 10). At that moment water was also flowing in the city via PA Ciliwung Lama, which also overtopped, somewhere between 08:00 and 09:00 am. Figure 11 shows a rise of water levels at Melati and Cideng at that moment. The operator of Cideng opened PA Cideng and PA Taragan, connecting Cideng with Pluit. At the evening of January 19th the gap in the BKB was fully closed.

Lower Krukut

Figure 8 – Revetment collapse (BKB break) and the Melati, Cideng and Pluit polders

Deltares, HKV, PusAir , RHDHV 7

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 9, Revetment collapse at Laturharhari (76 meter long, From 17/1 7am – 19/1 10pm)

Figure 10, Revetment collapse at Laturharhari

Deltares, HKV, PusAir , RHDHV 8

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 11 – Rising of water levels at Cideng, Melati and waduk Pluit`

2.3.3 January 17th till January 24th – Inundation of pluit After the BKB overtopping Water could flow to Pluit via the Ciliwung Lama and the roads north of the BKB (see Figure 12). Because PA Sogo, Taragan and Cideng all where open, the water could flow to Pluit polder (see Figure 13). During this period pompa Cideng was shortly out of operation. At Melati pump station, most pump stations where working properly.

Figure 12 – Overland flooding of Pluit area

Deltares, HKV, PusAir , RHDHV 9

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 13 – Canal routes from the BKB break to Pluit

In fact, the flooding of Pluit polder took place one day later in the afternoon of January 18th. At that moment, waduk Pluit (80 ha) was totally filled. When the water levels at Pluit reach +/- 3 meter at the peil skaal, water will flow to the surrounding area. At Pluit no pumps where working. The east pumphouse is demolished and currently under reconstruction. The middle pump house was immediately flooded and out of operation as a consequence. The west pump house was not working since the power supply was cut and the backup generator was not functioning. After about 2 days power was reinstalled. Pluit pumped with capacities between 6m3/s (1 pump working) and 18 m3/s (3 pumps working). During a visit at January 19th three pumps where functioning. Also it must be noted that the given capacities at Pluit are design capacities. Nobody can tell the exact capacity of each pump, especially under influence of sea water levels.

Figure 14 and Figure 15 shows the path of the flood waters from the BKB break and the heavy rainfall towards Pluit. Figure 16 shows the flood extent of Pluit polder in more detail. Flood depths of > 2 meter were reached for several days, requiring the evacuation of around 15,000 families.

Deltares, HKV, PusAir , RHDHV 10

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 14, Path of the flood waters from BKB break towards Pluit

Figure 15, Flooding by rain and BKB break at Plaza Indonesia

Deltares, HKV, PusAir , RHDHV 11

Jakarta Floods January 2013 1207961 April 2013 Main Report

Flood depth [m]

0-0.25 0.25 - 0.5 0.5 - 0.75 0.75 - 1 1 - 1.5 1.5 - 2 >2

Figure 16 – Flooding of Pluit

2.4 Preliminary analysis – Conditions leading to Pluit flooding

2.4.1 Discharge of the Ciliwung Figure 17 shows maximum discharges estimated based on the water levels at Depok on the Ciliwung. The problem with deriving Discharges at the Ciliwung is the quality of the rating curves. In Jakarta Flood Management Studies (JFM) 1, rating curves are derived from a limited number of discharge-water level observations at low water levels. The rating curve is extrapolated by the FHM-framework to high QH combinations. These high QH combinations should be verified in the field (during floods) to improve accuracy. Two further aspects should be considered while interpretation of Figure 17:

- The regulating effect of the slopes and backwaters between Depok and Manggarai will reduce peak levels. Upstream peaks (Katu Lampa, Depok) are characterised by short high peaks, while downstream peaks are characterized by long low peaks. - The local rainfall between Depok and Manggarai will increase discharge at Manggarai. Roughly 1/3 of the total Ciliwung catchment is situated downstream Depok.

Taking all aspects into consideration, it is expected that discharges at Manggarai on the morning of January 17th could have been in the order of 300-400 m3/s. Further analysis with the FHM-framework fed by the BBPT rainfall radar could be done to verify this number.

Deltares, HKV, PusAir , RHDHV 12

Jakarta Floods January 2013 1207961 April 2013 Main Report

Discharge at Depok

300 peak causing Discharge flood in city Depok

250

200 ) s / 3 m (

e

g 150 r a h c s i D 100

50

0 14-1-2013 15-1-2013 16-1-2013 17-1-2013 18-1-2013 19-1-2013 20-1-2013

Figure 17 – Estimated discharges at MT Haryono using two rating curves

2.4.2 Overtopping of the Banjir Kanal Barat Backed by model simulations, field observations (February 2nd 2013) and discussions with PU and DPU, the overtopping of BKB is prescribed to three factors:

- High upstream discharge at the Ciliwung and Krukut - High backwaters from PA Karet, caused by subsidence of the gate and a large accumulation of trash. Subsidence of the gate causes a high contraction of through flow and corresponding high reductions of flow capacity (estimated up to 50%). Trash also blocks flow through the gate. - Poor construction and maintenance of parapets at the BKB embankment. It does not seem that these parapets can withstand a lot of pressure (increased at overtopping).

The maximum flow capacity through the BKB is estimated on 400m3/s based on model simulations, assuming 300m3/s from the Ciliwung and 100 m3/s from the Krukut. Discharges higher than these figures, will cause problems. If Karet and Manggarai are functioning properly (not obstructing the flow), the bottle-neck of the BKB should be downstream of Karet. See Figure 19 for underpinning of these numbers.

Deltares, HKV, PusAir , RHDHV 13

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 18 – Karet at February 2nd 2013

Figure 19 – BKB water levels with a proper functioning Karet and Manggarai gate (m = 0.03)

The function of Karet (and also Manggarai) should be reconsidered. What was the purpose of the gates during construction? Are these functions still present today? Can these functions also met in other ways?

The amount of trash in the Krukut and Manggarai is very high, obstructing flows and polluting the city and marine environment. Proper trash collecting facilities should be

Deltares, HKV, PusAir , RHDHV 14

Jakarta Floods January 2013 1207961 April 2013 Main Report

provided at the Krukut and Ciliwung. At this moment, such facilities at Manggarai and Karet are insufficient.

Overflow BKB to Melati Polder

140 Low estimate Expected high High estimate 120

100 ) s / 3

m 80 (

e g r a h

c 60 s i D Expected high 40

20

0 0 0.1 0.2 0.3 0.4 0.5 0.6 Height over levee (m)

Figure 20 – Overtopping of BKB. Assumed free flow, a crest width of 76 meters and different flow conditions represented in a discharge coefficient of 1 (high estimate) and 0.6 (low estimate)

2.4.3 Inundation of Melati, Cideng and Pluit polders To understand the flooding of Pluit, a water balance is made of January 17th (January 17th 07:00 till January 18th 07:00) for the Melati, Cideng and Pluit polders, taking into account: - Rainfall volume over the Melati, Cideng and Pluit polders - Overtopping volume over the levee of the BKB - Pumped volume by Melati, Cideng and Pluit pumps

Rainfall is extracted from PU2 rainfall observations. The method to derive water volumes in Melati, Cideng and Pluit is described in Annex A. The rainfall map for January 17th is given in Figure 21. Average rainfall for all polders per day is given in Table 1.

Figure 21 shows, average rainfall over Pluit, Cideng and Melati. Figure 22 shows that the rainfall at the 17th was high (about 1:25 – 1:50 year rain event)

Overtopping of the BKB is assumed to by 100 m3. The period of overtopping is assumed to have been at least for the entire day (24h).

Melati pump is assumed to be functioning at full capacity (14 m3/s) for the entire day. From correspondence it is known that Cideng was not operational in the first hours of flooding due to power failure. Therefore it is assumed it was only pumping half of the day (12h) at full capacity 32.8 m3/s. Pluit was not functioning the 17th of January.

Deltares, HKV, PusAir , RHDHV 15

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 21 – Rainfall January 17th 2013

250

KATULAMPA 200 DEPOK MANGGARAI Estimate 1:25 – 1:50 event KARET SETIABUDI TIMUR MELATI 150 ISTANA KRUKUT HULU SUNTER HULU PESANGGRAHAN ANGKE HULU 100 TANJUNGAN TOMANG BARAT TELUK GONG PULO GADUNG KODAMAR 50 RAWA BADAK CIDENG

0 January 10 January 11 January 12 January 13 January 14 January 15 January 16 January 17 January 18

Figure 22, Rainfall mm/24 hours (from 6am-6am) from January 10 – 18, 2013

Deltares, HKV, PusAir , RHDHV 16

Jakarta Floods January 2013 1207961 April 2013 Main Report

Table 1 – Average rainfall (mm/day) in Pluit, Cideng and Melati Date Pluit Cideng Melati 10-1-2013 21 16 9 11-1-2013 0 0 0 12-1-2013 49 42 34 13-1-2013 31 25 20 14-1-2013 50 50 54 15-1-2013 45 43 42 16-1-2013 62 43 39 17-1-2013 173 164 153 18-1-2013 7 5 3

The Total inundation volume of Pluit (19-20 January) is estimated as described in Annex B. This volume is assumed to be 12.6 Mm3 (12600000 m3).

Table 2 shows the water balance of Pluit of January 17th. The table shows (given all assumptions!) around half of the inflow in the Pluit system is caused by overtopping of the BKB. From this amount of volume only 18% could be pumped out by Cideng and Melati pumps.

The surplus on the water balance corresponds reasonably well with the inundation volume in Pluit January 19th- January 20th. Therefore, it is likely that the inundation of Pluit is caused by the deficit on the water balance of the Melati, Cideng and Pluit system of January 7th, which is caused by a combination of very extreme local rainfall and overtopping of the BKB.

Table 2 – Water balance of Pluit (January 17th 2013) Rainfall 17-01 6.1 Mm3 3 Inflow Overtopping BKB 8.6 Mm Total 14.8 Mm3

Cideng 1.4 Mm3 Melati 1.2 Mm3 Outflow 3 Pluit 0.0 Mm Total 2.6 Mm3

Balance 17-01 12.1 Mm3

3 Total flood volume Pluit 12.6 Mm

Deltares, HKV, PusAir , RHDHV 17

Jakarta Floods January 2013 1207961 April 2013 Main Report

3 Identification of Urgent Flood Measures

3.1 Identification of measures

The first high waters end of December 2012 and the severe floods mid-January 2013 triggered a wide range of suggestions to mitigate the floods. Most of these measures have been earlier studied during the earlier FHM (Flood Hazard Mapping) projects during 2007-2009, but also some new measures have been suggested. After the January floods the Government wanted to take immediate action and requested urgent assistance to be able to properly discuss and prioritize proposed measures with all stakeholders involved and to be able to quickly formulate the ToR’s for the selected works. In particular assistance was requested to:

x Assist the design teams of PU and BBCilCis with the hydraulic dimensions and characteristics to connect the Ciliwung with BKT: ‘The Ciliwung – BKT diversion’ x Follow the activities of the ‘Multipurpose deep tunnel’ design team, to enable better understanding (based on earlier FHM deep tunnel analysis) and good comparison between the effectiveness of the Ciliwung – BKT diversion and the Multipurpose deep tunnel x Evaluate and understand the flooding of the Pluit polder to assist preparation by flood and disaster services to avoid similar problems during expected February and March storm events

During the recent Flood Management Information Management (FMIS) project (2012) also new ‘quick win’ flood measures have been proposes, including:

x Closure of Kali Muara Karang in combination with a redirection of the drainage flows from the Lower Grogol and the Tobagus Angke and Jelembar Polders to both the Lower Anke and BKB x Optimization of the polder connections to improve drainage flows and to optimize pumping

3.2 Diverting flow from the Ciliwung

The evaluation of the January 2013 floods clearly showed that diversion of water from the Ciliwung away from BKB to other systems would most probably had prevented the floods. A very effective diversion between the Ciliwung and the newly built BKT was identified for the first time during the FHM project in 2007: the Ciliwung – BKT diversion. Another potentially effective diversion was identified in the 90s: the Katu Lampa – Cisadane diversion.

Figure 23 gives an indication of the location of both the Ciliwung – BKT and Katu Lampa – Cisadane diversions in the Jakarta catchment area. When both diversions would be implemented up to at least 400 m3/s can be diverted away from the Ciliwung before the peak flows reach BKB, which will very significantly reduce the chance on flooding in the downstream Ciliwung – BKB system, effectively improving the safety of people and properties.

Deltares, HKV, PusAir , RHDHV 18

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 23, Effective Ciliwung diversion to BKT and Cisadane

3.2.1 Ciliwung – BKT diversion Figure 24 shows part of the no regret measures proposed by FHM in 2007, including the implementation of the East Banjir Channel (EBC or BKT) in combination with a connection to BKT from Ciliwung. To allow for this connection the capacity of Cipinang – Sunter BKT stretch had to be enlarged, to allow not only the high flows from the Cipinang, but also from the Ciliwung. During the construction of BKT it was decided to follow the advice of FHM to increase the capacity of the Cipinang – Sunter stretch to allow for a possible future connection from Ciliwung. The BKT was completed in 2010 and is very effective in reducing the floods in the eastern parts of Jakarta.

Deltares, HKV, PusAir , RHDHV 19

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 24, Proposed 'no regret' measures, FHM 2007 Due to the different hydrological characteristics of the Ciliwung and BKT catchments, it can be shown that during high flow conditions on the Ciliwung, nearly always BKT is capable to receive considerable flows from the Ciliwung. Also during the January 2013 floods, the BKT system was virtually empty and most probably the floods would have been prevented with the diversion from Ciliwung to BKT. For that reason the Government decided to immediately start the preparation by re-evaluation of the hydraulics for the diversion.

In chapter 3.3 the evaluation and effectiveness of the Ciliwung – BKT diversion is presented. It clearly shows that the diversion would bring great relieve to the BKT system without compromising the drainage task of BKT. The construction of the diversion would immediate optimize the investments of the BKT.

3.2.2 New flood strategy for the Ciliwung – BKB system With the diversion also the flood strategy can/should be optimized and changed. So far, the flood strategy included the further widening of BKB to allow more flood waters from the Ciliwung to pass through the inner city. However, BKB is a very old channel, with many bottlenecks located in the dense urban areas of Jakarta. It is very difficult to keep BKB safe as was shown by the revetment collapse during January 2013. By including the BKT in the flood management strategy of the Ciliwung – BKB system, immediately the safety levels increase, as BKT is a brand new channel, flowing around the urban areas for most part and enough space along BKT is available and already reserved to allow for future capacity increase of BKT. It is therefore proposed to change the current flood strategy to:

x Minimize the flow to BKB (instead of maximize the flow to BKB)

Deltares, HKV, PusAir , RHDHV 20

Jakarta Floods January 2013 1207961 April 2013 Main Report

x Optimize the flow to BKT

An ‘Equal BKB-BKT distribution’ principle is therefore proposed for the future flood management strategy.

3.2.3 Katu Lampa – Cisadane diversion With the implementation of the Jakarta Flood Early Warning System (JFEWS) also another possibility to divert water from the Ciliwung: from Kata Lampa – to the Cisadane. This connection was earlier proposed in the 90s, but could not be implemented because of increased risk on flooding in Tanggerang. The Katu Lampa – Cisadane diversion requires a flood prediction and operational management to avoid increase of flood hazards in Tanggerang. With the implementation of JFEWS such an operational system comes available to properly manage the Katu Lampa – Cisadane connection.

The location and characteristics of the Katu Lampa – Cisadane connection is presented in chapter 3.4. A detailed design of the Katu Lampa – Cisadane diversion has already been made, but it is advised to reconsider the detailed design as a better alignment seems to be available with the entrance closer to Katu Lampa, which makes the operation of the diversion easier and more effective.

3.3 Ciliwung-BKT diversion

3.3.1 Introduction The main reason to divert water from the Ciliwung to the Banjir Kanal Timur (BKT) is that discharges higher than 400m3/s on the Banjir Kanal Barat (BKB) can be considered unsafe. This statement is supported by the fact that the BKB overtopped January 2013 with upstream discharges of 300-400 m3/s. Model simulations show that with a proper functioning Manggarai and Karet gate discharges of >400 m3/s will limit the freeboard downstream of Karet gate to 40cm (see Figure 25). It must be noted that an assumption of 400 m3/s as maximum discharge depends on assumptions of bed friction (m=0.03), downstream water levels (MSL=1.2m). Taken into account uncertainties, 400m3/s is considered to be a “likely assumption” for the maximum discharge on the BKB with an uncertainty of +/- 100 m3/s.

Since a discharge of 400 m3/s or higher occurred in 2007 as well as in 2013, access water needs to be diverted elsewhere. A diversion option is to discharge excess water to the Banjir Kanal Timur (BKT).

Deltares, HKV, PusAir , RHDHV 21

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 25 – Water levels at the Banjir Kanal Barat (BKB) under 390 m3/s discharge at the Ciliwung and Krukut

From January 21st 2013 onward, Deltares is assisting PU with the analysis of four alternatives (see Figure 26): 1. Alternative BBWSCC: Connects Ciliwung at Otista tiga, underpasses Kali Baru Timur and Cipinang and connects to the Banjir Kanal Timur (BKT) downstream the dropstructure at the Cipinang 2. Alternative Otista tiga (OT3): Connects to the Ciliwung at the same location as alternative BBWSCC. However, it connects directly to the Cipinang, shortening the trajectory with +/- 1km, but making it necessary to replace the Cipinang drop structure. 3. Alternative Casablanca: Connects to the Ciliwung at Jl Casablanca. It connects to the BKT at the same location as alternative BBWSCC. Jl Casablanca also overpasses the water supply line to Pejompongan. 4. Alternative Tarum Kanal Barat (TKB). It connects the Ciliwung and BKT at the Tarum Kanal Barat.

Deltares, HKV, PusAir , RHDHV 22

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 26 – Alternatives BBWSCC (up left), Otista tiga (up right), Casablanca (down left), Tarum Kanal Barat (down right)

3.3.2 Improvements required at the BKT and Cipinang Depending on the alternative improvements are necessary or suggested to the Banjir Kanal Barat (BKT), see Figure 27: - BKT improvement: For a stretch of +/- 1km the canal should be deepened with +/- 1 meter. This is only suggested for alternatives all alternatives and only when significant bypass discharges are reached (>50m3/s) - Removal of drop structure. If the diversion diverts from the Ciliwung to the Cipinang, the drop structure at the connection between the Cipinang and BKT should be removed. Note: the removal of the drop structure possibly requires an extra gate downstream of the lower Cipinang confluence if BKT water is used to flush the lower Cipinang. Removing the drop structure is required for alternatives OT3 and TKB - Cipinang improvements. For alternatives OT3 and TKB the Cipinang should also be improved until the outlet of the diversion. Upstream the slope of the Cipinang should be gradually changed to meet bed levels, or a weir can be constructed similarly to present currently at the drop structure. For all alternatives a side-spill is purposed at the Ciliwung. From the formula of submerged weir flow, the discharge can be calculated (see eq1). If the width of the side spill is 50 meters, the loss over the structure will be only 0.1 in most extreme cases. Such losses are acceptable. 1/2

QccWhh ewsupcrst˜˜˜˜˜˜ 2 ghh dwnup (eq1) with: Q = discharge (m3/s) ce, cw = loss and contraction coefficients (both assumed 1) Ws = width (m) hup,hdwn,hcrst = upstream, downstream and crest width elevation (m) g = gravity coefficient (9.81 m/s2)

The crest level of the inlet structure should be constructed at a safe level. The current perception of such a level is a Q5. However, at Q5, the floodplain of the Ciliwung is already flooded.

Weir 1 drop Cipinang

BKT

Outlet Proposed Outlet Outlet BBWSCC and

Figure 27 – Modifications BKT required for different alternatives

Deltares, HKV, PusAir , RHDHV 23

Jakarta Floods January 2013 1207961 April 2013 Main Report

3.3.3 Diversion capacities To divert water, three strategies have been discussed: - Open cut; an open canal between the Ciliwung and BKT. Early studies (JFM1) already have shown that capacity of such a diversion is easily sufficient. Further analysis has not been conducted at this point, since space for constructing such diversion is generally considered too limited - Tunnelling; an underground tunnel between Ciliwung and BKT. Depending the diameter required, the tunnel has to be dug several meters to 30 meters below the surface. Therefore it will always function as a siphon. Neglecting negative aspects such as sedimentation and captivation of air and trash inside the tunnel, a sufficient discharge capacity requires pipe diameters of (roughly) 2x6meters or 1x8 meters in diameter (see Figure 28). - Box culverts; a concrete culvert placed in segments directly below the street surface. Such diversion will function similar to an open cut, until the water levels in the Ciliwung and BKT are higher than the top of the culverts. When water levels at Ciliwung and BKT are higher than the top of the culverts, the capacity is similar to that of a siphon. Assuming culvert diameters of 5X6 (width X height), two till three box culverts are required depending on the trajectory (see Table 3).

Maximum tunnel discharge capacity under T=100 design Under current situation Ciliwung 300 Capacity (BBWSCC alternative) Capacity (Otista Tiga alternative) 250 ) s / 3 200 m (

y t i c a p

a 150 c

e g r a h

c 100 s i D Parameters: 50 Head difference: 3 Inlet loss coefficient: 1 Outlet loss coefficient: 1 Bend loss coefficient: 2 0 0 1 2 3 4 5 6 7 8 9 10 Diameter (meter)

Figure 28 – Discharge versus diameter for different alternatives

Table 3 – discharge capacity (m3/s) of tunnel diversions using box culverts under T=100 design. 1 Culvert is 5X6 meters. 1 culvert 2 culverts 3 culverts BBWSCC 70 140 210 OT3 77 153 230 TKB 79 158 237 Casablanca 64 129 193

Deltares, HKV, PusAir , RHDHV 24

Jakarta Floods January 2013 1207961 April 2013 Main Report

The nature of the Ciliwung water system, high sedimentation rates and trash accumulation, limit the possibilities of constructing diversions with siphons. Discharges plotted in Figure 26 are based on the assumption that there are no obstructions in the siphon. Siphons are very sensitive to obstructions by captivation of air, accumulation of sediments and accumulation of trash.

3.3.4 Effect of diversions on Ciliwung and Banjir Kanal Timur water levels To significantly reduce the water levels at the Ciliwung a diversion with a capacity of >150m3/s should be constructed. To underpin this number, system behaviour has been analyzed using two eventas: - The T100 design event. In this event, rainfall occurs in the entire catchment at the same time. Figure 29 shows the relation between rainfall, peak discharge at the Ciliwung at MT Haryono (just upstream of the diversion inlets) and the BKT. - The 2007 event. This event represents the rainfall which led to the flooding of Jakarta city in February 2007. This event is characterised by high rainfall intensities in the city prior to extreme rainfall in the upper Ciliwung catchment.

Figure 29 – Relation between rainfall and discharge peaks on the Ciliwung and BKT

Effects on maximum water levels at the Ciliwung under T=100 design conditions, are given in Figure 30. Analysis shows that for this particular event, the water level of the Ciliwung drops with more than a meter when >140 m3/s is diverted from the Ciliwung to the BKT.

Effects of the diversion on maximum water levels on the Ciliwung are less, but in the same order of magnitude, as shown in Figure 31. However, when maximum water levels are compared with the canal embankment, it is clear that BKT capacity is sufficient to handle the amount of discharge diverted in this particular event.

Deltares, HKV, PusAir , RHDHV 25

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 30 – Effect diversions on water levels of the Ciliwung (T=100)

Figure 31 – Effect diversion on water levels on the Banjir Kanal Timur (BKT) (=100)

In Figure 32 the effect of a diversion at Casablanca with three box culverts is plotted. It must be noted that such diversion will divert around 200 m 3/s in a T=100 case, such diversion will discharge +/- 195 m3/s. Figure 32 shows that effects are significant, +/- 1.75m upstream Manggarai and +/- 1.5m downstream Manggarai.

Figure 33 shows the effect on water levels of the BKT for the same event. Effects on maximum water levels on the BKT are zero, since discharge trough the diversion under peak discharge conditions in the BKT is zero.

Deltares, HKV, PusAir , RHDHV 26

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 32 – Effect diversions on water levels of the Ciliwung (2007 event)

Figure 33 – Effect diversion on water levels on the Banjir Kanal Timur (BKT) (2007 event)

The effects on the Ciliwung and BKT discharges are shown in Figure 34 and Figure 35. Peak discharge trough the Cilwiung lasts for a period of 2-3 days. Even before the peaks are reached water is diverted to the BKT. The first peak of the Ciliwung coincides with a peak on the BKT, which reduces the discharge to the diversion to zero. Therefore, the peak discharge and corresponding water levels at the BKT are determined by discharge to the BKT from its tributary rivers only. After the discharge peak at the BKT, with a duration of a few hours, has passed, sufficient capacity is available to reduce the rest of the discharge peak at the Ciliwung.

Deltares, HKV, PusAir , RHDHV 27

Jakarta Floods January 2013 1207961 April 2013 Main Report

Discharge distribution Ciliwung at diversion outlet (2007 simulation)

460 440 420 400 380 360 340 320 300 )

s 280 / ³

m 260 (

e 240 g r

a 220 h c s

i 200

D 180 160 140 120 100 80 60 40 20 0 26-1-2007 28-1-2007 30-1-2007 1-2-2007 3-2-2007 5-2-2007 7-2-2007 9-2-2007

Ciliwung discharge us diversion Ciliwung discharge ds divesion Diversion Discharge

Figure 34 – Discharge distribution on Ciliwung (2007 event)

Discharge distribution BKT at diversion outlet (2007 simulation) 380 360 340 320 300 280 260 240 ) s

/ 220 3 m (

200 e g

r 180 a h

c 160 s i

D 140 120 100 80 60 40 20 0

26-1-2007 28-1-2007 30-1-2007 1-2-2007 3-2-2007 5-2-2007 7-2-2007 9-2-2007

BKT discharge (downstream inlet) Cipinang discharge (upstream inlet) Diversion Discharge

Figure 35 – Discharge distribution BKT (2007 event)

From analysis the conclusion is drawn (based on available data), that diverting water from the Ciliwung to the BKT must be possible in most cases. Discharge waves at the Ciliwung near the possible locations for inlets are diffusive. In extreme cases multiple rainfall events build up one discharge peak which causes high water levels for multiple days. This is caused by the relatively long travel time of a wave trough the Ciliwung. At the BKT, travel times are significantly less, in the order of a few hours. In between discharge peaks at the BKT a large capacity is available to discharge excess water from the Ciliwung.

3.3.5 Towards “equal distribution” Based on the alternative trajectories and discharge capacities of different diversion strategies, a concept for redistribution is defined henceforward referred to as “equal distribution”. Figure 36 shows how water redistributes when the Casablanca alternative in combination with three box culverts is constructed. In this fictive design event, water

Deltares, HKV, PusAir , RHDHV 28

Jakarta Floods January 2013 1207961 April 2013 Main Report

from the Ciliwung is about equally redistributed over the Banjir Kanal Barat and Banjir Kanal Timur.

Redistribution gives flexibility. If discharge at the Ciliwung is low and discharge at the BKT is high, a significant amount (around 50% until 400 m3/s upstream MT Haryono is reached) can be diverted from the Ciliwung to the BKT. If peak discharges at the BKT is high, the diversion volume can be limited. As explained in section 3.3.4, it is likely that such occurrence only takes place during a limited amount of time.

Figure 36 – Equal distribution concept using Casablanca and three box-culverts (T=100 event).

3.3.6 Prefer ability of alternative

Table 4 shows different aspects for every alternative. The value in every cell indicates how this aspect can be met under the given alternative, the colour indicates its prefer ability, scaled green till red from preferable till non-preferable. - Achievable capacity: Indicates how much water can be diverted from every alternative under the diversion strategy. Only for Casablanca a box culvert strategy has been discussed and seems achievable. For all other alternatives tunnelling is assumed to be the diversion strategy. - Length: Length of the diversion - Type of tunnelling: Indicating which tunnelling strategy seems to be possible. - Deepening of BKT: Indicating the length over which the BKT has to be deepened (see Figure 27) - Improvement of Cipinang: Indicating the length over which the Cipinang has to bee improved (see Figure 27) - Removal of weir at Cipinang: Indicating if weir at Cipinang, the drop structure which connects the Cipinang to the BKT, has to be removed (see Figure 27) - Constructing flushing gate at BKT: Indicating if a new flushing gate has to be constructed at the BKT. This gate is necessary if water should be diverted to the lower Cipinang in the dry season and the weir at the Cipinang is removed. Note: at the moment no water is diverted to the lower Cipinang. Before a diversion gate is constructed the necessity of flushing of the lower Cipinang should be discussed

Deltares, HKV, PusAir , RHDHV 29

Jakarta Floods January 2013 1207961 April 2013 Main Report

- Inlet structure at Ciliwung: The structure at the Ciliwung (side spill) which allows water to flow from the Ciliwung to the diversion - Inlet gate at Ciliwung: gate at the inlet structure at Ciliwung, which allows a closure of the diversion for maintenance purposes and in case diversion is undesired - Outlet structure at BKT/Cipinang: structure at the BKT which connects the diversion to the BKT.

Table 4 – Different aspects (“features”) per alternative

Based the analysis in this report, in our point of view the Casablanca alternative should be the preferable alternative. Main reason is the type of tunnelling deemed possible and the fact that no modifications to the Cipinang river profile are necessary. Feasibility of this alternative should be studied further on (at least) the following aspects: - Mapping of conflicts with the Casablanca diversion and existing “underground” infrastructure, such as electricity lines, water pipes, etc. - Traffic impacts of constructing box culverts under jl. Casablanca - Further detailing of the diversion itself, including detailed design of the inlet structure, gate and outlet structure

3.4 Katu Lampa – Cisadane diversion

With the implementation of the Jakarta Flood Early Warning System (JFEWS) also another possibility to divert water from the Ciliwung: from Kata Lampa – to the Cisadane. This connection was earlier proposed in the 90s, but could not be implemented because of increased risk on flooding in Tanggerang. The Katu Lampa – Cisadane diversion requires a flood prediction and operational management to avoid increase of flood hazards in Tanggerang. With the implementation of JFEWS such an operational system comes available to properly manage the Katu Lampa – Cisadane connection.

A detailed design of the Katu Lampa – Cisadane diversion has already been made, but it is advised to reconsider the detailed design as a better alignment seems to be available with the entrance closer to Katu Lampa, which makes the operation of the diversion easier and more effective.

The new alignment is shown in Figure 37 - Figure 39. The length of the diversion is approximately 3 km and the level difference between entrance and outflow point over 50 m, which provides easy diversion of at least 200 m3/s, which is a significant

Deltares, HKV, PusAir , RHDHV 30

Jakarta Floods January 2013 1207961 April 2013 Main Report

reduction of the peak-flows from Katu Lampa. As can be seen from Figure 40 the diversion requires a bored tunnel, which is similar to the earlier designs from the 90s. But where for the Ciliwung – BKT soft soil ground works are required, the Katu Lampa – Cisadane diversions is located on hard rock.

Figure 37, Proposed alignment for the Katu Lampa - Cisadane diversion

Figure 38, Proposed entrance for the Katu Lampa - Cisadane diversion

Deltares, HKV, PusAir , RHDHV 31

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 39, Proposed outflow point for the Katu Lampa - Cisadane diversion

Figure 40, 3D - view of the Katu Lampa - Cisadane diversion

Deltares, HKV, PusAir , RHDHV 32

Jakarta Floods January 2013 1207961 April 2013 Main Report

4 Flood information at BNPB and BPBD Jakarta

4.1 Pusdalops at Badan Penanggulangan Bencana Daerah (BPBD)1 As BNPB as well as the BPBD, the Pusdalops (Emergency Operation Room) is at the heart of the flood information of disaster management operations. Besides the Pusdalops, BPBD staff is kept up-to-date via information and coordination meetings with the various stakeholders in flood management. The standard procedure in non- emergency situations in the Pusdalops of BPBD: - A radio operator listens to the radio for the water level information - Next they manually insert the water level information into an SMS gateway software. The software produces a graph and a table that they view on a TV screen at the door of the Pusdalops. With regular intervals depending on the Siaga level, they send out automated message to recipients. The SMS gateway was installed by a freelance developer named Pak Agus (www.agusaryanto.net) some time ago. The software is not being sustained (there is no maintenance contract with Pak Agus or someone else) and is known to have flaws (not reaching people with the SMS they send out). - In the Pusdalops there is no information coming from PU directly, except for the FEWS Client that has been installed in the Pusdalops.

Figure 41 Pusdalops of BPBD

According to Pak Edy and Fahzi, their radio and SMS system worked fine during the January flood. The FEWS system has been very beneficial for the BPBD but unfortunately was offline during the disaster. As the disaster was scaled up to national level (17 Januari) the BPBD moved the Pusdalops to the Ruang Pola. In effect that meant that the radio connection for water levels was done now at the Ruang Pola as

1 Source: Pak Edy (BPBD, Kepala Bidang Informatika dan Pengendalian), Pak Fahzi (BPBD, Pusdalops)

Deltares, HKV, PusAir , RHDHV 33

Jakarta Floods January 2013 1207961 April 2013 Main Report

well as the Pusdalops on the third floor. The Ruang Pola during the floods was equipped with: - Posko Banjir: Receiving water levels by radio, noted on a white board - Call Centre: Exchange of information outside the Ruang Pola a) Outgoing calls: Provide information on the situation to volunteers, among which water level information and b) Incoming calls: Volunteers and citizens call 164 to report about the situation. The centre then uploads the information via Lapor! to www.lapor.ukp.go.id. Lapor is a government web service that connects citizen reports to the government via a website. Citizens mainly requested for evacuation. - Main screen in the Ruang Pola: The screen can handle one information source. The BPBD decided to display the Lapor website to show citizens’ concerns. - Meeting table

Figure 42 Posko Banjir, Ruang Pola, DKI Jakarta

A simplified communication overview for flood disaster management between government agencies is given below. Take note that the Pusdalops is part of the BPBD and BNPB, taking a central position in the dissemination of flood information.

Deltares, HKV, PusAir , RHDHV 34

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 43 Communication during January Flood Disaster

4.2 Pusdalops at Badan Nasional Penanggulangan Bencana (BNPB)2 As with BPBD, the Pusdalops takes a central position in the communication about floods. Besides the information in the Pusdalops, when a disaster is considered a national disaster they coordinate assistance to the disaster area in information and coordination meetings. On floods, the standard procedure at the BNPB Pusdalops is that they monitor the water levels by listening to the radio and write that down on a white board. From PU they do not receive any information, except for the FEWS Client that is installed in the Pusdalops.

During the disaster of January 2013, the function of the Pusdalops as data hub did not work well says BNPB. All 14 Pusdalops personnel were working at the Wilayah for coordination and logistics, leaving the emergency control room empty. As emergency measure, BNPB bought 14 Blackberry’s to be able to communicate, but there was no central data hub with a clear overview of the situation. About the FEWS system they explained that they are very happy with it, but regretted that the application could not be used for considerate periods of time. Also they reported they did not know what to look at. On 18 January the FMIS team helped BNPB to open the correct windows of FEWS. BNPB chaired the various information and coordination meetings between BNPB, BPBD and other disaster managers.

4.3 Information and coordination meetings The second way in which information is exchanged is via information and coordination meetings with the BNPB, BPBD, PU and other disaster managers. In these meetings the situation is discussed and actions and task division are agreed upon. For the January flood, the BNPB chaired the meeting, as it was considered a national disaster.

As situation report, the disaster managers used a flood map created by Worldbank and AIFDR, on the basis of various reports from Walikota (coming in per SMS at the BPBD

2 Source: Noel Pitoy, ICT Interoperability Officer, AIFDR

Deltares, HKV, PusAir , RHDHV 35

Jakarta Floods January 2013 1207961 April 2013 Main Report

Pusdalops), citizen and media. They combined this flood map with InaSafe software to get a picture of the damage and affected people. After the meeting, the task holders stayed in contact with each other via the mobile phone or in person.

Figure 44 Provisional flood map shown during coordination meeting of disaster management organisations

4.4 Problems identified by BPBD, BNPB The largest problem in the flood mitigation says the BPBD, was that they did not have an overview of the disaster (extent, damage, casualties, displaced, vulnerables etc.): - The flood map they used from AIFDR, Worldbank was important, however only 60% correct as they found out later. In fact it took them nine or ten days (after start of the floods) to get the complete overview of the disaster. - The information that heads of districts receive is often not correct. Sometimes they let know that they do not need any assistance so the BPBD sends their resources elsewhere. But the next day it turns out they receives false information and they actually do need logistical support.

BNPBs main concerns had been that they do not have any flood information available except for radio water levels in the Pusdalops. Just like BPBD, they had no overview of the disaster as it unfolded. The Pusdalops did not function as information hub, for lack of good information and for lack of resources to disseminate the information. After each meeting, BNPB laid down new functional requirements for the system, as described in Appendix B.

On this basis, we designed the IT architecture for a national FMIS as well as developed FMIS quick wins for Jakarta, as described in the next two sections.

Deltares, HKV, PusAir , RHDHV 36

Jakarta Floods January 2013 1207961 April 2013 Main Report

5 National FMIS for Disaster Management

5.1 Background The FMIS system has been discussed with the disaster management organisations during a number of meetings and visits. Beyond Jakarta, their wish is to have such a system on national scale. To anticipate on this, in this Emergency Project for Jakarta we set-up the IT-architecture in such a way that it can be extended nationally. This section discusses the components of such a national FMIS system for disaster management. The next section discusses what parts have been developed for Jakarta in the past few months.

5.2 FMIS architecture In FMIS we use web-technology to organise the information exchange. The web- technology that we use consists of three components: - Webserver: Data import, data storage and server tasks - Web services: Communication between the webserver and client applications - Client applications: Interface for users of the webserver

Webserver

Webservices

Client applications

Figure 45 Information exchange and the use of web-ICT

Public Works (PusAir) is currently using the FEWS controller for server tasks and web services and a FEWS Client as a Client application, to interface with the user. BNPB and BPBD do not yet have such a structured approach to flood information yet, but can take advantage of the already made architecture of Public Works. In the next figure we illustrate how the software for the disaster management organisations relates to the software of PU:

Deltares, HKV, PusAir , RHDHV 37

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 46 Relation between Public Works and the BNPB

For the disaster management organisations, this translates to the following systems’ overview:

Figure 47 Architecture of FMIS for the disaster management organizations

In words: The information from the dedicated PU webserver will be transferred to a dedicated webserver for the disaster management organisations. This is done to improve the robustness of the system in case of an internet failure. Furthermore, besides data from the dedicated PU webserver the dedicated webserver for the disaster

Deltares, HKV, PusAir , RHDHV 38

Jakarta Floods January 2013 1207961 April 2013 Main Report

management organisations is also retrieving information from other sources. By downloading the information from the PU dedicated webserver onto the webserver for the disaster management organisations, all data is centralized. Client applications communicate with the webserver via one or more web services. At the preference of the Client, the web service can connect also to other Client webservers. The communication will be arranged via a secure connection for registered users, as not all flood information data is public data. The restrictions are managed from a control panel. Clients using a secure connection to the web service cannot be monitored by any third party, which guarantees that only the intended client reads the information. Besides security, the system will be able to guarantee a certain amount of robustness. Robustness depends on the used hardware/software and on the amount and strength of redundant paths.

Hereunder we explain the individual components of the FMIS architecture: - Client applications - Web services - Webserver

5.3 Client applications The set-up of FMIS supports the following functionalities, combined in one or more Client applications: - Customized visualisation of FMIS information for control room, desktop, tablet, smartphone and mobile phone, with adequate interface to switch information - Supports data entry by SMS or other web-apps - Supports crowd sourcing functions - Supports internal communication - Produces impuls upon exceedance of thresholds - Support downloads and onwards communication of FMIS information - Supports registration and access management by an information manager

5.3.1 Customized Dashboard of FMIS information Any type of information can be visualised customized to viewers’ preferences.

In the emergency project we realised two of these Dashboards, the “Planar Screen” and “Water Levels on the Map” for BNPB. You can find these views on www.banjironline.co.id.

Figure 48 Planar screen for BNPB

Deltares, HKV, PusAir , RHDHV 39

Jakarta Floods January 2013 1207961 April 2013 Main Report

5.3.2 Supports crowd sourcing functions News via social media are usually the first monitors of disasters. The FMIS system can receive and store crowd sourced information.

In the emergency project we embedded the HKV twitter web application in the Planar Screen for BNPB.

5.3.3 Supports data entry by SMS or other web-apps At times of disasters, there is heavy telephone and SMS traffic between flood and disaster managers. The system can receive information via SMS and other web-apps, organise and store the information and use it in other processes (e.g. display the information through a Dashboard).

In the emergency project we set-up a pilot for BPBD, to store and display SMSs from the Paks Lurah, through BPBD SMS gateway.

5.3.4 Supports internal communication To facilitate the information flow, FMIS supports Instant Messaging. Via Instant Messaging, officials and volunteers can txt their say, while the FMIS system registers where the senders are. On banjironline.co.id you will find an alpha version of Instant Messaging.

5.3.5 Produces impuls upon exceedance of thresholds When thresholds in the database are exceeded, for instance water levels or amounts of tweets, the system will give out an impuls.

In the emergency project, we set impulses for Siaga changes in the water levels as well as a legend to the Twitter application. The Siaga change impulses cause 1. Lighting up of the Planar screen and 2. Voice calling name and siaga of the concerning station.

5.3.6 Support downloads and onwards communication of FMIS information Usually, FMIS information is passed on from the source (web application) to other applications and devices. The FMIS supports downloads of selected information to pdf and xls. and supports onward communication of selected information by SMS and fax.

5.3.7 Supports registration and access management by an information manager An information manager administrates the access to information for different users in an access management system.

5.4 Web services A web service arranges the communication between a webserver and a web application. The web service for a national FMIS should be available for Client applications at all times and generate the appropriate feedback. The set-up of FMIS supports: - Data request process - Communication process

5.4.1 Data request processes The web service handles requests for data. This includes processes to prepare the data (merging data ranges etc.). The web service returns: - Data ranges: Typically contain information about water levels or precipitation (both measured and forecasted), but can also contain different information. - Map layers: Can be overlain over a (2D) spatial map

Deltares, HKV, PusAir , RHDHV 40

Jakarta Floods January 2013 1207961 April 2013 Main Report

- Images: Not necessarily static, they can also be represented by animated images like GIF files, videos and live streams.

The client application can add some extra parameters to the request to get more specific data.

5.4.2 Communication processes The web service handle requests for internal and external communication, according to a set of international standards. The web service accepts incoming traffic, supports outgoing traffic and supports internal communication between Client applications.

5.5 Webserver The webserver retrieves the information from data sources and runs server tasks. Data will come from Public Works, but Disaster Management will also have other data sources such as twitter. The webserver makes sure that the gathered information is reliable and up-to-date.

5.5.1 Data gathering processes There are at least five ways that the webserver can load data: - FEWS process: The webserver can import a special FEWS format called “FEWS PI.” This XML based file can contain all information that is available within the FEWS system. - FTP process: The Webserver can be connected to an FTP box via (S)FTP. Generally, data coming from FEWS will be put in such an FTP box for others to use. Besides the one of FEWS, the Webserver can also connect to other FTP boxes for data retrieval. - API process: Some companies nowadays create Application Programming Interfaces (APIs) for other developers to communicate with their system. For instance Twitter has set up an API so that developers can get tweets from their servers. The Webserver is able to connect to these APIs to download additional data. - User data input process: Sometimes it is useful to let the user input data himself. For instance, when all connection from a web application to the client webserver fails, but the user still receives information via other means (e.g. radio connection), the user can choose to input this data directly onto the webserver so that the web application is still useful and up-to-date. Another example is the connection to a mobile application that can be used in the field during a flood. The mobile can send data via the web or SMS. - External website process: The webserver can also be configured to retrieve information from other websites.

5.5.2 Other server tasks Besides loading and organising data, the webserver has server tasks, such as: - Information update process: Alert to Client applications when there is new data available. Every time after the Webserver retrieved new data, it sends out a signal to active Client applications. These Client applications then download the newest information automatically. - External program process: The Webserver can run external, third party programs. These programs can help to gather information (e.g. a FEWS client) or these programs can help sending out information (e.g. SMS gateway).

Deltares, HKV, PusAir , RHDHV 41

Jakarta Floods January 2013 1207961 April 2013 Main Report

6 Emergency Assistance Development

6.1 Customized visualization of FMIS information: On the basis of meetings with the BNPB and BPBD (see appendix B for the meeting minutes) we designed two applications: - Planar application: This application is running on the main screen in the control room of BNPB. It displays flood management information and can update itself automatically. This application is designed for low user interaction. - Water level map application: This application is made to show the user more location based water level information. The user can see all the locations of the water gates in Jakarta as well as the water level of the past week for each water gate. This application is designed for user interaction.

For improved robustness, both applications retrieve their information from multiple sources. The sequence prioritizes first published data, and is overwritten by data from the FEWS-server.

6.1.1 Planar Application The Planar application runs on the main screen in the control room of the BNPB. The application displays fourteen graphs, for each of the water stations of Jakarta in one window, together with two maps that indicate flooded areas on the basis of tweets (Twitter map) and show the precipitation of the past three hours (Rain Radar map). Sources used in this Application: - JFEWS: Used for both the current water levels and the precipitation map. - Jakarta government website: This website is used as a redundancy for the water level in case the FEWS fails. - Twitter: Used to count in which areas of Jakarta people tweet about floods.

The Application automatically selects the correct data source when there is a redundancy in sources. A ‘correct’ data source is defined as the most up-to-date resource.

The Planar Application has the following characteristics: - The header of each graph includes the name of the station, together with the maximum occurrence left from the name and the station’s alarm level right from the name. The font needs to be: arial, all caps, white and small. - Each graph flashes red for five times when an alarm level raises. - When an alarm level is on level II or higher, the box in which the alarm level is written keeps flashing red until the alarm level lowers below level II again. - The application gives out an audible alarm when an alarm level is exceeded. This alarm is the vocal representation of the station + exceeded level. - Each graph looks 24 hours in the past and 6 hours in the future. If there is no forecasted data available, the 6 hours in the future need to be empty. - The application updates itself when there is new information available. - The x-axis has an interval of two hours and only shows the hours on the labels. - The y-axis has an interval as small as possible, but maintains readability. - There is a small table on the side of every graph, indicating a past few most recent measured water levels. - The graphs is draggable so that the user can rearrange them. - All graphs are bound in a grid and cannot move freely. - The graphs are grouped per river/system. Each group has its own colour. - On the bottom of the graphs, there is a legend, linking the colours to the rivers/systems.

Deltares, HKV, PusAir , RHDHV 42

Jakarta Floods January 2013 1207961 April 2013 Main Report

- The background of the application is black so that it’s easier to see at night and in dark rooms. - There is no space between the boxes of the graphs. - One box is kept empty for future use.

Figure 49 Initial visualization of the requirements. The wind map was later replaced with a twitter map.

- The Twitter map and the Rain Radar map are connected with each other. When the user changes the view of one map, the view of the second map changes with it. - The Rain Radar map loops over the past three hours. Once the loop reaches its end the loop holds for a few seconds, showing the last image, before continuing to the beginning again. - The Rain Radar map has a legend, explaining the appearing colours. - Both the Twitter map and the Rain Radar map have a quiet and dark background to match it with the rest of the application. - Both maps have the administrative names on there.

6.1.2 Water Map Application The Water Map Application is a Map application with all the 14 water gates in Jakarta. These water gates are represented by water gauges to indicate its current alarm level. Once the user clicks on one of the gauges, a window pops up with a graph of all measured water levels of that particular water station of the past week. This application is designed to run on a desktop, where the user can easily interact with it. The data sources of the application are: - JFEWS: Used for both the current water levels and the precipitation map. - Jakarta government website: This website is used as a redundancy for the water level in case the FEWS fails.

The Application automatically selects the correct data source when there is a redundancy in sources. A ‘correct’ data source is defined as the most up-to-date resource.

For the Water Map Application, the following requirements were set up: - Each water gate is selectable by clicking on its location. - Once a water gate is selected, a window pops up showing a graph of the measured water levels at that point for the past week. - When the user hovers over a water station with his mouse, a tooltip appears to tell the user which water station it is. - The water gates are represented by gauges. These gauges correspond to the current alarm level of the water station.

Deltares, HKV, PusAir , RHDHV 43

Jakarta Floods January 2013 1207961 April 2013 Main Report

To support the Planar Application and the Water Map Application, we also created a “back-end”. This back-end is a Web service and Webserver in one to retrieve and give out information.

6.1.3 Web service The Web service required for these web applications use two data request processes as described in 5.4.1 - Water level process: This process returns a data range about water levels in Jakarta. To specify what data exactly is returned, some parameters have to be given upon request. Supported parameters are: a. Beginning of interval: From how long ago the range starts. b. End of interval: Until what time and date the range is. c. Location: Location of the water stations that is included in the data range. d. Rain indicator: Whether to include a textual representation of the weather at each station on each point in time. - Precipitation radar process: This process return Map layers about the precipitation around Jakarta over a certain interval. Just like the other two processes, this one also includes the use of parameters upon request: a. Beginning of interval: From how long ago the range starts. b. End of interval: Until what time and date the range is.

6.1.4 Webserver The Webserver that was created for this project uses all processes described in 5.5. The processes that were used to visualize FMIS information are: - FEWS process: The Webserver uses the FEWS process for water level information from JFEWS. - FTP process: This process is used to retrieve the precipitation information from an FTP box of JFEWS. - External website process: For the robustness of the system, water level information is also retrieved from a second source via this process. The Jakarta government gives out water level information via their official website and the Webserver can read and store them. - Information update process: Once the Webserver is finished with retrieving new information, it gives out a signal to all active client applications. These client applications then automatically download the newest information. - External program process: The Webserver runs a JFEWS client to get all the updated information from JFEWS.

6.2 Impulse upon exceedance of threshold The Planar Application supports the feature that it gives out an impulse when a certain threshold is exceeded. This is according to the following requirements of the Planar Application: - Each graph flashes red for five times when an alarm level raises. - When an alarm level is on level II or higher, the box in which the alarm level is written keeps flashing red until the alarm level lowers below level II again. - The application gives out an audible alarm when an alarm level is exceeded. This alarm is the vocal representation of the station + exceeded level.

Because the client application keeps updating itself, it knows when an alarm level is raised. Once the application notices that the alarm level is raised, the given requirements are activated.

6.3 Crowd sourcing from Twitter The Twitter application counts the amount of Tweets on floods and categorises them into one of the 267 Kelurahan in Jakarta. The web service has been developed by HKV.

Deltares, HKV, PusAir , RHDHV 44

Jakarta Floods January 2013 1207961 April 2013 Main Report

The output from this web service is shown on the Planar Application in the Twitter map. This map shows if and where people tweet about floods. All tweets about floods are saved to a server. The Twitter map on the Planar screen shows the following: - Each kelurahan is drawn separately on the map. - When the user hovers over one of the areas, a box appears with the name of the kelurahan in there. - When there is no flood in an area, the area is drawn yellow. - When a flood is happening in an area, the area will turn red.

6.3.1 Web service The web service required for this web application uses one data request processes as described in 5.4.1 - Twitter process: This process returns a data range concerning tweets from twitter. This process knows two types of ranges: ranges with actual tweet objects and ranges with “tweet counts”. A tweet count range is an array of kelurahans in Jakarta; each telling how many tweets were counted about a flood in this area in the last hour. Just like the water level process, this process also supports some parameters: a. Beginning of interval: From how long ago the range starts. b. End of interval: Until what time and date the range is. c. Counts: Whether to include actual tweets or only the tweet counts. d. Top: Whether to return all the kelurahans or only the top few areas (only for tweet counts). e. Maximum: Whether to include all the tweet counts or only the maximum occurrence of each kelurahan in the given interval (only for tweet counts).

6.3.2 Webserver The Webserver uses only one process to get information from Twitter: - API process: To get the flood related tweets from Twitter, the API process is used. The Webserver connects to the API of Twitter to get all the tweets.

6.4 Data entry by SMS for Flood map The BPBD is training its people to send text messages in case of a flood. These text messages contain flood information such as inundation depth, displaced persons and evacuation location. For HKV to be able to work with these text messages and make real-time flood maps, we first need to receive these text messages. To get text messages from the BPBD to a server of HKV, the two most robust options are: - BPBD expands their SMS Gateway software to store all data automatically in the databases of HKV. - HKV receive forwarded text messages from the BPBD.

6.4.1 BPBD expands their SMS Gateway At the moment, the BPBD already uses a system to send and receive text messages called a SMS gateway. They mostly use the SMS gateway to notify the heads of all the Kelurahan in Jakarta about the water levels in the water stations. However, they just started training these heads of all the Kelurahan to regularly send formatted text messages to the BPBD about inundation depth, displaced person and evacuation locations. Steps to realize this option are: - The SMS gateway of the BPBD can be expanded that the text messages from the heads of the Kelurahans are also stored in the server of HKV. - HKV needs to build a database for BPBD’s SMS gateway to communicate with.

Deltares, HKV, PusAir , RHDHV 45

Jakarta Floods January 2013 1207961 April 2013 Main Report

6.4.2 HKV receiving text messages As a short term solution, HKV can set up a system to receive forwarded text messages from the BPBD. The SMS Gateway in the BPBD can be set up in such a way that every time when it receives text messages from the heads of the Kelurahans, it is automatically forwarded to a SMS Gateway of HKV. Once the message is received by HKV, it can automatically be stored in the server of HKV. However, because the server of HKV does not support sending and receiving text messages, they will have to set up the SMS Gateway at a different location and connect it to their server via the internet. Note that this set up can only be temporarily, as it is less robust than the first solution. Steps to realize this option are: - BPBD needs to configure their SMS gateway to forward text messages. - HKV creates a SMS gateway to receive text messages. - HKV needs to build a database that can communicate with their SMS gateway.

Deltares, HKV, PusAir , RHDHV 46

Jakarta Floods January 2013 1207961 April 2013 Main Report

7 Testing of the Twitter Map

Since January there have been three more floods in Jakarta: 5 February, 5 March and 18 April. Thanks to the Emergency Assistance, all of these floods could be monitored by the Twitter application that is now part of the Planar screen of BNPB. Hereunder the results (also available on banjironline.co.id):

7.1 5 February inundations After heavy rainfall, parts of Bekasi started flooding severely. The Twitter Monitor recorded over 800 tweets per hour at the peak. Hereunder the output of the application:

Figure 50 Twitter monitor dd. 5 Februari 2013

Figure 51 Twitter graph dd. 5 Februari 2013

Deltares, HKV, PusAir , RHDHV 47

Jakarta Floods January 2013 1207961 April 2013 Main Report

And some photos of the event:

Figure 52 Verification of the Twitter Output

7.2 5 March inundations The Twitter Monitor had been further developed to show the 267 Kelurahan of the city. 5 March it showed the following output:

Deltares, HKV, PusAir , RHDHV 48

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 53 Twitter map dd. 5 March 2013

Figure 54 Twitter graph dd. 5 March 2013

Deltares, HKV, PusAir , RHDHV 49

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 55 Verification of the Twitter Output

7.3 18 April inundations 18 April the twitter map showed inundations in Jati, Pulo, Bangka, Setia Budi, Cipinang Melayu, Johar Baru, Cawang, Bintaro, Sunter Agung, Kalibata, Cipinang, Kapuk, Kapuk Muara, Kamal Muara, Pluit, Cengkareng Timur, Joglo, Ceger. See Figure 56 Twitter map dd. 18 April 2013. 19 April the twitter map showed further inundation in Bintaro, Cipulir, Senen, Jati, Pulo, Joglo and Pluit.

Deltares, HKV, PusAir , RHDHV 50

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 56 Twitter map dd. 18 April 2013

Figure 57 Twitter graph dd. 18 April 2013

Hereunder a selection of verification photos on these dates. For the full overview please find www.banjironline.co.id.

Deltares, HKV, PusAir , RHDHV 51

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 58 Verification of the Twitter Output (for the complete picture see www.banjironline.co.id)

Figure 59 Verification of the Twitter Output (for the complete picture see www.banjironline.co.id)

Deltares, HKV, PusAir , RHDHV 52

Jakarta Floods January 2013 1207961 April 2013 Main Report

A Generation of rainfall maps for Melati, Cideng and Pluit

Method for determination of rainfall volume per polder 1 Posko piket (PU2) daily rainfall gauges, plotted on a map (see figures below) 2 From points to map rainfall spatial interpolation. Method: Inverse distance weighting. Settings: distance to the power two with a maximum of 4 gauges (see figures below) 3 Mean daily rainfall determined per polder on the maps generated by step 2. (see Figure 60 - Figure 68)

Figure 60 – January 10th rainfall

Deltares, HKV, PusAir , RHDHV 53

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 61 – January 11th rainfall

Figure 62 – January 12th rainfall

Deltares, HKV, PusAir , RHDHV 54

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 63 – January 13th rainfall

Figure 64 – January 14th rainfall

Deltares, HKV, PusAir , RHDHV 55

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 65 – January 15th rainfall

Figure 66 – January 16th rainfall

Deltares, HKV, PusAir , RHDHV 56

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 67 – January 17th rainfall

Figure 68 – January 18th rainfall

Deltares, HKV, PusAir , RHDHV 57

Jakarta Floods January 2013 1207961 April 2013 Main Report

B Creating the flood depth map

Deltares has created a flood depth map for the flood event in January 2013. This flood depth map is used to analyse the situation at polder Pluit during the flood event and to be able to calculate the water balance.

Input data The flood level map is based on: 1. Digital elevation map from Jakarta 2. Lidar data (2x2m) from laser altimetry 3. Flood depth alerts on googlemaps (ww.gosur.com)

Figure 69 Example of the detail of LIDAR (2x2m) at Pluit; Color red = Higher area, Yellow = lower area; Houses and streets are clearly visible

Deltares, HKV, PusAir , RHDHV 58

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 70 Flood depth alerts on internet (http://www.gosur.com/en/indonesia/alerts/weather/2013-jakarta- flood-indonesia-map/?gclid=CPm8r8Ps6rUCFeXLtAode3gAEQ).

Deltares, HKV, PusAir , RHDHV 59

Jakarta Floods January 2013 1207961 April 2013 Main Report

Generate a flood depth alert point map from internet information

The point information about the flood depth is downloaded in KML-format from the http://www.gosur.com/en/indonesia/alerts/weather/2013-jakarta-flood-indonesia- map/?gclid=CPm8r8Ps6rUCFeXLtAode3gAEQ:

The kml-file looks as follows: Lokasi Banjir Harco Glodok Ketinggian air 80cm

]]> #style81 106.817215,-6.144075,0

The coordinates and the flood depth for all locations (see the text in red) are extracted from this kml-file for all locations and is put in a shape-file which can be displayed in ARCGIS, see Figure 71.

Flood depth [m]

0.00 - 0.25 0.26 - 0.50 0.51 - 1.00 1.01 - 3.00 Figure 71 Flood depth alerts from KML schematised in ARCGIS

Deltares, HKV, PusAir , RHDHV 60

Jakarta Floods January 2013 1207961 April 2013 Main Report

Combine LIDAR surface level and the flood depth alert point map to create a flood level map

The surface level data and the flood depth alert map are combined in a two step procedure to create the flood level map given in chapter Resulting flood depth map0.

x Step 1: The surface level data (LIDAR) is now combined with the flood depth alert map. The result is a flood level map, see Figure 72

Figure 72 Flood level map (= flood depth alerts + Surface elevation (LIDAR))

x Step 2: The medium flood level is now calculated per polder assuming the inundation in one polder is not affected by the neighbor polder.

Deltares, HKV, PusAir , RHDHV 61

Jakarta Floods January 2013 1207961 April 2013 Main Report

Figure 73 Medium flood level per polder

Resulting flood depth map The resulting flood depth map is given in the figure below. It is calculated by extracting the in level map (see previous chapter)

Figure 74 Flood depth map

After the floods, the FMIS team visited the BNPB and BPBD on several occasions, see the meeting minutes in Appendix B. Hereunder the main results on the flood information

Deltares, HKV, PusAir , RHDHV 62

Jakarta Floods January 2013 1207961 April 2013 Main Report

exchange at both organisations during the January Floods and their main concerns on flood information.

Deltares, HKV, PusAir , RHDHV 63

Jakarta Floods January 2013 1207961 April 2013 Main Report

C Technical documentation

C.1 Introduction This document describes the technical background of two applications developed in the extended FMIS project: the Planar Application and the Map Application. This document starts with the conventions used to develop the applications and next describes the application in two parts: the server-side and the client-side.

C.2 Conventions The software is developed using the following general conventions: x Structured code: The code is logically structured, not complex and perform small and simple tasks per function. All the source files are grouped according to a clear and logical structure. For this application, the files for the source code are grouped in a folder structure according to their language. Each folder contains multiple files with source code. For the planar, that means this folder structure: +-- audio +-- css | \-- external +-- data +-- js | \-- external +-- php \-- nodejs - The main folder keeps all the HTML files, so they can easily be accessible for the client. - In the audio folder there are audio files which can be played by the application. - The css folder holds all the layout related files, and the external folder keeps all the style sheets from external sources. - The data folder contains general, easily accessible data ranges. - The js folder is set up in a similar way as the css folder. The folder itself contains all the JavaScript files and the external folder keeps all the JavaScript files created by third parties. - The php folder contains all the server-side PHP scripts. In addition, this folder also contains one Octave file. - The nodejs folder contains all the server-side NodeJS scripts. The folder structure of the water level map application is more complicated because it is part of a bigger application called BanjirOnline. x Modularity: The applications are of a modular nature so that pieces of code that are developed for other project or applications, can easily fit in this application. Likewise, the code created during this project can fit in other (future) projects. Both applications in this project consists out of a few main tasks for both server-side as client-side. Those tasks in their turn consists out of functions grouped together in one file. The files created during this project can be used in other projects with minimal configuration, just like files of other projects are used in this project.

C.3 General scripts General scripts mostly involve server-side scripts. However, some pieces of client-side code are also reused throughout the application.

Server-side The server-side is written in two different languages: PHP and NodeJS.

Deltares, HKV, PusAir , RHDHV 64

Jakarta Floods January 2013 1207961 April 2013 Main Report

x PHP is used to retrieve data from external sources to save it into the database and handle requests from the client application. x NodeJS makes sure that the client application is always connected to the back-end and is informed when new data is available.

PHP These PHP scripts are used by both the Planar and the Map application: x colourize.php. This script colours command line output of an application to make it more human readable. x post_request.php. This script handles the POST requests from PHP to NodeJS. These POST requests are used to notify clients about new data. x fetch.php. This php script handles all client requests for data. With a few GET parameters, the answer can be specified by the user. This script can make a connection with the server database. To prevent things like SQL-injections, this script is only allowed READ access to the database and has no WRITE privileges. More about this script can be found lateron. x save_waterlevels.php. This script saves water levels from the Jakarta government website. It first gets all the already saved water levels of the past 48 hours. Next, the same data is downloaded from the website and compared against the existing data. If some data differs, or if there is any new data available, the new data is saved in the database. In the end, the script take the timestamp of the earliest occurrence of new data and sends that to NodeJS to notify clients.

fetch.php The file fetch.php is located on the server of HKV Indonesia and can be approached by making GET requests. This way, it works seamlessly together with AJAX. This part of the document explains all the parameters that are available in fetch.php. x request (string). This parameter lets the server know what type of data is requested. Legitimate requests are: - get_tweets. This request returns all the actual relevant tweet objects of a certain time period. - get_count. This request returns the an array with all the available kelurahan and their counted value from process_tweets_count.php. These values are either the latest values, or the maximum occurrence of a certain time interval (depending on other parameters, default: latest value). - get_count_range. This request returns an array of arrays with kelurahan and their counted values in a certain time period. Each array of kelurahan represents a time in the past. - get_waterlevels. This request returns an 3D array, with the water levels and their measured time, over a certain time period of all the 14 water stations in Jakarta. - get_grid_image. This requests return an array over JSON objects. Each JSON object contains an image location, an availability boolean and a time stamp. The array contains all object from within a certain time period. x from (string). This parameter indicates the beginning of the time period of the returned object. Default: ‘1 hour ago’. x to (string). This parameter indicates the end of the time period of the returned object. Default: ‘now’. x location (string). This parameter works with the requests get_tweets and get_count. When this parameter is set, only objects for this location is returned. Default: ‘’. x include_rain (boolean). When set, the request get_waterlevels will not only return the water levels, but also a precipitation indication. Default: false.

Deltares, HKV, PusAir , RHDHV 65

Jakarta Floods January 2013 1207961 April 2013 Main Report

x top_ten (boolean). When set, get_count_range returns only the top ten kelurahan instead of all the kelurahan (put in to reduce data transfer). Default: false. x max (boolean). When set, get_count will return the maximum counted value of a certain time period of each kelurahan, instead of the latest. Default: false. x top (boolean). This parameter works only in combination with max. When both max and this parameter are set, get_count will return only the kelurahan over a certain time period when their maximum counted value is above a certain threshold. Default: false. x source (string). This parameter switches the output between returning tweet related data, water level related data and grid images related data. Default: ‘twitter’. x series (boolean). When set, get_grid_image will return an array of JSON object, otherwise only the latest is returned. Default: false.

NodeJS There is only one NodeJS used for both the Planar and the Map application: x Notify.js. This script consists out of two parts: listening to POST request and maintaining connection with clients. Once a POST request comes in, it first checks the data. If the data is in the correct format, it is forwarded to the right clients. These clients then know that there is new data available and will automatically download this updated information. Currently only water level and radar data is supported by this script.

Client-side The client-side is written in the languages: HTML5, CSS3 and JavaScript, all separated into different files. The technical requirements of the client-side are described a little further in this document. x HTML5 is used as a placeholder for all the content. x CSS3 is used to create the layout of the application. x JavaScript makes the application dynamic. It makes sure that all the information is constantly updated and handles event.

Because HTML5 and CSS3 scripts are rather static easy to read, this document will focus mainly on the JavaScript for the client-side. As mentioned before, there are no whole scripts (apart from external libraries) used twice on the client side, only pieces of codes. Two pieces that are used at more places are pieces for displaying graphs (water levels) and drawing maps. The external libraries are: 1. jQuery 1.8.2. jQuery forms an enhancement of the existing JavaScript library. The reason why an older version of jQuery is used, is because in later versions the ‘$.browser’ object was disabled. 2. jQplot 1.0.4. This library is used to plot graphs. Besides the regular jquery.jqplot.js, this library come with a whole set of plugins. More information about these plugins can be found on the website. 3. date.js 1.0 Alpha-1. This library expands the original JavaScript Date library with some useful functions. 4. jquery.animate-colors.js 20120928. This library makes sure that colour fading can be used with the jQuery function ‘animate’. 5. LeafletJS 0.5.1. This is a library that works together with the maps from CloudMade to display them in the browser and creates the interaction between the user and the map. 6. KineticJS 4.4.3. This library extends the existing canvas library in JavaScript. KineticJS makes it easier to draw shapes and figures on a HTML5 canvas

Deltares, HKV, PusAir , RHDHV 66

Jakarta Floods January 2013 1207961 April 2013 Main Report

element. Within the applications described in this document it is only used in the Map Application to draw the header and footer.

General Data Both the Planar Application and the Map Application make use of a few general data files. These files are mostly used for client-side purposes and are therefore written in JavaScript. x kelurahan.js. This file holds a JSON object with the administrative boundaries of all the 261 kelurahans in Jakarta. x location_names.js. This file holds a JSON object with some meta data about all the 261 kelurahans in Jakarta. Meta data that is saved into this file is: its full name, its shortened name, its center point, its radius (in meters) and some keywords (like points of interests) about the kelurahan. This file is also read by the server-side script process_tweets.php to check the relevance of a tweet. x siaga_levels.js. This file holds a JSON object with the siaga levels of 14 water stations in Jakarta. Of each siaga level both a maximum and a minimum is given per water station.

The Planar Application

Server-side For the server-side of the Planar application specifically, there are PHP scripts and Octave scripts used. These scripts make sure that the database is up-to-date.

PHP The planar application consists out of three parts, each of which have their own PHP scripts due to the modular nature of the application. However, all three parts use the same fetch.php to get (new) data from the server. The three parts, with their PHP scripts are: x Water levels. This part only uses the script save_waterlevels.php, which is already explained earlier in the General scripts. x Twitter map. The Twitter map part uses five different scripts; two external (OAuth.php and twitteroauth.php) and three own made (save_raw_tweets.php, process_tweets.php and process_tweets_count.php). - OAuth.php. This external library is used to help setting up a connection that is secured via OAuth. - twitteroauth.php. This external library is used to connect our application to a twitter account. This is necessary, because twitter does not allow others to search through tweets without authentication in the non-deprecated API. - save_raw_tweets.php. This script makes sure that all the tweets with a certain keyword (in our case “banjir”) are saved into the database. This script only saves all ‘raw tweets’ to improve speed. - process_tweets.php. This script reads all the saved tweets and checks them for relevance. The tweets are first checked on geo location, then for any relevant keywords in the tweet itself. Once a tweet is deemed relevant, it is categorized and put into a second table. All the ‘raw tweets’ from the first table are then deleted, to prevent the database from flooding. - process_tweets_count.php. Every five minutes, this script counts all the relevant tweets for each category of the past hour and puts this (as a JSON string) into a third table. x Radar map. This part plots the precipitation of the Jakarta area on a map. In order to do this, it uses one PHP script (get_radar_data.php) and one Octave script

Deltares, HKV, PusAir , RHDHV 67

Jakarta Floods January 2013 1207961 April 2013 Main Report

(rain2png.m). get_radar_data.php periodically (every ten minutes) checks an FTP- box with the radar data saved on there. Once there is new data available, this script saves the data locally, create precipitation map overlays and archives old data. Last, the script checks if any new images were created. If so, the script sends the name of all the new images to NodeJS to notify clients.

Octave Octave is a high-level interpreted language, primarily intended for numerical computations. It is an open source version of Matlab. In this application, only one Octave script is used to work together with the Radar map. x rain2png.m. This script reads grid data in a NetCDF format, creates an image from that and afterwards creates a legend image for the given data range.

Client-side As mentioned before, the client side exists out of three parts: HTML5, CSS3 and JavaScript. x HTML5. The only HTML5 file available in this application is index.html. x CSS3. There is only one non-external CSS3 library called style.css. x JavaScript. There are five JavaScript files written for this application. - main.js. This file contains the main controller. Once the page is loaded, this script is executed and distributes tasks to other files. In addition, this file also adds drag and drop functionalities and makes sure that every graph is plotted in the right square. - draw_graphs.js. This script is responsible for downloading the water level data and plotting all the graphs in the right place. Once this script receive a notification that new data is available, it downloads that data automatically and plots a new set of graphs. - draw_twitter_map.js. This script draws the latest twitter data from process_tweets_count.php on a map. - draw_radar_map.js. This script puts the image overlay created by rain2png.m over a map. It creates a time loop of three hours with a five minute interval. On every interval, the script shows the overlay with a timestamp closest to that specific interval (if the difference is not more than three minutes). If there is no overlay available, the previous overlay will slowly fade away in time. The script also listens to the server about any new data. Once new data is available, this script automatically downloads it and put it together with the existing serie. Once an overlay gets too old, the overlay is removed from the client to save memory. - handle_socket.js. This piece of code makes sure there is a connection to the server via NodeJS.

The Map Application

Server-side The server-side of the Map Application does not use any scripts that have not been described already before. The scripts used in this application are: fetch.php and save_waterlevels.php.

Client-side The Map Application is part of a bigger application called BanjirOnline. Therefore the structure and naming convention is different from the Planar Application. However, also the Map Application consists out of HTML5, CSS3 and JavaScript.

Deltares, HKV, PusAir , RHDHV 68

Jakarta Floods January 2013 1207961 April 2013 Main Report

x HTML5. There is only one HTML5 called kml_process.html. x CSS3. There are several CSS3 files, because some layout needs to be the same throughout the whole BanjirOnline application. All files are: - header.css. Stylesheet for the header of the page. - body.css. Stylesheet for the body of the page. - footer.css. Stylesheet for the footer of the page. - process_style.css. Stylesheet for all processes of BanjirOnline. - kml_process_style.css. Stylesheet for the process of which the Map Application is a part. x JavaScript. There are four JavaScript files written for this application. All of them are not written for this application specifically, but also for other applications within the BanjirOnline application. - process_script.js. This script makes sure that the right process is activated. - helper_process.js. This script draws the header and the footer on the page. - kml_process_script.js. This script creates the map on which the markers are plotted. In addition, this script changes the marker of a water station in accordance to its siaga level. - kml_graph_script.js. This script draws the graph after a marker is clicked.

Deltares, HKV, PusAir , RHDHV 69

Jakarta Floods January 2013 1207961 April 2013 Main Report

D Meeting Minutes BNPB/ BPBD

D.1 Minutes of meeting BNPB

Project : FMIS extension Date : 25 March 2013 Subject : Meeting minutes HKV-BNPB From : Wagemaker To:

Location: BNPB Present: Noel Pitoy (BNPB), Pusdalops team, Adit Dwi Putra (HKV), Ron Boortman (HKV), Jurjen Wagemaker (HKV)

We demonstrated the FMIS web-IT and discussed the following: - Adjustments to Planar view - Adjustments to Desktop view - Potential of the twitter application

Adjustments to Planar view Noel Pitoy requested the following adjustments:

Radar in the right pane: - Create loop of three hours. At the end of one loop, stop for few seconds (3) before continuing. So we know what is the beginning and what is the end. - Add legend of the colours - Create a more quiet background, with thinner lines, softer colours - Add names of administrative units to the map

Water levels boxes: - Add legend on bottom explaining the colors of the boxes (water systems Ciliwung a.o.) - Font of the title and legend: Arial, all caps, black, smaller than current - Grid: More horizontal lines, 36 vertical lines (every hour one). Total time span 30 hours history and reserve 6 hours for future forecasts. The lines should be thinner. - Horizontal legend: Only show the hours (9,10,11,12 etc.). Preferable every hours or every two hours (10,12,14 etc). Place date on far right and far left in the box. - Add next to the title, on the right side: Siaga level. - Add next to the title, on the left side: Maximum Depth: X m. - Upon change of the Siaga level: Flash entire box for 5 seconds. Then only flash Siaga box. The Siaga box flashes more quickly at each higher Siaga level - The screen can be filled more optimally: Have the boxes touch eachother. - Keep box no. 15 open for a future menu, for instance for printing function.

Appearance: Too white, not good for the eyes of the people in Pusdalops. Suggestion to invert colours to all black with white grid lines.

Other functions: Noel would like to hear an automated sound upon exceedance of a

Deltares, HKV, PusAir , RHDHV 70

Jakarta Floods January 2013 1207961 April 2013 Main Report

certain level. This is possible all we need are 14 (stations) times 3 (siagas) spoken and saved as a wav. Noel will deliver this asap. HKV will incorporate the function into the application.

Fig. 1: Changes illustrated by Noel Pitoy

Adjustments to desktop view - Improve the zoom in/out and scrolling to historic data of water levels - Create a 3D overview with vertical bars and names of the stations (Noel will send an example)

Potential of the twitter application Conclusively we discussed the Twitter application of BanjirOnline. Noel was very interested and proposed to discuss this a.s.a.p. with several directorate within BNPB. We tentatively scheduled for end of next week.

Actions Noel Pitoy understands that there are limitations to this project and that we have to prioritize. The FMIS team has a clear vision of the most important adjustments for BNPB and will make according priorities in the web development. Actions are: - Noel Pitoy: Record 3 times 14 wav. files - FMIS team: Make the requested adjustments (within time-limits of project) - Noel Pitoy: Schedule next meeting to discuss result and more specifically the potential of the Twitter application

Deltares, HKV, PusAir , RHDHV 71

Jakarta Floods January 2013 1207961 April 2013 Main Report

D.2 Minutes of meeting BPBD

Date: 25 March 2013 Location: BPBD Present: Pak Edy (BPBD, Kepala Bidang Informatika dan Pengendalian), Pak Fahzi (BPBD, Pusdalops), Adit Dwi Putra (HKV), Ron Boortman (HKV), Jurjen Wagemaker (HKV)

Before the meeting, we talked to the people in the Pusdalops: - Their procedure is that they receive their information from the radio and input it into their SMS gateway software. The software produces a graph and a table. With regular intervals depending siaga, they send an atomized message to recipients. The system worked fine during the disaster. - Fahzi showed us the JFEWS client that he is very happy with, even though they are not using it much. During the emergency of January the JFEWS was offline says Fahzi.

Upon the arrival of Pak Edy, we sat down in the meeting room, discussing: - Pak Edy says thanks for all the help that they are receiving, such as the JFEWS in the Pusdalops and the explanations given by JanJaap on JFEWS and on the water system of Jakarta - Their largest problem is that they do not have an overview of the disaster (extent, damage, casualties, displaced, vulnerables etc.). Edy explains that during the disaster of January, the information flow was not well-organized. It took them nine or ten days (after 17 january) to get the complete overview of the disaster. - During January disaster, they moved the Pusdalops to the Ruang Pola, in effect meaning that the radio connection for water levels was done now at the Ruang Pola as well as the Pusdalops on the third floor. - The flood map they used is based on the information that they receive from the mayors, who received their information from District level and Subdistrict level by fax. With the help of Worldbank and AIFDR they created a flood map. After the flood, when they got all the information, they found that only about 60% had been correct. - The information that heads of districts receive is often not correct. Sometimes they let know that they do not need any assistance so the BPBD sends their resources elsewhere. But the next day it turns out they receives false information and they actually do need logistical support. - After demonstration of the twitter functionality, we discussed the use of SMS from the Paks Lurah to get an overview of the situation. This SMS should contains three information: Location, Maximum Water Depth, Amount of displaced persons. End of April there will be a training for all the Paks Lurah and he can make it part of the training. We agreed that HKV will prepare such functionality, in cooperation with Pak Fahzi and his SMS gateway. - End of this year there will be installed an Emergency Operation Centre on the third floor of Blok F (where BPBD sits). Budget is now Rp. 7 billion.

With Pak Fahzi we moved to the Ruang Pola: - During the disaster the Ruang Pola had a posko banjir, a call centre, the big screen with the Lapor website and a meeting table with the heads of departments. - Posko banjir: Received water levels by radio, wrote it on the white board and informed volunteers about the water levels through the call centre

Deltares, HKV, PusAir , RHDHV 72

Jakarta Floods January 2013 1207961 April 2013 Main Report

- Call centre receives informatioon from volunteers and citizens (call 164) and uploads the information to www.lapor.ukp.go.id which is shown on the big screen. Citizens mainly requested for evacuation. The call centre is also used for calling out, for instance to the volunteers. - Big screen: The big screen can only handle one information source, and that was Lapor website during the past January flood.

Way forward and actions: - Quick win would be to develop a service that automatically obtains data from the SMSes of the Paks Lurah and shows them on a map, like the Twitter application. Proposed action: Ron/ Adit will visit Fahzi to find out how this can best be realized. - Next month we (FMIS team, Edy) will discuss the possibilities, so that Edy can decide to make the realtime flood information from Lurah part of the training. Proposed action: Make appointment as soon as we know how to tackle this. - Option: We could make FMIS at BPBD more robust by creating a redundant offline website for BPBD containing the flood map information from the SMS gateway and containing the water levels from BPBD radio. Proposed action: Ron will follow-up with Fahzi how to realize this.

Deltares, HKV, PusAir , RHDHV 73

Jakarta Floods January 2013 1207961 April 2013 Main Report

E Presentation Soft Soil Tunneling in Urban Areas

Soft soil tunneling, in urban areas How to manage the risks?

Frits van Tol, Member of Scientific board of Deltares Professor of Foundation Engineering, Delft University of Technology

Indonesian delegation, 1st of May 2013

Deltares, HKV, PusAir , RHDHV 74

Jakarta Floods January 2013 1207961 April 2013 Main Report

Overview of presentation • Introduction • Soft soil tunneling • Research • Risk management

Introduction - Situation in Jakarta and - In the Netherlands

Deltares, HKV, PusAir , RHDHV 75

Jakarta Floods January 2013 1207961 April 2013 Main Report

Jakarta flooding December 2012

28 juni 2013

Elevation

28 juni 2013

Deltares, HKV, PusAir , RHDHV 76

Jakarta Floods January 2013 1207961 April 2013 Main Report

project Tunnel Ciliwung – Banjir Kanal Timur through Bidara Cina (China Town)

28 juni 2013

project Tunnel Ciliwung – Banjir Kanal Timur

28 juni 2013

Deltares, HKV, PusAir , RHDHV 77

Jakarta Floods January 2013 1207961 April 2013 Main Report

soil profiles 1

28 juni 2013

soil profiles 2

28 juni 2013

Deltares, HKV, PusAir , RHDHV 78

Jakarta Floods January 2013 1207961 April 2013 Main Report

soil profiles 3

28 juni 2013

soil profiles 4

28 juni 2013

Deltares, HKV, PusAir , RHDHV 79

Jakarta Floods January 2013 1207961 April 2013 Main Report

Bidara Cina – low rise buildings

28 juni 2013

Nurhuda Medical Centre

28 juni 2013

Deltares, HKV, PusAir , RHDHV 80

Jakarta Floods January 2013 1207961 April 2013 Main Report

Some high rise

28 juni 2013

The Netherlands

Half of the surface of the Netherlands lays below sea level The top soil layers in that area are very soft

Deltares, HKV, PusAir , RHDHV 81

Jakarta Floods January 2013 1207961 April 2013 Main Report

The top soil layers in that area are very soft

…. with a high groundwater table

With sometimes flooding

Wilnis 2003

Deltares, HKV, PusAir , RHDHV 82

Jakarta Floods January 2013 1207961 April 2013 Main Report

Bored tunnels in the Netherlands

•North-South line Amsterdam •Green Heart Tunnel •Hubertustunnel •Sofia tunnel •Tunnel Pannerdenskanaal •Statenweg tunnel R’dam •Service tunnel Oude Maas •Botlek Railway tunnel •Second Heijenoord tunnel •Westerschelde tunnel •Sluiskiltunnel

Nearly all in the western part .

North-South Line Amsterdam

A few underneath city centers

Deltares, HKV, PusAir , RHDHV 83

Jakarta Floods January 2013 1207961 April 2013 Main Report

Overview of presentation • Introduction • Soft soil tunneling • Research • Risk management

Soft soil tunneling

Important aspects

During construction - Stability during tunneling - Settlements - Shafts

During life time - Tunnel lining - Subsidence

28 juni 2013

Deltares, HKV, PusAir , RHDHV 84

Jakarta Floods January 2013 1207961 April 2013 Main Report

Stability during tunneling

Face stability, Cave in, Blow out

A proper face support is required

Varying soil conditions along the alignment are an important risk

Stability during tunneling

Face stability, Caves in, Blow out A proper face support is required

Cave In of Tunnel in Munich, 4 people killed, 27 injured

Deltares, HKV, PusAir , RHDHV 85

Jakarta Floods January 2013 1207961 April 2013 Main Report

Surface and building settlements

Important topic: how to related building deformation to surface settlement Surface settlements

Modification factors (Potts and Addenbrooke, 1997)

Deep shafts

Deep shafts have high risks

Deltares, HKV, PusAir , RHDHV 86

Jakarta Floods January 2013 1207961 April 2013 Main Report

Deep shafts

North South line Amsterdam

Inflow of water and sand caused severe settlements of neighboring buildings

Tunnel lining

Lining deformation

In dry tunnels the water pressure is confining the ring In water and sewer tunnels the internal pressure might be higher then external pressure >>> sometimes secondary lining necessary

Deltares, HKV, PusAir , RHDHV 87

Jakarta Floods January 2013 1207961 April 2013 Main Report

Influence of subsidence

Subsidence and earthquakes might cause additional loading of the tunnel lining

Differential settlements between shafts and tunnel

Overview of presentation • Introduction • Soft soil tunneling • Research • Risk management

Deltares, HKV, PusAir , RHDHV 88

Jakarta Floods January 2013 1207961 April 2013 Main Report

Research topics

In 1993 the Dutch government started an extensive research program on underground construction. One of the main topics was to develop knowledge in the field of the impact of shield tunnelling on buildings situated in the vicinity of the bored tunnels. Several research projects were started in 1993 combined with the tunnel projects, (Second Heinenoord tunnel, the Botlek railway tunnel and Sophia railway tunnel). The results of the research projects and an evaluation of the impact of shield tunnelling on pile foundations and the ratio between surface settlements and pile settlements is described in Kaalberg et al, (2005) and van Tol & Bosch, (2005):

Kaalberg, FJ, Teunissen, EAH, Tol, AF van & Bosch, J.W. (2005). Dutch research on the impact of shied tunneling on pile foundations. In K Bakker, A Bezuijen, W Broere & EA Kwast (Eds.), Geotechnical Aspects of Underground Construction in soft ground (pp. 123-131). London: Taylor & Francis. Tol, AF van & Bosch, J.W. (2005). Dutch research on the impact of shield tunnelling on pile foundations. In G Hofmans (Ed.), Proceedings of the 16th International Conference on Soil Mechanics and Geotechnical Engineering (pp. 1615-1620). Rotterdam: Millpress. 28 juni 2013

Some results

Many partners worked together in these research projects

Deltares was involved all the research projects:

-Planning -Instrumentation -Evaluation -Predictions -Reporting -Reviewing

28 juni 2013

Deltares, HKV, PusAir , RHDHV 89

Jakarta Floods January 2013 1207961 April 2013 Main Report

Instrumentation Northern Monitoring Area

A Settlement plates B Inclination gauges C Extension gauges

D Waterpression gauges TBM front E G E Ground pressures gauges F F Open stand pipe D

A C

B

Settlement at Northern Monitoring Area

Distance [m] -40 -30 -20 -10 0 10 20 5

] 0 m m [

-5 l e

v -10 e l

Settlement trough

d -15 n u

o -20 r g

t -25 n e -30 m

e Position TBM: -8 m, 0, l

t -35 t

e +8 m, +16 m and + 32 m

S -40 -45

Deltares, HKV, PusAir , RHDHV 90

Jakarta Floods January 2013 1207961 April 2013 Main Report

Settlement at Northern Monitoring Area

0,005

0

-0,005

] -0,01 m [

s n o i t

a -0,015 m r o f e

d -0,02

l a c i t r e

v -0,025

-0,03 first passage second passage

-0,035

-0,04 -100 -80 -60 -40 -20 0 20 40 60 80 distance to front of TBM [m]

North - vertical displacements at -4D

4

2

0

-2

-4 ] P

A -6 N

+

m -8 [

P

A -10 N

. 50 mm v .

o -12 . t

e t

p -14 e i d -16

-18

-20

-22

-24 -20 -15 -10 -5 0 5 10 z'-as [m]

gemeten predictie Plaxis

NB. verticale deformatie w_y' is 100 maal vergroot

Deltares, HKV, PusAir , RHDHV 91

Jakarta Floods January 2013 1207961 April 2013 Main Report

North – horizontal displacements at -4D

horizontale verplaatsing in z'-richting x 100 [m] / z'-as [m] -20.000 -15.000 -10.000 -5.000 0.000 -4

-2

0

2

4

6 ] P

A 8 N

50 mm -

m 10 [

e t

p 12 e i d 14

16

18

20

22

24

gemeten predictie

NB. horizontale deformaties w_z' met factor 100 vermenigvuldigd

Monitoring at Heinenoord tunnel

Monitoring of 43 wooden piles, 20 concrete piles loaded up to Amsterdam practice, during tunneling at distance of 0.5 D up to 0.25 D

Deltares, HKV, PusAir , RHDHV 92

Jakarta Floods January 2013 1207961 April 2013 Main Report

Monitoring at Heinenoord tunnel

Results

First passage Second passage

distance from tunnel (m) distance from tunnel (m) -20 -10 0 10 20 -30 -20 -10 0 10 0 4 0 4 surface ) ) m settlement m ( -20 -1 -10 -1 ( l l ) ) e

pile e v v m m e e l l m pile settlement m settlement ( . ( -40 -6 .

f -6

-20 f s s e e

t surface t r r n n e w e settlement w o o m l l -60 -11 m -30 -11 l l t e t e t t b b e e s s h h t piles tunnel t p -80 tunnel -16 -40 -16 p e e

piles d d -100 -21 -50 -21 -20 -10 0 10 20 -30 -20 -10 0 10

Volume losses 1 – 2 % 0.75%

Overview of presentation • Introduction • Soft soil tunneling • Research • Risk management

Deltares, HKV, PusAir , RHDHV 93

Jakarta Floods January 2013 1207961 April 2013 Main Report

Risk management

Deltares is often asked to perform the risk management;

Review of - Tender documents - Soil Investigation plans and reports - Design - Monitoring plan

Risk management - Entire project - Construction phase

Geo Risk management

Initiative Deltares’ philosophy : - Geo Risk Management throughout entire

Preliminary project design - Manage both process and content

contrac t 1. Project data gathering 2. Risk identification final design 3. Risk classification 4. Taking risk control measures 5. Assessing residual risk profile constructio n 6. Mobilising the risk register

operation

11 juni 2009

Deltares, HKV, PusAir , RHDHV 94

Jakarta Floods January 2013 1207961 April 2013 Main Report

Geo Risk Management at North South Metro line

After events at Vijzelgracht Deltares was commissioned by City of Amsterdam for control of the specifications (work plan) for every new activity of contractor (end of the line control)

Deltares pointed out to manage ground-related risks in a structured way:

This demands for: 1. full access to all information 2. identification of risks involved, 3. assessment of probability of occurrence of risks, 4. selection and execution of risk remediating measures etc, etc,

11 juni 2009

Organization schedule (Deltares N-S line)

Routing of documents (Sept 2008 – April 2009)

Risk analysis project board

8 local authorities Contract manager Deep stations Contract manager Contract manager 5 1 4 Central Station Bored tunnel 2 P c o r P 3 c o n o

6 r

7 j t e o n r P c a c j t o e r r t c o a n c

t o j t o t c e f r o t f r a c o i c f t c f r

e i o t c o f e f Deltares r i c

Quality Contr. e

11 juni 2009

Deltares, HKV, PusAir , RHDHV 95

Jakarta Floods January 2013 1207961 April 2013 Main Report

Organization schedule (Deltares N-S line)

Routing of documents (April 2009– today)

Risk analysis project board

local authorities Contract manager Contract manager Deep stations Contract manager Central Station 1 6 Bored tunnel 2 p c r o P c

o 3 n o r j o t e n r P c j c t a e o r r t c a c o

n o t t c j t o

e f r o t f r o a c i f c f r t c i

e c t o

4 o e f f r i Deltares c e 5

11 juni 2009

Conclusions

Soft Soil Tunneling in urban conditions requires - Experienced principle (in complex infra projects) - Design office with experience in soft soil tunneling - Contractor with experience in soft soil tunneling - Experienced quality control by the client

- Appropriate geotechnical investigations and consultancy - Appropriate management of soil related risks - Appropriate monitoring of excavations and surroundings

Deltares, HKV, PusAir , RHDHV 96

Jakarta Floods January 2013 1207961 April 2013 Main Report

Deltares is a reliable partner for Soft Soil Tunneling and Geo Risk Management

28 juni 2013

Deltares, HKV, PusAir , RHDHV 97