Western Region- WAGIN. Tactical Interoperable Communications Plan (TICP)

Transcription

1 Western Region- WAGIN Tactical Interoperable Communications Plan (TICP) March 2012

2 Tactical Interoperable Communications Plan Signature Page Approved by: Name/Title/Agency Date Name/Title/Agency Date Name/Title/Agency Date Name/Title/Agency Date Concurrence: Name/Title/Agency Date Name/Title/Agency Date Name/Title/Agency Date Name/Title/Agency Date Name/Title/Agency Date March 2012 ii

3 Record of Change Change No. Description Change Date Approved By 001 Initial Document 10/01/ Update 09/01/2011 This Tactical Interoperable Communications Plan (TICP) is subject to information and/or equipment updates and changes. The use of this Record of Change helps manage TICP modifications throughout the life of this document. All attempts have been made to ensure the accuracy of the information within this TICP as of the initial distribution date. Any subsequent adjustments should be logged and coordinated with user agencies within this Western Region. March 2012 iii

4 Preface This document establishes a Tactical Interoperable Communications Plan (TICP) for the Western Region (Washington, Allegany, and Garrett Counties). The TICP is intended to document the interoperable communications resources available within the designated area, who controls each resource, and what rules of use or operational procedures exist for the activation and deactivation of each resource. See Appendix J for a list of resources available to assist in preparing/updating the TICP. March 2012 iv

5 Executive Overview This document establishes a Tactical Interoperable Communications Plan (TICP) for the Western Region (Washington, Allegany, and Garrett Counties). The TICP is intended to document the interoperable communications resources available within the designated area, who controls each resource, and what rules of use or operational procedures exist for the activation and deactivation of each resource. Interoperability is the ability to communicate between agencies that utilize disparate radio systems and other interoperability methods such as mutual aid channels, gateways, dispatch centers and radio caches. Interoperable resources are defined as shared systems, shared channels, gateways, and radio caches: Shared systems refer to a single radio system used to provide service to several public safety or public service agencies. Intra-system shared channels refer to common frequencies/talkgroups established and programmed into radios to provide interoperable communications among agencies using the same shared radio system. Channel, in this context, refers to the name of a common frequency/talkgroup visually displayed on a user s radio. Inter-system shared channels refer to common frequencies/talkgroups established and programmed into radios to provide interoperable communications among agencies using different radio systems. Channel, in this context, refers to the name of a common frequency/talkgroup visually displayed on a user s radio. Gateway systems interconnect channels of disparate systems (whether on different frequency bands or radio operating modes), allowing first responders using their existing radios and channels to be interconnected with the channels of other users outside of their agency. Dispatch consoles that are able to create patches will also be captured as gateways. Cache radios, also known as swapped radios, refer to maintaining a cache of standby radios that can be deployed to support regional incidents. These radios may be from a regional cache or from a participating agency. These radios allow all responders to use common, compatible equipment during an incident. Mobile Communications Units (MCUs) (also known as a Mobile Communications Centers (MCCs) or Mobile EOCs) refers to any vehicular asset that can be deployed to provide or supplement communications capabilities in an incident area. Examples of the types of communications devices an MCU can house are: subscriber and base station radios of various frequency bands, gateway devices, satellite phones, wireless computer networks, video broadcasting/receiving equipment, etc. Typically these communications devices are permanently [located/stored] in the MCUs when not used. The MCU should also be able to temporarily provide the electrical power required to operate the communications devices. March 2012 v

6 Table of Contents 1 Western Region Information Participating Jurisdictions/Agencies/Disciplines Nongovernmental Agencies Represented in the TICP Tribal Entities Represented in the TICP Other TICP(s) in the State TICP Point of Contact Governance Overview Governing Body Membership Responsibilities of the Subcommittees Meeting Schedule TICP Maintenance and Update Agency Responsibilities and Rights Prioritization and Shared Use of Regional Interoperability Assets Interoperability Equipment, Policies, and Procedures Shared Systems Region-wide Shared System Technology Overview Region-wide Shared System Policies and Procedures Region-wide Shared System Rules of Use Region-wide Shared System Problem ID and Resolution Intra-System Shared Interoperability Channel(s) Definition of an Intra-System Shared Channel Intra-System Shared Channel Technology Overview Designated Intra-System Interoperability Channel(s) Western Region Intra-System Shared Channel Policies and Procedures Western Region Intra-System Shared Channel Rules of Use Western Region Intra-System Shared Channel Problem ID and Resolution Inter-System Shared Channel(s) Policies and Procedures Definition of a Region-wide Inter-System Shared Channel Region-wide Inter-System Shared Channel Technology Overview Region-wide Inter-System Shared Channel Policies and Procedures Region-wide Inter-System Shared Channel Rules of Use Region-wide Inter-System Shared Channel Problem ID and Resolution CALL/8TAC Shared Channel(s) CALL/8TAC Shared Channel(s) Introduction Phase II 800 Project March 2012 vi

7 Requirements Constraints and Limitations Interoperability Objectives Calling Channel Implementation Tactical Channel Implementation Tactical Channel Assignments Management Guidelines Technical Guidelines Operational Guidelines VCALL/VTAC Shared Channel(s) VCALL/VTAC Shared Channel(s) Programming the Federal Interoperability Channels Regulations and Guidelines for using the Interoperability Channels Conditions for use of Interoperablility Channels Emergency Preparedness using the Calling Channels UCALL/UTAC Shared Channel(s) UCALL/UTAC Shared Channel(s) Programming the Federal Interoperability Channels Regulations and Guidelines for using the Interoperability Channels...34 Conditions for use of Interoperablility Channels Emergency Preparedness using the Calling Channels WAGIN Shared Channel(s) WAGIN Shared Channel(s) Calling/Tactical Shared Channel Technology Overview Calling/Tactical Shared Channel Policies and Procedures Calling/Tactical Shared Channel Rules of Use Calling/Tactical Shared Channel Problem ID and Resolution Gateways Region-wide Gateway Policies and Procedures Region-wide Gateway Rules of Use Region-wide Gateway Communications Request Region-wide Gateway Deployment Procedures Region-wide Gateway Activation Procedures Region-wide Gateway Deactivation Procedures Region-wide Gateway Problem ID and Resolution Region-wide Gateway Limitations Region-wide Gateway Test Procedures Cache Radios Region-wide Cache Radio Policies and Procedures VHF Cache Radios UHF Cache Radios March 2012 vii

8 Region-wide Radio Cache Rules of Use Region-wide Radio Cache Request Region-wide Radio Cache Equipment Activation Region-wide Radio Cache Equipment Deactivation Region-wide Radio Cache Problem ID and Resolution Mobile Communications Units Mobile Communications Unit Policies and Procedures Region-wide Mobile Communication Units Rules of Use Region-wide Mobile communications unit Request Region-wide Mobile communications unit Activation Region-wide Mobile communications unit Equipment Deactivation Region-wide Mobile communications unit Problem ID and Resolution RACES Regional Emergency Resource Staffing CASM Overview Appendix A Points of Contacts... A-1 Appendix B Shared Systems... B-1 Appendix C Inter-system Shared Channels... C-1 Appendix D Inter-system Shared Channel Coverage Plots... D-1 Appendix E Gateways... E-1 Appendix F Radio Caches... F-1 Appendix G Mobile Communications Units... G-8 Appendix H Policy Documents, Governing Documents, MOUs, and Agreements... H-1 Appendix I Incident Command System Planning... I-1 Appendix J Reference Materials... J-1 Appendix K Glossary... K-1 List of Tables Table 1 Jurisdictions, Agencies, and Disciplines Represented in the TICP... 1 Table 2 Western Region Shared System(s) Table 3 Intra-System Shared Channel(s) Table 4 8CALL/8TAC Shared Channel(s) Table 5 VCALL/VTAC Shared Channel(s) Table 6 UCALL/UTAC Shared Channel(s) Table 7 WAGIN Shared Channel(s) Table 8 Western Region Gateway Systems Table 9 Western Region Radio Cache(s) Table 10 Optional Channels for Western Region 800 MHz Cache Radio(s) March 2012 viii

9 Table 11 Required Channels for Western Region VHF Cache Radio(s) Table 12 Optional Channels for Western Region VHF Cache Radio(s) Table 13 Required Channels for Western Region UHF Cache Radio(s) Table 14 Optional Channels for Western Region UHF Cache Radio(s) Table 15 Western Region Mobile Communications Unit(s) Table 16 RACES Points of Contact Table 17 Regional Emergency Resource Personnel Table 18 CASM AM POC Information Table A - 1 Dispatch Center Points of Contact... A-1 Table A - 2 Nongovernmental Agency Contact Information... A-3 Table A - 3 Executive Committee Member Information... A-5 Table A - 4 WAGIN Workgroup Contact Information... A-5 Table A - 5 Washington County Agency Information... A-8 Table A - 6 Allegany County Agency Information... A-15 Table A - 7 Garrett County Agency Information... Error! Bookmark not defined. Table B 1 Western Region Shared System(s)... B-1 Table B.1 WCP 25 Shared Talkgroup Information... B-4 Table B.2 MIEMSS Shared Channel Information... B-7 Table B.3 AC Fire/EMS Shared Channel Information... B-9 Table B.4 MSP VHF-Lo Shared Channel Information... B-11 Table B.5 Cumberland Public Works Shared Channel Information... B-13 Table B.6 AC Board of Education Shared Talkgroup Information... B-15 Table B.7 DNR Shared Channel Information... B-17 Table B.8 SHA Shared Channel Information... B-19 Table B.9 GC Fire/EMS Shared Channel Information... B-21 Table B.10 GC Sheriff Shared Channel Information... B-23 Table B.11 GC EMS Shared Channel Information... B-25 Table B.12 GC Public Roads Shared Channel Information... B-27 Table B.13 GC Public Utilities Shared Channel Information... B-29 Table B.14 GC Board of Education Shared Channel Information... B-31 Table B.15 National Park Service Shared Channel Information... B-33 Table C - 1 Western Region 800 MHz Inter-system Shared Channel(s)... C-2 Table C - 2 Western Region VHF Inter-system Shared Channel(s)... C-2 Table C - 3 Western Region UHF Inter-system Shared Channel(s)... C-3 Table C - 4 WAGIN Inter-system Shared Channel(s)... C-3 Table E - 1 Western Region Gateway System(s)... E-1 March 2012 ix

10 Table F - 1 Western Region Radio Cache(s)... F-1 Table F - 2 WC DES VHF Lo Talkgroup Information... F-2 Table F - 3 WC EEC UHF Talkgroup Information... F-4 Table F - 4 WC SO UHF Talkgroup Information... F-6 Table G - 1 Western Region Mobile Communications Unit(s)... G-8 List of Figures Figure 1 Western Region Governance Organization Chart... 7 Figure 2 Phase II 800 Coverage Figure 3 Existing VHF Composite Coverage Figure 4 Existing Low VHF Coverage Figure 5 Phase II Low VHF Proposed Coverage Figure 6 Exisgting UHF Coverage Figure 7 Existing UHF with Phase II Coverage Figure G - 1 MC18/MCC G-11 Figure G - 2 MCHPD/MCC... G-14 Figure G - 3 GCPS/MCC... G-17 Figure G - 4 AC Cumberland City PD MCU... G-20 Figure G - 5 AC EMA MCU... G-23 March 2012 x

11 1 Western Region Information 1.1 Participating Jurisdictions/Agencies/Disciplines This Tactical Interoperability Communication Plan (TICP) has been created for the Western Region. The plan is intended for use by first responders and may be used by governmental or non-governmental organizations and personnel requiring coordination of communications assets during an incident or planned event. The jurisdictions, agencies, and disciplines represented in the TICP are listed in Table 1 based upon their ability to provide their own communications assets. Additional contact information for each agency is listed in Appendix A. Table 1 Jurisdictions, Agencies, and Disciplines Represented in the TICP Jurisdiction Agency Discipline WASHINGTON COUNTY Washington County Sheriff s Office Washington County Division of Emergency Services Washington County Volunteer Fire and Rescue Association Washington County Board of Education Washington County Health Department Washington County Humane Society Department of Public Works Law Enforcement Emergency Communications Center Fire and EMS Education Public Health Community Services Public Works Boonsboro Boonsboro Police Department Law Enforcement Hancock Hancock Police Department Law Enforcement Smithsburg Smithsburg Police Department Law Enforcement Hagerstown City of Hagerstown Fire Department Fire Department City of Hagerstown Police Department Law Enforcement City of Hagerstown Public Works Public Works ALLEGANY COUNTY Allegany County Department of Emergency Services Allegany County Fire Allegany County EMS Allegany College of Maryland Allegany County Board of Education Allegany County Health Department Bureau of Police Division of EMS Special Operations Team Emergency Services Fire Emergency Medical Education Education Public Health Law Enforcement Emergency Medical HAZMAT, Technical Rescue March

12 Jurisdiction Agency Discipline Department of Public Works Allegany County Sheriff s Office Animal Control Division Public Works Law Enforcement Public Safety City of Cumberland Cumberland City Police Department Law Enforcement Cumberland Fire Department Cumberland Public Works Fire, EMS Public Works Frostburg Frostburg City Police Department Law Enforcement Frostburg University Police Department Law Enforcement Frostburg University Education GARETT COUNTY Frostburg Public Works Garrett County Department of Public Safety Garrett County Fire Garrett County EMS Garrett County Sheriff s Office Garrett County Public Roads Garrett County Public Utilities Garrett County Animal Control Garrett County Board of Education Garrett County Health Department Public Works Fire/EMS Dispatch Fire Emergency Medical Law Enforcement Transportation Public Works Public Safety Education Public Health City of Oakland Oakland City Police Law Enforcement STATE FEDERAL Oakland Public Works Maryland Institute for Emergency Medical Services Systems (MIEMSS) Department of Natural Resources Emergency Management Agency Maryland Department of Environment State Highway Administration Civil Air Patrol Public Works Emergency Medical Law Enforcement Emergency Management Environment Transportation/Highways Military 32 nd Civil Support Team Military Maryland National Guard Maryland State Fire/ Marshal s Office Maryland Division of Corrections Maryland State Police National Park Service US Marshals Service Federal Bureau of Investigation Federal Bureau of Prisons Alcohol, Tobacco, Firearms, and Explosives Military Fire/Law Enforcement Corrections Law Enforcement Law Enforcement Law Enforcement Law Enforcement Corrections Law Enforcement March

13 Jurisdiction Agency Discipline US Park Police Mine Safety and Health Administration US Secret Service Law Enforcement Safety Law Enforcement Nongovernmental Agencies Represented in the TICP Medical Facilities Meritus Hospital Western Maryland Hospital Center Western Maryland Health System Potomac Valley Hospital Garrett County Memorial Hospital Brook Lane Psychiatric Hospital Private Transport Services (Land) Valley Medical Transport Garrett Medical Transport Allegany Ambulance Service AAA Ambulance Service Butler Medical Transport Service County Medical Transport Service Private Transport Services (Air) STAT Med-Evac Life Flight MedStar HealthNet Education Bishop Walsh Middle/High School Hagerstown Community College Utilities Potomac Edison Power Columbia Gas Applied Energy Services Verizon Railroad CSX Norfolk Southern Red Cross March

14 RACES VOAD (Volunteer Organizations Active in Disaster) Salvation Army Tribal Entities Represented in the TICP N/A Other TICP(s) in the State NCR Baltimore Urban Area Southern Region Eastern Region March

15 1.2 TICP Point of Contact The primary and alternate points of contact (POC) for copies of or questions regarding this Plan are: Primary: Agency Name: Washington County Emergency Services POC Name: Kevin Lewis Title: Director, Division of Emergency Services Address: Elliott Parkway, Williamsport, MD Office Phone: Cell: /7 Phone: Alternate: Agency Name: POC Name: Title: Garrett County Department of Public Safety and Emergency Management Brad Frantz Director, Garrett County Department of Public Safety and Emergency Management Address: 204 South 3 rd Street, Oakland, MD Office Phone: Cell Phone: /7 Phone: bfrantz@garrettcounty.org 2 nd Alternate: Agency Name: Allegany County Department of Emergency Services POC Name: Roger Bennett Title: Chief of 911 Joint Communications Division Address: PPG Road SE, Cumberland, MD Office Phone: x123 Cell Phone: /7 Phone: rbennett@allconet.org March

16 2 Governance 2.1 Overview The Western Region TICP addresses interoperable communications equipment and planning for the region. Though each agency, discipline, and jurisdiction participating in this plan is unique regarding their own interoperable communication needs and capabilities, proximity to one another, population, and shared incident/event responsibilities allow them to develop a single, consolidated regional TICP rather than several individual, potentially incompatible plans. The TICP, therefore, consolidates information across agencies, disciplines, and jurisdictions by documenting regional communications capabilities in order to provide a usable and accurate regional tactical incident response tool. The TICP was developed under the authority of the Washington Allegany Garrett Interoperability Network (WAGIN). The WAGIN appointed members to the Operations Subcommittee and Technical Subcommittee. Members include representatives from the following public safety and public service disciplines: Communications Emergency Management Emergency Medical Services Fire/Rescue Special Operations Information Technology (IT) Investigations and Intelligence Law Enforcement Nongovernmental Organizations (NGOs) Public Health Public Works Transit Transportation/Highways March

17 2.2 Governing Body The WAGIN is comprised of agency representatives in addition to the following fixed committee positions: Chair Vice Chair Workgroup WAGIN Chair WAGIN Vice Chair Washington Allegany Garret Interoperability Network Workgroup (WAGIN) Maryland Statewide Interoperability Executive Committee (MSIEC) WAGIN Standing Committee WAGIN Ad Hoc Committee Technical Subcommittees Operations Subcommittees Figure 1 Western Region Governance Organization Chart March

18 2.3 Membership Appendix A provides POC information for members of the governing body and its subcommittees. 2.4 Responsibilities of the Subcommittees The Operations Subcommittee will: Maintain and update the TICP at regular intervals, or as critical updated information is identified. Disseminate updated plans to all participating agencies. Establish training requirements in support of the TICP. Promote interoperable communications capabilities through trained communications personnel. Initiate Memoranda of Understanding (MOUs) and Agreements for interoperable communications. The Technical Subcommittee will: Promote regular interoperable equipment/solutions testing, assist agencies with test evaluations, and dissemination the results. Re-evaluate regional requirements as technology evolves and circumstances dictate. Review communications related SOPs created by the included agencies, to preclude conflicts or non-compliance with current standards or initiatives. 2.5 Meeting Schedule The WAGIN meets at least quarterly or as needed. The Operations and Technical Subcommittees are included in the WAGIN meetings. 2.6 TICP Maintenance and Update The WAGIN has the responsibility to ensure this document is reviewed annually at the first meeting of each calendar year. Requests for modifications or additions to this document should be submitted to the TICP POC for distribution to the WAGIN. Updates to this document can be recommended by any of the participating agencies. Agencies participating in this plan will be formally notified within 5 business days of any approved modifications or additions to this TICP. 2.7 Agency Responsibilities and Rights Agencies will retain the following rights and responsibilities: Agencies are responsible for complying with MOUs and Agreements in coordination with their respective jurisdictions. March

