Acknowledging WFAM responses

Started by Zippy, December 05, 2008, 08:14:01 AM

Previous topic - Next topic

Zippy

MFS: *CFSRES INC016 05/12/08 09:09,RESPOND Private Alarm,7 BRAUN DR,HAHNDORF MAP 159 K 9 TG128,DEFAULT MT BARKER & HAHNDORF,LTHT00 OAKB00

i think this could be classed as a 1 in 300 event? mt barker > default  :-o

CFS_Firey

Quote from: Zippy on December 05, 2008, 08:14:01 AM
MFS: *CFSRES INC016 05/12/08 09:09,RESPOND Private Alarm,7 BRAUN DR,HAHNDORF MAP 159 K 9 TG128,DEFAULT MT BARKER & HAHNDORF,LTHT00 OAKB00

i think this could be classed as a 1 in 300 event? mt barker > default  :-o

Probably more likely a mix up in communications...

safireservice

Quote from: CFS_Firey on December 05, 2008, 02:15:40 PM
Quote from: Zippy on December 05, 2008, 08:14:01 AM
MFS: *CFSRES INC016 05/12/08 09:09,RESPOND Private Alarm,7 BRAUN DR,HAHNDORF MAP 159 K 9 TG128,DEFAULT MT BARKER & HAHNDORF,LTHT00 OAKB00

i think this could be classed as a 1 in 300 event? mt barker > default  :-o

Probably more likely a mix up in communications...
HAHN MBKR RESPOND FIRE ALARM ST PAULS LUTHERAN, HOMES 7 BRAUN DRIVE, HAHNDORF *CFSRES:, FIP
ALARM *WFAM*, 05/12/2008 09:07:40

Maybe the didnt acknowledge the original page?
Treat everyone as if they are an idiot, until they prove you otherwise.

OMGWTF

Quote from: safireservice on December 05, 2008, 03:22:23 PM
Quote from: CFS_Firey on December 05, 2008, 02:15:40 PM
Quote from: Zippy on December 05, 2008, 08:14:01 AM
MFS: *CFSRES INC016 05/12/08 09:09,RESPOND Private Alarm,7 BRAUN DR,HAHNDORF MAP 159 K 9 TG128,DEFAULT MT BARKER & HAHNDORF,LTHT00 OAKB00

i think this could be classed as a 1 in 300 event? mt barker > default  :-o

Probably more likely a mix up in communications...
HAHN MBKR RESPOND FIRE ALARM ST PAULS LUTHERAN, HOMES 7 BRAUN DRIVE, HAHNDORF *CFSRES:, FIP
ALARM *WFAM*, 05/12/2008 09:07:40

Maybe the didnt acknowledge the original page?


Yeh, whether they actually responded or not, im guessing they obviously didn't acknowledge there alarm call.


Must have been contagious yesterday;

MFS: *CFSRES INC030 05/12/08 14:27,RESPOND Vehicle Accident,53/57 MURRAY ST,NURIOOTPA MAP 0 0 0 TG095,KAPUNDA SES DEFAULT FOR NURI,CAR V MOTORBIKE,KAP029 NTPA19 CFS Angaston Group Officers Response

Robert

#4
Quote from: OMGWTF on December 06, 2008, 05:58:39 AM
Quote from: safireservice on December 05, 2008, 03:22:23 PM
Quote from: CFS_Firey on December 05, 2008, 02:15:40 PM
Quote from: Zippy on December 05, 2008, 08:14:01 AM
MFS: *CFSRES INC016 05/12/08 09:09,RESPOND Private Alarm,7 BRAUN DR,HAHNDORF MAP 159 K 9 TG128,DEFAULT MT BARKER & HAHNDORF,LTHT00 OAKB00

i think this could be classed as a 1 in 300 event? mt barker > default  :-o

Probably more likely a mix up in communications...
HAHN MBKR RESPOND FIRE ALARM ST PAULS LUTHERAN, HOMES 7 BRAUN DRIVE, HAHNDORF *CFSRES:, FIP
ALARM *WFAM*, 05/12/2008 09:07:40

Maybe the didnt acknowledge the original page?


Yeh, whether they actually responded or not, im guessing they obviously didn't acknowledge there alarm call.


Must have been contagious yesterday;

MFS: *CFSRES INC030 05/12/08 14:27,RESPOND Vehicle Accident,53/57 MURRAY ST,NURIOOTPA MAP 0 0 0 TG095,KAPUNDA SES DEFAULT FOR NURI,CAR V MOTORBIKE,KAP029 NTPA19 CFS Angaston Group Officers Response


