Messaging – Being the cloud Part 1 – Flow, tracking and logging.

32
Messaging – Being the cloud Part 1 – Flow, tracking and logging

Transcript of Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Page 1: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Messaging – Being the cloud

Part 1 – Flow, tracking and logging

Page 2: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Agenda

• Announcements• What coming up• Messaging Part 1

Page 3: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

ANNOUNCEMENTAny

Page 4: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Training and Events

• Porky Work Parties– ??

• Training– Tonight – Messaging Part 1 – being the cloud– June – Messaging Part 2 – format and protocol– July – Shadowing– Aug – Porky Training – Date to be scheduled.

• Exercises– Exercise in July-Aug, need shadow volunteers

Page 5: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Messaging – Being the cloud

Part 1 – Flow, tracking and logging

Page 6: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Flow of a Message

Field

EOC/Office

Our Function is Copy and Log

Page 7: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Classes of Messages• Common Classes of Messages– Directed Message – From -> To

• From a specific person or team• To a specific person or team

– Broadcast Messages – Goes to everybody• General information everyone need to know

• Less common but important– Indirect message – From -> ?

• Sender does not know who the receiver should be• We will need to direct the message

Page 8: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Key Assumptions of the Cloud

• Though the Cloud has no knowledge of is surrounding, We act as if:– Organization Awareness – DEM, Boeing EOC,

ESCA EOC …– Function Awareness – Phones are preprogram for

the Emergency Support Function within DEM– It is reliable– All modes of communication are available– Copying, logging and routing are build in.

Page 9: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

AND THEN THE BIG ONE HITSWhat happens when the cloud fails

Page 10: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

The cloud after the big one

Field

EOC/Office

Page 11: Messaging – Being the cloud Part 1 – Flow, tracking and logging.
Page 12: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

How do we do this?

Defined ResponsibilitiesFunctional AlignmentDivide and conquer

Page 13: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Defined Responsibilities

• Each Command Post (or Base) has a designated area of authority.– SnoDEM – is responsible for the county, – Monroe EOC is responsible for Monroe– Firebase 1 is responsible for the north fire– Firebase 2 is responsible for the south fire

• Specific Frequencies are used for specific things– Mt. Pilchuck Repeater is used for resources net– Fire Trail Hill Repeater is used for command net– Clearview Repeater is used for Tactical

Page 14: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Functional AlignmentEmergency Support Functions

• ESF 1 – Transportation• ESF 2 – Communications• ESF 3 – Public Works and

Engineering• ESF 4 – Fire Fighting• ESF 5 – Information Analysis

and Planning• ESF 6 – Mass Care, Housing

and Human Services• ESF 7 – Resource Support• ESF 8 – Public Health and

Medical

• ESF 9 – Search and Rescue• ESF 10 – Hazardous

Material Response• ESF 11 - AG & Natural

Resources/ Food and Water• ESF 12 – Energy• ESF 13 – Public Safety, Law

Enforcement and Security• ESF 14 – Long Term

Recovery, Damage Assessment, Mitigation

• ESF 15 – Public Affairs

Page 15: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

6m

2m

FRS

800MHz

Page 16: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

How are we going to do all that?

Time for a drill

Page 17: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Our Scenario• A major disaster has occurred effecting most of WWa. Sno RACES is fully active.

The Communication Officer has requested teams of two (2) to be deployed to forward bases to support communication.

• You and your partner’s assignment is to one of the forwarded bases (Base 6) providing support for tactical team, base to base, and base to EOC communications. At these location there is no WebEOC.

• The location you have been deployed to will support tactical group Fire12, Fire 14, Fire 18, SAR11, SAR21, and Air 6. The groups are further divided into 3 teams of 5 that are deployed to the field, designated A,B, and C. Because of location you are able to communicate with all teams, but communications between teams are limited, and you will be asked to relay messages.

• The Base Commander has three ESF teams for Fire, Search and Rescue and Resource Support that you will also be supporting

• In addition to communications you are asked to monitor two emergency channels and report any civilian emergency communications.

• Upon arrival at the base camp, after checking in, you find that there are two(2) radio stations, one with three (3) radio, for communications between the base and the tactical team and one (1) to communicate with Air 6. The second has four (4) radios, one for base to base and base to EOC and three (3) set up to monitor emergency channels

Page 18: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Your Assignment• Divide up into teams of two (2), and decide who will be

handling which station.• The packet in front of you, you will find Envelopes

labeled for the ESF functions and Other, Paper for logging, and the messages you will process.

• Your task is for you and your partner to process and log the messages, and decide which envelope to put the messages in.

• This is a discovery process, how and what you log is up to you. It’s ok to make mistakes, this is how we learn

• You have 10 minutes.• Questions?

Page 19: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

BEGINExercise

Page 20: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

How did we do?

Looking out our logs

Page 21: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Radio Map

• How many made a radio map?• Radio maps identifies what each radio is for.– Location– Frequency– Type– …

Page 22: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Example Radio MapRadio 1 Radio 2 Rad10 3 Radio 4

Type

Frequency

Use Fire Team SAR11 SAR21 AIR

Page 23: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Contact map

• How many built a Contact Map?• You use a contact map, when a single radio or

contact represents more than one person or group.

• Contact maps need to be routinely updated

Page 24: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Example Radio Contact MapStation___________ Operator _______________ Date: ___________

Fire Teams SAR11 SAR21 AIRFire12 A X

Fire12 B

Fire12 C X

Fire14 A

Fire14 B X

Fire14 C

Fire18 A X

Fire18 B

Fire18 C X

SAR11 A

SAR11 B X

SAR11 C

SAR21 A X X

SAR21 B

SAR 21 C

AIR 6 X

Page 25: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Example Radio Contact Map Station___________ Operator _______________ Date: ___________

Command

Base 1

Base 2

Base 3 X

Base 4

Base 5 X

Base 6 -

EOC X

Page 26: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

The Log• What should be in the message log?

– From– To– Subject**– Needs Reply*– Relay*– Assigned To*– Date

• Date time of the message, date when received– Time

• Time of the message and the time received– Number of pieces*– Destination**– Priority**– Sender*

Page 27: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Messages from Tactical Team

• Where did you route the messages for the tactical teams?– Fire Teams - normally go to ESF 4– SAR teams – normally go to ESF 9– Resources – normally go to ESF 7

Page 28: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Relay Messages

• How did you handle the message from Air 6 to Fire14 B?– This is a message you need to relay. In our

scenario, the operator that received the message would need to relay. If Air 6 was on a another station, you would need to get the message to the other station.

– You should also notify ESF 4, noting that the message was relayed

Page 29: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Emergency Messages

• How did you handle the message from Fire12 C and Fire 18 B?– If this was real:• For Fire12 C – find out if they need assistance, then

route to ESF 4• For Fire18 B – Route to ESF 4

Page 30: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Monitoring Emergency Traffic

• How do you handle emergency traffic?– Stay calm – Get the required information• Who, What, Where, When and Severity

– Route the traffic to the appropriate support team for response. (for our scenarios is was … SAR -> ESF 9)

– If possible move the communication to another frequency, with direct contact. If not, stay in touch until help arrives.

Page 31: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

Messages in envelopes

• ESF 4 – 7• ESF 7 – 2• ESF 9 – 3• Other – 1• How did your team do?

Page 32: Messaging – Being the cloud Part 1 – Flow, tracking and logging.

HOW DO YOU FEEL YOUR TEAM DID?

Group Comments