19 Authorized representatives of agencies participating in this plan have the authority to request the use of equipment, including systems and mobile assets, in accordance with Standard Operating Procedures (SOPs). Where applicable, agencies will be responsible for consistently maintaining, testing, and exercising connectivity to interoperable communications. Agencies retain the right to decide when and where to participate in interoperable communications. For example, agencies will retain the right to accept or decline a patch to a gateway system to provide interoperable communications during an incident. 2.8 Prioritization and Shared Use of Regional Interoperability Assets In response to events or incidents which cross over political jurisdictions, there will potentially be competing demands and priorities for interoperable communications assets. Until such time as Incident Command is established, the lead agency designee (i.e., communications supervisor/command personnel), in cooperation with assisting agencies, will have the authority to designate the use of interoperable assets. Once Incident Command has been established, Command Staff or Communication Unit Leaders (when designated) direct the further coordination and delegation of the interoperable communications assets assigned to the event or incident in question. Agencies should judiciously activate needed interoperable assets so as to both effectively respond to the event and/or incident and also minimize any negative impact on surrounding agencies or jurisdictions. Specifically, interoperable communications should be attempted with the following order of operations in mind (subject to variability based on the agencies involved and the nature of the event/incident): 1. Leverage face-to-face communications wherever appropriate. For example, the co-location of all Command and General Staff at the incident command post (ICP) provides the best direct communications and reduces the demand on interoperability resources. 2. Employ local communications assets until such time as either those assets become taxed or inadequate based on the nature and/or scope of the incident. 3. If response agencies are users of a shared system, utilize that shared system to establish interoperable communications. 4. If response agencies operate on disparate systems, utilize shared or mutual aid channels to establish interoperable communications. 5. If response agencies do not share systems or channels, utilize a gateway solution to establish interoperable communications. 6. Where interoperable communications cannot otherwise be established between response agencies, utilize swap or cache radios to establish operable communications for responders. March

20 7. If no other method of interoperability can be established, relay communications through staff members. When the same resources are requested for two or more incidents, resource assignments should be based on the priority levels listed below: 1. Disasters, large scale incidents, or extreme emergencies requiring mutual aid or interagency communications. 2. Incidents where imminent danger exists to life or property. 3. Incidents requiring the response of multiple agencies. 4. Pre-planned events requiring mutual aid or interagency communications. 5. Incidents involving a single agency where supplemental communications are needed for agency use. 6. Drills, tests and exercises. In the event of multiple simultaneous incidents within the same priority level, the resources should be allocated with the following priorities in mind: 1. Incidents with the greatest level of exigency (e.g., greater threat to life or property, more immediate need, etc.) have priority over less exigent incidents. 2. Agencies with single/limited interoperable options have priority use of those options over agencies with multiple interoperable options. 3. When at all possible, agencies already using an interoperable asset during an event should not be redirected to another resource. Reference to applicable policy documents, governing documents, MOUs, and sharing agreements can be found in Appendix H. March

21 3 Interoperability Equipment, Policies, and Procedures This section describes all interoperable communications equipment and their associated policies and procedures in the Western Region. 3.1 Shared Systems Shared system refers to a single radio system used to provide service to several public safety or public service agencies. The table below lists all radio systems shared by more than one public safety or service agency operating in the Western Region. Details on each system are provided in Appendix B. Note: that intra-system shared channels refer to common frequencies/talkgroups established and programmed into radios to provide interoperable communications among agencies using the same shared radio system. Channel, in this context, refers to the name of a common frequency/talkgroup visually displayed on a user s radio. Radio System Make / Name Model WASHINGTON COUNTY Motorola WCP 25 ASTRO 25 Motorola /MA WC Fire/EMS COM WC Law Motorola /MA Enforcement COM Motorola /MA WC Highways COM WC Local Motorola /MA Government COM Motorola /MA WC DWQ COM Table 2 Western Region Shared System(s) Type Digital Trunked Digital Trunked Digital Trunked Digital Trunked Digital Trunked Digital Trunked Frequency Band WC Schools Motorola Conventional UHF/VHF WC Transit WC DPW Motorola Motorola Digital Trunked Digital Trunked Owning Agency Service Area UHF 450 Washington County Washington County UHF 450 Washington County Washington County UHF 450 Washington County Washington County UHF 450 Washington County Washington County UHF 450 Washington County Washington County UHF 450 Washington County Washington County WC Board of Education Washington County UHF 450 Washington County Washington County UHF 450 Washington County Washington County ALLEGANY COUNTY AC Fire/EMS Kenwood Passport VHF-Lo Allegany County Allegany County and into Somerset County, Pa. AC Sheriff Kenwood Passport UHF Commercial Allegany County AC Health Kenwood Passport VHF Allegany County Health Department Allegany County AC Public Works Kenwood Trunked 800 MHz Allegany County Public Works Allegany County Cumberland Fire Kenwood Trunked UHF City of Cumberland Cumberland Cumberland Police Kenwood Passport UHF City of Cumberland Cumberland March

22 Radio System Make / Frequency Type Name Model Band Owning Agency Service Area Cumberland Public Works GE Conventional VHF City of Cumberland Cumberland AC Board of Education Kenwood Trunked UHF Commercial Allegany County GARRETT COUNTY GC Fire/EMS Motorola Conventional VHF-Lo Garrett County Public Safety Garrett County GC Sheriff Kenwood Conventional Low Band Garrett County SO Garrett County GC Health GE/Kenwood Conventional VHF Garrett County Health Garrett County GC Public Roads Kenwood/ Garrett County Conventional VHF Motorola Public Roads Garrett County GC Public Utilities Kenwood Trunked 800 MHz Garrett County Public Utilities Garrett County GC Board of Garrett County Board Kenwood Trunked 800 MHz Education of Education Garrett County STATE MIEMSS MA COM Kenwood Conventional UHF State of Maryland Statewide MSP VHF-Lo Conventional VHF-Lo MSP Statewide DNR Conventional VHF DNR Statewide SHA Daniels Conventional VHF-Lo SHA Statewide FEDERAL National Park Service Motorola Conventional VHF US Parks Federal Region-wide Shared System Technology Overview The WAGIN Workgroup has identified shared communication systems that provide service to the Western Region. General interoperable communications rules of use, policies, and procedures that apply across these systems are detailed below. Region-wide Shared System Policies and Procedures Use the following procedures when requesting, using, or discontinuing the use of shared communication systems: When an individual responder needs to interoperate with other agencies on their same shared system, the responder will notify their dispatch center. The dispatcher can then identify and designate an appropriate channel. Note that in cases where no dispatcher intervention is required, responders still notify dispatch that they are switching to a shared channel to maintain responder safety. Notify dispatch when the interoperability channels/talkgroups are no longer required and announce the return to normal operations channels. For extended incidents: o The lead agency dispatcher notifies the Communications Coordinator (COMC)/Communications Unit Leader (COML)/designee that interoperability channels/talkgroups are in use. March

23 o o Each agency s dispatch center tells additional en-route responders what interoperability channels are in use for the incident. The Incident Commander determines when the interoperability channels are no longer required and notifies the appropriate dispatch center. Region-wide Shared System Rules of Use National Incident Management System Use an Incident Command System (ICS) compliant with the National Incident Management System (NIMS) when using any regional interoperability resource. Plain Language All interoperable communications during multi-agency, multidiscipline incidents will be in plain language. Avoid using radio codes, acronyms, and abbreviations as they may cause confusion between agencies. Ensure that all verbal requests for assistance or backup specify the reason for the request. Unit Identification Announce your home agency prior to announcing your unit identifier during interoperable communication situations. (i.e., Allegany County Engine Rescue 16). National Response Plan Under the National Response Plan, ICS forms will be used for all appropriate documentation. Region-wide Shared System Problem ID and Resolution During an incident: During activation, report shared system problems to the Communications Technician (COMT) or COML/designee assigned to the incident/event who will follow established agency procedures to resolve the problem. Following an incident, the following general problem ID and resolution processes apply to all shared systems: Report any problems with the shared system to the appropriate POC for the owning agency listed in Appendix B. The POC will be responsible for ensuring effective resolution to problems that exist with the shared system. Report any unresolved problems with that system directly to the Western Region Communications Coordinator/COML/designee. The Western Region Communications Coordinator/COML/designee ensures effective resolution to the reported shared system problems Intra-System Shared Interoperability Channel(s) Definition of an Intra-System Shared Channel Intra-system shared channels refer to common frequencies/talkgroups established and programmed into radios to provide interoperable communications among agencies using the same shared radio system. Channel, in this context, refers to the name of a common frequency/talkgroup visually displayed on a user s radio. March

24 Intra-System Shared Channel Technology Overview The WAGIN Workgroup has identified shared communication systems that provide service to the Western Region. General interoperable communications rules of use, policies, and procedures that apply across these systems are detailed below. Specific shared interoperable communication channels available within the region are listed in the tables below. More detailed information on each channel is documented in Appendix B. Designated Intra-System Interoperability Channel(s) Table 3 Intra-System Shared Channel(s) Channel/TG Primary Use Agencies Supported Frequency /Band WASHINGTON COUNTY Primary Dispatch WCSO1 Law Enforcement WCSO and MSP UHF HPD1 Law Enforcement HPD UHF FIRE MAIN Fire and EMS All Fire and EMS UHF Secondary Dispatch WCSO2 & 3 Law Enforcement WCSO and MSP UHF HPD2 & 3 Law Enforcement HPD UHF Tactical Talkgroups OPS1 Law Enforcement WCSO, HPD, MSP UHF OPS2 Law Enforcement WCSO, HPD, MSP UHF OPS3 Law Enforcement WCSO, HPD, MSP UHF OPS4 Law Enforcement WCSO, HPD, MSP UHF OPS5 Law Enforcement WCSO, HPD, MSP UHF FIRE OPS Fire and EMS All Fire and EMS UHF TAC1 thru TAC6 Fire and EMS All Fire and EMS UHF WC Emergency Management Emergency AREA1 thru 3 Management ALLEGANY COUNTY All Fire/EMS and Law Enforcement UHF Mutual Aid 1 Intra-Agency Fire/CMS/LEA UHF Mutual Aid 2 Intra-Agency Fire/CMS/LEA UHF Western Region Intra-System Shared Channel Policies and Procedures The policies and procedures in this section apply to the local, regional, State, and Federal channels shared across multiple systems. March

25 Western Region Intra-System Shared Channel Rules of Use Intra-system shared channels are common frequencies/talkgroups established and programmed into radios to provide interoperable communications among agencies using the same shared radio system. The following rules of use apply to these channels: National Incident Management System Use an Incident Command System (ICS) compliant with the National Incident Management System (NIMS) when using any regional interoperability resource. Plain Language All interoperable communications during multi-agency, multidiscipline incidents will be in plain language. Avoid using radio codes, acronyms, and abbreviations as they may cause confusion between agencies. Ensure that all verbal requests for assistance or backup specify the reason for the request. Unit Identification Announce your home agency prior to announcing your unit identifier during interoperable communication situations. (i.e., Allegany County Engine Rescue 16). National Response Plan Under the National Response Plan, ICS forms will be used for all appropriate documentation. Western Region Intra-System Shared Channel Problem ID and Resolution During an incident: During activation, report shared channels problems to the Communications Technician (COMT) or COML/designee assigned to the incident/event, who will follow established agency procedures to resolve the problem. Following an incident, the following general problem ID and resolution processes apply to all shared channels: Report any problems with the intra-system shared channel to the appropriate POC for the owning agency listed in Appendix B. The POC will be responsible for ensuring effective resolution to problems that exist with the intra-system shared channel. Report any unresolved problems with that system directly to the Western Region Communications Coordinator/COML/designee. The Western Region Communications Coordinator/COML/designee ensures effective resolution to the reported intra-system shared channel problems. March

26 3.2 Inter-System Shared Channel(s) Policies and Procedures Definition of a Region-wide Inter-System Shared Channel Inter-system shared channels refer to common frequencies/talkgroups established and programmed into radios to provide interoperable communications among agencies using different radio systems. Channel, in this context, refers to the name of a common frequency/talkgroup visually displayed on a user s radio. Region-wide Inter-System Shared Channel Technology Overview Specific inter-system shared interoperable communication channels available within the region are listed in Appendix C. Inter-system shared channel coverage plots are shown in Appendix D. Region-wide Inter-System Shared Channel Policies and Procedures The policies and procedures in this section apply to the local, regional, State, and Federal channels shared across multiple systems. Region-wide Inter-System Shared Channel Rules of Use Inter-system shared channels are reserved for situations that require interoperable communications to coordinate multiple public safety entities and/or activities across two or more separate radio systems. The following rules of use apply to these channels: National Incident Management System Use an Incident Command System (ICS) compliant with the National Incident Management System (NIMS) when using any regional interoperability resource. Plain Language All interoperable communications during multi-agency, multidiscipline incidents will be in plain language. Avoid using radio codes, acronyms, and abbreviations as they may cause confusion between agencies. Ensure that all verbal requests for assistance or backup specify the reason for the request. Unit Identification Announce your home agency prior to announcing your unit identifier during interoperable communication situations. (i.e., Allegany County Engine Rescue 16). National Response Plan Under the National Response Plan, ICS forms will be used for all appropriate documentation. Region-wide Inter-System Shared Channel Problem ID and Resolution During an incident: During activation, report shared channels problems to the Communications Technician (COMT) or COML/designee assigned to the incident/event, who will follow established agency procedures to resolve the problem. Following an incident, the following general problem ID and resolution processes apply to all shared channels: March

27 Report any problems with the inter-system shared channel to the appropriate POC for the owning agency listed in Appendix C. The POC will be responsible for ensuring effective resolution to problems that exist with the inter-system shared channel. Report any unresolved problems with that system directly to the Western Region Communications Coordinator/COML/designee. The Western Region Communications Coordinator/COML/designee ensures effective resolution to the reported inter-system shared channel problems CALL/8TAC Shared Channel(s) 8CALL/8TAC Shared Channel(s) Table 4 8CALL/8TAC Shared Channel(s) Channel Name Primary Use Agencies Supported Frequency /Band 8CALL90 Mutual Aid All Public Safety Agencies 800 MHz 8TAC91 Mutual Aid All Public Safety Agencies 800 MHz 8TAC91D Mutual Aid All Public Safety Agencies 800 MHz 8TAC92 Mutual Aid All Public Safety Agencies 800 MHz 8TAC92D Mutual Aid All Public Safety Agencies 800 MHz 8TAC93 Mutual Aid All Public Safety Agencies 800 MHz 8TAC93D Mutual Aid All Public Safety Agencies 800 MHz 8TAC94 Mutual Aid All Public Safety Agencies 800 MHz 8TAC94D Mutual Aid All Public Safety Agencies 800 MHz Introduction 1 The National Plan specifies five channel assignments in the / MHz Band (800 MHz NPSPAC Band) that have been assigned for nationwide interoperability among federal, state, and local governments for mutual aid and disaster operations. These five common NPSPAC Band Interoperability / Mutual Aid channels are to be used for command, control and coordination radio communications at incidents requiring inter-agency and/or multi-jurisdiction responses. The NPSPAC Interoperability/Mutual Aid channels have been referred to as the 821 MHz Interoperability Calling and Tactical channels or the National Calling and Tactical Channels. Phase II 800 Project 1 Information for this section are excerpts from GUIDELINES FOR THE IMPLEMENTATION, MANAGEMENT, AND OPERATION OF THE NATIONAL CALLING and TACTICAL CHANNELS (821 MHz BAND) March

28 The WAGIN Phase II Project was developed to incorporate 800 MHz coverage. The following map illustrates the 800 MHz coverage that will be gained once the Phase II Project is completed. March

29 March

30 Requirements The FCC has mandated that any public safety agency or eligible entity authorized under part 90 of the FCC Rules and Regulations that is licensed to operate five or more channels in the / MHz (NPSPAC) Band is required to implement the National Calling and Tactical Channels. The National Calling Channel ( CALLING CHANNEL ) has been established on a nationwide basis to provide a common means for any 800 MHz public safety radio user to request emergency assistance from the local jurisdiction. The National Tactical Channels ( TACTICAL CHANNELS ) are reserved for use by entities requiring interoperability communications during disasters and other emergency situations. Incidents requiring multi-agency communications may use these channels as directed by the incident commander having responsibility for an incident. The TACTICAL CHANNELS are intended for on-scene incident (tactical or fireground) communications ( talk-around mode) or in conjunction with a mobile repeater for a larger area of operation. The TACTICAL CHANNELS are not intended to be used for extended or wide-area coverage (e.g., simulcast) in order to minimize co-channel interference to/from adjacent jurisdictions. The CALLING CHANNEL and the TACTICAL CHANNELS must be implemented as a base or control station (with satellite receiver sites, if required) to provide optimum onstreet coverage to and from mobile stations within the jurisdiction s boundaries. The CALLING CHANNEL must be monitored continuously. The mobile repeater function shall normally be ENABLED, but capable of being remotely DISABLED from the primary control point. A base or control station for a TACTICAL CHANNEL must be implemented for every increment of five NPSPAC Band channels in licensed operation. A licensee operating a 8-channel trunked radio system, for example, is required to operate a fixed base station capability for two of the National Calling and Tactical Channels. The mobile repeater function for each TACTICAL CHANNEL shall be DISABLED but capable of being remotely ENABLED from the primary control point. The preferred operation of a TACTICAL CHANNEL is the talk-around mode at the incident scene. Constraints and Limitations Under the FCC Rules, an entity must have a license to operate a base or control station on any of the Interoperability Channels, including the National Calling and Tactical Channels. Public Safety licensees who are eligible to hold a Part 90 license, or who are otherwise licensed under Part 90, can operate mobile units on the Interoperability Channels without an individual license. The FCC requires that all mobile and portable radios for the 800 MHz Band shall be equipped to operate on all five of the National Common Channels, to include the talkaround mode. March

31 Interoperability Objectives The National Calling and Tactical Channels are primarily intended for use between federal agencies, state and county agencies and the local jurisdiction(s) in which an incident occurs. The National Calling and Tactical Channels also provide an effective means of communications interoperability between agencies and emergency responders that normally do not share any other compatible communications system. The utilization of the CALLING CHANNEL and the four TACTICAL CHANNELS is clearly different. The CALLING CHANNEL must be actively monitored at all times, in order for the local jurisdiction to respond to an emergency or request for assistance (e.g., 9-1-1). The TACTICAL CHANNELS are maintained in a standby mode and are reserved for use during a specific incident to satisfy interoperability communications requirements. The Region 20 guidelines for the implementation and technical operation of the CALLING and TACTICAL CHANNELS are described in the following three sections. Calling Channel Implementation Every public safety entity licensed to operate a fixed base or control station in the NPSPAC Band ( / MHz) is required to maintain a radio watch 24-hoursper- day, 7-days-per-week on the National Calling and Tactical Channels. The radio watch shall include the capability to both receive and transmit on the Calling Channel from a central dispatch or communications center, while actively monitoring for an emergency call in order to render assistance to the calling party as necessary and within their capabilities. The monitoring of the NATIONAL CALLING CHANNEL is an appropriate responsibility for a Public Safety Answering Points (PSAP), emergency communications center, or a public safety (police or fire) dispatch center. Only qualified call-takers, radio operators, or emergency operations center personnel shall perform the monitoring of the CALLING CHANNEL. Entities are encouraged to establish central monitoring of the CALLING CHANNEL for adjoining jurisdictions or a sub-region. The central monitoring point shall be capable of distinguishing the location of the received call from a mobile station and subsequently notifying the appropriate jurisdiction without delay. The NATIONAL CALLING CHANNEL will be used only for initial contact and resolution of the emergency request. The CALLING CHANNEL shall not be used as a working channel, once initial contact has been established. Once contact is made and a response is initiated, the local jurisdiction is responsible for assigning a mutual aid or regular response channel. The requesting party (CALLER) shall not be assigned a TACTICAL CHANNEL unless authorized by the Incident Commander. All local jurisdictions within Region 20 with responsibility for call response (Public Safety Answering Point (PSAP)) or primary dispatching for fire, law enforcement or emergency medical services shall actively monitor the CALLING CHANNEL. March

