AFRRCS Agency Handbook

AFRRCS Agency Handbook Policies and Procedures Documents AFRRCS Agency Handbook Section: Policies and Procedures Documents Version 2.0

AFRRCS Agency Handbook Policies and Procedures Documents Contents 1. Introduction a. Introduction b. Communications Policy (Planned) 2. Agencies a. Agency Positions, Training and Security 3. Security and Clearance (Planned) 4. Permitted Radios a. Permitted Radio Policy 5. Radio Programming a. Programming Key Policy (Planned) 6. Talkgroups a. Talkgroups b. Coverage Classes c. Talkgroup Naming Policy d. Talkgroup priority 7. Trunking Features (Planned) 8. Encryption a. AES and KMF Vendor b. Link Layer Authentication (Planned) 9. Over the Air Updates a. Over the Air Reykeying b. Over the Air Programming 10. Problem Management a. Problem Management Policy (Planned) 11. System and Data Integrity a. System Continuity Policy (Planned) 12. Connectivity a. Dispatch Center Connectivity 13. Site on Wheels Deployment a. Deployment Request 14. Operational Change a. Operational Change Policy (Planned) b. System Improvements for Agencies (Planned) Version 2.0

AFRRCS Agency Handbook Policies and Procedures Documents HANDBOOK REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 July 22, 2015 BS First Draft 1.0 January 5, 2016 BS First version, removed drafts. 2.0 March 22, 2016 BS Added new and amended policies approved by AFRRCS Governance; Dispatch Center Connectivity (Amended to v02), Patching (new), Programming Key (new), Talkgroups (amended to v02), Unconfirmed Talkgroups (new) Version 2.0

Introduction

December, 15 2015 Introduction AFRRCS is a P25 radio network with over 300 sites almost all built with redundant power and backhaul services. The two geographically separated core switches are each backed up by a redundant switch and multiple routing paths between locations. All of this to say AFRRCS is truly a public safety grade radio solution designed to provide first responders with a highly resilient and available radio network for the primary purpose of improving Responder Safety and ultimately the safety of all Albertans. The AFRRCS team has compiled this User Handbook with the purpose of providing a reference manual to assist with getting the most out of the use of AFRRCS. This manual is set up according to logical groupings and headings allowing you to quickly find the relevant information regardless of choice of electronic or paper copy. This document will be subject to ongoing revisions, we recommend that the practice of downloading the latest version from the AFRRCS website once or twice a year will almost always provide you with the most current version. Your feedback on this document and suggestions for ways to make it more useful to you the user are always welcome at the Transformationconsultant@gov.ab.ca mailbox. Thank you for your support of the province wide, interoperable, public safety radio network.

Section 2 - Agencies

AFRRCS Policies and Procedures for Interoperability Agency Positions, Training and Security Policy AFRRCS Policies and Procedures for Interoperability Section: Agency Positions, Training, and Security Policy Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability Agency Positions, Training and Security Policy DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 January 26, 2015 BS First draft agency position & training requirements policy 0.2 February 27, BS Update based on February WG meeting 2015 0.3 March 9, 2015 KC Formatted for final approval 1.0 June 23, 2015 Approved by AFRRCS Governance Council Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability Agency Positions, Training and Security Policy Contents Agency Position, Training and Security Policy...4 1.1 Agency Positions, Training, and Security... 4 1.2 Effective Date... 7 Appendix...8 2.1 Course Descriptions... 8 Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability Agency Positions, Training and Security Policy Section 1 Agency Position, Training and Security Policy Each agency is responsible for the duties defined in each of the following positions. Crypto Officer and Console Operator position may not be required for each agency. Minimum training standards are listed for each position. An Agency Administrator and Technical Administrator must be named for each agency. The Administrator position: 1. Must have signing authority for the Agency 2. Cannot be contracted to a third party. All other duties and positions can be contracted to third parties, if the agency so chooses. Individuals may fill more than one position, as long as they adhere to the training and security requirements for each position filled. 1.1 Agency Positions, Training, and Security 1. Agency Administrator i. Required Background 1. Understanding of radio communications usage in agency 2. Management responsibility for agency communications ii. Responsibilities 1. Single point of contact for the agency and the RSO 2. Cannot be contracted out and requires agency signing authority 3. Receives, applies for, delegates agency radio programming dongles iii. Minimum Training 1. AFRRCS Policies & Guidelines iv. Minimum Security Level 1. Refer to AFRRCS Security Policy 2. Agency standard 2. Technical Administrator i. Required Background 1. Understand P25 terminology, components and operational processes 2. Understand fleet mapping concepts and the AFRRCS implementation of Fleet mapping 3. Capable of logging into UAS to access user accounts 4. Concepts of Over the Air Rekeying (OTAR) ii. Responsibilities 1. Maintain system databases using the Unified Administration System (UAS) Version 1.0 Page 4

AFRRCS Policies and Procedures for Interoperability Agency Positions, Training and Security Policy 2. Adding/deleting users 3. Adding/deleting talk groups 4. System monitoring at agency level 5. Activity reporting 6. Establish support policy for agency 7. Initiates trouble calls to the RSO 8. Access AFRRCS metrics 9. Manage use of VTI 10. Manage an configure voice logger, consoles 11. Contacts other PSAP s directly iii. Minimum Training 1. P25 Sys Admin 2. P25 Fleet Mapping 3. Unified Sys Admin 4. AFRRCS Policies 3. Agency Trust Technician i. Required Background Working technical knowledge of radios, programming 1. Working technical knowledge of agency communications environment ii. Responsibilities 1. Programs Radio 2. Receives keys from Agency Crypto Officer- Agency directed 3. Manual Key Loading to radios, logging recorders and consoles 4. Radio Repairs 5. Mobile installation 6. Retain inventory, inventory management 7. User Training - trains the agency end-user 8. Console install, programming, updating, db mgt. 9. Manages and configures voice logger 10. Manages and configures consoles for responsible agencies 11. Manages and configures telephones 12. Does not liaise directly with RSO to troubleshoot 13. Contact other PSAPs directly iii. Minimum Training 1. AFRRCS Policies 2. Vendor radio technical training iv. Minimum Security Level 1. Refer to AFRRCS Security Policy 2. Agency minimum Version 1.0 Page 5

AFRRCS Policies and Procedures for Interoperability Agency Positions, Training and Security Policy 4. Radio End User i. Understanding Required 1. Radio indicators and icons 2. Radio alert tones 3. Make and receive group calls 4. Change groups, change systems 5. Declare, receive and clear emergency 6. place and receive individual calls 7. Return missed individual calls 8. Utilize scanning function 9. Change battery ii. Minimum Training Required 1. Subscriber radio user course 2. Common Event Talkgroups 3. Agency Talkgroups 5. Agency Console Operator i. Required Background 1. Console functions 2. Dispatch knowledge ii. Function requirements 1. Pick and select communication channels 2. Transmit and receive group and individual calls 3. Transmit, receive and clear emergency calls 4. Review call history 5. Modify communication modules 6. Create, modify and transmit on Patches and Simulselects 7. Change console setups 8. Use special and enhanced console features iii. Minimum Training Requirements 1. Console vendor specific training 2. AFRRCS training: a.patching, b.use of Common Event Talkgroups iv. Minimum Security Requirements 1. Refer to AFRRCS Security Policy 2. Agency minimum 6. Agency Crypto Officer i. Required Background 1. Understanding of encryption usage in agency ii. Responsibilities 1. Manage accounts 2. Configure crypto networks Version 1.0 Page 6

