Author Topic: Interesting Fire and Emergency Related Paging (Read 4727890 times)

alphaone · « **Reply #250 on:** October 16, 2007, 04:00:38 PM »

MFS: Call Sign ELZ331 changed to 331. MFS Elizabeth 331 Response

Any one know what this is about?

Zippy · « **Reply #251 on:** October 16, 2007, 04:12:19 PM »

15:35:09 16-10-07 MFS: INC # 40 - 16/10/07 15:35,RESPOND GRASS FIRE,PARNDANA ,PARNDANA KI, MAP 087 F 3 ,,FIRE AT MT BROWN,PARN19*CFSRES: CFS Parndana Response

**PARN19**

probie_boy · « **Reply #252 on:** October 16, 2007, 09:30:26 PM »

1908906 17:44:43 16-10-07 MFS: INC # 49 - 16/10/07 17:44,RESPOND Vehicle Accident,RAZOR BACK RD,MEADOWS, MAP 000 0 0 ,,2-3KM FROM CUTHILL RD,MDWS19 MBKR19 ECHG00*CFSRES: CFS Echunga Response

this must be the new codes. from this message im gathering codes ending in 19 are rescue still and 00 are standard fire response.

1925389 20:41:26 16-10-07 MFS: INC # 61 - 16/10/07 20:41,RESPOND Smoke in Area,WANDEARAH RD,PORT PIRIE, MAP 0 0 0 ,,BEHIND THE SCHOOL,501*CFSRES: MFS Pt Pirie

But i also noticed that MFS haven't changed. I dunno

Morgan · « **Reply #253 on:** October 16, 2007, 09:52:27 PM »

Quote

But i also noticed that MFS haven't changed. I dunno

you can't teach and old dog new tricks

CFS_Firey · « **Reply #254 on:** October 16, 2007, 09:54:15 PM »

Quote from: Morgan on October 16, 2007, 09:52:27 PM

Quote
But i also noticed that MFS haven't changed. I dunno

you can't teach and old dog new tricks

Does that make the CFS a young dog?

Comms · « **Reply #255 on:** October 17, 2007, 12:27:58 AM »

MFS codes have also changed, just not retained yet. Some examples follow.

INC # 68 - 16/10/07 23:48
RESPOND Vehicle Accident
GRANGE RD MAP 116 F 3
SEATON
INT OF TAPLEYS HILL RD.
WDV249

DAILY INC. NO. 65 - 16/10/07 22:07
RESPOND ALARM 11/134
MYER CENTRE
NORTH TCE MAP 4 A 4
ADELAIDE
FIP S FIRE CONTROL ROOM PANELS 1--7

ADL205 ADL201 ADL204 ADL203

JC · « **Reply #256 on:** October 17, 2007, 06:14:15 AM »

What has brought on the change.

Zippy · « **Reply #257 on:** October 17, 2007, 08:00:21 AM »

i can think of a few people who requested this change...but i think there were a whole lot more!

tis good to see its done , nice work mfs comcen

Alan (Big Al) · « **Reply #258 on:** October 17, 2007, 09:39:56 AM »

SES changing?

Pipster · « **Reply #259 on:** October 17, 2007, 11:23:06 AM »

The short names on the pager messages were what we were promised from the start of the new CRD system.....but when the new CRD system commenced, it was found there were software issues, and short names couldn't be used without changes being made to the software.