32 Tactical Channel Implementation The NATIONAL TACTICAL CHANNELS are reserved for use during incidents, emergency situations and other public safety events requiring coordination between multiple public safety entities. As an operational guideline, jurisdictions should expect and plan for the TACTICAL CHANNELS serving as a vital link in disasters and major emergencies. The FCC has emphasized that the TACTICAL CHANNELS are not intended for routine, administrative, or intra-agency communications. Planning for the dedication of these channels for use during critical, non-routine situations will insure that the Incident Commander may use these channels as needed for communicating command, control and coordination communications. The TACTICAL CHANNELS are primarily for on-scene incident (tactical or fireground) communications and would not usually be used for extended area coverage. Every public safety entity licensed to operate a fixed base or control station in the NPSPAC Band ( / MHz) is required to implement at least one TACTICAL CHANNEL for every increment of five (or less) NPSPAC Band channels in licensed operation. A licensee operating a 20-channel trunked radio system, for example, is required to operate a fixed base station capability for all five of the National Calling and Tactical Channels. A licensee with a 6-9 channel trunked system would be required to implement a base station for two of the TACTICAL CHANNELS and the CALLING CHANNEL. When more than one TACTICAL CHANNEL is implemented there is no firm requirement that each channel provides complete coverage of the jurisdiction s geographic area. Public safety entities are encouraged to coordinate the location of their TACTICAL CHANNEL base station(s) to avoid overlapping coverage and the selection of the identical channel by an adjoining jurisdiction. The preferred operation of a TACTICAL CHANNEL is the talk-around mode at the incident scene. The mobile repeater function for each TACTICAL CHANNEL base or control station shall be DISABLED but capable of being remotely ENABLED from the primary control point. The Incident Commander shall be responsible for requesting the activation and deactivation of the mobile repeater. In the event that a wider area of coverage is required the Incident Commander shall request the local jurisdiction enable the mobile repeater function for the assigned TACTICAL CHANNEL. A disaster scene may require the activation of the mobile repeater to provide more definitive communications between the Command Post and the staging areas, transportation routes and logistics points, for example. The TACTICAL CHANNEL mobile repeater, when no longer required for emergency communications, shall be DISABLED as soon as possible. Because the TACTICAL CHANNELS are shared across the region the base station licensee must insure that the base station contour does not exceed the jurisdictions boundaries by more than 3 miles (protected service area contour). March

33 Tactical Channel Assignments The limited number of TACTICAL CHANNELS requires that the adopted system of channel assignment for a specific incident shall be carefully controlled. Whenever a mobile repeater function is enabled for a TACTICAL CHANNEL the responsible jurisdiction must immediately notify all adjoining jurisdictions (up to 75 miles). The notification shall identify the event or incident (by name), the CHANNEL involved, the jurisdiction, and the expected duration. The procedures for adjacent jurisdiction notification shall be developed locally. It is recommended that some type of conference or multicast voice system (e.g., NAWAS) be utilized rather than relying on individual telephone calls or a point-to-point radio system (i.e., PMARS). The TACTICAL CHANNELS cross all public safety services (law enforcement, fire, EMS, transportation, etc.) and therefore any utilization notification shall be afforded the widest dissemination. The Region MHz RPRC shall approval the procedures for TACTICAL CHANNEL NOTIFICATION to insure effective use and minimization of interference. Management Guidelines The Region 20 Regional Planning Review Committee (RPRC) has published the approved Region MHz Plan. The Plan was adopted in 1989 and contained very little detail regarding the implementation of the National Calling and Tactical Channels. These guidelines are intended to supplement and expand upon the contents of Section 4 (National Calling and Tactical Channels). The National Calling and Tactical Channels have been addressed by each of the 55 Regions, with varying degrees of implementation. Most regions chose to develop a statewide implementation of the National Calling Channels with strategically selected fixed base station sites and a central control point. The unique composition of Region 20 (the state of Maryland, the District of Columbia, and the Northern counties of Virginia), does not lend itself to the creation of a region-wide implementation, and must therefore accommodate the needs of the individual entities for the common good. The implementation of the NATIONAL CALLING CHANNEL by each jurisdiction in Region 20 is required. First priority shall be the 24 x 7 monitoring of the National Calling Channel. Centralized monitoring is encouraged. Response to an emergency request shall be handled just as a call. Each jurisdiction shall adopt a CALLING CHANNEL PROTOCOL The Calling Channel shall not be used for routine or non-emergency communications. Second priority shall be the implementation of the required number of National Tactical Channel fixed base or control stations. The Region 20 shall recommend a specific TACTICAL CHANNEL(s) to be implemented by a jurisdiction that is required to implement at least one of the Tactical Channels. March

34 Each jurisdiction shall adopt a TACTICAL CHANNEL PROTOCOL for the preassignment of a PRIMARY and a SECONDARY TAC CHANNEL for any incident occurring within their area of responsibility. Each jurisdiction shall adopt a TACTICAL CHANNEL COORDINATION PROTOCOL The Calling Channel shall not be used for routine or non-emergency communications. Third priority shall be development of Region-wide procedures for coordination and resolution of National Calling and Tactical Channel interference and suspected missutilization. Operating requirements and procedures developed by each jurisdiction shall include the requirement that plain ENGLISH language shall be used at all times; the use of unfamiliar terms, codes, or phrases is not allowed. Telephone interconnect (i.e., telephone patch) shall be allowed on any of the National Calling and Tactical Channels. Radio cross patching shall not be allowed on any of the National Calling and Tactical Channels when the channel is operated from a fixed base or control point. Radio cross patching may be allowed, under emergency conditions, when using a transportable (lowpowered) base station (FB2) at an incident scene. Cross patching utilizes twice the channel capacity and increases channel loading significantly. Technical Guidelines Licensee applications for the National Calling and Tactical Channels shall be submitted using FCC form 601 for fixed base and control stations, and optionally for mobile and portable radios. Fixed base and control stations shall provide coverage on the National Calling and Tactical Channels at least equivalent to the mobile and portable ( on-street ) coverage on their radio system NPSPAC channels. The National Calling and Tactical Channels shall be operated in the conventional (nontrunking) mode with analog modulation. All fixed and mobile and portable radio equipment operating on the National Calling and Tactical Channels shall use continuous tone-controlled squelch CTCSS) tone of Hz. None of the National Calling and Tactical Channels shall be incorporated in a trunked radio system. Operational Guidelines The National Calling and Tactical Channels are designated for nationwide public safety use and should be included in any suite of Interoperability solutions. Telephone interconnect (i.e., telephone patch) shall be allowed on any of the National Calling and Tactical Channels. Radio cross patching shall not be allowed on any of the National Calling and Tactical Channels when the channel is operated from a fixed base or control point. Radio cross March

35 patching may be allowed, under emergency conditions, when using a transportable (lowpowered) base station (FB2) at an incident scene. Cross-patching utilizes twice the channel capacity and increases channel loading significantly. The one-way patching of the base frequency transmit audio from a jurisdiction s incident command channel or talkgroup to one of the TACTICAL CHANNELS is allowed but should be determined on a case-by-case basis by the Incident Commander. No means of encryption or voice privacy shall be used on the National Calling Channel. The National Calling and Tactical Channels should be incorporated in the radio communications suite of all public safety mobile command post and communications center vehicles. The National Tactical Channels should be utilized for all multi-agency incidents. Interoperability between Federal, state, and local government entities should primarily take place on the five National Common Channels. Federal use of non-federal communications systems is in compliance with FCC requirements VCALL/VTAC Shared Channel(s) These channels have been used as ground tactical, but have not been repeater licensed. VCALL/VTAC Shared Channel(s) Table 5 VCALL/VTAC Shared Channel(s) Channel Name Primary Use Agencies Supported Frequency/Band VCALL 10 Mutual Aid All Public Safety Agencies*; all VHF are Simplex 100 MHz VTAC 11 Mutual Aid All Public Safety Agencies*; all VHF are Simplex 100 MHz VTAC 12 Mutual Aid All Public Safety Agencies*; all VHF are Simplex 100 MHz VTAC 13 Mutual Aid All Public Safety Agencies*; all VHF are Simplex 100 MHz VTAC 14 Mutual Aid All Public Safety Agencies*; all VHF are Simplex 100 MHz VTAC 17 Mutual Aid All Public Safety Agencies*; all VHF are Simplex 100 MHz VTAC 17D Mutual Aid All Public Safety Agencies*; all VHF are Simplex 100 MHz March

36 March

37 March

38 March

39 Programming the Federal Interoperability Channels 1. If there is enough room in your radio, program all channels as analog and again as digital channels. If not, program as follows: a. Incident Response Channels all analog; b. Law Enforcement Channels - program all as P25 with NAC $68F except LE A, LE 1, LE B, LE 10 and LE 16, which are to be programmed analog with Tx CTCSS Hz (6Z) and no Rx CTCSS (carrier squelch, CSQ). 2. If your radio has a user-selectable option to enable/disable CTCSS on receive, you may choose to configure this option so that the user can enable the same CTCSS tone used on transmit for receive. The default configuration should be CSQ receive. Note on using the Federal Interoperability Channels: These channels may not be used for state/state, state/local or local/local interoperability. A Federal entity must be involved when these channels are used. Regulations and Guidelines for using the Interoperability Channels 1. The FCC and NTIA rules allow for some flexibility in frequency use by personnel directly involved in a situation where there is imminent danger to human life or property. This does NOT mean In an emergency, anything goes. 2. For communications not covered by #1, your use of a radio frequency must be authorized by: a. Your (or your agency s) FCC license or NTIA authorization; b. License by rule a provision in FCC rules that authorizes use of a radio frequency under specified conditions without a specific license or authorization issued to the user; c. A Special Temporary Authorization provided by FCC or NTIA. 3. Digital P25 operations on non-federal interoperability channels should transmit the default Network Access Code (NAC) $293 and receive with NAC $F7E (accept any incoming NAC). Specify talkgroup $FFFF, which includes everyone. Conditions for use of Interoperability Channels 1. The VHF Incident Response (IR) Federal Interoperability Channel Plan, the UHF Incident Response (IR) Federal Interoperability Channel Plan, the VHF Law Enforcement (LE) Federal Interoperability Channel Plan, and the UHF Law Enforcement (LE) Federal Interoperability Channel Plan show frequencies available for use by all Federal agencies to satisfy law enforcement and public safety incident response interoperability requirements. These frequencies will be referred to here in after as Federal Interoperability Channels. 2. The Federal Interoperability Channels are available for use among Federal agencies and between Federal agencies and non-federal entities with which Federal agencies have a requirement to operate. March

40 3. The channels are available to non-federal entities to enable joint Federal/non-federal operations for law enforcement and incident response, subject to the condition that harmful interference will not be caused to Federal stations. These channels are restricted to interoperability communications and are not authorized for routine or administrative uses. 4. Extended operations and congestion may lead to frequency conflicts. Coordination with NTIA is required to resolve these conflicts. 5. Only narrowband emissions are to be used on the Federal Interoperability Channels. 6. Equipment used (transmitters and receivers) must meet the standards established in Section of the NTIA Manual: a. TIA/EIA 603-B for narrowbanding analog; b. TIA TSB 102.CAAB-A for narrowbanding digital. 7. A complete listing of conditions for use by Federal users can be found in Section of the NTIA Manual. 8. Use of these frequencies within 75 miles of the Canadian border and 5 miles of the Mexican border require special coordination and in some cases will not be available for use. Emergency Responders using the Calling Channels As you approach an incident scene or staging area, you might establish contact on a dispatch or working channel. If you can t make contact, or if no channel was designated for this purpose, attempt to make contact on one of the designated interoperability calling channels. If it is a repeater channel and you receive no response, try the direct or talkaround mode if your radio has that capability. In some cases, the talk-around channel exists as a district channel on the radio. For example, the VHF Incident Response Federal Interoperability Channel is known as NC 1. The talk-around for this repeater channel is known as IR 5. The non-federal nation interoperability calling channels are VCALL10, UCALL40 and 8CALL90; the Federal IR and LE calling channels NC 1 (direct: IR 5 ), NC 2 (direct: IR 15 ), LE A, and LE B. If you are unable to make contact on these channels, consider the wideband interoperability channels if you are authorized to use them, or if your situation qualifies as IMMEDIATE protection of life or property. You may be able to learn what you need without transmitting, by just listening to radio traffic on one of these channels. 2 2 Information for this section are excerpts from the National Interoperability Field Operations Guide March

41 3.2.3 UCALL/UTAC Shared Channel(s) These channels have been used as ground tactical, but have not been repeater licensed. UCALL/UTAC Shared Channel(s) Table 6 UCALL/UTAC Shared Channel(s) Channel Name Primary Use Agencies Supported Frequency/Band WASHINGTON COUNTY UCALL 40 Mutual Aid All Public Safety Agencies 400 MHz UCALL 40D Mutual Aid All Public Safety Agencies 400 MHz UTAC 41 Mutual Aid All Public Safety Agencies 400 MHz UTAC 41D Mutual Aid All Public Safety Agencies 400 MHz UTAC 42 Mutual Aid All Public Safety Agencies 400 MHz UTAC 42D Mutual Aid All Public Safety Agencies 400 MHz UTAC 43 Mutual Aid All Public Safety Agencies 400 MHz UTAC 43D Mutual Aid All Public Safety Agencies 400 MHz March

42 March

43 March

44 Programming the Federal Interoperability Channels 1. If there is enough room in your radio, program all channels as analog and again as digital channels. If not, program as follows: a. Incident Response Channels all analog; b. Law Enforcement Channels - program all as P25 with NAC $68F except LE A, LE 1, LE B, LE 10 and LE 16, which are to be programmed analog with Tx CTCSS Hz (6Z) and no Rx CTCSS (carrier squelch, CSQ). 2. If your radio has a user-selectable option to enable/disable CTCSS on receive, you may choose to configure this option so that the user can enable the same CTCSS tone used on transmit for receive. The default configuration should be CSQ receive. Note on using the Federal Interoperability Channels: These channels may not be used for state/state, state/local or local/local interoperability. A Federal entity must be involved when these channels are used. Regulations and Guidelines for using the Interoperability Channels 1. The FCC and NTIA rules allow for some flexibility in frequency use by personnel directly involved in a situation where there is imminent danger to human life or property. This does NOT mean In an emergency, anything goes. 2. For communications not covered by #1, your use of a radio frequency must be authorized by: a. Your (or your agency s) FCC license or NTIA authorization; b. License by rule a provision in FCC rules that authorizes use of a radio frequency under specified conditions without a specific license or authorization issued to the user; c. A Special Temporary Authorization provided by FCC or NTIA. 3. Digital P25 operations on non-federal interoperability channels should transmit the default Network Access Code (NAC) $293 and receive with NAC $F7E (accept any incoming NAC). Specify talkgroup $FFFF, which includes everyone. Conditions for use of Interoperability Channels 1. The VHF Incident Response (IR) Federal Interoperability Channel Plan, the UHF Incident Response (IR) Federal Interoperability Channel Plan, the VHF Law Enforcement (LE) Federal Interoperability Channel Plan, and the UHF Law Enforcement (LE) Federal Interoperability Channel Plan show frequencies available for use by all Federal agencies to satisfy law enforcement and public safety incident response interoperability requirements. These frequencies will be referred to here in after as Federal Interoperability Channels. 2. The Federal Interoperability Channels are available for use among Federal agencies and between Federal agencies and non-federal entities with which Federal agencies have a requirement to operate. March

45 3. The channels are available to non-federal entities to enable joint Federal/non-federal operations for law enforcement and incident response, subject to the condition that harmful interference will not be caused to Federal stations. These channels are restricted to interoperability communications and are not authorized for routine or administrative uses. 4. Extended operations and congestion may lead to frequency conflicts. Coordination with NTIA is required to resolve these conflicts. 5. Only narrowband emissions are to be used on the Federal Interoperability Channels. 6. Equipment used (transmitters and receivers) must meet the standards established in Section of the NTIA Manual: a. TIA/EIA 603-B for narrowbanding analog; b. TIA TSB 102.CAAB-A for narrowbanding digital. 7. A complete listing of conditions for use by Federal users can be found in Section of the NTIA Manual. 8. Use of these frequencies within 75 miles of the Canadian border and 5 miles of the Mexican border require special coordination and in some cases will not be available for use. Emergency Responders using the Calling Channels As you approach an incident scene or staging area, you might establish contact on a dispatch or working channel. If you can t make contact, or if no channel was designated for this purpose, attempt to make contact on one of the designated interoperability calling channels. If it is a repeater channel and you receive no response, try the direct or talkaround mode if your radio has that capability. In some cases, the talk-around channel exists as a district channel on the radio. For example, the VHF Incident Response Federal Interoperability Channel is known as NC 1. The talk-around for this repeater channel is known as IR 5. The non-federal nation interoperability calling channels are VCALL10, UCALL40 and 8CALL90; the Federal IR and LE calling channels NC 1 (direct: IR 5 ), NC 2 (direct: IR 15 ), LE A, and LE B. If you are unable to make contact on these channels, consider the wideband interoperability channels if you are authorized to use them, or if your situation qualifies as IMMEDIATE protection of life or property. You may be able to learn what you need without transmitting, by just listening to radio traffic on one of these channels. 3 3 Information for this section are excerpts from the National Interoperability Field Operations Guide March