AFRRCS Policies and Procedures for Interoperability Agency Positions, Training and Security Policy 3. Rekey talk groups, user and system keys using the Unified Administration System (UAS) 4. Managing encryption Keys through the Key Management Facility (KMF) iii. Minimum Training 1. P25 Sys Admin 2. KMF Course 3. Unified Sys Admin 4. AFRRCS Policies 5. Radio vendor course iv. Minimum Security Level 1. Refer to AFRRCS Security Policy 2. Agency standard 1.2 Effective Date Agency Position and Training policy shall become effective upon approval and shall remain in effect until rescinded. This policy shall be reviewed yearly and updated when required. Version 1.0 Page 7

AFRRCS Policies and Procedures for Interoperability Agency Positions, Training and Security Policy Section 2 Appendix 2.1 Course Descriptions Course Content Duration Cost P25 System This course is strongly recommended for 4 ½ days $2,000 Administration individuals responsible for system implementation (YTsNsi) and management. It provides an understanding of terminology, equipment, components, and operational processes associated with the P25 system. Additional topics covered include fleet mapping, radio programming, overview of system management tools, configuration options, and implementation processes. Unified Administration System (VTSN6B) P25 Fleet Mapping Workshop (YriN6A) Over-The- Air Rekeying (YTSN6C) The purpose of this course is to provide system administrators and managers with the ability to create and maintain system databases using the Unified Administration System (UAS). This handson course requires an in-depth understanding of the job functions within the customer's organization as well as an operational understanding of the radio system. Course topics include logging into the UAS, establishing user accounts, navigating through the user interface, creating and changing parameter values, and adding/deleting radio users and talk groups. Completion of the P25 1P System Administration (YTSN5Z) course is a prerequisite. This workshop assists new customers in defining the system's fleet map and planning radio personalities. The advantages of different group structures and associated property, priority and coverage options are explored, and fleet mapping experience gained from other customers is shared. System configuration and radio programming options (i.e.. wide-area roaming. scanning, and emergency calls) arc also examined. Completion of the P25 r System Administration (YTSN5Z) course is a recommended prerequisite. This course provides system administrators and managers with the knowledge and skills to manage encryption keys using the Key Management Facility (KMF) product in a P25 IP network. This includes defining Crypto Officer Administration classes and user privileges; managing Crypto 2 days $800 3 days 1,200 1 day $400 Version 1.0 Page 8

AFRRCS Policies and Procedures for Interoperability Agency Positions, Training and Security Policy Officer user accounts; configuring crypto nets; and rekeying talk groups, users and system keys using the Unified Administration System (UAS). Completion of the Unified Administration System (YTSN6B) course is a recommended prerequisite. Whenever possible, courses will be offered within Alberta. Version 1.0 Page 9

Section 3 Security & Clearance

Section 4 Permitted Radios

AFRRCS Policies and Procedures for Interoperability Permitted Radio Policy AFRRCS Policies and Procedures for Interoperability Section: Permitted Radio Policy Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability Permitted Radio Policy DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 Jan 23, 2015 BS First draft version Permitted Radio Policy 0.2 March 4, 2015 BS Final draft from I&S Council 0.3 March 9, 2015 KC Formatted for approvals 1.0 June, 23, 2015 Approved by AFRRCS Governance with the addition of permitted radio tests into Appendix A Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability Permitted Radio Policy Contents Permitted Radio Policy...4 1.1 Permitted Radio Policy... 4 1.2 Effective Date... 4 Appendix A Permitted Radio Tests...5 1. Emergency ID and Alarm... 5 2. Unit ID Display (applies to display units only)... 5 3. Announcement Call... 5 4. Repeater Talk Around (must be performed away from P1 Lab to avoid interference)... 6 5. Group Scan... 6 6. Transmit Lockout... 6 7. Late Entry... 7 8. VDOC site Emergency Call Processing... 7 Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability Permitted Radio Policy Section 1 Permitted Radio Policy 1.1 Permitted Radio Policy Prior to being permitted to operate on AFRRCS, all handheld and mobile radio models must successfully pass AFRRCS Permitted Radio testing and be included on the Permitted Radio List. 1.2 Effective Date Permitted Radio Policy shall become effective upon approval and shall remain in effect until rescinded. This policy shall be reviewed yearly and updated when required. Version 1.0 Page 4

AFRRCS Policies and Procedures for Interoperability Permitted Radio Policy Section 2 Appendix A Permitted Radio Tests 1. Emergency ID and Alarm Setup Set Portable Radios 1, & 2 to Group 2, logged into system, on a multi channel site. Execution 1. On Radio 1 press and hold the emergency button to declare an emergency. (A minimum time that the emergency button must be pressed may be configured into the Radio before an emergency is declared.) 2. Verify that the Emergency ID and Alarm shows up on Radio 2 3. Clear Emergency Alarm to proceed 2. Unit ID Display (applies to display units only) Setup Set Radio 1 and 2 to Talk Group 2, Logged into Site 1 Execution 1. PTT Radio 1 and hold. Verify that Radio 2 receives the call and displays the LID of Radio 1 2. Verify that the Radio Displays Unit ID. 3. Announcement Call Setup Radio 2 to Talk Group 2 and Radio 3 to Talk Group 3. Execution 1. Place the All Call from console or supervisory radio 2. Audio should be heard at Radios 2 and 3. 3. Set Radio 2 to Talk Group 3. 4. Place the All Call from console or supervisory radio 5. Audio should be heard at Radios 2 and 3. Version 1.0 Page 5

AFRRCS Policies and Procedures for Interoperability Permitted Radio Policy 4. Repeater Talk Around (must be performed away from P1 Lab to avoid interference) 1. Place both radios on CH1 and PTT Radio 1 - verify audio is heard on radio 2. PTT Radio 2 verify audio is heard on radio 1. Verify Repeater Talk Around feature. 5. Group Scan Setup Two radios (radio 1, radio 2) each with valid IDs and two valid groups (group 2, group 3) on selected system. Radio 1 set up with group A and group B in the scan list, group A selected, and group scan initially disabled. Execution 1. Place a call from radio 2 on talk group 2. 2. Verify the call is received and audio is heard on radio 1. 3. Place a call from radio 2 on talk group 3. 4. Verify the call is not received by radio 1. 5. Enable group scan on radio 1. 6. Place another call from radio 2 on talk group 3 7. Verify that the call is now received and audio is heard on radio 1. 6. Transmit Lockout Setup use single channel site for this test Two radios (radio 1, radio 2) each with valid IDs and same valid group on selected system. Talk group used for test must be set up as transmission trunked. This feature does not apply to message trunked calls. Execution 1. Place a call from radio 1 on selected talk group by pressing and holding the PTT button. 2. Verify the call is received and audio is heard on radio 2. 3. While the call is in progress, press the PTT button on radio 2. 4. Verify that radio 2 does not transmit over (step on) the call in progress. Version 1.0 Page 6

AFRRCS Policies and Procedures for Interoperability Permitted Radio Policy 7. Late Entry Setup 2 subscriber units, both turned off Execution 1. Turn on Radio 1 (Group 2, logged into site 1) and PTT and talk. 2. While talking on Radio 1, Turn on Radio 2 (Group 2 logged into site 1). 3. Audio should be heard on Radio 2. 8. VDOC site Emergency Call Processing Objective The purpose of this test is to verify that the subscriber unit registered to a VDOC (composite channel) Site can process emergency calls, when the control channel is temporarily unavailable and later becomes available. Setup The two radios used for this test must be capable of emergency calls.. The radios must be valid on the VDOC Site being used to conduct the tests. Log Radio 1 and Radio 2 onto the VDoc used for this test. Ensure the radios are communicating on this system, when in the same Talk Group. Execution Verify the system initially logged into by Radios 1 & Radio 2 is Site the VDOC site. PTT Radio 1 and talk. The transmit (TX) indicators should turn on at Radio 1. Audio should be heard in Radio 2. The ID of Radio 1 should be seen at Radio 2. Unkey Radio 1. Press and hold the PTT on Radio 2. Immediately after pressing the PTT on radio 2, activate the Emergency Button on Radio 1 and hold down for 10 seconds. Release the Emergency Button on Radio 1, release the PTT on Radio 2 60 seconds after releasing the Emergency Button on Radio. Verify that Radio 1 indicates the TX EMER declaration and that it reverts to the home group. Verify that Radio 2 on VDOC Site (Site 2) indicate a RX EMER and hear audio on the emergency home group. Clear the emergency from Radio 1. Verify the emergency clears in the Radio 2. Using the Radio 1, select the pre-stored ID of Radio 2 or enter the Radio 2 ID directly from the keypad, and PTT Radio 1. Verify that Radio 2 receives the call and displays the ID of Radio 1. Version 1.0 Page 7

