To: Emergency Communications Units - Information Bulletin Here's an example of ACS/RACES mutual aid in the l997 floods. SEMS and RIMS were new and untested and had just been implemented. In other aspects the RIMS computer system proved quite effective, but in this specific case the telephone was the means used instead of the computer. An out-of-the-ordinary factor was that at the time a state OES Region Telecommunications Coordinator was physically at the OA when the OA ACS/RACES coordinator requested mutual aid for the OA ACS. When that happened the on-premises State OES TCOMM Coordinator took the request that would otherwise have gone over RIMS to the EOC and immediately contacted the Region ACS Officer (who was located at the REOC) regarding the request along with an incident number from OA#1, the requesting county. The Region ACS officer (RACSO) - who basically, at that time, filled the position of both Logistics and Plans within the REOC for ACS resources only - then obtained a mission number from the REOC Operations Officer, and then the reverse chain was briefed. The RACSO called the paid-staff ACS/RACES coordinator of each of several nearby counties for permission to access that OA for ACS/RACES Mutual Aid. Once approved he asked permission to speak to their ACS/RACES Officer (RO) in order to make the detailed arrangements needed to fill the request of OA#1. The RACSO then called the RO in OA# 2,3,4,5 for mutual aid from their ACS or RACES unit. On receiving their return list of available resources, the RACSO coordinated the resources, then advised each RO in OA# 2, 3, 4, 5 of exact duties, timing, travel routes, arrival points, and operation locations, along with the mission and incident ID numbers. The RO in OA# 2, 3, 4, 5 dispatched communications mutual aid resources (ACS or RACES) to the aid of OA#1 in accord with the RACSO coordination details. Those mutual aid resources proceeded to OA#1 in accord with the arranged dispatch information. Arrival was communicated back to the RACSO, thence to the responding OA. When demobilizations at OA#1 began, and until its completion, the requesting OA#1 RO notified the Region ACS Officer, who notified the source OA Radio Officers of released resources. When all resources of each responding OA had arrived back at that OA, the source OA Radio Officers notified the Region ACS Officer. At that point the Region ACS Officer contacted REOC Operations and requested that the mission be closed. In the illustration just detailed, certain factors existed that will not always apply. One was the presence of the OES Region TCOMM Coordinator at the OA when it needed communications mutual aid. Another was the presence of the OES Region ACS Officer at the REOC. A third was that, at the time, the RACSO was filling the dual ICS role of both Logistics and Plans within the REOC for ACS resources (only). That third element is critically important as ICS logistisc and plans personnel at an EOC may not be familiar with ACS (or RACES) resources. This is an on-going education process that is an ACS responsibility to accomplish; and it is a step that may need to be repeated time and again as new personnel come on the EOC scene, whether at an OA EOC or at a State REOC. Cary Mangum, W6WWW - E-mail: [email protected] To subscribe to bulletins send a blank email to [email protected] or go to www.cesra.org/subscribe/ Submit suggestions, topics or comments on the bulletins to Cary Mangum, State ACS Officer, California. (W6WWW), [email protected] or [email protected] Bulletins archives: ACS Web page: acs.oes.ca.gov, ftp.ucsd.edu/emcomm or ftp.oes.ca.gov/ACS/EMCOMM and a Landline BBS at 916-255-0798 (graphical & standard interface) EOM |