We were mobile when the page went out :? (Barker), was a stuff up with MFS Comms when Hahndorf requested a Default.
Funny we got a mouth fall from the staff wen we arrived, asking what took the fire service so long to respond, when the station is only 2min down the road. She apologised after we said we were from Mt Barker and explained that Hahndorf was unable to crew etc.


Zippy

#5
im pretty sure that comcen did the right thing,  5min clock....radio in or ring in before 5mins  (yes theres slack operators, but seems like that particular call had a on the ball Adelaide fire operator).

The pager message may not say its from MFS, but MFS recieve WFAM and (MBKR:) Fixed Alarm Panel fire calls and create the job without sending out a job number. Hence the 5min clock still applys. They DO know instantaneously when any monitored fire alarm goes off in the state, within technological reason ;))

Alex

Quote from: Robert on December 06, 2008, 12:28:57 PM
We were mobile when the page went out :? (Barker), was a stuff up with MFS Comms when Hahndorf requested a Default.


No stuff up mate, i should know. Neither brigade booked in with comms, so both were  defaulted. That was before Barker 24p booked mobile on radio at 0911.

Robert

#7
Hey Alex, Funny  :roll: Thats what we got told when we inquired about it,  I think it was a bit quick on the default tho but anyhow. cheers rob




Zippy

you might notice that, that particular WFAM panel's clock is umm 2 minutes fast (Fire detected:0905)....and Littlehampton/Balhannah received there page's at 0910.

Alex

#9
1908904 09:05:11 05-12-08 HAHN MBKR RESPOND FIRE ALARM ST PAULS LUTHERAN, HOMES 7 BRAUN DRIVE, HAHNDORF *CFSRES:, FIP ALARM *WFAM*, 05/12/2008 09:07:40  

1909018 09:10:15 05-12-08 MFS: *CFSRES INC016 05/12/08 09:09,RESPOND Private Alarm,7 BRAUN DR,HAHNDORF MAP 159 K 9 TG128,DEFAULT MT BARKER & HAHNDORF,LTHT00 OAKB00  

You got your 4 minutes [and a little more]... Dont really see what the problem is. Theres almost never a problem with Barker, usually phone in and all is sweet. Im guessing you guys were racing the clock to ack page when mobile, just didnt quite make it.


But don't blame us for your brigades slight mess up, i dont think anyone was having a go at you... We already cop enough rubbish.

Anyway, hope all is well mate.

Robert

#10
Not having ago at anyone, just going on information we got told, we have never had to ring in before with WFAM Alarms???. 

Alex

WFAM alarms have always had to be acknowledged. Alarms from your station; ie Barker Central [i think it is?] dont have to be, as we dont even know about them until you book mobile.

Robert

Alex, We have never been told that we had to acknowledge WFAM alarms. Cheers for clearing this up, will pass on to the rest of the officers.....

Alex

 :-o Wow, big mess up in communications there somewhere then. That oughta clear it up no probs.

Robert

Quote from: Alex on December 06, 2008, 01:51:51 PM
:-o Wow, big mess up in communications there somewhere then. That oughta clear it up no probs.

This is just typical of the CFS, lack of communication with the front line guys. funny we have the most WFAM/ fixed alarm in our area, and the CFS Comms/tecs Don't tell us anything. We have sent a please explain through the chain to Gary Bau...

mengcfs

We have two premises on WFAM and one direct to station.  Our Brigade has never been advised on what to do on turn out of a WFAM in regards to communications. Albeit common sense prevails and we contact AF to book mobile regardless. Thanks for clearing it up Alex. Nice to know we are doing the right thing even if it's not on a 'formal' piece of paper. :wink:

CFS_Firey

Quote from: Robert on December 06, 2008, 01:46:10 PM
Alex, We have never been told that we had to acknowledge WFAM alarms. Cheers for clearing this up, will pass on to the rest of the officers.....

Likewise, we were never told that either.  When the WFAMs were first being installed we asked SOC what the procedure was, and although there wasn't an official one, we were told to treat them the same as fixed line alarms (ie, no need to acknowledge the page).
Might be a good idea to send a memo out to all brigades with WFAM alarms.

Alex

Thats very interesting then guys, i wonder what CFS's stand on it is then, hopefully someone from CFS is watching/reading...

But beware...the procedure in comcen is to default if no acknowledgment.

Hair

Have been told by Region to acknowledge page with AF or be defaulted.
Also, when you reset alarm at premises, contact AF via radio or landline to validate alarm has reset BEFORE returning to station

6739264

So, in this day and age, all we need is something automated... like a big "Ack Page" button connected to the FSE.
To think they employed me as a drooling retard...