AFRRCS Policies and Procedures for Interoperability Permitted Radio Policy Release the PTT on Radio 1 and immediately PTT on Radio 2. Verify that Radio 1 receives the call and displays the ID of Radio 2. Criteria for Success Criteria for success is the subscriber unit successfully buffering the emergency call until a control channel is available to complete the call. Version 1.0 Page 8

Section 5 Radio Programming

AFRRCS Policies and Procedures for Interoperability Programming Key Policy AFRRCS Policies and Procedures for Interoperability Section: Programming Key Policy Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability Programming Key Policy DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 January 26, BS First draft programming key policy 2015 0.2 February 18, BS Approved by IS Council 2016 0.3 February 22, KC Formatted for Governance review 2016 1.0 March 22, 2016 Approved by AFRRCS Governance Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability Programming Key Policy Contents Programming Key Policy...4 1.1 Policy... 4 1.2 Effective Date... 4 Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability Programming Key Policy Section 1 Programming Key Policy Programming of radios on the Permitted Radio list can be controlled for each agency limiting them to the talk groups they can access and radio IDs for that agency. There is no restriction placed on programming conventional mutual aid channels or the use of simplex. The controls are enabled through the use of Master and Daughter programming keys. The manufacturers have all agreed to provide a Master programming key to AFRRCS for each of their permitted models. AFRRCS would provide a Daughter key configured correctly for the agency when it came onto the system. Daughter keys would require refresh every two years. 1.1 Policy a. AFRRCS will hold the master key which is able to create Daughter keys; b. Agencies will purchase a Daughter key when ordering radios, the Daughter key is to be delivered to AFRRCS; c. AFRRCS will program the provided Daughter key to match agency assigned resources. The keys will be set to expire within 2 years at which time the keys will need to be refreshed; d. The radio manufacturer must not distribute Master or Daughter keys directly to an agency; e. Payment for Daughter keys is the responsibility of the agency; f. Agency must notify AFRRCS if a Daughter key is lost or misplaced; g. AFRRCS will deny network access to any unauthorized radio(s). 1.2 Effective Date This policy shall become effective upon signature and shall remain in effect until rescinded. This policy shall be reviewed periodically and updated when required. Version 1.0 Page 4

Section 6 - Talkgroups

AFRRCS Policies and Procedures for Interoperability - Talkgroups AFRRCS Policies and Procedures for Interoperability Section: Talkgroups Version 2.0 Page 1

AFRRCS Policies and Procedures for Interoperability - Talkgroups Contents Talkgroup Policies...4 1.1 Local Talkgroups... 4 1.2 Shared Talkgroups (Interagency)... 4 1.3 Combined Event Talkgroup (CET)... 5 Appendix...6 2.1 Talkgroup Example Small Agency First Responder in Rural Alberta... 6 Version 2.0 Page 2

AFRRCS Policies and Procedures for Interoperability - Talkgroups DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 July 16, 2013 KC Talkgroup guidelines approved by IS Council 0.2 August 13, 2013 KC Draft Copy of Interoperability Guidelines with Encryption topic added. Introduction (including Council members), Purpose, and Roles and Responsibilities have been removed to a separate document. 0.3 October 11, KC Updated the number of Talkgroups for each 2013 0.4 January 23, 2014 KC CET type to be smaller and more manageable. Updated based on feedback from Governance including removing requirement for each individual Talkgroup to have an SOP. 0.5 March 13, 2014 KC Updated based on feedback from Alfred Klein to change appendix Talkgroup example to be a generic small first responder agency instead of a fire agency. 0.6 May 26, 2014 KC Ready for submission to Governance reflecting latest changes from all groups in bold. 1.0 June 10, 2014 Approved by AFRRCS Governance 1.1 November 6, 2015 1.2 February 18, 2016 KC Annual policy review BS Changed total of Provincial CET s to 16 from 5. Added emergency button policy for CETs is to be determined. Renamed Combined Event Talkgroups to Common Event Talkgroups. 2.0 March 22, 2016 Approved by AFRRCS Governance Version 2.0 Page 3

AFRRCS Policies and Procedures for Interoperability - Talkgroups Section 1 Talkgroup Policies User Agency talkgroups are initially developed when the User Agency goes through the AFRRCS Transformation process with JSG. The transformation process provides guidance on setting up talkgroup structures as well as best practices. In the transformation process, the talkgroup plan is defined, and Operations, Maintenance and Sustainability (OMS) adds the talkgroup range into the AFRRCS UAS. Note that each User Agency is responsible for programing their talkgroups into the AFRRCS UAS. The following diagram illustrates a general talkgroup structure. Diagram 1 AFRRCS Talkgroup Structure External Agency - Frequent Contact Internal Agency Communications (Talkgroups CAN be encrypted) A. Dispatch B. Fire Ground (radio to radio) C. Local Communications Local Talkgroups D. Ops Talk Group Internal Agency Communications. Talkgroups owned by local agency. Talkgroup sharing agreement used to bring in external agencies Talkgroup CAN be encrypted Common Even Talkgroup (CET) Rural, Urban and Provincial Infrequent Infrequent agency communication Agency / Does not require a talkgroup sharing agreement Incident Talkgroups CANNOT be encrypted External Agency Frequent Contact External Agency Frequent Contact Infrequent Agency / Incident Shared Talkgroup (Interagency) External Agency Frequent Contact Talkgroups owned by OTHER agency. Requires Talkgroup sharing agreement Talkgroup CAN be encrypted 1.1 Local Talkgroups A local talkgroup is used when an agency is conducting internal communications. Local Talkgroups Policy: a. An agency SOP should exist for the use of each local talkgroup. 1.2 Shared Talkgroups (Interagency) A shared talkgroup is used when user agencies need to communicate with other user agencies on a frequent (recommended minimum weekly) basis. Shared Talkgroup Policy: a. User agencies are responsible for their talkgroups and must give authorization for their talkgroups to be shared with another User Agency. b. An agency SOP shall exist for the use of shared talkgroups. c. Encryption shall be allowed on shared talkgroups. Encryption policies and procedures are the responsibility of the User Agency to define. Version 2.0 Page 4

