Module 4 - Multi Agency Flashcards Preview

FSV Dispatch > Module 4 - Multi Agency > Flashcards

Flashcards in Module 4 - Multi Agency Deck (24):
1

WHAT IS THE WORKFLOW FOR A MULTI AGENCY EVENT?

- SELECT THE EVENT FROM PENDING AND REVIEW
- UPDATE EVENT TO CORRECT EVENT TYPE AND PRIORITY IF REQUIRED
- ADD THE APPROPRIATE SC
- SELCT RECOMMEND, DISPATCH AND TURNOUT.

2

WHO MUST BE NOTIFIED WHEN AN EVENT TYPE HAS BEEN UPDATED DUE TO AN INCORRECT EVENT TYPE?

THE TEAM LEADER

3

WHAT IS THE CPS FOR A MULTI AGENCY EVENT?

60 SECONDS

4

WORKFLOW FOR UPDATING A MULTI AGENCY EVENT PRIOR TO DISPATCH (EG. 138-139) (7)

- SELECT THE EVENT
- UPDATE THE EVENT TYPE AND ACCEPT
- ENTER SC
- RECOMMEND, DISPATCH AND TURNOUT
- ADD REMARKS: ===EVENT TYPE ALTERED - INCORRECT EVENT TYPE===
- CAS EVENT TO OTHER AGENCIES REMOVING THE FSV RESPONSE
- ENSURE NOTIFICATION COMMENTS ARE RECORDED IN THE CHRONOLOGY (EG. NA: POL)

5

WORKFLOW FOR UPDATING A MULTI AGENCY EVENT POST INITIAL DISPATCH

- SELECT THE EVENT
- UPDATE THE EVENT TYPE AND ACCEPT
- ALTER SC IF REQUIRED
- RECOMMEND, DISPATCH AND TURNOUT TO FILL THE INITIAL RESPONSE
- ADD REMARKS NOTING REASON FOR CHANGE, EG. ===EVENT TYPE ALTERED - REPORT OF PERSONS TRAPPED===
- CAS EVENT TO OTHER AGENCIES REMOVING THE FSV RESPONSE
- ENSURE NOTIFICATION COMMENTS ARE RECORDED IN THE CHRONOLOGY (EG. NA: POL)

6

WHEN A REQUEST IS RECEIVED FROM THE FIELD TO CANCEL A MULTI AGENCY RESPONSE FOR ANOTHER AGENCY, IN WHAT FORMAT ARE REMARKS ENTERED?

=== FROM FSV - (AGENCY) NO LONGER REQ - (REASON) ===

EG:

=== FROM FSV - AMB NO LONGER REQ - NIL PERSONS TRAPPED/INJ ===

7

WORKFLOW FOR SINGLE AGENCY TO MULTI AGENCY EVENT

- UPDATE THE EVENT TYPE AND ACCEPT
- UPDATE OR ENTER AN APPROPRIATE SC
- RECOMMEND, DISPATCH AND TURNOUT
- NOTIFY THE OTHER AGENCIES VIA CAS, OR PHONE AV IF CONFIRMED PATIENTS
- INSERT NOTIFICATION COMMENTS (NA: POL VIA CAS, AV VIA PHONE ETC)

8

WORKFLOW FOR MULTI AGENCY TO SINGLE AGENCY

- UPDATE THE EVENT TYPE AND ACCEPT
- ALTER THE SITUATION COMMENT IF REQUIRED
- RECOMMEND, DISPATCH AND TURNOUT
- ACTION ANY APPLIANCE CANCELLATIONS REQUIRED

9

MFB CANCELLATION PRIOR TO DISPATCH

CANCEL THE EVENT

10

MFB CANCELLATION AFTER DISPATCH

- APPLIANCES TO BE INFORMED VIA RADIO THE REQUESTING AGENCY HAS ADVISED RESPONSE IS NO LONGER REQUIRED, AND GIVEN THE REASON AS SUPPLIED.

- IF THE CREW CHOOSE TO CANCEL, A WB IS STILL REQUIRED

- ENTER APPROPRIATE 'NA' TO THE CHRONOLOGY OF APPLIANCES BEING ADVISED

11

CFA CANCELLATION PRIOR TO CREWS TURNING OUT

- CANCEL THE EVENT
- SEND A CANCEL PAGE IF THE BRIGADES HAVE ALREADY BEEN PAGED

12

CFA CANCELLATION AFTER CREWS HAVE TURNED OUT

- APPLIANCES TO BE INFORMED VIA RADIO THE REQUESTING AGENCY HAS ADVISED RESPONSE IS NO LONGER REQUIRED, AND GIVEN THE REASON AS SUPPLIED.

- IF THE CREW CHOOSE TO CANCEL, A WB IS *NOT* REQUIRED

- ENTER APPROPRIATE 'NA' TO THE CHRONOLOGY OF APPLIANCES BEING ADVISED

13

WHERE IN CAD CAN IT BE DETERMINED WHETHER AN EVENT IS MULTI AGENCY OR SINGLE AGENCY?

