Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Zippy

Pages: 1 [2] 3 4 5 ... 100
26
Mmm interesting. Looks like they have accidentally created a saas event and then attached you to a "saas job".

There is no "assist saas" event type in cad for fire or ses attendance, hence why we are seeing a lot of "assist resident" with further details saying the job is assisting ambos.

That job "request saas assist" is actually used to send a message to the Ambos for them to attend a fire job  in 'interCAD'' which is the link between safire, saas and spoil when SACAD is brought fully online.

Hope that makes sense.

I read from that: operator error :P

27
SA Firefighter General / Re: Ammusing pager message.
« on: January 04, 2012, 05:12:27 PM »
Fingers crossed someone will wake up to replace it with only one instance of "4TH ALARM"

All that text is a waste of space, and cause for concern when good information can be missed.

28
SA Firefighter General / Re: Birdwood QRV
« on: December 21, 2011, 09:30:16 PM »
Clown fire service

29
SA Firefighter General / Re: Birdwood QRV
« on: December 20, 2011, 10:38:05 AM »
Do areas with a brand new 300,000 truck get a call every month? :P

30
SA Firefighter General / Birdwood QRV
« on: December 18, 2011, 10:58:38 AM »
it is neither a "need" nor a replacement for an older appliance...

That equals "Kulkami / Marama"

31
SA Firefighter General / Re: SACAD
« on: December 17, 2011, 10:49:15 PM »
Then we really will see CAD go into meltdown.....

Not if a decent multiple incident procedure is put in place for all 3 services covered by the safecom comcen.

Almost every member that comes in contact with a GRN radio or appliance leadership should become well versed in multiple incident procedures.

You could send every priority 2 job as a pager message to a Group Duty Officer/Base for local resource assignment... that's an option that'd take the strain off Adelaide Fire.

32
SA Firefighter General / Re: SACAD
« on: December 17, 2011, 04:17:49 PM »
A few SES units seemed to self respond during todays storm event. SES SCC was open, wonder how that all went with SCC dispatching work, and if AF went to dispatch if that resource had been tasked by SCC??

We all know what a positive and a negative equal... When two systems collide who do we call...captain planet...

33
SA Firefighter General / Re: Ammusing pager message.
« on: December 17, 2011, 12:20:40 PM »
An undeveloped idea to follow, but it could work!

All "groups" (1 brigade at least) included in a 3 Alarm or higher incident, could be given "Advisory", "Alert/Active Standby", "Contained" and "Stop" message for information purposes only. This would make information flow pretty awesome, and would mean brigades would not have to self-monitor incidents.

E.g

IC calls a 3rd alarm, as part of that, SACAD could look at which brigades have gone, and then send a message to all the relevant group info addresses:

MFS: INFO ONLY: Escalating incident at Lenswood. Await further notifications.

MFS: CFSRES: Active Standby for Lenswood incident. Await further notifications.

MFS: INFO ONLY: Lenswood incident contained. Cancel Active Standby.

MFS: STOP MSG: Stop recieved for Lenswood Incident.

34
SA Firefighter General / Re: Ammusing pager message.
« on: December 16, 2011, 03:10:09 PM »
MFS: *CFSRES INC0042 16/12/11 10:16 RESPOND GRASS FIRE, MAWSON RD CHERRYVILLE,MAP:ADL 123 C 3,TG 140, ==IN VICINITY OF TRACK 9. REPORTED SMOKE FROM AIRCRAFT == Alarm level updated to 2 ==ADDED FOR G/O KIESSLING

Lol well outside his realm, heard over the radio he was trying to get lofty almighty team in before the 2nd alarm arrived.... Probably get Norton Summit, Summertown, Oakbank/Balhannah & Cudlee Creek in first....

35
SA Firefighter General / Re: SACAD
« on: December 12, 2011, 08:58:52 AM »
Google says 2 hours minimum before backup arrives on scene.

Coober Pedy and Roxby Downs should be treated just like Whyalla. Isolated.

2 tankers and a BWC seems a bit light on for Coober...

It'd be worth making the brigade retained, with at least 3 tankers supported by a 13000L BWC.

Any one or two truck that goes out of town for a long distance RCR. There would always be two trucks back home.


