16.06.2014 Views

Chapter 5 - Information - 2009 Victorian Bushfires Royal Commission

Chapter 5 - Information - 2009 Victorian Bushfires Royal Commission

Chapter 5 - Information - 2009 Victorian Bushfires Royal Commission

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

INFORMATION<br />

5


<strong>2009</strong> <strong>Victorian</strong> <strong>Bushfires</strong> <strong>Royal</strong> <strong>Commission</strong>—Interim Report<br />

5 INFORMATION<br />

The community seeks information about fire risk from a range of sources. Current means of communicating with<br />

and informing the public do not always satisfy the community’s needs and do not always cope with the levels<br />

of demand. This chapter is concerned with information: the content, sources and means of the dissemination<br />

of bushfire information to the public. It deals with three discrete areas in which the provision of information to the<br />

community might be improved: the fire danger index and fire danger ratings; websites; and the <strong>Victorian</strong> Bushfire<br />

<strong>Information</strong> Line.<br />

revisiting the fdi and the fire danger rating<br />

5.1<br />

5.2<br />

5.3<br />

5.4<br />

The McArthur Forest Fire Danger Index (FFDI) and the Grassland Fire Danger Index (GFDI) are used by<br />

fire services to assess ‘the difficulty of controlling or suppressing a wildfire’. 1 These indices are calculated<br />

by reference to fuel characteristics and weather in order to generate a numerical index.<br />

The FFDI and the GFDI indicate expected fire danger and are regularly calculated by the Bureau<br />

of Meteorology (BoM) for the use of fire agencies. 2<br />

The FFDI is calculated using the ‘inputs’ of drought, recent precipitation levels, temperature, relative humidity<br />

and wind speed. The FFDI is calculated on the basis of a normative fuel load. 3<br />

The GFDI is calculated using the ‘inputs’ of curing or fuel moisture, temperature, relative humidity and<br />

wind speed. 4<br />

Table 5.1: The FFDI and GFDI fire danger ratings<br />

Ratings FFDI 5 GFDI 6<br />

Low danger rating 0–4 0–2<br />

Moderate danger rating 5–11 3–7<br />

High danger rating 12–23 8–19<br />

Very High danger rating 24–49 20–49<br />

Extreme danger rating 50+ 50+<br />

Source: Exhibit 3 – Statement of Rees (WIT.004.001.0001) [237.2], [237.5] 7<br />

156<br />

5.5<br />

The FFDI and the GFDI are together referred to as the fire danger index (FDI). The FDI was originally<br />

calculated on a scale of 0 to 100. As can be seen from Table 5.1, the fire danger rating of ‘Extreme’<br />

corresponds to an FDI of 50 and above. The scales are effectively ‘capped’ at 100, though higher values<br />

are possible. 8 As Dr Mark Williams, Regional Director, <strong>Victorian</strong> Regional Office of the BoM explained, the<br />

FDI was originally only designed to ‘go up to’ 100. Computing models now allow the FDI to exceed this. 9<br />

10<br />

5.6 The declaration of a Total Fire Ban (TFB) day is a separate, though related, process. The Country Fire<br />

Authority (CFA) (following consultation with the BoM) generally declares a TFB for a day on which the<br />

forecast FDI exceeds 50. 11 The declaration of a TFB is guided by, but not rigidly tied to, the FDI. 12<br />

The declaration of a TFB triggers statutory controls on activities that use heat and fire. 13<br />

5.7<br />

Witnesses referred to the difficulty that arises because all days on which the FDI exceeds 50 are described<br />

as ‘Extreme’ fire danger days, yet there is a significant difference between a day with an FDI of 50, and a day<br />

on which the FDI is above 100 or even 200. 14 Fire danger ratings do not distinguish between FDI values of<br />

50, 200 or 300. The original work underpinning the development of the FDI has not been validated beyond<br />

the value of 100. 15<br />

16<br />

5.8 The FDI forecast for 7 February <strong>2009</strong> exceeded 100 for most locations in Victoria. Accordingly, the fire<br />

danger rating for the day was ‘Extreme’, but in the view of many lay witnesses, this failed to convey the<br />

especially extreme nature of the fire danger risk for that day. 17


<strong>Information</strong><br />

Table 5.2: Fire danger indices forecast for 7 February <strong>2009</strong><br />

Location Forest Fire Danger Index Grass Fire Danger Index<br />

Walpeup 148 190<br />

Swan Hill Airport 159 210<br />

Horsham Airport 137 178<br />

Stawell 133 195<br />

Ballarat Airport 185 330<br />

Hamilton Airport 128 186<br />

Mortlake 102 133<br />

Bendigo Airport 142 186<br />

Shepparton Airport 127 167<br />

Mangalore Airport 131 171<br />

Geelong Airport 129 167<br />

Coldstream 142 186<br />

Tullamarine 164 175<br />

Dunns Hill 136 159<br />

Wonthaggi 79 110<br />

Albury-Wodonga 100 93<br />

Wangaratta Airport 100 95<br />

Hunters Hill 86 102<br />

Latrobe Valley 133 175<br />

East Sale Airport 112 129<br />

Mount Moornapa 125 163<br />

Orbost 84 29<br />

Gelantipy 95 173<br />

Falls Creek 56 126<br />

FFDI/GFDI between 0–50 FFDI/GFDI between 101–150<br />

FFDI/GFDI between 51–100 FFDI/GFDI above 151<br />

Source: Exhibit 3 – Statement of Rees (WIT.004.001.0001) at 0069 18<br />

Note: The locations are listed generally from west to east of the state.<br />

5.9<br />

5.10<br />

Expert witnesses expressed interest in reviewing the FDI, the language of the fire danger ratings or developing<br />

some other index to predict the potential for a fire to cause damage. For example, Dr Williams accepted that<br />

it was time to revise the FDI for indices greater than 100. He said that it was ‘clearly a research project that<br />

would have to be done with all the parties involved’. He proposed that the Bushfire Cooperative Research<br />

Centre (Bushfire CRC) might be involved in such work. 19<br />

Professor John Handmer, Innovation Professor in Risk and Sustainability and Director of the Centre<br />

for Risk and Community Safety at RMIT University, suggested that we need to find a way of reflecting a<br />

gradation above 50 or even above 100: ‘Some extreme level. At the moment I think we don’t have a way<br />

of institutionalising responses for a very extreme fire risk’. 20 He said that further research and work was<br />

required by the fire behaviour specialists to devise a scale to deal with very extreme fires. 21<br />

157


<strong>2009</strong> <strong>Victorian</strong> <strong>Bushfires</strong> <strong>Royal</strong> <strong>Commission</strong>—Interim Report<br />

5 INFORMATION<br />

5.11<br />

5.12<br />

5.13<br />

5.14<br />

5.15<br />

Expert witnesses agreed that current FDI scales provide insufficient information on the severity of fires,<br />

and they highlighted the importance of revisiting the FDI and the related fire danger ratings. 22 The indices<br />

and ratings need to be enhanced to reflect a meaningful set of numbers and language to express fire<br />

danger ratings above the present FDI 50+ (Extreme) category. This would assist in informing and educating<br />

the community about the graduated degree of risk on days when the FDI exceeds 50.<br />

A revised FDI that retains its purpose as an operational tool, indicating the level of fire risk and the difficulty<br />

of suppression, could also provide the community with a more objective indicator of potential fire intensity.<br />

The Commonwealth agreed that research should be undertaken to explore the option of including an<br />