AFRRCS Policies and Procedures for Interoperability - Talkgroups d. Recording shall be allowed on shared talkgroups. Recording policies and procedures are the responsibility of the local User Agency to define. 1.3 Common Event Talkgroup (CET) User Agencies that need to communicate with other User Agencies not frequently contacted, during special events or emergencies for example, can use Common Event Talkgroups (CET). There are three types of CETs (rural, urban, and provincial) that can enable communication on scene within a region or within the entire province. Common Event Talkgroup Policy (CET): a. Agency Protocol (e.g. SOP, dispatch, local use, command) will direct users to the appropriate CET. b. Recording of CETs (TBD) c. The use of plain language is encouraged. d. Limit the use of acronyms or abbreviations as they can mean different things to different people. e. 1 CET shall exist in each of the defined Rural Operational Areas. f. 5 CETs shall exist for each of the seven defined urban districts. g. 16 CET provincial unassigned talkgroups shall exist. The provincial CET will be activated when the event occurs using AFRRCS operating procedures. h. CETs should be used for on scene command coordination only. i. CETs are unrestricted and open to all AFRRCS agencies. Requests from first responder agencies to activate a Provincial CET should not be denied. j. Dispatch verifies if the talkgroup is clear for urban CETs. Incidents take priority. k. All AFRRCS radios shall be programmed for the CETS used in the agency response area and the 16 provincial CETs. l. Programming of emergency button on a CET (TBD) Version 2.0 Page 5

AFRRCS Policies and Procedures for Interoperability - Talkgroups Section 2 Appendix 2.1 Talkgroup Example Small Agency First Responder in Rural Alberta Communication Requirements: Local communication are required between o Dispatch and Responders o Responders Radio to Radio o Local Communications o Operations Communications with neighbouring MDs o Municipal District A (more than weekly) o Municipal District B (yearly) Communications on adhoc emergency basis or other events in surrounding areas o Estimate max 3 simultaneous events possible Municipal District A Shared Talkgroups - Radio to Radio Rural CET (e.g. Municipal District B ) Agency Local Talkgroups - Dispatch - Radio to radio - Local Communications - Ops Talk Group Version 2.0 Page 6

AFRRCS Policies and Procedures for Interoperability Coverage Classes Policy AFRRCS Policies and Procedures for Interoperability Section: Coverage Class Policy Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability Coverage Classes Policy DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 October 23, BS First draft version Coverage Class Policy 2014 0.2 December 3, KC First version approved by IS Council 2014 1.0 December 17, 2014 Approved by AFRRCS Governance Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability Coverage Classes Policy Contents Coverage Class Policy...4 1.1 Coverage Class Policy... 4 1.2 Effective Date... 4 Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability Coverage Classes Policy Section 1 Coverage Class Policy The coverage provided to each talkgroup is through the selection of a Coverage Class. Coverage Classes are defined by the System Administrator, for assignment by the Agency Administrator to their talkgroups. A Coverage Class is the definition of what geography the talkgroup is operative within. 1.1 Coverage Class Policy a) Agency talkgroups are to provide coverage within the operational area for that agency. b) County Common Event Talkgroups (CET) are to provide coverage within that County and each County adjacent to the primary County. c) Common Event Talkgroups (CET) assigned to the seven urban areas are to provide coverage within the boundaries of that city + a radius of 50 kilometres around the city limits. d) Province Wide Common Event Talkgroups (CET) are assigned a Coverage Class based on the request of the Incident Commander. 1.2 Effective Date Agency Component Testing policy shall become effective upon approval and shall remain in effect until rescinded. This policy shall be reviewed yearly and updated when required. Version 1.0 Page 4

AFRRCS Policies and Procedures for Interoperability Talkgroup Naming Conventions AFRRCS Policies and Procedures for Interoperability Section: Talkgroup Naming Conventions Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability Talkgroup Naming Conventions DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 January 23, BS First draft Talkgroup Naming Conventions 2015 0.2 March 4, 2015 BS As amended at March 4 IS Council meeting 0.3 March 9, 2015 KC Formatted for final approval 1.0 June 23, 2015 Approved by AFRRCS Governance Council Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability Talkgroup Naming Conventions Table of Contents Talkgroup Naming Conventions...4 1.1 Talkgroup Naming Conventions... 4 1.2 Effective Date... 4 Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability Talkgroup Naming Conventions Section 1 Talkgroup Naming Conventions There are three categories of talkgroups within AFRRCS: 1. Agency specific talkgroups, which are for the day to day use of the specific agency. 2. Geographically defined Common Event Talkgroups (CET s), assigned on a fixed basis to each rural municipality and the seven urban areas. 3. Province wide Common Event Talkgroups (CET s), assigned with a specific coverage, as required. 1.1 Talkgroup Naming Conventions a) Talkgroups assigned for the use of specific agencies are to be named according to the standards established by the agency assigned the talkgroup. b) Geographically assigned CET s (one per county, five for each of the seven urban areas) will follow the three digit numbering scheme for that jurisdiction, as listed in the attached Municipal Affairs 2015 Municipal Codes. Special Areas will be assigned one CET, with the designation number 464. Those areas assigned more than one CET will append a dash plus 1 digit identification for each of their assigned CET s i.e. City of Calgary 046-1, 046-2. Assigned Common Event Talkgroup (CET) designation not to be aliased in user radio. c) Province Wide CET s will be assigned the designations AFRRCS01 to AFRRCS16. Assigned Common Event Talkgroup (CET) designation not to be aliased in user radio. 1.2 Effective Date Talkgroup Naming Conventions Policy shall become effective upon approval and shall remain in effect until rescinded. This policy shall be reviewed yearly and updated when required. Version 1.0 Page 4

TalkGroup # Code Status Legal Name 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 0001 Municipal District Municipal District of Acadia No. 34 18 0012 Municipal District Athabasca County 19 0015 Municipal District County of Barrhead No. 11 20 0020 Municipal District Beaver County 21 0036 Municipal District Municipal District of Bonnyville No. 87 22 0046 City City of Calgary 23 0046 City City of Calgary 24 0046 City City of Calgary 25 0046 City City of Calgary 26 0046 City City of Calgary 27 0049 Municipal District Camrose County 28 0053 Municipal District Cardston County 29 0098 City City of Edmonton 30 0098 City City of Edmonton 31 0098 City City of Edmonton 32 0098 City City of Edmonton 33 0098 City City of Edmonton 34 0107 Municipal District Municipal District of Fairview No. 136 35 0110 Municipal District Flagstaff County 36 0111 Municipal District Municipal District of Foothills No. 31 37 0118 Municipal District County of Forty Mile No. 8 38 0132 City City of Grande Prairie 39 0132 City City of Grande Prairie 40 0132 City City of Grande Prairie 41 0132 City City of Grande Prairie 42 0132 City City of Grande Prairie 43 0133 Municipal District County of Grande Prairie No. 1 44 0159 Improvement District Improvement District No. 04 (Waterton) 45 0164 Improvement District Improvement District No. 09 (Banff) 46 0167 Improvement District Improvement District No. 12 (Jasper National Park)

47 0191 Municipal District Kneehill County 48 0193 Municipal District Lac Ste. Anne County 49 0195 Municipal District Lacombe County 50 0198 Municipal District Lamont County 51 0201 Municipal District Leduc County 52 0203 City City of Lethbridge 53 0203 City City of Lethbridge 54 0203 City City of Lethbridge 55 0203 City City of Lethbridge 56 0203 City City of Lethbridge 57 0204 Municipal District Lethbridge County 58 0217 City City of Medicine Hat 59 0217 City City of Medicine Hat 60 0217 City City of Medicine Hat 61 0217 City City of Medicine Hat 62 0217 City City of Medicine Hat 63 0222 Municipal District County of Minburn No. 27 64 0226 Municipal District Mountain View County 65 0235 Municipal District County of Newell 66 0243 Municipal District County of Paintearth No. 18 67 0245 Municipal District Parkland County 68 0246 Municipal District Municipal District of Peace No. 135 69 0251 Municipal District Municipal District of Pincher Creek No. 9 70 0255 Municipal District Ponoka County 71 0258 Municipal District Municipal District of Provost No. 52 72 0262 City City of Red Deer 73 0262 City City of Red Deer 74 0262 City City of Red Deer 75 0262 City City of Red Deer 76 0262 City City of Red Deer 77 0263 Municipal District Red Deer County 78 0269 Municipal District Rocky View County 79 0286 Municipal District Smoky Lake County 80 0287 Municipal District Municipal District of Smoky River No. 130 81 0290 Municipal District Municipal District of Spirit River No. 133 82 0294 Municipal District County of St. Paul No. 19 83 0296 Municipal District Starland County 84 0299 Municipal District County of Stettler No. 6 85 0302 Specialized Municipality Strathcona County 86 0305 Municipal District Sturgeon County 87 0312 Municipal District Municipal District of Taber 88 0314 Municipal District Thorhild County 89 0323 Municipal District County of Two Hills No. 21 90 0329 Municipal District County of Vermilion River 91 0334 Municipal District Vulcan County 92 0336 Municipal District Municipal District of Wainwright No. 61 93 0340 Municipal District County of Warner No. 5

