Severe Weather Dispatch: Difference between revisions
From Portland NET Wiki
AWestervelt (talk | contribs) m noting for readers to find new changes because it's underlined |
AWestervelt (talk | contribs) clarifying priorities for transport options; special things to look for in transportation requests |
||
| Line 122: | Line 122: | ||
# In the Dispatch Nexus, select your name from the drop-down menu in the “Dispatcher Name” column; select “In Progress” in the STATUS column; and click “Save.” This will signal to those monitoring that someone is working on the request, and clearly stops others from coordinating the same ride. | # In the Dispatch Nexus, select your name from the drop-down menu in the “Dispatcher Name” column; select “In Progress” in the STATUS column; and click “Save.” This will signal to those monitoring that someone is working on the request, and clearly stops others from coordinating the same ride. | ||
# Using the Shelter Map and Shelter Dashboard, determine the appropriate warm/cool space nearest to the rider. If we have capacity information for this location on the Shelter Dashboard, make sure there are more than 5 spaces left at the location before sending someone there. If you are unsure whether to transport to a day-only location or a 24/7 location, ask a 211 liaison in Slack. | # Using the Shelter Map and Shelter Dashboard, determine the appropriate warm/cool space nearest to the rider. If we have capacity information for this location on the Shelter Dashboard, make sure there are more than 5 spaces left at the location before sending someone there. If you are unsure whether to transport to a day-only location or a 24/7 location, ask a 211 liaison in Slack. | ||
# Find transportation for the rider (see “How to Coordinate Rides” section below). Pay close attention to any special circumstances in the | # Find transportation for the rider (see “How to Coordinate Rides” section below). Pay close attention to any special circumstances. <u>Check the Rider Safety column to see if they are directly in the weather or sheltered. Also look for things such as the presence of children, pets, lots of belongings, many riders, bikes, wagons, wheelchairs, etc.</u> If ECC Ground Support has vehicles dedicated to NET Dispatch, check to see if they can take the request (Ground Support fleet availability for guest transport varies by event). <u>If not, seek transportation according to the event's transportation option priorities. Ask in chat if you're not sure if you should to move to the next tier of transportation options.</u> | ||
# Complete the grayed-out columns for Transportation. Enter Transport Arranged, Shelter and Address, and Pickup ETA (unless it’s an ECC Ground Support ride, in which case they will enter the ETA). Save! Once the spreadsheet is saved with an ETA, an email will go to 211info prompting them to call the rider with the ETA. | # Complete the grayed-out columns for Transportation. Enter Transport Arranged, Shelter and Address, and Pickup ETA (unless it’s an ECC Ground Support ride, in which case they will enter the ETA). Save! Once the spreadsheet is saved with an ETA, an email will go to 211info prompting them to call the rider with the ETA. | ||
# If ECC Ground Support is being used, wait for your GS Lead to confirm they have accepted the ride. The handoff between Dispatch and GS should read in Slack like a radio conversation. This assures both that (1) Ground Support doesn't send a vehicle to pick up a client that a Dispatcher is also coordinating a ride for through another transport provider, and (2) also makes sure a client does not get inadvertently dropped: | # If ECC Ground Support is being used, wait for your GS Lead to confirm they have accepted the ride. The handoff between Dispatch and GS should read in Slack like a radio conversation. This assures both that (1) Ground Support doesn't send a vehicle to pick up a client that a Dispatcher is also coordinating a ride for through another transport provider, and (2) also makes sure a client does not get inadvertently dropped: | ||