46 3.2.4 WAGIN Shared Channel(s) These channels have been used as ground tactical, but have not been repeater licensed. WAGIN Shared Channel(s) Table 7 WAGIN Shared Channel(s) Channel Name Primary Use Agencies Supported Frequency/Band WASHINGTON COUNTY Primary Dispatch WCSO1 Law Enforcement WCSO and MSP UHF HPD1 Law Enforcement HPD UHF FIRE MAIN Fire and EMS All Fire and EMS UHF Secondary Dispatch WCSO2 & 3 Law Enforcement WCSO and MSP UHF HPD2 & 3 Law Enforcement HPD UHF Tactical Talkgroups OPS1 Law Enforcement WCSO, HPD, MSP UHF OPS2 Law Enforcement WCSO, HPD, MSP UHF OPS3 Law Enforcement WCSO, HPD, MSP UHF OPS4 Law Enforcement WCSO, HPD, MSP UHF OPS5 Law Enforcement WCSO, HPD, MSP UHF FIRE OPS Fire and EMS All Fire and EMS UHF TAC1 thru TAC6 Fire and EMS All Fire and EMS UHF WC Emergency Management AREA1 thru 3 GARRETT COUNTY Emergency Management All Fire/EMS and Law Enforcement UHF GC Fire VHF Fire and EMS Fire/EMS VHF GC Fire Lowband Fire and EMS Fire VHF-Lo GC Sheriff Lowband Sheriff Sheriff VHF-Lo STATE MSP MSP Lowband MSP VHF SHA Lowband SHA VHF Calling/Tactical Shared Channel Technology Overview [Add text] Calling/Tactical Shared Channel Policies and Procedures [Add text] Calling/Tactical Shared Channel Rules of Use [Add text] March

47 Calling/Tactical Shared Channel Problem ID and Resolution [Add text] 3.3 Gateways Gateway systems interconnect channels of disparate systems (whether on different frequency bands or radio operating modes), allowing first responders using their existing radios and channels to be interconnected with the channels of other users outside of their agency. Dispatch consoles that are able to create patches will also be captured as gateways. Gateways are listed in the following table. More detailed information on each gateway is provided in Appendix E. Gateway Name PHASE I SITES Washington County Table 8 Western Region Gateway Systems Owning Agency Day-to-Day or Incident / Event Make / Model Fixed / Mobile No. of Simultaneous Nets Elliott Parkway WAGIN Day-to-Day CISCO Fixed 50 across all West Washington WAGIN Day-to-Day CISCO Fixed 50 across all 4 Motobridge (5 sites) WC ECC Incident/ Event Motorola Fixed Sidling Hill WC ECC Incident/ Event Motorola Fixed -Hwy 65 & I-70 WC ECC Incident/ Event Motorola Fixed -Fairview WC ECC Incident/ Event Motorola Fixed -Lambsknoll WC ECC Incident/ Event Motorola Fixed -Quirauk WC ECC Incident/ Event Motorola Fixed ICRI 1 WC HPD Incident/ Event CAT Mobile 5 5 ICRI 2 WC DES Incident/ Event CAT Mobile 5 5 Allegany County Allegany Tower WAGIN Day-to-Day CISCO Fixed 50 across all 10 Allegany Bunker WAGIN Day-to-Day CISCO Fixed 50 across all 4 Eagle Rock WAGIN Day-to-Day CISCO Fixed 50 across all 8 Dan s Rock (county) WAGIN Day-to-Day CISCO Fixed 50 across all 8 Dan s Rock (SHA) WAGIN Day-to-Day CISCO Fixed 50 across all 6 ACU-T 1 Allegany County Incident/Event Raytheon ACU-T Mobile 3 6 ACU-T 2 Allegany County Incident/Event Raytheon ACU-T Mobile 3 6 Garrett County Garrett PSAP WAGIN Day-to-Day CISCO Fixed 50 across all 6 PSI-Net WAGIN Day-to-Day CISCO CM Fixed PHASE II SITES RT 135 SHA Thayerville WVTV Garrett County Garrett County No. of Ports Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all 8 March

48 Gateway Name Grantsville MIEMMSS Keysers Ridge SHA Martin Mountain SHA Town Hill DNR Savage Mountain SHA Westernport Owning Agency Garrett County Garrett County Allegany County Allegany County Allegany County Allegany County Day-to-Day or Incident / Event Make / Model Fixed / Mobile No. of Simultaneous Nets No. of Ports Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all Region-wide Gateway Policies and Procedures Region-wide Gateway Rules of Use The following rules of use shall govern interoperable communications between agencies via gateways: National Incident Management System Use an Incident Command System (ICS) compliant with the National Incident Management System (NIMS) when using any regional interoperability resource. Plain Language All interoperable communications during multi-agency, multidiscipline incidents will be in plain language. Avoid using radio codes, acronyms, and abbreviations as they may cause confusion between agencies. Ensure that all verbal requests for assistance or backup specify the reason for the request. Unit Identification Announce your home agency prior to announcing your unit identifier during interoperable communication situations. (i.e., Allegany County Engine Rescue 16) National Response Plan Under the National Response Plan, ICS forms will be used for all appropriate documentation. Encryption All encrypted radios users must operate in a clear mode when a gateway is used, unless otherwise arranged in advance. Never assume encryption carries across the gateway. Monitoring The Incident Commander, or their designee, will ensure that each activated interoperability channel is monitored consistently while in use. Region-wide Gateway Communications Request The COML and/or Incident Commander must be aware that activating multiple gateways to support an incident can result in mutual interference. Interference issues are best resolved by the technical support team assigned to the gateways. March

49 The agency requesting the use of a fixed or mobile gateway device for incident/event communications support should document and provide the following information to the owning gateway agency POC, on request: Requesting agency On-scene agencies requiring interoperability Incident/event type (e.g., wild land fire, etc.) Equipment required Expected duration of event Location required/access information Incident POC User/requestor and/or servicing dispatch contact phone number Additional support services requested (e.g., gateway operator, generator, etc.) Region-wide Gateway Deployment Procedures Upon receiving a request for the deployment of a mobile gateway, the owning agency dispatcher should follow these deployment procedures: Contact the on-call mobile gateway operator/technician responsible for mobile gateway deployment. Dispatch the mobile gateway operator to the incident scene. Inform the requesting agency that the mobile gateway is en route and provide an estimated time of arrival (ETA), if available. The mobile gateway operator should follow these deployment procedures: Provide dispatch with an ETA at the incident and method of communications while en route (e.g., designated radio channel, cell number). Retrieve the dedicated unit and mobile gateway from its storage location and deliver it to the incident scene Report to the Incident Commander or Check-in on arrival. Once on-scene, establish patches via the mobile gateway in accordance with the Gateway Activation Procedures listed above. Region-wide Gateway Activation Procedures Once the owning agency grants authorization to use their fixed gateway, the region-wide procedures for establishing communications connectivity are: Select a channel or talkgroup on the home system for use in the gateway patch. Verify the system-wide availability of required resources (coordinate among control point dispatchers). Provide radio call sign/designator information to connected agencies as needed. Assign the requested unit/agency to that channel or talkgroup. Connect the agency to the appropriate talkgroup. March

50 Announce to users that interoperability is activated. Identify users on the interoperability channel using their agency name and unit identifier through a roll call. Monitor the interoperability channel to address requests. Region-wide Gateway Deactivation Procedures When the gateway connection(s) is (are) no longer required, agencies should follow these deactivation procedures: Contact the monitoring dispatcher (for fixed gateways) or the mobile gateway operator (for mobile gateways) to request patch/gateway deactivation. Announce over all patched channels/talkgroups that connections will be deactivated prior to the connection being disabled. Return all personnel to their appropriate home system channel assignments. Region-wide Gateway Problem ID and Resolution During an incident: Report gateway problems to the owning agency dispatcher (for fixed gateways) or mobile gateway operator (for mobile gateways), who will follow established agency procedures to resolve the problem. Following an incident, the following general problem ID and resolution processes apply to all regional gateways: Report any problems with the gateway to the appropriate POC for that agency listed in Appendix E. The POC will be responsible for ensuring effective resolution to problems that exist with the gateway. Report unresolved gateway problems directly to the Western Region Communications Coordinator/COML/designee. The Western Region Communications Coordinator/COML/designee ensures effective resolution to reported gateway problems. Region-wide Gateway Limitations Interoperability provided through a gateway can connect participating agency responders but has the following limitations: The number of simultaneous patches that can be supported by the gateway will be limited by switch capacity and the number of lines connecting control centers and consoles. As a result, a limited number of patches involving resources at different control points can be supported simultaneously. Likewise, a limited number of patches involving resources that are accessed through a communications center console may be supported simultaneously. Home system coverage may limit communications. Gateway users must be within the footprint of their coverage area. March

51 Agencies not permanently configured on a given gateway will require additional planning to establish interoperable communications through that gateway. Region-wide Gateway Test Procedures To ensure that equipment components of the gateway operate properly, each agency will participate in the following testing procedure: Representatives from multiple agencies should meet on a regular basis to test each gateway. Testing should include deployment (mobile only), setup, operation, and deactivation of each gateway. If an issue or problem is identified during the testing procedure, determine who will take corrective action. If the issue or problem cannot be resolved, contact the appropriate technical personnel to address the issue or problem. Weekly PSAP testing of the WAGIN IPICS is scheduled for every Monday at The duration of the tests is 30 seconds and results are logged for quality control and assurance. Any connectivity issues are to be addressed immediately. The Weekly PSAP Testing follows a monthly rotation and is to be initiated in the following order each week by the named jurisdiction/agency: Week 1 Washington Week 2 Allegany Week 3 Garrett Week 4 MJOC Week 5 DNR 3.4 Cache Radios Cache radios, also known as swapped radios, refer to maintaining a cache of standby radios that can be deployed to support regional incidents. These radios may be from a regional cache or from a participating agency. These radios allow all responders to use common, compatible equipment during an incident. Specific caches within the Western Region are listed in the following table. Detailed information on cache radios can be found in Appendix F. Table 9 Western Region Radio Cache(s) Radio Cache Owning / Managing Frequency Make / Model Name Agency Band Quantity WASHINGTON COUNTY WC DES UHF Motorola/2500 WC DES UHF 10 WC ECC UHF Motorola/2500 WC DES UHF 10 WC SO UHF Motorola/2500 WC SO UHF 10 March

52 Radio Cache Make / Model Name ALLEGANY COUNTY Owning / Managing Agency Frequency Band Allegany ACES Kenwood 880 Allegany ACES UHF Region-wide Cache Radio Policies and Procedures Quantity Western Region radio caches have the following characteristics: Portable radios are fully charged and maintained, ready for immediate deployment. Deployed equipment includes battery chargers to support extended deployments. Personnel are available to transport equipment to the incident scene. Technicians are available for on-scene support during the deployment. Table 10 Optional Channels for Western Region 800 MHz Cache Radio(s) Channel Name Primary Use National Common Names are utilized in the Western Region. The adoption of uniform common channel naming, in concert with programming and using existing national interoperability channels, allows jurisdictions across various disciplines to effectively share information on demand and in real time during an incident. Utilizing common nomenclature avoids the confusion created by using disparate coded language systems and various tactical interoperability frequencies. Interoperability requirements for agencies operating in the same frequency band are addressed by utilizing the National Common Names. VHF Cache Radios All Western Region VHF radio caches are required to have the following channels programmed: Channel Name VCALL10 VCALL11 VTAC12 VTAC13 VTAC14 Table 11 Required Channels for Western Region VHF Cache Radio(s) Primary Use Public Safety Public Safety Public Safety Public Safety Public Safety If possible, the following channels should also be programmed into Western Region VHF cached radios: March

53 Table 12 Optional Channels for Western Region VHF Cache Radio(s) Channel Name Primary Use UHF Cache Radios All Western Region UHF radio caches are required to have the following channels programmed: Table 13 Required Channels for Western Region UHF Cache Radio(s) Channel Name Primary Use Agencies Supported Frequency/Band UCALL 40 Mutual Aid National Interop. UHF UCALL 40D Mutual Aid National Interop. UHF UTAC 41 Mutual Aid National Interop. UHF UTAC 41D Mutual Aid National Interop. UHF UTAC 42 Mutual Aid National Interop. UHF UTAC 42D Mutual Aid National Interop. UHF UTAC 43 Mutual Aid National Interop. UHF UTAC 43D Mutual Aid National Interop. UHF If possible, the following channels should also be programmed into Western Region VHF cached radios: Table 14 Optional Channels for Western Region UHF Cache Radio(s) Channel Name Primary Use Region-wide Radio Cache Rules of Use The following are general rules of use and apply to all Western Region radio caches: National Incident Management System Use an Incident Command System (ICS) compliant with the National Incident Management System (NIMS) when using any regional interoperability resource. Plain Language All interoperable communications during multi-agency, multidiscipline incidents will be in plain language. Avoid using radio codes, acronyms, and abbreviations as they may cause confusion between agencies. Ensure that all verbal requests for assistance or backup specify the reason for the request. Unit Identification Announce your home agency prior to announcing your unit identifier during interoperable communication situations. (i.e., Allegany County Fire Rescue 16). National Response Plan Under the National Response Plan, ICS forms will be used for all appropriate documentation. March

54 Equipment Return The requesting agency is responsible for the return of any cache radios/equipment in the condition that they were received. OR Responsibilities for lost or damaged equipment lie with the appropriate agency as dictated by existing Memoranda of Agreement (MOAs). Region-wide Radio Cache Request The Incident Commander, or their designee, determines when a situation exists that requires the use of a regional radio cache and notifies the appropriate dispatch center. The dispatch center will follow internal agency procedures to contact the COML or Radio Cache Agency POC and relay pertinent information regarding the event. The requesting agency documents and provides the following information to the Radio Cache Agency POC, on request: Requesting agency On-scene agencies requiring interoperability Incident/event type of event (e.g., wild land fire, etc.) Equipment requirements Expected duration of event Location required/access information Incident POC User/requestor and/or servicing dispatch contact phone number Additional support services requested (e.g., technician, chargers, etc.) The Radio Cache Agency determines what radio caches are available for use, identifies a specific cache, activates that cache, and coordinates the cache deployment with the requesting agency Incident Commander or their designee. Region-wide Radio Cache Equipment Activation Upon receiving a request for the deployment of a radio cache, the owning agency dispatcher should follow these deployment procedures: Contact the on-call technician responsible for radio cache deployment. Dispatch the radio cache technician (or an approved designee) to the incident scene. Inform the requesting agency that the radio cache is en route and provide an estimated time of arrival (ETA), if available. The radio cache technician (or designee) should follow these deployment procedures: Provide dispatch with an ETA at the incident. Retrieve the radio cache from its storage location and deliver it to the incident scene. Report to the Incident Commander or Check-in on arrival. March

55 Once on-scene, sign the cache over to the requesting agency for incident use or, if assigned to remain on scene, coordinate radio cache deployment procedures with the Communications Unit. o Each radio in the radio cache will have a unique identification number for inventory tracking. Ask the receiving agency to sign a property transfer form if they take responsibility for managing the radio cache on scene. o The requesting Incident Commander/ designee will be responsible for: Supporting radio deployments on-scene Maintaining a record of each user and agency to whom a radio and associated accessories have been distributed Documenting the identification number of each radio deployed Documenting the channel(s) in use Each user and/or agency that receives a radio from the radio cache will be responsible for returning that radio and all associated accessories to the cache at the end of the incident. Region-wide Radio Cache Equipment Deactivation When the radio cache is no longer required, agencies should follow these deactivation procedures: Coordinate the return of all cache radios to the Communications Unit through the Incident Commander/designee. The Communications Unit will be responsible for inventorying all radios and accessories returned to the cache. Before leaving the incident scene, the Communications Unit will determine if any radios have not been returned to the radio cache and note the user and agency to which the radio was distributed. Provide this information to the Incident Commander or their designee. If the missing radios cannot be recovered at the incident scene, the Communications Unit will provide this information to the Radio Cache Agency POC for resolution. Region-wide Radio Cache Problem ID and Resolution During an incident: Report radio cache problems to the radio cache technician/designee who will follow established agency procedures to resolve the problem. Following an incident, the following general problem ID and resolution processes apply to all regional radio caches: Report any problems with the radio cache to the appropriate POC for the owning agency listed in Appendix F. The POC will be responsible for ensuring effective resolution to problems that exist with the radio cache. March

56 Report unresolved radio cache problems directly to the Western Region Communications Coordinator/COML/designee. The Western Region Communications Coordinator/COML/designee ensures effective resolution to reported radio cache problems. 3.5 Mobile Communications Units A mobile communications Unit (MCU) (also known as a Mobile Communications Center (MCC), Mobile Command Vehicle (MCV), or Mobile EOC) refers to any vehicular asset that can be deployed to provide or supplement communications capabilities in an incident area. Examples of the types of communications devices an MCU can house are: subscriber and base station radios of various frequency bands, gateway devices, satellite phones, wireless computer networks, video broadcasting/receiving equipment, etc. Typically these communications devices are permanently located/stored in the MCUs when not used. The MCU should also be able to temporarily provide the electrical power required to operate the communications devices. More detailed information on each MCU is provided in Appendix G. Table 15 Western Region Mobile Communications Unit(s) Unit ID / Designator FEMA Type Owning Agency Deployment Area WASHIGNTON COUNTY MC18/MCC III WC DES Washington County MCHPD/MCC III WC HPD Washington County ALLEGANY COUNTY AC Cumberland City PD III AC Cumberland City PD Allegany County AC EMA III AC EMA Allegany County GARRETT COUNTY GCPS/MCC III GC Public Safety Garrett County Mobile Communications Unit Policies and Procedures Region-wide Mobile Communication Units Rules of Use The following are general rules of use and apply to all Preparedness Area 6 radio caches: National Incident Management System Use an Incident Command System (ICS) compliant with the National Incident Management System (NIMS) when using any regional interoperability resource. National Response Plan Under the National Response Plan, ICS forms will be used for all appropriate documentation. Equipment Return The requesting agency is responsible for the return of any mobile communication units in the condition that they were received and/or as dictated by existing Memoranda of Agreement (MOAs). Resource Modifications The requesting agency is not allowed to change anything in the mobile communications unit without written permission of the March

57 owning agency. Should a modification need to be made, (i.e., changing an electric end) the requesting agency will incur costs of any modification/restoration. Operational Expenses Operational expenses should be decided upon ahead of time or within an MOU. Region-wide Mobile communications unit Request The Incident Commander/designee, determines when a situation exists that requires the use of a regional mobile communications unit and notifies the appropriate dispatch center. The dispatch center will follow internal agency procedures to contact the COML or mobile communications unit agency POC and relay pertinent information regarding the event. The requestor documents and provides the following information to the mobile communications unit agency POC, on request: Requesting agency On-scene agencies requiring resource Incident/event type of event (e.g., wild land fire, etc.) Equipment requirements Expected duration of event Location required/access information Incident POC User/requestor and/or servicing dispatch contact phone number Additional support services requested (e.g., technician, chargers, etc.) The mobile communications unit agency determines what mobile communication units are available for use, identifies, activates and coordinates the unit deployment with the requesting agency Incident Commander/designee. Region-wide Mobile communications unit Activation Upon receiving a request for the deployment of a mobile communications unit, the owning agency dispatcher should follow these deployment procedures: Contact the mobile communications unit POC responsible for deployment. Dispatch the mobile communications unit operator to the incident scene. Inform the requesting agency that the mobile communications unit is en route and provide an estimated time of arrival (ETA), if available. The operator should follow these deployment procedures: Provide dispatch with an ETA at the incident. Retrieve the mobile communications unit from its storage location and deliver it to the incident scene. Report to the Incident Commander/designee and check-in on arrival. Once on-scene, operator will prepare the mobile communications unit for operations, if assigned to remain on scene, supervise use of the mobile communications unit. March