94 0346 Municipal District Westlock County 95 0348 Municipal District County of Wetaskiwin No. 10 96 0349 Municipal District Wheatland County 97 0353 Municipal District Municipal District of Willow Creek No. 26 98 0361 Specialized Municipality Municipality of Crowsnest Pass 99 0373 Improvement District Kananaskis Improvement District 100 0376 Municipal District Cypress County 101 0377 Municipal District Clearwater County 102 0382 Municipal District Municipal District of Bighorn No. 8 103 0383 Municipal District Brazeau County 104 0418 Specialized Municipality Municipality of Jasper 105 0480 Municipal District Woodlands County 106 0481 Municipal District Municipal District of Greenview No. 16 107 0482 Municipal District Yellowhead County 108 0496 Municipal District Northern Sunrise County 109 0501 Municipal District Municipal District of Ranchland No. 66 110 0502 Municipal District Birch Hills County 111 0503 Municipal District Saddle Hills County 112 0504 Municipal District Clear Hills County 113 0505 Specialized Municipality Mackenzie County 114 0506 Municipal District Municipal District of Big Lakes 115 0507 Municipal District Municipal District of Lesser Slave River No. 124 116 0508 Specialized Municipality Regional Municipality of Wood Buffalo 117 0511 Municipal District County of Northern Lights 118 0512 Municipal District Municipal District of Opportunity No. 17 119 4353 Municipal District Lac La Biche County 121 464 Special Areas Special Areas No. 2,3,4 123 550 Fort McMurray 124 551 Fort McMurray 125 552 Fort McMurray 126 553 Fort McMurray 127 554 Fort McMurray

Name Talkgroup Description Alias Province Wide CET AFRRCS01 AFRRCS01 Province Wide CET AFRRCS02 AFRRCS02 Province Wide CET AFRRCS03 AFRRCS03 Province Wide CET AFRRCS04 AFRRCS04 Province Wide CET AFRRCS05 AFRRCS05 Province Wide CET AFRRCS06 AFRRCS06 Province Wide CET AFRRCS07 AFRRCS07 Province Wide CET AFRRCS08 AFRRCS08 Province Wide CET AFRRCS09 AFRRCS09 Province Wide CET AFRRCS10 AFRRCS10 Province Wide CET AFRRCS11 AFRRCS11 Province Wide CET AFRRCS12 AFRRCS12 Province Wide CET AFRRCS13 AFRRCS13 Province Wide CET AFRRCS14 AFRRCS14 Province Wide CET AFRRCS15 AFRRCS15 Province Wide CET AFRRCS16 AFRRCS16 ACADIA NO. 34, M.D. OF CET001ACADMD CET001ACADMD ATHABASCA COUNTY CET012ATHCNT CET012ATHCNT BARRHEAD NO. 11, COUNTY OF CET015BARRCNT CET015BARRCNT BEAVER COUNTY CET020BEAVCNT CET020BEAVCNT BONNYVILLE NO. 87, M.D. OF CET036BONNMD CET036BONNMD CALGARY CET0461CALG CET0461CALG CALGARY CET0462CALG CET0462CALG CALGARY CET0463CALG CET0463CALG CALGARY CET0464CALG CET0464CALG CALGARY CET0465CALG CET0465CALG CAMROSE COUNTY CET049CAMRCNT CET049CAMRCNT CARDSTON COUNTY CET053CARDCNT CET053CARDCNT EDMONTON CET0981EDM CET0981EDM EDMONTON CET0982EDM CET0982EDM EDMONTON CET0983EDM CET0983EDM EDMONTON CET0984EDM CET0984EDM EDMONTON CET0985EDM CET0985EDM FAIRVIEW NO. 136, M.D. OF CET107FAIRMD CET107FAIRMD FLAGSTAFF COUNTY CET110FLAGCNT CET110FLAGCNT FOOTHILLS NO. 31, M.D. OF CET111FOOTMD CET111FOOTMD FORTY MILE NO. 8, COUNTY OF CET118FORTMD CET118FORTMD GRANDE PRAIRIE CET1321GRPR CET1321GRPR GRANDE PRAIRIE CET1322GRPR CET1322GRPR GRANDE PRAIRIE CET1323GRPR CET1323GRPR GRANDE PRAIRIE CET1324GRPR CET1324GRPR GRANDE PRAIRIE CET1325GRPR CET1325GRPR GRANDE PRAIRIE NO. 1, COUNTY OFCET133GRANMD CET133GRANMD I.D. NO. 04 (WATERTON) CET159WATID CET159WATID I.D. NO. 09 (BANFF) CET164BANFF CET164BANFF I.D. NO. 12 (JASPER NATIONAL PARK) CETI167JASPER CETI167JASPER

KNEEHILL COUNTY CET191KNEECNT CET191KNEECNT LAC STE. ANNE COUNTY CET193LACSA CET193LACSA LACOMBE COUNTY CET195LCMBCNT CET195LCMBCNT LAMONT COUNTY CET198LAMTCNT CET198LAMTCNT LEDUC COUNTY CET201LEDUCCNT CET201LEDUCCNT LETHBRIDGE CET2031LETHB CET2031LETHB LETHBRIDGE CET2032LETHB CET2032LETHB LETHBRIDGE CET2033LETHB CET2033LETHB LETHBRIDGE CET2034LETHB CET2034LETHB LETHBRIDGE CET2035LETHB CET2035LETHB LETHBRIDGE COUNTY CET204LETHCNT CET204LETHCNT MEDICINE HAT CET2171MHAT CET2171MHAT MEDICINE HAT CET2172MHAT CET2172MHAT MEDICINE HAT CET2173MHAT CET2173MHAT MEDICINE HAT CET2174MHAT CET2174MHAT MEDICINE HAT CET2175MHAT CET2175MHAT MINBURN NO. 27, COUNTY OF CET222MINBCNT CET222MINBCNT MOUNTAIN VIEW COUNTY CET226MOUNV CET226MOUNV NEWELL, COUNTY OF CET235NEWCNT CET235NEWCNT PAINTEARTH NO. 18, COUNTY OF CET243PAINCTY CET243PAINCTY PARKLAND COUNTY CET245PARKCNT CET245PARKCNT PEACE NO. 135, M.D. OF CE T246PEACMD CE T246PEACMD PINCHER CREEK NO. 9, M.D. OF CET251PINCMD CET251PINCMD PONOKA COUNTY CET255PONCNT CET255PONCNT PROVOST NO. 52, M.D. OF CET258PROVMD CET258PROVMD RED DEER CET2621REDD CET2621REDD RED DEER CET2622REDD CET2622REDD RED DEER CET2623REDD CET2623REDD RED DEER CET2624REDD CET2624REDD RED DEER CET2625REDD CET2625REDD RED DEER COUNTY CET263REDCNT CET263REDCNT ROCKY VIEW COUNTY CET269ROCVCNT CET269ROCVCNT SMOKY LAKE COUNTY CET286SMOKLCNT CET286SMOKLCNT SMOKY RIVER NO. 130, M.D. OF CET287SMOKRVMD CET287SMOKRVMD SPIRIT RIVER NO. 133, M.D. OF CET290SPRVMD CET290SPRVMD ST. PAUL NO. 19, COUNTY OF CET294STPLMD CET294STPL MD STARLAND COUNTY CET296STARCNT CET296STARCNT STETTLER NO. 6, COUNTY OF CET299STETTCNT CET299STETTCNT STRATHCONA COUNTY CET302STRATHCNT CET302STRATHCNT STURGEON COUNTY CET305STURCNT CET305STURCNT TABER, M.D. OF CET312TABERMD CET312TABERMD THORHILD COUNTY CET314THORCNT CET314THORCNT TWO HILLS NO. 21, COUNTY OF CET323TWOHMD CET323TWOHMD VERMILION RIVER, COUNTY OF CET329VERRVCNT CET329VERRVCNT VULCAN COUNTY CET334VULCNT CET334VULCNT WAINWRIGHT NO. 61, M.D. OF CET336WAINMD CET336WAINMD WARNER NO. 5, COUNTY OF CET340WARNCNT CET340WARNCNT

