Loading...
HomeMy WebLinkAboutRegional Planning Public Safety Intranet-Regional Interlocal Agreement w/Broward CountyREGIONAL INTERLOCAL AGREEMENT BETWEEN BROWARD COUNTY AND THE CITY OF TAMARAC PROVIDING FOR COOPERATIVE PARTICIPATION IN A REGIONAL PUBLIC SAFETY INTRANET This Regional Interlocal Agreement ("Agreement") is made and entered into by and between Broward County ("County"), a political subdivision of the State of Florida, and City ol'amarac ("City"), a Florida municipal corporation (collectively City and County referred to as the "Parties") providing for cooperative participation in a Regional Public Safety Intranet ("RPSI"). WHEREAS, this Agreement is entered into pursuant to §163.01, Florida Statutes, also known as the "Florida Interlocal Cooperation Act of 1969"; and WHEREAS, County is to establish, with cooperation of Broward cities, a county -wide interoperable public safety intranet that can support closest unit response in life -threatening emergencies and regional specialty teams; and WHEREAS, the Parties desire to satisfy the intentions of the Broward County Charter by insuring that someone with a life -threatening emergency receive care from the closest available emergency vehicle; and WHEREAS, the City agrees to work towards insuring someone with a life -threatening emergency receive care from the closest available emergency vehicle, including pursuing automatic aid agreements with neighboring cities who utilize the county -wide CAD system; and WHEREAS, the Parties desire to enhance radio interoperability by interconnecting County and City public safety radio users and to enhance information sharing by interconnecting County and City public safety data users; and WHEREAS, County maintains a Trunked Radio System, Computer Aided Dispatching ("CAD") System, Automated Vehicle Location ("AVL") System, a Law Records Management System ("LRMS"), and a Fire Records Management System ("FRMS") as part of its public safety intranet that supports county -wide police, fire, and emergency services; and WHEREAS, the Parties desire to make the most efficient use of their technical resources to enable the Parties to cooperate with each other to provide quality county -wide public safety communication services; G NOW, THEREFORE, IN CONSIDERATION of the mutual covenants and promises, set forth, the Parties agree as follows: ARTICLE 1 DEFINITIONS 1.1 Advanced Tactical Mapping ("ATM"): A component of the RPSI that provides computer aided dispatch mapping. In conjunction with AVL, these maps pinpoint the real time location, availability, status,. and routing of emergency vehicles which ultimately enhance response times. 1.2 Automated Vehicle Location ("AVL") System: A component of the RPSI that provides GPS-based tracking of public safety vehicles. AVL facilitates closest unit response when coupled with a common CAD platform. 1.3 Board of County Commissioners: The term "Board of County Commissioners" shall mean the Board of County Commissioners of Broward County, Florida. Page 1 of 99 1.4 Capital: The term "Capital" shall mean costs for machinery, equipment, vehicles or other tangible assets that are used in operations and that* have initial useful lives extending beyond a single reporting period. The term shall exclude call -taking and dispatch equipment and other capital items that are purchased by County pursuant to the provisions of Section 5.03A of the Charter of Broward County. 1.5 Change Management Requests ("CMR"): The- process used to specify the times and conditions when designated tasks can be performed on all software and hardware affiliated with the RPSI including but not limited to the Trunked Radio System, Public Safety Network, Computer Aided Dispatch (CAD) System, E-911, etc. The CMR is more fully explained in Exhibit D. 1.6 Computer Aided Dispatch ("CAD") System: A component of the RPSI that has as one of its functions, in conjunction with the AVL System, the ability to assist a radio dispatcher in identifying and dispatching public safety vehicles and personnel closest to the scene of an incident. 1.7 Contract Administrator: County's Director of the Office of Communications Technology. 1.8 County: The term "COUNTY" shall mean the government of Broward County, acting through the Board of County Commissioners or its designee. 1.9 Demarcation Points: A "Demarcation Point" or "Demarc" identifies a responsibility boundary between City -responsible items and County -responsible items. Exhibit B further defines and visually portrays the RPSI Demarcation Points and entity responsibilities on a portion -by -portion basis. 1.10 Equipment: The County -owned and maintained items listed in Exhibit C and any other County - provided items. 1.11 Fire Records Management System ("FRMS"): A component of the RPSI that archives fire -related dispatch records and information. 1.12 Fire Rescue Frontline Vehicles: Vehicles that are typically dispatched in the initial stages of an incident for the protection and preservation of life, property, and the environment. Vehicles whose primary purpose is responding to emergencies where time is critical, i.e., Fire Engines (Pumpers), Ladder Trucks, Medical Rescue Vehicles, and Shift Commanders. Frontline vehicles are staffed and dispatched and do not include resources held in a reserve or staff capacity. 1.13 Fire Station Alerting: Allows regional and non -regional communication centers to efficiently respond to emergencies by managing the assets of multiple fire stations. Public Safety - Dispatch Centers can dispatch an engine, ambulance, entire station, or multiple stations by selecting them on their computer screen or by the push of a few buttons. 1.14 Hosted Master Site: The Hosted Master Site is the central hub for all analog and secure two-way radio voice processing. The Motorola Hosted Master Site replaced the County owned SmartZone Controller which was at end of life. The Hosted Master site uses Motorola's SmartX solution inclusive of analog to digital site converters which will allow the existing SmartZone 3.0 Radio Network to communicate to a P25 I P platform. 1.15 Law Records Management System ("LRMS"): A component of the RPSI that archives law enforcement dispatch records and information. 1.16 NetMotion: A component of the RPSI that improves mobile data network performance, encryption, communication stability, and roaming between disparate private and public wireless networks. Page 2 of 99 I 1.17 Network Mobility Zone ("NMZ"): A component of the RPSI which extends the public safety network to multiple jurisdictions. The network mobility zone provides the mobile data and remote facility user's access to the core of the Public Safety Intranet applications. 1.18 Non -Dispatch Facility: A City owned facility hosted by the infrastructure, applications, and services of the RPSI. A non -dispatch facility does not receive E-911 calls nor does it provide City-wide or county -wide dispatch services. A non -dispatch facility may require access to FRMS, Read -Only CAD Services, and PMDC via their owned and operated Local Area Networks. The City -County demarcation boundaries are outlined in Exhibit B. 1.19 Non -Regional Dispatch Center ("NRDC"): A cooperative dispatch center providing E911 call taking and dispatch services for a municipality. A NRDC is also hosted by the infrastructure, applications, and services of the RPSI. A NRDC supports the overall goals of closest unit response, radio interoperability, and data sharing and utilizes the Regional CAD and County - Wide Radio System. The County will be solely responsible for designating each qualifying dispatch center as a NRDC based upon the dispatch center's participation in the regional system. Upon such written designation by the County, the dispatch center will qualify as a NRDC under this Agreement unless and until the County otherwise designates in writing or the Agreement Is otherwise terminated. 1.20 Peripheral Equipment: The City -owned and maintained items listed in Exhibit C and any other City -provided items. Peripheral equipment includes but is not limited to Ethernet cabling, mouse, keyboard, speakers, printers, etc. 1.21 Project: The integration of a regional public safety intranet comprised of radio and data systems, benefiting public safety agencies within Broward County that choose to participate. 1.22 Project Charter: Outlines the requirements, direction, constraints, and collectively accepted deliverables within a project. In addition, the charter will act -as a guideline for the project manager and project team members to establish scope, schedule, and cost pertaining to the Project. The Project Charter template is further explained and listed in Exhibit E. Upon written confirmation by both parties, the completed Project Charter (including any subsequent updates by the parties) shall be automatically substituted and incorporated herein and shall operate as Exhibit E to this Agreement. 1.23 Project Manager: An employee of the County who is assigned by the Contract Administrator to of the Project -from inception to completion. 1.24 Public Safety Network ("PSN"): A component of the RPSI which provides the communication connectivity and network infrastructure for data portions of the RPSI. 1.25 Regional Dispatch Center ("RDC"): A cooperative and consolidated dispatch center providing E911 call taking and dispatch services for multiple jurisdictions. A RDC is also hosted by the infrastructure, applications, and services of the RPSI. A RDC supports the overall goals of closest unit response, radio interoperability, and data sharing and utilizes the Regional CAD and County -Wide Radio System. The County funds the personnel and operating expenses associated to a regional dispatch center. The County will be solely responsible for designating each qualifying dispatch center as a RDC based upon the dispatch center's participation in the regional system. Upon such written designation by the County, the dispatch center will qualify as a RDC under this Agreement unless and until the County otherwise designates in writing or the Agreement is otherwise terminated. 1.26 Regional Public Safety Intranet ("RPSI"): The overall collection of Equipment — including but not limited to County's Trunked Radio System, Public Safety Network, and Public Safety Applications Page 3 of 99 -- that constitutes the Regional Public Safety Intranet. City -owned equipment interfaces to the County -owned RPSI. 1.27 Service Level Agreements ("SLA"): Defines an expected level of service segregated into various categories: System performance, trouble resolution, operations, and administration. The Service Level Agreements are further explained and listed in Exhibit F. 1.28 SmartZone: A component of the RPSI that interconnects disparate radio systems to provide county -wide coverage for roaming, efficient use of channels, and voice communication interoperability. 1.29 Subscriber Maintenance: Refers to City's responsibility to maintain the City owned user's equipment. Subscriber maintenance is further explained in Exhibit B. 1.30 System Maintenance: Refers to County's responsibility to maintain the regional public safety intranet (RPSI) as described in Exhibit B. 1.31 Trunked Radio System: County's Trunked Radio Communications System, a major portion of which is used by police and fire rescue personnel within Broward County. County currently owns and operates a twenty-eight (28) channel 800 MHz tunked simulcast SmartZone radio system. ARTICLE 2 SCOPE OF WORK 2.1 County and City agree to install the necessary Equipment and Peripheral Equipment and perform their respective required tasks in accordance with the Statement of Work (Exhibit A). 2.2 The work to be done shall be referenced, for convenience, according to the project designations and as further identified and detailed in the Exhibit A Statement of Work. 2.3 County agrees that the Trunked Radio System will meet appropriate coverage, functionality, and availability parameters and accepted industry standard levels of performance as determined by Federal Communications Commission (FCC), Telecommunications Industries Association (TIA), and Association of Public Safety Communication Officials (APCO) standards together with manufacturers' specifications. 2-4-�- ��Coun "-shall-own tY gill -Equi-Pmerit theCounYsuP7pliesto itY..p ursuant"tothis 9reemen :*- 2.5 City shall provide County access to the City's equipment rooms to the extent required for the installation of the County -owned equipment and integration of any applicable City system into the RPSI. City will exercise due care to ensure that the electrical, security, and environmental requirements are maintained for such equipment rooms. 2.6 County agrees that the CAD, AVL, FIRMS, LRMS, Mobility Zone, and Public Safety Network functionalities supplied to City shall also meet appropriate performance levels as defined in Exhibit F. 2.7 The Regional Public Safety Intranet will perform based on the specifications of any given application being run on the system as defined in the Exhibit A (Statement of Work). The RPSI shall allow for exchange of information amongst public safety users. 2.8 City shall be responsible for supplying County with needed uninterruptible power system (UPS) electrical power, electrical wiring, heating ventilating and air conditioning (HVAC), and standby power generation to meet. manufacturer guidelines and operational standards established by County for dispatch center Equipment. Page 4 of 99 l 2.9 City agrees to allow County, with notice to City and monitoring by City personnel, to assist in troubleshooting a City local area network (LAN) which adversely impacts the Regional Public Safety Intranet. City agrees to correct any problems found in an expeditious manner. 2.10 City agrees to comply with the Demarcation Point division of responsibilities for the RPSI as provided in Exhibit B. 2.11 County shall maintain all systems outlined as "County responsibility" in Exhibit B over the life of this Agreement. 2.12 City shall maintain all systems outlined as "City responsibility" in Exhibit B over the life of this Agreement. 2.13 County shall not be responsible for the payment of any taxes, insurance, and utilities for City owned facilities. 2.14 Access to City's facilities for County personnel, or County's subcontractors, consistent with City security practices and procedures, shall be unlimited as to time and day. 2.15 City shall be responsible for any and all maintenance and repairs to the existing City owned facilities and any upgrades to such facilities. City shall maintain the structural and operational integrity of all associated City owned facilities and supporting equipment including but not limited to: batteries, buildings, cable plant, generators, roof, skylights, walls, foundations, sidewalks, floors, windows, ceilings, sprinkler and hot water systems, elevators, heating systems, air conditioning systems, plumbing, electrical and all other structural components. 2.16 Prior to the issuance of the Notice to Proceed from the County's Contract Administrator to the contractor, the Parties shall develop a mutually acceptable Project Plan inclusive of Project Charter (Exhibit E), project schedule, and communication plan set forth, among other things, (i) selected tasks, deliverables, and activities required of -each party, including all dates by which the responsible party must complete such activity, (ii) the milestones and the agreed upon date for completion of each milestone; and (iii) the date for System Acceptance. This development shall constitute a Detailed Design Review. The Project Schedule shall be in the form of a progress chart of suitable scale to appropriately indicate the percentage of work scheduled for completion at any time. Each party represents that it will act in good faith to establish the, Project Schedule within thirty (30) days of a signed contract between the County's Contract Administrator and the _..._......_....____-_�..__.-.contractor-an -that-the-number--of days establistred-will-bereamonaible-as�to each Adt tIVIV. 2.17 Upon City's concurrence with, and County's acceptance of, the Detailed Design Review and . Project Schedule submitted to County, County will provide contractor with a Notice to Proceed. 2.18 Effective with the execution of this Agreement, City shall become a voting' member of the Regional Public Safety Communications Committee ("RPSCC") (or equivalent committee that has the authority to make technical decisions with regard to major upgrades and configuration changes to the RPSI) and other applicable governance boards to the extent approved by'County. 2.19 City shall follow all RPSI Trunked Radio System policies and standard operating procedures in place at the time of this Agreement, a list of which are included .in Exhibit G, as well as those developed in the future and issued to City by County. City agrees to comply with any enforcement actions required by these policies and procedures for misuse or abuse of the RPSI Trunked Radio System. 2.20 County and City shall jointly be responsible for developing desired fleet mapping *and programming of all subscriber units and system parameters necessary to meet the operational requirements. Page 5 of 99 2.21 SmartZone operation shall be limited to public safety users only. 2.22 City acknowledges that the services to be performed under this Agreement, relative to County's responsibilities, shall be performed by County and/or. its contractors and shall be under the sole supervision and direction of County. At City facilities, City may monitor installation work done by the County, its employees, agents, and subcontractors. Likewise, County acknowledges that the services to be performed under this Agreement relative to City's responsibilities shall be performed by City and/or its contractor(s) and shall be under the sole supervision and direction of City. County may monitor installation. work done by the City, its employees, agents, and subcontractors. 2.23 City is responsible for Subscriber Maintenance including repair and sub -fleet additions, moves, and changes to City subscribers as provided in Exhibit B. City may utilize the services of a third party to provide maintenance of City subscribers, or City may contract with County for a fee for a combination of the aforementioned services or for all of the above services. 2.24 County shall reprogram all City subscriber radios and control stations for operation on the County's Trunked . Radio System. 2.25 City is responsible for all removals and installations of its subscriber equipment. 2.26 County agrees that it will not implement any changes/enhancements to the RPSI that could adversely affect the City system subscribers unless directed to do so by federal or state mandates as stated in Section 3.3 of this Agreement.or otherwise agreed to, in writing, between the parties. Prior written notice as defined in Exhibit D shall be made by County to City for proposed changes and their potential effect on City operations. Should City or County desire to perform changes to the facility or the RPSI that may impact the Equipment or services provided by the County, the Change Management Request (CMR) procedures (Exhibit D) will be followed. 2.27 The parties agree that any and all drawings, plans, specifications or other documents or materials will be reviewed by City and County, or its sub -contractors to ensure that they are: (a) consistent with the City and County requirements for the Project; (b) sufficiently fit and proper for the purposes intended; and (c) comply with all applicable laws, statutes, building codes, and City and County guidelines or regulations, which apply to or govern the Project. City's approval, acceptance, use. of or payment for all or any part of County's services under this Agreement or of the Project itself shall in no way alter County's obligations or City's rights. Copies of all items .-______—_ Shall -be provided-tc City--and-County: The-Project--Charter-will--be--used~to-identify-the---- --- requirements and expectations set forth by City and County. 2.28 In the event that County or City believe that any aspect of a Project is not in compliance with approved plans or applicable codes, or that work cannot be completed as designated, County or City shall notify the appropriate other party within the next business day after discovery, in writing or electronically, as to the reason(s) the proposed portion of the work is not in compliance or not feasible to meet the scope of services to be provided in this Agreement. 2.29 City agrees to complete a joint Acceptance Test Plan (Exhibit A, Attachment 2) with County to inspect County's or the contractor's performed work on the System to determine if it meets the- City's operational needs and County's requirements. 2.30 City public safety users shall have equal accessibility to County's RPSI similar to other public safety agency subscribers. 2.31 City agrees to purchase all necessary City subscriber equipment as described in Exhibit B within ninety (90) days of the City providing written notice to County exercising its option to participate in a regional public safety intranet consisting of any one or combination of the following: Trunked Radio System, CAD, ATM, AVL, FRMS, LRMS, or PSN. Page 6 of 99 2.32 City agrees to provide County or County's contractor, for the term of the Agreement, with facility space associated with the on -site maintenance, troubleshooting, and repair of all County Equipment. ARTICLE 3 TERM 3.1 The obligation of the Parties to perform under this Agreement shall commence upon the date of the last party executing this Agreement ("Effective Date"). 3.2 The term of this Agreement shall be for five (5) years from the Effective Date. This Agreement may be renewed every five (5) years with the written approval of both County and City, unless terminated pursuant to Article 4. 3.3 The terms of this Agreement may be amended if a state or federal regulatory agency mandates significant technological modifications of the system requiring a major reconfiguration or upgrade. In such instances, the Parties shall meet to determine an appropriate solution and funding. In the event the parties are unable to reach an , agreement regarding state or federal mandates -for technological modifications and/or funding of said modifications, either party may terminate the Agreement for cause pursuant to Article 4. ARTICLE 4 TERMINATION 4.1 This Agreement may be terminated by the County or City for convenience upon providing written notice to the other party at least 365 days prior to the effective date of such termination. 4.2 The failure of the City to perform its responsibilities as set forth herein for a period of thirty (30) calendar days after written notice by County shall constitute a breach of this Agreement. In the event the City fails to cure the breach within such thirty (30) day period, County may immediately terminate this Agreement upon written notice to the City. 4.3 City recognizes that the Board of County Commissioners, Broward County, Florida is the authority which establishes, allocates or otherwise provides for County's budget year funding. If in any budget year, funding, for any reason, is not provided to cover the Count s responsibilities and obligations under th s Agreement, this Agreement may be terminated by County without penalty upon written notice to the City. ARTICLE 5 COMPENSATION 5.1. Section 318.21(9), Florida Statutes, requires that Twelve dollars and fifty cents ($12.50) from each moving traffic violation must be used by the County to fund the County's participation in an intergovernmental radio communication program approved by the Department of Management Services. City understands such revenue generated within its jurisdiction will be used by the County to help fund the RPSI's operating costs. ARTICLE 6 ADDITIONAL SERVICES 6.1 It is mutually acknowledged that during the term of this Agreement it may be desirable to change the scope or extent of the maintenance services or to have County substitute items of Equipment and/or provide new items of Equipment. The parties also recognize that during the term of this Agreement, additions, changes, or modifications may be necessary or desirable to carry out the intent or purpose of this Agreement. The ' Parties agree that during the term of this Agreement Page 7 of 99 they will negotiate in good faith any requested changes to the scope or extent of the maintenance services or to substitution of items of Equipment and/or provision of new items of Equipment and other services proposed by County. All requested changes to the scope or extent of the maintenance services or to substitution of items of Equipment and/or provision of new items of Equipment, upgrades and other proposed additional services are subject to funding availability. 6.2 Any and all modifications to the terms and conditions of this Agreement must be contained in a written amendment executed by both parties with the same formalities as set forth herein. Should City or County desire to perform changes to the facilities, the RPSI or PSN that may adversely impact the Equipment provided by the County, the Change Management Request (CMR) procedures (Exhibit D) will be followed. ARTICLE 7 FREQUENCY USAGE 7.1 City agrees to authorize County, pursuant to state and federal regulations, to integrate City's 800 MHz frequencies into County's public safety intranet for the purpose of building a regional public safety intranet benefiting public safety agencies within Broward County that choose to participate. 7.2 City agrees to authorize County, pursuant to state and federal regulations, to. integrate City's eligible 700 MHz frequencies into County's public safety intranet for the purpose of building a regional public safety intranet benefiting public safety agencies within Broward County that choose to participate. 7.3 City shall continue to maintain its radio frequency license ownership and, therefore, shall comply with all applicable federal, state and local laws and regulations to maintain such licensure. 7.4 County shall assist -City with filing appropriate documents to facilitate County's usage of the 800 MHz .frequencies, including documents regarding Federal Aviation Administration (FAA) or FCC licensure. 7.5 County shall assist City with ding appropriate documents to facilitate County's usage of the 700 MHz frequencies, including documents regarding Federal Aviation Administration (FAA) and/or FCC licensure. 7.6 County understands and agrees to maintain City radio - -- -- integrated-into-the-County-Trunked-Radio--system(s)— - ------ ARTICLE 8 LIABILITY frequencies (direction and range) 8.1 City and County shall each individually defend any action or proceeding brought against their respective agency pursuant to this Agreement and shall be individually responsible for all of their respective costs, attorneys' fees, expenses and liabilities incurred as a result of any such claims, demands, suits, actions, damages and causes of action, including the investigation or their defense thereof, and from and against any orders, judgments or decrees which may be entered as a result thereof. 8.2 City and County agree that no indemnification or hold harmless agreement shall *be in effect concerning any claims, demands, damages and causes of action which may be brought against either party pursuant to this Agreement. This paragraph does not affect in any way any indemnification or hold harmless obligations of any third party to City or County under any other contract, agreement or obligation. 8.3 City and County. are "state agencies or subdivisions" as defined in Section 768.28, Florida Statutes, and agree to be fully responsible for acts and omissions of its agents or employees to r. Page 8 of 99 w the extent required by law. Nothing herein is intended to serve as a waiver of sovereign immunity by any party to which sovereign immunity is applicable. Nothing herein shall be construed as consent by a state agency or political subdivision of the State of Florida to be sued by third parties in any matter, whether arising out of this Agreement or any other contract. ARTICLE 9 INSURANCE 9.1 The Parties acknowledge that County is self -insured in accordance with the provisions set forth in Section 768.28, Florida Statutes. ARTICLE 10 PERFORMANCE 10.1 Operational Performance Metrics will be provided by County to City on a quarterly basis to collectively evaluate system integrity. The operational performance metrics will be a part of the service level agreement provided by County to City and further explained in Exhibit F. ARTICLE 11 MISCELLANEOUS PROVISIONS 11.1 ASSIGNMENT: County shall perform the services provided for -in this Agreement utilizing County's employees, contractors, and subcontractors. Said services shall be performed exclusively and solely for City which is a party to this Agreement. City and County shall not have the right to assign this Agreement without the express written approval of both parties. 11.2 JOINT PREPARATION: The Parties acknowledge that they have sought and received whatever competent advice and counsel as was necessary for them to form a full and complete understanding of all rights and obligations herein and that the preparation of this Agreement has been their joint effort. The language agreed to expresses their mutual intent and the resulting document shall not, solely as a matter of judicial construction, be construed more severely against one of the parties than the other. 11.3 SEVERABILITY: In the event any portion or provision of this Agreement is found to be unenforceable by any court of competent jurisdiction, that provision or portion shall be deemed severed from this Agreement and the balance of this Agreement shall remain in full force and - - ---_--_-_ _- effect: -- -- - - - ---- - -- - _-------.--------... 11.4 ENTIRE AGREEMENT AND MODIFICATION: This Agreement incorporates, supersedes and includes all prior negotiations, correspondence, conversations, agreements or understandings applicable to the matter contained herein. Specifically, this Agreement supersedes and replaces in its entirety any prior Agreement Providing for Cooperative Participation in a Regional Public Safety Intranet Between City and County for between City and the Broward Sheriffs Office and assigned by Broward Sheriffs Office to the County). It is further agreed that no change, alteration or modification in the terms and conditions contained herein shall be effective unless contained in a written document executed by both parties with the same formality and of equal dignity herewith. 11.5 COMPLIANCE WITH LAWS: Each party shall comply with all federal, state, and local laws, codes, ordinances, rules and regulations in performing its duties, responsibilities and obligations pursuant to this Agreement. 11.6 BINDING EFFECT:- This Agreement shall be binding upon and inure to the benefit of the parties hereto and their respective successors. 11.7 FORCE MAJEURE: Neither party shall be obligated to perform any duty, requirement or Page 9 of 99 A obligation under this Agreement if such performance is prevented by fire, hurricane, earthquake, explosion, wars, sabotage, accident, flood, acts of God, strikes, or other labor disputes, riot or civil commotions, or by reason of any other matter or conditions beyond the control of either party, and which cannot be overcome by reasonable diligence and without unusual expense ("Force Majeure"). 11.8 AUTHORITY: The individuals executing this Agreement on behalf of any entity do hereby represent and warrant that they are, on the date of this Agreement, duly authorized by all necessary and appropriate action to execute this Agreement on behalf of their principal. 11.9 NOTICES: In order for a notice to a party to be effective under this Agreement, notice must be sent via U.S. first-class mail with a contemporaneous copy via e-mail to the addresses listed below, and shall be effective upon mailing. The addresses for notice shall remain as set forth herein unless and until changed in writing in the manner provided in this section: Broward County Director, Office of Communications Technology 115 S. Andrews Avenue, Room 325 Fort Lauderdale, Florida 33301 With a copy to: Broward County Attorneys Office, Government Center 115 S. Andrews Avenue, Room 325 Fort Lauderdale, FL 33301 City of Tamarac (Insert Address Here) 7525 NW- 88th Ave . , Tamarac, FL 33321 With a copy to: City of Tamarac General Counsel -- ------ U*?W Samuel S---Gor-en;-------- (insert Address Here) 3099 E . Commercial Blvd . , Ft . Lauderdale,, FL 33308 11.10 MATERIALITY AND WAIVER OF BREACH: The parties agree that each requirement, duty, and obligation set forth herein is substantial and important to the formation of this Agreement and, therefore, is a material term hereof. Either party's failure to enforce any provision of this Agreement shall not be deemed a waiver of such provision or modification of this Agreement. A waiver of any breach of a provision of this Agreement shall not be deemed a waiver of any subsequent breach and shall not be construed to be a modification of the terms of this Agreement. 11.11 INDEPENDENT CONTRACTORS: The parties agree that each party to this Agreement is an independent contractor. In providing such services, neither of the Parties, nor their respective agents shall act as officers, employees, or agents of the other party. This Agreement shall not constitute or make the -parties a partnership or joint venture. 11.12 RECORDING: This Agreement shall be recorded Cooperation Act of 1969. in accordance with the Florida Interlocal Page 10 of 99 obligation under this Agreement if such performance is prevented by fire, hurricane, earthquake, explosion, wars, sabotage, accident, flood, acts of God, strikes, or other labor disputes, riot or civil commotions, or by reason of any other matter or conditions beyond the control of either party, and which cannot be overcome by reasonable diligence and without unusual expense ("Force Majeure"). 11.8 AUTHORITY: The individuals executing this Agreement on behalf of any entity do hereby represent and warrant that they are, on the date of this Agreement, duly authorized by all necessary and appropriate action to execute this Agreement on behalf of their principal. 11.9 NOTICES: In order for a notice to a party to be effective under this Agreement, notice must be sent via U.S. first-class mail with a contemporaneous copy via e-mail to the addresses listed below, and shall be effective upon mailing. The addresses for notice shall remain as set forth herein unless and until changed in writing in the manner provided in this section: Broward County Director, Office of Communications Technology 115 S. Andrews Avenue, Room 325 Fort Lauderdale, Florida 33301 With a copy to: Broward County Attorneys Office, Government Center 115 S. Andrews Avenue, Room 325 Fort Lauderdale, FL 33301 City of Tamarac (Insert Address Here) 7525 NW- 88th Ave . , Tamarac, FL 33321 With a copy to: City of Tamarac General Counsel -- ------ U*?W Samuel S---Gor-en;-------- (insert Address Here) 3099 E . Commercial Blvd . , Ft . Lauderdale,, FL 33308 11.10 MATERIALITY AND WAIVER OF BREACH: The parties agree that each requirement, duty, and obligation set forth herein is substantial and important to the formation of this Agreement and, therefore, is a material term hereof. Either party's failure to enforce any provision of this Agreement shall not be deemed a waiver of such provision or modification of this Agreement. A waiver of any breach of a provision of this Agreement shall not be deemed a waiver of any subsequent breach and shall not be construed to be a modification of the terms of this Agreement. 11.11 INDEPENDENT CONTRACTORS: The parties agree that each party to this Agreement is an independent contractor. In providing such services, neither of the Parties, nor their respective agents shall act as officers, employees, or agents of the other party. This Agreement shall not constitute or make the -parties a partnership or joint venture. 11.12 RECORDING: This Agreement shall be recorded Cooperation Act of 1969. in accordance with the Florida Interlocal Page 10 of 99 11.13 PRIORITY OF PROVISIONS: If there is a conflict or inconsistency between any term, statement, requirement, or provision of any exhibit attached hereto, any document incorporated into this Agreement by reference and a term, statement, requirement, or provision of this Agreement, the term, statement, requirement, or provision contained in Articles 1 through 11 of this Agreement shall prevail and be given effect. Notwithstanding any other provision herein, if City and County execute a Lease Agreement for a 911 Emergency Dispatch Center ("Lease Agreement"), then, solely for the term of the Lease Agreement, to the extent any terms of the Lease Agreement directly conflict with any provision(s) herein, the terms of the Lease Agreement shall supersede and control as to any conflicting provision herein. 11.14 MULTIPLE ORIGINALS: This Agreement may be fully executed in five (5) copies by all parties, each of which, bearing original signatures, shall be the force and effect of an original document. 11.15 NON-DISCRIMINATION: The parties shall not discriminate against any employee or participant in the performance of the duties, responsibilities and obligations under this Agreement because of race, age, religion, color, gender, disability, marital status, sexual orientation or national origin. 11.16 RECORDS: Each party shall maintain its own respective records and documents associated with this Agreement in accordance -with the records retention requirements applicable to public records. Each party shall be responsible for compliance with any public documents requests served upon it pursuant to Section 119.07, Florida Statutes, and any resultant award of attorney's fees for noncompliance with that law. 11.17 CHOICE OF LAW, _WAIVER OF JURY TRIAL: Any controversies or legal problems arising out of this transaction and any action involving the enforcement or interpretation of any rights hereunder shall be submitted exclusively to the jurisdiction of the federal or state courts of Broward County, Florida, and shall be governed by the laws of the state of Florida and any applicable federal laws, codes or regulations. To encourage prompt and equitable resolution of any litigation that may arise hereunder, each party hereby waives any rights it may have to a trial by jury in any such litigation. 11.18 OWNERSHIP OF EQUIPMENT: County retains ownership of all Equipment that the County provides to the City pursuant to the terms and conditions of. this Agreement. In the event this Agreement is terminated by either party, the County shall remove and/or recover all equipment within ninety (90) days of the effective date of termination. ----1-1-19 ATTACHMENTS -AND -REFERENCES: The following-name-d exhibits are made an integral part of this Agreement: Exhibit A: Statement of Work Attachment 1: System Description Attachment 2: Acceptance Test Plan Exhibit B: System. Demarcation Points Attachment 1 A: Regional Dispatch Center Attachment 1 B: Non -Regional Dispatch Center Attachment 1 C: Non -Dispatch Facility Attachment 1 D: Mobile Data Law Enforcement Attachment 1 E: Mobile Data Fire Rescue Frontline Vehicles Attachment 2: Demarcation Drawings Exhibit C: Equipment List Exhibit D. Change Management Request Exhibit E: Project Charter Page 11 of 99 Exhibit F: Service Level Agreements Attachment 1: Terms and Conditions Attachment 2: Trouble Ticket Workflow Exhibit G: RPSI Trunked Radio System SOP's 11.20 THIRD PARTY BENEFICIARIES: This Agreement is not intended to benefit any third party nor shall it create a contractual relationship with any third party. The remainder of this page is intentionally blank. 0 Page 12 of 99 00 REGIONAL INTERLOCAL AGREEMENT BETWEEN BROWARD COUNTY AND THE CITY OF TAMARAC PROVIDING FOR COOPERATIVE PARTICIPATION IN A REGIONAL PUBLIC SAFETY INTRANET WITNESS: (Signature) SUSAN SEFERM (Print Name of Witness) il (Print Name of Witness) Insurance requirements approved by Broward County Risk Management Division Risk M ine A. Binns Pri ireisur'art gkWeSaj Contracts Manager BROWARD COUNTY (Date) BROWND COUNTY, by d through its Bo r of C my Co ssioners r By Co my Administrator day of er , 20 Approved as to form by Joni Armstrong Coffey Broward County Attorney Governmental Center, Suite 423 115 South Andrews Avenue Fort Lauderdale, Florida 33301 Telephone: (954) 357-7600 gyI-.;w- (Sigr)ld)JU`� Assistant County Attorney (Date) rj Page 13 of 99 REGIONAL INTERLOCAL AGREEMENT BETWEEN BROWARD COUNTY AND THE CITY OF TAMARAC PROVIDING FOR COOPERATIVE PARTICIPATION IN A REGIONAL PUBLIC SAFETY INTRANET ATTEST: I $!IATY TR� L, CMC CITY OF TAMARAC 0 CITY OF TAMAC By. MAYO BETH TALABISCO Print Name �' -"-day of , 201S. Approved as to form and legal sufficAncy suojea}k execution by the parties: Attorney 005S /P/$ /*I Page 14 of 99 Exhibit A - Statement of Work lu Page 15 of 99 c , Exhibit A - ATTACHMENT 1 SYSTEM DESCRIPTION To be provided at Detailed Design Review Phase of the project Exhibit A- ATTACHMENT 2 Acceptance Test _Plan To be provided at Detailed Design Review Phase of the project Page 16 of 99 ft I EXHIBIT B — ATTACHMENT 1A Re tonal Public Safety Intranet Demarcation Points Regional Dispatch Center RPSI Portion Demarc COUNTY CITY Responsibility Responsibility Trunked Radio GOLD ELITE Infrastructure and software All mobile and portable radio System CONSOLE(S) up to and including the subscriber units including any COUNTY -owned Gold software operating on the RPSI Elite/P25 IP based Radio Trunked Radio System; and any Console(s) located in the advanced features and other Regional Dispatch Center. monitoring equipment, as desired. Hosted Master Site COUNTY OWNED Maintain COUNTY owned Maintain CITY owned radio (HMS) SMARTX radio equipment in equipment in accordance to CONVERTERS accordance to COUNTY CITY HMS User Agreement. HMS User Agreement. The The HMS cost is the HMS cost is the responsibility of the radio sub - responsibility of the radio system owner. sub -system owner. Radio Talkgroup RECORDER AT Logging recorder CITY has no responsibility for Recording REGIONAL equipment located at the talkgroup recording in a regional DISPATCH CENTER Regional Dispatch Center. dispatch center Any software playback at the Regional Dispatch Center. Fire Station Alerting CITY FSA Fire station alerting Fire station alerting equipment (FSA) EQUIPMENT equipment located in the located at the CITY fire stations. -- ��- LOCATED AT THE --FIRE STATION Regional Dispatch Center. -COUNTY-Will-be CITY is responsible for any communication medium other responsible for COUNTY than COUNTY RF (ie: leased RF connectivity from the lines). CITY is responsible for Regional Dispatch Center the Fire Station Radio to the CITY Fire Station. Frequency (RF) antenna to the Zetron Model 6 to the AudioNideo (AV) equipment including the Public Announcement (PA) system and speakers. Any CITY LAN requirements. CAD System CITY LAN Infrastructure and software All extended CITY LAN up to and including the equipment along with software, CAD server, Regional client licenses, peripheral dispatch console equipment to provide workstations, Regional communications to City "read Dispatch CAD client only" CAD workstations and all licenses, and the needed existing interfaces. (Future communications via the interfaces to the COUNTY - Page 17 of 99 RPSI Portion Demarc COUNTY CITY Responsibility Responsibility RPSI. supplied systems do not apply.) AVL System CITY LAN Infrastructure up to and All extended CITY LAN including the AVL server, equipment along with software, regional client desktop client licenses, peripheral software licenses, and the equipment to provide needed communications communications to City "read via the RPSI. only" .CAD workstations and all existing interfaces. (Future interfaces to the COUNTY supplied systems do not apply.) Advanced Tactical CITY LAN Infrastructure up to and All extended CITY LAN Mapping including the advanced equipment along with software, tactical mapping servers, client licenses, peripheral regional standard desktop equipment to provide client software licenses, communications to City "read and the needed only" CAD workstations and all communications via the existing interfaces. (Future RPSI. interfaces to the COUNTY - supplied systems do not apply.) Fire Records CITY LAN Infrastructure up to and Desktop hardware and all LANs Management including the Fire Records connected to the FRMS; non - System Management servers and standard or customized software standard software site and desired by CITY. client licensing for Fire Records. Law Records CITY LAN Infrastructure up to and Desktop hardware and all LANs Management _ _ _ r including the Law Records Management servers. —� connected to the LRIVIS; non - standard or customized software _ System desired, by CITY and standard software site and client licensing for Law Records. Page 18 of 99 EXHIBIT B -ATTACHMENT I Re Tonal Public Safety Intranet Demarcation Points Non -Regional Dispatch Center RPSI Portion Demarc COUNTY CITY Responsibility Responsibility Trunked Radio Gold Elite Console(s) Infrastructure and software All mobile and portable radio System up to and including the subscriber units including any COUNTY -owned Gold software operating on the RPSI Elite/P251P based Radio Trunked Radio System; and any • Console(s) located in the advanced features and other Regional Dispatch Center. monitoring equipment, as desired. Hosted Master Site COUNTY OWNED Maintain COUNTY owned Maintain CITY owned radio (HMS) SMARTX radio equipment in equipment in accordance to CONVERTERS accordance to COUNTY CITY HMS User Agreement. Or HMS User Agreement. The HMS cost is the CITY OWNED The HMS cost is the responsibility of the radio sub- SMARTX responsibility of the radio system owner. CONVERTERS sub -system owner. Radio Talkgroup N/A COUNTY is not responsible Logging recorder equipment Recording for radio talkgroup located at the Non -Regional recording at a Non- Dispatch Center. Any software Regional Dispatch Center. playback at the Non -Regional Dispatch .Center. Fire Station A#ertin g N/A COUNTY 'is not responsible All fire station alerting related (FSA} for fire station alerting at a equipment and communication Non -Regional Dispatch 9 P medium at the Non -Regional 9 -�- - - - Center. -Dispatch Cen er and ache CITY fire stations. CAD System CITY LAN Infrastructure and software All extended CITY LAN up to and including the equipment along with software, CAD server, Regional client licenses, peripheral dispatch console equipment to provide workstations, Regional communications to City "read Dispatch CAD client only" CAD workstations and all licenses, and the needed existing interfaces. (Future communications via the interfaces to the COUNTY- RPSI. supplied systems do not apply.) AVL System CITY LAN Infrastructure up to and All extended CITY LAN including the AVL server, equipment along with software, regional client desktop client licenses, peripheral software licenses, and the equipment to provide needed communications communications to City "read Page 19 of 99 RPSI Portion Demarc COUNTY CITY Responsibility Responsibility via the RPSI. only" CAD workstations and all existing interfaces. (Future interfaces to the COUNTY - supplied systems do not apply.) Advanced Tactical CITY LAN Infrastructure up to and All extended CITY LAN Mapping including the advanced equipment along with software, tactical mapping servers, client licenses, peripheral regional standard desktop equipment to provide client software licenses, communications to City "read and the needed only" CAD workstations and all communications via the existing interfaces. (Future RPSI. interfaces to the COUNTY - supplied systems do not apply.) Fire Records CITY LAN Infrastructure up to and Desktop hardware and all LANs Management including the Fire Records connected to the FRMSI non - System Management servers and standard or customized software standard software site and. desired by CITY. client licensing for Fire Records. Law Records CITY LAN Infrastructure up to and Desktop hardware and all LANs Management including the Law Records connected to the LRMS; non; - System Management servers. standard or customized software desired by CITY and standard software site and client licensing for Law Records. Page 20 of 99 EXHIBIT B -- ATTACHMENT 1C Regional Public Safety Intranet Demarcation Points -Non-Dis atch Faciil RPSI Portion Demarc COUNTY CITY ff Responsibility Responsibility CAD System CITY LAN All extended CITY LAN. Infrastructure up to and equipment along with software, including physical network client licenses, desktop connectivity from the RPSI workstations, peripheral to -a single pre -defined equipment to provide CITY location. communications to City "read only' CAD workstations and all existing interfaces. (Future interfaces to the COUNTY - supplied systems do not apply.) Advanced Tactical CITY LAN Infrastructure up to and All extended CITY LAN Mapping including physical network equipment along with software, connectivity from the RPSI client licenses, desktop to a single pre -defined workstations, peripheral CITY location. equipment to provide communications to City ATM workstations and all existing interfaces. (Future interfaces to the COUNTY -supplied systems do not apply.) Fire Records CITY LAN Infrastructure up to and Desktop hardware and all LANs Management including physical network connected to the FRMS; non- --System- -- -- -- -- - connectivity-from-the-RPSI -standard-or customized software to a single pre -defined desired by CITY. CITY location. FRMS standard site and client desktop software licenses will be provided from COUNTY to CITY. Law Records CITY LAN Infrastructure up to and Desktop hardware and all LANs Management including physical network connected to the LRMS; non - System connectivity from the RPSI standard or customized software to a single pre -defined desired by CITY and standard CITY location. software site and client licensing for Law Records. Page 21 of 99 EXHIBIT B -- ATTACHMENT 1 D Re Tonal Public Safety Intranet Demarcation Points Mobile Data — Law Enforcement RPSI Portion Demarc COUNTY CITY Responsibility Responsibility Trunked Radio Gold Elite Console(s) Infrastructure up to the All mobile and portable radio System COUNTY -owned Gold subscriber units including_ any Elite/P25 IP Console(s) software required to operate located in the Regional on the RPSI Trunked Radio and/or Non -Regional System; and any advanced Dispatch Center. features and other monitoring equipment, as desired. CADS tern � CITY MDT Infrastructure up to and including the CAD server All extended LAN equipment and the needed along with software, client communications via the licenses, peripheral equipment RPSI. to provide communications to City CAD M DTs and all existing interfaces. (Future interfaces to the COUNTY - supplied systems do not apply) AVL System COUNTY's Infrastructure up to and All vehicle -related equipment Infrastructure including the AVL server; and any remote monitoring and the needed equipment and software communications via the RPSI. All vehicle Equipment Law Record _ !COUNTY Infrastructure up to and Management System infrastructure including the Law Records including laptop, modem, Management servers. cabling, associated mounting hardware, antenna — and any monitoring Equipment and standard software site and client licensing for Law Records. Non-standard or customized software is also the responsibility of the CITY. Page 22 of 99 EXHIBIT B - ATTACHMENT 1E Re ional Public Safebt Intranet Demarcation Points Mobile Data - Fire Rescue Frontline Vehicles RPSI Portion Demarc COUNTY CITY Responsibility Responsibility Trunked Radio Gold Elite Console(s) Infrastructure up to the All mobile and portable System COUNTY -owned Gold radio subscriber units Elite/P25 IP Console(s) including any software located in the Regional required to operate on and/or Non -Regional the RPSI Trunked Radio Dispatch Center. System; and any advanced features and other monitoring equipment, as desired. CAD System CITY LAN Infrastructure and software All vehicle related up to and including the peripheral equipment CAD server, MDT and an monitorin y 9 hardware, MDT regional � Non- CAD client software Regional Regional or customized licenses, and the needed software desired by communications via the CITY. (Future interfaces RPSI. to the COUNTY - supplied systems do not apply.) AVL System Frontline Vehicle Infrastructure up to and All vehicle -related including the AVL server, peripheral equipment -and -GPS-devices-Iodated-in- -and-any-remote - ------ -------- - Fire Rescue frontline monitoring equipment vehicles. and software. Mobile Data Frontline Vehicle COUNTY will assume All vehicle related Terminals capital and lifecycle, peripheral equipment procurement of MDT's and and any monitoring associated regional Equipment. CITY standard software for Fire responsible for wireless Rescue frontline vehicles. modems and recurring operating costs. Non - regional or customized software desired by CITY. Fire Record COUNTY Acquisition of FRMS Page 23 of 99 0 RPSI Portion Demarc COUNTY Responsibility CITY Responsibility Management infrastructure COUNTY infrastructure up standard site and client System to and including the FRMS mobile software licenses Server and the needed . will be the responsibility communication interfaces of CITY. All vehicle via the RPSI, related peripheral equipment and any monitoring Equipment. Non -regional or customized software desired by CITY. (Future interfaces to the COUNTY -supplied systems do not apply.) 11 Page 24 of 99 EXHIBIT B -- ATTACHMENT 2 Drawin s Page 25 of 99 No Text 0 is • A. - AR', aQ 0 No Text No Text m No Text EXHIBIT "C" Equipment List Model numbers are provided for reference only in this proposal and are subject to change. Page 34 of 99 Exhibit D Change Management Request Procedure Introduction ' This document defines the Chan a Mana ement Request CMR process for any 6nd-users. Pcom p onerit(s)' that make upthe Regional Public Safety Intranet providing delivery of services to The CMR process will be used to specify the times and conditions when designated tasks can be performed as maintenance on all software and equipment affiliated with the Regional Public Safety Intranet including but not limited to the Public Safety Network (PSN), trunk6d Radio System, Computer Aided Dispatch (CAD) System, LRMS, FRMS, PMDC, UDT/DSS, E-911, etc. Objective The objective of the CMR process is to implement maintenance and expansion guidelines that will assure system reliability; minimize the impact on end -users and prevent unintended outage conditions. Definition The CMR- process will be an ongoing activity involved with the scheduling, communication and coordination of maintenance and construction activities impacting the RPSI. This process includes a- Request, Review and Approval process. All change and maintenance activities are performed during predetermined and mutually acceptable Maintenance Windows. Sc�opwe The CMR process should be followed for any installation, equipment and software maintenance activity or any construction activity which either directly or indirectly impacts the Regional Public Safety Intranet. CMR Process Requirements All scheduled change and maintenance activities will require completion of an electronic CMR form and must conform to the following criteria: • All work requests that impact directly or indirectly the end -users of Public Safety Mission Critical applications must be thoroughly documented in the CMR forms and sent as an e- mail attachment to: octchangemanagemenl@bro,ward.og. + County's Office of Communication Technology. (OCT) will review all requests and obtain consensus from Operations and from all impacted end -users on, scheduling the Maintenance Window for the request. • Activities will be scheduled and performed only during predefined or mutually acceptable Maintenance Windows. • The Requestor submitting the Method of Procedure (MOP) form must identify the scope of the associated outage and a best estimate of the duration of the activities involved in the Page 35 of 99 project. Stop times must take into account the time needed to restore the system to an operational state. • Following County OCT approval of the submitted Method of Procedure (MOP), a project coordination meeting involving representatives of all involved or impacted parties will be scheduled by the assigned OCT Program Manager prior to the start of the scheduled work. MOP Requirements • The MOP must clearly state the objective(s) of the work to be performed; the parties performing the work; the parties impacted by the work and the steps to be completed by each party. • A Maintenance Window identifying a clear Start and Stop time and.a work flowschedule must be developed and included as part of the MOP. • The scheduled work must follow the predetermined schedules identified in the MOP, and, as previously noted, stop times must take into account the time needed to restore the system to an operational state. • The MOP must clearly. identify the Program Managers responsible for coordination of the activity -and provide telephone numbers and any other, relevant contact information. • The MOP must include an escalation list with notification time frames should unforeseen problems occur that would result in an outage extending beyond the scheduled Maintenance Window. • The' MOP must include a fallback plan should the original plan not work. Emergency Maintenance Emergencies by their nature are not a part of the CIVIR process, but can seriously impact end- -- user-s-and-any-scheduled-maintenance-activities. In the event of an emergency outage, both the affected erid-user and first responder must notify the designated on -call person for the Office of Communications Technology (OCT). An on -call list will be provided to each. 911/Dispatch. Center Duty Officer and Manager. The OCT contact will be responsible for the following actions: • Identifying and assigning resources to work the emergency. • Acting as a liaison between the maintenance provider and the 911/Dispatch Center Duty Officer and Manager for the duration of the outage or service degradation. • Documenting response times and actions taken, followed by generating an after -action report. The maintenance provider(s) responding to an outage or service affecting emergency must take the following measures following notification: Page 36 of 99 I. I • Upon notification, use remote access to diagnose andrepair the problem or arrive on site within the contracted time frames of the responder's maintenance agreement. • Assess the nature and scope of the problem. • Notify the County OCT on -call person .of all actions to be taken and provide the best possible estimate of the duration of the outage or service degradation. • Notify the County OCT on -call person of any break in maintenance activity prior to completion of the repair for any reason. • Provide periodic updates for extended outages. • Document each step of the repair/troubleshooting process as it is performed. • Within 24 hours of completion of a repair, provide a written summary of the problem and the measures taken to repair the problem and (if relevant) prevent similar future outages. • County OCT managers will review the submitted documentation and on a case by case basis schedule a debriefing session to review the steps taken to resolve the problem and suggest changes or improvements for responding to future unscheduled outages. Maintenance Windows • The standard weekday Maintenance Window for Public. Safety Communications Operations is 12:01 AM --- 06:00 AM Sunday through Thursday or as otherwise specified by the Operations managers. • The standard weekend Maintenance Window for Public Safety Communications Operations is 5:01 AM — 02:00 PM Saturday and Sunday or as otherwise specified by the Operations managers. • A CMR must include sufficient time to perform a back -out of the change within Ahe Window timeframe and restore systems to their normal operational state. • A CMR that requires work to. be performed outside the standard Maintenance Windows must include justification for performing the work during a non-standard window and be approved by Cou nty's OCT. Page 37 of 99 Process Work Fl4W Requestor OCT ! t Y®s f ( ! Page 38 of 99 FYI Non - Service Affecting Scheduled Scheduled Scheduled Emergency Prep work activi which has low risk to end -users of Public Safety Mission Critical analicatlons. Potential Any activity that may -Service impact end -user access Affecting to Public Safety Mission Critical Service Includes any activity Affecting which will result in the loss or degradation of accessibility to end - users of one or more Public Safety Mission Critical applications. Outage Any work which will Required necessitate a total outage of one or more of the Public Safety Mission Critical applications or the Public Safety Wide Area Network. or any extremely high risk activity which may inadvertently cause an butacie. Service Affecting or Outage Required The. unscheduled outage of one or more Public Safety Mission Critical applications or the Public Safety Wide Area Network. Minimum 2 da s Minimum 5 da s Minimum 10 days Minimum 1_0 days None No I FYI as needed. Yes Notify all End - Users and Support Management Yes Obtain written or e-mail approval from Management. Provide Written Notification to all affected End - Users. Obtain Written Approval of all affected End - Users. Yes Obtain written or e-mail approval from Management. Provide Written Notification -to -all affected End - Users. Obtain Written Approval of all affected End - No Requires immediate manacement and End -User notification and a debriefing meeting once the problem has been resolved. Page 39 of 99 6. End -User Notification Not less than ten (10) business days prior to an approved CIVIR project affecting the Regional Public Safety Intranet, the County OCT project manager must notify all end -user management by e-mail of the pending activity with all CIVIR and MOP documentation attached. The e-mail should summarize the attached documentation but must include: • A list of all affected end -users. • A generic statement of nature of upgrade or maintenance procedure and the operational need to make the change. • The* Maintenance Window, date and time the work will be performed including the projected end time. • A generic impact statement that identifies the nature of the work being performed; the impact of the work.on the end -user while the work is performed and the effect of the work on the restored system or application. Telephone numbers of project managers and key staff involved in the activity. Approval Authority Any and all activities being performed must be supported by an approved CIVIR document. Page 40 of 99 0 . Broward County Office of Communications Technology (OCT) Change Reguest ,Form Note: Complete and submit to the Broward County Office of Communications 'Technology at OCTChangeMana,ement@broward.org. All Change Requests submitted prior to Wednesday are reviewed during the Thursday morning conference calls and either approved or returned for modifications. Please allow a minimum of ten (10) business days from the date of approval for your Maintenance Window to be scheduled. Any work performed on the Public Safety Communications Network, its supporting infrastructure, or the application servers must be documented and approved in a CMR. Today's Date and Time: Requestor_ Name: Requeestor Company Name or Agency: Requestor E-Mail; Requestor Phone Number: Office: Mobile: Briefly describe the 'Work to Be Performed: Identify End -Users & sites impacted by the work to be performed: Page 41 of 99 What is the expected and desired end. result of the Work to be Performed? Identify any loss or degradation of functionality and the impact on end -users - during the Maintenance Window: Name & Contact Number: Identify your On -Site Contact during the scheduled Maintenance Window: Start Date & Time: Requested Maintenance Window for Work Stow Date &-Time: -to-be Performed: Start Date & Time: Approved Maintenance Window for Work to be Performed: Stop Date & Time: r Maintenance Window Date: Approved By: Page 42 of 99 • Assigned MOP Tracking Number: Method of Procedure — for Primary Contractor or Service Provider Note: An MOP must be completed for each Contractor or Service Provider working on a specific project. Use. electronic attachments as needed. Company or Agency Name: Project Manager Name: Project Manager Office Phone Number: Project Manager Mobile Phone Number: Project Manager E-Mail: Detailed Project Description Specify each step in the MOP Work Process. Attach additional pages or any supporting documents as. needed: Page 43 of 99 i Describe back -out and restoration plans if stated project goals are not achieved within the allotted Maintenance Window: OCT to complete Items 1 through 10 BeloW: 1 OCT Contact.for Project: () 1 (2) Name: (3) Mobile Phone Number: (4) E-Mail: (6) FYI - Non -Service Affecting: ❑ _ _7_ _—Sche () _P duled�otential�ervice Affecting:_. (5) MOP Type. (g) Scheduled -- Service Affecting: . (9) Scheduled -- Outage Required: ❑ (1 o) Emergency: El Reviewer Comments: .Method of Procedure Approved By: Date Approved Page 44 of 99 Exhibit E Project Charter PROJECT CHARTER [Note: All fields in blue text must be filled in.] .�:%if�r, i<L,�'•'2i 1t"ra Y :fS tdi .:':!):' 3.4w ^'I 1 •,t✓'^"' .>li'Y,Cht• rk..' ,:. ? ..E•,• c:'dS 6 •'0>.. ': 1. :.w . 4' :'! . fi, ,' . .,.,, .. w:...v ,..i«} . ►_rs. sry i •. ?.:,:.'tt�. i.. :� 4..,Ae. 'ffi.•;2.. :"ci. ..1 e�' yt{,wgFP �vLi:�i. .'it., i.. >> •.s . li:l li�Ws.` f.. C �li�> . .�;l.7��w:}.a• yt •3F>' N, t`n! y... , ::1":.:,«>> 9 C>": .�/1•.• a',}'' I�r - �.-'�, 7 Si���::'• .'• '«l.� rf �i+i }I�f •',,l. .MLF... �.Y ;.r... '••�''�!i'2f AtS , s> t iG '<>;i:'2..:vv :!';.•�•ltlf �'� y. :.,. i..... ... �,, + e'` ' s. > b:�,p <;i.. 3.ki .v = ,>r. y ? - .•',, �.••i;re-: .;i •.:vr t:i:,;: '�.-r'.hTs.r.::::: .-4�+...r.....jj :•�'!! lk ..'�,,,..d t%�' '.,. �c :i,•>••+.:,.:-'ti G.1;.: '�,ij �1H3:- ,y r3,». ,):,. <4:L- ,.:.£', �., + t, .. .i>Yi'✓3.r, {;�. a� "•x. > `ex s , t,I^ tt 'i. ., �; . �:•''::�` it.. ,tr � .� � - '•, i :t : �� rr r'?r�>' �•` • t' � t,.•,y`h'j•.. t'cy>. i°fr ,_ ,<<) iy a i. i 2 s <,.: , . }. i••Z: ; ; .: •> } :•�,. t"�,rL • r 3(. �.;. r. n H< • ;'i'rz '�:�,c C .t %." } i r i Yb •rS . .i`/ I e r4Y�'CrL''iA+ yf , R. ,t �' .. .. •+:.' :T .. '2' .>i.e` ,Jr.:T+ :.!/i., ... V o: z'�i•^4yi�i, w3'�'. "• ',..[r�[••:'N'1�.F:•, >! ,, .1 '(; iYBe, '' { .: .,,,,t AS i{ `.i�t, ... ,. .. !' N:,1n4 `i.' 1 �. r.l.itI�r i.�1 !'xl�llr'i..!• ., i, tl ly l...ik:� t.y YSC .5. S' %h'i' �t^-'.1.. y f.i•w .'-'l,':'' ,.i'.. '% 2k,(:• 1"`' .,E+:¢1 >>: a!'s..,.. :.'.'a>- r<!:�° Q.'.;,: ,,r .•2�3.,; •'sthe 3 •::>i� .2 t�5.2.t..vl')� •.ti,.f .,s. L',,tfi�•�• '`��'�4;�:i `xf�`=., i•,r��.'i: �r...-. a t. . .r.'t,t.'� . . .(i !;t : , tC.l.' ,• '•i,lt S;�'pt... ::! 's ? p..`. ..e. �,' Rs -',f , 5 :,', Sr• e.. t' v'!>u.,l: vs .' ttjYe�.,.r .. > w .�: .�..1 ..;.. -hl..� ..y:lr` IE:i'•..:'fii •.:i P:E:i:: i; `' !s.'t:...i ..� s. pi:�'!�.,'.:•3. 17. ..An�i•. :. i, y �j t 6i'. {i •Y• A ✓T.: .1•!. 2.. i^-..>.. ff . i.�. t v.ia c7F .:7 >;•.�(1)'S _! ..!•••>. t ij..r :::. <::.>,. .. qt .- .l.. :'2_ `3.. %2>. i �s,. ?tti�.. ..►., s ::E 't`� :�a •.. _ , �{'C.r•.f'. ,.7. �: # "!,a.�i'"•<}•�Yj�i., tlx:< ,•A 'iJ]� .Y •( ,H K. H'A. -.y� �O Y.f '' :), •,(': ".�''4< :!Yl'} :;:.f�i;'s �r: r: :, :+:,i• �, '�2: •;;., •,g;},�'itu..?.n','i .,tY, P f•.+k�l .: i °'�• . t � x= _.ft/ 1 ; �,'f. f 1yt . i .. ��� y � � !� .:• ro`jQ��1 ` � r ��i � �♦. r�. hf2e � :a t.., ,.,,��';;:.._• ., .�. t, ri .., �:.>w.. • � ,:w� �g( t � .>.y�i� • .,, , f,.• • � ,. � ::: ���.: �,..,;..�� .::+:.. ..� . �i r��.�. J . •. ,: s T n ..r, ��i� . �.. ..3.. .q++Y t t> s.,. .(t <- 4 `2L'k�.,.:� . {•L �a,,: .., L. �; t,1tt1� sf' : 1 ' ,ryq sti , ..�k�„ .. yr, .{i� 2.. sI,V . �. .•P.. ry>.�..t3 •:;^li,l1•. ,t.tt ;:�r1.:':t.`. :' •2f�✓ ,. ��-: .. `a'. •YY i>.t.,,.��,ss,�.�•t:s., � ~'�1�i. ... •. •%<,-.:.:: -:. sb _ yer.f�%:'..,. J,: V.!!r: r•? ;f2r.9'$Y•4 +•�xi 'i;'. }•�..->'R.?.!">,r,q:jV1.•% i;•.. t �„!_ .,2.w+�:'P ,e. .: :ci .::3 .: ...e.l,%. .,,t`•S•w..M .. nt, >...r•. .. r.v ..i E.••..2 •• ;• � f�i, i,".✓ .:sii'•+a ��'�. „?''-. >,..«.."_ .,.:.iir...-..d•:i .::+:.:f:::. . st. .>. �.:xp':.>,.n • , �' <I Ctr i � ,,, u M i•'i�;w' ) I. �, ni!;-. ?:: i.• ':,$ •iiN^ v:•:. ..: j..,r[.• ..:..:. vn�< 4,.. >,tiiii?r r''.''isd- A{' :. ° >, ?._.f.. .;,ei,;?,f..e.•.iy: J.�r:`•-•... <..`:..•2•. 2s.1,,. ;:�.4: .,. �. t� •-•'>igEs l:i.b t�E°.EC <�:iLiti.,.. 4Q( ,: st. s. ......>� ;;.�, ��: a �•'�'-:�;'..,,.x...°.-..-s?•;"�t?'c e''t.'s w..'.•1 •. ',;1 } ° "yes .et y .^•7;�. •..0 >,l. "4.h r•!2�f 2.....:'c.w 3yyn .. �t .. trz'.r., .� t 31:'j ,i ,>.> .:1,'!,%,�tS;i ;''}3�1•j i�; i.' ..? :f... Mt >..-.jx ;te.p. s.r... .r 1. {'' • S t r +.::t f. 3 _S%.>. ' -ri: Qsii. '•:i•[ i+ � �Y tv,>. 5 �' ' x,.' w.s ' ..;i .. 7 r i :;'si• r �. tu+ l !t�• s• «. i..f . .t : e a t. : - s P .s � . • � 1.:. r ;�•L'' •e•t• 2 t �:'+ d$i�`' .; ;!5., f.a.]Q�•� ''17 �Qo iG i+ttl i `:�`�iQ.�ia , °�iy?7� �� 1 � Ks. � � S �' �{ 3 •,y v :. ,y ...... .... F� fQ:y r ;y. {.i:�yy'��yy]i.": E -s � °C. �.,..,�..�.....£ �.�A/ >� S �-'4, - y>[[ �,�}!, :lLwil•Ct�? l:$ VE ? re . !�:. %�` ::...R,i t..'r'.. 2�; 0..�?`M is 4.it .Y',. L�'r.•`;"!.'1)�: �'.:: 1.'l; ry>:':: t.A <,'S t:�.,• 4:t-Sh'i��1�1�..... A; �,>ts s � -•"f..t q{. .:+t Y•i. .. I. P':t��' .('.. •.��:t '• x ! it t w i� {f ', s,.11 d:?'i.'i ? ' dAF-7�. : .:.:>s,� ""vM; I w' 1' y- p >..s.. ,r''• ,sx1 i.�,,. ,' 1. ,. j. •�• ,i 'sN•:L: . 1i71•�'•rN .L:u r ,•.: w;i4•.EY �:.,; r 'it 1' s t v .i. i X,wi e r � t'F + J, 't <t•r , 1t ), I,, t , i 2,!'.Z�} (�� Nx kl`..I i'�� �:t.. • � �� . ,. 0 � ' � } , 2 �'"i - .. e �►� fT if �,�` � j�5 f�f i �►H:'� �W � AasS stS. �.. r.. i!•r �2 pr �> Il ilN.;... , s q �, t. _ t `i'�'SV :. ..':!i (""i V �t = :+ ir,� ,�'Y '. ..�i I.t 7 Axay i. 'k � i w .!'x • �t id,> Y:: . .Q�.�J r�o_ii y, • u•w° :' �lsrC_ L. 1 , .s.. �f •4i # ss' •:•: c', w' � ' T {�• i a � `5. :re>.2:::,.,. r�:=- .s .,..s�'.?�eT. :. �.r..., .. 'i•:?,, �'•'�'is°:s�'yq .'.f :t, r�.�v�.e'Y 2e yy,, •'� e.-r �a_ h s.� zC wb.,'•�'... s,t ,> •s�sc.. '.d 4'.S"�',�. �'i .':.�., •Y., 1.., i '•.C'i: :.��• �•. t.) :1. .t•c:r c�e- <fY:it'.. S.. •r.1.t., .i. i•.• .>•'•�. ?4.'k6i .L •ix, i>..r t .i.y :�t. 2.I tJ ",�'�;�;' •' a:!.i.. t::•%;.,c x• .y.;q..;. 9dN'1 ,•�•� :y p.^.,•.i: '''+, +" .y "� �1 . !L }.. ;r ) .vi,�... • [ ,•t3s., !_r?. 1�s ;,'?;r,.... n&. , 1� > > i , 1..;.. ,.,: S k ° 2.' �1•°'> ��., r2 < "t .2 } ;. ' . y'+'.,t .R`. .h:f:? .. >.'} 1 . >� }t. %''r t t 5&`i <,sj: 9;c tl �-,� 4s '$y ..4 .� t ! :e�k�. S .s .p�,`e.: • i ,«;l .,c �> . r ;F t. , F ,� -i'• �� :)✓: y ri S f` s _ , i :? � s � h �� � h k �P... .{ -ijfis: "<-"!�y.0 ,�- �^is,� �:Y 'i .2 � . {• 1. .!R• 3t7e�3[tt' �.. eF%:... ,J12 E�. �:�t= �.1 i.. •�+ '�.r*.>r i t , r.��, <r MsSI (f� w ��,• �• .f �♦ : ��!..� + � ��X . ^ 3'�.1 ��.:� ,°, I 1, + :�•� s.� • �. � � on o � ���� �i - art ;t � �� i Bits t ">g 'r'•,t`+'`:. t` t f•e 'iF:,f°F' 4 a?^Y�.,'� i- .,de.: t..:n•:•...,. , ' .Lr'X'•{< V.,..," . , ,>,�;). t°�n • � .:v!i�{p�.0 .i' s s�:' i }'�:2 .Z • j •,; >. in .;7 •r j�. .,,�ui .14 i,,•r.:.>iei.x ,4 t 1 '�'t�?C•/^..�'�.%i`::•3' •'2?'j�•Fi,ilr!� 'ilL► ,t r.t ` Vie, ,•> ` ` . ! ',i. -.. y .i> �i;•.�5:=!Y.: ;,•F, .. {ti,.t `f' I'.•.:r. $,ii: �.� %. r,`••> ' 'S,. .. ., , iVt t. ., . •f EY;:,^>.;�r•F. �.: i:;Yi. _r ; s�. p' y s°. �' .'�#.. . ',r, .• r x ''.'1'•r•• 'u ., t �',�,,�r . r . c, +, ;:'f'�•"rw •rF; :r'. •,;J, �r. •.::" SHf f 3J 34� :,� .ryy�[,: a✓'._ ,�, � ' ., .0 A '. t ' } Ey.!) 'i > f kN� t;'%I- �,r�. �' � � >,r�.,• Yi, ° ' 'i �i,�. , .�/'{/�11it�s;ii s...e'S y ., •:: < � .. . /�F{;l:N, i.. :, r..., . igp,.I�r: .tY.• 4::.i.' a �� <'. f.' t t'7 � i «. i s ,��� F.iM .r. •r ,�.'! .i,F �. �. ✓r , ';f ..6:�;s. is :H .:i ..��'�.:: ,�'C, , a 1 �...s�::i-;•:+7"' �t < � � �1; i !. ,��:r� 's "�3;:t. �!� ,�' l�.i }.>. � •ti�` � i�.,( .. .? FAY:%•:<'.=v::::: .�: !-� ..... !,,., .a:::. i ',:1'^. <,+._°'•s�, .,.. ..r,. r:::.. � ,..,,;", :.''��..,.i ! 1 • f r fi '<h i �'Ft ,%v -� '• (f 14V 4r'4y kf } t t. 1 l #ed bar • s ( r•,�ctO7:•S� f..,�`i.^'.il.'I.L7P 2:' > i• J :)2 t e� i :.y:r,�'.e,� y •�4'•t.+ Y... t if«�..��� ?f> !'._.e'S'i. 4 i -1A y 'tswh rrs.4 J�''a:, c`• r;x i;yy":I�.: KY�•�t ei:�f �� . i�i`: °� � i i rs- _ tf. - r r :�a.,n'-'°t)rF's�.3 .. .. s:?ry',"•i.j�t is . s !: C;.' Page 45 of 99 Y > •a 1 Mx .� E �t1A��i��i k�� €� 4• E ! r ,� 14a ri; �Er. stiff! `i y f, yt, i•"t .,f�iYi{! /.�j i 1`��7 i2Y e�,� � t Uu� ypa IiL..a�. ,14��•di y.7 - .Y off, Gt,^!•�. S. i... w♦. ..t. Y::�` '!: �.'..L,i...;.e'A r"•,1 �1 :': },1. .} L:i�rli�(i-V�trJ( a..w.-.+;r :' '; 9` _ ::. r �, Co �.I:t:>.: ki• rlk�.S,' , !To��,r� a,: :'..s }4Yr.:5'J.A'"i '.9.•...3r .Y•.t S � :. .ti ., ,Y. r., ,1„ :.Y '2'.'J: :A'r .'a':'.>..Y•: '•1♦.'.'�,.. �r"„')'. 'S.1. r:... t. .I. ,.4'wY,4v .'R,,. . a. ".tip : .,'f.t: • !: , .t ' .1t' • ..i .f •., tv : rt' e• L•� 5• t i. 1' +'r F 1 v 'zv .' w •i :.1� •3�.t� lti. v t•t :��: '.� •r .i..... n><..... r. .. ... S . ., ,,, . f .. .....:.... .. i.. Y. t: , F .1 .i5'.:i •:}`A9 . At. •1. • va•r •, t ,. __.... .. .f,..t.., ..,,.. ,.,...E � .,., �, ,..... .. ....J.. ..J _ \ 1 r . � .. ta,.� f.r , ' r�..,• � i• \Y tta><. t. • .a..a'a`€; 1: ;;:= �• ! > ...... 9. � .... , .. .. .. .. ... e t r.. ..... ....., .. ... !v .... .. �.. A• ' ...c €. v. �' :1. !� t- a• =:-a.: a• .Z;v. ': i; . .f -, •`::�., . t . . A ..b..... .. /. .t er. ,f o?.::.'r;".;.. xru'� s. r:: i? i t •.:x. t, .. s ., Y. ..., •. 4:'.'>.Y t..:.' ..�r ! 'it r '�i." ''rl' �-a• 'iM• CS. ' .. .. ._ ,a .. .. , .N, .. .. .,., ... ..x-� .; f .i] ... �1;5 .,,.. .,..•e . ..2 ....:� ., ,, of ... .. .. J ... •. •... -. •i•.�`�\ .. �.,. <A ..... ,,�t. ✓.,, ..f ....«. <.......ti.. .: t. .� ..v .. a.r 7t0'' ,t'.'{{',,, fE [ ,f .d ,. .h. tl•�.. ♦ • .-�..f J . . .i•t rD r. .i.4. ... ..:• t <tt� E.•Iat .. !.' a;:� .1.<. •i x >rf rT>> St••. .V,Y •.f . •••"t�'•i .,>, t .:� .Y .. ! .. 1 E; .. r. J' . \.a:f4< u ii` .. .. . , . . \. . .e • e, >s ,� .... � ,.d . ... � . 4.. . >. , . ..... <. .. a . r..._ .. ri..... �'.'.:...... •u:A.,+.° � : ?! ... . ! •.f::: S? firY. '?. a- i E• �-,�liP',"'- ! ,_.`. °t..,t .. .,,�._.. .•. .,e3.,.14. •..._,.,.o. r.. t ,.. 1.... ....^. .t. .-.. It .. ,. '^2� ';i''-"r::♦ �... ':if. _r � r .. ._ Y:.4. S ... s ., Y. >,., 4y .,.. .A. .. .-•.<. ri ! .. , ...r. e >.1'.' +>i✓'2-». y • ,! "t. f <`f :". .<R•v.a.. I'F <.< a Y•. .� r .v `` , , .., ., .. , ,. . ,.... .�. " ,>a! ... , r t . ttSS . E ..•n>..,: •, . ...r... . . ,. v .: L�%c: rr.'fS....:,:. ,... .'::7d'' f 1 t <dk' ))S, • -Y.i v :iJ tpp ..r, � i. '. •i , .it. » Y. <. .. ltV \. .v. ..,.\ f.. ... >f4} NA .... J7 ., Yp ,. �<Y .'!'r» .: .. .♦.. ,f e. <r.n 1 . .R �7 �� .M.. i. .:4;:!.. r. <✓. ...f. �.. ' 1 !f'In jj Y �L i...R •'i >J ' .l' t �2 'A•':' .Sj ;... t'� �t {�•^". 'w, � !-:`r i . 1, } .. �. i ....t ��'Y+'. Jt . ).. . i ,.. 1 .. r � � 4 . � ., . ... y 5• < .. E r > � ... t r .. . k t !.. Y .. ,"�.'•}. �.:,. -� It^: .. t ..r,"Jt _ c� .. .. .. Y. ',.n .. rAt ! T , . ♦.P. . ♦ .. ,. .. . . : . . �I .. 1. �.. . . ..'f(n. ,:Y t•. .1 1 \, ly �':�. -. •! , f, :..Y .•wf: .v� .At rt 1 J .] i ... T Y.v y .v. .,. �C .. . ..s .i- .. • .w. a-.... ,. .. .r v � tt t..e. ..E'h 4 ... :•,'! i t'•i'' ,..��!fl' r a..S :1,. ..•a i) .. ..... � �.•e, 'i: >t. .,ti. .JSk .is. ,:.....::: .s.t /' Y a `i. J'4l , .t. r . t4. C °' .. , 'R. -h • v ::Ei .13: .< �d• ,r e _ r "3 i• R i .•, t •.. .. � .J.,, .,. yr. . , :<� .. 1. µ .-• , A. -3 ;yily. .... q ,.1 :,.v ..i ..... ,. v ..•:: .rJ. rr 1..,.. •.... ..._ .v.�.:oih r. A.t fc. ,.... t. _.. r ..., ..l,. ..., ♦... •......,. ..� , f. i ,, , )_r...: 2 t .� 1. i { � r`. f. .J '4! ::P•. 'xY,,,;r _....... .i� • ' . �.<.+ v¢ ; : � t r t r t). .. t • � ... <t •Y}" •;w!",... 'l ; � i'!: •'• • w ' E' �••' Sti,a�Y`.: ! �''� :. .. .. ... .... JIR . . . . .�,j1 ..a, .. .. A.Y: A .. .....iY.. ,;1 . .. C. � r . ... ..: ,..�. .:• .1.. t.. >..� .<..r •/,\. >Y�.l.. lr. .ti .. .l.• .E • <. i• . 1 >. :! t\4 �.. INN l., Y.. :.M<\ .6 i.. .t R"ri :i: .�•'♦ �. .' l�tl. .S. .. �, .A.:, ..'!-:.r -•..t. :..1�__�JaT <a..:. .1 f t4. ..\ Jn ..r, ., �'i. .. .a a,.:. ,i t s•'f.,� fir': uii--. •3�'F ,fir ., �� , :....a Y♦ fAh ..t .r,.i .t t 5 '� / . t3: s..f,... ,•S.,r .Y .,t :, to••.•.. s. t..r >L•,:.!�: ,' \ a::.i'. •R�1, 4. r.l+p: �.. "F�^�;.... S V_.. - 'i�f &44: <t� ri. ,?Y!+:t i'� t':`L`Y'� _. 5, :! • "• o. .. : ra,bT 1'f i.;N•.• ,t! 4t: �e' .:Y :;'..,` }. .... Wit: .?.�:. �.:... •. 7. •� •; b•6•'.., i.at'{ t,t :1`.`1.1t y •• s.: :!f-�':.`�:. ;1 Yil:4 •� .{R YI •.'�}. S.�. „t. J., h':<%•:V <;. iEi:•'E:t .,y r _._: d..a .� :•.f M, A♦..a..`, i.,...f q .{: lw.• .v-. Y. �•. i'r tti 't+.tt> Y .�.•Yf .. .Y. � T'`L �', r.' t. •:.... '1 i � � �„•� ,��a .. ..� .... ,:r :. r :r r '�. .F• iq. 'Y•) Yr T •vt. .LJ t\ i•, '•a: 1' 22 .•. '�:.. .� :v..o t•^ .a x •.�•• •r ,t a.Y:-. t .:.at !i o•. a. :->:Y .:(•:i s•: ;�;L f •I A. E },.. :,R. :1:"" t"�•5:{1,j'r..,�:.!.. or S:: r t.• ((tt�` .r;+ l:1 a` ..t. ..l.T7 \ ... ...R •.': i'!'.a S ..Y..a _f. }�, `. �•it l.. 7.a �}. ;i... t. .Y•.f':':':. .�,aea. IH. Ji;.•..�' .^ti ,1!:M .f` ItY_., sD lu• 3i': j. fH %^%L. 'i Agency Lead: TechLead: r Tech Lead: Page 46 of 99 .. ...:. ... .. _ .x.. ...1 .. .> tt„ x x .. ...,- :.. ....5 ....•.t.,i. ' ;. :r.. .,° , : -f. •, .r .. .,.a::,, �.�...i ...R,.. x :: >.t . .:!x.; ..,.::.i--;::•.•nt' ai_:: :} •:. ,fig . . , kw J t. a.r 't z xs..... h ,.r .. • r., :. e, x ,r• } . < 1 , }.. ..• i, e � ..£, a ,.. s. „ . , .. a,. 1 " . , , ...>< . k....1 : • .'iti • N , k:i: A � '� ,.. ,;. .t :.�a .'} .. e. :, ( 1, 1 . Y •. •. i:.•.' � ) ► i as 5 x $ .r ro .T .d '. •L` L!� A,t:'i'1::'rfiy• �. K'. a y4,•:;+r •3„x,t -.Z::i :�, S a.. .'�. •• .. f t �• s,: z� .. ,.. ° - i , ':�' a a .: �� . .,. # �•" .. a. <.. t `� t: a a t .. .) .t: t. i • - • : 'N �,•a . , t .,sl .., n .7 .SS`Y?: k=.3'.,... ,y. _4-,.,•:. •• #.. u x 3 :b ,lE t . i ? �•la. •►+' „a„• <•r "'1! :i^ ti. ar f.. i.r'•,> .F,t' s: ik. �', c, 'ilk s. 3 ,.r° •pr. 1• ae ! F :1 .�Si.• rs'r• 1 . � •a . .i' '. . ;i•< is ,:,. ::� . t,r• .: .Sf Ir „ r, > :,�"Y�,•'i�i t an. .vCwA r•: ...}:::. s .. ,. -.,•Jr �: n�•r } .. -a « v s,. .,.. �ir�;y<♦ •; ••. d:.'tS k[);. >'' r f °� xi, .�. a 1 :,.r, GC• . t : :: a•a:rz:: '! a° b'-. ::r:'• . i- . s�pyy :- 4, . 3• 1�y •,t ••�, i+.:..;.�., 1 ''� 1S ?£q'��f :;j...wr:'.• 3', •$..r,.' 'T . • Nt. •. y 9a : s- y tY.9 f k. E.• Pit > ! . 1 } "� ^sl�^. �i • �t< � °�, r}t.•.y r w , r ..N f , . • as t ... , ... :.:- .. ' °:., v .. . , ..A. 1'' . .f r 4 » .7 s•^��!•. a. :.4n*•t :1.' •}:• - rS .r •f •7 kr Q ^, ..rN !!.. . .R r r., iP, .. ..,. ...,. t:., •, ,�..... i!c .... :a .rt. • r'4 ..n. .,� e..r•J... it-.F.::. ,•5 }�. 1:£. i♦t., `Vi:,•y� .�:i a t�:t' f .. "4L 'S A h •{a' r c.••t .i i. C . :.._y, .,. 'fk ..a.. .. . , .n w r. •�� T 4 .:�.iy :•.•. .A r a.! rli '.• �'.t• a.... i � ...a .�,l,L 1. .f .3 tv. � a§"- . !k•9 .0',St..�; s . # , t. .1 fi• . •., ..t . {p .� T . k r . ,d:. ..:F ?i t. i r . 9'Y• a✓(' -` i"�'i i:N. '2t tr , a n f. - -r. . f 1, 1 ... .. , .. qY tt: •. . s, - a. ....: at.:. 5.,s ,y �r� � p �i t.. • •,: t • L'.-.! . i. .: :i!� .A:.t, .;. , i ,t2r Q rr • .t• .<�• ".i -Y'tt '•f{.: .t:•.., ••4v �C't '^k`r �x9 °,rs.' .,-Y`<l>,:: ia•J..S♦'. k. CD'•.: •w �t ':,i.:-. ..'4... v.'�r.�'t •q;•• !! ,:.,, ♦ >n , ��... .1 y},,� k t . tw,.., ..,><.. ..2A i .a. ,«y<•° tC•a 1 a •R:� 2,.•. "�r -J ,.a, r'ii 'a.":' i.. °',i�'•ii.. .1.. ..f.'• :r5 :frt : a�•'',`.. .•l. • n..,... e t .. .. ^r �":, 4" .� • , A .,,.:. '• .;.... �� ...,... +r» ^.. .»; • ,:•:.., :.... t }i... ,. I .. r . r :,.,.,. K!'. aar't) . $"•1 .. : r, '`y. ,- [.nSle'�`''..i:,t•4 af'3. :1.....r.: -E. a,. f iFa9} Xt ..�aia .#, a<[.: .t %t!5 4G.'i_.. Ci''iai. ^•.`'+.: 1>:' :at. 4 . ••F:'•i. T ...-: }.?.K .^E (° „at: °,."x .?%$.°1"r.. .F .v. •.i!•� i r!.^.. �4;k '!x.l, .\, .; .. .,, ,, r,, ,.,•.,., - ... <r�.t <.. ). - }._3r �.�.. r,..;. a, ...r:.f ,. ,. •,>, •. 3../.+<.:e4kt!•21,<.. kt°:.... ds ...,{ h. .s'�t ?... i... .. .1^i M. !1� x,.. a .y... '•. ,}yi( yy..: •. r�: °. l .... ... ..... .. .c. i. �.-; , 9�. iyy' > , _ . .r . ,. r •IA,'.:• 1 ..k.:,> ♦ t�;l .l : •, ,...;; :..x:. w t ::.1... �.., {.. s «.5. t t ' :a. .. :� iu: -':. , *-,'•t.,.;_�u,.; r.. ft r..4C r.,f-:r t'^... >. a yy t y,z..rz..z 4 , FM:t,«.:Y�_.c "�. e 1 t i'. ,{,. >r+ 'i.. .. 1} ) Y.<a. t.M.. pp t-+. :Y s a<, '� 'f } 'i,.a Y.> .}tj � 4�t '� ') 'tf:;<. ,>.. 5-,,.{s, .:...i. .'i .., .. .. .. .S17aNk 5�•�': 4.. . .. 1.. 3..„... <. :.1- F.ry , .Rr. . r•.f 1 • r.' •- r, .., , y. i� t y 11 f. r , �, t.i'."249 ,- a:t ¢,a. ) - <:. 1• u V .\Y�••;('G. .Xi'. : <t'. . £ � , iaf : -.i4 r. : it £ : 5,�• i. ti A i 4+... if� w . f « 1 ,,,. , > .. .. • +d ,'{• 't$t , .t . rr , , j Y:; . r,y ...; .. ,'1 r.£x �• :i2 t •!' !.r . s.:'• ) E -i '7 it, .t•. •:• i„ t `Yn£• -.� 3 ,.d')�Er •''•�:`.:.„.t. �,.5 .. „r...ilt.,, i#�r �d .^,'`. E<'{ at: :'� f )S ,, r:M J .) .:i - i:.•.a•.# �. ,, �r j1 ..i .. 'tS'1: #:v. :�? r. �.. p, ,., .,,fir,• ,t L. ,:•<>«,.5tf I .r q>; '. "!: .. i. r.. .v:r{.� �., Y:' ,;� �.7 ?i' ) t,w i%♦�' r ••. t +,�. +._„ + `5r':•:, •. 4:. 3 i a9r Y<'•:7Fa. :.:•„��''•tatt,, �xt!.d ,#t', - y /,. (y� �/(t}�,�//Y ♦R �•.4r,.M r:. fti :: 3jY. Y,L.":•:. `. :�1 •.� '?•ir,x8 C,1#•� }}.•J4 A���j�t •} .. .sat:`.-, ,. „ , .. ..: ., �i'"aT :- ,: 3' :.a n._. ii:.^�. �.Yy.•!. .L ,y :•.° .. .... }.s. .r .. ♦ ,,1, f.La :C. 1�' � A}.\. t.:tiR •4..:. 4.':�: < . .. > r,. ,. •. t1 :, . .7. � • x v, t x. ..r., .N. '<. Y r 3•:.z A,:t::'a{� y,,',i "ril i, ,..� ,... ,..f�/►5��..'i� ,:t.. r� t',1{>. „�. �9,5, 1. 1\...a .;1't.. > n�.k, ..i' ..'?l 1, .rrek .Ent .4 .;r,N..?YS .ir, .".\C,�!„1:1.!9 4�.r.�"FfC66,. 3Z1.': i'iY7': `i.•.C„ ti `j -.F�'C.i:. .4:. ,.-,£-!:' �.•?''4 1 .t'): 1•t,. a.i �.t:A ..,r,,..6u�t".t •'t 4... •. .. .5 . ...... ..5, -. ....... , Y C.,... tit:.,: t:'. I'f.r::r':` .v;a ..., ..^„, ..3 ,.. .. .. r ✓,. ... t. .....E ♦.., r .. _„. , - - so+!. _..,. .° y �;i `z '.�o-• itS !t.-t . 5... ., _.. i. ..... ", .... „ ,... t .. ..• . r.. ._. t ... .. .• a ...: .. •. .r .:�... ,.?,,., £r�.,i..;.:::'.-': � ::''�:<a: .'r : 5: } •'J..t., t : [ :. ., ,.r.. , .. S. .K„ ..:., .... .°.: ... ..,, r r'i.._. r. .-.. ... ,c ,,.}. .. ,4.., i ., a. .a •, .71.: n-•4d•-�1. b.• .t 5 t ;�>�' :•. s., t :.}.::y♦°:`.: t '�S'=rr .. ,,.. e t, ... r .i. -i .. . , .... t.w F. , .....:. t:.>.. r''.. a Y... ... .... ..... 'eE.r :p •E.':... ::�.t !x. ... :.:!i'�.Y. S ,E. i4.t •t. .z .4A r '1 ...i. �,S'3 �:. .:•C `: n 1 . , ...„, ....,,.. ,„ . , .... t ra ... .[:.\, .it{.t..1_ r^ ..., .. .} ...!: °-, ....... C.a. .:t< r::.:. •:. '':':t ♦r .. .::> . ai::, ii sA>,°:-.£.1'"= ,•,...E y £[> 't �'� r. ° ....:•,• rt: ...: 1> ,r- .. .... _. . ... .. M . .. , r.. . . . . . ... ..:... .. y.. - (. ih: °°: .. }: ti:i �. ,..j; !'i .' T`: #� ,° :°- t ,.r .. ., .: ..♦. ,. N.> v. r. ;. 1 .., r.. •'., , .,. ::.. .£• . .,, .^:1 r e .ate: i a..« 'i'x •s:r i .. I a ., .. _... 5, .. r..-.... ..,. d. .. s..£°. .�•Iv 4 1 ..... .. r ..,a ,. ..,. I,.re. < ,S `.a.. l x a_. :e•>r�;a stir .. , .. r.• A • tp..... t.. ! ... .-...v .: Y. ., ,. ..Y i,. •.r:: ::-�Y{: [..': ,r. -t f eT ,. ,, s., t^n. ,Y a, <�,.......zr :. i :�!: �r.,l...: :. t,. !. ,:t:"�??'y.t ., ry Cw .r?i ;t,.. L,r . .r r . ir. rk`: S 9.., 'A KY .,Z• ,U>. t:. ,J. ,S„Y. ,Si ^a.. .r), ,;a £ _4. :�.'•r v? k 'i .\'.-a{.. A2��e-- 2. �' 4t , �: ,•t t: ' 0. w ':i'' 'I : i'r i a , t.r i : >k'!� ,:}: v'`'Y'• .) ./' ` f.:',^.: •.r 5 r? sr 'k • .t J'. j- jj D •. Art• ''ri�� ,> •,•.t r I.Y .y. •t.• ♦ a f - 'rtti t i 'It /a�� r.. • 4. iir st V !/��Y��V� Cj`:.Y e: : _w M» ii,C 4> �i:9# a"°''iS •!}i ` i'f` y .'. : >: ::': •: C' is 4 f r'.- Lob."" ROW y3.^p: - .f.r`-• •: .,. .., .; ,. xr ,. •t>.>, .:.: ,.. .: � .... •. .., ,•. .,.• .. ... .,... •"r .,.r., r-.,. .,-: :�•°.•: ..> .x• arr r, .Y.,•es,. a t. 1,. .. ♦r :x' '.z t' ..:.7: +2 °.,. � ., Sat < ...r .rt ?£ }.. A .tx-3r ld♦ ,. •.. ., _>+ �♦:r♦ <• ]:.• . .. U ... .. _. 1.. .. A.w t iw• ..? !i. i-. x .a. , :, j..y•' 9v . •tt r•a^, ' 1 't+•' i. :) ai't''f: t� , jj _ .. .... ,- . .. �✓ r .... J > a. Y. ... S .,,. .... ... :. ... L'� {{ - {t t. • : tt . s �.S •.�'<' `-i.i ° • . a4:x-. ,- a ,'.: -::� .:? ,, Ef ,£:1 f:, z J r•L r.4 : S`. :'i.'" �.l' n'{. x,i_, ') rai ,r-12'• ii ,., ,:r.. .,• .4.. ., ;',k,... :k:34 i':' . <..L w, .., ,a.,.. , a. •, .. R.., .,. ... .. +t: t« 1. 1 .. ,>. vi : .(., ..A.: V... i:. :i`•Yt .., : rt4a r♦f..;:-f , .. f' ..k i" t,> r \>, a kr •,. tt,'r. : •:1.- �. , f :'L•�'r < , ! :� .. at ,. .•s s " r ♦ }} ., ..r. ,.... ♦: ..-.... ..., i „r .„� 1 +s. , ..r'.t,. t. e. ,^. ,i,s. t 5t••r : _Y. . 7 . . , yr .... v ,. r .S .. , ... . , , A .., A: .i ..1: �, .: a-.., a , .: ( .r.•t U!.}. ,v 1:: i, . tT � . a�' �j, .1 ' • ST. a?':.:> ,"r Y:'1 .-. - .. d:. ....." , ... 2....r .nn :. .. ,.. .. 5: r. .., J. .. ,. .,,.tt.� : ., j' t:i �.. t!•, •'i•' r �''t9•.,Ic 'r.:• .`�. �:•: is • ..-» .-a .. f.. .. ....t. >. ,n a , 5I , .. . r rL .. .Rr , :1{#, r .3'••,, :•,: ..'. .'C•.wr: .zEl: fF>i a'{:i i .f •.ti' } b:'' tt.„, d' , :r:. .. .......... . _. .s,. ✓ .. ... ^., �. , .a r 'i} <., t r.. r ... .. S ... a ..! . r..:..., �." , w , .... .t.. i. •• "i... r., 'iia:u'. �::'�. kj:. i� :•ki5ti' - . w p. i. , r Y V. ... .. r,. , .f.3... ,n ... ,a....,,, .. .t .. .•£ a . „ �r < . . • .:YS `ir .,._<kz3 ,• M'. .•.i rt •. r•' '•r • :'i�2 ...,. .. .) . . ,. . , .. .. i"s. .. . .. .,7 .. ! .c..-t : - . . r � .✓ 1 « ., 1. , ... > . •s : ti '�f bb i,� Y r ra.,i 3 t .•• A.z'.: .... a ,. ..n. � . r aft r .t .t•'tt>, r #.ik.i a. SS. ,> ._ .,i a_. :. . , r..r . .r rr. :!.. .l„ :.. . : ...: e.:�:� 4•ru• �i :r -:7 .k. .i ..r ..•it'• 3„ '•iXaw• rr :ri.. •%•t qqa � : �•I' ' !1•r:. y°w»: ... . ,. ° !. ^:�aKAkr d , ,,� .»... ,, .A ...47 .0 .,.7 ... yt ">.., .�, .. et-.Y,<.<i.°:: • l..t, 3 t r . F.r kti 7 i,.. f: ti 'i> ts� ',:- ,x "7•iat,..,T> , , ,_ yi «•} R. . iz;V . 1. •' e6�il3:l�''a»• ,:.� . . .>wrt v t 1 •.x I,r < k. y . 1 .'�, RXr,!• , e i... c. . t. .t '+ .t . il:• �>-rs ) . .0 a,r,.>rr ...'�'t, r, ,. .l.. .t•!:r•:f .t. .ttr,,, �.,.: .>�x„ { 5t• :• r. • ' 'aa" . Y..'.•.!B::rd: ",. .„', : , ».r:•: �'••,:. :'v .. u,a. •°: r'- ^:L: ..!'. , 13 - � 4; "#>=F"-, b :.h ` °">�s .T : ,.. . ... 1 t - , �F ,. S,r:.rf ••ilt .>•.f•; ;:',•..«.;.;';43..!•::;,., 4•.. ':°-'+'.,i, t• i . .�t �`i;.t;� : t: t !£mil,. .. ± ar...a y s r .. :: £'�•' F.♦ �' •2.t;. °'ii'. >;:Sw...6.i�' i;. i �r '«_ ";f�,<t:. ' � "v::`.. $.: a'�, iw}: >•I'A .......... .. ,.. .. . "1 ... _ .l ... ... .. ,.. ..'.- ...�' >'� . - ! r. .-., .t. ak t ..>. c - t. a .. ., . _..r•... ... n S'{ . . .,, r.•b..ti ,.. ,, + ,wt. :caF ,:•ait,. [� i i r 'a= t .- :>:. . a . ,. ... .. �:,.i ........,.. r°Sl...... ...4. ....._, A ._...::,..aa.. ,a. .-. :_ . ..-. .t a w., .t : �w•:.• v , rf. 1 r»': x,.. :•.1•.. . , :q :t�' -'}r'. . � , v .,.! _. t..._ _ t. :. .[,... ^t... ... .. , ..,*'Es.. „ ..� ..., .. .- - .. 3: ., r , < .� .♦ > ,°:» ,.> r .. < .;,. :.... ,.. ...... ,•, 7 _, i .f: :, ,.}.. ... , a..-rt •.-^, N ..a. ,t: i.Y <r 'ii.'.•' 'i'. :f+• .:4�� ai,..r: «,3. .. •.�.s }M:t�-. .u.. t£° ..t r _ , ...,. a...?aa. ., wa, ..,,. x., �:z. ..<,_,,: . < >. • � a ,i-• ,:,i :i%' i <:. ...,a. �' v... � a i ra r.ti _ ':?.„kx 2i' r .il'•S • . r x • _ .. -a £ t .:,. .,,, E55 }. .)) ,., .,,. r.d .. rr n . a . YI k '> :, ., ,. ° > , •, .Yr, r, tt" . ¢ „ T. 4 .'! (, a d� [. •£ r it '. ,r Y 5t .. / t": T'-n} 1',< r '` Yx•i - (i . A`kt . :iAk' ':d . •'.t> .Z. 4. � � 5•!• f r4.•• r .4 .'i! 'i ..t!� C: .i.. . t'.'.`,I r,. :! .. .:. ,. ,t..'�i ., r,�',... ..t. �' Y •.. .. ... ,. •, .. .rt 7 <.r •.. r ...n.. .. .>:'. .i :r Y., `.:x,.. .:V r ,t •. .: s ..c .}f,;p r0 a }`' r. .5� ... .eKr.♦ ,.fr.-- ., "i, ,N� ., a_, t,; .6:r«'.3'i�::. .z a�r..lt.. .. :h � iry � .L7, t .. ♦,, }}a,.r £d:. :£ ..i.Sr ,6 i, .::-Y•fr ' iaa,�, .,r F.it. . .. >(y�� � m�aatt'' 3t tt �! w' Fe :r:... Ise, t... 3, •. J!<. £ , 1. M2. $'w3.• i[ •:ul:a n:r..•. k: w,>.,:",� : ,1: ::, is 3 .S i 5 i �Iat_::f'�t:S , .�''li�•.. y.a ,ft � .:��, �h ':t>.:...: .a:... ..:: ♦... a r .. .1.., . ... .:.. ..... _ ,. i . ,... . , •:6'. t 5.v. .. j{' °:; Y .,a .5 t . . r i. , .4• s.> .fd-...i .;YS.. �„`q!T A it .}t:C":?ii.F yt,•;:.:r'i .£. el. > ..t.. J- z4•.. E :L';^.t ` •1 3: ,; : , ... .: v.... ,-.. ,, ....- . .r. ,.......r., - k t , •7'°. ..:r. -S:: .- r - ,i::• !°::. ,J Y[. .�r F,i, 'ail, 2 `...li• i;. .,, .:.E44: ,f>... �■ .. .. .. -... .,rci,.._. [.>r -, ... a. I. ... .'!, s :,L{. Yf Y.I r. „• 3 ia:i.. !' r y�. r +: l.w f. 1 �' :, Nf. '�tl� �i'•w tt,-'.>•r •J.a: �> �� '€.9. a' '•i•F � � ',": �.n._ � Y/■�� ->.r .`. ... ,.`.f° ..t .:. . r .. .. ....: r.. .. .t:. .e .J « .-i.. .),. z: .t a <. .a.t •. r.!!.. ... ,t .7, , 4.. .l, , 3... ..� t>.i', .T,,. rV: .� . T:P. n♦. .�, .w .... ,4tt• , .. .ft L fe „ .. ., .t 1 , .. •t d ...,, .. r . a.. r,R �•1 S,' •5'!i .; 1...9': 5 „ 9t:Y� ..4 i . S . . .h ;z4:.E..'t MY r. r,:) [:,r;:,, l'•l.:K•� •i�,. -., ., .. -»... _... .1� T .�' •. ,f .°„ ,,,. ,x,.. ¢.: t ,t'Y,,. ....} .,y.. r. I, .t if. !.:>• :•.4„ "r.°:.;. c,. t: }"M .. Z ... z.. .Y ...... .rt .... .. ... .. ...<s.... tP�. r J ,,., ,w . , ..„ i .... ,t J. „ 9 "4 1 tl ci•• :t <t.::' `:iT't t. •!'7v'.' �.%y'. -.. ..xr , r f. .. .. .._•.. -. .. .. .. .. .:.n ...w.r<.:. !i,)..'t, t 4.. a a1^ 4 « r 9 .• ,:..i I, ..,• .. :«.: ..-l.. ... ... ..> .,. .. , .. .. ... • ': La 4-^.4;`< �'t t• , i, '.a.:.., .'.a e:.M 1. . •. :.! ., ... ., !: . .... .... ..... .. : .<,t° C'. :ifia; .w :.< S • ! t.. !ii"�. '•;t j'i'z ••t'! !i. t �, ', r., ..lj.. .. .. ... -.. .. r,..... .. . ... ... .i. .. .. ..a >.. r.,... 6.. 1 ., t. 7. .. ... .f .. ,i. c• .- a } W.,... r ,r.. !Nf. •'`L. a• .J+ t., zJ'9'f1' . t 3. , t:v .,;. (r 1' � • j-1 :> . t.r Sr :.17.' .., ' :,s . :lay'•' ... F , .... ... .... .1..t _. .a*t�.! ..t �S .Y'' •. .:.. ,.. �. - .:<,.�. Y.-. .>At. t r'yo: •,.:' •4>:. C .5 .... ,... , .r . ♦ , _ . x.... t' .. 1 ...., ♦ 4 ... ., .: , ....: i . ' :i r .. ; ..:... ai d e,.ni.•}w ». i .i. ,r ],•r, p : ati':�•i:., ' c� } � � n �' -N .r. 1'6. i. tT `, •i :i�. N �• }'£.- V r::' .t '•f: � _ :: .V, # a. r9, ..;Cr'I'�(.iz:a:?':N., i^ •e' ar ,.• !d' :: :i: '•f r wr; 5r•i 3. :i / s •S*i:• li:'i '. i ° t . :4e • i; "E ••'t, t art > `ei'.:'J'':�'rs ' r a. it ,y • r! ' r '! :,t ' to . a: +' iti . •:.,• a:.u.' `':.. , a., •. J•� .•n.f..w tt:- :'Y• ir;,«.t ., z [r .4 i3 .i•:' .1: . ..r._ .. .. .. .. ... T 7. .... i ... .. .. _ [.... t ... .. t .... i ... , i a .li! :v�'. <'# 3 ..h. �� �.✓.r".:♦,. ,: �, t t. " s,.. r . J .. .,.i t . dl t! y r: ;.,:... ,...:.+. 1 :. • .3 ...,...•..... 4' r)...♦._, .. - :.. , ". _-:-.w.l.a. 7... ,. ,.�u.:.,. .e, "�" t . }} :•.•!-; r t .. -r`♦ ., ,' •. v -• .•••. .. r. ..1 "t . ^ .. _1 1 J'i .. r' 1' �%` i � .4.LC " Ss -ri a'.4: r„+. - i .Y :.t...,' . t . ' wr r f !.i '•vt,-- 2 • } '$ . ..e , - 'A'`--'t:: ':d , ".; .. t. ,. ..}..::. [.: :� f( ...�..r 3 - i::• Lr..S. L::•:: d :d�'•C•-'Si•�-... .i ., Lla.+.. rC2•.,. 4r ...:i'''"•a4.1 •'r.., tt i•r. .-Tay':-::Y �," .�i"• ..�:• ° f e sr•r• t, :#� Y> , P , , , a,r � : £ .•six. .. .,. ..'.' .. ..yj ...: ..xv e. „: .; °; �a f.. ,pt 3L. f♦..... i•:: ``': J: •. _:r•:•: •: ....4, tt .. w.. ,. .. .., ._. .... ( , h9 ,. S •••:+•. ...:£. 1. •i•{!^.,r •'): ,•3 r ,-ily ait}pi::'• V Rr .. t: >,. s'�. ,:a:i'ta. 1# ra :':r�' i:h�:C>.,!,- .:: t 1.... ., a a w < .t 1 : ., , : w ,fm n, •, < :• :w :,., .. ..•.. .. ria ,. .. ,N , +. -.r ,.. ... ., ,.... ! .. . < Y Y ,. ., t ., i•. t ,. J r t. .... AY. i,rr ..,x .. .a. . . W, t.r ..> ...,.....v, i,�t t.K.. .t , -., .. ., .f.. a .. .. ..: r .i. .-T. h... ,4 :•.. ...ti .. t�#''3 •T'.: � r:^ c. ...... - .�x. .... Jr.. ,, b., , ...3 •,. ».. .« t-a. >, rif .. a#. 5. 1. .< ."$.i ,..,. .. ,�...., .,. 7t .t .t ...,.,i ., <. Y. .9. « i : r .. .., :.L ..." ,'.. ..r ., - .::.:::::.:4)£,. , ,n ,•i3:;r. .a.. i , d.. .. .a, ., . ..� j. .y., ;, 9 t•. ,, . Y'R ... .,r ...,.a,:r 'yh> t. ... ..... .}.. xr:; r.a .,,,.;;<,, •°^`t.. :-.Y•: "•-. �. ":L4: 1:. '...i ,i+i ,t..!'a. .:JFS,: ..,-'J!.>. .G'}`�":o•'i - is .r , ,..,. �.,. .r.. .4 t i!:ta .',a,.'• .. ,5..,/".7^: .: e•i YG •. ;.'.. i... :at. P3''... ir. s... .... ! .r,.,:[•r,� •?'�. .. '>t. -:1'�;��,. u ,,�:€.. f.r t. r;r .;, .,.a. w....£a ::Y [. y +':t. d:'i°° •; f'4' > 5 :1 ,4r :'}: ^•9n'1 ,-r 1r. �<. a e... t:rq'•+'. •...rrR;.i1a r J%:',,, ?'•�' •. a. ... .a:..... ., � ,,..., 'v ♦... ...t)° .,.. .., :.$. .h. ,..S' 8:•'>i 4t 'v i�ti S.,.r: ,..ar" > .P'; Dria r e ll:i•S., j:. 1 « (' '„ .....� .. � t . inn , {', , #. <.... 4 �+.:i" •,:.•,�. „ : i;•:S,-., �` }� ... r 5 s : • v .r .. ; ,} ... ...:..::. ... ..f♦ .i yy,•'StC: `%.P... "�:. •.F Y.-. Y •°d---Y>"i°A. r @i' 4.„;�,a �::: ^.! ,t •.. r. , r, .4.'.'r. '•. �2 �`i '.`£ •y,wr; ••,.. •'i,�•at f..: .r ^� l z #:- 1. , <' '-i:�C•. .i. - r .�:. t . £a�.y ,:r:• .d'ir .r` ° .t :,e :"L;."':•. i ., r., �.i '•w•> ';y-''.'(t::'d'!•! row ... .., r., •t♦ '15 ,f i• rr• :�:. T•Y arr.: a. ., ,i :..i.•.F� is :A .. ,s t : ••e tn•af� F'' '-'i a' . i. • •�• • .3. 3 :<, •,t'•a., L, ::":A- t7C Y '3:. • •ra :a.. . :.-� .. 'a.. ,i„:.. .% 1 t _ 1' ..t id:> i , .fin -•x:^.'e' �^: `Y'. ?' , V� ,Y'•.r; �. C,a. .. it, l«• 't4.-)' >- r_t. ° LS+ �, ;k •!d. .9+t� '•a�f } :'rt • ? :,;a {' a, i. ..i'Y .'S �i i.'r<. �. r..: t� .�9:•��� Jai' ��''! : £44"e .ii�. i' !,y i ':,i' �ap) yf'�:r �•?�:s'y .i. 2 ) • ..ri,. '!; ��,r M": Y.v,,. � ,t,4E 11-• .4^4t. rl ♦ r a> :1 ° , t,•1 .� •t,:•.•!•. !Mri, � 'w'�'i •fY',r � - t, �'YY-.3I.:Y �? ,: > pp cc � , � r}•.: ! gg „} •.,• �+ 'ii: w tt' t;.. G. �•• ii�� t <! :I r'.,... .�.. 5rtr:.. 's�.t;�� - 'i: u:aar,La♦>...t:.r'^�r.,e�.•,;•a,;,,,,,,;•t.• •,I•,s,'g,4..Y,;7p'•3a ' a• ..; 3<...: � ., ,t : �!Tc'8!:.ii!.�•r•r,[:x:rfr%'�♦�'`.;•i•c;:: ;f<. },a :+.:.,i'.. .�ii., � :u•�. .:/�]`: ...�` , t.: a.. .... ,� .Y.i 5t., ..: c�.. , `.`C ••::. ' .: ° :.:: , . -: - .fi :ti. ,tr..+�.tr:1 :+:::t: ;.v:•:r•a:..r..., ,:,vxt..... s.r ''� 0!e --� r . r. r � .r t 4.: • s9. .t:k. :.£ , ..�Si Y 'S � . >,;, .•r�l, Risk Rating (Hi, Mod, Lo): ^a ,. i , .. ,[ .. r.: .i r.a.1. .._. .,:. t.'t{ ., . ,.- ,•.. ,.. .. - .f. :•) ., :.. ... .. .a. ,: ..,....,,, ...l. .. .... w.... af.1 ,x..... o. „,lf }.. i• ... .. .. ..£ ., - .f r .r JgCt ..r.<a . { .. . D... .. a7.,. .,.i.:, : .%..<,. .. "Y' ',.#sz,ta. ... . [ ? <.... a .. _ .,. a•, .. k a ..:a ., . , . .A R ..,..... ... f ,3° . .. .. .... .. 't .. .. t. ...'r... .. .... r y .._ ...- _ .a'_. :. ..1. 'k £. s .-.:: •3. t t. ,.. �n -t '/•.i`-°.f>:' .:D ''F°'' , a :4 k.• dr. ,4.>•..•.i:� •'ti •' i , 5 .'! < a4 a t ^•il:: .. , , .,:fir, .[ A .z}.,. a$;:? f S' � • :f' .,,•' t.. < .a .# .,L ra� Z; i... ..i.i:? .f•<t ,t _ .n.. p S _, t. .. .• a ... ...t ._ , . ..- .. .. , A.. t . .. r _. . _!} £-. r._„ }.. _, ... i! r .r . ,. , r ,a i z. t.f i, ,.. .. tr .. r' v ,r �. .. ! t'a ,..+:: '.t• 4 ! t. L ♦Y •.., .A.. .. .r.. ... ♦.... .. ....... ...• .,,. .5. :. v:, .•. :' .. r,. S :. ,. .. ., ,..>, .1 .} �. f O t 4 ,IY .t ., a .a i J , < , 1. v >t ,M. ..>. J, i t f a. `i 4x,. ! �a,! ti.-,. .., .. .. s...yz°� r t .. ..a. ..x'' ,':%..e l•: .•'1t • ''i' '7 . to . E i'�, 7 < r. :.... • >i :• t'. 3 ,w1..: :1 J >ra£ 1.'::':t't., .,h .rr `, �'h•.: '. >..,i•.J. 'S:. "•! f. t: '` c.t„ •L 'li• ,A"w!: V-_ !3:� 1�N fi..:: Wl-: y.eY .•' 4w .> n t� �».. •i {{ .tt t •['. :r 7 5: C j, . i ::• :CG'i' ,'v.,.::iaf tt.. •>,;?•., i'. _. '!r. '•y';1i 'S :',i.. .;::•#': ': .., .,... ,^r. .. l•::•, [ .:.'.- .. ... ....s i. .. �.r. 9. ... t w.„.. .. .� at ... 4..t°. - >. •-'tim•ie at.x'[:'2[.F. a• .t t• asi!♦. °S. J.. Nr. 1. 1 rid ::.`,.t,3«., a;,{. .$.>...< s z.t .-... �<...: .,. .:,Y, v:.:: •.:: <. . ;... ..... 'it` :. r.... �is ,....t. �. �. �^J{ •i! s> j'r }:�,'{: 1•.- .. Y.�. .& it-tti rn»,.-. 3L. [X ...we a.t r.k i.�}�r :, .. 7.51 r••,.fi. I:e y,..s .i YC , .$, I. y: r. :?.i .0 .i«> 1' ':F 't. .,rnr s, . :w. . `: :��•.' � tit :•3 « r {, 'f .. .. , . - ti: >.: �,:. r w,l .., . �!t.. .. .-,.:..)y.. ..:.. r. r.z. : r .t.. -. x. ..J.• .. ws..r. .. .: .... r ... ...,., h fl vle .\': ..... .. t: .,. ... ..FA..... .. ...... ... ... ,... r... .. r,.. Y .!. i..h• /^• ...:`: r7•r: � ...<rt:: 1 r:,•.. •a •r'a ,. t, s.:` ..�'<. .?'2: ,.::i^:>S '._4..!ii�z .' . aL .v;-, 1�;»'•.: tr. .b `t. Vr.. <'+r.t.. ;.3.1+�-r Page 47 of 99 .•X . ...',. ,y11 rt' a .. i, .,t «' , '.. , . - i', ..r v L \ N dC,d•. ,y ..,VtV' ,\ : i 1'a i '>- l.: :Sai Y a.-341. '•`t ' ] a 3i 1 1 1 . I ••).; ''{ •S' § .YSY . 7t '.tr 'C: ►A.. •'S.Yr w• ' .'i" r.' :,1' v r t•'.`. }• v `��ir+" ': t. :+aS Y' a' rr' '.� ♦ ::S •i , y. � ,), . >f ;r t; •3 i ., 1 �' x i`( �s,1 , . i . si M l .p. :h .. d".". ra:i: .y •,I : .� t •��'' .[, 1 �'1; 131, J+ ?A . S• w n. Y.• L.,,.r, , 'r y : N .u. ,,r :♦ ,,I .,,I 2y(� F : .l.i •ti �. t ': � Y �iF,V { 1- w:l V. y, Y , �e 4 J•'.. n "i' ♦ 1, i M ir' i.'"•t Y h .{ f.. f 3.iJ.. . � .•A ,L.. 1'. t • .; 'tl P N }Y' 1! i'^I.�.• {�y�, i`i i•) N'" F� :i+: ':11. S I. 11 . M A`F+J .•"• i'•� 3 Y.. :/} iy�,Y rrt. • '� .S J I !',i•nl. :! 1` {{ ' f.:: _ •• 7,♦T ,,,. !i�•�...) � F �i f �,, ]� � Y. •i ,T A 'Ia• h ••,,. L cC•t{, r - ' °i. .�•ig. , Ird c..'i rc'IDI' ' }�•. i{ I �f, i 1 •:�. •T�',• .,i'3,'l �{ g•• • . ;/ ..i j. 1. .yr'r .S' . «t fm. t .4.: .. ,y Eu'' r + •,w .. .NI" ..�. `::'., ,i. �., .. L•;... i... jr BY,... t'•.'i�' Y, l,1}!, . wl1 !Y �r. � a � IJ' 3. r.k 4, . n ii• �7.. • ...f ;• i".�3y4 1 '' ,''. +iR�3�' T .: t. � ! �, : S'� 7:' i� • 5 "+`S , 4• ...••t i .9.5 t ! .. i , :ri . % N'S 711 :� �h.}'. ..x y. 1a J;'� •I .•w. �sti Y lrl+ .7 i:` rl. ri .�: �,t;-J lit. ; !d 'i •v ., t .'Y •� i pv?,. .a, Z- .7 . . t i' 3 4. i . f) i;• ,., :i 1 y i1 :i+1 "\ • y, . r 4: fi .1 f f •wiv. ,,1�• _ d?1..1.. t l . . � i � i. �".i .a : ii j1f 'x. � .: C. 1`. y, Yr ' G:7.I�S..r D t .1}1, . 1 - ,. •a i^' : <1 �» ' 1. .. A.. ,.ryry,,•,J,ti'�Ti^.,: •J• . .•.,::xr Yv J c. A�'' i `�••: •'i •!. w31 ..• � , Y ' ./ .�: .Y.:. •frt h. -•. i, ..t� ::,�,ai .0 ) .-�!. .1.• D lii�: ., r....t „a i <....• 7',.rA ,Y, L � �i.. �y,.. .. r�S iS -�7,• .i elii' a � . •,. ,.rr ... =7. '3dw N {, '1 ,: t�Cx iM..Y.0 %.> ,. i � .. fr••:: - a e. .y., 4r r, '-:.'.''{. t C Ix.-•tti: S'2 ijy •..' ala, yi iti�.:x>•'f i. '+�.. ♦ �{!S ��,,j} 1 ',�)��3y t !J� iy� 1♦ L. . 'Q �� ,, r, :e. ,r+".: �.�,:rti, -,I�' ' >,,.,..F.::• t, h . V r.1. it .: R. ,' t..:..,f i,'' xd: i; t'.b :�, .Y,, ! �.... r•S.C; •ir, I(�' , t� l••:.: r..,. � l .h . far ..� ,. �i't �x:'9 I,P. •F` "M -'1+., Y i,: r .• '.o f Y. Y.. ,/$7 � AI• � � • Yiw : Y, y-J.d' n) S.k•? � 1 .u. ,L. `. i .. ^p k � > 4 C :`E:�.L'r ,r h . ,I' ,. r � ✓,,,. i r): . , ..lkt'• rr. :,v��, . .. C .., ,1. , �v]ifil';{ :I.t',is 42.t 'fir' t .t •t, �''j;; .•s �'. a 11 :a) !s ...>: t., ; � �: s': :C�.. d ,S� Yr •..Y<9 ..�. �3 FS-'l•}.• 'r.4 • ( `is', y >'� 4`, .a IJ 1a ] , NL "`ityNa... •�•�••C/( ��• ! d.t ':Y � � � la'. .fY a'.,- • 2 .a ,,. r:.:. 1.» 2,1�.�:'>:kl.ri :. rl:.t,-. •i'. wi), •.l ii..., .3•a• .�i►'1v V. i'. It ...ti t' l'„T �. t .1. �. .� . � ji,',�V1, �{ .> 'C. h. J. � 4 T♦: • 7 •LA 'J.i. 4 "9 '.'1�•. i { { Y 1• ,A . i .:'1 . f}r;•. . �•' ..2: � -:y.. i ' yV I' '• ) r' • r .'_ .j]��... •. [ Sia �',: . •. r ,: l':'. i �v �.t K i•..i '1 '�j: �::xn�':yit - 1,. � �I �L.� � A - !.. � �11 .�Itk .. q4.� C i �1 [� � 1 • >i !.• '. a C: �r j' � '�~� '"•ta T`•({;• x.:a (... ' e" ',�'.: ;: 2 � Aj ,: ,�• ,:r' .i.,*i''�i•••• '}•E1 � a fi, 1 S 1' S t' l L � % R •, ��I{(� ]� :i\ � 1a}' .. .. 'Z• S ",. L 5 .Ci : �i: :it)!K, L'F 3�L Y'}8'•�y, •• C•' '4}L/ y N�• r . t�i .'{.�y}.��v."Jd:' 7•5 ,•.!;:..'� r•'s,. }} ���... � r ,'kS,� :4 ''-i:':�n lY1 �. � ��,IK,� � � id i J. �� �h�. i}Y ;S �": �''•ti'..' -,, MO•���V.r':� :�� .,-�i:a'Stt _ y:�.i .'Jz'S: a .,t': ° ?t' <e. Y.ii,. ..'S'i ' 1 ,1i , •.S 1�.v '. t 1. AL� ..j.� � r... r l e• . a.. , .:. ', . d J :: : "i!+! si..',.: .. '•Z . n t : 'L.,. •,: +f. f r. f.'s )• A: ,. :,.. '.e 1, y5. ♦�'•. �'.1■�,tY • .r .,7 ix t.. •A. r. :°..n i ?:, tc• t.. 7';: ).t= .._�lt.+:..... : r ..� : ,� "':»'i •='•... 'i a•X.. � "'!i ,2, f.. a. Lir.r.i L... is 'F� b . a ' V ,qq��' n'> C �' F» .S'•'::i � , >ria .1. ..5.. [ � .Y. f: , . 4 •i, t. ..J,. .,.o ti•. -i'�' ,J.. t T. ' r C i:. ,: •: '. .., '� 1 ` .e.66 .•C }�•�! i?. 7y r 3 • ,i • C �Ci' 2 `4.i ', . i Y': • , w. ci-tX :� Y . G * .y f i,i,.:: .3.: .,i lr. ,Y .i„ L°.;� -i• :i:.,' >:.. ;.•i.• :.�.. .IL;"• .t'i:•. Js 1`..:i. vta i• i::lx :kl.' 'A`.`:.. ::k� e• ai• :.i .l r.. ••!•''r.:v ,:.rC.(;L7!.v t»! r:« r r lr.'••:. •. .xe. Zt r. .i.• t•,:;::" 942, "l ... -. Y' 1 ♦ . ».. . .. ,. . , f .> i a •', ,: , .. ..t 1> . ,.r .. .p •:A.... f:" i C. ,`.Yvl... 11: . Dt L..l .: ,,� •.:( -i �.M i .: ,' .:'):: , :i .., 1 ,r., AL. )... G _4, Tt. .) J rn- A- ::ram f; u Y° .'S '•'L'r)' ro+ . ,1 + � i., ,r .� ..C• •R deb. .+S),I f. e,-...: i' , i' at ,. .�c tva •"'tt:i ( . A •,s. t: :.r7 ii. :.+. t 3 /■�■ i• Ew '°.S!°, ��'•`:.7 ": �W �P..,. t•.•.. >.: i.t••... ,•. ?. •Si pS �.♦P'..' ie}. y. 7._a... L. •.a:-. a:7i.:"':.. ..?,y:?e t. 1' .:S'.r t: >...,.r. ...I v.,. ,,i� t?;;•�C',.'•F��.. ••.1.. .r .. f.` /. f 9,.. ::°7•• .J. ,.. - S ,. ...... ... • .. . .) I .. . .. .. .. .,. . ,r. f . > . r M . f .. I ... » , ,t, .a.: v h r.. y...• •+'.' to :a ., • .•pr•F' ,"}•: MS,A'....: 1•. ,ii ". i i • M:L .r.. ru ,...., ,,,., < ...... .. «.., f.n i.. .,:. n p+. !•t ,rv.:. ... •C'?' °.. °... :. , ,. .D•f. t•.i•• •p., 7. v f• !, � a•!:. )«•,� t.11 J. •.i i 4 t?• "03/ 1.. .Sr •:' �° 3r, ,�.... f: �•i i[' x.• !'d., .. ...V ....... C .. .. x. i .. i ... ' I, .... v , .. ..),,1,.. .. ; 4n. ... ,i... �.t• .. i[`. ..tt-..1, ,1 {T t. i. r♦..- J vY'` l .\ \• :.J R ♦ rti ' 7^ • N .:... ....,A ... t♦ t. .. ,. ...v. L. .... r.>�E... f(.... .. .. .,• ) •v. . v t r..: -e:Y. T 2: h I,.Mr. ,♦ .'b > { E:.LI ♦.l 'S.'.• V,Jfl:t •. i.y.r. h. k .Lt .. ..{ i • 11 :>:..finl,S:i. x. ._,.., ....... max. �ti,. 1, I > .«d.Ia ,!(..,, ..'rxv., .„. •n,) •t.. iJ ., f. + r,i. Y, X a.. ): .., .•r�• .T. ..a .,t. a�A.. .•�. .•{ •'••'a' E. }S ry "� r- -Y• i 7 It •, )fi::, l y } ?,. r. , . ..v. JY >•."I:. :"'1'.. a Ko. r;^. ..i.,.. ., `' , , < �.�.0 -�, N• I , r ...r ' tax :.} . s y r .� , ♦ ... h .!.' ). q.;..b L ' i . ..•� 'Q: = :"'9"•' . t-$�. ': }•. r•1. fi c.'•7i. Y. o. '! •e.*;. .:/` •1^;�'� _�.. ;.; .. .J '+Xr9 •i,y •r .Yf• r _ !' (, r » f $ : 'M' ,i. I ' ' 3' N .M--.. '{?. .: � . . l r }• •. id I) r �1,,.. :.1: ..:y . i11�' ' :.. � .. r» • iiq •` I A .:v.ly ;.:,.i°� I E''� •� ,.t >s. ..f .. t,..:, ......: ,... � : ` �; �.a:. , l 'h f• ,.. .[trr.. : •� . •i.. J}• :.t . � . ,.,.x., ff .f. +! !_ "il.• � i A a.. 4i`I`4 ; r: 1 ,4.., „xr,' :?. x • •hr' ..5.. •' .�� f �. r '>+<,, . <:.... _ < ... ° •... (:c�:. .i i1"•,1 l} .,• . r .. �.... Mr ....:•1 l t :: :� . "� 1 � '� 1 r r' r .... A(( x 1+. ._... . .{ .. . ,. , r. d > , , <... ,j .r.:. r ".: � :.,:.. ,Jr . c ... ..i• •L•.jS.. I s.,. ,,,d 1 « .14J ' v; ',:r ., , . 5 , �. i .IS1yg r••v [ r}.A . ,v+ l .. : -.v • R ., t r. r ....• ..4.t � rDt', i, . i. ,f Y ,. is s�1 ti 'a M �.. ...r4. 1. }y� J; � ..<. ... Yf• .':�IZ�� ` Xf1•' Il •::� � }, + 1 1 < C .i.).. t FF �, , .. »{ •ax 6. tv ., K.1. 4 . ..il, r'1. ..,.L f,:. 1 N� �M����V�xx...w;b { M •! Y, :. i,• KI•'..;. Y'A'v• �S w�%,.;.1' �. . y''�� 5.. �:. � ,Y. .., <.. >, tw .. : ' .. ,. �' ...: > H). , �". �. i ',. ._ , .. .t4hA ... 1 ; c. ..::,, ..:. . �tt , i•i , 'ir''t` �.y •. S : S: ..t S' . •C.. ,� Ix. "`. N,: : .i,, r fie, 1 e ' ti. t 1 !�{J"t- _ { �. ,. \ } ..n nr I i,...... `.,,.. 0t �I+;i.9 Z. •V. �,fli. r.....J.... i-. t `;.: ;. !_. �.•_ . .:' 2) •r'..��.,♦ S � a�y ':•t � �N„i,.1.2 l! a y Jj4': ).) Y.� � .'l •T j� :54:•':• .t. >, �,�.j .cr3,. 3A. F...,. [ 'U:'t`� `y .h r. 1,. , i�+'��' i .�`(, t !•!' +ia 1 x` . , , t . , ., .. .-:. .. , .,..y : , d.. ... w .. ,r .� ... ...'Y" . :31:`.« .a .. .: ,} t!1 ,.1 r ,% •� .'•...5 xr, .I., .,it♦..... V•,, ,•�,. ..• ., ,. ... ly..�li .... ,tyr .�, �,i>i .% 9iIR .Y�. ,. ,.,.r>, .... .tY, • Ll��."' t tl}I I'i .h... t 'r� ? 1. at _ tt .. .. A:. 7 7 t.. �f{ /�. . s5 [� • ,°i.. A ♦ Sa. . N r •! , jn �i ,. & a[S :' i'. y .:a •y7 Yt' � , .y. ,••ii�:' .. •Erh.e 'f' 7 r.a . %.4. t... .: .:..:..:. t .... •q � ra 1 i.I.'.!,�•-..�. ty�d3 � �i•+�}a�• : i r" ly• 4', ,i :.»� „t« �. �. )1:.•jIf "�.: :.::7 �'.P♦'.g.;.: - w..ai °'':4`• i- G:< ). tT �p� ...�:'. L .'+i't` t ,:) �;..+¢ ^ ;:r°• /x r:�� 0 Y 1 s,�. r yy}�.�.::.•>. � .� •:w.f: �. �.. �' ' � ' c ..:> 4 ^;. # 11- ' S�• � .... .•: ^'�%�• 4h••1' "{2" . .' .: ' �� /. I�.+,i .. �.1; i:v^•J r°"� .� yi.Str' .E. ,�ii7T 7,'S:•r 's>`•.713 .. 1 < . 1.. M 1)f.1 i� : ■�� :i°Yp"i:' •.:�,id. ; y� i .;I . o:....,v-, ..,, .. j '� 1 Y, .f A•.• h ..,i�. > .: .' h .. !I:•, � r •..:,,[.. �i.<� � ' � P �-1.,. i . �".6 �. -.r� ! 5,. i ��.s. » .,i>•.Aj:•Sv ,•., ..:.• :%.:Y.I. , �,. .:.i�T.-S1..W. i' ,� �i/'{N, •.1•Vf KI::;�S•iy.�%':wtM!11iP/ yYA4� .iR�T,:. t :L. ,,,rA! ��R�b� >..�. ty .• , a.,,.., ..: .. 1 ,.. ,,.,� .:•.',ra„ ,...;'itS v,.,.�'i � .� lit•, ,..,. .tt r•,.;:,.r +Y?ti .'�•'..,y ..f.r• ,A.:Y M ?II .> �• ✓ .} ;,t.,..y .x 3• SI rp.. r r• �....; S�. d• yy { aa 11II�>., F.,'t� �L"i J Jd.((•�1. .a:: �. 1 • W •., > vtY,\1 'p ..r^ +g•SJ�Qj f ' '� ,'�. S jf.. ••�� ,.-x•tA /s 1�'C•` Mr ..>.IJ :'1 .t . ,,:��.. r..+.Ei r... .:..11.t _.l: r"r .;f . ..f .:a :. Y (•_`` ..e�?.•,.. )s•?i,: h; .. ?,c,!:.i. 'i1 ,a..i ,,. 1. '.'.,..�f..... .. :... :. ikr+I. `. ix....j__,.; ..j+,i .h�T.":S r1i�,.t7.:. 3. ...�•4'.. ..>C Kr. B.' f?. �..ZY'.\�,..a r�l., )! .•.20 °: :�:.: I: r2�: ..:•. ...:¢r• ./. :•. r5^ .i.:'JII...dfi. ... .... ..r.♦. D ... .. �.i, .l �» i:,..»i�i! c--6r.-1.::. �...:' .:�. '�i•�1 r.'�l'.I�.i .tJ .'•Lr.a `I'. i:i : .'f:'�E..1 ,:Y;.- I e•D`: >'%" a?Ip- ly'' .i<♦,., •Tv �1)I'•i: �..fld. �l. � :. y,t[ ,3>♦ ••�•�i. i,` t1.•2.,!t'.,il.t. •211. :i j^.-1 �Y •tt�v{r fti�• (.i. riyL ,:,;. .•t ` "! ' ..t`:lr' ."r).':.�F. •:�: 'r:��:'1 Y��' .�+�. y3<:.: �.i ,�i:�:'lt" •; , ..�,C• r »r4"" x,{ I �Y'' ♦'tC:. '7'y}• 7 " .iv.;. ,.a•r. �' ^et .t Ll. g :;r�► 6 !i`s. .S• •fit 'd. F.) ••t .r•' '",.. v ' J ` i.: •dy .• CK 1-.: a '�.:. 4,Y`i :C .,.�. _ :.� • .J- �"';•L, !:tli Yh. x �-:� j. . .r� -2N-- 3I*i+ ►?7't�SJ.• 1 • .t .ii. x y.. .tin »t�'!Sx?3.}j ••.�. 'N i'i ..-., J.:•:.:, ..r4i •_.?°!K ..7'7.ti,'f•✓ ,•.•.. , t• i. "� ., i.:: � . lY`,.�/.. . I�, .�• .r .V .. .S st i. 'a 1. ,c: - R4• !.. a`.'`,r w'p. (... 9 R M �!`:'.. .: /F. J„'• i•i: v #•: c';, '♦ J N:'. .ems.. ►. •k.•: a. J A ..fS.:�:. �•:; ',1 t't:• 2✓ y, f ., ra . , x, .:' }r, r/::.. •a.�A R•t •t } 7.1 ": .. y.:r s • �J .: .i 4 : I � f > » /� ,y.�'��: yam, • •�. ..•�•a'. �� A!.t ii, 'S..i '>, v : SS � 1.1.,}„.. '�.,. •r.. � "3•t4,r �. �y :i�>f•t• •, �"' 2�. ? ,•c•y,»• �: Jyl.'6 fi'S...�. � �. •'+a � �� � ��.. .9' r:; .4,�.%� , t.:it.. ►, f y i .i 'Jli'r T ;:. a►,. L• E ;., , .. .._.. , •t j +`Sal, * 4r•5..�1 t�.t'�. a i• ...�. •i ,wi .,:i: t ,}_, e... 1"7� r:h ,1.., � F,� i ..i''" it~. 9,' .. r.:-_ i '. Y'V •::' 1��S�t} .< 1 : ,. g.. ay,. :N• i. •....�. .; n•, •,; .1+•• �..:. .. ... .. .. :• .. :. •15. :J..., .. .: 3'i�.•._: i >�•' 1F' •� ... .'� ..%-. ,`ik'.Si. •.�.: .>.f !1 •. �7i {+^ l� t ry ..r , .,i. £ �. r. i'� i � C:..., ti',v,.. �Sy •n pi •)•,• •>, rit'4N V.". 3 � •..:.. +' .•,.}.:.( ^1• u4 '1 }•71''/:-af :•L' ..ai• 3[ � �.. . .v.. r....... .. r, i• D rC A,. ., •. .' :., .' �t.,�, rl .•1 f•d} -� ,,•.. �f�+ ,,¢ t .4 J.:.i'j S'1 L..: nd . ♦ rf... ,,"" .. ,e •.w .. its:.., .... . :.v• .. . , ., < .H .....• . hi. <. > � Y '# -f / >: SyC .xA: 11. r�'c''3., ,e,t., 1!.. s,.,A J.. ,I C <, ..! tz :.dt.l:4. ;r. �.ild ,.r. .Z.i'1• .a a, r°:\.ii� •p• 1 iG',•:+..:4 ��. �!i.Y'�`•. �.:}�i•i ;C. 1. :� :L eNe•, 5s F•, r 2.' ���d,.• :,•, t.V.l,7..1.••r' a• {►., 'it.. t.r :.;a., l.,-r�. w».�... ,.1.. ....... . •, :::..:.,li,s..b'I D�.": r; r . ., ♦ - 1 . ). i, .. u:. d.,l.•. v•A •. • r• ��.•'�.. !'...,,:,3 f� n s 'YS F, Page 48 of 99 ;f •; {.M '..�, .: }i''Y'. 4''3 biKt'?�lo.ia":il, a t<'r�: r. u j:'F'' ft:v :ia i. »< �.. r 1.. Y} 1. a r ,r- 7 �fi. r, ., .,:4:?ti '+fi; fi . ,.y :.f ,: ><,'1t .. zt 9 , .. '�'� ee+, a, ..� .... '� ... i # . ...:�. ..fir <.�,•: r�., a t'; ,i; >r .. r :•... > . ! , tt ., •. . •,,. .. Zas. •� !aa .t%; r.al. ' M Y •.eke .1 .i {{ ��j �. /� ''.t' �j i� .i :1' i. i,l' i`l, .i .i l�M�- ��i .:,,.� �w{ f;• r �+ �;.�1.1. 1�. .� •4 frt. !, t44 � ' : • }t.. 2� '. - J ...., r.. f.: ; :: : ,,;: .« • r ;.:+• r ; ; r«, ... s:;w c..::.: ,. ;+.:{ fti: .'� ,,>•.... .iy.. • : ,tTf• ...� t:•tf N •jf .,,..Y�. �., :.r ; .,r„ ,;; f • •. ... i\ . ».-r' .... !>.•.,, . �{.. ,r:.,e�T,?..w 1.: yyyyyyffrrrr...... ,. A, .-Y. �? >;;»� .3a.�a.'{ ^4.i {R,.. Vv':: 'S, `'•ij>)G? 'ki:,t'�'.w t� 9 �."z .t l!. i !w� jyP !t l zt .f r.< S�S. .'L>.t. i 1 �i< � �� .r<i,j • ..� k b .'..` .ia: �'r,l> .. rf. ,�'t }" :L't�,• 7.Fv::` ■ '•t.k- ,t..� .tl� 4< !tt /•f •r '•7: t .5 a• - z f �, � :'c! . A`"�rr-. � �� 3F,.» .:.� i•�' � �., , - '.r 't.l rA ♦t - t.Ft.: .fs. ,1f-c L 1� rlJw':.«r r>..; ;as•.:..�• xi t+•:• .l - 1' A,�..»'Yfa `!: 1"e:.••tiS; :'Y.: .F �'{ 4f ••..at-,:.. ,w r. .�• •4•�f�1t�. y .,,i:. .i'.: T � Q. , _ a'S'�' ,r t , S ,S+TiC" 1 { . y€,.'€'S. qn:.e.�r,'!i5k2:'...•e° i z'iP a •:,: � ...�,. wt t _.. >,{>.>. , •''�'�••',' ,th«��%`� � .xr>'>: i e ,f: ;?'!�' 3._ti.. �;: A x J �< Y.'.ri ' , � .', , rlfiz.:�.... �� .. \:.• .. j.,1 Y. '., �x•. •, .a. � .. X "'bir , � .0' .!{•! •t s.. ,C. .. A.. ... �?..ii ...f , :.:.}, F'.`.i`! i�• Y',% }L';. '�, s S , .,.fr �.:,...r� i' . . •. !,. .. ._., d .., 3,..at .. P :.;. :. M �.. ... :.r t+t.•._>,t..ti r' 6 ..... t. .<. t >..t - • :ea :... & " ..2�<' 7''iiar..x. •r^ t'.c 'sue.• 'i e i , .. .•i.• ._f- •i E �i< A ��.``. � +Y.. � .r'> S... r.i .xr. a. ., x.k-: '-h: •I""YI 4:.Y ,tY "e� �I ! .. a:'.mi<� < :. V.'r: :":.;^::-..• .1 < .. ':'.�. 1 I ... 1 si,A S.. t. -t::'1:' ffr «r k.,.. •it�r :t•, � �� r ) R,,. .i r. «..,t . ,.r .}�.. ^';Y,:'•'r,'{ :;<� :f, . . t . ..r .• rt i '. 'f .?� - t, Jt . i,.. , : i ;`. }R , : •.: .:.: _:: i••e .. .,.:_ >. 1 _ �^ 3 t r ! w . .i•,,'k • � » .,. f't.. ,.� , >a:f <..� _ ' tt r . t t • t . e y; .�:. n{, .#� 2:.l:•:, y ! '.... ... ...;... }cc., »:"tir •b., !. --tiNSaiS!r+.• » }.: 't:�S• .t,•,.. ., - C er'�•... r� "'•E , 1.>,,,t '�it. 7r''t .. i.... 3', ��;:• .;,! - �, i, `.z�,. A. ,ni :;y<'r. .�',Lt•'�lb::,r,r is ".ae• •.:Hf a `it_. �.s 3':•�, 'f : .l . ., }�:-�• �:i J. -< . sa.. . 4': , i ., - � YA.,•. e... f : '+t iS• . !• , . �'.. � � ..., F �x',..:f•: •, ri. ..r.rs» 't,�i:. , .i •'1.t4''• t•' fe:: ,t :. ;, .: ,�'.•":: ...:. ... .. ... ...... .. .•.. ..•1..t. :.4v t. i• ': t': ..t ..`•.. '}!e ...,..F' '4. � •.:� 1,,�� 1)1... 4-S., ,t .♦r U t� ` y •1•r�l.. •l•»i � ',<. '.i-.e t<-. i�•�.. Y•:f �}`�S�rh .1 A.. ..•. S w .. / ,., !i. µ •. : ,f .. w. F .. } J. Y.Y Jt, 1� .Y P..•.. !" . .; ::':'-:-.'J'::< < .T'• x t >f. ..._ .. .... :� ,::'". /i.:: Y:,'7!y�.,. -i" '{' • .. .:'%.. ( ±., k, »!'.:. ., ,W v�Fk. �., .• .art.. . 4 j"TF alr3t .. ,. i i. t.- �•'`' ♦ > . L { -.. a ..�., .. w, ♦a'. g,,. l.:�•}!.•t .� :bLrf..�{` .�•. t'? .!. ,r':'.3 '-'^a �: :t.sf .N t. f. .v. > !•.' ,• , .... it .. �:1..:..,., 1- F' ' :}.. »F. .�.f ,{ , .•,� . tom, ,,. ... :�€ 2� .:a,�::.drt "'k:l.: 't •: r a•� '.� ry.: .C'. .. ta.i:;",F.,�'t� i- ! '. 2' .it :1: •i-0». ti: -'�. i• F. (,�' ..,E''a. ..�,:: ('� •: 3-:: �.:. ifztt' • ,AF'<:fr«f . 1:�•:� •. d• :1 ':.r.. r>t>A�''"�y'' ixt. .�,?9.px'':,r. •0. ♦...St,4.•Y»:��i. it :.'.: .t, l2J tiy7 Ny. N � .i/ �{� \, ��'Y:.rQ•. q.p?4a! -i � !i. 1 Ar. y4i a$"SIS v S- J} i+ F'' R6 ¢ }3: .y't Xt v3 1 f z•a,','! ax Irk. e s.^?"Y, s '!rY, �E{q`P'6 1 ��' 2 i t •tyr7 l,kti..f<..i. `iy+°�i:°--rO o,.> .:{. ., ,;4^''.. -•. 3.j:�?r �. /� . "�<< it711 <'rx J !+*�:nr .:.. '{43� fn i•(r a 'u r - A ♦ 'fi' R P $r.t 1 it i?,:,>♦' i:• . w8: ...{ ."i?�3.r�i: <:�x i'�i ..{.. ;>.FaY. .t:�tY>;. ,,�nr4:. ^�•:>.{. ,.ix i,,�l.i•t��� it'i b, , T i •^ � G t J p ! .t'.,iK� i� % i +t + h� tr a i,} f n: y A bc� r Yr rt 4 ♦� � >;fi J{ t t£ s � �•�' i d„ f z r S 'F,. Z'A i' (A 'fir tY � } <4 .zt .<= 3 ♦ , 6 ,,«i I r'N 0 0 - ii'i ,. t S t. > 'T�r•.« G , �< , Y of " , r,>r t t�i�t .r� J ,!!��?t4 �r,!! a 7t t,T.OLOTI::,,i«crr �''•.t, ':t••>§�.::.;(�•• t,• .t, .. . .. ... �'� ,.y �.f tr I G )t f f3,� }I'}l f.�I,iJ/ J <AJ r i.•r'1•t>f. a } ...t �i `� a+3>� �i �i'� fy'� } b W�}� eY S r}at r•Jt:{,r�,f r ' 44Ir1 ``ir R''.i�l �•Oi 4 f(.F o 'y'S:Y... f: r<.rjr�r Id 9 i tA'tt + ✓t{ rt; ;t,f -.: tt T?,it •J• F r:f.a.t>tt3,••-i k ';.,. �brf,.a,it% ,_ ....•.i .....4.,,: ra3 a;i;.f,•-. fd v. f.. ^r?':Z {: .i t'G txt�^•t 7�'ayj'j t.(} k'ii�'•'rt E "a � ram'" } { 1 ��' � r fit) ifi+a•. { ,.r. F t ,,��Sei'r�N,.eR a,t.,{, •irt Wiz, 3�j"� ltl�i,j7 iMv�piA�� %i i' > 4 k`� ��f> ft �Rfi't ' } 'ia X !.) t 37}f�{ (r ^Y1 •1... ! `L�Fa'[ii'! r'SjR�fi„ AQQQCCC������LLL��- O o IMftFt21 r �e•4� il"1�S e .{ ye .r .iY4 'it ''� � �'tA>'a! { � ,� !r•�y�s 4� a it r� t! S JR� �}-C. ��.��1> �� r y01J�Af Y, t S F'{vF^�E.�iYKN . eii� iv .9'�c t>t1a 3» 'v r.Ft •1�>•, a•<:.Jt':•{,!i.v 1PIt•S 23.gts g :!'7 YI .,t ,� cif (.t•'« r�c.t3 .zt ! � .zs:,d,..,,, .. r: �p.� � ; a,:,A{<�•%J ..� •.:E•-•a�e.i rt €� 1 r E{ f � ei. tr!. J•,ytY «5�1+�� � -i , 4-i 3 � .A P �iLS •�. {. ,`<tt't'13yyy ,�/�J`, ''/`j't .fit• yfi2 t3 t[J M.tb., �� 7 )�.f+�{,Y�f"FY"r. . 0 O �fr, R �'dx?r; �s''"'3 ? r 1 fir � f';'t'P... �>{ 3 ;1•ti{�i� h�S ! ; 'ii�lt:: r� Z:'G. 1T• <,aa Y?e :S +! , t _ VE4� � s ti{g a .L7 t:♦;i:i. �. t7r461� i�t•t M it' t"ca�' f _ 'j' "Ft t ;s` ^ 'A«4 t':t t ; �t}o' ftr x3 2a{��ffi w S Yi 4i ' so Jr {x t7y 3 iJ ii. { .rL.�k%I,�jilty�ear9r?$s(rrN ....t'�} i«t�'t"i,� aY. • >P+�•,' ��� � €' r a .�•It.• i i <�S'i ,...3,5 `�« i �A31] � • 3 . t.. :1'br �J'.^.'a... R t.:t. $o : ;. .l.\�.ft `...a: f ,' ai't• .'yy: �..• .•�f ,, .V`. ,r;.. 9.:♦♦-:r>,':.: f .:,:' > .if .... ..*,; ,', t }.% ty r.."* t w ..•:A- .�~•�..Y k'>4 ,.. 3\, }• :�M1< ,•ii•f�� f- ,; �.t'1;�.. •;i of : .1..; } •i .T, .Y.:. 11f' w ,. .. '.l 4 x. V.t . ). T•t a r. V .V ., k. 5 > J! Jtit. '>{'.. �.• 'K-.. ,. ).. y..e:, r . t.: - f:.;r fit: ,: T < f ,.i .,: .. Y'.�At: TA2 ',P •...< iA„ • .... , ;.. <L ! : 1 ) >4 ,{, ra•;.!. ' U'• , e'°." .. r•. h..�'. t• .>r ! i ..S . i A!t>• ..<. ...... ..... .:. ,e '�<3l.1>{q..-- �. Ypa Y, /' ..�t Y :.. w:..cA .,>, ,.. , t .. F � R:..x-:S ; .r; � t..f -•jG i "i1-i or.! Sfi i. .i• i� t ! •.rid:'r .elRi �% `Pa':l.f p ;>`-t+.i'i.: ♦ R V •59. ,4�`' 3, k. ,,1 F. •: ".:: K} .r. .. 7 .. ,. .. ,�:. iA :^r4i.'.rj'Yi�,I�A��A1-.:::fie: !��! •tt... "` r :3 �' •.{`-'.•�i i.,.. ^ .•di' a .; �1, ;!f. .ti 4:.. -.! .:=yy.{r.. •1,+f5 -i v': .,, .z ,}.«> ,.t 1.. ,; .;,.��.{..,_, i t ::�a.,,«n,..... . } '.�S':. r.i(.:'--.,;:'k, !t� - '!` � J i•;''' : <i•• 3 ..fit .;�� .v^a . '.4. .•'•� ��� '� ;t! r � r�rf t ..;3.l..tt..tt v !• �':.• /'1..,n.i� ;«.7i it ';T '. }•et<� ��'.; t..)•F�:�•Y... .,ty.S T. .,>} r x�::..' fa '%f. ■.• i r J«{.A'.r st •'?: A''; ::•"hCiE!'.i��y! .} , .f•' .b S i'. k a. A •r% v k. <I :x.' 1�., .�{ . ., I.. .... }t- 1T ..�/�.. ., �. ��. lY %r. Sr'1 �.::t' >i:4�� ����.: �Q� f. ��•iW'<.' A,. .I.t}:r >t..:.:i ... F• T, ..t». 9 ra: l2 h'. :a�. t 2 x �•• ..... .. .. .r ,. ra L ...-•.., .. ....:«.:f ... » .. ..,.:;. j ..: ,. +.,:'".i:. tF,• ,,.,.. ;y�. i .,t : r �,j■J � {„ .w,rf5a.f'�j:. ... eS. .r .��... r •. .- < .i'r. vY • <....... ...< , � .. .. .5 ... 1F. :.t ;.. .,. .. A.. ,..• .� t ,...{{ . ,� •J �, .t,.a .,M- h 't i > "CC� t• .�.• �•�' .t . . :Si n�• n 11'r. �...r t. .. ,t ! •`r F .t. .e.I .4. .J.. .�w ..'i'r. r�,Np !t< Y.. «v• rr. .y•2♦ �� +-a.•-.+.f.: .F'r.{. .iLf!:• ji >.ati' �. vft.t � r. R.•y.• 'LY„ . t.. A �r ...St�SR... <. } r•. ••�•, 4 -<,:. <.:t±<t+..._. �.... •�•• 3 rA s +t � � Y.,x a .i, .. y.•> �i'.r, n'2 •4.•r ...a){• •e.• `i ..+ f.Pa. ': A,' '� .�.. ••r:','•'i {A.. ',:.s- � 'Y • R: }i�.Y "b � i � !J i .,.: •� :..f,.:,-.i�F ...... ...... + .. •..;;.:,q .Y=.......<. ,M. .b... r>..wr. ..8. .k. '•Rr ! . )S.Vt...J 'i%1' S .. 1 ,. A ... ,..,,.., :•:n,�':.:: s:!:,: r.aa;, 1'f, .. w •: . >•, f>,�t ;ha' <•.. :. '}. t. .. :. > � .� .i )�. .. k,`. ,. .j'Ct. .. ! .Y,.; .• a ;...- .n.i.. •. '•; f.9 :{{ �.• t•. .� ....� ..� ..-.. �,-�� t,!«,. '{y.�;� .Atw. . ., - - •. •.•, f .: •1/Y 'M'4. L}...«..<.. I,, ri;t.t � � - Y. ei'i ::!'?:.'•": x.i. ..., A..d .,.... ;.f •, :•.a,:: I , .in. ..t,: •»,F,,;, zr• s,;a • :'iap:'3. . �•' d .. r ..r. ztl''.s )... ...�..•'. �2#" y-:!. Lf <: ... ,., ..... . .. f r7:^.f: rr ;i...v.... . R .. • .. .. i.. ... vy .. ..... ,.. • . 4 J.. .,., .> :: _.....F''t .. ri.i ^'...< � c:.':---......:: • ,,,,,f ..: a ; n : ft . z ---'. t .. .,• ,...r - :: ,.) >>§ ..,.:�..+:i .,. t,:. .;; ., , tt t , >•: t,.. .. .. •L.^'j. 1. +w. .. nt, » ,,111»'. .... :..� .^y. > ,�j'.I� : h.I[• t. .... .. ,y. �' ' i .f . ._.i si..<...: x •: wC .l ! ..�6>:.d , :,t. .:. - ::, i.-. ^w *.. ^.L a, ti .'a• ..�, . ,°S r• Y : f. k :: t' a .:v, 4 I,!`t1'i :,, y4 •'«-: S x'` .:<'•:^< t r„c.. - 1p Ct;.x� �. •.�'43.3 �,,r�.a ;f �'.:�..j[ qq�� :>S .1 ✓:L .x....; ,';• •L a/.:-• .�. pNN,: .).,.. J .f, �i>- .<S• �b ..•YY:: 1 A T �y�.lf,� > .i p•.• -r;:rti)r �w.r. y5.!!n fTy H.. �'t X }'?S: �'�3 ati5r 'F- -• a ..... +�. >•t ,.i ] �" q J.:�i.. -...: ! L• f..�.'. idt� x_;,�z'i«'J ,f 1 . % •." f ra J, j t ' J' � T $..:.t[j .- ! "li... :.1. «.1 �y(r w «'. .:•)', �'l t•� :%YV :.,r,. }. ..i,. �� . ...ri?... .tA ..+�'. .. .lf�• .. .. :. - .,..- .. ..» ...' • t r .r A «...•.�.,4 .....�.• .... •\ ., i.i+.. ... ..... .. ...• . ,.. ,....i,.. ...! .,.... .l. ,r<.. > ,i'.) ..'1... i Yyt. .$ ... •.. t.».. Y. r.zf.... .$. � -•��J ... N- .., , >K... i t ..s •. l\++. ... t. ., t, ». .. i'H" a •, .. .•f «.}., :•.••K.,f.rk•� vVx S._, .�...,. . r :.f ,f. f ,. . r•,. 'i ,.. .., !:•. ... .u..-. .f+ ,. S .. n,..�.f .{1. )•,: ... :.f2.v.J.}}. . e... >.., r. ..k. J,.. �cr�s .. ..a ..1•,>..tit. '>;. ..r. }t ... .::'• ... J.. .\r. 4. J>.: •.e.. .:+ :t>: n�f-=J, .I: 7t � ' .. .: Y,.. . e,�,v.; .fr :t.:. ,..>ii .:..•• 1,. .3; •i?!•:,f. .. .r'IY e..". y .: pe.t, , .,ri. a�L• , <'°''t'\11-..., ..\ t. ,•r'.. ,f �; ,! ,Y ;T.• �}• { s'+' 62. .r�fu>, .fJ-in;F :;j6: ;. Ito v:•W,; �•r tF1y ;t!i�•'w f, J. a'!k ei: wJ'fo� s ., . ..i <f.: ., ..: �t . 7:/,... ., r. r•,t f �3i lib.. qiy ,�.')•it ,,. > �•� • J x. }:l •• .�r^ y,t .}if tar: •:a t",•,";z '' �f. �..�,� <e� F^t ri•'�` .!- ,) -+.. .. :.'i'.' , t<,':•. o ,-: -...: .. °'a t , 5 � « , ati ;„t : tee{' ,.•.`r v� i,..; a, •::�;r1 .t , ,, •°:!/:?:• '.:a,Ay!• ;j 'x':e , :a •c •:v �rt'..r•FP s. ♦ r.. . ,'iw S q ..�'.S.il, J�#.0 • t.' <' %M w:i.t,lv.r M' >•?,?-.4. ..f-•t�..•: • �)' C�:t > i•t�9-,y'�;:,�;�;,kt�d �a1;?•�j} ,p•,�w,a,.. .� « •> ;f i...r �s,. x�:•,''f ifa}:'i',t';ati�i�l lf:f'•: Brat 1.: :[ J ! y i '''1l�.N JT J}.. �... y. ft t f;h • 2.'l i'S%Y,.r'.t.Y L 1«•,}L > is , ..:. ........., .:��..�«••1i. T. ".Ml.>iii•••,,,. ,o: f,, r •..f ii � hM.� .i4i .:4:y fp.:J�'?::�. •y� $0.00 4't3t1. z r� � x A t i�Ja•f. ++t ,,ttf°vir' i d;rat ;.SJa6•B 'l a} -� 4 A,•y 'q- .yiY ' ^ „S� � 1 t f � r ! A .a t iQlp� � b 'r�,^. S' �' `tgyt'rr •r ri.�,4 -Y �!t' f t ♦ Yl1 C� { ,tS `'t •S ) %'ft•ia i ! •i,V i�T'<1 4 yy 1 - -{:•,' Tr rr �.,y �I�,fia,�t' YfrJ } ii't YF * ' p ( rtv > i M in $0.00 0 0 $O �I�J°!>A P�( ..th..e'2oY Y r, -w. l..'tp!i 4itr1.:R}b. A.,it... +,J.if{ 4j ri,>�+•G �f�ii r i.''ri ,)S�S 6[�� 4, 4� t !'!YY ,f,t •f'f'��nn,, •i .t. 1i :2 .lM !%.'4<tit. .i,;-..f '�••�<4•If,>e :le'27?.f� • -1 �„A > rY .t ,jr� ,''rJ I't a. to r �'C �,R Jt' �J6 ,,rl V ,Sx }VifJ.f '•; Nfi s lkrw� �`'tfQ14> '� /°�� r �• o 00 �0 00 • :csa•�:'.S»+'l ,.; S-{..w ; iii•' ;I:c r } ii.l�. '! i��ii �rt3•'�'•• #Sx.,. t, i vrt l j• ; ,r tti>ka�, Fr�1. �'t:9! - t�Y'3+77 xii� i;fl•°f i aa•; J rA •�1 'r`!)t� Y :fjtia• T i t t <t , �fYh3Y Y e; r�t r,,}J�q t�a�J •f,�3 (7 f fi € 1R Y !'�i. �J tr . � 1 ) ! }, �dE. r t t : [ E ! t !{ < ��! `G■p a !Nt T ,!i t ?� fr �p �jt► $0.00 ' l i `t ..i ' Awf3 t<�J, \ is .F �1 3 . i� ix �11ai F tlJA >•'.i 1� •p •.f3.it,� �. .t•Y :: i $o.00 ii •t<,'itai:•:,3„}4Er,'r.ri8:: •e !xt.tii!.,.J.:Se..:..rt. <..Jse�fg:• f+.t!tt. F)?h(;�: 1'tT N. ij' i l�r ,,,�f,7 •I•tIR kt� A$lYw ��•t''p. �. ttAi_ J`i. .tr4 it •:"irt <'tj\ '• S ,i'4S w4L4 ... ��3 M{ri .' 4 i!1'.".`a'•w:r» IP\'/.. i p.j N LTi k fff bY.' } 1 �� tS.ILT % f /[ , 'l y;4 D X'r ( fiC:>K.r•• r f4_t a++'.ld;a �l,r3 Az 0.00 K? t3` '^ ♦ N'«M, J afar ,<1J ,7,'RRt�t�tSi� ; zi�`f� S !C ii� t J4.. M• > FYl�� � iit�.<•-� 3 >...• a t > �r :! r. , '. v . �,r a•I k'. '1 .., �1 • $0.00 •ys a•r• ,G k+t,3.s.•�•'if ?> s ir•Cw�aN1, ;: 3! y,1•+}a•': c•;; '' .�,��• :.5!{a:.l,,..lts�'. t <:s �•;. • car rl�L�'� s '� t !, '+.f 4�xL° 1' ;i � zr al ; x'R '�rY.'•;,)i' �,cG . r�r'><"i t�;d'' :,f:`s !� \ e I/ ""�,,�yls�i• ; ; rrx tw ,• w.irar 2 s} � tt AAA � { Ja '4sN+.,t T`o% s; , $0.00 , : p- --tZ{� ��it, �,� : �t :W-� x1 kf 11,t.SJ.vj'.eC:3^a�,,►ir}yMru� ;� 0 00 �s Page 49 of 99 Page 50 of 99 E . • .. ... .yj,. �`. ) 4. .-r : .. ..] .. .. � �! '..... • t rrtt q�� < ,fV 9) e,i r t ... , y .: its t 4 21 }• - S . » ,. . Y ., Lf . , r^S. .1. .. ... t. . N . ... 1:..... .� •�' :'n t,, k.. .♦ Wn _.i :r, .!.' '>, ' .'�. 'Y 4Y. ! �•< w - !, v t t• _..t.L.. ... -. ...i / .. 1 . 4... a. .. r i iY;t•. .... i, , .G i kr ..• ! •r.. •. i ? � i'..k.. .. A. > V 4 '� Ki. Y i n 1'e i1 H . ° 'ti...> ... ! .NS` 1- _ .... , S -�! . 4f 6 A, . �` r: :'i.i i'. jt: �.`. .._ ,, .f Y". ,w>4. �' _. _ .. A• .. .... .. ^?. :tf: ;� .Lyn. •::�;."FAreh .,i::=., .�E :�_ ...t. �' •.r !l.Y.\.r::� _�►,'{;if'c:d .. )r.'� ; ..« .. r .k.,r a r>r.•. ..f..r..>. '>.:.. . , . %. ...l.. a..z .. r. ,,� £t • , r w ,,.. ! .. E .,.., .., .,��•' ..a t. . a •i•. ..a •fl:: , > 's-.... ,•,, ds. :. ,... .... t, ,K$ �! .. Jr. wlr , ....Fr.., .3z• �. .. £'%.r5 �s:r, .t ,ra..;t-. '.,:•<_•' r.-'tti r.:..:,••:.,:s; ,ry,tt, .4,• o'e`..:cf'�,� .).t.. .•£i.;t� X i . 4 '�, ss,�, .< i , a A..•. i , 4 . •j• E .-f. . y _.{: <'i.' s7 •j`j1. 7 .•.•.."('+..1 7t, 'K •.: .. .,. .. ..'..... .:L h .<...t ... ..... .-.. .. tw. R e,. ........ ..r ,..• t `:�t. .,'.A "?.• - «)�!. i. i. tf!t :: h'.. qq f E, t . E .,.£. , 1 .A . k .. • r. I. .. ?4 .. .. A.G. ...... ..[ .. .I ,. .. c..... . . ... 4 0 3. , ._ :•si:!'• •"t%3,' .1 .. '.•9 . u' . : . ...�i .� i..,. .... . �, �� C . t a x.. •m• 3 •: - _ .. r_ .. ..t'r �': ii✓ .:•.< . 1 •rt : 'I'�i r 1 'r' ., . .i . 3 ....r ... ... rl,.,,�fi,, .. � •...... 5,.^ .. .r ,t, . t. .: A . - . ,N , r.t ., i . F _ .� �. _ � , .r. ,.*� -i a _ t .. ..d . Y , � •., Y3 tr <f• ' •� :' i : rs:; :`4 ait' . .s'if,.o .•. .•iY d. ,.:r , .r, ., ?c iM1!+�.,... ... .41'wr: t, t .,. ,..� .t .j.s• ,. d �:• •'>,,:. .I:. ...fi:• s•. i' .Y. �.... .< .4 +tk=". ,�i[ t { t ..\S � ..- t�.. .. ,.. E ,. .. 1 f. .,»t .�.. >... d>.. ). .. r.: 1 .: •r" .t,. ";;"h- "t': 1 ::}ir. :1. Rt t..�« .. - ... r i ; L..<. ..Y ,.. .Y .K . ..• , :. t..r .. .. .. •tt , � �SR t.l, p h } � kr. ... �> t ,Y ;tw t �..♦ • l..t.. .Y ;;: .. tl ..F.J t. S. . 1 J r, .• ` ( .. .. .{ .. .� ., .. r.:t=. w • ♦ , • aS'i�. n, t� ]� r1.'. ..' f.. ! s �v5t . ..� � � .«t. ., . ... ... .. . ... .N ; .;- . . ..{p;.. L ,.h. e., a'. , r��, NNN i ... .5 T . .. f ♦ .'<.. • •, lt. E'L % ., /. a..R; , . . I..£! t/i . �< ! x : •!.• t r !• ( .. ! > . . : \: f r .... 'E'. . «i .. a .. .. ,< .. ,. r • ... .fi. ,«. t... •n,.. ..+ •) h.. .i. k ...ri'c. n .I. ♦ t- I: .K/.,!- t !t,t Ftn ce. .a. � !1 .4 a n- �i x .r. ;`r: :t� .)�.:v.v. aa :•a. r4' i..£ •i•,£:: .t•ri: , N,, --2 i .:1. 1.. 2 :,(: 'J.� �` t i•. ♦r .! it:: •Y4• .,i . � .. .L , ♦ ... .. ... ... .. .... ,. .... .. .. _ .. T.Y.. .. I , s.... .rr. n.. r,....r 1. y '.£,' .••{': �'E•it ^ . ). . "k. A.t t.e �r. a .t .. .... ... �. r_.: t � :: n.. 'r -.:..� �� •... .w 4 'lr 6.:Ex �'3 '. ri..:..�;�•E: .• , ., -.3 ♦... ... K ��.t - [ � ... .. ..L. �' ..j�(. .f .?. .. .. r.• ,. }... I_ i •+1. 4. � E' .. y'.. .•.r,..,' �3. Y^. Ir.-i. • f '..... .. ttr . §. _„f,!J.- S.v:. . e •rK.?: v , w,. ;!1 is {�i)>i. ♦ ).. 2!.t +:^f:.v .r.•. ,!` ■ .: (�� �'!nr :F...iroi %f:. } ,� i •M,, � , �t - 3 i t ., F1 '�.'r�,J\'\. kY.T:♦[ `¢«.fit -Kr. ... .rd:...r:/ ..,. � :%G ;'pf. •c., .-i •'.::i, �:. •iY.•:. ..A.•t.A, !r ^!• "'� .! h .) .;i £!•. <..£..R..-I,F..... %. >. ♦. i! yi.i• dS t: • :' : ! `•?-: � �-:. ih•...«._�t.w�K,.a..., n.. c. �>`j �., .,. .. .; As i'a :: E.. p.. •rc t.•a ;p ■ •� ,.. .: �. ,:r•• r; A••'i ..�. .Ai, r �'f . ! j.A \t .i� .:. £' ?i� r,\).. .. Ali :._. •. ) st > M .- r. s � • }.. --.s ... .• ,$, : ■ t :::1;y,.e+r!: •,:.}! .{.pia,-. s.. rr•8;' ,: si S'.: p Y .\S'r �� £..-•.i.P iP !.}a....r .c , ..A• li:; �F .v r b4` __ m .: 'i•%✓'.•:� ' • f :.; r �.. .).:... i . ,,; .. :r..u.« " ; .; � ?,t { i i ^1: � f a%{ j. ui �,' . i'E A 7 t-lY.. i !' .. ..S`t1- .,... i .. {?T'$r d.. :•(: r' ��>> !•• >. ♦.•• .. ...� ......, _...F., .:...>S.Y �■M■ t<•.. , r a,.),..::� .v: ..r.£• a"'�_ ..t:�„ .. S .♦.:- a • r d� .. .. : t K .'E•{ .a .. 1.,Ki 7,Y•.Tu w1v[ ..v .S . .'Aft ., .:.. rf .J• . A%. > .....c..0 } r . r... .�.. • .: � �.. >S ! .: i•: ♦. 'Fr .M ,. t ...... .... ...•:.F,•••c •>,.:: ,F,..., . .a. ,.. .. �.. t.... . .. .:::Ct lt.;. •, ,'.•] iJr i<k• r• i).: ,•,.�.. � � :.:v... o1 '..,r :. .�<: •:r ::. j, A:.. .•') •'•E9 t•..t..., , .. ,�. ..E...1,. F ...Y , Y .!, .i.. ...,-...>..$ r.i ._ ♦�•K' s i i 1.... . .... r ,. . .. £s ! i. •eY=. . . h ;. ;....N :. . F .. . .t 4 .. >x ,'..:LN ... .. i i ,..v .. .), t .. 4., 9. .«d .n . .t.. li tL . : uw !iH:•. ).f-. .. ..: �\ ,•. !:.e 'M:f 4A Ai? t .......1_r. _,f:....�.�,a.....,... ,_....;;,. .. rt>. > , ....<-i.:••::�:.r.* .....:f. � F, , ..>, .� A. :}t .t r: .i.. .c.... u, � i'£rt.• .,.. �:%... _ , «. d •..�.,. ...... t 'i't ::.iL'r••-;_•:: E: :•: s'n.... :.....: •.'t. .�. .Il:rrF.. a:?i, $� .r*:• 7'n•.'. �. ,::•: D"-':: i`.•£1 t-.r>a't .'zt r:, ::izc::.. +,. ._. ..Ik Page 51 of 99 INTRODUCTION This purpose of this Service City and the County with rE hardware architecture ma responsibilities. Exhibit F -- ATTACHMENT 1 Service Level Agreements Terms and Conditions Level Agreement (SLA) is to clarify the mutual expectations of the spect to the RPSI system ("System"). Changes in software and ;e it imperative that all members understand their mutual 1.0 MAINTENANCE SERVICE AND SUPPORT 1.1 Maintenance Service and Support being provided are based on .the Severity Levels as defined below. Each Severity Level defines the actions that will be taken by -County for Response Time (IVITTR), Resolution Time, and Resolution Procedure for reported errors. Response Times for Severity Levels 1 and 2 are based upon voice contact by City, as opposed to written contact by e-mail, facsimile or letter. Should delays by City prevent scheduling of downtime to resolve an issue, County will not be. held responsible for Resolution time frames listed below. 1 Failure/Outage occurs when the system is not s30 minutes of Resolve within 24 functioning which prohibits continuance of initial voice hours of initial mission critical operations. notification* notification* 2 Failure occurs when an element in the systems 24 business Resolve within 5 is not functioning that does not prohibit hours of initial standard continuance of normal daily operations. voice notification.* business days of initial notification* 3 An Inconvenience occurs when software or s48 business Resolution hardware causes 'a minor disruption in the hours of initial determined on a Iway tasks are performed but does not stop notification case by case workflow. basis. *Does not apply to "READ-ONLY" CAD systems 1.2 The City Agency Administrator or IT Representative shall conduct a preliminary error review to verify a problem, determine if such is the direct result of a defect in Hardware, Software, or other and the direct conditions under which the problem occurred, identify the applicable urgency rating scale by which errors, problems, and other issues are scheduled ("Severity Level"), and ascertain that errors are not due to an external system, data link between systems, or network administration issue prior to contacting County. 1.3 City shall assign an initial Severity Level for each error reported, either verbally or in writing, based upon the Severity Levels defined above. Severity Level 1 or 2 problems should be reported verbally to the County by City IT Representative or Agency Administrator. County Page 52 of 99 may modify the initial Severity Level (upgrade or downgrade), in which event County will notify the City of the change in Severity Level of any City -reported problem. 1.4 County shall provide telephone support for maintenance issues 24 hours per day, 7 days a week (24 x 7). 1.5 All requests for support for the products specified in this Exhibit will be logged with the County Customer Support Center ("CSC") via telephone at 1-954-357-8686 or email at selfheII2 broward_ or_g,_ 1.6 County will provide City with a resolution within the appropriate Resolution Time and in accordance with the assigned error Severity Level. when County diagnostics' indicate that the error is present. Additionally, County will verify: (a) the hardware and software are being operated in conformity to the System Specifications, (b), the hardware and software are being used in a manner for which they was intended or designed, and (c) that the hardware and Software are being used only with County approved hardware and software. Resolution Time period shall not begin to run until such time as the verification procedures have been completed. County will continue to provide service support under this Interlocal Agreement until final resolution is determined. 1.7 Should County determine that it is unable to correct such reported error within the specified Resolution Time, County will upgrade and escalate its procedure and assign such personnel or designee to correct such error. This will include automatic problem call escalation to appropriate levels of County management. 1.8 County will extend, to the extent permitted under applicable maintenance or service agreements, any and all maintenance service provided to County by the maintenance or service provider to City provided that: . a) Any -third party hardware, software, and any other related supplies shall conform to any and all applicable industry approved technical, functional, and performance specifications; b) The System is free of modifications and alterations which have not been pre -approved by County. c) The System has not been subject to any misuse and/or abuse, whether negligent, intentional or otherwise. 1.9 Unless otherwise specified herein, any and all suspected errors will be investigated and corrected at County facilities. County shall decide whether on -site correction of any hardware and software error is required. 1.10 Any third party equipment supplied by County to City shall be subject, to the extent permitted under applicable agreements, to the manufacturer's warranty for that equipment. 2.0 RECORD —KEEPING AND REPORTING RESPONSIBILITIES 2.1 County will provide verbal and written status reports on Severity Level 1 errors. Written status reports on Outstanding errors will be provided to City Agency Administrator or IT Representative on a monthly basis upon request. Page 53 of 99 2.2 County shall provide annual account reviews to include: a) service history of site; b) downtime analysis; and c) service trend analysis. 2.3 3.0 County will prepare the following reports (for PremierCAD software only), to include: a) System Analysis MEASURE: Evaluate disk and CPU load . PEEK: Evaluate memory availability and use VIEWSYS: Evaluate use and availability of PCBs EMSA/TMDS: Review logs for hardware reports File Sizing: Review file sizing on changeable files b) Pathway Analysis Evaluate effectiveness of system configuration for current load. , Evaluate TCP/Server statistics. Evaluate efficiency of server class maximum and minimum settings. c) Performance Analysis TMX Timings; Evaluate application response times d) Printrak Technical Support Analyst. Based on an annual system performance review and reports, the Printrak Technical Support Analyst will review findings and recommend software or hardware changes to improve overall operations. MISCELLANEOUS 3.1 When County performs service for the System at a City location, City agrees to provide County, at no charge, a non -hazardous environment for work with shelter, heat, light, and power and with full and free access to the System. 3.2 City will provide all requested information pertaining to the City -owned hardware and software elements of any equipment with which the System is interfacing so as to enable County to perform its obligations under this Service Agreement. . 3.3 It is not required that parts furnished-by--Go-unty be newly manufactured, provided -that any furnished parts be equivalent to new in performance. County -owned parts replaced in the course of repair shall remain County's property. 3.4 City will provide a qualified Agency Administrator for the Printrak system portion to perform all functions as defined in the CAD Security Matrix or Printrak System Administrator's guide (which has been made available to the City). 3.5 Upon the expiration or earlier termination of this Agreement, City and County shall immediately deliver to%the other party, as the disclosing party, all Confidential Information of the other, including any and all copies thereof, which the other party previously provided to it in furtherance of this Agreement. ' "Confidential Information" as used herein shall include: (a) proprietary materials and information of the disclosing party regarding technical plans; (b) any and all other technical information, whether to a softcopy or hardcopy medium, including but not limited, to data, developments, trade secrets and improvements that was disclosed in any form by the disclosing party; (c) all GIS, address, telephone, or like records and data provided by the disclosing party that is required by law to be held confidential. Page 54 of 99 . a 3.6 This Service Level Agreement does not grant directly, by implication, or otherwise, any ownership right or license under any patent, copyright, trade secret, or other intellectual property including any intellectual property created as a result of or related to the products sold or services performed under this Service Level Agreement. 4.0 SOFTWARE UPDATES County shall provide software updates, to the extent permitted under applicable license, maintenance or services agreements, as defined below: 4.1 Supplemental Release is defined as a minor release that contains primarily error corrections to an existing Standard Release. It may also contain limited improvements that do not affect the overall structure of the Software. Supplemental Releases can be installed remotely. Supplemental Releases are identified by the third digit of the three -digit release number, shown here as underlined: "1.2.3". 4.2 . Standard Release is defined as a major release of .Software that contains product enhancements and improvements such as new databases, modifications to databases, new server/requesters, etc., and may involve file and database conversions, System configuration changes, hardware changes, additional training, modifications of Software license terms, on -site installation, and System downtime. Standard Releases are identified by the second digit of the three -digit release number, shown here as underlined: 1.2.3". 4.3 Product Release is defined as a major release of Software considered the next generation of an existing product or a new product offering. Product Releases are identified by the first digit of the three -digit release number, shown here as underlined: 1.2.3". 4.4 The City will not be required to pay any additional fees for County provided software releases. 4.5 At City's request, County will provide a current list of compatible hardware operating system releases. A list of Software Supplemental or Standard Releases will also be made available at no charge to City. 4.6 City must maintain all hardware and software connected to the County's network to the latest compatible revisions. 5.4 ADDITIONS AND CHANGES 5.1 . The City may request an enhancement to System functionality. Enhancement requests should be submitted to. County's Office of Communications Technology (OCT) for review. If OCT accepts the enhancement request, the request will be referred to' the Program Management Team for possible inclusion in - a future project. County OCT will provide a response to the enhancement request within ninety (90) standard business days of written receipt of initial request: If accepted, a proposed Project Plan will be, furnished with any applicable enhancement fee. The City may choose to pay for an enhancement request that has been accepted by Program Management but is not viewed as a high enough priority to include in a release. Page 55 of 99 r i 6.0 ACCESS 6.1 The City agrees to maintain any and all electrical and physical environments in accordance with System manufacturer's specifications. 6.2 The City agrees to ensure System accessibility, which includes physical access to building as well as remote access. Remote access is required and will not be substituted with on -site visits if remote access is not allowed or available. 7.0 EXCLUSIONS 7.1 Maintenance services and support not expressly listed in this SLA are excluded, and County shall not be liable under this Agreement for such services. Exclusions consist of, but are not limited to: a) Any service work required due to incorrect or faulty operational conditions, including but not limited to equipment not connected directly to an electric surge protector, equipment used in a non -office environment, and equipment not properly maintained in accordance with guidelines set forth in the manufacturer's User's Guide; b) The repair or replacement of parts resulting from failure of the City's facilities or City's personal property and/or devices connected to the System for interconnected to devices) whether or not installed by County's representatives; c) The repair or replacement of Equipment that has become defective or damaged due to physical or chemical misuse or abuse from causes such as lightning, power surges, or liquids; d) The repair or replacement of any transmission medium, such as telephone lines, computer networks, or the worldwide web, or for Equipment malfunction caused by such transmission medium; e) Accessories; custom or special products; office furniture which includes chair(s) and workstations); modified units; or modified software; f) The repair or replacement of parts resulting from the tampering by persons unauthorized by County or the failure of the System due to extraordinary uses; g) . Operation and/or functionality of City's personal property, equipment, and/or peripherals and any non -County provided application . software including service of any accessory, attachment, or component owned by City, whether or not installed by County; h) Removal, relocation, and/or reinstallation of System or* any component thereof without prior written consent by the County; D Services to diagnose technical issues caused by the installation of unauthorized components or misuse of the System. j) Operational supplies including, but not limited to, printer paper, printer ribbons, toner, photographic paper, magnetic tapes, any supplies in addition to that delivered with the System, and battery replacement for uninterruptible power supply (UPS). Page 56 of 99 k) Unauthorized installation of any software or hardware modifying Printrak Software and/or the System. 7.2 City shall be responsible for payment of any desired service and support not included within the scope of this SLA and such service or support shall be performed at the rates set forth below. Billable rates are subject to a two (2) hour minimum: $100 per hour 8 a.m. - 5 p.m. (local time) Monday - Friday (excluding County established holidays) $150 per hour After 5 p.m. Monday - Friday, and all day on Saturday, Sunday and County established holidays Travel Expense In addition to the above hourly labor rates, all other actual travel related expenses may be charged to City. Page 57 of 99 Exhibit F - ATTACHMENT 2 Service Level Agreements Trouble Ticket Workflow MTMr �rAMn (WM AUT N Wmdm Ileoe�ii PAR From CADk0wo As" YMi M y ceNcwapr s1�Me•>< CdMNsMb WNCwlbd IN4"4w Ii Yti N0 CaNATN.T 0, . " - I eeM+elpMeeeordere MiriOe NONauT�N000 Na»11NN Nw afer Munhr NMw Nwftr hoof TwheOden CwAower ilh �IpMe�ed q AUTO Pwb ew.rM « Ner SLA No Now r� «P-ift «» NOW 116 cMeeWlet Mhwbe� iwrd�leN InelwM In vm6b Won* EJID qpmpdft ON"ewAwd worof PM OCTSOME! t NA1 NO NeS der *Wow YM NJ1T > Nob1. All Smft1Cam wMIMNO&MINLvmdCft*OCT. s► NNb2:Rwblul"ttwwmCOYNNaan lioddramp�N h--lMM+MNM*. > Nab & CITY ffq bm amNt aWnlwiMw eonMNcts w ddm dw ft Opelksk TMAIM MLw •SMOWARDCOUNTYOn411W OMALANDIMIMPAWARY • :v► r MOIOJMIALICBMWAPPSY KIMIEI011110W MtRM anrrhr Nreel«M a uss".n woes aft i�+ OYr/M eneew Page 58 of 99 � Exhibit G Trunked Radio System Standard Oneratina Procedures Regional Public Safety Communications — Radio Sub -Committee Standard Operating Procedures For the Broward County Public Safety Intranet RPSCC RADIO SUB -COMMITTEE Page 59 of 99 STANDARD OPERATING PROCEDURES FOR THE BROWARD COUNTY PUBLIC SAFETY INTRANET TABLE OF CONTENT SOP # PROCEDURE TITLE 1.1 Fleetmap Standards 1.2 Talk Group & Radio User Priority 1.3 Telephone Interconnect 1.4 Private Call 1.5 Radio Aliases 1.6 Radio Model and Features , 1.7 Radio Auxiliary Equipment 1.8 Talk Group Names 1.9 Shared Use of Talk Groups 1.10 Scanning Talk Groups 1.11 Emergency Button 1.12 Encryption 1.13 Definitions & Acronyms 1.14 Console Naming Page 60 of 99 STANDARD OPERATING PROCEDURES (SOP) 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures Document Section: 1.1 Sub -Section: Procedure Title: Fleetmap Standards Date Established: 12/15/06 Replaces Documents Dated: N/A Date Revised: NIA 1. Purpose or objective: RPSCC Radio Sub -Committee ADoroved Date: 08/02/07 The 800 MHz system will contain a large number of talk groups & multigroups to support the various agencies that will be subscribing to the system. The System has multiple administrating agencies that will be responsible for maintaining the Fleetmaps and system programming for the agencies for which they are responsible. Talk groups must be configured identically by name in the SmartZone Manager Terminal database, Radio Consoles and the Subscriber Radio. The minimum characters are six (6) and maximum is 14. The Talk Group number of characters will need to be based upon the individual agency's subscriber radio model types, used within their fleet. For the effective management of - the system a defined process needs to be used to document the Fleetmap information that each agency is supporting. This information needs to be in a format that is shared with the other administrators. 2. Technical Sackaround: • Capabilities: The Fleetmap- is parameter information programmed into the. system infrastructure and into the subscriber radios to control how the radios will behave on the 800 MHz system. The Fleetmap itself contains the following information: Page 61 of 99 r Fleetmap Information Definition Talkgroup Name of the talkgroup & multigroup as it is programmed into the system Talkgroup ID Numerical ID of the talkgroup & multigroup Owner The actual "owning" a enc of the talkgroup General description of the talkgroup & multi rou Descri tion Multigroup If the talkgroup is part of a multigroup, this will identify the multigroup_. Priority Priority level of the talkgroup Admin Agency The agency that is responsible for the system administration for this talkgroup Site # access Will be a listing of the RF sites individually, and if the talkgroup is authorized Media Access If media access is permitted for this talkgroup Global Sharing The predefined global sharing authorizations User Groups = The subscriber groups using the talk groups, this becomes a matrix for programming. The Fleetmap spreadsheet will become a documented matrix of the talk groups in the system and the subscriber groups that are using / sharing these talk groups. 3. * operational Context: The System Managers will be responsible for managing the Fleetmap information of the users they are representing. This information is also shared with the other system managers; the ID information also must be kept. 4. Recommended Protocol/Standard: The detailed matrix will be maintained on the system database. An example of the matrix layout is shown in this manual. Need to develop the matrix layout. Each System Manager will maintain a master Fleetmap spreadsheet containing data on the subscribers for whom they are responsible. 5. Recommended Procedures: As individual System Managers make updates and changes to their spreadsheets, the spreadsheet will be e-mailed to the Broward County County Ps Office of Communications Technology Radio Communications Manager, the Administrator (for future reference this person will be referred to as the "Primary Administrator) of the system. This will allow the Primary Administrator to update the master spreadsheet information easily and provide the information to the other System Managers for reference and integrity of the Fleetmap planning process. Talk groups that are shared between subscribers of different administrating agencies will be reflected on all the spreadsheets having subscribers using these talk groups. The portion of the System Manager's spreadsheet containing data on talk group ownership will be considered the master reference for the Talk group. The disclosure of the Fleetmap configuration information 113s, user privileges and other related system information the security of the system from tampering, sabotage hacking, unauthorized access to the contents of including Talk Group IDs, user would substantially jeopardize unauthorized use, jamming, confidential voice and data Page 62 of 99 communications, etc. Therefore, the master Fleetmap spreadsheets shall be classified as "Security Information" and 'Non -Public Data." The System Managers may choose to disclose some or all of their own information to their users; however, they shall not disclose other Agencies' information without prior approval from the responsible System Manager. 6. Management: The System Managers Group will manage the Fleetmap information and the details of the process for communicating the information. Page 63 of 99 4 Standard Operating Procedures (SOP) Document Section: Sub -Section: Procedure Title: 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures 1.2 Talk Group $ Radio User Priority Date Established: 12/15/06 Replaces Document Dated: * N/A Date Revised: N/A 1. Purpose or obiective: RPSCC Radio Sub -Committee ADDroved Date: 08/02/07 The purpose of establishing varying priority levels for talk groups is to assure the most critical talk groups on the system are granted a channel as quickly as possible when the system is experiencing busy conditions. 2. Technical Backeround: ■ Capabilities The system priorities can be managed at the user level and at the Talk Group level. Constraints All User Priorities will be set at 10, as radio users change talk groups, their effective priority will be set by the Talk Group that they are on. 3. operational Context: Priority levels in the system will be managed at the Talk Group level. The goal is to distribute priorities across the systems talk groups in a way that maximizes the ability for critical groups to communicate and minimizes the number of talk groups with high priority. All User Priorities will - ---- —be set to the lowest priority 1evel-1 ------ --- _ _-----� - ---------____ _ — _ 4. Recommended Protocol/Standard: The Talk Group owner, or the applicable subsystem owner, shall assign Talk Group priority levels not exceeding the level defined by the criteria below. Talk Group priorities that are assigned to level five or above are subject to the review and audit of the RPSCC Radio Sub -Committee. Priority 1 Definition — EMERGENCY: Only Emergency Alert calls, i.e. emergency button pressed, will be given the Priority 1 status. Definition of an EMERGENCY means when a public safety radio subscriber encounters a life -threatening situation and needs help by activating their emergency button which then activates their designated dispatcher's -radio console with an emergency alert. Priority 2 Definition — Unassigned Priority 3 Definition — Unassigned. Priority 4 Definition — Public Safety Talk Groups Page 64 of 99 Priority 5 Definition - Low Priority Public Safety Talk Groups Priority 6 Definition - Unassigned Priority 7 Definition — Local Government Essential Priority 8 Definition — Unassigned: ! . Priority 9 Definition — Local Government Non -Essential Priority 10 Definition -- PRIVATE & INTERCONNECT CALLS: Will be used for Telephone Interconnect Calls, Private Calls as defined by direct point-to-point or radio -to -radio communications that are not carried out within a talk group. This priority will also be used for talk groups that are established for system testing. 5. Recommended Procedures: NIA 6. Management: The RPSCC Radio Sub -Committee is responsible for supervision and management of this procedure. Page 65 of 99 STANDARD OPERATING PROCEDURE (SOP) Document Section: Sub -Section: Procedure Title: Date Established: 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures 1.3 Telephone Interconnect 12/15/06 Replaces Document Dated: N/A Date Revised: N/A 1. Purpose or Obiective: RPSCC Radio Sub -Committee Date: 08/02/07 To manage the use of interconnect on the system. Although this is a useful feature and needed by some users, it must be managed to an appropriate level to protect the primary radio communications purpose of the system. 2. Technical Background: ■ Capabilities Interconnect calls can be placed to individual users of the system, if they are configured for interconnect functionality. Interconnect calls can be placed to talk groups of the system, if the Talk Group is configured for interconnect functionality. Interconnect is intended to be a BACKUP functionality to cellular communications and used primarily on an emergency basis. • Constraints o An interconnect call will consume an RF channel for the duration of the call. o Interconnect calls are half duplex; only one end can talk at a time. o A type 1 portable cannot initiate an interconnect call. o A type 2 portable can only place calls to numbers that are pre-programmed into the radio. - ---A type-3 portable -can -place -an -interconnect call -by -dialing -the -number -directly: - o The general public can easily monitor the interconnect calls and they are NOT private or protected in any way. o Interconnect shall NOT be utilized to conduct confidential business such as discussing case strategy with the State Attorney's Office. 3. operational Context: If a radio user has a need for interconnect, it shall be granted, but the resources impact needs to be carefully managed. Due to the risk of cutting off emergency / life safety communications, the duration of interconnect calls shall be set to a time limit of two (2) minutes. Only one channel within a radio system will be allowed the feature of Telephone Interconnect. The need to make a Telephone Interconnect call must be restricted to emergency and business related use. The City of Fort Lauderdale has two (2) channels available for the users that are allowed the Telephone Interconnect feature; however, they do not permit other agencies to utilize their Interconnect resources. 4. Recommended Protocol/Standard: Interconnect usage shall only be programmed for the users of the system that have a need for the Page 66 of 99 function, the primary purpose of the system is for radio communications, but there may be some users that may require a backup ability to cellular communications. The priority level for interconnect calls is "10," this is defined under the priorities standards documents. The interconnect equipment of the system will be configured to use the "overdial" method of operation, where the incoming calls come into a generic phone number, and then the interconnect ID of the radio is entered to complete -the call. The Fort Lauderdale radio system does not support inbound interconnection. 5. Recommended Procedures: The System Managers need to define and manage the interconnect properties of the RI= subsystem(s) that they are responsible for. Each RF subsystem can be configured individually for the number of calls that they will be allowed to simultaneously carry. 6. Management: The System Managers shall be responsible for following this procedure and monitoring the effect and usage of this resource. If negative impact or excessive usage is determined, interconnect permission will be reconsidered and possibly revoked. Definition of "negative impact or excessive usage is defined as individuals who are reported for using this feature for non -emergency and/or non -business related matters. Page 67 of 99 . STANDARD OPERATING PROCEDURE (SOP) 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures Document Section: 1.4 Sub -Section: Procedure Title: Private Call Date Established: 12/15/06 Replaces Document Dated: N/A Date Revised: N/A 1. Purpose or Obiective: RPSCC Radio Sub -Committee AW)roved Date: 08/02/07 To manage the use of private call on the system, although this is a useful some users, it must be managed to an appropriate level to . prot communications purpose of the system. 2. Technical Background: Capabilities feature and needed by ;ct the primary radio Private calls can be placed to individual users of the system, this communication is outside of the Talk Group communications, and is a private communication between two radio users. Console operators can place private calls to the radio users. ■ Constraints o A private call will consume a RF channel for the duration of the conversation. o Private calls are half -duplex, only one end can talk at a time. o A. type 1 portable cannot initiate a private call. o A type 2 portable can only place private calls to numbers that are pre- programmed into the radio. o A type 3 portable can place a private call by dialing the number directly. o Private calls are not recorded. o For the duration that a radio user is involved in a private call, the user will involved -in dispatch tTalk Group communication o The system is not able to restrict the usage of private call on the system, interconnect calls, which can be managed. 3. Operational Context:, not be unlike The private call resource should primarily be used as a supervisory function, if there is a business need for a radio user to have this ability, it should be granted, but the resource overall needs to be managed to protect the RF resources of the system. This is also a function that 'dispatch consoles overall would 'be capable of. Due to the risk of cutting off emergency / life safety communications, the duration of Private Calls must be set to a time limit of two (2) minutes. The number of channels that allow the feature of Private Call will be determined by the individual System Manager. The need to make a Private Call must be restricted to emergency and business related use. Radio users of the Private Call feature must understand that .when this feature is being used, they cannot hear a Dispatcher call. 4. Recommended Protocol/Standard: Private call usage will only be programmed for the users of the system that have a need for the function the primary purpose of the system is for radio communications. Site access for private Page 68 of 99 call is managed in the "Sites Profile Group" that the radio user belongs to. 5. Recommended Procedures: System Managers shall work with the user groups they are responsible for to plan the appropriate private call programming requirements for those users, in order to protect the RF resources of the system. 6. Management: The System Managers shall .be responsible for following this procedure and monitoring the effect and usage of this resource. If negative impact or excessive usage is determined, private call permission will be reconsidered and possibly revoked. Definition of "negative impact or excessive usage is defined as individuals who are reported for using this feature for emergency and/or non - business related matters. Page 69 of 99 STANDARD OPERATING PROCEDURES (SOP) 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures Document Section: 1.5 RPSCC Radio Sub -Committee Sub -Section: Approved Date: 08-02-07 Procedure Title: Radio Aliases Date Established: 12/15/06 Replaces Document Dated: N/A Date Revised: NIA 1. Purpose or Ob ective: The purpose of this section is to set forth the principle by which all radio users in the regional system will establish names for their radios in order to ensure that there are no duplicate names, and also.to facilitate intuitive understanding of the radio name. 2. Technical Background: • Constraints Every Radio User ID in the system has to be unique; there can be no duplicate IDs. The Radio User Alias field itself will hold up to 14 characters and the legal values that the system will accept are: Upper Case Alpha, Numeric, Period, Dash, Forward slash, Number sign. When agencies make additions, deletions and changes to the database for Radio Aliases the modifications will not take effect until Motorola performs a database back-up that will occur every Friday. The Dispatch consoles will not reflect these modifications until that step is taken. 3. Operational Context: With the exception of the first three (3) characters users are technically free to choose any unique name they wish for their radio aliases. However, since this is a shared system Radio User Aliases that are programmed into the system must have naming conventions between agencies that will not conflict with each other. 4. Recommended Protocol/Standard: In order to meet this need the Radio User aliases would be prefixed with an agency identification that would be unique to that agency and would preferably readily identify the agency the Radio User is associated with. Because of the number of agencies using the. system the prefix would be a minimum of two alphanumeric characters in length in order to avoid contention between agencies. Regional Operating Agencies and all agencies within the County of Broward would have naming prefixes of at least two digits that would stand alone. Counties would be pre -named with a two digit mnemonic, and the Cities and Agencies of the Counties would be included under the prefix of the County they are in. Region 7 Operating Agencies and Broward County Region Agencies will have a naming prefix of at least two (2) letters that would describe their area. The naming standard only governs the first two characters; the characters following the first two are at the individual agency's discretion, for example; the agency may opt to internally use more than two characters for the internal identifications. Page 70 of 99 11 a s The following are suggestions for the body of the subscriber alias name. The body of the alias would contain an agency's identification for the individual or pool radio etc., possibly the radio user's call sign as an example. The alias could be suffixed with identification for the radio itself, such as a "-P" for portable for example to differentiate between a mobile & portable radio used by the same person. This would allow Dispatchers & System Managers to readily identify radio users and if the radio is a portable or a mobile. Lost radios or radio IDs that are not associated with a radio user or console: A possibility for locating unused radios in the system that are lost, or not assigned to subscribers would be to temporarily prefix the radio serial number with a dash "-"at the time the radio is lost, or when the radio user is assigned to another radio. A report of these radios can be created by the SmartZone configuration reports tool and setting the radio selection criteria to "Radio .Serial Start range -0, End range-999999. A master list of Radio User Aliases will be created and maintained in the system. They will be readily accessible through the data terminal for all who have rights on that part of the system. As alias names are created and approved they will be placed on this master list so as to be available for all appropriate parties for operations and planning. REGIONAL SYSTEM NAMING PREFIXES 2-3 Character Prefix Name of the Agency using the Prefix BC Broward County Local Government BCP NPSPAC Mutual Aid BCSB Broward County City BSO Broward Count 's Office Police and Fire Rescue CC Coconut Creek CM Communications -- Joint Operations CS Coral Springs DV Davie DB Deerfield Beach Fire Rescue DN Dania Beach Fire Rescue FL Fort Lauderdale - FSO Motorola Field Service Operation eration FSO HB Hallandale . Hillsboro Beach _ ._. _ .._.. _..... HW Hollywood Police, Fire Rescue and Local Government LH Lauderhill LP Lighthouse Point MED Broward County MEDCOM MG Margate MM Miramar OP Oakland Park PB Pompano Beach Local Government PB Pompano Beach Fire Rescue PL Plantation PP Pembroke Pines SEM Seminole Tribe SN Sunrise WM Wilton Manors 5. Recommended Procedures: N/A Page 71 of 99 S. Management: The System Managers are responsible for seeing that the defined standard is followed and maintained. Page 72 of 99 . STANDARD OPERATING PROCEDURES (SOP) 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures Document Section: 1.6 RPSCC Radio Sub -Committee Sub -Section: roved Date: 08/02/07 Procedure Title: Radio Model and Features Date Established: 01 /04/07 Replaces Document Dated: N/A Date Revised: NX 1. Purpose or objective: The purpose of this section is to set forth the recommended standards by which all 800 MHz radio users in the regional system will agree to purchase subscriber radios that are defined in this standard. This standard is to ensure that radios that are not in compliance do not affect the radio system. This document will be revised after the RPSCC approves the purchase and implementation of a -new APCO P25 700 MHz radio system and the manufactured radio models have been identified to work with the P25 system. 2. Technical Backaround: ■ Constraints Radios must meet the recommended standards as set forth. These standards identify the proper radio to be used in conjunction with the required features and auxiliary equipment (to be described in Section 1.1) Each subscriber. radio will be assigned it's unique Radio ID number, Alias Name and programmed with a codeplug/template that has been approved by the user's upper level management. 3. Operational Context: All radios are programmed with the required Talk Groups, Mutual Aid (Local and Statewide) and features to allow it to operate on the 800 MHz Trunked radio system. Codeplugs/templates are created by the individual agencies radio shop or their contracted vendor. 4. Recommended Protocol/Standard: In order to meet these requirements the following information describes the minimum standards that must be considered when new radios are purchased. Radios of various manufacturers and models are capable of operating on this network. The Network currently consists of a Motorola SmartZone 3600 Baud Control . Channel infrastructure. It is recommended that mobiles and portables be capable of operation with SmartZone features to permit the automatic roaming between sites as the users move out of range of their home* system. SmartNet radios can be utilized where there is no intention of providing the automatic roaming features. With an eye to the future, where P25 and 700 MHz may be introduced, it is recommended that the subscriber units with a life expectancy past 2009 be either upgradeable or be equipped to operate on 700 MHz using the P25 protocol. For Public Safety users it is strongly recommended that the current Motorola products be utilized. System Managers can advise on the appropriate* features, functionality and options to purchase. As a minimum, all radios shall have the ability to be assigned a unique individual ID. number for system access, have the ability to be inhibited by command from the System Management tools and have an adequate talkgroup/channel capacity to permit the Local, Regional and National Mutual Aid talkgroups and channels to be programmed along with local agency requirements. The radios shall be capable of operating both in conventional mode and Motorola Trunking modes. There are other Trunking protocols that are Page 73 of 99 not compatible, and radios utilizing these protocols shall not be authorized. These protocols include, but may not be limited to, Privacy Plus, EDACS, LTR and TETRA. Mobile Radios shall have their power set to the lowest possible value. The radio systems in Broward County are designed to work in -building with portable radios. Constraints are placed upon the acceptable mobile radio power levels that should be utilized by this in -building design and the close spacing of the frequencies utilized by the network. Excessive power can cause undesired interference to the other users on the network. Older model radios shall be set to the lowest power permitted by their design, typically the half -power point. Non -Public Safety mobiles shall utilize 1/4 wave antennas, not gain style antennas. Any Public Safety user that desires to utilize a high power setting for a specific System's Talk Groups shall obtain permission from the System Managers. The radios shall be programmed to power up in the low power mode and require a positive action on the part of the user to increase the power level. There shall be policies and procedures written to address the use of high power only after communications are unsuccessful when using the low power setting, .and when working outside the primary coverage area of the network. If wide area talkgroups are involved, the totality of the wide area coverage, and not that of a more restricted coverage system, shall determine if high power usage is appropriate. PORTABLE RADIO STANDARDS Model XTS2600 XTS2500 XTS2500 XTS5000 XTS5000 XTS5000 XTS1500 Description Model l Model II Model III Model l Model l) Model III Model t Digital O 0 0 O O 0 O SmartZone 0 0 0 0 O O 0 Dual Mode S S S S S S S 800/700 M H z capable Project 25 O O O 0 0 0 O 9600 SW RF Switch S S S S S S S (764-806 MHz) ---- -- ... _ __ -_ -- --------__ _- ------- --- - -- -- - -- -- -- ---__ ---- ------ _(808-870 _____ -- - -_ MHz Encryption 0 0 0 O O 0 Software Encryption 0 0 O 0 0 0 Hardware Multi -Key 0 O O O 0 0 (Required only if other System Talk Groups are programmed in the radio Page 74 of 99 MOBILE RADIO STANDARDS Model Description XTL1500 XTL2500 XTL5000 Digital 0 0 Dual Mode 800/700 MHz capable S S S SmartZone 0 0 P26 9600 Software 0 0 O ID Display 0 0 Encry Lion Software 0 0 0 Encryption Hardware O 0 Multi Key (Required only if other System Talk Groups are programmed in, the radio 0 O Remote Control Head 0 0 S = Standard Feature 0 = Optional Feature 5. Recommended Procedures: NIA 6. Manacement: The System Managers are responsible for seeing that the defined standard is followed and maintained. Page 75 of 99 � M � STANDARD OPERATING PROCEDURES (SOP) 800 MHz Trunked Regional, Public Safety Radio System Standards, Protocols, Procedures Document Section: 1.7 RPSCC Radio Sub -Committee Sub -Section: Approved Date: 08/02/07 Procedure Title: Radio Auxiliary Equipment Date Established: 01/04/07 Replaces Document Dated: N/A Date Revised: N/A 1. 2. 0 4. Purpose or Obiective: The purpose of this section is to set forth the recommended standards by which all 800 MHz radio users in the regional system will agree to purchase subscriber radios auxiliary equipment that are defined in this standard. This standard is to ensure that radios that are not in compliance do not affect the radio system. These standards will be revised once the RPSCC has purchased and implemented a new APCO P25 700 MHz radio system and the radio model types have been identified to work with the. P25 radio system. Technical Background_: ■ Constraints Radios must meet the recommended standards as set forth when auxiliary equipment is needed by the individual radio subscriber to perform their job. These standards identify the proper radio auxiliary equipment to be used in conjunction with the radio subscriber's model type. Operational Context: All radios must meet these specific requirements for antennas and batteries when installed on a subscriber's radio. Failure to utilize the manufacturer's recommended standards for the radio auxiliary equipment may cause Law Enforcement and/or Fire Rescue field force personnel to experience static, interference or audio communication breakdown with their assigned Dispatchers. while it is recognized that it is desirable to utilize the accessories manufactured by ---the-radio-manufacturer, there--are-alternative-after=market--accessories--that- provide -performance------------- equivalent to the manufacture's items, or functionality not available from the Original Equipment Manufacturer (OEM). The permissibility of these after -market items shall be determined by the System Manager after performing a technical evaluation to insure a performance level equivalent to the OEM items. Recommended Protocol/Standard: In order to meet these requirements the. following information describes the minimum standards that must be considered when new auxiliary radio equipment is purchased. Antennas: Radio antennas shall be either the OEM part or an equivalent as determined by the System Manager. No antenna shall be used that is not pre -approved. In no cases shall "cellular" or shortened stubby designs be permitted unless -technical testing confirms that the radiated energy is'within 1 dB of the OEM antenna radiation. Testing shall be performed under the direction of the System Manager, not the end user. Batteries: The battery is the life -blood for the radio and can have a major impact on the radio performance over' the course of a shift. It is encouraged that each Public Safety user will have a spare charged battery available. In car charges are an option, either the OEM version or Page 76 of 99 the AdvanceTec model as appropriate for the radio model in use. These shall only be utilized to charge the spare battery. It is highly encouraged that OEM batteries be utilized as they have proven to present fewer quality and performance issues then many of the after -market products. After -market batteries shall be evaluated prior to implementing their use. Testing shall include fit and finish, drop tests, vibration, cycle capacity, long-term capacity and self -discharge after the battery has been in use for six (6) months. Testing shall be on a representative sample of the after -market manufacturer's product. Speaker/Microphones: Speaker/Microphones come in two basic styles; Public Safety — equipped with an antenna; Standard — usually equipped with a coiled cord and does not have antenna. The radio system coverage is predicated upon the use of a Public Safety microphone with the appropriate antenna installed on the microphone. Use of Standard speaker/microphones for users that ride in vehicles is discouraged due to the significant range reduction caused by having the antenna below the vehicle glass level and shielded by the vehicle's construction. They may be utilized by bicycle and motorcycle units with the understanding that when radio user is in a vehicle, the coverage may be significantly reduced. Surveillance kits such as the two or three wire kits, and ComPorts also utilize the antenna mounted on the radio. The same in vehicle coverage issues apply to these units. After -market microphones, surveillance kits, etc. require technical evaluation by the System Manager before they are promoted to the end users. The following are the manufacturer's recommend standard specific to radio. models MTS2000 (antennas only), XTS3000 and XTS5000 (batteries only) series. Antenna: • 806 870 MHz -'/2" Wavelength Whip (MTS2000 only) • 806 — 941 MHz —'/a" Wavelength Whip (MTS2000 only) Public3afety Microphone (Models MTS2000, XTS3000 and XTS50001: • Straight Cable 30 inches '... Straight Cable 24 inches • Straight Cable 18 inches • Command Shoulder Speaker (water -proof) microphone Batteries „ for Portable Radios (Models IIATS2000, XTS3000 and XTS5000�: • Nickel -Cadmium 7.5 volt Battery (MTS2000) • Ultra -High Capacity Battery (MTS2000) • High Capacity NiCD • High Capacity NiCD FM •. High Capacity NiMH • High Capacity NiMH FM • High Capacity NiMH Rugged FM • High Capacity Lithium Ion • NiCAD (State approved) 5. Recommended Procedures: All Antennas, Public Safety Shoulder Mics and Batteries must meet the specifications identified in this standard, protocol and procedures. It is strongly recommended that all after -market vendors Page 77 of 99 0 work through the System Managers to present their products for evaluation before they contact the end users. End users shall refer all vendors to their System Manager before entertaining the use of an after -market product that connects to, attaches to, or otherwise involves the subscriber units and/or the radio system. 6. Management: The System Managers are responsible for seeing that the defined standard is followed and maintained. e Page 78 of 99 ., • t STANDARD OPERATING PROCEDURES (SOP) 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures Document Section: 1.8 Sub -Section: Procedure Title: Talk Group Names Date Established: 01 /04/07 Replaces Document Dated: 08/02/07 Date Revised: 04/08/08 1. Puroose or objective: 2. 3. 4. RPSCC Radio Sub -Committee Approved Date: 04/08/08 The purpose of this section is to set forth the principals by which all radio users in the regional system will establish names for Talk Groups (TG) and to facilitate intuitive understanding of the TG name. The TG- naming standard is also essential because, in keeping with the regional interoperability concept, some TG's will be shared by multiple agencies. Technical Background: rr� All TG names programmed in the County's 800MHz Trunked Radio System must- be unique and consistent from Zone Manager to subscriber. Due to the fact that the newer subscriber units will have a maximum of twelve (12) characters on their display, TG length will be limited to a maximum of twelve (12) characters. When possible, subscriber TG will be consistent with the console database and zone controller. Any subscriber with less than eight (8) characters display will be handled on a case by case basis. Operational Context: With the exception of the first four (4) characters (see .Appendix A), the System Managers are technically free to choose any unique name they wish for TG's assigned within their partition (maximum of twelve (12) characters). The NPSPAC Mutual Aid conventional TG's are assigned a name that is known nationwide. When possible, subscriber TG will be consistent with the console database and. zone controller. Any subscriber with less than eight (8) characters display will be handled on a case by case basis. Recommended Protocol/Standard: The first two characters of the TG alias identify the talk group governing entity/municipality (see Table 1). The third character identifies the departmentlagency within the governing entity/municipality (see Table 2). The fourth character will have a dash.(-) as a separator. The remaining available characters will be used to complete the talk group alias. It is important to note, depending on the subscriber type and/or model, character display may be smaller or larger. Subscribers units with displays smaller than twelve (12) characters will require condensing the TG name to fit within the display. Any subscriber displays that are under eight (8) characters will be handled, by the Radio System Administrator, on a case by case basis. It is understood that there is currently a wide variety of subscribers out in 'the field. In addition to this, there are many agencies who still wish to continue to identify zone and channel assignments prior to the TG in the subscriber unit. Even though the concept that the TG's are to remain consistent from zone controller up to the subscriber is fully supported by Broward County Office of Communications Technology, this may be too big of a challenge to overcome at this time. We have come to the understanding that if the agency wishes to continue to identify zone and channel assignment prior to the TG name in the subscriber, they have this ability if they can leave the TG name consistent, as it appears in the zone controller, as much as possible. Page 79 of 99 r 5. Recommended Procedures: N/A G. Management: The System Managers are responsible for seeing that the defined standard is followed and maintained. I Page 80 of 99 Appendix A Purpose: The following is required in order to standardize and document talk group naming convention for the Broward County SmartZone 800Mhz Trunked Radio System. Description: The first two characters of the talk group alias identifies the talk group governing entity/municipality. The third character identifies the department/agency within the governing entity/municipality. The fourth character will have a dash (-) as a separator. The remaining available characters will be used to complete the talk group alias. It is important to note, depending on the subscriber model, character display may be smaller or larger. Any subscriber displays that are under eight (8) characters will be handled, by the Radio System Administrator, on a case by case basis. See examples below. xample 12 character display s name itifier (see -, - Table 2). example: } a %D I S P- 4 A = PSE3/6S0 dispatch channel "Disp4A" . Note: Depending on the subscriber model, character display may be smaller or larger. There is a max of twelve (12) characters allowed for talk group alias names. Example 8 character display al. 0-- r } .-��.zzzz Lyj k.- Talk group alias name Dash separator Ingle Letter Department Identifier (see Table 2). T o Letter Identifier (see Table 1). ? t Ffw�lVk©©P 4 w i o dispatch f i j 5 example: dispatch channel Note: Depending on the subscriber model, character display may be smaller or larger. There is a max of twelve (12) r Page 81 of 99 Tables Table 1 BC Broward Count BS Broward Sheriff Office CC Cooper City CK Coconut Creek CS Coral S rin s DN Dania DR Deerfield DV Davie FL Fort Lauderdale HA Hialeah, Miami Dade Ct . HD Hallandale HW H-ollywood LH Lauderhill LL Lauderdale Lakes LP Lighthouse Point LS Lauderdale b the Sea LZ Lazy Lake MC City of Miami, Miami Dade Ct . NIB Miami Beach, Miami Dade Ct . MD Miami -Dade Count MG Margate MM Miramar NL North Lauderdale OP Oakland Park PC Palm Beach Count PB Pompano Beach PD Parkland PK Pembroke Park PL Plantation PP - _ Pembroke Pines _ P SF State of Florida SM Seminole SIN Sunrise SR Sea Ranch Lakes SW Southwest Ranches TM Tamarac WM Wilton Manors WP West Park WS If eston To be used only by Broward Sheriffs Office Table 2 A Alr art B FUTURE USE C Communications D FUTURE USE E Port Everglades F Fire Rescue G FUTURE USE H FUTURE USE I FUTURE USE J FUTURE USE K FUTURE USE L Local Government M Mutual Aide N FUTURE USE '.' .3. P • r• ii. T} TY. . Police 0 FUTURE USE R Parks & Rec S School T FUTURE USE U FUTURE USE V FUTURE USE W FUTURE USE X FUTURE USE Y. FUTURE USE Z FUTURE USE 0 Page 82 of 99 STANDARD OPERATING PROCEDURES (SOP) 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures Document Section: 1.9 Sub -Section: Procedure Title: Shared Use Of Talk Croups Date Established: 01/04/07 Replaces Document Dated: N/A Date Revised: N/A 1. Purpose or objective: RPSCC Radio Sub -Committee Approved Date: 08/02/07 The intent of this standard is to provide an option to the users of the 800 MHz system, which will allow the talk group owners to "at their discretion" predefine sharing authorizations for other agencies. 2. operational Context: Talk Groups are considered to be "Owned" by the agency requesting the creation of the Talk Group, similar to the ownership that applies to conventional RF resources. As the owner of the Talk Group the owning agency has the authority and control to define who can and cannot use the Talk Group and to what "degree. Traditionally this process has been primarily accomplished with "letters of authorization." The optional method to simplify this process is for the owning agency to predefine sharing authorization, as diagrammed in the table example below. The predefined authorizations would be kept in the Talk Group spreadsheet maintained by the System Managers. These spreadsheets would be shared between the System Managers, and would be a reference available for Talk Group planning. If an agency does not pre -define sharing authorization for a particular talk group, the default will be a "P" as defined below. 3. Recommended Protocol/Standard: The use of the following codes, which are combined to define the intended pre -authorizations... P =Permission is required to gain authorization for use. A letter of permission must be generated from the System Manager of that agency that wishes to use another agency's Talk Groups for their radio 'subscribers and/or their Dispatch consoles and this written request must be sent to the System Manager of the system that has ownership of those Talk Groups for their system. D = Defined agencies may share, to be defined in a separate letter. The letter would outline specific purpose talk groups, i.e., only dispatch consoles, only neighboring cities, etc. The letter will be on file with the appropriate System Managers. L = Like agencies may share, "Fire, Medical, Law, Public Works, etc." A = All agencies. RX = Only authorized to receive. TX = Authorized to transmit and receive. 4. Recommended Procedures: The System Managers, working with the user groups, would perform this task. Page 83 of 99 5. Manaoament: The System Managers are responsible for the management of this procedure. The larger table is also used to layout the Fleetmap information as described in this manual in Section 1.1, Fleetmap. Standards. Talk Group owning Agency . Description Administrating Global Sharing Agency Authorizations P = Permission letter required to gain authorization for use D = Defined Use 7 Letter required L = Like agencies may share "Fire, Medical, Law, Works' etc. A = All agencies . RX = Are only authorized to receive TX = Are authorized to receive & transmit Talk Group 1 D-TX Talk Group 2 L-TX Talk Group 3 A TX Talk Group 4 P-RX Talk Group 5 P-TX Talk Group6 D-TX . _.Talk-Grou -7.-- ....... Talk Group8 � A -TX Talk Group9 P'RX Talk Group10 P-TX Talk Group 11 D-TX Talk Group_12 L-TX Talk Group 13 A-RX Talk Group 14 P-RX Etc. P-RX The "RX" option shown in the table is an authorization that permits receive only use, although the radio would be technically capable of transmit (TX) operation on the talk group. Page 84 of 99 11 v STANDARD OPERATING PROCEDURES (SOP) 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures Document Section: 1.10 Sub -Section: Procedure Title: Scanning Talk Groups Date Established: 01/04/07 Replaces Document Dated: N/A Date Revised: N/A 1. Purpose or objective: RPSCC Radio Sub -Committee Approved Date: 08/02/07 This procedure is to identify operational procedures and responsible authorities governing Scanning activities as it relates to the Scan function in the individual subscriber radio- 2. Technical Backcround: ■ Capabilities The network infrastructure and subscriber units need to be configured to permit managed user Scanning of Talk Groups. Whether or not Scanning will be utilized in subscriber radios, it is at the option of the user agency. Users also need to be trained that merely including a Talk Group in a non -priority Scan list will not necessarily result in the user hearing traffic on that Talk Group. The Talk Group must also be "active" at the site where the user is affiliated. Talk Groups are active on a site if the Zone Controller is programmed to allow the Talk Group to appear on that site and there is at least one user affiliated at the site which has the Talk Group of interest as their selected channel. ■ Constraints How the radio is programmed to handle wide area and local sub -system Talk Groups will determine priority Scan capabilities. If the local subsystem Talk Groups is not programmed to the same "system" in the radio, they cannot be included in the priority monitor Scan list. In this case, only Talk Group Scan can be implemented. Priority Scan re wires " q� ys em-n rastructure con figuration '-in...ordertoperform-as expected: The Talk Groups that are deemed to be Priority Monitor Groups need to be configured as such by the System Managers. There are practical limitations on the overall number of Priority Monitor Groups that can be enabled due to the amount of time required to distribute the list of active Talk Groups to the radios in real-time. Talk Group Scan does not provide a priority feature to direct the radio to the priority Talk Group. Talk Group Scan can Scan Talk Groups from different systems (as defined in the radio internal programming) and conventional channels. It is strongly recommended that "talkback Scan" not be used. Talkback Scan would direct the user to transmit on the last active Talk Group the radio heard traffic on. This will cause confusion as the radio user will not know what Talk Group the radio will be transmitting on as it will constantly change based upon what the radio last received. Scan is not recommended for those users that must hear critical communications. While Scanning will be available on the systems it will necessarily be limited and, therefore, not be as robust as in conventional radio systems. 3. Operational Context: The network infrastructure and subscriber units will be configured to balance the ability for users Page 85 of 99 M to achieve wide area coverage where necessary, and maintain an acceptable level of service for all users. The use of "Critical User" and "Critical Site" in the system for the purpose of non -priority Scanning is not permitted and Scanning between different sites will be accomplished by the use of "requested sites." Before priority Scanning is allowed on an individual subscriber's radio, it must be pre -approved by the agency's management and/or command. Additionally, priority Scanning of Talk Groups must be evaluated by the System Manager to make sure the radio system is not affected by the use of this feature. 4. Recommended Protocol/Standard: Limited Scanning/monitoring privileges may be pre -approved by the affected Talk Group owners and System Managers. Before Scanning of owned Talk Groups, permission must be granted. permission must come from: ■ The System Managers of the sites that are being requested for the Talk Group • The jurisdiction/agency who is the "owner" of the requested Talk Group Mutual aid, special roaming and other shared Talk Groups may be Scanned at any time; however, "requested site" determinations will be made by the System Managers of the affected sites. 5. Recommended Procedures: Permission: If the Talk Group does not appear on the approved Scanning list, permission must be obtained in writing from the Talk Group owner and the System Manager of the non -home site or sites being "requested" if applicable. Scanning Configuration: If trunked Scanning is desired, it is recommended that Scanning should normally be limited to owned trunked Talk Groups which are affiliated with their "always preferred sites)". It is further recommended that Scanning normally be disabled when the user leaves the system and switches their radio to a conventional (non-trunked) channel. However, if mixed mode Scanning (both trunked Talk Groups and conventional channel members) is required by some users, it is also recommended that this Scan type only be available when the radio is selected to a conventional channel. This is because mixed mode Scan does not provide priority reverts and the user will typically miss substantial portions of conversations on the selected channel. Talkback Scan is highly discouraged, as the user cannot control the Talk Group used to transmit. Can lists can be either programmed into the radio with no user access for changes, or the list. can be made accessible for user modifications. It is preferred that the list is made user configurable to allow those users that can handle Scan to determine what they want to listen to and make changes "on the fly" as their requirements .change. Scanning of Non Home Site Talk Groups: It is possible to monitor a non -home Talk Group by configuring the system to request the desired non home Talk Group appears on your primary/home system or `always preferred site(s)". Doing so however, will consume a repeater channel on your primary/home system or "always preferred site(s)" and will carry the requested non -home Talk Group priority setting with It. Also, a call on the requested non -home Talk Group- will not be delayed (busy queued) if the home system or Page 86 of 99 "always preferred site(s)" does not have a channel available. This however may cause unacceptable conditions where the majority of users do not receive the call while the dispatcher or calling party -has no indication that a large segment of their users did not receive the call. While this "requested site" is the recommended approach, it must be carefully controlled, monitored and evaluated due to the potential to exhaust system resources. It must be approved by the affected System Managers. S. Management: The System Managers will. be the final authority for controlling the Scan feature and Scanning issues. The agency's management and/or command will have the authority to approve/disapprove this feature for their users. Page 87 of 99 STANDARD OPERATING PROCEDURES (SOP) 800 MHz Trunked -Regional Public Safety Radio System Standards, Protocols, Procedures ' - Document Section: 1.11 Sub -Section: Procedure Title: Emergency Button Date Established: 01/04107 Replaces Document Dated: N/A Date Revised: N/A 1. Purpose or objective: There will be a large variety of users on t The various- ways L the emergency key can is important to design the system in such responded to quickly and appropriately. 2. Technical Background: ■ Capabilities RPSCC Radio Sub -Committee Approved Date: 08/02/07 ie radio system with various Emergency Button needs. be configured will allow for flexibility of use, however, it a way that when an Emergency Button is pushed, it is The "Emergency Button" feature, if -it is programmed into the subscribing agency radios, will allow a radio user to send an emergency notification by pressing the specific Emergency Button on the radio. The notifications will audibly and visually alert all dispatch console positions that have the talk group up that the emergency notification is routed to. Other radios that have the talk group selected will also receive the emergency notification, and display the radio ID of the radio generating the emergency. The display of an ID is dependent upon radio model, firmware version, and purchased options. The user activating the Emergency Button has the obligation to properly cancel the activation by pushing — and holding the Emergency Button until a continuous tone sounds. Failure to properly cancel the alarm on the originating radio will cause a new alarm activation each time the user transmits. Emergency calls are also automatically assigned the highest priority available and would M- be "the' first­available- fr6m-th6' queue ** if 1he * *system- is- in -a- busy "situation: Subscriber's radios can optionally be configured to automatically activate the Push -to -Talk (PTT) for a programmed period of time if the Emergency Button is pressed. Constraints_ Consider two situations a fire department engine company could be faced with, that show different operational needs: 1. An engine company responds to a medical at a private home. Upon entering the home, they are met by an out -of -control person who fires a handgun at them. 2. An engine company is conducting an interior fire attack when the floor collapses, trapping them in the basement. In the first example, a firefighter may push K the home. He may want it to signal his dispatcher would immediately see the signal, assist. Emergency Button as he is running out of dispatcher on the main talk group. The assess the situation, and send the police to Page 88 of 99 In the second example, a firefighter may push his Emergency Button, and have it send the signal on his fire ground operations channel. The on -scene safety officer would attend to this signal by immediately sending in a rescue crew comprised of people already at the scene. The design should also avoid the instance where an Emergency Button is pressed, and nobody can identify the user, or the wrong people attend to the emergency. Such a situation would occur if a police officer's Emergency Button were configured to signal on a Main Channel talk group. In that case, pressing his Emergency Button would probably signal every police dispatch console on the radio system. Another example is that a public health official pushing the button when alone in a dangerous situation. If the public health official's radio were configured- to signal on the County main dispatch talk group, but is unknown to the dispatcher, the dispatcher may be confused by who is in distress, and may not know how to respond. This example shows the importance of an agreement between the central monitoring agency and the radio user agency. Emergency Button programming cannot be configured on a talk group by talk group basis. This function is defined within the radio personality consisting of a group of 15 talk groups. The personality may be configured -to direct the radio to a specific talk group or to use the current selected talk group of the talk groups within the personality. Emergency Button configuration requests shall be discussed with the System Manager of the affected System as radio programming codeplugs are impacted. It is recommended that non -Public safety, i.e. Public Service, or general government, users not have the Emergency Button functionality unless appropriate training and monitoring resources are available to respond to the alarms. Non-public safety emergency alarms shall not be directed to a Public Safety Talk Group unless the Public Safety Dispatch Center responsible for the Talk Group -agrees to assume responsibility for the alarms. . 3. Os)erational Context: An Agency may choose to utilize the Emergency Button functionality, or to disable its use. If an Agency chooses to use the Emergency Button it shall be utilized as an indication of an immediate --threat -to life- or, property.- .Use of the* Emergency Button -to -advance a routine -Talk--Group call * in the priority cue is not an accepted usage. Agencies may choose to have the emergency activations occur on a primary dispatch Talk Group, or be directed to a* specific Talk Group set aside to handle Emergency Activations. Agencies that may have access to the Talk Groups from other Agencies in their consoles will receive the emergency activation notifications if that Talk Group is active in a folder in the console operator position. Agencies shall NOT acknowledge/silence/cancel emergency activations from another Agency without contacting that agency before taking action. To do so may cause a valid emergency alarm to go unanswered. Any Agency that acknowledges/silences/cancels emergency activations from another Agency more than 3 times, without contacting that agency before taking action, shall remove the other Agency Talk. Groups from their consoles within 30 days of receiving notification from the Talk Group owner or System Manager. Subscriber units that send an excessive number of false emergency alarm activations shall be located and corrected by the subscriber owner agency as expediently as possible. Excessive is determined to be four (4) or more false alarm. activations within a 24-hour period. The subscriber owner agency shall take all steps necessary to locate and correct the false activations. There are circumstances where it is not possible to stop the false activations by attempting to inhibit the radio or by removing the radio authorization record from the system databases. In these cases Page 89 of 99 the radio must and shall be located by the Owner Agency and brought to the servicing vendor for repairs within 30 days of the first false activation. Dispatch Centers shall report all instances of excessive false emergency alarm activation to their System Manager. The report shall include the date, time and Talk Group the emergency occurred on, along with either the subscriber alias or displayed radio I D #. 4. Recommended Protocol/Standard: Use of the Emergency Button as an emergency signaling option should be available to any agency on the radio system, subject'to certain conditions and provisions. I . Agencies are not required to use this capability of the radio system. 2. No agency will be permitted to enable their emergency signal on- a talk group designated as "emergency restricted." 3. All agencies implementing the Emergency Button must have a plan in place to respond to an Emergency Button activation. 4. All Emergency Button response plans must include, at minimum: • A central radio monitoring point that can identify which radio user pushed the button, the location and nature of the emergency and what the proper agency response should be • A central monitoring point must -be available during any/all hours that personnel are using the radio system. • A policy for use of the Emergency Button by radio users. • A response plan to assist the radio user in need. • In the event the central radio monitoring point is not the same agency as the radio user, an agreement on policy, monitoring, use and response must be in place among the agencies. • Where available the orange button should be used to program the Emergency Button. 5. Recommended Procedures: N/A 6. . Management: Agencies wishing to use the Emergency Button unction must coordinate wh[c_h agency resources that will be receiving the emergency calls, the receiving agencies must have an appropriate plan in place, and documented as to the process that they will use to handle the emergency calls. Page 90 of 99 STANDARD OPERATING PROCEDURES (SOP) 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures Document Section: 1.12 RPSCC Radio Sub -Committee ' Sub -Section: Approved Date: 08/02/07 Procedure Title: Encryption Date Established: 01 /04/07 Replaces Document Dated: N/A Date Revised: N/A 1. 2. 3. 4. Purpose or Objective: This procedure is to identify operational procedures and responsible authorities governing Encryption activities. Technical Backcround: • Capabilities The network infrastructure and subscriber units need to be configured to permit Encryption of selected Talk Groups. Whether or not Encryption will be utilized in subscriber radios, it is at the option of the user agency: Users also need to be trained to know how to activate the Encryption feature when needed on- a specified talk group. ■ Constraints It will be the subscriber radio user's responsibility to activate the Encryption feature when needed. In most cases the use of Encryption will be decided once a talk group is dedicated to the use by the personnel in the field that are involved in the operational situation. The Encryption feature blocks all non-approved/intruder radio users and scanners from hearing the conversation of the talk group that is being used for the situation. At this point in time (2007), only the City of Hollywood and County of Broward infrastructure support Encryption capabilities. Encryption can only occur on a digital capable talk group. Both the availability of digital Talk Groups and digital subscriber IDs is limited and must be coordinated with the System Managers prior to any desired implementation. Currently only DES-0F13 and DES -XL Encryption algorithms are supported. Encryption Talk Groups that must appear on a console will need to have Encryption key loaded into the Console DIU. This has the potential to reduce the security of the talk group as others may be able to access the clear audio via a console. 02erati onal Context: The Encryption feature needs to be pre -approved by the agency's upper level management.. Police units that are approved to receive Encryption for their subscriber radios are designated as SWAT, K-9, Homeland Security and Special Investigation Division, and any other unit as determined by the Department.. Other Departments and Divisions such as the Fire Department may choose to encrypt some or all of their Talk Groups as needed to insure operational security. Recommended Protocol/Standard: Limited Encryption privileges may be pre -approved by the affected Talk Group owners and System Managers. Page 91 of 99 11, r r- Before allowing Encryption as a feature of a subscriber radio user of owned Talk Groups, permission must be granted. Permission must come from: = The System Managers of the sites that are being requested for the talk group ■ The jurisdiction/agency who is the "owner" of the requested talk group 5. Recommended Procedures: A subscriber radio user that has the Encryption feature will be responsible for activating/deactivating it as needed. Talk Groups may also be "strapped" secure in the subscriber programming to permit only encrypted operation if desired. Encryption Keys shall be maintained by the Agency utilizing the Encryption feature. Each agency is responsible to insure that they do not duplicate Logical IDs (LIDs). Logical IDs for the keys consist of a four -digit number entered as the last four digits of the Key. LIDs for Broward County shall be in the 1000 series, Deerfield Beach shall use 2000, Hollywood shall use 3000, Fort Lauderdale and Pompano Beach shall use 4000, and Hallandale Beach shall use 5000. As other systems are brought .into the Regional Public Safety Communications System, their LIDs shall start with the site number for their infrastructure. This structure insures that there will not be duplicated LIDs which will cause problems when utilizing Encryption in the integrated environment that we share. The first 16 digits of the key are at the discretion of the Agency. There- are two shared Regional Zpecial Investigations Joint Operations Talk Groups that utilize a shared common key. These two Talk Groups may not be utilized on a permanent basis for any one specific unit or agency. They are common, shared resources dedicated to interagency operations. The talk group information and key are available to authorized personnel by contacting either the System Managers of the Broward County's Office and Fort Lauderdale. 6. - Mananement: w The System Managers group and the agencies upper level management will be the responsible authority for Encryption issues. Page 92 of 99 STANDARD OPERATING PROCEDURES (SOP) 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures Document Section: .1.13 RPSCC Radio Sub -Committee Sub -Section: A roved Date: 08/02/07 Procedure Title: Definitions & Acronyms Date Established: 06/28/07 Replaces Document Dated: N/A Date Revised: N/A 1. Purpose or Objective: To clarify terms used throughout the standards, protocols and procedures manual. All definitions will be found in this section. 2. Manaaernent: Should there be additions, deletions or changes to these procedures the Regional Public Safety Communications Committee (RPSCC) members are responsible for revising this section. 3. Definitions (in alphabetical order) APCO P25 Compliant: Public safety equipment that meets (Association of Public Safety Communications Officials) APCO P25 standards. Announcement Group: is a collection of Talk Groups. Audit: An audit is defined as a one time, Infrequent or occasional in depth analysis of comprehensive elements. An audit may be annual or upon demand. An audit may be stimulated by an event or complaint of monitoring outcome. "Common" or "Pool" Talk Groups: Common/pooled talk groups (TG) are those that are set - aside for communicating across multiple agencies. Agency radio users in appropriate service areas who need to talk to one another for day to day business or for mutual aid will all put the - appropriate- common, --or -pool **talk group- it their--radios-10 be available in time of "need -Example: Fire Departments will all have the common Statewide Fire Mutual Aid TG in their radios. "Pool" is distinguished from "common" in that pool implies more than one, such as TAC 1 — 4 is a pool of common regional tactical TGs for law enforcement. Failsoft Signaling: During normal system operation, the central controller supplies the base station's Failsoft circuit with a Transmit Data (TDATA) signal. The TDATA signal consists of an OSW followed by an LSHS signal, followed by a Disconnect Word signal. The TDATA signal keeps the base stations in the trunking mode. If TDATA transmission stops because of failure of the central' controller, the base stations revert to the Failsoft mode. • The base station unmutes and transmits a Failsoft data word • Radios respond to the Failsoft word and unmute, allowing service to continue via community repeater type operation. • The base station sends out a 900 Hz tone for 280 milliseconds every 10 seconds to alert the radio user that the system is in Failsoft mode. Logging: Audio recording of a radio communication. Mission Critical Operations: Those governmental, quasi -governmental and non -governmental Page 93 of 99 operations carried out by authorized users which are reliant upon a functioning two-way radio communications system which unavailability, degradation, delay or failure, partial or complete, would significantly impact or impair the successful delivery of a vital service or mission. Operations would include, but are not limited to the categories below: Public Safety — Those functions of government that exist to protect the physical well- being of the public as a whole from physical danger — continuous delivery of essential public services. Included with this group are Legal Counsel and City's Special Investigative Unit (SIU) and the Administration Site Operations. Transportation — Those functions of the government that exist to provide safe, effective and efficient multi -mode movement of the public commodities including public roads, highways, waterways, railways, airways and public transportation systems. Included with this section is the Broward City buses that may need to be used as a back-up to the Broward County Mass Transit buses should a mass evacuation occur due to a major incident. Environmental Protection — Those functions of the government that exist to protect the environmental from changes that are detrimental to the existence and continuance of that environment. Public Works — Those functions of the government that provide "first �esponders!' that may -be necessary to clear streets and highways so that Public Safety operations can be conducted after a major event like a hurricane. Mobile Radio: A station in the mobile service, generally installed in a vehicle, intended to be used while in motion or during halts at unspecified points. Mobile Service: A service of radio communication between mobile and base stations, or between mobile stations. Monitor: Monitoring is defined as the scheduled and routine inspection of operational practices and facilities and/or the review of system reports and documents. Monitoring frequency would generally be on a predetermined, scheduled basis Non -Critical Operations: All other governmental, quasi -governmental and non -governmental ireliant-Upotl a1unctioning tWO:Vay; -,radio com,m*unications,that, do- not meet hiohlare the above mission critical or department critical definitions. Operational Fixed Station: A fixed station, not open to public correspondence, ope ' rated by, and for the sole use of those agencies operating their own radio communication facilities in Public Safety, Industrial, Land Transportation, Marine or Aviation Radio Services. Patch:, Permanent (hard) Patch: *A patch between two or more audio resources on a system, which is fixed and cannot be controlled or edited by the dispatcher. Manual (soft) Patch: A patch between two or more audio resources on the system, which is setup and, controlled by the dispatcher. The dispatcher owning the patch can add and delete resources as needed. Portable Radio: A radio that is completely freestanding and may be hand -carried or worn by the radio user. Preferred Site Assignment: A SmartZone system can also be configured with Preferred Site Assignment. operation.- This feature allows, radio users to maintain conversations on sites Page 94 of 99 especially useful to operations and group requirements. In areas with overlapping coverage, radios will work on their preferred site in order to efficiently utilize channel resources while minimizing the number of channels necessary to complete a talkgroup call. Four types of preference can be programmed into the radio personality: • Always Preferred — The subscriber unit will always use this site if it has at least acceptable signal strength, even if the site enters site trunking mode. • Preferred - The subscriber unit will use this site if it has at least an acceptable signal strength rating and is in wide -area trunking mode. • No Preferred Site — This is the default setting for subscriber radios. The subscriber unit will use the best signal according to the best Receive Signal Strength Indication (RSSI). • Least Preferred — The subscriber unit will avoid this site unless no other sites with at least acceptable signal strength are available for use. Private Call: This allows one radio user to talk to and be heard by only one other radio user. This feature allows a supervisor to discuss confidential matters with a particular member of a talkgroup while other members of the same talkgroup remain squelched. Public Safety:. All Law Enforcement / County, Fire, Emergency Medical and related service areas. These include badged and/or sworn ancillary personnel such as Park Rangers, Court Security Officers, Community Corrections, and those who support public safety operations under special circumstances. Public Safety Answering Points (PSAPs): Primary: The PSAP where a 9-1-1 call is originated and received by a call taker then transferred to a dispatcher for dispatching police, fire or emergency medical assistance. Secondary: � The PSAP that receives transferred 9-1-1 call taker calls and is then dispatched and monitored from this center. Public Service: Public Service in this context refers to general government personnel such as Public Works, Transportation, and other similar public service operations. RF: Radio Frequencies Regional Public Safety Communications Committee (RPSCC): The governing body of municipal Police and Fire Chiefs, IT Management and decision -making staff that are empowered to develop Standards, Protocols and Procedures regarding the intent to accomplish the Broward County's Charter direction to achieve regional communication plans to establish Radio Interoperability and Closest User Response objectives. Region 7: State of Florida Homeland Security region that is made up of Broward, Dade, Monroe and Palm Beach Counties. Regional System: In this context of this manual this term is intended to represent the entire Region -wide 800 MHz Public Safety Communication System. SmartZone Trunked System: The 28 channel trunked radio system that serves public safety communication users in a wide -area coverage network. This system allows for roaming from one radio system to another trunked or conventional system seamlessly and provides communications back to the municipality's home based dispatch center. This system can operate in an analog or digital mode. SmartZone Manager Terminal: The resource tool that is used by System Managers to administer their radio system for maintenance issues and controls of how their radio subscriber Page 95 of 99 and consoles are configured I programmed. Subscriber Radio: A portable radio that is assigned to a specific individual or a mobile radio that is shared by multiple staff that drives and operates the vehicle. System: A countywide public safety radio communication system that consists of a shared region -wide infrastructure, the elements of which are identified in the Regional Public Safety Communications Plan and Subsystem integrated into or interconnected by the shared countywide network. System Manager] Administrator Positions: • System Manager -- individual in charge of the radio system of a participating agency. • System Administrator — individual who is responsible for the day to day radio system operations of a participating agency. • Sub -System Administrator — individual who is responsible for the day to day radio sub- system- operations of a participating agency. • Contract Manager -- Director of Broward County Office of Communications Technology or his appointed designee. Talk Group: The Talk Group is the primary level of communication in a Trunked radio system. This provides the effect of a private channel down to the talkgroup level and prevents members of one talkgroup from hearing the talkgroup calls generated by radios in other talkgroups. Telephone Interconnect: The use of a radio to make a two-way call between two radios subscribers when privacy is needed to block other radio subscribers from hearing the conversation. This feature must be programmed in the radio and activated on the system in order for it to be functional. Variance: An allowed divergence from full adherence of ,an adopted standard, protocol or procedures Waiver: A complete release from an adopted standard, protocol or procedure. 4. ACRONYMS (in alphabetical order ALS - Advanced Life Support ATAC - All (user)Tactical talk group for 800 radios AVL - Automatic Vehicle Locator APCO. - Associated Public Safety Communications Officials BLS - Basic- Life Support CEB - Central Electronics Bank CTCSS - Continuous Tone Coded Squelch System DIU - Digital Interface Unit DTMF - Dual Tone Multiple frequency Page 96 of 99 EDICS - Emergency Deployable Interoperability Communications System EMS - Emergency Medical Services EMRS - Emergency Medical Radio System FCC - Federal Communications Commission ICALL - International 800 MHz Calling Channel ITAC - MHz - NAEMSID- NPSPAC PSAP - PSWAN- PTT RF RX International 800 MHz Tactical Channel Megahertz National Association of State EMS Directors National Public Safety Planning Advisory Commiftee Public Safety Answering Point Public Safety Wide Area Network Push to Talk, i.e. talk button Radio Frequency Receiver of radio communications SMG - System Manager, the owner of the Regional Public Radio System and Sub -Systems RSS - Radio Service Software Tx - Transmission of radio communications UHF Ultra High Frequency VHF Very High Frequency Page 97 of 99 R i STANDARD OPERATING PROCEDURES (SOP) 800 MHz Trunked Regional Public Safety Radio System Standards, Protocols, Procedures Document Section: 1.14 - RPSCC Radio Sub -Committee Sub -Section: Approved Date: 08/02/0.7 Procedure Title: Console Naming Date Established: 06/28/07 Replaces Document Dated: N/A Date Revised: N/A 1. PurRos9 or objective: The purpose of this section is to set forth the principle by which all System Managers / Administrators of the regional system will establish names for the Radio IDs used to support dispatch console positions. This is necessary because IDs are not associated with a Radio User Alias. 2. Technical Background: Constraints: The serial number field in Radio ID screens in 12 characters long. Every Talkgroup per console position requires a Radio ID programmed for that position, for example a single console position may have 50 radio ID programmed to support that position. 3. Operational Context: Every radio in the system represents a radio, but not every Radio ID in the system is a radio, some are consoles. By planning an identification process, we can use the radio serial number field in the radio entry screen in the system to categorize consoles so that they can be easily identified. 49 Recommended Protocol/Standard: The Serial Numbers used in the records for console Operator positions will be formatted according to the following: OPTION 1 • Regional Operating Agencies would have naming prefixes of at least two characters that would stand alone. Counties would be pre -named with a two character identifying mnernonic� and the Cities and Agencies of the Counties would' be included under pr6fx'of the County they are in. • The next three characters would be the letters "con" for console, so as to easily distinguish this identifier from other radio aliases. • The characters following these first five are at the individual agency's discretion. OPTION 2 • Starting with a 2 — digit prefix to identify the Console location "for example FL, PB, H L, etc. • The next 2 digits represent the CEB number. • The following 2 digits indicate the TDM slot on that CEB • The last four characters are to be unique, at the individual agency discretion. 4. Recommended Procedures: N/A Page 98 of 99 5. Management: The System Managers / Administrators are responsible for ens*uring compliance with the standard. Page 99 of 99 I b� STATE OF FLORIDA )SS COUNTY OF BROWARD ) 1, Bertha Henry, County Administrator, in and for Broward County, Florida, and Ex-Officio Clerk of the Board of County Commissioners of said County, DO HEREBY CERTIFY that the above and foregoing is a true and correct copy of an Agreement, the same appears in said Board of County Commissioners meeting held on the 7 th day of May, 2013; Item No. 14. IN WITNESS WHEREOF, I have hereunto set my hand and official seal this 15 th day of October, 2013. . i111111111 1P 0% % I 0 M Aq/�q 1000 CREATED amp OCT 1st #AP 00, < : ;0 = we' 'a doo % S E9A4- Co do BERTHA HENRY COUNTY ADMINISTRATOR Deputy Clerk Ir"' i If � v8v 0 "1 0-38 00 4-1 - Rd 8 1130 a