36
SA Firefighter General / Re: CFS using K-codes
« on: December 10, 2011, 08:11:32 AM »
How about a button box?

(SHOCK. HORROR.)

+1

One less sport stadium can buy 100,000 of these.

37
SA Firefighter General / Re: Ammusing pager message.
« on: December 09, 2011, 04:55:01 PM »
Lofty group can never escape the wrath of the Port Augutta Region.

38
SA Firefighter General / Re: SACAD
« on: December 07, 2011, 10:20:26 AM »
MFS: *CFSRES INC0050 07/12/11 10:59 RESPOND VEHICLE FIRE INC LPG, STURT HWY BLANCHETOWN,MAP:C/211 54,TG 205, :BLAN34 SWAN34 WAIKPUMP

truck at weigh bridge west of town

BLAN: *CFSRES: MORE CREW REQUIRED RESPOND BLANCHETOWN STN 07-12-11 11:04

MFS: *CFSRES INC0050 07/12/11 10:59 RESPOND VEHICLE FIRE INC LPG, STURT HWY BLANCHETOWN,MAP:C/211 54,TG 205, ==WAIK19 RESPOND DEFAULT, SWANREACH DID NOT ACKNOWLEDGE :WAIK19


Lets take a look at Waikerie's actual resources, as right now, its waikerie Pumper and Blanchetown 34 Mobile to the incident.

WaikeriePUMP = 2000L Water. 4 BA.
Waikerie19   = Rescue/Hazmat/BA/Lighting/etc. No Water.
Waikerie24   = 2000L Water.
Waikerie14   = 450L Water.

From that assessment, all that Waikerie19 can offer to a Vehicle fire is bums on seats + extra BA. No additional water.

Dependant on the onsite water reticulation and the scale of the fire...would it be better to send Waikerie 24 as the backup appliance to a vehicle fire instead of the 19.

Again a case of questionable input of data.

There i think needs to be a clear way of seeing which appliance carries only water, or carrys water AND specialist equipment, or only specialist equipment.

19    CFS Rescue Vehicle (Standalone Rescue)
28       CFS Hazmat Vehicle (Standalone Hazmat)
42    BWC 4000L Plus

Everything else should be (or include the above 3 in plain english terms):

Pumper
Pumper-Tanker (34P, 24P)
Tanker (34, 24)
Light Tanker (14, QRV)

E.g  Strathalbyn Pumper-Tanker 1, Pumper-Tanker 2, Light Tanker


An ideal situation would be to see SACAD with 95-100% reasonable data, so that minimal rework will ever have to be done on a very shitty day.

39
SA Firefighter General / Re: SACAD
« on: December 06, 2011, 11:41:40 AM »
42 makes sense. Thats a bulk water carrier, heaps of them, no differences.  (Gets us beyond the whole BWC9 BWC13 ordeal)

Meanwhile there are only 2 or 3 actual "28" appliances.

I'm in a brigade that has X number of appliances, but SACAD says we have one more, and that's a 28.

therefore, all excess 28's should be deleted of the system and the dual purpose appliances (normally a 34P) should be 34P tagged with hazmat capability.

40
SA Firefighter General / Re: CFS using K-codes
« on: December 04, 2011, 10:31:26 AM »
SOP 7.1 Dated August 2011 says K-Codes are not to be used by CFS resources.....



Cool, looks like they weren't then.

Alex is right, they were only used by Adelaide fire ;)  

However, i fully back the idea of using K-Codes on regional talkgroups now. After hearing all the dribble by surrounding groups and even local brigades, it's a waste of valuable attention that Adelaide Fire could spend elsewhere during a busy period.

CFS needs to get into the mind set, that we need to keep our messages *VERY* brief, unless one of three things happen:

- Incident Escalation. (This in itself should be kept to 2nd Alarm, 3rd Alarm, 4th Alarm, or Specialist resources)
- Adelaide Fire wanting to clarify information from a particular resource calling.
- The resource wanting to gain further information.

The example of Sturt group appliances not talking to Adelaide fire, undermines the actual need for SACAD.

"Adelaide Fire Strathalbyn 34P"
"Send Strathalbyn 34P"
"Strathalbyn 34P K1 incident 81"
"Roger, Strathalbyn 34P K1, Adelaide Fire Out"