additional fire danger rating beyond ‘Extreme’. 23 The Commonwealth noted, however, that this would<br />

require careful consideration because, presently, FDI values above 100 are not supported by fire<br />

suppression research. This is accepted, and it is assumed that the validity of values over 100 would<br />

be considered in the proposed research.<br />

In its written submissions, the State also supported this proposal. It suggested it would, however, await<br />

the outcomes of a reconsideration of the FFDI and GFDI being undertaken by the Australasian Fire and<br />

Emergency Service Authorities Council (AFAC) before implementing any <strong>Commission</strong> recommendations<br />

on this issue. 24 The work of AFAC, to which reference was made by Ms Jillian Edwards, pertains to a<br />

new approach to bushfire warnings, dealt with in <strong>Chapter</strong> 4 of this report. 25<br />

In supporting the proposed recommendation AFAC suggested that it, the Bushfire CRC and the BoM be<br />

included in the parties that could explore the options for revisiting the fire danger ratings. 26 Given that the<br />

Bushfire CRC, the CSIRO and a number of universities are potential recipients of research funds for this work,<br />

the <strong>Commission</strong> makes no recommendation on which body should be invited to undertake this research.<br />

RECOMMENDATION 5.1<br />

The Australasian Fire and Emergency Service Authorities Council and the Bureau of Meteorology<br />

collaborate with researchers to explore options for the fire danger indices and fire danger ratings<br />

including:<br />

■■<br />

■■<br />

■■<br />

an additional fire danger rating beyond ‘Extreme’;<br />

adjusting the existing fire danger ratings to correspond to higher Fire Danger Index values; and<br />

developing a revised fire severity scale for use in bushfire warnings based on new fire danger ratings.<br />

Making the FDI Available to the Public<br />

5.16 The BoM issues the FDI every afternoon for a selection of locations in each forecast district. When a rating<br />

of 50 or more is forecast at two or more locations, the BoM issues a Fire Weather Warning for that district<br />

after consulting with the CFA and the Department of Sustainability and Environment (DSE). 27<br />

5.17<br />

5.18<br />

The BoM makes the FDI available to the public, but only in the fire weather forecasts posted to the BoM<br />

website on the afternoon before the day in question. 28 The FDI is not included in the general weather<br />

forecasts posted on the BoM website or in material distributed to the media. Dr Williams accepted that if<br />

people knew where to look they could have accessed information about the FDI late on Friday, 6 February<br />

<strong>2009</strong> on the BoM website, but there was no general broadcast by the BoM of the FDI for 7 February. 29<br />

Dr Williams was asked whether there was any reason why the FFDI and GFDI could not be provided with<br />

future general forecasts issued by the BoM.<br />

158<br />

Well, that’s an interesting question. It could be. I guess my concern is that I don’t know how well they<br />

would be understood. People like numbers and obviously the higher the number, the more extreme the<br />

fire danger index is. It is there for the 24 hour forecast so I suppose they could be made available for<br />

longer periods. We calculate them routinely, we do them every day. 30


<strong>Information</strong><br />

5.19<br />

5.20<br />

It does appear to be the case, as Dr Williams puts it, that ‘people like numbers’. The BoM is an extraordinarily<br />

popular site — one of the most popular in Australia. 31 The site received 75 million hits on 7 February, which<br />

compares with a daily average number of approximately 44 million hits. 32 This provides some indication of<br />

the level of public interest in the weather forecasts and fire information the BoM is able to provide.<br />

A number of lay witnesses expressed a desire to have the FDI published more widely and for it to be more<br />

readily available. Typical of these views was Ms Jesse Odgers of Kinglake, who said:<br />

I feel the information is absolutely essential and I would like to educate myself more as to better understand<br />

what those indexes mean because they are going to assist me in making a more informed choice about<br />

when to leave. It assists me in that somebody external to me who is educated and experienced in fire is<br />

going to be able to give me an external assessment as to the danger other than a broad message such<br />

as that it is a total fire ban day or it is a day of extreme fire danger. So the more information that we can<br />

receive the more informed we will be and the more informed choices we can make. 33<br />

5.21<br />

Mr Ken Rogers of St Andrews noted that he was surprised after the fires to learn that a fire severity index<br />

exists and felt that information about such an index would have helped him to decide whether to stay or<br />

go. 34 Mr David Brown of Strathewen also expressed a desire to have had access to the information that<br />

the FDI was forecast to be in excess of 100 in his area. 35 He said that it would be a very graphic way of<br />

demonstrating the level of potential risk:<br />

When you have an index that normally runs from nought to 100 as its top end and it was registering 328,<br />

that is a very graphic illustration of the seriousness of the potential event and I think that would have<br />

been quite easy for people to understand … 36<br />

5.22<br />

5.23<br />

5.24<br />

5.25<br />

Dr Chris Harvey of Kinglake expressed a similar view that the FDI should be more readily available to<br />

the public, and accompanied by education about its meaning. 37<br />

Ms Karen Ward of Mudgegonga also said that had she ‘known how high the fire danger index was for<br />

that day,’ she would have left as soon as she knew of a fire in the area, because she would have known<br />

‘how bad the fire was going to be’. 38<br />

It therefore appears that in times of fire threat, the public has a strong desire for fire knowledge and<br />

information. It appears likely that there are as many in the community who prefer to have access to<br />

FDI figures, as there are those who find language such as high or extreme helpful and it would, therefore,<br />

assist the public to have ready access to the FDI.<br />

When asked whether there was any reason why the FDI is not provided to the community by the CFA<br />

with the other information provided about bushfires, Mr Russell Rees, Chief Officer, CFA, responded:<br />

Only in the sense that to understand those figures ... you need to understand what they mean so there<br />

needs to be an educative process and the language of low, moderate to extreme, high extreme is the<br />

language that is considered best to explain that scenario. If we move to explain those numbers it is<br />

a bit like using the UV index. If I say, ‘the UV index today is 35’ what does that mean to you and I?<br />

But if I said, ‘it is extreme today’, the chances are we would take action and put sunscreen on. 39<br />

40<br />

5.26 But Mr Rees accepted that if one provided the FDI in conjunction with ‘the words as well’ this ‘would be fine’.<br />

5.27<br />

5.28<br />

In relation to Mr Rees’ concerns that some may not understand the index figures, it is expected that the FDI<br />

would be provided in combination with the fire danger rating descriptors. In short, the numbers and words<br />

would be provided together. Of course, it is also desirable that information be available to the public about<br />

the meaning of both these resources.<br />

The FDI should be placed in easily accessible publicly available material, along with the fire danger rating,<br />

to increase the prospect that the message is understood by the widest possible sector of the community,<br />

including those who ‘like numbers’ and those who find language more comprehensible.<br />

159


<strong>2009</strong> <strong>Victorian</strong> <strong>Bushfires</strong> <strong>Royal</strong> <strong>Commission</strong>—Interim Report<br />

5 INFORMATION<br />

5.29<br />

5.30<br />

5.31<br />

In their submissions, Counsel Assisting proposed that the FDI ought to be published and more readily<br />

available to the community to assist individuals to assess the level of bushfire risk on particular days. 41<br />

The State agreed in principle with this recommendation, but said it did not intend to implement it until it had<br />

had the opportunity to examine the outcome of AFAC’s consideration of this issue. 42 The Commonwealth<br />

supported the proposed recommendation, but indicated it wanted to consult with the fire agencies before<br />