WESTLOCK COUNTY CET346WESLCNT CET346WESLCNT WETASKIWIN NO. 10, COUNTY OF CET348WETACNT CET348WETACNT WHEATLAND COUNTY CET349WHEACNT CET349WHEACNT WILLOW CREEK NO. 26, M.D. OF CET353WILLMD CET353WILLMD CROWSNEST PASS, Municipality of CET361CROWPMD CET361CROWPMD KANANASKIS IMPROVEMENT DISTRICT CET461KANID CET461KANID CYPRESS COUNTY CET376CYPCNT CET376CYPCNT CLEARWATER COUNTY CET377CLRWCNT CET377CLRWCNT BIGHORN NO. 8, M.D. OF CET382BIGHMD CET382BIGHMD BRAZEAU COUNTY CET383BRAZCNT CET383BRAZCNT JASPER, Municipality of CET418JASPER CET418JASPER WOODLANDS COUNTY CET480WOODCNT CET480WOODCNT GREENVIEW NO. 16, M.D. OF CET481GREENMD CET481GREENMD YELLOWHEAD COUNTY CET482YELHCNT CET482YELHCNT NORTHERN SUNRISE COUNTY CET496NORSUCNT CET496NORSUCNT RANCHLAND NO. 66, M.D. OF CET501RANCHMD CET501RANCHMD BIRCH HILLS COUNTY CET502BIRCHCNT CET502BIRCHCNT SADDLE HILLS COUNTY CET503SADDLCNT CET503SADDLCNT CLEAR HILLS COUNTY CET504CLEARCNT CET504CLEARCNT MACKENZIE COUNTY CET505MACKCNT CET505MACKCNT BIG LAKES, M.D. OF CET506BIGLMD CET506BIGLMD LESSER SLAVE RIVER NO. 124, M.D. CET507LSLAVRMD OF WOOD BUFFALO, Regional Municipality CET508WOODBMD of CET507LSLAVRMD CET508WOODBMD NORTHERN LIGHTS, COUNTY OF CET511NORLTMD CET511NORLTMD OPPORTUNITY NO. 17, M.D. OF CET512OPPMD CET512OPPMD LAC LA BICHE COUNTY CET4353LLBCNT CET4353LLBCNT CET464SPAR CET550FTMAC CET551FTMAC CET552FTMAC CET553FTMAC CET554FTMAC CET464SPAR CET550FTMAC CET551FTMAC CET552FTMAC CET553FTMAC CET554FTMAC

8 Non-Agency AFRRCS Coverage Class Map 28

AFRRCS Policies and Procedures for Interoperability Talkgroup Priority AFRRCS Policies and Procedures for Interoperability Section: Talkgroup Priority Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability Talkgroup Priority Contents Contents Talkgroup Priority Policy...4 1.1 Talkgroup Priority Policy... 4 1.2 Effective Date... 4 Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability Talkgroup Priority DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 October 23, BS First draft version Talkgroup Priority Policy 2014 0.2 March 4, 2015 BS Final version approved by Interoperability & Standards Council 1.0 June 23, 2015 Approved by AFRRCS Governance Council Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability Talkgroup Priority Section 1 Talkgroup Priority Policy Trunked radio systems provide the opportunity to prioritize some talkgroups at a higher level than other talkgroups. This only comes into play if calls are queued, waiting for resources, at a repeater site. Higher priority talkgroups are placed higher in the queue for those resources than lower priority talkgroups. Higher priority calls do not pre-empt calls that are in process 1.1 Talkgroup Priority Policy a) Common Event Talkgroups (CETs) will not be assigned a higher or lower priority than first responder agency talkgroups. b) First responder agency talkgroups will have a higher priority level than secondary responder talkgroups. c) Individual agencies may choose to assign different priorities within their own talkgroups i.e. Training TG lower priority than Event TG. 1.2 Effective Date Talkgroup Priority Policy shall become effective upon approval and shall remain in effect until rescinded. This policy shall be reviewed yearly and updated when required. Version 1.0 Page 4

AFRRCS Policies and Procedures for Interoperability Patching Policy AFRRCS Policies and Procedures for Interoperability Section: Patching Policy Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability Patching Policy DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 January 27, BS First draft version of the Patching Policy 2016, 2014 0.2 February 18, BS Approved by IS Council 2016 0.3 February 22, KC Formatted for Governance review 2016 0.4 March 14, 2016 BS Added the use of consoles that support System Assigned IDs to be exempt from the limitation of patching 2 talkgroups. 1.0 March 22, 2016 Approved by AFRRCS Governance Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability Patching Policy Contents Patching Policy...4 1.1 Patching Policy... 4 1.2 Effective Date... 4 Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability Patching Policy Section 1 Patching Policy Approximately 80% of AFRRCS sites have four channels, one channel is dedicated for controlling leaving three available channels for voice traffic. An issue was found when patching talkgroups with non-harris consoles that a channel is required for each patch, this could easily tie up most AFRRCS sites. Patching three talkgroups together consumes the total number of channels. Patching four or more talkgroups produces an unpredictable result. 1.1 Patching Policy Patching policies: a) For multiagency communications, users should be directed to a shared talkgroup or Common Event Talkgroup when possible; b) All agencies should design their talkgroups to minimize the use of patching c) Dispatchers should not patch more than two AFRRCS talkgroups together. If the combination of more AFRRCS talkgroups is required, intra-agency communications, users should be directed to an agency tactical talkgroup or Common Event Talkgroup d) Consoles utilizing a System Assigned ID (SAID) to create a new combined talkgroup at the system level will be deemed exempt from (c) of this patching policy. e) OMS reserves the right to limit the use of patching to preserve system integrity 1.2 Effective Date This policy shall become effective upon approval and shall remain in effect until rescinded. This policy shall be reviewed yearly and updated when required. Version 1.0 Page 4