"Adelaide Fire, Strathalbyn 34P"
"Send Strathalbyn 34P"
"Strathalbyn 34P, K5"
"Roger out"


Nice and Simple.

Whats even better you say? effing mobile comm terminals.

41
SA Firefighter General / Re: SACAD
« on: December 01, 2011, 09:35:48 PM »
First clear example of how the system works if acknowledgement/mobile isnt done.

MFS: *CFSRES INC0185 01/12/11 22:22 RESPOND GRASS FIRE, PORT ST GLADSTONE,MAP:SGL 1 H11,TG 066, ==FIRE IN THE CREEK OPPOSITE 92 GLADSTONE ST :AIRDESK GLAD34 GRGT24 :

12 minutes later... MFS: *CFSRES INC0185 01/12/11 22:33 RESPOND GRASS FIRE, PORT ST GLADSTONE,MAP:SGL 1 H11,TG 066, ==FIRE IN THE CREEK OPPOSITE 92 GLADSTONE ST ==INITIAL ALARM UNITS FAIL TO ACK :AIRDESK CALT24 LAUR34 :

6 mins later... MFS: STOP FOR INC185 (all except Gladstone)

20mins later... MFS: CALT24 - STOP FOR INC185 (to Caltowie)

42
SA Firefighter General / Re: Interesting Fire and Emergency Related Paging
« on: November 17, 2011, 02:52:51 PM »
Quote
SACAD offline and now this

MFS:*CFSRES: INC 082 COONALPYN & TAILEM BEND RESPOND HOUSE FIRE 49 WARRENGIE DR MENINGIE KITCHEN FIRE. BA OPERATORS REQUIRED - CFS Tailem Bend Response

Whats the problem with this message...I have been out at a job all night so might be missing something. No Brigade codes?

Problems
==============
- No Allocated talkgroup to the incident. Quite important at group boundaries.
- No automated allocation of resources, manually driven.
- Slower message creation when multiple incidents or quick escalation of incidents occur.

43
SA Firefighter General / Re: Interesting Fire and Emergency Related Paging
« on: November 16, 2011, 08:03:09 PM »
Good old Boms broken.

44
SA Firefighter General / Re: SACAD
« on: November 14, 2011, 04:56:04 PM »
Fingers crossed my local group will take on a professional approach...

45
SA Firefighter General / Re: SACAD
« on: November 09, 2011, 05:21:20 PM »
FYI SACAD DOCUMENTATION NOW FOUND ON CFS WEBSITE MEMBERS ONLY SECTION.

and the caps lock key is found just above the left shift key on most keyboards :)

Just wanted to get the attention of the speculators that the final document is out and now they can get back to work on there paid jobs :P

46
SA Firefighter General / Re: SACAD
« on: November 08, 2011, 09:24:29 PM »
FYI SACAD DOCUMENTATION NOW FOUND ON CFS WEBSITE MEMBERS ONLY SECTION.

47
SA Firefighter General / Re: SACAD
« on: November 06, 2011, 12:38:33 AM »
I would prefer Up to 10 FTE positions per shift in Comms (Be it mixed fireys and mixed civvies), compared to some of the bad projects/money spending by SAFECOM (encompassing all three services).

Having a full allotment of trained comms staff of that amount, would mean better SLA adherence and the ability to take communications on regional talkgroups for Level 1 Incidents (Level 2: GCC/Level 3: RCC) (Just an Idea)

CFA uses radio protocols that CFS should mix with our current ones. And from random listening to VicFire channels, using the protocols by volly appliances is well done.

9 CFA Radio Procedures

48
Emergency Vehicles / Re: New 24 prototype
« on: November 01, 2011, 09:27:04 PM »
Crewdeck :/

49
SA Firefighter General / Re: SACAD
« on: October 28, 2011, 09:41:44 PM »
Hopefully SOP's will state absolutely every truck offline moment needs to be logged with AF...

50
Incident Operations / Re: Strike team to Alice Springs
« on: October 05, 2011, 06:02:46 PM »
The initial strike team went up to help with asset protection and some mitigation burning, with the relief crews doing mitigation and hazard reduction burns around Alice Springs, as well as being a rapid response team to any new fires.

Rapid Response: Sitting in the staging area for 8 hours. Done that.

Pages: 1 [2] 3 4 5 ... 100