58 Region-wide Mobile communications unit Equipment Deactivation When the mobile communications unit is no longer required, agencies should follow these deactivation procedures: Coordinate the return of the mobile communications unit to the owning agency through the Incident Commander/designee. The Logistics Unit will be responsible for inventorying all mobile communications unit equipment. Before leaving the incident scene, the operator will determine if all mobile communications unit equipment is accounted for. Provide this information to the Incident Commander/designee. The mobile communications unit operator will ensure that the unit has been properly configured for movement. Any discrepancies at the incident that cannot be resolved should be reported to the Incident Command. Region-wide Mobile communications unit Problem ID and Resolution During an incident: During activation, report mobile communications unit problems to the owning agency who will then follow established agency procedures to resolve the problem. Following an incident, the following general problem ID and resolution processes apply to all mobile communication units: Report any problems with the mobile communications unit to the appropriate POC for the owning agency listed in Appendix G. The POC will be responsible for ensuring effective resolution to problems that exist with the mobile communications unit. March

59 3.6 RACES The EOC Amateur Radio Team will consist of volunteers from the Radio Amateur Civil Emergency Services (RACES). Upon activation of the EOC and EOC request for deployment, radio operators will report to the EOC, Hagerstown Hospital and other places as necessary and man the radios for the duration of the Emergency. Radio Teams consist of volunteers committed to the operations of the EOC but possibly unable to respond immediately to a deployment. There are several Points of Contact for the Radio Teams listed below in order of contact that will enable the Radio Teams to be deployed in the fullest and fastest manner. Washington County Table 16 RACES Points of Contact Name/Location Cell Phone Home Call Sign Bob Long rjlong@myactv.net KD3JK Herman Niedzielski hajn@myactv.net K2AVA Allegany County Name/Location Cell Phone Home Call Sign Bill Tucker K3UEZ@AOL.com K3UEZ Jim Robinson KB3JRW@ARRL.net KB3JRW Barry Wagoner N8WG@HamTalk.org N8WG Ken Currence N0BSD@HamTalk.org N0BSD Garrett County Name/Location Cell Phone Home Call Sign Bill Shomo bshomo@us.ibm.com KB3FMJ Tim Gift trgift@verizon.net W8VB Activation of the Radio Teams will be the responsibility of the EOC for the RACES Teams. Deactivation of the Radio Teams will be determined by the EOC for the RACES Teams. March

60 The Radio Teams are composed of individuals familiar with all aspects of radio communications in their area of responsibility and will provide multiple and redundant communication avenues in case of emergency deployment and will be able to address all problems/issues associated with their radio systems that may arise as a result of the emergency. Amateur radio equipment in the EOC is capable of operating on frequencies ranging from 144 MHz to 450 MHz. These frequencies allow for communications locally and across the county. RACES is activated by the Radio Officer under local jurisdiction. The Radio Officer is appointed in writing by the local jurisdiction. The Radio Officer appoints RACES Operators under the Presidents War Emergency Powers, Provision Section 706 of the Communications Act of This allows the Amateur Radio Operators to communicate with other RACES and Government Stations. Amateur Radio communications will be in compliance with FCC Rules and Regulations, Part Amateur Radio frequencies are open and not subject to the non-disclosure rules of other radio services. Therefore, these communications should be treated as open mike communications and sensitive information should not be sent via Amateur Radio. Amateur Radio Operators will also operate the Shared Resources High Frequency Radio Program (SHARES). These are Government HF ( MHz) frequencies that provide a single agency emergency message handling system for worldwide communications. SHARES communications will be in compliance with FCC Rules and Regulations. March

61 4 Regional Emergency Resource Staffing Emergency Resource Directory The Emergency Resource Directory establishes a list of personnel who will respond to fill the Communication Unit positions. Identified personnel must train and exercise to a regional response level. See Appendix A, Section A.1 for a list of dispatch centers. Job descriptions and qualified personnel for each Communications Unit position are detailed below. Dispatch Center Communications Coordinator (COMC) The COML will work with the COMC to coordinate communications with other dispatch centers and the incident communication plan. Locally, the jurisdictional dispatch center supervisor or dispatcher will act as the Communications Coordinator. Coordinators may also be located at the region/county, State, and Federal level. At an Incident/Event Communications Unit Leader (COML) Manages the technical and operational aspects of the Communications Function during an incident or event. Develops National Incident Management System (NIMS)/Incident Command System (ICS) Form 205 Incident Radio Communications Plan and supervises the communication unit. Technical Specialist (THSP) Allows for the incorporation of personnel who may not be formally certified in any specific NIMS/ICS position. THSPs may include Local Agency Radio Technicians (as opposed to the COMT), Telephone Specialists, Gateway Specialists, Data/IT Specialists, and or Cache Radio Specialists. Incident Communications Technician (COMT) Deploys advanced equipment and keeps it operational throughout the incident/event. Incident Communications Center Manager (INCM) Supervises the operational aspects of the Incident Communications Center (ICC) (Mobile Unit and/or Fixed Facility). During an incident, the ICC is designed to absorb incident traffic in order to separate that traffic from the day-to-day activities of the dispatch center. The ICC is typically located at the Incident Command Post (ICP) in a fixed site, tent, trailer, mobile communications unit. Radio Operator (RADO) - Staffs a radio at the ICC and is responsible for documenting incoming radio and telephone messages. Incident Dispatchers or Tactical Dispatchers are used as RADOs. The following table lists contact information of the Regional Emergency Resource Personnel for each Communications Unit position. March

62 Table 17 Regional Emergency Resource Personnel COMC Michael Garber Terry Cain Name Agency Address Phone Maryland State Police Maryland State Highway Administration Maryland State Highway Administration COML Gary Davis Michael Garber Terry Cain Maryland State Highway Administration Maryland State Highway Administration Maryland State Highway Administration DNR Other THSP Gateway THSP Cache THSP RADO INCM COMT March

63 5 CASM 5.1 Overview The Communication Assets Survey and Mapping (CASM) tool provides the ability for representatives of public safety agencies within an urban area or State to collect, store, and visualize data about agencies, communication assets, and how agencies use those assets. The purpose of CASM is to: Provide a single repository for information about land mobile radio systems, other interoperability methods, and how they are used by public safety agencies within a state or urban area. Provide a method to display the data. Provide tools to analyze the data and visualize interoperability gaps in accordance with the Interoperability Continuum framework. The CASM tool is composed of two components: the Communication Assets Survey (CAS) and the Communication Assets Mapping (CAM) tool. The CAS component provides a means to enter, edit, and delete information about agencies, communication assets (such as radio systems, dispatch centers, mutual aid channels/systems, gateways and radio caches), and agency usage of those assets. The CAM component provides a means to display this information in a map-based interface and provides analysis tools for displaying agency-to-agency interoperability, including interoperability gaps, in various ways. The CASM tool is web-based and requires the user to have an active internet connection in order to access both the CAS and CAM components. CAS is a website that may be accessed via any internet browser, such as Internet Explorer, Netscape Navigator, or Mozilla Firefox. CAM is a client application that must be downloaded, installed, and executed on the user s computer. A user must have internet access in order to operate CAM. Authorization to view data for a particular urban area or State is controlled by the Western Region Administrative Manager (AM); each user must have a user name and password in order to login. The CASM AM POC is listed in the following table: Table 18 CASM AM POC Information Name Phone Kevin Lewis klewis@washco-md.net Dick DeVore ddevore@allconet.org Brad Frantz bfrantz@garrettcounty.org Area of Responsibility March

64 Appendix A Points of Contacts A.1 Dispatch Centers Table A - 1 Dispatch Center Points of Contact Name 24/7 Contact Organizations / Agencies Served 32 nd Civil Support Team Alcohol, Tobacco, Firearms, and Explosives Allegany County 911 Communications Center Boonsboro Police Department City of Hagerstown Fire Department City of Hagerstown Police Department City of Hagerstown Public Works ext 176 Civil Air Patrol Cumberland City Police Department Cumberland Fire Department Cumberland Public Works Department of Natural Resources Department of Public Works Emergency Management Agency Federal Bureau of Investigation Allegany County Department of Public Safety Allegany County Fire Allegany County EMS Allegany College of Maryland Allegany County Board of Education Allegany County Health Department Bureau of Police Division of EMS Special Operations Team Department of Public Works Allegany County Sheriff s Office Animal Control Division March 2012 A-1

65 Name 24/7 Contact Organizations / Agencies Served Federal Bureau of Prisons Frostburg City Police Department Allegany County Fire Frostburg Public Works x23 Frostburg State University Police Department Allegany County EMS Frostburg University Garrett County PSAP Bureau of Police Garrett County Animal Control Garrett County Board of Education Garrett County Department of Public Safety Garrett County EMS Garrett County Fire Garrett County Health Department Garrett County Public Roads Garrett County Public Utilities Garrett County Sheriff s Department (GCSD) Hancock Police Department Highway Administration Maryland Department of Environment Maryland Division of Corrections Maryland Institute for Emergency Medical Services Systems (MIEMSS) Maryland National Guard Maryland State Police Barracks C Maryland State Police Barracks O Maryland State Police Barracks B Maryland State Police Barracks W Mine Safety and Health Administration National Park Service Smithsburg Police Department St. Mary s County Government March 2012 A-2

66 Name 24/7 Contact Organizations / Agencies Served US Marshals Service (Baltimore) US Park Police US Secret Service Washington County Board of Education Washington County Division of Emergency Services Washington County ECC Washington County Emergency Management Washington County Health Department Washington County Humane Society Washington County Department of Public Works Washington County Division of Environmental Management Washington County Highways Washington County Sheriff s Office Washington County Transit Washington County Volunteer Fire and Rescue Association A.2 Nongovernmental Agency Contact Information Table A - 2 Nongovernmental Agency Contact Information Agency Name Position Phone AAA Ambulance Service Allegany Ambulance Service Applied Energy Services Bishop Walsh Middle/High School Brook Lane Psychiatric Hospital March 2012 A-3

67 Agency Name Position Phone Butler Medical Transport Service Columbia Gas County Medical Transport Service CSX Garrett County Memorial Hospital Garrett Medical Transport Hagerstown Community College HealthNet Life Flight MedStar Norfolk Southern Potomac Edison Power Potomac Valley Hospital RACES Red Cross Salvation Army STAT Med-Evac Valley Medical Transport Verizon Meritus Medical Center Western Maryland Health System Western Maryland Hospital Center March 2012 A-4

68 A.3 Executive Committee Member Information Table A - 3 Subcommittee Member Information Agency Name Position Phone Subcommittee(s) Washington Co. Division of Emergency Services Allegany Co. Emergency Sercives Garrett County Public Safety Kevin Lewis Director (240) klewis@washco-md.net WAGIN Chair Richard DeVore Emergency Management Chief, Acting Communications Chief (301) ddevore@allconet.org Jon Bradley Frantz Director (301) bfrantz@garrettcounty.org A.4 WAGIN Workgroup Member Information Table A - 4 WAGIN Workgroup Contact Information WAGIN Executive Committee WAGIN Executive Committee Agency Name Position Phone Allegany Co. Commissioners Garrett Co. Commissioners Washington Co. Commissioners MSP Electronic Services SHA District 6 Michael W. McKay David A. Eberly President Commissioner.McKay@allconet.org County Administrator countyadministrator@allconet.org Gregon Crawford President gcrawford@garrettcounty.org R. LaMont Pagenhardt County Administrator mpagenhardt@garrettcounty.org Terry Baker President tbaker@washco-md.net Gregory Murray Alan Hepding Anthony Crawford County Administrator Technical Supervisor gmurray@washco-md.net ahepding@mdsp.org District Engineer acrawford@sha.state.md.us Governing Body(s) County Commissioners County Administrator County Commissioners County Administrator County Commissioners County Administrator March 2012 A-5

69 ARINC Agency Name Position Phone Washington Co. Division of Emergency Services SHA Communications State of Maryland Interoperability PMO Beth Leek Director, Public & Enterprise Solutions Charlie Summers Craig Fetzer Division Chief Curt Andrich Project Manager Cisco Robert Bowman Account Manager ARINC Dave Chapman Product Manager DNR Wireless David Christner Technician Manager DNR Wireless Ed Ryan Director MEMA Erica Carlson Regional Administrator MSP Electronic Services Gary Davis Section Chief SHA District 6 Gary Shank Asst. District Engineer Maint gshank@sha.state.md.us SHA District 6 George Small Asst. District gsmall@sha.state.md.us TWR Maryland Interoperability Program Management Office Harry Wolford Engineer Traffic Sales & Service Engineer wink.wolford@twrcommunications.com Lori Stone lstone@law.umaryland.edu ARINC Marvin Ingram Senior Director mingram@arinc.com MSP Information Technology Mike Roosa Director mroosa@mdsp.org Washington County Communications Pete Loewenheim Manager ploewenheim@washco-md.net Maintenance SHA Philip Lazarus Asst. Division Chief plazarus@sha.state.md.us Governing Body(s) Technical Subcommittee March 2012 A-6

70 Agency Name Position Phone MIEMSS Communications MIEMSS Communications ARINC State of Maryland Allegany County 911 Joint Communications Division SHA Office of Maintenance Garrett County Public Safety Allegany County Emergency Services SHA Communications Reuben Fairchild Engineer PSInet Rich Berg Robert Anderson Ray Lehr Director of Communications Engineering Services Engineering Manager Interoperability Director Roger Bennett Chief Russ Yurek Director Stephen Smith Asst. Director Susan Lee Acting Chief Terry Cain Technician Skyline Tom Miller Garrett County Public Safety Virginia Smith EM Planner Maryland Emergency Acting MJOC Gary Zamerski Management Manager Agency Governing Body(s) March 2012 A-7

71 A.5 Agency Information Table A - 5 Washington County Agency Information Company Number Company Name Address Officers Pagers/Cell Telephone Fax Department of Emergency Services 18 Div. of Fire & Emergency Services 33 West Washington Street Hagerstown, MD Kevin Lewis, Director klewis@washco-md.net Charlie Summers, Deputy Director csummers@washco-md.net Emergency Management 33 West Washington Street Hagerstown, MD Brigitte Heller, EMS Coordinator bheller@washco-md.net Verna Brown, CEM - EMA Coordinator vbrown@washco-md.net Sam Anderson, Emergency Planner sanderson@washco-md.net Fire & Rescue Communications / West Washington Street Hagerstown, MD Bardona Woods, Chief bwoods@washco-md.net Roy Lescalleet, Deputy Chief rlescalleet@washco-md.net Special Operations Team 638 Frederick St. Hagerstown, MD Emergency Air Unit York Road Hagerstown, MD Jennifer Swisher, Assistant Chief jswisher@washco-md.net John Bentley, Chief Andy West, Deputy Chief Bill Snodderly, Chief Ed Brady, Deputy Chief Les Adelsberger, Captain (Alpha Page) Answering. Serv Advisory Boards & Committees March 2012 A-8

72 Company Number Company Name Address Officers Pagers/Cell Telephone Fax Emergency Services Advisory Board Council Chair - Commissioner Jim Kercheval Fire & Rescue Communications Advisory Committee Chair - Ron Horn Local Emergency Planning Committee Co-Chairs - Kevin Lewis & Doug Mullendore Washington County Citizen Corps - POC - Verna Brown 33 West Washington Street Hagerstown, MD Association 14 Washington County Volunteer Fire & Rescue Association 1501 Pennsylvania Ave. Hagerstown, MD Glenn Fishack, President Clinton Stouffer, 1st VP Skip Menzies, 2nd VP Rick Blair, Administrative Asst. Becky Maginnis: Accident Reporting Fire Companies 1 Sharpsburg Volunteer Fire Co, Inc. 2 Williamsport Volunteer Fire & Emergency Medical Services, Inc. P.O. Box W. Chapline St. Sharpsburg, MD P.O. Box Brandy Drive Williamsport, MD James Morgan, Chief Allen James, Deputy Chief Chris Mullendore, Assistant Chief William Ball, Chief Fred Cole, Deputy Chief Michael Grinder, Assistant Chief (cell) (cell) March 2012 A-9

73 Company Number Company Name Address Officers Pagers/Cell Telephone Fax 4 Clear Spring Volunteer Fire Dept. P.O. Box Mulberry Street Clear Spring, MD Mike Reid, Chief Warren Royce, Deputy Chief Craig Werner, Assistant Chief (cell) Hancock Volunteer Fire Company, Inc. 3 Fulton Street Hancock, MD Greg Yost, Chief Robert Hoopengardner, Deputy Chief Bill Willison, Assistant Chief The First Hose Company of Boonsboro, Inc. Substation 8 7 Smithsburg Community Volunteer Fire Company 5 Saint Paul Street Boonsboro, MD Rohrersville Road Rohrersville, MD P.O. Box N. Main St. Smithsburg, MD Oley Griffith, Chief John Sherwood, Deputy Chief Jay Brandenburg, Assistant Chief Oley Griffith, Chief John Sherwood, Deputy Chief Jay Brandenburg,, Assistant Chief Steve Lewis, Chief Chris Rohrer, Deputy Chief Patrick Baker, Assistant Chief (cell) (cell) Leitersburg Volunteer Fire Company, Inc Leiter Street Hagerstown, MD Kirk Mongan, Chief Kenny Diffenderfer, Deputy Chief Clinton Stouffer, Assistant Chief Funkstown Volunteer Fire Company Inc. P.O. Box S. Westside Avenue Funkstown, MD Dave Fraley, Chief Steve Pifer, Deputy Chief Kevin Kotanko, Assistant Chief March 2012 A-10

74 Company Number Company Name Address Officers Pagers/Cell Telephone Fax 11 Potomac Valley Volunteer Fire Co Dargan School Road Sharpsburg, MD Ronnie Gray, Chief Arnold Martin, Deputy Chief Eric Gray, Assistant Chief Fairplay Volunteer Fire Company 13 Maugansville Goodwill Volunteer Fire Co. 16 Mt Aetna Volunteer Fire Department 26 The Volunteer Fire Company of Halfway, Md., Inc. P.O. Box Tilghmanton Road Fairplay, MD P.O. Box Maugansville Road Maugansville, MD Crystal Falls Drive Hagerstown, MD Lincoln Avenue Hagerstown, MD Leonard Heller, Jr, Chief Ira Heller, Captain Brian Chaney, Lieutenant William Garrett, Chief Ian Swisher, Deputy Chief Travis Keefer, Assistant Chief Terry Stouffer, Chief Scott Smith, Deputy Chief Eric Banfe, Assistant Chief Jeff Ringer, Chief Edward Ernst, Deputy Chief Nicola Dattilio, Asst Chief -Fire James Drawbaugh, Asst Chief-EMS (cell) (cell) (cell) Longmeadow Volunteer Fire Company, Inc Longmeadow Road Hagerstown, MD Jason Eckstine, Chief Adam Hopkins, Deputy Chief John Latimer, IV, Assistant Chief (cell) Hagerstown Fire Department March 2012 A-11