deciding on the best way of providing the FDI to the public. 43 AFAC endorsed the proposed recommendation,<br />

but called for an accompanying national public education campaign. 44<br />

This is a simple matter, but one worthy of immediate action, to ensure that the FDI is readily available to<br />

the public. Drawing on the comments of Mr Rees, it would be desirable for the FDI and the revised fire<br />

danger rating to be as well publicised and as well known as the UV rating. To that end, the FDI should<br />

be included in fire weather warnings and general weather forecasts to promote the visibility of this tool<br />

in predicting fire danger.<br />

RECOMMENDATION 5.2<br />

The Bureau of Meteorology include the Forest Fire Danger Index and the Grass Fire Danger Index in its fire<br />

weather warnings and general weather forecasts on its website and in material distributed to the media.<br />

Building A Single, multi-agency bushfire information website<br />

for Victoria<br />

160<br />

5.32<br />

5.33<br />

5.34<br />

5.35<br />

5.36<br />

5.37<br />

The CFA and DSE maintain separate websites. Mr Rees explained that the State <strong>Information</strong> Desk at<br />

the Integrated Emergency Coordination Centre (iECC) currently publishes information on the CFA website,<br />

based on information received from Incident Control Centres (ICCs) in the field. 45 Mr Ewan Waller, Chief Fire<br />

Officer, DSE, described the DSE website as providing ‘rapid access to critical incident updates, map based<br />

information, warnings and other related information’. He said the DSE website had evolved to meet ‘rapidly<br />

increasing public demand’. 46<br />

Members of the public rely on fire agency websites for accurate and up-to-date information about fires in<br />

their area. A number of lay witnesses attested to seeking information from websites. 47 On 7 February, ABC<br />

staff also monitored the CFA and DSE websites as one of the sources of information available to them. 48<br />

The <strong>Victorian</strong> Bushfire <strong>Information</strong> Line (VBIL) staff also relied on the websites. 49<br />

The public reliance on websites was reflected in the interviews analysed for the purposes of the Bushfire CRC<br />

<strong>Victorian</strong> <strong>2009</strong> Bushfire Research Response Interim Report (June <strong>2009</strong>). The preliminary analysis in that interim<br />

report noted that, ‘many interviewees sought information from the CFA and DSE websites ... There were no<br />

positive references to the websites. There were several negative evaluations of both websites’. <strong>Information</strong> on<br />

the sites lagged behind fire events. 50<br />

Professor Handmer provided expert opinion on the use of websites to gain information about fire risk and<br />

location. He expressed the view that ‘web based material has become the primary source of information in<br />

our society, both official and unofficial’. 51 He noted, however, that websites are often unreliable under heavy<br />

demand. 52 Professor Handmer stated that the public should have access to one website with the relevant<br />

information but, to reduce overload, there may be more than one site with identical content. 53<br />

Several witnesses agreed with the need for a single website. For example, Mr Alexander Caughey,<br />

Community Education Coordinator for the CFA, agreed there should be one site. 54<br />

Ms Kathryn Venters, Manager of Customer Service at DSE (based at the VBIL Customer Service Centre),<br />

also expressed the view that VBIL staff find it confusing to have to consult two agency websites, and said it<br />

would be a great advantage to have a single website. 55


<strong>Information</strong><br />

5.38<br />

Counsel Assisting has proposed the development of a single, multi-agency website to publish bushfire<br />

information in Victoria. This need was identified some time ago in the July 2006 report, Joint CFA/DSE Review<br />

of Effectiveness of <strong>Information</strong> Flow to Communities and Media During Fire Incidents — Preliminary Findings<br />

(the Joint CFA/DSE <strong>Information</strong> Review) where the following findings and recommendations were made:<br />

Along with the VBIL, the websites are a powerful tool for the dissemination of accurate and timely<br />

information directly to the community. The growing importance of the website can be measured by<br />

the fact that CFA’s website was recording in excess of 100 new users per minute during peak times in<br />

January 2006. The CFA’s website eventually encountered serious overloading to the point where it could<br />

not be accessed at some times. This created credibility problems; having created an expectation that<br />

information will be available it is imperative that this can be met …<br />

It would appear that there is a degree of duplication in the website presentations of both agencies.<br />

These sites have evolved over time to serve different purposes. They continue to serve a multitude<br />

of purposes and are aimed at multiple audiences.<br />

It also seems clear that there will be increasing demand for web-based information. Given the efficiency<br />

of such distribution and its capacity to deal with routine as well as urgent messages and information,<br />

the further development of web-based information should be treated as a priority … the prospect of<br />

permitting for web updates from IMT [Incident Management Team] or RECC [Regional Emergency<br />

Coordination Centre] level is worthy of consideration.<br />

Recommendation: Ensure websites have sufficient technical capacity to deal with public demand<br />

during peak periods.<br />

Recommendation: That the possibility of web messages being authorised or uploaded from IMT<br />

or RECC level be examined.<br />

Recommendation: That the creation of a single, multi-agency bushfire information website for<br />

Victoria be considered. 56<br />

5.39<br />

The findings and recommendations made above are strikingly similar to those now recommended. In particular,<br />

concerns about website capacity, the speed with which material is posted to the site and the desirability of a<br />

single website all received detailed and careful attention in the Joint CFA/DSE <strong>Information</strong> Review. When asked<br />

why the recommendation on a single website had not been implemented since July 2006, Mr Rees said:<br />

… I can’t answer you why not except to say that it was a project that was started following a review in<br />

06–07 to create one website. Whether it failed due to a lack of funding, the clear objective we had was<br />

that we in CFA reached a view that ... two changes needed to happen as we moved forward towards<br />

this one website. The first was that the CFA adopted the CAP [Common Alerting Protocol] as part of the<br />

AFAC recommendation ... the other thing we were looking forward to was the standardisation of message<br />

through the electronic telephone type message system. So we were looking to make the change all at<br />

once. I think the one website is a weakness. It is simply a case that we haven’t got there yet. 57<br />

5.40<br />

5.41<br />

5.42<br />

These comments do not fully explain the failure to implement the single website by February <strong>2009</strong>.<br />

Mr Rees said in his statement that the CFA and DSE were presently engaged in a project designed to<br />

develop ‘one website for the display of fire emergency information. It is envisaged the website will provide<br />

a simple summary of the information from the CFA and DSE websites on a single map of Victoria using<br />

common terminology to describe the fires’. 58 Mr Waller also referred to a current project to have ‘one<br />

website and I would very much welcome that, and a very quick website’. 59<br />

The State accepted the proposed recommendation for a single website, but in its written submissions<br />

proposed that the CFA would be promoted as the official bushfire website, with the DSE site remaining<br />

available to ‘ease capacity constraints’ and for individuals who wish to continue using that site. To ensure<br />

consistency, the State proposed that behind the scenes there would be a single website with single data<br />

entry and ‘same time’ uploads to both the CFA and DSE websites. 60 This suggestion of a principal and<br />

subsidiary website is arguably a little different from the evidence already given by Mr Rees concerning<br />

the project he attested was underway.<br />

161


<strong>2009</strong> <strong>Victorian</strong> <strong>Bushfires</strong> <strong>Royal</strong> <strong>Commission</strong>—Interim Report<br />

5 INFORMATION<br />

5.43<br />

5.44<br />

5.45<br />

In any event, the development and promotion of a single multi-agency website is essential. If the DSE<br />

