Regional SOP Text Messaging – Emergency Operations Use
Text Messaging – Emergency Operations Use
Purpose:
To establish consistent practice amongst agencies in Emergency use of the TransitMaster Text Message feature.
Definitions:
Text message – Text Message sent to MDT by user from Bus Operations Module.
Store and Forward (SF) Allows user to store a message in system for defined duration.
Repeat Interval Allows user to put the message on a schedule to repeat at defined interval.
Emergency: For purposes of this SOP, an Emergency is defined as a sudden incident that must be dealt with urgently, that could have imminent consequence to personal safety if action is not taken.
User Requirements:
Defined by individual providers.
Procedure:
Individual providers have the authority and responsibility to determine their own internal procedures related to the use of emergency text messaging, except as indicated below:
Note: MVTA has AVAIL CAD and will communicate with their fleet via AVAIL.
Repeat interval
The Repeat Interval feature is not to be used. This is due to historical concerns with the frequency of messages causing system slowdowns and lock-ups.
Emergency Messages to Another Provider’s Bus:
In the interest of expediency, Metro Transit’s Transit Control Center (TCC) is authorized to send an Emergency Text message to other regional provider buses in the interest of Operator and Passenger safety (for example if the bus is approaching an unsafe area and there is no time to alert the other provider’s dispatch center). This decision will be at the discretion of the TCC Supervisor on duty and will be based on emergency circumstances only. If this occurs, TCC will precede the emergency message with the words “EMERGENCY MESSAGE FROM TCC” and follow with an instruction for the operator to contact their dispatch for more information.
Note: If a message needs to be sent to MVTA buses, the TCC will contact MVTA dispatch via phone to alert them of the situation and MVTA will use their own protocol and procedure to alert their buses.
Shared Routes:
Sharing information
In incident situations where another provider’s operation will benefit from texted information, or is in interest of public safety, but a threat is not imminent, the following process will be used to communicate the text message information:
Individual agencies will notify other providers that a text message has been placed that may affect other providers. This message will contain the details of the message to include:
Location affected
Content of text message
Duration of message if Store and Forward (SF).
Individual providers will send updates to others when incident has been cleared.
The Regional AVL Operations workgroup will create, maintain and distribute an email distribution list for all providers for use in this context.
The Communications History feature within Transitmaster will be used as a shared resource of information for text messages that have been distributed.
Notifications:
Any changes to this procedure must be approved by the RAVL Operations Committee.
Reports:
Written documentation or TM Incident report where available, is to be created when an emergency text message has been sent that may affect other providers. Each provider will determine their own method of documentation. Documents are to be stored and maintained separately by each agency provider. Reports may be shared between providers under provisions agreed upon in separate SOP.
References:
TransitMaster User Guide, page 16, 17, 22