AFRRCS Policies and Procedures for Interoperability Unconfirmed Talkgroup Policy AFRRCS Policies and Procedures for Interoperability Section: Unconfirmed Talkgroup Policy Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability Unconfirmed Talkgroup Policy DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 January 27, 2016, 2014 BS First draft version of the Unconfirmed Talkgroup Policy 0.2 February 18, BS Approved by IS Council 2016 0.3 February 22, KC Formatted for Governance review 2016 1.0 March 22, 2016 Approved by AFRRCS Governance Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability Unconfirmed Talkgroup Policy Contents Unconfirmed Talkgroup Policy...4 1.1 Unconfirmed Talkgroup Policy... 4 1.2 Effective Date... 4 Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability Unconfirmed Talkgroup Policy Section 1 Unconfirmed Talkgroup Policy Confirmed Talkgroups, do not permit a call to be established until radio channel resources are available to support all of the users in the talkgroup. This feature gives users confidence that all of their colleagues are participating in a call, but when the system is under high load it can result in call delays. Unconfirmed Talkgroups are permitted to start even if the system can only support a subset from the outset. As radio channel resources free up, additional users are able to join the call. This mode of operations allows the call to begin quickly, particularly in times of high usage. 1.1 Unconfirmed Talkgroup Policy a. AFRRCS Talkgroups are to be configured as unconfirmed talkgroups. 1.2 Effective Date This policy shall become effective upon approval and shall remain in effect until rescinded. This policy shall be reviewed yearly and updated when required. Version 1.0 Page 4

Section 7 Trunking Features

Section 8 - Encryption

AFRRCS Policies and Procedures for Interoperability AES, and KMF Vendor AFRRCS Policies and Procedures for Interoperability Section: AES, and KMF Vendor Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability AES, and KMF Vendor Contents AES and KMF Vendor Policies... 4 1.1 Encryption Policy... 4 1.2 Effective Date... 4 Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability AES, and KMF Vendor DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 March 17, 2014 KC Encryption policy and procedure for Encryption Work Group second reading. 0.2 March 27, 2014 BS Amendments made by Encryption Workgroup 0.3 May 22, 2014 KC Version 1 1.0 December 17, 2014 Approved by AFRRCS Governance Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability AES, and KMF Vendor Section 1 AES and KMF Vendor Policies AFRRCS, as well as some subscriber radios, support both AES 256 bit encryption and DES encryption. AES, a newer more robust encryption algorithm that has generally replaced DES, has been set as the encryption standard for AFRRCS. Standardizing on one algorithm will simplify interagency communications where encryption is required and provide a more secure environment for users. No KMF manufacturers who made presentations to the AFRRCS Encryption Workgroup, except Harris, had a product that would successfully and directly connect to a Harris P25 VIDA network. A Harris, or non- Harris manual key-loading device could be used if desired by agencies. All manual key-loading devices should be tested prior to implementation on AFRRCS. 1.1 Encryption Policy AES shall be the only encryption algorithm used by AFRRCS agencies, unless otherwise approved by RSO. Agencies utilizing encryption on AFRRCS and who desire the use of a network-connected Key Management Facility (KMF) shall use a Harris KMF. 1.2 Effective Date This policy shall become effective upon approval and shall remain in effect until rescinded. This policy shall be reviewed yearly and updated when required. Version 1.0 Page 4

Section 9 Over the Air Updates

AFRRCS Policies and Procedures for Interoperability OTAR AFRRCS Policies and Procedures for Interoperability Section: OTAR Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability OTAR Contents OTAR Policies and Procedures... 4 1.1 OTAR Policy... 4 1.2 OTAR Procedures... 4 1.3 Effective Date... 4 Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability OTAR DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 March 17, 2014 KC For second reading by Encryption WG 0.2 March 27, 2014 BS Amendments made by Encryption Workgroup 0.3 May 27, 2014 KC Version 1. 1.0 December 17, 2014 Approved by AFRRCS Governance. Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability OTAR Section 1 OTAR Policies and Procedures Over-the-Air-Rekeying (OTAR) is the process for changing a Traffic Encryption Key (TEK) or Key Encryption Key (KEK) in a radio or device by sending a new key directly to the radio or device over the communication path it secures. 1.1 OTAR Policy OTAR shall not be undertaken during network busy periods. Scheduling to be negotiated with the Radio Service Organization (RSO). If a network event occurs that makes reprogramming inadvisable, the RSO must notify agencies scheduled for reprogramming and arrange an alternative time. Data usage for four channel sites shall be restricted to one repeater, two repeaters at eight channel sites, three at twelve channel sites. 1.2 OTAR Procedures A crypto-officer must be appointed for agencies using encryption. Minimum training requirements for Crypto-officer will be provided by the Interoperability & Standards Council. Rekeying and programming frequency are determined on an agency basis, and scheduling must be approved by the RSO. Emergency re-keying of 100 or fewer radios is permitted as required. Emergency rekeying of more than 100 radios to be approved by RSO. Emergency rekeying can be supported by RSO partitioning of the data channel, as required. AFRRCS will provide troubleshooting procedures for OTAR, as it pertains to the network. Prior to an agency implementing OTAR the RSO must verify that there is no negative impact on the AFRRCS network. AFRRCS will provide facilities for this testing. The RSO reserves the right to limit the use of OTAP to preserve system integrity. 1.3 Effective Date This policy shall become effective upon approval and shall remain in effect until rescinded. This policy shall be reviewed yearly and updated when required. Version 1.0 Page 4

AFRRCS Policies and Procedures for Interoperability OTAP AFRRCS Policies and Procedures for Interoperability Section: OTAP Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability OTAP Contents OTAP Policies and Procedures... 4 1.1 OTAP Policy... 4 1.2 OTAP Procedures... 4 1.3 Effective Date... 4 Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability OTAP DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 March 17, 2014 KC For second reading by Encryption WG 0.2 March 27, 2014 BS Amendments made by Encryption Workgroup 0.3 May 27, 2014 KC Version 1. 1.0 December 17, 2014 Approved by AFRRCS Governance Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability OTAP Section 1 OTAP Policies and Procedures Over-the-Air Programming (OTAP) provides the capability to change the radio s entire personality and features over the air. Changes to a radio s specific personality, such as talkgroup affiliation, user preferences, access to system features, etc., are transmitted over the air to the radio. User agencies will have an easier, less time-consuming method of managing their radios. 1.1 OTAP Policy OTAP or shall not be undertaken during network busy periods. Scheduling to be negotiated with the Radio Service Organization (RSO). If a network event occurs that makes reprogramming inadvisable, the RSO must notify agencies scheduled for reprogramming and arrange an alternative time. Data usage for four channel sites shall be restricted to one repeater, two repeaters at eight channel sites, three at twelve channel sites. 1.2 OTAP Procedures Programming frequency are determined on an agency basis, and scheduling must be approved by the RSO. Emergency programming of 100 or fewer radios is permitted as required. Emergency programming of more than 100 radios to be approved by RSO. Emergency programming can be supported by RSO partitioning of the data channel, as required. AFRRCS will provide troubleshooting procedures for OTAP as it pertains to the network. Prior to an agency implementing OTAP the RSO must verify that there is no negative impact on the AFRRCS network. AFRRCS will provide facilities for this testing. The RSO reserves the right to limit the use of OTAP to preserve system integrity. 1.3 Effective Date This policy shall become effective upon approval and shall remain in effect until rescinded. This policy shall be reviewed yearly and updated when required. Version 1.0 Page 4

Section 10 Problem Management

Section 11 - System & Data Integrity

Section 12 - Connectivity

AFRRCS Policies and Procedures for Interoperability Dispatch Centre Connectivity AFRRCS Policies and Procedures for Interoperability Section: Dispatch Centre Connectivity Version 2.0 Page 1

AFRRCS Policies and Procedures for Interoperability Dispatch Centre Connectivity DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 January 27, BS Draft policy for Dispatch Centre connectivity 2015 0.2 March 4, 2015 BS As discussed with Interoperability & Standards Council 0.3 March 9, 2015 KC Formatted for final approval 1.0 June 23, 2015 Approved by AFRRCS Governance Council 1.1 Feb 18, 2016 BS Updated with feedback from the Console workgroup and the IS Council 1.2 February 22, KC Formatted for Governance approval 2016 2.0 March 22, 2016 Approved by AFRRCS Governance Version 2.0 Page 2