site simply mirrors the CFA site and is provided to ease demand, this appears sensible, assuming identical<br />

information is posted and updated to both sites simultaneously. But the continued maintenance of separate<br />

sites, with the potential for separate information, is unlikely to be as useful.<br />

The creation of a single website would enable information dissemination and receipt to be streamlined,<br />

would eliminate confusion, and would prevent possibly contradictory information being placed on more<br />

than one site. Further, the promotion of a ‘one stop shop’ website is likely to relieve demand on other<br />

services, including the VBIL and even Triple Zero.<br />

Ultimately, consideration should also be given to the creation of one ‘brand’ for bushfire information and<br />

warnings. There is potential confusion in the use of both the CFA and the VBIL as sources of bushfire<br />

warnings and information. But for the purposes of the interim report, the recommendation concerns only the<br />

creation of a single multi-agency portal which would permit a single data entry point to be used to upload<br />

the same bushfire information to multiple websites at once, in time for the next bushfire season.<br />

RECOMMENDATION 5.3<br />

The State ensure that a single, multi-agency portal for bushfire information be established that uploads<br />

information simultaneously to both CFA and DSE websites.<br />

EXTREME DEMAND and delays in posting information on Agency WEbsites<br />

5.46 The agencies’ websites experienced difficulties on 7 February. There is evidence of delays in information<br />

being posted to the CFA and DSE websites, particularly for the Kilmore East fire, and of information being<br />

double-handled. The delays associated with the Kilmore East fire are addressed in more detail in <strong>Chapter</strong> 9.<br />

5.47<br />

5.48<br />

5.49<br />

Ms Samantha Stayner, Acting Program Director, 774 ABC Radio, noted that on 7 February the CFA and<br />

DSE websites often lagged behind information the ABC was receiving from the emergency services. 61<br />

To reduce delays in the posting of information onto websites, there should be capacity for ICCs to upload<br />

bushfire information and bushfire warnings directly to the new single multi-agency website. This would reduce<br />

the need to disseminate material. If this approach is adopted, in combination with sensible protocols, it is likely<br />

to increase the speed with which such material can be publicly displayed. The Joint CFA/DSE <strong>Information</strong><br />

Review also suggested this.<br />

In its written submissions, the State indicated that it is exploring the technical capacity required for ICCs<br />

to upload data to the website. 62 This is a very positive development.<br />

It appears that the agencies’ websites also slowed down due to the extreme levels of demand.<br />

5.50<br />

63<br />

Professor<br />

Handmer referred to ways of reducing the risk of the website malfunctioning or ceasing to function on days<br />

of extreme demand. These included using different display modes so more users can access the site quickly<br />

— for example, placing some of the key information on fixed rather than interactive pages, which reduces the<br />

time taken to deal with particular queries. 64 Graphics and logos can also ‘slow down’ web pages, so there is<br />

the option of going to ‘text only’ during periods of high demand. 65 Professor Handmer gave the example of<br />

the British Commonwealth and Home Office websites, which, during extremely high demand following the<br />

tsunami, switched to a ‘text only’ service to reduce the memory being used on the site, enabling the site to<br />

handle more inquiries or ‘hits’. 66 In addition, page design could be altered to speed up access, or information<br />

could be fed to other sites like Twitter to relieve demand. 67 This happened to an extent on 7 February with the<br />

ABC’s use of a Twitter site. 68<br />

162


<strong>Information</strong><br />

69<br />

5.51 The BoM website has been designed to carry extremely high levels of traffic. Though the information<br />

maintained on the BoM website is different from that regularly accessed on the fire agencies’ websites,<br />

it provides a useful model for the way in which a site can be designed to increase its functionality and<br />

accessibility during periods of peak demand. Steps, such as those referred to above, should be taken<br />

to preserve the functionality of a single website during periods of extreme demand.<br />

5.52<br />

The <strong>Commission</strong> is of the view that the bushfire information website should provide timely, accurate and<br />

up-to-date warnings and information that is posted by the fire agencies. This needs to be consistent with<br />

information being delivered through other means including the VBIL and ABC Radio. The website needs<br />

to be functional during periods of high demand and communicate simply text and visual information.<br />

RECOMMENDATION 5.4<br />

The State ensure that the single multi-agency portal for bushfire information be designed to allow Incident<br />

Control Centres to directly post information and warnings.<br />

The <strong>Victorian</strong> Bushfire <strong>Information</strong> Line<br />

Operations and funding of the vbil<br />

70<br />

5.53 The VBIL was established in 2003 by the CFA. It first operated during bushfire season 2003–04. From 2004,<br />

the VBIL operated with the CFA and DSE as joint stakeholders. The Department of Human Services and<br />

the Department of Primary Industries (DPI) are now also stakeholders, predominantly in the areas of health<br />

and recovery following bushfires. 71 The VBIL operates out of a Customer Service Centre (CSC) in Wendouree,<br />

Ballarat. 72 The VBIL service provided by the CSC gives information to the public via telephone, email,<br />

fax and TTY (textphone/telewriter for the speech and hearing impaired). 73<br />

5.54<br />

5.55<br />

5.56<br />

5.57<br />

5.58<br />

The CSC is funded from a contribution from DSE and DPI for core business and a fee per customer contact<br />

during campaigns, funded by the relevant stakeholder. The VBIL service is funded equally by the CFA and<br />

DSE. When one agency generates a particular campaign, that agency pays for the VBIL service. 74<br />

The CSC’s base funding for 2008–09 was approximately $1 million from DSE and $550,000 from DPI.<br />

VBIL stakeholders were charged campaign fees of approximately $1.3 million from 1 November 2008<br />

to 30 March <strong>2009</strong>. 75 Campaign fees for 7 February <strong>2009</strong> were $36,350. 76<br />

The VBIL provides information to the public on major bushfires; bushfire safety messages; community<br />

meetings; Emergency Relief Centre locations; bushfire recovery; TFB days and fire restrictions; DSE fuel<br />

reduction burns and other planned burns; annual DSE fire planning; and community consultations. 77<br />

The VBIL is promoted on the CFA and DSE websites and in promotional material distributed by both<br />

fire agencies. 78 The average call handling time for a VBIL call is six to seven minutes. 79<br />

The VBIL does not report fires, liaise with the Emergency Services Telecommunications Authority or Telstra<br />

Triple Zero, or play a role in dispatching emergency services to fires. 80<br />

VBIL staff are recruited by the CSC, with an emphasis on staff with ‘good active listening and question-framing<br />

skills’. 81 Training is delivered onsite by DSE staff. 82 Staff have access to Google maps and VicRoads materials<br />

to locate towns and suburbs. 83<br />

There is a Service Level Agreement between the CSC, DSE and the CFA:<br />

5.59 <strong>Victorian</strong> Bushfire <strong>Information</strong><br />

Line Service Level Agreement 2008/<strong>2009</strong>. 84 The Service Level Agreement contains requirements on staffing<br />

and reporting. The staffing levels are set in the Agreement by reference to ‘Readiness Levels’. For example,<br />

‘Readiness Level Red’ (referred to as code red) corresponds to FDI forecasts in excess of 50, or when a<br />

major fire (or a number of smaller fires) is burning. On these days, the Agreement requires that the VBIL<br />

operate extended hours, with the potential for 24/7 hours of operation. It also requires that between 11 and<br />

20 call takers be working on shift. 85<br />

163