At least two Regions were insisting on the short names (I am guessing the others did too - but I haven't heard anything from them about it)

It is good to see the change has now occurred.

Pip

mengcfs · « **Reply #260 on:** October 17, 2007, 11:25:57 AM »

Quote from: Morgan on October 16, 2007, 09:52:27 PM

Quote
But i also noticed that MFS haven't changed. I dunno

you can't teach and old dog new tricks

But you're never too old to learn

mack · « **Reply #261 on:** October 17, 2007, 01:00:39 PM »

Quote from: probationary one on October 16, 2007, 09:30:26 PM

But i also noticed that MFS haven't changed. I dunno

perhaps MFS are smart enough to remember a few numbers... and dont need to change a perfectly good system..

has everyone got the info re: that.. i believe it is on the CFS website...

good news is with the new system we should at least be able to tell when rescue, hazmat and tankers have been responded still...

Darius · « **Reply #262 on:** October 17, 2007, 01:07:58 PM »

Quote from: probationary one on October 16, 2007, 09:30:26 PM

this must be the new codes. from this message im gathering codes ending in 19 are rescue still and 00 are standard fire response.

it was explained in a fax to all brigades in the group back on 20th August ("brigade short names"). For the 2 digit suffix 00 is the default/generic one replacing 24. The others (19, 28, 42 etc) remain the same as before. There are more changes concerning CRD coming very soon, not quite finalised yet though.

safireservice · « **Reply #263 on:** October 17, 2007, 04:49:06 PM »

MFS have seemed to have changed as well.

Morgan · « **Reply #264 on:** October 17, 2007, 06:17:53 PM »

Quote

Does that make the CFS a young dog?

young and agile unlike another service that could be sonsidered old and stale

mack · « **Reply #265 on:** October 17, 2007, 07:00:50 PM »

Quote from: Mundcfs on October 17, 2007, 09:39:56 AM

SES changing?

meant to be some time

Zippy · « **Reply #266 on:** October 18, 2007, 06:40:07 PM »

09:15:03 18-10-07 R4HQ STLN: INFO ONLY. STIRLING NORTH WILL BE DUEL RESPONDED TO PORT AUGUSTA WITH MFS FOR FIRE CALLS FOR DURATION OF WATER DISRUPTION - DUE TO BURST MAINS 18/10/2007 9:14:53 AM CFS Stirling North Info

Port Augusta has no water at all.

mack · « **Reply #267 on:** October 18, 2007, 07:49:45 PM »

MFS: INC # 86 - 18/10/07 19:04,RESPOND Vehicle Fire,208 ESPLANADE ,SEAFORD, MAP 195 F 14
,,,SEAF00 MRPH00 CDN431*CFSRES:

hahaha seafoo......... everyone knows what im talking about...

chook · « **Reply #268 on:** October 18, 2007, 07:55:41 PM »

Not sure Mack is that the same as SNAFU?

Zippy · « **Reply #269 on:** October 18, 2007, 08:04:05 PM »

19:23:58 18-10-07 MFS: *CFSRES: RESPOND OPERATION BINGLE, PORT LINCOLN AIRPORT, 18/10/2007 7:23:45 PM MFS Pt Lincoln Response

wonder what this is

an operation with a scripted stuff up?? lol or a real incident gone pear shaped lol

Pipster · « **Reply #270 on:** October 18, 2007, 09:00:15 PM »

They had the real incident yesterday...and the training exercise today!!

Pip

Zippy · « **Reply #271 on:** October 18, 2007, 09:02:59 PM »

lol.. they musta felt "knew we should planned it a week early"

Zippy · « **Reply #272 on:** October 26, 2007, 11:34:21 PM »

removed by request.

littlejohn · « **Reply #273 on:** October 27, 2007, 07:58:48 AM »

Quote from: Zippy on October 26, 2007, 11:34:21 PM

....soo why not just see WHEN the pager goes...how many people rock up...?

I am GUESSING that page was sent becuase a fire ban was declared, and no one (or not enough) has bothered to let the BDO know if they're available. (I'm also assuming it's a statewide practise to have a radio sched on a fire ban day?)

If you think about why those scheds exisist - so the group (GOs, DGOs, captains etc) have an accurate idea of what resources area available in the instance of an incident, it strikes me as quite fair to give the brigade a rev for being a bit slack.

Waiting ten minutes after a page has gone out to discover that a brigade has no crew is unneccessary on a high fire risk day. Similarly, if you know a neighbouring brigade is low on numbers you can make a conscious effort to fill your own truck, with the knowledge that you'll lose a couple of crew when you reach the fireground.

Lots of good reasons to have a fire ban sched. Bit harder getting crew to keep you informed!

rescue5271 · « **Reply #274 on:** October 27, 2007, 11:49:30 AM »

I can never understand why we still have to see if we can get crews on a fire ban day by doing a radio check or call captains...We should treat each day as the same and if its a fire ban then you know you have to page extra units....

Author Topic: Interesting Fire and Emergency Related Paging (Read 4727890 times)

probie_boy

rescue5271