- THE EVENT TYPE FIELD

- THE AGENCY RESPONSE FIELD

14

WORKFLOW IF AN EVENT FOR A ROAD ACCIDENT EVENT IS RECEIVED WITH THE REMARKS 'N/K TRAPPED'

- UPDATE THE EVENT TO 138/139
- ADD APPROPRIATE SC
- RECOMMEND, DISPATCH AND TURNOUT

15

WORKFLOW IF AN EVENT IS RECEIVED WITH THE EVENT TYPE 599 (DEFAULTS TO 624 RESPONSE)

- UPDATE THE EVENT TYPE AND RESPONSE CODE IF REQUIRED PRIOR TO DISPATCH, BASED ON COMMENTS PROVIDED IN THE EVENT.

- IF 624 IS APPLICABLE, THEN LEAVE AS IS.

16

WHAT AMB CODES ARE NEVER TO BE CREATED OR CHANGE BY AN FSV OPERATOR?

542 - EXPLOSION (POLICE NOT ATTENDING)

570 - SAR RESCUE TRAPPED (POLICE NOT ATTENDING)

627 - HAZMAT INCIDENT (POLICE NOT ATTENDING)

17

MULTIPLE EVENT WORKFLOW - HIGHER RESPONSE AFTER DISPATCH

- UPDATE THE EVENT TO THE HIGHER RESPONSE
- ALTER SC IF REQUIRED
- RECOMMEND TO FILL IN THE MISSING RESPONSE, DISPATCH AND TURNOUT
- D&C THE TWO EVENTS (AFTER NFD HAS BEEN ENTERED, AND AFTER CHECKING WITH THE RADIO OPERATOR)
- NO REQUIREMENT TO CAS

18

WORKFLOW - UPDATE OF EVENT LOCATION FOR MULTI AGENCY JOBS - CALL RECEIVED BY FIRE

- UPDATE THE EVENT LOCATION (IF NOT DONE BY CALLTAKER)
- NOTE IF ASSIGNMENT RULE OR MFB/CFA BOUNDARY HAS ALTERED
- ADVISE RESPONDING APPLIANCES AND COMPLY WITH THEIR DIRECTION (ASK THE RADIO OPERATOR)
- ENTER REMARKS, EG ===EVENT LOCATION ALTERED - ADDITIONAL CALL RECEIVED===
- CAS EVENT TO AV/POL, REMOVING THE FIRE RESPONSE
- NA INTO CHRONOLOGY (NA: AV AND POL)

19

WORKFLOW - UPDATE OF EVENT LOCATION FOR A MULTI AGENCY, NEW OR CAS JOB RECEIVED FROM POL OR AV

- CONFIRM SAME EVENT (ESPECIALLY FOR POL AS THEY CREATE A NEW EVENT)
- UPDATE EVENT IF REQUIRED
- NOTE IF ASSIGNMENT RULE OR MFB/CFA BOUNDARY HAS ALTERED
- ADVISE RESPONDING APPLIANCES AND COMPLY WITH THEIR DIRECTION
- D&C THE CAS'D EVENT INTO THE ORIGINAL EVENT

20

WORKFLOW IS AN AMB CLIN EVENT IS MISTAKENLY TRANSFERRED TO FSV

- ADVISE THE AMB T/L LEADER
- WHEN ADVISED, CAS THE EVENT BACK TO THE CLIN NODE AS ADVISED BY THE AMB TEAM LEADER

21

WHAT IS A POLICE BEACON SAFETY WARNING AND
WHAT ACTION SHOULD BE TAKEN?

AN INSERTED COMMENT IN THE REMARKS FIELD FROM POLICE, WHEN THERE IS POTENTIAL FOR RISK TO MEMBERS SAFETY.

RESPONDING APPLIANCES SHOULD BE ADVISED THAT POLICE HAVE ISSUED A SAFETY WARNING TO THEIR MEMBERS

22

WORKFLOW WHEN DISPATCHING AN SES UNIT

- CONTACT THE SES OPERATOR BY PHONE WHEN DISPATCHING (NUMBER DISPLAYS IN THE TURNOUT WINDOW) AND ADVISE THEM THE RESCUE UNIT HAS BEEN PAGED.

'THIS IS MIKE FROM FIRE, I'M RINGING TO CONFIRM THAT I HAVE JUST PAGED (UNIT NAME) TO RESPOND TO (ADDRESS)'

23

WORKFLOW IF A GENERAL SES UNIT IS RECOMMENDED (EG, LIGHTING)

- CAS THE EVENT TO SES USING 577
- CALL SES TO CONFIRM RECEIPT OF JOB

24

WORKFLOW IF ESCALATING A LIGHTING UNIT AND CAD RETURNS AN SES RESCUE

- CAS THE EVENT TO SES USING 577, REQUESTING A RESPONSE FOR LIGHTING IN REMARKS
- CALL SES TO CONFIRM RECEIPT OF JOB