<strong>2009</strong> <strong>Victorian</strong> <strong>Bushfires</strong> <strong>Royal</strong> <strong>Commission</strong>—Interim Report<br />

5 INFORMATION<br />

5.60<br />

The VBIL is available all year round, operating during the core hours between 8:00am and 8:00pm<br />

on business days. The CSC is able to activate surge capacity within two hours of notification by a<br />

State Duty Officer or the iECC <strong>Information</strong> Unit. 86<br />

VBIL ARRANGEMENTS WITH CENTRELINK<br />

5.61 Centrelink has 25 networked call centres around Australia, which deliver information and assistance<br />

about government services and payments. Centrelink call centres answer approximately 100,000 calls<br />

a day. Centrelink maintains a 24 hour a day, seven day a week standby capacity at its Geelong call centre.<br />

It is also able to call on other centres to provide emergency call centre services, subject to limits on access<br />

to relevant information about the emergency. 87<br />

5.62 Centrelink operates an overflow service to the VBIL whereby specially-trained Centrelink operators can<br />

answer VBIL calls at times of peak demand. 88<br />

89<br />

5.63 DSE and Centrelink are parties to a Memorandum of Understanding (MOU). The MOU includes the<br />

following:<br />

■■ Parties will use best endeavours to provide each other with information (Clause 7.1.3).<br />

■■ Centrelink staff will record information on the calls received (Services Schedule – Clause 3.1.1(g)).<br />

■■ Centrelink is required to provide daily reporting on the numbers of calls received, numbers of calls<br />

abandoned, average speed of answer and average handling time (Services Schedule – Clause 3.2.1(d)).<br />

■■ DSE is required to provide Centrelink with the necessary scripts and information to allow its staff to<br />

properly answer calls (Services Schedule – Clause 3.3.1(d)).<br />

■■ Centrelink is required to ensure its staff provide callers with information in accordance with the scripts<br />

and information supplied by DSE (Services Schedule – Clause 3.3.1(d)).<br />

5.64 Under the MOU, the VBIL provides Centrelink with all necessary scripts and other information required to<br />

answer callers’ questions, including secure remote access tokens that enable Centrelink operators to log<br />

in directly to the VBIL database. 90<br />

91<br />

5.65 The overflow arrangement is activated by a specific request from the VBIL to Centrelink. The MOU’s<br />

timeframes for activating ‘overflow’ are conservative. The MOU’s terms allow six or seven hours between<br />

a request to activate the overflow and the service commencing. 92 But the evidence was that, in reality,<br />

there is usually a reasonably rapid activation of the arrangement. 93<br />

5.66 Centrelink’s capacity to assist by activating the VBIL overflow is clear. However, there were problems<br />

with the outcomes on 7 February. The reasons for these problems are discussed below.<br />

164<br />

VBIL Call taking parameters and resouRces<br />

94<br />

5.67 As at 7 February, there were 90 telephone lines into the VBIL call centre. There was one queue for calls<br />

into the VBIL and no priority was given to different calls — although a VBIL call was answered before general<br />

enquiry line calls for DSE and DPI. The general enquiry line was not open on Saturday 7 February. 95<br />

5.68 The VBIL call-taking system, as it operated on 7 February, had the following characteristics:<br />

■■ When there was no available line (that is when more than 90 callers rang in at the same time), the caller<br />

heard a recorded message informing them that the VBIL was not able to take the call due to high demand,<br />

and referred them to Triple Zero or the CFA and DSE websites. 96<br />

■■ When there were, at any one time, more than 90 callers attempting to get through to the VBIL, there was<br />

no capacity for those callers to be placed ‘on hold’ — as a result, callers who did not ‘get a line’ were not<br />

counted in the VBIL’s count of calls abandoned on 7 February. 97<br />

■■ When the number of callers to the VBIL exceeded 90 at any one time, the system of overflow calls<br />

to Centrelink (see below) could not operate. As a result, those callers could not wait either for a VBIL<br />

or Centrelink operator to take their call and, again, the call was not counted in the statistics on<br />

abandoned calls. 98<br />

■■ When a call overflowed to Centrelink, two of the VBIL’s lines were occupied for the duration of the call —<br />

as one line into the VBIL and one line out to Centrelink. 99


<strong>Information</strong><br />

5.69<br />

The technical and physical limitations of the VBIL system on 7 February contributed to the difficulties callers<br />

had getting through to the service. Since the fires, the VBIL has increased the total number of available phone<br />

lines to the centre to 210. Sixty of these lines are outgoing lines only, to enable calls to be transferred to<br />

Centrelink during overflow periods. 100<br />

VBIL WORKSTATIONS AND STAFFING<br />

5.70 On 7 February, there were 20 work stations available at the VBIL for use by call takers. At no stage on the<br />

day were all those work stations in use. 101<br />

5.71<br />

5.72<br />

5.73<br />

These work stations apparently comprise simple desks, with phones, headsets and computers. At present,<br />

there is no funding for additional work stations, although Ms Venters indicated that consideration was being<br />

given to refitting the centre and to new funding arrangements in the next Service Level Agreement. 102<br />

As at 7 February, the VBIL staffing was as follows:<br />

■■<br />

■■<br />

■■<br />

15 ongoing or fixed-term staff employed by DSE — 13 full-time and two part-time<br />

35 DSE casuals, able to take all types of calls received at the CSC<br />

17 DSE casuals trained only to take the VBIL calls received at the CSC.<br />

Ms Venters explained that on a typical weekday at the VBIL, operating normal hours, 70 call taker hours<br />

would be rostered. On a typical Saturday, operating normal hours, between 32 and 40 call taker hours<br />

would be rostered. On a typical summer day, on which high temperatures are forecast, closer to 140 call<br />

taker hours would be rostered. On a code red day, Ms Venters said that the number of staff to be rostered<br />

is determined by the Service Level Agreement. As is noted above, this requires that between 11 and 20<br />

call takers be rostered. 104<br />

PROVISION OF INFORMATION TO THE VBIL AND CREATION OF FAQS<br />

5.74 The VBIL Call Centre staff are supplied with Frequently Asked Questions (FAQs), which they are required<br />

to use when answering particular categories of questions from callers. 105<br />

5.75<br />

5.76<br />

5.77<br />

The process intended to operate at the VBIL during fires is that awareness, alert and urgent threat<br />

messages are supplied by the CFA and DSE to the VBIL call centre. The <strong>Information</strong> Officer at the VBIL<br />

monitors email, checking for information received from the fire agencies. The <strong>Information</strong> Officer processes<br />

authorised information from the fire agencies and turns it into FAQs used by call takers to answer queries. 106<br />

All VBIL calls are answered using the FAQ database. Two main responses are used when callers have<br />

queries relating to fires:<br />

■■<br />

■■<br />

The general FAQs are used when a fire is not known or there is no specific current fire FAQ for a particular<br />

fire — in that instance, for example, if a caller says they can see smoke or flames in their area, the call is<br />

dealt with by the call taker reading out the information in the Smoke and Fire FAQ. 107<br />

Where a fire is already ‘known’ to the VBIL and a specific FAQ has been prepared for that fire, based on<br />

information provided by an ICC or the iECC, the call taker provides the caller with information drawn from<br />

the specific FAQ. 108<br />

If the fire reported by a caller is not known, the VBIL call takers are trained to search the external CFA and<br />

DSE websites for information on the fire. If such information appears on the fire agencies’ websites, this<br />

is read to the caller. Standard safety messages (from the general FAQs) are also conveyed to the caller,<br />