75 Company Number Company Name Address Officers Pagers/Cell Telephone Fax Hagerstown Fire Department 25 W. Church St. Hagerstown, MD Gary Hawbaker, Chief Ronald Horn, Deputy Chief Battalion 1 Mark Cleck, Captain Justin Mayhue, Battalion Chief Battalion 2 Randy Myers, Battalion Chief Brian Pile, Captain Battalion 3 Kyd Dieterich, Battalion Chief Russell Grim, Captain Douglas DeHaven, Fire Marshal Cindy Lewis, Admin. Coordinator E-1 First Hagerstown Hose Co E-2 Antietam Fire Company E-3 Independent Junior Fire Engine Company E-4 Western Enterprise Fire Company 33 S. Potomac Street Hagerstown, MD Summit Avenue Hagerstown, MD P.O. Box Eastern Boulevard North Hagerstown, MD Washington Square Hagerstown, MD Andy Smith, Captain Blaine Snyder, President James Sprecher, Jr, Captain Jeff Snyder, President Woody Morris, Captain Charles Elgin, President James Schaffer, President Clyde Tressler, Vice President March 2012 A-12

76 Company Number Rescue Companies Company Name Address Officers Pagers/Cell Telephone Fax E-5 South Hagerstown Fire Company Truck 1 Pioneer Hook & Ladder Company 19 Sharpsburg Area Emergency Medical Services Inc. 35 Washington County Regional Airport 49 Clear Spring Ambulance Club, Inc. 59 Hancock Rescue Squad Inc. 69 Boonsboro Ambulance & Rescue, Inc. 409 West First Street Hagerstown, MD P.O. Box 2799 (21741) 21 West Franklin Street Hagerstown, MD P.O. Box ½ W. Chapline Street Sharpsburg, MD Showalter Road Hagerstown, MD P.O. Box Cumberland Street Clear Spring, MD East Main Street Hancock, MD P.O. Box Old National Pike Boonsboro, MD Rodney McCoy, President David Pheil, Vice President Lester Bussard, Chief Donald Weigel, Assistant Chief Kevin Willis, Lieutenant Phil Ridenour, Chief Terry Stouffer - 2nd in Command Bill Garrett - 3rd in Command James Miller, Chief Bev Witmer, Deputy Chief Stephanie Stellard, Assistant Chief Michael Yonker, Chief Ryan Keyser, Assistant Chief Douglas Shaw, President Morgan Boyd, Chief Clifford Davis, Deputy Chief Tommy Carter, Captain (Cell) March 2012 A-13

77 Company Number Company Name Address Officers Pagers/Cell Telephone Fax 75 Community Rescue Service, Inc 110 Eastern Blvd. North Chris Amos, Chief James Sprecher, Deputy Chief (cell) Hagerstown, Dave Hays, Assistant Chief MD Sub-Station 754 Sub-Station 759 Western Enterprise 526 Washington Square Hagerstown, MD Smithsburg Emergency Medical Services Inc. Maugansville Station 13 P.O. Box Maugansville Road Maugansville, MD P.O. Box Maple Avenue Smithsburg, MD Jon Snyder, Chief James Ulrich, Assistant Chief Garrett Snyder, Captain (cell) Washington County Emergency Rehab Unit 301 Devonshire Road Hagerstown, MD Terry Smith, Chief Bryan Stallings, Deputy Chief Bill King, Assistant Chief C.I.S.D. Maryland State C.I.S.D. Team - Region 2 Julie Kugler-Bentley Behavioral Health Services 747 Northern Avenue Hagerstown, MD Notification through 911 Headquarters March 2012 A-14

78 Table A - 6 Allegany County Agency Information Company Number Company Name Address Officers Pagers/Cell Telephone Fax Department of Emergency Services Department of PPG Richard DeVore, Director Emergency Services Road SE Cumberland, MD ddevore@alconet.org Emergency Management Division PPG Road SE Cumberland, MD Susan Lee, Chief slee@alconet.org x Joint Communications Division 414 Hudson Avenue Cumberland, MD Roger Bennett, Chief rbennett@alconet.org Emergency Medical Services Division PPG Road SE Cumberland, MD John Herath, Chief jherath@alconet.org Animal Control and Shelter Division PPG Road SE Cumberland, MD Karl Brubaker, Chief kbrubaker@allconet.org Special Operations Team PPG Road SE Cumberland, MD Tim Growden, Chief 48 hirt@allconet.org March 2012 A-15

79 Company Number Company Name Address Officers Pagers/Cell Telephone Fax Advisory Boards & Committees Emergency Services Board Chair Richard DeVore Fire Service Committee Chair Tim Dayton PPG Road SE Cumberland, MD Emergency Medical Service Committee Chair Allen Ruby Local Emergency Planning Committee Chairman Jim Swauger Allegany County Citizen Corps Chairman Susan Lee Association Allegany-Garrett County Volunteer Fire & Rescue Association PO Box 1340 Cumberland, MD Clarence Broadwater, President Fire Departments 16 Frostburg Fire Department Station 1 Station 2 22 South Water Street, Frostburg MD East Main Street, Frostburg MD Nathan Blubaugh, Chief March 2012 A-16

80 Company Number 2 Company Name Address Officers Pagers/Cell Telephone Fax LaVale Volunteer Fire Department Station National Highway, LaVale MD Ryan Reichert, Fire Chief John Reichert, Deputy Chief James Swauger, Assistant Chief Station 2 Baltimore Pike Volunteer Fire Company 1047 National Highway, LaVale MD Baltimore Pike NE, Cumberland MD Barton Hose Company Legislative Road SW, Barton MD Bedford Road Volunteer Fire Department Bedford Road NE, Cumberland MD John Harr, Chief Wayne Round, Chief Derek Crippen, Chief Seth Miller, Assistant Chief A John Herath, Assistant Chief B Shaft Volunteer Fire Department Shaft Road, Frostburg MD Scott Yates, Chief Bowling Green Volunteer Fire Department McMullen Highway, Cumberland MD Shannon Adams, Chief March 2012 A-17

81 Company Number 11 5 Company Name Address Officers Pagers/Cell Telephone Fax Bowman's Addition Volunteer Fire Department Corriganville Volunteer Fire Company Boardwalk Avenue NE, Cumberland MD Corrigan Drive, Corriganville MD Dennis Bonner, Chief Jeff DeHaven, Chief Cresaptown Volunteer Fire Department District 16 Volunteer Fire Department Warrior Drive, Cresaptown MD PO Box 2413 Cumberland, MD Jeremy Athey, Fire Chief Pat Reid, Deputy Chief Rick Wolford, Assistant Chief John Pratt, 1 st Assistant Chief Sue Clark, EMS Captain Greg Boyd, Chief Flintstone Volunteer Fire Company Flintstone Drive NE, Flintstone MD Steve Bowman, Chief Good Will Volunteer Fire Company 6 Douglas Avenue, Lonaconing MD Robert Ritchie, Chief Luke Volunteer Fire Company 300 Pratt Street Luke, MD Pete Pamepinto, Capt March 2012 A-18

82 Company Number 23 Company Name Address Officers Pagers/Cell Telephone Fax McCoole Fire & Rescue Department Crooks Ave SW McCoole, MD Chuck Pearce, Chief Midland Fire Company Railroad Street, Midland MD Donnie Sweitzer, Fire Chief Jeff Cutter, Deputy Chief John Monahan, Assistant Chief Ed Kenner, Assistant Chief Mount Savage Volunteer Fire Company Iron Rail Street, Mt. Savage MD Rick Robinson, Chief Oldtown Volunteer Fire Department PO Box 87 Oldtown, MD Kenneth Wolford, Chief Potomac Fire Company 61 Main Street, Westernport MD Tim Dayton, Fire Chief Bill Kight Jr., Deputy Chief Josh Clark, Assistant Chief Bobby Pattison, Assistant Chief Rawlings Volunteer Fire Department Volunteer Drive, Rawlings MD Kenneth McKenzie, Chief Allegany County Special Operations Department PPG Road SE, Cumberland, MD Tim Growden, Chief Sam Wilson, Deputy Chief March 2012 A-19

83 Company Number 43 Company Name Address Officers Pagers/Cell Telephone Fax Orleans Volunteer Fire Company Orleans Road Orleans, MD John Clingerman, Chief Clarysville Volunteer Fire Company Clarysville RD, SW, Frostburg, MD Eric Clark, Chief Ellerslie Volunteer Fire Company Ellerslie Road, Ellerslie, MD Scott Williams, Chief Cumberland South End Fire Station #2 Cumberland Fire Headquarters Station #1 Third Street, Cumberland MD Bedford Street, Cumberland MD Donald Dunn, Chief Rescue Squads Tri-Towns EMS PO Box 144 Westernport, MD LaVale Rescue Squad PO Box 3343 LaVale, MD Eric Mowbray, Chief Adam Miller, Capt March 2012 A-20

84 Company Number 53 Company Name Address Officers Pagers/Cell Telephone Fax Frostburg Area Ambulance Service PO Box 57 Frostburg, MD Paul Hostetler, Chief George s Creek Rescue Squad PO Box 155 Lonaconing, MD Jim McVay, Capt New Page Ambulance Ellerslie Ambulance Service 300 Pratt Street Luke, MD Ellerslie Road, Ellerslie, MD Pete Pamepinto, Capt Luke Merkel, Capt March 2012 A-21

85 Table A - 7 Garrett County Agency Information Company Number Company Name Address Officers Pagers/Cell Telephone Fax Office of Public Safety and Emergency Management Office of Public Safety and Emergency Management Brad Frantz, Director bfrantz@garrettcounty.org Emergency Management Fire & Rescue Communications / Special Operations Team Emergency Air Unit Advisory Boards & Committees 311 East Alder Street Oakland, MD East Alder Street Oakland, MD East Alder Street Oakland, MD East Alder Street Oakland, MD Deep Creek FD McHenry, MD Steve Smith, Communications Chief ssmith@garrettcounty.org Virginia Smith, EM Planner vsmith@garrettcounty.org Brad Frantz, Director bfrantz@garrettcounty.org Steve Smith, Communications Chief ssmith@garrettcounty.org Steve Smith, Communications Chief ssmith@garrettcounty.org Steve Smith, Communications Chief ssmith@garrettcounty.org March 2012 A-22

86 Company Number Company Name Address Officers Pagers/Cell Telephone Fax Emergency Services Board Contact through Brad Frantz, Chair Ed McLellam Vice-Chair Lou Baltistella Local Emergency Planning Committee Chairman Brad Frantz Emergency Medical Services Council Chair Dwayne Kitis Health Dept. Emergency Planning Committee Chair Rodney Glotfelty Traffic Advisory Committee Chair Jay Moyer Director of GC Public Safety and Emergency Management Association Garrett County Fire & Rescue Association Pat Bowser, President Mike Simmons, 1st VP Rod Bowser, Secretary John Feather, Treasurer Fire Companies 20 Deer Park Volunteer Fire Department P.O. Box 3152 Deer Park, MD Kenny Collins, Fire Chief Jeff Simpson, Deputy Chief Craig Collins, Assistant Chief Bittinger Volunteer Fire Department 30 Deep Creek Volunteer Fire Department P.O. Box 27 Bittinger, MD P.O. Box 419 McHenry, MD Dan Warnick, Chief Justin Orondorf, Deputy Chief Jason King, Fire Chief Dave Hook, Assistant Chief Bloomington Volunteer Fire Department Bloomington, MD Danny Beaver, Fire Chief Shane Bosley, Deputy Chief Kathy Bever, Assistant Chief Oakland Volunteer Fire Department 31 3 rd Street Oakland, MD John Feather, Fire Chief Chris Crabtree, Deputy Chief Phil Rook, Assistant Chief March 2012 A-23

87 Company Number Company Name Address Officers Pagers/Cell Telephone Fax 110 Friendsville Volunteer Fire & Rescue Department P.O. Box 186 Friendsville, MD Terry Spear, Chief Dave Sines, 1 st Assistant Chief Mike Hoover, 2 nd Assistant Chief Accident Volunteer Fire Department P.O. Box 50 Accident, MD Richard Carlsom, Fire Chief Paul Custer, 1 st Assistant Chief Ed Livengood, 2 nd Assistant Chief Gorman Volunteer Fire Department 270 Gorman Road Oakland, MD Mike Steyer, Fire Chief Gary Pritts, Deputy Chief Ruff Neal, Assistant Chief Grantsville Volunteer Fire Department P.O. Box 248 Grantsville, MD Duane Stein, Fire Chief Herman S. Yoder, Deputy Chief Raymond Yoder, 1 st Assistant Chief Shaun Broadwater, 2 nd Assistant Chief Kitzmiller Volunteer Fire Department P.O. Box 438 Kitzmiller, MD David Burrell Jr., Fire Chief Tom Davis, Deputy Chief Shawn Nesselrodt, Assistant Chief Eastern Garrett Volunteer Fire Department 401 Finzel Road Frostburg, MD Tim Clark, Fire Chief Don Gaumer, Deputy Chief Dave Wiland, 1 st Assistant Chief Randy Baker, 2 nd Assistant Chief Pete Smith, 3 rd Assistant Chief Rescue Squads March 2012 A-24

88 Company Number Company Name Address Officers Pagers/Cell Telephone Fax Northern Garrett Rescue Squad P.O. Box 293 Grantsville, MD Lucretia Sines, Chief Station Miller Street Grantsville, MD Doris Beal, Assistant Chief, Station Station 2 67 Friendsville Road McHenry, MD Justin Orendorf, Assistant Chief, Station Station 3 1 st Avenue/ Chestnut Street Friendsville, MD Kenny Sines, Assistant Chief, Station Southern Garrett Rescue Squad P.O. Box 378 Oakland, MD John Mayne Rick Harding March 2012 A-25

89 Appendix B Shared Systems Detailed information on shared systems available for use within the region is listed in subsequent pages of Appendix B. The table below lists the shared system(s). Radio System Name Make / Model WASHINGTON COUNTY WCP 25 Motorola ASTRO 25 WC Fire/EMS Motorola /MA COM WC Law Enforcement Motorola /MA COM WC Highways Motorola /MA COM WC Local Government Motorola /MA COM WC DWQ Motorola /MA COM Table B - 1 Western Region Shared System(s) Type Digital Trunked Digital Trunked Digital Trunked Digital Trunked Digital Trunked Digital Trunked Frequency Band WC Schools Motorola Conventional UHF/VHF WC Transit WC DPW Motorola Motorola Digital Trunked Digital Trunked Owning Agency Service Area UHF 450 Washington County Washington County UHF 450 Washington County Washington County UHF 450 Washington County Washington County UHF 450 Washington County Washington County UHF 450 Washington County Washington County UHF 450 Washington County Washington County WC Board of Education Washington County UHF 450 Washington County Washington County UHF 450 Washington County Washington County ALLEGANY COUNTY AC Fire/EMS Kenwood Passport VHF-Lo Allegany County Allegany County and into Somerset County, Pa. AC Sheriff Kenwood Passport UHF Commercial Allegany County AC Health Kenwood Passport VHF Allegany County Health Department Allegany County AC Public Works Kenwood Trunked 800 MHz Allegany County Public Works Allegany County Cumberland Fire Kenwood Trunked UHF City of Cumberland Cumberland Cumberland Police Kenwood Passport UHF City of Cumberland Cumberland Cumberland Public Works GE Conventional VHF City of Cumberland Cumberland AC Board of Education Kenwood Trunked UHF Commercial Allegany County GARRETT COUNTY GC Fire/EMS Motorola Conventional VHF-Lo Garrett County Public Safety Garrett County GC Sheriff Kenwood Conventional Low Band Garrett County SO Garrett County GC Health GE/Kenwood Conventional VHF Garrett County Health Garrett County GC Public Roads Kenwood/ Garrett County Public Conventional VHF Motorola Roads Garrett County GC Public Utilities Kenwood Trunked 800 MHz Garrett County Public Utilities Garrett County GC Board of Education Kenwood Trunked 800 MHz Garrett County Board of Education Garrett County STATE March 2012 B-1

90 Radio System Name MIEMSS Make / Model MA COM Kenwood Type Frequency Band Owning Agency Conventional UHF State of Maryland Statewide MSP VHF-Lo Conventional VHF-Lo MSP Statewide DNR Conventional VHF DNR Statewide SHA Daniels Conventional VHF-Lo SHA Statewide FEDERAL National Park Service Motorola Conventional VHF US Parks Federal Service Area March 2012 B-2

91 B.1 WC P25 Responsible Agency This radio system is owned or managed by: Washington County Division of Emergency Services Name: Kevin Lewis Title: Director Address Elliott Parkway, Williamsport, MD Phone: /7 Phone Cell: Number of Radios No. of Mobile Radios on this System: 350 No. of Portable Radios on this System: System Type 750 Radio System Make: Trunked / Conventional/Both: Radio System Model: Radio System Frequency Band: P25 Compliancy: Motorola Trunked Astro P25 Digital UHF Yes Number of Channels: 10 Encryption Protocol: AES Year Installed: 2009 Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Repeated Both Narrowband Yes Yes March 2012 B-3

92 Service area Service area includes Washington County. Participating Agencies Washington County Fire and Rescue Washington County Sheriff s Office Washington County Public Works Washington County Department of Water Quality Hagerstown Police Department Hancock Police Department Smithsburg Police Department Boonsboro Police Department Maryland State Highway Administration Hagerstown Shop Maryland State Police - Barrack O Washington County Transit Washington County Schools Shared Talk Groups Table B - 2 WC P25 Shared Talkgroup Information Channel/TG Primary Use Agencies Supported WASHINGTON COUNTY Primary Dispatch WCSO1 Law Enforcement WCSO and MSP UHF HPD1 Law Enforcement HPD UHF FIRE MAIN Fire and EMS All Fire and EMS UHF Secondary Dispatch WCSO2 & 3 Law Enforcement WCSO and MSP UHF HPD2 & 3 Law Enforcement HPD UHF Tactical Talkgroups OPS1 Law Enforcement WCSO, HPD, MSP UHF OPS2 Law Enforcement WCSO, HPD, MSP UHF OPS3 Law Enforcement WCSO, HPD, MSP UHF OPS4 Law Enforcement WCSO, HPD, MSP UHF OPS5 Law Enforcement WCSO, HPD, MSP UHF FIRE OPS Fire and EMS All Fire and EMS UHF TAC1 thru TAC6 Fire and EMS All Fire and EMS UHF WC Emergency Management Emergency AREA1 thru 3 Management All Fire/EMS and Law Enforcement Frequency /Band UHF March 2012 B-4

93 Other Shared Channel/Talkgroup Notes: [Add notes] March 2012 B-5

94 B.2 MIEMSS Responsible Agency This radio system is owned or managed by: Name: Title: Address Phone: 24/7 Phone Cell: Number of Radios No. of Mobile Radios on this System: No. of Portable Radios on this System: System Type Radio System Make: Trunked / Conventional/Both: Radio System Model: Radio System Frequency Band: P25 Compliancy: Number of Channels: Encryption Protocol: Year Installed: Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Service area Service area includes. March 2012 B-6

95 Participating Agencies Enter agencies Shared Channel Table B - 3 MIEMSS Shared Channel Information Channel Name Analog / Digital Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported Other Shared Channel Notes: [Add notes] March 2012 B-7