AFRRCS Policies and Procedures for Interoperability Dispatch Centre Connectivity Contents Dispatch Centre Connectivity Policy...4 1.1 Policy... 4 1.2 Effective Date... 4 Version 2.0 Page 3

AFRRCS Policies and Procedures for Interoperability Dispatch Centre Connectivity Section 1 Dispatch Centre Connectivity Policy Dispatch Centres are the hub in the center of each first responder agency. If Dispatch is not available, first responder agencies are severely handicapped in meeting their mandates. The connectivity policy ensures that each dispatch centre will be connected to the AFRRCS radio system in a manner that ensures uninterrupted access. 1.1 Policy a. Agency dispatch is allowed to use over-the-air connected AFRRCS dispatch radios under the following conditions: Dispatch radio is within the operational area of the agency; the dispatch radio is within the coverage of the radio-site that participates in most of the agency s radio traffic; the additional network traffic from the dispatch radio will not degrade capacity at the existing AFRRCS sites. b. Every first responder dispatch centre not utilizing the over-the-air-connection, will be connected to the AFRRCS network through an agency provided, AFRRCS approved IP connection sized to meet their operational volumes. c. Each first responder dispatch centre should provision an agency provided, AFRRCS approved back-up IP access to AFRRCS. d. Each first responder dispatch centre should provide an AFRRCS approved wireless backup connection to AFRRCS, to be used only in the event of an IP connectivity loss. e. IP Connected Consoles can be connected to the AFRRCS by the following methods i. Proprietary Harris Interface ii. ISSI/CSSI interface iii. Harris Gateway 1.2 Effective Date Dispatch Centre Connectivity policy shall become effective upon approval and shall remain in effect until rescinded. This policy shall be reviewed yearly and updated when required. Version 2.0 Page 4

Section 13 - Site on Wheels Deployment

AFRRCS Policies and Procedures for Interoperability - Site on Wheels (SoW) Deployment Request AFRRCS Policies and Procedures for Interoperability Section: Site on Wheels (SoW) Deployment Request Version 1.0 Page 1

AFRRCS Policies and Procedures for Interoperability - Site on Wheels (SoW) Deployment Request Contents Site on Wheels (SoW) Deployment Request Policies... 4 1.1 Available Resources for Deployment... 4 1.2 Deployment Authorized Uses... 4 1.3 SoW Deployment Request Policy... 4 1.4 SoW Deployment Procedures... 4 1.5 Effective Date... 5 Signature Page... 6 Version 1.0 Page 2

AFRRCS Policies and Procedures for Interoperability - Site on Wheels (SoW) Deployment Request DOCUMENT REVISION HISTORY Version Date Modified By Section, Page(s), Text Revised 0.1 March 17, 2014 KC Site on Wheels (SoW) Deployment Request approved by IS Council 0.2 May 26, 2014 KC Updated based on feedback from IS Council for SoW location for storage and organization that would manage and prioritize requests. 1.0 December 17, 2014 Approved by AFRRCS Governance Version 1.0 Page 3

AFRRCS Policies and Procedures for Interoperability - Site on Wheels (SoW) Deployment Request Section 1 Site on Wheels (SoW) Deployment Request Policies Fully featured 4 channel, 700 MHz P25 trunked Site on Wheels (SoW) with satellite backhaul to the network core provides quick deployment of portable communications coverage virtually anywhere in Alberta. 1.1 Available Resources for Deployment This deployment policy covers four separate resources: Radio Cache 1, 150 handheld radios Radio Cache 2, 150 handheld radios Site on Wheels 1, mobile four repeater site Site on Wheels 2, mobile four repeater site 1.2 Deployment Authorized Uses The SoW may be deployed by AFRRCS first responder user agencies for: Planned events that may overload normal radio capacity (Sporting event, concerts, rodeo, rallies, demonstrations, protests) Emergencies (fire, flood, tornado, winter storm, explosion) Temporary System capacity issues Temporary System coverage issues Loss of agency radios or requirement for additional radios Interoperability requirement Other uses as authorized by RSO 1.3 SoW Deployment Request Policy a) Request for SoW deployment shall come from the Chief/Executive Director or Delegate of the requesting agency. b) Suitable security measures (to be defined), responsibility of requesting agency. c) Requesting agency assumes financial responsibility for the equipment issued. d) The AFRRCS SoW deployment team shall adhere to the AFRRCS SoW Deployment SOP including training guidelines. e) SoWs should be based in Edmonton and Calgary for deployment. SoW must be inspected and returned to full operational readiness upon return. Damages or loss of equipment incurred during the mobilization will be charged back to the requesting agency. 1.4 SoW Deployment Procedures a. Example recording system to track radios as issued and returned is located in Appendix A. b. The requesting agency/chief or designate would request SoW deployment through the POC who would prioritize and determine where and when they would be deployed Version 1.0 Page 4

AFRRCS Policies and Procedures for Interoperability - Site on Wheels (SoW) Deployment Request c. Service Level Objectives for response times of the SoW are i. Four hours from receipt of authorized call for SOW to be mobile ii. Four hours from receipt of authorized call for radio cache to be made available for transport to requesting agency 1.5 Effective Date This policy shall become effective upon signature and shall remain in effect until rescinded. This policy shall be reviewed periodically and updated when required. Version 1.0 Page 5

AFRRCS Policies and Procedures for Interoperability - Site on Wheels (SoW) Deployment Request Section 2 Signature Page Signature Page AFRRCS Policies and Procedures for Interoperability Site on Wheels (SoW) Deployment Request Interoperability and Standards Council Approval: Interoperability and Standards Council Chair Date AFRRCS Governance Approval: Governance Chair Date Version 1.0 Page 6

AFRRCS Policies and Procedures for Interoperability - Site on Wheels (SoW) Deployment Request Section 3 Appendix A Radio Inventory Scanner Example The following is an example of an inventory scanner app that can be used to track the distribution of radios from the radio cache. Other Apps from different vendors or systems can be evaluated for agency use. Note that bar codes must be added to phones for this solution to work. Installing the Inventory Scanner App on your iphone 1. Download the Inventory Scanner software: https://itunes.apple.com/ca/app/inventory-scanner/id365563373?mt=8 Setting Up Inventory Scanner 1. Select the Inventory Scanner icon on your iphone. 2. Select the + symbol on the top left of the screen. 3. Add inventory name, description, and date. Version 1.0 Page 7

AFRRCS Policies and Procedures for Interoperability - Site on Wheels (SoW) Deployment Request 4. Select save. Distributing Radios to Radio Users 1. From the inventory screen for the inventory created above select the camera symbol. 2. Scan the serial number of the radio. Version 1.0 Page 8

AFRRCS Policies and Procedures for Interoperability - Site on Wheels (SoW) Deployment Request 3. The serial number should display as the name of the product, add the person s name receiving the radio to the description field. 4. Check to see the serial number is added to the Products list with a Quantity of 1. Version 1.0 Page 9

AFRRCS Policies and Procedures for Interoperability - Site on Wheels (SoW) Deployment Request 5. Continue adding the radio cache to the inventory as the radios are distributed. Receiving Radios Back from Users 1. From the inventory screen for the inventory created above select the camera symbol. 2. Scan the serial number of the radio. 3. Already in inventory screen should display, select -1. 4. Select Remove. 5. Check to see the serial number is removed from the Products list. 6. Continue removing the radio cache from the inventory as the radios are received. Finalizing Inventory Version 1.0 Page 10

AFRRCS Policies and Procedures for Interoperability - Site on Wheels (SoW) Deployment Request 1. From the inventory screen review the list of the Unaccounted-For Barcodes, click the product to view details. Version 1.0 Page 11

Section 14 - Operational Change