if appropriate. If there is no information about the fire in a FAQ or on the CFA or DSE websites or a caller<br />

is reporting seeing flames, or is concerned about the amount of smoke, they are advised to hang up and<br />

ring Triple Zero. 109 The protocol requires that once the call taker has concluded a call with a caller who has<br />

reported flames or smoke in relation to an unknown fire, the call is escalated via the Duty Officer to the iECC<br />

within 15 minutes.<br />

103<br />

165


<strong>2009</strong> <strong>Victorian</strong> <strong>Bushfires</strong> <strong>Royal</strong> <strong>Commission</strong>—Interim Report<br />

5 INFORMATION<br />

5.78<br />

5.79<br />

If, after information from the FAQ on a known fire has been provided to the caller, the caller reports that the<br />

information does not correspond with their experience, or the situation in their area has escalated and they<br />

feel immediately threatened, they are advised to ring Triple Zero. Again, once such a caller has terminated<br />

the call, the call taker escalates the call to the iECC. 110 Alternatively, if the caller does not feel immediately<br />

threatened, but does require more information urgently, their details are taken and their query is escalated<br />

to the iECC within 15 minutes by phone, and a copy of their request is sent by email. When further<br />

information is received from the iECC, it is relayed in a return phone call to the caller, if time permits. 111<br />

The process of escalation was undertaken on a number of occasions on 7 February, but was not always<br />

able to be completed in a timely fashion, or at all, given the extreme demands on call takers and all staff<br />

on the day. 112<br />

VBIL PLANS FOR 7 FEBRUARY <strong>2009</strong><br />

5.80 In preparation for 7 February, the VBIL Duty Officers monitored the information on Fire Web for updates on<br />

weather conditions. Daily iECC briefings were also reviewed to keep up to date on forecast conditions that<br />

might trigger increased calls to the VBIL. Over the course of the week prior to 7 February, it became clear<br />

that the weekend would be one of extremely high fire danger. 113<br />

114<br />

5.81 Plans were put in place to have the VBIL resourced to its highest levels ever for a TFB day. Ms Venters<br />

met with the VBIL Duty Officers on 5 or 6 February to discuss strategies for the weekend, including<br />

contingency plans for resourcing, logistics and IT support, and related issues. 115<br />

5.82<br />

5.83<br />

There is no specific requirement that the VBIL provide Centrelink with advance notice when it is expecting<br />

days of peak demand. 116 Prior to 7 February, Centrelink received a situation report from DHS regarding<br />

the heatwave and an informal email that indicated that Victoria was expecting a high fire danger day<br />

on 7 February. 117 The VBIL did not formally notify Centrelink that its overflow services were likely to be<br />

required. 118<br />

On the morning of 7 February, Ms Christine Millington, Manager Customer Liaison and Education DSE<br />

and Duty Officer at the CSC on 7 February, reviewed and updated the process for activation of overflow<br />

arrangements with Centrelink. 119<br />

VBIL Staffing on 7 February <strong>2009</strong><br />

5.84 During the course of 7 February 45 staff worked at the VBIL call centre in Ballarat, comprising 33 operators<br />

and 12 administrative staff and team leaders. 120<br />

5.85<br />

5.86<br />

5.87<br />

However, perusal of the roster for 7 February demonstrates that at times, including during peak periods<br />

in the afternoon and early evening, the number of call takers who were working dropped below 11.<br />

Between 2:45pm and 3:15pm, for example, the number of staff taking calls dropped to as low as nine.<br />

This is less than the minimum level of 11 call takers required on a code red day under the VBIL’s Service<br />

Level Agreement with DSE. 121<br />

It is difficult to understand why that on a code red day, in light of the information available in the preceding<br />

week about the extreme weather forecast, the VBIL did not roster closer to the top of the 11 to 20 range<br />

for call takers.<br />

Centrelink had shifts in place with up to 26 staff at various times of the day available to take calls from<br />

the VBIL. 122<br />

The events of 7 February <strong>2009</strong> at the VBIL and Centrelink<br />

5.88 Unfortunately, the events of 7 February, despite the best efforts and goodwill of those involved at the VBIL<br />

and Centrelink, unfolded as a sequence of errors.<br />

5.89<br />

The CSC opened at 6:00am. Ms Millington, Duty Officer for the VBIL, recorded a ‘call spike’ in her log book<br />

at 9:00am and increasing activity, including further call spikes, from that time. 123<br />

166


<strong>Information</strong><br />

5.90<br />

5.91<br />

5.92<br />

5.93<br />

5.94<br />

5.95<br />

5.96<br />

At approximately 12:47pm, Ms Millington contacted Centrelink Telephony Network Support requesting that<br />

they commence taking the VBIL overflow calls. Initially, Centrelink expressed hesitation about its capacity<br />

to assist, as its staff were already taking increased volumes of calls due to the flooding in Queensland. 124<br />

At approximately 1:05pm, Centrelink advised that it would activate the overflow arrangements, and<br />

contacted its Geelong call centre and directed it to prepare for activation. 125<br />

At 2:10pm, DSE informed Centrelink it needed to activate overflow arrangements immediately, rather than<br />

within the timeframes provided for in the MOU. Ms Tracey Tozer, Business Manager Telephony Network<br />

Support, Centrelink, informed the Team Leader at the Geelong call centre to activate three experienced staff<br />

immediately. 126 Ms Millington manually directed the VBIL overflow to Centrelink at 2:16pm. At 2:18pm the<br />

overflow was halted. Ms Millington said this was done because it was discovered Centrelink was not able<br />

to access the VBIL database and a request came from Centrelink to halt the activation. 127 The evidence from<br />

Centrelink suggested that the request may only have been to alter the parameters for the overflow. In any<br />

event, the function was turned off. 128<br />

It transpired that, as a result of Centrelink conducting a technology systems upgrade a few days prior to<br />

7 February, Centrelink operators were ‘locked out’ of the DSE database. 129 Centrelink’s practice was to<br />

test its remote access capabilities once a week and the access problem caused by the system upgrade<br />

was not detected until the VBIL requested that Centrelink activate its overflow capacity. 130<br />

With the exception of a few calls received between 2:16pm and 2:18pm, Centrelink operators did not begin<br />

answering the VBIL calls until approximately 5:25pm. To overcome the difficulty caused by Centrelink staff<br />

being unable to access the VBIL database, information was provided to Centrelink by fax but not before<br />

5:25pm, at which time the overflow to Centrelink recommenced. 131 Ms Venters did not know why it took<br />

two hours to commence sending information by fax. 132<br />

Shortly thereafter, the fax machine at the Ballarat Centrelink Centre broke down. This necessitated a<br />

manager from the Ballarat Centrelink office visiting the VBIL CSC to physically convey the documents<br />

back to Centrelink. 133<br />

Ms Carolyn Hogg, Deputy Chief Executive Officer, Centrelink, explained that Centrelink now tests its<br />

systems more regularly and accepted that it should have tested its systems after the upgrade. 134<br />

TIMELY PROVISION OF INFORMATION TO THE CALL CENTRE AND TO VBIL STAFF<br />

5.97 <strong>Information</strong> on current fires is provided to the VBIL by ICCs. The material usually comes directly from ICCs<br />

or the iECC, by email or, less often, by fax or telephone. When received, the information is used to create<br />

a new FAQ, using a template (paragraph 5.74).<br />

5.98<br />

5.99<br />