96 B.3 AC Fire/EMS Responsible Agency This radio system is owned or managed by: Allegany County Department of Emergency Services Name: Dick DeVore Title: Director Address PPG Road, Cumberland, MD Phone: x100 24/7 Phone Cell: Number of Radios No. of Mobile Radios on this System: 250 No. of Portable Radios on this System: System Type 750 Radio System Make: Trunked / Conventional/Both: Radio System Model: Radio System Frequency Band: P25 Compliancy: Number of Channels: Encryption Protocol: Kenwood Passport MSTR-II UHF No Passport None Year Installed: 2010 Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Passport Analog Wideband No Yes March 2012 B-8

97 Service area Service area includes Allegany County and southern Somerset County, PA. Participating Agencies All Allegany County Volunteer Fire and EMS Departments Wellersburg Fire Department (Volunteer), Somerset County, PA Allegany County Sheriff s Office Allegany County Department of Public Works City of Cumberland Fire Department City of Cumberland Police Department Bloomington Volunteer Fire Company (Company 36) Western Maryland Health System Allegany County Health System Western Maryland Railroad Frostburg State University Police Department Frostburg Police Department Lonaconing Police Department Ridgely Volunteer Fire Department (WV Company 25) Shared Channels Table B - 4 AC Fire/EMS Shared Channel Information Channel Name Analog / Digital Wide / Narrow Tx and Tone Rx and Tone Primary Use Fire1 Analog Wide Alerting Fire2 Analog Wide OPS Fire3 Analog Wide OPS Fire4 Analog Wide OPS Other Shared Channel Notes: [Add notes] Agencies Supported All Allegany County Volunteer Fire and EMS Departments Wellersburg Fire Department (Volunteer), Somerset County, PA All Allegany County Volunteer Fire and EMS Departments Wellersburg Fire Department (Volunteer), Somerset County, PA All Allegany County Volunteer Fire and EMS Departments Wellersburg Fire Department (Volunteer), Somerset County, PA All Allegany County Volunteer Fire and EMS Departments Wellersburg Fire Department (Volunteer), Somerset County, PA March 2012 B-9

98 B.4 MSP VHF-Lo Responsible Agency This radio system is owned or managed by: Name: Daryl McCarty Title: Radio Technician Address 1125 National Highway, Cumberland, Maryland Phone: /7 Phone Cell: Number of Radios No. of Mobile Radios on this System: 30 No. of Portable Radios on this System: 30 System Type Radio System Make: Trunked / Conventional/Both: Radio System Model: Radio System Frequency Band: P25 Compliancy: Number of Channels: Encryption Protocol: Year Installed: Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Service area Service area includes: All of Allegany County March 2012 B-10

99 Participating Agencies Enter agencies Shared Channels Table B - 5 MSP VHF-Lo Shared Channel Information Channel Name Analog / Digital Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported Other Shared Channel Notes: [Add notes] March 2012 B-11

100 B.5 Cumberland Public Works Responsible Agency This radio system is owned or managed by: Name: Title: Address Phone: 24/7 Phone Cell: Number of Radios No. of Mobile Radios on this System: No. of Portable Radios on this System: System Type Radio System Make: Trunked / Conventional/Both: Radio System Model: Radio System Frequency Band: P25 Compliancy: Number of Channels: Encryption Protocol: Year Installed: Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Service area Service area includes. March 2012 B-12

101 Participating Agencies Enter agencies Shared Channels Table B - 6 Cumberland Public Works Shared Channel Information Channel Name Analog / Digital Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported Other Shared Channel Notes: [Add notes] March 2012 B-13

102 B.6 AC Board of Education Responsible Agency This radio system is owned or managed by: TWR Communications Name: Harry Wolford Title: Manager Address 549 North Center Street, Cumberland MD Phone: /7 Phone Cell: Number of Radios No. of Mobile Radios on this System: 160 No. of Portable Radios on this System: System Type 25 Radio System Make: Trunked / Conventional/Both: Radio System Model: Radio System Frequency Band: P25 Compliancy: Number of Channels: Encryption Protocol: Trident Passport Trunked Kenwood UHF No Trunked Talkgroups No Year Installed: Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Repeated Both Narrow No No March 2012 B-14

103 Service area Service area includes Western Maryland, Western Pennsylvania, West Virginia and Northern Virgina. Participating Agencies Board of Education (BOE) Shared Talk Groups Bus Table B - 7 AC Board of Education Shared Talkgroup Information Talkgroup Name Talkgroup ID Primary Use Agencies Supported Transportation Maint Other Shared Channel/Talkgroup Notes: [Add notes] BOE BOE BOE March 2012 B-15

104 B.7 DNR Responsible Agency This radio system is owned or managed by: Department of Natural Resources Name: David Christner Title: Operations Manager Address Headquarters Drive, Flintstone, MD Phone: /7 Phone Cell: Number of Radios No. of Mobile Radios on this System: Western Region No. of Portable Radios on this System: System Type Western Region Radio System Make: Trunked / Conventional/Both: Radio System Model: Radio System Frequency Band: P25 Compliancy: Number of Channels: Encryption Protocol: Kenwood Conventional Kenwood MHz No Forestry: 4 Parks: 8 Repeaters NRP: 8 Repeaters None Year Installed: 2008 Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Both Analog Narrow No No March 2012 B-16

105 Service area Service area includes Garrett, Allegany, Washington and Frederick Counties. Participating Agencies Enter agencies Shared Channel Table B - 8 DNR Shared Channel Information Channel Name Analog / Digital Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported Other Shared Channel Notes: Will be using VTAC Channels for connection into WAGIN. March 2012 B-17

106 B.8 SHA Responsible Agency This radio system is owned or managed by: Maryland State Highway Administration Name: Phil Lazarus Title: Division Chief for Statewide Engineering & Technical Address 5901 Baltimore National Pike, Baltimore, MD Phone: /7 Phone Cell: Number of Radios No. of Mobile Radios on this System: 300 No. of Portable Radios on this System: System Type 125 Radio System Make: Trunked / Conventional/Both: Radio System Model: Radio System Frequency Band: P25 Compliancy: Daniels Conventional MT-3 Low Band VHF Lo No Number of Channels: 8 Encryption Protocol: No Year Installed: 1954 Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Simplex Analog Wideband Yes No March 2012 B-18

107 Channel Name Channel 2 Interop Service area Service area includes Washington, Allegany, and Garrett Counties Participating Agencies Maryland State Highway Administration District 6 Office District EOC Maryland State Highway Administration LaVale Office Allegany County Maryland State Highway Administration Keyser s Ridge Office Garrett County Maryland State Highway Administration Hagerstown Office Washington County Local County Public Safety Agencies in Allegany, Garrett, and Washington Counties Maryland State Police Shared Channels Analog / Digital Table B - 9 SHA Shared Channel Information Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported Analog Wide Other Shared Channel Notes: Interoperability Highway Incidents, Winter Storm Operations and Traffic Management Agencies listed above There are 8 channels on the system; however on the INTEROP channel is being shared. Other channels can be shared if required. March 2012 B-19

108 B.9 GC Fire/EMS Responsible Agency This radio system is owned or managed by: Name: Garrett County Government Title: c/o GC Public Safety Brad Frantz, Director Address 311 East Alder Street, Oakland MD Phone: /7 Phone Cell: Number of Radios No. of Mobile Radios on this System: 50 No. of Portable Radios on this System: 40 System Type Radio System Make: Trunked / Conventional/Both: Radio System Model: Radio System Frequency Band: P25 Compliancy: Various Conventional Various VHF Partial Number of Channels: 2 Encryption Protocol: Year Installed: Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: N/A N/A Both Analog Both No No Service area Service area includes. All of Garrett County. March 2012 B-20

109 Channel Name Participating Agencies All Fire/EMS Companies (See Table A-5) Shared Channels Analog / Digital Table B - 10 GC Fire/EMS Shared Channel Information Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported Dispatch Both Both CSQ Dispatch All Fire/EMS Grantsville Repeater Both Both CSQ Repeater All Fire/EMS Elder Hill Repeater Both Both CSQ Repeater All Fire/EMS Eagle Rock Repeater Both Both CSQ Repeater All Fire/EMS Other Shared Channel Notes: [Add notes] March 2012 B-21

110 B.10 GC Sheriff Responsible Agency This radio system is owned or managed by: Name: Garrett County Sherriff s Office Title: Sheriff Address 3 rd Street, Oakland, MD Phone: /7 Phone Cell: N/A rcorley@garrettcounty.org Number of Radios No. of Mobile Radios on this System: 50 No. of Portable Radios on this System: 25 System Type Radio System Make: Trunked / Conventional/Both: Motorola Conventional Radio System Model: Radio System Frequency Band: P25 Compliancy: Low Band / UHF Yes Number of Channels: 2 Encryption Protocol: Year Installed: Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Both Both Both No No Service area Service area includes. All of Garrett County. March 2012 B-22

111 Channel Name Participating Agencies Garrett County Sherriff s Office (GCSO) Shared Channels Analog / Digital Table B - 11 GC Sheriff Shared Channel Information Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported Dispatch Both Both Sherriff Dispatch GCSO MSP Both Both MSP Shared MSP / GCSO Eagle Rock South Both Both Repeater Repeater GCSO Grantsville North Both Both Repeater Repeater GCSO Other Shared Channel Notes: [Add notes] March 2012 B-23

112 B.11 GC EMS Responsible Agency This radio system is owned or managed by: Name: John Bradley Frantz Title: Director, GC Public Safety and Emergency Management Address 311 East Alder Street, Oakland MD Phone: /7 Phone Cell: Number of Radios No. of Mobile Radios on this System: 50 No. of Portable Radios on this System: 50 System Type Radio System Make: Trunked / Conventional/Both: Radio System Model: Radio System Frequency Band: P25 Compliancy: Various Conventional Various High Band / VHF Partial Number of Channels: 2 Encryption Protocol: N/A Year Installed: Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Simplex Both Both No No Service area Service area includes. All of Garrett County. March 2012 B-24

113 Channel Name Participating Agencies All Fire/EMS Companies (See Table A-5) Shared Channels Analog / Digital Table B - 12 FC Health Shared Channel Information Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported Fire Fire Ground Both Both All Fire/EMS Ground OPS Talk- All Fire/EMS Both Both Talk-Around Around EMS 1 Both Both EMS All EMS EMS 2 All EMS (MD-WV) EMS 2 Both Both CSQ CSQ (WV) Other Shared Channel Notes: [Add notes] March 2012 B-25

114 B.12 GC Public Roads Responsible Agency This radio system is owned or managed by: Name: Jay Moyer Title: Superintendent Address Alder Street, Oakland MD Phone: /7 Phone Cell: Number of Radios No. of Mobile Radios on this System: 100 No. of Portable Radios on this System: System Type 25 Radio System Make: Trunked / Conventional/Both: Motorola Conventional Radio System Model: Radio System Frequency Band: P25 Compliancy: VHF Yes Number of Channels: 1 Encryption Protocol: Year Installed: 2012 Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Both Both Narrowband No No March 2012 B-26

115 Channel Name Service area Service area includes. All of Garrett County. Participating Agencies Garrett County Public Roads Department (GCPRD) Shared Channels Analog / Digital Table B - 13 GC Public Roads Shared Channel Information Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported Roads Both Narrow Public Roads GCPRD Other Shared Channel Notes: [Add notes] March 2012 B-27

116 B.13 GC Public Utilities Responsible Agency This radio system is owned or managed by: Garrett County Public Utilities Name: Linda Lindsay Title: Director Address 2008 Maryland Highway, Suite 2, Mt. Lake Park, MD Phone: /7 Phone Cell: Number of Radios No. of Mobile Radios on this System: 25 No. of Portable Radios on this System: 5 System Type Radio System Make: Trunked / Conventional/Both: Radio System Model: Kenwood Trunked TL 980K Radio System Frequency Band: 800 P25 Compliancy: No Number of Channels: 4 Encryption Protocol: LTR Year Installed: 2002 Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Repeated Analog Wideband N/A N/A Service area Service area includes Garrett County, Maryland. March 2012 B-28

117 Participating Agencies N/A Shared Channels Table B - 14 GC Public Utilities Shared Channel Information Channel Name Analog / Digital Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported Other Shared Channel Notes: [Add notes] March 2012 B-29

118 B.14 GC Board of Education Responsible Agency This radio system is owned or managed by: Transportation Department Name: Ed Wildesen Title: Director of Transportation Address 40 South 2 nd Street, Oakland, MD Phone: /7 Phone Cell: Ewildesen@ga.k12.md.us Number of Radios No. of Mobile Radios on this System: 100 No. of Portable Radios on this System: System Type 5 Radio System Make: Trunked / Conventional/Both: Radio System Model: Kenwood Trunked TK 980K Radio System Frequency Band: 800 P25 Compliancy: No Number of Channels: 4 Encryption Protocol: LTR Year Installed: 2001 Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Repeated Analog Wideband N/A N/A March 2012 B-30

119 Service area Service area includes Garrett County, Maryland. Participating Agencies N/A Shared Channels Table B - 15 GC Board of Education Shared Channel Information Channel Name Analog / Digital Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported Other Shared Channel Notes: [Add notes] March 2012 B-31

120 B.15 National Park Service Responsible Agency This radio system is owned or managed by: Name: Title: Address Phone: 24/7 Phone Cell: Number of Radios No. of Mobile Radios on this System: No. of Portable Radios on this System: System Type Radio System Make: Trunked / Conventional/Both: Radio System Model: Radio System Frequency Band: P25 Compliancy: Number of Channels: Encryption Protocol: Year Installed: Repeated/Simplex/Both: Analog / Digital / Both: Wideband / Narrowband / Both: Voted: Simulcast: Service area Service area includes. March 2012 B-32

121 Participating Agencies Enter agencies Shared Channels Table B - 16 National Park Service Shared Channel Information Channel Name Analog / Digital Wide / Narrow Tx Tone Rx Tone Primary Use Agencies Supported Other Shared Channel Notes: [Add notes] March 2012 B-33

122 Appendix C Inter-system Shared Channels Detailed information on shared channels available for use within the region is listed in the following table to include shared channel name(s) and frequency/talkgroup details for each shared channel. March 2012 C-1

123 Table C - 1 Western Region 800 MHz Inter-system Shared Channel(s) Channel Name Analog / Digital Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported 8CALL 90 (8CALL) Analog Wide Mutual Aid All Public Safety Agencies 8CALL 90D Analog Wide Simplex Mutual Aid All Public Safety Agencies 8TAC 91 (8TAC1) Analog Wide Mutual Aid All Public Safety Agencies 8TAC 91D Analog Wide Simplex Mutual Aid All Public Safety Agencies 8TAC 92 (8TAC2) Analog Wide Mutual Aid All Public Safety Agencies 8TAC 92D Analog Wide Simplex Mutual Aid All Public Safety Agencies 8TAC 93 (8TAC3) Analog Wide Mutual Aid All Public Safety Agencies 8TAC 93D Analog Wide Simplex Mutual Aid All Public Safety Agencies 8TAC 94 (8TAC4) Analog Wide Mutual Aid All Public Safety Agencies 8TAC 94D Analog Wide Simplex Mutual Aid All Public Safety Agencies Table C - 2 Western Region VHF Inter-system Shared Channel(s) Channel Name Analog / Digital Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported VCALL 10 Analog Wide Simplex Mutual Aid Statewide VTAC 11 Analog Wide Simplex Mutual Aid Statewide VTAC 12 Analog Wide Simplex Mutual Aid Statewide VTAC 13 Analog Wide Simplex Mutual Aid Statewide VTAC 14 Analog Wide Simplex Mutual Aid Statewide VTAC 17 Analog Wide Mutual Aid Statewide VTAC 17D Analog Wide Simplex Mutual Aid Statewide March 2012 C-2

124 Channel Name Analog / Digital Table C - 3 Western Region UHF Inter-system Shared Channel(s) Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported UCALL 40 Analog Wide Mutual Aid All Public Safety Agencies UCALL 40D Analog Wide Simplex Mutual Aid All Public Safety Agencies UTAC 41 Analog Wide Mutual Aid All Public Safety Agencies UTAC 41D Analog Wide Simplex Mutual Aid All Public Safety Agencies UTAC 42 Analog Wide Mutual Aid All Public Safety Agencies UTAC 42D Analog Wide Simplex Mutual Aid All Public Safety Agencies UTAC 43 Analog Wide Mutual Aid All Public Safety Agencies UTAC 43D Analog Wide Simplex Mutual Aid All Public Safety Agencies Channel Name Analog / Digital Table C - 4 WAGIN Inter-system Shared Channel(s) Wide / Narrow Tx and Tone Rx and Tone Primary Use Agencies Supported GC Fire VHF Fire and EMS All Public Safety Agencies GC Fire Lowband Fire and EMS All Public Safety Agencies GC Sheriff Lowband Sheriff All Public Safety Agencies MSP Lowband MSP All Public Safety Agencies SHA Lowband SHA All Public Safety Agencies AC Lowband Fire Backup All Public Safety Agencies AC UHF All Public Safety Agencies Cumberland City Police Channel 2 All Public Safety Agencies Cumberland City Fire Ops Channel March 2012 C-3

125 Appendix D Inter-system Shared Channel Coverage Plots March 2012 D-1

126 March 2012 D-2

127 March 2012 D-3

128 March 2012 D-4

129 March 2012 D-5

130 March 2012 D-6

131 March 2012 D-7

132 March 2012 D-8

133 March 2012 D-9

134 March 2012 D-10

135 Appendix E Gateways Detailed information on gateways available for use within the region is listed in subsequent pages of Appendix D. The table below lists the owning or managing agency, gateway name(s), make/model and whether the device is fixed or mobile. Gateway Name PHASE I SITES Washington County Table E - 1 Western Region Gateway System(s) Owning Agency Day-to-Day or Incident / Event Make / Model Fixed / Mobile No. of Simultaneous Nets Elliott Parkway WAGIN Day-to-Day CISCO Fixed 50 across all West Washington WAGIN Day-to-Day CISCO Fixed 50 across all 4 Motobridge (5 sites) WC ECC Incident/ Event Motorola Fixed Sidling Hill WC ECC Incident/ Event Motorola Fixed -Hwy 65 & I-70 WC ECC Incident/ Event Motorola Fixed -Fairview WC ECC Incident/ Event Motorola Fixed -Lambsknoll WC ECC Incident/ Event Motorola Fixed -Quirauk WC ECC Incident/ Event Motorola Fixed ICRI 1 WC HPD Incident/ Event CAT Mobile 5 5 ICRI 2 WC DES Incident/ Event CAT Mobile 5 5 Allegany County Allegany Tower WAGIN Day-to-Day CISCO Fixed 50 across all 10 Eagle Rock WAGIN Day-to-Day CISCO Fixed 50 across all 8 Dan s Rock (County) WAGIN Day-to-Day CISCO Fixed 50 across all 8 Dan s Rock (SHA) WAGIN Day-to-Day CISCO Fixed 50 across all 6 ACU-T 1 Allegany County Incident/Event Raytheon ACU-T Mobile 3 6 ACU-T 2 Allegany County Incident/Event Raytheon ACU-T Mobile 3 6 Garrett County Garrett PSAP WAGIN Day-to-Day CISCO Fixed 50 across all 6 PSI-Net WAGIN Day-to-Day CISCO CM Fixed PHASE II SITES RT 135 SHA Thayerville WVTV Grantsville MIEMMSS Keysers Ridge SHA Martin Mountain SHA Garrett County Garrett County Garrett County Garrett County Allegany County No. of Ports Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all 8 March 2012 E-1