Once an FAQ is complete, it is published on the FAQ database. Call takers are informed by email or<br />

verbally that a new FAQ is available. FAQs are intended to be created by the CSC <strong>Information</strong> Unit as soon<br />

as practicable after their receipt. The process usually involves copying the information over without retyping.<br />

It is difficult therefore to understand why there were, on occasions, lengthy delays between the provision<br />

of information to the VBIL and the creation of FAQs. 135<br />

Generally, the time required to circulate new and updated FAQs is between 30 minutes and an hour,<br />

depending on the complexity of the information and the number of other incidents being reported.<br />

There may also be a need to clarify or verify information. 136<br />

5.100 The system did not work perfectly on 7 February. On a number of occasions information was slow to reach<br />

the VBIL or slow to be disseminated within the VBIL, or both. Table 5.3 summarises the evidence on the<br />

timeframes during which information was made available on 7 February.<br />

167


<strong>2009</strong> <strong>Victorian</strong> <strong>Bushfires</strong> <strong>Royal</strong> <strong>Commission</strong>—Interim Report<br />

5 INFORMATION<br />

Table 5.3: Timeframes for making information available through the VBIL<br />

Fire<br />

Ignition time<br />

First warning provided to<br />

the VBIL<br />

FAQ created<br />

for new fire<br />

campaign<br />

distributed<br />

to VBIL staff Findings 137<br />

4:19pm 140 Messages not supplied to the VBIL<br />

Kilmore East 11:49am 138 3:25pm [four messages, one<br />

alert and three urgent threat<br />

attached to one email] 139 until 3.25pm under the title ‘Catch‐up<br />

messages, Kilmore … fire’. This<br />

lagged over three and half hours<br />

behind the time of ignition of this fire.<br />

The FAQ was created nearly one hour<br />

after its receipt at the VBIL, adding to<br />

the delay.<br />

Horsham 12:26pm 141 12:46pm [urgent threat] 142 1:25pm 143 The FAQ was created within<br />

approximately 30 minutes of receipt<br />

of the message.<br />

Coleraine 12:36pm 144 1:15pm [urgent threat] 145 1:46pm 146 The FAQ was created within<br />

approximately 30 minutes of receipt<br />

of the message.<br />

Pomborneit–<br />

Weerite<br />

(known earlier<br />

in day as<br />

Camperdown–<br />

Danedite Rd<br />

fire)<br />

Churchill–<br />

Glendonald<br />

Rd Fire<br />

1:17pm 147 2:03pm [urgent threat] 148 2:47pm 149 The FAQ was created within<br />

approximately 45 minutes of receipt<br />

of the message.<br />

1:33pm 150 2:07pm [urgent threat] 151 3:01pm 152 The FAQ was not prepared for<br />

approximately one hour after receipt<br />

of the message.<br />

4:58pm 156 The FAQ was not prepared for<br />

Murrindindi 3:00pm 153 3:49pm [awareness] 154<br />

4:46pm [urgent threat] 155 approximately one hour after receipt<br />

of the message.<br />

4:45pm 160 The FAQ was not prepared for<br />

Redesdale 3:11pm 157 3:40pm [awareness message] 158<br />

3:57pm [urgent threat] 159 approximately one hour after receipt<br />

of the message.<br />

Narre Warren–<br />

Crawley Rd<br />

8:47pm 164 The FAQ was not prepared for<br />

3:32pm 161 6:44pm [alert] 162<br />

8.28pm [urgent threat] 163 approximately two hours after receipt<br />

of the message.<br />

Bendigo 4:34pm 165 5:02pm [awareness] 166<br />

9:15pm [urgent threat] 167 5:35pm 168 The FAQ was created within<br />

approximately 30 minutes.<br />

Beechworth 6:09pm 169 7:05pm [urgent threat] 170 7:44pm 171 The message was not supplied until<br />

approximately one hour after ignition.<br />

The FAQ was not prepared for<br />

approximately 45 minutes.<br />

Source: Statements of Ms Venters, Mr Rees, Mr Caughey and Mr Waller and tenders and oral evidence of Ms Venters 172<br />

168


<strong>Information</strong><br />

5.101 Table 5.3 indicates that on some occasions on 7 February, short periods elapsed between the ignition<br />

of fires, provision of warning messages by the CFA or DSE to the VBIL, and creation of relevant FAQs.<br />

However, on other occasions, there were significant delays. The FAQ for the Kilmore East fire was not<br />

created for the VBIL staff until 4:19pm. This is despite the fact that Ms Millington’s log reveals that at 12:39pm<br />

on 7 February, she contacted Ms Henshaw of the CFA <strong>Information</strong> Unit to report that the VBIL had received<br />

calls about the Kilmore East fire, which was not yet on the CFA website. Ms Henshaw, who had access to<br />

the Incident Management System live feeds concerning fire information was able to supply Ms Millington<br />

with some information about the fire and indicated that further information would be available. Nevertheless,<br />

messages were not supplied to the VBIL until 3:25pm and the FAQ was not created until 4:19pm. 173<br />

5.102 Ms Venters said the different time frames may be explained by virtue of the fact that the Horsham and<br />

Coleraine fires were earlier in the day, and during a period when less information was being received at the<br />

CSC. 174 She said it was also a case of people having to ‘process an immense amount of information’. 175<br />

VBIL Calls answered and abandoned on 7 february <strong>2009</strong><br />

5.103 The VBIL experienced unprecedented demand — 12,846 calls were presented to the VBIL from 6:00am<br />

to midnight on 7 February. This compares with 2981 calls on 10 January <strong>2009</strong> (during the Delburn fires)<br />

and 2544 calls on 11 January 2007 (during the Great Divide fires). 176<br />

5.104 The statistics for the VBIL’s performance on 7 February reveal that the CSC fell well short of its performance<br />

benchmarks. 177 There were high numbers of calls abandoned. Of the 12,846 calls made to the VBIL on<br />

7 February:<br />

■■<br />

■■<br />

■■<br />

■■<br />

■■<br />

731 calls were answered by the Interactive Voice Response (a recorded message service whereby<br />

callers can ‘self help’ by selecting options from a menu without the need to speak to an operator)<br />

27 calls were made to the after-hours Interactive Voice Response service<br />

902 calls were transferred to the overflow queue (Centrelink)<br />

9879 callers entered the operator queue<br />

178<br />

1307 calls were terminated before entering the operator queue.<br />

5.105 Of the 9879 calls that were queued, waiting to speak with an operator, only 1754 were eventually answered<br />

and 8125 were terminated while the caller waited in the operator queue. 179<br />

5.106 Ms Venters said these figures demonstrated an abandonment rate of 82.2 per cent (8125 calls abandoned<br />

from the 9879 calls waiting to speak to an operator). 180 The abandonment rate is even higher if the 1307<br />

calls terminated by callers before they entered the queue are included. Of course, those callers may have<br />

terminated their calls by choice on hearing the recorded messages that the VBIL was experiencing heavy<br />

demand and that callers might instead ring Triple Zero or call back on another occasion. Further, this figure<br />

does not include callers who were unable to get a line because the number of people calling the VBIL<br />

call centre exceeded the 90 lines available.<br />

5.107 There were also long delay times before calls were answered. The average wait time was 11 minutes<br />

25 seconds. The longest recorded waiting time was 16 minutes and 22 seconds. 181<br />

5.108 Due to the technical difficulties on the day, the data on calls overflowed to Centrelink on 7 February is<br />

incomplete. Centrelink staff answering the VBIL calls would ordinarily log calls in a DSE database in the<br />

same way as the VBIL operators. Due to the failure of the remote access facility, Centrelink staff were<br />

unable to do so on 7 February. 182<br />

5.109 Other sources of data are also incomplete or inconsistent. <strong>Information</strong> on call levels for 7 February first<br />

supplied by Centrelink to the VBIL in April <strong>2009</strong> was incorrect. 183 In June <strong>2009</strong>, Centrelink obtained data<br />

from Telstra indicating that Centrelink received 117 overflow calls from the VBIL and answered 62 of these,<br />

but these figures are also incomplete as there were no statistics available after 9:00pm on 7 February. 184<br />

The VBIL has alternative data indicating that 902 calls were overflowed to Centrelink, but it was suggested<br />

in evidence that this could not be relied on either. 185<br />

169


<strong>2009</strong> <strong>Victorian</strong> <strong>Bushfires</strong> <strong>Royal</strong> <strong>Commission</strong>—Interim Report<br />

5 INFORMATION<br />

5.110 Data from Centrelink’s national emergency database (which Centrelink staff filled out on 7 February,<br />

albeit not uniformly) shows that at least 124 calls were answered. 186<br />

5.111 Further, it has also come to light that Centrelink sought information from Telstra that might have enabled<br />

it to capture or recreate the relevant phone records. However, Telstra were unable to recreate the data,<br />

as it was not sought by Centrelink within 20 days, the normal period before records are destroyed. 187<br />

5.112 The data available on calls answered by Centrelink does not appear to match the recollections of staff as<br />

to the level of activity. The Team Leader on shift at the Geelong Centrelink call centre recalls that the calls<br />

were constant and staff were fully occupied. 188<br />

5.113 It is also not possible to determine accurately the abandonment rate of calls to Centrelink because of<br />

the doubts about the core statistics. However, taking one version of the Centrelink figures at face value<br />

(117 calls received and 62 answered), while noting the significant doubts about the accuracy of this<br />

material, the abandonment rate for calls overflowed to Centrelink on 7 February could have been as high<br />

as 47 per cent. 189 The MOU requires at least 80 per cent of calls to be answered within 60 seconds. 190<br />

191<br />

5.114 Staff at the VBIL call centre maintained logs of calls taken in the Centre. The call logs for 7 February reveal<br />

that the VBIL staff were placed under considerable pressure. 192 The log reveals distressing examples of calls<br />

received from people in circumstances of significant danger and stress. Callers included people seeking<br />

advice about evacuation for themselves and relatives; young people at home without their parents; people<br />

desperately seeking information about the fate of loved ones; callers whose home was under ember attack;<br />

and people reporting fires very close to their homes anxiously seeking assistance or advice. Some callers<br />

were angry and frustrated about the lack of information. 193 The VBIL staff were offered counselling in the<br />

aftermath of this difficult day. 194<br />

5.115 Witnesses attested to difficulties in reaching the VBIL and deficiencies in the information supplied by the<br />

service. Dr John Ferguson of Buxton called the VBIL five times, and when he got through eventually was<br />

placed on hold. He said the operator did not know where Buxton was and told him that there was a small<br />

grass fire in Murrindindi. He said this did not match his own observations about the threat at that time. 195<br />

Mrs Joan Davey attempted to call the VBIL, desperately seeking information about her son’s family and<br />

the fires at Kinglake. None of her calls were answered and she was placed on hold for up to two hours. 196<br />

Dr Lachlan Fraser of Marysville called the VBIL about the fire threat to Marysville. He was on hold for about<br />

20 minutes, and when his call was answered, the operator had to look up where Marysville was. 197<br />

5.116 There appears to have been no way for VBIL staff to isolate the urgent from the non-urgent calls on the<br />

night, with the result that call takers were occupied with trivial requests at a time when they were also<br />

fielding calls from members of the public in life-threatening situations. 198<br />

VBIL Debriefs — past and present<br />

5.117 The Joint CFA/DSE <strong>Information</strong> Review referred to in paragraph 5.38 also considered the VBIL’s<br />

performance. It made the following recommendations to address concerns about the speed of information<br />

flow, consistency of formatting, the demand on the system and the desirability of capturing valuable<br />

information from callers in fire affected areas:<br />

That the protocols covering the forwarding of authorised information and the formats in which that<br />

information is presented be reviewed.<br />

The use of recorded appropriate, updated messages by VBIL be examined as a method of dealing<br />

with caller demands.<br />

The possibility for formal processing and use of intelligence gathered by VBIL as part of the information<br />

flow system be examined. 199<br />

170


<strong>Information</strong><br />

5.118 Some aspects of the recommendations made in 2006 have been implemented, but it is clear that speed<br />

of information flow remains a problem. Debriefs have been conducted with VBIL staff since the January–<br />

February <strong>2009</strong> fires. The report of the debriefs reveals that some of the same issues have been raised again.<br />

Call takers on 7 February reported the following concerns:<br />

■■<br />

■■<br />

■■<br />

■■<br />

■■<br />

FAQs were too large and difficult for operators to use<br />

operators were not provided with sufficient up-to-date information and the information<br />

that they did receive was sometimes unclear<br />

inconsistent naming of fires created confusion for operators<br />

there was a lack of well-trained, experienced call operators<br />

200<br />

high stress levels due to the failure of the Centrelink overflow capability.<br />

5.119 The ability of the VBIL to offer a surge in capacity to meet extreme demand was severely hampered on<br />

7 February due to physical constraints (numbers of phone lines and workstations) and staffing levels.<br />

5.120 The State accepted Counsel Assisting’s proposed recommendation that more staff should be rostered<br />

on to answer calls during extreme events and that all endeavours should be made to produce FAQs<br />

and disseminate them to call takers as quickly as possible. 201<br />

5.121 The State indicated that it is considering expanding the VBIL to an ‘all hazards’ <strong>Victorian</strong> Emergency<br />

<strong>Information</strong> Line. In this context, it intends to examine the operations and procedures of the VBIL,<br />

including information technology, telephony and service standards, and protocols on receipt of<br />

information. 202 Further information on these matters will be adduced in the subsequent hearings<br />

of the <strong>Commission</strong>.<br />

5.122 The time frames for providing information to the VBIL and creating FAQs within the VBIL should be improved.<br />

Counsel Assisting proposed recommendations to improve the protocols for handling those links in the<br />

information chain. The State agreed improvements are necessary, but suggested that the focus ought to<br />

be on staff levels and the currency of information provided to the VBIL. 203<br />

5.123 To improve the activation of overflow arrangements with Centrelink, the Commonwealth proposed that<br />

DSE be obliged to provide formal advance warning of the potential activation of Centrelink overflow demand<br />

as soon as practicable, and that Centrelink and DSE share information about total call demand, overflow<br />

parameters to be employed, and the staffing capacity of both agencies. 204<br />

RECOMMENDATION 5.5<br />

The State ensure the <strong>Victorian</strong> Bushfire <strong>Information</strong> Line is funded to enable it to provide greater surge<br />

capacity during extreme events and to improve the efficiency of its internal information function.<br />

171


<strong>2009</strong> <strong>Victorian</strong> <strong>Bushfires</strong> <strong>Royal</strong> <strong>Commission</strong>—Interim Report<br />

172<br />

Source: Simon Schulter, courtesy of The Age

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!