136 Gateway Name Town Hill DNR Savage Mountain SHA Westernport Owning Agency Allegany County Allegany County Allegany County Day-to-Day or Incident / Event Make / Model Fixed / Mobile No. of Simultaneous Nets No. of Ports Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all 8 Day-to-Day CISCO Fixed 50 across all 8 March 2012 E-2

137 E.1 Allegany Tower Equipment Location This gateway is located at the Allegany County Center, 414 Hudson Ave., Cumberland, MD Responsible Agency This gateway is owned or managed by: Maryland State Highway Administration Name: Craig Fetzer Title: Division Chief Address 5901 Baltimore National Pike, Baltimore, MD Phone: /7 Phone Service Area Service area includes the Cumberland area. Participating Agencies All public safety agencies Other Gateway Notes: [Add notes] March 2012 E-3

138 E.2 Eagle Rock Equipment Location This gateway is stored at Eagle Rock Tower. Responsible Agency This radio system is owned or managed by: Garrett County Public Safety Name: Stephen Smith Title: Chief of Communications Address 311 East Alder Street, Oakland, Maryland Phone: /7 Phone Cell: Service Area Service area includes Garrett County, Maryland. Participating Agencies All Fire / EMS Other Gateway Notes: Add notes March 2012 E-4

139 E.3 Dan s Rock (SHA) Equipment Location This gateway is located at Dan s Rock Road, Midland, MD Responsible Agency This gateway is owned and managed by: Maryland State Highway Administration Name: Phil Lazarus Title: Division Chief for Statewide Engineering & Technical Address 5901 Baltimore National Pike, Baltimore, MD Phone: Cell: /7 Phone plazarus@sha.state.md.us Service Area Service area includes Western Allegany County. Participating Agencies All Public Safety Agencies and those utilizing National Mutual Aid Other Gateway Notes: The following resources are patched on this gateway Asset Type of Radio # of Ports Used # of Ports Available Technical documentation is referenced in the WAGIN IPICS System as Built documents. March 2012 E-5

140 E.4 Dan s Rock (County) Equipment Location This gateway is stored at Dan s Rock, Midland, Maryland Responsible Agency This radio system is owned or managed by: Allegany Department of Emergency Services Name: Roger Bennett Title: Chief of 911 Joint Communications Division Address PPG Road, SE, Cumberland, Maryland Phone: x123 24/7 Phone Cell: rbennett@allconet.org Service Area Service area includes Western Allegany County. Participating Agencies All Public Safety Agencies and those utilizing National Mutual Aid Other Gateway Notes: Add notes March 2012 E-6

141 E.5 Elliott Parkway Equipment Location This gateway is stored at Washington County ECC Elliott Parkway, Williamsport, Maryland Responsible Agency This radio system is owned or managed by: Washington County Division of Emergency Services. Name: Kevin Lewis Title: Director of Emergency Services Address Elliott Parkway, Williamsport, MD Phone: /7 Phone Cell: Service Area Service area includes Washington County. Participating Agencies All Public Safety Agencies and those utilizing National Mutual Aid Other Gateway Notes: Add notes March 2012 E-7

142 E.6 33 West Washington Equipment Location This gateway is stored at Washington County s back-up ECC on 33 West Washington Street, Hagerstown, Maryland Responsible Agency This radio system is owned or managed by: Washington County Division of Emergency Services. Name: Kevin Lewis Title: Director of Emergency Services Address Elliott Parkway, Williamsport, MD Phone: /7 Phone Cell: Service Area klewis@washco-md.net Service area includes Washington County. Participating Agencies All Public Safety Agencies and those utilizing National Mutual Aid Other Gateway Notes: Add notes March 2012 E-8

143 E.7 Garrett PSAP Equipment Location This gateway is stored at 311 East Alder Street, Oakland, Maryland Responsible Agency This radio system is owned or managed by: Garrett County Public Safety Name: Stephen Smith Title: Chief of Communications Address 311 East Alder Street, Oakland, Maryland Phone: /7 Phone Cell: Service Area Service area includes Garrett County, Maryland. Participating Agencies All Fire / EMS Other Gateway Notes: Add notes March 2012 E-9

144 E.8 MotoBridge Equipment Location This gateway is stored at Washington County ECC Elliott Parkway, Williamsport, Maryland Responsible Agency This radio system is owned or managed by: Washington County Division of Emergency Services. Name: Kevin Lewis Title: Director of Emergency Services Address Elliott Parkway, Williamsport, MD Phone: /7 Phone Cell: Service Area Service area includes Washington County. Participating Agencies All Public Safety Agencies and those utilizing National Mutual Aid Other Gateway Notes: Add notes Locations Location *All locations have low band MHz Assets *All have 8CALL MHz Assets *All have UCALL MHz Assets * All have VCALL10 Sidling Hill 8TAC 91 UTAC43 VTAC13 Hwy 65 & I-70 8TAC 93 UTAC43 VTAC13 Lambs Knoll 8TAC 91 UTAC41 VTAC12 Fairview 8TAC 92 UTAC42 VTAC11 Quirauk 8TAC 94 UTAC43 VTAC14 March 2012 E-10

145 E.9 ICRI 1 Equipment Location This gateway is stored at Hagerstown Police Department. Responsible Agency This radio system is owned or managed by: Hagerstown Police Department. Name: Art Smith Title: Chief of Police Address 50 N Burhans Blvd., Hagerstown, MD Phone: /7 Phone Cell: asmith@hagerstownpd.org Service Area Service area includes the City of Hagerstown. Participating Agencies All Public Safety Agencies and those utilizing National Mutual Aid. Other Gateway Notes: Add notes March 2012 E-11

146 E.10 ICRI 2 Equipment Location This gateway is stored at Washington County Special Operations Team, 638 Frederick Street, Hagerstown, Maryland Responsible Agency This radio system is owned or managed by: Washington County Division of Emergency Services. Name: Kevin Lewis Title: Director of Emergency Services Address Elliott Parkway, Williamsport, MD Phone: /7 Phone Cell: Service Area klewis@washco-md.net Service area includes Washington County. Participating Agencies All Public Safety Agencies and those utilizing National Mutual Aid Other Gateway Notes: Add notes March 2012 E-12

147 Appendix F Radio Caches Information on radio caches available for use within the region is listed in subsequent pages of Appendix F. The table below lists the owning or managing agency, cache, frequency band and quantity of radios in each cache. Table F - 1 Western Region Radio Cache(s) Radio Cache Owning / Managing Frequency Make / Model Name Agency Band Quantity WC DES UHF Motorola/2500 WC DES UHF 10 WC ECC UHF Motorola/2500 WC DES UHF 10 WCSO UHF Motorola/2500 WCSO UHF 10 March 2012 F-1

148 F.1 WC DES UHF Equipment Location This radio cache is stored at Washington County Division of Emergency Services, Elliot Parkway, Williamsport. Responsible Agency This radio cache is owned or managed by Washington County Division of Emergency Services: Name: Kevin Lewis Title: Director of Emergency Services Address Elliot Parkway, Williamsport, Maryland Phone: /7 Phone Cell Service Area Service area includes any agencies within Washington County. System Type and Capacity Cache Description: Make / Model: Motorola XTS 2500 Frequency Band: UHF Digital No. of Radios in Cache: 10 No. of Available Channels: 10 No. of Spare Batteries: 10 Talk Groups Programmed on Cache Table F - 2 WC DES VHF Lo Talkgroup Information Talkgroup Name Talkgroup ID Primary Use Agencies Supported Patrol PTL Law Enforcement WCSO, MSP, HPD Washington County Fire WF1 Fire/Rescue All Fire/Rescue Washington County Emergency All First Responders in Emergency WEM Management Washington County Management March 2012 F-2

149 Other Cache Notes: [Add text] March 2012 F-3

150 F.2 WC ECC UHF Equipment Location This radio cache is stored at Washington County Emergency Communications Center, Elliot Parkway, Williamsport. Responsible Agency This radio cache is owned or managed by Washington County Division of Emergency Services: Name: Alan Crawford Title: Deputy Director of Operations for Emergency Communications Address Elliot Parkway, Williamsport, Maryland Phone: /7 Phone Cell Service Area Service area includes any agencies within Washington County. System Type and Capacity Cache Description: Make / Model: Motorola XTS 2500 Frequency Band: UHF Digital No. of Radios in Cache: 10 No. of Available Channels: 10 No. of Spare Batteries: 10 Talk Groups Programmed on Cache Table F - 3 WC DES UHF Talkgroup Information Talkgroup Name Talkgroup ID Primary Use Agencies Supported Patrol PTL Law Enforcement WCSO, MSP, HPD Washington County Fire WF1 Fire/Rescue All Fire/Rescue Washington County Emergency All First Responders in Emergency WEM Management Washington County Management March 2012 F-4

151 Other Cache Notes: [Add text] March 2012 F-5

152 F.3 WCSO UHF Equipment Location This radio cache is stored at Washington County Sheriff s Office, 500 Western Maryland Parkway, Hagerstown. Responsible Agency This radio cache is owned or managed by Washington County Sheriff s Office: Name: Doug Mullendore Title: Sheriff Address 500 Western Maryland Parkway, Hagerstown, Maryland Phone: /7 Phone Cell dmullendore@washco-md.net Service Area Service area includes any agencies within Washington County. System Type and Capacity Cache Description: Make / Model: Motorola XTS 2500 Frequency Band: UHF Digital No. of Radios in Cache: 10 No. of Available Channels: 10 No. of Spare Batteries: 10 Talk Groups Programmed on Cache Table F - 4 WC SO Talkgroup Information Talkgroup Name Talkgroup ID Primary Use Agencies Supported Patrol PTL Law Enforcement WCSO, MSP, HPD Washington County Fire WF1 Fire/Rescue All Fire/Rescue Washington County Emergency All First Responders in Emergency WEM Management Washington County Management March 2012 F-6

153 Other Cache Notes: [Add text] March 2012 F-7

154 Appendix G Mobile Communications Units Detailed information on mobile communications units (MCU) (also known as Mobile Communications Center (MSS) or Mobile EOC) available within the region is listed in subsequent pages of Appendix F. Table G - 1 Western Region Mobile Communications Unit(s) Unit ID / Designator FEMA Type Owning Agency Deployment Area MC18/MCC III WC DES Washington County MCHPD/MCC III WC HPD Washington County GCPS/MCC III GC Public Safety Garrett County AC Cumberland City PD III AC Cumberland City PD Allegany County AC EMA III AC EMA Allegany County March 2012 G-8

155 G.1 MC18/MCC Equipment Location This Mobile Communications Unit equipment is stored at Washington County Sheriff s Office. Responsible Agency This Mobile Communications Unit is owned or managed by: Washington County DES Name: Charlie Summers Title: Deputy Director Address Elliott Parkway, Williamsport, MD Phone: /7 Phone csummers@washco-md.net Deployment Area This Mobile Communications Unit is available for deployment throughout Washington County. System Type and Capacity Unit ID / Designator: Owning Agency Type/Make/Model: MC18 Washington County DES Type III, Wells Fargo Mobile Trailer Quantity: 1 Primary Deployment Method Deployment Method (Other) MCU Storage Address Latitude Longitude Trailer N/A Washington County Sheriffs Office N W Year Activated 2008 FEMA Type Activation Method III WC Emergency Communications Center General Comments March 2012 G-9

156 Time to Setup Chassis Size Capability to Extend a Regional LMR System Dispatch Capability 10 minutes 28 ft. No Yes Number of Dispatch Consoles 1 SATCOM Capability SATCOM Type No N/A Number of Phone/Data Lines 1 Microwave Connectivity Capability PBX Capability Cellular PBX Capability FAX Capability Computer Server Capability LAN Capability No No No No No Yes Number of Workstations 6 Conference Internet Access Yes Yes Network Access Speed in KBPS Video Teleconference Capability On Scene Video Monitoring Capability Self-contained Power Supply Capacity (Watts) TV Reception Capability Expandable Mast No Yes Yes Yes Yes March 2012 G-10

157 Other Mobile Communications Unit Equipment Notes: Figure G - 1 MC18/MCC March 2012 G-11

158 G.2 MCHPD/MCC Equipment Location This Mobile Communications Unit equipment is stored at Hagerstown Fire Department, Engine 3. Responsible Agency This Mobile Communications Unit is owned or managed by: Hagerstown Police Department Name: Charlie Summers Title: Deputy Director Address Elliott Parkway Phone: /7 Phone Deployment Area This Mobile Communications Unit is available for deployment throughout Western Maryland. System Type and Capacity Unit ID / Designator: Owning Agency Type/Make/Model: MCHPD Hagerstown Police Department Winnebago Quantity: 1 Primary Deployment Method Deployment Method (Other) Vehicle chassis mount N/A MCU Storage Address Eastern Blvd, Hagerstown, MD Latitude Longitude N W Year Activated 1996 FEMA Type Activation Method III Washington County Emergency Communications Center March 2012 G-12

159 General Comments Time to Setup Chassis Size Capability to Extend a Regional LMR System Dispatch Capability Number of Dispatch Consoles SATCOM Capability SATCOM Type Number of Phone/Data Lines Microwave Connectivity Capability PBX Capability Cellular PBX Capability FAX Capability Computer Server Capability LAN Capability Number of Workstations Conference Internet Access Network Access Speed in KBPS Video Teleconference Capability On Scene Video Monitoring Capability Self-contained Power Supply Capacity (Watts) TV Reception Capability Expandable Mast 5-10 minutes 32 ft. No No N/A No N/A 2 cell No No No No No No No Yes No N/A No No Yes Yes No March 2012 G-13

160 Other Mobile Communications Unit Equipment Notes: Figure G - 2 MCHPD/MCC March 2012 G-14

161 G.3 GCPS/MCC Equipment Location This Mobile Communications Unit equipment is stored at the Public Service Center, Maryland Highway, Mountain Lake Park Responsible Agency This Mobile Communications Unit is owned or managed by: Garrett County Public Safety Name: Jon Bradley Frantz Title: Director Address 311 East Alder St., Oakland, MD Phone: /7 Phone Deployment Area This Mobile Communications Unit is available for deployment throughout Garrett County. System Type and Capacity Unit ID / Designator: Owning Agency Type/Make/Model: GCPS/MCC Garrett County Public Safety Specialty Vehicle Solutions (SVS) trailer Quantity: 1 Primary Deployment Method Deployment Method (Other) MCU Storage Address Latitude Longitude Trailer N/A Public Service Center, Maryland Highway N W Year Activated 2005 FEMA Type Activation Method III PSAP Page General Comments March 2012 G-15

162 Time to Setup Chassis Size Capability to Extend a Regional LMR System Dispatch Capability Number of Dispatch Consoles SATCOM Capability SATCOM Type 15 minutes 28 ft. No Yes 1 console No N/A Number of Phone/Data Lines 2 Microwave Connectivity Capability PBX Capability Cellular PBX Capability FAX Capability Computer Server Capability LAN Capability No Yes No Yes No Yes Number of Workstations 4 Conference Internet Access Network Access Speed in KBPS Video Teleconference Capability On Scene Video Monitoring Capability Self-contained Power Supply Capacity (Watts) TV Reception Capability Expandable Mast Yes No N/A No No Yes, redundancy (battery, generator, commercial power) Yes No March 2012 G-16

163 Other Mobile Communications Unit Equipment Notes: This vehicle has amateur radio capability. Figure G - 3 GCPS/MCC March 2012 G-17

164 G.4 AC Cumberland City PD Equipment Location This Mobile Communications Unit equipment is stored Responsible Agency This Mobile Communications Unit is owned or managed by: Name: Greg Leake Title: Captain Address 20 Bedford Street, Cumberland, Maryland Phone: 24/7 Phone Deployment Area This Mobile Communications Unit is available for deployment throughout. System Type and Capacity Unit ID / Designator: Owning Agency Incident Specific Cumberland Police Department Type/Make/Model: Quantity: 1 Primary Deployment Method (Other) Motor Vehicle Deployment Method MCU Storage Address Latitude Longitude Year Activated FEMA Type III Activation Method General Comments Time to Setup 10 minutes March 2012 G-18

165 Chassis Size Capability to Extend a Regional LMR System Dispatch Capability Number of Dispatch Consoles SATCOM Capability SATCOM Type Number of Phone/Data Lines Microwave Connectivity Capability PBX Capability Cellular PBX Capability FAX Capability Computer Server Capability LAN Capability Number of Workstations Conference Internet Access Network Access Speed in KBPS Video Teleconference Capability On Scene Video Monitoring Capability Self-contained Power Supply Capacity (Watts) TV Reception Capability Expandable Mast March 2012 G-19

166 Other Mobile Communications Unit Equipment Notes: Figure G - 4 AC Cumberland City PD MCU March 2012 G-20

167 G.5 AC EMA Equipment Location This Mobile Communications Unit equipment is stored at Allegany Department of Public Safety Headquarters, PPG Road, Cumberland, MD Responsible Agency This Mobile Communications Unit is owned or managed by: Allegany Department of Emergency Services Name: Roger Bennett Title: Chief of Allegany County 911 Joint Communications Division Address PPG Road, Cumberland, MD Phone: x123 24/7 Phone Deployment Area This Mobile Communications Unit is available for deployment throughout. System Type and Capacity Unit ID / Designator: Owning Agency Type/Make/Model: AC EMA Allegany Department of Public Safety Emergency Management Division 2000 Fleetwood Motor Home Quantity: 1 Primary Deployment Method Deployment Method (Other) Self-contained, vehicle chassis mount N/A MCU Storage Address PPG Road, Cumberland, MD Latitude Longitude N W Year Activated 2006 FEMA Type Activation Method III Allegany County Dispatch General Comments March 2012 G-21

168 Time to Setup Chassis Size Capability to Extend a Regional LMR System Dispatch Capability 22 minutes 42 ft. No Yes Number of Dispatch Consoles 1 SATCOM Capability SATCOM Type Number of Phone/Data Lines Microwave Connectivity Capability PBX Capability Cellular PBX Capability FAX Capability Computer Server Capability LAN Capability Yes SkyTerra Satellite Communications N/A No No No Yes No Yes Number of Workstations 5 Conference Internet Access Yes Yes Network Access Speed in KBPS Video Teleconference Capability On Scene Video Monitoring Capability Self-contained Power Supply Capacity (Watts) TV Reception Capability Expandable Mast No No Yes Yes Dish Network Only for wireless communications March 2012 G-22

169 Other Mobile Communications Unit Equipment Notes: Figure G - 5 AC EMA MCU March 2012 G-23

170 Appendix H Policy Documents, Governing Documents, MOUs, and Agreements March 2012 H-1

171 WASHINGTON COUNTY ALLEGANY COUNTY GARRETT COUNTY INTEROPERABILITY NETWORK GOVERNANCE In cooperation with the State of Maryland