Loading...
HomeMy WebLinkAboutBack-Up DocumentsDocuSign Envelope ID: 1830EDDC-7E2A-438A-9438-79AF9DCE008E INTERGRAPH CORPORATION Action By Unanimous Written Consent of the Board of Directors Acting by unanimous written consent pursuant to and with the effect provided in Section 141(f) of the Delaware General Corporation Law, the undersigned, constituting all of the directors of Intergraph Corporation, a Delaware corporation (the "Corporation"), hereby adopt the following recitals and resolutions: Approval of Signature Authority Matrix: WHEREAS, the Corporation is required from time to time to provide evidence of the authority of the Corporation's officers employees and agents to execute documents, perform contracts, and otherwise to bind the Corporation, its subsidiaries and affiliates; and WHEREAS, the Hexagon PPM ("PPM") Global Approval Authority Matrix and the Hexagon Safety Infrastructure & Geospatial ("SIG") Approval Matrix attached hereto collectively as Exhibit "A" (the "Authority Matrix") sets forth various levels of authority for certain officers and employees as required in the ordinary operation of the Corporation's business; and WHEREAS, the Board desires to ratify the adoption of the Authority Matrix in order to effectively and efficiently carry out the Corporation's day to day business. NOW, THEREFORE, BE IT RESOLVED, that the Authority Matrix as attached hereto as Exhibit "A" is hereby adopted, ratified, confirmed, and approved in all respects; and BE IT FURTHER RESOLVED, that the persons set forth on the Authority Matrix shall have authority to take the actions set forth on the Authority Matrix as set forth opposite their individual names on the Authority Matrix. Hexagon Employee Retirement Savings Plan Fiduciary Committee: WHEREAS, the Board of Directors of the Corporation deems it advisable and in the best interests of the Corporation to provide for retirement benefits and other benefits incidental thereto in the form of certain plans for eligible employees; WHEREAS, the committee of the plan entitled "Hexagon Employee Retirement Savings Plan Fiduciary Commitee" (the "Committee") has submitted a Status Report, attached hereto as Exhibit "B", covering activity of the committee for the twelve (12) month period ending December 31, 2020 (the "Annual Status Report"). DocuSign Envelope ID: 1830EDDC-7E2A-438A-9438-79AF9DCE008E NOW, THEREFORE, BE IT RESOLVED, that the following persons are hereby appointed as the members of the Committee effective immediately to serve until their respective successors are elected and qualified or their earlier resignation or termination: Steven L. Cost Richard B. Jacks Mark Delaney M. Scott Moore Anthony P. Zana Nicholas Hare BE IT FURTHER RESOLVED, that the individuals serving on the committee shall be indemnified to the extent allowable by applicable law for actions performed in good faith while serving in this capacity. BE IT FURTHER RESOLVED, that the actions of the Committee for the period covered by the Annual Status Report are hereby ratified and approved. Appointment of Officers: WHEREAS, Wendy D. Ormstedt has resigned as Empowered Export Official as of March 5, 2021; WHEREAS, Kristen Sims is being elected as the Empowered Export Official to be effective as of the date of this resolution; RESOLVED FURTHER, that the following persons are hereby elected as the Officers of the Corporation effective on the date of this resolution to serve until the next annual meeting of the Board of Directors, or until their respective successors are elected and qualified: Steven L. Cost Chairman of the Board, Chief Executive Officer, President, President of SIG Mattias Stenberg Executive Vice President, President of PPM M. Scott Moore Executive Vice President, Treasurer, Chief Operating Officer of PPM Richard B. Jacks Chief Financial Officer of SIG Mladen Stojic President ofGSP Anthony P. Zana Vice President, Secretary, General Counsel Richard L. Morris Assistant Secretary Stephany L. Steinfath Assistant Secretary Kristen Sims Empowered Export Official Annual Ratification: -2- DocuSign Envelope ID: 1830EDDC-7E2A-438A-9438-79AF9DCE008E BE IT RESOLVED, that all actions taken by the Officers of the Corporation during the previous year are hereby ratified and approved. General Resolutions: BE IT RESOLVED, that by execution of this action, the Board of Directors hereby waives any and all notice required by the Certificate of Incorporation, the bylaws and the laws of the State of Delaware; and BE IT FURTHER RESOLVED, that these resolutions shall be filed with the minutes of the proceedings of the Board of Directors, and shall have the same force and effect as if unanimously adopted at a duly called and held meeting thereof; and BE IT FURTHER RESOLVED, that this unanimous written consent may be executed in any number of counterparts, all of which together shall constitute one unanimous written consent; and BE IT FURTHER RESOLVED, that it shall not be necessary that any counterpart be signed by all parties, so long as each counterpart shall be signed by one of the parties and a facsimile copy of this unanimous written consent shall be considered the same as an original. [Signature Page of Unanimous Written Consent to Follow.] -3- DocuSign Envelope ID: 1830EDDC-7E2A-438A-9438-79AF9DCE008E [Signature Page to Unanimous Written Consent.] Executed as of the Pt day of April, 2021. EDoco Signed by, A. rho c,4,1C2.456am- a 5 _ Ola Rollen Doc kiSigncd by: •,�&rjYAAA,$:9&U#a9r- Steven L. Cost (CONSTITUTING ALL OF THE BOARD OF DIRECTORS OF THE CORPORATION) -4- � A HEXAGON Safety, Infrastructure & Geospatial (SIG) 305 Intergraph Way V Madison, AL 35758, USA T: 1-256-730-2000 CERTIFICATE OF DELEGATED CORPORATE AUTHORITY I, Steven Cost, in my capacity as President of Intergraph Corporation, through its Safety, Infrastructure and Geospatial Division ("Hexagon"), and in accordance with the policies of Hexagon and the actions of its governing board of directors, do hereby authorize the following persons to execute all contracts, documents, and instruments on behalf of Hexagon, binding Hexagon to the terms thereof: Debra T. Huser; Blair Jacks; Richard Morris; and Jennifer Williams. I further authorize the following additional persons to execute non -disclosure agreements and certifications or representations of fact on behalf of Hexagon, including without limitation, certifications of the authority of any third -party to deal in Hexagon products, certifications regarding Hexagon's business practices, or confirmations of actions taken by Hexagon: Alice Bertelmann; Miles Brandon; Haiden Redmond; Williams (Bill) Starnes; Jason Statum; Christopher Tompkins; Pat Thompson; Paul Valis; Victor Vasile; and Billy Woods. This authorization shall be effective from December 1, 2021 through December 31, 2022, unless sooner revoked in writing. Any third -party relying upon this certificate during the stated period of validity and without actual knowledge of its revocation shall be entitled to so rely. LA Steven Cost President SIG, Hexagon 1 HEXAGON MASTER TERMS AND CONDITIONS These Master Terms and Conditions (the "Master Terms") govern transactions and relations between Customer and Intergraph Corporation through its Safety & Infrastructure division ("Hexagon") (each a "Party" and collectively the "Parties"). Hexagon will make available to Customer certain proprietary software, including related proprietary documentation, software maintenance services, Cloud Programs, and professional services, all of which will be provided to Customer pursuant to these Master Terms and an Order. Before Hexagon will provide any Software licenses, Cloud Programs or any services (including the Services), Customer must agree to these Master Terms and to the terms of a corresponding Order. The Parties agree these Master Terms will govern each Order. To the extent that the Master Agreement purports to impose obligations, restrictions, or limitations upon Customer's Affiliates or Users, Customer shall be responsible to Hexagon for Customer's Affiliates' and Users' compliance with such terms and shall procure Customer's Affiliates and Users compliance. These Master Terms consist of the following: • The General Terms and Conditions set forth below • Exhibit A — End User License Agreement • Exhibit B — Maintenance Terms and Conditions for Software • Exhibit C — Sample Project Deliverable Sign -Off Form • Exhibit D — Cloud Program Conditions • Exhibit E — Subscription License Terms • Exhibit F — COTS Training Program Terms • Exhibit G — Common Terms Glossary GENERAL TERMS AND CONDITIONS 1 Definitions. All capitalized terms not otherwise defined herein shall have the meaning set forth in Exhibit G (Common Terms Glossary). Elements of an Order. 2.1 Order Composition. 2.1.1 Each Order will be comprised of Order Documents. 2.1.2 From time to time, Customer may request from Hexagon or Hexagon may provide Customer a draft Quote and/or SOW for Deliverables. Once the Parties mutually agree upon the contents of the Order Documents, as applicable, the Parties shall accept the Order Documents. 2.1.3 Upon mutual acceptance of the Order Documents, Customer will execute the Order Documents and/or issue a PO or a notice to commence work, unless otherwise specified in the Order Documents. 2.1.4 Notwithstanding the foregoing, Orders for Maintenance Services and Cloud Programs shall commence on the date specified in the Order Documents regardless of whether Customer has issued a PO or notice to commence work. 2.2 Pricing. The following minimum elements shall be included with the Order Documents associated with the following types of Orders: 2.2.1 For a Software License Sale, a Quote identifying the Software licenses and quantities being procured and the total price for the Software License Sale. Hexagon Master Terms and Conditions S1082020-MT Page 1 2.2.2 For Time and Materials Project Assignments, a Quote setting forth the number of hours allocated for each grade of Hexagon resource to be utilized on the assignment and the hourly rate for each grade of Hexagon. Unless otherwise specified in the Order Documents, the Time and Materials Project Assignment shall expire and end six (6) months from the date the Order was formed between the Parties. 2.2.3 For Fixed Price Project Assignments, a Quote and SOW shall set forth the price of the work to be performed for and the Deliverables provided for that Order; provided however, that for a Fixed Price Project Assignment consisting of a COTS Training Curricula, a SOW may be omitted and pricing may be set forth solely in a Quote. 2.2.4 For Orders for Maintenance Services, a Quote identifying the Software to be maintained and the total price for the associated Maintenance Services. 2.2.5 For Cloud Program Sales, the quantity of License Keys subscribed for, the duration (beginning and end) of the period of the Customer's subscription to the Cloud Program, the amount of Cloud Program Fees payable to Hexagon for the Cloud Program, and Cloud Services Schedule(s) associated with the ordered Cloud Applications. 2.2.6 For Subscription License Sales, a Quote identifying the name of the Subscription Licenses, the quantity of the Subscription Licenses being purchased, and the Subscription Term. 2.3 Change Control. During the course of Hexagon's performance under an Order, either Party may request a change in the scope of the Order in writing, delivered to the other Party's project manager. Any changes in price, schedule, or other terms must be documented either by an amendment or Change Order. No change, as contemplated in this paragraph, shall become effective until agreed to by both Parties in a -mutually executed writing. 2.4 Acceptance. Acceptance will occur based upon the following: 2.4.1 For Fixed Price Project Assignments, not governed by Exhibit F, acceptance shall occur when the applicable Task Acceptance Criteria has been satisfied in accordance with the Task Acceptance Process as set forth in an SOW. 2.4.2 For Time and Materials Project Assignments and Maintenance Services, the services are accepted as performed. 2.4.3 For a Software License Sale, once the Software has been delivered or access to the Software has been provided. 2.4.4 For a Cloud Program Sale, when the License Keys are provided to Customer 2.4.5 For a Subscription License Sale, once the applicable Subscription License(s) has been delivered or access to the Subscription License has been provided to the Customer. 3 Composition of the Master Agreement. 3.1 Components. The agreement between the Parties (herein referred to as the "Master Agreement") consists of: (1) the Primary Contracting Document, (2) these Master Terms (including the General Terms and Conditions and all Exhibits), (3) any amendments to the Master Agreement, (4) Orders, together with any Change Orders, that may be delivered, prepared, or issued after the Effective Date, and (5) all documents, including applicable documents referenced via hyperlink, incorporated by reference in the documents identified in this Section. For certain Third Party Software, Third Party Terms will also be applicable and be considered as part of the Master Agreement. 3.2 Order of Precedence. In the event of any conflict or inconsistency among documents forming the Master Agreement, the following order of precedence shall be used to determine the resolution of the discrepancy, unless the Parties mutually agree in writing to an alternative decision: (1) Any amendments to the Master Agreement; (2) The Primary Contracting Document; (3) Applicable Cloud Services Schedules and Training Program Statements; (4) These Master Terms (excluding exhibits); (5) Exhibits to these Master Terms; and Hexagon Master Terms and Conditions S1082020-MT Page 2 (6) Order Documents (exclusive of Cloud Services Schedules and Training Program Statements), as amended or modified by a change order. For only Third Party Software subject to Third Party Terms, the Third Party Terms shall have precedence in the event of a conflict between the Third Party Terms and any other terms of the Master Agreement. 4 Invoicing and Payment. 4.1 Invoices. Invoices shall be issued based upon the following: 4.1.1 For Software License Sales, Hexagon shall invoice Customer for the amount set forth in the Quote upon delivery of or access having been provided to the Software identified in the Order Documents; 4.1.2 Orders for Fixed Price Project Assignments shall be invoiced and become payable upon completion of a payment milestone identified in the SOW, or when applicable, in accordance with Exhibit F; 4.1.3 Time and Materials Project Assignments shall be billed and invoiced on a monthly basis as the hours are expended and Onsite Fees are incurred, or after all hours set forth in the Order Documents have been expended, whichever occurs first. 4.1.4 Orders for Maintenance Services shall be billed and invoiced in accordance with Exhibit B. 4.1.5 Cloud Program Sales shall be billed and invoiced in accordance with Exhibit D. 4.1.6 Orders for Subscription License Sales shall be billed and invoiced in accordance with Exhibit E. 4.2 Payment. Customer shall make payment for any invoices issued by Hexagon within thirty (30) calendar days of the date the invoice was issued. 4.3 Late Payment. If Customer does not make timely payment, an interest charge of two percent (2%) per Month (or the maximum allowed by law, whichever is less), which shall be compounded on a monthly basis, will be due on any unpaid and overdue amounts. To the extent the Customer is the subject of an applicable prompt pay act statute or ordinance, the Customer shall be subject to the terms set forth in that statute(s) and/or ordinance(s) in lieu of the prior sentence. 4.4 Taxes. The purchase price is exclusive of all Federal, State, or Local taxes. Any taxes applied to this sale by a Federal, State, or Local taxing authority will be the responsibility of Customer. Such taxes do not include franchise taxes or taxes based on net income. If Customer is claiming tax-exempt status, it must submit the proper documentation satisfactory to Hexagon evidencing its tax-exempt status. Applicable taxes may be invoiced at any time such taxes become fixed and certain. 5 Term and Termination. 5.1 Term. The Term of the Master Agreement shall begin on the Effective Date and remain in effect for a period of sixty (60) consecutive Months or until the Master Agreement is earlier terminated pursuant to the terms set forth herein or by mutual agreement of the Parties. An Order that is executed prior to the expiration of the term of the Master Agreement shall be governed by the Master Agreement even if the Master Agreement Term expires during the performance of the Order. To the extent Customer executes an Order pursuant to later issued master terms, then this Master Agreement shall terminate upon completion of all Orders executed hereunder regardless of the amount of time remaining in the Term. 5.2 Termination for Convenience. Except for Orders for Maintenance Services, Cloud Program Sales, and Subscription License Sales, either Party may terminate the Master Agreement or an Order in its sole discretion at any time upon providing the other Party with thirty (30) days written notice. The Coverage Period, Cloud Term, or Subscription Term, (if applicable) shall survive termination if the Master Agreement is terminated for convenience. In the event of a termination pursuant to this paragraph, Customer agrees to pay Hexagon for the Work performed and Software delivered and provided, plus the cost of any labor, equipment, or materials ordered in good faith prior to notice of termination that could not be canceled, less amounts previously paid by Customer for such Work and/or Software. To the extent a Party exercises its right to terminate a specific Order, that termination shall have no effect upon the remaining Master Agreement, which, along with any other active Orders, shall remain in full force and effect. If a Party desires to terminate the Master Agreement, then the Parties shall proceed to wind down all ongoing work under the Hexagon Master Terms and Conditions S1082020-MT Page 3 respective Orders in effect under the Master Agreement by the termination date. Each Party shall take commercially reasonable steps to bring the work to a close and to reduce its costs and expenditures. 5.3 Termination for Cause. Either Party may terminate the Master Agreement or a specific Order, as the case may be, in the event that other Party materially breaches a material term of the Master Agreement or any Order. 5.3.1 In the event a Party has materially breached an Order, the non -breaching Party may terminate the Order only after providing a sixty (60) calendar day cure period to cure such breach and the breach has not been cured, except for material breaches arising from non-payment. During the sixty (60) day cure period, the Parties shall try to determine a mutually agreeable plan to cure such breach. If such breach cannot be cured or an acceptable plan is not provided within the sixty (60) day cure period, the non -breaching Party may, but does not have the obligation to, terminate the Order. 5.3.2 In the event a Party has materially breached the Master Agreement or multiple Orders, the non -breaching Party may terminate the Master Agreement only after providing a sixty (60) calendar day cure period to cure such breach and the breach has not been cured except for material breaches arising from non-payment. During the sixty (60) day cure period, the Parties shall try to determine a mutually agreeable plan to cure such breach. If such breach cannot be cured or an acceptable plan is not provided within the sixty (60) day cure period, the non -breaching Party may, but does not have the obligation to, terminate the Master Agreement. If the Master Agreement is terminated pursuant to this paragraph, by the termination date, Hexagon will stop all Work pursuant to any Orders arising under the Master Agreement. In the event the Master Agreement is terminated for cause, Hexagon shall be entitled to, and Customer agrees to pay Hexagon, payment for all Work performed and Software provided on all ongoing Orders up to the termination date, less amounts previously paid by Customer under the affected Orders. 5.3.3 Notwithstanding the foregoing, Hexagon may suspend its performance of or terminate any Order or the Master Agreement for cause if payment is not received within thirty (30) days following the date when payment was due. In the event an Order is suspended or terminated for cause, Hexagon shall be entitled to, and Customer agrees to pay Hexagon, payment for Work performed and Software delivered on said Order up to the suspension or termination date, less amounts previously paid by Customer under the affected Orders. If Hexagon suspends an Order under this paragraph, then it may thereafter terminate the Order upon giving written notice to the Customer. 5.3.4 Notwithstanding the foregoing, Customer may not exercise a termination pursuant to the terms of Section 5.3 if Hexagon's material breach of the terms and conditions of the Master Agreement or any Order thereunder is caused or partially caused by Customer's negligence or failure to perform its obligations. 6 IP Ownership Customer acknowledges Hexagon will retain ownership and title of Hexagon IP made or provided pursuant to any Order. All Software provided under the Master Agreement is licensed to Customer in accordance with Exhibit A (End User License Agreement) except as it is inconsistent with the terms set forth herein. Third Party Software is licensed to Customer pursuant to Third Party Terms. 7 Warranties. 7.1 Software. The Software Products licensed under Exhibit A are warranted to substantially conform to the user documentation for a period of thirty (30) days from the initial installation; provided that Software Products covered by a Maintenance Contract between Customer and Hexagon shall instead be warranted and supported as stated in the Maintenance Contract. 7.2 Subsystem Warranty Coverage. For, and only for, new Subsystems procured/implemented pursuant to an Order under these Master Terms, the warranty coverage shall be set forth in the applicable SOW, which shall be in lieu of the warranty coverage set forth in Section 7.1. 7.3 Third -party Warranty Coverage. To the extent third -party products are supplied by Hexagon, those products are provided with a pass-thru-warranty from the original manufacturer, if any. 7.4 Disclaimer. Any product information Hexagon has shared with Customer during the proposal and/or contract activities to date was to provide an understanding of Hexagon's current expected direction, roadmap, or vision and is subject to change at any time at Hexagon's sole discretion. Hexagon specifically Hexagon Master Terms and Conditions S1082020-MT Page 4 disclaims all representations and warranties regarding future features or functionality to be provided in any Software or Deliverable. Hexagon does not commit to developing the future features, functions, and/or products discussed in this material beyond that which is specifically committed to being provided by Hexagon pursuant to a valid Order. Customer should not factor any future features, functions, or products into its current decisions since there is no assurance that such future features, functions, or products will be developed. When and if future features, functions, or products are developed, they may be made generally available for licensing by Hexagon. 7.5 Warranty Disclaimer. EXCEPT AS SPECIFICALLY SET FORTH IN THIS ARTICLE, HEXAGON DISCLAIMS (TO THE FULLEST EXTENT PERMITTED BY LAW) ALL WARRANTIES ON PRODUCTS FURNISHED PURSUANT TO THE MASTER AGREEMENT, INCLUDING ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE WARRANTIES SET FORTH IN THIS ARTICLE 7 IS IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED, AND, EXCEPT AS SET FORTH IN ARTICLE TITLED "INDEMNIFICATION PROVISIONS" BELOW, REPRESENTS THE FULL AND TOTAL WARRANTY OBLIGATION AND/OR LIABILITY OF HEXAGON. 8 LIMITATION OF LIABILITY IN NO EVENT WILL HEXAGON BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR SPECIAL DAMAGES, INCLUDING, BUT NOT LIMITED TO, LOST PROFITS, LOSS OF USE OR PRODUCTION, LOSS OF REVENUE, LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF HEXAGON HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. UNDER NO CIRCUMSTANCE WILL HEXAGON'S LIABILITY UNDER THIS MASTER AGREEMENT EXCEED THE AMOUNT THAT HEXAGON HAS BEEN PAID BY CUSTOMER UNDER THE INDIVIDUAL ORDER UNDER WHICH THE EVENT GIVING RISE TO THE CAUSE OF ACTION HAS OCCURRED. 9 Indemnification Provisions. 9.1 Subject to the limitation of liability provisions in the Master Agreement, Hexagon will defend, at its expense, a third party action, suit, or proceeding against Customer ("Claim"), and indemnify Customer from any judgments, settlements, and reasonable attorney's fees resulting therefrom, to the extent such Claim is (i) attributable to bodily injury, death, or physical damage to tangible property caused by Hexagon's negligent acts or omissions arising under the Master Agreement; or (ii) based upon an allegation that a Software Product, Customized Software, Cloud Application, or Services Deliverable as of its delivery date under the Master Agreement, infringes a valid United States: patent, copyright, or trademark, or misappropriates a third party's trade secret ("Infringement Claim"). 9.2 Hexagon's defense and indemnification obligations are conditioned upon: 9.2.1 Customer providing prompt written notice to Hexagon in writing of any Claim; 9.2.2 Hexagon having primary control of the defense of any actions and negotiations related to the defense or settlement of any Claim, understanding Hexagon may not settle a claim without Customer's consent if such settlement assigns fault or culpability to Customer; and 9.2.3 Customer cooperating fully in the defense or settlement of any Claim 9.3 Hexagon will have no obligation to defend Customer or to pay any resulting costs, damages, or attorneys' fees for any Infringement Claims alleging direct or contributory infringement of the Software Product, Cloud Program, or Service Deliverable (i) by the combination of or integration with a product, process, or system not supplied by Hexagon; (ii) by material alteration by anyone other than Hexagon or its subcontractors; (iii) by use after Customer has been notified of possible infringement; (iv) by use after modifications are provided to Customer; (v) by use after a return for refund as described below is ordered by Hexagon; (vi) if the creation of which was pursuant to specifications provided by Customer; or (vii) by use other than as specified in the documentation associated with the Software Product. 9.4 In connection with any Infringement Claims, Hexagon, at its own expense and option, may either (i) obtain rights for Customer to continue using the allegedly infringing Hexagon supplied item; (ii) replace the item with a non -infringing alternative, or modify the allegedly infringing elements of the item, while maintaining substantially similar software functionality or data/informational content; or (iii) refund to Customer a prorated portion of the license fees paid by Customer for the infringing item(s); provided that proration for perpetually licensed software shall be based on a five (5)-year, straight-line depreciation basis beginning from the initial date of delivery. In the event of a prorated return, Customer will uninstall, cease all use of and return to Hexagon the infringing item(s). Hexagon Master Terms and Conditions S1082020-MT Page 5 9.5 In no event will the indemnification for Infringement Claims apply to any Beta Software, or sample, hot fix, royalty free, or evaluation software delivered pursuant to the Master Agreement. 9.6 This section provides the sole and exclusive remedies of Customer and Hexagon's entire liability in the event of a Claim. Customer has no right to recover and Hexagon has no obligation to provide any other or further remedies, whether under another provision of the Master Agreement or any other legal theory or principle in connection with a Claim. 10 Insurance. 10.1 Policies and Coverage Amounts. Hexagon agrees to procure and maintain in force during the term of the Master Agreement, at its own cost, the following policies and amounts of coverage: 10.1.1 Workers' Compensation Insurance as required state statute or regulation 10.1.2 Commercial General Liability Insurance with minimum combined single limits of ONE MILLION DOLLARS ($1,000,000) each occurrence and ONE MILLION DOLLARS ($1,000,000) general aggregate. The policy shall be applicable to all premises and operations. The policy shall include coverage for bodily injury, broad form property damage, and personal injury. 10.1.3 Automobile Liability Insurance with minimum combined single limits for bodily injury and property damage of not less than ONE MILLION DOLLARS ($1,000,000) for any one occurrence, with respect to each of Hexagon's owned, hired or non -owned vehicles assigned to or used in performance of the services or work under the Master Agreement. 10.1.4 Umbrella/Excess Coverage with minimum combined single limits of ONE MILLION DOLLARS ($1,000,000) per occurrence. 10.2 Policy Maintenance. Hexagon shall procure and maintain, and shall cause any subcontractor of Hexagon to procure and maintain, the minimum insurance coverages listed herein. All policies shall be continuously maintained for the term of the Master Agreement. 10.3 Certificate of Insurance. A Certificate of Insurance shall be completed by Hexagon's insurance agent(s) as evidence that policies providing the required coverage amounts, conditions, and minimum limits are in full force. The completed Certificate of Insurance shall be sent to the contact person identified in the Primary Contracting Document. 10.4 Insurance Deductible. Hexagon shall be solely responsible for any deductible losses under the policies required above. 11 Security and Breach Notification. 11.1 Hexagon shall take reasonable industry action to prevent, detect, identify, report, track and respond to Security Incidents. In the event of a Security Incident, Hexagon will provide a Security Incident report to the Customer or its Affiliates via the support website or Cloud Portal (as applicable). The report shall be provided within twenty-four (24) Business Hours following Hexagon's discovery, confirmation, and investigation of a Security Incident. 12 Dispute Resolution. 12.1 Resolution Protocol. The Parties shall exercise their best efforts to negotiate and settle promptly any dispute that may arise with respect to the Master Agreement or Order made pursuant to the Master Agreement ("Dispute") in accordance with the provisions set forth herein. If either Party disputes any provision of the Master Agreement (the "Disputing Party"), or the interpretation thereof, or any conduct by the other Party under the Master Agreement, that Party shall bring the matter to the attention of the other Party at the earliest possible time in order to resolve the Dispute except for Disputes for non-payment. If such dispute is not promptly resolved by the employees responsible for the subject matter of the dispute, the Disputing Party shall be permitted to deliver to the non -Disputing Party contact person identified in the Primary Contracting Document a written notice of the dispute, whereupon the Parties shall endeavor in good faith to escalate the dispute to appropriate executives for each Party for resolution within fifteen (15) business days, or such longer period as to which the Parties may mutually agree. 12.2 Mediation. To the extent a dispute is not resolved through the process outlined in the previous section and remains unresolved, the Parties agree to enter into non -binding mediation to resolve the dispute. Within sixty (60) calendar days, of the issuance of the Dispute Notice, or such longer period that is mutually agreeable to the Parties, the Parties agree to identify a mutually acceptable mediator who shall Hexagon Master Terms and Conditions S1082020-MT Page 6 mediate the dispute. If after making reasonable efforts to identify a mutually acceptable mediator and no later than fifty (50) calendar days after the issuance of the Dispute Notice, the Parties are unable to identify such a mediator, the Disputing Party shall provide the non -disputing party with a list of five (5) proposed mediators. The non -disputing Party shall have five (5) business days from receipt of such list from the Disputing Party to identify one proposed mediator on the list to use as a mediator. If the non -disputing Party fails to identify and communicate its choice to the Disputing Party in the time allotted, then the Disputing Party shall be permitted to unilaterally identify the mediator from the list of five (5) mediators previously given who shall mediate the Dispute. The mediator shall be an attorney licensed to practice law in the state courts identified in section below titled "Governing Law." Subject to the mediator's availability, the Parties agree to mediate the dispute within thirty (30) days after the Parties have identified a mediator who has agreed to mediate the dispute. To the extent the mutually identified mediator is unavailable, unwilling, or unable to mediate the Dispute, the Parties shall utilize the same steps listed above to identify a new mutually agreeable mediator. To the extent the Disputing Party had to prepare a list of proposed mediators previously, it shall prepare and transmit a revised list within five (5) business days of receiving notice of the proposed mediator's unavailability. Subject to the mediator's requirements, the Parties agree they shall be permitted to attend the mediation via telephone or video conferencing. The Parties agree to pay in equal shares the mediator's fee and expenses unless otherwise agreed to pursuant to a settlement agreement. 12.3 Prerequisites to Litigation. Except for disputes for non-payment, only after the Parties have endeavored to resolve the dispute through the processes outlined in the immediately preceding two sections may a Party commence litigation to resolve the dispute. 12.4 Injunctive Relief. Notwithstanding the foregoing, either Party may, before or during the exercise of the informal dispute resolution procedures set forth above, apply to a court identified in the section titled "Governing Law" for a temporary restraining order or preliminary injunction where such relief is necessary to protect its interests pending completion of such informal dispute resolution procedures. 13 Notices. All notices given between the Parties shall be in writing and shall be considered properly sent by postage prepaid United States Mail or overnight carrier to the Customer and/or Hexagon representative, as applicable and identified in the Primary Contracting Document, or such substitutes as may hereafter be disclosed by proper notification. 14 Force Majeure. Neither Party shall be deemed to be in default of any provision of the Master Agreement or an Order or be liable for any delay, failure in performance, or interruption of service resulting from acts of war, acts of terrorism, criminal acts, acts of God, natural disaster, fire, lightning, acts of or restriction imposed by civil or military authority, pandemics, epidemics, cyber-attack, labor disruption, civil disturbance, expropriation, embargo, lawful export restriction, or any other cause beyond its reasonable control. This section does not relieve or suspend a Party's obligation to pay money to the other Party under the terms of the Master Agreement. 15 Place of Performance. To the extent necessary, Customer agrees to provide appropriate work space and work place accommodations; computer equipment; software; access to relevant data, documents, plans, reports, and analyses; and necessary access to Hexagon personnel to perform work on an Order. To the extent work is performed remotely, Customer must provide VPN or secured remote connectivity (including a login and password) to all servers and workstations requiring installation/configuration by Hexagon. 16 Amendments. Any and all amendments to the Master Agreement shall specifically reference the fact the amendment is intended to alter these Master Terms. No Order or Change Order shall affect these Master Terms. 17 Confidential Information. The Parties agree not to disclose Confidential Information provided to it by the Disclosing Party to the maximum extent allowable under applicable law unless it first obtains the Disclosing Party's written consent to such disclosure. It is further understood and agreed that money damages may not be a sufficient remedy for any breach of this provision of the Master Agreement by the Receiving Party and the Disclosing Party may be entitled to seek equitable relief, including injunction and specific performance, as a remedy for any Hexagon Master Terms and Conditions S1082020-MT Page 7 such breach. Such remedies shall not be deemed to be the exclusive remedies for a breach of this provision of the Master Agreement but will be in addition to all other remedies available at law or equity. The covenants set forth herein and the rights and obligations related thereto shall continue for a period of five (5) years from the date of disclosure. 18 Personal Data. 18.1 Where Personal Data is provided by the Customer to Hexagon, the Customer shall act as the data controller and shall be responsible for complying with all applicable data protection laws. Hexagon shall act as the data processor in respect of such Personal Data and shall process the Personal Data in accordance with applicable data protection laws. The Customer acknowledges and agrees that Hexagon is not capable of being a data controller due to Hexagon's inability to determine the purpose and means of the processing of Personal Data provided by Customer to Hexagon. To the extent that: (a) Personal Data of Users or Authorized Cloud Users provided by the Customer to Hexagon pursuant to the Master Agreement is subject to the European Union General Data Protection Regulation 2016/679, as may be amended from time to time ("GDPR"); and (b) the Customer and Hexagon do not have a separate, written data processing agreement, then the Customer and Hexagon agree that the terms of Hexagon's Data Processing Addendum, as updated from time to time, found at: https://www.hexagonsafetyinfrastructure.com/- /media/Legal/Hexagon/SI/Policies/DPA/DPALP/DPA LP 08-2019.pdf, shall apply. 18.2 Where Customer is responsible for providing Personal Data on behalf of Users or Authorized Cloud Users directly to Hexagon, Customer will secure and maintain all necessary consents and make all necessary disclosures before including Personal Data in Customer Data input to, or otherwise supplied to Hexagon. In the event Customer, including all its Users, does not consent to Personal Data being processed as a result of the Master Agreement, Customer acknowledges Hexagon may be unable to provide Services, Software Products, Maintenance Services, and/or Cloud Program (or part thereof). 18.3 Hexagon will only process Customer supplied Personal Data in accordance with the Customer's lawful instructions and to the extent and as necessarily required to provide the applicable goods and services under the Master Agreement and for no other purpose. Except as may be otherwise required by law, contract, or judicial order, after expiration or earlier termination of the Master Agreement, Hexagon will destroy all Customer -supplied Personal Data in accordance with applicable data protection laws. 18.4 If Hexagon supplies maintenance, support, or subscription services to Customer with respect to third -party products, and if the third -party supplier or proprietor of such requires Customer be party to any data processing agreement in connection therewith, and if Customer has not separately executed an instrument to satisfy such requirement, then Customer and Hexagon agree that the terms of the applicable third -party data processing agreement, as updated from time to time, found at https://www.hexagonsafetyinfrastructure.com/- /media/Legal/Hexagon/SI/Policies/DPA/DPALP/DPA LP 08-2019.pdf, shall apply. 19 Assignment. Neither Party shall assign, sublet, or transfer all or any portion of the Master Agreement, nor any interest in the Master Agreement, without the express written consent of the non -assigning Party, which consent may be granted or withheld in the sole discretion of the non -assigning Party. Notwithstanding the foregoing, Hexagon may assign its rights and obligations under the Master Agreement, without the approval of Customer to: (1) an Affiliate or (2) another business entity in connection with a merger, consolidation, or reorganization of Hexagon or any of its subsidiaries. If Customer is a government entity, another government entity (referred to in this paragraph as a cooperative purchaser) may, with prior written consent of Hexagon, use the Master Agreement, excluding Orders to which it is not a party, as a contract vehicle for its purchases from Hexagon; provided that in such event the term "Customer" shall refer solely to the relevant cooperative purchaser with respect to its transaction and shall not refer to the cooperative purchaser with respect to transactions not for its direct benefit. Software, services, hardware, and maintenance will be priced and scoped upon request of the cooperative purchaser and dependent upon the scope of the intended project. To the extent this clause is exercised by any cooperative purchaser with Hexagon's consent, Hexagon shall deal directly with the cooperative purchaser regarding the scope and pricing of the project. Cooperative purchasers shall make their own legal determination as to whether the collective purchasing permitted by this clause is consistent with laws, regulations, and other policies applicable to the cooperative purchaser; and, Customer shall have no liability with respect to obligations of any cooperative purchaser utilizing the terms of this section 19 to place Orders under the Master Agreement. Hexagon Master Terms and Conditions S1082020-MT Page 8 20 Export. Hexagon IP, including any technical data related to Software, Services, Maintenance Services, or Cloud Programs is subject to the export control laws and regulations of the United States. Diversion contrary to United States law is prohibited. Hexagon IP, including any technical data related to Software, Services, Maintenance Services, or Cloud Programs shall not be exported or re-exported, directly or indirectly (including via remote access), under the following circumstances: • To Cuba, Iran, North Korea, Syria, the Crimean region of Ukraine or any national of these countries or territories. • To any person or entity listed on any United States government denial list, including, but not limited to, the United States Department of Commerce Denied Persons, Entities, and Unverified Lists, the United States Department of Treasury Specially Designated Nationals List, and the United States Department of State Debarred List (http://export.gov/ecr/eg_main_023148.asp). • To any entity if Customer knows, or has reason to know, the end use is related to the design, development, production, or use of missiles, chemical, biological, or nuclear weapons, or other unsafeguarded or sensitive nuclear uses. • To any entity if Customer knows, or has reason to know, that a reshipment contrary to United States law or regulation will take place. Customer agrees to hold harmless and indemnify Hexagon and its Affiliates for any causes of actions, claims, costs, expenses and/or damages resulting to Hexagon from a breach of the export restrictions set forth in the Master Agreement by Customer or any User. Any questions regarding export or re-export of the Software should be addressed to Hexagon's Export Compliance Department at 305 Intergraph Way, Madison, Alabama, 35758, USA or at exportcompliancea-intergraph.com. If the Software Customer received is identified on the media as being ITAR-controlled, the Software has been determined to be a defense article subject to the U.S. International Traffic in Arms Regulations ("ITAR"). Export of the Software from the United States must be covered by a license issued by the Directorate of Defense Trade Controls ("DDTC") of the U.S. Department of State or by an ITAR license exemption. The Software may not be resold, diverted, or transferred to any country or any end user, or used in any country or by any end user other than as authorized by the existing license or ITAR exemption. Subject to the terms of the EULA included herein, a Software Product may be used in other countries or by other end users if prior written approval of DDTC is obtained. If Customer is located outside the United States, Customer is responsible for complying with any local laws in Customer's jurisdiction which might impact Customer's right to import, export or use the Software, and Customer represents that Customer has complied with any and all regulations or registration procedures required by applicable law related to the use and importation of the Software Products. 21 Non -Solicitation of Employees. Customer agrees it will not, without the prior written consent of Hexagon, solicit any Hexagon employee, or induce such employee to leave Hexagon's employment, directly or indirectly, during the Term and for a period of twelve (12) Months after the Master Agreement expires or is terminated. 22 Miscellaneous. 22.1 Authority. Each Party represents and certifies to the other Party it has the requisite legal authority to enter into and be bound by the Master Agreement and all Orders arising from the Master Agreement. Any individual purporting to execute or accept a Quote, Primary Contracting Document, or any Order Documents governed by the Master Terms on behalf of a Party represents and warrants to the other Party that such individual has the authority to bind, and does bind, the Party on whose behalf such individual purports to execute or accept such instrument(s). 22.2 Survival. In addition to other provisions that are specifically identified as surviving termination of this Master Agreement, the rights and obligations in sections titled "IP Ownership", "Limitation of Liability", "Dispute Resolution", "Confidential Information", "Export", and the terms of any license or access granted pursuant to the Master Agreement (including, but not limited to, Exhibit A, Exhibit D, and/or Exhibit E), shall survive and continue after expiration or termination of the Master Agreement, shall remain in effect until fulfilled, and shall apply to any permitted successors and assigns. Upon termination of the Master Agreement, the provisions of the Master Agreement, including those in the preceding sentence, which by their express terms survive termination, shall remain in full force and effect. Hexagon Master Terms and Conditions S1082020-MT Page 9 22.3 Waiver. The waiver by either Party of any of its rights or remedies in enforcing any action or breach under the Master Agreement in a particular instance shall not be considered as a waiver of the same or different rights, remedies, or actions for breach in subsequent instances. 22.4 Severability. If any provision of the Master Agreement or an Order is void, voidable, unenforceable, or illegal in its terms, but would not be so if it were rewritten to eliminate such terms that were found to be voidable, unenforceable, or illegal and such rewrite would not affect the intent of the provision, then the provision must be rewritten to be enforceable and legal. 22.5 Headings. Numbered topical headings, articles, paragraphs, subparagraphs or titles in the Master Agreement are inserted for the convenience of organization and reference and are not intended to affect the interpretation or construction of the terms thereof. 22.6 Governing Law. The Master Agreement shall for all purposes be construed and enforced under and in accordance with the laws applicable to and governing the Customer's location as identified in applicable Order Documents. The Parties agree any legal action or proceeding relating to the Master Agreement shall be instituted in an appropriate court having personal jurisdiction over Customer. The Parties agree to submit to the jurisdiction of and agree that venue is proper in these courts in any such legal action or proceeding. The Parties waive the application of the United Nations Commission on International Trade Law and United Nations Convention on Contracts for the International Sale of Goods as to the interpretation or enforcement of the Master Agreement. 22.7 Governing Language. The controlling language of the Master Agreement is English. If Customer received a translation of the Master Agreement into another language, it has been provided for convenience only. Les parties confirment que ]'accord -cadre et toute la documentation connexe sont et seront en anglais. (Translation: "The Parties confirm that the Master Agreement and all related documentation is and will be in the English language.") 22.8 Independent Contractor. The Parties agree that Hexagon is an independent contractor, that nothing in the Master Agreement shall be construed as establishing or implying a relationship of master and servant between the Parties, or any joint venture or partnership between the Parties, and that nothing in the Master Agreement shall be deemed to constitute either of the Parties as the agent of the other Party or authorize either Party to incur any expenses on behalf of the other Party or to commit the other Party in any way whatsoever. Hexagon and its agents, employees, or subcontractors shall at no time be deemed to be agents, employees, or subcontractors of Customer, or be deemed to be under the control or supervision of Customer when carrying out the performance of its obligations in the Master Agreement. Without the prior written consent of Customer, Hexagon shall not carry on any activity that could be construed as being on behalf of Customer. 22.9 Limitation on Claims. Except as otherwise prohibited from applicable law, no claim, regardless of form, arising out of or in connection with the Master Agreement may be brought by Customer more than two (2) years after the event giving rise to the cause of action has occurred. 22.10 Anti -Bribery. Each Party hereby certifies it shall comply with all applicable laws in carrying out its duties under the Master Agreement, including, but not limited to, the United States Foreign Corrupt Practices Act ("FCPA"). In particular, Customer, on behalf of itself and its Affiliates, and Hexagon, each severally represent and agree that: Such party is familiar with the FCPA and its purposes and agrees to comply with the acts. Specifically, such party is aware of and will comply with the FCPA's prohibition of the payment or the gift of any item of value, either directly or indirectly, to an official of a government, political party or party official, candidate for political office, or official of a public international organization, for the purpose of influencing an act or decision in his/her official capacity, or inducing him/her to use his/her influence with the government to assist a company in obtaining or retaining business for, with, or in that country or directing business to any person; Such party has not made, and will not make, payments to third parties which such party knows or has reason to know are illegal under the FCPA, or the laws of any applicable jurisdiction; The method of making payment to Hexagon as provided hereunder is not in violation of the law of any applicable jurisdiction. Either Customer or Hexagon has the right to terminate the Master Agreement upon any violation of the FCPA or similar laws by the other Party. 22.11 Hexagon Authority. BY ISSUANCE OF A QUOTE TO CUSTOMER WITHOUT THE WORD "DRAFT" OR SIMILAR MARKINGS OR DISCLAIMERS THEREON, HEXAGON REPRESENTS IT HAS THE REQUISITE LEGAL AUTHORITY TO ENTER INTO AND BE BOUND BY THE MASTER Hexagon Master Terms and Conditions S1082020-MT Page 10 AGREEMENT AND THE ORDER INTENDED TO RESULT FROM THE QUOTE. BY EXECUTING THE QUOTE AND RETURNING IT TO HEXAGON OR OTHERWISE ENTERING INTO AN ORDER, CUSTOMER REPRESENTS AND CERTIFIES TO HEXAGON IT HAS THE REQUISITE LEGAL AUTHORITY TO ENTER INTO AND BE BOUND BY THE MASTER AGREEMENT AND THE ORDER ASSOCIATED THEREWITH. 23 Entire Agreement. The Master Agreement constitutes the entire agreement between the Parties with regard to the subject matter hereof. Except as otherwise provided in the Primary Contracting Document, the Master Agreement supersedes any and all prior discussions and/or representations, whether written or oral, and no reference to prior dealings may be used to in any way modify the expressed understandings of the Master Agreement. Any future representations, promises and oral agreements related to the products, product features, future product enhancements, product functionality, or services covered by the Master Agreement will be of no force or effect unless reduced in writing and made a part of the Master Agreement or an Order thereto. The Master Agreement may not be amended or modified unless so done in a writing signed by authorized representatives of both Parties. The pre-printed terms and conditions of Customer's PO or any other terms and conditions of a Customer PO shall be void, even if issued subsequent to the effective date of the Master Agreement, and shall not be deemed to constitute a change to the Master Agreement. Hexagon Master Terms and Conditions S1082020-MT Page 11 EXHIBIT A END -USER LICENSE AGREEMENT IMPORTANT —READ CAREFULLY: This EULA is a legal agreement by and between User and Hexagon for the Software Product. Software Products are also subject to the Use Terms. Any software, including, without limitation, any third party components and/or Upgrades, associated with a separate end -user license agreement is licensed to User under the terms of that license agreement. Use Terms delivered with an Update or Upgrade of a Software Product shall apply to the Update/Upgrade. All use of the Software Product is subject to applicable Order Documents. 1.0 LICENSE GRANT. Provided User is not in breach of any term or condition of this EULA, Hexagon hereby grants User a limited, non-exclusive license up to the quantity of Software Product licenses purchased by User to: (i) install and use the Software Product, in object code form only; (ii) use, read, and modify documentation prepared by Hexagon and delivered to User pursuant to the Order Documents; and/or (iii) view and/or use Hexagon audio-visual training materials provided to User pursuant to the Order Documents; provided all of the foregoing shall be strictly for User's internal use and strictly in accordance with this EULA and the applicable Order Documents. The license is non -transferable, except as specifically set forth in this EULA. User assumes full responsibility for the selection of the Software Product to achieve User's intended results, and for the installation, use and results obtained from the Software Product. 2.0 UPDATES AND UPGRADES. If the Software Product is an Update to a previous version of the Software Product, User must possess a valid license to such previous version to use the Update. Neither the Software Product nor any previous version may be used by or transferred to a third party. All Upgrades are provided to User on a license exchange basis and are subject to all of the terms and conditions of the EULA provided with the Upgrade. By using an Update, User (i) agrees to voluntarily terminate User's right to use any previous version of the Software Product, except to the extent that the previous version is required to transition to the Update or Upgrade; and (ii) acknowledges and agrees that any obligation that Hexagon may have to support the previous version(s) of the Software Product will end upon availability of the Update. If an Update is provided, User will take prompt action to install such Update as directed by Hexagon. If User fails to do so, User acknowledges that the Software Product may not work correctly or that User will not be able to take advantage of all of the Software Product's available features. In such event, Hexagon will not be liable for additional costs User incurs because of User's failure to install such Update. 3.0 RIGHTS AND LIMITATIONS. 3.1 The Following are Permitted for User's License: User may make one copy of the Software Product media in machine readable or printed form and solely for backup purposes. Hexagon retains ownership of all User created copies. User may not transfer the rights to a backup copy unless User transfers all rights in the Software Product and license as provided for in Section 3.2.1. Any other copying of the Software Product, any use of copies exceeding the number of copies User has been authorized to use and has paid for, and any distribution of the Software Product not expressly permitted by this EULA, is a violation of this EULA and of federal and/or applicable governing law. 3.2 The Following are Prohibited for User's License: 3.2.1 User shall not sell, rent, license, lease, lend or otherwise transfer the Software Product, or any copy, modification, or merged portion thereof without Hexagon's express written consent for such transfer, which consent may not be unreasonably withheld. Any such unauthorized transfer will result in automatic and immediate termination of the license. 3.2.2 The Software Product is licensed as a single product. User shall not, and User shall not authorize anyone else to: (i) decompile, disassemble, or otherwise reverse engineer the Software Product; (ii) work around any technical limitations Hexagon Master Terms and Conditions S1082020-MT Page 12 in the Software Product; (iii) publish the Software Product for others to copy or use; (iv) use, copy, modify, distribute, disclose, license or transfer the Software Product, or any copy, modification, or merged portion, in whole or in part, except as expressly provided for in this EULA; (v) re -use the component parts of the Software Product with a different software product from the one User is licensed to use or on different computers; (vi) circumvent any license mechanism or in the Software Product or the licensing policy; (vii) publish to a third party any results of benchmark tests run on the Software Product (viii) use or view the Software Product for any purposes competitive with those of Hexagon; (ix) use the Software Product except as expressly set forth in this EULA; and (x) unless otherwise specifically permitted in writing by Hexagon, use the Software Product outside the country in which it is licensed. 3.3 Fault Tolerance. The Software Product is not one hundred percent (100%) fault -tolerant. Unless the Software Product's documentation expressly provides the contrary: Software Product is not designed or intended for use in any situation where failure or fault of any kind of the Software Product could lead to death or serious bodily injury of any person, or to severe physical, property or environmental damage ("High -Risk Use"); and, User is not licensed to use the Software Product in, or in conjunction with, any High -Risk Use. High -Risk Use is STRICTLY PROHIBITED. High Risk Use includes, for example, the following: operation of aircraft or other modes of human mass transportation, nuclear or chemical facilities, and Class III medical devices. User hereby agrees not to use the Software Product in, or in connection with, any High -Risk Use. High Risk Use shall not mean use of the Software Product for purposes for which it is regularly marketed and sold (e.g. public safety and utility dispatch software may be used to dispatch police, fire, emergency medical services, and emergency utility services). 3.4 Licensing Mechanism Disclaimer. Without waiver of any of its rights herein, Hexagon may at its sole discretion provide User who is operating public safety Software Products a licensing mechanism to allow such Software Products to be available for use even when User has accessed all of its purchased licenses. Regardless of whether it receives the licensing mechanism, User acknowledges it is permitted to use the Software Products only up to the number of licenses it has purchased. Any usage of Software Products beyond the amount purchased by User will be subject to the payment of additional fees by User to Hexagon at then current prices for the Software Products in like manner as provided in Section 6.2 (Audit). 4 USER OBLIGATIONS. 4.1 The Software Product may require User's System to comply with specific minimum software, hardware and/or Internet connection requirements. The specific minimum software, hardware and/or Internet connection requirements vary by Software Product and type of license and are available from Hexagon upon request. 4.2 User is responsible, and bears the sole risk, for backing up all systems, software, applications, and data, as well as properly using the Software Product. 4.3 At all times, User must keep, reproduce and include all copyright, patent, trademark and attribution notices on any copy, modification or portion of the Software Product, including, without limitation, when installed, used, checked out, checked in and/or merged into another program. 4.4 User shall comply with the Use Terms, including limitations that apply to specific types of licenses identified therein. 5 TERM. 5.1 For a Perpetual License, this EULA is effective until terminated (a) by User, by returning to Hexagon the original Software Product or by permanently destroying the Software Product, together with all copies, modifications and merged portions in any form; (b) by Hexagon, upon User's breach of any of the terms hereof or User's failure to pay the appropriate license or subscription fee(s); (c) upon User's installation of an Upgrade that is Hexagon Master Terms and Conditions S1082020-MT Page 13 accompanied by a new license agreement covering the Software Product Upgrade; or (d) by expiration of the applicable license files, if this is a temporary license. User agrees upon the termination of this EULA to cease using and to permanently destroy the Software Product (and any copies, modifications and merged portions of the Software Product in any form, and all of the component parts of the Software Product) and certify such destruction in writing to Hexagon. For a Subscription License, this EULA is effective until the User's Subscription Term expires without being renewed; by Hexagon upon User's breach of any of the terms hereof or User's failure to pay the appropriate Subscription License fee(s); or the Subscription is otherwise terminated. User agrees upon the termination of this EULA or expiration of User's Subscription to cease using and to permanently destroy the Software Product (and any copies, modifications and merged portions of the Software Product in any form, and all of the component parts of the Software Product) and certify such destruction in writing to Hexagon. 6 AUDIT. 6.1 Hexagon shall have the right to: 6.1.1 Audit User's use of the Software Product and User's compliance with the provisions of this EULA during User's normal business hours. Hexagon will provide User with thirty (30) days prior written notice of an audit under this Section. Hexagon's right to conduct this type audit shall be limited to twice per calendar year. Prior to the start of an audit, Hexagon's personnel will sign a reasonable non -disclosure agreement provided by User. During the audit, User shall allow Hexagon's personnel to be provided reasonable access to both User's records and personnel. 6.1.2 Obtain certain documentation from User, as follows. If the Software Product includes logging mechanisms intended to track usage volume or quantity, User shall transmit log files associated therewith to Hexagon upon Hexagon's demand and in accordance with Hexagon's reasonable transmission instructions. Hexagon will not demand the transmission of usage tracking log files more frequently than four (4) times in any calendar year. 6.2 In the event the results of the audit in Section 6.1.1 or the documentation provided by User in Section 6.1.2 indicate User has used unlicensed Software Products or quantities thereof, User agrees to promptly pay Hexagon: (i) the current list price for each unlicensed Software Product(s) used by User (ii) interest of two percent (2%) per month or the highest rate allowed by applicable law for each month, commencing with the initial month of unlicensed usage of the Software Product(s), and (iii) the costs for the audit in Section 6.1.1. END OF EXHIBIT A Hexagon Master Terms and Conditions S1082020-MT Page 14 EXHIBIT B MAINTENANCE TERMS AND CONDITIONS FOR SOFTWARE These terms and conditions ("Maintenance Terms") govern the provision of maintenance and support services by Hexagon with respect to Covered Products. 1. DEFINITIONS. All capitalized terms not otherwise defined herein shall have the meaning set forth in the associated Exhibit titled "Common Terms Glossary." 2. TERM. 2.1. Term. The Maintenance Contract shall begin, retroactively (if applicable), on the first calendar day of the first Month of the Coverage Period and shall expire on the last calendar day of the last Month of the Coverage Period. The Coverage Period shall be for whole Months only. 2.2. Renewal. Prior to expiration of the Coverage Period, Hexagon may submit to Customer a renewal quote with pricing for extension of the Coverage Period. The Parties may extend the Coverage Period pursuant to Order Documents. 2.3. Lapse. In the event of a Lapse: (i) Hexagon shall, at any time, be entitled to discontinue Maintenance Services, in whole or in part, for the affected Covered Products; (ii) Hexagon shall be relieved of any previously provided pricing commitments or options for Maintenance Services, if any, related to time periods following the Lapse; and, (iii) Hexagon may permit Customer to reinstate support for Covered Products pursuant to Hexagon's then current policies and practices, including any policies or practices related to payment of reinstatement fees. 3. SCOPE OF COVERAGE FOR COVERED SOFTWARE PRODUCTS. Maintenance Services described in this Section apply to Covered Software Products only. Maintenance Services for Covered Third Party Products are separately stated. Hexagon offers three levels of Maintenance Services for Covered Software Products, dependent upon the Software Product and other factors. Under all levels of Maintenance Service, Hexagon shall provide reasonable commercial efforts to aid in the diagnosis of Defects. Under all levels of Maintenance Services, but only until the subject Software Product version reaches Version Limitation I or Version Limitation II, Hexagon shall provide reasonable commercial efforts to aid in correction of Defects. After a Software Product version reaches Version Limitation I, but only until the subject Software Product reaches Version Limitation II, Hexagon shall provide reasonable commercial efforts to aid in correction of Level One Defects only. The level of Maintenance Services for each Software Product is identified in the Order Documents, subject however to Version Limitations. Defect corrections provided by Hexagon shall, unless otherwise agreed by Hexagon, be delivered within Hexagon's product releases, and in accordance with Hexagon's standardized release cycles. Levels of Maintenance Services are as follows: 3.1. Advantage Support. Advantage Support will include and be limited to the diagnostic and Defect correction support as described above, and the following: Out -of -the -box functionality support via the support help desk (telephone or eService via Hexagon's support website where available at https://support.hexagonsafetyinfrastructure.com; and, access to any applicable Hexagon problem knowledge base online self-help tool. Phone support is available Monday through Friday from 8AM — 5PM at Customer's local time, excluding Hexagon -observed holidays. Local variances in support hours will be posted on the Customer Support Web Site or applicable local support website or can be determined by contacting Customer's local Hexagon office. 3.2. Standard Support. Standard Support will include and be limited to the following: 3.2.1. All features of Advantage Support. Hexagon Master Terms and Conditions S1082020-MT Page 15 3.2.2. Access to available Updates of Covered Software Products. Hexagon will notify Customer when Updates are made available for any Covered Software Products for which Maintenance Service have been purchased, by way of posting notices of such to the "Support Notices and Announcements" section on the Customer Support Web Site or applicable local support website or via direct notification by Hexagon. Updates are shipped to Customer upon Customer request, logged in the Customer Support Web Site. Hexagon is not obligated to produce any Updates. For avoidance of doubt, a Customer's entitlement to Updates shall not include entitlement to any therein embedded or otherwise related module or function which is licensed and priced separately from Covered Product(s) for which Customer has purchased an entitlement to Updates. 3.3. Premium Support. Premium Support will include all features available under Standard Support (subject to Version Limitations). Additionally, for a Level 1 Defect, phone support is also available after-hours and on Hexagon -observed holidays. 3.4 Product Change Requests (also referred to as CR-E) will be reported in like manner as set forth in Section 3.1. Hexagon will review Product Change Requests and at its sole discretion decide whether to make the requested change to the Covered Product(s) through an Update. Product Change Requests not accepted may be the subject of a separate contract between the Parties. For the avoidance of doubt, to the extent Hexagon agrees to make a requested change to a Covered Product pursuant to a Product Change Request, any and all IPR resulting from the Update including the change or modification is and shall remain the property of Hexagon. 4. MINIMUM SYSTEM REQUIREMENTS; CUSTOMER'S OBLIGATIONS. Performance of Maintenance Services by Hexagon is specifically conditioned upon the following minimum system requirements and fulfillment by Customer of the following obligations (collectively, minimum system requirements and customer obligations hereinafter referred to as "Customer Obligations"): 4.1. System Requirements. Customer is responsible for ensuring: the System Equipment and network infrastructure meet minimum system requirements specified by Hexagon and made available to Customer upon request; its System Equipment and network infrastructure are adjusted as required to accommodate Updates of Covered Products; compatibility of non - Hexagon provided products with products provided by Hexagon; and, its systems, software, and data are adequately backed up. Hexagon is not liable for lost data. 4.2. Hexagon Access and Customer Cooperation. Customer's system and/or System Equipment must have input and output devices that enable the use of Hexagon's diagnostic programs and supplemental tests. Customer will permit Hexagon to electronically access Customer's system via SecureLinkTM, a tool providing secure, auditable remote access to Customer's system for Hexagon to effectively render Maintenance Services. Customer will ensure availability of its own system technical support personnel so that Hexagon can fulfill its Maintenance Services obligations. When reporting problems to Hexagon's support help desk, Customer will provide a complete problem description, along with all necessary documents and information that is available to Customer and required by Hexagon to diagnose and resolve the problem. Customer will grant all necessary access to all required systems as well as to the Covered Products, and any other reasonable assistance needed. Customer will carry out any reasonable instructions and will install any necessary patches, Defect corrections, or Updates. Customer will appoint a minimum of two and a maximum of three contact people who are each authorized to make use of the Maintenance Services ("Authorized Contacts"). Customer must assure Authorized Contacts have adequate expertise, training, and experience to provide professionally accurate descriptions of malfunctions and facilitate Hexagon's efficient response. Authorized Contacts must have successfully completed Hexagon product training or complete it at the next available scheduled opportunity, for those products for which formal training is available. Customer will bear the cost of this training. Customer is obligated to select only those personnel for this task who are suitable for it by means of training and function, and who have knowledge of Customer's operating system, network, and hardware and software. Customer agrees to promptly notify Hexagon of any replacement of an Authorized Contact. Hexagon Master Terms and Conditions S1082020-MT Page 16 5. EXCLUDED SOFTWARE SERVICES. Services for the following are outside the scope of the Maintenance Contract and may be available under separate Order at an additional charge (collectively "Excluded Services"): 5.1. Installation of any Covered Product, Update, or interface software. 5.2. Network configuration. 5.3. Configuration or customization of Covered Products to Customer or other third party requirements (except as necessary to remedy a Defect). 5.4. System -level tuning and optimization and system administration support. 5.5. Training. 5.6. Services required because the Authorized Contact is not available or is not trained. 5.7. On -site services (unless waived by Hexagon, in its sole discretion). 5.8. Services required due to modifications of Covered Products by Customer. 5.9. Services required due to use other than in the ordinary manner intended for the Covered Products, or use in a manner that contravenes terms hereunder, or Customer's disregard of the installation and operating instructions according to the Documentation provided with the Covered Products. 5.10. Services required due to failure of software or hardware that is not a Covered Product. 5.11. Services required due to Customer's use of hardware or software that does not meet Hexagon specifications or failure of Customer to maintain or perform industry standard maintenance on Customer's hardware or software. 5.12. Services required due to software or portions thereof that were incorrectly installed or configured (other than by Hexagon) or use in an environment inconsistent with the support environment specified by Hexagon, or used with peripherals, operational equipment or accessories not conforming to Hexagon's specifications. 5.13. Services required due to cases of force majeure, especially lightning strikes, fire or flood, third - party criminal acts, or other events not caused through Hexagon's fault. 5.14. Services required due to Customer's failure to fulfill the Customer Obligations. 5.15. Services required due to faulty or incomplete Customer data. 6. COVERED THIRD PARTY PRODUCTS. Support and Updates of Covered Third Party Products shall be provided in the fashion and to the extent or duration that Hexagon is authorized to provide such by the third party manufacturer of the Covered Third Party Products, and such Covered Third Party Products and related services may be subject to additional terms and conditions of the third party manufacturer of the Third Party Software. Services and updates for any Third Party Software not listed in the Order Documents as Covered Products must be obtained from the third party owner of the products or their designated representative. 7. REQUIRED COVERAGE. 7.1. Multiple or Interdependent Licenses. If Customer holds multiple licenses for any Covered Product, all held licenses must be included as Covered Products in the Maintenance Contract. 7.2. Prerequisite Licenses. All prerequisite licenses for Software Products necessary to operate the Covered Products, together with all licenses of Software Products interoperating with Covered Products in a single solution, must be included as Covered Products in the Maintenance Contract. 8. ADDITIONS AND REMOVALS OF COVERED PRODUCTS. 8.1. Additions of Covered Products. Software Products licensed from Hexagon during the term of the Maintenance Contract may be added as Covered Products, if such addition is addressed through additional related Order Documents. If Software Products are not added as Covered Products by commencement of Production use thereof, Hexagon may permit Customer to add support, but subject to additional fees payable pursuant to Hexagon's then current policies or practices. Hexagon Master Terms and Conditions S1082020-MT Page 17 8.2. Removal of Covered Products from Maintenance. Either Party may provide written notice to the other Party at least sixty (60) calendar days prior to the end of any Coverage Period Anniversary of its intent to remove any individual Covered Products from the Maintenance Contract at the end of the then current and contracted Coverage Period or any Coverage Period Anniversary. Neither Party may remove Covered Products except upon Coverage Period renewal or extension or Coverage Period Anniversary; provided that Hexagon may additionally remove Covered Products as part of a general discontinuance program at any time upon one hundred eighty (180) days' written notice. Customer may not remove from the Maintenance Contract individual software licenses of a Covered Product for which Customer has multiple copies under Maintenance Services or for Covered Products that are being used interdependently, unless Customer has first certified to Hexagon on a "Software Relinquishment Agreement" that it surrenders and relinquishes all rights in and to the applicable Software licenses and the copies of the Covered Product for which Customer desires to cease Maintenance Services (the "Relinquished Licenses") for the renewal Coverage Period have been uninstalled and removed from its system(s). Should Customer desire to resume usage of the Relinquished Licenses at a later date, Customer must re -purchase the licenses at the then current list price. 9. PAYMENT. 9.1. Terms of Payment. Charges for Maintenance Services are due and payable annually and in advance. All charges are due net thirty (30) calendar days from the date of invoice or prior to the beginning of the applicable Coverage Period, whichever is earlier. Charges for Covered Software Products added during a Coverage Period shall be prorated to the remaining Months of the Coverage Period, in whole Month increments only, and such charges shall be due and payable in full upon receipt of invoice. Covered Third Party Products added during a Coverage Period are subject to Section 6 of these Maintenance Terms. 9.2. Past Due Accounts. HEXAGON RESERVES THE RIGHT TO REFUSE SERVICE TO ANY CUSTOMER WHOSE ACCOUNT IS PAST DUE. At the discretion of Hexagon, Customers who have not paid any charges when due (i) under the Maintenance Contract, (ii) under any other agreement between the Parties, or (iii) under any agreement between Hexagon and Customer's parent and/or subsidiary, may not be rendered Maintenance Services until all past due charges are paid in full. The start of the Coverage Period shall not be postponed due to delayed payment of any charges. 9.3. Customer's Responsibilities Concerning Invoice Questions. Subject to applicable law, if Customer intends to dispute a charge or request a credit, Customer must contact Hexagon within ten (10) calendar days of the date on the invoice. Customer waives any right to dispute a charge or receive a credit for a charge for Maintenance Services that Customer does not report within such period. 10. CUSTOMER ACKNOWLEDGEMENTS. During the Coverage Period, Customer commits to the following: 10.1. Customer shall have reviewed the Order Documents and by executing the Order Documents confirms the Order Documents accurately reflects all Hexagon software in its possession or control. 10.2. Customer acknowledges and confirms that for all Covered Products supported under the Maintenance Contract, all licenses of a Covered Product for which Customer has multiple copies in its possession and all prerequisite licenses necessary to operate Covered Products, are accounted for in the Order Documents. If all like Covered Products or prerequisite software licenses are not accounted for in the Order Documents, Customer agrees to notify Hexagon so that Hexagon may issue a revised Quote to Customer. 10.3. Customer acknowledges and confirms Maintenance Services provided herein shall be utilized only for the quantity of Covered Products licenses listed in the Order Documents. 10.4. Customer shall, and Customer shall cause each of Customer's employees and representatives to, comply with each and every term and condition of the EULA applicable to the Covered Products supported under the Maintenance Contract. Hexagon Master Terms and Conditions S1082020-MT Page 18 11. ADDITIONAL TERMS. 11.1. Software License. Any Updates furnished hereunder shall remain the property of Hexagon, Hexagon's Affiliate, or applicable third party, and are licensed in accordance with the then current Hexagon EULA, EULA of Hexagon's Affiliate, orthird party SLA, which shall supersede any EULA or SLA associated with prior releases of the Covered Software Products or Covered Third Party Products. Upon Customer's request, Hexagon shall provide Customer with such EULA or SLA. Upon Hexagon's request, Customer agrees to execute a EULA or SLA, as applicable, for Covered Products. 11.2. Pass -Through Third Party Warranties. Covered Third Party Products are only warranted pursuant to a pass -through warranty to Customer from the applicable Third Party Software manufacturer and only to the extent warranted by the applicable Third Party Software manufacturer. 11.3. Remedies. In the event a warranted Maintenance Service, Covered Product, or Update provided pursuant to the Maintenance Contract does not substantially comply with the limited warranties set forth in the Maintenance Contract, Hexagon's entire liability and Customer's exclusive remedy shall be, in Hexagon's sole and absolute discretion, either (i) providing of a Service, Covered Product, or Update which conforms substantially with the warranty; or (ii) a refund of the purchase price of the particular warranted Service, Covered Product, or Update for the period of time that the warranted Service, Covered Product, or Update did not substantially conform to the limited warranties set forth in the Maintenance Contract. Hexagon is acting on behalf of its suppliers for the sole purpose of disclaiming, excluding and/or limiting obligations and liability as provided in the Maintenance Contract, but in no other respects and for no other purpose. 11.4. WARRANTY DISCLAIMERS. In addition to the Warranty Disclaimer provided in the Master Terms, Hexagon does not warrant that any Services, Covered Products, and Updates provided pursuant to the Maintenance Contract will meet Customer's requirements, and under no circumstances does Hexagon warrant that any Services, Covered Products, and Updates will operate uninterrupted or error or Defect free. 11.5. Third Party Providers. Hexagon reserves the right to provide Maintenance Services through a third party provider. END OF EXHIBIT B Hexagon Master Terms and Conditions S1082020-MT Page 19 EXHIBIT C PROJECT DELIVERABLE SIGN -OFF FORM CUSTOMER NAME, CUSTOMER CITY - PROJECT NAME Submission Date: Month/Day/Year Sign -Off Target Date: Month/Day/year Submitted By: Hexagon Contact Name Submitted To: Customer Contact Name Customer Contract #: Customer Contract Number Customer/Project #: Hexagon Project Number TYPE OF DELIVERABLE ❑ SOW Tasks ❑ Payments ❑ Plans/Designs ❑ Training ❑ Other DELIVERABLE INFORMATION DELIVERABLE DESCRIPTION $AMOUNT OF PYMT THIS SECTION DESCRIBES THE DELIVERABLE (If applicable) With the deliverable described above complete, the Customer shall have ten (10) working days after receipt of a written request from Hexagon, to either sign -off that the deliverable has been met or state in writing to Hexagon the reason the deliverable has not been met. Sign -off of the deliverable shall be based solely upon the deliverable meeting the requirements stated in the Contract between Hexagon and CUSTOMER NAME dated Month/Day/Year and shall be indicated by the Customer signing the Project Deliverable Sign -off Form. If the Customer does not provide such sign -off or rejection within the ten (10) working day period then the deliverable will be deemed to have been signed off. The signature below acknowledges that the deliverable described in the Contract and listed above meets all of the appropriate criteria and supersedes all prior requirements for this item. Customer acknowledges completion of this payment milestone according to the Contract Payment Milestone Schedule and provides authorization to invoice this milestone. Authorized Customer Representative Customer Contact Name SIGNATURE DATE Hexagon Master Terms and Conditions S1082020-MT Page 20 EXHIBIT D CLOUD PROGRAM CONDITIONS These terms and conditions ("Cloud Conditions") govern the provision of the Cloud Program by Hexagon to Customer under a Cloud Program Sale Order. Any additional terms in any Cloud Services Schedule(s) also apply. 1. DEFINITIONS. Capitalized terms used and not otherwise defined herein have the meanings assigned in the Common Terms Glossary. 2. SCOPE OF CLOUD PROGRAM. 2.1 From the Cloud Program Start Date and for the duration of the Cloud Term, Hexagon will provide the License Key(s) to Customer in the amount specified in the Quote with respect to the Cloud Program purchased by Customer to use the Cloud Program subject to the provisions of these Cloud Conditions. Except for the Cloud Services, no other service, including Cloud Consulting Services, are provided by Hexagon pursuant to a Cloud Program Sales Order. 2.2 Hexagon may from time to time provide or otherwise make available Local Software. Local Software may include mobile applications obtainable from an online applications store, applications owned by a third -party, or other facilitating applications. In the event Hexagon provides or makes available such applications, the same shall be made available to Customer and owned by Hexagon (or the relevant third party), and used subject to these Cloud Conditions. If not sooner terminated, the license to use such Local Software shall terminate upon expiration of the Cloud Term. 3. CLOUD SERVICES AUTHORIZATION. During the Cloud Term, Hexagon grants Customer and its Affiliates the right to access and use components of the Cloud Program listed in the quantities reflected on the Quote solely for Customer's and Affiliates' own internal business purposes and subject to these Cloud Conditions 4. TERM, TERMINATION AND SUSPENSION. 4.1 The Cloud Program Sale Order commences on the Effective Date of the Order and shall continue for the Cloud Term, unless earlier terminated in accordance with the Master Terms and these Cloud Conditions. To the extent any optional renewals are identified in the Quote, the Customer must issue a PO or a notice to proceed to extend the Cloud Term and at the prices set forth in the Quote not less than sixty (60) days prior to the end of the Cloud Term. Prior to the end of the Cloud Term, the Customer may renew the Cloud Program Sale Order and/or have Customer Data Offboarded. 4.2 In addition to the rights and remedies set forth in the Master Terms, once notified in writing of the overdue payment, Customer acknowledges Hexagon may, without further notice, reduce the Cloud Services to the lowest tier of Cloud Services offered by Hexagon. During such time, Hexagon or the Third Party Service Provider is not obligated to facilitate or provide any services related to Onboarding or Offboarding. Without waiver of its right to terminate the Master Agreement and/or Cloud Program Sale Order or seek additional remedies, if full payment has not been received by Hexagon within thirty (30) days following written notice, Hexagon may suspend providing the Cloud Program to Customer until all outstanding Cloud Program Fees together with any applicable interest has been paid to and received by Hexagon. For avoidance of doubt, and without limitation, if Hexagon suspends providing the Cloud Program to Customer for non-payment, Customer shall have no right to access or use Cloud Applications, software applications provided by Hexagon which are incidental to the Cloud Program, Third Party Software Products, Cloud Services, Cloud Optional Services, or any goods, services, or benefits Hexagon Master Terms and Conditions S1082020-MT Page 21 to be provided by Hexagon hereunder. Suspension of the Cloud Program for non-payment shall not prejudice Hexagon's rights hereunder or relieve Customer from the obligation to pay Cloud Program Fees associated with the period of suspension. 4.3 Termination shall not relieve the Customer of the obligation to pay any Cloud Program Fees accrued or payable to Hexagon prior to the date of termination. Unless otherwise agreed to in writing by Hexagon, in the event Hexagon terminates a Cloud Program Sale Order due to any of the conditions set forth in Section 4.2 above, then under no circumstances whatsoever shall Customer be entitled to any refund of Cloud Program Fees paid in advance to Hexagon pursuant to the terms of the Master Agreement. 5. AVAILABILITY. Hexagon shall reasonably endeavor to deliver Availability in accordance with the Service Level specified in the applicable Cloud Services Schedule. "Availability" or "Available" means the ability to connect to the Cloud Portal, connect to the Customer Cloud Environment for Production, launch Cloud Application(s), and access Customer Data contained in the Customer Cloud Environment for Production. Availability does not include the availability of third -party portals or Cloud Optional Services. Availability of Cloud Application(s) shall be determined by launching the main application for the applicable Cloud Application. For purposes of calculating Availability time, the following is excluded: time expended for Planned Maintenance; downtime required to perform Cloud Consulting Services; time expended due to the inability for Customer to connect to the Cloud Portal due to problems with the Customer's infrastructure or the internet; unavailability arising from Customer exceeding Customer purchased Cloud Application capacity; and, time expended due to any other circumstances beyond Hexagon's reasonable control, including Customer's or any User's use of third -party materials or use of the Cloud Program other than in compliance with the express terms of the Master Agreement and Hexagon's reasonable instructions (collectively "Exception(s)"). 6. CRITICAL SERVICE LEVELS. The purchased Service Level classifications are set forth in the Cloud Service Schedule. "Service Operational Time" means the time, expressed in a percentage as set forth below, that the Cloud Application is Available for a given Month during the service. The method of calculating the Service Operational Time is: Hours of Cloud Program Availability for a given Month Hours of Cloud Program Availability + downtime hours for such Month which are not related to x 100 an Exception 7. SERVICE CREDITS. 7.1 If in any Month the Service Operational Time in a Cloud Environment for Production falls below the purchased Service Level (a "Service Incident"), a "Return to Green Plan" shall be initiated for the Customer's Environment for Production. Hexagon shall have: (i) the remainder of the Month in which the Customer notified Hexagon of the Service Incident by way of a Cloud Service Request, which notified Hexagon of the problem which resulted in the Service Operational Time falling below the applicable Service Level, plus (ii) one (1) additional Month (collectively, the "Go Green Period"), to return the Service Operational Time to such Service Level. 7.2 Subject to Section 7.3 below, if the Service Operational Time does not rise to the applicable Service Level within the Go Green Period, then the Service Credit provided in the Cloud Service Schedule will be applied against each Month in which the Service Operational Time remains below such Service Level. 7.3 Service Credits apply: 7.3.1 Only as specified within the Cloud Services Schedule; 7.3.2 Only to the extent that the affected Customer Environment is used in Production; 7.3.3 In strict accordance with Section 5; 7.3.4 Only if a Customer has logged a Cloud Service Request which notified Hexagon of the problem that causes the Critical Service Level to fall below the identified Availability percentage in the Cloud Services Schedule ("Green"); and Hexagon Master Terms and Conditions S1082020-MT Page 22 7.3.5 Only where Customer is compliant with the AUP 7.4 To the extent applicable and properly noticed by Customer in accordance with Section 7.1 above, Service Credits shall be credited against the next invoice until such applicable Service Credits have been used. If the Master Agreement is terminated or Customer elects not to renew the Master Agreement before an ensuing invoice is issued, then such Service Credits are forfeited. Customer shall have no right to receive any monetary remuneration in exchange for unused Service Credits. Notwithstanding anything herein to the contrary, in no event shall Service Credits for any given year during the Term exceed twenty percent (20%) of the amount of Cloud Program Fees payable by Customer to Hexagon pursuant to the Quote for the annual period in which the Service Credit accrued. 7.5 The Customer's exclusive remedy for not meeting the Critical Service Level specified in the Cloud Services Schedule shall be the Service Credits as set forth in this Section. 8. CLOUD SERVICES SUPPORT. 8.1 As part of Cloud Services, Hexagon will provide the Cloud Services Support described within this Section 8. 8.2 Cloud Services Support is available at the times specified in the applicable Cloud Services Schedule. Cloud service requests and Product Change Requests can be directed by an Authorized Cloud User to Hexagon by: (i) the support website (https://support.hexagonsafetyinfrastructure.com), or (ii) telephoning Hexagon support at the times permitted within the Cloud Services Schedule. 8.3 When reporting a Cloud Service Request, if an Error, an Authorized Cloud User shall assign the Cloud Service Request a priority level based upon the criteria set forth in the support website (https://support.hexagonsafetyinfrastructure.com). The Authorized Cloud User shall provide a brief justification as to the criticality of the Cloud Service Request and a description of the Error giving rise to the Cloud Service Request, to include a statement of steps necessary to produce the error. Hexagon shall respond to the Cloud Service Request and provide commercially reasonable efforts to aid and address the Cloud Service Request. If Hexagon disagrees with the priority of the Cloud Service Request, it shall discuss the matter with Customer, but Hexagon, in its sole discretion, reserves the right to revise the initially reported priority level of the Cloud Service Request. 8.4 Product Change Requests will be reported in like manner as set forth in Section 8.3. Hexagon will review Product Change Requests and at its sole discretion decide whether to make the requested change to the Cloud Program. Product Change Requests not accepted may be the subject of a separate contract between the Parties. For the avoidance of doubt, to the extent Hexagon agrees to make a requested change to the Cloud Program pursuant to a Product Change Request, any and all IPR resulting from such change or modification is and shall remain the property of Hexagon. 8.5 Customer acknowledges and agrees that, as part of providing Cloud Services Support, Hexagon is permitted to make necessary changes to the Cloud Program without notice if necessary to perform Emergency Maintenance. Hexagon shall be permitted to access the Customer Cloud Environment in the event Hexagon deems Emergency Maintenance is necessary. 8.6 As it relates to, and only to, Local Software which is listed on the Quote, Hexagon shall provide support in like manner as is provided for Cloud Applications except Customer will permit Hexagon to electronically access the Local Software in the Local Environment via SecureLink TM. SecureLinkTM is a tool for providing secure, auditable remote access to the Local Software in order for Hexagon support personnel to effectively troubleshoot and address Errors related to Local Software. Support for Local Software listed on the Quote is included within Cloud Services Support except as is otherwise rendered commercially unreasonable due to the Local Software being hosted by Customer. 8.7 Except as otherwise necessary, as determined by Hexagon in its sole discretion, to satisfy the requirements of Sections 8.3 and 8.4, Cloud Services Support does not include: (i) training; (ii) configuration of Cloud Application(s), Cloud Optional Services, Cloud Portal, Third Party Software Products, Software Products, or other components of the Cloud Program; (iii) Customer Hexagon Master Terms and Conditions S1082020-MT Page 23 Cloud Administration; (iv) programming or software development; (v) modifications to the Cloud Applications or Cloud Optional Services not accepted as a Product Change Request; (vi) onsite services; or (vii) services required because Customer has not performed its obligations under the Master Agreement. 8.8 Upgrades or Updates. 8.8.1. As part of Cloud Services Support, Customer is entitled to receive all updates and upgrades to the purchased Cloud Application(s) and Local Software that Hexagon makes available. Cloud Consulting Services may be necessary to upgrade or update Cloud Optional Services, which is not part of Cloud Services Support. 8.8.2. From time to time, Hexagon may notify Customer through the Cloud Portal or support website (https://support.hexagonsafetyinfrastructure.com) that Hexagon has developed an upgrade or update for the purchased Cloud Application(s) and intends to deploy said update or upgrade, including any applicable Third Party Software Products. On the date specified in the notification, Hexagon will deploy the update or upgrade to the Cloud Development Environment for Customer testing and review, which Customer shall complete within the time prescribed in the notification of the availability of the update or upgrade, but not less than thirty (30) days thereafter (the "Testing Period"). In the event no Material Adverse Effect is reported by Customer within the Testing Period, then on a subsequently specified date by Hexagon, Hexagon will, at its discretion, deploy the update or upgrade to Customer Cloud Environment for Production. 8.8.3. In the event Customer provides written notice to Hexagon, within the Testing Period, of a Material Adverse Effect as a result of Customer's testing of the upgrade or update in accordance with Section 8.8.2 above, Hexagon shall discuss the matter with Customer and use commercially reasonable efforts to address any reasonable workarounds to such Material Adverse Effect, such agreed upon workaround to be subject to the same protocols set forth in Section 8.8.2 and this Section 8.8.3; provided, however, if Hexagon reasonably finds that no Material Adverse Effect exists, Hexagon may deploy the update or upgrade to the Customer Cloud Environment for Production. 8.8.4 As it relates to implementing updates or upgrades for Local Software that is included within the Cloud Program, Customer shall permit Hexagon to electronically access the Local Software on Customer's System Equipment via SecureLink to implement the Update in conjunction with the updating or upgrading of the Cloud Applications and provide any other reasonable support and cooperation required by Hexagon to upgrade or update the Cloud Program. 9. CUSTOMER RESPONSIBILITIES. 9.1 Customer shall be responsible for all activities that occur in Authorized Cloud User and User accounts, including, but not limited to, its Affiliates' accounts, and for Authorized Cloud Users' and Users' compliance with the Master Agreement. Customer shall: 9.1.1 Have sole responsibility for the accuracy, quality, integrity, reliability and appropriateness of all Customer Data that is placed into the Customer Cloud Environment; 9.1.2 Use commercially reasonable efforts to prevent unauthorized access to or use of Cloud Program, including preventing utilization of more Credentials than otherwise reflected by the License Key(s) set forth in the Quote, and notify Hexagon of any such unauthorized access or use; 9.1.3 Provide and maintain its own System Equipment, third party software, networks, internet access, and communication lines, including any public lines required to properly access the Cloud Portal and use the Local Software, including content or data and ensure such meet the minimum standards required to interoperate with the Cloud Program as communicated by Hexagon to Customer via the Cloud Portal or as otherwise determined by Hexagon; and 9.1.4 Abide by and comply with the Acceptable Use Policy, Documentation, and other requirements of these Cloud Conditions. Hexagon Master Terms and Conditions S1082020-MT Page 24 10. CLOUD SERVICE PROGRAM FEES. 10.1 Generally. Subject to Section 10.2 below, in consideration of the Cloud Program provided by Hexagon, Customer shall pay to Hexagon the Cloud Program Fees. 10.2 Adjustment. Hexagon may periodically review the Customer's usage of the Cloud Program to determine whether Customer's usage is consistent with the quantity of License Key(s) and/or Cloud Application capacity purchased. If the usage shows the Customer has used more License Key(s) than are specified in the Quote, then Customer shall pay Cloud Program Fees corresponding to the number of License Key(s) used in excess of the purchased quantity. If a Cloud Application is subject to capacity limitations (e.g. a limited number of transactions in a period), as expressly set forth in the applicable Cloud Services Schedule, the Cloud Application may be configured to cease or degrade some or all functions upon Customer reaching those capacity limitations and/or may be configured to permit additional usage for additional fees, all as and if described in the applicable Cloud Services Schedule(s). 11. TERMS OF PAYMENT. The invoice corresponding to the first year of Cloud Program Fees shall be provided to Customer upon Hexagon's issuance of License Key(s) to Customer. For purposes of clarity, once the first License Key(s) is issued for any Cloud Environment, the annual Fee will be due and payable in full. Invoices for subsequent years included within the Cloud Term as specified in the Quote (as may be adjusted pursuant to Section 10.2 above) will be issued prior to the Cloud Anniversary. 12. ACCEPTABLE USE POLICY (AUP). 12.1 The AUP forms part of these Cloud Conditions and is incorporated by reference. It may be found at the following site: https://www.hexagonsafetyinfrastructure.com/- /media/Legal/Hexagon/SI/Policies/AUP/Cloud AUP-L.pdf. The Customer and any Authorized Cloud User or User shall comply with the AUP. A User or Authorized Cloud User will be prompted with review and acceptance of the AUP to gain access to the Cloud Application(s). Any update to the AUP will require each User or Authorized Cloud User to re -accept the modified AUP. Failure to comply with the AUP may result in the suspension of the Cloud Program or termination of the Cloud Program Sale Order as provided in Section 5 of the Master Terms. During any period of suspension, the Customer will still be liable for payment of the applicable Cloud Program Fees. 12.2 Hexagon reserves the right to change the AUP at any time, but to the extent within the control of Hexagon, it will give Customer thirty (30) days' notice in accordance with the Master Terms and the Primary Contracting Document of any such changes by posting notice of the upcoming change in the AUP on the Cloud Portal or as otherwise determined by Hexagon, unless otherwise required by law or where a Third Party Service Provider requires a change to be made to the AUP and is unable to provide such period of notice. If a Third Party Service Provider requires a change to be made to the AUP, Hexagon shall provide the equivalent period of notice as is provided by the Third Party Service Provider to Hexagon. 12.3 Without waiver of any other requirement or limitation set forth herein, Customer's use of any third party software in conjunction with the Cloud Application, Cloud Optional Services, and Hexagon Software Products that is not certified by Hexagon to operate in conjunction with the same is solely at Customer's risk. Addressing service requests arising from the use of uncertified third party software is not included within Cloud Services Support or the Cloud Program. 13. OWNERSHIP AND INTELLECTUAL PROPERTY. 13.1. In accordance with Section 6 of the Master Terms, Hexagon owns all right, title and interest in and to Cloud Application(s), Cloud Optional Services, the Software Products, Local Software, Documentation written by Hexagon, and any other data and information provided as part of the Cloud Program (except for data and information being owned by a third party), and all copies of all or any part thereof, are and shall remain vested in Hexagon. Third parties shall retain any and all IPR in and to their intellectual property that may be provided as part of the Cloud Program. Hexagon Master Terms and Conditions S1082020-MT Page 25 Customer and its Affiliates do not have, and shall not attempt to decompile, disassemble, or otherwise attempt to gain access to any source code for the Cloud Application, Cloud Optional Services, any other Hexagon Software Product, or Third Party Software Products. Customer, for itself and its Affiliates acknowledges and agrees the Cloud Program is comprised of trade secrets, proprietary information, and Confidential Information, and that Customer, and its Affiliates shall not use, distribute, copy, perform, amend, alter, modify, create derivative works, reverse engineer, exploit, sublicense, or assign the Cloud Program or any component thereof except as expressly permitted by Hexagon (which permission may in some instances, subject stated limitations, be contained in a Cloud Services Schedule with respect to a particular Cloud Application). Without Hexagon's express, written permission, Customer shall ensure that no User transfers or assigns any Credentials to any other person or entity that is not an employee of Customer. 13.2. Customer and its Affiliates, respectively, shall retain their respective full ownership and all rights associated therewith solely to Customer Data to the extent they owned IPR to said information, as well as work product input or output generated by the Cloud Program. This ownership shall not extend to any formats or other intellectual property provided by Hexagon under the Master Agreement that makes a particular data file intelligent or that structures output, said formats and intellectual property which shall remain the property of Hexagon or the respective third party that owns said format or intellectual property. 14. PERSONAL DATA. 14.1. Hexagon reserves the right, but does not assume the obligation, to investigate any violation of this Exhibit D (Cloud Program Conditions) and/or AUP or misuse of the Cloud Services or Cloud Program. Hexagon may: (a) investigate violations of this Exhibit D (Cloud Program Conditions) and/or AUP or misuse of the Cloud Services or Cloud Program; and (b) remove, disable access to, or modify any content or resource that violates this Exhibit D (Cloud Program Conditions) and/or AUP. Hexagon may report any activity that Hexagon suspects violates any law or regulation to appropriate law enforcement officials, regulators, or other appropriate third parties. Hexagon's reporting may include disclosing appropriate information related to Customer or any User. Hexagon also may cooperate with appropriate law enforcement agencies, regulators, or other appropriate third parties to help with the investigation and prosecution of illegal conduct by providing network and systems information related to alleged violations of this Exhibit D (Cloud Program Conditions) and/or AUP. 14.2. Unless a Customer Specified Data Center(s) is included in the Cloud Services as identified in the Quote, Hexagon and its Third Party Service Provider shall have sole discretion of the location of the Data Center(s). 15. SECURITY & BREACH NOTIFICATION. 15.1. Hexagon shall take reasonable industry action to prevent, detect, identify, report, track and respond to Security Incidents. 15.2. Hexagon Response to Security Incident. The following will apply in the event of a Security Incident: 15.2.1. Hexagon will provide a Security Incident report to the Customer or its Affiliates (as applicable) via the Cloud Portal, supportwebsite, or otherwise. The report shall be provided within twenty-four (24) Business Hours following Hexagon's discovery, confirmation, and investigation of a Security Incident. 15.3. Additional Requirements for Personal Data. With respect to any Personal Data in the possession or under the control of Hexagon, which does not include Customer Data within the Customer Cloud Environment, and in order to protect Personal Data from unauthorized access, destruction, use, modification or disclosure, Hexagon shall: 15.3.1. Develop, implement, and maintain reasonable security procedures and practices appropriate to the nature of the information to Personal Data from unauthorized access, destruction, use, modification, or disclosure; and Hexagon Master Terms and Conditions S1082020-MT Page 26 15.3.2. Develop, implement and maintain data privacy and security programs with administrative, technical, and physical safeguards appropriate to the size and complexity of Hexagon's business and the nature and scope of Hexagon's activities to protect Personal Data from unauthorized access, destruction, use, modification, or disclosure. 16. WARRANTIES, DISCLAIMER AND INDEMNITIES. 16.1. During the Cloud Term, Hexagon does not warrant the Cloud Application(s) purchased by Customer will meet the Service Level specified in the applicable Cloud Services Schedule. The Cloud Program may be subject to limitations, delays and other problems inherent in the use of the internet, electronic communications, and Customers' IT infrastructures. Hexagon will not be responsible for any delays, delivery failures, or other damage. 16.2. Hexagon does not warrant the Cloud Application(s) and Third Party Software Products accessed via Cloud Services will perform substantially in accordance with the Documentation provided. To the extent an Error should be discovered, Customer shall report such Error to Hexagon as provided in Section 8 of the Cloud Program Conditions and Hexagon will respond as provided therein. 16.3. Cloud Services will use industry standard Virus detection software to avoid transmission to the Customer, its Affiliates, any Viruses (except for any Viruses contained in Customer Data uploaded or Onboarded by Customer). 16.4. Hexagon does not warrant the Cloud Program (to the extent accessed by Customer under the Master Agreement) will meet the Customer's or any of its Affiliate's requirements or that it will run uninterrupted or be Error free. Customer and its Affiliates are responsible for the results obtained from the use of the Cloud Program. 16.5. The warranties set forth herein are in lieu of all other warranties, expressed or implied, and represents the full and total warranty obligation and/or liability of Hexagon 17. ACCESS TO THE MASTER AGREEMENT BY CUSTOMER'S AFFILIATES. If an Affiliate accesses or utilizes any or all components of the Cloud Program, the Affiliate shall be deemed to have agreed to be bound by the terms and conditions of these Cloud Program Conditions. The Affiliate, in accessing the Cloud Program (or any part thereof), and Customer, in permitting the Affiliate's access, each represent to Hexagon they have entered into an agreement by which Affiliate is permitted to use the Cloud Program is bound to the terms herein. Except for Affiliates and employees of Affiliates, no other person, including any third parties not authorized by Hexagon, may access the Cloud Program or be provided with Credentials. END OF EXHIBIT D Hexagon Master Terms and Conditions S1082020-MT Page 27 EXHIBIT E SUBSCRIPTION TERMS AND CONDITIONS These Subscription Terms and Conditions ("Subscription Terms"), govern the licensing and support for the Subscription. 1. DEFINITIONS. All capitalized terms not otherwise defined herein shall have the meaning set forth in Exhibit G (Common Terms Glossary). 2. SERVICES PROVIDED. 2.1 Access. Subject to an Order for a Subscription License Sale and these Master Terms, including Exhibit A (End User License Agreement), Hexagon will make the Subscription Licenses available to Customer for Customer's use during the Subscription Term. Any renewal or extension of the Subscription Term shall be subject to such terms and product components as reflected in the applicable renewal or extension Quote issued by Hexagon (the "Renewal Quote"). Customer acknowledges and agrees that Customer shall compensate Hexagon for Customer's continued use of a Subscription after expiration or termination of a Subscription Term, at a rate equitably and proportionately calculated based upon the Renewal Quote and based upon the period of such extended use; provided that if no Renewal Quote is issued prior to expiration or termination of the Subscription Term, the initial Quote shall be substituted in the calculations set forth in this Section 2.1. 2.1.1 As it pertains to Metered Licenses, the Customer's right to use the Metered Licenses shall end upon the earlier of: (i) expiration of the Subscription Term, or (ii) Customer's use of its allotment of units of service as set forth in the Quote. 2.2 Maintenance and Support. During the applicable Subscription Term, Hexagon will provide maintenance services and support to the Customer for the Subscription Licenses in accordance with Exhibit B (Maintenance Terms and Conditions) of these Master Terms. 2.3 Services. These Subscription Terms only provide for the licensing and support of the Subscription. If the Customer desires for Hexagon to provide Services for implementation, configuration, training, or other work in relation to the Subscription, then Customer may contract with Hexagon pursuant to these Master Terms for Services under a separate Order. 3. INVOICES. Hexagon shall invoice Customer for the full amount set forth in the Quote upon delivery of or access having been provided for the Subscription Licenses identified in the Quote in any environment. To the extent the Quote includes multiple types of Subscription Licenses, Hexagon shall invoice the Customer once the first type of Subscription License is allowed to be invoiced as provided in this section. 4. CUSTOMER OBLIGATIONS. 4.1 Customer Control. Customer's and its authorized Users of the Subscription shall at all times comply with Exhibit A (End User License Agreement). Customer will be solely responsible for administering and monitoring the use of login IDs and passwords provided by Customer to authorized Users pursuant to the Subscription, or by Hexagon on behalf of Customer. Upon the termination of employment of any authorized User, Customer will terminate that individual's login ID and password. Hexagon is not responsible for any damages resulting from Customer's failure to manage the confidentiality of its login ID and passwords and Customer is responsible for any actions arising out of use or misuse of Customer's login IDs. 4.2 Security. Customer shall take commercially reasonable security precautions to prevent unauthorized or fraudulent use of Hexagon IP by Customer, Customer's employees, consultants, agents, or any other third parties authorized by Customer to access the Subscription on Customer's behalf. END OF EXHIBIT E Hexagon Master Terms and Conditions S1082020-MT Page 28 EXHIBIT F COTS Training Program Terms These terms and conditions ("COTS Training Program Terms") govern the provision of the Training Curricula by Hexagon to Customer under a Fixed Price Project Assignment. Any additional terms in a Training Program Statement also apply; and, notwithstanding the order of precedence stated in the Master Terms, but without otherwise modifying such order of precedence, any conflict between these COTS Training Program Terms and any applicable Training Program Statement shall be resolved in favor of the Training Program Statement. 1. DEFINITIONS. Capitalized terms used and not otherwise defined herein have the meanings assigned in the Common Terms Glossary. 2. SCOPE OF TRAINING PROGRAM. Hexagon will provide the Training Curricula specified in the Quote and purchased by Customer, in accordance with and subject to the provisions of these COTS Training Program Terms and the applicable Training Program Statement(s). The Training Program Statements(s) and Quote shall describe the duration and delivery method for the Training Curricula; provided that if no duration is otherwise stated for a Training Curricula delivered by online means, Customer shall cease use thereof twelve (12) months following the date the Order was placed for the Training Curricula. 3. FEES AND PAYMENT. Unless otherwise expressly provided in applicable Training Program Statement(s) corresponding to the Order, fees for Training Curricula delivered by a live instruction method shall be invoiced as and when the Training Curricula is delivered; and, fees for Training Curricula delivered by an online on -demand method shall be invoiced upon first delivery to Customer of the initial ability to access any portion of the Training Curricula. 4. SPECIFIC ONLINE TERMS. 4.1 Assignment of Credentials. For Training Curricula delivered by an online on -demand method, Customer acknowledges and agrees that: each specific student/user must be assigned individual credentials, thereby consuming one of the overall quantity of credentials available to Customer under the terms of the Order, and student/user credentials may not be shared or used by more than one student/user. Upon request, and subject to processing and any requirements of the Third Party Service Provider, credentials may be subject to reassignment to a new student/user and from a student/user no longer requiring access to the Training Curricula. The period of availability of an online on -demand Training Curricula shall not be extended due to delays in Customer's assignment of available credentials or in any reassignment of credentials. 4.2. Use Restrictions. Customer shall comply, and assure all students/users comply, with terms of use of the Training Curricula and the platform through which it is provided, including without limitation, each of the following: the platform and assets associated therewith shall never be used to perform unlawful activity or activity which interferes with networks, systems, or facilities associated with operation of the platform; the platform shall not be used to store, process, or publish threatening, disparaging, or offensive material, or material that constitutes Spam/E- Mail/Usenet abuse or to create a security risk or an infringement of privacy or intellectual property rights; the platform shall not be used for any activity intended to directly or incorrectly circumvent security measures of the Third Party Service Provider or Hexagon; and, the platform shall be used solely within the use requirements of the Third Parry Service Provider and solely for the purpose of consuming the Training Curricula. Hexagon Master Terms and Conditions S1082020-MT Page 29 5. OWNERSHIP AND INTELLECTUAL PROPERTY. In accordance with Section 6 of the Master Terms, Hexagon owns all right, title and interest in and to Training Curricula, and any other data and information provided as part of Training Curricula (except for data and information being owned by a third party), and all copies of all or any part thereof, are and shall remain vested in Hexagon. Third parties shall retain any and all IPR in and to their intellectual property that may be provided as part of the Training Curricula, to include without limitation the Third Party Service Provider's retention of intellectual property associated with the platform through which any online on - demand Training Curricula is provided. Customer and its Affiliates shall not attempt to decompile, disassemble, obtain any source code for, or record Training Curricula, in whole or in part. Customer, for itself and its Affiliates and their respective personnel accessing the Training Curricula, acknowledges and agrees the Training Curricula is comprised of trade secrets, proprietary information, and Confidential Information, and that Customer, and its Affiliates shall not use, distribute, copy, record, perform, amend, alter, modify, create derivative works, reverse engineer, exploit, sublicense, or assign the Training Curricula or any component thereof except as expressly permitted by Hexagon. The Customer acknowledges Hexagon shall retain sole custody and control of the underlying online Training Curricula and any documents and information displayed therein. Unless otherwise set forth in the Training Program Statement, Hexagon shall only provide electronic copies of any specified Documentation. Without Hexagon's express, written permission, Customer shall ensure student/user credentials issued to Customer are only assigned and/or used only by Customer's employees. 6. CUSTOMER OBLIGATIONS. Customer shall at all times be responsible for administering and monitoring the use of Training Curricula by its students/users. Training Curricula shall be used solely for Customer's internal training purposes. Upon the termination of employment of any student/user, Customer will terminate that individual's access to Training Curricula. Customer shall be responsible for supplying all components necessary to supply of the Training Curricula not expressly specified in the Training Program Statement as a deliverable by Hexagon. Depending upon the nature and delivery method of the particular Training Curricula, components to be supplied by Customer may include, by way of example only, computers or software for use by students/users, internet connectivity, or training space at the Customer's site. END OF EXHIBIT F Hexagon Master Terms and Conditions S1082020-MT Page 30 EXHIBIT G COMMON TERMS GLOSSARY "Acceptable Use Policy (AUP)" means the Acceptable Use Policy identified as such within Exhibit D (Cloud Program Conditions). "Activity" or "Activities" means a single work activity/event or collection of work activities/events by a Party or by both Parties under a specified Task. "Affiliate" means, for business entities, the parent business entity of a Party and any business entities in which a Party or its parent company directly or indirectly holds a controlling ownership interest. "Affiliates" means, for government entities which are Customers, an entity which has entered into an intergovernmental agreement with Customer which: (i) relates to or addresses the subject matter of the Primary Contracting Document; and (ii) was disclosed to, and acknowledged by, Hexagon (A) prior to the Effective Date for any existing intergovernmental agreements, and (B) prior to any renewal date of such Primary Contracting Document for any intergovernmental agreements entered into after the Effective Date. "Control" for the purposes of this definition means that Customer owns in excess of fifty percent (50%) of the ownership interest of the Affiliate or owns a majority of the voting shares of the Affiliate. For purposes of Section 9 in the General Terms and Conditions, an Affiliate is not a third party. "Authorized Cloud User" means an individual user authorized by the Customer to use an entire Cloud Program on behalf of the Customer and for whom an account is set up by which the Authorized Cloud User can utilize Cloud Services Support and log Cloud service requests and Product Change Requests. "Auxiliary System License" means the license(s) of Software Product made available by Hexagon for select Software Products to augment Production System Licenses. Each Auxiliary System License requires a corresponding Production System License and the term of the Auxiliary System License shall not exceed the term of the applicable Production System License. "Beta Software" means any version of Software prior to a generally available commercial release of such Software. "Business Day" means any day other than a weekend or public holiday in the country listed on the Quote. "Business Hour" means an hour occurring during a Business Day and during the generally recognized eight (8) working hours comprising the Business Day at the Customer's location. "Catastrophic Event" means a rare circumstance in which mass casualties and/or significant property damage has occurred or is imminent (e.g. September 11th, hurricanes, earthquakes greater than 6.1 on the Richter scale). "Change Order" means a document executed or accepted in writing by both Parties that modifies the scope, price, milestones, and/or project schedule of an Order. "Client" means a computing device connected to a Server. "Cloud Anniversary" means the anniversary of the date on which Hexagon provided the License Keys to Customer. "Cloud Application(s)" means the Hexagon software applications, including without limitation application programming interfaces made available by Hexagon through the Cloud Portal as part of the Cloud Program. "Cloud Consulting Services" means Services that relate to the Cloud Program including, but not limited to, implementation, configuration, customization, data conversion, Onboarding, design, training, and or enhancement of the Cloud Program. "Cloud Cutover" means the point in time when Customer first uses the Cloud Program for its generally marketed purpose. Hexagon Master Terms and Conditions S1082020-MT Page 31 "Cloud Development Environment" means a logical group of virtual or physical computers comprised within the Cloud Environment to which the Customer will be provided with access and use for the limited purpose of making modifications, as specifically permitted herein, to the Cloud Application. For purposes of clarity, the Cloud Development Environment cannot be used in production or for training purposes. "Cloud Environment" means the collection of remote environments provided to Customer on which the Cloud Application(s) operates that is supported by Hexagon. "Cloud Optional Services" means those certain Hexagon Software Products that provide ancillary functionality or capability to the Cloud Applications, including, but not limited to, interfaces and custom forms and functionality. Unless specific Cloud Optional Services are identified in the Quote with a corresponding purchase commitment from Customer, Cloud Program does not include Cloud Optional Services. "Cloud Portal" means the website through which Customer accesses and uses the Cloud Program. The Cloud Portal provides access to the Cloud Program according to Customer's rights, and further provides access to additional Cloud Services, as made available by Hexagon. "Cloud Program" means the combination of Cloud Services, Cloud Application(s), Local Software, Third Party Software Products, and Cloud Optional Services provided pursuant to the Order Documents. The components of the Cloud Program are specifically identified in the Quote and for purposes of this definition shall mean only those components and not any other components not specifically listed in the Quote. "Cloud Program Fees" means, collectively, any of the fees payable by Customer to Hexagon for the Cloud Program (or any part thereof). Cloud Program Fees shall be in the amount described in the Quote and/or Cloud Services Schedule, and shall be invoiced on an annual basis, except to the extent otherwise expressly provided in the Primary Contracting Document or the Cloud Services Schedule. "Cloud Program Sale" means a type of Order providing access to the Cloud Program for the Cloud Term to the Customer. While a Cloud Program Sale may be the subject of a Quote, SOW, Order Documents, or other instruments which simultaneously address other types of sales, a Cloud Program Sale shall nevertheless always be construed as a separate Order under the Master Terms, i.e. not part of a combined Order along with a sale of Software Product licenses, Services, or other items. "Cloud Program Start Date" means the date on which the first License Key(s) are provided to the Customer. For Cloud Program Fees purposes, Cloud Program use by Customer will be assumed to be for the entire Month in which the Cloud Program Start Date falls regardless of the actual date in such Month that access to the applicable Cloud Application began. "Cloud Service Request" means a request made to the first level support service to diagnose and address an Error in a Cloud Application or to report the purchased Cloud Application(s) is not Available. "Cloud Services" means the services, service levels, Cloud Services Support, Customer Cloud Environment, and Third Party Service Provider's hosting services (which are more particularly described in the Cloud Services Schedule(s) attached to the Quote), for Cloud Application(s), Cloud Optional Services, and Third Party Software Products and ordered by the Customer. "Cloud Services Schedule" means a document(s) titled "Cloud Services Schedule" attached to the Quote containing additional details regarding the Cloud Services being provided to Customer with respect to the applicable Cloud Program components purchased by Customer, including, but not limited to: (i) Customer Data backup frequency, and, (ii) level of redundancy for the Customer Cloud Environment. "Cloud Services Support" means the service specified as such in the Cloud Services Agreement through which Customer can report Cloud Service Requests and Product Change Requests. "Cloud Staging Environment" or "Cloud Testing Environment" means a logical group of virtual or physical computers comprised within the Cloud Environment to which the Customer will be provided with access and use for the limited purpose of testing modifications, as specifically permitted herein, to the purchased Cloud Application(s). For purposes of clarity, the Cloud Staging Environment cannot be used in production or for training purposes. "Cloud Term" means the duration of a Cloud Program Sales Order. "Cloud Training Environment" means a logical group of virtual or physical computers comprised within the Cloud Environment to which the Customer will be provided with access and use for the limited purpose Hexagon Master Terms and Conditions S1082020-MT Page 32 of training users on the operation and use of the purchased Cloud Application(s). For purposes of clarity, the Customer shall only be entitled to a Training Environment as part of the Cloud Program if such is purchased by Customer and noted on the Quote. "Confidential Information" means any data or information, tangible or intangible, disclosed or made available by either Party (the "Disclosing Party") to the other Party (the "Receiving Party") that the Disclosing Party considers confidential or proprietary and is not generally known in the industry or to competitors of the Disclosing Party and which shall include: (i) tangible information marked by the Disclosing Party with the word "Confidential" or otherwise identified by an appropriate stamp or legend indicating its confidential nature; (ii) Confidential Information disclosed orally or visually and identified by the Disclosing Party as confidential when disclosed, and confirmed by the Disclosing Party in a written notice within thirty (30) days following disclosure, which notice shall include markings similar to those outlined above; and (iii) all other information that, notwithstanding the absence of markings or designations, would be understood by the Parties, exercising reasonable business judgment, to be confidential. The term Confidential Information does not include information that: (i) is or becomes available in the public domain through no act of the Receiving Party; (ii) has been received on a non -confidential basis from a third party without breach of the Primary Contracting Document, where the Receiving Party has no reason to believe that such third party is bound by any confidentiality obligation to the Disclosing Party; (iii) was developed independently by the Receiving Party without reliance on the disclosed Confidential Information, provided that such independent development can be substantiated; or (iv) is confirmed by the Disclosing Party as not being confidential in writing. "Core" means a physical processor on a computer Server that can respond to and execute the basic instructions that drive the computer. A Central Processing Unit ("CPU") may have one or more Cores, and a given Server may have multiple CPU sockets that may each contain multiple Cores. "COTS" means commercial off the shelf Intellectual Property in the form generally released and distributed to Hexagon's customers and not including any functionality or features requiring source code changes. "COTS Documentation" means commercial off the shelf Documentation in the form generally released and distributed to Hexagon's customers and not including or requiring changes thereto. "Coverage Period" means the period of performance of Maintenance Services with respect to a Covered Product, as stated in the Order Documents. Coverage Periods may differ for discrete Covered Products. "Coverage Period Anniversary" means, in the case where the Coverage Period is greater than one (1) year, the anniversary of the date on which the Coverage Period commenced. "Covered Products" means collectively, Covered Software Products and Covered Third Party Products. "Covered Software Product(s)" means Software Product(s) identified in the Order Documents as software for which Maintenance Services are to be provided by Hexagon. Covered Software Products shall not include Third Party Software or any Cloud Program. "Covered Third Party Products" means Software Product(s) identified in the Order Documents as Third Party Software for which Maintenance Services are to be provided by Hexagon. Covered Third Party Products shall not include Software Products or any Cloud Program. "Credentials" means the unique log -in identifier entered via the Cloud Portal by which a person could access the Cloud Program. "Customer" means the non -Hexagon party to the Primary Contracting Document. "Customer Cloud Administration" means providing User's access to the Cloud Application(s) purchased by Customer, managing User accounts, providing Credentials to Users, and any system administration beyond User interface. "Customer Cloud Environment" means a logical group of virtual or physical computers comprised within the Cloud Environment and Local Environment to which the Customer will be provided with access and use of as part of the Cloud Program. Except as may be otherwise set forth on the Quote, including the purchase of other Cloud Optional Services, including but not limited to a Training Environment, a Customer Cloud Environment consists of a Cloud Development Environment, Cloud Staging Environment, and Production Environment. Hexagon Master Terms and Conditions S1082020-MT Page 33 "Customer Data" means all electronic data or information: (i) provided by Customer to Hexagon in connection with the Deliverables provided pursuant to an Order; and/or (ii) created by Customer and/or submitted to the Cloud Environment by Customers, Users, and/or Authorized Cloud Users. "Customer Data" shall not mean data which (i) is not peculiar to Customer, and/or (ii) is of value to the general implementation, development, operation, or use of Hexagon products or services for the benefit of other customers. For the avoidance of doubt, Customer Data shall not include the Cloud Application(s), Software Products, Cloud Optional Services, Documentation written by Hexagon, and any other data and information provided as part of the Cloud Program or constituting a Hexagon Deliverable. "Customer Specified Data Center(s)" means a data center used in the provision of a Cloud Environment, whose location has been specified by the Customer and agreed to by Hexagon and identified in the Quote. Additional Cloud Program Fees may be payable for a Customer Specified Data Center. "Customized Software" means those Services Deliverables that are software or computer code, whether in source code or object code. "Cutover" means the point in time in which a Software Product(s) is first used by User for its generally marketed purpose. "Data Center(s)" means the data center(s) from which the Cloud Program (or part thereof) will be stored as determined by Hexagon or its Third Party Service Provider. "Defect" means a reproducible instance of an adverse and incorrect functioning of a Software Product or Cloud Application that impacts the ability to use functionality intentionally integrated in the design of the Software Product, assuming proper usage of the Software Product in its required operating environment. Defects are further classified into four levels as follows: Level Impact of Defect Level One No workaround available and either: � Productive use prohibited, or � Aborts. t Level Two No workaround available and either. - Primary purpose compromised, or Productive use significantly impacted � Level Three Productive, but incomplete operation Level Three Defects generally have a workaround or do not otherwise substantially impair productive use. Level Four Defects not qualifying as Level One, Two, or Three, including defects of a cosmetic nature and defects not materially limiting complete productive use Customer shall classify a Defect in accordance with the foregoing; provided that, Hexagon shall reclassify the Defect as appropriate following its review thereof. "Deliverable(s)" means all Services Deliverables, software, hardware, Cloud Programs, and other items delivered or to be delivered by Hexagon to Customer and identified in the Order. "Documentation" means, whether in electronic or printed form, User's Guides, Reference Guides, Administrator's Guides, Configuration Guides, and Help Guides made available at the support website (https://support.hexagonsafetyinfrastructure.com) for Software or Cloud Applications provided by Hexagon to the Customer. Not all of the types of Software or Cloud Applications are provided with Documentation or with similar Documentation. "Effective Date" means the date and time the last Party is on notice that all Parties have accepted the Primary Contracting Document. Hexagon Master Terms and Conditions S1082020-MT Page 34 "Emergency Maintenance" means all maintenance performed when a Cloud Service Request demands immediate, unplanned attention, as reasonably determined by Hexagon. "Error" means a Defect with a purchased Cloud Application, Cloud Optional Service, or Third Party Software Products causing a purchased Cloud Application to fail to materially conform to its designed functionality or Documentation. Errors are further classified into the same four levels as corresponding to the definition for "Defect." "EULA" means the certain Hexagon End -User License Agreement set forth in these Master Terms as Exhibit A and/or that delivered with Software and which must be accepted prior to Software installation. "Exchanged Product" means a later released Software Product which the Customer will receive pursuant to its Maintenance Contract and supplant the Replaced Product "Fixed Price Project Assignment" means a type of Order where Hexagon will provide Services and/or Software licenses for a fixed price. "Hexagon" means Intergraph Corporation through its Safety & Infrastructure division. "Hexagon IP" means Hexagon or Hexagon Affiliate developed, created, or prepared Intellectual Property. "Installation Guide" means a computer file in a Microsoft Word or Adobe PDF document or a text file that contains information a User may need to install or operate a Software Product. "Intellectual Property" or "IPR" means all forms of intellectual property including, but not limited to, patents, trademarks, copyrights, trade secrets, methodologies, logos, techniques, processes, know-how, formulae, algorithms, logic designs, screen displays, schematics, source and object code computer programs or software, documentation, mask work rights, design, ideas, product information, inventions and improvements thereto (whether or not patentable), and all works of authorship fixed in any medium of expression (including any form of online, digital, or electronic medium), whether or not copyrightable and whether registered or not. "Lapse" means an occurrence of any period of time, regardless of duration, during which (i) a Covered Product is not the subject of an active Order for Maintenance Services or other Maintenance Contract and an active Coverage Period, and/or (ii) payment is past due to Hexagon under a Maintenance Contract. Extension of a Coverage Period and/or payment to Hexagon after the occurrence of a Lapse shall not negate a Lapse, absent Hexagon's express written waiver. "License Key(s)" means certain unique data string(s) verifying authorized access to the Cloud Application(s), which are purchased by the Customer and provided by Hexagon, as set forth on the Quote. "Local Environment" means the collection of environments provided and supported by Customer (e.g. providing System Equipment, etc.) in which the Local Software operates. "Local Software" means software applications incidental to the Cloud Program which are designed to operate natively on devices outside the Cloud Portal and in the Local Environment. "Maintenance Services" means only those services described in the document titled "Maintenance Terms and Conditions for Software" provided by Hexagon with respect to Software and other Deliverables licensed to Customer and identified in the Order Documents as the subject of Maintenance Services. "Material Adverse Effect" means a change that individually or collectively in aggregate with other changes has the impact of (i) negatively and materially reducing the Customer's and/or its Affiliates and/or its/their Authorized Cloud Users' or Users' access and/or usage rights in respect of the Cloud Program and which render the Cloud Program unusable for its primary intended purpose or (ii) making the Cloud Program materially less secure which results in increased risk to Customer Data or other data belonging to other Hexagon customers. For clarity, a Material Adverse Effect is a condition which would render the Cloud Program un-usable or materially less secure for intended users generically, and not merely as a result of individual characteristics associated with Customer or its specific implementation or operation. "Maintenance Contract" means a contract under which Hexagon provides Maintenance Services tc Customer in relation to Covered Products and under which Customer is to compensate Hexagon therefor. "Metered License" means a specific type of Subscription License that allows the Customer to use the Subscription License up to the number of hours set forth in the Quote during the Subscription Term. For Hexagon Master Terms and Conditions S1082020-MT Page 35 reference, a Subscription License that is a Metered License shall have the word "Metered" in the Software Product name and/or have the letters "MTR" at the end of the product number for the Software Product instead of the other identifiers corresponding to an unmetered Subscription License referenced in its definition. "Modern Release" means a version of a Software Product published by Hexagon no more than eighteen (18) months prior to Customer's first use thereof in Production. "Month" means, unless otherwise stated in the applicable provision, a calendar month. "Network Requirements" means (i) the minimum requirements, including but not limited to software and/or hardware, internet connection, latency or other requirements, which must be met by Customer in order to access the Cloud Portal and use the Cloud Program; and (ii) network recommendations to the Customer which describe general and specific recommendations for the network connection requirements of the Cloud Program in order to enable the Cloud Program to function as designed. The Network Requirements may be updated from time to time and Customer will be notified of such update via posting in the Cloud Portal or as otherwise determined by Hexagon. "Offboarding" or "Offboarded" means the process for offboarding the Customer Data (or part thereof) from the Customer Cloud Environment and relocating or facilitating relocation of Customer Data to another Customer -designated location. "Onboarding" or "Onboarded" means the process of loading Customer Data into the Customer Cloud Environment. "Onsite Fee" means a fixed fee encompassing Hexagon's travel expenses for an individual trip (an individual trip means to travel from the Hexagon resource's primary duty station in furtherance with Order and lasting no more than five (5) consecutive days). "Order" means each individual purchase transaction in which the Parties engage, as evidenced by Order Documents. "Order Documents" shall mean written documents, the terms of which include Hexagon's commitment to provide specific products, licenses, and/or services at a specified price, subject to the terms and conditions of the Primary Contracting Document. Order Documents may consist of a single document executed by the parties or a combination of documents that together form an Order. "Perpetual License" means a type of license for a Software Product which allows the User to use the Software Product in perpetuity so long as the User does not otherwise violate the terms of the EULA. For reference, a Perpetual License on a Quote is denoted by its absence of either the terms "Subscription," "SaaS," or "Metered" and/or the absence of the letters "SU" or "MTR" at the end of the Software Product number or the letters "HCL" at the beginning of the Software Product number. "Personal Data" means data, including but not limited to criminal justice information, and other information which corresponds to a living individual person defined to be Personal Data under the applicable Personal Data protection laws of the Customer's jurisdiction. "Planned Maintenance" means maintenance planned and communicated in advance by Hexagon to Customer for the maintenance of the Cloud Program. "Primary Contracting Document" means the contract document accepted by the Parties which references and incorporates this Terms Glossary and/or references and incorporates a document to which this Terms Glossary is an exhibit or attachment. "Primary License" means the license(s) of the Software Product provided to Customer for general production use as authorized by the EULA. "Product Change Request" means a request for additional functionality or modification to the purchased Cloud Application(s) or Covered Products. "Production" means, as applicable, where a Subsystem or Cloud Program is used in production/operation with an aim to accomplish one or more of its ultimate intended purposes. Operation solely for testing or training is not Production. Hexagon Master Terms and Conditions S1082020-MT Page 36 "Production Environment" means a logical group of virtual or physical computers comprised within the Cloud Environment to which the Customer will be provided with access and use the purchased Cloud Application(s) in production and for its generally marketed purpose. "Production System License" means the license(s) of Software Product provided to User for general production use. "Product -Specific Terms" modify the EULA, and (ii) in the event of a conflict between the EULA and Product -Specific Terms, Product -Specific Terms shall govern for the applicable Software. In the event of a conflict of terms between the EULA, any prior Product -Specific Terms (including any product -specific terms delivered in the form of an addendum to the EULA), and later Product -Specific Terms, the later Product -Specific Terms shall take precedence over the EULA and any prior Product -Specific Terms regarding the subject Software. "Purchase Order" or "PO" means a document issued by Customer to Hexagon to authorize the delivery of certain Services, Deliverables, or Cloud Programs. "Quote" means a document issued by Hexagon reflecting Services, Maintenance Services, Deliverables, and/or Cloud Programs, which Hexagon offers to provide Customer, as well as the prices and fees therefor, the Customer's name and location, and any applicable Cloud Services Schedule. To the extent any document or information is identified in the Quote with the intention of it being incorporated into the Quote, it will form part of the Quote. "Replaced Product" means an earlier Software Product which will be replaced pursuant to a Maintenance Contract for an Exchange Product. "Security Incident" means an event or set of circumstances resulting in a compromise of the security, confidentiality, or integrity of Customer Data under Hexagon's control. Examples of Security Incidents include: (i) security breaches to Hexagon's network perimeter or to internal applications resulting in compromise of Customer's Data; (ii) severe degradation of, Hexagon's security controls, methods, processes or procedures that result in compromise of the security, confidentiality or integrity of Customer Data; and (iii) the unauthorized disclosure of Customer Data. "Server" means a computer or computer program which manages access by Clients to a centralized resource or service in a network. "Server -based Software Product" means Server -based software that is accessed by one or more Clients. "Services" means the work, services, projects, assignments, or tasks Hexagon shall perform pursuant to an Order. Services do not include Maintenance Services or Cloud Programs. "Services Deliverable" means any data, document, information, Customized Software, Third Party Software, or material provided to Customer as a product of Hexagon's performance of Services pursuant to the Primary Contracting Document. Cloud Programs are not Service Deliverables. "Software" means the software owned by Hexagon or an Affiliate and Third Party Software that is licensed to Customer. For the avoidance of doubt, Cloud Programs and their contents are not "Software" as that term is used herein. "Software License Sale" means a type of an Order that involves only the sale of Perpetual Licenses from Hexagon to Customer. This type of Order does not include Services or Cloud Programs. "Software Product" means the Hexagon software product(s) identified in the Order Documents, which includes (i) any associated Hexagon files or media with which the software is provided, (ii) any associated templates, data, printed materials, and "online" or electronic Documentation, and (iii) any Updates or Upgrades of such Software Products not made the subject of a separate license agreement. The term Software Products shall not include, and no rights of use are granted to User for, third party components, Hexagon products, or dependencies unnecessary to operate products made the subject of the Order Documents, but incidentally delivered within the same files or media. Software Product shall not mean any Third Party Software. For the avoidance of doubt, Cloud Programs and their contents are not "Software Products" as that term is used herein. Software Products are subject to all of the terms and conditions of the EULA which the Parties agree will apply to the same; and in the absence of such agreement, then the terms of the EULA provided with the Software Product. Hexagon Master Terms and Conditions S1082020-MT Page 37 "SOW" means a statement of work setting forth the scope of Services being provided pursuant to an Order "Subscription" means the collection of Subscription License(s) identified on the Quote and or purchased by the Customer. "Subscription License" means a particular type of license to a Software Product that allows a Customer to use the Software Product for a specified period of time identified in the Quote. For reference, a Software Product that is a Subscription License shall have the word "Subscription" in the Software Product name and/or have the letters "SU" at the end of the product number for the Software Product. "Subscription License Sale" means a type of an Order that involves only the sale of Subscription Licenses from Hexagon to Customer. This type of Order does not include Services or Cloud Programs. "Subscription Term" means the period of time during which Users are authorized to use the Subscription License as set forth on the applicable Quote beginning on the date the Subscription Licenses are provided to the User or the User is provided license keys or access to the Subscription License, unless otherwise noted in the Order Documents. "Subsystem" means a Hexagon solution that is designed to provide a specific capability independent of the procurement of any other Subsystem. Hexagon's computer aided dispatch system ("I/CAD"), records management system ("RMS"), field based reporting ("FBR"), G/Technology (G/Tech), In/Service and mobile for public safety ("MPS") are each an example of a Subsystem. "Supplementary License" means a license(s) of the Software Product which is made available by Hexagon for select Software Products to augment Primary Licenses for special purposes. Each Supplementary License requires a Primary License and the term of the Supplementary License shall not exceed the term of the applicable Primary License. "System" means a physical or operational location where the Software Product resides and operates on an individual server or where a single operational identification number ("Site ID") has been assigned by Hexagon. "System Equipment" means all computer -related hardware, including but not limited to, servers, workstations, cables, mice, keyboards, cameras, and SAN's; operating system software; database software; and other third party software. "Task" means an Activity or combination of Activities of any nature whether tangible or intangible, whether onsite or remote, or an event, as further identified in an SOW. "Task Acceptance" means the event when the Task Acceptance Criteria has been satisfied in accordance with the Task Acceptance Process. "Task Acceptance Criteria" means the criteria by which a Task will be evaluated for completion as described in an SOW. "Task Acceptance Process" means the process by the Customer and Hexagon verify completion of the Task Acceptance Criteria as further described below. Once Hexagon believes the Task Acceptance Criteria has been successfully completed, Hexagon shall submit for execution by Customer's project manager a sign -off form in substantial conformity with Exhibit C, "Project Deliverable Sign -off Form." Within ten (10) calendar days of receipt of the applicable Project Deliverable Sign -off Form for the completed milestone or Task, Customer's project manager will either: (i) execute the Project Deliverable Sign -off Form provided by Hexagon, or (ii) provide a written description of all deficiencies to Hexagon. If Customer fails to perform either action identified in the preceding sentence within ten (10) calendar days, or if the Deliverable, including the Software contained in the Fixed Price Project Assignment Order, is placed into production or utilized in a live environment, then the Task or milestone shall be deemed accepted. "Term" means the duration of performance under the contract into which this Terms Glossary is incorporated by reference. "Third Party Service Provider" means the third party service provider with whom Hexagon enters into a subcontract with respect to the hosting of a cloud platform, Training Curricula, and/or other services to provide an element of the Cloud Program, Training Curricula, or other service to Customer (if applicable) on behalf of Hexagon. Hexagon Master Terms and Conditions S1082020-MT Page 38 "Third Party Software" means computer software or other technology in which any person or entity, other than Hexagon or Hexagon's Affiliate, has any right, title or interest, including any restrictions or obligations (such as obligations to obtain consents or approvals and restrictions that may be eliminated only by obtaining such consents or approvals) applicable to the computer software or technology, but does not include software embedded in the Software Products by license from third parties. The use of Third Party Software is subject to all of the terms and conditions of the Third Party Terms. "Third Party Software Products" also means, where applicable, pre -requisite third party software products used by Hexagon in order for Customer to receive other components of the Cloud Program or licensed by Hexagon and used by the Customer to use Cloud Application or Cloud Optional Services. "Third Party Terms" means for certain Third Party Software additional terms and conditions provided with the Order Documents and/or cited in the Use Terms, or otherwise made available to the Customer or any User. "Time and Materials Project Assignment" means Hexagon will perform the Services set forth in an Order on an hourly basis until the project is either completed or the authorized hours are exhausted, whichever comes first. "Training Curricula" means one or more training classes or resources provided by Hexagon to Customer as a service over a limited time period. "Training Program Statement" means document(s) titled "Training Program Statement," attached to the Quote and containing additional details regarding the Training Curricula parts being provided to Customer, including, but not limited to: whether the training is provided live on -site, live but remotely, or by way of recorded or static online content; and, certain other pertinent details; provided that "Training Program Statement" may alternatively refer to only those specific terms of an SOW containing additional details regarding Training Curricula being provided to Customer. "Update" means any Upgrade, modified version, fix, patch and/or update of the Software Product. Updates not meeting the definition of Upgrades are subject to all of the terms and conditions of the EULA provided with User's then current version of the Software Product. "Upgrade" means each new release of the Software Product. Upgrades require a full installation and may be provided with a separate EULA. Any EULA delivered with the Upgrade will supersede any EULA associated with prior releases of the Software Product. "User" means Customer or an individual employed by Customer and authorized by Hexagon to use a particular Software Product, Cloud Application, Third Party Software Product, or Cloud Optional Services on behalf of the Customer. A User may also include Customer's contractor who requires temporary use in order to provide services on Customer's behalf. A person can only be authorized and a User if the person is an employee or designee of Customer and Customer has purchased the requisite number of licenses, or in the case of Cloud Programs, the requisite number of License Key(s) to provide Credentials for that User. "Use Terms" means the Hexagon Product Usage Policy and Product Specific Terms accessible from https://www.hexagonsafetyinfrastructure.com/-/media/Legal/Hexagon/SI/Licenses/LLP/LLP 08-2019.0 which are incorporated herein. For purposes of clarity, the Use Terms corresponding to the date of the Order shall apply to that specific Order and the Software provided thereunder. "Version Limitation I" is a status reached by a Software Product on the earlier of the (i) the third anniversary of the Customer's first operation of that Software Product in a live production environment or (ii) the fifth anniversary of Hexagon's first actual delivery of the Software Product to the Customer for implementation; provided that each time Customer upgrades the version of the Software Product used in production to a Modern Release, a reset shall occur, such that Version Limitation I shall thereafter be reached upon the third anniversary of the Customer's first operation of such Modern Release in a live production environment. "Version Limitation II" is a status reached by a Software Product on the earlier of (i) the fourth anniversary of the Customer's first operation of that Software Product in a live production environment or (ii) the sixth anniversary of Hexagon's first actual delivery of the Software Product to the Customer for implementation; provided that each time Customer upgrades the version of the Software Product used in production to a Modern Release, a reset shall occur, such that Version Limitation 11 shall thereafter be reached upon the Hexagon Master Terms and Conditions S1082020-MT Page 39 fourth anniversary of the Customer's first operation of such Modern Release in a live production environment. "Version Limitations" means, separately and collectively, limitations on Services to be provided hereunder based upon a Covered Product reaching Version Limitation I and/or Version Limitation II. "Virus" means any thing or device (including any software, code, file or program) which may: (i) prevent, impair or otherwise adversely affect the operation of any computer software, hardware or network, any telecommunications service, equipment or network or any other service or device; (ii) prevent, impair or otherwise adversely affect access to or the operation of any program or data, including the reliability of any program or data (whether by rearranging, altering or erasing the program or data in whole or part or otherwise); or (iii) adversely affect the user experience or security, including worms, Trojan horses, viruses and other similar things or devices. "Work" means, as applicable, the performance or providing of Services, Maintenance Services, or Cloud Services. "XML Files" means the XML (Extensible Markup Language) files generated by the Software Product, where applicable. "XSL Stylesheets" means the XSL (Extensible Stylesheet Language) presentation of a class of XML Files which, when included with the Software Product, describe how an instance of the class is transformed into an XML (Extensible Markup Language) document that uses the formatting vocabulary. END OF EXHIBIT G Hexagon Master Terms and Conditions S1082020-MT Page 40 40, A HEXAGON CLOUD SERVICES - ACCEPTABLE USE POLICY OVERVIEW The purpose of this Acceptable Use Policy ("AUP") is to ensure the responsible use by Customers, and their associated Authorized Users, of the Cloud Services and to avoid practices which degrade the usability of the Cloud Services. This AUP is designed to protect the image and reputation of all Customers, the Cloud Services, and Hexagon as a responsible service provider, by taking care of confidentiality and availability of the Cloud Services. The rules in this AUP are rules for the acceptable use of the Cloud Services. All Customers and Authorized Users of the Cloud Services must at all times comply with this AUP. Failure to comply with this AUP, as determined by Hexagon, may result in suspension of the Cloud Services or termination of the Cloud Services Agreement. Hexagon, without limitation to its other rights, reserves the right, without liability or notice to the Customer: (i) to disable any Authorized User's access to any material that breaches the provisions of this AUP, and/or (ii) to disable access to the Cloud Services in the event an Authorized User breaches this AUP. OBLIGATIONS 1. You MUST understand your security obligations within your role and abide by them. 2. Your use of the Cloud Services MUST be decent, honest, and comply with both legislative and regulatory requirements applicable to the use of the Cloud Program. 3. You MUST scan ALL files for viruses and malware using a commercial Anti-Virus/Anti-Malware solution PRIOR to uploading them to the Cloud Program. Under no circumstance are files corrupted with viruses or malware to be uploaded to the Cloud Program. 4. You MUST NOT share user IDs or passwords. It is your responsibility to keep your password confidential. If you believe your account has been compromised, change your password and immediately report this to your company's authorized Cloud Services contact. 5. You MUST NOT access, assist, or enable others to access, anything you or they have not been explicitly authorized to access, or attempt to do any of the foregoing. 6. You MUST NOT attempt to scan, stress, probe, test, or carry out any activity that may be deemed to compromise or risk the confidentiality or availability of the Cloud Services, unless explicitly authorized by a Hexagon representative to do so. 7. You MUST NOT disable, reconfigure, or attempt to bypass any security measures (for example Anti -Virus), unless explicitly authorized by a Hexagon representative. 8. You MUST NOT use the Cloud Services to harass, defame, defraud, libel, slander, intimidate, impersonate, or otherwise abuse another person, including other Customers, Hexagon, or Hexagon's suppliers. 9. You MUST NOT use the Cloud Services for the creation, collection, storage, downloading, or displaying of any offensive, obscene, indecent, or menacing images, data, or material capable of being resolved into such. 10. You MUST NOT use the Cloud Services for the creation or transmission of material such that infringes the copyright or intellectual property of another person/organization. GUIDANCE (a) In the event of any security issues, incidents, or near misses, you MUST promptly take all possible steps to notify your company's authorized Cloud Services contact and preserve any supporting information/evidence. (b) Hexagon reserves the right to investigate any suspected violation of this AUP or misuse of the Cloud Services, and report any activity that Hexagon suspects violates any law or regulation to appropriate law enforcement officials, regulators, or other appropriate third parties. (c) If you are unsure or are concerned about an issue relating to, or have a query about, this AUP, seek guidance from your company's authorized Cloud Services contact. AGREEMENI By accessing and/or using the Cloud Program you accept and agree to be bound and abide by this AUP. If you do not want to agree to this AUP, you must not access or use the Cloud Program. HEXAGON THIS DATA PROCESSING ADDENDUM ("DPA") supplements the Master Terms between Customer and Hexagon, or other agreement between Customer and Hexagon (the "Agreement") governing Customer's use of Hexagon Software Products, Maintenance Services, and/or the Cloud Program Hexagon's performance of Services (collectively, "Hexagon Products") when the GDPR applies to Customer's use of Hexagon Products to process Customer Data. This DPA is an agreement between Customer and Hexagon. Any and all terms capitalized but not otherwise defined herein shall have the meanings ascribed to them in the Agreement. DEFINITIONS AND CONSTRUCTION 1.1 Definitions "EU Model Clause Agreement" means an agreement made using the relevant EU Model Clauses as adopted by the EU Commission for the transfer of personal data to third countries. "EU Personal Data Legislation" means (a) until 24 May 2018, Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data and any amendments made thereto, (b) until 24 May 2018, local legislations where the Directive referred to in (a) is implemented and any amendments made thereto, and (c) the GDPR. "GDPR" means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing the Directive 95/46/EC (General Data Protection Regulation), and any amendments made thereto. "Hexagon Affiliates" means a legal entity that directly or indirectly through one or more intermediaries is controlled by or under common control with Hexagon's ultimate parent company. For the purposes of this definition, the term "control" shall be understood as the possession, directly or indirectly, of the power to direct or cause the direction of the management and policies of a legal entity, whether through the ownership of voting stock, by contract, or otherwise. "Party" or "Parties" means the Customer and Hexagon separately, or jointly, as the case may be. "Regulatory Requirements" means the privacy and personal data legislation applicable to the processing of personal data, including the EU Personal Data Legislation, and such legislation as may replace the aforementioned legislation from time to time (and in case of discrepancies or contradictions between different rules or regulations, the one which provides the highest degree of privacy and/or information security shall apply). "Supervisory Authority" means any court, regulatory agency or authority which, according to applicable laws and/or regulations (including the Regulatory Requirements), supervises privacy issues and/or the processing of personal data. 1.2 Construction 1.2.1 Non -capitalized terms and expressions used in this Agreement, e.g. `data subject', `controller', `personal data', `processing', `processor', `third country', etc., shall have the same meaning as in EU Personal Data Legislation. 1.2.2 Unless it is otherwise stated herein, or clearly follows from the context in which appears, the term "including" shall mean "including without limitation". Hage 1 of i t 2. SPECIAL UNDERTAKINGS OF THE PARTIES 2.1 Roles, Ownership of Personal Data, Processing and Purpose 2.1.1 The Customer shall be regarded as a controller of all personal data processed on behalf of the Customer and in accordance with its instructions. Hexagon shall be considered a processor of the personal data processed on behalf of the Customer. 2.1.2 Hexagon may only process the Customer's personal data for the purpose set forth on Schedule 1 attached hereto and to the extent it is necessary for the fulfilment of Hexagon's obligations under this DPA or the Agreement. 2.1.3 Hexagon acknowledges that, between the Parties, all rights, title, and interest in the personal data processed as a result of this Agreement is vested solely in the Customer, irrespective of whether Hexagon is considered to be a controller of personal data. 2.2 Special Undertakings of the Customer The Customer undertakes to: (a) Ensure that there is a legal ground for processing the personal data covered by this DPA; (b) Ensure that the data subjects, as required by the EU Personal Data Legislation, have received sufficient information regarding the processing, including information on that Hexagon may process the personal data on behalf of the Customer; (c) Immediately after it is brought to the Customer's attention, inform Hexagon of any erroneous, rectified, updated or deleted personal data subject to Hexagon's processing; (d) In a timely manner, provide Hexagon with lawful and documented instructions regarding Hexagon's processing of personal data; (e) Before this DPA enters into force, provide Hexagon with the Customer's applicable policies and guidelines for processing of personal data; and (f) Act as the data subject's point of contact. 2.3 Special Undertakings of Hexagon Hexagon undertakes to (a) Only process the personal data in accordance with the Customer's documented instructions, including with regard to transfers of personal data to a third country or an international organization, unless required to do so by Regulatory Requirements; in such a case, Hexagon shall inform the Customer of that legal requirement before processing the personal data, unless such information is prohibited by the Regulatory Requirements on important grounds of public interest; (b) Ensure that such employees (of Hexagon or its subcontractors) which process personal data on behalf of the Customer have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality; (c) Take all measures required pursuant to GDPR, Article 32; (d) Taking into account the nature of the processing, assist the Customer by appropriate technical and organizational measures, insofar as this is possible, for the fulfilment of the Customer's obligation to respond to requests for exercising the data subject's rights set forth in the EU Personal Data Legislation; Hage j of i t (e) Except in cases of personal data breach, upon a timely request by the Customer, assist the Customer in ensuring compliance with the obligations pursuant to GDPR, Articles 32 to 36 (e.g. assist in data protection impact assessments) taking into account the nature of the processing and the information available to Hexagon; and (f) Make available to the Customer the information necessary to demonstrate compliance with Hexagon's obligations set forth in this DPA and allow for and contribute to audits, including inspections, conducted by the Customer or another authorized third party, in accordance with Section 4. 2.3.1 Hexagon shall immediately inform the Customer if, in its opinion, a Customer instruction infringes the EU Personal Data Legislation. 2.3.2 The Parties agree that the security measures taken by Hexagon, listed in the Agreement, fulfils Hexagon's undertakings in Sections 2.3(c) and 2.3(e). SUBCONTRACTORS 3.1 Hexagon shall be entitled to engage subcontractors acting as sub -processors of the personal data under the condition that such subcontractors are bound by a written contract which states that they must adhere to the same data protection, privacy and audit obligations as Hexagon under this DPA. 3.2 Should Hexagon wish to engage a subcontractor different from or additional to those subcontractors set forth in the Agreement or the Quote, it shall notify the Customer in advance. The Customer may, within twenty-four (24) hours from receipt of the notification, object to Hexagon appointing that specific subcontractor. Should the Customer's objection(s) result in any additional costs or expenses for Hexagon, e.g. if the engagement of another subcontractor than the one initially proposed by Hexagon would result in additional or increased costs or expenses by Hexagon, Hexagon shall be compensated for such additional and/or increased costs and expenses. 3.3 Hexagon shall remain the Customer's sole point of contact, unless otherwise agreed. 3.4 For the avoidance of doubt, the Customer fully and explicitly consents to the use of the subcontractors with whom Hexagon has agreements in place with at the time this DPA enters into force, including all Hexagon Affiliates, regardless if they have been engaged as subcontractors at the time of this DPA. 4. AUDIT RIGHTS AND LOCATIONS 4.1 The Customer shall have the right to perform audits of Hexagon's processing of the Customer's personal data (including such processing carried out by Hexagon's subcontractors, if any) in order to verify Hexagon's, and any subcontractor's, compliance with this DPA and the EU Personal Data Legislation. 4.2 Hexagon will, during normal business hours and upon reasonable notice (whereby a notice period of twenty (20) Business Days shall always be deemed reasonable), provide an independent auditor, appointed by the Customer and approved by Hexagon, reasonable access to the parts of facilities where Hexagon is carrying out processing activities on behalf of the Customer, to personnel and to all information relating to the processing of the Customer's personal data. The auditor shall comply with Hexagon's work rules, security requirements and standards when conducting site visits. 4.3 A Supervisory Authority shall always have direct and unrestricted access to Hexagon's premises, data processing equipment and documentation in order to investigate that Hexagon's processing of the personal data is performed in accordance with the Regulatory Requirements. 4.4 The Customer is responsible for all costs associated with the audit mentioned in Section 4.2, save for when the audit concludes a material breach of Hexagon's undertakings in Page 4 Oi 1 / violation of this DPA. If so, Hexagon shall compensate the Customer for reasonable and verified costs associated with the audit. 4.5 The Customer's personal data may not be processed in a manner that entails a transfer to a third country or an international organisation (including inadvertently through the use of cloud -based IT solutions) unless this is in accordance with the Customer's instructions. 5. INTERNATIONAL PERSONAL DATA TRANSFERS 5.1 Hexagon Affiliates and sub -contractors outside the EU/EEA 5.1.1 When providing the Hexagon Products, Hexagon may need to process the Customer's personal data outside of the EU/EEA. Therefore, the EU Model Clause Agreement as set out in Schedule 2 shall apply in such instances. The Parties agree that any disputes arising under an EU Model Clause Agreement shall be treated as if they had arisen under the Agreement. 5.1.2 If the Customer's personal data is to be transferred to and processed by a sub- contractor located outside the EU/EEA, Hexagon is obliged to ensure that the sub- contractor accedes to the EU Model Clause Agreement as set out in Schedule 2. 5.1.3 The above shall not apply if the jurisdiction in which Hexagon or sub -contractor is established has been deemed by the European Union as a jurisdiction with adequate protection for personal data. 6. REMUNERATION 6.1 The remuneration for Hexagon's undertakings under this DPA shall, unless otherwise stated in this Section 6.1, be included in the remuneration paid by the Customer under the Agreement. Notwithstanding the aforesaid, Hexagon shall always, in case of the Customer's instructions or other requests under this DPA requires extra measures by Hexagon in addition to what is reasonably required under the Agreement, be entitled to compensation for such surplus work on a time and material basis. This includes, for example, Hexagon's assistance handling data subject requests. 6.2 In the event that (a) the Customer amends its written instructions mentioned in Section 2.2(d), or (b) the Customer would require the implementation of technical or organizational measures, in addition to those mentioned herein, and this would cause a cost increase to Hexagon, then Hexagon shall be entitled to request an equitable adjustment in the remuneration. 6.3 The payment terms for the adjusted remuneration shall be governed by the provisions regarding payment in the Agreement. TERM AND TERMINATION 7.1 This Agreement shall enter into force on the Effective Date. Unless terminated earlier due to a material breach of the terms of this DPA, this Agreement shall remain in force until the termination or expiration of the Agreement, whereupon it shall terminate automatically without further notice. 7.2 On termination of this DPA for any reason, Hexagon shall cease to process the personal data processed on behalf of the Customer and shall, at the Customer's expense, provide for the return to the Customer (or its nominated third party) of all such personal data together with all copies in its possession or control unless storage of the personal data is required under the Regulatory Requirements. If the Customer does not respond to an offer from Hexagon to return the personal data processed by it under this DPA, within a period of three (3) months from when the offer was made, Hexagon will be entitled to delete any such personal data, including copies thereof, unless storage of the personal data is required under the Regulatory Requirements. 8. FORCE MAJEURE Hage b of 1 t Hexagon shall not be liable for any default or delay in the performance of its obligations under this DPA if and to the extent the default or delay is caused by Force Majeure. A failure by a subcontractor will be considered a Force Majeure event provided that the underlying reason for the subcontractor's non-performance is an event which, if it had been related directly to Hexagon, would have qualified as a Force Majeure event under this DPA. MISCELLANEOUS 9.1 Neither Party may assign its rights or obligations under this DPA without the prior written consent of the other Party. Notwithstanding the foregoing, Hexagon may assign its rights and obligations under this DPA, without the approval of Customer to: (a) a Hexagon Affiliate, or (b) another business entity in connection with a merger, consolidation, or reorganization of Hexagon or any of its subsidiaries. 9.2 This DPA and the Agreement sets forth and constitutes the entire agreement and understanding between the Parties with respect to the subject matter hereof and all prior agreements, understandings or promises with respect thereto are hereby superseded. 9.3 No amendment, modification, release, or discharge of this DPA shall be binding upon the Parties unless in writing and duly executed by authorised representatives of both Parties. 10. GOVERNING LAW AND DISPUTES 10.1 Provisions regarding governing law and disputes are set forth in the Agreement. [SCHEDULES ATTACHED HERETO] Hage b of 1 t SCHEDULE 1 DESCRIPTION OF THE PROCESSING OF PERSONAL DATA Subject matter. The subject matter of the data processing under this DPA is Customer Data. 2. Duration. As between Hexagon and Customer, the duration of the data processing under this DPA is determined by Customer. 3. Purpose. The purpose of the data processing under this DPA is the provision of the Hexagon Products initiated or requested by Customer from time to time. 4. Nature of the Processing: Compute, storage, and such other services as described in the Agreement and documents referenced therein and initiated by Customer from time to time. 5. Type of Customer Data: Customer Data uploaded to or provided by Customer in its use of or receipt of Hexagon Products. 6. Categories of Data Subjects: The data subjects may include Customer's end -users and natural persons that are the subject of Customer's business and/or operations. Hage t of i t SCHEDULE 2 EU MODEL CLAUSES Commission Decision C(2010)593 Standard Contractual Clauses (processors) For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection. For the purposes of Article 28 of the EU General Data Protection Regulation (the "GDPR"), the provisions in Appendix 3 shall form an integrated part of these Clauses. Name of the data exporting organisation: The entity indentified as "Customer" in the DPA (the data exporter) Name of the data importing organisation: The entity identified as "Hexagon" in the DPA (the data importer) each a "party"; together "the parties", HAVE AGREED on the following Contractual Clauses (the Clauses) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. Hage b of 1 t Clause 1 Definitions For the purposes of the Clauses (a) 'personal data, 'special categories of data, 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority'shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data; (b) 'the data exporter' means the controller who transfers the personal data; (c) 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC; (d) 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract; (e) 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established; (f) 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing. Clause 2 Details of the Transfer The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 which forms an integral part of the Clauses. Clause 3 Third -Party Beneficiary Clause 1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to 0), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third -party beneficiary. 2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by Hage 9 of i t contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. 3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third -party liability of the subprocessor shall be limited to its own processing operations under the Clauses. 4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law. Clause 4 Obligations of the Data Exporter The data exporter agrees and warrants: (a) that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State; (b) that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses; (c) that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 to this contract; (d) that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation; (e) that it will ensure compliance with the security measures; (f) that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC; (g) to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension; (h) to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information; Hage i u of it (i) that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and that it will ensure compliance with Clause 4(a) to (i) Clause 5 Obligations of the Data Importer' The data importer agrees and warrants: (a) to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; (b) that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; (c) that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred; (d) that it will promptly notify the data exporter about: (i) any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation, (ii) any accidental or unauthorised access, and (iii) any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so; (e) to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; (f) at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; (g) to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain t Mandatory requirements of the national legislation applicable to the data importer which do not go beyond what is necessary in a democratic society on the basis of one of the interests listed in Article 13(1) of Directive 95/46/EC, that is, if they constitute a necessary measure to safeguard national security, defence, public security, the prevention, investigation, detection and prosecution of criminal offences or of breaches of ethics for the regulated professions, an important economic or financial interest of the State or the protection of the data subject or the rights and freedoms of others, are not in contradiction with the standard contractual clauses. Some examples of such mandatory requirements which do not go beyond what is necessary in a democratic society are, inter alia, internationally recognised sanctions, tax -reporting requirements or anti -money-laundering reporting requirements. Hage i i of i i commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter; (h) that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent; (i) that the processing services by the subprocessor will be carried out in accordance with Clause 11; (j) to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter. Clause 6 Liability 1. The parties agree that any data subject, who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered. 2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity. The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities. 3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses. Clause 7 Mediation and Jurisdiction The data importer agrees that if the data subject invokes against it third -party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject: (a) to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; (b) to refer the dispute to the courts in the Member State in which the data exporter is established. Hage 11 of i i 2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law. Clause 8 Cooperation with Supervisory Authorities 1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law. 2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law. 3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5 (b). Clause 9 Governing Law The Clauses shall be governed by the law of the Member State in which the data exporter is established. Clause 10 Variation of the Contract The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause. Clause 11 Subprocessing The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement. 2. The prior written contract between the data importer and the subprocessor shall also provide for a third -party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or Hage i j of it data importer by contract or by operation of law. Such third -party liability of the subprocessor shall be limited to its own processing operations under the Clauses. 3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established. 4. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 0), which shall be updated at least once a year. The list shall be available to the data exporter's data protection supervisory authority. Clause 12 Obligation After the Termination of Personal Data Processing Services The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore. 2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1. Page 14 of 1 / APPENDIX 1 TO THE STANDARD CONTRACTUAL CLAUSES This Appendix forms part of the Clauses and must be completed and signed by the parties. The Member States may complete or specify, according to their national procedures, any additional necessary information to be contained in this Appendix. Data exporter The data exporter is the entity indentified as "Customer" in the DPA. Data importer The data importer is Hexagon. Data subjects Data subjects are defined in Schedule 1 of the DPA. Categories of data The personal data is defined in Schedule 1 of the DPA. Processing operations The processing operations are defined in Schedule 1 of the DPA. Hage 1 b of it APPENDIX 2 TO THE STANDARD CONTRACTUAL CLAUSES This Appendix forms part of the Clauses and must be completed and signed by the parties. Description of the technical and organisational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c) (or document/legislation attached): The technical and organizational security measures implemented by the data importer are as described in the Agreement. Hage 1 b of it APPENDIX 3 TO THE STANDARD CONTRACTUAL CLAUSES This Appendix forms part of the Clauses and by signing the Clauses, the data importer undertakes to comply with the undertakings listed in this Appendix, in addition to its undertakings following the Clauses. In the event of inconsistencies between the provisions of this Appendix and any other provisions of the Clauses, the other provisions of the Clauses shall prevail. Processing in Accordance with Documented Instructions The Data importer undertakes to only process personal data in accordance with applicable law and on documented instructions from the data exporters, including with regard to transfers of personal data to a third country or an international organisation, unless required to do so by applicable law; in such a case, the data importer shall inform the data exporter of that legal requirement before processing the personal data, unless such information is prohibited by the applicable law on important grounds of public interest. Confidentiality Commitments The data importer undertakes to ensure that such employees (of the data importer or its subcontractors) who are authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. Technical and Organisational Security Measures The data importer undertakes to, taking into account the nature of the processing, assist the data exporter by implementing appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the data exporter's obligations to respond to requests for exercising the data subject's rights laid down in the GDPR. Data Breach In the case of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored or otherwise processed by the data importer on behalf of the data exporter, the data importer shall immediately inform the data exporter of such security breach and thereafter, within twenty four (24) hours at the latest, provide the data exporter with: (a) a description of the nature of the personal data breach including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned; (b) a description of the likely consequences of the personal data breach; and (c) a description of the measures taken or proposed to be taken by the data importer to address the personal data breach (including measures to prevent similar security breaches in the future), including, where appropriate, measures to mitigate its possible adverse effects. Hage i t of i i Data Protection Impact Assessment and Prior Consultation The data importer undertakes to provide reasonable assistance to the data exporter with any data protection impact assessments, and prior consultations with supervisory authorities or other competent data privacy authorities, which the data exporter reasonably considers to be required of any data exporter by Article 35 or 36 of the GDPR or equivalent provisions of any other applicable data protection law, in each case solely in relation to processing of personal data by, and taking into account the nature of the processing and information available to, the data importer. Deletion or Return of Personal Data The data importer undertakes to promptly of the date of cessation of any services involving the processing of personal data, delete and procure the deletion of all companies of such personal data or, if preferred by the data exporter, to return such data to the data exporter. Audit Rights The data importer undertakes to make available to the data exporter on request, all information necessary to demonstrate compliance with this Appendix and shall allow for and contribute to audits, including inspections, by the data exporter or an auditor mandated by the data exporter in relation to the processing of personal data by the data importer. Instructions in infringement of the GDPR or other Applicable Law. The data importer shall immediately inform the data exporter if, in its opinion, a data exporter's instruction infringes the GDPR or other applicable law. End User Data Processing Agreement for SAP Support and Professional Services This End User Data Processing Agreement ("End User DPA") applies if User has Hexagon Software Products with SAP Business Objects Software. Capitalized terms not defined herein are defined in the PERSONAL DATA PROCESSING AGREEMENT FOR SAP SUPPORT AND PROFESSIONAL SERVICES ("SAP DPA") attached hereto and made a part of this End User DPA. Hexagon and SAP have entered into an agreement through which SAP grants Hexagon the right to provide support services to Hexagon's customers ("End Customers"). In accordance with the agreement, SAP will provide certain support services to Hexagon, and on behalf of Hexagon to End Customers, which may include the processing of, and/or access to, Personal Data controlled by End Customers. Any such processing of Personal Data requires prior entry into a data processing agreement ("DPA' between all parties of the data processing chain: i.e. (i) a DPA between Hexagon and SAP, and (ii) this End User DPA between Hexagon and End Customer. This End User DPA includes the general principles of data processing in connection with support services provided by SAP. Hexagon is entering into this End -User DPA for Hexagon to use SAP as a sub -processor of Personal Data as follows. a) To the extent Personal Data controlled by End Customers, whether or not established in the European Economic Area ("EEA', is processed by SAP and its Subprocessors within the territory of the EEA, Hexagon is entering into End User DPAs with End Customers. End Customers are hereby required Under this End User DPA to enter a DPA with the same terms with other Controllers who have been authorized by End Customer to receive Support Services under Hexagon's Order Documents with End Customer ("End User Agreement', except for Section 7.2(b)-(c) of the SAP DPA. b) Regarding Section 7.2 (b)-(c) of the SAP DPA, if Personal Data controlled by End Customers or Other Data Controllers established within the EEA is processed by SAP and its Subprocessors outside of the EEA, then by executing this End -User DPA, End Customers must include it in their DPAs that End Customers or Other Data Controllers accede to the Standard Contractual Clauses between SAP SE and its relevant Non-EU Subprocessors ("Accession Model'. Other Controllers who have been authorized by End Customer to receive support service under the End User Agreement may also enter into Standard Contractual Clauses with SAP and/or the relevant Subprocessors in the same manner as End Customer in accordance with this Section. c) End Customers may request audit reports or may audit SAP as further detailed in Section 5 of the SAP DPA. SAP-DPA08292019 PERSONAL DATA PROCESSING AGREEMENT FOR SAP SUPPORT AND PROFESSIONAL SERVICES 1. BACKGROUND 1.1 Purpose and Application. This document ("DPA") is incorporated into the Agreement and forms part of a written (including in electronic form) contract between SAP and Customer. This DPA applies to Personal Data provided by Customer and each Data Controller in connection with the performance of the SAP services as set out in the relevant Agreement ("SAP Service(s)") to which is attached the present DPA which may include: (a) SAP Support as defined in the Software License & Support Agreement; and/or (b) Professional Services as described in the services agreement concluded between SAP and the Customer ("Services Agreement"). 1.2 Structure. Appendices 1 and 2 are incorporated into and form part of this DPA. They set out the agreed subject -matter, the nature and purpose of the processing, the type of Personal Data, the categories of data, the data subjects and the applicable technical and organizational measures. 1.3 GDPR. SAP and Customer agree that it is each party's responsibility to review and adopt requirements imposed on Controllers and Processors by the General Data Protection Regulation 2016/679 ("GDPR"), in particular with regards to Articles 28 and 32 to 36 of the GDPR, if and to the extent applicable to Personal Data of Customer/Controllers that is processed under the DPA. For illustration purposes, Appendix 3 lists the relevant GDPR requirements and the corresponding sections in this DPA. 1.4 Governance. SAP acts as a Processor and Customer and those entities that it permits to include Personal Data in systems accessible by SAP when performing the SAP Service act as Controllers under the DPA. Customer acts as a single point of contact and is solely responsible for obtaining any relevant authorizations, consents and permissions for the processing of Personal Data in accordance with this DPA, including, where applicable approval by Controllers to use SAP as a Processor. Where authorizations, consent, instructions or permissions are provided by Customer these are provided not only on behalf of the Customer but also on behalf of any other Controller. Where SAP informs or gives notice to Customer, such information or notice is deemed received by those Controllers permitted by Customer to include Personal Data and it is Customer's responsibility to forward such information and notices to the relevant Controllers. 2. SECURITY OF PROCESSING 2.1 Appropriate Technical and Organizational Measures. SAP has implemented and will apply the technical and organizational measures set forth in Appendix 2. Customer has reviewed such measures and agrees that the measures are appropriate taking into account the state of the art, the costs of implementation, nature, scope, context and purposes of the processing of Personal Data. Appendix 2 applies only to the extent that such SAP Services are performed on or from SAP premises. In the case where SAP is performing SAP Services on the Customer's premises and SAP is given access to Customer's systems and data, SAP shall comply with Customer's reasonable administrative, technical, and physical conditions to protect such data and guard against unauthorized access. In connection with any access to Customer's system and data, Customer shall be responsible for providing SAP personnel with user authorizations and passwords to access its systems and revoking such authorizations and terminating such access, as Customer deems appropriate from time to time. Customer shall not grant SAP access to Licensee systems or personal information (of Customer or any third party) unless such access is essential for the performance of SAP Services. Customer shall not store any Personal Data in non -production environments. 2.2 Changes. SAP applies the technical and organizational measures set forth in Appendix 2 to SAP's entire customer base receiving the same SAP Service. SAP may change the measures set out in Personal Data Processing Agreement for SAP Support and Professional Services enUS.v.11-2018 Page 1 of 11 Appendix 2 at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data. 3. SAP OBLIGATIONS 3.1 Instructions from Customer. SAP will process Personal Data only in accordance with documented instructions from Customer. The Agreement (including this DPA) constitutes such documented initial instructions and Customer may provide further instructions during the performance of the SAP Service. SAP will use reasonable efforts to follow any other Customer instructions, as long as they are required by Data Protection Law, technically feasible and do not require changes to the performance of the SAP Service. If any of the before -mentioned exceptions apply, or SAP otherwise cannot comply with an instruction or is of the opinion that an instruction infringes Data Protection Law, SAP will immediately notify Customer (email permitted). 3.2 Processing on Legal Requirement. SAP may also process Personal Data where required to do so by applicable law. In such a case, SAP shall inform Customer of that legal requirement before processing unless that law prohibits such information on important grounds of public interest. 3.3 Personnel. To process Personal Data, SAP and its Subprocessors shall only grant access to authorized personnel who have committed themselves to confidentiality. SAP and its Subprocessors will regularly train personnel having access to Personal Data in applicable data security and data privacy measures. 3.4 Cooperation. At Customer's request, SAP will reasonably cooperate with Customer and Controllers in dealing with requests from Data Subjects or regulatory authorities regarding SAP's processing of Personal Data or any Personal Data Breach. SAP shall notify the Customer as soon as reasonably practical about any request it has received from a Data Subject in relation to the Personal Data processing, without itself responding to such request without Customer's further instructions, if applicable. SAP will correct or remove any Personal Data in SAP's possession (if any), or restrict its processing, in accordance with the Customer's instruction and Data Protection Law. 3.5 Personal Data Breach Notification. SAP will notify Customer without undue delay after becoming aware of any Personal Data Breach and provide reasonable information in its possession to assist Customer to meet Customer's obligations to report a Personal Data Breach as required under Data Protection Law. SAP may provide such information in phases as it becomes available. Such notification shall not be interpreted or construed as an admission of fault or liability by SAP. 3.6 Data Protection Impact Assessment. If, pursuant to Data Protection Law, Customer (or its Controllers) are required to perform a data protection impact assessment or prior consultation with a regulator, at Customer's request, SAP will provide such documents as are generally available for the SAP Service (for example, this DPA, the Agreement, audit reports or certifications). Any additional assistance shall be mutually agreed between the Parties. 4. DATA DELETION Customer hereby instructs SAP to delete the Personal Data remaining with SAP (if any) within a reasonable time period in line with Data Protection Law (not to exceed six months) once Personal Data is no longer required for execution of the Agreement, unless applicable law requires retention. 5. CERTIFICATIONS AND AUDITS 5.1 Customer Audit. Customer or its independent third party auditor reasonably acceptable to SAP (which shall not include any third party auditors who are either a competitor of SAP or not suitably Personal Data Processing Agreement for SAP Support and Professional Services enUS.v.11-2018 Page 2 of 11 qualified or independent) may audit SAP's service and support delivery centers and IT security practices relevant to Personal Data processed by SAP only if: (a) SAP has not provided sufficient evidence of its compliance with the technical and organizational measures through providing a certification as to compliance with ISO 27001 or other standards (scope as defined in the certificate). Certifications are available under: https://www.sap.com/corporate/en/company/quality.htmi#certificates or upon request if the certification is not available online; or (b) A Personal Data Breach has occurred; or (c) An audit is formally requested by Customer's data protection authority; or (d) Mandatory Data Protection Law provides Customer with a direct audit right and provided that Customer shall only audit once in any twelve month period unless mandatory Data Protection Law requires more frequent audits. 5.2 Other Controller Audit. Any other Controller may audit SAP's control environment and security practices relevant to Personal Data processed by SAP in line with Section 5.1 only if any of the cases set out in Section 5.1 applies to such other Controller. Such audit must be undertaken through and by Customer as set out in Section 5.1 unless the audit must be undertaken by the other Controller itself under Data Protection Law. If several Controllers whose Personal Data is processed by SAP on the basis of the Agreement require an audit, Customer shall use all reasonable means to combine the audits and to avoid multiple audits. 5.3 Scope of Audit. Customer shall provide at least sixty days advance notice of any audit unless mandatory Data Protection Law or a competent data protection authority requires shorter notice. The frequency, time frame and scope of any audits shall be mutually agreed between the parties acting reasonably and in good faith. Customer audits shall be limited to remote audits where possible. If an on -site audit is mandatory, it shall not exceed one business day. Beyond such restrictions, the parties will use current certifications or other audit reports to avoid or minimize repetitive audits. Customer shall provide the results of any audit to SAP. 5.4 Cost of Audits. Customer shall bear the costs of any audit unless such audit reveals a material breach by SAP of this DPA, then SAP shall bear its own expenses of an audit. If an audit determines that SAP has breached its obligations under the DPA, SAP will promptly remedy the breach at its own cost. 6. SUBPROCESSORS 6.1 Permitted Use. SAP is granted a general authorization to subcontract the processing of Personal Data to Subprocessors, provided that: (a) SAP or SAP SE on its behalf shall engage Subprocessors under a written (including in electronic form) contract consistent with the terms of this DPA in relation to the Subprocessor's processing of Personal Data. SAP shall be liable for any breaches by the Subprocessor in accordance with the terms of the Agreement; (b) SAP will evaluate the security, privacy and confidentiality practices of a Subprocessor prior to selection to establish that it is capable of providing the level of protection of Personal Data required by this DPA; (c) For SAP Support, SAP's list of Subprocessors in place on the effective date of the Agreement is published by SAP (under: https://support.sap.com/en/my-support/subprocessors.htmi) or SAP will make it available to Customer upon request, including the name, address and role of each Subprocessor SAP uses to provide the SAP Service; and (d) For Professional Services, SAP will, upon request of the Customer, make the list available at https://support.sap.com/en/my-support/subprocessors.html or identify such subprocessors prior to the start of the applicable SAP Services. 6.2 New Subprocessors. SAP's use of Subprocessors is at its discretion, provided that: (a) SAP will inform Customer in advance of any intended additions or replacements to the list of Subprocessors including name, address and role of the new Subprocessor (i) for SAP Personal Data Processing Agreement for SAP Support and Professional Services enUS.v.11-2018 Page 3 of 11 Support - by posting on the SAP Support Portal, or by email, upon Customer's registration on the SAP Portal and (ii) for Professional Services - by similar posting on the SAP Support Portal, or by e-mail, or in other written form; (b) Customer may object to such changes as set out in Section 6.3. 6.3 Objections to New Subprocessors. (a) SAP Support: If Customer has a legitimate reason under Data Protection Law to object to the new Subprocessors' processing of Personal Data, Customer may terminate the SAP Support upon written notice to SAP, such notice to be provided to SAP no later than thirty days from the date SAP informs the Customer of the new Subprocessor. If Customer does not provide SAP with a notice of termination within this thirty days period, Customer is deemed to have accepted the new Subprocessor. Within the thirty days period from the date of SAP informing the Customer of the new Subprocessor, Customer may request that the parties come together in good faith to discuss a resolution to the objection. Such discussions shall not extend the period for providing SAP a notice of termination and does not affect SAP's right to use the new Subprocessor(s) after the thirty days period. (b) Professional Services: If Customer has a legitimate reason under Data Protection Law that relates to the Subprocessors' processing of Personal Data, Customer may object to SAP's use of a Subprocessor, by notifying SAP in writing within five business days of SAP's information as per Section 6.2. If Customer objects to the use of the Subprocessor, the parties will come together in good faith to discuss a resolution. SAP may choose to: (i) not use the Subprocessor or (ii) take the corrective steps requested by Customer in its objection and use the Subprocessor. If none of these options are reasonably possible and Customer continues to object for a legitimate reason, either party may terminate the relevant services on five days' written notice. If Customer does not object within five days of receipt of the notice, Customer is deemed to have accepted the Subprocessor. If Customer's objection remains unresolved thirty days after it was raised, and SAP has not received any notice of termination, Customer is deemed to have accepted the Subprocessor. (c) Any termination under this Section 6.3 shall be deemed to be without fault by either party and shall be subject to the terms of the Agreement. 6.4 Emergency Replacement. SAP may replace a Subprocessor without advance notice where the reason for the change is outside of SAP's reasonable control and prompt replacement is required for security or other urgent reasons. In this case, SAP will inform Customer of the replacement Subprocessor as soon as possible following its appointment. Section 6.3 applies accordingly. 7. INTERNATIONAL PROCESSING 7.1 Conditions for International Processing. SAP shall be entitled to process Personal Data, including by using Subprocessors, in accordance with this DPA outside the country in which the Customer is located as permitted under Data Protection Law. 7.2 Standard Contractual Clauses. Where (i) Personal Data of an EEA or Swiss based Controller is processed in a country outside the EEA, Switzerland and any country, organization or territory acknowledged by the European Union as safe country with an adequate level of data protection under Art. 45 GDPR, or where (ii) Personal Data of another Controller is processed internationally and such international processing requires an adequacy means under the laws of the country of the Controller and the required adequacy means can be met by entering into Standard Contractual Clauses, then: (a) SAP and Customer enter into the Standard Contractual Clauses; (b) Customer enters into the Standard Contractual Clauses with each relevant Subprocessor as follows, either (i) Customer joins the Standard Contractual Clauses entered into by SAP or SAP SE and the Subprocessor as an independent owner of rights and obligations ("Accession Model") or, (ii) the Subprocessor (represented by SAP) enters into the Standard Contractual Clauses with Customer ("Power of Attorney Model"). The Power of Attorney Model shall Personal Data Processing Agreement for SAP Support and Professional Services enUS.v.11-2018 Page 4 of 11 apply if and when SAP has expressly confirmed that a Subprocessor is eligible for it through the Subprocessor list provided under Section 6.1(c) or (d), or a notice to Customer; and/or (c) Other Controllers who have been authorized by Customer to include Personal Data under the Agreement may also enter into Standard Contractual Clauses with SAP and/or the relevant Subprocessors in the same manner as Customer in accordance with Sections 7.2 (a) and (b) above. In such case, Customer will enter into the Standard Contractual Clauses on behalf of the other Controllers. 7.3 Relation of the Standard Contractual Clauses to the Agreement. Nothing in the Agreement shall be construed to prevail over any conflicting clause of the Standard Contractual Clauses. For the avoidance of doubt, where this DPA further specifies audit and subprocessor rules in sections 5 and 6, such specifications also apply in relation to the Standard Contractual Clauses. 7.4 Governing Law of the Standard Contractual Clauses. The Standard Contractual Clauses shall be governed by the law of the country in which the relevant Controller is incorporated. S. DOCUMENTATION; RECORDS OF PROCESSING Each party is responsible for its compliance with its documentation requirements, in particular maintaining records of processing where required under Data Protection Law. Each party shall reasonably assist the other party in its documentation requirements, including providing the information the other party needs from it in a manner reasonably requested by the other party (such as using an electronic system), in order to enable the other party to comply with any obligations relating to maintaining records of processing. 9. DEFINITIONS Capitalized terms not defined herein will have the meanings given to them in the Agreement. 9.1 "Authorized Users" means any individual to whom Customer grants access authorization in compliance with a SAP software license to use the SAP Service that is an employee, agent, contractor or representative of (i) the Customer, (ii) Customer's Affiliates, and/or (iii) Customer's and Customer's Affiliates' Business Partners (as defined under the Software License and Support Agreement). 9.2 -Controller- means the natural or legal person, public authority, agency or other body, which alone or jointly with others, determines the purposes and means of the processing of Personal Data; for the purposes of this DPA, where Customer acts as Processor for another Controller, it shall in relation to SAP be deemed as additional and independent Controller with the respective controller rights and obligations under this DPA. 9.3 -Data Protection Law" means the applicable legislation protecting the fundamental rights and freedoms of persons and their right to privacy with regard to the processing of Personal Data under the Agreement (and includes, as far as it concerns the relationship between the parties regarding the processing of Personal Data by SAP on behalf of Customer, the GDPR as a minimum standard, irrespective of whether the Personal Data is subject to GDPR or not). 9.4 -Data Subject" means an identified or identifiable natural person as defined by Data Protection Law. 9.5 -Personal Data" means any information relating to a Data Subject which is protected under Data Protection Law. For the purposes of the DPA, it includes only personal data which is supplied to or accessed by SAP or its Subprocessors in order to provide the SAP Service under the Agreement. 9.6 -Personal Data Breach" means a confirmed (1) accidental or unlawful destruction, loss, alteration, unauthorized disclosure of or unauthorized third -party access to Personal Data or (2) Personal Data Processing Agreement for SAP Support and Professional Services enUS.v.11-2018 Page 5 of 11 similar incident involving Personal Data, in each case for which a Controller is required under Data Protection Law to provide notice to competent data protection authorities or Data Subjects. 9.7 -Professional Services" means implementation services, consulting services and/or services such as SAP Premium Engagement Support Services, Innovative Business Solutions Development Services, Innovative Business Solutions Development Support Services. 9.8 -Processor- means a natural or legal person, public authority, agency or other body which processes Personal Data on behalf of the Controller, be it directly as Processor of a Controller or indirectly as Subprocessor of a Processor which processes Personal Data on behalf of the Controller. 9.9 -Standard Contractual Clauses" or sometimes also referred to the "EU Model Clauses" means the (Standard Contractual Clauses (processors)) or any subsequent version thereof published by the European Commission (which will automatically apply). 9.10-Subprocessor" means SAP Affiliates, SAP SE, SAP SE Affiliates and third parties engaged by SAP , SAP SE or SAP SE's Affiliates in connection with the SAP Service and which processes Personal Data in accordance with this DPA. Personal Data Processing Agreement for SAP Support and Professional Services enUS.v.11-2018 Page 6 of 11 Appendix 1 to the DPA and, if applicable, the Standard Contractual Clauses Data Exporter The Data Exporter is the Customer who concluded a Software License and Support Agreement and/or Services Agreement with SAP under which it benefits from SAP Service as described under the relevant Agreement. The Data Exporter allows other Controllers to also use the SAP Service, these other Controllers are also Data Exporters. Data Importer SAP and its Subprocessors provide the SAP Service as defined under the relevant Agreement concluded by the Data Exporter that includes the following SAP Service: - Under the Software License and Support Agreement: SAP and/or its Subprocessors provide support when a Customer submits a support ticket because the Software is not available or not working as expected. They answer phone calls and perform basic troubleshooting, and handles support tickets in a tracking system - under the applicable Services Agreement for Professional Services: SAP and/or its Subprocessors provide Services subject to the Order Form Services and the applicable Scope Document. Data Subjects Unless provided otherwise by the Data Exporter, transferred Personal Data relates to the following categories of Data Subjects: employees, contractors, Business Partners or other individuals having Personal Data transmitted to, made available or accessed by the Data Importer. Data Categories The transferred Personal Data concerns the following categories of data: Customer determines the categories of data and/or data fields which could be transferred per SAP Service as stated in the relevant Agreement. The transferred Personal Data typically relates to the following categories of data: name, phone numbers, e-mail address, time zone, address data, system access / usage / authorization data, company name, contract data, invoice data, plus any application -specific data transferred by Authorized Users and may include financial data such as bank account data, credit or debit card data. Special Data Categories (if appropriate) The transferred Personal Data concerns the following special categories of data: As set out in the Agreement (including the Order Form), if any. Processing Operations / Purposes The transferred Personal Data is subject to the basic processing activities as set out in the Agreement which may include: • use of Personal Data to provide the SAP Service • storage of Personal Data • computer processing of Personal Data for data transmission • execution of instructions of Customer in accordance with the Agreement. Personal Data Processing Agreement for SAP Support and Professional Services en US.v.11-2018 Page 7 of 11 Appendix 2 to the DPA and, if applicable, the Standard Contractual Clauses — Technical and Organizational Measures 1. TECHNICAL AND ORGANIZATIONAL MEASURES The following sections define SAP's current technical and organizational measures. SAP may change these at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data. 1.1 Physical Access Control. Unauthorized persons are prevented from gaining physical access to premises, buildings or rooms where data processing systems that process and/or use Personal Data are located. Measures: • SAP protects its assets and facilities using the appropriate means based on the SAP Security Policy • In general, buildings are secured through access control systems (e.g., smart card access system). • As a minimum requirement, the outermost entrance points of the building must be fitted with a certified key system including modern, active key management. • Depending on the security classification, buildings, individual areas and surrounding premises may be further protected by additional measures. These include specific access profiles, video surveillance, intruder alarm systems and biometric access control systems. • Access rights are granted to authorized persons on an individual basis according to the System and Data Access Control measures (see Section 1.2 and 1.3 below). This also applies to visitor access. Guests and visitors to SAP buildings must register their names at reception and must be accompanied by authorized SAP personnel. • SAP employees and external personnel must wear their ID cards at all SAP locations. Additional measures for Data Centers: • All Data Centers adhere to strict security procedures enforced by guards, surveillance cameras, motion detectors, access control mechanisms and other measures to prevent equipment and Data Center facilities from being compromised. Only authorized representatives have access to systems and infrastructure within the Data Center facilities. To protect proper functionality, physical security equipment (e.g., motion sensors, cameras, etc.) undergo maintenance on a regular basis. • SAP and all third -party Data Center providers log the names and times of authorized personnel entering SAP's private areas within the Data Centers. 1.2 System Access Control. Data processing systems used to provide the SAP Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP's systems with a unique identifier (user ID). • SAP has procedures in place to so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password -protected screensaver. Personal Data Processing Agreement for SAP Support and Professional Services enUS.v.11-2018 Page 8 of 11 • The company network is protected from the public network by firewalls. • SAP uses up-to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP's corporate network and critical infrastructure is protected by strong authentication. 1.3 Data Access Control. Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage. Measures: • As part of the SAP Security Policy, Personal Data requires at least the same protection level as 11confidential" information according to the SAP Information Classification standard. • Access to Personal Data is granted on a need -to -know basis. Personnel have access to the information that they require in order to fulfill their duty. SAP uses authorization concepts that document grant processes and assigned roles per account (user ID). All Customer Data is protected in accordance with the SAP Security Policy. • All production servers are operated in the Data Centers or in secure server rooms. Security measures that protect applications processing Personal Data are regularly checked. To this end, SAP conducts internal and external security checks and penetration tests on its IT systems. • SAP does not allow the installation of software that has not been approved by SAP. • An SAP security standard governs how data and data carriers are deleted or destroyed once they are no longer required. 1.4 Data Transmission Control. Except as necessary for the provision of the SAP Services in accordance with the relevant Agreement, Personal Data must not be read, copied, modified or removed without authorization during transfer. Where data carriers are physically transported, adequate measures are implemented at SAP to provide the agreed -upon service levels (for example, encryption and lead -lined containers). Measures: • Personal Data in transfer over SAP internal networks is protected according to SAP Security Policy. • When data is transferred between SAP and its customers, the protection measures required for data transfer are hereby mutually agreed upon between SAP and its customer and included as a part of the Agreement. This applies to both physical and network based data transfer. In any case, the Customer assumes responsibility for any data transfer once it is outside of SAP -controlled systems (e.g. data being transmitted outside the firewall of the SAP Data Center). 1.5 Data Input Control. It will be possible to retrospectively examine and establish whether and by whom Personal Data have been entered, modified or removed from SAP data processing systems. Measures: • SAP only allows authorized personnel to access Personal Data as required in the course of their duty. • SAP has implemented a logging system for input, modification and deletion, or blocking of Personal Data by SAP or its subprocessors within the SAP Service to the extent technically possible. 1.6 Job Control. Job Control is required to ensure that personal data processed on behalf of others are processed strictly in compliance with the Customer's instructions Measures: SAP uses controls and processes to monitor compliance with contracts between SAP and its customers, subprocessors or other service providers. Personal Data Processing Agreement for SAP Support and Professional Services enUS.v.11-2018 Page 9 of 11 As part of the SAP Security Policy, Personal Data requires at least the same protection level as 11confidential" information according to the SAP Information Classification standard. • All SAP employees and contractual subprocessors or other service providers are contractually bound to respect the confidentiality of all sensitive information including trade secrets of SAP customers and partners. For SAP Support, SAP customers have control over their remote support connections at all times. SAP employees cannot access a customer system without the knowledge and consent of the customer. For SAP Support, SAP provides a specially designated, secure support ticket facility in which SAP provides a special access -controlled and monitored security area for transferring access data and passwords. SAP customers have control over their remote support connections at all times. SAP employees cannot access a customer on premise system without the knowledge and active participation of the customer. 1.7 Availability Control. Personal Data will be protected against accidental or unauthorized destruction or loss. Measures: • SAP employs regular backup processes to provide restoration of business -critical systems as and when necessary. • SAP uses uninterrupted power supplies (for example: UPS, batteries, generators, etc.) to protect power availability to the Data Centers. • SAP has defined business continuity plans for business -critical processes; • Emergency processes and systems are regularly tested. 1.8 Data Separation Control. Personal Data collected for different purposes can be processed separately. Measures: • SAP uses appropriate technical controls to achieve Customer Data separation at all times. • Customer (including its approved Controllers) will have access only to their own Data based on secure authentication and authorization. • If Personal Data is required to handle a support incident from Customer, the data is assigned to that particular message and used only to process that message; it is not accessed to process any other messages. This data is stored in dedicated support systems. 1.9 Data Integrity Control. Personal Data will remain intact, complete and current during processing activities. Measures: SAP has implemented a multi -layered defense strategy as a protection against unauthorized modifications. In particular, SAP uses the following to implement the control and measure sections described above. In particular: • Firewalls; • Security Monitoring Center; • Antivirus software; • Backup and recovery; • External and internal penetration testing; • Regular external audits to prove security measures. Personal Data Processing Agreement for SAP Support and Professional Services enUS.v.11-2018 Page 10 of 11 Appendix 3 to the DPA The following table sets out the relevant Articles of GDPR and corresponding terms of the DPA for illustration purposes only. Article of GDPR Section of DPA Click on link to see Section 28(1) 2 and Appendix 2 Security of Processing and Appendix 2, Technical and Organizational Measures. 28(2), 28(3) (d) and 28 (4) 6 SUBPROCESSORS 28 (3) sentence 1 1.1 and Appendix 1, 1.2 Purpose and Application. Structure. 28(3) (a) and 29 3.1 and 3.2 Instructions from Customer. Processing on Legal Requirement. 28(3) (b) 3.3 Personnel. 28(3) (c) and 32 2 and Appendix 2 Security of Processing and Appendix 2, Technical and Organizational Measures. 28(3) (e) 3.4 Cooperation. 28(3) (f) and 32- 36 2 and Appendix 2, 3.5, 3.6 Security of Processing and Appendix 2, Technical and Organizational Measures. 28(3) (g) 4 Data Deletion 28(3) (h) 5 CERTIFICATIONS AND AUDITS 28 (4) 6 SUBPROCESSORS 30 8 Documentation; Records of processing 46(2) (c) 7.2 Standard Contractual Clauses. Personal Data Processing Agreement for SAP Support and Professional Services en US.v.11-2018 Page 11 of 11 HEXAGON City of Miami Police & Fire Departments Statement of Work for HxGN OnCall Dispatch Cloud Hosted CAD/Mobile Implementation PRESENTED BY: Trent Lowe Regional Sales Manager Hexagon Safety & Infrastructure 305 Intergraph Way Madison, AL 35758 USA Phone: 772-559-6489 Email: trent.lowe@hexagonsi.com January 19, 2022 HEXAGON TABLE OF CONTENTS 1. Introduction..................................................................................................................................... 4 2. Purpose........................................................................................................................................... 4 3. Project Outline................................................................................................................................ 5 4. Cloud Program Functionality & Support..................................................................................... 5 5. Customer Project Team Structure................................................................................................5 Core Team Roles and Responsibilities............................................................................................ 5 6. Project Assumptions..................................................................................................................... 7 7. Project Tasks................................................................................................................................10 ProjectInitiation.............................................................................................................................. 10 Initial Operating Capability (IOC) Phase........................................................................................ 11 1. Project Kickoff Meeting.......................................................................................... 11 2. COTS Interface Questionnaire Completion........................................................... 13 3. OnCall Dispatch and Mobile Unit Launch.............................................................. 15 4. OnCall Dispatch Map Overview............................................................................. 17 5. Creation of Cloud Environment............................................................................. 18 6. IOC Completion..................................................................................................... 19 Final Operating Capability (FOC) Phase........................................................................................ 21 7. CAD System Build 1.............................................................................................. 21 8. CAD System Build 2.............................................................................................. 23 9. CAD System Build 3.............................................................................................. 25 10. Custom Interface Requirements Gathering.........................................................26 11. Custom Interface Development...........................................................................28 12. Connectivity to Cloud Program............................................................................ 29 13. On Premise Local Software Server Installation and Configuration ..................... 30 14. OnCall Map Service Configuration and Consulting Services .............................. 32 15. Informer Setup(CommSys)................................................................................. 33 16. OnCall Dispatch Police Configuration Consulting Session ................................. 35 17. OnCall Dispatch Fire Configuration Consulting Session ..................................... 37 18. OnCall Dispatch Configuration Follow-up Workshop .......................................... 39 19. Customer Rules Engine Configuration Workshop...........................................40 20. OnCall Dispatch Mobile Unit Police Configuration Consulting Session ............42 21. OnCall Dispatch Mobile Unit Fire Configuration Consulting Session................44 22. OnCall Dispatch Mobile Responder Police Consulting Session .......................... 46 1 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 23. OnCall Dispatch Mobile Responder Fire Consulting Session ............................. 47 24. COTS Interface Product Installation and Configuration......................................48 25. Custom Interface Product Installation and Configuration....................................49 26. Standard Interface Product Installation and Configuration..................................50 27. Develop Test Plan and Test Cases..................................................................... 51 28. Customer Functional Testing...............................................................................52 29. Hexagon -Led Training......................................................................................... 54 30. Replicate Cloud Environments............................................................................ 56 31. Cloud Cutover Plan.............................................................................................. 57 32. Cloud Program Readiness Review......................................................................58 33. Cloud Cutover to Production Use........................................................................ 59 34. Post-Cutover Support.......................................................................................... 60 Termsand Conditions.............................................................................................................................. 62 ApprovalSignatures.................................................................................................................................63 Attachment A — Pricing Summary ...........................................................................................................64 Attachment B — Payment Schedule......................................................................................................... 68 Attachment C — Initial Project Schedule................................................................................................. 69 Attachment D — Training Curriculum...................................................................................................... 75 HxGN OnCall Dispatch Advantage System Administrator Training (Qty: 1)...75 HxGN OnCall Dispatch Advantage Train -the -Trainer (Qty: 4)........................... 76 2 for Police, 2 for Fire.............................................................................................. 76 HxGN OnCall Dispatch I Viewer Train -the -Trainer (Qty: 4).................................. 77 2 for Police, 2 for Fire.............................................................................................. 77 HxGN OnCall Dispatch I Mobile Unit Train -the -Trainer (Qty: 4)..........................78 2 for Police, 2 for Fire.............................................................................................. 78 Mobile Responder Train -the -Trainer (Qty: 4)........................................................ 79 HxGN OnCall Analytics Dispatch User Training (Qty: 1)................................... 80 HxGN OnCall Analytics Dispatch System Administrator Training (Qty: 1) ..... 81 Attachment E — OnCall Dispatch Cloud Specifications........................................................................ 82 Attachment F — System Configuration Diagram.................................................................................... 83 Attachment G — CAD/Mobile Functional Specifications Matrix............................................................ 84 Attachment H — Interface Descriptions................................................................................................... 85 COTSInterfaces.............................................................................................................................85 HxGN Dispatch I CAD Link........................................................................................85 HxGN OnCall Dispatch Fire Station Alerting........................................................... 85 HxGN OnCall Dispatch Deccan LiveMUM..............................................................86 Statement of Work 2 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation HxGNDispatch Informer..........................................................................................87 HxGN Dispatch Tracker to Radio............................................................................ 89 HxGN OnCall Dispatch I ProQA................................................................................ 90 HxGN Connect Video I Streamer............................................................................... 91 HxGN Interface I Milestone VMS............................................................................... 92 StandardInterfaces........................................................................................................................93 ASAP (External Alarms OnCall Dispatch Interface)..................................................93 Shotspotter (External Alarms OnCall Dispatch Interface) ......................................... 93 Harris Radio (PLT Radio OnCall Dispatch Interface) ................................................ 94 WebEOCInterface.....................................................................................................94 Everbridge (Dispatch Alerts OnCall Interface)...........................................................95 RapidSOS OnCall Call -Taker Interface.....................................................................95 ConsultingServices........................................................................................................................ 95 ALPR.......................................................................................................................... 95 CustomInterfaces.......................................................................................................................... 96 MotorolaRMS Query................................................................................................. 96 Traffic Management System(Opticom).....................................................................97 Telestaff..................................................................................................................... 97 Hydrant...................................................................................................................... 98 Attachment I — CJIS Security Addendum............................................................................................... 99 Attachment J — Glossary of Terms........................................................................................................101 Attachment K — Azure Maps Overview.................................................................................................104 What is the Mapping Technology within the HxGN OnCall System? ........................................... 104 AzureMaps.................................................................................................................................. 105 RenderService........................................................................................................ 106 RouteService.......................................................................................................... 106 GeoCodingService.................................................................................................. 107 HighAvailability............................................................................................................................ 107 AttachmentL — REMOVED.....................................................................................................................108 Attachment M — Cloud Service Schedules...........................................................................................109 Attachment N — Deccan LiveMUM SOW...............................................................................................110 Statement of Work 3 4 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 1. Introduction This Statement of Work together with the attached Quote is part of the Cloud Consulting Services Order and made pursuant to the Master Terms identified in the Quote between the City of Miami acting on behalf of its Police and Fire Departments ("Customer") and Intergraph Corporation by and through its Hexagon Safety & Infrastructure division (`Hexagon"). This SOW describes the Cloud Consulting Services provided by Hexagon in connection with the initial implementation of the Dispatch Cloud Program. Hexagon will provide the Cloud Consulting Services to facilitate implementation of the Dispatch Cloud Program as expressly set forth in this SOW (the "Project"). Unless otherwise defined in this SOW capitalized terms shall have the same meaning as set forth in the Master Terms and Attachment J (Glossary) attached hereto. Execution of this SOW reflects the Customer's acceptance of the Orders, including this SOW. The SOW describes the Cloud Consulting Services for the Dispatch Cloud Program. It documents: Project implementation requirements, Cloud Application and Local Software functionality, the Activities and Tasks comprising the Project, the timeframe for completion of Activities and Tasks, the responsibilities for each Party, and the Task Acceptance Criteria. The SOW includes and incorporates the following Attachments: Attachment A — Pricing Summary Attachment B — Payment Schedule Attachment C — Initial Project Schedule * Attachment D — Training Curriculum • Attachment E — OnCall Dispatch Cloud Specifications • Attachment F — System Configuration Diagram • Attachment G — CAD/Mobile Functional Specifications Matrix • Attachment H — Interface Descriptions • Attachment I — CJIS Security Addendum Attachment J — Glossary of Terms Attachment K — Azure Maps Overview * Attachment L — REMOVED • Attachment M — Cloud Service Schedules • Attachment N — Deccan LiveMUM SOW Each Task identified in the SOW includes the following as necessary: Task Description, Task Deliverables, Task Prerequisites, Task Assumptions, Hexagon/Customer Team Participation and Responsibilities, and Task Acceptance Criteria. The Tasks defined in the SOW may not be listed chronologically, and the actual Project implementation Tasks and timelines will follow the Final Project Schedule, unless otherwise noted. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 3. Project Outline The Project consists of two (2) phases: Initial Operating Capability ("IOC') and Final Operating Capability ("FOC"). During IOC, Hexagon will create the cloud environment and conduct the first data build workshop. For the Project to be successful, it is imperative the Customer timely perform its Activities. Upon IOC completion, the Dispatch Cloud Program is in a state that it can be used to perform its primary function: dispatch emergency resources in accordance with the Specifications. IOC Completion also marks the Cloud Program Start Date for the Dispatch Cloud Program. Following the completion of IOC, the additional data build workshops, additional configuration, interface development and implementation, functional testing of the Cloud Applications in accordance with the Benchmark Criteria ("Functional Testing"), training, and deployment Activities can occur. As part of FOC, Hexagon shall provide services to support Customer Activities as expressly described in this SOW, develop and implement identified Interfaces, perform Hexagon -led training, provide a draft Cutover plan, and provide support to the Customer during Cloud Cutover. 4. Cloud Program Functionality & Support As part of the Cloud Program, Hexagon shall provide Credentials/License Keys to the COTS Cloud Applications identified in the Quote. The Dispatch Cloud Program shall have the capabilities and functionality set forth in the Specifications, which reflects all of the functionality Hexagon is obligated to provide in the Dispatch Cloud Program. User Acceptance Testing shall only test for conformance to the Specifications. Errors identified during testing are addressed in accordance with the terms related to Cloud Services Support. Only Blocker Errors are required to be resolved prior to Cloud Cutover. This scope does not include any Product Change Requests. As part of the Dispatch Cloud Program, the Customer will have access to various Cloud Environments: Production, Development, Staging, and Training. This Project contemplates most Activities occurring in the Development Environment. After the Dispatch Cloud Program has completed Functional Testing and prior to Cloud Cutover, Hexagon will replicate the Development Environment to the Production Environment, Staging Environment, and Training Environment. Upon issuance of the Credentials/License Keys for the Dispatch Cloud Program, the Cloud Program Start Date shall have occurred. Consequently, Cloud Services Support will also begin at that time. The Customer is responsible for performing its Cloud Services Support obligations as reflected in the Master Terms for the duration of FOC and the remainder of the Cloud Term, as may be extended. 5. Customer Project Team Structure The Customer shall provide qualified resources to staff the Core Team (described below) to facilitate a successful implementation of OnCall Dispatch and Analytics. The Core Team roles and responsibilities are described in the following sections. Core Team Roles and Responsibilities The Core Team (as described below) shall consist of designated agency (Customer) personnel with the various skill sets and knowledge and backgrounds required to implement OnCall Dispatch, including, OnCall Mobile Unit, and OnCall Analytics. The following list identifies the required Core Team and its respective roles and corresponding responsibilities: Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Project Manager — responsible for the day-to-day coordination of Project activities with the Core Team and with Hexagon • System Administrator Personnel — responsible for all system administration and configuration responsibilities related to the new System, all System interfaces, and the mobile Subsystem • GIS Administrator — responsible for providing Hexagon Map Lead with source GIS data as documented in the GIS Requirements (Attachment K) during the Project Training Personnel — responsible for training other agency personnel Subject Matter Experts (e.g., dispatchers, call takers, supervisory personnel) — responsible for representing end -users' needs • Departmental Sponsors — responsible for making decisions on recommended business process changes and other related items Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 6. Project Assumptions The following list of assumptions and Customer responsibilities reflect Hexagon's understanding of the Project. Changes in any of the assumptions and Customer responsibilities will affect the scope, Project Schedule, and/or cost of the Project. Agreement and Schedule Assumptions This Cloud Consulting Services Order and the Cloud Program Order have been executed by the Customer, accepted by Hexagon, and the Customer has provided a notice to proceed, Purchase Orders (PO) for both Orders, or written confirmation only the execution of the Orders is necessary to bind the Customer. Hexagon and the Customer will review the SOW and determine a mutually agreeable date for the Services to be performed The Customer shall perform its assigned responsibilities as identified within the Initial Project Schedule (Attachment C) and Project Schedule developed as part of Task 1 in the time allotted. If the Customer does not reasonably comply with the Project Schedule, Hexagon is permitted with written notice to suspend its performance on this Project and redeploy its resources on other active projects until the parties determine a mutually agreed upon date to re -start the Project. At that time, a new Project Schedule will be provided Hexagon will have timely access to the Core Team and other Customer Project staff in accordance with the Project Schedule. Customer shall make additional personnel available on a priority basis, as needed, to provide subject matter expertise to complete this Project Customer shall assign personnel to the Core Team and ensure they are actively engaged in the Project. Customer shall provide Hexagon Project Manager with contact information for a Customer resource to resolve any issues that should arise from Hexagon's access of Customer's System during working and non -working hours The Customer shall provide Hexagon with access to all data, documents, plans, reports, diagrams, and analyses related to the scope of work and responsibilities of this Project Unless expressly stated in this SOW, all Documentation, if any, provided by Hexagon under this SOW will be COTS Documentation, and the Documentation will not be customized. All Documentation delivered will be in Hexagon -approved format. Changes to Hexagon -format to accommodate specific Customer requests may be done at Hexagon's discretion and at an additional cost Unless Hexagon and Customer mutually agree otherwise, all Documentation provided by Hexagon will only be provided in electronic format All Hexagon personnel performing remote tasks will be identified and properly vetted prior to commencement of those remote Activities Notwithstanding anything to the contrary within the Master Terms, the Customer shall substantively respond to the delivery of a sign -off form within five (5) Business Days as part of the Task Acceptance Process Historical data conversion or importation is not included in this Project For meeting or workshops involving both the Customer and Hexagon there will be at least a fifteen (15) minute break every two (2) hours with a one (1) hour lunch break for meetings scheduled to last an entire day (eight (8) hours) Statement of Work % r HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Hardware and Software Assumptions • All Software will be electronically delivered Local Software, if any, will be electronically delivered to the Local Environment The Customer shall provide access to its Local Environment to Hexagon for the duration of the Project. No Local Software will be delivered during the IOC Phase. The Customer shall purchase, install, and test all physical client hardware comprising the Local Environment. The Customer will ensure its hardware, operating system software, and other third -party products/environments conform with Attachment E: OnCall Dispatch Specifications and Attachment F: System Configuration Diagram Hexagon and the Customer will test the final system hardware configuration to ensure conformance with Attachment F: System Configuration Diagram and Attachment E: OnCall Dispatch Specifications Customer shall purchase all applicable operating systems and software in the Local Environment, including, but not limited to, client workstations, and ensure such operating systems and software meet the minimum requirements as defined in Attachment E Cloud Application System Requirements Customer shall be responsible for the wired and wireless connectivity between servers/clients and clients/clients and with the Cloud Applications Except as specified in this Order, including Attachment A: Pricing Summary, Hexagon is not required to provide any additional software customizations, custom forms, forms modifications, third -party software, custom interfaces, or custom reports To the extent the Customer desires to use the Dispatch Cloud Program or other deliverables provided herein in a manner or in combination with software or hardware that is not certified or recommended by Hexagon, then the Customer shall be solely responsible for such use. Hexagon shall not be responsible for the correction of any Errors, reduced performance, compromised functionality, or other unintended consequences arising from such use. The Customer also shall not withhold acceptance of any Task or the Cloud Program due to such use System Access/CJIS Assumptions The Cloud Program shall store data (in either transit or at rest) in the Cloud Environment, which is within Microsoft Azure Government Cloud. Customer is solely responsible for (i) assuring it is permitted by appropriate State agencies to transmit CJI and store data (in either transit or at rest) in the Cloud Environment and (ii) otherwise complying with and ensuring this Project and the Cloud Program to be provided does not violate applicable State CJIS policies Through inclusion of Attachment D -- CJIS Security Addendum, Hexagon acknowledges and agrees to comply with its limited obligations applicable to a software vendor provided under CJIS Customer shall purchase, install, configure, and administer its Network Infrastructure, including, but not limited to, its WAN/LAN and wireless infrastructure. Customer's wireless infrastructure shall be the same for all agencies Upon Customer request, Hexagon personnel may undergo a criminal background check consisting of biographical information necessary to initiate an NCIC query and fingerprinting. To the extent the Customer requires Hexagon personnel to undergo such criminal background check, the Customer shall arrange for such criminal background check and fingerprinting and be Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation responsible for all costs associated with the criminal background check and fingerprinting. Any remote personnel shall only be required to provide biographical information necessary to initiate a NCIC query and a fingerprint card completed by any law enforcement agency Customer consents to Hexagon's inspection and use of Customer's data and systems, including, but not limited to, log files and databases, for the limited purpose of providing the Cloud Services and Cloud Consulting Services. SecureLink is the remote access solution used by Hexagon. If Customer desires for Hexagon to utilize an alternate method and/or process for remotely working on the Cloud Program, such alternate method and/or process shall be mutually agreed upon prior to this SOW being executed. Such alternate method and/or process may impact the original level of effort and Project Schedule quoted for this upgrade, which in turn may require a Change Order to modify Customer shall provide unrestricted system and VPN access via SecureLink to Hexagon developers and implementers who will need to have access to multiple infrastructure platforms at the same time. The Customer shall provide Hexagon personnel individualized system access credentials and allow Hexagon authorized resources VPN access twenty-four (24) hours a day, seven (7) days a week for the duration of the Project Customer shall provide external VPN access while on -site to access various Hexagon resource libraries After completion of this Project, Hexagon will VPN using SecureLink into the live System only at Customer's request and will follow Customer's required VPN access procedures Third -Party Assumptions • Customer shall schedule and coordinate third -party technical resources with the skills necessary to perform and/or support all Customer Responsibilities, respond to Hexagon requests, and support the testing of interfaces, as required. Customer shall schedule and coordinate third -party technical resources in such a way as to ensure that a negative impact to the overall Project Schedule does not occur Customer shall maintain, in good working order, all third -party systems which will integrate with Hexagon software or on which the Hexagon software depends as part of this Project except for the Third -Party Software included as part of the Cloud Program and provided thereunder Customer shall be responsible for the operation and timely availability of external systems or third - party software necessary for the execution of the Project • If a delay in the Project is caused by a third -party vendor, Hexagon services not covered in this SOW may be required at additional costs • Customer may use any supported third -party mapping provider for GIS information within the Dispatch Cloud Program during this Project (see Attachment K). It is the Customer's responsibility to provide this. Alternatively, the Customer can use the default map, which is Azure Maps. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 7. Project Tasks Project Initiation Prior to the Kick-off Meeting and after execution of this Order, the Hexagon Project Manager will contact the Customer Project Manager to identify the Project Start date and coordinate scheduling the Kickoff Meeting. For the Project to be successful, the following initial Activities must be performed before any Tasks can occur: The Hexagon Project Manager will contact the Customer Project Manager. During this initial contact, the Hexagon Project Manager will: Schedule the Kickoff Meeting Identify the Project Start date Create a detailed agenda describing the goals of the kickoff meeting Discuss any mitigating factors that could affect the Project (e.g., scheduling conflicts, communication factors, and other risk factors) Schedule a conference call before the kickoff to go over the kickoff agenda Ensure both Hexagon and Customer have appropriate Subject Matter Experts available for kickoff • Hexagon's Project Manager will prepare kickoff materials • Hexagon's Project Manager shall have updated the Initial Project Schedule and provide the draft Updated Initial Project Schedule and sent a copy to the Customer Project Manager for review prior to the Kickoff Meeting Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Initial Operating Capability (IOC) Phase 1. Project Kickoff Meeting Task Description The objective of this Task is to discuss and address questions regarding Project Assumptions, discuss the updated Initial Project Schedule and agree to it at the meeting or shortly thereafter, and all requirements are understood prior to beginning any significant work. A meeting for Project Kickoff will be held at Customer's facility after the SOW has been fully executed. The Project Kickoff meeting will be scheduled by each party's Project Manager as part of Project Initiation Activities. Prior to the Kickoff Meeting and after written acceptance of the Cloud Program Order and this Cloud Consulting Services Order, the Hexagon Project Manager will contact the Customer Project Manager to identify the Project Start date and coordinate scheduling the Kickoff Meeting. The Project Kickoff Meeting will be conducted on site and shall last no more than eight (8) hours. During this Task, the Parties shall confirm the updated Initial Project Schedule as updated by the Hexagon Project Manager. The resulting updated Initial Project Schedule shall be substantially similar in durations as provided within Attachment C. Prior to the Project Kickoff Meeting Task, the Customer Project Manager shall have reviewed the updated Initial Project Schedule and be in a position to succinctly identify any needed changes understanding material extensions of the Initial Project Schedule may require additional Hexagon Services to be added via a Change Order. Once the list of changes has been made to the updated Initial Project Schedule by the Hexagon Project Manager, the Hexagon Project Manager will thereafter provide the Project Schedule to the Customer Project Manager. From time to time, the Parties' Project Managers may modify the Project Schedule upon mutual written consent or upon transmission of an updated Project Schedule to the Customer Project Manager as part of a status report and the Customer Project Manager offers no objection to the updated Project Schedule within five (5) Business Days thereafter. At the Project Kickoff Meeting, the Customer shall provide: (i) contact information for all members of its Core Team and Executive/Departmental Sponsor, (ii) proposed alterations to the updated Initial Project Schedule, (iii) contact information for any third party vendors which the Cloud Program will integrate as contemplated in Attachment H, and (iv) identify to Hexagon any perceived concerns or risks with the Project. Task Deliverables Kickoff meeting agenda Project Schedule Project Risk Register template Kickoff meeting minutes, to include identified risks and action items COTS Interface Questionnaire Task Prerequisites The Cloud Consulting Services Order and Cloud Program Order have been accepted in writing by the Customer and the Customer has issued to Hexagon Purchase Orders for the full amount reflected in both Quotes (or the Customer has indicated in writing it does not need to issue Purchase Orders to facilitate transactions of this type) Hexagon Project Manager has verbally communicated with the Customer to (i) identify the Project Start date and (ii) coordinate a date for the Project Kickoff Meeting Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Customer has assigned a Customer Project Manager Customer's Core Team has reviewed this SOW Customer is in compliance with Attachment K - GIS Requirements Task Assumptions The Hexagon Project Manager will conduct the kickoff meeting at Customer's site c Some members of the Hexagon Project Team may participate remotely Hexagon Team Participation and Responsibilities Hexagon shall: Review the Project organization, roles, and responsibilities with the Customer Conduct an overview of the Project including a review of the SOW to verify all aspects of the Project approach Review the draft Updated Initial Project Schedule and adjust the Updated Initial Project Schedule as needed and mutually -agreed upon with Customer Work with Customer to identify and document any potential Project risks Provide meeting minutes that document risks and action items that affect the Project Schedule, resources, and/or the SOW Inform the Customer of VPN requirements for Project implementation and continued System maintenance for any Local Software server access Review of delivery methodology Establish status reporting requirements Customer Team Participation and Responsibilities Customer shall: • Review the SOW • Provide location and logistical support for Kickoff Meeting Ensure its Core Team attends the applicable portions of the Kickoff Meeting Provide SMEs and any other resources as recommended by the Customer and Hexagon Project Managers • Provide Hexagon with VPN access and individualized user accounts to Customer's System as appropriate for this Project and continued software maintenance for Local Software server access • Designate and prepare workspace for Hexagon personnel • Have previously reviewed the Updated Initial Project Schedule and work with Hexagon to finalize the Updated Initial Project Schedule Task Acceptance Criteria This Task is complete at the conclusion of the Project Kickoff Meeting and delivery of the Project Schedule to Customer. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 2. COTS Interface Questionnaire Completion Task Description For each COTS Interface, Hexagon will provide an interface questionnaire ("COTS Interface Questionnaire"). The Customer shall complete the COTS Interface Questionnaire within five (5) business days of receipt whereupon Hexagon will be able to install the COTS Interface and configure it based upon the information provided in the COTS Interface Questionnaire subject to the functionality and features within the COTS Interface. The following Interfaces are regarded as the COTS Interfaces (collectively, "COTS Interfaces"): 0 HxGN Dispatch CAD Link • HxGN Dispatch Fire Station Alerting e HxGN Dispatch Deccan LiveMUM • HxGN Dispatch Informer • HxGN Dispatch I Tracker • HxGN Dispatch I ProQA • HxGN Connect Video I Streamer • HxGN Interface I Milestone VMS For more information on, parameters of, and assumptions underlying the COTS Interfaces, see Attachment H, Interface Descriptions. Task Deliverables Completed COTS Interface Questionnaires Task Prerequisites Project Kickoff Meeting Task Assumptions This Task will be conducted remotely The Customer will direct its third -party vendors to provide any API or specification documentation required to configure the COTS Interfaces If required, all NDAs between Hexagon and third parties will be executed and current. The Customer will exercise all reasonable efforts to facilitate its third -party vendors reasonable cooperation with this requirement The Customer exercise all reasonable efforts to facilitate cooperation and information from its third -party vendors and/or state agency as reasonably necessary for the configuration, testing, and Cutover of the COTS Interfaces The Customer shall be responsible for underlying requirements pertaining to its third party systems as described in Attachment H Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Hexagon Team Participation and Responsibilities Hexagon shall: • Submit COTS Interface Questionnaires to Customer • Review completed interface questionnaires Customer Team Participation and Responsibilities Customer shall: ® Promptly review and submit all COTS Interface Questionnaires and provide comments, questions, or approval within five (5) business days of receipt Task Acceptance Criteria This Task is considered complete upon submission of all COTS Interface Questionnaires and final approval of the COTS Interface Questionnaires by both Hexagon and the Customer. Statement of Work 14 0*4 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 3. OnCall Dispatch and Mobile Unit Launch Task Description During this Task, Hexagon resources will teach the Customer the features and functions of a COTS OnCall system that apply to static data collection tasks that precede the System Build 1, 2, and 3 sessions. Included in this Task is up to twenty-four (24)-hours of on -site instruction for OnCall Dispatch and up to eight (8)-hours of on -site instruction for Mobile Unit/Mobile Responder. In the System Build 1, 2, and 3 sessions to be conducted later in the Project, the Customer will be exposed to the administrative tools used to create, modify, and remove various static data elements from the OnCall Dispatch system. Part of those sessions is dedicated to loading information specific to the Customers operation. In order for the Customer to make solid choices about their static data, this workshop will educate the Customer core team members on the features and functions of OnCall Dispatch that pertain to the specific static data elements required by OnCall to function. Those static data elements include: • Agencies • Unit Types • Units • Event Types • Disposition Codes • Out -of -Service Types • Facility Service Types • Known Caller Types • Special Situation Types • Personnel/Users Beats/Station Areas • Dispatch Groups • Stations (Police Stations, Sub -Stations, Fire Stations) • Number Formats (Event, Case, Dispatch) • Rotational Services (Towing, Ambulance, Lock Smith, etc.) • Vehicles Task Deliverables • OnCall Dispatch and Mobile Unit Launch • OnCall Dispatch Data Collection Worksheets Task Prerequisites • Project Kickoff Meeting Statement of Work 15 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Task Assumptions The OnCall Dispatch and Mobile Unit Launch will review only COTS functionality in a demo environment The OnCall Dispatch and Mobile Unit Launch will be up to twenty-four (24) hours for OnCall Dispatch and up to eight (8) hours for Mobile Unit Hexagon Team Participation and Responsibilities • Hexagon shall provide the OnCall Dispatch and Mobile Unit Launch at the Customer's facilities Customer Team Participation and Responsibilities Customer shall: • Attend the OnCall Dispatch and Mobile Unit Launch • Supply facilities to support number of attendees and remote viewing • Designate and assign Customer system administration and Core Team to attend the entire workshop Task Acceptance Criteria This Task will be completed when the OnCall Dispatch and Mobile System Launch has been conducted Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 4. OnCall Dispatch Map Overview Task Description This Task introduces the Customer GIS core team to the requirements and concepts involved in the development of the OnCall Dispatch map dataset and visual representation. This is a one (1)-day remote Task, conducted via online conferencing. Topics include, but are not limited to: Introduction to OnCall Dispatch GIS data requirements (see Attachment K) Optional GIS data elements that can be used by OnCall Dispatch This session will use Hexagon -provided GIS data for the purposes of discussion. Hexagon will use its equipment to conduct any demonstrations that may occur. Customer attendance should be limited to GIS professionals with responsibility for the creation and maintenance of Customer GIS data. Up to six (6) Customer personnel may attend. No new map content rolls or conversion of map data are included in the SOW scope. Map content will be provided to the OnCall Dispatch system through map layers and web services to be provided by the Customer. Task Prerequisites • Project Kickoff • OnCall Dispatch and Mobile Unit Launch Task Assumptions • Appropriate facilities have been identified to support number of attendees (if co -located), including an LCD projector, a projection screen, and a whiteboard This workshop will be conducted remotely via online conferencing over one (1) day Hexagon Team Participation and Responsibilities • Hexagon shall conduct the OnCall Dispatch Map Overview Customer Team Participation and Responsibilities Customer shall: Ensure its GIS/Map Administrator is involved throughout this Task Supply facilities, including an LCD projector, a projection screen, and a whiteboard Designate and assign no more than four (4) Customer mapping/GIS personnel to attend the entire workshop. Two (2) additional people may attend as observers/auditors Ensure that all appropriate Customer GIS professionals are sufficiently trained and experienced in GIS fundamentals Task Acceptance Criteria The Task is considered complete after the OnCall Dispatch Map Overview is conducted. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 5. Creation of Cloud Environment Task Description The objective of this Task is to create and "spin -up" the Customer's Development Environment for the Dispatch Cloud Program. The Development Environment will be used by Customer during the Project and serve as the basis for the Development Cloud Environment upon Cloud Cutover. Hexagon will inform the Customer once the applicable Development Environment for Customer has been created. Task Assumptions • None Hexagon Team Participation and Responsibilities • Hexagon will create the Cloud Environment (only Development Environment at this Task) with the Dispatch Cloud Applications identified in the Cloud Program Order, which will be used for subsequent Tasks (Customer is not provided Credentials/License Keys at this time). Customer Team Participation and Responsibilities • None Task Acceptance Criteria This Task shall be complete upon creation of the Customer's Development Environment. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 6. IOC Completion Task Description This Task serves as a milestone and culmination of the previous Tasks. It is at this point in the Project that Hexagon has created the Cloud Environment. With the completion of the foregoing Tasks and as part of this Task, Hexagon will host a remote meeting with the Customer Project Manager to: (i) deliver to Customer the Credentials//License Keys applicable to the Dispatch Program and identified in the Quote to the Cloud Program Order and (ii) ensure the Customer Project Manager is able to access the Cloud Program with the Cloud Credentials/License Keys ("Credentials Delivery Meeting"). The Credentials Delivery Meeting is complete once those two objectives are achieved. Completion of this Task also serves to mark the completion of IOC Phase. Task Deliverables- • Delivery of Credentials/License Keys for Dispatch Cloud Program included within the Quote • Customer can login to the Dispatch Cloud Program using Credentials/License Keys Task Prerequisites Creation of Cloud Environment Task is complete Task Assumptions Customer has necessary hardware, equipment, and Network Infrastructure ready and available to access the Cloud Program The Credentials Delivery Meeting is of a limited duration and only intended to cover the two topics specified above. Hexagon Team Participation and Responsibilities Hexagon shall: Host the Credentials Delivery Meeting Deliver Credentials/License Keys for Dispatch Cloud Program Ensure the Customer can log into the Dispatch Cloud Program to confirm connectivity (-, Address Customer reported issues with accessing the Dispatch Cloud Program Customer Team Participation and Responsibilities Customer shall: Attend the Credentials Delivery Meeting Access the Dispatch Cloud Program via the Credentials/License Keys provided during the Credentials Delivery Meeting Report to Hexagon verbally during the Credentials Delivery Meeting whether the Customer can access the Dispatch Cloud Program or identify issues encountered in accessing the Dispatch Cloud Program Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation If Customer encounters issues in accessing the Dispatch Cloud Program, it will work collaboratively with Hexagon to troubleshoot and address the issue until resolution Task Acceptance Criteria This Task is complete when Hexagon has delivered the Dispatch Cloud Program Credentials/License Keys to Customer and confirmed the Customer is able to access the Dispatch Cloud Program. Statement of Work 20 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Final Operating Capability (FOC) Phase 7. CAD System Build 1 Task Description The objective of this Task is to provide the Customer with a basic Dispatch Cloud Program that Hexagon and the Customer can use for subsequent build, configuration, and training tasks in FOC. Each on -site workshop will last 32 hours over one (1) week. Once the workshop is completed, Hexagon shall implement the data and information into the Dispatch Cloud Program consistent with the topics addressed in this Task. To prepare for this Task, the Customer will need to collect the data required to configure the Dispatch Cloud Program to reflect its data and workflows, which should be consistent with the Specifications. This Task and other System Build Tasks will not include the Interfaces. This Task builds upon the concepts and topics covered in the OnCall Dispatch and Mobile Unit Launch task already conducted. Hexagon will provide a review of those topics and the Dispatch Cloud Program to re - familiarize the Core CAD Project Team with OnCall Dispatch features, including event processing, dispatching, map utilization and inquiries. Hexagon will also begin to build the final Dispatch Cloud Program, entering some Customer -specific OnCall Dispatch configuration data as it walks the Core Team through the system features. Hexagon will review with the Customer how the Dispatch Cloud Program is configured and set up OnCall Administrator functionality. Hexagon will also begin entering OnCall Dispatch configuration data provided by the Customer into the Cloud Environment. During this week, the Customer should have ready and provide Hexagon with the following types of data: Agency Event / Case Numbers Event types /Subtypes Unit Types Units Vehicles Stations Task Deliverables Conduct the first of three (3) collaborative System Build sessions Task Prerequisites Customer completion of necessary OnCall Dispatch Data Worksheets for applicable data, provided during OnCall Dispatch and Mobile Unit Launch Task. Hexagon Team Participation and Responsibilities Hexagon shall: Provide services for the initial Dispatch Cloud Program build Work in collaboration with the Customer's Core Team to load and/or import refreshed site -specific data into the Dispatch Cloud Program, if necessary Statement of Work #1 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Customer Team Participation and Responsibilities Customer shall: • Ensure appropriate Customer personnel are available for the System Build sessions • Observe installation and begin to develop an in-depth understanding of the Dispatch Cloud Program • Participate fully during joint system build -out sessions Task Acceptance Criteria This Task is considered complete at the conclusion of the first of three (3) collaborative System Build sessions. Statement of Work 22 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 8. CAD System Build 2 Task Description In this Task, Hexagon will continue System review with the Customer during the second week of the system build sessions. System Build 2 will follow the same process and framework as described in System Build 1 Task. At the outset of this Task the Customer should have and be able to provide Hexagon with the following types of data, which are intended to be addressed during this Task: Deployment and recommendation planning ESZs Beats Dispatch groups Deployment plans Response requirements Response plans Continue data build, including but not limited to: Personnel Out of service Dispositions Lineups Task Deliverables Conduct the second of three (3) collaborative System Build sessions Task Prerequisites Customer completion of necessary OnCall Dispatch Data Worksheets for applicable data Hexagon Team Participation and Responsibilities Hexagon shall: Provide services for the initial Dispatch Cloud Program build Work in collaboration with the Customer's Core Team to load and/or import refreshed site -specific data into the Dispatch Cloud Program, if necessary Customer Team Participation and Responsibilities Customer shall: Ensure appropriate Customer personnel are available for the System Build sessions Observe installation and begin to develop an in-depth understanding of the Dispatch Cloud Program Participate fully during joint system build -out sessions Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Task Acceptance Criteria This Task is considered complete at the conclusion of the second of three (3) collaborative System Build sessions. Statement of Work 24 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 9. CAD System Build 3 Task Description During this task, Hexagon will finish the Dispatch Cloud Program and begin the department specific configuration discussion. System Build 3 will follow the same process and framework as described in System Build 1 Task. This configuration will address more advanced OnCall Dispatch functionality, including Department -specific and advanced functions such as response plans, message groups, lineups, etc. By the end of this week, the Core Team will have an in-depth understanding of OnCall Dispatch and be able to test configuration data and establish scenarios for upcoming configuration work. Task Deliverables Conduct the third of three (3) collaborative System Build sessions Task Prerequisites r Customer completion of necessary OnCall Dispatch Data Worksheets for applicable data Hexagon Team Participation and Responsibilities Hexagon shall: Provide services for the initial Dispatch Cloud Program build Work in collaboration with the Customer's Core Team to load and/or import refreshed site -specific data into the Dispatch Cloud Program, if necessary Customer Team Participation and Responsibilities Customer shall: Ensure appropriate Customer personnel are available for the System Build sessions Observe installation and begin to develop an in-depth understanding of the Dispatch Cloud Program Participate fully during joint system build -out sessions Task Acceptance Criteria This Task is considered complete at the conclusion of the third collaborative System Build session. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 10. Custom Interface Requirements Gathering Task Description During this Task, Hexagon and Customer will meet via conference call to validate the assumptions and design of each CAD Custom Interface identified in this SOW and Attachment H (Interface Descriptions). The information obtained in combination with the information in Attachment H will be used to develop an Interface Control Document (ICD) for each Custom Interface. If the assumptions reflected in Attachment H materially change, a Change Order may be appropriate. The ICDs will become the foundation for the Custom Interface development by the Project team. The ICDs will go through a change control process to ensure validity and alignment with the agreed -upon scope of work. Once the ICDs are approved, changes will be managed through the change control process and reviewed against Project Schedule and/or budget. The Customer shall not make and shall take appropriate actions to prevent its third -party vendor from making substantive changes to the third -party software that is the subject of a Custom Interface once that Custom Interface's respective ICD has been finalized. The interfaces review workshop is intended to contain a series of discussions to validate the requirements and assumptions underlying the Custom Interfaces. These sessions should include third -party vendors where appropriate. During the sessions, the specific workflow and data requirements for each of the following interfaces will be discussed in detail. The following are regarded as "Custom Interfaces" as the term is defined in Attachment J of this SOW: • Informer query interface to Motorola RMS • Interface to Traffic Management System • Interface to Telestaff • Interface to Hydrant For descriptions and assumptions regarding each interface listed above, please see Attachment H: Interface Descriptions. As it pertains to the development of the ICD, the parties shall follow the following process. After the interface review workshop, Hexagon will prepare a draft ICD for each Custom Interface. Hexagon will then provide the initial draft ICD to the Customer for its review. The Customer shall review the draft ICD and provide any feedback or comments within ten (10) business days. As appropriate Hexagon will incorporate the feedback into the ICD or advise the Customer why certain requests could not be included (e.g. the request conflicted with Attachment H) and finalize the ICD. Hexagon will provide the finalized ICD to the Customer for its written acknowledgement. The Customer will provide a response within three (3) business days from Hexagon providing the finalized ICD. Task Deliverables Workshop meeting minutes, to include notes on the specific workflow and data requirements for each custom interface proposed c ICD documents Task Prerequisites Project Kickoff Meeting Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Task Assumptions This Task will be conducted remotely The Customer will coordinate interactions with the third -party vendors, including obtaining and providing any API or specification documentation required to develop the proposed interfaces If required, all NDAs between Hexagon and third parties will be executed and current. Customer is responsible for facilitating its third -party vendors reasonable cooperation with this requirement The Customer is responsible for obtaining cooperation and information from its third -party vendors and/or state agency as reasonably necessary for the development, testing, and cutover of the interfaces Hexagon Team Participation and Responsibilities Hexagon shall: Lead the interface requirements gathering process and track outstanding items requiring resolution Confer with Customer and third -party points of contact to gather information required to develop ICDs Validate the third -party points of contact are appropriate sources of information necessary to develop ICD Mutually agree with the third -party vendors on the operational and technical interface requirements Gather all available interface data detailed schema, protocols, and specifications, as needed Prepare draft ICDs and submit to Customer for feedback Incorporate Customer feedback into draft ICDs Finalize ICDs for Customer review and approval Manage the approved ICDs consistent with the change control process Customer Team Participation and Responsibilitie€ Customer shall: Identify and set up appropriate facilities Provide points of contacts who are knowledgeable of the workflow and data requirements for Customer hardware and software components with which the Custom Interfaces will interact Promptly review all draft ICD submissions and provide comments, questions, or approval within ten (10) business days of receipt Agree to and sign the ICDs before any development work can begin. Failure to approve in a timely manner may impact Project Schedule and incur additional cost Task Acceptance Criteria This Task is complete upon completion of all ICDs and final approval of the ICDs by both Hexagon and the Customer. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 11. Custom Interface Development Task Description During this Task, Hexagon will be working remotely to develop the Custom Interfaces based upon the ICDs that were created from the Custom Interface Requirements Gathering Task. Task Deliverables Custom Interface documentation Task Prerequisites (' Custom Interface ICDs Task Assumptions All work associated with this task will be performed remotely Any changes to a third -party interface developed by Hexagon that will alter the agreed -upon ICD will have to follow the change management guidelines in accordance with the Agreement Development of the interface shall not commence until the signed/approved ICD is returned to Hexagon. Failure to approve in a timely manner may impact project schedule and incur additional cost Hexagon Team Participation and Responsibilities Hexagon shall: Develop the Custom Interfaces Customer Team Participation and Responsibilities Customer shall: Ensure SMEs are available as needed Obtain third -party cooperation as reasonably requested by Hexagon Task Acceptance Criteria This Task is complete when all Custom Interfaces listed above are developed. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 12. Connectivity to Cloud Program Task Description During this task Hexagon will establish the VPN tunnel to allow connectivity between the Cloud Program and the Customer's on -premise networking resources. Once established, Hexagon will collaborate with the Customer to confirm connectivity to the Cloud Program. Task Deliverables Ping message sent from the Customer is received by the Cloud Program Ping message sent from the Cloud Program is received by the Customer Task Prerequisites IOC Phase is completed Task Assumptions Credentials/License Keys have been provided to Customer Hexagon Team Participation and Responsibilities Send ping message between Cloud Program and the Customer to confirm connectivity Customer Team Participation and Responsibilities Send ping message between Cloud Program and the Customer to confirm connectivity Task Acceptance Criteria This task is complete upon the Customer confirmation of ping messages are sent and received between the Cloud Program and the Customer. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 13. On Premise Local Software Server Installation and Configuration Task Description This Task is for creation and configuration of the Local Server VMs. It includes the creation of the VMs, setting server names and IPs, joining them to the domain and adding the Hexagon CAD Admin groups to the local admins groups of the servers to provide the implementers the required access for the rest of the Project. Task Deliverables - Server configuration documentation, which consists of a spreadsheet with server names, IPs and passwords utilized Updated Visio document showing servers, applications installed, names, and IPs Task Prerequisites Customer must have available virtual environment resources for staging of project VMs VPN credentials and client (if needed) must be provided to the Hexagon Project Manager Not required if Customer is using SecureLink Complete the Server name, IP Address and Service account template provided by Hexagon Task Assumptions All work being performed by Hexagon that requires physical access to the equipment will be performed on site, and those tasks that do not require physical access may be performed remotely at Hexagon's discretion New virtual servers will be created/provided for the sole purpose of the Project defined by this SOW and will not serve other roles Access to the vCenter server via Power CLI is required by the Hexagon staff to script the creation of the VMs Hexagon Team Participation and Responsibilities Hexagon shall: Import VM Templates to vCenter, create the VMs, assign them the required CPU, memory, and disk space to comply with the OnCall Dispatch Specifications document Assign the I Addresses to the VMs Join the VMs to the domain Apply current Windows updates if Internet connectivity or access to another repository for updates is available Create and deliver the Server Configuration Documentation Provide spreadsheet with server names, IPs, and passwords utilized Customer Team Participation and Responsibilities Customer shall: Statement of Work A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation • Provide domain level credentials for the vCenter server and join servers to the domain • Provide assistance with resolving issues related to network connectivity and/or remote access • Answer other configuration questions as needed Task Acceptance Criteria This Task is considered complete when the Server Configuration Documentation has been delivered to Customer. Statement of Work 31 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 14. OnCall Map Service Configuration and Consulting Services Task Description A central feature of OnCall Dispatch is interoperation and use of a map source in the Dispatch Cloud Program. The Dispatch Cloud Program utilizes the mapping services provided by Azure Maps. The objective of this Task is to collaborate with the Customer's GIS Administrator regarding use of Azure Maps within the Dispatch Cloud Program and management of the source map. Over the course of up to five (5) Days, a Hexagon technical resource will host a remote meeting facilitating the mapping workshop ("Map Consulting Session") with the Customer GIS Administrator and any other interested Customer SMEs. The Mapping Consulting Session is intended to be a collaborative session and for Hexagon and the Customer GIS Administrator to discuss use of the Azure Maps within the Cloud Dispatch Applications and management of the Azure Maps or other map in the context of the Dispatch Cloud Applications. As time permits, the parties can discuss other GIS related topics. To facilitate a productive Map Consulting Session, the Customer GIS Administrator, at a minimum, should have participated in the OnCall Dispatch Map Overview. The Customer shall also have complied with the mapping requirements prior to this Task. As a result of the Map Consulting Session, the Customer's GIS Administrator shall have additional insight and information on how to manage and use the map in connection with the Dispatch Cloud Program. For purposes of clarity, this Map Consulting Session is not intended to result in configuration or modification of Azure Maps. The Customer may configure the map at its discretion up to the commencement of Functional Testing. At the commencement of Functional Testing, the Customer shall refrain from making any modification or configurations to the map until after Cloud Cutover. Task Prerequisites • Completion of IOC • Completion of the OnCall Dispatch Map Overview task Task Assumptions ® Azure Maps will serve as the source map for the Project The Customer GIS Administrator has sufficient authority to make decisions about the use, configuration, and integration of the source map Hexagon Team Participation and Responsibilities • A Hexagon technical resource will conduct the Map Consulting Session Customer Team Participation and Responsibilities ® Customer GIS Administrator attends the Map Consulting Session Customer Project Manager has provided Customer's GIS Administrator Credentials/License Keys to the Dispatch Cloud Program Customer manages and makes any desired configurations to Azure maps Task Acceptance Criteria This Task is complete at the conclusion of the Map Consulting Session. Statement of Work 3 1% HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 15. Informer Setup (CommSys) Task Description During this Task, Hexagon will utilize the CommSys ConnectClC state Interface middleware product for the Interface to the state message switch for the following state and national transactions respectfully. The CommSys ConnectClC middleware product will work with the Customer's Informer interface to support the transactions listed below. Person (In State and NLETS) (FQW, QW, DQ, FDQ, QM) Wanted/Warrants Missing Driver's license Vehicle (In State and NLETS) (QV, FRQ, FQL, RQ) Wanted/stolen Registration Vehicle Parts Gun by (serial, caliber, make) (QG) Florida Concealed Weapons Permit Query (FCW) Article (serial, type) (QA) Boat (In State and NLETS) (QB, FBQ, BQ) Hull Number Registration ID • Aircraft (GQ) • Hazmat (MQ) • Canadian Queries Person Driver's License/Want (WQ, UQ) Vehicle Registration/Want (VQ, XQ) Boat by License, Hull, Registration (CBQ) Gun by Serial (CGQ) Article by Serial (CAQ) HxGN OnCall Dispatch I Informer Interface will support the queries to state/NCIC (via CommSys ConnectClC) from Dispatch and Mobile Unit Task Deliverables CommSys ConnectClC setup and installation Task Prerequisites 4. The current version of ConnectClC is 2.9 Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Task Assumptions Primary agency is intended to be Customer The supported transaction is basic query only This SOW does not include the development of any new forms, queries, or transactions for Informer unless specifically identified herein ConnectClC will be installed on premise on the Local Software server Hexagon Team Participation and Responsibilities Hexagon shall: Work with CommSys to verify the ConnectClC state interface middleware product is set up and installed for the Customer agencies listed above. Customer Team Participation and Responsibilities Customer shall: If there are any changes that impact the Informer interface(s), Customer is responsible for ensuring that documentation detailing the format, development\design, and connection information (IP, protocol, credentials, etc.) is provided to Hexagon either by the State or by Customer. If this information is not provided by the State, Customer is responsible for collecting and determining if this information is valid and providing it to Hexagon. If the documentation is not provided to Hexagon, additional services\charges may be incurred by Customer Have CJIS-related security in place as it relates to Informer data, transactions, and responses Provide points of contact who are knowledgeable of the workflow and data requirements for Customer hardware and software components with which Hexagon deliverables will interface Provide test connections to State/NCIC, as well as other external system required for the Project Provide live connections to State/NCIC, as well as other external systems required for the Project Enter associated ORI, user credentials (if applicable), and terminal mnemonics Provide test records to ensure that the transactions received by the System in a test environment are in the same format and contain the same information as those received in a production environment Test and report any Errors to Hexagon within ten (10) business days of installation on Customer's test System Task Acceptance Criteria This Task is considered complete upon installation of the CommSys ConnectClC product. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 16. OnCall Dispatch Police Configuration Consulting Session Task Description The objective of this Task is to familiarize the Customer Police Department with configurability of the Software to facilitate configuration for its call -taking and dispatching operations, plus administrative and supervisory operations. The Customer is responsible for configuring the Dispatch Cloud Program. Hexagon will provide specific consulting sessions as part of the Project (described below), but the Customer Core Team's understanding of configuration will correspondingly allow the Customer to adapt the Dispatch Cloud Program to better suit its business processes and workflows. The Customer shall complete configuration of the System within ten (10) business days after the Dispatch Configuration Session (as the term is defined below) the "Dispatch Configuration Period." If the Customer has questions as it configures OnCall Dispatch it may contact Hexagon to address the question. As part of the configuration consulting, Hexagon will conduct two consulting sessions, the first being four (4) days of on -site time with the Customer's Core Team to review configuration options for OnCall Dispatch ("Dispatch Configuration Session"). Topics will include layout manager, custom fields, unit and event boards, parameter settings, and notification settings. The second session is one (1) day of remote time to review the needs for configuring the Mapping related options for geocoding, routing, deployment polygons and map display ("Mapping Configuration Session"). The Mapping Configuration Session is intended to occur during the Dispatch Configuration Period. After the Dispatch Configuration Session and Mapping Service Configuration Session, Hexagon will provide the Customer with a document titled, "Site Configuration Document." The Site Configuration Document is a working document that will be updated throughout implementation and finalized and delivered to Customer at OnCall Dispatch/Mobile Unit Subsystem Cutover. Task Deliverables • One (1) Police Dispatch Configuration Session • One (1) Mapping Configuration Session • OnCall Police Site Configuration Document Task Prerequisites • Completion of OnCall Dispatch Build Workshops Hexagon Team Participation and Responsibilities Hexagon shall: • Conduct the Police Dispatch Configuration Session • Conduct the Mapping Configuration Session • Provide support (question and answer support) as Customer configures the Dispatch Cloud Program • Deliver the Police Site Configuration Document Customer Team Participation and Responsibilities Customer shall: Statement of Work 35 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Ensure appropriate personnel attend, and fully participate in all the Dispatch Configuration Session and the Mapping Configuration Session • Provide department -specific CAD configuration and workflow data as needed • Provide CAD interface configuration and workflow data as needed • Configure OnCall Dispatch within the Dispatch Configuration Period Task Acceptance Criteria The Task is complete when Hexagon has conducted the Police Dispatch Configuration Session and the Mapping Configuration Session. Statement of Work 36 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 17. OnCall Dispatch Fire Configuration Consulting Session Task Description The objective of this Task is to familiarize the Customer Fire Department with configurability of the Software to facilitate configuration for its call -taking and dispatching operations, plus administrative and supervisory operations. The Customer is responsible for configuring the Dispatch Cloud Program. Hexagon will provide specific consulting sessions as part of the Project (described below), but the Customer Core Team's understanding of configuration will correspondingly allow the Customer to adapt the Dispatch Cloud Program to better suit its business processes and workflows. The Customer shall complete configuration of the System within ten (10) business days after the Dispatch Configuration Session (as the term is defined below) the "Dispatch Configuration Period." If the Customer has questions as it configures OnCall Dispatch it may contact Hexagon to address the question. As part of the configuration consulting, Hexagon will conduct two consulting sessions, the first being four (4) days of on -site time with the Customer's Core Team to review configuration options for OnCall Dispatch ("Dispatch Configuration Session"). Topics will include layout manager, custom fields, unit and event boards, parameter settings, and notification settings. The second session is one (1) day of remote time to review the needs for configuring the Mapping related options for geocoding, routing, deployment polygons and map display ("Mapping Configuration Session"). The Mapping Configuration Session is intended to occur during the Dispatch Configuration Period. After the Dispatch Configuration Session and Mapping Service Configuration Session, Hexagon will provide the Customer with a document titled, "Site Configuration Document." The Site Configuration Document is a working document that will be updated throughout implementation and finalized and delivered to Customer at OnCall Dispatch/Mobile Unit Subsystem Cutover. Task Deliverables • One (1) Fire Dispatch Configuration Session • One (1) Mapping Configuration Session • OnCall Fire Site Configuration Document Task Prerequisites • Completion of OnCall Dispatch Build Workshops Hexagon Team Participation and Responsibilities Hexagon shall: • Conduct the Fire Dispatch Configuration Session • Conduct the Mapping Configuration Session • Provide support (question and answer support) as Customer configures the Dispatch Cloud Program • Deliver the Fire Site Configuration Document Customer Team Participation and Responsibilities Customer shall: Statement of Work 37 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Ensure appropriate personnel attend, and fully participate in all the Dispatch Configuration Session and the Mapping Configuration Session • Provide department -specific CAD configuration and workflow data as needed • Provide CAD interface configuration and workflow data as needed • Configure OnCall Dispatch within the Dispatch Configuration Period Task Acceptance Criteria The Task is complete when Hexagon has conducted the Fire Dispatch Configuration Session and the Mapping Configuration Session. Statement of Work 38 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 18. OnCall Dispatch Configuration Follow-up Workshop Task Description The objective of this Task is to review the Customer -specific configuration of the Dispatch Cloud Program. Hexagon will conduct one (1) four (4)-day system configuration follow-up session at Customer's facilities. As part of this workshop Hexagon will review the Customer configurations for both Police and Fire including layout manager, custom columns, unit and event Boards, parameter settings, and notification settings. After the workshop, Hexagon will update the OnCall Site Configuration Document. Task Deliverables • Updated CAD Site Configuration Document Task Prerequisites • Customer has completed OnCall Dispatch Configuration Hexagon Team Participation and Responsibilities Hexagon shall: Conduct one (1) on -site configuration follow-up workshop Provide the updated OnCall Site Configuration Document Customer Team Participation and Responsibilities Customer shall: Ensure appropriate personnel attend, and participate fully and collaboratively Provide department -specific CAD configuration and workflow data as needed Provide interface configuration and workflow data as needed Task Acceptance Criteria This task is considered complete upon the delivery of the updated OnCall Site Configuration Document and upon the completion of the OnCall Dispatch Configuration Follow-up Workshop. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 19. Customer Rules Engine Configuration Workshop Task Description The objective of this Task is to familiarize the Customer with configurability of the OnCall Dispatch Customer Rules Engine (CRE), an add -on component to the HxGN OnCall Dispatch product suite. CRE allows customized business rules to be created using a drag -and -drop editor. The customized business rules can be used to implement workflows that are specific to a particular customer and therefore not available out -of -the -box in the core HxGN OnCall Dispatch product suite. The Customer is responsible for configuring CRE. Hexagon will provide specific consulting sessions as part of the Project, but the Customer Core Team's understanding of configuration will correspondingly allow the Customer to use CRE to create custom workflows. Hexagon will also provide an example of how to implement a CRE-based configuration in the Customer's Environment. Hexagon will conduct a workshop (`CRE Workshop") to familiarize the Customer with CRE, provide an example of a CRE configuration, and, if time permits, begin working on implementing CRE-based configurations. The CRE Workshop shall last no more than four (4) Business Days. Any CRE-based configuration not completed at the end of the CRE Workshop shall be the responsibility of Customer. The Customer shall complete configuration of CRE within ten (10) Business Days after the CRE Workshop (the "CRE Configuration Period"). If the Customer has questions as it configures CRE, it may contact Hexagon to address the question. Task Deliverables • CRE Workshop Task Prerequisites OnCall Dispatch Configuration Follow-up Workshop Task is complete. Task Assumptions • Hexagon responsibilities will be executed on site at a Customer -provided facility that: Has a projector and screen for displaying the content being presented; and If the Customer's policies preclude connecting Hexagon owed equipment to their network, a computer workstation for use by Hexagon for presenting content shall be made available. Attendance by the Customer's personnel will be limited to no more than twelve (12) people and must consist of field users and stakeholders capable of making finalized decisions about configurations within OnCall Dispatch. Each Customer attendee will have access to their own computer workstation that: Has Google Chrome installed and is ready for use; Has Internet access; and • Has at least one (1) external monitor with a resolution no smaller than 1920x1080, two (2) external monitors are preferred. Hexagon Team Participation and Responsibilities Hexagon shall: Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Conduct the CRE Workshop; and • Provide support (question and answer support) as Customer configures CRE. Customer Team Participation and Responsibilities Customer shall: Ensure appropriate personnel attend, and fully participate in all the CRE Workshop; Provide department -specific CAD configuration and workflow data as needed; and Configure CRE within the CRE Configuration Period. Task Acceptance Criteria This Task is considered complete when Hexagon has conducted the CRE Workshop. Statement of Work 41 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 20. OnCall Dispatch I Mobile Unit Police Configuration Consulting Session Task Description The Customer Police Department is responsible for configuring the Mobile Unit subsystem. Hexagon will conduct one (1) on -site consulting session with the Customer over three (3) days as part of the Project ("Mobile Configuration Session"). During the Mobile Configuration Session, Hexagon will provide information regarding configuration options for Mobile Unit workflows as they pertain to the mobile environment. The workshop will address: Sign on/Sign off Brief Overview of Application Screen Layout Navigation Buttons Alerts Toolbars Event Search • Menus and Submenus • Map • Messaging • Unit Board Event Board The included Dispatch Report Network requirements and ports to ensure the Mobile Unit client can communicate appropriately The Customer will need to make available one dispatcher familiar with OnCall Dispatch to perform dispatching and other related tasks as necessary during the Police Mobile Consulting Session. Following the Mobile Configuration Session, the Customer will configure Mobile Unit during the next ten (10) business days ("Mobile Configuration Period"). At the conclusion of this period, Hexagon will review the Customer's configuration and provide feedback in a four (4) hour remote consultation. The Customer will then have the next ten (10) business days to continue or revise configuration ("Mobile Configuration Follow -Up Period"). At the conclusion of the Mobile Configuration Follow -Up Period, Hexagon will perform a final review with the Customer and provide feedback in a four (4) hour remote consultation. Upon completion of this Task, the Customer will have at minimum one (1) or up to two (2) mobile configuration(s) of Mobile Unit for testing. Task Deliverables • Police Mobile Configuration Session (on -site) • Police Mobile Configuration Consultation (remote) • Police Mobile Configuration Follow -Up Consultation (remote) Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Task Prerequisites • Completion of OnCall Dispatch and Mobile Unit Launch Completion of OnCall Dispatch Configuration Task Hexagon Team Participation and Responsibilities Hexagon shall: Conduct one (1) instance of Police Mobile Configuration Session Begin the Police Mobile Unit Configuration Document Provide support as the Customer Police Department configures Mobile Unit Customer Team Participation and Responsibilities Customer shall: Provide mobile SME to support Hexagon as needed Provide a Dispatcher SME to provide feedback on how Mobile Unit will affect disptachers and assist with various dispatching Activities Participate fully and collaboratively in the Mobile Configuration Session with the understanding that Mobile Unit client configuration decisions must be documented and agreed upon at the conclusion of these sessions • Configure Mobile Unit during the Mobile Configuration Period Task Acceptance Criteria The Task is complete when Hexagon has conducted the Police Mobile Configuration Session, Police Mobile Configuration Consultation, and Police Mobile Configuration Follow -Up Consultation. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 21. OnCall Dispatch I Mobile Unit Fire Configuration Consulting Session Task Description The Customer Fire Department is responsible for configuring the Mobile Unit subsystem. Hexagon will conduct one (1) on -site consulting session with the Customer over three (3) days as part of the Project (`Mobile Configuration Session"). During the Mobile Configuration Session, Hexagon will provide information regarding configuration options for Mobile Unit workflows as they pertain to the mobile environment. The workshop will address: Sign on/Sign off Brief Overview of Application Screen Layout Navigation Buttons Alerts Toolbars Event Search • Menus and Submenus • Map • Messaging • Unit Board Event Board The included Dispatch Report Network requirements and ports to ensure the Mobile Unit client can communicate appropriately The Customer will need to make available one dispatcher familiar with OnCall Dispatch to perform dispatching and other related tasks as necessary during the Fire Mobile Consulting Session. Following the Mobile Configuration Session, the Customer will configure Mobile Unit during the next ten (10) business days (`Mobile Configuration Period"). At the conclusion of this period, Hexagon will review the Customer's configuration and provide feedback in a four (4) hour remote consultation. The Customer will then have the next ten (10) business days to continue or revise configuration (`Mobile Configuration Follow -Up Period"). At the conclusion of the Mobile Configuration Follow -Up Period, Hexagon will perform a final review with the Customer and provide feedback in a four (4) hour remote consultation. Upon completion of this Task, the Customer will have at minimum one (1) or up to two (2) mobile configuration(s) of Mobile Unit for testing. Task Deliverables • Fire Mobile Configuration Session (on site) • Fire Mobile Configuration Consultation (remote) • Fire Mobile Configuration Follow -Up Consultation (remote) Statement of Work 44 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Task Prerequisites • Completion of OnCall Dispatch and Mobile Unit Launch Completion of OnCall Dispatch Configuration Task Hexagon Team Participation and Responsibilities Hexagon shall: Conduct one (1) instance of Fire Mobile Configuration Session Begin the Fire Mobile Unit Configuration Document Provide support as the Customer configures Mobile Unit Customer Team Participation and Responsibilities Customer shall: Provide mobile SME to support Hexagon as needed Provide a Dispatcher SME to provide feedback on how Mobile Unit will affect disptachers and assist with various dispatching Activities Participate fully and collaboratively in the Mobile Configuration Session with the understanding that Mobile Unit client configuration decisions must be documented and agreed upon at the conclusion of these sessions • Configure Mobile Unit during the Mobile Configuration Period Task Acceptance Criteria The Task is complete when Hexagon has conducted the Fire Mobile Configuration Session, Fire Mobile Configuration Consultation, and Fire Mobile Configuration Follow -Up Consultation. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 22. OnCall Dispatch Mobile Responder Police Consulting Session Task Description Hexagon will conduct one (1) remote consulting session with the Customer over one (1) day as part of the Project ("Police Mobile Responder Configuration Session"). During this session, Hexagon will consult with the Customer on the OnCall Dispatch Mobile Responder for the Customer's Police agency. The Customer will need to make available one (1) Dispatcher familiar with OnCall Dispatch to perform dispatching and other related tasks as necessary during each workshop. Following the Police Mobile Responder Configuration Consulting Session, Hexagon will implement the Customer -requested configuration changes. Regardless of volume of requested configurations Hexagon will not exceed sixteen (16) hours of effort. Task Deliverables • One (1) remote Police Mobile Responder Configuration Session Remote Police Mobile Responder Configuration Services of up to sixteen (16) hours Task Prerequisites Completion of OnCall Dispatch Configuration Consulting Session Task Assumptions • Attendance by the Customer's personnel will be limited to no more than twelve (12) people and must consist of field users and stakeholders capable of making finalized decisions about product behavior and functionality Hexagon Team Participation and Responsibilities Conduct one (1) instance of Police Mobile Responder Consulting Session Conduct up to sixteen (16) hours of Police Mobile Responder Configuration Services Customer Team Participation and Responsibilities Provide mobile SME to Hexagon as needed Provide a Dispatcher SME to give feedback on how OnCall Dispatch Mobile Responder will affect dispatchers and assist with various dispatching tasks Participate fully and collaboratively in the consulting session with the understanding that OnCall Dispatch Mobile Responder client configuration decisions must be documented Task Acceptance Criteria The Task is complete when Hexagon has conducted the Police Mobile Responder Consulting Session and the Police Mobile Responder Configuration Services. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 23. OnCall Dispatch Mobile Responder Fire Consulting Session Task Description Hexagon will conduct one (1) remote consulting session with the Customer over one (1) day as part of the Project ("Fire Mobile Responder Configuration Session"). During this session, Hexagon will consult with the Customer on the OnCall Dispatch Mobile Responder for the Customer's Fire agency. The Customer will need to make available one (1) Dispatcher familiar with OnCall Dispatch to perform dispatching and other related tasks as necessary during each workshop. Following the Fire Mobile Responder Configuration Consulting Session, Hexagon will implement the Customer -requested configuration changes. Regardless of volume of requested configurations Hexagon will not exceed sixteen (16) hours of effort. Task Deliverables • One (1) remote Fire Mobile Responder Configuration Session Remote Fire Mobile Responder Configuration Services of up to sixteen (16) hours Task Prerequisites Completion of OnCall Dispatch Configuration Consulting Session Task Assumptions • Attendance by the Customer's personnel will be limited to no more than twelve (12) people and must consist of field users and stakeholders capable of making finalized decisions about product behavior and functionality Hexagon Team Participation and Responsibilities Conduct one (1) instance of Fire Mobile Responder Consulting Session Conduct up to sixteen (16) hours of Fire Mobile Responder Configuration Services Customer Team Participation and Responsibilitie° Provide mobile SME to Hexagon as needed Provide a Dispatcher SME to give feedback on how OnCall Dispatch Mobile Responder will affect dispatchers and assist with various dispatching tasks Participate fully and collaboratively in the consulting session with the understanding that OnCall Dispatch Mobile Responder client configuration decisions must be documented Task Acceptance Criteria The Task is complete when Hexagon has conducted the Fire Mobile Responder Consulting Session and the Fire Mobile Responder Configuration Services. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 24. COTS Interface Product Installation and Configuration Task Description During this Task, Hexagon will install and unit test the COTS Interfaces in the Customer's Dispatch Cloud Program. Hexagon will be able to install the COTS Interface and configure it based upon the information provided in the COTS Interface Questionnaire subject to the functionality and features within the COTS Interface. Although the Customer is expected to participate in Hexagon's internal testing of the interfaces, the Customer will formally test interface functionality and reliability during Functional Testing. Task Deliverables Installation and configuration of the COTS Interfaces For more information on the COTS Interfaces, see Attachment H, Interface Descriptions. Task Prerequisites • Operation or availability of the external system or Third Party Software • Approval of completed COTS Interface Questionnaires Hexagon Team Participation and Responsibilities Hexagon shall: Install COTS Interfaces in the Customer's Dispatch Cloud Program Unit test interfaces in accordance with the approved COTS Interface questionnaires Customer Team Participation and Responsibilities - Customer shall: Ensure SMEs are available to support Hexagon Activities as needed Verify that physical connectivity and communication has been achieved to the remote system servers and all other third -party systems (such as RMS systems etc.) Provide availability and confirm operation of external systems or third -party software Ensure the System and network administrators are available to work closely with the Hexagon team for the duration of the Task �_ Ensure third -party cooperation with Hexagon's reasonable requests Task Acceptance Criteria This Task is considered complete when each COTS Interface is installed, configured in accordance with the COTS Interface Questionnaire, and it has passed Hexagon's unit testing. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 25. Custom Interface Product Installation and Configuration Task Description During this Task, Hexagon will install, configure, and test the Custom Interfaces. Although the Customer is expected to participate in Hexagon's internal testing of the Custom Interfaces, the Customer will formally test the interface functionality and reliability during Functional Testing. Task Deliverables Documentation of Custom Interfaces installation/testing Task Prerequisites Operation or availability of the external system or Third Party Software Development and approval of ICDs Hexagon Team Participation and Responsibilities Hexagon shall: Install Custom Interfaces Test Custom Interfaces in accordance with the approved [CDs Customer Team Participation and Responsibilities Customer shall: Ensure SMEs are available to support Hexagon Activities as needed Verify that physical connectivity has been achieved from Customer's communication server to the Dispatch Cloud Program Provide availability and confirm operation of external systems or third -party software Provide the following information to Hexagon: I address for remote databases Socket value for remote systems Operator IDs (ORls), terminal mnemonics, etc., as needed by remote systems Ensure the system and network administrators are available to work closely with the Hexagon team for the duration of the Task Ensure third party cooperation with Hexagon's reasonable requests Task Acceptance Criteria This Task is complete when each Custom Interface is installed and configured in accordance with the applicable ICD. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 26. Standard Interface Product Installation and Configuration Task Description During this Task, Hexagon will install and configure the Standard Interfaces. The Customer will formally test the interface functionality and reliability during Functional Testing. The following are regarded as "Standard Interfaces" as the term is defined in Attachment H of this SOW: External Alarms OnCall Dispatch Interface to ASAP External Alarms OnCall Dispatch Interface to Shotspotter • PLT Radio OnCall Dispatch Interface to Harris Radio • WebEOC CAD Interface • Dispatch Alerts OnCall Interface to EverBridge RapidSOS OnCall Call -Taker Interface Task Deliverables Documentation of Standard Interfaces installation Task Prerequisites Operation or availability of the external system or Third -Party Software Hexagon Team Participation and Responsibilities Install Standard Interfaces as identified in Attachment H Customer Team Participation and Responsibilities Ensure SMEs are available to support Hexagon Activities as needed Verify that physical connectivity has been achieved from Customer's communication server to the Cloud Dispatch Program Provide availability and confirm operation of external systems or third -party software Provide the following information to Hexagon: I address for remote databases Socket value for remote systems Operator IDs (ORls), terminal mnemonics, etc., as needed by remote systems Ensure the system and network administrators are available to work closely with the Hexagon team for the duration of the Task Ensure third -party cooperation with Hexagon's reasonable requests Task Acceptance Criteria This Task is complete when each Standard Interface is installed and configured. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 27. Develop Test Plan and Test Cases Task Description During this Task, the Customer will create a test plan ("Test Plan") with Test Cases. A Test Plan and Test Cases are essential for the Customer to be able to validate and prove the functionality of the Dispatch Cloud Program. Every Benchmark Criteria should have at least one Test Case; some Benchmark Criteria may have multiple associated Test Cases. The Customer will identify the Benchmark Criteria that correspond to the applicable Test Cases. A clear pass/fail criterion must be defined for each Test Case. The Test Plan and Test Cases will be agency -specific and work -process driven with clearly documented Pass/Fail criteria. Only the elements of the Test Plan and Test Cases conforming with the Benchmark Criteria shall be used in evaluating and testing the System in subsequent testing. The Test Plan is the set of Test Cases that will serve as the basis of testing the fully configured Dispatch Cloud Program, including interfaces. The Customer will not need a fully configured Dispatch Cloud Program to create the Test Plan and Test Cases. The Test Case creation should be accomplished using a workflow -based Test Case. Task Deliverables Customer's Test Plan and Test Cases Hexagon Team Participation and Responsibilities Hexagon shall: Consult with the Customer during the Test Plan and Test Cases creation task to validate the Test Cases correspond to the Benchmark Criteria Customer Team Participation and Responsibilities Customer shall: Create a Test Plan and Test Cases Provide Test Plan and Test Cases to Hexagon Task Acceptance Criteria This Task will be considered complete when the Customer has created the Test Plan and Test Cases and Hexagon has validated the same in accordance with the Benchmark Criteria. Statement of Work 44 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 28. Customer Functional Testing Task Description The Customer, with on -site and remote support from Hexagon, will conduct test of the Dispatch Cloud Program's conformance with the Benchmark Criteria. The Customer will conduct Functional Testing over the course of thirty (30) days ("Testing Period"). During the Testing Period, the Customer shall execute the Test Plan. No subsequent testing or evaluation is contemplated in this Project. Hexagon and the Customer will jointly document and track the results of each Test Case as either pass or fail. Within five (5) business days of the end of the Testing Period, the Customer shall provide the Hexagon Project Manager a written report of any Blocker Errors encountered during Functional Testing ("Blocker Report"), if any. For any Blocker Error identified in the Blocker Report, the Customer shall provide, at minimum, the following information: a description of the Error and the steps used to reproduce it, the functionality tested when the Blocker Error was encountered, the manner in which the functionality was tested, and the outcome when the functionality was tested. If the Blocker Report is not provided to Hexagon within the time allotted, it is presumed Functional Testing was completed without any Blocker Error, and this Task is complete. The Customer may report Permissive Errors to Hexagon through Hexagon's Customer Resource Management (CRM) system, which will be addressed in accordance with the Agreement. The existence of Permissive Error(s) shall not preclude or be a condition of completion of any subsequent Tasks or implementation of a new Release. To the extent requested, Customer agrees to promptly respond to requests for additional information regarding the Blocker Error requested by Hexagon. Upon diagnosing the Blocker Error and validating the Error encountered meets the attributes of a Blocker Error, Hexagon resources shall proceed to resolve the Blocker Error accordingly. If the investigation determines the reported Blocker Error did not meet the attributes of a Blocker Error then the reported Error will be reclassified in accordance with the levels provided in the Master Terms Glossary. Alternatively, if the investigation shows the reported Blocker Error was caused by Customer hardware, Network Infrastructure, or Third Party Software not provided by Hexagon, or non-conformance with Attachments E and F, then Hexagon will provide such information to the Customer for the Customer to resolve and the Blocker Error will be closed and regarded as complete. As part of its resolution efforts, Hexagon may at its discretion provide a procedural or programmatic work around, a configuration change, or provide an Update. Once the Blocker Error(s) is addressed, Hexagon will report to Customer the Blocker Error has been addressed and the Customer will have five (5) Business Days to execute its Test Plan ("Resolution Testing Period"). Task Deliverables • Hexagon remote support services Two (2) 32-hour weeks of on -site support from a CAD Engineer • One (1) 32-hour week of on -site support from a Mobile/Interfaces Engineer • OnCall Dispatch/Mobile Functional Testing Task Prerequisites O Completion of all prior Tasks Customer and Hexagon mutual confirmation that OnCall Dispatch and Mobile Unit are ready for testing a-, Development of the Test Plan Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Hexagon Team Participation and Responsibilities Hexagon shall: • Verify the Dispatch Cloud Program and Local Software Server are ready for functional testing • Provide on -site and remote support during Functional Testing • Review any Errors identified in the Blocker Report by the Customer • Resolve Blocker Errors identified in the Blocker Error Report Customer Team Participation and Responsibilities Customer shall: Verify the Dispatch Cloud Program and Local Software Server are ready for functional testing Execute the Test Plan Track and document results from executed Test Cases and provide Hexagon a Blocker Report If applicable or desired, re -execute Test Cases during the Resolution Testing Period. Task Acceptance Criteria This Task is complete upon completion of the Testing Period and resolution of all Blocker Errors identified in the Blocker Report. Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 29. Hexagon -Led Training Task Description During this Task, Hexagon resources will conduct Administrative and Train -the -Trainer sessions for Customer -designated personnel. The following formal training classes are included in the Project ("Hexagon Training Classes"): HxGN OnCall Dispatch System Administrator Training (on site) — Qty: 1 HxGN OnCall Dispatch Train -The -Trainer (on site) — Qty: 4 Note Video Responder training is included with this training • HxGN OnCall Dispatch Viewer Train -The -Trainer (remote) — Qty: 4 • HxGN OnCall Dispatch Mobile Unit Train -The -Trainer (on site) — Qty: 4 • HxGN OnCall Dispatch Mobile Responder Train -The -Trainer (remote) — Qty: 4 • HxGN OnCall Analytics Dispatch User Training (on site) — Qty: 1 • HxGN OnCall Analytics Dispatch System Administrator Training (on site) — Qty: 1 Please see Attachment D, Training Curriculum for course descriptions and quantities. It is recommended that Customer develop its own training program, including, but not limited to: creating a training plan suitable for its needs, identifying a training cadre for both Dispatcher and Mobile disciplines, and leveraging the Hexagon training materials and Documentation to ensure its Users have acquired the necessary knowledge and are in a position to use the Dispatch Cloud Program upon Cutover. The Customer is solely responsible for training its Users. The Customer shall complete its User Training (no later than sixty (60) calendar days after Hexagon has completed the Hexagon Training Classes ("End User Training Period"). Task Deliverables • Training course agendas • Applicable COTS Documentation for training for the Hexagon Training Classes Task Prerequisites • Customer has identified and secured an appropriate training room and set up with the workstations, at least one (1) LCD projector, display screen or other appropriate surface to display a projected image, and white -board space or other ability to take notes and record questions The Customer has installed and configured at least one (1) workstation for use by the Hexagon instructor during the sessions The Customer has installed and configured at least one (1) workstation per student attending the session Task Assumptions • The Customer will complete end user training within the End User Training Period Both end -user training and train -the trainer training will be provided as specifically identified herein. Training will take place during normal business hours, which is typically from 8:00 am - 5:00 pm, and will not exceed eight (8) hours per 24-hour period. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation • Training documentation provided by Hexagon with this SOW will be standard COTS Documentation and help files and will not be customized to the Customer's site -specific configuration. All Documentation will be provided in electronic format. Should printed copies be required, the Customer is responsible for providing them Hexagon Team Participation and Responsibilities Hexagon shall: • Conduct Hexagon Training Classes Customer Team Participation and Responsibilities Customer shall: • Provide appropriate facilities and install/configure workstations as indicated in the prerequisites to be used during training • Ensure appropriate personnel participate in the Hexagon Training Courses • Complete end user training within the End User Training Period Task Acceptance Criteria This Task is complete once Hexagon has delivered the Hexagon Training Classes to the Customer. Statement of Work 55 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 30. Replicate Cloud Environments Task Description Up to this point in the Project, the Project has focused on creating the Cloud Development Environment, configuring, and testing the Dispatch Cloud Program in the Development Environment, which was the only Cloud Environment available. Following achievement of a Production Ready System, Hexagon will replicate the Production Ready System in the newly created Staging Environment, Production Environment, and Training Environment. This Task is intended to be completed within five (5) Business Days prior to scheduled Cloud Cutover. Task Deliverables Replication of Production Ready System in a Staging Environment, Production Environment, and Training Environment Task Prerequisites Achievement of Production Ready System Task Assumptions This Task is intended to be completed within five (5) Business Days prior to scheduled Cloud Cutover. Hexagon Team Participation and Responsibilities Hexagon shall: Hexagon resources will replicate the Production Ready System in a Staging Environment, Production Environment, and Training Environment Customer Team Participation and Responsibilities • None Task Acceptance Criteria This Task is considered complete when Hexagon has replicated the Production Ready System into the Staging Environment, Production Environment, and Training Environment. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 31. Cloud Cutover Plan Task Description Cloud Cutover is a significant event, and this Task is intended to provide the Customer COTS Documentation in the form of a Cutover Plan to assist the Customer in preparation for Cloud Cutover. The Cutover Plan will detail the steps necessary for Cloud Cutover. To ensure Cloud Cutover goes as smoothly as possible, the Cutover Plan identifies the events immediately leading up to Cloud Cutover and the type of resource intended to accomplish that Task. The Cutover Plan covers topics including: Customer staffing, movement of equipment into final locations, procedures to report issues, and planned sequence of events for the day of Cloud Cutover. Hexagon will provide the Cutover Plan at the commencement of Functional Testing to Customer's Project Manager. To the extent the Customer modifies or alters the Cutover Plan, the Customer shall provide it to Hexagon no less than five (5) Business Days prior to scheduled Cloud Cutover in the then most current Project Schedule. Task Deliverables Cutover Plan Task Prerequisites • Completion of all Functional Testing Task Prerequisites Task Assumptions • None Hexagon Team Participation and Responsibilities • Hexagon shall provide Customer's Project Manager with Hexagon's Cutover Plan Customer Team Participation and Responsibilities Customer shall review the Cutover Plan If the Cutover Plan is modified, the Customer will return its final copy of the Cutover Plan to Hexagon's Project Manager no later than five (5) Business Days prior to scheduled Cloud Cutover Task Acceptance Criteria Hexagon has completed its obligations under this Task when it has delivered the Cutover Plan to Customer's Project Manager. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 32. Cloud Program Readiness Review Task Description As part of final preparations for Cloud Cutover, Hexagon and the Customer will hold a six (6) hour meeting to verify the teams and the Dispatch Cloud Program are ready for Cloud Cutover ("Cloud Program Readiness Review"). During the Cloud Program Readiness Review, a Hexagon technical resource, the Hexagon Project Manager, and the Customer Core Team will meet remotely and validate the Cloud Program is ready for Cloud Cutover, confirm and walk through the final Cutover Plan and related Cloud Cutover Activities, and finalize Cloud Cutover preparations. Task Deliverables • Hosting of Cloud Program Readiness Review Task Prerequisites r All prior Tasks must be completed. This meeting will take place remotely via conference call. Task Assumptions The Customer has trained all of its Users (-, Customer has notified internal and external stakeholders about pending Cloud Cutover Hexagon Team Participation and Responsibilities Hexagon shall: ® Host and facilitate the Cloud Program Readiness Review • Address the topics in the Cloud Program Readiness Review • Address other Customer questions related to Cloud Cutover Customer Team Participation and Responsibilities The Core Team, and applicable members of Customer's training cadre (if formed) will attend and participate in the Cloud Program Readiness Review Task Acceptance Criteria This Task is complete when the Cloud Program Readiness Review has been conducted. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 33. Cloud Cutover to Production Use Task Description During this Task, Hexagon personnel will assist the Customer with placing the Dispatch Cloud Program into production use. Cloud Cutover is the culmination of the Tasks that comprise this SOW. Before Cloud Cutover, the Customer shall have completed the preceding Tasks. Although the Customer may use the Cloud Program at any time after IOC, Cloud Cutover reflects the point at which the Cloud Program has been configured, had Interfaces installed, completed Functional Testing, and the Customer has trained all of its end users. Hexagon will provide SMEs on site for five (5) days to assist the Customer. Task Deliverables • Dispatch Cloud Program in production use Task Assumptions (" All prior Tasks must be completed The End User Training Period has concluded Hexagon and the Customer agree that Cloud Cutover can proceed First year maintenance of Hexagon Local Software, CommSys software, and Deccan software will begin upon Cloud Cutover/Cutover Cutover will take place on the day and time specified in the Cloud Cutover Plan If Cloud Cutover cannot take place due to issues within the control of the Customer or as a result of a third -party Customer vendor, there may be a cost associated with re- scheduling the Cloud Cutover Hexagon Team Participation and Responsibilities Hexagon shall: Provide SMEs on site for five (5) days Customer Team Participation and Responsibilities Customer shall: * Ensure availability of trained end users • Ensure availability of Core Team during Cloud Cutover activities • Ensure availability of all third -party vendors impacted by the Cloud Cutover ® Ensure availability of all IT disciplines necessary to immediately address issues as necessary Task Acceptance Criteria This Task will be complete when Cloud Cutover for the Dispatch Cloud Program has occurred. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 34. Post-Cutover Support Task Description During this Task, Hexagon resources will provide Post-Cutover support to Customer. The "Post-Cutover Support Period" is the ten (10) business days beginning the week following Cloud Cutover and conducted on site for Week 1 and remotely for Week 2. It is designed to provide the Customer with dedicated, quickly accessible support for questions and errors encountered in the ten (10) business days following the Cutover to production use of the new System. During this Task, Hexagon resources will be assigned Blocker Errors that are filed by the Customer against the Dispatch Cloud Program. Hexagon resources will work to identify and address the Blocker Errors reported. The Post-Cutover Support Period is not a configuration period. Requests for new configurations that are not related to addressing an Error will not be supported during this time frame and Hexagon shall have no responsibility to address or support any such requests. This is done to ensure the stability of the System delivered and that focus remains on Errors and to minimize the introduction of new opportunities for errors or problems. Task Deliverables Task Completion Form confirming that Post-Cutover Support has been provided in accordance with SOW Post-Cutover Support task description Task Prerequisites • Cloud Cutover to Production Use Task Assumptions • Post-Cutover Support is provided Monday -Friday during normal business hours. Standard after- hours emergency support procedures, defined in the Cloud Cutover Plan, remain the same for the duration of this task Errors will be reported via Hexagon's designated CRM tool The Customer System Administrator remains the primary point of contact and initial troubleshooting point of contact for all issues during this task The Customer System Administrator maintains responsibility for core system administration tasks Hexagon Team Participation and responsibilities Hexagon shall: 6 Provide ten (10) business days of Post-Cutover support in accordance with this SOW • Address Blocker Errors Customer Team Participation and Responsibilities Customer shall: Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Ensure Errors are recorded in Hexagon's CRM tool in a timely manner and in accordance to the mutually agreed upon Project Schedule. Task Acceptance Criteria This Task is complete when the Post-Cutover Support Period has expired. Statement of Work 61 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Terms and Conditions The terms and conditions governing this SOW are set forth in, that certain agreement titled, "City of Miami's Supplemental Agreement to Master Terms and Conditions of Intergraph Corporation through its Safety & Infrastructure division" as modifying that certain contract between Hexagon and Lee County dated February 11, 2021 (collectively, the "Agreement"). The Agreement (including the agreement between Hexagon and Lee County are incorporated herein by reference. Statement of Work 62 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Approval Signatures Signature by all parties listed below constitutes acceptance of and notice to proceed with this Cloud Consulting Services Order, and the Cloud Program Sales Order (reflected in the Quote (Attachment A)). This SOW may be executed in one or more counterparts, each of which shall be deemed to be original, and all of which together shall constitute one and the same agreement. A signature delivered by facsimile shall be deemed to be an original signature and shall be effective upon receipt thereof by the other party. This document is approved by: AUTHORIZED HEXAGON SIGNATURE Name: Debra T. Huser, North America Finance Director Hexagon Safety & Infrastructure Signature: Date: AUTHORIZED CUSTOMER SIGNATURE Name: Signature: Date: Statement of Work 63 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation AttachmentA— Pricing Summary Pricing provided below is valid through 3/31/2022. Description Quantity Number of Months Extended Price (CY1- CY2) OnCall Dispatch System Cloud Software HxGN OnCall Dispatch - RestAPl - Cloud 1 24 $ 28,103 HxGN OnCall Dispatch - RestAPl - Cloud - TRN 1 24 $ 21,439 HxGN OnCall Dispatch - Informer - Cloud 1 24 $ 13,018 HxGN OnCall Dispatch - Informer - Cloud - TRN 1 24 $ 9,945 HxGN OnCall Dispatch - Fire Station Alerting - Cloud 1 24 $ 5,967 HxGN OnCall Dispatch - Deccan LiveMUM Interface - Cloud 1 24 $ 2,945 HxGN OnCall Dispatch - CAD Link Interface - Cloud 1 24 $ 5,967 HxGN OnCall Dispatch - Call -Taker Interface - CLD 1 24 $ 2,867 HxGN Connect Video - Streamer VMS - Subscription 1 24 $ 9,454 HxGN Connect Interface - Milestone VMS - SU 1 24 $ 4,520 HxGN OnCall Analytics - Dispatch Data Models & Reports — CLD 1 24 $ 1,214 HxGN OnCall Dispatch - DEV - CLD 1 24 Included HxGN OnCall Dispatch - STG - CLD 1 24 Included HxGN OnCall Analytics - DEV - CLD 1 24 Included HxGN OnCall Analytics - STG - CLD 1 24 Included HxGN OnCall Integration Engine 1 24 $ 16,918 HxGN OnCall Integration Engine - Training 1 24 $ 1,550 Xalt Runtime Engine NL - Subscription 1 24 $ 21,981 Xalt Runtime Engine NL - Subscription - BCK 1 24 $ - Xalt Runtime Engine NL - Subscription - TST 1 24 $ - Xalt Runtime Engine NL - SU - Training License 1 24 $ 16,970 HxGN OnCall Dispatch - Customer Rules Engine Editor - CLD 1 24 $ 4,774 HxGN OnCall Dispatch - Customer Rules Engine Editor— CLD - TRN 1 24 $ 3,652 HxGN OnCall Dispatch - Customer Rules Engine Server - CLD 1 24 $ HxGN OnCall Dispatch - Customer Rules Engine Server — CLD -TRN 1 24 $ - Total: $ 171,284 Miami City Police Department Client Cloud Software HxGN OnCall Dispatch - Advantage - Cloud 15 24 $ 230,533 HxGN OnCall Dispatch - Advantage - Cloud - TRN 10 24 $ 123,984 HxGN OnCall Dispatch - Advanced Mapping - Cloud 15 24 $ 77,103 HxGN OnCall Dispatch - Advanced Mapping - Cloud - TRN 10 24 $ 45,719 HxGN OnCall Dispatch - Video Responder Advantage - CLD 15 24 $ 61,217 HxGN OnCall Dispatch - Video Responder Advantage - CLD 10 24 $ 34,096 Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Description - TRN Quantity Number of Months Extended Price (CY1- CY2) HxGN OnCall Dispatch - Essentials - Cloud 14 24 $ 150,072 HxGN OnCall Dispatch - Essentials - Cloud - TRN 10 24 $ 88,339 HxGN OnCall Dispatch - Viewer - Cloud 50 24 $ 255,717 HxGN OnCall Dispatch - Viewer - Cloud - TRN 10 24 $ 45,461 HxGN OnCall Dispatch - Call -Taker - Cloud 14 24 $ 74,494 HxGN OnCall Dispatch - Call -Taker - Cloud - TRN 10 24 $ 47,269 HxGN OnCall Dispatch - Tracker - Cloud 1600 24 $ 330,624 HxGN OnCall Dispatch - ProQA Interface - Subscription 14 24 $ 7,232 HxGN OnCall Dispatch - ProQA Interface - Subscription-BCK 14 24 $ - HxGN OnCall Dispatch - ProQA Interface - Subscription — TRN 10 24 $ 3,875 HxGN OnCall Dispatch - ProQA Interface - Subscription — TST 14 24 $ - HxGN OnCall Dispatch - Video Responder Essentials - CLD 14 24 $ 47,734 HxGN OnCall Dispatch - Video Responder Essentials - CLD- TRN 10 24 $ 30,738 HxGN OnCall Dispatch - Mobile Unit - Cloud 250 24 $ 452,025 HxGN OnCall Dispatch - Mobile Unit - Cloud - TRN 10 24 $ 15,498 HxGN OnCall Analytics - Viewer - Cloud 50 24 $ 40,037 HxGN OnCall Analytics - Author - Cloud 5 24 $ 10,719 HxGN OnCall Dispatch - Mobile Responder Client - Cloud 150 24 $ 228,596 HxGN OnCall Dispatch - Mobile Responder Client - Cloud — TRN 10 24 $ 13,432 HxGN OnCall Dispatch - Customer Rules Engine Client - CLD 79 24 $ 71,808 HxGN OnCall Dispatch - Customer Rules Engine Client — CLD - TRN 30 24 $ 21,527 Total: $ 2,507,846 Miami City Fire Department Client Cloud Software HxGN OnCall Dispatch - Advantage - Cloud 8 24 $ 122,951 HxGN OnCall Dispatch - Advantage - Cloud - TRN 6 24 $ 74,390 HxGN OnCall Dispatch - Advanced Mapping - Cloud 8 24 $ 41,121 HxGN OnCall Dispatch - Advanced Mapping - Cloud - TRN 6 24 $ 27,431 HxGN OnCall Dispatch - Essentials - Cloud 2 24 $ 21,439 HxGN OnCall Dispatch - Essentials - Cloud - TRN 2 24 $ 17,668 HxGN OnCall Dispatch - Viewer - Cloud 50 24 $ 255,717 HxGN OnCall Dispatch - Viewer - Cloud - TRN 6 24 $ 27,276 HxGN OnCall Dispatch - ProQA Interface - Subscription 8 24 $ 4,133 HxGN OnCall Dispatch - ProQA Interface - Subscription-BCK 8 24 $ - HxGN OnCall Dispatch - ProQA Interface - Subscription — TRN 6 24 $ 2,325 HxGN OnCall Dispatch - ProQA Interface - Subscription — TST 8 24 $ Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Number Extended Description Quantity of Price (CY1- Months CY2) HxGN OnCall Dispatch - Mobile Unit - Cloud 15 24 $ 27,122 HxGN OnCall Dispatch - Mobile Unit - Cloud - TRN 6 24 $ 9,299 HxGN OnCall Analytics - Viewer - Cloud 50 24 $ 40,037 HxGN OnCall Analytics - Author - Cloud 5 24 $ 10,719 HxGN OnCall Dispatch - Mobile Responder Client - Cloud 85 24 $ 129,537 HxGN OnCall Dispatch - Mobile Responder Client - Cloud — 6 24 $ 8,059 TRN HxGN OnCall Dispatch - Customer Rules Engine Client - 60 24 $ 54,537 CLD HxGN OnCall Dispatch - Customer Rules Engine Client — 14 24 $ 10,046 CLD - TRN Total: $ 883,807 Custom Interfaces OnCall Dispatch Xalt Import Interface to Hydrant 1 NA $ 18,118 OnCall Dispatch Xalt Interface to Traffic Management System (Signal Pre-emption) 1 NA $ 34,305 OnCall Dispatch Xalt Import Interface to Telestaff 1 NA $ 14,077 OnCall Dispatch Informer Query Interface to Motorola RMS 1 NA $ 23,039 WebEOC CAD Interface 1 NA $ 14,467 External Alarms OnCall Dispatch Interface (Shotspotter & APCO ASAP) - SU 1 24 $ 9,464 Dispatch Alerts OnCall Interface (Everbridge Paging) - SU 1 24 $ 6,168 PLT Radio OnCall Dispatch Interface (Harris P25 Radio) — SU 1 24 $ 6,168 RapidSOS OnCall Call -Taker Interface - SU 1 24 $ 4,520 Total: j $ 130,327 Project Services & Third Party CommSys ConnectCIC v2.9 w/ASAP 1 NA $ 23,500 Deccan LiveMUM 1 NA $ 249,153 Project Implementation (including installation, testing, training and associated travel) 1 NA $ 1,302,897 Total: 1 $ 1,575,550 2 Year Contract Value 1 $ 5,268,814 Recurring Costs Software Maintenance CY3/MY2 1 NA $ 87,650 Software Maintenance CY4/MY3 1 NA $ 92,032 Software Maintenance CY5/MY4 1 NA $ 96,634 Subscription Renewal Fee CY3/MY2 1 12 $ 1,925,890 Subscription Renewal Fee CY4/MY3 1 12 $ 2,022,184 Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Number Extended Description Quantity of Price (CY1- Months CY2) Subscription Renewal Fee CY5/MY4 1 12 $ 2,123,293 Total, $ 6,347,684 5 Year Contract Value $ 11,616,498 Options Fire Department Only) HxGN OnCall Dispatch - Tracker - Cloud CY1 150 12 $ 14,400 HxGN OnCall Dispatch - Tracker - Cloud CY2 150 12 $ 15,120 HxGN OnCall Dispatch - Tracker - Cloud CY3 150 12 $ 15,876 HxGN OnCall Dispatch - Tracker - Cloud CY4 150 12 $ 16,668 HxGN OnCall Dispatch - Tracker - Cloud CY5 1 150 1 12 1 $ 17,496 Total: 1 $ 79,560 Statement of Work 67 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment B — Payment Schedule On or after the completion of the Tasks identified below, Hexagon shall invoice the Customer the corresponding amounts set forth below for Services and Local Software, which Customer shall pay in accordance with the Agreement: TASK AMOUNT Upon Completion of Task 1: Project Kickoff Meeting $168,779.62 Upon Completion of Task 14: OnCall Map Service Configuration and Consulting Services $253,169.43 Upon Completion of Task 9: OnCall Dispatch System Build 3 $168,779.62 Upon Completion of Task 18: OnCall Dispatch Configuration Follow-up Workshop $253,169.43 Upon Completion of Task 24: OnCall Dispatch COTS Interface Installation $168,779.62 Upon Completion of OnCall Dispatch Analytics Training (see Task 29) $253,169.43 Upon Completion of OnCall Dispatch Mobile Unit Train the Trainer class (see Task 29) $253,169.43 Upon Completion of Task 33: Cloud Cutover to Production Use $168,779.62 Total $1,687,796.22 For purposes of clarity, the subscription fee amount for the first year of the Cloud Program is $1,746,839, and the amount for the second year of the Cloud Program is $1,834,181 are due in accordance with the Master Terms. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment C — Initial Project Schedule BUSINESS TASK NAME Miami City Police and Fire OnCall Dispatch (Cloud Hosted) Project Project Initiation Hexagon provides initial project schedule to Customer Customer reviews/approves updated initial project schedule DURATION DAYS SINCE START 456 days 0 days 28 days 1 day 1 day 6 days 7 days 5 days Hexagon submits updated project schedule to Customer 1 day 11 days Customer reviews/approves updated final project schedule 3 days 12 days Initial Operation Capability (IOC) Phase Project Kickoff Meeting Kickoff Meeting and Deliver COTS Interface Questionnaires Deliver Project Kickoff Meeting Notes COTS Interface Questionnaires Completion 27.5 days 3 days 20 days 30 days 31 days 32 days 1 day 1 day 22 days 20 days Questionnaire Follow-up 1 day 32 days Customer completes COTS Interface Questionnaires 5 days 37 days OnCall Dispatch and Mobile Unit Launch OnCall Dispatch Map Overview Creation of Cloud Environment 6 days 33 days 39 days 40 days 1 day 1 day IOC Completion 2.5 days 45 days Hexagon Hosts Credentials Delivery Meeting 0.5 days 45 days Hexagon Delivers Credentials/License Keys to Customer 0.5 days 45 days Customer Confirms Log into Dispatch Cloud Program 1 day 45.5 days Final Operating Capability (FOC) Phase 423.75 days 32 days OnCall Dispatch System Build 1 20 days 39 days Customer Completes Data Import Worksheet 7 days 39 days OnCall Dispatch System Build Session #1 5 days 49 days Customer System Build Period 5 days 54 days OnCall Dispatch System Build 2 OnCall Dispatch System Build Session #2 Customer System Build Period OnCall Dispatch System Build 3 11 days 5 days 59 days 60 days 65 days 5 days 11 days 70 da s Statement of Work 69 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation BUSINESS ohTASK NAME DURATION DAYS SINCE STARm &= — T OnCall Dispatch System Build Session #3 5 days 71 days Customer System Build Period 5 days 76 days Custom Interface Requirements Gathering (ICD) 255 days 32 days Hexagon and Custom Interface Meeting 1.25 days 32 days Hexagon and Customer Interface Meeting to validate assumptions and design of Custom Interfaces 0.25 days 1 day 32 days 32.25 days Hexagon Delivers Interface Meeting Minutes to Customer Customer Planning Tasks Provide Interface Connections Coordinate Third -Party Vendors for Interfaces 11.26 days 0.25 days 1 day 32 days 32 days 32.25 days Coordinate Third -Party Vendors NDAs 10 days 33.25 days Query Interface to Motorola RMS ICD Development 17 days 43.25 days Query Interface to Motorola RMS ICD Development 2 days 43.25 days ICD Delivered to Customer Customer Reviews ICD 1 day 45.25 days 46.25 days 10 days Hexagon updates ICD based off Customer Review 1 day 56.25 days ICD Si noff 3 days 57.25 days Interface to Hydrant ICD Development 17 days 270 days Interface to Hydrant ICD Development 2 days 270 days ICD Delivered to Customer Customer Reviews ICD 1 day 272 days 273 days 10 days Hexagon updates ICD based off Customer Review 1 day 283 days ICD Si noff 3 days 284 days Interface to Traffic Management System ICD Development 18 days 46.25 days Interface to Traffic Management System ICD Development 2 days 46.25 da s ICD Delivered to Customer Customer Reviews ICD 1 d ay_�46.25 days 10 days 1 46.25 days , Hexagon updates ICD based off Customer Review 2 days 59.25 days ICD Si noff 3 days 61.25 days Interface to Telestaff ICD Development 17 days 61.25 days Interface to Telestaff ICD Development 2 days 61.25 days ICD Delivered to Customer 1 day 63.25 days Statement of Work 70 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation DURATION BUSINESS DAYS SINCE START _ Customer Reviews ICD 10 days 64.25 days Hexagon updates ICD based off Customer Review 1 day 74.25 days ICD Signoff 3 days 75.25 days Connectivity to Cloud Program 1 day 47.5 days Establish VPN Tunnel 1 day 47.5 days 1 day 47.5 days Ping Message sent from the Customer is received by the Cloud Program 1 day Ping Message sent from the Cloud Program is received by the 47.5 days Customer _ On Premise Local Software Server Installation and 16.63 days 32 days Configuration 5 days OnCall Map Service Configuration and Consulting Services 47.5 days Informer Setup (CommSys) 1 da 33 days OnCall Dispatch Police Configuration Consulting Session 17.5 days 81 days OnCall Dispatch Configuration Session - Layout Manger, 4 days 82.5 days Custom Fields, Unit & Event Boards, Parameter Setting, Notification Settings OnCall Mapping Consulting 2 - Decoding, Routing, Map 1 day 86.5 days _Display Customer Configures OnCall Dispatch 10 days 87.5 days 98.5 days OnCall Dispatch Fire Configuration Consulting Session 27.5 days OnCall Dispatch Configuration Session - Layout Manger, 4 days 100 days Custom Fields, Unit & Event Boards, Parameter Setting, Notification Settings OnCall Mapping Configuration Session - Decoding, Routing, 1 day 104 days Map Display Customer Configures OnCall Dispatch 10 days 105 days 126 days OnCall Dispatch Configuration Follow -Up Workshop 6 days OnCall Dispatch Customer Rules Engine (CRE) 23 days 132 days 141 days CRE Configuration Workshop 4 days 145 days Customer Configures CRE 10 days 98.5 days OnCall Dispatch I Mobile Unit Police Configuration 46.5 days Consulting Session OnCall Dispatch Mobile Unit Consulting - Layout Manger, 6 days 99 days Custom Fields, Unit & Event Boards, Parameter Setting, Notification Settings Statement of Work 71 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation BUSINESS TASK NAME DURATION DAYS SINCE START JL Customer Configures Mobile Unit 10 days 105 days Support Customer Configuration/Config Audit and Review 10 days 115 days Customer Configures Mobile Unit 10 days 125 days Support Customer Configuration/Config Audit and Review 10 days 135 days OnCall Dispatch I Mobile Unit Fire Configuration Consulting 46 days Session OnCall Dispatch Mobile Unit Consulting - Layout Manger, 6 days Custom Fields, Unit & Event Boards, Parameter Setting, Notification Settings Customer Configures Mobile Unit 10 days 105 days 105 days 111 days Support Customer Configuration/Config Audit and Review 10 days 121 days Customer Configures Mobile Unit 10 days 131 days Support Customer Configuration/Config Audit and Review OnCall Dispatch Mobile Responder Police Consulting Session OnCall Mobile Responder Consulting Session - Application Settings, Parameters, Statues, Unit Properties, Disposition Types, Event Types, Filters Hexagon Configures Mobile Responder - Police 10 days 141 days 145 days 145 days 6 days 1 day 5 days 146 days OnCall Dispatch Mobile Responder Fire Consulting Session 8 days 1 day 151 days 151 days OnCall Mobile Responder Consulting Session - Application Settings, Parameters, Statues, Unit Properties, Disposition Types, Event Types, Filters Customer Configures Mobile Responder - Fire 5 days 152 days COTS Interface Product Installation and Configuration 33.5 days 270 days Custom Interface Product Development and Implementation Standard Interface Product Development and Implementation Harris P25 Radio ShotSpotter 232.75 days 188.75 days 60.25 days 82.25 days 107.25 days 1 day 1 day 108.25 days ASAP RapidSOS Everbridge WebEOC ALPR Consulting Services 2 days 109.25 days 1 day 111.25 days 1 day 112.25 days 1 day 113.25 days 208 days 1 day Statement of Work 72 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation BUSINESS TASK NAME DURATION DAYS SINCE START IL Develop Test Plan and Test Cases 30.13 days 157 days Customer creates a Test Plan with Test Cases 30 days 157 days Customer provides Test Plan and Test Cases to Hexagon 0.13 days 187 days Customer Functional Testing 42 days 293 days Customer Conducts Functional Testing Post Customer written report on Blocker Errors - Follow Up Customer Executes Test Plan (Resolution Testing Period) Hexagon -Led Training 30 days 294 days 324 days 326 days 2 days 4 days 56.03 days 4 days 335 days 336.5 days OnCall Dispatch System Administrator Training OnCall Dispatch TTT - Police #1 4 days 342 days OnCall Dispatch TTT - Police #2 4 days 349.01 days OnCall Dispatch TTT - Fire #1 OnCall Dispatch TTT - Fire #2 4 days 356.02 days 363.03 days 4 days OnCall Dispatch Viewer TTT — Police #1 1 day 346.26 days OnCall Dispatch Viewer TTT — Police #2 1 day 353.27 days OnCall Dispatch Viewer TTT — Fire #1 1 day 360.28 days OnCall Dispatch Viewer TTT — Fire #2 OnCall Dispatch Mobile Unit TTT — Police #1 OnCall Dispatch Mobile Unit TTT — Police #2 1 day 367.29 days 368.28 days 370.53 days 2 days 2 days OnCall Dispatch Mobile Unit TTT — Fire #1 2 days 373.78 days OnCall Dispatch Mobile Unit TTT — Fire #2 2 days 376.03 days OnCall Dispatch Mobile Responder TTT — Police #1 1 day 378.28 days OnCall Dispatch Mobile Responder TTT — Police #2 OnCall Dispatch Mobile Responder TTT — Fire #1 OnCall Dispatch Mobile Responder TTT — Fire #2 1 day 379.53 days 380.78 days 382.03 days 1 day 1 day OnCall Analytics User and SysAdmin Training 3 days 386.03 days Customer Led End User Training Customer Led End User Training (60 Calendar Days = 42 Business Days) Replicate Cloud Environments Cloud Cutover Plan Cloud Program Readiness Review 42 days 391.03 days 42 days 391.03 days 431 days 2 days 30.29 days 391.03 days 0.61 days 433.03 days Statement of Work 73 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation BUSINESS TASK NAMIEMIL DURATION DAYS SINCE START _ Cloud Cutover to Production Use Post Cutover Post Cutover 6 days 437 6 days 1 443 5 days 1 449 Statement of Work 74 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment D —Training Curriculum HxGN OnCall Dispatch I Advantage System Administrator Training (Qty: ILA The HxGN OnCall Dispatch I Advantage System Administrator course is a four -day, hands-on training class on how to configure and manage the OnCall system. During this course, the students will learn how to access the Dispatch Cloud Program and use available tools to administer and configure the system. MAJOR TOPICS • Understanding the Environment • Deployment Configuration • Map Legend Management • Response Plans Configuration • UI Editor • Role Management • Localized Strings • Type Codes Management • Layout Manager • Agency Management • Notification Configuration • Geographic Custom Fields Resources Parameter Management Change Management PREREQUISITES Customer Cloud Environment fully staged and available HxGN OnCall Dispatch I Advantage fully licensed, staged, and available Credentials available Hexagon user account provisioned with local administrator rights on all appropriate workstations TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience Personnel responsible for administering and supporting the system Duration Four(4)days Student Capacity Six (6) Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation HxGN OnCall Dispatch I Advantage Train -the -Trainer (Qty: 4) for Police, HxGN OnCall Dispatch I Advantage Train -the -Trainer is a four -day comprehensive course to familiarize communications personnel with the use of OnCall. Students will learn all of the essential functions of OnCall including navigating the application, entering and updating events, performing inquiries, handling units including updates and status changes, and communicating with other users. An introduction to the use of interfaces to such things as NCIC, state crime databases, and mobile units is also presented, if the interfaces are available. Students completing the course should have a good working knowledge of using HxGN OnCall Dispatch I Advantage. MAJOR TOPICS • Events — Creation, Updates, and Status Changes Mapping — Commands, Controls, and Views Units — Status Changes and Properties Updates • Inquiries — Events, Units, and Employees • Messaging — Send, Receive, and Attachments • Using training guidelines and techniques for HxGN OnCall Dispatch I Advantage PREREQUISITES • Customer Cloud Environment fully staged and available • HxGN OnCall Dispatch I Advantage fully licensed, staged, and available • Credentials available • Hexagon user account provisioned with local administrator rights on all appropriate workstations TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience Personnel responsible for training call -taking and dispatching staff Duration Four(4)days Student Capacity Twelve (12) Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation HxGN OnCall Dispatch• for Police, COURSE OVERVIEW HxGN OnCall Dispatch I Viewer for Trainers is a one -day comprehensive course to familiarize communications trainers with the use of OnCall Viewer. Students will learn all of the essential functions of Viewer including navigating the application, viewing events and units, performing inquiries, and reading messages. Documentation needs will be discussed to identify customizations the trainers may want to make to their own materials to better facilitate training their specific scenarios and configurations. Training best practices will also be part of the curriculum, to ensure the trainers are ready to begin training their own users. MAJOR TOPICS Events — Viewing and Searching Mapping — Commands, Controls, and Views • Units — Viewing and Searching • Inquiries — Events, Units, and Employees • Messaging • Documentation and training materials review and discussion • Using training guidelines and techniques for HxGN OnCall Dispatch Viewer PREREQUISITE,' • Customer Cloud Environment fully staged and available • HxGN OnCall Dispatch I Viewer fully licensed, staged, and available • Credentials available for all students and instructors • Hexagon user account provisioned with local administrator rights on all appropriate workstations TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience Personnel responsible for training call -taking and dispatching staff Duration per Course One (1) day Student Capacity Twelve (12) Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation HxGN OnCall Dispatch•• • for Police, COURSE OVERVIEW HxGN OnCall Dispatch I Mobile Unit Train -the -Trainer is a two-day comprehensive course to familiarize trainers with the operation and use of the HxGN OnCall Dispatch I Mobile Unit software. Trainers will learn all of the essential functions of HxGN OnCall Dispatch I Mobile Unit including navigating the application, creating, receiving and updating events, utilizing the map, performing inquiries, handling units including updates and status changes, and communicating with other users. Trainers completing the course should have a good working knowledge of HxGN OnCall Dispatch I Mobile Unit. MAJOR TOPICS • Create, receive and update active events • Update active unit status and properties • Submitting inquires for events and units • Submitting and receiving messages • Create and receive HxGN OnCall Dispatch I Informer queries from HxGN OnCall Dispatch Mobile Unit • Using training guidelines and techniques for HxGN OnCall Dispatch I Mobile Unit PREREQUISITE, • Customer mobile hardware fully staged and available • HxGN OnCall Dispatch I Advantage and HxGN OnCall Dispatch I Mobile Unit fully licensed, staged, and available • Credentials available • Hexagon user account provisioned with local administrator rights on all workstations • Customer Data collection spreadsheets completed • HxGN OnCall Dispatch I Advantage and HxGN OnCall Dispatch I Mobile Unit fully staged and available on the trainer's workstation COURSE DETAILS Method Conducted on site by Hexagon Personnel Target Audience Personnel responsible for training the field personnel that respond to CAD events Duration Two (2) days Student Capacity Twelve (12) Statement of Work HEXAGON r City of Miami OnCall Dispatch/Mobile Implementation Mobile Responder . Police, Mobile Responder training is a Train -the -Trainer course designed to train Agency trainers in the use of the Mobile Responder product. MAJOR TOPICS • Using Mobile Responder on Smartphone or tablet • Changing unit status • Submitting inquiries • Sending and receiving messages A Updating unit properties Updating events • Informer queries PREREQUISITES • Responsibility for mobile computing operations • Assignment of at least one person who has been through OnCall Dispatch training to perform necessary dispatching and other CAD functions • Availability of customer -specific Mobile Responder configuration • Availability of test or training Mobile Responder smartphone or tablet for use in class TRAINING DETAILS Method Conducted remotely by Hexagon Personnel Target Audience Designed for Mobile Responder Trainers Duration One (1) day, but can be changed depending on Customer needs Student Capacity Twelve (12) Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation HxGN OnCall Analyt g COURSE OVERVIEW HxGN OnCall Analytics I Dispatch offers the ability to perform reporting and analysis from a data warehouse containing data from databases, as well as provide capabilities for the user to view and modify reports and conduct ad -hoc queries from the data warehouse. This course is designed to familiarize the end user with HxGN OnCall Analytics I Dispatch. It will provide instruction on accessing, viewing, and creating reports from the OnCall Analytics Report portal. It will also provide an overview of the delivered reports and data models. The delivered report provides out -of -the box access to key performance metrics while the data models provide an easy and powerful way for users to ask their own questions of the data and create new reports. TARGET AUDIENCE Personnel responsible for reporting and analysis (Report Builders, Report Consumers, and System Admins) MAJOR TOPICS OnCall Analytics Report Portal Creating and Modifying Reports: Introduction • Add Visualizations Overview and Navigation • Filtering Visualizations Delivered Reports and Data Models • Formatting Visualizations Overview of delivered reports • Pages — Size and Alignment Overview of analytical data Interacting and Sharing models Power Visuals Overview of live data models Creating pin, cluster and heatmaps Playback data over time PREREQUISITES • Familiarity with Windows -based applications Familiarity with agency workflows COURSE DETAILS Course Duration Two (2) days Course Type Conducted on site by Hexagon Personnel Student Capacity Ten (10) Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation COURSE OVERVIEW This System Administrator Training course is designed for System Administrators, to provide instructions on the setup, site -specific configurations, and administrative tasks needed to maintain the HxGN OnCall Analytics - Dispatch Solution. ARGET AUDIENCE System Administrators MAJOR TOPICS • Introduction • Site specific Configuration User and Group Management • Data Security PREREQUISITES Familiarity with Microsoft Windows -based applications, administrative tasks, and agency workflows • Familiarity with CAD configuration COURSE DETAILS Course Duration One (1) Day Course Type Conducted on site by Hexagon Personnel Student Capacit\ Four (4) Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment E — OnCall Dispatch Cloud Specifications [following this page] Statement of Work 82 HEXAGON HxGN OnCall' Dispatch Suite System Specifications for Cloud Deployments Release date: 10/29/2021 Release version: 10.00.2109 Release type: On -premises Released by: Hexagon Global Product Center Release method: Hexagon Global Software Delivery Process � A HEXAGON HxGN OnCall° Dispatch Suite Copyright © 2019-2021 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved Warning: This software product, including the computer program, icons, graphical symbols, file formats, audio-visual displays and documentation may be used only as permitted under the applicable software license agreement and contains confidential and proprietary information of Intergraph Corporation ("Hexagon") and/or third parties that is protected by patent, trademark, copyright and/or trade secret law, and therefore, may not be transferred, assigned, provided or otherwise made available to any third party without proper authorization from Hexagon. Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c) (1) and (2) of Commercial Computer Software -- Restricted Rights at 48 CFR 52.227-19, as applicable. Unpublished - rights reserved under the copyright laws of the United States. Terms of Use Use of this software product is subject to the End User License Agreement ("EULK) delivered with this software product, unless the licensee has accepted a valid license agreement for this software product that Hexagon has identified to licensee as taking precedence over the EULA, in which case the accepted license agreement will govern the use of this software product. Subject to the terms contained within the applicable license agreement, Hexagon gives licensee permission to print a reasonable number of copies of the documentation, as defined in the applicable license agreement and delivered with the software product, for licensee's internal, non-commercial use. The documentation may not be resold or redistributed and may not be copied or printed for those purposes. Disclaimers Hexagon and its suppliers believe the information in this publication is accurate as of its publication date. Hexagon is not responsible for any error that may appear in this document. The information and the software discussed in this document are subject to change without notice. Language translation disclaimer: Any translation of this document is not an official version and has been provided for convenience only. Some portions of the translation may be obtained using machine translation. It has been provided on a pure "As Is" basis. The official version of this documentation is its English version. Any discrepancies or differences created in this translation are not binding and have no legal effect for compliance or enforcement purposes. Hexagon disclaims any and all warranties, whether express or implied, as to the accuracy of this translation. Reasonable efforts have been made to provide an accurate translation, however, no translation, whether automated or provided by human translators is perfect. If any questions arise related to the accuracy of the information contained in the translated version of this article, please refer to its official English version. Additionally, some text, graphics, PDF documents and other accompanying material may not have been translated. Trademarks Hexagon, HxGN, Intergraph, the Hexagon logo, and HxGN OnCall are registered trademarks of Hexagon AB or its subsidiaries in the United States and in other countries. Other brands and product names are trademarks of their respective owners. HEXAGON HxGN OnCall° Dispatch Suite Contents GeneralNotes...........................................................................................................................4 HxGN OnCall Dispatch Specifications - Cloud Only.............................................................. 5 Cloud Access Network Specifications................................................................................... 5 Browser Requirements......................................................................................................... 5 Desktop Client Specifications............................................................................................... 6 OnCall Dispatch Client Workstations.............................................................................. 6 HxGN OnCall Dispatch Records Client Workstations.................................................... 8 HxGN OnCall Dispatch Analytics Client Workstations................................................... 9 Mobile Client Specifications................................................................................................ 10 HxGN OnCall Dispatch Mobile Unit Client Specifications ............................................ 10 HxGN OnCall Dispatch Mobile Handheld Client Specifications ..................................... 11 HxGN OnCall Dispatch I Tracker GPS Device Specifications ....................................... 12 TechnicalSupport.................................................................................................................. 13 Submita Case Online......................................................................................................... 13 3 HEXAGON HxGN OnCall° Dispatch Suite General Notes This document provides the specifications for hardware and software required to support the HxGN OnCall Dispatch Cloud Program. The system specifications included in this document apply to HxGN OnCall Dispatch Application Client specifications only. The HxGN OnCall Dispatch Cloud applications are cloud -hosted and the server components required to support the various customer configurations and resource needs are provided based on the Cloud Services documented in the associated Cloud Program Orders. The client specifications in this document reflect technology that is currently considered standard and is routinely available from hardware vendors. These specifications should be used when purchasing new equipment. For customers with existing hardware and planning on a software upgrade, these specifications are intended to serve as a guide for determining whether existing equipment should be upgraded or replaced to support a mission -critical configuration. In HEXAGON HxGN OnCaII® Dispatch Suite HxGN OnCall Dispatch Specifications - Cloud Only Cloud Access Network Specifications Some customers may want a dedicated connection to the Cloud platform provider. In the case of a dedicated connection, the specifications of that connection are agreed upon during contract negotiation and are separate from the system specifications contained in this document. Browser Requirements Customers should use Google Chrome"' browser version 77 (or greater) to access and use the Cloud Program. 5 HEXAGON HxGN OnCall° Dispatch Suite Desktop Client Specifications OnCall Dispatch Client Workstations Item Specification Processors i3-2350M processor or greater (Not ARM) Memory 8GB Internal Disk 80 GB or greater (Solid State is recommended but not required.)' OS 64-bit Windows 10 Video 1920x1080 resolution display or better HEXAGON HxGN OnCall° Dispatch Suite Graphics Card NVIDIA Quadro 4000 (2 GB GDDR5 PCI) Minimum: 256 MB PCI-Express x16 video card Recommended: • NVIDIA° QuadroTM K620 2 GB video card • High Performance: 2 x NVIDIA • GeForceTM GTX 970 4 GB video card • GPU Considerations: • Minimum of 2 GB of video RAM recommended • NVIDIA° Maxwell -based or better GPU recommended • Intel° Quick Sync Video is recommended only if the Intel discrete graphics card is directly connected to a display device. • Two or more graphic cards can be used to support different monitors individually. To have the video decoding done on the card, at least one monitor must be connected to each card. NVIDIA SLITm bridge is not supported. Example Hardware Dell OptiPlex 3000 series 1 The OS and client application require -80 GB of space. HEXAGON HxGN OnCall° Dispatch Suite HxGN OnCall Dispatch I Records Client Workstations Item Specification Processors i3-2350M Processor or greater (Not ARM) Memory 8GB Internal Disk 80 GB or greater OS Windows 10 64-bit Video 1024x768 resolution display or better Webcam (optional)' Any Windows -compatible webcam Example Hardware Dell or HP compatible 1 Webcam only needed to use optional image capture feature. HEXAGON HxGN OnCall° Dispatch Suite HxGN OnCall Dispatch I Analytics Client Workstations Item Specification Processors i3-2350M Processor or greater (Not ARM) Memory 8GB Internal Disk 80 GB or greater (Solid State is recommended but not required.)' OS Windows 10 64-bit Video 1920x1080 resolution display or better Example Hardware Dell OptiPlex 3000 series 1 The OS and client application require -80 GB of space. P. HEXAGON HxGN OnCall° Dispatch Suite Mobile Client Specifications HxGN OnCall Dispatch I Mobile Unit Client Specifications Item Specification Processors i3-2350M Processor or greater (Not ARM) Memory 4-8 GB' Internal Disk 80 GB or greater (Solid State is recommended but not required.)2 OS Windows 103 Video 1024x768 resolution display Touch screen recommended Ports RS-232 Serial\USB Optical Drive Recommended but not required NIC 1 Gb physical and Wireless (WiFi and/or Cellular) 3G or 4G is recommended of cellular wireless data connectivity, either built-in or attached using a USB port. Example Hardware Panasonic, Dell, or Samsung 1 Mobile Unit memory requirements are dependent on what other applications are being used, such as field -based reporting, third -party citation application, and so forth. 2 The OS and Mobile Unit application require -80 GB of space. If pictometry or other data resides on the device, then additional space is required. 3 Mobile Unit has not been tested on Windows 8. Mobile Unit does not support Google° Android TM or AppleT"' iOST"'. It is a Windows -only product. Windows RT (Windows using ARM Processor) is not supported. 10 HEXAGON HxGN OnCall° Dispatch Suite HxGN OnCall Dispatch Mobile Handheld Client Specifications • Apple Inc.° devices (iPhone° and iPad°) with iOS 9.0 or greater (Tested using iPhone 6, iPad Mini, and iPad Pro) • Google LLC Android devices with OS versions 5.0 or greater (Tested using Galaxy S6, LeEco Le2, Moto G2, and OnePlus One) Certification has been performed on a limited number of devices due to the extreme diversity in the Android market. Testing has been performed with the platforms and devices listed above. While other devices are certainly viable, Hexagon strongly recommends customers to test with a single device before purchasing large quantities. 11 HEXAGON HxGN OnCall° Dispatch Suite HxGN OnCall Dispatch I Tracker GPS Device Specifications Hexagon AVL products only support the protocols listed below. Devices that support one of these protocols should be compatible with the HxGN OnCall Dispatch I Tracker product. Protocols supported: • NMEA (National Marine Electronics Association) • TAIP (Trimble ASCII Interface Protocol) • OpenSky Subscriber Application Interface (M/A-COM Tyco Electronics — Revision 1.3) • BlueTree (10 Management and Event Reporting for the BlueTree 4000 and 5000 Series —Version 1.0) • OMA/MLP 12 HEXAGON HxGN OnCall° Dispatch Suite Technical Support Hexagon's Safety & Infrastructure division provides several ways to contact Support, including online case submission and phone support. For general Hexagon information, call 800-345-4856 (US). For phone support, see the Contact Support page (https.//supportsi.hexagon.com/help/s/contactsupport?language=en US). Submit a Case Online Hexagon provides an online method of requesting support 24/7. 1. Go to the Support page (https.//supportsi. hexagon. com/help/s/?language =en_ US). 2. Click Login. 3. Type your username and password, and click Log in. 4. From the Resources list, select Contact Support. The Contact Support page displays. 5. Click Online case submission. 13 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment F — System Configuration Diagram [following this page] Statement of Work 83 � ■t 3 .2 E m ¥ _ /\§ \\ §f0 @ CO4— 0—Co k 0 co co o cCD co X §\/ 2C) 0 �k O _04n-e M M w M 0000 ■ ■ ■ ■ aaaa \7 /(D ■ \\ \\ 2G §> o ■=.zRw $2 \ _ ® S ■ u /±� •� 2 § . cn k / � \ / 6 0 2f2 CL w ,e0 =f ■ E y = e.= e ES7 ») (\/ �) _ & 0 0 _ (D @ % a Q \ \ c g a I O % 2 2 % a U� !t -0 §o»>E?G/} g ' @ =g=U) ©_ > mm ay===% \ m E Q Q 0 Lo E( 2§22//�/\ 0 §e>�/3\ § § k } @ 0 ■ J , // _ \ x CLLU � \ O d N J O m m N N m m fA U) N 'm 8 00 o m N N �_ Cf) coi ao o m v�i CLi Q \ i / I m (p Y Y N L,Y N N > U) I m N Y y N �Y N Mn O Z Z -0-0 Z:)O N O Z:) O (n _� m � N N co c p m " m o as U i N U a) VOj U �1 Z •� r %- N Q a r0+� y L 0) i 'a O m O 1 0 o LO ' a? o% O w 0 p a) O .� N C) O U -6 (O I I I fC d a) E to Q to W 7 c O) -Ez 0 0 ) L o m U v o Q (6 cn aa)i o O �i o • .-+ L O O C a o o u, u, U J J c Z 0 O E� d v U) �Y U O .N N N H a) Z) E p N a) U o w i IL > N (n Q o >> N oO i E 0 C pU H Z O Q J J J U CO O a) w w o Ico I O N LLI N 2 � C O N N V. y_ L N t� I E] N _ a) CDo a _ 72 - I ON _ c w 2T w E I co I y 0 0 Q O OU I W a1 w co - .. 0 C a I � 0 Q I oa �U U I _m }' O L Co O I U �w L �3 >Y Q ° Q U _ I co �o U +� N I t� = ++N D O 7 �p O o co (n co N (n I 4 _>�Q U U U Q) a o N I � I QM o �° a) �Q ° ` � D L��� 0•o�U0Q� 0E Qc Q 2 cu c II I ° v= ai o_ 'dO•c— Cl-� ap 0 �m��0°. 2 o� NQ(� Nh mOO zzoz O Oz OI ___ �yew x� M � L i N co N U)wo� a�i E •� cu � C1 a a > vim) c c c O O a)M CD N -a 0)Q cn LLJ N O) 0) O) c c c 0) � •� W W W W a1 /�mayy Q o C1 N N N N w O O Q N �7/ O L L LL LL O O a N `�-� L O O N C �N/ L L L LL N N N > L U� �� V_ cu v O O L N OEEE� O O O Y Y �J Q Ica) U) V E +V+ _ N > N cu N N � E � i) N N N U U N 0 N U O fC !� d t3 Cn r W Co C) -O t3 G > t3 > N > O m .L O 7 7 7 .L w C) C) C) N Q fy C) L N LL D / \ \ \ d ® B E \ � I=& E o ®E mf ■ o\k}/ \_/ / �5+«« m/ k 2 g )/)%% 7 2\ \ \ k { / ? / / \ $ � FiD; Q � 04 2 S U S o _ ■ m c �E k: h 2\ o c § ■ > 2 O e k � ■ « co I W f v o _ •- \ E o §§§ t\ GI \\)\ ƒ/40 co 0 § / =o,, \ ago ) k } / I_t \ \ h \ o / p ® 7� \//)) U 0 \ Z® \ \ }\o/ƒ \ � [ . [ � � $ w � § � ■ o c o Cl) �; f e \ �O (o? \ I c u e — o /)\ �f \\ �\ �� \ 2 \ �L =CO 1 \5® @ E %o )ASS —_F I—t E c E o G E my o/ 8[[ /\\ 7 �o+«« jo _ \ e5 ( / / h % i f \_ ƒ / U &2o<- \ f 2 » c /\\ | 0 2 | ■_ 7 § $3\ u a) a 2 2 2 ul o \ w 3 w | = _ _ 0 eee N O N L Q m Q 0 Q 0 Q O Z L Q c Q a� E (>6 i U Q � (6 Z L� (n0 (D DN AND Op N (U6 �. 0 �p•U > U0 Q 0 E 0 L p N� N E (6 U tp O- .- 0 p L �' O N m O '- -0 0c6� U � NO to 0 o _0 E N_0 N 0- N (6 �N N E z3 U�� � Z3•- i -0 U 4-- 0 U) N 0 0 N D U i O N U O O _ N L y U) N 0 (n O N _0 O y M O O (D 0 U p U L N �. �- p (6 j Q N —�i E O N O �� 0m N 0-0 QUO U (DU L m E _0 E N N U) O U � U U > (6• (DN U �• 2 O p(L L6 (D_0L U U U 0 m O 0L Np N O N0 (6 N 2L� Q a)O O -0 �� L N > O ��4 U) 0 U 0�0 N X m � U U (D Ur N( O U 0 (6 � i O O (6 U N N �- N LLO (6 X (6 (6 L O N O U) O U) E a_� "M �� O 0 L (6 >, 0 i E O m (nL j Q L� U p L 00 (6 N 0— L L 0� o 4 _o Z �� Z Q> M -0 o �E cn Q i Y~ > N(E6N O(D`� -0 0) 70 O U N �- O (6 N >, L (6 > a Q > _ ~- 0 0 7 N L= U 70 N 0 Q o O p 0 Q �" U) (6 N� (6 U) 0) 7 N N (D-0 Z,- � 0�� � UE _ (6 ��O (6 O (>6•V0 LJJ U m O L U) L (D 0— N N NQ OV N� �0N p L Q U (6 O U� �� j E 0 U (�6 U'- J� 0 ��� Q� OON �. _0 (DL O N E O O U N —per E 0) UO(6 0 U) N L 0-00) 0- (6-0 L mma) L X+ O U O U N E L _ LO O (6 U) O O 0� U) (6 U� L 0� � O CnOp L 0 0- 0- c6 U� a)4-U >,� a— U N E Opp -0 U- Q O O �.� O U� N N �_0 0 u) >1 00> (6.-w D U 0 • u Cn (6 Q� _ 0 0 U m 0 �, m L U _0 > 0 0 0) N m U 0) 0 U -0O� U) O 0) O N Q. Q O 0 per- �a�i� (6 Lc) o 0E(6 p m 0 O O 0 X U O U 0) X U 0' Cn >-� Z U U '- N Q0) C (� =cn WaiE Q( 2 H 0MM 2 H N cli "i L6 O ti 00 N L N U) N U) Q 0 N L N O O N D 0 U L N N N 0 U N 0 U L 0 N E 0 Q U) N 0 U N H �f rL� � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment G — CAD/Mobile Functional Specifications Matrix [following this page] Statement of Work 84 t t t t t t t t t t G7 E Q L Q a� Q Q Q Q Q Q Q Q Q C •�_ z Y Q 6 N N N N N N N N ~ v {% m U U -0 m v U v U (a v U (a v U (a v U (a v U (a v U (a v U C O C C C C C C> C> C> O O U O O O O O O O O O a z z z z z z z z z z X X X X X X X X X X 2 2 2 2 2 2 2 2 2 2 N C O -0 .7 U a'' C M Lr- C O L-0 N C u N 7 > w U C N Q� 4 J O— O vi C N j p O Q t> �C^ aJ cOo O O WOD +j C z (A C L fB N C i L N O L +� C 'i O O Q- Q C f0 '— 7 Ln ?i 4' N > N >, Q O U m U Q C U N W O Q 0 (A a)O _ C f0 O N L O co O U �; 4 J O v O U vi O O L O Q 4• 4 J } co U 4' O co +, -0 � � > , O U+' N C O � � Q Om tD4 O O u mJ Q- N QN C L O J cu > U Ln 'T N m O C f0 \ a, �aQ-J -C +' •C L Q N to L O O � Q ut Ucu f0 Q O C > cu C C v 4J +� �' +J C 4 J 7 VI -0 N •C Vl Q Q -` E (a Q C M v }� C Q -0 o m N co +, L -0 > >`na N O V U C �0 C cu N N E E E O �0 Q _ CUQ � O 4-0 N p 4 cu OO 4 UO m O U E CL C O U C N � N +' O O 4Jcu +' >, 0 O +' m C C t O .V O C 'M-0 N O 4J f0 N ut to L co cu > Q cu U 4J _ � +' U >O CU 0 to c O M cu N Q Q 4 L _ O U OU L 4' 7 U O � 7 ^ U a) CJ u C ut N } �' U C 4O N N L N N Q >` 4 co O +� +J v�i N �' p L 7 N W Q .� 7 f0 C p L t 4 J 4• '� N +J C O 4O Ln f0 X C .V ( L C � N 4' � `~ U C fB O ( C O i '� +J C }, N N f0 C 4 J co �� O L `� O� ut O N 4 J N > fB >, L .(A L 7 f0 +J U 4O O O-0 U co Q O �_ O Q ut Q N i C� C i 'n 0A U Q •o co L •o N t a. Q 0 O L tlA O � O L CO L - L 4 J V1 Q U Q- o Q O Q Q co O a Q oo C v v, v vcL cu Q 7 >, L C L N C C Q Q N Q L L Q M O L > U 4O N U f0 Q 4J CL f0 4J CL ut W ._ U f0 L U U 4J O C Q L O N — (n }J L 4� U U U U U C 4� C 4� C L L L L L > > cu > v v v v v W W W to to to to to O O O O O 4� 4� 4� +j 0 cu 0 au a) cu +j c +j c +j c 11 � c +J c 1 0 cC io io Q Q Q Q Q Q- > Q- > Q- > Q- > Q- > U U U U H U H U H w w w w w C C C C C C C C C C O O O O O O O O O O N N N L N N N N N N N L U L U U L U L U L U L U L U L U L U C C C C C C C C C C > > > > > > > > > > w w w w w w w w w w Q Q Q Q Q Q Q Q Q Q U U U U U U U U U U to to to to to to to to to to C C C C C C C C C C i C C C C C C C C C C p co co co co co co co co co co G7 co co co co co co co co co co N U U U U U U U U U U *k -i N M �t Ln l0 Il 00 Ol O c-I N to d U L G7 E }J p a s 41 a 41 a 41 a 41 a 41 a• a• a. a. ut N ut ut ut ut a ut a ut a ut a ut a ut z N N N N N N N N N 4+ — io — N — N — N — N — N — N — N N N U f0 C fo fo fo fo fo fo fo m m C +J C C C C C C C C C O O O O O O O O O O O a z v z z z z z z z z z a X O X X X X X X X X X 2 2 2 2 2 2 2 2 2 2 4J C a cu OU O O u c 4 J •Q s +, N 0A p O O \ N L co 4 J U p 4O 00A L O L 4 J m m t WD +J E N t C I O +J O O C N +J Q � v p L U 4- C L a..� U N O C }' c0 N m .c +� aJ O O cu aJ > =3 0 aJ co O U aJ -0O O cu M N C N +J cup m mC (n = L Q LO 4 J > > -0Z < L O a-•� N O co 7 U a U 0A O N Q c0 Q � U Ca N 4 J V1 f fo i (-a L p 4O 4. C � v1 W � Q cu Ca v co E C N E +J L O co .Q u O f° v 4- +j v LO C C N v > C N v � (� U O L C O U Q O v j C .O cu cuQn N °c° cu Q �, CL Q 7 v 41 m v Q aU > v, E fB f0 C Q 7 v > N Q C N O C v, 4 J L v ut _ > co N v >, �_ N +J ^ Qn m 4- a-•� V1 � L L N +J a C C N L O N O Q Q m � N U \ C C N U mC N N > t >� N N t E vi .0 O N a-•� 4 J O f0 u C f0 N p vi O C � L-0 >� to >- O M Q 4 J N +J m Q > N -0 4• N L O Z 'n � cu -0 In4 p N J � L U O O aL n to C ^ 7 N > 7 E - + a m- J m tLD Q O m C m Q C X - C O_ N m� Q m O 7 Q +J C =3 C m O p v N LJ N >, 41 p ._ N N N z Q U O N 7 E +' L N N L N Q� O U L N N L N Q U — > •� fB C N �^ cu 7 Q vi O 7 _ C N N 7 ut fo 4 J C ut > 7 ut 7 L a•, C _ f0 O C > N O co � O dA p 4 J -0 0-0 4 J p O v� w L 0 4. O v c 4 J > v > �_ v > — v 4- v 0A 4- Q M L v > v w O U O L U N > } 7� Q O O N L Q 7 N 7 f0 m-0 O Q� O .Qn O N N O +' O Q O m O X C O U N O cr-0 O p p w 7 C cn m Q U vi M Q �O p Q vi t 4 J L d U O O C O— vi t— Q U Q U N p to O U O 4 J L d N Q cr- 7 U U U U U U U U U U L L L L L L L L L cu L Q L Q L Q L Q L Q L Q L Q L Q L Q L Q i U Ca U Ca U Ca U Ca U m U m U Ca U(a U Ca U Ca O N 0 N 0 N 0 N 0 N 0 N 0 N 0 N 0 N 0 N 0 dA G1 +' 4J fB C +' 4J fB C +' 4J fB C +' 4J fB C +' 4J fB C 4- 4J fB C +' 4J fB C +' 4J fB C +' 4J fB C +' 4J fB C ++ -0 cu-0 cu cu cu-0 cu-0 cu-0 a)-0 cu-0 cu -0 cu -0 p m a> a> a> a> a> a> a> a> a> a> U D w D w D w D w D w D w D w w D w D w C C C C C C C C C C O O O O O O O O O O a= a= a= a= a= a= a= a= a= a=u N N N N N L N N N N N L U L U L U L U U L U L U L U L U L U cu cu cu cu cu cu cu cu cu cu > > > > > > > > > > w w w w w w w w w w Q Q Q Q Q Q Q Q Q Q U U U U U U U U U U \ \ \ \ \ \ \ \ \ \ 0A 0A 0A 0A 0A 0A 0A 0A 0A 0A C C C C C C C C C C i C C C C C C C C C C O co co co co co co co co co co G7 co co co co co co co co co co N U U U U U U U U U U -i N M �t Ln l0 Il 00 Ol O c-I c-I c-I c-I c-I c-I c-I c-I c-I N 1 cu to Ca d y t t t t t t u u u y p u E Q Q Q i u z N Q Q Q Q Q +' Q Q a to cu cu U N N 41 Qj U 4� 4� 4� N N 3 f0 u m u m M i u > p .O fB N U vi fo N U vi fo N U vi fo N U vi fo U f0 U fB U O O O O a o m O w O w O w O w O O O X X X X X X X X X X 2 2 2 2 2 2 2 2 2 2 O f0 � 7 vi a— � N O N Q CU N vi L cu > f0 -0 N N 4� `� t' O -0 7 O N ro (A7 U N C Q a�-J � C cn U O p O C , O -0 p O N u co co v O U �cu C >, O— LJ � N vi Q c� Q a N N N (A O *' C N f +J O O aO O Q C 7 -0 Q c c v L N co ^ -0- O V1 p v C N Q U -0 cu v> a., 0 to t to t t +' w +� N CJ U � N O Q> V1 N > �O 4, co N C c0 (^ i L co c U NC U L U v L 0A L O N 7 C to 0 a C Q Q > — O O C � .O O N U U 7 p Nto C +�+ C \ \ f0 N vi L QC M mC N O CL Q i OU N u O N CB Q O C C C L CB p fC u 4' 4' 4O Ln N O C -0 CU LO cu p} OC .L 4Q O N Q � C C to � O Vl f0 f0 7 C f0 di C f0 f0 m +J +J L a..i .Vl CC U Y V1 U C�C C N C�C C > N +J N O a..i M O >` -0 > L CUO L U V1 U — C N-0 O M Q co Q� `� E p N U N OU CU> p U p CU O vOi O Lr— vi vi O L M p O N >, 4, O a' co cu 4O N> L O N U O aJ O +J . 7 co Q p O 4J > 4% O p 4J cu C N-0 co C Q L N U N O L cu L +J M V1 = U CU L O L N to t > N O O m .O U � vi V1 N 7 Q L +J N C 7 vi 7 O cu N M N CU 7 7 >, to 0 7 O Ocu vi fB C O 4� v v> 4J a,o '� v v U co 4J Q- v Q U N N 4 J uj 4 J O O O cr 4- N 4� v fB c N 4 O f0 Q Q Q Q 72 3: E CU•� � Q —cu Q U o v > o a, O > +� OL vi O Q E p O +J _ U O O o L o-0 _ O M Q O O CL f0 Q N Q U N CL f0 C Q U Q -0 _ O U L CL Q U >, O w 4J cu cu cu U U U L L L U U -0 N L N L N L fo CL fo CL a. 4 J Q Q Q a. Q a. Q Q a. Q Ca Q Q Q Q Q Q Q cuU .2 U 72 U 72 U 72 O U Ca i 0 u Ca 0 C cu 0 ucu cu 0 E vi vi vi vi G1 au C fB C fB C N N N N O N N O N N O N N O p� vi L ++ m N Q> -0 N Q> - N Q> 4- N N N 4J N N N Q - - +J ^ Q - " +, ^ — CL +, ^ - -to Q +, ^ vi ^ O 7 2 L U D w D w D w Z Z Q u a Q Q Q Q Q Q Q Q Q Q O O O O O O O O O O Q Q Q Q Q Q Q Q Q Q L U L U L U L U L U L U L U L U L U L U Q Q Q Q Q Q Q Q Q Q cu cu cu cu cu cu cu cu cu cu > > > > > > > > > > w w w w w w w w w w Q Q Q Q Q Q Q Q Q Q U U U U U U U U U U to to to to to to to to to to C C C C C C C C C C i C C C C C C C C C C p co co co co co co co co co co G7 co co co co co co co co co co N1 U U U U U U U U U U -i N M �t Ln l0 Il 00 Ol O N N N N N N N N N M M Q to Ca CL t t t t t t t t t 4-1 � co co co co co co co co co E Q Q Q a-Q L Q L Q L Q Q z v v v v Y Y Y v o a) m C / c / C / c / C C Ca C Ca C / C / O 0 0 0 0 0 U 0 U 0 U 0 0 a z z z z z z z z z X X X X X X X X X 2 2 2 2 2 2 2 2 2 Q CU � N O 4 N— c0 > E u N a-J � +J L- m +' 4' C N U O U C Lcu +� N 4J N O N N> > 4 J Q- M �_ C > Q N >- L N U O L VI C C U N Q m U C � O n V1 O i U-O U C N cu O � O 0) w > V1 -0>, � w +' �' CB N .N > L to N L Ucu •L N a�-J •O OEiD U Y •C U ZI 4"J N 7 '� Q ut C 7 Q O fB O O L Q C '� 4 J C N O fB •C -o O O Nc >- E > U Ncu 7 U C O f0 4O > t N m N N LJ N -0 N +� •� N 4J N > 41 N ..0 C L C C m G w w +J to 4 J C U N +� O � �;� 4J N C> m L O N 0 U O 00D +O t o � U N 2� � +� � U w O p � O N� a n coo t � a Ca to � C Q � L O L w U C � a..l � � Q fC U u > � O L co -0 4• +J O O O U � � ^ � co � co Q co +J N L U O t .`^ 4J a�J +, +, N +� 4J f0 +' N C L N +J N Q U Q vi C U L N N C N U C C N Q f0 to U aLJ O N (n w L N fB cu 4- E C O C N 0p 4 J co L �, N N Ca > p N L L L O � aj L C p N C U _ co > O U O t o L ,C N N N O 4 J 0A C — 4 a�J au m O U f0 C O O Q C C" m > N 4 N > Q N > 7 C C N C C N C to N O i f0 m N 4J > 4J L > O fB +J 72 O� p cu O U C m C � Q +' cu 7 C� C LNL U � C L L C C L O L L% Q -0 -O +J C N co +' N a�j Ca CU (A vi C — � n 4' C- ( 4 J co L O co N co N NC -0 C C N 0A = C 7 O C- 7 O 7 N O -0 fB U — N }' L Qn C N .� LJ U_ 4 J C N � N � N > m L OU 00 , Q N 41 � tvD L N C ^ O co � a J N ' 41 N +J 4� Q C- p 4� � N m � L LJ � E N � 72 U N . •C � O M U O vmi Y C N p > 4 J O N p m U O +J N O L Q O p C vi to N C p N p LJ —_ Q L d C di > di L d +J > Q di Q Q fSS f0 Q C m V1 L d N O w to Q U m V1 Q L to d fSS L d U f0 V1 U 4J c c c c c c c c c c f° c Ca c Ca c Ca c Ca c Ca c Ca c Ca c C° v c v c v c v c v c v c v c v c v c -0 O -0 O -0 O -0 O -0 O -0 O -0 O -0 O -0 O i C fB C fB C fB C fB C fB C fB C fB C fB C fB U — U U — U — U — U — U U — U to V1 L to V1 L to V1 L to V1 L to V1 L to V1 L to V1 L to V1 L to V1 L ++ ^ V1 p •L •� ^ p V1 •L '� ^ p V1 .L ^ p V1 .L ^ p V1 .L ^ p L ^ p V1 •L '� ^ p V1 •L ^ p V1 •L U Q U d Q U d Q U d Q U d Q U d Q U d Q U d Q U d Q U d O O O O O O O O O Ca Ca Ca Ca Ca Ca Ca Ca Ca L U L U L U L U L U L U L U L U L U C C C C C C C C C > > > > > > > > > w w w w w w w w w Q Q Q Q Q Q Q Q Q U U U U U U U U U 0A 0A 0A 0A 0A 0A 0A 0A 0A C C C C C C C C C i C C C C C C C C C p co co co co co co co co co G7 co co co co co co co co co N U U U U U U U U U c-I N M Ln l0 00 Ol M M M M M M M M M N to Ca CL N X 4-1 5m L W ^m m 4-1 t U m Q H U O z Q x t t t t t t t t t t � � O^y 41 to to to 41 to 4 to to to to to to Y Q L Q' L Q- L Q- Q- L Q- L Q- L CL L CL L CL L cu CU cu cu cu cu cu cu cu {.% CO CO CO CO CU CO m m CO CO CO m U U U U U U U U U U CB C CB C CB C C CB C CB C CB C CB C CB C CB O O v O U O U O w O U O U O U O U O U O U a z z z z z z z z z z X X X X X X X X X X 2 2 2 2 2 2 2 2 2 2 L (n CU LL a- CB 4- CO Q -0 to CaQ a -•I U C CU L O O !ECa a 2j V1 4 J +J 4- 4. L O Q N > � > � vi •Q m vi •� C m -C cu-0 4. +' cuN NL� p �O N Q- m Qi CO a-'' E Z, V1 W U C > O di U 40 m t > O N L N 4O U N L Lr N N Q N i Y cO p UA cu cO O C N i m� V1 — L- CU CUC N O � C =3 Ca U a `^ > 4J `^ O N Co C cO O vi Q �+ > vi Q a) a-o L O 17D O +' O -•I N C N C L O Q to L to L O to v U C U 7 N CO U Q N > to U U w U N O U L >' N 0 cu � N O co O +, +J N U N O vi co +J U O +' +J O O C�-a L m to C co C N t N dA C m N U U O (n a�-•I C vn N X N O C T +� N � O 4J LaP O Q Q) N m Ovi w U p C - C, C cu m O � L t Z vi - �_ (A O ra oO cu cuL vi 7 (o �O cu vi LJ t CU � 41 O L N O O C } p > N fC Q C O N C N ^ co C N Q� O u Ln N co U � >, ;} O +' pto 4- `^ p O C 4- vi N M CU J vi N O N t m O O CO > N O C L� C O cu7 C O U- 4 cu aj t t (A 7 V > C mC fB vi N cu4 C p 4- CU CO O i U -0> M 4J vi CU CU a -•I CO C Q a••I >� 4J C O a -•I O +' >� CU vi N O N > O C O L N L N a N p +, V1 a C CO C L 7 O 4 J C—> +J C O U 4- C N O> 4J Q O � Q vi C C L U N co C U a -•I >- co 4. >, N C7 C N a -•I > N CB O U O N co ^ v L U N O L N v L L L O CO L > N > L, N O� N C N +' U Co 4- vi CB U `^ a -I +' OU O L N +J O N N N CL ,C CI N Q N > N '� N E Co u t o N > r-0 t � � U CLo U N U co U C C (A C O .L O a= C O cu `U � v CU o cO +J v> L a " E O `� ra a O C Q- v O U +J V1 v v O C a -•I V1 c 4- N co N Q CU a••I I O M i N t .p 4- L CB U Q— � p +J C co U vi CU v O N C O N N = N N to N Q Ca U N Q� O > vi N M c a C co N N 4- Q v� Q F QC v LL U -0 v v v 2j v> v U +J } �' � v v C p p `� O i C u N ;0 O O to a +J N N U N co O +J U N L to a OU CU OU U OU WD O vi O W —0-0— OU a .S a -0 a Q Q a t N (A Q U N Cn N N U N -0 U m U 2i cu cu ° + c c c c c U_ U_ U_ U_ C CO C CO C CO C CO C CO C Q CL CL CLcuC cuC cuC cuC cuC N C 7 7 7 7 -0 O -0 O -0 O -0 O -0 O -0 O p p p p T U a••I U a••I U a" U a" U a" U a- L L L L i C fB C C C fB C fB C o C o C o C o C a -•I 'L a -•I 'L a -•I 'L 4- 'L Y N Y N `1 N Y N G) to V1 L to V1 L qp vi to vi to vi to ++ is ^ O V1 L ^ O V1 L ^ V1 O L ^ O V1 L ^ O V1 L ^ O V1 L cu t U N t U N t U N t U U Q U Q U Q U Q U Q U Q U U U U U O O O O O O O O O O cu cu cu cu cu cu cu cu cu cu L U L U L U L U L U L U L U L U L U L U C C C C C C C C C C cu cu cu cu cu cu cu cu cu cu > > > > > > > > > > w w w w w w w w w w Q Q Q Q Q Q Q Q Q Q U U U U U U U U U U to to to to to to to to to to C C C C C C C C C C i C C C C C C C C C C O Co Co Co Co Co Co Co Co Co Co G7 fo fo fo fo fo fo fo fo fo fo N U U U U U U U U U U m cu to CO d r-I N 4-1 5m L W ^m m 4-1 t U m Q H U O z Q X U U U U U U U U U E Q O Q Q Q Q Q Q Q Q L Z 0 co 0 v N v v Y ~ { % m (o (o U > (o v U .—\ co v U .—\ co v U \\ co v U —\ co v U .—\ co v U V1 co v U \\ co U C -0 C / C / C / C / C / C C / C Ca 0 O a O O O O O O w 0 O U a z z z z z z z z z X X X X X X X X X 2 2 2 2 2 2 2 2 2 N -0 U -0 CU too Lcu (a o a o L cu+J C N vi cu(O cu .0 � O L O 7 O r I N cu N L N �J L O M C cu O C 4J z L > U L C N N }CU � > 4% L > a- � 4 J V1 E In L >- Q L Q � c +J (0 _ U +J O � Ln O w > w � U C lH � O 7 +J Q Q N Ca f0 U w U 0 4J U 4J N N U E O O C c (0 cu 0 � L — .Q C L O +J U Q .V Q Q 4= C L (0 CU 4, cu p 7 O Q 4- O U Q cu (B �_ (B U > N > i Q 4� Ca to C O N -0 4� � .� U 4� Ca O N Y CU 4O � N X (OO 0 to 'T � +L, � § Q � M +J O L O � O O a J C 0 ++ tvD L O_ ?i p N 4- O O C- N O-0 U V Q m ^ a•J C N Q w U CO N E u C O w t U U C O O O N v C O >. U 4J N Q U — U (+o N Q (p 4J t v CL O p O (C VO O (o aJ � cu O 4� ; � L Z U L N N +� C > C O ^ O C O +� C N O Q OCU N Qn 0A L 4- N N 4 J } L O L N N WD (0 N L � 4� -0 U vi O O - > � C— Q U-0 O > > 7 U > �7 U C M N-0 p N 4� N U-0 m O C LO +, N N O Q N C O (0 O O O N O - cu C O C L N +J +J +J Ca +J ,O ra N N 4� L N O a.J (0 +J O N U C N t (o > Y O P p N 4� O 4� 4— E E O L U W — L 0 +, N m U U U u� — 1— -0 — O p W U n i NC Qn Q 7 Q •v � � i N �O aW O > UO '`� 7 >, L C O C O N< `� '} cu -0 o 0 u (0 (0 (0 (o V1 41 7 (o m >` L v t — .� 41 C v > > c v v C v E (o '— v v Q v— t v v t c v C t o c v O Q C +� � c o o o CU v C CU w w Q v — 4 J a,o +J .� +J +J M C cu O t +' cu +' 4' N �, U O N N Q (o U +�J t N C� C u •— u •— 4% -0 N� V1 L V1 � -0-0 C N (.7 L 4- ^ }J L7 (0 > O (B +J +J L a J vi p > > p L > Q O M (o N aU C U H w N O —_ 1 > N Q O —_ Q N 7 O U O O N O O U N Q L CL O Q O O O O O Q— C (o +J � Q-0 7 p 4- L L � U L O L N CL � L CL (o a +J C C C C cu +J v +J v +J v +J v 4 J o 0 0 0 Ca U_ Ca U_ Ca U_ Ca U_ Ca+� U_ (a +� fB +� fB 4 _ (Ca (a C C C CL CL CL CL CL O O O O O O O O O 0 0 0 0 0 C C C C Qn O +J Qn O +J Qn O +J Qn O +J O +J +J +J +J +J tw U U U U U U U U U U U u u u u O O O O O O O O O Ca Ca Ca Ca Ca Ca Ca Ca Ca cu cu cu cu cu cu cu cu cu L U L U L U L U L U L U L U L U L U C C C C C C C C C cu cu cu cu cu cu cu cu cu > > > > > > > > > w w w w w w w w w Q Q Q Q Q Q Q Q Q U U U U U U U U U 0A 0A 0A 0A 0A 0A 0A 0A 0A C C C C C C C C C p (o (o (o (o (o (o (o (o (o G7 (o co (o (o (o (o (o (o (o N U U U U U U U U U O r-I N M �t Ln l0 Il 00 T� cu to Ca CL t t t t t t t t t t t U U U U U U U U U U 4� U ^y 4-1 (o (o (o (o (o (o (o 4� (o 4� (o (o 4� (o Y Q' Q' L Q' L Q L Q_ Q_ L Q_ Q_ Q_ Q_ Q_ .� L 4% Q Q L 4% L L L L cu u m m v U m U co U co U co v U \\ co U co v U co v(a U v(a U \\ v(a U \\ v U \ / C C Q C / Q \\ C / \\ Q / Q / Q / .-\ Q / O O O U O U O U O O U O O O O O a z z z z z z z z z z z x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 L a x � Ln U O QLi- � V1 cu Q " � (:Q C Vl Q Q a -.I CU c-I Q O U a�-.I (f°J Q � >` -0 7 � L a•' v Q_ C v C U 4- v Q m L v+ � L 4' O N N N O O 7 C N m-0 O 4J N t vi N > 4� vi m m a�J -0 E t 4� LJ m O O a t C E U C C O N L E-0 ZIQn dCA tvD acu C C 0A 4' 4 J (C0 O 7 N U L +, vi 4' NC m m (o (0 ,O U N L N = N O C ^ N vi L C (o O 7 Q Q fB +J L � cu +J .. (0 Qn (0 N N C (0 - C cr O U U C � O Q >, t Q C Q- N C J Q 4 L � cr U L r-I Q NC V1 Q V1 Q L_ O 7 O d) C O O O O cu > C N o v 0 +J O aJ 4J N 4J N C C O N Q L � +, O 0A L N C 'Q Q mL � Q_ to mM VC E V1 L 0 +J O Oa cu -0NC N C cu O N O N +J N > Z N >� O aJ CtD u CN N -0 N (0 to U L (a O Q Q O u 0O Oa• CL C N N Q- O +' v O cu cu O CU Q I m N m C O w O L L `LJ � N Q U mm L N C QO N CL Q N ci 4' C N U N " OU O -0 +, � 4� 4� — -0 v >, Ol � 4� t o � 4� >, t � N +J N > (�� � 4� N L N N m N U M L N N N L C .. Q C ^ (O O +J N N � (0 N N 4� 7 Ln (0 `^ _ _ C C Q E m _ C � � Q-0 _ CU � (0 (� L Q C > Q_ > i a N C O Q O L L > N > C 7 L � - > p Q O > N O M O d d N vi O w U C C , Q N 7 7 CL C Q > Q Q_ N U— C- Q m (0 L vi m CU � 0A U CL (O C Q 7 7 Q C C v v C C C C C C C O O O O O O O O O 0 o 7L Q_ (o (o (o (o (o (o (o (0 (o U U U U U U U L L U U Lr- � •\\Q � QQ toto•\Q •\Q •\Q •\Q .•\\Q •\Q C C / / i O 4�+J C C C O C O C O C O C O C O C O C O C O txo N N L 4J L +J +J +J +J +J +J +J ZI 41 (0 4 (0 (0 (0 (0 (0 (0 (0 (0 4+ U U 4� U u a"' U CU U U U U U U U U p p O O O O O O O O O O O O z O O O O O O O Z Z Z Z Z Z Z Z v v v L v v v v v v v L U L U U L U L U L U L U L U L U L U C C C C C C C C C C C Q Q Q Q Q Q Q Q Q Q Q > > > > > > > > > > > w w w w w w w w w w w Q Q Q Q Q Q Q Q Q Q Q U U U U U U U U U U U \ \ \ \ \ \ \ \ \ \ \ 0A 0A 0A 0A 0A Q O 0A 0A 0A 0A 0A 0A C C C C C C C C C C C tB i C C C C C CU C C C C C C p (o (o (o (o (o U (o (o (o (o (o (o 00Ln 0) (0 (0 (0 (0 (0 rn (0 (0 (0 (0 (0 (0 (A U U U U U 00 U U U U U U 0) O c-I N M Ln l0 Il 00 0) Ln l0 l0 l0 l0 l0 l0 l0 l0 l0 l0 Q to d J� J N X �L 4-1 cm G H G! ^m m 4-1 t U m Q H U O z Q X t t t t t t t t t t G7 Q Q Q Q Q Q Q Q Q Q E p to z N N N N N N N N N 0 m U N N N N N N N N N 3 m U f0 U f0 U f0 U f0 U f0 U f0 U f0 U M U M m U> m O c O c O c O c O c O c O c O c O c O c-0 O Q a z z z z z z z z z z X X X X X X X X X X 2 2 2 2 2 2 2 2 2 2 L O •— J > c Q L c p ra � t u O n3 c � � � > N c L E 7 4J u - § f0 -a E O E O -0 N O -0 -0 to O O N N -0 vOi vi 7 > +J +J c N = N =+� a•J � ^ f0 Qj to L N N c0 t� N +J +J `� O N 4- u c f0 c +J V1 c0 m — a J f0 vi n3 N vi L N L• O MC � cUo N -0 Qn > v c vOi N N N vi N N n N O cu C m +J L .� {n = N L N N +J +J c 4� N L c Q c0 a•J ^ N u — � Q O N V1 a•J c O Ln L •� c0 +J N vi CU L N +J m > +J vi > M N aLJ `n O � N — c0 > 0A N N 4 J +' vi 4- Q N O '} O -0 c N-0 m N c Q to O N O L c c U L c Q T-0 +' c m f0 L 7 c } 7 c'A O Ncu >, w n3 O Q cu p O cu O c0 p aJ p O aJ J O J c0 V ` -0 O c " 0 + +� `naJ v -0 c -0 aJ O m0 v c O t J 4J Q NU E 4, c O 0 pL N c +nJ3 cu Q vOUOMQ OOXN O MuQ MQN m N CL Vp p O— U OOc0 c M W L N m L O L N C O L N-0 L = -Qn N +J > L N NL O n v Q c uO 4J o +J c M +J 4J J 4J c 4J c} Hi p N L > +J cvQ c 0-0 N -0 LA O N - U N OmIn to O N 0cLoA u UaJ O UaJ M O +J E O aJ O m +J > O +J O +J m 7 u >�•Sp p M N • -0 W -0L Qn c Q Q � 4�4�\ a- 4�.L �.J � M •L O M .� N mu t� � � p � -0 N N -0 4 n p -0 -0 N > O L >� N N � N c M� N 10 m N 4L m 7 N O J M +J N O m N m N U c a�Jcu a J N p N-0 a•J f0 4� 4� c X 4� 4- 4� a J O a�J a�J a�J O NcL ocUA 3 10 -0 O� i� N LO N N O cu CU -•0 -0 , cv0i N 0 NN� �� _ LL Q L_}_z > 04� c O c >L O- > O > O >O O N L("U Q -0 t— O Q c 7 N to Q Q m d E d-0 N O cn �O m d m� m d E v d O Wp d 0- 0 0 0 0 0 0 0 0 0 0 U U U U U U U U U U L L L L L L L L L L 0 dA O O O O O O O O O O 41 a" Ca U Ca U Ca U Ca U Ca U Ca U � U ��� U U U O O O O O O O O O O U c c c c c c c c c c O O O O O O O O O O 1J n3 1J n3 1J n3 1J n3 1J n3 1J n3 1J n3 1J n3 1J n3 1J n3 v v v v v v v v v v L U L U L U L U L U L U L U L U L U L U c c c c c c c c c c > > > > > > > > > > w w w w w w w w w w Q Q Q Q Q Q Q Q Q Q U U U U U U U U U U 0A 0A 0A 0A 0A 0A 0A 0A 0A 0A c c c c c c c c c c 0 c0 c0 c0 c0 c0 c0 c0 c0 c0 c0 G7 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 N U U U U U U U U U U O -1 N M �t Ln l0 Il 00 Ol 00 N to n3 d U U U U U U 41 � E Q Q L Q L Q L Q Q Z o v o o o o v o v u U \\� U U U U \\� U \\ O O O v O v O v O O a z z z z z z X X X X X X 2 2 2 2 2 2 C 4J CU L u � O > >- CU CU 7 u O N c0 +J CUC 4J -0 Qn u E O -0 a 4 N C f0 O U L Q N 4J co � L C f0 0 'C� ^ +J C Q 3 U-0 O (a C 1 O O +J C � U >, L N N O u 7 Q N m c U O V1 4J N > \ 4J CU N OCU aJ O n Q 00 � t co � C 4J > -0 u O 4J Q O O i iCU +� Q 7 O N N O Qn i O �, N = � Q- N U U CaN (AO O N �+ •N N rl N O O .1 •O CUQ N O Ca to > 4J -0 U C C � Q C C U-0 O 4J Q N Ca M u CU Ca 4� m � L= N ( N Q C u O U Q •� U O O ^ u a C 4' N v v O co U •TO +� — m i �J a E 4- tvo > 4' +, N L w C Q +, m U O to Q ^ U u O O Z M N �O >, co OL co Q L N vi O N dA ^ �, vi N (n N vi Y O O L W V1 Q C�_ � a J O U O O co WD O-0 J J cu >- U m 7 vi O O N vi Q L N cu 4� L L � O 4" Q C m L U O CU O C L U i 4 J N CO }.i L � > m L L L O L L fo O +' cu O � co � — 4 E L vi � O Q O O C O -0 O� to E N '� C Q- �_ O .S O O +' coo coo � > Q O N +' O O C n N U N +J L to N N N -T L o v f° Q E >. +� C— +� co L U L ai co tvo m >, M W M Q Q" X >� > 7 N vi N Q a J � .� H vi vi co N Q w 2 2 Z 0 0� (n Q vi 0 v v v v o ao ao ao ao m c c c c E E E E o O O O O T > c c c c a o i O C N N N N -0 v v v v� > E u L 4 4 4 4 L > O++ U o cu c c c c c c c c O O O O O O v v L v v v v L U U L U L U L U L U 4� c 4� c 4� c 4� c 4� c 4� c > > > > > > w w w w w w Q Q Q Q Q Q U U U U U U dA dA dA dA dA dA C C C C C C i C C C C C C p co co co co co co G7 co co co co co co N U U U U U U U O ci N M �t Ln 00 00 00 00 00 00 •1 N Ca dA d cn O r-I N �L }i m G H G! ^m CL m 4-1 t U m Q H U O z Q X t t t t t � � � 41 1 Q Q Q Q Q E (a V1 L V1 L V1 L (/� L V1 L Z o v o v o v o v o v E E E E E U f0 LO f0 LO f0 f0 LO f0 LO 3 U U U U U O O O O O O L- z z z z z X X X X X 2 2 2 2 2 Q w aJ O E Y — N 7 7 O O (6 cr cr Q LJ LJ f6 OLO > (6 cu 1} O w i O v> a- > n +1 L O (u 1 O a-1 C C 2 O O O v -0 4-1 � cu N ���NQ- -0 C: M 4-1 �t -0U Q O V7 4.1 f6 V1 . -1 .� O CU =3 w O w � � CL � Q � L ML } 'L +� O WD O p p O 0A p p iC O O v: L cu aJ (6 co aL O aL L U p O O y (U a U OL aJ cu 417 aJ OL aJ N aJ Y a a O }� v1 C .� t 4-1 v1 .1 .N W O O N M O 0A +' N m O 0A +' 0 L i-•� V1 -0 Q L i 0 -0 Q L t (6 'o C 0 O O 0A C 0 O O 0A m } O O O O Q a•J O O Q a•J O O O — a 0 w42 al > = L 0 > L O O •N O a--� > .� i6 c >, 4-1 4O >, +J +' f6 E E- 4J a aJ — CU ^ L V1 O L —_ V1 v L p V1 L aJ O aJ O E — aJ 0 O � 4-1 p 0 O � 4-1 O 4- EM - Ca L of M of M L _0 to •� U > to L _0 _0 to •� U > a) fO L L L a) ra L L C:O (u — — — 00 co O .— 00 co O c c c v v O O O U U CU O CU O CU O cu O CU O O D_ O D_ O O > •O i 4J 4J 4J 4J +J dA > E > E > E > E > E ++ O O O O O O O O O O > > > 2 > > U c c c c c c c c c c c c c c c O O O O O 1J 1J 1J 1J 1J aJ aJ aJ aJ aJ L U L U L U L U L U 4-1 c 4-1 c 4-1 c 4-1 c 4-1 c > > > > > w w w w w Q Q Q Q Q U U U U U 0A 0A 0A 0A 0A C C C C C i C C C C C p co co co co co U a1 co co co co co V1 U U U U U l0 Il 00 m O 00 00 00 00 m V I O 4-1 cm G H G! ^m m 4-1 t U m Q H U O z Q X t t t t t t G7 � � Q Q Q Q Q Q E O (a Z V1 L o V1 L o V1 L o V1 o v V1to o (ao }J V1 cu LO LO LO N N U f0 f0 f0 f0 f0 (0 f0 3 u C U C U C U U > U p C O C O C O C> O C-0 O Q C> O a z z z z z z X X X X X X 2 2 2 2 2 2 C O O Y U U 1 u -0 N C O N C U L -0 m U N -aO 4O N f0 f0 C C O N !E N 7 Q O �^ 4. C 7 f0 4- m 7 fo 4' f0 `~ > f0 N vi O L N O vi w M O to O vCi 0 C to 4- C f0 U (a f0 f0 v v c0 . � +Jcu (� m m C O 0N 4 J oOO m >. M O O qp N M O +O +J vQc0 a- a-O m 4J •Q- +J N W 0 a- 0 C V O N OC W � > > =N •v U O f7' O +J U m O 41 OcuO U f0 C � E D CO�CU -0 N> m Ucu OdA OO O�\N O N fu C O QC c -2J — NQ 4J > C 7 cv tD L Qacu to Z� N O O C (a 4�N O L L cu CU O � O O U > Y> 7 t 4J 4J � O O O O -0 to U C U 4, 0N N O +J N C- CT to 4- L �JN U M MU OU -M U U cu U E UV � -0 CU Ov E C . O a- cu N cu -F4' a 01 U� N N N N U 4J cu N O O N U 0 0 0N -0= U-0 4. m ON 0 N N O > +' CL +' t N U 41 C O 4J 4' '^ 4J C Q -0 0 Q- -0 N 00QQQ> CC > M O }U m U m �N �> m Z� C m V1 (o > N _ +J O-0 U 4- 0 di00 (A 4• 0d mdQ N i` = > cu cu cu cu •� "CU m " Z f0 > 7 a-•� .Vl cu Q }� •Vl w C L co a,o C V U U U U Qi Qi Qi Qi U > > N Q C 0 cu U roJ J J J D_ >>>> (n d' +' (a J> +' N N N ( N +� N OU CO W O O O O O O O O O O O -0 m m O O 4- �� v 2 Q fo 2 Q C m C C C a, a, a, -0 L -0 L -0 L U U U O O (0 O t C t c t c N +J M V1 N +J M V1 N +J m V1 > .2 > .2 > .2 m cu cu m m cu O O O O O O dA > E > E > E L O O O 0) O L O L O L > > > v v v v v v C C C C C C O O O O O O v v v v v v L U L U L U L U L U L U C C C C C C cu cu cu cu cu cu > > > > > > w w w w w w Q Q Q Q Q Q U U U U U U dA dA dA dA dA dA C C C C C C i C C C C C C p c0 c0 c0 c0 c0 c0 G1 c0 c0 c0 c0 c0 c0 V1 U U U U U U c-I N M Ln l0 01 m m 01 m m cu to c0 d V I O 4-1 m G H G! ^m CL m 4-1 t U m Q H U O z x U U U U U � E z N N N N N 3 U O U cuU O U a)U N m c c c c c O O O O O O a z z z z z X X X X X 2 2 2 2 2 C LJ Q U a••I O N =3 E N m cuO O t +J c vi NcOo 0A O C O 7 fB O vi N O 5. c +J O c O to L O O cO WD O N O� -0i >, -0 vi -0 m LJ � 4 J c U O O � L L m0 U O f0 vi f0 Q- CU N CU CO O Qn N O N 7 cu vi -0 (a CO � ON -0 Co L U 4, N +J Q a�•I Q O i > c c 4 �O O CB L CB � >, > O O 4J f0 0 c N N +j 4J N Q �, +J N U O .0 a- z CO O N 4, N O N +, Co +J c = 4 J c N 4J c U N L +' C N M a L a -•I O � 7 O- CL CU L 0A L N U N fC O Q O 1 +J m e O v Z v to to v W a Q � Wp C � O C L N C C O O LJ +' O O 4 J N m w ,� ,^ L N (B t Q O +, L �' CO O J j U c CO O L O c N C O �O c� 7 O — O� +J CU L `~ 4O O m f0 } a 4 m � O 0-0 �_ Co u u0A 0A 0A `^ aJ U +. O O (� O O O Co a aJ L CO L L U m O cu t I C L O, CU a••I a••I Co U— Ncu cu E m E >- (o O U N M U +J C Co N Q CU vi O c u O c Q vi O C O L c cu N cu Co WD O N O O N O O O 7 O v C O O O O O u Q- •vi 4J 41 vi Co 4J vi Z cu vi L 7 Y vi +J -0 'A E 4 J N Co +' O X O t' N t � +' N `� � c O t + t m N E m 0A c 4= Co p U m� +J O ^ O 4 J +� O Q c m m L L O CO N L � L X f0 O c L O 7 0 CO 0A m 0A >, N N O CO L Q a••I O N +, O O Q O O L Q `� f L `� U Q CO L O N to E O` d a••I O w c > Q O O CO � O 0 -0m O0 w m L O O O .� O 2 to Co L O O c c c c c N N � N N O cu O M V1 fSS V1 O (Sj V1 (Sj V1 U 4J O Q � O O N( > O O O w �O - - f41C LJ LJ LJ LJ LJ LJ LJ cu Q U a s a s a s a s U c c c c c O O O O O 1J 1J 1J 1J 1J v v v v v L U L U L U L U L U 4 J c },I c 4„I c 4� c 4„I c cu cu cu cu cu > > > > > w w w w w Q Q Q Q Q U U U U U 0A 0A 0A 0A 0A c c c c c p (o (o (o (o (o G7 f0 f0 f0 f0 f0 N U U U U U *k Il m 00 m m m O O c I O N cu to CO d U U U U U U U E a a a a a a a z N N N N N N N 3 U O U O U CU a)a)U a)U O U N m O O p p O O p 0 O O O O O O O a z z z z z z z X X X X X X X 2 2 2 2 2 2 2 L N O '� U U to c v c O 3 N 4J > N 4J U > vi O p U vi N L O 7 c N N CU CU O M CUCU M i ( a J L CU L Y N N c L CUU a N �, vi N � V1 `1 4 J CU M c N -0 4• +J N p 4- = LJ OL -0 N >. 4Oj L M N (0 L (o — +J cu t di L c -0 v >` v to �^ V1 4• c � a +J c c U 'E O CU _0 > W a �O u N u O > C t to M M N N C cu O L N N m I � N +, t 4' 3 N > O N m O41 a I v o +' +' o U cu � � X c v N +' v v co v •" f° �, > � v c c- ° L E O c c N L O N to M N N U U .O N to > p N c `}-, 4' N O N E O v m — >, U O L N c (o vi O p < O O O +_T+ N Q1 I 7 vi N N O +' m M� � } 4O U N U- CU-0O I u cr— a U O O t CUO L N O tvD 0 U CULn -- N c >CU " '� O co v (-a Ca4 J O t o U CLO N 7 N t +J vi 7 c m U N 3: aC O N ^ Q U (o •Q U c E Ca N +J c tr- -0 � (B Q tLD N N WD L C O O N w O O +J U L 4; U 4 Q •L N > N W w aJ +, CU (o Q U aJ `^ � to (o N O O O O -0= � 3 N - O O N dA c V1 4 J > L 'n < O N (o c O c u fo O (o N i p V1 to N c •2 O t U E= a� O O L U 4� ate" N mN N C aJ a +' LO vi c (o N U> U } O ( t aJ 4' 4J 4, 4, u aJ >, N 4J � (A O Q t O 4 J Q O CU N 4J c ^ c O L O t N •(U O O O N U p N In .O a v N � 4" 4' c a a N to O O LCa O 7 L N (Lo N N (o +' c O 0 to N (o O O N to N N N t o � � N +� .v a c vi O t (o (o N (a i ( c t N Q vi 4J — c 4J � N vi c � � to (o 4 � (o L m O L � O L O O E c a 4, O O N M E t +j p � a O N m aJ u CL O ( L 4 J c N t aJ L �_ m O � O c L > m Q �_ U c Q a ^ Q m CLD O aO j LJ LJ O Q Oto cu to p U L to CO C c (o (o N vi �O to U > vi (o (o (A a N (o (o CL 4 J U > a (o m m m m m N LJ N LJ N LJ N LJ N LJ c Q c Q c Q c Q c Q O O O U cu CL aCU O U cu , O U CU a, O U CU a, O U a, (o (o a) L a) L CU L CU L CU L cu L L (n (n (n (n (n i u O u O c (co O (co c (co c (co c (co w u u u u " u dA w " " " " 0) 41 N c 4J N N c 4J N N c 4J N N c 4J N N c 4J N fC Q Q N 0A N 0A N 0A N 0A N 0A U U U Q Q Q Q Q c c c c c c c O O O O O O O v v v v v v v L U L U L U L U L U L U L U 4� c 4� c 4� c 4� c 4� c 4� c 4� c > > > > > > > w w w w w w w Q Q Q Q Q Q Q U U U U U U U 0A 0A 0A 0A 0A 0A 0A c c c c c c c i c c c c c c c p (o (o (o (o (o (o (o G7 (o (o (o (o (o (o (o N U U U U U U U N Ln l0 Il 00 0) *k O O O O O O O c-I c-I c-I c-I c-I c-I c-I m c-1 N to Ca CL t t t t t t t t t t U 4 U U 4 41 41 41 V 4 V G7 +UJ 4 41 4 z N N N N N N U N N N N N N 3 (a U (a U (a U (a U m U m U M N U M N U M N U (a N U O O O O O O O O w O w O w O w a z z z z z z z z z z X X X X X X X X X X 2 2 2 2 2 2 2 2 2 2 C vi Q O p ^cu L (n vi O > O vi Ca Q U C O vi � CU O o o CU � N 7 w U O Q 4' N n v U X v L CUt N N 41 t Q N � EuraQ C VI Q a-J ut 4 J N N i c0 N +� -0 U a J a J a J Q O }J V1 7 Q" N U ut O N Q- +J cu 4 J L L Q L a••' a••' i m Q- N U 2 O U m 4- O Q Vi CUQ t �O Vi >, f 'L t 4J U 4 J Q- `^ N m O > N 0 CUN O U cu C Q�� O +' L CU Q UO a)� O Q � Q O O N ,O 4, V1 N N Qn N O N 0 aJ 0 O cu O Q cu X +JC � L +' O > Q U N L O +J O Q O O L �O L N Q u Q - Ca O Q a= .O L 00 U cO 4 J O +' > a N vi U O G U Q u N N L Q N LJ v fC cu +J fu — N Q io ut � L Q O Q Q WD O c O +J N � N N -0 7 dA O U w" +� 4' O > O O N t O 'O O }' +, > N ut w u O 1 a +J O O C Q Q L Q O X U CU N 4- > u O W V1 O L� U L 4- +=J Q+ -0 > CU Q O to a L w U Q vi O Q t Ucu co O U co N O aJ to 4- L = O M co Ucu N 7 t O� C i U '� O a.,, LJ Q N L Q � O N N O � N U_ 41 Q 7= (n O O v N N Q m O 4U C N U +OJ � E 4O N� 4 U +� d >` Q- — f0 (n +J L N CU N f0 O Q> 4J = m 4- Q .� O 7 O f0 L 7 Q L� L C N +J N >- N -0 O N t U U-C U > CU- a)V1 N - `� CL to L Q cO O C L > u � vi M -0 +J U N +J N N t +J ut O M N N +J O +J O C L +J O 4J 7 O L — a-J Q ,� N U N f0 .L � fo fo fo '� O m ut Z, N Q- N C m Q aU Q O N U aOJ O a�-J Q O CL ut m U O Qn Q> O L +J N co Q Q (o X 7 � O N L > N= O ^ C N ^ m N N O O D m N d L Q (n m w L 4. Q N CO 4 J -0 M ,� m-0-0 M CO L — Q m cu v Q cu 0 CU Y dA co N O co N O co N O co N O c O Q to to c 4 J u a'J u a•' +' u Q � CU w Q •V1 Q •V1 � � N CO 41 Q N CO a. Q a J N CO a. Q N a'J Q di (n ut ut O � O � 7 ut O 7 ut O 7 Ln7 O Ln O Q U O U O � � Ln i E d p p O O O O O O O O O O O O -0 L O dA CU C d E E > w > w_ 4- +J +J +J Ca U CU vi fC v to f° L Ca Q Q -0 p � p � p � p Q p co U Q Q Q U U Q Q Q Q cr- a c c c c c c c c c O O O O O O O O O C v v v v v v v v v L L U L U L U L U L U L U L U L U U Q Q Q Q Q Q Q Q Q > > > > > > > > > w w w w w w w w w U U U U U U U U U L O CL to to to to to to to to to Q Q Q Q Q Q Q Q Q Q Q N i C C C C C C C C C U O f0 f0 f0 f0 f0 f0 f0 f0 f0 +J CL G7 co co co co co co co co co N U U U U U U U U U O -1 Ln Ol c-I N M �t Ln l0 *k c-I c-I -i -i N N N N N N c-I c-I c-I c-I c-I c-I c-I c-I c-I c-I c-I Q to Ca d — t — t — t — t — t — t — t — t — t — t — t — t — t — t U U U U U U U U U U U U U U E f0 Q f0 Q f0 Q f0 Q f0 Q f0 Q� f0 CL f0 CL f0 CL f0 CL f0 L 0-0 f0 L 0-0 f0 L a-0 f0 L Q O � .L .2 .a ! L ! L ! L ! L � � _ � _ � _ � _ � _ � _ _ _ V1 —_ V1 — V1 — V1 m U U U U U U U U U U Vl U U U U ' O O w O w O w O w O w O w O w O w O w O w 0-0 0-0 0-0 0-0 a z z z z z z z z z z z Q z Q z Q z Q x x x x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 2 2 2 v cu CL � — N aJ C O LCU to -0O -0 J " +' i = N Q u �O N p O m m C N Q- m 7Eb •� m 4J C N '^ L m cu rn CL U WD O Qn > O > m Qj N CL� p � miJ �^ to`^ O � O N 0 O mU •� � J U -0 m mN vi cu 4J O O C O N U + OO E-0= LU p C Qn m CLp N 7 N 4' CU _N>v v 0 v CL N 0 c v O Q �+ v -0 C O � to o to Qn 0- f0 CLv �v O v Uo vN C UO v C Qn C B O to CL U >- — N UO +J + -0 N v 4' o N O Nm N A Qi >- a. u C �N CL 0 E C �F U o N M Qn Lcu E o p= n ao J u fc0 Q Q .Q 4 J Q c LJ •vi Q Q Q -0 v cu C Q LJ � O c0 - N to '.1— 0A O O N 0A N N t O O N co cocu +JQn Q Vl i V1 Q f0 (�/1 Y L fSS Li Ca " 7 7 7 N t N �+ C f0 C N t v, N C V1 t O � N f0 t Q N t � 7 C +j 7 N f0 � f0 f0 7 N > m J U Q 4 J +J E +J _ p a�j a-J a-J N _ L O L O L ,Q' O 7 L 0 Q L (� O O m L O vi L O i L O L lH O O L O L O L O N m O cr N O O O O O� N N O O 2� Q •C � j - �= O Q O CLO N O-0 O O O CL -0 co Q Q Q m Q f E Q Q cn Q4� Q O Q Q Q u w co N Q N N N N N N N N N N 0 0 0 0 0 0 0 0 0 0 Q CL Q Q Q Q Q Q Q Q m m m m Ln Ln Qn Qn Qn Qn Qn Qn Qn Qn Q Q Q Q O L L L U L L U L L L L L U m m m m U U vi U U vi U vi U vi U vi vi —^ vi —^ vi —^ vi cu CL d' CL d' CL d' CL d' CL d' CL d' CL Q J Q J Q J Q J L O L O L O L O L O L O L O L O L O L O L O L O L O L O Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q a- 0 u a U C U U U U U U U U U U U U co co co co co co co co co co co co co co Q Q Q Q Q Q Q Q Q Q Q Q Q Q N o 0 0 0 0 0 0 0 0 0 0 0 0 0 Il 00 Ol O c-1 N rn U) l0 Il 00 Ol O *k N N N rn rn rn rn rn rn rn rn rn rn c-I c-I -i c-I c-I c-I c-I c-I c-I c-I c-I c-I c-I c-I U) c-1 N to Ca CL t t t t t t t t t t t t U U U U U U U U U U U U f0 L 0- O f0 Q CU f0 Q f0 Q f0 Q f0 Q f0 L Q O f0 Q f0 Q f0 Q f0 Q f0 L Q O z f0 o aL dA L cu L cuD L cu L cu2 L f0 Qn L f0 04� 41 {% 3 co v co co v> co v v v v v v co v v v v v �, v v �, v v �, v v �, v 0 0-0 O a O> O> O> O> 0-0 O w O w O w O w O-0 a z a z z z z z z a z z z z z a x x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 2 O N U } N N _ c N O Q- >- Q c Z 4• 4 J 4� +� +� c0 p cu— cu c0 C O O t j 4' +' N u LJ O � N +' coo N coo — -0 4J O N U 4O � 7a w N- p E a-J � O -0 co > c c CU cu N U � ._ E to V1 cu V1 cu O +J V1 � � .Q- U >, � CU C > � to CU � � L cu � •� M E > U cu LJ O C c co O C n cu �_ O +� m +� m O vi = cu.� O N N� O O p Q O cu' cu4J Q C> a t +cu c O co �+ � v O Q Q c L O c 4 J 1 t cu+, O co cOo O co cu O cuO O 7 O cuO vi O O +J c Ca cuL N Q > Q N �to 0 O E E —O O a� E N 41 -0+' O� m UN N 2i O u c m Q O vi O > c N L U p} co Q N L N u ,} WOD dOD L to O N +, 4' Q O N O L vi m N p co O c E m N O O Q 7 O m U-0 N m m vi m 4 J Q O x U L CU 4-J co N cu N N 4 J W f° O O o o N v NCU � +� C- CU v w Q' N v Q= p } +� — 4' O L} > L > vi 4 J c N vi c vi c Ln c Ln c L 0 7 O Q O L O O O U N > — co co co co co +J +, c 1 � L cB O -0 Qn LJ ;t N Q +J —} N N N c N n +' c0 N O Q L N 7 N 4 J co > N O U co c O N 7 c> U N L O m U Q vi +' co a J U c N N N— U L N N f0 _ f0 N f0 N f0 L L �_ N� N 4, fo N -0 Qnn O 72 Q-0 c U co L 4 J Qi J m 'n Qi cu c-0 cu a. 7-0 c U U U U c L M 4 J CU Qn a„i +_ p L M N — N CU 4, 4 i -0 - O0 > cu p QC CU to N 0 O LJ O O WQ vi +J C C N > O > O L p > OL p N O dA C Y c > +J 7 L > O = m c O p L L N L 4• N N O O O } 7 N N c 2 Q 7-0 U a a Q a to a- 'A Q L aJ U U 2 7 m O U 2 7 o O _ _ _ fu cu cu cu cu cu 4J +J 7 7 7 7 m — m — f0 — Q co Q co Q -0 -0 -0 -0 � Ca Ca Ca L L L L > > > U � Q � Q � Q � Q O O Q 7 — 7 Q 7 Ca Q lu M 4 4 T i-0 CaZ,� a co tvo c Ca L c co L c ra L 4 4 c O c O c O c O 4J c 0 'u 4J c 0 u O 4 J a O +� a O +� a tXo Q -0 Q -0 Q io •V ++ O O +' + c Q c Q c Q cufC N N c co O co O w O O w Q U Q Q Q Q Q Q co Z:) co U O u O u O N L O L O L O L O L O L O L O L O L O L O L O L O Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q to to O U 4J U 4J U 4J U 4J U 4J U 4J U 4J U 4J U +J U +J U 4J U 4J co co co co co co co co m m m m U Q Q Q Q Q Q Q Q Q Q Q Q c-I N M U) LD c-I N M U) l0 �t lfl to to lfl lfl lfl c-I c-I c-I c-I c-I c-I c-I c-I c-I c-I c-I c-I cu to Ca d N X �L 4-1 m 2 H G! m Q m 4-1 t U ^m U O z Q X t t t t t t � � � � � v E Q O Q O Q O Q O Q Q m m n (o 'n (o a' 1 Ca a' (o a' N ^ i z p p p p p p cu 4- 4- LA 4- �_ 4- L C 4- C •� •� •� •E m C C C C C C C O O O O 0-0 O v O o a z a z a z a z a z z a X X X X X X 2 2 2 2 2 2 c U a C f0 iJ cuE t 70 cua N O cu= co C co L E N cuL C N (n 00 N cu�, O U O .Q p to O � O cucuW C Ln+' N U a- O a- vi Q N C N w L Q ^ .- N M U Q L L p 7 cu u c E N 4' C cu cu cu`� C Q uC L N O on 4• L L N O } (a N C N 4 J O C u O co O E m O 4L cu O� OC cuLU O i to L m O cu N Q O O O L- U O m cu O O O O O N Q N Q vi �i O cLo L N Q O m Um V f0 E N LJ Q N +J f Q .� O Q f0 C-0 � Q u c N L co � t .0 t N E N p O O U O O co aD ctb i u N >' 4 N� m O C L N cu N co Q .� +, co +J -0 O _ +' L, .`n L L w 4' N O +, N ._ -0 C C Q i ;. -0 o v o 0 o U a fY0 v L m � m L O m CU C Q 2i Q E E Q 4- — C N U C O co N vi m O C O O Q O O-0 O O co -0 O C L Q U C C (SS U C N 0A 4 J vi V L Q N U (J � C X N CU Q Qn Vctb1 N Q O - L .� O 4 J U L O `~ L N Q vi N-0 O U C 4 J N — O L O N C O a•'' 4J O _ L vi O v�i _ C � N C N Q U \lj �_ Qn N O Q N_ C i Rio C U t > C > O 7.- O 0A N V1 C v v L O � cu CUtvD Q a N 7 N OL N m U U 0p � tvD J Q co co cn -0 a-0 'n H Q •- • O m O N O Q a Ca Ca Ca of u cu cu cu Q Q Q Q U C U C N N U f0 U f0 U f0 U f0 N�2 u N :2 u Q V1 Q V1 Q V1 Q V1 U \ \ T t U � t txo fo f0 f0 f0 00A 41 N 00A 4v N G1 � +raU U cu U cu U N U N N Q to N Q to Ln Ln Ln Ln w H w H L L L L L L Q Q Q Q Q Q Q Q Q Q Q Q Ln Ln Ln Ln Ln Ln U m Q m Q m Q m Q m Q m Q V1 p p p p p p Il 00 m O N �# L.0 L.0 L.0 n n n c-I c-I c-I c-I n c-I cu to Ca CL N X 4-1 m 2 H G! m Q m 4-1 t U ^m U O z Q X t t t t t t t t � 47 v m U f0 f0 f0 f0 f0 f0 f0 m L CL CL Q CL V1 n n to to to L n to to n z p N p co co co N 0 m 0 m .� O {% co co co co co co co co v M m M m (B CU 3 U Q v> v> v> v\\ v> v> v O O o O Q O a O Q O O Q O Q O a z a z z z z z z z X X X X X X X X 2 2 2 2 2 2 2 2 vi O -0O O N C 4O CU a� U O N LJ fB %' E >, U C C f0 f0 -0 C O L C O W u 4J L _ O O O C O C 7 f0 4 J � O 4' C >. L O � N L 4- N MC vi > 4J C L 0A Q -0 OC C _ +J mC N N L N L ,O O N N N +� O � � m `~ vi ^ Q O O C L L N L Q C L co > C L t O U U O U (� 4- CO O O a-•i C Q m U N -0 cu cu •L Q O m u J t a•' c c +' >- N ,� L O U o C C >, C O cu 0 0 t' � v Lap C L U N N C O N m L U � j..i +J U � m N > O O cu U 0 - ++ � N O o o _ CU � N vi O Q- C CO O O co C O L +J C aA U- O N cLo N a-•� O LJ U O a-•� C w � '� O L V1 C 'O O m CU O O O N m O O ^ Ocu Q L — a"� Q M +J Q m - O +J " -0 JO t co > N O co = � O aA O 7 4 , C = co CO -0 m U p ^ cu � W (A 0 m -0 Ov 4 J 4' L-0 t t. N 7 N O m CU m } cu +J O +J > M 4' � C -0 N to u 'n •� vi O N coo mC to L Q w 43 Q >, NC N C L V1 N -0 � cu C O Z — vi U N +J 'L C m co C L 4% vi 0 +J _ m Q U cu 4• � V1 N � a. Q M O C C Q� C U L O O I c O Q , co N N O Q C co Y O O O cu mL U 4J O O c-0 Q O L J t C C Q � O 4- Q N mcu LJ t O +' +J N c0 ^ +� u LJ �- 00 O N�CU O N u u N N O 00 Q O cu EU N O N 7 i N fC0 O fC0 N m mC L N i C C CU O N Ov O Q to 0 O C N C 7 C m 4- O 0 �' 7 U > 7 L i N N N N a C > L 0A L > U "M O CL Q O t O O N +' Q 4' L a••' Q O 4' O O O O `c `� O — 04 J >, a Q >, > U i L M O - O L m L N 7 C 7 7 C f0 H a 4J C • 4J • O O w O (n o_ L Q o_ vi m m LL m (n m 2 N C 4J O° 4J O� 4J O� 4J O� +J O� +J O� v �_ Y U Y U Y U Y U Y U Y U U O O O O O O O O O O O O 4 C O J O J O J O J O J O J _ J J J J O J J U \ CU O CU O CU O CU WO W O i C t t 4J t 4J t 4J t 4J t +J t 4J t O CUU 4J Q 4J Q 4J Q +J Q 4J Q 4J Q U +J +J v a m O cu O cu O cu O cu O cu O cu a 41 w U H m Q m Q m Q m Q m Q m Q L L L L L L L L Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Ln Ln Ln Ln Ln Ln Ln Ln co co co co m m m m U Q Q Q Q Q Q Q Q rn In l0 Il 00 m O *k rl n n n n n n 00 c-I c-I c-I c-I c-I c-I c-I c-I 00 cu to Ca d t t t t t t t t t t t U 4-1 U U U U U 4 U 4� U cc 4 G U cc 4 G U cc 4 G U 4� cO cO CL cO cO cO �, m Ln +� CL z m " a-O M M (a (a CL f� .� Q C O O Qj- Q aJ .� v .L aJ +� _ } _ N _ Ca —_ n3 u i 6 —_ Ca —_ > —_ > —_ > } _ +J U f0 a) f0 aJ f0 aJ f0 f0 U f0 U a" f0 U f0 J aJ f0 J aJ f0 J aJ aJ 3 U U U U U :'~ U � OCL U :t U C 4� U C 4� U C 4� U O C O C O W C O W C O O C +' O z C +' :3 O z C 4' O z C f0 C O u— C f0 C O C f0 C O u— C O W Q u— v z v z v z x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 O cu U_CUE -0 (a cu Q V1 +� 0A vi > U 7 L O C f0 7 C O 7 a -J C C _ (AO N u Q > O � O C 4J O v t U m cu Qr L O O +' OCL Q Q m 4J 4 cu cHc G Ln > L cu O Y cu cuf U0 LO L Q U L C �' O C 4 C L cu ._ > O > a +� U 7 (a c ,0A chi aJ CU aJ cu Q 41 UUcu v O v cu O cu C N vi 4. O +J cO L a) Q Y-0 � _ U a) Z = O E m mC m Q aJ m — 4 J Q � Q > +J M aJ U M O aJ 4 J +� 7 C f0 L •� � L •� � -0 V1 Q L cu cO fC Q O f0 aJ O O 4O -0 WD C 0A u 4' N � > m vi U L Ca fC L O Q to L vi tvD O aJ C C f0 N C vi O t 4' U U aJ C vi O cu aJ c0 L (.i E n3 to O �n Q aJ Q N }_ > �O U C - m N c C U Ln c0 L 0A +� aJ aJ V1 U -0 aJ N � ((A U O O U O N O O U O L O aJ -0 Q O +� c M L L C C (n m U = Q >` aJ cu +J 4' 7 E 0 O 7 0A 0A 7 Q- U M O m 0-7 O-0� C C C O O O 7 •Eb +J 4 j -0 aJ C 4J = ^ U 7 C aJ m t cO � 7n O O CU `n CU +' aJ O > cO C U aJ _ v _Q U cu � cu O aJ 7 aJ Q cO cu aJ vOi m m c0 aJ N V1 Q n3 aJ c0 4 J Q n3 +� L V1 Q +� L C N (� aJ L aJ +J mC � L O a) C O O O U > N n O O CO WD L C C a) � C � O aJ 0A .— 4 J Q 4 J co i aJ -0 Q a Q-0 O �O O Q > M N M C p N N +� Q Z 7 O aJ aJ aJ O U Q +J U L U CO 4-Q " (D �i cO (n (n (n E I= Q O 4 E cO 4� C (a C C (a cua,o a,o a,o a,o c c c � +� aJ aJ aJ cu W W W C D D Q Q Q Q W W W i u u aJ aJ aJ cu Q Q Q > tXo G7 4- 7 7 7 7 O > O > O > 1 Q Q Q O O O O J (a O O U2iN v, v, v, cu cu cu cuO 4 4 J 2iN +J 2iN c0 Ln D c c c c aj v v v cu cu cu cu a,o a,o a,o a,o n3 n3 n3 n3 C C C C n3 n3 n3 n3 L L L L L L L O O O O O O O Q Q Q Q Q Q Q C C C C Q Q Q Q Q Q Q D D D D Q Ln Q Ln Q Ln Q Ln Q Ln Q Ln Q Ln cu U cu U cu U cu U 0 � � 41 � � � L L L L V Q Q Q Q Q Q Q Q O Q O Q O Q O G7 aJ aJ aJ aJ N cr- cr- cr- cr- c-1 M �t Ln N M 1.n l0 *k 00 00 00 00 00 m m m Ol m m c-I c-I c-I c-I c-I c-I c-I c-I c-I c-I c-I Ol aJ to Ca d t t t t t t t t t t t t U U U U U U U U U U U U ^y f0 f0 f0 f0 m m M L m m m m m Y Q Q Q Q Q Q Q Q Q Q Q W Q Q CU z M to to cu4� to C = C C C C C Ln C C C u M y M y M y M v M v M y MC: M y M m M m m y M m m U V1 U V1 U V1 U V1 U V1 U V1 U U V1 U > U > U \\ U > O O w O w O w O w O w O w O O w O a O Q O O Q a z z z z z z z a z z z z z x x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 2 N vi 41 L N > 4� C > Q� v C O 0 - O CU Ca '� L C O N O cO L cu N C � -0 `0 cu >, —_ CO C c0 0A Q V1 C 0A N L 4' M c0 N Q- `� C\ > O C u u U O O N t (o 7 O co co N t E vi -0 C to CO L 0 -0co �_ C +' vi +' N 1 N u U ^ -0-0 > � > u N *' co L O 0 O V1 +•' +� C f0 4J 4% L L V1 m C N 0 � N 4J L Q � i .Lap U co L (B L O L �� .Ucu C to 0A 7� cu N Q vi N M p N O +J N 7 N L m '� 4 J N m C '> p vi ^ 7 O m Q Q -0 L O � C p N t (^ to vi L vi � to CLD N a f0 L t 4 4 J O Ln N O Q 41 O vi 4 J O Q 0p co N +� .L O O v V1 N � L N O +�+ _ U C O O � N �-0 O 7 O cu N L C O v _ 4J L _ > C U C U f0 N L L N -0 O O O C C Q N i L cu Z 7 p O O C '} O O t iC Q N L U N c0 � O 7 +, +J m C � V1 N O 7 +� .O f0 U fO 0A 4J t U � a J f0 .O N Q v +J J +, OL p 7 u Q � > `� L N C ^ p Ca Q U vi cu N O tvD Q to a�J L O � N C c 4 J Q Q C -0 N O 4� f0 N— L O L p O � i � C � 7 C C co L co to +' � t O _ O i O a••' � C C (A WD O 4 J L co C C N=3 +' N N L O i f0 N > = U L O C C O f0 O� cu •L �O cu L N O co o p 'L U - co U > co 0 N > U N O u t o W C N O +' C L L L O — m N Q N 4 J O0 Q m N C i O 'C Q O O 4' C --0 a CU .CU > +� •Q }' � �, � •> ce U O vi 4" vi Q 0 •C N u 4O m N N C N N � C 4 J C � O OU N (A f0 E � p m a..� M M W f0 N M - O C 4 J N N NC i f0 L +J O vi Ccu Q L vi } J Bu ^ O N N C U C O N (n L v N 0A N-0 cu -0 Q o 4 Q C7 i L 1 N U O O Y O U p 4 J .O L L C 0D O L 0 C cu L N vi t 4J m U L N N 7 C 7 vi O N t � " C L 4J OL N �i �i > CL O co — Q L (n Q 'n H co > L a Q 4- Q M C U 4 J a O a O cu cu U U cu C � � � O O cu Ca Ca U v UiD can can can ^ to to to to L ,� C C C C N O ? ? ? V1 V1 U U U U c E CO E CO tLo tLo tLo tLo T \ U co co co fo fo ao an H H H H O N to an o 0 o H o cuo � � cu cu cu cu +� C C +J 4= +J N uCp N uCp cu N coo coo coo coo 4j O 7 `� `� -0 i5 � Y vi •LcuLcu Y vi � � N cu cuN m o m c c c U U U Ln LnQ Q Q Ch (n cr- Icr- G cu cu cu cu cu cu cu cu cu cu cu cu a,o a,o a,o a,o a,o a,o a,o a,o a,o a,o a,o a,o C C C C C C C C C C C C C C C C C C C C C C C C N a) N N N N N N N N N N U L U L U L U L U L U L U L U L U L U L U L U L O +� O O O O O O O O O O O O U vi vi vi vi vi vi vi vi vi vi vi vi G1 N N N N N N N N N N N N N cr- cr- cr- I = I� 00 Ol O -1 N rn 00 m O c I *k Ol m Ol O O O O O O O cI cI c-I c-I c-I N N N N N N N N N O N cu to CL C1 O r-I N X m G H G! m Q m U t U m Q H U O z Q x — t — t — t — t — t — t — t — t — t — t — t — t — t — t U U U U U U U U U U U U U U f0 f0 f0 M L M L m m m m m m m m m E Q O Q Q Q 0 1 Q O Q Q Q Q Q O Q O Q O Q O Q (� V1 uo V1 L V1 V1 V1 f V1 V1 V1 V1 V1 � V1 � V1 � V1 � n L z o 41 o v a ° �; �; � ° �° �° o 4 � 4 � 4 �� 0 v 4 �_ �_ v v v v M co M co M co M m C -0 C / C C C C C C C C -0 C -0 C -0 C -0 \v C / O O a 0 O w 0-0 0-0 O w O w O w O w O a 0 a 0 a 0 a 0 a z z z z a z a z z z z z z z z z x x x x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 2 2 2 cu > N ^ �' L C O N c Q co -0 O p 7 t } C Q a L au L u t 4 J qA vi O O (� cu U C dA 4' > -0 7 p co Q C N co C vi u L N cu p N co vi Q O C O dA O N 7 N > � N U � 4 O �} O L V1 C C }J = � Q� vi UA co vi � +� O N L 7 O = O O M p NC CO +J N WD dA 7 O +, vi _ � O N L 4 J Q- -a C C � O t N O m O C > ^ O N ZI p +' p 4� U L to -0 v -0 -0 v v >_ * o v, O U n o v v o Q Q 4, O O UN v U -0 v CL v Q aOO C Ln O N O 4�U `� N M NC QQ N N L Uo E m C � Lp LCim O O QO C � V +J m f> 0 o U -0 NL u m E _ m O O� NO U CC +J cu (A O`^ N CT +� 0V N U N p 4' CT toC C t LN LO C CL U^ N (a O QC-0 O L O � U L .Q 0 J N 4J ` N� C N O O Ca O U p 2� co to -0 � O U co z N N QO N 4NCf 4' Q N �(A Vi O U N Q U 4J U CVm -0 L NL to N C QOQ C +J ^7 +J WvJiD� O m -0 -0U Ut ^ M O E a)O C�' U L —O QU UM - m di -0 vn O ( C (A O a' (A 4, m O va) +J N 0 O p to vi . N u O .+O Nx CL N vN N M M N Vi1 N Q N C 4�u >` 0J cu 4J N >. O>, _ �co O OQ N O Q N LnN m C C N C v�i � L U fB vi = p OL p ^ U U f0 N 7.^ O C d' d' � w 7 d' w f0 LL O C7 c C +J _ H Q a- a- L.L to (n > Ur f0 C C u,o C C C o O 4� 4� 4� 4� 4� 4� *' ( c c c c c c u D v+ D v+ D v+ D v+ v+ D v+ ao a o a o a o a o L O O C C C C C C C C C C C i H J J io O m O m O m O m O m O O N 4J 4J C +J C +, C +, C +J C +J C +J C C C C C to C (A(A. C .O O O O .O O 7 N N N N N G�1 co O O O 4' O +� O + O 47 47 � ++cu -0 +' -0 +' -0 Q- -0 Q- Q i5 Q -0 Q Q O O O O O fC > > � `^ `^ -0 ^ ^ ^ ^ N N N N N U 2 Ln 2 cn Q Q Q Q Q Q C7 C7 0 0 0 C C C C C C C C C C C C C C N N N N N N N N N N N N N N N N N N N N N N N N N N N N to to to to to to to to to to to to to to C C C C C C C C C C C C C C C C C C C C C C C C C C C C N N N N N N N N N N N N N N U L U L U L U L U L U L U L U L U L U L U L U L U L U L O +� O O O O O O O O O O O O O O u Ln Ln Ln Ln ai v v v v v v v v v v v v v v � � � � � � = rn �t Ln L.D rl 00 m O r1 �t Ln L.D rl 00 *k c-I c-I c-I c-I c-I c-I c-I N N N N N N N N N N N N N N N N N N N N N N cu to Ca d N 4-1 m 2 H G! m Q m 4-1 t U m Q H U i O z Q X U U p U U U U U U U coo coo coo coo coo coo coo E Q _ Q p Q Q Q Q Q Q 0A cu cu cu cu V N 4, +J N 4, N N N 1 3 U Q c00 U > m U M N U vi ra U ra U ra U Ca N U vi O C O Ln C-0 O Q C O C O w C O C O C O C O w a z Ca z z z z z z z X X X X X X X X C 2 O 2 2 2 2 2 2 2 � L co O Q I -0 L Q O � a v, v, v N U N O to 7> � N �, E co 7 Q CO O p 4 J vi C Qn-0 vi m N 0— C7 O N L O L O C >` +J N— Z 4J (.n 4J = 4 J N-0 CU U N FabJ p Lcu O `^ N -0 E N L m ^ m 7 U C C > +J L L N C 7 O C i O Q O Q O _� 7 N pcuC I C C c X N L 4% +J p u 4= U 4, C U WD E u ' co O O `~ N U N 0 N N Lto t� N M N p O L +J N N -0 ++ i� Im �O i N N +� t o Z Z O C L L +� C N U _ 4J O C t 0A C� c0 c O t C 0 O 4' O u C vi Q N +- vi 4 J 7 fu — cu +� X ^ co O cC0 > C aUJ Q v�i 0A N j cu jto = O CL O N C N `^ +J N 4J f0 C vi f0 Q' C >, `n p f0 `^ i U �- C O N N E t O vi t u Q O Q V1 C p O +J f0 f0 O U C —_ N L N -0 m p �, N t L L N L 4, C 4J 4- 4. p C O +J f0 On U C L C U O C Ov � u Q U O Y N'� +J O i t co M 7 4 Q 4J C �, N N LCU L U c0 > t � N 4' Ca 7 N N vi >4 O � N 4, + M M 4- C L CU O O Q � +' +� to f0 Ca — 4 C Q 3 t_ }_ `~ C C 4' co N O O vi co N= Ln L WD p O p L Q C 4, co N 'n O w � C O cu > m 7 O vi N.� 7� U LJ E p WCDm N to N 4� N 4' a�J a�J co N LO N M O N p 4J E � c>0 >. � O `^ `^ 0A M N 7 L 7 N C 4 J V1 � C •F 4O Qn NC +� LJ N N .� O +� O � 'n O � �' C t N N - .T O0 N O L N +' N C- M L N 7-2 C O � C C O O C O C O ( N 7 >' L O N C C Y- 7 C N N O ,C f0 +J > U O > vi > Z vi O O— }' 7 O O U m N U o' C7 C� H Q co N X O C vi L O L L N p L L N U N U CT 4. .� ra Q Q O O O O O O C C co � 0- � LJ a- Q a Q Q 4 J Q co L Q co H U 4- C C C C fu fu fu fu U u u u u a,o a,o a,o a,o f0 Q C C C C T C C C C vi D D D D y O U U U U N N N N C N N N N '} '} '} '} O U U U U ++ O O O O 4' t t t t U C7 (D (D (D can > > > > c c c c c c c c c v v v v v v v v v v v v v v v v v v C C C C C C C C C C C C C C C C C C U U U U U U U U U C 7 7 7 7 7 7 7 7 7 V O O O O O O O O O G7 N N N N N N N N N Ol O c-I N M Ln l0 Il 00 *k N rn rn rn rn rn rn rn rn N N N N N N N N N N N N to Ca d 01 JO 4-1 N �L 5m L W ^m m 4-1 t U m Q H U O z Q X 41 U +J U +J U 4J U 4J U 4J U 4J U 4J U 4J U C 4J U QJ a +J �_ U +J co Q co Q a Q co Q co Q a Q co Q co Q co Q +J Q C � a co Q +J vi vi vi vi vi vi vi vi vi C is C Qj �^ C Z N N N N .2 T D D Q O c p D +J +J +J 41 N a — N = — N 3 U U N U N U N CO N U vOi CO vOi U vOi CO a o CO z U .n C C C C C C C C (n C O i C O ';z i C O O O "' O O O O O "' O w O w O a, O o; O O a z z z z z z z z z z a z CJ CJ CJ CJ CJ CJ CJ CJ (D O (D N { UD X X X X X X X X X U X X co cu N U -0 N m U �-I f0 C 0A 4� C CN C Q Q '} O O N tvD N cu >- 4' O CU E Q N to � `L° � � u � U } +J 7 vi LJ N N `° > CO 4E 'L U Q N 0A C 0p O C C M > -0 -0 4 J vi N C +J O > -0 t Q O +' L O N Q a N 4' co N N N C 4J O — N Q m 4� U O +J `� >. E C Qi E .L C Qi 4, M � tLD •Q m m +' C Q cu cu� X u •� cu Q Fu Q O Q C � m C v U -0 > i +J Q U 4: .Q Vl a-•i v 7 cu u +, Q C U U N N N L m cu _ N O +' C L +-� C 41 L O L t ro > Q Q L (A_ +� O fu L cu cu � C N ^ (A — vi O cu CU N j 4' > Q Q fC cu � CL Q O u > U N u U cu C 4� -0 N N'n LJ L fC m Q O C +' C C N -0 .7 L .7 Q U C LJ � 7 O U� f0 > C cu N > m C �^ C f�0 m m 7 7 N (A `� vi N f0 Q L L L � C >` U 4J U C C O C O L +J +J +J +J V1 +J N Q 4J +' V1 L N OC N L N N 7 O O N Q- N U C O on 4' > N N to >� m C m-0 t co m �� m E m E O > t C N O vi Q C vi C L C C +' O +' O -0 O .� N +J L, N E m 7 N 1 N N N 4J N 4J m io m Q 4' M N V1 U L C Q 4J f0 > L 4, 7 V1 > m cO WD Q N O co V1 L V1 4J Q V1 N cu L C cu Q V1 4� L a. M N L L L > > 4J 4J QU C O L N N � M N N NC � 'L L Wo >• 4 J C m m vi N Q f0 N to f0 N m m N f0 •� N 4J 4J m N f0 \ C Q C �O m N Q-0 w U N � {n 72 Q � � qA L �_ M O i vi N > U •> Q > > } 4O > vi t > 4 J U to N O O� • O C N N U O m= O Q 0 O O C N O N +•' O 'n N V1 m Q 7 7 n Q m m to C Q vi O L U a m L Q � a L> L a vi L a L Q a U E L L a Q L N a cu cu cu cu to to to to to to to to to to to C co C co C co C co to to to •� to to to •c to •c t t t t C 4' � 4' � 4' � 4' � 4' � 4' � 4' � v v v v > O >_ o > o >_ o > O > O > O L c L cr- L cr- L cr- L cr- L cr- L cr- T D D D D U V1 U V1 U V1 U V1 U V1 U V1 V1 U0 dA cu cu cu cu co Q z co Q z co Q E -Z co Q E -Z co Q Z co Q Z co Q E Z, u u u u U U U U U U U +�+ 4O cuN cuN cuN 4O N C C C C C C C C C C C cu cu cu cu cu cu cu cu cu cu cu cu cu cu cu cu cu cu cu cu cu cu a,o a,o a,o a,o a,o a,o a,o a,o a,o a,o a,o C C C C C C C C C C C C C C C C C C C C C C N cu N N N N N N N N N U L U L U L U L U L U L U L U L U L U L U L O +� O O O O O O O O O O O U vi vi vi vi vi vi vi vi vi vi vi G1 N N N N N N N N N N N Ol O c-I N M Ln l0 Il 00 m N N N N N N N N N N N m N cu to Ca d O r-I N X fc� G H G! Q m U t U m Q H U i O z Q X t t t t t t C N t C N t t t t � U +J U +J U +J U +J U +J U +J E U +J E U +J U +J U +J U +J co Q m Q m Q m Q m Q co a- O (a Q O (a a- (a a- (a a- co Q Ln C: � (A(AZ Ln to to .L E— 0� E N D N C C N N N N ++ — — � — N — — — — — — — — U 3 !0 N U !0 N U m U m W U m N U U U (a N U (a N U (a N U (a N U vi C vi O O C C> C O C O C C C C> o 0 O O O O O L O L O O O O a z z z z z z o z o z z z z x x x x x x v x v x x x x 2 2 2 2 2 2cr- 2cr- 2 2 2 2 C m - L E N Q +J N � N O O C Q V1 L � Q 3: i 2� � -0 N 4 J to to V1 u C � Q Q m N L 4J Y m +' m p 7 N O N -0 co N O L O a-•, m vi L (A t U L O U N +J Q U > L N Q a..i L O N +' L N +J L � 4, +' O p t t C vi m N -0 N Q C cu U Q O vNiO N > vi C Q � N O U N �C-0N - � U Ln N 4J Q Q (A-0\Q O �� >•Q UJ p 4 N O aA N O a U (o N 7 O C O O t co U (10 >, QU m \ (,0 N 7 O > M 4J C >` m m C u N `n +' N co O O +J O O aj +J .� Q co O O O i + -0 +' O +J to — O U i uto Q -0 �Ca N N to LNL U U Q v vi vi t X Ca CU 4� C CL fB Q Ln Q U -0 Q O Q O V1 +� 4 J >, f° C o Q V1 C •^ Q Q v a•.' Q v i- Q v � Q O (� O � O E •� N 4, ^ t i Q U p t 7 CCU OU > vi i M N E � vi O � O 4' 7 N� W O N N m C) Q- �� -0 C m a L C O ?i O •� N N a to 0A C 0A !0 u-0 U� N ^ - N Q E u 4 J C � 4 J 4, to co C '� C N :-7 (oc 4, (a co C w = vi � L O CU O CU N U M O0 +' U O U co — .� Q O O0 W >= a-•� O Q E 4 J - L p �O Q-0 C N cO O L L v. 4O to O C N m N-0 L C U--0O U-0 >C ^ - 'n cO N —' j N � O N O +' C Ca O Y `� U O 0A `� C fo +� v C L +' Q O 7 Z> >- O cu +' U vi vi N N t > U N t Q +' O L O t N O 'vi > p CU co 4J N M +' O O t >� N +J O O p N O L +' Q C Q Q" O U f0 aJ O Q Q O N U 4 J Q O U C f0 C -0 m L O a C C— Q L Q "U N 7 Q-0 u O Q- O t Z M U 4J N U vi M C Q L C L 4J Q `n -0 L O t a� 4J N C to to to to to Q \ \ \ \ C •C •C •C •C Q- 4J 4J 4J 4J O O O O Oo c c �_ c �_ c � 0 > 0 > 0 > o > (A�_ L � L � L c L � L _ �"' C U O U C U C U C _ U C A U U (A m co co �co cfo0 �4 4 4 Qa' O m O m O O O dA O E z 0 E +J 0m0m0 E *z E z E 1J cu > > co > > co " �' " U " (A to +J +J co +J +J 0) ++ O 4 J a% L O 4 J a% L O +J cu L O +J a% L O +J a%In L Q +J T Q C n Q C n Q C n Q C n fC 7 Q Q Q Q O N > > > > U Q Q Q Q Q ol co acr- L L L L 4J C 4J C 4J C 4J C N N N N E E E E N N N N C C C C C C C N N N N N N N E E E E E E E co co co co co co co 4 J 4 J 4 J 4 J c c c c c c c c c c c co co co co co co co > > > > L L L L 4J 4J 4J 4J 4J 4J 4J \ \ \ \ C C C C C C C 4J 4J 4J 4J D D D D D D D C C C C \ \ \ \ \ \ \ O O O N N U L N U L N U L N U L N U L N U L N U L U U U U O V O O O O O O O O O O O O 7 O \ \ \ \ — — — — 0) N N N N N N N !0 !0 !0 !0 (A cr- cr- cr- cr- = U IU IU U O c-1 N rn �t U) l0 Il 00 Ol O N N N N N N N N N N N N N to Ca CL U U U U U U U U U U U U co co co co m m m m m m m m Z N N N N N D N .2 .2 N D .L T u C i — C — C — C 3 io N U (a N U (a N U (a N U (a N U m N U (a N U m N U Qn N U M N U M N U (a N U m p p p p p p p p In p p p c O O O O O O O O w O w O O w O w O w L.. z z z z z z z z z z z z x x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 2 v c -0�+ O v+ cu 7 N O L C t O tvo O U Q U O +; Qj •L U co E L N N N 4 E O +J O _ L c N O co N L *' m C N Q O cu u C- N CO cr C N p O > a-•� m +� Q Q Q •� C u L a„i C Q Q cr C N C Q �% C O m L �O = N p 4 O L u 7 .E_ LJ -0 X +' 4J vi O O N 7 n m C >L U O C 0 Q .0 N u � +' '� N N O� O N Q -0 i5 � v v p - O c N u Q N �O U t m— v Q '� co � 7 ^ co O p � io C co Q +J O Q O Q 4J N L C � Qn w N C U N O L Q 41 _ -0 V1 L CO N N = N 0) U L +cu � V1 7 vi L Q Q N +' � .vi L p � L 7 N i � N O LJ U L CL > C C C cu >, v v, v E +, C C m v v ao v C 4, C U\ L ; CO O Q N L M L L V1 !� N -0 Q U L � L Q N v o o�-0 4= Q o C o Vl Q to} C C co O 4' � +J Ln p 7 vi vi co N O C O O O m cu co O N C p O > N ra U co Q� - L 4 J N L O > Q' O O +' u O OB j `^ N O cO V1 4' Q - 7 CU CT N � L N N N +J U +' M 4 J N C t Cn w C fB Q� +J Q O 4' U � L N qA N vi O ^ N +J 7 C `1 N fB N O u > f0 U +' O � 4J O L 7 (A u m 0 N C fB C L >, C N N ( 4' L� +� C Q a, > +' N N fu Q cO N � O t O a Q N-0 C L N co N O L t O u co t +J Q- O co c- +J — O t f0 O D C N to Q- u = C Q f00 N N � -0 +J E � U C U' -0 4 J C L u Q v > w w U N m O L E C C c N N Q >, N > N N m cu O N p C U C vi u U Q `~ O N vi u N vi +' C N f0 4' vi Q 4J m N vi cn M w > t t > 4J 4J N ^ � L m Q N +J -a- u co Q O L Q 0 cn N O vOi +' C Q t > t U O > (0 > O O 7 O O U > N O Qn Q Q Q" L O OL O Q 7 7 N O O cu N N N= O N N N N >� N t m O N d V1 d V1 a- �} � d Q L Q d > U L L a. d Q N L Q Q Q \ \ \ Ca co co co+' +' c to c c c N N N U v c -0 -0 -0C C C 7 N N N N U U C U C U C -0 -0 -0 o N to •� to •� to •� to •� Q � Q i f O coo f O coo f O coo U C U C U C Qn Qn Q N Qn Qn Q N Qn Qn Q N V1 V1 Q N V1 cn N O > > > N N N C U p N L N L N L N L N L f0 +J C f0 +J C f0 4J C m m m m V1 'U m m O m O m O m O }1 Q- Q- Q- -0 -0 -0 CL Q -0 -0 fC �' > ^> �' > Q Q Q ^ v Q v Q v Q v Q- v Q- v U w w w D =) = 0 D cr- D cr- D cr- D c C C C C C C C C C C C C Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q to to to to to to to to to to to to C C C C C C C C C C C C 4J c +J c +J c +J c +J c 41 c +J c +J c 4J c 4J c 4J c 4J c v v v v v v v v v v v v > > > > > > > > > > > > w w w w w w w w w w w w \ \ \ \ \ \ \ \ \ \ \ \ +J c +J c +J c +J c 41 c +J c 4J c 4J c 4J c 4J c 4J c 4J c N N N N N N N N N N N N U U U U U U U U U U U U O C C C C C C C C C C C C G7 m m m co co co co co co co co co (A U U U U U U U U U U U U c-1 N M �t U) l0 1l 00 Ol O c-I N to lfl lfl lfl lfl lfl lfl to to rl r N N N N N N N N N N N N U) N N to Ca CL O r-I N X �L fc� G H G! Q m U t U m Q H U O z Q X O t t t t t t t t t t N t � U +J U +J U +J U +J U +J U +J U +J U +J U +J U +J E U +J co co m m m m m m m cocu co co 3 U U U U U vi U U U U U U -0 O Cvi O "' C vi O w C vi O w C vi O w C vi O w C vi O w C vi O w C vi O w C vi O w O N O L C vi O w a z z z z z z z z z z o z x x x x x x x x x x v x v c to -0 c O O c L c to � a w C tvo Q 4- L v C U O Ca C C Q L C cO C O O N Q O L N cO O N Y O M 7 O U 0A O O ' +� CL C O L F +� O C U, N cu ON 4�to 7 C cu > � O u � +J N co > O > +J 7 O vi Q O v L t ° _, .O I to � .>, >- O +J � t c m m a"' ai 7 U U N cu O�� O f0 cu +� 7 4' -0 O N C� cu Q N 0A +J O L C cuC N t 7 0 vi N O t O O � U" O C f0 tLD C +J O L Q O N C E Q 4, co WD � O vi L +J Q _ cO '{n O L co �, `� N �+ O C 0 O N N O � — L O >� OU N a�-J i (B +' N L vi > O N to N to O 7 �O 7 -0 C f0 f0 > c0 �� N C 7 O WD cu vi fB = � .� f0 L vi N � fB fB O ( 4J (A fora C A L Q Q o cu �"I E c C .0 cu N t fC �O > O � co O t +J 4' � f0 O 7 C ^ O L vi C 0 co 7 t o C co N C C U O N U ^ N" O O E Q N > 4J vi (A O O N m > +J O O CL O O O U-0 O N O tvD U Q O O +� co v m U-0, u C U u= N Z N L O Q .O O O a••' - cO i O O vi O Ca 4 J O Q *� U O O O CU u N � � to to 0 O uA o Q +� v a�j v M 41 > cn C 4 J .0 4 J m a- +� C 4 J +' , N C Y fO i �' — t L O Q w N U O N — vi m — C .� � L � L +� V1 Y -0 cO N -0 U O 4J _0 — N t p ( co N Ca qp (�i — Q r (a O co co co -0 L U +' CU 4J �O N C Y N C ' c� c 4, = O N v +, O N O `� N N 7 O U O C 0A O C 4to � O ate' N-6 N N a� +.I •� a� N a� N N O L L m O C U C N m O .O N +� c i C 4J m 7 O N O E O 4J N C C 4J N O C N EC U L N C N > O L C O L '; O L Q '; +J 7 N �' 72 N � > N �� -0 C .2 M N Y o L I o CT O ; ; L .2 > O ; U o a� o .o U o +J U> o o — C v O v m O O v O v c C C N N Q L L-0 d a..l N-0 d C U Q Qcr- C 7 CL .0 CL C L CL 4 Ca Ca Ca Ca c to c to c to c to v c v � v c � v c v � v c v 12 aEi CL a a aLn i cn `^ N n `^ N N u u u u D D D D D D pip 4O j 4O j 4O j 4O O m O O O LapLapLapao Lapao LapG1 ++ ' ' � (A (A(A fC Q- N Q- N Q- N Q- N vi vi (A vi vi vi vi U D Dcr- Dcr- Dcr- Q Q Q Q Q Q Q 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C N N N N N N N N N N N N N N N N N N N N N N 0A 0A 0A 0A 0A 0A 0A 0A 0A 0A 0A C C C C C C C C C C C c c c c c c c c c c c v v v v v v v v v v v > > > > > > > > > > > w w w w w w w w w w w \ \ \ \ \ \ \ \ \ \ \ 4J c 4J c 4J c 4J c 4J c 4J c 4J c 4J c 4J c 4J c 4J c N N N N N N N N N N N U U U U U U U U U U U O C C C C C C C C C C C G7 co co co co co co co co co co co (A U U U U U U U U U U U rn �t U) l0 Il 00 Ol O c-1 N rn U Il n n n n n n 00 00 00 00 N N N N N N N N N N N N cu to Ca d C1 O r-I N X �L c� G H G! Q m U t U m Q H U O z Q X t t t t t t t t t t t t U U U U U U U U U U U U co co co co m m m m m m m m Z 00 L N L N L N L N L N L N L N L N {.% m M Q U M Q U M Q U M Q U (a Q U \\ (a Q U \\ (a Q U \\ (a Q U \\ (a Q U \\ (a Q U \\ (a Q U \\ M Q U \\ O C O w C O w C O w C O w C / O C / O C / O C / O C / O C / O C / O C / O a z z z z z z z z z z z z C7 (D (D 0 C7 C7 C7 C7 C7 C7 C7 C7 x x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 2 Ln (n NU L U Q Q� Q U- C LL U E 4J 0AQ N O cu O Ncu N Qn 'v O Q w+ Qn O C 7 `� C 0 U C O +' C �O C f0 4J (A (n U N N a�j Q co a-J C •C Ca CL 7 Q- co E vi L vi N 4„ +J L co C NC O C 0A Q f0 Q L N N u _0 t o co Q 0 4' N C Q O C 4O O C 4- n Q 0 4Q 0 4- •C C L Q a� O +� O `~ C > 0 +� C u O C O — E C N> O O 41 O c L N co u .— +� C O OU > > w C vi U 0 Q +J U tB C 0 U N +� N 0A > = t 4J 4J f° fB N O L . -0 N u N O N C N C C N to •0 }Ti _ C 0 L � +' — C O L O U p L -0 -0 0- C 0 0 = C 4J L (n w � C �O 0 C I' C f0 +� C C (B vi C � � L 0A fB C a"i C C C 0 � Q +� Q O C C f0 C U f0 L 4J Zn L •0 O •C f0 4 J C f0 � C O O vi N C - O 0 E L +, O C 0 O cr to f0 a-J 0 — N M O C u N co Q O O u L co O co t +J L -0w -0 -0 O O= N "> L vi � O U O O _ vi C 0 C N Uto M > L N -,.J C N t U O C +� dA t +� U C WD N +' f0 co CO (n O -0 L .0 7 -0 t +-' 4J .C_ N m Q C C V1 U C O O Q O C w C� O Q L U CU Q Q L �_ O f0 f0 f0 Q vi +' Q- � +� +J >- N L f0 vi C 0 C — p O Q 4' N M > N U C (A C N N N C N c0 C t j •U N N +' 41 C 4J 00 O O O •0 t +� t t v v p 4' - vi co - +' UO t > 4 J 0 V O N N w N U t +� cu 4, ai 4J cu E v v +� }J (o O +� Q +� co }J o 4' ao v +J U (o +� v U C aJ L 4 J v (o �_ a,.i �_ v i +J f0 u N a-J C +' L a-J 0 E +J N N V1 > C QdL > C Q > Q O+ C N Q N- O > N 0 L > 0 Q 0 a Q N O UC > Q > Q 0A m Q 0 Q U Q N cu O Z i LCU m m m m m m m 0 0 0 0 0 0 0 0 +J c +J c +J c +J c 41 c +J c 4J c 4J c v v v v v v v v i 4' C 4' C +' C +' C U C U C U C U C U C U C U C U C O D D D D N N N N N N N N qp C C C C + 4J 4J 4J 4J 4J 4J 4J dA an ao ao 41 Q Q Q Q Q Q Q Q U Q Q Q Q D =) D D D D D D 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C v v v v v v v v v v v v v v v v v v v v v v v v tvD tvD tvD tvD tvD tvD tvD tvD tvD tvD tvD tvD C C C C C C C C C C C C c c c c c c c c c c c c v v v v v v v v v v v v > > > > > > > > > > > > w w w w w w w w w w w w \ \ \ \ \ \ \ \ \ \ \ \ +J C +J C +J C 41 C +J C +J C 4J C 4J C 4J C 4J C 4J C 4J C N N N N N N N N N N N N U U U U U U U U U U U U O C C C C C C C C C C C C G7 co co co co co co co co co co co co N U U U I U U U U U U U U U �t U) l0 Il 00 Ol O c-1 N M �t U) U 00 00 00 00 00 00 Ol Ol Ol Ol Ol Ol N N N N N N N N N N N N N Q to Ca d 3 0 U U U U U U U U U U 4-1 Z p N p N p N p N p N p N p N p N p N 3 U CUU CUU CUU a)U a)U a)U a)U CUU a1 m O C O C O C O C O C O C O C O C O C O a z z z z z z z z z X X X X X X X X X 2 2 2 2 2 2 2 2 2 to 2i a) 4� E � aJ -0 U a1 N tY +J O a�jcu `cu � � O fo _ aJ U C aJ +' cu cu au Ca > O v�i CU 4ra O 4O CU aJ L Q 'vi C fo O 4J U +J L O `n p `� fn O C .� U C N — 0-0 \CU O C t O 4J vi aJ a� CU aJ cuZ -0 O O >-Ca 4' Q N C U Q fo X O t +' ^ vi C: a) L 4 J O C Ca (-aaOj U L C C C to +' C 4J O a) L cu vi Ca +' U 7 cu 4J '} O 4J a) j N aJ fo v C O cu t C O L O 4' c v (A > fo C N " 4 J _ to f0 O vi L O 4' to " a•'' C L CL C C •L 7 +� -0 f0 aJ C aJ cu � Q L +J v O v = C >-0 m O c v >- O v u aJ t to 7 O 4 J O u U M Q C O L fo C O 4 J _ p Ca CU O L cu V L a) }J V � L Q C m U L C V1 m a. L L N > -0 N -0 O C U O C O O to O O O CU(AO O- C w aJ >, `� C > 7 aJ >� fo i aJ i C m� C i L m � N N N +' cu + L N � +J +J m O 4, +' O Q vi N Z > Z t, Q cu � UU O CU aJ aJ -0 w aJ - C CU vi f0 �i aJ aJ O C C � aJ } O � n C O m C= +' dOD .0 laA N ^ aJ C N O 72 N v +J M qp aJ O a= O 4J 4J C C C fo O� t O +, L w O +' � aJ +J fn C >. m �_ C +J C �_ m f0 aJ �_ aJ aJ 0 > > N aJ 0 �_ C C O � - m +j . w N f0 > — — > to > -0 � > > O Q U C > U � Q L O cu u m O ^ U U > O t ^ O > O aJ U a� 7 w 4L a tr a a U- a U m C Z a1 a p L a) L a) L a) 4� 4� p 4- Qn � >, ' V1 >, ' V1 >, ' L V1 C O >, L V1 C O fSS fSS fSS C vi to aJ vi to aJ vi to aJ U N U N CU O O O L C f0 L C fo L C fo vi C U vi C 4(. +� +� u o v U o v U o v U fo v v fo a) ai a fB fo fo i a1 E\ a1 E\ a1 E\ m E m� E Q p Q p Q p 0 cu onC to C qp C L cu u L cu aJ O to >C >C >C to -0 to � -0 to � -0 W a..i � m c n 4. C m 7Q � Q � Q Qf0 U f0 U f0 'U fL0 f0 m m f0 vi U vi U vi U U p Q Q Q H p p p p p C C C C C C C C C aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ a) a) aJ to to to to to to to to to f0 f0 f0 f0 f0 f0 f0 f0 f0 C C C C C C C C C fc0 fcc0 fc0 fc0 fcc0 fc0 fc0 fc0 fc0 G G c c G c c c c c c c c c c c c c cu cu cu cu cu cu cu cu cu w w w w w w w w w +J C +J C +J C +J C +J C +J C +J C +J C +J C aJ aJ aJ aJ aJ aJ aJ aJ aJ U U U U U U U U U 0 C C C C C C C C C U G7 m m m m m m m fo fo N U U U U U U U U U l0 rl 00 Ol O N rn *k Ol Ol Ol Ol O O O O O N N N N rf) rry rry rP) rP) 00 N aJ to fo d O r-I N X �L f5� G H Q M U t U M Q H U O z Q X -��, v t o t t t t t t t t t t t U U U U U U U U U U U U a -• co � �, co co co co co co co co co co co — +J E Q Q Q Q Q Q a- a- C_ C_ p C_ p C_ U C Z L {� C o v a m L p v L � v L � v L � v L � v L � v L � v L � v �� (n � f° (n N � t a i — — � — � — � — � — � — � — — C — C �.�/ v U 3 f0 N ,M u a" � N U N U N U N U m N U m N U m N U N U f0 f0 U> f0 f0 U> f0 0A 0A U C � C � O O Qj O O O O O O O O O Q O a O Ca z z z z z z z z z z z v � a (D (D (D (D (D (D (D (D (D (D (D = x x x x x x x x x x x x U co C an an co p U Ca i, _ M N M 4- O �O a M N ' Q x m L >. +� C -0C C 3 w O U N O ^ C +' au O +� N � c0 ^ 7 O vi N acu N > O L 4• (n -0 f0 > 0) U (n i •� �' � cu v v v C (^ 7 co O 4J \ O (n c C 4' +J O C (a 4' C C 4J �' ^ (n w 4- O co O E L O w U >. N > > N 4J - t to 4 J •Ca U } > a C co C O N � a-•� � a O LO O -0 (n N � Q N C N N w LNL LNL N }J C o Q Q Q C 4 O� N N U U C t ; U co — 4J cco > v > +J •— v U w u �+ O Vl o U N fB L V1 0 U L) O f0 +J N +, p p N +J 4• C Z p M 4, is 0) fB — f0 U V1 •� N di C� C fSS U U t 4 J di >� U-0 Q ^ ��= U m N C N t o w U Q > N p ,C U 0A C N � C N m E cu O U 4 J (n 4 O N� O O +� tvD C C L N C C N- L Q +' O C- O C N O 4• f0 U N C n t n co m cu CL L cn � tLD > m U N� �� N LJ 7 O C U t t .� O O O = O O O O Q u Q 4- 4- u> +� m 4' >, >. C_ > -a In N + >, WD O > >. >, 4' � p M p L O N L n Q 4J 4J n 4J Q N N to +, 4J C 4J +J 4J 1i 4J p O p > C_ C O� LO L - to 0 N-0 N- ZZ Z E +' � m WD C 4J p m n � Q > m C_ m m m O m } — N O 7 o N 0A v O O U U N O N O N - (n 0 41 ON O 4' m N NOt• O L t � •C� CL > C N(,0 a, LC -p a- O _wa- 4J U ' a„ a- a, co4- _ OM E > •OO m • • N C C Q Q > C (n CU —O n O O M O M OmOp J � QO 7 NN LL CU o M> o > U ua O d E t a41 .� -0 w n Z c a a C a 7 a U C 2 7 N U m a O O O O O O +� co -0 co -0 co -0 co u u u u u u> Ca Ca C �. 0 0 0 +J v i +J _EO dA > c c c c N N N N N N N p m :E 4' E m N m N m N m N p} m G1 Q �_ Q � Q � Q � Q Q Q Q Q Q m Q— Q ++ fC U U U U O N O N O N O N O N O N -0 U -0 Q (A m U O > N U d' d' d' d' d' d' Q J S Q 0' C C C C C C C C C C C C C C C C C C C C C C C C 41 41 41 w w 41 41 41 41 41 41 41 a,o a,o a,o a,o a,o a,o a,o a,o a,o a,o a,o a,o f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 C C C C C C C C C C C C fc0 fc0 fcc0 fc0 fcc0 fc0 fcc0 fc0 fc0 fc0 fc0 fc0 G C G C G C G C C C C C C C C C C C C C C C C C v v v v v v v v v v v v > > > > > > > > > > > > w w w w w w w w w w w w \ \ \ \ \ \ \ \ \ \ \ \ 4J C 4J C +J C 41 C +J C 41 C +J C 41 C +J C 41 C +J C 4J C N N N N N N N N N N N N U U U U U U U U U U U U O C C C C C C C C C C C C G7 m m m co co co co co co co co co N U U U U U U U U U U U U U) l0 Il 00 Ol O c-I N M U) l0 rn rrf rrf M rrf M M M M M M M Ol N Q to Ca d t t t t t t t t � � � � L � L � � � L E f0 Q f0 Q f0 Q f0 N Q fo N Q m Q m Q f0 N Q f� N z cu cu cu 0- Q cu cu 0- M 3 U O U O U O U� U= U O U O U=> c c c c O O O c> O> O 0-0 O O O O O v O v O O O v a a z z z z�2 > z�2 > z z z�2 > (D (D (D (D c o to cu � cu 4J C to 4J v Ca i5 to t CU U � O O c �' `~ f0 t >` O � N c E vi N '} N E 4 J O c N aUJ M M Y Q c cu U vi +J c I � — +J O (n U w m N Lcu � O (Y'I ZI 7 cu � N m N i WD O +J L c U LJ O C O a..i Ln O 'V1 - U c i 4 J � U O O Q Q Qn �' N Q N U- U� Qn L Q co L O ,} a-J c d `� '^ U i O c Qn � � O L � +J O O O co ai L O O c +J � 0- O CL � N m cuO c O N � m .O -0 � � CL L (B Q L L c c v fC° o CU +� Q O -0O -0 -0 c m M N U v O U >, v, O Q O a >. O L C w 4J a.J O m m cO Q v N t O U v m U O ("U L O o O O 0 4J +J 4• CL �, Q 4J m Q aJ +J U vi t U v (�Qn O fC C, co S N E N t � m 7 Q O cu N 4J } Q O +J O +' Q UCL L co co (n O a•J c •� O m Q O+ a•J „ -0 w � di O '} c (.i cu Ou cu co -0 CL f0 f0 Vl Q t O O � co N Y u Q a•J Qn— N 7 _ co UO i � i� ^ O M m CL 4O 0 i co Q L > O �+ •� cu � Q a�J N c Q to Q c a•J co co N �^ N O +J cu cu U +J O +' . O �; L co O vi N +' +J t O 4- N c t a U Q co 4' v O +J a�J co 0 N-0 4J � 7 N M"" i5 N 4J -0 m O +' = c N n N 7 cr N Q co m m N N L UO (� O O Fa t L— m aj Qn N � Q Q - M a.J O cu (� � C O N 4••L O O a�J cO N +J Q- 7 m N i m N � L � V1 to O N c N 0 Mi +J O Q c0 O m t N +J vi N vi O cu .� N 4' L Q t N N Q t vi cu L � O, cuO 7 4- -0V1 U-7 CL co a-J E O E cuO0 Q-0 LJ V1 i m 9 cu > N �O N Ou CL O v Ou O O O co cn OU 4 Jcu O N O 7 O +' 2 +J O .S � Q co d E L Q E Q E Q O OM vi O vi O- m Q t E f E Q-0 m m m m m m O O O O O O N N N N N N iz LZ LZ LL LL LL to to 0 0 0 0 o O c c U U Q < Q Q Q Q O O c m O O c M O O c M O O c M O O c M O dA c c tow to w O to w O to O w to O w to O w 0) cu cuO Q U CL CL J U J U J U J U J U J U +J c +J c +J c +J c +J c +J c +J c +J c 41 41 41 41 41 41 41 41 E E E E E E E E f0 f0 f0 f0 f0 f0 f0 f0 c c c c c c c c fc0 fcc0 fc0 fcc0 fc0 fc0 fc0 fc0 G G C G C C C C +J c +J c +J c +J c +J c +J c +J c +J c > > > > > > > > w w w w w w w w +J c +J c +J c +J c +J c +J c +J c +J c N N N N N N N N -0 -0 -0 -0 -0 -0 -0 -0 U U U U U U U U O c c c c c c c c G7 co co co co co co co co (A U U U U U U U U 1l 00 O N rn U)l0 *k c-1 c-I N N N N N N rn rn rrf rrf rrf rrf rrf rrf O n•f Q to Ca d t t t t t t t t U L U U U U U U U Q Q Q Q Q Q Q Q u io N N M N M N M N M N M N M N 3 U U U U U U U U m O p p O v c vi O w c vi O w c vi O w c vi O w c vi O w c vi O w c vi O w a X X X X X X X X 2 2 2 2 2 2 2 2 4 N O N a••' c f0 c •� -0 f0 f0 4- 4- 4� -0 O ' U N 4J 4J 3: O N O_ > L � tvD >- N O 7 4� 0f0 O N '� N +j cu t -0 f0 U > f0 0 c c fL t u +' QC N p +J `0 O 4 J c 4. fo L vi fo O 4 J L � -0aJ C > L O O c O c }J p N t �O �_ a J f0 O i N N N L }' c O O N N O � m-0 cu N Q p Eb OC L N > Y c N N c f0 U O 'L C O� �. ++ Q E U N a;f0 > O O f0 > � N vi > 4J O c c Ca u O Q L L 4 J N c 4 J fO `� U > �' c N N C cu L to fC N O O O E O N O N w> +J LL O O U U +J N p c � N �-J NCU - a'' U N t +� WD O > p toC fo Lnw L +' aJ aJ � fo O -o L vi t fO � N L >. � O � >- Q . = vi L o E N = � fB cu (B > cu Q fu c a"i = :cu v O U +� Q to v > o v Vl ma c" O L N c Q' c p +' p vi 4J `^ fo N L N N N i= p � L � N fo Q fo N c i •N +J .� V1 O � +J CC N i � N > w u a-J N C L 4% vi a�-J a„ ' E -0 i N fO — O C �' N� cu V1 m O - O 4 J U p N CU U O U +J > t OA cu U OC > Q Q 7 7 O} vi vi O OL N O — p — to U N m Q Q Q '^ C � Q} `^ N to fo Q fo O fo O a-0 Q Q O tY Q Q-0 +J f1 -0 0-0 m p +J +J +J +J +J +J +J v O D O D O D O D O D O D O D c v c v c v c v c v c v c v o fo ao fo ao fo ao fo ao fo ao fo ao fo ao p in in in in in in in Q E o E o E O E o E O E O E o c c in 4� in 4� in 4� in 4� in 4� in 4� iCU N N 4 N 4 N 4 N 4 N 4 N 4 N4� do to Q N Q N Q N Q N Q N Q N Q N Y41 c Q O u O u O u O u O u O u O u U J U O O O O 4� 4� 4� 4� 4� 4� 4� 4� Cc C Cc C Cc Cc Cc C Cc Cc Cc C to to to to to to to to f0 f0 f0 f0 f0 f0 f0 f0 c c c c c c c c fc0 fcc0 fc0 fc0 fc0 fc0 fc0 fcc0 G G C C C C C G c c c c c c c c > > > > > > > > w w w w w w w w \ \ \ \ \ \ \ \ 4J c 4J c 4J c 4J c 4J c 4J c 4J c 4J c N N N N N N N N -0 -0 -0 -0 -0 -0 -0 -0 U U U U U U U U 0 c c c c c c c c G1 fo fo fo fo fo fo fo fo N U U IU IU IU IU IU IU I� 00 Ol O c-1 N rn �t *k N N N rn rn rn rn rn rn rrf n'f rrf n'f rrf n'f rrf r-1 m cu to Ca d t t t t t t t t O O t O cuU t O cuU t t U 4-1� J U +J U +J U +J U +J U +J U +J U +J � U +J � +J E +J U +J E m a m a m a m a fo a� fo a fo a to a fo a to a to a fo a m Ln � Ln to to to u io N M N M N M N M N m cu (a N F (a N (a N 3 U U vi U vi U vi U vi U vi U U U U U U C C C C C C C C O C O C O C C O O w O w O w O w O w O w O w O L O L O L O w O w a z z z z z z z z o z o z o z z x x x x x x x x v x v x v x x cr- L C O N qp Q to w fa Q cu O LL• L � L U CaCa O +C' cu u Q t aJ U U w U C0 +' cu f0 i C 41 cu c t 4• L fo co aJ > Q% 4'Ca Ca O U U O +J C 7 Q cu > C N 4J � O L O O U .to_cu �, a v a ai 4. cu 4� U t v Q -C to (n L �_ vi ,} CU f0 v - Q v fo o U c f0 4- O CL O O +- 4' 3 fo t vi > U v aj vi a fo a OO= t i cu aJ aJ C Q O cu >- aJ T f� >' >. 4 � cu � L � L W cu _ U i M � +� (a f0 v � � fo aJ t aJ f0 co -0 E fo Q -0 L a1 Ln ( w = a-0 C O Z U O N Q a Ca L fB i U L +, C U O> Q E OL E Ca aJ 0 cu Q U � O aJ 0 O LJ aJ - O to N C C� v O L O a cu 4' O O U aJ +� O f0 7 U vi to Q vi L -0 +J U O !E t co C t N aJ aJ -0 vi L O L O f0 f0 C aJ .0 L C O U L C +' U vi -0 a f0 f0 N > ^ ,O Q> too > O O> O O co O O • > -0 i5 aJ (A f0 O O N -0 � aJ U m vCi " � — CU L NC 2 Q + — O �O CU '> to C O aJ — 4, — f0 z t •v 4> aJ — t 4' aJ — — O v C -0 aJ } aJ Q C C w f0 � aJ Q 7 O f0 > aJ aJ U (n f0 U f0 }J O N '^ vi f0 L E aJ -0 f0 a) f0 N a) > +1 L aJ = N -F aJ to aJ = -0 N -0 O = C vi Q = - L \ aJ t +J t a) a a-J O U C +J N aJ - a-J f0 a-J f0 a-J a-J C a..� \ a-J 0 - O � a1 � -0 V1 -0 f0 a a) 7 7 L a) -0 Ln -0 aJ i *' aJ aJ -0 > aJ • •{n 4. > C C CU V � > ai -0 -0 a) O a O aJ > > L � f0 Q > C �; > cu � aJ > 4• O a, O t C t CL O L -0 O aJ to aJ Q to Q u a>i Q-0 m a� fn � fn a m m a a4� CU a U a +' 4J N N •C 4J O N C O -0 a -0 a N U U ' C N C C C C vUi C vUi f0 to + C 4- C 4- C 4' C 4' C 4- C 4J C aJ -0 aJ -0 cu -0 cu Q Ncu cu cu cu cu cu cuC C C O w w w w w w a O a O T j7j 4� -0 -0 -0 -0 -0 -0 L L L V1 Un O O C -0 O -0 O -0 O p c p C 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 � Q aJ c Z c Z c Z aJ U aJ -0 aJ U aJ -0 41 aJ aJ aJ aJ aJ aJ O f0 O f0 O f0 7Eb m' fa c O U U U U U U aJ O aJ O aJ O O O U O O u U - Ln Ln Ln Ln Ln Ln N J fn J N J Ln 4J fn +J C C C C C C C C C C C C cu cu cu cu cu cu cu cu cu cu cu cu C C C C C C C C C C C C v v v v v v v v v v v v a,o a,o a,o a,o a,o a,o a,o a,o a,o a,o a,o a,o f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 C C C C C C C C C C C C fc0 fc0 fc0 fcc0 fc0 fcc0 fc0 fc0 fc0 fc0 fc0 fc0 G C C G C G C C C C C C c c c c c c c c c c c c v v v v v v v v v v v v > > > > > > > > > > > > w w w w w w w w w w w w \ \ \ \ \ \ \ \ \ \ \ \ +J c +J c +J c +J c +J c +J c 4J c 4J c 4J c 4J c 4J c 4J c v v v v v v v v v v v v U U U U U U U U U U U U O C C C C C C C C C C C C G7 f0 f0 f0 f0 f0 f0 f0 f0 f0 (0 f0 f0 N U U U U U U U U U U U U U) l0 Il 00 Ol O c-I N rn U) l0 N rn a) to Ca d 01 O r-I N X �L c� G H G! Q m U t U m Q H U O z Q X t t t t t t t t t t t t U U U U U U U U U U U U E Q Q Q Q O Q O Q O Q O Q O Q O Q O Q O Q a1 fC ^ ^ ^ ^ to ^ to ^ to ^ to ^ to ^ to to ^ to ^ to u io N CU a1 3 U vi U vi U vi U > U > U > U > U > U > U > U > U > O O w O w O w O Q O Q O Q O a O Q O a 0 a O Q O Q L.. z z z z z z z z z z z z C7 C7 C7 C7 C7 C7 0 (D (D (D (D (D x x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 2 v a-• V1 w v n3 aJ O E v aJ t C ai L o cu v i Q Ln3 V1 C i O +� 4J U V1 41 O Q O U co O aJ M vi Q vi O +UJ Q C -0 O cucu +J E Q -0(A -0 O -0 O m L a-•� m +' L-0 L cu aCJ C aJ U aJ Q O aJ O O C C +_� U L L U C 4- vi 4- � t o O > Q O Q Q co L aJ co v: m L C O 4 J U O L *' ^ O aJ 7 aJ c � 4O 4' aJ 4- cu O Q E to (� L m aJ aJ E E - m Q +, t Q O > aJ t C cu (� aJ u cu U c — 4, 0 fC � t O 0cu CU � O u 7 +' O N � U m+, Ca +, O cu O (> `1 f0 u +J aJ 7 U " >` 7 4J C L aJ � vi ^ +J O 0A C 0A L � }O L �O C LJ O O O cu`� Q '} O aJ vi O aJ > co aJ U U O O O Q L cuQ vi •> n3 WD >, 4. >, 4. aJ >, 4 c U-0 E U O aJ t cu �_ O} a-; _ L — Q f0 4 J -0 Z � M 4' Q c �:Q a-•i a) aJ aJ aJ C CU O U L L Q U 7 C 7 >� , cu CL aJ aJ O � Cn U — Q C 4J C V1 f0 _ C V1 O v`�i \ C O aJ Q L N j a) 4 J aJ U aJ aJ Q f0 +J O M M V w U 7 N U f0 O 4' O 7 O > Q (> cu O to C\ O aJ O O OU O aJ L L C L C m O m > w ^ N Q L N L a- .E 6-C CL - 2 0 Q t 2 a1 Q u t Q CO U a Ucr- CL 4 J a) a• a) 4. a) CU = CU = CU = Q 72 Q Q N p N p N p coo coo coo coo can can can can _ v _ v _ v v v v O o C o c o vi vi vi vi vi p vi vi vi p vi w wd w u w a) U a) a) U CU L L L L L L L L L Eb - a aCJ aCJ aCJ aCJ aCJ aJ aCJ aJ aCJ 4(V C U fB C U (a C U C C C C C El cu C C (a O C O C O Ciz V1 V1 V1 V1 U N cn cn 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C 4J C aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ to to to to to to to to to to to to n3 n3 n3 n3 n3 n3 n3 n3 n3 n3 n3 n3 C C C C C C C C C C C C n3 n3 n3 n3 n3 n3 n3 n3 n3 n3 n3 n3 2t 2t 2t 2t c c c c c c c c c c c c v v v v v v v v v v v v > > > > > > > > > > > > w w w w w w w w w w w w \ \ \ \ \ \ \ \ \ \ \ \ 4J c 4J c 4J c 4J c 4J c +J c +J c +J c +J c +J c +J c +J c v v v v v v v v v v v v U U U U U U U U U U U U O C C C C C C C C C C C C N U U U U U U U U U U U U Il 00 Ol O c-1 N rn �t U) l0 Il 00 ry) rrf M M M M M M M M M M m rn aJ to Ca d N X 'L }i m 2 H G! m Q m U^ 4-1 i U m Q H U O Z Q X t t t t t t t t u U u U u u u u G7 u io io io io N Q N Q N Q N Q N 3 U U U U U U U U O O w O w O w O w O w O w O w O w a z z z z z z z z X X X X X X X X 2 2 2 2 2 2 2 2 U vi +J C f0 N C N C Q p 4J p p N -0 4J C -0 N N U L N O -- L O L N c0 L .0 4 J c0 NC 7 N c� O N •> N N � U N u CO U GA m C O � U O L L 'L > O L -0 C N N L C O N L 0 O N vi C p 4J C M M U U O N = `^ O t O L C 4- C M N 0 O to � I +J Q O vi aC� m � L O 4J a � O `^ M N N L N C 7 CL C O 4O vi f0 N U N C O > i +' O a 7 L N � p +' C } cu +' cu E O� N a ate, O >� to N N O am N N � N +, p OWUC C N U U p= 1 ^ a N � , } C N v i > N 7 E N N N 4 J � cO V1 L O -0 N O N cu U -0 p Qn N 7 m O m O Q +J U N i f0 -0 ++ N u i vi U N O a U N p +J C N N L 7 N w > vi 7 O L C vi vi O N L +Ca J C t 4 J E U C M N O� L O N N N L N �i N N O +J 'E-0 m m N N � m XO LJ Q LCL N O t `^ C-0 O +J C 4 J Z U a L a L N N (.i co -0 N CU m v 4J OL U N ra E O m 7 ^ Q Q a M — 4 J a -0 cr N C U to vi C U N N — U N C v � N a p a O C E m C m w m N E to L 0 i N: � � N N E 6 N N t p +' N 4 m N C O t O .0 O O t a U C m C to N m N +J .0 > N �' E t U U 7 U N N 7 O0 4- f0 N N Q- m > CT N N m 4O N N u vi CO O N co to to co CL CU vi 0O C v � N 7 +' N O 7 .� N m N v m C a to -0 Qn U N U O N t CT O •— U C O L N-0 m C C N O p p O C LJ U 7 C N N 7 } O 7 E C N M C N C �O m f0 4J �_ N L �_ N O L a Y N to u V � 4, C p L N > O > � +� N N co m -0-aN M .V1 � X O l E m co '7 co +J N O O N N L O O O C M n, LJ N CO C C M M 4 J cO -0 L a O p U N N o0 -0 N m C 7 L m Q N L N L > N +J 4. L Ln a L N D_ > N CO m p -0L to m - F F F F F F 41 41 41 41 41 CU CU CU 41 41 41 41 2 41 4J 41 4J 41 4• a a a a a a° a� a a a a a a a 0 a 0 a 0 � � � y Ln N LnLnLnLnLn N N N N N Ln N Ln N Q L Q L Q L Q L Q L Q L Q L Q L �O txo O O O O O O O O O O O O O O O O 01 O O O O O O O O O O O O O O O O fC N N N N N N N N N N N N N N N N Ucr- C C C C C C C C N N N N Ln N Ln N Ln N Ln N 7 7 7 7 7 7 7 7 N N N N N N N N cr- cr- cr- U U U U L U L U L U L U L L O L O L O O O O O O O O O O O O O O cr- cr- cr- cr- Q Q Q Q Q Q Q Q C C C C C C C C E E E E E E E E O CU .E v .E v .E v .E v v v C a u a u a u a u a u a u a u a u G% O L O L O L O L O L O L O L O L Ln Ln Ln Ln Ln Ln Ln Ln Ol O c-1 N M Ln l0 *k Ln l0 l0 l0 l0 l0 l0 l0 rn rn rn rn rn rn rn rn M O to Ca d U U U U U U U U U U m L � � L u CO N CO N N N N N N N N N 3 U U U U U U U U U U � O C vi O w C vi O w C vi O w C vi O w C vi O w C vi O w C vi O w C vi O w C vi O w C vi O w a z z z z z z z z z z X X X X X X X X X X 2 2 2 2 2 2 2 2 2 2 O u O a 4� 00 N v C O -0 N X ccu o c C N E ra O L N N u N OC 4J N C U N O U N L 7 O N t O +' Q 7 p t N 4J Q- + N N C N vi 4J vi C cu � U O vi -0 Q w � O N c0 Q 4� N O L 4� O C-0 4J Q u— vOi N N Qn N p v a�J -0 M v O O V w4 v cu v ^ vU Q LCL O OO > E N 4J m - O 4J O N u N CL � 7 4 O = Oa-J N> U N O L o p Q C N-0 U N N L F p .v N B O 4 J M 0 t 4U — 4 J v vi L 4, 7 (B a-J E cu t C '^ N 4 J .0 Q m u L _0 - t � N 41 O N N O 0 O _ O O 4� N Q 'L_ N Q4� Op v U �N L U O U N L �U 0A 'n N NUU = N L> O u p N LO U p .0E O p p M 4' h c > > N m QU > p 4 4' v 4 7 v 4 } N Ov— Oa' >- cLo +�=v+� tvD U M Z C UN N p -0 "7 m 4J U Ct m NM B -U CU L N to m � O O O > N N -0 N t t u Ot� O O � N cu � Nt = N 4J N t cu v Z v O O + u +J pQ N O4'cN .2 Q' >0- O N mL u } N-0 .> O O > O LU ^ > L o -0 > � O7 O on OQ N 7 O > o O Q N C cr-d -0 !� m L p d a. O Q }� d N L N d V1 U M O Q L L N d L 4' d V1 4 C: J v U v U v U v U O C N O C N O C N O C N N CU L 4J N CU L 4J N CU L 4J N CU L +J N N N aJ U U U U m (n m cn m cn m cn -0 Q 4 J N > N i N i N i Q co Q cO Q m Q C N N N N T L a- Q Q Q c c c c c 0 � u N U N U N U N u C E C E N C E N C E 4J dA N 7 > 7 > 7 > 7 > 7 p p } p p } p N Q O u N Q O N Q O N Q O N C 41 fC � vi N N 0 vi O N ' vi O N vi O N +' vi O N Q U C 7 N a Q U C 7 N a J Q U C 7 N a J Q U C 7 N 41 N N > U �� Z� Z� Z� Z� w cn w cn w cn w cn w C C C C C C C C C co 4J co +J co +J co 4J co 4J co +J co 4J co 4J co 4J N N N N N N N N N N N N N N N N N N cr- cr- cr- cr- U L U L U L U L U L U L U L U L U L O O O O O O O O O O N N N N N N N N N 4� cr- cr- cr- cr- cr- i io io io io io io io i O Q C C C C C C C C C N N N N N N N N N E WD E WD E WD E WD E WD E WD E WD E WD E WD 4J O aJ .� aJ .� aJ .� aJ .� aJ .� aJ .� aJ .� aJ .� v .0 c v +� Q --e Q Q Q Q Q Q Q U uQ ce ce ce ce ce ce ce -0 U N N H N H N H N H N H N H N H N H N H I� 00 m O c-1 N rn 1n 1-0 rn rn rn rn rn rn rn rn rn rn U) n'f N to Ca d V I JO J N X 4-1 Sm G H m Q m 4-1 t U m Q H U O z Q X u u u u u u u u G741 Q Q 41 Q 41 Q 41 Q 41 Q 41j Q a Q Q Q i (.n ( Y N f0 f0 CU CO CU f0 Q f0 CU f0 Q f0 N CO N f0 U c v E m c 0 c 0 c �+ w c> C �+ w c c C �+ w C �+ w C U O O O O O O O O � O O 0 a z z z z z z z ZZ z z z X X X X X X X X * X X 2 2 2 2 2 2 2 2 2 2 0A Ca aJ +J C C t C C L L O +J Q 0 C C O Q -0 O c aJ 4� co UN aJ O 4' cuC cu E O L aJ 4J O O C C LnU O C_ •L •m C N 4, U- C (n +� CT aJ C_ 4J cu 4J tY C LJ u Ln -0 cu -0 cu cu L O aJ 4' -a O C Ca •`� .� O 0A aJ N cu C (a U L a-•i CLn w (n U m M -0 cu4' L cu O O C � w u ++ L V Z i` � Q cu � 4 • aJ t M O O c cu co C O 4" aJ >, C Ca Ca U O +' 4' C- > Cu L O O -0 aJ Q aJ M U U Ca Ca E C v cu U Co to fC aJ +J O -0 4J . vicu 4O cCo U aJ -0 N f0 C_ C 0 u cu7 4, Ln 7 M C aJ O X O O Cho j L L U O LJ aJ " cu N aJ O L L Ca W a••' Ca Ca cu C aJ •� w 4• U Ln Ca � U f0 cu +J 4. L cu (n aJ U Ca cu cu f° �° 4 J ai �; C ,} 41 v C �- C_ C v v> m cu -0L 4 J C L N v C U aJ O U aJ Co N � aJ 4- — O O 4 J O 4- +J C t O � cu CU t u4J W WCE +J v _ L _ �_ cu Y o >4 o Q O E u >- O > Q O t+C�m >QOB O -2 Q Q E O cu Q��/Q d .� d d •� E c c +� +� +� c c o +n Q Q L L L Q Q U {n cu cu C C CU aJ C tY O O O C a) � a) = ai ai Q .� cu cu .� C_ C_ +J cu E L � WOD to E O E O E O � � p txo G7 aJ C aJ C N C N C aJ U O U aJ U O O C 41 4J a) 4J a) = — 4- 4J 4. U U U 0 w 0 w cM D c cM D G 0 U-L.L 0 L.L tY tY cM Ln G 0 0 0 0 0 0 0 0 0 0 C C C C C C C C C C aJ aJ aJ aJ aJ aJ aJ aJ aJ aJ U U U U U U U U U U N C C C C C C C C C C I- 00 m O N rn Ln l0 *k Il n n 00 00 00 00 00 00 00 LD C•f) a) to Ca d U U U U U U U U U E O Q Q +J Q Q Q Q Q Q Q v to Z Cu Cu Cu Cu Cu Cu — ' U c { % 3 c0 Cu u Ca C U c0 aU u c0 aU u \ c0 aU U m W U m W U c0 Ca U L co co U> C > C \ C > C > C > C > C > C C O O 0-0 O O O O O O O a a z z a z z z z z z z X X X X X X X X X 2 2 2 2 2 2 2 2 2 u f0 CuC U O +' = Cu > C i a-J CU Op Cu C �O _ C f0 CU f0 4� Cu Cu L O Q X O > tLD O a-J E f0 -C 4" C a�-J C } O 4O N _u O t 4CU X t C L � •O O X Cu N -C U C E O N -0 `� X � U Cu N 4' m Cu OAto C U L Q L O C >' L O f0 OA rl ^ N — C O +� C U O L Cu O co m Cu m Cu U Cu L vi U O C '^ L O O > N 7 N 1> vi U C LO Cu- OA N E Cu Cu Cu (A CU ZI L} u N m C c� C vi > Q E� io U M O E- X to Q- 'n O O C co ` N N M N-0 4- N Z 7 X O E _ N 2i Cu +J Q d j c�0 C +T+ � C t 4, t o (.n O N � t O a� � +, U U vi p � O L L > O N C > Cu vi f0 N C U Cu L N 4J +' to 7 C fC Q Cr 4� � w U vi v � N U O O N CL Cu Cu C Cu cn � t Q E t0 X O O " O LL >- 4 U � v •C CO -9 U � �Qn U � (j O O OA Cu cn m 'V � Vl Cu -0 di = -0 X �_ L f0 to u Cu �' +' > p Cu O > N L O co � Q f0 c0 U O `X E C � Z 4 J C L Z m > N C7 WD C J N C C L C I Cu +J X X O U M m N co U Q O 4D O C" c0 C LJ > U U .^ `X .� L N C N ^ CuZ a- vi (A •� O N O C Q •� t 41 Q f0 O m L w � di 0 to -0 Ca OA Cr a 0 +J O X C to +J U O c0 p O � O� �_ _ a} U � � O m Cu L � +J � 7 j, E _ C c0 Cu C C O O +J N +J � N O U co vi c0 U vi X � vi C C C O Z N m � C •f0 � 4 J 4 J � O O +� C +� +� f0 .� Cu vi f0 N > f0 M C to i O L N f0 vi vi c0 Cu CL O O CL N UI O O 4 J N N vi Q-0 cn LL — Q O Cu E C0 Q O L c�0 +O' C U Q N Cu Cu U Cu Q 7 cYo O Q O U--— Q N-0 L c0 U Q� cV > U a� p= 4- N Cu Co L-0 CO E f0 cn J � Q cn 7 C C V1 U U :t :t Cu Cu Cu Cu Cu Cu Cu U U U U U U U U U Cu Cu C C C C C C C Q Q fo fo fo fo fo fo fo to L N L C C C C C C C >` Cu Cy4J Cu Cu 4J Cu 4J Cu 4J Cu 4J Cu 4J Cu 4J U C U u C C C C C C C to to Q� Q� Cu Cu Cu Cu Cuv v wO yy � L � L to O to +�+ C O O O O O O O U Q Q C7 (D (D (D (D (D (D v Cu Cu Cu Cu v v cn cn cn cn cn cn cn Q Q Q Q Q Q Q c c v v v v v v v O O C C C C C C C +' +' O O O O O O O O O U C U C U C O U C O U C O U C U C Q Q C .� C .� C 4= C 4= C 4= C •� C .0 vi Q vi Q p 4 J L p 4 J Ca p LL Ca L p Ca LLL n p LL Ca L A p 4- Ca L LLL A O 4- L= Ca L C C I a"I O Cu v C v C v C v c_ v c_ v c_ v C u E E E E u �n S m Q m Q m Q m Q m Q m Q m Q Il 00 Ol O c I N rn U)*k 00 00 00 Ol Ol Ol Ol Ol Ol n•f rrf rrf rrf rrf rrf rrf rrf rn rl M Cu to Ca CL cn O r-I N X �L }i m 2 H G! m Q m 4-1 t U m Q H U O z Q X U U U U U U U U U E Q O 4� Q Q Q Q O Q Q Q O 4� Q z L N N N L N N L N m U U \\� U \\� U \\� U U \\� U \\� U U\\ O O O O O O O O 0-0 O a z a z z z z a z z z a z X X X X X X X X X 2 2 2 2 2 2 2 2 2 O N CaN cu cu > +' +' +' N CA (cu L (0 (0 L 4' cu _ (0 C C C N U LJ C (a Q N U " — (o -0 +' O fB C 4. C C N L 0A (0 L `^ -0 L 7 +' `n c " u V1 Y U V1 L O CL M M vi t N 4' m •L Q �O C N O .L O `n -0 vi a-' L (0 Q (0 � t L Q N N L C N vi +' � to vi +' N O O N O Q t Q >, � C C a-' L i � a-' p +' L -0 N C � O O 0A 0A O to a-' O N � X N " C: qp C vi N � - C Q O�(0 7 U > •L O +' w O ^ p C L p vOi t U O p O U � 7 L +' (n co -- vi L N O to O O t - L C (0 fB - p p +' — 7 LJ +' N L v C L N O t O_ - •0A O Q WD (D to a-' Q N N C (0 M� C t 4' N p +' U U-0 c0 p c0 > N N a' N O O (0 (� v1 t N Q�� U- � -0C C U C:L vi (0 ++ N O U LJ 4' vi Q N E O > m N . Q U C N 0A p co C (� O co O p co C E N C O vi 0 a' N co p 0A p N ate' L-0} U U O p Q O 4' Q O L N N Q� � O O U �7 t Lr n ^ N p M U p 4' `� O (0 cu 0A O N Z - fC +' O L OL X CU C O L vi =n U U O U •� p O co Q O U aJ vi +' -- O Q W M E C - C Q 0A vi Q-0 t o N � vi N to vi O vi L t o aJ L Q vi N (0 - (6 N n � 4' L U N qp '� vi � C N C C U C N C C U +' UI N L O ate' (2 4' L N vi L M L L L � L '� L N O +' O N-0 >' N > (SS a-' -0 — V1 O 3 C: to -0 Q Qn (O (O �' (CO Q N (SS � L •L C0 O CamC" CQC' N p a-' � C p L 4' N O .Q — �- +' U N Qn cu O vi O O C O-a O C t O O +' L O N N O O C U N N C a } N M +' U N O N N-0 L U U .� (D c0 C 7 ate' +' O O p } WD vi ^ 0A t� Q L Y Q t O vi N Q � O N C N Q m i U Ca CL vi +' C Q- O L Q- V O CL L � O O 0A CL +' O U O -0 O (� 4— 0A �' i 0A 7 C Q L Q (O U C O Q N C U Q N U _ O U .0 p U WD L O v N� Q O Q t (o Q Q N 7 N L N N +' N N O N (0 N L N -0 7� 7 a' vi C � 7 N ,�_ = O 00 Q m C 7 0A 00 m Q Zn m Q to � Q cn .� N vi O (0 (0 (n L +' +' -0 U U U U U U U U U C C C C C C C C C C C C C C C C C C C C C C C C C C C i 0 N N N N N N N N N dA— — — — — — — — — 41 O O O O O O O O O fC N N N N N N N N N U (7 (7 (7 (7 0 1 0 0 (7 (7 v v v v v v v v v 4 (n (n (n (n (n (n (n (n (n U U U U U U U U U C C C C C C C C C O O O O O O O O O 4' C 4' C 4' C 4' C 4' C 4' C 4' C 4' C 4' C O O c O c O c O c O c O c O c O c c Li Ca Li Ca Li Ca Li Ca Li ra Li Ca Li Ca Li Ca Li Ca 0 � L L In O N C N C N C N C N C N C N C N C N C V1 00 Q 00 Q 00 Q 00 Q 00 Q 00 Q 00 Q 00 Q 00 Q l0 Il 00 Ol O c I N rn rn rn rn rn 00 M N to d cn O r-I 4-1 N X m 2 H G! m Q m 4-1 t U m Q H U O Z Q X t t t t t t t t U 4-1 E Q Q Q L Q Q Q O Q Q Q Z o ("U ("UY cu ("UE" 0 cu3 cu3 cu 3 ai — v v v v 3 v ai v ai U~ v v ai U :c v a) v ai v- -0 c > c > c co c > c > c c > > c > > c > > O O O O v O O O O O O a z z z z z z a z z z X X X X X X X X X 2 2 2 2 2 2 2 2 2 c O cu c0 N fu L Ca cu t o N � N U O m U iiQ � cu •L V1 U a..i .U Q O 'L w 7 w cu t cu �' O 0-0 >` O N Q O 4' N vi O— 4 J ,} >� c 4�c Q vi O 7 cu +J — O Ca N .c vi +J Q N O vi U �>. � a- c v > v N N O V1 CU a% O i U Q N U i t w 7 L t-0 t L O-0 N CU 4" L `� N 4 J N O Q U c �^ m C LJ -0 O O 4�+ N Q N Nv N QC O O N u m u U E^ =CIA O Ca M N O c �. -0 4�O U +J i vi `� z N O f0 � > L N O 4� (A � {n c N— c O O O co vi 4- co L 4- < O Ca O -- Y U N 7 N L O N ( N 7 N co >- a=J O N "ra Q 4, N +� U cu cu U -0 f0 N N -0 O +' > vi L 7 � Q V1 U 4� L vi L f0 = t N N vi �— O co � 4 J > O O Qn O ^ ]fCl. ( J a. L C L '� - U L N L � mC N L � �O L O +' c U c +� ?i f0 Q O L= ,}J O c C L Q t gOip Ocu (.i N !E cu crN i L 7 � cO N N +J O cu 7 C +J N m O N _a N cu u+J N cO 0 c m N O c O O N .c co +� N +-' 4 Q N N O 'cu � m i O V1 C (� O U � O M 4J m L 4 vi d) O � O M � c-0 Q> CU N m _0 CU > � m L U C N 20 cu - U u U t M U Q" w O N m N M c 7 .� m-0 Q U '0A U N u c M 4' L Q •5 +j U Z Q N c U t a-J f0 Q m t fB L cu N m Q N N `^ Q N m N O CL N � Qn c O Q 7 O +� N 4J � �' L co �cu N m L C7 M N m Q _ to N L a"i N c L .O 4' V1 7 L M " O L O N N t Z N O -0 N E O U O 10 N0 -0 O vi Q= C � 7 f0 N L -0 Q L Q 'M N 7 � Q Q Q 3: > i =3 N `� u N U NN � v O >, C E Q � E m N OL Q Q u t O O c Q >. W 7 (n O (/� U CO Vl U a J O V1 O fB Vl fSS W V1 CL fSS U cu cu cu cu cu cu U U U U U U c c c c c c Ca Ca Ca Ca Ca Ca c c c c c c cu cu cu cu cu cu c c c c c c Ca Ca Ca Ca Ca Ca i O N N N N N N 4� 4� 4Mo fC N N N N N N U N U N U N U C7 (D (D (D (D (D cn cn cn v v v v v v v v v 4 cn cn cn cn cn cn cn cn cn Q Q Q Q Q Q Q Q Q v v v v v v v v v E c c c c c c c c O O O O O O O O O 4J 4J 4J 4J 4J 4J 4J 4J 4J c cO cOcO cO O cOcOcO . cO c Ca Ca ra Ca Ca Ca ra Ca Ca Li Li Li Li Li Li Li Li Li � � 'c_ 'c_ L 'c_ L O cuc w w c v v c v v c v c v c E E E E vOi CO Q CO Q CO Q m Q m Q m Q m Q m Q m Q Ln l0 Il 00 Ol O N rn *k O O O O O c-I c-I rl ci M cu to d U U 4� U 4� U U U U 41 U 41 U 4� U 4� Q 4� O Q O 4J Q O 41 CLv Q v CLO Q O 4J O 4J CLO 4J CLQ +J M to lu Z p p p v 3 v 3 v 3 p — ' — ' — v — v — c — v 'c — v — v —_ 3: — v 3 M U M U M v U M v U M m U> M U M c U M c U M Cuv U M c U > �> O O O O O O Q O O O O> O-0 a z a z a z z z z a z a z a z z a X X X X X X X X X X 2 2 2 2 2 2 2 2 2 2 V -0 � E O C Q U O O U Q L L Q L Cu p Cu f0 L +� C O Q _ a..l � C L L Cu N V1 V1 7 (ACU a L U O V1 O O +� > X O Cu 3 4, C O O �- co 7 co Q m O VI N u ut C C CO u U O 4 J •� O N OL 7 � f0 co 4 J CL M -0 CU >' •� c v E to CL to •> >` Cu ,� 7 .2 N U Cr >, Cu c0 p O 0 > C E w— f0 N a O m 7 0 O O +J p >, L 7 N U L Cu ut i v L N Cu Cu m L 1.1 U Cu Cu Cu U � 7 = f0 Cu (A �� f O CU V1 C (A L Q CU _ .O VI > O co 7 NC O t O a�-J �, Cu O U `� O CU —Cu 0 — T ++ L O pQ Cu C C N +J 0A 7 O u CU tvD C +� � 7 M 4 J O Cu +J Cu Cu +' O +� O vi C m O E � O ^ i 7 C O D U � M 4. L ut f0 cLo �, +J v, f0 +� > 4 J M C 4- Cu i Cu N `1 +J L uA M Cu V1 fC N t N Cu to X L c0 O L 4• O O Q O Q- t +J -0 i N O Cu Q Q O — U O C O � L, N -0 +J Q +JCu L Cu O CL c t U Cu M C " C � � '� M E " (A N t N U v- -0 to to +� O p O +� L O m U m O aLJ L O Cu +' � C — O U C — Q C � O N X Cu O 0 �_ c0 L — ut O O L O � Cu f0 CL 'V -0 U O N 7 C OC_ � O Cu Cu t Q O f0 i O m f0 O N Cu +, C O `~ L C- O O v 4 > Cu co Q t O � C U -0 N O O-c m CO Cu O w N W U 7 M 7 O N U vi L L N 7 M O +J N m � O Cu Cu— Cu i U Cu O > U U 4- cn O (A WD vi � :� E 4- m L N -0 cn Cu O vi O M O N U (A >. N U- > L c0 -a" Cu L O O U Ca � Cu N L C Ca 4' L Z (A N L ut Q +J a U Cu Cu > N .5 > f0 +J U U +J Q O Cu ^ L C O O N O O � (0 u. Q .0 N -0 � m z X O " a..l � U Cui O d Q CL 4O M CL C W 4� U M W U m Q W f0 0A J O T y O L L L L L L L L L L 41 U U U U U U U U U U U cn cn cn cn cn cn cn cn cn cn v v v v v v v v v v 4 cn cn cn cn cn cn cn cn cn cn Q Q Q Q Q Q Q Q Q Q U U U U U U U U U U C C C C C C C C C C O O O O O O O O O O 4J O 4J O 4J O 4J O 4J O 4J O 4J O 4J O 4J O 4J O U UOU O U O UO O O O O 7 4' 7 4' 7 4' Ca 7 4' Ca 7 4' Ca 7 4' Ca 7 4' Ca 7 4' ra 7 +' Ca 7 4' Ca LL L L O v C v C v C v C v C v C v C v C v C v C u E �n Co Q Co Q m Q Co Q Co Q Co Q m Q m Q m Q m Q Ln l0 Il 00 0) O -1 N rn *k c I c I -i -i -i -i N N N N Itt Itt Itt Itt Itt Itt Itt Itt O Cu to Ca CL 01 O r-I 4-1 N X m 2 H G! m Q m 4-1 t U m Q H U O z Q x U U U U U U U U U L L L L L 0-0 Q v 0-0 0-O 41 Q 0-0 Q O Q v Q v to Z p p v 3 ° ° v 3 v 3 '� 'C '� 'C u io m CU v M c M co co co co CU v M CU v 3 U U U U U> U U U U C C>> C C C C C C>> C>> O 0-0 O a 0-0 0-0 O O a z a z z a z a z z a z a z z X X X X X X X X X 2 2 2 2 2 2 2 2 2 N c0 � tvD O to _ E -C N O C O +J C O C Q L C C f0 OL `� O C �^ O � N > 'ZI N O C C �O Q f0 •O U � N co ,O i N >, O O Q L E L 4• co -- N � O 4• C i U N C M N +J U O 0A E 4 J O V1 fO Ln U > � V1 � L 4% 0A L N N L QUA +J co L C O N amj u O � -0 N N m C >- O 7 O U ^ O 7 C L 7 co In Q O vi 4' O C +� Ucu N � VC1 � C V1 O cu 4. V1 L •� t O N C N O N cu CU Q 0A O C 0A U OL O 4 J O - vi O E m Q E � m .0 Q co N 0A N co co LJ > p to co O `� a J a�j C O O �, ++ N 'n NCU N Q— � t +J vi i N vi a J O +J O p •> — O U N co co Q N O N U CL a�j N +' 'n � (a N O � > +J N C +J Y O L Q O � co a vi U N C N i U N L U +J N 4J f0 > M O> co `~ 1 O O N +, > +, U (A Ca 7 ra _ .L p C co CL OC ra 41 O N vi i N fB O O U N to f0 C L to C C V1 f0 C L 7 V1 N f0 -0 C Q C C^ a,, fB U � >` C C C L� U Vl U Vl Vl > U U 4J 'E U O Z- �>, fB O co co V1 O O N 'n >` N N — U N 7 cO O - L L t 4 J Q Q Q C `� U U aj N U p U C Z E E qp 4, C vi O '^ O O U i co Q Q co O Q m N .O N E L to L O N O U O M' � V1 O 4 J U L O N — vi N N O w N N •L N N } vi O N> C(A N N L t C U M N 4J � Q } v � Z -0 f0 L - N +J m U L N L U N 4J +J O O to Q UOA cu U fo cu U L O O O cu O O O 4 � aJ � N O U O co > �_ C 'vi +' 7 7 4J > '� O L L z L U N t f° " v % L v i N N i L O v_ +� Q +J N Q O O i Q- U O N t O U t O N U •U C C 0 4 J w 7 a a u m a 7 a O a 7 OU m a 'A m 0 ra t ra `L Q �Ca Ca � T O Mo 47 u u u u u u u u u 41 U U U U U U U U U U cn cn cn cn cn cn cn cn cn v v v v v v v v v cn cn cn cn cn cn cn cn cn Q Q Q Q Q Q Q Q Q U U U U U U U U U C C C C C C C C C O O O O O O O O O 4• O 4' O 4, C 4' C +' C +' C +' C 4J O 4J C U O U O U O U O u O U O U O U O U O Ca Ca Ca Ca Ca Ca Ca Ca Ca Li Li Li Li Li Li Li Li Li O � L Ln L O N C N C N C O C N C N C N C N C N C E E E V1 00 Q 00 Q 00 Q 00 Q 00 Q 00 Q 00 Q 00 Q 00 Q �t Ln l0 Il 00 Ol C:,c-I N *k N N N N N N M M M �t �t �t �t �t �t �t I r-I cu to CL 01 O r-I 4-1 N X m 2 H G! m Q m 4-1 t U m Q H U O Z Q X 2 U -Q QJ U t U U U U U U U � (0 L '� •U (0 � (0 L (0 L (0 (0 L (0 (0 (0 E Q O Q ` Q O Q O Q Q O 4 J Q v Q Q a to 4- 4. to Z e ro Z 4 3 ° — a _ � � cu 3 U •c_ a h U> a U U U 5 U U> U ° u- -0 c = C� o c c c> c c-0 c>> > O O O a_ a, O O O O O a O Oc a z a c o z z a z a z z a z z z �U c o X X X X X X X X X 2 * 2 2 2 2 2 2 2 2 E vi N C N dA aU O M to N +, _ (o v1 E O 4 m N d. c m _ m p U N N -0 Z, t m-0 V1 N 41 m > 4J � � O L O u u QQ > C co vi Q (A O -O 4J N L O 4J O N Q v1 >, N u co 4, •L L C dA 0 L u N Q v1 w 4' `^ 0i1 Ncu L N ^ Q N (o v1 O O O t v1 O E O Q C aU N C N cu (A O M � vi O O v1 L N N 7 C C N 7 Y 4, n M 4- 4 J N m (0 L Q 4 J a,, N C V1 C CL O � m � L C — I 41 m � L m-0 Z (A� {/1 7 co O , O p 4, C C cLo C c U 0 to O _ > O N L m C Q 4 E u vOi O- N to � — � Y 0 � �� Q O �� O 7 Y t - > — 4J t (0 > 4' N N U 7 7 C U U p O 4J N C LJ O 'Q � C L O C � 7 a a C m v1 L v1 O N m p p� C C O p N -0 C L N L >, M N --O m � U 4J L > Q N (o O +' U O (A � U 4 J N M N v1 4O � v >- � U � > � 4 , v�i N dA E C n O O O+ a� Q(a (o + O u 'E ^ CO 4 J (a 4, L -0 +J L vi co E M 7 N (0 C 4J C N 4J N Q N 2i N to L C O Q >- C O m a D U O m O m ( = = c 4 J (0 1� (o O u N N +� aL +� 4' aL 7 N +J +J +, (p aL (0 N N U (0 v1 (0 41 v1 N N (0 4J U 4' C 4 J U � a'' +J (0 (0 N +J " C V1 -0 C L (0 -0 C- -0 to � � :'� V1 aj �_ (0 +� U N i 0 i > O w � �. ^ > L > O N +� : C LJ O > fu O O p � v1 aJ >- O aJ O u (A cu O O m O cu ( �- pU J � 2 m a-m 0' d 4 J d +•� d 4 J (n m T O ao ao ao qp c c c O ao ao ao +' U U U U U U ao ao ao cu cu O O O U (cu n (n (n (n (n (n v v v v v v v v v 4 (n (n (n (n (n (n (n (n (n Q Q Q Q Q Q Q Q Q C C C C C C C C C O O O O O O O O O 4J C 4J C 4J C 4' C 4' C 4J C 4' C 4' C 4J C C C C C O C •� •� •� •L C •2 C •2 C •L C •� Li � �i � �i � �i � �i � �i � �i � �i � �i Ca (A � (A � � L O v C v C v C v C v C v C v C v C v C u E E E �n m Q I m Q I m Q I m Q I m Q I m Q I m Q m Q I m Q m �t Ln L.D rl oo rn o -1 x rn rn rn rn rn rn rn N cu to d 01 O r-I N X �L }i m 2 H G! m Q m 4-1 t U m Q H U O z Q X U U U U U U U U 0) E (� L 0- O (� L 0- O (� L 0- O (� L Q O (� L 0- O (� L 0- O Q O Q O Z4J 4J 4J 4J 4J +J +J +J m U 'Q U 'Q U •Q U •Q U •Q U •Q U •Q U •Q C C C C C C E C E C E O O O-0 O O O 0-0 0-0 0-0 a z a z a z a z a z a z a z a z a X X X X X X X X 2 2 2 2 2 2 2 2 CL > CL fu i V1 C +� " Q I V1 CL > Lcu CL N U O L �� t v O Ca O Y-0 Q U >. 4 J , V O � a••I Co C L 4- N � L OA C C 7 +� +J O co UA vi 3 Cn � -0 — W U t +J C C.c CL U >� V1 L _ _ _ Q O CO C u U 4, CL C t m< CO QC m 4 J > m Lu CU to -0 t +' 7 cu vi N L QU U U C N = CL L O 4' C N +J C � O ub +' U N CL CU L �, UOA 7 CCO - U U 4 J >, CU >� OL CU L O L O >` L c C >` C O f 2 C O >• U CO L 4' Q `� Q L CL O OC C t m O O �' Q CL O U vi CL +� 4J -0 4" CL t C C + Q L +J `~ E U 0 to +' 7 4J t OA C O " +' C N � Q C Q O Q CO C �, a -I C 41 , 'O � N '' N WD O O +T+ E O � .0 � 4= CU U vi c C CU - C O " U CL vi CL m � U C L � CL j > �• i C ro +J •L L C 7 V1 f0 CL i f0 •� ;•� CL Qm to � CO U O 4 J � � LJ �CO CL � � is CT CU C m CBS p Q � M >- cu I > O C CL 0 Vl .`^ a N L a Q aO.I +� U c L a J L c L SL +J +� Q E O O 4. CO C i C CO C L _ V1 >• 7 CL CL CL CL CL 7 L > L M M L U U vi M L CL +J L CL CL L L ^ O 4J vi t +� 4J 4J 4J '^ O 4J } O L m O 4' M Q O 4J 4J CU 7 O `� U 7 > CU O O p > > U +J CL E > CU L CU > (0 > Q > } L O > t > ^ N � > Q +J CL " � 4' O � O > � O — +J (5 � +J W Co > +J U C CL L L p io O io — `~ m t CL U io L O V U Q" CL co CL N E E m j N CO C C U C C C M C M 4' C fis Q C �, E .L O CL Q .L L Q O C O C vi O 4� OC O a�-J CL Q O Q- to O— O vi � O i O 4J p O p +J 7 L +J C 4• ,} +� Q O +J C O +J CU co ^ .0 p t C > > O t L O CL vi U U +, -0 U Q 4 J U p > U L U O V U C Q +, C CU +J +, +J >, C 7 N C 7 O C C 7 C L O O CL C 7 CO C 7 O C 4J CO L CL O CU N m 4 J CL vi 4 J � M � CL 4 J +J 4. L w m o co ^ - a CCli U �C' u O >, CU � � � cu � Q Cli • C CL -0 CL Cli -a Z 'L CL -0 OA 4 , L W �_ �' � Cli -a v U Z vi t o OA OA L U � 7 7 � �' CL 7 m C 7 O w � 7 U C m 7 4 U f0 C f0 to C v1 — U M (S7 V1 L C QJ U— Q- QJ QJ OU Q OU U O U U U +J QU U L V1 U CL to U 7 W L C c f0 -0 Q CO -0 Q U U CU f0 W a= 0 0 0 0 0 0 0 0 Ca Ca Ca Ca Ca Ca Ca Ca O O O O O O O O O dA to tvD tvD tvD tvD tvD tvD tvD (1) fC O O O O O O O O U U U U U U U U U v v v v v v v v cn cn cn cn cn cn cn cn U U U U U U U U C C C C C C C C O O O O O O O O 4J C 4J C 4J C 4J C 4J C 4J C 4' C 4' C O O C •� C •� C •� C •� C •� C C C •� Li Ca Li ra Li Ca Li Ca Li Ca Li Ca Li Ca Li Ca O Ln In .O Z .O � .O .O .O � .O � .O .O O Cli CU CU CU CU CU CU CU u �n m Q m Q m Q m Q m Q m Q m Q m Q N rn Ln l0 Il 00 Ol m CL to f1 01 O 4-1 X m 2 H G! m Q m 4-1 t U m Q H U O z Q X U U U U U U U U U U U Q 0 Q 0 Q O Q 0 Q O Q 0 Q 0 Q O Q 0 Q O Q O .� M M z Q L Q L Q L Q L Q L Q L Q L Q L Q L Q L Q L m U U U U U U U U U U U C C C C C C C C C C C 0 0 0 O O O O O O O O O a z a z a z a z a z a z a z a z a z a z a z a x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 v v Q Q Ca Qi Qi L a- 4� Qi � � 4 p O Q C p 7 � qA Q C N vi Ca � co O O O 4 J 4J i N Q ^ L N �' cO V1 +J +J 0A 0A Q cu � co aJ co cu +' O L C u ^ p aJ C Q V1 O N to � � N N cu 4' ^ 4' �_ +' to Qn � c c � 7 > _ �, N N `� � L Q +J L Y _ cu Y L +J Q 7 U O U � L L Q Q N U L N � O O N C vi cr M E C O N u Q a�j vi co O 4 O O Q O O O CU N N U L N L Q N V1 E LNL N N- N Qn N �. 4J N 7 C Q N t U t 4' t O t t V1 4J t 4- v m cu 4J C O `^ cu 0A +J 4J 4, p L 4J >• 4J -0 4J 4J N m 4J Qn 7 cu to f° "' Q .�_ +� to � vi m v to � tvo �_ an to = to L to � � " i` L C c L O to = �-0 C U C C� O Q +� O C +' 7 N �• m ao O O N +J C C L `� N �_ Q N fC U ^ U O L p 4 J C� 0A �_ U •� L N v vi v L C } } - co vi O N O p U �_ N Q N N N vi +' O N C p N N 4 J C U N LJ N N m C p p Q p U 7 Q t Q i` C Q- -0 O •— Q 4 J c co Vl Q U +� Q v v Q E O c cr VV1 +J V1 V1 N 4 U U fSScu V1 V1 V1 Q Q (� L O - L c O t L � O - L U O m L � > O L O p L L O N L O m vi L O L � O 0 L U a..i O z c N� i +, i t U i a N N i L Qn N L i a••- +J i L �-0 N i L i N i O p i 41 O � � 7 i L a-J a-J � a-J U +J O �. +J C +J O U +J +-' +J Q 4 J 4 J M N 4 J N 7 co o U o ~ S N M p co mC Uo C CmCNCNQ-C`^N C=C COCQ" p ' O O O Q^ O 4, O .0 .vaJ O N N U � U O U a-J +' U U U p U U U `� U U Q- O U U U U C O C U C M-a C O C C C L C U C �; O C Qn C U-0 C_ 7 L 7 7 N + 7 Q- 7 O 7 N 0O 7 O C L} O C `^ L} 7 Y C O C � LJ O f0 '- 4 J L} � O L Q � = � = 7 L} > -- L} N n p aO } } Q Q C vi N p N -a cu N ^ U - — N U -a — N C -a O N C � Q" N 4J -a m N p N 2i N co N O C - .Lu u L C L U to v U Q Q C O v (° t U O .L C" v U U— U vi O U vi to U U `� m U L M U 4 J O �' U a U U N > p U C N 7 O Q C to N +J C O Q C O aJ C — U co C — U C fB t N U — +J +J - C 7 — Q cr c c c c c c c c c c c O O O O O O O O O O O L L L L L L L L O L O L O L O L O O O O O O 7 bOw to to to to to to to to to to to 41 fC O O O O O O O O O O O U U U U U U U U U U U U v +J v +J v +J v +J v +J v +J v +J v +J v +J v 4J v 4J n n Q Q Q Q Q Q Q Q Q Q Q U U U U U U U U U U U C C C C C C C C C C C O O O O O O O O O O O 4, C U p 4' C U p 4' C U p 4' C U p 4. C U p 4' C U p 4' C U p 4' C U p 4' C U p 4J C U p 4' C U p C C C •- C C C .- C C •- C C C •- O 4, O 4J O 4J O 4J O 4J O 4J O 4J O 4J O 4J O 4J O 4J 4 Ln n 4J In 4J 4J 4J LA 'c_ 4J 'c_ 4J 4J LA 4J 4J +J Qn n O w c w c v c v c v v v c v c v c v c v c v�i m Q m Q m Q m Q m Q m Q m Q m Q m Q m Q m Q O -i N rn �t Ln l0 Il 00 m O N to d cn 0 � � .� 4-1 @ 2 � @ � � @ CL @ U � 4-1 @ CL : � � U c D 2 Q x 2 5 u u u u t / \ � \ / e J \ \ / \ ƒ to / m { / � 2 \ \ \ \ \ / $ \ \ 2 O= O= O m O= O< z« z« z % z« z x x x x $ I I I I I k u / 0 cu � ® _ \ § = 0 3 # 4 3 § / t / E \ c cu E \ 0 0 / / cu \ = u 2 0 < d k 2 %-0_ / e\ u 2 o E ƒ % f 2 = 3 u 3 \ Ca{ 2 a \ g \ / 3 / u/ /� 2 y 7 @} 5® E o< \ E CL _— 2 ƒ § \ ( / _ � cu " \ § 2 = E e 2 t E \ \ / / 3 k \ -0 / \ t = / ° a E / 7 / 2 / = 2 g -0 > = e @ ' 3 3 % 2 \ o s = • $ \ \ \ \ k c < < c \ \ u C 2 e . u o f = ® _ \ e o to / -z E / ) -0 2 ° k k = ƒ k �� 3 / 7 / t \ E m$ o§ o c u/ z 2 E z 4 z u 3/%/ 0 E< o u u u u § § § § § ) ) ) ) t t t t L \ . . . . } � 0 \ e - e e e e 41 -0 -0 -0 / / 2 2 % 2 2 Ln Ln Ln Ln Ln \ / / / / § k k § k / \ / \ / c / C .0\ 2 f 2 f 2 f 2 f 2 f § ) \ ) \ ) \ ) \ \ ) \ E \ \ \ $ \ $ \ $ 3< 3< 3< 3< 3/ - # D % 7 f � � � / � cn 0 � � x 4-1 @ 2 � @ � � @ CL @ U � 4-1 @ CL : � � U c D 2 Q x 2 u U 5 = E �/ CL/� CL J \ / t \ 0 t Li k u u u u _ E = 5 E = 5 O -0O (a) O 2 ƒ ƒ ƒ x x x I I I ® = \ 7 7 / cu / U � E •- _ CL \ / e e m E � s S � / E � S 2 g s e I u E 0 e $ / _ Ca $ } \ § / 0 £ / = e = - 2 ° E m \ 1 m � 7\ / e 7 -00 £ _ 0 > e o < 9 $ cu E ) E / / 2 cu § 2 k 2 3 u u u / § k 2 : £ / f / _ = — } 4 @ () M� E k\ u � \ Ln �� 0 c E = ° m a e E 2 9 ƒ _ m \ � 3 { § = � � ± / \ ƒy t a CL } k = 5 / / $ / 2 �\k 2 / % / ¥ = E § E e u = _ / . u e 4 o _ - s (A$ f= 2 E 2 U/ / / f 2 / \ k O _ � 2 CL E _ ƒ ± 7 e § ƒ ) / \ § /W �� \ / t m e t 7 \ \ \ \ / 2 2 / ( \ \ \ \ \ E ¢ § E § / > E t G § / % 2 2 e o<= u I I z 2>> z a-� Ln Ln�_____> e 8 2 u a- E= o o o o o o o o o o o o o o o o o o o o s o > <_/< E E E u u u u } § / o / § / / \ / \ U \ § e 'E 2 2 2 e e txo E E E E e a- 41 / Ln Ln Ln u u u 2 2 % 2 Ln Ln Ln Ln u u u u k k k k \ ULULU / .0 2 f 2 f 2 f 2 f ) \ ) \ ) \ ) \ % \ \ \ \ \ \ \ E -0 3 < 3 < m < m rl f ƒ # ƒ / to cn O r-I 4-1 N X �L m 2 H G! m Q m 4-1 t U m Q H U O Z Q x t t t t t t t t t t t U U U U U U U U U U U U U U U ^y f0 f0 f0 m m m M L m m f0 m m m Y Q Q Q O Q O Q O Q O Q Q Q O Q O Q O Q O Q Q L L Un Un O Un L L Z N N p m f0 f0 m L f0 }, O O �j c O O c Ln O c co m U c u 3 m CU v\\ CUM U \ m U> co m U> co m v> co m U> U �_ m U> m U> co U :} M m v> m CUm v\\ CU v\\ m c / c / c -0 c -0 c -0 c -0 c c -0 c -0 O a" c -0 c / c / O O O O a 0 a O a O a O-0 O a 0 a O O Q O O a z z z z z z z a z z z z z z z x x x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 2 2 4� C Q V1 cu � L L cu Q+ c N O co 3 i � pu p Ca cu cu >, O O >- c U- U O O CU O O O +� O O O L cu to O O c 0_ 7 c N cu t (a 4 J _ co N N vi O 4' t O> -0 N t Ln 4' a••' L 7 L t C NC � Q +J c 4p co > N U U- O-0 vn O c -0 4' 4 J C vi O 0) U 0) 7 cu L V1 U L N ,� mC cu L N 0) c M CU i — 0) to - L U c CU O 4J +' t +' C L C +J C L� O N � M 4 J N 4 J , •-0 a••' CU vi Z Q p mCU O O u N N N to N ++ L U cu NC CU Ln LJ c U CU �O m N N CU Ca L c 4" Q C C U 45 U c ra dA u +J p f0 f0 � U f0 > O O N O N >' L +� O � ^ N N p O E c- p -0 f0 N +J +J M N + p - p N � vi L O O co L co cu vi co vi N O N c Q f0 t c c c +-' L > co ^ +' p c vi v U `� +J N + p -- V > 7 '} O n U -0 m 7 �' N 0A � 4 J +' c _ E p +J _ 4 co L Q c 0 o >, L Q uj 4� cu F +' m N cu .p E O iJ :-7 fo C +� p co Q O C a O L O O O > >' N 4O c cCo NLn 7 O c vi O +� m O � O vi c L �mm Q C co C +, p O -6 O vi 7 O > > .L +' LL p �- p � p p C N C CU ^ ^ L L p '^ Y N U a••' > 4' — 4 �, — v m U p N O L N +, N m m +� C N — > > N +' V1 — � N — t p V a J c ou �' LJ " a�j Ln O m m m U +�, +' E u E = � ` u- co co > N L E E L O -0 O O O >` M O a-.� U O O UA N— 4, p U O O � p O p C p t 4" co O t p N f0 = M N-0 p O vi N N U t E t-0 O L C L, N 4J z � +� L a J f0 L = *' 4J 4J cu N Q C v >, v p v � CU m v v� a�J p C L -0 t o 4 J +J N C -0 C a�J � p U > +' � � O �_ N-o O-0 U N E 72 >- 72 N Q O� O > p N > L > t N N O 7 > O t 7 p > `^ > U 7 O u vi � O L N O LO O +J � U U 4 J O u O +J v N +J O N O O O > Q V1 r'I t d a. = V1 d c v v d U Q v co L O a c Q O > — O O Lu m L a � L L a CL L Q to. v v 4� c 4 c v v c c c c o p o •° a a a a a a a D D D D D D D c c c c U U O U U •E o t t t t t t t o 2 O o 2 O i U U U U U U U 0 p� E p� E fu U fu U fu U fu U fu U Ca U fu U Ca U Ca u Ca u Ca u fC O Ln O Ln Q Q Q Q Q Q Q O O O O U U a U a U U U U U U U Z Z Z Z cu cu cu cu cu cu cu cu N 4 Ln Ln Ln Ln Ln Ln Ln Ln Ln Q Q Q Q Q Q Q Q Q U U U U U U U U U E c c c c c c c c O O O O O O O O O c c c c 4_ c 4= c 4- c 4- c 4- c 4- c 4- c 4' c 4- c O O O O U O U O U O U O U O U O U O U O U O 4 � c c c c .— c c c c c •— U U U U Ca Ca ra ra Ca Ca Ca ra ra c c c c LL LL LL LL LL LL LL LL LL 7 7 7 7 O (n L Ln - LL LL LL LL O v In� w w c w c v c v c v c v c cuc E E E E c v, E c v, E v, E 'v, v, v, c v, 'v, cu v v v v v v v �n m Q m Q m Q CO Q m Q m Q m Q m Q m Q Ln Ln Ln N O -i N M Ln l0 Il 00 Ol O c-I N *k Il n n n n n n n n n 00 00 00 It N to CL cn 0 � � x m 2 � @ � � @ CL @ U � 4-1 @ CL � � � U c D 2 Q x 2 u u u u u u u ECmL CL CL e CL CL CL �\ \ \ \ \ \/ J\ t\ t 9 t t t k / / / \ / / / / -0 _ _ _ _ _ _ _ _ E 2 O O O< O O O O= z< / / / $ / / $ I I I I I I I 0 -0� / 2 # 0 � } 2 / - \ } § 0 : \ o / / m \ / / \ \ k k { /0 > { ® ¥ \ \ \' / E e @ e E ® / \ ° E 2 cu @ \ / Qn -0 \ U / ƒ / / § ' _ / m _ \ M _ � � 4 _ \ \ = t \ \ � \ 2 f t ° ' U 2 \ \ ° u ® / \ ° \ ( / m k \ / \ -0 / / Qn @ o 2 \ � 2 f § \ m g e e = E 7& \ / \ 0 2 % e s / 0 E \ k" % _ f ° E 2 § u 0-0 k° / _» = 0 2 _ , e » 2 / / § m , e e k CL Qn Rƒ g 7 g\$\[\ E f R\ k 7\ E U k\/ cu 2 2 m 2 E 2 4><= e> 2 2 e 2 u y g e�= 2$ < m 2 E o 0 0 0 o f o / to = 0 0 0 0 0 0 a- m � 0 # E k 2 g 0 - - - — txo/ \ \ \ \ m k S ' e ' e ' \ / / / t t t \ ƒ / / / g g g g g g g u u u u u u u - § § § § § § % E E E E E E E ± ± ± ± ± ± 3 (A Ln Ln Ln Ln Ln L ^ \ \ \ \ \ \ \ § \ a- O r-I N X 4-1 cm G H G! m Q m 4-1 t U m Q H U O z Q X t t t t t t � � � � 0) � Q O Q Q O O Q+J O Q+J QE O � +J N +J +J +J +J °' U .c 3 U •C U U •c U •c U •c O E C O E O O O E O 0-0 O 0-0 0-0 0-0 0-0 a z a z z a z a z a z a X X X X X X 2 2 2 2 2 2 - O O N co -0 p vi M vi C cu E N N C � L p O L N U .. O Q +J ^ O Q L to vi m L C Q O L C C m C co cu O 7 O C 0 vi O u N N �' L O p N cu co L c N vi N -0 M Q� Q N U co Q O C L Vl _ O _�cu w M OZ U w -0 � > � Cm C fo O O m +' co O O O N O � vi L O O L C m cu L O C 4 O U cu O cu cu E cu > 4, Qn cu�, v U m •> a� •L O o v : Q C C N C i X O L O N O_ Q- O O �' O N C +, 4 J L �_ L +, N O fC v 4J O vi �; ao Z cu cCo . co > co to O +, C � � v O m � v —_ CL O O +J C C L co N C^ C C N C O In +' C C -0 N N -0E 41 O Q C 7 U +, Q f° 0 O N vi O N 4J L , m N N 6- O v � O N +J N m E vi X L Q 4' 7 Q N -0 C N Q +J O N U O L V1 co O ^ '� u N � C O c O L � � N O L O cu Q p >_ �+ > (� > CU � E C L +� fo (B L N C N C LLD -0 N O N 4 J �_ N U c0 +J vi cu +J m C -0 Lr N +� — U +� - ,^ > t — c0 M +� —� +� — CL O " p f ° O U Oc V1 -0 4— N � L N L 0 coo co U co > co co co co u v v v 7 Q U 4• v Q v U v - v E C S" CU v C� o v aj o v C L O O O co c cuN Z 0 `� O '0 O L to O t 7 O 4' Q- -0 � O 0 O U N (o vi U N L 7 O +J O .O +J Q +J Q co L +J .S '} +' `^ N U to � L � L � N d L +, N � N (o N .0 +, p N O N U � N N N N U U C C N 4' L L 4' N t U U � O 72 •> v +J �_ '> fo a••' �_ N �_ _ > U fo fo C >� fo O L +� > N 4. L O O L L N > fo to > U L N Q 2 2 2 w > Q d O w O N O O CL > w O N N O D_ Vl O O O O O O O O O O O O O D_ U� d— D_ .- N LJ — 0- t 4• 0 0 0 0 0 0 m m m m m m E E E E E E 0 0 0 0 0 0 c c c c c c Qn Qn Qn Qn Qn Qn i O v(.n v(.n v Ln v v v Ln dA L (.n (.n (.n (.n (.n 0) E to E to to E to to to 41 cu N cu N cu N cu N cu N cu N Qn C Qn C Qn C Qn C Qn C Qn C O O O O O O 4J U 4J U 4J U 4J U 4J U 4J U C C C C C C 7 7 7 7 7 � LL LL LL LL LL LL O E E E E E E v v v v v v U Ln Qn Qn Qn Qn Qn >- >- >- >- >- >- N N N N N N N O N M Ln l0 *k 01 01 01 m m m 0) cu to Ca d cn O r-I 4-1 N X 5m L W ^m m 4-1 t U m Q H U O z Q X U U U U U U U m m m m E Q CL CL CLQ Q Q Z N N N N N N N 3 U O U cuU a)U cuU cuU O U cu m C C C C C C C O O O O O O O O a z z z z z z z X X X X X X X 2 2 2 2 2 2 2 N t f0 4- C >' +' U C N O +J Z L O vi d -0 N O Q >- 4 J C v> > co � O co `^ m v cu cuC p L O V1 a N L O cu L -0 N LJ L O m 4J Q O +, C ° L L L U C 4 cu C O � C cu (� +� p O N Q E _� U 7 •� > N cu 7 � O a�-J _ +J N M .� C N M M L N cu LA cu+J — C t U O m 4J cu> , O CLO 4J 4J O c cu N 4 J cu vi X `n > N 4 J C m > Q C O OL C p to vi N p L N 7 N O p 41 i N p Q O u N m •L �_ N U 0A vi uO 4 J � N to L fo a••' U co U (� N � 4' � C U +� � +� C L � vi � (a +J V co :EO U m C O O cuU m N C 0A a C CU V1 +J CL fC EC p L N L CL m cu4J > O C E O N a 4J 7 U 4 J p O 4• O t cu cucuN +J C O Q ^ cu (0 L 7 U v 4, an C o 4' C)_C � O V1 v Vl L v (n M o Q L Q C t �\ O p aj C 4, co N� -0 O t O U Qn p O p 49 t � C L M .O U C" O0 M U v> t t cu 0 co O O co O O i� O = L Q � 4J 4J 4J O .2 N vi 4% � co M V1 E � N W Q � Qn CL -0 O C M = i O C 4" a L m E " O N C L 4 J N � L C t 4 J >. O O N N L } O vi O C L vi a••' Qn 4J Q � C Q> v0 p z 1 M _ C M N a 7� co O N L N N co p co � L N O O N N N N N Q N Q O cu E Q p U N O 0 (mu 2- O O U ° p Q O U O. cup +' Q co CU (mu C LJ cum cu Q CL U U N N O C O CL CLCL m m vi CL c0 U 4 J cu cu c C C C C C C cu 0 0 0 cu a u a u a � u °o °o °o EE E C ° M C ° M C C:M U cLo C C C C v a a tvo O° m U 0 a to a O m U 0 a ao a O v, a CU CL O v, co M v co j Q° v y vi cuV1 vi N V1 vi N V1 C (n C L L � p (n C L L L � C (n C 'L L L � N O L L � O 1xw VC1 •C VC1 •C VC1 •C � U L — f0 � U — di f0 � U — m -0 -0 V m -0 -0 �7 � - -0 CU - C U U O E U Ecu m U O 0 co U O fC U co d = co d = co d = p U a C 4� Q (n d p U a C Q a�j (n d p U a C Q (n d to Q (n d O O O O O O O U U U U U U U C C C C C C C 7 7 7 7 7 7 � LL LL LL LL LL LL LL O E E E E E E E v v v v v v v U 4� 4� N N N N N N N N Il 00 Ol O ci N M *k Ol Ol Ol O O O O Ln Ln Ln Ln O Ln cu to d cn O 4-1 m 2 H m Q m 4-1 t U m Q H U O z Q X t t t t t t t t t t ^y fo fo fo fo -Q fo fo fo fo L fo L fo Y Q Q Q a- q Q Q Q Q Q Q Q Q z v v v v Ln v Ln v v ; ; cu a .O {% 3 M y U m y U m v U m U v �n i M v U M y U M y U M U M U M y U p i p a p i p i p i O O O O O o O 3 0 O O O O O a z z z z c z z z z a z a z _ _ _ _ _ _ _ _ _ _ a 0AcuO L N C O O 7 O C O +J vi O +co 4J L aJ to 4 U >- O z' U O � Cv a O cu u OtO\ u 4 CCU > O O cu 4JO i cu Q co Q +� O cu U CU Ca 4- > CU Q 4" +J — +J O U fo +J V1 co •O L +J m C L p V1 Q Qn N O fo +J C U C N C 7 O N C L O 7 U L O m U Q O O O0 C O -0 fo do O _ U � U O `� O O O\ N-0 aJ Qn L to N+ J CL u Qn U +' N '� � +' u co 7 O `^ E Ca N C � E O � � O '� 7 O a W O LJ �O _ �O - Qn L L N O � 4-.� Qn p O Qn N vi O fC O co vi - C Y cu Q Z U C Q E E O E 4-1 Q `~ N U O C a cuQ U 7 N M 4-1 a•J Qn Qn OL N - � vi U O 0A '� 0 a-1 � � � Y L cu O U fO do co (a L 4-1 cu p Vl V1 Q L � L � do L CU U O 4-1 V1 U N V1 C fO C -0 > co Q cu v Q m v O o N V1 v U C v +� E (o to U o L 4-1 O O -0 i` U O O L\ L co '} -0 U N M U +J co O '1 U U Vl O O C U vi � +' i � L O p E N vi d aJ N t -F p w Y O N p 1 +� +1 L co vi O N C N N +J — t u U to co vi N O Cn +J C O U N O U 0 U O .� -0 4, co Q vi to to O 7 Z Q N m +J u aJ U- �, m O O E L O m N Q a vi co Ca Ln vi vOi N O Z aJ N - N O u Q N L -a LJ N— N - N L N co co vi L += t p +� C p co cu � U co vi i 7 O N (p N co vi Q co N a = O -0 LJ 4-1 m C O N N O Ou O L 7 U O .� E N Q C p Q O-0 O O N 4J M � C cu to 4J N 7 Q vi fo � p (n U L CL U L CL o � m V1 L CL fo +J W p J C C Q 0o Q tLD Q tLD Q tLD v v U U U U -0 U -0 U o 'ao +J m o to a..i m o to 4-1 m o to 4-1 m O C p C i vi i vi i vi i vi U 4-1m U a m ON O O O � ? Qn Qn Qn Qn Qn Qn Qn Qnc cN c cN c cN N N N N N N m m m m O O U U U U O O Qn O >, Q O N Q O Q Q Q Q Y .O +J Y +J Y +J Y +J L p (n O L L O (n O L L O N N N N L O L O L O L O tx a J > +J > +J > +J > C U-0 c N U u u-0 N U O C O C O C O C 1 Q L 1 Q L 1 Q L 1 Q L 41 fC cu to O J 4-1 ° to O J ° v Cal Cal Cal Q p Q p Q p Q p U Q\ (n a Q\ (n a a' a' a' a' U U U U O O O O O O O O O O U U U U U U U U U U C C C C C C C C C C 7 7 7 7 7 7 7 7 7 7 � LL LL LL LL LL LL LL LL LL LL O E E E E E E E E E E v v v v v v v v v v U N N N N N N N N N N N Ln l0 Il 00 0) O c-I N M Ln Ln Ln Ln Ln Ln Ln Ln Ln Ln Ln cu to d t t t t t t t t t t t U U U U U U U U U U U ^y f0 L f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 Y Q Q Q Q Q Q Q Q Q Q Q Q Z p to p to p to p L p cup L cup L a")p L a")p L ("Up .2 L p v u m co U co m U > co m U > co m U > co v U v U co v U v U co v U v U V1 co v U \\ \\ \\ \\ \\ \\ o 0-0 O a O a O a O O O O O O "' O a z a z z z z z z z z z z x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 Qn E -a cuC L cu �' Vt I � ate, cu7 Qn m co O C LO O O + yn U � E C i C -0O m � �' cu +� L f0 L N — C � Qn N � L ut '} f0 cu O f0 �O U = a•'i 1} L U I M � �' cu " � � c Q O Q (o O L C� C U I a a..i E > C— v N u 0 u O L O +, vi O vi Q co N t �' O O O U v Qn L Qn E co O O co �, N m a-, L,L L >` >- N O C O E -0 O 1 cu 7 cO L Q > a-, > N , N '� '— +, O f0 dA L U X � j - t U t V1 Zn n O N oN u +� L ate, +� O C � ,� u N � N � �' O co O p C >, v � C tvo CL aO, t N ^ N O N 0A O� Q Q NC U C U cO N C a .- O >- U C 'vi U m C m C co t +� (a L O co C L N Q C O O L L E 1O Qn 1 C N co LJ U N Q •� j +' N O O ^ L — > C N Q vi C to co N n O O Q cu cu C E Q � � — � � f0 � U C c co C U L V1 C co (o fSS C +, C O C C t O a-, V1 f0 > O N (0 CL +� Y U +, N +, Qn O L — = Q N O N O c m O ut N 7 N O O p E io C N u— E B +' C vOi O-0 � I � t U +, � co O — CU L +, OC �, �, m CU O +, -0 aA +, c aJ } Q M aJ �, O L C aJ N 0A N m I = N a, C VI L I N CU 'L � +, N O O •C �, V1 WD +, co �_ co >O •Q t a, LL U t Q qp a, O c.0 ate, N > L O N N O +, m U Q Vi O 7 i +, E C N `~ co C + N > }O, 7 O U L N C O co U .O_ O ^ 0A cu L V1 L 7 X N C U C }, t C O C m L O N O L 7 N +, CL 7 f0 W Q f0 N (n U C m (n d -0 Q +, ut CL -0 -0 .� U N N N ^ p H H H o Q o 0 0 o (D Qn Qn Qn �, +� u Q, CU 7 Q 7 Q 7 Q \ Q Q Q Q ut L I Q cc G � \ : \ � \ f0 f0 f0 f0 f0 T cu •� J N N N N ~V1 O L L.L Ll Ll � N N N N t N i I O m N � > N � > N m > c E E E aO, p 41 Qn Z' +, z I Cm CC - � i I X Ln N Q cu Y L O L L O u u u u 'L U pL O L L O L C + +OQ to Ln O ON U(a U Ln m C C C C C C C C C C C O O O O O O O O O O O U U U U U U U U U U U C C C C C C C C C C C 7 7 7 7 7 7 7 7 7 7 7 � Ll Ll Ll Ll Ll Ll Ll Ll Ll Ll Ll O E E E E E E E E E E E v v v v v v v v v v v ut ut ut ut ut ut ut ut ut ut ut N Ln Ln Ln Ln Ln Ln Ln Ln (n Ln Ln �t rl 00 Ol O ci N M �t Ln L.O *k c-I c-I c-I c-I N N N N N N N Ln Ln Ln Ln Ln Ln Ln Ln Ln Ln Ln N Ln cu to d t t t t t t t t t G7 z N N N N .� N N N U N N N N a-1 N N 4� N 3 f0 U f0 U M U m U fo N U fo U fB U fB N U fB U O O O O O O w O O O w O L.. z z z z z z z z z X X X X X X X X X 2 2 2 2 2 2 2 2 2 cu t N C to C N v t > � N O u Oi( U Ca cu C N Ca O N O +, O +J +, +J vi N N N � O t > N a u 4J C a C 'L C c N L C C 0 C � L 4O O O 4J O O O t CL C cu > v v +J •� Q v C C n C +J 4� p N 0 O � X a••' C O 0 U c0 -- O -0 N N L N N � C tvD cu n O n L > N N O O N U 4J U O N > L; ° O O N C p vi -0 m m m 0 U +' Ln N co N ^ u �� ,... N > M L U N � •C L -0 N (a > a U U N O O �, L U O U N N +J N O t O u u N +' � U In L ++ > O C ° cu n C N 7 C C n +' O N LL CL Q L �� � CL U 7 t O +J p O n N = +' > N N n O O L N to }_ (.i co N 4U co co N N +' n 4� co L U 4 J N (A C U U +J Y NC L t t U +' m N � O m +J 4 J C C f0 +J U -0 co N C co co N O Qcu > U N O +J N O Q U �' L = 4' >— ° _ co Q C L aA L U U U U C O Q ^ +� C +� U O a-J O U 4 J C O L 4- M C (n N +' LJ U O C O n 4- p C a�j a�-J N > X C ° — — — Q O = Q M 4J > N 0A +J U `^ N U O O L L 4J L 7� Z U 0A - 0p 'L � Q- } V1 , N U E f0 — C L N N f0 C f0 C C f0 fB ° = — 0 Z U v -0 to v O co ° U � O v- v> v v +� v� O c In -0� (/, v� O m C 4' N TO co co +� co C U 4 J t +' 4' co C N t N t 0A M= M C N O L O co C N N L N a,,, cu M t V1 n L m Q Q 4, N 4, N 0A 4, N t cO N 4, 4, .� N co Q N Q+ U N E E N+ v +� ° v '� ° v v 0 C o `° CL - ° c f° `° -0 °' o 0 OCL 5 > Q > cr Q O > co N N Q U O O O N O N O-0> U L p C 2 E 2 coo E 2 4 w N coo CU a a M� oo a c E 2 m Q a tco OU U U U U U U U U U u u u u u u u u u c c c c c c c c c c c c c c c c c c i N O N O N O N O N O N O N O N O N O O to aW � to � to to to to to aA � dA Q Q Q Q U c 1 G 1 c 1 c 1 c 1 c 1 G 1 c 1 G 1 C C C C C C C C C O O O O O O O O O 4J U 4J U 4J U 4J U 4J U 4J U 4J U 4J U 4J U C C C C C C C C C 7 7 7 7 7 7 7 7 7 � LL LL LL LL LL LL LL LL LL v v v v v v v v v U Ln Ln Ln Ln Ln Ln >- >- >- >- >- >- Il 00 Ol O -1 N M �t Ln U N N N M M M M M M m U) v to Ca CL V I JO 4-1 N X �L m 2 H m Q m 4-1 t U m Q H U O z Q X u u u u4� u41 U^ U^ U^ U 41 (a (a (a � O � O > L > •L j •T j T Q O Q O io io io C N C N C N C N Z Q � Q � Q � Q � w = w = w = w c� io aa) aa) aa) C C to to to to 3 U vi U vi U vi U O u O U u U u U u U u C C C C +J C +J C 4J C 4J C 4J C +J O O w O w O w O ra O M O MO f° O ra O ra a z z z z v z v z Q" z Q" z Q" z Q" X X X X o X o X X X X L Q U i M O N fB •� � N 4� N V1 +J , f0 — C > 4' -0 NC O U C a L O CU �O WD C C u a,.l C N N Ccu 4CL O fo V� C E N U •O_ L CU cu C O � N � a,.l O •C C " cu C O C M vi U M L = C- L � L ,C f0 L Q ^ N a„I V1 •C N O C L M N u N N O U `n M N m L Q L M L U I N }J CO -0 Q a,.l L Q L Q L U O Q M O u �' C% M Qn Qn Q M 1 U � �� 5. > V1 M 4 J Q O a n L Q + CU WD 7 aJ � O 00 — C 7 N C C N L C C `^ - 'A m >, C N O O `^ +' C O O O U 4" C= Q O co vi N t .O L 4 J C- cu N N V1 C>M U CL +J O vi L CL O C to fC Q a to U C +J �� �� 7 U i }� C > L N a=1 4• M C U U •Ca M M co U CU p C L Q C cu N O i O C t U U L U •� L O O Q (0 � U 0A O O >, '} L +J N 4 J U Q Q N WD C- O C- > N L O L L N N— -0 O N 4' Q C N CL �_ O O p Q Q � � M L Qn E C � Q 4� 41 U +J _ M> c O L +J N� C co L O +� O CU i O aj a�j L O O 4J U 4- > L >- +� � +, N L N O N C- Q vi 4 _ N Q +, O Q t -0 M — M C N vi C— O _� C +J U C vi L fB Q iJ -0 N U O C N OU N C O C to U cu `^ O C O L O > M � L N > +J N L U .� U C O cu �_ — ` L o C +U Q M .� = N O W Q vi U N 4 J 4 J L > C M vi M 2 co v U> C C: M Q Q �, t v L v Q-0 v M v� v O v o Q v �_ � L Q L C O " � L �_ C �_ V1 I �_ > O to v O O U •> E 7 v > M - > Q Vl co Q > L U C cL U L U N M O 0A O Ln -o N C C Q C fB C O N C C O O cu L 4 d-0 O Q M w M 7 2 M WD +J d Q �- a O a L O L O L O Ln Ln C C C C C C > > > v v v v v v Q Q Q v v vto v v v to to y t C C C C C C 4 J 4 J +J �w a"I O a" O a" O S i L 5 i L 5 i L 5 i L 5 i L 5 i L 0) CL M M CL ++ Q Q C Q Q Q Q p Q p Q p Q p Q p Q p Q 7 7 Ln 7 Q N Q N Q N Q N Q N Q N V N N N U cr- U cr- U U U U a,o a,o a,o C C C L O L O L O O O O O O O O O O a=1 a=1 a=1 a=1 a=1 C C C U U U U U U co co co C C C C C C 0A 0A 0A 7 7 7 7 7 7 LL LL LL LL LL LL O O O a; a; a; a; a; a;u G1 C- N C- N C- N Qn vi vi vi vi vi >. > > > > > l0 Il 00 m O -1 N rn *k rn rn rn rn �t �t �t �t Ln Ln Ln Ln Ln Ln Ln Ln Ln U) Q to Ca d cn O r-I 4-1 N X �L m 2 H G! m Q m 4-1 t U m Q H U O z Q X U U u u u u u u u U U U U U U U L (a cu V1 V1 V1 cu V1 V1 V1 V1 z Q v v Y v v v v LU U u U \\Q U \\Q U U \\Q U \\Q U \\ra Q U \\ Ca Q C 4� C / C / C Ca C / C / C / C / o O Q O O O U O O O O a z In z z z z z z z X X X X X X X X 2 2 2 2 2 2 2 2 N 0A C -0 NC C +J � +� N L U a to O �, C O 4. U CU O N a ctb L M .� � O N 4' C O N O OL L � � M vt to U V1 N N C C C N ut } a f0 OL •E 'Q Q L +J N N �' N C� L N a 0 Q Q v CU to -0 Q � Q Q c E Q Q C fC° a CU cu > E-o E to } C C 4J 4J 7 to C > a C C Q C v " L c v, t Q 4 J N N C u vi c U 7 t O � a-J O N- m U O M -0 4J m m L iJ O L ut C C L +� C L C to cu to O .� 7-0 vi O O C 0_ > t O U Q� M N > N - +J O f0 to U m N C � N C p 4' O C N N 4- N C 7 U C +� N Y N C' O > WD O +J C N p O Z a� f0 m t .o +J C C Q O N A> f0 a- U C Q U f0 Q Q a L V C C _ L +J U Q N U E 0A (B I O O CU Q Q C L m U M � N `� C a"I C Q OL cu -0 � 4" U N L > M M C N 0-0 V1 '} O N +J +' C O N U '� Q m a C— N f0 L Q a- C N aL 7a N ut > a a L O vi vi .� M +' ,� N .� TO +, +J C > M U V1 O t -0 v1 " 40 L C V1 �_ cu V1 .L (Cu N (J 0A C C U -0 w >` �, a L > (A a 4-J co E 4, .0 C o- Q> C O 'n m +� -0 v— v C M 4J a CU +, > m N m O p=J O O o O � Ln O a J U O mO+' L�NU C c } O O� = >, N O+� NO O o 4J O N r-I u C m cu - -i LN Q U m v v, a L }J m I O m a C C 4J0 v, co cLo O ^ m L Oi _0 C }, tvD cO E L C Oi N N C 4 J 4• C Q +� C C 4- C C7 a O w O > c Q Q a 0 f° w-0� v v, fB •L L O c cu to O O U fo N •41 U C fj dA > L QU N C O F N — L' m z vt C Ca N N a a .� ut M j O O �O p C •> � Q r " U 2 C Q C +J Z > Z > ._ Q Q � > CC C a L C Q O N C 4" i N Ca U > O N N Q O L N > N a�.I L > O Q N L N Ol N a N O t Ol C t Q C >. a — U 4 J vi m CO 2 w._ co 7 4 J co 4 J E— w +J 2 w co ._ H U N vi to to to to to to to +� c 4� 4J 4J 4J 4J 4J 4J v v v v v v v v E F H H H H H H v to -0 -0 -0 -0 -0 -0 -0 i 10 0A c f0 c f0 c f0 c f0 c f0 c f0 c f0 C m C to 0A 0A 0A 0A 0A 0A dA 2i +' L C C C C C C C 0) 0 c c c c c c c a U U� H H H H H H H C C C C C C C C O O O O O O O O 4J U 4J U 4J U 4J U 4J U 4J U 4J U 4J U C C C C C C C C 7 7 7 7 7 7 7 7 � w w w w w w w w v v v v v v v v U 4� 4� 41 Ln Ln Ln Ln Ln Ln Ln Ln Ln l0 Il 00 0) O c-I N Ln Ln Ln Ln Ln Ln Ln Ln Ln Ln Q to CL JO J N X 4-1 m G H G! m Q m 4-1 t U m Q H U O z Q X cu Uto U U U U U U �7 m l Q Q Q Q Q Q E (Sj L L L � C � N N N L {/� L c (A L cu Z Q> �1 �1 �1 v E E U U U U U U U 1� C U C M C fB C fB C> C C C C O O (o O U O U O U O O O a z CL z z z z z z X X X X X X X 2 2 2 2 2 2 2 N O L t (n }J cu L p v N N CO t C N E N O L a..1 N C t O +' co � Q O Q `� C I 4� � M p m m ( co = C � Q O 0A N �' O � vi N > M O -0 O p O O C +' N 4� cu +J vi N O N 7 N N 2i L U to > C� N� > vi t Q (o C Q 0A N N 7 L N C 4 J a• (0 O O O O C +� `~ N L u N O N O aJ Q C O vi N U aj Q � vi C 4 U vi +J O +J ^ O aJ >` C U O •� O U N +OJ N O C L C� L U 7 � a-•1 (11 Vvi E U Vl (SS L N U Qi C C Q Q O 'O >` N Q a�J U a� co N-0 p N +� X O fB U M- �. � V1 U N (p vi L I Q � U (0 Q > N N L 1} a J m co L N Q O N > C aJ LJ -0 >� O m aJ +' vi +OJ E t Q E— -O� m ai Q-0 7 +`J c O N � m w +' m +' m O c -_ > Q Q C O O Q O aJ 1} 7 L aJ cLo C Z � `~ C co p +J � Q Qi 41 co > 4 J U Q Q (� +J Q N c a>, O ate,,, N cu a� N cCL Q > N m +J (0 O C p p O N � o_ co u mZ O X L cu 7 O O 4J +J p rl C L N z O `~ } (o +J (A U C C O +' ( Q aO (n Q i N (zn N U O O Q N (0 fB C � LLA V1 V1 W U r-I CV L W — > 'L pU � �' Co N -0 Co vi p i N (0 -0 to N (0 c-I = a.J t o t o ,} a�'.J O 7- cu p � O N cu p O 5 N C L N Ln Q c C (a � (o vi WD OCa p > U Q- a•' � C O N a'' >� W > J U U vi N L� �' t -0 U O 2i (0 (0 U 7� au N-0 +�J 41 4� ,C -0 N U v am•1 1} O O Q CU -0 c0 � c a-•1 N Q �cu (B `^ O co cu •C O i (co (A N +cu Ln j -0 vi ^� L N Qcu O rl cu :E+J Q UI N N a•' (0 >- a U O +J vi Q O \ N uO U L ^ Q > N > U (0 7 Q (� C m (0 (0 Q d v 7> (0 4J C > z ^ O N (0 41 1� 1} V1 O C - O N G D C C +J Q U a•J > Q Q +J L O L vi vi vi (0 W vi Cn > to W N 0A O (0 O O d (0 } d (0 (0 c v v v v v v N U U U U U U U L L L L L 4T L — cu }J cu a•J cu a-•1 cu a..1 cu }J cu a-J i O io io io io io io t >� Q mC a-1 a=1 C 41 C 41 C a-1 C 41 C M Q cu cu cu cu cu cu fC C N U Ln W W W W W W C O +J U C W cu cu cu cu cu cu i U U U U U U O E N L U 4� L N N L N L N L N L N N > (n C C C C C C rn Ln l0 Il 00 m *k Ln Ln Ln Ln Ln Ln Ln Ln Ln Ln Ln Ln Ln Ln to U) N to Ca d JO J N X 4-1 m 2 H G! m Q m 4-1 t U m Q H U O z Q X t t t t t t t t t t U +UJ +UJ +UJ +UJ +U J U G7 4-1J +UJ +UJ +UJ 4 (a Z V1 L Q cCu V1 L Q cCu V1 L Q cCu (/� L Q cCu V1 Q L cCu V1 L Q wC (/� L Q wC V1 L Q wC V1 Q L wC (/� L Q cCu c� L co p L co p L co p L co p co L p L co p L co p L co p co L p L co p m U U U U U U U U U U 0 0 O O O O O O O O O a z z z z z z z z z z X X X X X X X X X X 2 2 2 2 2 2 2 2 2 2 E N N N m L i -0 O p 4 J N fo W U O 7 L O 4J O N co �O O N � O N� 4J p L a p N > O CU CL CU L '^ m N O . N to a• m m a- Ncr N U v C O U O -0 (A vi — N L p t N N O Ln O L O � N `^ 0 N Q C M cu w a-•� N L Q co `~ > cu -0^ O p p O L U � V O 4 J N L N co N O a"i � co L C N N w '^ O t >` +' >` L N L .� O >� L L N O CT 4• � 4• O O w �_ N H U C C +' Q fB -0 i f0 � U V1 L `^ 4- co v WE +J C +J � N 0 CT O v Vl v> v U p v U >, +J 4J 4J 7 � Q N L Q co a- �' a•, CO p L L co 7 O L N N N N O ��� C vi O� CL U 7 •`^ 0� � Q CU +, Q t o Q cr co p � � aC � L � p N vi C U vi N c0 C O L N C 0A vi O 7 Y a•' N p 4 J vi >, = > C Q Q N L N a••' O O vi C U N_ E N N C m C L N Q- _ f0 t 4 J O N 4, 4J C V1 0A C +J C U O U L N _ p > _ m > O f0 U 7 U V1 CL O N m a O L m `� L N `^In p p N cOCU N cr v MC} N-0 O -0 U L O Q � O i O M c U +' +J E N � +•' u C C p CT N Q � 0 Q L E vi N N +' C C 0A Q N M � vi a-•� N vi C p L V O O L C L �_ Q— " L V1 0C vi O c0 +J Q O �; 0A :E N '^ N = � N c0 �O Q 7 N c0 O co O co p N Q — L O Q N co N C a C Qn a C > +� U +' O > L L un CT C X C _ �^ L O L O 4' CO N L O N N u .� +� U N p 4J N Q O Q N O O n X O Q N V1 O ` a-•i 4O a-J ,O Q V1 N a-•i V1 N fSS V1 a-•i O L O N 7 O N �_ L �_ +J �_ cr > '� 7 > i N co -0 > Co 4- � tvD O > N > U co > N Y L L U U +� '� N +J p O +J O Cn co N OL p N O O 7 O Q O 00 Q O W Q co U O w 7 7 co vi 7 4 J a O N a V1 m a = N a� L 7 co M Q O Cr +J f0 cO U a- a n L L N CL U v a) a) a) a) a) a) a) v v U U U U U U U U U U L L L L L L L L L L T Q I dA 41 C C C C C C C C C +' N N N N N N N N N N vi vi vi vi vi vi vi vi vi vi U W W W W W W W W W W i U � U � U U U U U U U U .2 U L N L N L N L N L N L N L N L N L N L N 0) N C C C C C C C C C C O N M Ln -D I- 00 m �# lfl lfl lfl lfl lfl lfl lfl lfl lfl lfl n Ln cu to CL JO J N X 4-1 m 2 H G! m Q m 4-1 t U m Q H U O z Q X t t t t t t t t t fC •n L n L n O n O n O n O n O n O n O V O fB O U fB fB U fB U U fB U fB U fB U 3 u U u `t u :t u :t u :t u :t u :t u :t -0 O O O O O O O C 4J O z C 4J O z C 4J O z C 4J O z C 4J O z C 4J O z C 4J O z a z z z z z z z z z X X X X X X X X X 2 2 2 2 2 2 2 2 2 L O > N L 4' Q ut ut WD O ~ cu O L t 4- O Ca - `u L Q CU V1 +J V V1 ut � cu CL 000 � V1 L N +� O -0-0 t o N O f1 C � �C N —� � +J i C O � N Q L L N V1 m C C M u Qn •� O u � 0A � � � M Q � fO to N C C— fO co fO t o (n 4J N � L N � N N � � a) ut -0 L N O � � CU � C E � Q O a-J C � a-J N t U vi C N N 0 � N 7 N -0 � U N +; �O O N +� N O `� •0 +, `^ M M C aOj t � N O C CU -0 N M u ++ N N N N O t 4J U m-0 C C C 7 Q C •to O �_ U ut O U C t >, Qn C N O t M • =� m U t +� co U " co i C m t .� f° t •VI c U C +' f0 a N C O N > `~ - C vi O � L (� t 4- -0 N C M M O N U Q Q L N O O N t Q C t •f0 t 4' O C>- f0 +J f0 = U LCiA O, N U N iC N L N U Q �, aU (� 4J 4J L} +� O Qn N L t Q U cC L O U N O O 0oE O C 4mU tO N L�L � ON J cf0 O C � Q � O C m Qn O O O v dA CU M 0 U +J V 0to U > f0 i = o � 'On L to M a= Q v C U L J to v v U Z Q � CL Q N O vi N N'n m� 7 U 4- aUJ m O C to C m � Q +� +, co C- .— CO N O N Q •N L O N O a"i O � CU Q to to L � 4 m � � = � U N Q N -0 to �i Q cr Q N m L N f0 •U _' U � f0 dA C •� N N m U I fC0 � ut C C > O U C > v a••' 'CU co p 3 Q U c U c Q > 7 7 .— > •� +, C o v cu -0 to C N O C N Q Q .0 O 7 J c0 D_ O co 7 4 J 00 ut C_ N u u Q c0 O m O D_ to C O — C d 7 C O U 4- O L C v v v v v v v v v U U U U U U U U U L L 4� L L 4� L L L L L 4� C C 4� C C C C 4 T C 4� as 41 C C C C C C C C +' N N N N N N N N N vi vi vi vi vi vi vi vi vi Ln U w w w w w w w w w i U Z U U U U � U U U U �1 U L 4O L 4Oj L aOj L aOj L aOj L aOj L aOj L aOj L aOj N C C C C C C C C C O -i M Ln l0 I- 00 m Ln Ln Ln Ln Ln Ln Ln Ln Ln 00 Ln cu to d t t t t t � � 4 G7 Q Q Q Q Q E (a V1 V1 V1 L v V1 V1 � z o cuo cuo o v o D m U U U O U U C C C C C i C O O O O O O O a z z z z z X X X X X 2 2 2 2 2 O — C O +' Ca cu�CUa LO cu C p N 4J M vi O E Q N a C m N 0A > N > L N C +J O O a C : C n O N WD C O , C U co co +J a U (n `^ O co N O 4 J C O vi 4 J > O v CL N O O O L Q L 4J +' N ^ U m u v E �_(10 4, � a a + Q > O O O +' +' co E O 4 0A cu 0A N W O Ini a -0� >� C N� vi vi �� M O N 7 M a Q� +' v N t O O C j c0 .O > OL => 4 J N i 0A L a 0p > � vi C vi +J -0 O-0 a O N U U 70 7 CUC O m N N C U- N > u- EC N C C m N L N f0 vi f0 4 J to 4' U > � 4 J (0 4J L C N N U +J U C C Y cCo L N N O +� N � i U i -a C O m C i L O C N " U-D N O Q C cu N > > O C •> v N O O 7 t Q � U vi m U f0 C 7 +' C LJ U N LJ N O > O O f0 C f0 Q f0 fU0 C � i O v v v v .� E a v v U 4 J Q v o o to co Fa �+ C Q O O N-0 � O C a U N m E a U C 41 N o p .> U N L C co N 1 u N Q � O O O-0 O� to O O c0 vi cu C E U N O L o N N U N 0A +' t C a L N N � L N O C (a N O N N N > L .> 4J N L +' N co C V1 L 4' t co C 4' a U t L m W m co +- CU N LJ -0 C N vi Q M CU C t C co C N +J > m 4O co C a O C C a O C +J O � N t N LJ L C O 4J C C N t a m O m .— N> N N O 2� N��cu N Q E C— ,. A C C co O U > N N EE ( w � O E O O N -0 > N a O O 4' Q a A N cu L vi vi +J +J v ^ v O +J O 4cu J co U -0 v v t> � oCL t Q � .� a E E •N CU C am~ = o= cu a( o-C co o 4 J Q v o w m O� vi M-0 a 4J O U L Q RE O 4J -0 =�" 4J > O a O U 2 4J 00 'vi a. C C v N U N U N U N U U Ca L cu cu 4J cu 4. cu 4. cu 4� a Fa 0 f0 f0 f0 f0 C O Mo 41 C C C C +J 41 N N N N U w w w w Q i cu cu cu cu cu U u U fu U U U U N N N N N N O Il 00 O *k 00 00 00 00 O) Ol U) N to Ca d V I JO J N X 4-1 m 2 H G! m Q m 4-1 t U m Q H U O z Q X t t t t t t t t t 4-1 0) Q Q Q Q Q Q Q Q '_^ c '_^ c '^ c .L c � c � c � c z p D p D p D p D p p p p p D ++ — N — N — N — N = N— N — N — N — N 3 U-0 U-0 U-0 U-0 U-0 U-0 U-0 U-0 U-0 c O c O c O c O c O c O c O c O c O 0 O 2i O O O 2i O O O O O a z z z z z z z z z X X X X X X X X X 2 2 2 2 2 2 2 2 2 O +J Ca M N 'u L j ^ N a 0A VO Y ,O +J (A c t cu (-ai 4O fo N fB U U f0 Q- �, O c c .Q Q c 4J N O c N co N +J t O c co +, O Q O � O .O 4- c O co -0 O co L CQ +' c 4J -0 O M m f0 41CU L U Q cu 7 M L 4 J N- co Q O C 0) Qn Q c a. C c C 4 J co i +J Q (o �, O O N vi � C Q U c O OQn O N O O — E O CO c � L L O L O i` Q' O N Qn U CO co C U J co c U N w toJ N X -0 L O U N = L L Q ut `� 7 0A N Q c LJ O N +J 4 +J x O V1 t Q +j Q c iiA a..; +J f0 L— T L Q m m c c m L Q O Qi — Q � Qi �+ E +' t C N Qn N O L m � � M N O O U �O cuc Q_ a�j O m 4 J 4J U -0 to N U 0 v v 7 c v i f° E E v N ° 4 v E u 00 E vOi Q � (n u Qn E u N to 7 4- � O � Z, N U 7 O co O c co p c C cu 7 L � OC c N O %` U O c ^ +J i L �_ co Q N L � OC O N C 0 cu co 4 -0 �, �_ c co vi 7 U - N cu O C N vi N `^ L U v— cu co i L-0 '> L c *' -a L v� +J O O 7 coo O f° m .� cr m 4 J O N O 7 � +, N � +� �O +' +, +J v Q -0 v M O i � i to L - m i E 7 .� U � Q = � ut 4' c ,c +' M O N to WD +' � 4J O N CU CU Q U� .� o C co > } O N O > M co U � co E 4J N M co M a U cu c N > L ut co U t a..i O Q f0 c U +J . fB O Q -0 to cu�, �, t Vi O O p O O E +J +J '� -0 co co a�-J O 0-co N '� N 7 m cu� — cu cu cu.O N v 00 cucu O Q V�U m N O u U M c c> �' > f° > > �i c E" 'U m p Q m O O cLo Q O o N O O O Q O O O N N c Q O c S V c Q � L N L L � L N O Q L L L Q a..1 -0 w ._ Vl f0 U +� m � a o CL � +� t U a a CL d V1 .� O CL V, V, V, V, V, V, V, V, V, cu cu cu cu cu cu cu cu cu U U U U U U U U U L L L L L L L L 4� 4 4 cu c c c c c c c c c 0 dA O a0_ O +J O Z O +J O +J O +. O Z, O +J O +J U Q Q Q Q Q Q Q Q Q i U U U U U U U U U 0 U N N N N N N N N N 41 N c c c c c c c c c c-I N M Ln -D I- 00 m *k Ol m m Ol 0) m m m m O LD cu to Ca CL V I JO J N 4-1 m 2 H G! m Q m 4-1 t U m Q H U O z Q X t t t t t t � � � � � � Q Q Q Q Q Q z o o o N N N N 3 U-0 U-0 U O U CU cucuU N o 0 0 0> O> O> O> a z z z z z z X X X X X X 2 2 2 2 2 2 N O U C O cu 4 O N N N cu L m N to m t ^ 4J O C C vi O O U O �i Q �O Q i O Q X O 4, C N to C m O Q- u c0 }, m E N •� Y 7 N O N L O N O Q� cOo J `n O U C E L cu O Q C L U V1 C7 M V1 a- } � 4• Y 7 O N to O E E to X O N M -0 N L C +J O u m 4J C O t L m J N C L m �_ U N +' L =3 O +J t U +J O +' m O 4' C 4J C +' U C N C c G N L O 'L Q Q Q N N i N N.- O N +�+ O cu C +J cu N t N U C E Q i Q Q 4- vi N a N a-J N Y Y N ._ O J O '� Q N i C f0 N f0 +� c0 ~ Q i LJ N E 'cu � O O N J UN m m V1 � Q �O �� O qp v m L 4' U Vl U '� Qn u� , E Q C O +' to CU CaM +' a• •� — � N a-•� C '^ O � N O to � U� O ut L N L 4J U Q N N 2i p O N O N U-a t 4J 4J C C— O O C ( L O co cu CUV, CU ut C7 C v ut ~ u O d D � o v o O +J m Q v Q O X N n U N-0 Q O N ago U C - M . E- (� `� N O 7 L WD +- N Qn N Q O= N � >- J U E N to � a co (a c0 7 � i — 4• c0 3 N > C c0 u -0 = L N N c0 7 dA O m O m O N +' c `� � �-0 M C N O E N m v H f0 f0 N U �-0 N uO dA m E L a N i +J Qn ut f0 M %` 4- a,,, ut f0 J N N i Qn cO N >` .nC N N C O +' 4 J N C N C 1 c0 U Q C N c0 c0 +J .0 L t (o �_ i cu Qn O U .0 O 1 N +J 7 Of0 4J > Eb N a'' O �. O CU cu c •� ut f0 M LJ -0 M 7 >N N! 1�1 L N C 4 J f0 Q C O C 4 J Q C U (n C CO N d U O Q U o0 > LL L d Q w 2 ro D U .S O U 7 O N U O O N .� � ML7- O N O O V1 O O O O O O cu cu E E E E L L N N N N 4- 4- Ln Ln Ln Ln CU w CU V, cu O dA O O U O (a U O (a U O (a U O U N U N U N U N V Q Q JO C JO C JO C � C i Qn cu Qn cu cu cu cu w U U m U U U U .Z U L N L N L N L N L N L N N O c I M Ln l0 *k O O O O O O L.0 L.0 L.0 L.0 L.0 L.0 r-1 LD cu to Ca d O r-I N X 4-1 5m L W ^m m 4-1 t U m Q H U O z Q X t t t t t t t t t � 41 41 41 41 � � � L v �nn L V E a- a- a Q Q �O U U •� O U U C C C C C C / C •� v C / C / O O O O O O O O a O O d Z Z Z Z Z Z Z a' a Z Z X X X X X X X X X 2 2 2 2 2 2 2 2 2 Vt m N N coo C mC O N N L O U O O C O 4J 4J N p C O C O C +j co > N = ^ N L O O io 7 O C U N N ut N cu L Q 4 J O O Ca >- N U O U L O cu L N L O > fa N u u U u U- U O C � O C t 4O N N 4�O N Q +� N Q N-0 N � O U on 4J O Qn L O N 7 Q- -0 � ate•' 4 J C 7 N C O Vi - cu +, N U C m N N � +J -0-0 C cu O 0A O 4, .� aj C to co Q Q +3 Vi 7 m cu Q .� Q L .`^ V1 N � N +� L N +' O O � O 4, N O m 7 m N N U C C M N - L T C C L m > Q L.L -0 m � (a 4, U -0 E m 4-1 N N +j >_ N � vi w p N U p O OL QnN N O `;t N +J tvD U U c 4-11 fC N C t +JC 4-1 o O cu NO u o Qn t U E O L +J 0 U 4-1 +J Q -0 to Cp u Qn 4-1 u to + N N } N > u U N-0 C NCC N •0 N O 4-1 N 4-1 vU 0 cu >4-1N m cu N L O-1 N � —+ ' �o CU N O Qn 4-1N C cu O 4-1 � +J+' � 6- C m vLQOi CO>� :E U CL O O U + m m u N C O > O 7Q ' +E O N � LO p 7 0 N CL oa-' M " O m U � U 4-1 � N O� 0 C4-1 0 CL 4-1O Qn a - cum N .a;H Cp Q N 4-1 - m L p +cBJ + a1C C=N cu v 0E OaJ N CU E 0 = O E + Q N Q- N U N p 4-1 +O > � U N N L N N U N Q" C)"C V +J cn m O C L^Ci~- o U O — U ( `7 +Jto V, V, Qn Qn cn cn cn cn cn cn cn cn cn i O N O N O N O N O N O N O N O N O N p U U U O m U O U Om U O O U U O U txoO m .O m m m m m .O m L U ai L u ai L U cu L U cu L u ai L u ai U L cu L u ai u L ai Q 4-1 � Q 4-1 � Q 4-1 � Q 4-1 � Q 4-1 � Q 4-1 � Q 4-1 � Q 4-1 � Q U i U U U U U U U U U U aOj 4Oj aOj aOj aOj aOj aOj aOj aOj N C C C C C C C C C I� 00 m O c I N M 111 lfl lfl lfl lfl lfl lfl lfl lfl lfl N LD N to Ca d C1 O r-I N X 4-1 5m G H m Q m 4-1 t U m Q H U O z Q x U co co co co m m >. +, m m m m E Q Q Q Q Q Q c:Q Q Q Q z � L cu � Lv Y Y cu cuQ > cu cu cu cu Q u 3 co CU u fu CU u co U L co U L ra aU u \ ra aU u \ co U= co CU U ra CU U ra CU U m a) U \ \ 0 O O O O O O O co O O O O a z z z z z z z Q- z z z z o x x x x x x x x x x x 2 2 2 2 2 2 2 2 2 2 2 _ c a-J c O Q aJ v � aj U O `~ (a cu O a-.� (a cu ( cu cu (a=Oi 7 O cu } > U L cu m� m w O O cu CU d 0 N u �O E cu CL m 0 Q f0 CJ a-E Q L N- O aJ -0 m E — O aJ U c L O O Lcu O � N >- CO Cn > OL t U m nC3 4, co c o aco a o O o O (7 m ao cu cuL C Qn cu u m -0 CU O >- O O vi O to 0 ^ aJ mCU N -0 L to a•' O O +J n3 c O c O c +J L N Qn +J aJ O m Q 7 -0 vi x 3i .0 0 C f0 O < U vi O cu m c C m aJ Q aJ � m m L U O cu +J c L U c ++ aJ J > c Q Ca •V1 4J Q Q V1 aJ J aJ — Ca O aJ Q 4' (n L O U > aJ 4 J J >> U CU J vi c 7 -0 aJ > 4O Q Ca O aJ L +J L fC Q Q O aJ D_ (� 4 J aJ N Q c Q O O } C +(A cu Q a_ O vi O +� u > aJ io aJ io U � fu °c_D n3 +, v Q t � 3 v O L O Q v 7 U `� co � � n3 Cn c U t o � n3 aJ aJ c c to a•' f0 U" CU O> J i O f0 +J f0 aJ aJ > Ca f0 E f0 E � f° � L o O O m Y � v O O � n3 +� �; v ( U ao m V1 cu U o � W _ U_ O w aJ m =3 J 7 V1 v, cuaJ O > v O CU O 4J 4, m c m c > v -0 � U U Q vi 7 •� m +� _ 7 CU '� >O Q > +J f0 f0 O U c O O m L v�i i aJ > cu t t vi vi m > f0 aJ 7 7 aJ -o O L aJ — L O L O aJ O O aJ cu > O C . �O aj Qn O cu O Q m 0o +' L �' aJ vi u O O C _ 2 U O Q O aJ N �_ _ U 0 �_ Q M Q O Q 4 J L co O L M M 4 J L aJ 7 O aJ Q U c 7 = t +-' �, m 4 J O_ U > a•' = > > O L > O 7 O O O f0 O aJ O I U O t W 7 U� c c O vi >, w c �i cu vi CU L CU L cn U L Q Q Q cn � 7— 4- L w— m O vi 00 7 c0 2 m > d V1 D_ Qn Qn Q Qn Q Q Q v +J v +J v +J v 4J v 4J v 4J v 4J v 4J v 4J v 4J v 4J n n i O cu O w O cu O cu O cu O cu O cu O w O w O cu 76 O aJ O n3 O n3 O n3 .O n3 .O n3 O n3 O n3 O n3 O n3 O n3 U O n3 4 U L aJ 4 L U aJ 4 L U aJ 4 L U aJ 4 L U aJ 4 U L aJ 4 L U aJ 4 L U aJ 4 L U aJ 4 L U w 4" L U O 4� O 4� O 4� O 4� O 4� O 4� O 4� O 4� O 4� O � O � i v v v v v v v v v v v U U U U U U U U U U U U cu a-J L cu 4 L cu +J L cu +J L cu +J L cu +J L cu +J L cu +J L cu +J L cu +J L +J 41 N c c c c c c c c c c c l0 Il 00 m O c-1 N M Ln l0 *k c-I c-I c-I c-I N N N N N N N lfl lfl to to to to to to to to to m to aJ to Ca d O r-I N X 4-1 m 2 H G! m Q m 4-1 t U m Q H U O z Q X t u U t t t t u U u U U >� U c0 U c0 U c0 U c0 >vi >vi Ec0 CL io C Q- Q- Q- CL „ co io co io z o N Q ^ N N cu 2 Q Q �^ — `1 — `1 — `1 4= U co ai co = n3 (o (o (o n3 v n3 L co L 3 U U u U L U L U L U V1 U a1 U a1 C > o 0 O fa O O O O w O O O O a z z .CL z z z z C C z CL X X X X X X X X 2 2 2 2 2 2 = 2 i C Ca aJ J aJ 4, aJ cu C aJ cu u co -0 v v Q� O C to — O — 3 V1 u cu L n3 C aJ cu -0= 7 aJ to t 4, t O C N 7 4 J O N Y p aJ U O Y O Q +J O OC cu 0o to � � 0 •� (a � � Ocu O � ^ O> O � t C +to ' aJ vi C vi CL CU> O + •= •�' aJ m c� cu o cu m O Q •� W O C aJ vi (A +J i5 a) aJ +J to 4 J cSS L c0 >� c0 p L J 4 J Q Q V1 U cu V1 U 'A N 4 J O 0 L " aJ aJ vi E O > C co O c0 O N vi c0 aJ aJ aJ a-� co U +' to > Q p Qi to a) m t.7 L }� +J Q cu T � C a-J co cu > aJ aJ aJ �_ c —_ n3 CO _� O E O _� O 7 +' +' +' aJ - O L O > C L O v C do O co C to O Q 0o N c0 Q L — c0 +J c0 O Q L p c0 z 7 4. aJ 7 — C C m p C = " O M cu > O �O aJ p cu O O to aJ O to c0 O L Q vi L O aCJ C co O co U tvD a1 O U a�J t •C Q t •C N L i O O C vi aJ O t L +J Q 4 J Q C L > V p a'' p— C +� 7 O L cu 4 � +, m p t Q J 4 J > C C Q co t X U Q c0 O C cu Q CU c0 cu v CL E c �U, O O O cu O 4 J u 7 J Q 7 Oo O N Q > > 61 p O �O aJ \ O O c O � cu U 4 O U� O O U cu CL cu c >` } Q > Q O L O L vi C C N cS3 U E +J n3 E t O a J L c0 Q aJ L c0 Q f V1 CL a�j ( co to 2 w Q J u> Y L� V1 L a�j C L +' E too > do E_ U +J aJ L 4' 7 +J U C +J p } Q u Q aJ 7 aJ C C n3 v �_ v n3 C L t J Q M+ E +� f° E O U t 4 J t 4 J Q' E a-J aJ aJ vi 7 0 u E. 4� N aJ Q U +J >, :} Q U C +J U U aJ +� � Z t -0 cu aJ QC U Q U Ln i C co C C vi C >` aJ O aJ L N +J aJ co > L N �^ aJ 72 > 72 > C p � aJ aJ i � cu 2 w > 7 ^ l" co ^ C O Q- C co L Q O aJ •C p Q > +' tLD p Q E a O i 7 O O U> X w > L ^ 4 J ^ E vi O 4 J vi .L vi w O vi 0o Q m w n3 m Q m 4 J U a a aJ Q a a N n O O O io O O 7 cn vOi .� cCU vOi cOo co O cu cu cu cu cu cu aa) aa) cn cn cn cn cn cn cn cn i N cu cu N N N N N p O U O U O U O U O U O U O U O U ++ U v u v u v u v u v u v u v u v o C o c o c o c o c o c o c o c V i U Z U U U U U U 4 U .2 U L v L v L v L v L v L v L v L v N C C C C C C C C Il 00 m O rI N M *k N N N M M M M M lfl lfl lfl lfl lfl lfl lfl lfl LD aJ to Ca CL O r-I N X 4-1 m 2 H G! m Q m 4-1 t U m Q H U O z Q X U U V1 U V1 U U U U U � +J > Ln +J f0 > z 4-1 CO > }, +J to +J to +J to +J to +J m c0 C C Q Q Q Q LLn Q Z Q Q Vl Q Vl E cu cu cuY cu > w Qn w V 3 M L U cuu m u co = U u Ca cura U CUra U CU U C~ U— ra CU U C 3: C 4J C 4J C C C C fB C> O O O O Q O Q O O O O v O a z z .LA z LA z z z z z o (D o -0 v t c V c N LL v v t ai Q CU c �- " � co o cu O O t +� ', v O C L N v u N +J �i N C -0 v Y `o O `~ O -0 OC C `~ Y m + Q `^ +J " O N 4 J M 4J N •vi + C L, O `-' C C O 00 E w O 00 C} qp +� U Qn^ U cu L O +, L E c +� �, c� v o an �-0 N v c d( c co U L co O vi Q co +, U CU -0 N Q O U U m 2i O N N L 7 CU-0� m N N t O J C E M C O L 4' > C 7 co f C - N L N U 4 J O C •� — m C O •� U m 4' > +J C 4' 4 v, v .Q CU Q O C C v co a= _ C cu N C O Q O m co C v v, N _ t UA =3 O O N .— Q U t O UA O U C u N vi Q Up N N O Ln -0 O i 7 p m - O UA toO CL O UA C N ut L U +J C L L N cu c O c0 Q 4� Q m co 4- Q L� C CU C LJ u J C fC L Q X UA N O L Q m O O O N L UA N N U C a-J c C m c0 Q a�-J i N •� C N U O M LJ 4 J O m LO ^ 4' co UO N j5.2 UA 0 O N— O � C C O Q Q C O U >` Z UA U Q u a�j U a�j UA O LO +, Q Q N io .0 ^ N C N cC0 N UA N cu -0 LJ C N N C O N O C 7 C N O 4, M , U 4 C� Q C t U Q +J L .0 .� O L CU_ C 4 J N C O U cCo U--0 O a.., U MC r'I N M ut 0 O — z m U cr! U N � Qn M Q •N C 0 m * C p co w vi +J cu U N t t m Qn 4J N N L N 4J C O > O N N - UA 4J > p Q 0 N t N m c a-J a.., L O Q t L >` f0 V1 N 4 J C Cc: 4 J Q fL0 Up L C -c 4 J a'' C Q L 7 +J f0 O CO C_ •� Q C v� L Q 4 J UA Qn O Q O f0 > a'' C 4 J L V1 N UA 4 J •L +J V1 (\/1 L N '� ut cr 0) Z (�/1 •C_ (�/1 C VI O L N'n f0 U f0 U CU U L a", _ C O Q w Q .L j Q >' N-0 N 0 N ?i w C O O cu C Q co +J U C co co U N U Qn Vi M O 4 J � N N O co O > N u N O (n QCa ut LA -0 -0 :-7 O 7 Q c (n ut f0 u Q Q c C f0 Q 4- > Ol W >` f0 ut Q L C Q C ._ M 4- 4- L d 4- (n > C N V, V, V, V, V, V, Ln 4 Ln Ln Ln Ln Ln Ln Ln Ln i(aQn C N m N C C cu Qn C cu C cu C N C N C N C U U U U U U U U � ++ u v u 0 �O— u v 4O— u v �O— u v �O— u v u v �O— u v U o c o c o c o c o c o c o c o c i U U U U U U U U U cu L cu L cu L cu L cu L cu L cu L N Ln l0 Il 00 m *k rn rn rn rn rn L.D L.D L.0 L.0 L.0 L.0 L.0 L.0 U) LD Q UA Ca d O r-I N X 4-1 m 2 H G! m Q m 4-1 t U m Q H U O z Q X t t t t t t t t � 41 41 41 m m 41 m 41 co co co 41 co co z N N D N N a- — — 3 U O O u O u Ca U Ca U O U N u u :t c c c c c ccr- c 4- p 4J O O O O O O O O z O z a z z z z z z z z X X X X X X X X 2 2 2 2 2 2 2 2 O L 4J Q >, 0A Q O c Q Q •� >- c I O N c CaU O O L 4J c LO c c O L O Q_ N cu �_ m vi N (a cO cO (n Q v Q O O O 0 CL U U p O O O O a U to L +J f° O O O O O co Q O Q f° U Q Q �C E L C QU u v t L �"I Ln to m N m c = O 7 f0 Q 7 m cu V1 O N •� � L ; — ?� Q c O 00 d V1 co O > 1 O a= O Z L c a J C O Qn vi m +J 00- +� L O N +� c toU O +J O co L O O O 4, Qn O +J c m O O +J L v t O vi c c L a J L to O co (0 O t v +� co O c v, i` v Q v v o co co v Q +J Q •U .O Q M � Q vi E U Q � ~ Q O vi O +J O _ v Q L m LJ O O � u L -0 m 4- E O Q O U O vi vi m c C _ dOA vi O Q" c O u +� vi O _ co .O O _ O CL N to L OOn O 0 L U �^ c Q vi p c � O c O O �= 4 J 4, c 4 J O Q tB U O t Q H co > Q � co Q (� U O c .2 c U L -- m �' Y O L O cO — N L E 7 O 4 J O t O vi 4 J 4' p co +, Qn Q � c i L p to M 0 4- L U t 7� U Q O > L m L U ,} O O OL Ln = m O 0 L O 00 O to L Q u .L p u N CL O t O O u � O Q — w" c0 O O 4 J M-0 U cu c O +J O +J +� U co co to O +J CL c cco U O O Qp O c O > ,} O N ^ vi O L +J 4' O c Q co O co c +J O — O a�j _ L O O vi O U U N n-a L p O c O cOo WD coo U +' O Q CU (n m U Q aJ a�J � C O L c Q U +O M > 4J L i to >' "-0 n vLn= c U Q Ca = < a- a" CU a• 41 L Q Q }L U \ a OO co Nc 0 O N UQ vi Q O O O -0 O Q N L io � Q> z >- U U O O O c u 0A — Q U � c O O O } fu Q i C c U U c O O O c co O L L O co .� U o_ O D 2 O +J 2 co O co Q ._ O to c to .— o_ L o_ O E Q E E v v v c c c O O O o o 4� z z cn cn cn 4J 4J m m m Qn c v c v c v 4J v ^ 4J v ^ c v c v c v O U O U U O U U U U U dA co .2 co m M C M +�+ u v u w u v E ("UE ("UE v E v E v U o c o c o c Q c Q c v c v c v c i U U U U U U U U U O L O L O L O L O L O L O L O N M Ln l0 I- 00 m O L.0 ID ID ID ID L.0 L.0 L.0 Q to d � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment H — Interface Descriptions COTS Interfaces HxGN Dispatch I CAD Link To Motorola RMS, ESO SafetyFAD, & ESO FRMS Description: OnCall Dispatch I CAD Link interface to facilitate the automatic periodic transfer of event and unit information from OnCall Dispatch to external systems such as Police Records Management, Electronic Patient Care, and Fire Records Management systems using XML files ASCII delimited files. The third -party vendor (or the Customer) is then responsible for importing the information into the designated database. The CAD Link interface includes support for configurable event profiles; these are sets of event criteria for matching data field values within the OnCall events to be exported and a configurable target directory for exported output files. The profiles act as event filters, determining which OnCall events are to be exported to which file system directories (inboxes). Assumptions: Hexagon assumes this is for the transfer of CAD event and unit data only to the specified systems. Additional services are required from the third -party vendor to consume and distribute the incident information provided via CAD Link. The Customer will be responsible for any data mapping The Customer will provide a technical resource as well as any necessary subject matter experts The Customer will provide a test system for installation and testing Hexagon will configure CAD Link to output to a single location where the Customer is responsible for consuming the data The Customer is responsible for ensuring that any third -party vendor technical resources are available to support the testing of this interface. Hexagon assumes that the third -party vendor will be utilizing XML protocols for this interface. This is a one-way interface. CAD Link exports OnCall Dispatch incident -related data, but it does not import data. Any import is the responsibility of Customer or of the third -party vendor. Constraints: OnCall Dispatch events must be closed before they are candidates for export by CAD Link. CAD Link does not provide features for obtaining "next available case numbers," "location verification," or any other OnCall Dispatch -related functionality or interface; it only provides export of specified event data for closed OnCall Dispatch events. HxGN OnCall Dispatch I Fire Station Alerting To WestNet First -In Statement of Work � /HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Description: OnCall Dispatch I Fire Station Alerting (FSA) is a software interface between OnCall Dispatch and WestNet First -In. It provides a method for OnCall Dispatch to send audible alerts to fire stations. The interface provides support for remote fire station turnout when units from a station are dispatched. It interfaces to third -party alerting controllers, such as Zetron I FSA, and performs such operations as ringing alarms and enabling public address systems. Fire station operators can also change the unit status of vehicles from the station, such as en -route and available -in -station, if the alerting controller supports this feature. The actions taken in the fire station (ringing alarms, enabling PAs) are implementation -dependent upon the station and the alerting controller. The functionality of this product is limited to sending alerts upon the dispatch of a unit from a station, disabling alerts on a unit status change, and setting unit status. Assumptions: Hexagon assumes the Customer uses one of the existing Fire Station Alerting systems currently supported: Motorola MFD-P 7.34 IP ACE 3600 Locution CADVoice revision 4.0 Westnet First -In CADI version 1.0.6 Zetron I FSA version 2.6.0 One implementation of FSA interface is required for each distinct Turnout Controller. Hexagon has assumed that all stations will use the same controller. If not, additional licenses and services may be required at additional cost. Constraints: Hexagon cannot be held accountable for incompatibilities in its interface that are due to changes in input/output formats or data requirements of the vendor's product The Customer is responsible for providing complete and accurate documentation on the devices with which FSA will be implemented The Customer is responsible for providing any specific SDK necessary to implement the interface to the Turnout Controller. HxGN OnCall Dispatch I Deccan LiveMUM Description: OnCall Dispatch I Deccan LiveMUM Interface provides a two-way interface between OnCall and the Deccan LiveMUM software for move -up algorithms to monitor and adjust resource coverage for Fire and Ambulance agencies. Deccan International's Move -Up Module (LiveMUM) interprets CAD unit and event data and presents it in an easy to understand, color -coded map format for evaluating unit coverage. LiveMUM reveals holes in service area coverage and offers recommendations for reallocation of first responder units. LiveMUM monitors OnCall Dispatch unit and event information and applies move -up algorithms to determine unit move -up recommendations in real time. The OnCall Dispatch I Deccan LiveMUM Interface supports a two- way interface between OnCall Dispatch and LiveMUM by which dispatchers are notified of move -up needs Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation in OnCall Dispatch. The dispatcher can then analyze, change move -up recommendations through LiveMUM and execute the move -up in OnCall Dispatch. This relieves the strain placed on the dispatchers to make complex analysis in maintaining the status of coverage in the service areas. Benefits: Get a continuous updated display indicating the status of live engine, ladder, and ALS coverage by accurately analyzing CAD data in real-time. Get color -coded maps that allow dispatchers to instantly view weaknesses and strengths in coverage. Test and evaluate the effectiveness of pre -planned reallocations taking into account the various specific agency criteria set by the agency. Achieve consistency in quality of reallocation across all dispatchers by removing need of personal objectivity. Obtain a log of dispatcher decisions for review. Assumptions: Hexagon only interfaces with LiveMUM for the relocation of units. Hexagon does not interface with Deccan's ADAM or BARB products. This interface will send the standard XML protocol that Hexagon has defined for unit status information to the Deccan -written server over the TCP/IP connection. Each unit status change will result in a transmission from Deccan Interface to the Deccan -written server. This interface price does not include the cost associated by Deccan to write their server piece. It is the responsibility of the external system vendor, or Customer, to develop any programs necessary to interface with Deccan Interface using the provided XML documents. HxGN Dispatch I Informer To NCIC & Motorola RMS Description: The Informer interface automatically routes queries and responses between clients and the external systems, and if the external database supports unique routing codes for each query and response, Informer may be implemented to automatically initiate queries in response to actions executed within the OnCall Dispatch system. For example, defining an event as a vehicle stop and entering the license tag number within OnCall Dispatch may automatically initiate the "Vehicle Query by License Number." The product can be further configured to automatically enter all query results in a centralized server log, as well as to automatically attach query results to the event. Using the OnCall Dispatch messaging capability, responses may also be forwarded. Informer can be configured to use and display HTML forms on its front-end client application. Informer can display HTML, XML/XSL or plain ASCII text responses on that same client. Informer is comprised of user dialogs and service components. The service components are: A module that runs in the OnCall environment, A provider that directly interfaces to external systems, and A bridge that handles communication between the two. Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation These services are orchestrated to route requests and responses between OnCall and the external systems. The services are architected so the module, bridge and provider can be configured to run in the cloud or on -premise. For example, OnCall and the module could be configured to run in the cloud with the bridge and provider configured to run on -premise to facilitate communications with the external systems. The user dialogs are a standard feature that work within OnCall Dispatch I Essentials and OnCall Dispatch I Advantage. When configured, these dialogs present the OnCall user with an Informer Message view that will allow them to submit requests and view responses. The dialogs component also supports a command line interface from within the OnCall Dispatch products. A set of configurable OnCall dialogs are provided which are used to collect request data and submit it to external systems. Informer includes eight unique OnCall dialogs and the request messages they generate. These are: 1. Person (wanted, missing, driver's license) 2. Vehicle (stolen, registration) 3. Article (serial number, type) 4. Boat (hull number, registration number) 5. Gun (serial number, caliber, make) 6. Hazmat (United Nations Number) 7. Lojack (lojack id, reply code) 8. Passthrough Additional OnCall dialogs, request messages, and response displays can be developed through extra services. Informer includes three providers that can be configured to communicate with external systems. These are: • Open Database Connectivity (ODBC) • CommSys • OnCall Records In addition, Informer provides: Explicit sign on and sign off using authorizations defined in the OnCall database Transaction level security, which verifies user authorization for each query type Hit detection that allows responses to be searched for specific text. If found, notifications can be automatically distributed based on configurable designations Informer currently supports XML responses in TCP/IP packets. Assumptions: • Implementation of the CommSys provider requires at a minimum the purchase of the CommSys ConnectCIC module and its data -mining feature. Additional CommSys features like secondary queries, normalization of response data and the transform of State/NCIC XML responses into "readable" text messages are available for an additional charge. Additional provider implementations can be developed through extra services. Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation The connection to a state or national database may require additional hardware and software. Connection through TCP/IP or Web Site is highly preferred. Each distinct provider requires OnCall Dispatch I Informer implementation installation and configuration services. A single license supports a given site. However, each distinct database connection requires custom OnCall Dispatch I Informer implementation development services. HxGN Dispatch I Tracker to Radio Description: HxGN OnCall Dispatch I Tracker accepts incoming Global Positioning Satellite (GPS) data directly from a GPS device, location servers or mobile data devices. HxGN OnCall Dispatch I Tracker functions as an extension to the dispatch environment, periodically updating vehicle and personnel locations in OnCall maps and monitors. Supported GPS Devices • Devices running Mobile Responder or other Hexagon mobile clients c Radios transmitting GPS data in the following message formats Trimble TAIP messages, UDP connection NMEA messages, UDP connection OpenSky messages, UDP connection Harris GPS Radio Types M-803, M5300, M7200, M7300, P5400, P5500, P7200 transmit OpenSky GLR1/GLP1 messages over UDP OMA/MLP (web service) Non -Supported GPS Device • Smartphones not running Mobile Responder or other Hexagon mobile clients 0 Motorola radios using the P25 message Harris radios that do not support OpenSky messages M7100, P7100, XG-100M, XG-75, XG-100P Certain GPS devices also accept commands from external systems to control the frequency of location reports. HxGN OnCall Dispatch ITracker can be configured to send the appropriate commands to these devices, setting the frequency of location reports based upon unit type, unit status, and the type of event the unit is currently assigned to. When OnCall Dispatch I Tracker is used with our mobile solution on MDCs, Mobile for Public Safety (MPS) uses the in -vehicle map and high-speed access to the GPS receiver to match the vehicles route to the map to determine the address of the vehicle. This approach is necessary because mapping information is seldom as accurate as the GPS device. The map is often several hundred feet off from the true location. This approach is more accurate than the more common method of using a server to attempt to place a point on the map based on a single position report. The computed location is used to pre - populate forms requiring a location such as on -view incidents and unit emergency. The officer can override the location if required as a final check before submitting the command. Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation The selected GPS receivers may support commands to change their delta time and/or delta distance reporting rates dynamically. AVL information may be used in the CAD system in the Recommend Unit processing. Assumptions: 0 Licensing is by device OnCall Dispatch I Tracker is a zero -cost product when bidding Hexagon mobile clients (Mobile Unit and Mobile Responder) Pricing is only required when connecting to non -Hexagon devices such as radios and third party mobile clients OnCall Dispatch I Tracker must be installed and licensed to track any device even if there is no cost to the Customer The OnCall Dispatch I Tracker interface establishes communications between a third -party AVL controller/message switch and the OnCall Dispatch System. Hexagon assumes that communication with the AVL controller/message switch will be achieved via TCP/IP or serial line (RS-232) communication protocol. The OnCall Dispatch I Tracker interface supports NMEA, OpenSky, BlueTree, Sierra Wireless RNAP, and TAIP protocols and devices that support these protocols should be compatible with OnCall Dispatch I Tracker. If the Customer is currently running AVL hardware that OnCall Dispatch I Tracker does not support, additional services must be purchased to develop a custom AVL interface. Hexagon recommends that the Customer purchase a device such as the Sierra Wireless, Trimble TrimFleet, or Airlink modems that supports one of the above protocols. Hexagon assumes that the Customer uses one of the supported GPS Receiver/Systems. If the Customer requires Hexagon to interface to a GPS Receiver/System that is not supported, additional development services will need to be quoted. Constraints: The Customer is responsible for providing Hexagon with a complete and accurate description of the interface to the AVL controller/message switch. Additional licenses may be required if the number of units exceeds 250. If the Customer has AVL hardware that OnCall Dispatch I Tracker currently does not support, Hexagon reserves the right to bid additional services to develop a custom AVL interface. Hexagon cannot be held accountable for incompatibilities that occur in this interface as the result of changes to input/output formats or data requirements associated with the third -party vendor's product. HxGN OnCall Dispatch I ProQA Description: The OnCall Dispatch I ProQA Interface for Paramount application is a protocol -based product that provides a standard certified set of determination questions and answers that Police, Fire and EMS can use to identify the necessary resources required when responding to an event. OnCall Dispatch I ProQA Interface for Paramount is an add -in to the OnCall Dispatch I Call -Taker application (included with OnCall Dispatch Advantage). Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Key Features: Multi -discipline launching Pre -alerts Transfer of location information to OnCall Dispatch I Call -Taker Configured to spill key questions into the Event information remarks field. We also provide a Pre -Alert capability, if ProQA is configured to send the chief complaint code and the answers to the initial questions to CAD before the user starts answering the Key Questions. CAD can then create the event or create and automatically accept the event dependent on the configuration. Per the Priority Dispatch Paramount website, Hexagon (as Intergraph Corporation) is listed at the platinum level. Upon determination by the operator that Paramount medical is needed, the operator clicks the Medical button, or issues the medical command. The interface brings the Paramount Medical application to the foreground and places focus in first editable control. The operator then progresses through the paramount application as normal. Upon reaching a determinant code, the operator clicks the flashing alert symbol in Paramount causing the data to be sent to OnCall Dispatch I Advantage. The Paramount application will populate location, caller information, an event -type and sub -type, and the key questions as configured by the Paramount medical admin utility, will spill into the event remarks. OnCall Dispatch Advantage can optionally automatically accept the event or allow the operator to make further edits and then accept the event. The operator then places the event into update to allow Paramount to make any further changes as the operator completes the case in Paramount. Upon completion of the Paramount case, the operator would accept any changes into the OnCall Dispatch event. OnCall Dispatch records the Paramount case number as part of the event record so that the case is permanently linked to the event. If the Paramount button (or command) is clicked for an event that already had Paramount run against it, the case summary is displayed in Paramount. A single agency event can only have one Paramount case number associated with it. Assumptions: The OnCall Dispatch system supports ProQA version 13.0. SMS Texting is not currently supported for Paramount 5.1. ProQA Interface is installed in Customer's data center. HxGN Connect Video I Streamer Description: The HxGN Video Streamer VMS (HVS) and associated client component (Video Responder) allows web applications to display video originating from Video Management Systems (VMSs) in an RTSP format encoded as H.264. Video Streamer and Responder are critical to delivering web -based video to the OnCall Dispatch and security -based applications. It is a prerequisite product for the OnCall Dispatch I Video Responder product for video display. Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation The HVS is comprised of a number of components: HVS Video Player Component HVS Configuration Server HVS Video Streamer HVS Signaling Server The HVS Video Player is a client web component for displaying low latency video streams within an HTML5 <video> element to the end user. Video streams are received through the WebRTC protocol using WebRTC-UDP and WebRTC-TCP transports. The HVS Configuration Server is used to configure the HVS application. It includes an administration web application that can be used to setup, configure, and monitor the overall health of the HVS. Features include the ability to discover and testing of cameras, the creation of HVS Streaming Servers, and monitoring active HVS Streaming Servers. It also serves as a load balancer for distributing network and application traffic across a number of HVS Streaming Servers. The HVS Video Streamer is a server component which reads RTSP input from video cameras or video management systems and converts the stream to a WebRTC protocol and video format suitable for playing in a web browser application. RTSP is a control protocol which is used for establishing and managing the transmission of video data. The HVS Signaling Server performs coordination of bi-directional communication between the HVS Video Player component and the HVS Video Streamer that will stream the video from the video source to the player. Assumptions: Each interface to an instance of a VMS or video system requires a separate license. If the Customer is connecting directly to cameras (e.g. URLs) then a license of HxGN Video Streamer Camera is required. The third -party VMS must support H.264 over RTSP. HxGN Connect Video I Streamer must be installed in the Customer's data center on the same network as their Milestone VMS. A VPN is required between HxGN Connect Video I Streamer in the Customer's data center and the Hexagon -managed Azure -hosted Video Responder environment. HxGN Interface I Milestone VMS Description: The HxGN Connect Interface I Milestone VMS provides a method to connect Milestone Video Management System to HxGN Connect Video I Streamer. HxGN Connect Video I Streamer is critical to delivering web -based video to the OnCall Dispatch and Security based applications. It is a pre -requisite product for the OnCall I Video Responder product for video display. Statement of Work 44 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Assumptions: • The Customer has the Milestone ONVIF bridge installed as part of their Milestone system. • HxGN Connect Video I Streamer VMS is a prerequisite. • One HxGN Connect Interface I Milestone VMS is required for every instance of Milestone VMS or Video System. • HxGN Connect Interface I Milestone VMS must be installed in the Customer's data center. Standard Interfaces ASAP (External Alarms OnCall Dispatch Interface) Description: The APCO ASAP Standard is supported using the External Alarms OnCall Dispatch Interface. It allows OnCall to interface with the APCO International Automated Secure Alarm Protocol (ASAP) Alarm System (also called "ASAP to PSAP"). The Automated Secure Alarm Protocol (ASAP) program is a computer -aided dispatch system designed by the Central Station Alarm Association (CSAA) and the Association of Public Safety Communications Officials (APCO Int'I). Because ASAP Alarm system operates on the National Law Enforcement Teletype System (NLETS) backbone — state specific development services may be required for each implementation to convert the APCO standard NLETS message into the State CJIS Message Switch format. Hexagon partner vendor CommSys licenses an ASAP add -on to their ConnectClC product that communicates with OnCall Dispatch Informer out of the box. Assumptions: • The Customer is responsible for coordinating deployment with The Monitoring Association (TMA) directly via CommSys as the representing agent. Requires ASAP Option from CommSys ConnectClC (included with this SOW). Constraints: • The Customer is responsible for providing complete and accurate description of the API needed to interface, and for any software/hardware/data required to implement communications with the external systems. Shotspotter (External Alarms OnCall Dispatch Interface) Description: The ShotSpotter Integration is an application that creates real-time incidents in OnCall when an Incident Notification message is received from ShotSpotter. The data is received over HTTP Transport. Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation ShotSpotter is a gunfire detection and location technology solution. When gunfire is detected within the solution, a message containing the alert and calculated location is transmitted over HTTP to this interface resulting in an incident to be created in OnCall. Constraints: The Customer is responsible for providing complete and accurate description of the API needed to interface, and for any software/hardware/data required to implement communications with the external systems. Harris Radio (PLT Radio OnCall Dispatch Interface) Description: The PLT Radio OnCall Dispatch Interface is an interface between Hexagon OnCall Tracker and a P25 Radio System to support receiving GPS data from the radio systems and report them to OnCall Dispatch as Tracker messages. This functionality is specific to the Person Level Tracking (PLT) Features in OnCall Dispatch. The vendors supported are: Motorola ASTRO P25 • Harris StatusAware P25 Assumptions: Additional third party licensing may be necessary; the Customer should consult with their radio provider for additional information. • Requires a separate license of HxGN OnCall Dispatch I Tracker. Constraints: The Customer is responsible for providing complete and accurate description of the API needed to interface, and for any software/hardware/data required to implement communications with the external systems. WebEOC Interface Description: The WebEOC CAD Interface provides real-time event data transfer from OnCall Dispatch to WebEOC for the purposes of supporting Incident Management workflows. Constraints: The Customer is responsible for providing complete and accurate description of the API needed to interface, and for any software/hardware/data required to implement communications with the external systems. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Everbridge (Dispatch Alerts OnCall Interface) Description: The Dispatch Alerts OnCall Interface provides a method for sending alerts, notifications and messages to third -party providers used in turn to notify a defined group of people. Notifications can include unit dispatch notification, command staff notifications, on demand personal notifications, etc. Assumptions: The Interface is compatible with the Everbridge REST API Specification document dated January 18, 2017 Constraints: The Customer is responsible for providing complete and accurate description of the API needed to interface, and for any software/hardware/data required to implement communications with the external systems. RapidSOS OnCall Call -Taker Interface Description: The RapidSOS OnCall Call -Taker Interface is an OnCall Call -Taker direct link based interface, for the purpose of receiving location accuracy information from the caller's device about the caller and offer updates on demand via the RapidSOS Web Portal. The interface will also support launching the RapidSOS portal using the phone number as a parameter to obtain additional information about the caller if desired. Assumptions: Call -taker interface requires OnCall Dispatch I Call -Taker (included as a component of Dispatch Advantage) as a prerequisite. Hexagon has also included pricing for the "connector" between RapidSOS and the Call -Taker Interface API (HxGN OnCall Dispatch I Call -Taker Interface) Consulting Services ALPR Hexagon has proposed consulting services for the ALPR vendor to become more familiar with the OnCall Dispatch I RestAPI. Assumptions: The third party vendor will write to Hexagon specifications. If Hexagon is also required to handle the transforms, a change order will be required for additional development services. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Custom Interfaces Motorola RMS Query The following inquiries are included: Person Inquiry by (NAM, DOB, SEX) or (OLN), State Vehicle Inquiry by (LIC), State Gun Inquiry by SER, MAKE, Caliber, Model This bid must be revisited if the transaction list is changed. A change order will be required if the agency requests changes to the transaction list after the SOW is approved. Assumptions: m The system supports an ODBC connection, SQL -based inquiries. This bid must be revisited if this assumption is not confirmed by the Customer. A change order will be required if the agency requests a different connection method is after the SOW is approved. • The Customer will provide the exact SQL for the inquiries listed. This is required during the ICD review phase. • Nested inquiries / follow up inquiries are excluded from this bid. • Images are excluded from this bid Test records will be provided by the customer/ ODBC system technical point of contact. This is required during the ICD review phase. Test records will return production -equivalent response data for each inquiry. The data requested in the select statements for the listed inquiries will not exceed the maximum number of fields listed below: Person Inquiry - 20 fields Vehicle Inquiry - 20 fields Firearms: 8 fields The inquiries will be supported from the Person, Vehicle and Gun forms that are included in the NCIC interface for OnCall Dispatch and Mobile Unit. No additional forms are included in this bid to support the inquiries. SQL and response examples will be provided during the Informer ICD review phase. This is required before software development begins. A test connection, including a compatible ODBC driver will be obtained by the Customer before the scheduled interface delivery milestone. The Customer will provide an SME during the development and implementation phases. Components of this interface will be installed in the Customer's data center (the Local Software Server). Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Traffic Management System (Opticom) Description: Hexagon will create an interface to import information such as incident location, vehicle locations, speed, direction of travel, vehicle type, etc., on a regular and frequent basis, as allowed by the communications network. This information will be used by Opticom to dynamically adjust traffic signals to expedite the routing of first responders. Assumptions: 1If Opticom allows communication via HTTP, this is the preferred method. If Opticom requires a TCP connection to a local controller, the main interface will be built in the Cloud Dispatch Program and communicate with an on -premise connector/provider that is Xalt based and installed in the Customer's data center (the Local Software Server). Constraints: • The Customer is responsible for providing complete and accurate description of the API needed to interface, and for any software/hardware/data required to implement communications with the external systems. Telestaff Description: Hexagon will create an Xalt-based interface that monitors a folder for Telestaff updates. Updates will be processed Xalt and submitted to RestAPI for updating. The interface and RestAPI will support updating the following information in Personnel records: Name Personnel Number Badge Number • Vehicle • Radio • Department • Position • Title • Skills Assumptions: Components of this interface will be installed in the Customer's data center (the Local Software Server). Statement of Work 44 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Constraints: • The Customer is responsible for providing complete and accurate description of the API needed to interface, and for any software/hardware/data required to implement communications with the external systems. Hydrant Description: The primary interface will exist in the Cloud Dispatch Program and talk to a connector/provider on premise via RabbitMQ to import hydrant information on some pre -defined interval (24 hours by default). Assumptions: • The on -premise connector can connect to the Hydrant database via ODBC, HTTP or file share. If not ODBC, data should be in XML, JSON or csv and delivered to a shared directory or via TCP socket or HTTP. Components of this interface will be installed in the Customer's data center (the Local Software Server). Constraints: • The Customer is responsible for providing complete and accurate description of the API needed to interface, and for any software/hardware/data required to implement communications with the external systems. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment I — CJIS Security Addendum FEDERAL BUREAU OF INVESTIGATION CRIMINAL JUSTICE INFORMATION SERVICES SECURITY ADDENDUM The goal of this document is to augment the CJIS Security Policy to ensure adequate security is provided for criminal justice systems while (1) under the control or management of a private entity or (2) connectivity to FBI CJIS Systems has been provided to a private entity (contractor). Adequate security is defined in Office of Management and Budget Circular A-130 as "security commensurate with the risk and magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of information." The intent of this Security Addendum is to require that the Contractor maintain a security program consistent with federal and state laws, regulations, and standards (including the CJIS Security Policy in effect when the contract is executed), as well as with policies and standards established by the Criminal Justice Information Services (CJIS) Advisory Policy Board (APB). This Security Addendum identifies the duties and responsibilities with respect to the installation and maintenance of adequate internal controls within the contractual relationship so that the security and integrity of the FBI's information resources are not compromised. The security program shall include consideration of personnel security, site security, system security, and data security, and technical security. The provisions of this Security Addendum apply to all personnel, systems, networks and support facilities supporting and/or acting on behalf of the government agency. 1.00 Definitions 1.01 Contracting Government Agency (CGA) - the government agency, whether a Criminal Justice Agency or a Noncriminal Justice Agency, which enters into an agreement with a private contractor subject to this Security Addendum. 1.02 Contractor - a private business, organization or individual which has entered into an agreement for the administration of criminal justice with a Criminal Justice Agency or a Noncriminal Justice Agency. 2.00 Responsibilities of the Contracting Government Agency. 2.01 The CGA will ensure that each Contractor employee receives a copy of the Security Addendum and the CJIS Security Policy and executes an acknowledgment of such receipt and the contents of the Security Addendum. The signed acknowledgments shall remain in the possession of the CGA and available for audit purposes. The acknowledgement may be signed by hand or via digital signature (see glossary for definition of digital signature). 3.00 Responsibilities of the Contractor. 3.01 The Contractor will maintain a security program consistent with federal and state laws, regulations, and standards (including the CJIS Security Policy in effect when the contract is executed and all subsequent versions), as well as with policies and standards established by the Criminal Justice Information Services (CJIS) Advisory Policy Board (APB). 4.00 Security Violations. Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation 4.01 The CGA must report security violations to the CJIS Systems Officer (CSO) and the Director, FBI, along with indications of actions taken by the CGA and Contractor. 4.02 Security violations can justify termination of the appended agreement. 4.03 Upon notification, the FBI reserves the right to: a. Investigate or decline to investigate any report of unauthorized use; b. Suspend or terminate access and services, including telecommunications links. The FBI will provide the CSO with timely written notice of the suspension. Access and services will be reinstated only after satisfactory assurances have been provided to the FBI by the CGA and Contractor. Upon termination, the Contractor's records containing CHRI must be deleted or returned to the CGA. 5.00 Audit 5.01 The FBI is authorized to perform a final audit of the Contractor's systems after termination of the Security Addendum. 6.00 Scope and Authority 6.01 This Security Addendum does not confer, grant, or authorize any rights, privileges, or obligations on any persons other than the Contractor, CGA, CJA (where applicable), CSA, and FBI. 6.02 The following documents are incorporated by reference and made part of this agreement: (1) the Security Addendum; (2) the NCIC 2000 Operating Manual; (3) the CJIS Security Policy; and (4) Title 28, Code of Federal Regulations, Part 20. The parties are also subject to applicable federal and state laws and regulations. 6.03 The terms set forth in this document do not constitute the sole understanding by and between the parties hereto; rather they augment the provisions of the CJIS Security Policy to provide a minimum basis for the security of the system and contained information and it is understood that there may be terms and conditions of the appended Agreement which impose more stringent requirements upon the Contractor. 6.04 This Security Addendum may only be modified by the FBI, and may not be modified by the parties to the appended Agreement without the consent of the FBI. 6.05 All notices and correspondence shall be forwarded by First Class mail to: Information Security Officer Criminal Justice Information Services Division, FBI 1000 Custer Hollow Road Clarksburg, West Virginia 26306 Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment J — Glossary of Terms Capitalized terms that are not defined below or within the body of the SOW, shall have the same meaning as set forth in the Master Terms Glossary. "Acceptance" to mean acceptance of a Task in accordance with Task Acceptance Process. "Analytics Cloud Program" means a certain Cloud Program that pertains only to OnCall Analytics. "Benchmark Criteria" means the objective criteria which identifies an intended outcome as reflected in, as applicable, an ICD, a Design Document, Specifications, or Software Requirements (whichever document having last addressed the functionality in question being dispositive) "Blocker Error" means a Level One Error. "CJIS" means the Criminal Justice Information Services Security Policy version number 5.8 formally published by the Federal Bureau of Investigation, Criminal Justice Information Services Division. "Cloud Consulting Services Order" means this Order for Cloud Consulting Services related to the Cloud Applications identified in the Cloud Program Order "Cloud Program Order" means that certain Order, which identifies the Cloud Applications and Cloud Term, executed simultaneously with this Order. For purposes of clarity, the Cloud Program Order is separate and distinct from the Cloud Consulting Services Order. "COTS Interfaces" means those Interfaces specifically identified in in the COTS Interface Questionnaire Completion task "Customer Responsibilities" means (1) those specific tasks and obligations identified in the SOW as being the responsibility of the Customer and (2) those obligations, not stated in the SOW, but which would otherwise be reasonably considered as being Customer obligations and responsibilities. "Custom Interfaces" means those Interface(s) specifically identified in the Custom Interface Requirements Gathering task "Customization" means a modification of the source code of Software "Cutover Plan" means a document reflecting the Activities and actions necessary to complete Cloud Cutover "Day" means a calendar day. "Design Document" means a document articulating the design and intended output of a Customization "Dispatch Cloud Program" means a certain Cloud Program, or as applicable, collection Cloud Applications, that pertains only to OnCall Dispatch, including but not limited to, OnCall Dispatcher, OnCall Calltaker, OnCall Viewer, OnCall Mobile Unit, and OnCall Mobile Responder "Documentation" means, whether in printed or electronic format, all documents (digital or hardcopy) delivered by Hexagon as part of the Project. Unless otherwise specified, it shall mean COTS Documentation. Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation "FIPS" means Federal information processing standards, which describe document processing, encryption, and other information technology standards for government contractors. "Fire/EMS" means the agency(ies) of Customer that are primarily oriented towards firefighting and emergency medical response. "GIS" means geographic information system "Initial Project Schedule" means the initial iteration of the Project Schedule, which is contained in Attachment A of the SOW. "Interface Control Document" or "ICD" means a document reflecting the design and requirements of a Custom Interface or certain Informer Interfaces based upon the requirements set forth in the Custom Interface Requirements Gathering task. "Help Desk Portal" the electronic portal through which Customer may access the Help Desk to among other actions, log Services Requests, review the Knowledge Base "Hexagon Project Manager" means the person authorized by Hexagon to coordinate and manage the providing of Hexagon Services and Deliverables for the Project on behalf of Hexagon, in addition to being responsible for other duties specified in the Agreement and SOW. "Law" means the agency(ies) of Customer that are primarily oriented towards statutory and regulatory code enforcement and service. "Master Terms Glossary" means that certain Common Terms Glossary contained in Exhibit G https://www.hexagonsafetyinfrastructure.com/-/media/Legal/Hexagon/Sl/Sales/MT/USMT082020.pdf "NCIC" means the National Crime Information Center "Network Infrastructure" means the provision of adequate network and internet connectivity to provide sufficient operational bandwidth for the operation of the Cloud Program in a manner consistent with the Product System Specifications together with all industry -standard network security, monitoring, and protection. "Permissive Errors" means a substantially failed Test Case that would correspond to a Level Two, Level Three, or Level Four Error (as defined in the HelpDesk website) if the Defect occurred in a live environment. "Production Ready System" means the earlier of: the point at which the Customer is either satisfied with the testing results for the Cloud Program or the resolution of all Blocker Errors reporting during Functional Testing. "Project Assumptions" means assumptions regarding the Project, which are listed in the SOW. Changes in any of the assumptions will affect the scope, schedule, and/or cost of the Project. "Project Start" means the date following mutual acceptance of the Cloud Consulting Services Order on which Hexagon communicates to the Customer the Project shall commence. "Project Team" means the applicable Core Team and other resources assigned to provide information or services in connection with the Project, or applicable part thereof. "Server Setup Worksheet" means a document reflecting, among other details, the identification of servers, IP addresses, and node names for the System. Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation "Site Configuration Document" means a document reflecting the configurations made to the System "Software Requirements" means the functionality and capabilities affirmatively included in the OnCall Software as expressly specified in OnCall Functional Matrix. "Specifications" means those certain capabilities and functionalities as explicitly expressed in the User Guide for OnCall Dispatch. To the extent there is any ambiguity as to the interpretation or meaning of a Specification, the actual functionality exhibited in the COTS Software shall control. "SR" or "Service Request" a request logged into Hexagon's Help Desk Portal identifying a request for Hexagon to address a Defect, question, provide an Update, or provide an enhancement request, among other requests. "Subject Matter Expert" or "SME" means a person(s) who has particular knowledge about a specific topic(s). "System Administrator(s)" means a person or persons having the appropriate education, training, and/or experience in information technology to provide first tier support of the System. "Task Prerequisites" means those events, Deliverables, or accomplishments that are required to occur prior to the commencement of the applicable Task, except as may otherwise be agreed by Hexagon. "Test Case" means a set of conditions and parameters agreed to by the Parties which the Parties shall use to test whether the intended functionality identified in the Benchmark Criteria is reflected in the System. "Test Case Failure" means a situation in which an executed Test Case has substantially failed in meeting the passage criteria set forth in the applicable portion of the Benchmark Criteria. "Updated Initial Project Schedule" means the Initial Project Schedule updated by the Parties' Project Managers during Project Initiation Task and reflecting the actual Project Start. " VPN" means virtual private network Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment K —Azure Maps Overview Hexagon's OnCall Dispatch System has been specifically designed to take advantage of server -based mapping services that may be a part of portal architectures that expand the development and deployment of Web mapping content. Having access to multiple basemaps and translucent raster overlays will allow users to call up the most appropriate map features for any number of dispatching scenarios. These services being available to users, yet managed in a highly available environment, is a significant strengthening of dispatching capabilities and begins to take advantage of current GIS technologies, as well as emphasizing the Web -centric nature of the technologies. What is the Mapping Technology within the HxGN OnCall System? Azure Maps is the default GIS provider for HxGN Dispatch Cloud application. Azure Maps web map services containing data for consumption by public safety and many other disciplines. Web Map Service - The map contains the area of responsibility for the dispatch system and is accessed by HxGN OnCall Dispatch through Web map services. Many maps may be accessible and configured as basemaps and/or translucent overlays to the basemaps. Azure Maps will be responsible for providing Web mapping services and is the default GIS provider for the Hexagon OnCall Cloud Program. Resiliency or the length of time the HxGN OnCall Dispatch system will wait to complete a request before returning an error is governed by the resiliency RequestTimeOut parameter and by default is set to 15 seconds. Note: The resiliency RequestTimeOut parameter is a high-level setting that applies to all URL requests and is not specific to just the Web map services being accessed. Web Geocoding Service - A Web geocoding service resolves address strings and street names to longitude/latitude coordinates (geocoding) and returns an address string for a point selected from the map or precision coordinate key -in (reverse-geocoding). Azure Maps will be responsible for providing Web geocoding services. Resiliency or the length of time the HxGN OnCall Dispatch system will wait to complete a request to the geocoding service or aggregated geocoding services before returning an error is governed at a high level by the resiliency RequestTimeOut parameter and at a low level by the geocoding AggregatorTimeout parameter. The default value of the geocoding AggregatorTimeout parameter is 5000 milliseconds (5 seconds) and applies to all the configured geocoders. Web Routing Service - A Web routing service is used to determine the best route between two or more points on the map based on time and distance. The routing service can also return driving directions for the calculated route. Azure Maps services have the capability to react to real-time traffic conditions, thereby increasing the accuracy of route results and providing more efficient workflows which strive to mimic real world conditions. Azure Maps will be responsible for providing Web routing services. Resiliency or the length of time the HxGN OnCall Dispatch system will wait to complete a request before returning an error is governed by the resiliency RequestTimeOut parameter and by default is set to 15 seconds. Latency in the Web router service could have an adverse effect on the recommend unit functionality. The recommend unit architecture has been extended to perform routes for multiple units in parallel thereby reducing susceptibility to latency issues. Polygons — The HxGN OnCall Dispatch System architecture has been expanded to take advantage of spatially -enabled database functionality available within Microsoft SQL Server and Oracle. The HxGN OnCall Dispatch System now supports storing polygons using the Geography data type for SQL Server and for Oracle, ST_Geometry (a data type that is interoperable with the SDO_Geometry data type). Deployment areas, special situations, and special addresses are now stored as uniquely attributed polygons in the database. For example, a four-story building with each floor having a unique response could be represented by four coincident polygons, each with a keyword and the overriding agency Statement of Work HEXAGON City of Miami OnCall Dispatch/Mobile Implementation response and additional messages. Special addresses have historically been part of the location verification system and used as rooftop locations. Now, Hexagon leaves address validation to the Geocoding services, and polygonal special addresses are used to augment the user workflows with messages or deployment overrides. Azure Maps is a collection of geospatial services that use fresh mapping data to provide accurate geographic context to web and mobile applications. The Cloud Dispatch Program is currently using the Routing, Map Rendering and GeoCoding services. Additionally, Azure Maps provides the features below: REST APIs for rendering maps in multiple styles and in satellite imagery. Searches for addresses, places, and points of interest around the world. Routing point-to-point, multipoint, multipoint optimization, isochrone, commercial vehicle, traffic influenced, and matrix routing; viewing traffic flow and incidents. • Mobility services for requesting public transit and alternative modes of transportation (like bike share, scooter share, and car share), and planning routes in real time. • Establishing user location through geolocation, and converting location to time zones. • Services for geofencing and map data storage, with location information hosted in Azure. Location intelligence through geospatial analytics. Azure Map Services leveraged by HxGN Dispatch Cloud Application currently leverages the following Azure services. Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Render Service The service uses either high -quality raster graphic images, available in 19 zoom levels, or fully customizable vector format map images. 0 - d x u Mao X P 0 r+Pps Baalanarb 71__ i � L w Route Service The Route service contains robust geometry calculations for real -world infrastructure and directions for multiple transportation modes. The service allows for developers to calculate directions across several Statement of Work 106 HEXAGON City of Miami OnCall Dispatch/Mobile Implementation travel modes such as car, truck, bicycle, or walking. The service can also consider inputs such as traffic conditions, weight restrictions, or hazardous material transport. v GeoCoding Service Redmond zaz If Bellevue 5ammamish U w� Microsoft When you search for a location with Azure Maps, the search service takes your search terms and returns the latitude and longitude coordinates, a process called geocoding. Address points - Addresses data can be resolved to a latitude/longitude coordinate within the address parcel (property boundary). Sometimes referred to as 'Rooftop' accurate. This is the highest level of accuracy available for addresses. House numbers - Addresses are interpolated to a latitude/longitude coordinate on the street. Street level - Addresses are resolved to the latitude/longitude coordinate of the street that contains the address. The house number may not be processed. City level - City place names are supported. High Availability High availability can be defined as a system that remains continually operational. These systems eliminate the threat of a single point of failure. Azure Map Service is a Platform as a Service (PaaS) offering from Microsoft Azure. The Azure platform is responsible for availability via the use of Regions, Availability Zones and performance thresholds. Because it is offered as a PaaS, Microsoft publishes the Service Level Agreements (SLA) associated with the Service. The SLA for Azure Maps can be found here: https://azure.microsoft.com/en-us/support/legal/sla/azure-maps/vl 0/ Statement of Work � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment L — REMOVED Statement of Work 108 � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment M — Cloud Service Schedules [following this page] Statement of Work 109 CLOUD SERVICES SCHEDULE PRODUCT: HCL2311— HxGN OnCall Analytics — Author — Cloud CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL2312— HxGN OnCall Analytics — Dispatch Models - Cloud CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/Geo-replication SERVICE LEVEL: Azure/Availability Zones, 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL2310— HxGN OnCall Analytics — Viewer - Cloud CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1133 — HxGN OnCall Dispatch I Advanced Mapping CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1122 — HxGN OnCall Dispatch I Advantage CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07:00 — 19:00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1235 — HxGN OnCall Dispatch I ALPR Interface CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07:00 — 19:00 CT US. SPECIAL NOTE: This Cloud Services Schedule is for a pre-release part and is subject to change once the part is released. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1206 — HxGN OnCall Dispatch I CAD Link Interface CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07:00 — 19:00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1167 — HxGN OnCall Dispatch I Call -Taker CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1227 — HxGN OnCall Dispatch I Call -Taker Interface CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1203 — HxGN OnCall Dispatch I Deccan LiveMUM Interface CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1155 — HxGN OnCall Dispatch I Essentials CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1197 — HxGN OnCall Dispatch I Fire Station Alerting CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1196 — HxGN OnCall Dispatch I Informer CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1202 — HxGN OnCall Dispatch I Mobile Unit CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL3209 — HxGN OnCall Dispatch I Mobile Responder CLOUD PLATFORM PROVIDER: AWS REDUNDANCY: AWS/Availability Zones SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1195 — HxGN OnCall Dispatch I RestAPI CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1186 — HxGN OnCall Dispatch I Tracker CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1234 — HxGN OnCall Dispatch I Video Responder Advantage CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. SPECIAL NOTE: This Cloud Services Schedule is for a pre-release part and is subject to change once the part is released. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1193 — HxGN OnCall Dispatch I Video Responder Essentials CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. SPECIAL NOTE: This Cloud Services Schedule is for a pre-release part and is subject to change once the part is released. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL1166 — HxGN OnCall Dispatch I Viewer CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/SQL Active Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) CLOUD SERVICES SCHEDULE PRODUCT: HCL3213— HxGN Integration Engine (Azure cloud) CLOUD PLATFORM PROVIDER: Azure REDUNDANCY: Azure/Geo-replication SERVICE LEVEL: 99.5% Availability SERVICE CREDIT: 10% of the monthly fee for this Cloud Application CLOUD SERVICES SUPPORT AVAILABILITY HOURS: For Level One Error (P1) telephone support is available 24x7x365; for all other errors telephone support is available between 07.00 — 19.00 CT US. Cloud Capacity Limitations The Azure environment sized for the Customer includes four (4) environments and shared components across all of the Customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 3 Linux nodes Message Bus — 3 Linux nodes 2 core • 1 VPN Gateways • 1 application Gateway 10 Units • Azure Front Door - monthly .5 TB inbound 30 Routing rules Interface Platform • Azure Map 100K tile 100K imagery 100K Routing transactions - monthly Dev/Stage/Training Environments —These are separate environments that include in total: 3 Standard sku databases with 100 GB 12 Windows nodes 4 core 9 Linux nodes 4 core Production (1) — includes: 2 P2 sku databases with 250 DTU per hour 500 GB storage read -access geo-redundant storage (RA-GRS) 12 Windows nodes 4 core 8 Linux nodes mix of 4 core and 2 core • 150 GB egress data (monthly) • 75 GB intra-regional (monthly) � A HEXAGON City of Miami OnCall Dispatch/Mobile Implementation Attachment N — Deccan LiveMUM SOW [following this page] Statement of Work 110 a r DECCAN INTERNATIONAL Decision -support software solutions for Fire & EMS City of Miami Fire -Rescue Department LiveMUM Statement of Work July 20, 2020 Disclaimer The information in this document is subject to change without notice. This document is provided under license in connection with an update version of the software named on the front page hereof. The software version to which this document relates is subject to the License and other terms and conditions of the contract under which the software was originally provided. This document is part of the Deccan documentation referred to in that contract and is likewise subject to the terms and conditions thereof, including, without limitation, the License and Confidentiality terms. THIS DOCUMENT AND THE SOFTWARE VERSION PROVIDED HEREWITH, IS PROVIDED AS IS, WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. Software Errors (as that term is defined and used in said contract) encountered in said software will be corrected pursuant to the terms and conditions of the Software Support Agreement currently in force with respect to said software and your sole remedy with respect to this software update version and this document is to receive the software support services provided under said Software Support Agreement. Companies, names, and/or data used in screens and sample output are fictitious unless otherwise noted. Copyright © 1996 — 2020 Deccan InternationalTM. All rights reserved. All information in this document is proprietary and confidential and owned by Deccan InternationalTM. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Deccan InternationalTM Deccan Internationallm 9444 Waples Street Suite 300 San Diego, CA 92121 PHONE: 858.764.8400 FAX: 858.764.8401 Deccan International I LiveMUM Statement of Work Change History Version Date Modified Published By Notes 1.0 7/20/2020 Tracy Gonzales — Deccan International 1. All information in this document is proprietary and confidential and owned by Deccan InternationalTM. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Deccan InternationalTM Deccan International I LiveMUM Statement of Work Table of Contents 1. Purpose of Statement of Work.............................................................................................................6 1.1 General Client Responsibilities.....................................................................................................6 1.2 Project Exclusions.........................................................................................................................6 2. LiveMUM Application...........................................................................................................................7 2.1 General Specifications...................................................................................................................7 2.2 Software Specifications.................................................................................................................7 2.3 Current Coverage (Area Coverage) Specifications........................................................................8 2.4 Recommendation (Redeployment Analysis) Specifications..........................................................9 3. Project Implementation......................................................................................................................10 3.1 The Client's Points of Contact.....................................................................................................10 3.2 Web Meetings.............................................................................................................................10 3.3 Project Phases.............................................................................................................................10 3.3.1 Phase I —Collection of Incident Data and Map Data..........................................................11 3.3.2 Phase 11— Building of LiveMUM Static Scenario Evaluator.................................................11 3.3.3 Phase III — CAD Testing & Acceptance................................................................................12 3.4 Services offered as a part of Maintenance and Support............................................................13 3.4.1 Bi-Annual Data Refreshes of LiveMUM...............................................................................13 3.4.2 Technical Support...............................................................................................................13 3.4.3 Application Enhancements.................................................................................................13 3.5 Services offered requiring additional cost..................................................................................13 3.5.1 Changing CAD......................................................................................................................13 3.5.2 New Product and Feature Releases....................................................................................13 3.6 Project Services...........................................................................................................................14 3.6.1 Project Manager..................................................................................................................14 3.6.2 Training Services.................................................................................................................14 3.7 Installation..................................................................................................................................14 4. Appendix.............................................................................................................................................14 4.1 APPENDIX A— CAD data needed by Deccan...............................................................................14 4.2 APPENDIX B — Map data needed by Client.................................................................................16 4.3 APPENDIX C — Providing the data to Deccan..............................................................................17 Deccan International I LiveMUM Statement of Work 4.4 APPENDIX D — LiveMUM Acceptance Test Plan..........................................................................18 4.5 APPENDIX E — LiveMUM Task Schedule...................................................................................... 20 4.6 APPENDIX F — Hardware and Software Requirements............................................................... 21 Deccan International I LiveMUM Statement of Work 1. Purpose of Statement of Work This statement of work has been created to define the work to be performed by Deccan International ("Deccan") for City of Miami Fire -Rescue Department (herein after referred to as the "Client") to build Deccan International's LiveMUM application. When mutually executed for implementation, this SOW becomes contractually binding on Deccan and the Client. 1.1 General Client Responsibilities In addition to those Client responsibilities stated elsewhere in this SOW, the Client is responsible for: a) Network/communications connections (e.g., Online Meeting, telephone, VPN, and other voice/data connections), or ongoing network/communications associated with installation, operation or support of the proposed system including the establishment and maintenance. b) Unless specified as a defined service to be delivered by Deccan International, the installation, configuration, maintenance (including patch management and upgrades of Microsoft software required by the System) shall be completed by the Client. c) Unless specified as a defined service to be delivered by Deccan International, the configuration of machine names and IP addresses for servers to be utilized by the System shall be completed by the Client. d) The provision of code files and GIS data as requested by Deccan International staff. This information must be provided on a timely basis in order to meet the project timelines. This information will be provided in the format specified in Appendix A and Appendix B e) The timely review and approval of the Acceptance Test Procedures (ATP), and other project documentation as further defined in this SOW. f) Active timely reviews of code file data and GIS data. g) Making the appropriate personnel available for scheduled training sessions h) Providing a training facility with the required computer and audio-visual equipment for training. 1.2 Project Exclusions Work, software, services, hardware, Systems, Subsystems, product/software modifications or any other deliverables not described in this SOW or the Agreement will not be included in the Project. Changes in scope will only be executed through a mutually agreed upon Change Management Process, as described in the Project Management Plan. The Agreement will be the governing document, and any deliverables that are not explicitly stated in the Agreement shall not be delivered in the Project. Deccan International I LiveMUM Statement of Work 2. LiveMUM Application Live Move -Up Module (LiveMUM) is a software tool that interfaces with a live CAD system to display to Communication Center dispatchers current coverage and offer move -up recommendations based on various criteria (business rules and/or operational procedures) set by the Communication Center. LiveMUM does the following: • Takes the guesswork out of move -ups. • Eliminates dependence on pre -plans, which are of limited use. • Allow dispatchers to test out and evaluate the effectiveness of planned move -ups. • Equips dispatchers with move -up rationale to show field units why a move -up is necessary. • Ensures a consistency of move -up quality across all the dispatchers. 2.1 General Specifications 1. LiveMUM analyzes CAD data and displays color -coded maps for specified unit types, which illustrate coverage, thus allowing dispatchers to view weaknesses and strengths in coverage. 2. LiveMUM makes tactical redeployment (move -up) recommendations based on criteria set by the Communication Center. 3. Communications center staff may test the effectiveness of their own move -ups, taking into account information not available to the LiveMUM. 4. LiveMUM incorporates an extensive list of business rules and/or operational procedures and strategies that dispatchers utilize when dispatching and redeploying units. 5. A user may make alternate recommendations beyond LiveMUM's standard recommendations. LiveMUM features the ability to calculate coverage scores and what the impact may be by using the user's recommendation. 2.2 Software Specifications 1. LiveMUM is user friendly and incorporates a visually appealing employing Graphic User Interface (GUI) operating in a Windows environment. 2. Once installed, Communication Center staff may use LiveMUM to perform area coverage & redeployment analysis in a convenient fashion without the assistance of analysts or other external personnel. Please see sections below for details on area coverage and redeployment analysis. 3. User inputs and actions are intuitive and utilize a pointing device, pull -down menus and standardized tables. Deccan International I LiveMUM Statement of Work 4. The primary display is the Client's map with the Client's response areas displayed. The display supports zoom features for selected response areas and/or grids. 5. LiveMUM permits the storage and retrieval of logs on disk for later analysis. 6. LiveMUM allows the application to be run in three settings: Live, Static, and Replay. 7. Live setting allows for move -up recommendations to be determined using real-time data from the CAD system and customized by client's business rules. 8. Static setting allows the Client to create scenarios and specific move -up recommendations for testing purposes. Feedback from this testing will be provided to Deccan to incorporate business rules. 9. Replay setting allows client to replay past log files to review move -up recommendations or, in limited cases, configure LiveMUM for future scenarios. This tool is useful to determine performance during extreme settings such as multi -alarm fires. 10. LiveMUM allows multiple map layers to be included such as water layers, major roads or highways, hospitals, and major landmarks. These layers may help make the visual map easier to navigate for end users. 11. LiveMUM features the ability to analyze historical call volume to predict when move -ups may not be required due to low call volume. This tool helps minimize unnecessary move -ups in addition to the regular business rules configured by the user. 12. Calculations are made based on all capabilities so as to not relocate units in a manner that negatively impacts one capability while positively impacting another. Also, this helps minimize the number of move -ups and maximize the effectiveness of move -ups. 13. LiveMUM supports AVL for real-time data tracking. Units may be posted to their current real- time location based on X/Y coordinates and not solely on unit status messages received from the CAD system. 2.3 Current Coverage (Area Coverage) Specifications Current coverage is displayed in the form of Current Coverage window. This window includes a tab for each capability whose current coverage is to be displayed. This window's specifications are listed below: 1. Coverage is displayed as color -coded response zones based on Client specified criteria. 2. Unit availability is displayed using color -coded stations. 3. Zooming in and out is supported in the coverage map display. Deccan International I LiveMUM Statement of Work 4. The user is allowed to click and see which units are present in a station. Unit attributes displayed are listed below: a. ID b. Status c. Estimated Time Back in service (ETB) d. Last Status Date -Time. 5. The user may switch on and off the map's station labels. 6. The Coverage Score and Unit Availability can be displayed above the map as percentages. 7. A list of units and their ETBs are displayed in their corresponding tabs (based on capability). ETBs can be calculated based on historical data or Client preference. 8. CAD messages and some Coverage Window User Actions are logged for analysis. 2.4 Recommendation (Redeployment Analysis) Specifications 1. The concept of station depth is used to calculate minimum coverage levels. 2. Units with multiple capabilities are supported. 3. Cross -staffed units are supported. 4. The Move -Up methods of nearest neighbor, leapfrog, & bump and cover are all supported and may be used individually by capability modeled. 5. Unmovable units are supported. 6. Preferred move -up stations are supported. 7. Preferred move -up units are supported. 8. Minimum score increase is supported to eliminate ineffective move -ups or maximize the score impact of move -ups. For example, a move -up may only be triggered if it increases the coverage score by 10% or more. 9. Coverage Drop thresholds are used to ensure that moved -up -from areas do not worsen too much. 10. LiveMUM may be configured to automatically recommend units back to their home station once coverage is increased in the area they were moved to. 11. Specific event types can be configured to prompt move -up recommendations. 12. A user -defined constraint on the move -up travel time may be implemented. Deccan International I LiveMUM Statement of Work 13. The user is alerted to move -up recommendations with a pop up window, task bar alert, and/or a custom sound. 14. When a recommendation is generated, the following are displayed and enabled: a. Maps displaying the coverage before and after the evaluated move -up are shown. b. The recommendation is displayed in a grid for easy view. c. The user can check or uncheck a recommendation and see the effects. d. The user can append recommendations and see the effects. 15. All recommendations are logged. Some user activities in the Recommendation windows are also logged. Client may combine recommendation log files to review daily, weekly, or monthly recommendations to determine problematic areas for coverage or which units are most useful for recommendations. 3. Project Implementation 3.1 The Client's Points of Contact Successful implementation of the LiveMUM application needs active participation and collaborative effort between the Client and Deccan. The support needed is primarily in the form of ability to ensure that the data is provided to Deccan in a timely fashion. As such, Deccan expects the Client to assign a primary point of contact familiar with the dispatch and move -up operations to partner with Deccan International in building applications. Since move -ups impact field operations, a field person experienced with move - ups should be assigned to participate in discussions. Please see the document titled "Deccan Project Resources Worksheet" for additional details. 3.2 Web Meetings Throughout the install process, the Client needs to have periodic meetings with Deccan International, which will occur remotely, via an online meeting tool such as Join.Me. These meetings will be scheduled with the Client as and when they are needed. For this purpose the Client is expected to provide a computer connected to Internet, a speakerphone, and a projector that can project the computer screen for convenient viewing by multiple people. 3.3 Project Phases The application will be built and delivered in three phases. The application requires of Client's relevant business rules to be provided in a tabular format. Each phase involves dialog and feedback between Deccan and the Client to ensure that the business rules built into LiveMUM meet the Client's needs. Project phases are employed to ensure accuracy for the application. Each of these phases, in the order of occurrence, is outlined below with associated tasks and responsibilities. Deccan International I LiveMUM Statement of Work During this phase Deccan International will work closely with the Client to retrieve the necessary data from its CAD system that is required to build the application. Deccan International will also work with the Client to obtain the necessary GIS data such as streets, stations and polygon layers. The Tasks in Phase I are as follows: Deccan International's Responsibilities: 1. Project Kickoff. An initial meeting summarizing expected timelines and data requirements will be held between Deccan Project Manager and client. Client's Responsibilities: 1. Identify and assign one key contact as project manager for the agency and a single point of contact for GIS and CAD data. This may be the same individual. 2. Retrieve raw Incident, Activity and CAD data from CAD System in specified format (Appendix A). Place CAD Data on Deccan FTP site. 3. Retrieve and upload raw map data from client in specified format (Appendix B). 4. Retrieve all necessary unit information and initial business rules for agency's move -up policies. 3.3.2 Phase II — Building of LiveMUM Static Scenario Evaluator Deccan International's Responsibilities: 1. Convert data into the standard format used by Deccan International. 2. Import data into mapping software for use with LiveMUM. 3. Build ETB (Estimated Time Back) table, defaulted station depths, station and unit information, and other client specific data into the application. 4. Work with Client to gain an understanding of current move -up procedures and strategies. These are known as "Business Rules" throughout this document. 5. Build "Depth" tables, one for each capability to be modeled in the application that reflects agency's tradeoff between coverage and doing too many move -ups. If possible, these will be built through business rules. 6. Build "Coverage Drop Thresholds" tables, which reflect the agency's tolerance for coverage worsening in moved -from areas. 7. Setup initial Business Rules if provided by client. 8. Deliver LiveMUM SSE to client via Deccan FTP site. 9. Provide client with download and installation instructions for LiveMUM SSE. Deccan International I LiveMUM Statement of Work 10. Provide client with training of Static/Offline LiveMUM application via the online meeting tool JoinMe. Client's Responsibilities: 1. Download and installation of LiveMUM SSE. 2. Schedule time to be trained about application's functionality and test configurations. 3. Provide feedback to Deccan based off initial off line testing for future changes. 3.3.3 Phase III -CAD Testing & Acceptance During the third phase Deccan International will setup and test LiveMUM. Deccan International and the Client will schedule regular feedback sessions that will be used to define and tune the coverage and business rules. The following work will be performed: Deccan International's Responsibilities: 1. Make configuration changes as required after feedback provided by client. Client will provide feedback after testing LiveMUM in Test/Production CAD environment. 2. Assist client with testing the CAD/LiveMUM interface by analyzing the initial Synchronization and Tracking logs received by the application. 3. Schedule formal acceptance testing 4. Perform acceptance with client or provide acceptance testing document for client to test application with individually. Client's Responsibilities: 1. Provide Deccan International with VPN connection to Test\Production CAD workstation if available. 2. Work independently, or with Deccan, to verify successful interfacing with CAD system in test and/or production environment. 3. Verify configuration of business rules is acceptable and closely matches requirements outlined by client. 4. Perform acceptance testing with Deccan Project Manager or independently and provide signed Acceptance Test Plan to Deccan PM. Deccan International I LiveMUM Statement of Work 3.4 Services offered as a part of Maintenance and Support 3.4.1 Bi-Annual Data Refreshes of LiveMUM LiveMUM uses CAD data from actual events to analyze past coverage holes and call volume to best recommend move -ups. As such, the currency of the application is dependent on the currency of the CAD data on which it is based. To keep the application current, it will have to be regularly updated with CAD data built up since the last update. This task involves, among others, updating ETBs, identifying new units, stations, incident types, and unit types in the new CAD data and updating LiveMUM Code Tables and business rules to reflect them. As part of Maintenance and Support, these tasks will be performed bi-annually by Deccan International. In between updates, it is possible for the Client to add units; Deccan does not currently support a convenient utility for this task, but will assist the Client in adding units at any time. If the Client prefers to add units directly to a Units table themselves, Deccan International will train the Client on this task. Since directly adding units to tables is not a foolproof task, the Client will have to do this with care. 3.4.2 Technical Support As part of Maintenance and Support, Deccan will provide technical support via phone and email during normal business hours 0900 to 1700 Pacific Time Monday through Friday with the exception of Deccan - observed holidays. Deccan -observed holidays include New Year's Day, Martin Luther King Jr. Day, President's Day, Memorial Day, Independence Day (July 4th), Labor Day, Thanksgiving Day, the Day after Thanksgiving, Christmas Eve Day, and Christmas Day. 3.4.3 Application Enhancements As a part of the goal to ensure that the application continues to meet client needs, Deccan adds features to the application on a continual basis. As part of Maintenance and Support, Deccan would offer these enhancement features during the maintenance cycle. However, any additional modules that are not part of these enhancement features would be available to the department for an additional cost. 3.5 Services offered requiring additional cost Occasionally, the Client might require additional tasks in addition to those included within the scope of this Project. Substantial updates or upgrades that require engineering or development work, include additional features/functionality not originally purchased, or require major configuration changes in between/in addition to biannual maintenance updates, will require additional cost. 3.5.1 Changing CAD LiveMUM interfaces with CAD. If the Client changes its CAD at any point during the build process or during maintenance, then Deccan will have to rewrite the interface at additional cost to the Client. 3.5.2 New Product and Feature Releases Deccan continues to develop new products and features to its' existing applications and release them to its' client base and the market at large. When a new product or feature has been commercially released, it will be offered to the Client for purchase. Deccan International I LiveMUM Statement of Work 3.6 Project Services 3.6.1 Project Manager Deccan will appoint a project manager to coordinate all project -associated tasks with the Client's assigned project manager. Through periodic meetings, Deccan will create the project plan and project schedule, review the project and its progress, and review the current task list and upcoming milestones. 3.6.2 Training Services Training courses for LiveMUM will be completed after the installation of the application. This course is required as a part of the installation process. Training will be conducted onsite by Deccan staff. Deccan will conduct a one -day training session (up to 8 hours) with a maximum of 18 attendees. Subsequently, all of Deccan's training is currently conducted remotely using via a web conferencing service like Join.Me. 3.7 Installation Deccan will install the LiveMUM application as outlined in the Statement of Work only. The installation program will be made available to the Client via FTP and/or shipped via CD/DVD. Deccan is not responsible for installing or configuring any hardware or other third party software components not outlined in this document. 4. Appendix 4.1 APPENDIX A - CAD data needed by Deccan To build and update LiveMUM, Deccan needs certain data from the Client's CAD. 1. Incident Data a. Deccan needs incident data for the past 2 years. The incident data contains incident - specific information especially: i. Incident Number ii. Incident Type iii. Incident Location iv. Incident Date -Time 2. Unit Activity Data a. The Unit Activity data contains Unit Activity related data especially: i. Incident Number Deccan International I LiveMUM Statement of Work ii. Unit Status (e.g. Responding) iii. Date -Time Stamp iv. Vehicle ID v. Unit Name vi. Unit's Current Station The Client should provide incident and Unit Activity data for the past 2 years. The Incident and Activity data should be provided as it appears in the Client's CAD without filtering of any fields in delimited ASCII text, DBF or Access (.mdb) format. Excel format cannot be used because of its size limitations and tendency to convert text fields to dates. Field descriptions for the data should also be provided. 3. Other CAD data a. In addition to the CAD incident and response data specified above, the Client must provide Deccan with the data in the code tables in Client's CAD or any documents describing the following: i. All Unit Statuses and their corresponding descriptions (e.g. DISP = Dispatched, RESP = Responding, OS = On Scene etc.) specifically: 1. ID 2. Code 3. Description b. All CAD Incident Types codes and their corresponding descriptions (e.g. FIB = Fire in Building, FIV = Fire in Vehicle, BRSH = Brush Fire etc.) specifically: i. ID ii. Code iii. Description c. All Station information, specifically: i. Station ID ii. Station Code iii. Station Name d. Vehicle Information: i. ID ii. Name iii. Type (Engine, Ladder, Truck, Brush Rig, Chief, Tender, ALS, etc.) iv. Associated Unit Deccan International I LiveMUM Statement of Work e. Vehicle Types i. Code ii. Description f. Unit Information i. ID ii. Code iii. Radio Name (If applicable) iv. Description v. Capability vi. Home Station 4.2 APPENDIX B - Map data needed by Client The Client must provide any available map layers to be used in LiveMUM. The maps can be provided in ESRI shape file format or ESRI Arclnfo export format or Mapinfo tab file format. Deccan also needs the projection system on which the maps are based. The following is a list of Map layers which can be used in LiveMUM: 1. Streets a. This is the most significant map layer that is needed for this implementation, since LiveMUM uses the streets file to perform routing. The following data must be provided for each street line: i. Street name ii. Co-ordinates of starting and ending nodes iii. From and to address ranges for the left and right sides of the segment iv. Alias street name, if any v. One-way info vi. Speed limit vii. F-level and Z-level, if any The Client must ensure that the street network provided has good connectivity and very close to the actual street network in the Client's service area. 2. Jurisdiction Boundary a. The polygon layer that defines the jurisdiction boundary or the service area boundary. 3. Fire Dispatch Grids a. This polygon layer is used to build LiveMUM response zones. Deccan International I LiveMUM Statement of Work 4. Fire Stations A map layer corresponding to the current fire station locations in the Client's jurisdictions and any mutual aid station locations that need to be modeled in LiveMUM 9 t A RIF -1 The Client can send the data to Deccan in two ways — via FTP or via mail. Deccan prefers data to be sent via FTP because it is more secure and able to handle larger amounts of data. Via FTP: (Preferred) The data can be uploaded to Deccan's FTP site. The Client will be provided with access to a secure FTP site upon project kick off. Deccan International I LiveMUM Statement of Work 4.4 APPENDIX D - LiveMUM Acceptance Test Plan Introduction This document will describe the test plans to ensure proper install and functionality of LiveMUM. The test plans would be performed on the LiveMUM installed on the Client workstations. The workstations used for this test purposes can be either test or production systems. Test Case 1- LiveMUM launches successfully On the workstation, double click on either the LiveMUM shortcut available on desktop or by clicking on MUM.exe available in LiveMUM install folder. LiveMUM launches successfully without errors Test Case 3 - Zone and station legends Yes No Launch LiveMUM. Create a Structure Fire incident or high emergency incident in CAD and dispatch units. LiveMUM should display the correct coverage on the maps as shown in the zone legend. The more units you dispatch, the more variation of colors you would see in the coverage. LiveMUM updates coverage as necessary. Yes No Also, you will notice that stations are changing colors according to the station legend shown. LiveMUM updates the station colors as shown in station legend Yes No Test Case 4 - Move -Up Recommendations Launch LiveMUM. Create a structure Fire incident or high emergency incident in CAD and dispatch units. Dispatch units till you see holes in coverage in LiveMUM (red regions). Depending on the Client's configuration, either the recommendation pop-up should appear or recommendation button should turn red for all capabilities with coverage holes, when applicable. Is a recommendation made for each capability as needed? Yes No Deccan International I LiveMUM Statement of Work Test Case 5 - Recommendation window Launch LiveMUM. Create a structure Fire incident or high emergency incident in CAD and dispatch units. Dispatch units till you see holes in coverage in LiveMUM (red regions). Depending on the Client's configuration, either the recommendation pop-up should appear or recommendation button should turn red for all capabilities with coverage holes, when applicable. Click on each pop-up window or recommendation button to view the recommendation window. On each recommendation window: Does LiveMUM display the from coverage map and to coverage map? Yes No Does LiveMUM display the recommendation(s)? Yes No Test Case 6 - Alternate recommendations Launch LiveMUM. Create a structure Fire incident or high emergency incident in CAD and dispatch units. Dispatch units till you see holes in coverage in LiveMUM (red regions). Depending on the Client's configuration, either the recommendation pop-up should appear or recommendation button should turn red for all capabilities with coverage holes, when applicable. Click on each pop-up window or recommendation button to view the recommendation window. On the alternate recommendations, select a unit and station of your choice and click "Evaluate". LiveMUM updates the to coverage map (right map) taking into account the alternate recommendations selected for evaluation? Yes No Deccan International I LiveMUM Statement of Work 4.5 APPENDIX E - LiveMUM Task Schedule NOTE: These task durations are dependent upon availability of Client resources, and are only provided as a general reference. The actual project duration may vary significantly, based upon project constraints, timelines, client availability, CAD Vendor support, and other factors. Task / Phase Estimated Estimated I Estimated Work Days Work Days Work Days for each for Each from Phase Sub -task Task Start date 1 1 1) Project Initialization — Phase 1 (3.3.1) 1. Project Kick -Off (1) Getting CAD/MAP data — Phase 1 (3.3.1) Data Requirements Provided to Client (1) 1 2) 17 18 1 Data Upload to Deccan International (2) 14 Data Analysis (3,4) 2 3) Building of LiveMUM SSE — Phase 2 (3.3.2) 24 42 Data Conversion (1) 5 Building of ETB Tables and CAD Data (2, 3) 3 Business Rule Discussions (4) 3 Building of Station Depths and Unit Files (5) 3 Implementation of Business Rules (7) 8 Delivery of LiveMUM SSE (9) 1 Installation and Training of LiveMUM SSE (9, 10) 1 4) CAD Testing & Acceptance — Phase 3 (3.3.3) Configuration Changes to Business Rules (1) 18 60 4 CAD Interface Set -Up by CAD Vendor (2) 10 Initial Synchronization and Tracking Testing (2) 1 Feedback Provided from Initial Testing (1,2) 2 cceptance Testine (4) 1 Deccan International I LiveMUM Statement of Work 4.6 APPENDIX F - Hardware and Software Requirements LiveMUM is a web -based application and does not require any complex hardware/software installations prior to LiveMUM install. Given below are recommended specifications for LiveMUM and LiveMUM Engine to operate. LiveMUM Server/Engine Environment Hardware Requirements Specification Minimum Optimal Processor Dual Core 2.4 GHz (or better) Quad Core 3.0 and above Memory 12 GB RAM 32 GB Ram 75 GB (50 GB working space free 120 GB (50 GB working space Disk Operating System 7200 RPM) Windows Server 2012 or 2016 with access to the internet free 7200 RPM) Windows Server 2012 or 2016 I with access to the internet Specification Microsoft OLE DB driver Microsoft .NET Framework Microsoft Visual C++ Internet Browser Software Requirements Minimum Visual FoxPro* v4.7.2 2012 Redistributable (x86)** Mozilla Firefox/Google Chrome LiveMUM Client Hardware Requirements Specification Minimum Optimal Processor Memory 2 GHz 4 GB RAM 2 GHz 8 GB Ram Operating System Windows XP (32-bit) Windows 10 (64-bit) Software Requirements Specification Minimum Internet Browser Mozilla Firefox/Google Chrome Deccan International I LiveMUM Statement of Work Notes The primary LiveMUM Engine, data set, and LiveMUM Server should reside in the same environment. The Internet Information Services (a standard component of Microsoft Windows Operating Systems) will need to be accessed and enabled. The amount of processing power and available memory required to run LiveMUM Server is dependent in part on the total volume of message traffic that is transmitted across the interface (<1,000,000/day is ideal) and the user - defined amount of logging files created. The LiveMUM Server should not be installed on a Laptop unless the Laptop will be physically connected to the network during operation hours. This is due to the unreliability of wireless connections for a roaming device (machine). LiveMUM Server can be configured to run as service with the use of FireDaemon*, if requested, except for TriTech (CentralSquare) CAD Systems. *can be provided by Deccan **will be replaced with a future version prior to end of life in 2023 Deccan International I LiveMUM Statement of Work ACCESSING COMPETED CO-OP and GOVERNMENTAL CONTRACTS CHECK LIST CONTRACT NO.: RFP 180081 LKD PROCUREMENT CONTRACTING OFFICER: Richard McLaren DATE SUBMITTED: 03-22-2022 TITLE: Computer Aided Dispatch Replacement and Associated Interfaces ("CAD") Accessing Co-ops and Governmental Contracts Package All Accessing of contacts must be reviewed and approved by the Department Director with signature below, Procurement Documents — to be included in Approval Package ❑ Award Summary Form for Director or City Manager (if applicable) X Agenda Item Summary Form (for Comrrlission Approval — if applicable) X Resolution(for Commission Approval— if applicable) X Copy of this checklist signed by the Director Co-op/Governmental Agency Documents — to be included in Approval Package a ❑✓ Copy of Tally/Evaluation Results (score sheets, ranking or summary) b ❑✓ Copy of Contract's Advertisement & Distribution information c ❑✓ Copy of Contract/Solicitation Being Accessed d ❑✓ Copy of Award Sheet/Approval Documents e❑✓ Copy of Proposal/Bid NOTES: VAPPROVED as a contract which was entered into pursuant to a competitive process in compliance with City laws, policies and procedures. ❑ NOT APPROVED as a contract which was entered into pursuant to a competitive process in compliance with City laws, policind procedures. nie artment of Procurement 10/8/14 Lee County RFP180081LKD 1. RFP — EVALUATION 1.1. Ranking Method: Lee County uses the Dense Ranking (1223" ranking). In Dense Ranking, items that compare equal, receive the same ranking number, and the next item(s) receive the immediately following ranking number. This ranking method is used for each individual committee member's scores. Thus if A ranks ahead of B and C (which compare equal) which are both ranked ahead of D, then A is ranked number 1("first"), B is ranked number 2 ("joint second"), C is also ranked number 2 ("joint second") and D is ranked number 3 ("third"). 1.1.1. Each Ranking is derived by the individual committee member's scores being totaled and then ranked with the highest "score" being "ranked" first with each following in the same manner. For example: a score of 100 would rank 1, a score of 75 would rank 2, and continue until all proposals have been ranked. 1.1.2. Upon completion of this method for each individual committee member the individual rankings are then totaled for an "Over-all Ranking." During the Over-all Ranking process the lowest total would be deemed the highest ranked (1). Example: Proposer A individual rankings totaled 5 and Proposer B individual rankings totaled 7 making "Over-all Ranking" order as Proposer A ranked 1, Proposer B ranked 2. 1.1.3. In the event of a tie, please refer to the tiebreaker section of this solicitation.) 1.2. Evaluation Meeting(s): 1.2.1. Evaluation 1: The first evaluation will rank Proposers based on the scores from the selection criteria point values. 1.2.2. Evaluation 2: Following the initial evaluation process, the short-listed proposer(s) will be required to provide an on -site interview/presentation. 1.2.2.1. Such subsequent evaluations will be accomplished by simply ranking the proposers. Proposers will be ranked in sequential order with one (1) being the highest ranking. Proposers' rankings will then be totaled with the total lowest scores receiving final rank order starting with one (1) - the highest ranking. LEE COUNTY SOLJT11WES-i F1,0RIDA Posted Date: 4/17/2018 Protest Deadline: 4/20/2018 Lee County Procurement Management Division 1500 Monroe Street 4th Floor Fort Myers, FL 33901 Main Line: (239) 533-8881 Fax Line: (239) 485-8383 www.leegov.com/procurement Notice of Intended Decision Proposal Action Proposal: RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) The Evaluation Committee for the above proposal project met April 10, 2018 for purposes of reviewing/ discussing all proposals/ presentations given by the short-listed firms. At the conclusion of the meeting. the Committee ranked the brobosals as follows: lst Intergraph Co d/b/a Hexagon Safety & Infrastructure 2nd Motorola Solutions Inc 3rd Su erion, LLC Recommendation will be made to the Lee County Commission that the County award to the following top ranked firm(s): 1st I Interarabh Cora d/b/a Hexaizon Safetv & Infrastructure :• Mary G. cker, CPPb ProcureInt Management Director Note: All submitters are furnished this notice. A submitter who has cause to file a Notice of Intent to File a Protest against the award must do so in writing to the Procurement Management Director no later than 4:00 p.m. local time on the third working day (Monday -Friday, excluding legal holidays) following the date of this notice. It must clearly state that it is a protest and must include specific information required by the County Government's current directive. Failure to protest on a timely basis, or to include the required information, will invalidate the protest. WWW.LeeGov.Com/Procurement is the County's official posting site NOIDPA ver 05/01/2016 Computer Aided Dispatch Replacement & Associated RFP Name Interfaces (CAD) Buyer Ext 38858 Lori DeLoach Intergraph Corp d/b/a Hexagon Motorola Solutions Inc Safety & Infrastructure (Hexagon) R F P # krl'`t3G1,81.'_iis=� Ranking Meeting -Ranking Only Members Casey Allo (Chair) Paul Filla Brandon Scribner Rob Price Andrew Hunter Total Score Ranking verbal verification by evaluation Scores Verified by: committee 1 2 3 2 3 1 1 3 2 1 2 3 2 1 3 Date: i I col D Date: b � C 0� t m N �r, m m m m 0 o 0 r! Ln m 'to 0 00 x v '� N V tn N t• A� ro� (p of rv4 eM Ln to 'O u, N 7*- uy H N. N O.' In .00 rl N H -N H M PtI ' cn a V .y G1 00 ,00 00 0J » 5 '+l N L • x: 00, ..r n V1. hd t a a c v `o V x Computer Aided Dispatch Replacement & Associated RFP # RFP180081LKD RFP Name Interfaces (CAD) verbal verification by evaluation Scores Verified by: committee Date: .1 1 r r r~ McLaren, Richard From: Cepero, Lindsay <LCepero@leegov.com> Sent: Tuesday, March 26, 2019 7:12 AM To: McLaren, Richard Subject: RE: RFP180081 LKD Attachments: 180081 Eval 1 scores.pdf, 180081 eval 2 rank final.pdf, RFP180081 LKD - Document Holders List.docx; 180081 ann.pdf CAUTION: This is an email from an external source. Do not dick links or open attachments unless you recognize the sender and know the content is safe. Richard, Please see attached documents available. Solicitations from our office are run in the NewPress paper, posted to Demandstar and published to our Countywebsite. Should you need any additional information do not hesitate to ask. Thank you, Lindsay Cepero, CPPB Interim Procurement Manager Procurement Management Ph: 239-533-8859 Em: LCepero@LeeGov.com Cell: 239-271-0169 Fax: 239-485-8383 Address: 1500 Monroe Street 4th Floor Fort Myers, FL 33901 (This is the Lee County Public Works Building) Please ncte. Florida tlas a very broad public records law. Most written communications to or from County Employees and oniiaals regarding County business are public records available to the public and medic upon request. Your arnail communication may be subiert to public disctosure. Under Ronda faw. email addresses are pubiic records. If you do notwant -y our email address r elaosed in response to a public records request. do not send electronic mail to this entity. Instead, contact this o.5re by phcr.e or m writing,. From: McLaren, Richard <RMcLaren@miamigov.com> Sent: Monday, March 25, 2019 8:07 AM To: Cepero, Lindsay <LCepero@leegov.com> Subject: [EXTERNAL] RFP180081LI(D Good Morning Lindsay; I am in the process of piggybacking on this contract to procure the Hexagon Computer Aided Dispatch Replacement and Associated Interfaces (CAD). I am still need copies of a few documents to complete the package for my Director. Allana had obtained most of needed documents. Listed below is what I still need: 1. Copy of Tally/Evaluation Results (score sheets, ranking or summary), 2. Copy of Advertisement & Distribution information for this RFP, 1 LIST OF BIDDERS Solicitation Number: RFP180081 LKD Project Name: Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Opening Date/Time: 2/20/2018 2:30 PM Contact Flame: Sara Pinkus Company: Axon Enterprise, Inc Mailing Address: 17800 N. 85th Street Address (Cont.): City: Scottsdale State: Arizona Zipcode: 85255 Phone: 4805156376 Fax: 4805156376 Email: spinkus(a)axon.com Contact Name- Larry Burns Company: Commdex Consulting Mailing Address: 655 Engineering Drive Address (Cont.): Suite 100 City. Norcross State: Georgia Zipcode: 30029 Phone: 4239306649 Fax, 4239306649 Email: Iburns@commdex.com Contact Name: melanle samy Company: erepublic Mailing Address: 100 blue ravine road Address (Cont.): City: folsom State: ca Zipcode: 95630 Phone: 916-932-1300 Fax: 916-932-1470 Email: msamy@erepublic.com Contact Name. Jane Pearson Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Mailing Address: 305 Intergraph Way Address (Cont.): City: Madison State: Alabama Zipcode. 35758 Phone: 2567308157 Fax: 2567308157 Email- jane.pearson(ftexagonsi.com Contact Name. Garrett Mercer Company-. Mercer Technologies Firm Mailing Address: 1501 E.15th Ave #115 Address (Cont.): City: Gary State. IN Zipcode: 46402 Phone: 2198859811 Fax- 2198859811 Email: mercertechnologiesflrmagmail.com Contact Name. Sheila Jensen Company: Priority Dispatch Corp. Mailing Address., 110 Regent Street, Suite 500 Address (Coat.): City: Salt Lake City State: LIT Zipcode: 84111 Phone: 801.36.9127 e Fax: 801.363.9144 Email: sheila.jensen@ priorityclispatch.net Contact Name: Ward Mintzler Company- StrataGen Systems Mailing Address: 8271 154th Ave NE Address (Cont.): Suite 200 City- Redmond State, WA Zipcode, 98052 Phone- 604-214-7234 Fax- 604-241-1440 Email: ward. mintzler(&ddswireless.com Contact Name: Andy Dean Company: TriTech Software Systems Mailing Address: 9477 Waples Street Address (Cont.). Suite 100 City: San Diego State. CA Zipcode: 92121 Phone: 858-799-7000 Fax: 910-401-1837 Email: proposalsObtritech.com Contact Name: Clark McCall Company-. Motorola Solutions, Inc. Mailing Address: 3861 Blue Crest Ave Address (font.): City: EUSTIS State: Florida Zipcode: 32736 Phone- 3525895721 Fax: 8772084318 Emall- clark.mccallamotoi,olasolutions.com Contact Name: Steven Raucher Company: RapidDeploy USA Corp Mailing Address-, 488 Madison Avenue, c/o Grassi Address (Cont.): Floor 21 City: New York City State, NY Zipcode: 10022 Phone: 7026307753 Fax, none Email: sr@rapiddeploy.com Contact Name: Urnair Naushahl Company: ISR Transit Mailing Address: 7771 W Oakland park Blvd. Suite, 175 Address (Cont.): City: Sunrise State: Florida Zipcode- 33351 Phone: 8884666706 Fax: 5146351252 Email: umair.naushahi@isrtransit.com Contact Name- xivakuma Company: visual Mailing Address: ecnagar1st Address (Cont); city' cbo State: M Zipcnda: 12365 Phone: 3474001475 Fax- 3471801475 Email: techzone(&visualinfomedia.com Contact Name: Tim Flanigan Company. Routematch Mailing Address. 12O1VVPeachtree Street NW, Suite 33OO Address (Cont.)-, City, Atlanta State- Georgia 0poo6m 30309 Phone: 404.239.2120 Pau/ 404.898.1145 Contact Name: gerry gemais Company- EmergemsysSolutions Inc Mailing Address: 4OO]ean'LosgeBLVD,Suite 12O Address (Cont.): City- Quebec City State: Quebec Zipcade; G1K8VY1 Phone: 511-708-6337 Fax., 418'380'8910 Contact Name- RFP180081LKD - Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Company: CODECOM Mailing Address: 40 CARR 165 SUITE 208 Address (Cont.): City, GUAYNABO State: PUERTO RICO Zipcode: 00968 Phone, 7877936000 Fax, 7877936001 Email: ebarreto(cocodecom.com Contact Name: Scott Eller Company: Plante & Moran, PLLC Mailing Address: 27400 Northwestern Hwy Address (Cont.): City, Southfield State: mi Zipcode: 48034 Phone. 248-223-3447 Fax, 248-603-5618 Email: Scott. Eiler(o.)plantemora n.com Contact Name, Rishil Patel Company: Microsoft Mailing Address. 5426 Bay Center Drive Address (Cont.). Suite 700 City- Tampa State, FL Zipcode: 33609 Phone: 8136394031 Fax: 0 Email, rishpate(cbmicrosoft.com Contact Name, Barbara Meyer Company: Infor Public Sector, Inc. Mailing Address: 1410 N Westshore Blvd., #505 Address (Cont.)* City: Tampa State: Florida Zipcode: 33607 Phone. 813-+207-6972 Fax. 678-393-5395 Email: barbara.meyer(cbinfor.com Contact Name: Katherine Grigg Company, Superion Mailing Address: 1000 Business Center Drive Address (Cont.), City- Lake Mary State: FL Zipcode: 32746 Phone, 4073044010 Fax, 0000000000 Email: katherine.grigg(asuperion.com Contact Name. Jan Bastien Company* CSI Technology Group Mailing Address: 330 Mac Lane Address (Cont.), City: Keasbey State: NJ Zipcode: 08832 Phone: 732-346-0200 Fax, 732,46.0209 Email: ibastien@csitech.com Contact Name: Steve Walse Company: SevenOutsource Mailing Address, rfi)alerts(a)qmail,com Address (Cont.), 113 Barksdale Professional Center City: Newark State: DE Zipcode: 19711 Phone: 315-308-7852 Fax: 315-308-7852 Email: rfpalerts(@qmail.corn Contact Name: Alain Laflamme Company, Next Generation Spatial Solutions Inc. Mailing Address. 3535 Saint -Charles Blvd Address (Cont.): Suite 455 City: Kirkland State: Quebec Zipcode: H9H 5B9 Phone: 514-505-6444 Fax, 514-505-6161 Email- a.laflamme@nextqss-com Contact Name: Glenn Foster Company, TripSpark Technologies Mailing Address, 10, 2175-29th Street NE Address (Cont.): City: Calgary State: Alberta Zipcode- T1Y 7H8 Phone: 4037773760 Fax; 4037773769 Email: rfoCaRripsoark.com Contact Name: Steven Lewis Company: Avail Technologies, Inc. Mailing Address: 1960 Old Gatesburg Road Address (Cont.), Suite 200 City: State College State: PENNSYLVANIA Zipcode, 16803 Phone: 8142343394 Fax: 8142343393 Email: proposals(chavalltec.corn Contact Name: Ann Herold Company, CIIS GROUP LLC Mailing Address: 124 Marriott Drive Address (Cont.). City: Tallahassee State: FLORIDA Zipcode, 32301 Phone. 8509269800 Fax: 8509269800 Email- Ann(aciisgroui).com Contact Name: Kathleen Fant Company, Tyler Technologies Mailing Address: 840 W. Long Lake Address (Cont.): City, Troy State: Michigan Zipcode: 48098 Phone: 2482691000 Fax, 2482691000 Email, kathy.fant@tylertech.com Contact Name: Melissa Smith Company: SmartCOP Mailing Address. 9165 Roe St Address (Cont.): City: Pensacola State. FL Zipcode: 32514 Phone., 850-429-0082 Fax: 850-429-0522 Email: melissa.smith(&smartcop.com Contact. tiame: Richard Stellacci Company: MobileTec International Mailing Address: 14502 N Dale Mabry Hwy. Address (Cont.),. Suite 226 City,, Tampa State: FL Zipcode, 33618 Phone: 813-876-8333 Fax, 813-877-7589 Email: rstellacci(comobiletec.ne Contact Name: Andrew Kennedy Company, Mark43 Mailing Address: 28 East 28th Street Address (Cont.), 12th Floor City: New York State: NY Zipcode: 10016 Phone, 9178559806 Fax, 5555555555 Email: andrew.kennedy(cbmark43.com Contact Name: Lisa Harris Company, Hitech Systems, Inc. c1ba Pu(siam Mailing Address: 16030 Ventura Blvd., Suite 250 Address (Cont.)* City: Encino State: CA Zipcode, 91436 Phone: 310-691-8115 Fax, 310-282-9929 Email, lharrisawlsiam.com Contact. Name. Larry I Andersen Company, West Interactive Mailing Address, 1601 Dry Creek Drive Address (Cont.), City: Longmont State, COLORADO Zipcode: 80504 Phone, 7204946138 Fax: 7204946138 Email: landersenl(-Owest.com Contact Name: Luke Granlund Company, ProPhoenix Mailing Address. 502 Pleasant Valley Ave Address (Cont.), City, Moorestown State, NJ Zipcode: 08057 Phone: 8505970506 Fax* 6099535311 Email: lul(e.granlund@proi)hoenix.com Contact Name. David Blaquiere Company: Zetron Mailing Address: 1524 Palm Ave Address (Cont.): City: Jacksonville State: Fl Zjpcode- 32207 Phone: 904-874-9511 Fax. 904-874-9511 Email: dblaquiere(azetron.com Contact Name: Lisa Allyn Company- Cyrun Corporation Mailing Address: 5619 Scotts Valley Drive Address (Cont.): Suite 120 City: Scotts Valley State: CA Zipcode. 95066 Phone: 8314580949 Fax: 8314599406 Email- lailyn@cyrun.com Contact Name: Denise Russell Company: Franklin County Government (NY) Mailing Address: 355 W Main St, Ste 456 Address (Cont.): City: Malone State: NY Zipcode: 12953 Phone: 5184811695 Fax. 5184830141 Email: drussell(c.)co.franklin.ny.0 HEXAGON SAFETY &INFRASTRUCTURE PRINCIPLE CONTRACTING DOCUMENT This Principle Contracting Document together with the Master Terms referenced below constitutes a Master Agreement by and between Lee County, a political subdivision of the State of Florida ("Customer") and INTERGRAPH CORPORATION by and through its Hexagon Safety & Infrastructure division I and is binding upon the Parties on the Effective Date. 1. Those Master Agreement Terms and Conditions ("Master Terms") attached hereto are incorporated into this Principle Contracting Document as if fully set forth herein 2. All capitalized terms in this Principle Contracting Document shall have the same meaning as provided in the Master Terms except as may be otherwise defined herein. 3. Any notice to be given pursuant to Section 13 of the Master Terms shall be directed to each Party at the following address, which reflects the Customer's location, in accordance with the Master Terms. CUSTOMER: HEXAGON' Attn: Roger Des'ariais Attn: Safety & Infrastructure Legal Department County Manager 305 Intergraph Way PO Box 398 Madison, Alabama 35758 Fort Myers, Florida 33902 victor. vasile hexa onsi.com 239 533-2221 256 730-2000 rddesjariais@leegov.com Attn: Mary Tucker Director of Procurement Management PO Box 398 Fort Myers, Florida 33902 (239-533-8881 mtucker@ leegov.com Hexagon Principle Contracting Document S108302019PCD Page 1 4. In consideration of the mutual obligations assumed under this Principle Contracting Document, Customer and Hexagon agree to the terms and conditions set forth herein and represent that this Principle Contracting Document has been executed by each Party's duty authorized representative. The signatories represent that they have the authority to bind their respective organizations to this Principle Contracting Document. This Principle Contracting Document may be executed in counterparts or In duplicate originals. Each counterpart or each duplicate shall be deemed an original copy of this Principle Contracting Document signed by each Patty for all purposes. AGREED BY,- INT G APH CORK RATI By L,C Name nnifer Wilms Title: Director Date:enl�� ATTEST: CLERK OF THE CIRCUIT COURT Linda oggett, Clerk BY: ,I d 1NI 1 rt "^ By: Name Title: [date: LEE COUNTY BOARD OF COUNTY COMMISSIONERS OF LEE COUNTY, FLORI A BY: DATE: ( I — APPROVED AS TO FORM FOR THE Commissioner Cecil L Pendergrass RELIANCE OF LEE COUNTY ONLY: Lee County Board or: County Commissioners District 2 BY: O't o���t�llttlll##l11a OFFICE OF THE COUNTY ATTORNEY THE REMAINDER OF THIS PAGE IS LEFT BLANK' INTEI LY �= firjr !f#tllPititt����`��� Hexagon Prinalpla Contracting Document s I08so2o1 9PCID Pogo 2 � A HEXAGONI�Jrl� MASTER TERMS AND CONDITIONS These Master Terms and Conditions (the "Master Terms") govern transactions and relations between Customer and Intergraph Corporation through its Safety & Infrastructure division ("Hexagon") (each a "Party" and collectively the "Parties"). Hexagon will make available to Customer certain proprietary software, including related proprietary documentation, software maintenance services, Cloud Programs, and professional services, all of which will be provided to Customer pursuant to these Master Terms and an Order. Before Hexagon will provide any Software licenses, Cloud Programs or any services (including the Services), Customer must agree to these Master Terms and to the terms of a corresponding Order. The Parties agree these Master Terms will govern each Order. To the extent that the Master Agreement purports to impose obligations, restrictions, or limitations upon Customer's Affiliates or Users, Customer shall be responsible to Hexagon for Customer's Affiliates' and Users' compliance with such terms and shall procure Customer's Affiliates and Users compliance. These Master Terms consist of the following: • The General Terms and Conditions set forth below • Exhibit A -- End User License Agreement • Exhibit B — Maintenance Terms and Conditions for Software • Exhibit C — Sample Project Deliverable Sign -Off Form • Exhibit D -- Cloud Program Conditions • Exhibit E — Subscription License Terms • Exhibit F — COTS Training Program Terms • Exhibit G — Common Terms Glossary • Exhibit H — Change Order Template GENERAL TERMS AND CONDITIONS 1 Definitions. All capitalized terms not otherwise defined herein shall have the meaning set forth in Exhibit G (Common Terms Glossary), 2 Elements of an Order.. 2.1 Order Composition. 2.1A Each Order will be comprised of Order Documents. 2.1.2 From time to time, Customer may request from Hexagon or Hexagon may provide Customer a draft Quote and/or SOW for Deliverables. 2.1.3 Upon mutual execution of the Order Documents, Customer will execute the Order Documents and issue a Notice to Proceed, unless otherwise specified in the Order Documents. 2.1.4 Notwithstanding the foregoing, Orders for Maintenance Services and Cloud Programs shall commence on the date specified in the Order Documents regardless of whether Customer has issued a Notice to Proceed. Hexagon Principle Contracting Document $108302019PCD Page 3 2.2 Pricing. The following minimum elements shall be included with the Order Documents associated with the following types of Orders: 2.2.1 For a Software License Sale, a Quote identifying the Software licenses and quantities being procured and the total price for the Software License Sale. 2.2.2 For Time and Materials Project Assignments, a Quote setting forth the number of hours allocated for each grade of Hexagon resource to be utilized on the assignment and the hourly rate for each grade of Hexagon. Unless otherwise specified in the Order Documents, the Time and Materials Project Assignment shall expire and end six (6) months from the date the Order was formed between the Parties. 2.2.3 For Fixed Price Project Assignments, a Quote and SOW shall set forth the price of the work to be performed for and the Deliverables provided for that Order; provided however, that for a Fixed Price Project Assignment consisting of a COTS Training Curricula, a SOW may be omitted and pricing may be set forth solely in a Quote. 2.2.4 For Orders for Maintenance Services, a Quote identifying the Software to be maintained and the total price for the associated Maintenance Services, 2.2.5 For Cloud Program Sales, the quantity of License Keys subscribed for, the duration (beginning and end) of the period of the Customer's subscription to the Cloud Program, the amount of Cloud Program Fees payable to Hexagon for the Cloud Program, and Cloud Services Schedule(s) associated with the ordered Cloud Applications, 2.2.6 For Subscription License Sales, a Quote identifying the name of the Subscription Licenses, the quantity of the Subscription Licenses being purchased, and the Subscription Term. 2.3 Change Control. During the course of Hexagon's performance under an Order, either Party may request a change in the scope of the Order in writing, delivered to the other Party's project manager. The Change Order shall be based upon the Change Order Template attached hereto as Exhibit H. Any changes in price, schedule, or other terms must be documented either by an amendment or Change Order. No change, as contemplated in this paragraph, shall become effective until agreed to by both Parties in a -mutually executed writing. 2.4 Acceptance. Acceptance will occur based upon the following: 2.4.1 For Fixed Price Project Assignments, not governed by Exhibit F, acceptance shall occur when the applicable Task Acceptance Criteria has been satisfied in accordance with the Task Acceptance Process as set forth in an SOW. 2.4.2 For Time and Materials Project Assignments and Maintenance Services, the services are accepted as performed. For Time and Materials Project Assignments, the Services are accepted as performed so long as such Services are performed with a standard of care no less than that of a reasonably prudent public safety software developer. 2.4.3 For a Software License Sale, once the Software has been delivered or access to the Software has been received. 2.4.4 For a Cloud Program Sale, when the License Keys are provided to Customer. 2.4.5 For a Subscription License Sale, once the applicable Subscription License(s) has been delivered or access to the Subscription License has been provided to the Customer. 3 Composition of the Master Agreement. 3.1 Components. The agreement between the Parties (herein referred to as the "Master Agreement") consists of: (1) the Primary Contracting Document, (2) these Master Terms (including the General Terms and Conditions and all Exhibits), (3) any amendments to the Master Agreement, (4) Orders, together with any Change Orders, that may be delivered, prepared, or issued after the Effective Date, and (5) all documents, including applicable documents referenced via hyperlink, incorporated by reference in the Hexagon Principle Contracting Document S108302019PCD Page 4 documents identified in this Section. For certain Third Party Software, Third Party Terms will also be applicable and be considered as part of the Master Agreement. 3.2 Order of Precedence. In the event of any conflict or inconsistency among documents forming the Master Agreement, the following order of precedence shall be used to determine the resolution of the discrepancy, unless the Parties mutually agree in writing to an alternative decision: (1) Any amendments to the Master Agreement; (2) The Primary Contracting Document; (3) Applicable Cloud Services Schedules and Training Program Statements; (4) These Master Terms (excluding exhibits); (5) Exhibits to these Master Terms; and (6) Order Documents (exclusive of Cloud Services Schedules and Training Program Statements), as amended or modified by a change order. For only Third Party Software subject to Third Party Terms, the Third Party Terms shall have precedence in the event of a conflict between the Third Party Terms and any other terms of the Master Agreement. Invoicing and Payment. 4.1 Invoices. Invoices shall be issued based upon the following: 4.1.1 For Software License Sales, Hexagon shall invoice Customer for the amount set forth in the Quote upon delivery of or access having been provided to the Software identified in the Order Documents; 4.1.2 Orders for Fixed Price Project Assignments shall be invoiced and become payable upon completion of a payment milestone identified in the SOW, or when applicable, in accordance with Exhibit G; 4.1.3 Time and Materials Project Assignments shall be billed and invoiced on a monthly basis as the hours are expended and Onsite Fees are incurred, or after all hours set forth in the Order Documents have been expended, whichever occurs first. 4.1 A Orders for Maintenance Services shall be billed and invoiced in accordance with Exhibit B. 4.1.5 Cloud Program Sales shall be billed and invoiced in accordance with Exhibit D. 4.1.6 Orders for Subscription License Sales shall be billed and invoiced in accordance with Exhibit E. 4.2 Payment. Customer shall make payment for any invoices within forty-five (45) calendar days in accordance with the Local Government Prompt Payment Act, Chapter 218, Florida Statutes. 4.3 Late Payment. If Customer does not make timely payment, an interest charge of two percent (2%) per Month (or the maximum allowed by law, whichever is less), which shall be compounded on a monthly basis, will be due on any unpaid and overdue amounts. To the extent the Customer is the subject of an applicable prompt pay act statute or ordinance, the Customer shall be subject to the terms set forth in that statute(s) and/or ordinance(s) in lieu of the prior sentence. Interest penalties will only be paid in accordance with the local Government Prompt Payment Act, Chapter 218, Florida Statutes. 4.4 Taxes. The purchase price is exclusive of all Federal, State, or Local taxes. Any taxes applied to this sale by a Federal, State, or Local taxing authority will be the responsibility of Customer. Such taxes do not include franchise taxes or taxes based on net income. If Customer is claiming tax-exempt status, it must submit the proper documentation satisfactory to Hexagon evidencing its tax-exempt status. Applicable taxes may be invoiced at any time such taxes become fixed and certain. Hexagon Principle Contracting Document S108302019PCD Page 5 Term and Termination. 5.1 Term. The Term of the Master Agreement shall begin on the Effective Date and remain in effect for a period of thirty-six (36) consecutive Months or until the Master Agreement is earlier terminated pursuant to the terms set forth herein or by mutual agreement of the Parties with the possibility of renewal for up to two (2) additional one (1) year periods upon the mutual written agreement of the Parties.. An Order that is executed prior to the expiration of the term of the Master Agreement shall be governed by the Master Agreement even if the Master Agreement Term expires during the performance of the Order. To the extent Customer executes an Order pursuant to later issued master terms, then this Master Agreement shall terminate upon completion of all Orders executed hereunder regardless of the amount of time remaining in the Term. 5.2 Termination for Convenience. Except for Orders for Maintenance Services, Cloud Program Sales, and Subscription License Sales, either Party may terminate the Master Agreement or an Order in its sole discretion at any time upon providing the other Party with thirty (30) days written notice. The Coverage Period, Cloud Term, or Subscription Term, (if applicable) shall survive termination if the Master Agreement is terminated for convenience. In the event of a termination pursuant to this paragraph, Customer agrees to pay Hexagon for the Work performed and Software delivered and provided, plus the cost of any labor, equipment, or materials ordered in good faith prior to notice of termination that could not be canceled, less amounts previously paid by Customer for such Work and/or Software. To the extent a Party exercises its right to terminate a specific Order, that termination shall have no effect upon the remaining Master Agreement, which, along with any other active Orders, shall remain in full force and effect. If a Party desires to terminate the Master Agreement, then the Parties shall proceed to wind down all ongoing work under the respective Orders in effect under the Master Agreement by the termination date. Each Party shall take commercially reasonable steps to bring the work to a close and to reduce its costs and expenditures. 5.3 Termination for Cause. Either Party may terminate the Master Agreement or a specific Order, as the case may be, in the event that other Party materially breaches a material term of the Master Agreement or any Order. 5.3.1 In the event a Party has materially breached an Order, the non -breaching Party may terminate the Order only after providing a sixty (60) calendar day cure period to cure such breach and the breach has not been cured, except for material breaches arising from non-payment. During the sixty (60) day cure period, the Parties shall try to determine a mutually agreeable plan to cure such breach. If such breach cannot be cured or an acceptable plan is not provided within the sixty (60) day cure period, the non -breaching Party may, but does not have the obligation to, terminate the Order. 5.3.2 In the event a Party has materially breached the Master Agreement or multiple Orders, the non -breaching Party may terminate the Master Agreement only after providing a sixty (60) calendar day cure period to cure such breach and the breach has not been cured except for material breaches arising from non-payment. During the sixty (60) day cure period, the Parties shall try to determine a mutually agreeable plan to cure such breach. If such breach cannot be cured or an acceptable plan is not provided within the sixty (60) day cure period, the non -breaching Party may, but does not have the obligation to, terminate the Master Agreement. If the Master Agreement is terminated pursuant to this paragraph, by the termination date, Hexagon will stop all Work pursuant to any Orders arising under the Master Agreement. In the event the Master Agreement is terminated for cause, Hexagon shall be entitled to, and Customer agrees to pay Hexagon, payment for all Work performed and Software provided on all ongoing Orders up to the termination date, less amounts previously paid by Customer under the affected Orders. 5.3.3 Notwithstanding the foregoing and subject to the Government Prompt Payment Act, Chapter 218, Florida Statutes, Hexagon may suspend its performance of or terminate any Order or the Master Agreement for cause if payment is not received within sixty (60) days following the date when payment was due. In the event an Order is suspended or terminated for cause, Hexagon shall be entitled to, and Customer agrees to pay Hexagon, payment for Work performed and Software delivered on said Order up to the suspension or termination date, less amounts previously paid by Customer under the affected Orders provided that the Deliverables and Services are Hexagon Principle Contracting Document S108302019PCD Page 6 properly delivered or performed in accordance with this Master Agreement or Order.. If Hexagon suspends an Order under this paragraph, then it may thereafter terminate the Order upon giving written notice to the Customer. 5.3.4 Notwithstanding the foregoing, Customer may not exercise a termination pursuant to the terms of Section 5.3 if Hexagon's material breach of the terms and conditions of the Master Agreement or any Order thereunder is proximately caused by Customer's negligence or failure to perform its obligations. 6 IP Ownership. Customer acknowledges Hexagon will retain ownership and title of Hexagon IP made or provided pursuant to any Order. All Software provided under the Master Agreement is licensed to Customer in accordance with Exhibit A (End User License Agreement) except as it is inconsistent with the terms set forth herein. Third Party Software is licensed to Customer pursuant to Third Party Terms. Warranties. 7.1 Software, The Software Products licensed under Exhibit A are warranted to substantially conform to the user documentation for a period of thirty (30) days from the initial installation; provided that Software Products covered by a Maintenance Contract between Customer and Hexagon shall instead be warranted and supported as stated in the Maintenance Contract. All Customer data and information it or Hexagon enters into the System, or that is provided to Hexagon by Customer to implement the System, shall be owned by Customer as provided below. Third Party Software is licensed to Customer pursuant to the software license agreement delivered with such Third Party Software product. All Customer information and data such as computer files, data bases, reports, etc. specifically prepared, developed, or managed by the Customer (referred to as "materials") is the property of the Customer and shall be subject to confidentiality obligations set forth in this Master Agreement. In the event of a dispute regarding payment, the Parties shall negotiate in good faith to resolve. Under no circumstances shall Hexagon withhold access to any materials so as to adversely affect the Customer or any of the Customer's operations. Upon completion or termination of the Agreement, all of the above materials, to the extent requested by the Customer, shall be delivered to the Customer or to any subsequent provider within ten (10) calendar days in a format acceptable to the Customer (or subsequent provider) and when multiple acceptable formats exist agreed between the Parties. Hexagon shall deliver these materials at no additional cost or expense to the Customer to allow Customer to conduct operations uninterrupted and to be available for general access and reporting going forward. Notwithstanding the foregoing, for Cloud Program Sales and Subscription Licenses, Hexagon shall not have any obligation herein if the Cloud Term or Subscription Term have expired. Where possible Hexagon shall deliver the materials in a non-proprietary format. If unavoidable to supply in a proprietary format, then a perpetual license shall be granted by Hexagon to the Customer to access, use, and report on the Customer's materials. Notwithstanding the foregoing, for Cloud Program Sales and Subscription Licenses, Hexagon shall not have any obligation if the Cloud Term or Subscription Term have expired. This provision shall not apply to Cloud Prgram Sales or Subscription License Sales. Hexagon, at its expense, can make and retain copies of all materials only as permitted and required by law. Hexagon shall at all times remain subject to confidentiality obligations set forth in this Master Agreement (or other governing agreement) Hexagon Principle Contracting Document S108302019PCD Page 7 7.2 Subsystem Warranty Coverage. For, and only for, new Subsystems procured/implemented pursuant to an Order under these Master Terms, the warranty coverage shall be set forth in the applicable SOW, which shall be in lieu of the warranty coverage set forth in Section 7.1. 7.3 Third -party Warranty Coverage. To the extent third -party products are supplied by Hexagon, those products are provided with a pass-thru-warranty from the original manufacturer, if any. 7.4 Disclaimer. Any product information Hexagon has shared with Customer during the proposal and/or contract activities to date was to provide an understanding of Hexagon's current expected direction, roadmap, or vision and is subject to change at any time at Hexagon's sole discretion. Hexagon specifically disclaims all representations and warranties regarding future features or functionality to be provided in any Software or Deliverable. Hexagon does not commit to developing the future features, functions, and/or products discussed in this material beyond that which is specifically committed to being provided by Hexagon pursuant to a valid Order. Customer should not factor any future features, functions, or products into its current decisions since there is no assurance that such future features, functions, or products will be developed. When and if future features, functions, or products are developed, they may be made generally available for licensing by Hexagon. 7.5 Warranty Disclaimer. EXCEPT AS SPECIFICALLY SET FORTH IN THIS ARTICLE, HEXAGON DISCLAIMS (TO THE FULLEST EXTENT PERMITTED BY LAW) ALL WARRANTIES ON PRODUCTS FURNISHED PURSUANT TO THE MASTER AGREEMENT, INCLUDING ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE WARRANTIES SET FORTH IN THIS ARTICLE 7 IS IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED, AND, EXCEPT AS SET FORTH IN ARTICLE TITLED "INDEMNIFICATION PROVISIONS" BELOW, REPRESENTS THE FULL AND TOTAL WARRANTY OBLIGATION AND/OR LIABILITY OF HEXAGON, 8 LIMITATION OF LIABILITY EXCEPT FOR INDEMNIFIED CLAIMS ALLOWED UNDER SECTION 9.1 BELOW, IN NO EVENT WILL HEXAGON BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, (EXCEPT BODILY INJURY TO A THIRD PERSON OR PROPERTY OR WRONGFUL DEATH PROXIMATELY RESULTING FROM ANY BREACH OF WARRANTY), PUNITIVE OR SPECIAL DAMAGES, INCLUDING, BUT NOT LIMITED TO, LOST PROFITS, LOSS OF USE OR PRODUCTION, LOSS OF REVENUE, OR LOSS OF DATA, EVEN IF HEXAGON HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. UNDER NO CIRCUMSTANCE WILL HEXAGON'S LIABILITY TO CUSTOMER UNDER THIS MASTER AGREEMENT EXCEED THE AMOUNT THAT HEXAGON HAS BEEN PAID BY CUSTOMER UNDER THE INDIVIDUAL ORDER UNDER WHICH THE EVENT GIVING RISE TO THE CAUSE OF ACTION HAS OCCURRED. Indemnification Provisions. 9.1 Hexagon will defend, at its expense, a third party action, suit, or proceeding against Customer ("Claim"), and indemnify Customer from any judgments, settlements, and reasonable attorney's fees resulting therefrom, to the extent such Claim is (i) attributable to bodily injury, death, or physical damage to tangible property caused by Hexagon's negligent acts or omissions arising under the Master Agreement; or (ii) based upon an allegation that a Software Product, Customized Software, Cloud Application, or Services Deliverable as of its delivery date under the Master Agreement, infringes a valid United States: patent, copyright, or trademark, or misappropriates a third party's trade secret ("Infringement Claim"). 9.2 Hexagon's defense and indemnification obligations are conditioned upon: 9.2.1 Customer providing prompt written notice to Hexagon in writing of any Claim; 9.2.2 Hexagon having primary control of the defense of any actions and negotiations related to the defense or settlement of any Claim, understanding Hexagon may not settle a claim without Customer's consent if such settlement assigns fault or culpability to Customer but Hexagon shall allow Customer to reasonably participate in its own defense and Hexagon shall reasonably cooperate with Customer with respect to the settlement of any claim.;; and 9.2.3 Customer cooperating fully in the defense or settlement of any Claim. Hexagon Principle Contracting Document S108302019PCD Page 8 9.3 Hexagon will have no obligation to defend Customer or to pay any resulting costs, damages, or attorneys' fees for any Infringement Claims alleging direct or contributory infringement of the Software Product, Cloud Program, or Service Deliverable (i) by the combination of or integration with a product, process, or system not supplied by Hexagon; (ii) by material alteration by anyone other than Hexagon or its subcontractors; (iii) by use after Customer has been notified of possible infringement; (iv) by use after modifications are provided to Customer; (v) by use after a return for refund as described below is ordered by Hexagon; (vi) if the creation of which was pursuant to specifications provided by Customer; or (vii) by use other than as specified in the documentation associated with the Software Product. 9.4 In connection with any Infringement Claims, Hexagon, at its own expense and option, may either (i) obtain rights for Customer to continue using the allegedly infringing Hexagon supplied item; (ii) replace the item with a non -infringing alternative, or modify the allegedly infringing elements of the item, while maintaining substantially similar software functionality or data/informational content; or (iii) refund to Customer a prorated portion of the license fees paid by Customer for the infringing item(s); provided that proration for perpetually licensed software shall be based on a five (5)-year, straight-line depreciation basis beginning from the initial date of delivery. In the event of a prorated return, Customer will uninstall, cease all use of and return to Hexagon the infringing item(s). 9.5 In no event will the indemnification for Infringement Claims apply to any Beta Software, or sample, hot fix, royalty free, or evaluation software delivered pursuant to the Master Agreement. 9.6 This section provides the sole and exclusive remedies of Customer and Hexagon's entire liability in the event of a Claim. Customer has no right to recover and Hexagon has no obligation to provide any other or further remedies, whether under another provision of the Master Agreement or any other legal theory or principle in connection with a Claim. 10 Insurance. 10.1 Policies and Coverage Amounts. Hexagon agrees to procure and maintain in force during the term of the Master Agreement, at its own cost, the following policies and amounts of coverage: 10.1.1 Workers' Compensation Insurance as required state statute or regulation. 10.1.2 Commercial General Liability Insurance with minimum combined single limits of ONE MILLION DOLLARS ($1,000,000) each occurrence and ONE MILLION DOLLARS ($1,000,000) general aggregate. The policy shall be applicable to all premises and operations. The policy shall include coverage for bodily injury, broad form property damage, and personal injury. 10.1.3 Automobile Liability Insurance with minimum combined single limits for bodily injury and property damage of not less than ONE MILLION DOLLARS ($1,000,000) for any one occurrence, with respect to each of Hexagon's owned, hired or non -owned vehicles assigned to or used in performance of the services or work under the Master Agreement. 10.1.4 Umbrella/Excess Coverage with minimum combined single limits of ONE MILLION DOLLARS ($1,000,000) per occurrence. 10.2 Policy Maintenance. Hexagon shall procure and maintain, and shall cause any subcontractor of Hexagon to procure and maintain, the minimum insurance coverages listed herein. All policies shall be continuously maintained for the term of the Master Agreement. 10.3 Certificate of Insurance. A Certificate of Insurance shall be completed by Hexagon's insurance agent(s) as evidence that policies providing the required coverage amounts, conditions, and minimum limits are in full force. The completed Certificate of Insurance shall be sent to the contact person identified in the Primary Contracting Document. 10.4 Insurance Deductible. Hexagon shall be solely responsible for any deductible losses under the policies required above. 11 Security and Breach Notification. 11 A Hexagon shall take reasonable industry action to prevent, detect, identify, report, track and respond to Security Incidents. In the event of a Security Incident, Hexagon will provide a Security Incident report to Hexagon Principle Contracting Document S108302019PCD Page 9 the Customer or its Affiliates via the support website or Cloud Portal (as applicable). The report shall be provided within twenty-four (24) Business Hours following Hexagon's discovery, confirmation, and investigation of a Security Incident. 12 Dispute Resolution. 12.1 Resolution Protocol. The Parties shall exercise their best efforts to negotiate and settle promptly any dispute that may arise with respect to the Master Agreement or Order made pursuant to the Master Agreement ("Dispute") in accordance with the provisions set forth herein. If either Party disputes any provision of the Master Agreement (the "Disputing Party"), or the interpretation thereof, or any conduct by the other Party under the Master Agreement, that Party shall bring the matter to the attention of the other Party at the earliest possible time in order to resolve the Dispute except for Disputes for non-payment. If such dispute is not promptly resolved by the employees responsible for the subject matter of the dispute, the Disputing Party shall be permitted to deliver to the non -Disputing Party contact person identified in the Primary Contracting Document a written notice of the dispute, whereupon the Parties shall endeavor in good faith to escalate the dispute to appropriate executives for each Party for resolution within fifteen (15) business days, or such longer period as to which the Parties may mutually agree. 12.2 Mediation. To the extent a dispute is not resolved through the process outlined in the previous section and remains unresolved, the Parties agree to enter into non -binding mediation to resolve the dispute. Within sixty (60) calendar days, of the issuance of the Dispute Notice, or such longer period that is mutually agreeable to the Parties, the Parties agree to identify a mutually acceptable mediator who shall mediate the dispute. If after making reasonable efforts to identify a mutually acceptable mediator and no later than fifty (50) calendar days after the issuance of the Dispute Notice, the Parties are unable to identify such a mediator, the Disputing Party shall provide the non -disputing party with a list of five (5) proposed mediators. The non -disputing Party shall have five (5) business days from receipt of such list from the Disputing Party to identify one proposed mediator on the list to use as a mediator. If the non -disputing Party fails to identify and communicate its choice to the Disputing Party in the time allotted, then the Disputing Party shall be permitted to unilaterally identify the mediator from the list of five (5) mediators previously given who shall mediate the Dispute. The mediator shall be an attorney licensed to practice law in the state courts identified in section below titled "Governing Law." Subject to the mediator's availability, the Parties agree to mediate the dispute within thirty (30) days after the Parties have identified a mediator who has agreed to mediate the dispute. To the extent the mutually identified mediator is unavailable, unwilling, or unable to mediate the Dispute, the Parties shall utilize the same steps listed above to identify a new mutually agreeable mediator. To the extent the Disputing Party had to prepare a list of proposed mediators previously, it shall prepare and transmit a revised list within five (5) business days of receiving notice of the proposed mediator's unavailability. Subject to the mediator's requirements, the Parties agree they shall be permitted to attend the mediation via telephone or video conferencing. The Parties agree to pay in equal shares the mediator's fee and expenses unless otherwise agreed to pursuant to a settlement agreement. 12.3 Prerequisites to Litigation. Except for disputes for non-payment, only after the Parties have endeavored to resolve the dispute through the processes outlined in the immediately preceding two sections may a Party commence litigation to resolve the dispute. 12.4 Injunctive Relief. Notwithstanding the foregoing, either Party may, before or during the exercise of the informal dispute resolution procedures set forth above, apply to a Florida court for Lee County or United States District Court for the Middle District of Florida as identified in the section titled "Governing Law" for a temporary restraining order or preliminary injunction where such relief is necessary to protect its interests pending completion of such informal dispute resolution procedures. 13 Notices. All notices given between the Parties shall be in writing and shall be considered properly sent by postage prepaid United States Mail or overnight carrier to the Customer and/or Hexagon representative, as applicable and identified in the Primary Contracting Document, or such substitutes as may hereafter be disclosed by proper notification. Hexagon Principle Contracting Document S108302019PCD Page 10 14 Force Majeure. Neither Party shall be deemed to be in default of any provision of the Master Agreement or an Order or be liable for any delay, failure in performance, or interruption of service resulting from acts of war, acts of terrorism, criminal acts, acts of God, natural disaster, fire, lightning, acts of or restriction imposed by civil or military authority, pandemics, epidemics, cyber-attack, labor disruption, civil disturbance, expropriation, embargo, or lawful export restriction. Customer shall have the option to terminate this Master Agreement fo convenience, if Hexagon fails to perform any Services in any material respect because of the occurrence of a force majeure event and: (a) the event of force majeure is not resolved within seven (7) business days after the occurrence of the force majeure event; or (b) such event of force majeure is not reasonably subject to resolution within seven (7) business days after such occurrence. This section does not relieve or suspend a Party's obligation to pay money to the other Warty under the terms of the Master Agreement. 15 Place of Performance. To the extent necessary, Customer agrees to provide appropriate work space and work place accommodations, computer equipment; software; access to relevant data, documents, plans, reports, and analyses; and necessary access to Hexagon personnel to perform work on an Order_ To the extent work is performed remotely. Customer must provide VPN or secured remote connectivity (including a login and password) to all servers and workstations requiring installationlconfiguration by Hexagon. 16 Amendments. Any and all amendments to the Master Agreement shall be in writing, executed by both Parties, and specifically reference the fact the amendment is intended to alter these Master Terms. No Order or Change Order shall affect these Master Terms. 17 Confidential Information. The Parties agree not to disclose Confidential Information provided to it by the Disclosing Party to the maximum extent allowable under applicable law unless it first obtains the Disclosing Party's written consent to such disclosure. Nothing in this Agreement shall be interpreted in a manner contrary to Customer's obligations under Ch. 119, Florida Statues, It is further understood and agreed that money damages may not be a sufficient remedy for any breach of this provision of the Master Agreement by the Receiving Party and the Disclosing Party may be entitled to seek equitable relief, including injunction and specific performance, as a remedy for any such breach. Such remedies shall not be deemed to be the exclusive remedies for a breach of this provision of the Master Agreement but will be in addition to all other remedies available at law or equity. The covenants set forth herein and the rights and obligations related thereto shall continue for a period of five (5) years from the date of disclosure. 18 Personal Data. 18.1 Where Personal Data is provided by the Customer to Hexagon, the Customer shall act as the data controller and shall be responsible for complying with all applicable data protection laws. Hexagon shall act as the data processor in respect of such Personal Data and shall process the Personal Data in accordance with applicable data protection laws. The Customer acknowledges and agrees that Hexagon is not capable of being a data controller due to Hexagon's inability to determine the purpose and means of the processing of Personal Data provided by Customer to Hexagon. To the extent that. (a) Personal Data of Users or Authorized Cloud Users provided by the Customer to Hexagon pursuant to the Master Agreement is subject to the European Union General Data Protection Regulation 2016/679, as may be amended from time to time (°GDPR"); and (b) the Customer and Hexagon do not have a separate, written data processing agreement, then the Customer and Hexagon agree that the terms of Hexagon's Data Processing Addendum, as updated from time to time, found at: https:l/www.hexationsafetyinfrastructure.com/- ImedialLe al/Hex. ontSI/Policies/DPAIDPALPIDPA LP 08-2019. df, shall apply. 18.2 Where Customer is responsible for providing Personal Data on behalf of Users or Authorized Cloud Users directly to Hexagon, Customer will secure and maintain all necessary consents and make all necessary disclosures before including Personal Data in Customer Data input to, or otherwise supplied to Hexagon. In the event Customer, including all its Users, does not consent to Personal Data being Hexagon Principle Contracting DOCUmen1 S108302019PC❑ Page 11 processed as a result of the Master Agreement, Customer acknowledges Hexagon may be unable to provide Services, Software Products, Maintenance Services, and/or Cloud Program (or part thereof}. 18,3 Hexagon will only process Customer supplied Personal Data in accordance with the Customer's lawful instructions and to the extent and as necessarily required to provide the applicable goods and services under the Master Agreement and for no other purpose. Except as may be otherwise required by law, contract, or judicial order, after expiration or earlier termination of the Master Agreement, Hexagon will destroy all Customer -supplied Personal Data in accordance with applicable data protection laws, 18.4 if Hexagon supplies maintenance, support, or subscription services to Customer with respect to third -party products, and if the third -party supplier or proprietor of such requires Customer be party to any data processing agreement in connection therewith, and if Customer has not separately executed an instrument to satisfy such requirement, then Customer and Hexagon agree that the terms of the applicable third -party data ,processing agreement, as updated from time to time, found at https:l/www. hexagonsafetVinfrastructure.com/- /media/Legal/H.exa,gon./SI./Policies/DPA/DPALP/DPA LP 08-2019.pdf, shall apply. 19 Assignment Neither Party shall assign, sublet, or transfer all or any portion of the Master Agreement, nor any interest in the Master Agreement, without the express written consent of the non -assigning Party, which consent may be granted or withheld in the sole discretion of the non -assigning Party. Notwithstanding the foregoing, Hexagon may assign its rights and obligations under the Master Agreement, without the approval of Customer, but with sixty (60) days' written notice to Customer to: (1) an Affiliate or (2) another business entity in connection with a merger, consolidation, or reorganization of Hexagon or any of its subsidiaries. If Customer is a government entity, another government entity (referred to in this paragraph as a cooperative purchaser) may, with prior written consent of Hexagon, use the Master Agreement, excluding Orders to which it is not a party, as a contract vehicle for its purchases from Hexagon; provided that in such event the term "Customer" shall refer solely to the relevant cooperative purchaser with respect to its transaction and shall not refer to the cooperative purchaser with respect to transactions not for its direct benefit. Software, services, hardware, and maintenance will be priced and scoped upon request of the cooperative purchaser and dependent upon the scope of the intended project. To the extent this clause is exercised by any cooperative purchaser with Hexagon's consent, Hexagon shall deal directly with the cooperative purchaser regarding the scope and pricing of the project. Cooperative purchasers shall make their own legal determination as to whether the collective purchasing permitted by this clause is consistent with laws, regulations, and other policies applicable to the cooperative purchaser; and, Customer shall have no liability with respect to obligations of any cooperative purchaser utilizing the terms of this section 19 to place Orders under the Master Agreement. 20 Export. Hexagon IP, including any technical data related to Software, Services, Maintenance Services, or Cloud Programs is subject to the export control laws and regulations of the United States. Diversion contrary to United States law is prohibited. Hexagon IP, including any technical data related to Software, Services, Maintenance Services, or Cloud Programs shall not be exported or re-exported, directly or indirectly (including via remote access), under the following circumstances; • To Cuba, Iran, North Korea, Syria, the Crimean region of Ukraine or any national of these countries or territories. • To any person or entity listed on any United States government denial list, including, but not limited to, the United States Department of Commerce Denied Persons, Entities, and Unverified Lists, the United States Department of Treasury Specially Designated Nationals List, and the United States Department of State Debarred List(http:fexport.gov/ecrleg_main_023148.asp). • To any entity if Customer knows, or has reason to know, the end use is related to the design, development, production, or use of missiles, chemical, biological, or nuclear weapons, or other unsafeguarded or sensitive nuclear uses. • To any entity if Customer knows, or has reason to know, that a reshipment contrary to United States law or regulation will take place, Hexagon Principle Contraoting Document S108302019PCD Page 12 Customer agrees to hold harmless and indemnify Hexagon and its Affiliates for any causes of actions, claims, costs, expenses and/or damages resulting to Hexagon from a breach of the export restrictions set forth in the Master Agreement by Customer or any User. Any indemnification by Customer, shall only be to the extent and limit provided in Section 768.28, Florida Statutes ($200,000.00), as may be amended from time to time, and shall not be considered a waiver of any statutory or constitutional sovereign immunity protections. Any questions regarding export or re-export of the Software should be addressed to Hexagon's Export Compliance Department at 305 Intergraph Way, Madison, Alabama, 35758, USA or at ex,00rtcomaliancet'7a..intergraoh.com. If the Software Customer received is identified on the media as being ITAR-controlled, the Software has been determined to be a defense article subject to the U.S. International Traffic in Arms Regulations ("ITAR"). Export of the Software from the United States must be covered by a license issued by the Directorate of Defense Trade Controls ("DDTC") of the U.S. Department of State or by an ITAR license exemption. The Software may not be resold, diverted, or transferred to any country or any end user, or used in any country or by any end user other than as authorized by the existing license or ITAK exemption. Subject to the terms of the EULA included herein, a Software Product may be used in other countries or by other end users if prior written approval of DDTC is obtained. If Customer is located outside the United States, Customer is responsible for complying with any local laws in Customer's jurisdiction which might impact Customer's right to import, export or use the Software, and Customer represents that Customer has complied with any and all regulations or registration procedures required by applicable law related to the use and importation of the Software Products. 21 Non -Solicitation of Employees. Customer agrees it will not, without the prior written consent of Hexagon, solicit any Hexagon employee, or induce such employee to leave Hexagon's employment, directly or indirectly, during the Term and for a period of twelve (12) Months after the Master Agreement expires or is terminated. 22 Miscellaneous. 22.1 Authority. Each Party represents and certifies to the other Party it has the requisite legal authority to enter into and be bound by the Master Agreement and all Orders arising from the Master Agreement. Any individual purporting to execute or accept a Quote, Primary Contracting Document, or any Order Documents governed by the Master Terms on behalf of a Party represents and warrants to the other Party that such individual has the authority to bind, and does bind, the Party on whose behalf such individual purports to execute or accept such instrument(s). 22.2 Survival. In addition to other provisions that are specifically identified as surviving termination of this Master Agreement, the rights and obligations in sections titled "IP Ownership", "Limitation of Liability", "Dispute Resolution", "Confidential Information", 7xport", and the terms of any license or access granted pursuant to the Master Agreement (including, but not limited to, Exhibit A, Exhibit D, and/or Exhibit E), shall survive and continue after expiration or termination of the Master Agreement, shall remain in effect until fulfilled, and shall apply to any permitted successors and assigns. Upon termination of the Master Agreement, the provisions of the Master Agreement, including those in the preceding sentence, which by their express terms survive termination, shall remain in full force and effect. 22.3 Waiver. The waiver by either Party of any of its rights or remedies in enforcing any action or breach under the Master Agreement in a particular instance shall not be considered as a waiver of the same or different rights, remedies, or actions for breach in subsequent instances. 22.4 Severability. If any provision of the Master Agreement or an Order is void, voidable, unenforceable, or illegal in its terms, but would not be so if it were rewritten to eliminate such terms that were found to be voidable, unenforceable, or illegal and such rewrite would not affect the intent of the provision, then the provision must be rewritten to be enforceable and legal. 22.5 Headings. Numbered topical headings, articles, paragraphs, subparagraphs or titles in the Master Agreement are inserted for the convenience of organization and reference and are not intended to affect the interpretation or construction of the terms thereof. 22.6 Governing Law. The Master Agreement shall for all purposes be construed and enforced under and in accordance with the laws of the State of Florida. The Parties agree any legal action or proceeding Hexagon Principle Contracting Document S108302019PCD Page 13 relating to the Master Agreement shall be instituted in Lee County, Florida or the U.S. District Court for the Middle District of Florida. The Parties agree to submit to the jurisdiction of and agree that venue is proper in these courts in any such legal action or proceeding. The Parties waive the application of the United Nations Commission on International Trade Law and United Nations Convention on Contracts for the International Sale of Goods as to the interpretation or enforcement of the Master Agreement. 22.7 Governing Language. The controlling language of the Master Agreement is English. If Customer received a translation of the Master Agreement into another language, it has been provided for convenience only. Les parties confirment que ('accord -cadre et toute la documentation connexe sont et seront en anglais. (Translation: "The Parties confirm that the Master Agreement and all related documentation is and will be in the English language.") 22.8 Independent Contractor. The Parties agree that Hexagon is an independent contractor, that nothing in the Master Agreement shall be construed as establishing or implying a relationship of master and servant between the Parties, or any joint venture or partnership between the Parties, and that nothing in the Master Agreement shall be deemed to constitute either of the Parties as the agent of the other Party or authorize either Party to incur any expenses on behalf of the other Party or to commit the other Party in any way whatsoever. Hexagon and its agents, employees, or subcontractors shall at no time be deemed to be agents, employees, or subcontractors of Customer, or be deemed to be under the control or supervision of Customer when carrying out the performance of its obligations in the Master Agreement. Without the prior written consent of Customer, Hexagon shall not carry on any activity that could be construed as being on behalf of Customer. 22.9 Public Records Law. Hexagon specifically acknowledges its obligations to comply with Section 119.0701, Florida Statutes, with regard to public records, and shall: 1) keep and maintain public records that ordinarily and necessarily would be required by the Customer in order to perform the services required under this Agreement; 2) upon request from the Customer, provide the Customer with a copy of the requested records or allow the records to be inspected or copied within a reasonable time at a cost that does not exceed the cost provided in Chapter 119, Florida Statutes, or as otherwise provided by law; 3) ensure that public records that are exempt or confidential and exempt from public records disclosure requirements are not disclosed, except as authorized by law; and 4) meet all requirements for retaining public records and transfer, at no cost to the Customer, all public records in possession of Hexagon upon termination of this Agreement and destroy any duplicate public records that are exempt or confidential and exempt from public records disclosure requirements. All records stored electronically must be provided to the Customer in a format that is compatible with the information technology system of the Customer. IF HEXAGON HAS QUESTIONS REGARDING THE APPLICATION OF CHAPTER 119, FLORIDA STATUTES, TO HEXAGON'S DUTY TO PROVIDE PUBLIC RECORDS RELATING TO THE CONTRACT, CONTACT THE CUSTODIAN OF PUBLIC RECORDS AT 239-533-2221, 2115 SECOND STREET, FORT MYERS, FL 33901, publicrecords@leegov.com; http://www.leegov.com/publicrecords. Hexagon Principle Contracting Document S108302019PCD Page 14 22.10 Anti -Bribery. Each Party hereby certifies it shall comply with all applicable laws in carrying out its duties under the Master Agreement, including, but not limited to, the United States Foreign Corrupt Practices Act ("FCPA"). In particular, Customer, on behalf of itself and its Affiliates, and Hexagon, each severally represent and agree that: Such party is familiar with the FCPA and its purposes and agrees to comply with the acts. Specifically, such party is aware of and will comply with the FCPA's prohibition of the payment or the gift of any item of value, either directly or indirectly, to an official of a government, political party or party official, candidate for political office, or official of a public international organization, for the purpose of influencing an act or decision in his/her official capacity, or inducing him/her to use his/her influence with the government to assist a company in obtaining or retaining business for, with, or in that country or directing business to any person; Such party has not made, and will not make, payments to third parties which such party knows or has reason to know are illegal under the FCPA, or the laws of any applicable jurisdiction; The method of making payment to Hexagon as provided hereunder is not in violation of the law of any applicable jurisdiction. Either Customer or Hexagon has the right to terminate the Master Agreement upon any violation of the FCPA or similar laws by the other Party. 22.11 Hexagon Authority. BY ISSUANCE OF A QUOTE TO CUSTOMER WITHOUT THE WORD "DRAFT" OR SIMILAR MARKINGS OR DISCLAIMERS THEREON, HEXAGON REPRESENTS IT HAS THE REQUISITE LEGAL AUTHORITY TO ENTER INTO AND BE BOUND BY THE MASTER AGREEMENT AND THE ORDER INTENDED TO RESULT FROM THE QUOTE. BY EXECUTING THE QUOTE AND RETURNING IT TO HEXAGON OR OTHERWISE ENTERING INTO AN ORDER, CUSTOMER REPRESENTS AND CERTIFIES TO HEXAGON IT HAS THE REQUISITE LEGAL AUTHORITY TO ENTER INTO AND BE BOUND BY THE MASTER AGREEMENT AND THE ORDER ASSOCIATED THEREWITH. 22.12 Non -Appropriations Clause. All funds for payment by the Customer under this Agreement are subject to the availability of an annual appropriation for this purpose by the Lee County Board of County Commissioners. In the event of non -appropriation of funds by the County for the services provided under this Agreement, the Customer will terminate the Agreement, without termination charge or other liability, on the last day of the then current fiscal year or when the appropriation made for the then -current year for the services covered by this Agreement is spent, whichever event occurs first. If at any time funds are not appropriated for the continuance of this Agreement, cancellation shall be accepted by Hexagon on thirty (30) days' prior written notice, but failure to give such notice shall be of no effect and the Customer shall not be obligated under this Agreement beyond the date of termination. 23 Entire Agreement. The Master Agreement constitutes the entire agreement between the Parties with regard to the subject matter hereof. Except as otherwise provided in the Principal Contracting Document, the Master Agreement supersedes any and all prior discussions and/or representations, whether written or oral, and no reference to prior dealings may be used to in any way modify the expressed understandings of the Master Agreement. Any future representations, promises and oral agreements related to the products, product features, future product enhancements, product functionality, or services covered by the Master Agreement will be of no force or effect unless reduced in writing and made apart of the Master Agreement or an Order thereto. The Master Agreement may not be amended or modified unless so done in a writing signed by authorized representatives of both Parties. The pre-printed terms and conditions of Customer's PO or any other terms and conditions of a Customer PO shall be void, even if issued subsequent to the effective date of the Master Agreement, and shall not be deemed to constitute a change to the Master Agreement. 24. Source Code Escrow. Subject to an additional fee for this service and only for Perpetual Licenses, Hexagon shall provide all Source Code and any updates or fixes for Hexagon's Commercial Off the Shelf application software that Customer has purchased from Hexagon for safekeeping with the Source Code escrow agent. Hexagon maintains an existing escrow agreement with Iron Mountain which allows Hexagon to register Customer as a beneficiary under the Escrow Agreement. As beneficiary of the Escrow Agreement, Customer will have access to all Source Code of the products that they license for all versions Hexagon Principle Contracting Document S108302019PCD Page 15 of the COTS software in the event that a triggering event (defined below) occurs. The software source deposited with the escrow agent will be a snapshot of the current version of the Source Code delivered by Hexagon in the form of a pure Source Code tree. Upon taking possession of the Source Code, Customer will have the right to use the Source Code for products that it owns in the versions currently installed on its system or any subsequent versions in the archive. Hexagon will make a deposit of the Source Code with the escrow agent once every six (6) months. Customer shall have access to the Source Code only in the event Hexagon during Extended Warranty Period or the maintenance period (1) files for bankruptcy protection under Chapter 7 of the Bankruptcy Code, (2) makes a general assignment for the benefit of creditors; (3) appoints a general receiver or trustee in bankruptcy of Hexagon's business or property; or (4) or takes any other action under any state or federal insolvency or similar law for the purpose of its bankruptcy or liquidation. Upon Customer taking possession of the Source Code, Customer hereby agrees as follows: (1) Customer accepts full and total responsibility for the safekeeping of the Source Code. Customer agrees that such Source Code shall be subject to the restrictions of transfer, sale, and reproduction placed on the software itself as stated in the software license signed by all parties. (2) Customer agrees to only use Source Code related to applications for which they own a license. There will be Source Code from other applications in the archive. (3) Customer agrees that any unauthorized release of the Source Code will cause irreparable harm to Hexagon. Therefore, Customer agrees, subject to Section 768.28, Florida Statutes, to compensate Hexagon for any and all damages Hexagon suffers, to include reasonable attorney's fees, resulting directly or indirectly from, but not limited to, the negligence, gross negligence, or willful misconduct of Customer, its employees, former employees, agents and third -party associates if so ordered by the court. Notwithstanding the foregoing, Customer agrees that Hexagon is entitled to an immediate injunction to stop any further alleged or actual disclosure. (4) No license under any trademark, patent, copyright, or any other intellectual property right, is either granted or implied by the disclosure of the Source Code to Customer. Hexagon's disclosure of the Source Code to Customer shall not constitute any representation, warranty, assurance, guarantee or inducement by the Hexagon to Customer of any kind, and, in particular, with respect to the non -infringement of trademarks, patents, copyrights, or any other intellectual property rights, or other rights of third persons or of Hexagon. (5) Hexagon will not be responsible for maintaining the Source Code. Furthermore, Hexagon will not be liable for any consequences related to the use of Source Code modified by Customer. 25. Background Check. Hexagon, at its expense, must conduct a background check for each of its employees when initially hired, as well as for the employees of its subcontractors, who will provide Services to the Customer or who will have access to Customer computer systems, either through on -site or remote access. The minimum background check process for all Hexagon personnel shall include, but not be limited to, the following checks: a. Criminal Felony & Misdemeanor b. Statewide Criminal Search c. Federal Criminal d. SSN Trace e. SSN Validation The background check must be conducted prior to initial access by Hexagon personnel. Hexagon shall provide proof of a satisfactory background check to the Customer prior to assignment of any Hexagon Principle Contracting Document S108302019PCD Page 16 Hexagon personnel. The Customer retains the right to reject assignment of any Hexagon personnel based on the results of a background check. Hexagon personnel who separate employment from Hexagon for any reason whatsoever, and for any length of time, must undergo another background check prior to renewed access to the Customer. The Customer shall have the ability to audit Hexagon's background check process to ensure compliance with Customer standards, at any time. Additionally, all Hexagon personnel have the responsibility to self -disclose any misdemeanor or felony convictions that occur while assigned to the Customer within three (3) business days of the conviction or upon return to a Customer assignment. The conviction must be reported to Hexagon, who shall then notify the Customer. If at any time it is discovered that any Hexagon personnel has a criminal record that includes a felony or misdemeanor, Hexagon is required to inform the Customer and the Customer will assess the circumstances surrounding the conviction, time frame, nature, gravity, and relevancy of the conviction to the job duties to determine whether that Hexagon employee will be placed or remain on a Customer assignment. The Customer may withhold consent at its sole discretion. Failure of Hexagon to comply with the terms of this paragraph may result in the termination of its Agreement with the Customer. Conduct. Hexagon agrees that all of its officers, employees and representatives shall conduct themselves in a professional manner. Each party shall communicate with one another and its employees and members of the public in a civil manner whenever conducting business with each other. All aspects of Hexagon's performance, including complaints received from the public, may impact the Customer's decision to renew or terminate this Agreement in accordance with the provision contained here. For that Order and future Orders under this Master Agreement, Hexagon will remove or suspend or further investigate their employees for any act of violence, sexual harassment, substance abuse, or act of bigotry/prejudice Hexagon Principle Contracting Document SI08302019PCD Page 17 EXHIBIT A END -USER LICENSE AGREEMENT IMPORTANT —READ CAREFULLY: This EULA is a legal agreement by and between User and Hexagon for the Software Product. Software Products are also subject to the Use Terms. Any software, including, without limitation, any third party components and/or Upgrades, associated with a separate end -user license agreement is licensed to User under the terms of that license agreement. Use Terms delivered with an Update or Upgrade of a Software Product shall apply to the Update/Upgrade. All use of the Software Product is subject to applicable Order Documents. 1.0 LICENSE GRANT. Provided User is not in breach of any term or condition of this EULA, Hexagon hereby grants User a limited, non-exclusive license up to the quantity of Software Product licenses purchased by User to: (i) install and use the Software Product, in object code form only; (ii) use, read, and modify documentation prepared by Hexagon and delivered to User pursuant to the Order Documents; and/or (iii) view and/or use Hexagon audio-visual training materials provided to User pursuant to the Order Documents; provided all of the foregoing shall be strictly for User's internal use and strictly in accordance with this EULA and the applicable Order Documents. The license is non -transferable, except as specifically set forth in this EULA. User assumes full responsibility for the selection of the Software Product to achieve User's intended results, and for the installation, use and results obtained from the Software Product. 2.0 UPDATES AND UPGRADES. If the Software Product is an Update to a previous version of the Software Product, User must possess a valid license to such previous version to use the Update. Neither the Software Product nor any previous version may be used by or transferred to a third party. All Upgrades are provided to User on a license exchange basis and are subject to all of the terms and conditions of the EULA provided with the Upgrade. By using an Update, User (i) agrees to voluntarily terminate User's right to use any previous version of the Software Product, except to the extent that the previous version is required to transition to the Update or Upgrade; and (ii) acknowledges and agrees that any obligation that Hexagon may have to support the previous version(s) of the Software Product will end upon availability of the Update. If an Update is provided, User will take prompt action to install such Update as directed by Hexagon. If User fails to do so, User acknowledges that the Software Product may not work correctly or that User will not be able to take advantage of all of the Software Product's available features. In such event, Hexagon will not be liable for additional costs User incurs because of User's failure to install such Update. 3.0 RIGHTS AND LIMITATIONS. 3.1 The Following are Permitted for User's License: User may make one copy of the Software Product media in machine readable or printed form and solely for backup purposes. Hexagon retains ownership of all User created copies. User may not transfer the rights to a backup copy unless User transfers all rights in the Software Product and license as provided for in Section 3.2.1. Any other copying of the Software Product, any use of copies exceeding the number of copies User has been authorized to use and has paid for, and any distribution of the Software Product not expressly permitted by this EULA, is a violation of this EULA and of federal and/or applicable governing law. 3.2 The Following are Prohibited for User's License: 3.2.1 User shall not sell, rent, license, lease, lend or otherwise transfer the Software Product, or any copy, modification, or merged portion thereof without Hexagon's express written consent for such transfer, which consent may not be unreasonably withheld. Any such unauthorized transfer will result in automatic and immediate termination of the license. Hexagon Principle Contracting Document S108302019PCD Page 18 3.2.2 The Software Product is licensed as a single product. User shall not, and User shall not authorize anyone else to: (i) decompile, disassemble, or otherwise reverse engineer the Software Product; (ii) work around any technical limitations in the Software Product; (iii) publish the Software Product for others to copy or use; (iv) use, copy, modify, distribute, disclose, license or transfer the Software Product, or any copy, modification, or merged portion, in whole or in part, except as expressly provided for in this EULA; (v) re -use the component parts of the Software Product with a different software product from the one User is licensed to use or on different computers; (vi) circumvent any license mechanism or in the Software Product or the licensing policy; (vii) publish to a third party any results of benchmark tests run on the Software Product (viii) use or view the Software Product for any purposes competitive with those of Hexagon; (ix) use the Software Product except as expressly set forth in this EULA; and (x) unless otherwise specifically permitted in writing by Hexagon, use the Software Product outside the country in which it is licensed. 3.3 Fault Tolerance. The Software Product is not one hundred percent (100%) fault -tolerant. Unless the Software Product's documentation expressly provides the contrary: Software Product is not designed or intended for use in any situation where failure or fault of any kind of the Software Product could lead to death or serious bodily injury of any person, or to severe physical, property or environmental damage ("High -Risk Use"); and, User is not licensed to use the Software Product in, or in conjunction with, any High -Risk Use. High -Risk Use is STRICTLY PROHIBITED. High Risk Use includes, for example, the following: operation of aircraft or other modes of human mass transportation, nuclear or chemical facilities, and Class III medical devices. User hereby agrees not to use the Software Product in, or in connection with, any High -Risk Use. High Risk Use shall not mean use of the Software Product for purposes for which it is regularly marketed and sold (e.g. public safety and utility dispatch software may be used to dispatch police, fire, emergency medical services, and emergency utility services). 3.4 Licensing Mechanism Disclaimer. Without waiver of any of its rights herein, Hexagon may at its sole discretion provide User who is operating public safety Software Products a licensing mechanism to allow such Software Products to be available for use even when User has accessed all of its purchased licenses. Regardless of whether it receives the licensing mechanism, User acknowledges it is permitted to use the Software Products only up to the number of licenses it has purchased. Any usage of Software Products beyond the amount purchased by User will be subject to the payment of additional fees by User to Hexagon at then current prices for the Software Products in like manner as provided in Section 6.2 (Audit). 4 USER OBLIGATIONS. 4.1 The Software Product may require User's System to comply with specific minimum software, hardware and/or Internet connection requirements. The specific minimum software, hardware and/or Internet connection requirements vary by Software Product and type of license and are available from Hexagon upon request. 4.2 User is responsible, and bears the sole risk, for backing up all systems, software, applications, and data, as well as properly using the Software Product. 4.3 At all times, User must keep, reproduce and include all copyright, patent, trademark and attribution notices on any copy, modification or portion of the Software Product, including, without limitation, when installed, used, checked out, checked in and/or merged into another program. 4.4 User shall comply with the Use Terms, including limitations that apply to specific types of licenses identified therein. Hexagon Principle Contracting Document S108302019PCD Page 19 111=17►yfI 5.1 For a Perpetual License, this EULA is effective until terminated (a) by User, by returning to Hexagon the original Software Product or by permanently destroying the Software Product, together with all copies, modifications and merged portions in any form; (b) by Hexagon, upon User's breach of any of the terms hereof or User's failure to pay the appropriate license or subscription fee(s); (c) upon User's installation of an Upgrade that is accompanied by a new license agreement covering the Software Product Upgrade; or (d) by expiration of the applicable license files, if this is a temporary license. User agrees upon the termination of this EULA to cease using and to permanently destroy the Software Product (and any copies, modifications and merged portions of the Software Product in any form, and all of the component parts of the Software Product) and certify such destruction in writing to Hexagon. For a Subscription License, this EULA is effective until the User's Subscription Term expires without being renewed; by Hexagon upon User's breach of any of the terms hereof or User's failure to pay the appropriate Subscription License fee(s); or the Subscription is otherwise terminated. User agrees upon the termination of this EULA or expiration of User's Subscription to cease using and to permanently destroy the Software Product (and any copies, modifications and merged portions of the Software Product in any form, and all of the component parts of the Software Product) and certify such destruction in writing to Hexagon. 6 AUDIT. 6.1 Hexagon shall have the right to 6.1.1 Audit User's use of the Software Product and User's compliance with the provisions of this EULA during User's normal business hours. Hexagon will provide User with thirty (30) days prior written notice of an audit under this Section. Hexagon's right to conduct this type audit shall be limited to twice per calendar year. Prior to the start of an audit, Hexagon's personnel will sign a reasonable non -disclosure agreement provided by User, if Customer/User elects to provide Hexagon with such agreement. During the audit, User shall allow Hexagon's personnel to be provided reasonable access to both User's records and personnel. 6.1.2 Obtain certain documentation from User, as follows. If the Software Product includes logging mechanisms intended to track usage volume or quantity, User shall transmit log files associated therewith to Hexagon upon Hexagon's demand and in accordance with Hexagon's reasonable transmission instructions. Hexagon will not demand the transmission of usage tracking log files more frequently than four (4) times in any calendar year. 6.2 In the event the results of the audit in Section 6.1.1 or the documentation provided by User in Section 6.1.2 indicate User has used unlicensed Software Products or quantities thereof, User agrees to promptly pay Hexagon: (i) the current list price for each unlicensed Software Product(s) used by User (ii) interest of two percent (2%) per month or the highest rate allowed by applicable law for each month, commencing with the initial month of unlicensed usage of the Software Product(s), and (iii) the costs for the audit in Section 6.1.1. END OF EXHIBIT A Hexagon Principle Contracting Document S108302019PCD Page 20 EXHIBIT B MAINTENANCE TERMS AND CONDITIONS FOR SOFTWARE These terms and conditions ("Maintenance Terms") govern the provision of maintenance and support services by Hexagon with respect to Covered Products. 1. DEFINITIONS. All capitalized terms not otherwise defined herein shall have the meaning set forth in the associated Exhibit titled "Common Terms Glossary." 2. TERM, 2.1. Term. The Maintenance Contract shall begin, on the first calendar day of the first Month of the Coverage Period and shall expire on the last calendar day of the last Month of the Coverage Period. The Coverage Period shall be for whale Months only. 2.2. Renewal. Prior to expiration of the Coverage Period, Hexagon may submit to Customer a renewal quote with pricing for extension of the Coverage Period. The Parties may extend the Coverage Period pursuant to Order Documents. 2,3. Lapse. In the event of a Lapse: (i) Hexagon shall, at any time, be entitled to discontinue Maintenance Services, in whole or in part, for the affected Covered Products; (ii) Hexagon shall be relieved of any previously provided pricing commitments or options for Maintenance Services, if any, related to time periods following the Lapse; and, (lii) Hexagon may permit Customer to reinstate support for Covered Products pursuant to Hexagon's then current policies and practices, including any policies or practices related to payment of reinstatement fees. 3. SCOPE OF COVERAGE FOR COVERED SOFTWARE PRODUCTS. Maintenance Services described in this Section apply to Covered Software Products only. Maintenance Services for Covered Third Party Products are separately stated. Hexagon offers three levels of Maintenance Services for Covered Software Products, dependent upon the Software Product and other factors. Under all levels of Maintenance Service, Hexagon shall provide reasonable commercial efforts to aid in the diagnosis of Defects. Under all levels of Maintenance Services, but only until the subject Software Product version reaches Version Limitation I or Version Limitation II, Hexagon shall provide reasonable commercial efforts to aid in correction of Defects. After a Software Product version reaches Version Limitation I, but only until the subject Software Product reaches Version Limitation II, Hexagon shall provide reasonable commercial efforts to aid in correction of Level One Defects only. The level of Maintenance Services for each Software Product is identified in the Order Documents, subject however to Version Limitations. Defect corrections provided by Hexagon shall, unless otherwise agreed by Hexagon, be delivered within Hexagon's product releases, and in accordance with Hexagon's standardized release cycles. Levels of Maintenance Services are as follows. 3.1. Advantage Support. Advantage Support will include and be limited to the diagnostic and Defect correction support as described above, and the following: Out -of -the -box functionality support via the support help desk (telephone or eService via Hexagon's support website where available at httgs:llsupr)ort.hexagonsafetvinfrastructure.com; and, access to any applicable Hexagon problem knowledge base online self-help tool. Phone support is available Monday through Friday from 8AM — 5PM at Customer's local time, excluding Hexagon -observed holidays. Local Hexagon Principle Contracting Document 8108302019PCD Page 21 variances in support hours will be posted on the Customer Support Web Site or applicable local support website or can be determined by contacting Customer's local Hexagon office. 3.2. Standard Support. Standard Support will include and be limited to the following: 3.2.1. All features of Advantage Support. 3.2.2. Access to available Updates of Covered Software Products. Hexagon will notify Customer when Updates are made available for any Covered Software Products for which Maintenance Service have been purchased, by way of posting notices of such to the "Support Notices and Announcements" section on the Customer Support Web Site or applicable local support website or via direct notification by Hexagon. Updates are shipped to Customer upon Customer request, logged in the Customer Support Web Site. Hexagon is not obligated to produce any Updates. For avoidance of doubt, a Customer's entitlement to Updates shall not include entitlement to any therein embedded or otherwise related module or function which is licensed and priced separately from Covered Product(s) for which Customer has purchased an entitlement to Updates. 3.3. Premium Support. Premium Support will include all features available under Standard Support (subject to Version Limitations). Additionally, for a Level 1 Defect, phone support is also available after-hours and on Hexagon -observed holidays. 3.4 Product Change Requests (also referred to as CR-E) will be reported in like manner as set forth in Section 3.1. Hexagon will review Product Change Requests and at its sole discretion decide whether to make the requested change to the Covered Product(s) through an Update. Product Change Requests not accepted may be the subject of a separate contract between the Parties. For the avoidance of doubt, to the extent Hexagon agrees to make a requested change to a Covered Product pursuant to a Product Change Request, any and all IPR resulting from the Update including the change or modification is and shall remain the property of Hexagon. 4. MINIMUM SYSTEM REQUIREMENTS; CUSTOMER'S OBLIGATIONS. Performance of Maintenance Services by Hexagon is specifically conditioned upon the following minimum system requirements and fulfillment by Customer of the following obligations (collectively, minimum system requirements and customer obligations hereinafter referred to as "Customer Obligations"): 4.1. System Requirements. Customer is responsible for ensuring: the System Equipment and network infrastructure meet minimum system requirements specified by Hexagon and made available to Customer upon request; its System Equipment and network infrastructure are adjusted as required to accommodate Updates of Covered Products; compatibility of non - Hexagon provided products with products provided by Hexagon; and, its systems, software, and data are adequately backed up. Hexagon is not liable for lost data. 4.2. Hexagon Access and Customer Cooperation. Customer's system and/or System Equipment must have input and output devices that enable the use of Hexagon's diagnostic programs and supplemental tests. Customer will permit Hexagon to electronically access Customer's system via SecureLinkTM, a tool providing secure, auditable remote access to Customer's system for Hexagon to effectively render Maintenance Services. Customer will ensure availability of its own system technical support personnel so that Hexagon can fulfill its Maintenance Services obligations. When reporting problems to Hexagon's support help desk, Customer will provide a complete problem description, along with all necessary documents and information that is available to Customer and required by Hexagon to diagnose and resolve the problem. Customer will grant all necessary access to all required systems as well as to the Covered Products, and any other reasonable assistance needed. Customer will carry out any reasonable instructions and will install any necessary patches, Defect corrections, or Updates. Customer will appoint a minimum a maximum of four (4) contact people who are each authorized to make use of the Maintenance Services ("Authorized Contacts"). Customer must assure Authorized Contacts have adequate expertise, training, and experience to provide professionally accurate descriptions of malfunctions and facilitate Hexagon's efficient response. Authorized Contacts must have successfully completed Hexagon product training or complete it at the next available scheduled opportunity, for those products for which formal training is available. Customer will bear the cost Hexagon Principle Contracting Document S108302019PCD Page 22 of this training. Customer is obligated to select only those personnel for this task who are suitable for it by means of training and function, and who have knowledge of Customer's operating system, network, and hardware and software. Customer agrees to promptly notify Hexagon of any replacement of an Authorized Contact. 5. EXCLUDED SOFTWARE SERVICES. Services for the following are outside the scope of the Maintenance Contract and may be available under separate Order at an additional charge (collectively "Excluded Services"): 5.1. Installation of any Covered Product, Update, or interface software. 5.2. Network configuration. 5.3. Configuration or customization of Covered Products to Customer or other third party requirements (except as necessary to remedy a Defect). 5.4. System -level tuning and optimization and system administration support. 5.5. Training. 5.6. Services required because the Authorized Contact is not available or is not trained. 5.7. On -site services (unless waived by Hexagon, in its sole discretion). 5.8. Services required due to modifications of Covered Products by Customer. 5.9. Services required due to use other than in the ordinary manner intended for the Covered Products, or use in a manner that contravenes terms hereunder, or Customer's disregard of the installation and operating instructions according to the Documentation provided with the Covered Products. 5.10. Services required due to failure of software or hardware that is not a Covered Product. 5.11. Services required due to Customer's use of hardware or software that does not meet Hexagon specifications or failure of Customer to maintain or perform industry standard maintenance on Customer's hardware or software. 5.12. Services required due to software or portions thereof that were incorrectly installed or configured (other than by Hexagon) or use in an environment inconsistent with the support environment specified by Hexagon, or used with peripherals, operational equipment or accessories not conforming to Hexagon's specifications. 5.13. Services required due to cases of force majeure, especially lightning strikes, fire or flood, third - party criminal acts, or other events not caused through Hexagon's fault. 5.14. Services required due to Customer's failure to fulfill the Customer Obligations. 5.15. Services required due to faulty or incomplete Customer data. 6. COVERED THIRD PARTY PRODUCTS. Support and Updates of Covered Third Party Products shall be provided in the fashion and to the extent or duration that Hexagon is authorized to provide such by the third party manufacturer of the Covered Third Party Products, and such Covered Third Party Products and related services may be subject to additional terms and conditions of the third party manufacturer of the Third Party Software. Services and updates for any Third Party Software not listed in the Order Documents as Covered Products must be obtained from the third party owner of the products or their designated representative. 7. REQUIRED COVERAGE. 7.1. Multiple or Interdependent Licenses. If Customer holds multiple licenses for any Covered Product, all held licenses must be included as Covered Products in the Maintenance Contract. 7.2. Prerequisite Licenses. All prerequisite licenses for Software Products necessary to operate the Covered Products, together with all licenses of Software Products interoperating with Covered Hexagon Principle Contracting Document S108302019PCD Page 23 Products in a single solution, must be included as Covered Products in the Maintenance Contract. 8. ADDITIONS AND REMOVALS OF COVERED PRODUCTS. 8.1. Additions of Covered Products. Software Products licensed from Hexagon during the term of the Maintenance Contract may be added as Covered Products, if such addition is addressed through additional related Order Documents. If Software Products are not added as Covered Products by commencement of Production use thereof, Hexagon may permit Customer to add support, but subject to additional fees payable pursuant to Hexagon's then current policies or practices. 8.2. Removal of Covered Products from Maintenance. Either Party may provide written notice to the other Party at least sixty (60) calendar days prior to the end of any Coverage Period Anniversary of its intent to remove any individual Covered Products from the Maintenance Contract at the end of the then current and contracted Coverage Period or any Coverage Period Anniversary. Neither Party may remove Covered Products except upon Coverage Period renewal or extension or Coverage Period Anniversary; provided that Hexagon may additionally remove Covered Products as part of a general discontinuance program at any time upon one hundred eighty (180) days' written notice. Customer may not remove from the Maintenance Contract individual software licenses of a Covered Product for which Customer has multiple copies under Maintenance Services or for Covered Products that are being used interdependently, unless Customer has first certified to Hexagon on a "Software Relinquishment Agreement" that it surrenders and relinquishes all rights in and to the applicable Software licenses and the copies of the Covered Product for which Customer desires to cease Maintenance Services (the "Relinquished Licenses") for the renewal Coverage Period have been uninstalled and removed from its system(s). Should Customer desire to resume usage of the Relinquished Licenses at a later date, Customer must re -purchase the licenses at the then current list price. 9. PAYMENT. 9.1. Terms of Payment. Charges for Maintenance Services are due and payable annually and in advance. All charges are due net thirty (30) calendar days from the date of invoice or prior to the beginning of the applicable Coverage Period, whichever is earlier. Charges for Covered Software Products added during a Coverage Period shall be prorated to the remaining Months of the Coverage Period, in whole Month increments only, and such charges shall be due and payable in full upon receipt of invoice. Covered Third Party Products added during a Coverage Period are subject to Section 6 of these Maintenance Terms. 9.2. Past Due Accounts. HEXAGON RESERVES THE RIGHT TO REFUSE SERVICE TO ANY CUSTOMER WHOSE ACCOUNT IS PAST DUE. At the discretion of Hexagon, Customers who have not paid any charges when due (i) under the Maintenance Contract, (ii) under any other agreement between the Parties, or (iii) under any agreement between Hexagon and Customer's parent and/or subsidiary, may not be rendered Maintenance Services until all past due charges are paid in full. The start of the Coverage Period shall not be postponed due to delayed payment of any charges. 9.3. Customer's Responsibilities Concerning Invoice Questions. Subject to applicable law, if Customer intends to dispute a charge or request a credit, Customer must contact Hexagon within ten (10) calendar days of the date on the invoice. Customer waives any right to dispute a charge or receive a credit for a charge for Maintenance Services that Customer does not report within such period. Hexagon Principle Contracting Document S108302019PCD Page 24 10. CUSTOMER ACKNOWLEDGEMENTS. During the Coverage Period, Customer commits to the following: 10.1. Customer shall have reviewed the Order Documents and by executing the Order Documents confirms the Order Documents accurately reflects all Hexagon software in its possession or control. 10.2. Customer acknowledges and confirms that for all Covered Products supported under the Maintenance Contract, all licenses of a Covered Product for which Customer has multiple copies in its possession and all prerequisite licenses necessary to operate Covered Products, are accounted for in the Order Documents. If all like Covered Products or prerequisite software licenses are not accounted for in the Order Documents, Customer agrees to notify Hexagon so that Hexagon may issue a revised Quote to Customer. 10.3. Customer acknowledges and confirms Maintenance Services provided herein shall be utilized only for the quantity of Covered Products licenses listed in the Order Documents. 10.4. Customer shall, and Customer shall cause each of Customer's employees and representatives to, comply with each and every term and condition of the EULA applicable to the Covered Products supported under the Maintenance Contract. 11. ADDITIONAL TERMS. 11.1. Software License. Any Updates furnished hereunder shall remain the property of Hexagon, Hexagon's Affiliate, or applicable third party, and are licensed in accordance with the then current Hexagon EULA, EULA of Hexagon's Affiliate, or third party SLA, which shall supersede any EULA or SLA associated with prior releases of the Covered Software Products or Covered Third Party Products. Upon Customer's request, Hexagon shall provide Customer with such EULA or SLA. Upon Hexagon's request, Customer agrees to execute a EULA or SLA, as applicable, for Covered Products. 11.2. Pass -Through Third Party Warranties. Covered Third Party Products are only warranted pursuant to a pass -through warranty to Customer from the applicable Third Party Software manufacturer and only to the extent warranted by the applicable Third Party Software manufacturer. 11.3. Remedies. In the event a warranted Maintenance Service, Covered Product, or Update provided pursuant to the Maintenance Contract does not substantially comply with the limited warranties set forth in the Maintenance Contract, Hexagon's entire liability and Customer's exclusive remedy shall be, in Hexagon's sole and absolute discretion, either (i) providing of a Service, Covered Product, or Update which conforms substantially with the warranty; or (ii) a refund of the purchase price of the particular warranted Service, Covered Product, or Update for the period of time that the warranted Service, Covered Product, or Update did not substantially conform to the limited warranties set forth in the Maintenance Contract. Hexagon is acting on behalf of its suppliers for the sole purpose of disclaiming, excluding and/or limiting obligations and liability as provided in the Maintenance Contract, but in no other respects and for no other purpose. 11.4. WARRANTY DISCLAIMERS. In addition to the Warranty Disclaimer provided in the Master Terms, Hexagon does not warrant that any Services, Covered Products, and Updates provided pursuant to the Maintenance Contract will meet Customer's requirements, and under no circumstances does Hexagon warrant that any Services, Covered Products, and Updates will operate uninterrupted or error or Defect free. 11.5. Third Party Providers. Hexagon reserves the right to provide Maintenance Services through a third party provider subject to Hexagon's assurance of performance, and the provider meeting Customer requirements, as applicable to Hexagon, including background checks and employee conduct requirements. Hexagon Principle Contracting Document S108302019PCD Page 25 END OF EXHIBIT B Hexagon Principle Contracting Document S108302019PCD Page 26 EXHIBIT C PROJECT DELIVERABLE SIGN -OFF FORM CUSTOMER NAME, CUSTOMER CITY- PROJECT NAME Submission Date: Month/Day/Year Sign -Off Target Date: Month/Day/year Submitted By: Hexagon Contact Name Submitted To: Customer Contact Name Customer Contract #: Customer Contract Number Customer/Project #: Hexagon Project Number TYPE OF DELIVERABLE ❑ SOW Tasks ❑ Payments ❑ Plans/Designs ❑ Training ❑ Other DELIVERABLE INFORMATION DELIVERABLE DESCRIPTION $AMOUNT OF PYMT THIS SECTION DESCRIBES THE DELIVERABLE (If applicable) With the deliverable described above complete, the Customer shall have ten (10) working days after receipt of a written request from Hexagon, to either sign -off that the deliverable has been met or state in writing to Hexagon the reason the deliverable has not been met. Sign -off of the deliverable shall be based solely upon the deliverable meeting the requirements stated in the Contract between Hexagon and CUSTOMER NAME dated Month/Day/Year and shall be indicated by the Customer signing the Project Deliverable Sign -off Form. If the Customer does not provide such sign -off or rejection within the ten (10) working day period then the deliverable will be deemed to have been signed off. The signature below acknowledges that the deliverable described in the Contract and listed above meets all of the appropriate criteria and supersedes all prior requirements for this item. Customer acknowledges completion of this payment milestone according to the Contract Payment Milestone Schedule and provides authorization to invoice this milestone. Authorized Customer Representative Customer Contact Name SIGNATURE Hexagon Principle Contracting Document SI08302019PCD DATE Page 27 EXHIBIT D CLOUD PROGRAM CONDITIONS These terms and conditions ("Cloud Conditions") govern the provision of the Cloud Program by Hexagon to Customer under a Cloud Program Sale Order. Any additional terms in any Cloud Services Schedule(s) also apply. 1. DEFINITIONS. Capitalized terms used and not otherwise defined herein have the meanings assigned in the Common Terms Glossary. 2. SCOPE OF CLOUD PROGRAM. 2.1 From the Cloud Program Start Date and for the duration of the Cloud Term, Hexagon will provide the License Key(s) to Customer in the amount specified in the Quote with respect to the Cloud Program purchased by Customer to use the Cloud Program subject to the provisions of these Cloud Conditions. Except for the Cloud Services, no other service, including Cloud Consulting Services, are provided by Hexagon pursuant to a Cloud Program Sales Order, 2.2 Hexagon may from time to time provide or otherwise make available Local Software. Local Software may include mobile applications obtainable from an online applications store, applications owned by a third -party, or other facilitating applications. In the event Hexagon provides or makes available such applications, the same shall be made available to Customer and owned by Hexagon (or the relevant third party), and used subject to these Cloud Conditions. If not sooner terminated, the license to use such Local Software shall terminate upon expiration of the Cloud Term. 3. CLOUD SERVICES AUTHORIZATION. During the Cloud Term, Hexagon grants Customer and its Affiliates the right to access and use components of the Cloud Program listed in the quantities reflected on the Quote solely for Customer's and Affiliates' own internal business purposes and subject to these Cloud Conditions 4. TERM, TERMINATION AND SUSPENSION. 4.1 The Cloud Program Sale Order commences on the Effective Date of the Order and shall continue for the Cloud Term, unless earlier terminated in accordance with the Master Terms and these Cloud Conditions. To the extent any optional renewals are identified in the Quote, the Customer must issue a PO or a notice to proceed to extend the Cloud Term and at the prices set forth in the Quote not less than sixty (60) days prior to the end of the Cloud Term. Prior to the end of the Cloud Term, the Customer may renew the Cloud Program Sale Order and/or have Customer Data Offboarded. 4.2 In addition to the rights and remedies set forth in the Master Terms, once notified in writing of the overdue payment, Customer acknowledges Hexagon may, without further notice, reduce the Cloud Services to the lowest tier of Cloud Services offered by Hexagon. During such time, Hexagon or the Third Party Service Provider is not obligated to facilitate or provide any services related to Onboarding or Onboarding. Without waiver of its right to terminate the Master Agreement and/or Cloud Program Sale Order or seek additional remedies, if full payment has not been received by Hexagon within thirty (30) days following written notice, Hexagon may suspend providing the Cloud Program to Customer until all outstanding Cloud Program Fees together with any applicable interest has been paid to and received by Hexagon. For avoidance of doubt, and without limitation, if Hexagon suspends providing the Cloud Program to Customer Hexagon Principle Contracting Document S108302019PCD Page 28 for non-payment, Customer shall have no right to access or use Cloud Applications, software applications provided by Hexagon which are incidental to the Cloud Program, Third Party Software Products, Cloud Services, Cloud Optional Services, or any goods, services, or benefits to be provided by Hexagon hereunder. Suspension of the Cloud Program for non-payment shall not prejudice Hexagon's rights hereunder or relieve Customer from the obligation to pay Cloud Program Fees associated with the period of suspension. 4.3 Termination shall not relieve the Customer of the obligation to pay any Cloud Program Fees accrued or payable to Hexagon prior to the date of termination. Unless otherwise agreed to in writing by Hexagon, in the event Hexagon terminates a Cloud Program Sale Order due to any of the conditions set forth in Section 4.2 above, then under no circumstances whatsoever shall Customer be entitled to any refund of Cloud Program Fees paid in advance to Hexagon pursuant to the terms of the Master Agreement. 5. AVAILABILITY. Hexagon shall reasonably endeavor to deliver Availability in accordance with the Service Level specified in the applicable Cloud Services Schedule. "Availability" or "Available" means the ability to connect to the Cloud Portal, connect to the Customer Cloud Environment for Production, launch Cloud Application(s), and access Customer Data contained in the Customer Cloud Environment for Production. Availability does not include the availability of third -party portals or Cloud Optional Services. Availability of Cloud Application(s) shall be determined by launching the main application for the applicable Cloud Application. For purposes of calculating Availability time, the following is excluded: time expended for Planned Maintenance; downtime required to perform Cloud Consulting Services; time expended due to the inability for Customer to connect to the Cloud Portal due to problems with the Customer's infrastructure or the internet; unavailability arising from Customer exceeding Customer purchased Cloud Application capacity; and, time expended due to any other circumstances beyond Hexagon's reasonable control, including Customer's or any User's use of third -party materials or use of the Cloud Program other than in compliance with the express terms of the Master Agreement and Hexagon's reasonable instructions (collectively "Exception(s)"). 6. CRITICAL SERVICE LEVELS. The purchased Service Level classifications are set forth in the Cloud Service Schedule. "Service Operational Time" means the time, expressed in a percentage as set forth below, that the Cloud Application is Available for a given Month during the service. The method of calculating the Service Operational Time is: Hours of Cloud Program Availability for a given Month Hours of Cloud Program Availability + downtime hours for such Month which are not related to x 100 an Exception 7. SERVICE CREDITS. 7.1 If in any Month the Service Operational Time in a Cloud Environment for Production falls below the purchased Service Level (a "Service Incident"), a "Return to Green Plan" shall be initiated for the Customer's Environment for Production. Hexagon shall have: (i) the remainder of the Month in which the Customer notified Hexagon of the Service Incident by way of a Cloud Service Request, which notified Hexagon of the problem which resulted in the Service Operational Time falling below the applicable Service Level, plus (ii) one (1) additional Month (collectively, the "Go Green Period"), to return the Service Operational Time to such Service Level. 7.2 Subject to Section 7.3 below, if the Service Operational Time does not rise to the applicable Service Level within the Go Green Period, then the Service Credit provided in the Cloud Service Schedule will be applied against each Month in which the Service Operational Time remains below such Service Level. 7.3 Service Credits apply: 7.3.1 Only as specified within the Cloud Services Schedule; Hexagon Principle Contracting Document S108302019PCD Page 29 7.3.2 Only to the extent that the affected Customer Environment is used in Production; 7.3.3 In strict accordance with Section 5; 7.3.4 Only if a Customer has logged a Cloud Service Request which notified Hexagon of the problem that causes the Critical Service Level to fall below the identified Availability percentage in the Cloud Services Schedule ("Green"); and 7.3.5 Only where Customer is compliant with the AUP. 7.4 To the extent applicable and properly noticed by Customer in accordance with Section 7.1 above, Service Credits shall be credited against the next invoice until such applicable Service Credits have been used. If the Master Agreement is terminated or Customer elects not to renew the Master Agreement before an ensuing invoice is issued, then such Service Credits are forfeited. Customer shall have no right to receive any monetary remuneration in exchange for unused Service Credits. Notwithstanding anything herein to the contrary, in no event shall Service Credits for any given year during the Term exceed twenty percent (20%) of the amount of Cloud Program Fees payable by Customer to Hexagon pursuant to the Quote for the annual period in which the Service Credit accrued. 7.5 The Customer's exclusive remedy for not meeting the Critical Service Level specified in the Cloud Services Schedule shall be the Service Credits as set forth in this Section. 8. CLOUD SERVICES SUPPORT. 8.1 As part of Cloud Services, Hexagon will provide the Cloud Services Support described within this Section 8. 8.2 Cloud Services Support is available at the times specified in the applicable Cloud Services Schedule. Cloud service requests and Product Change Requests can be directed by an Authorized Cloud User to Hexagon by: (i) the support website (https:Hsupport.hexagonsafetyinfrastructure.com), or (ii) telephoning Hexagon support at the times permitted within the Cloud Services Schedule. 8.3 When reporting a Cloud Service Request, if an Error, an Authorized Cloud User shall assign the Cloud Service Request a priority level based upon the criteria set forth in the support website (https://support.hexagonsafety infrastructure. com). The Authorized Cloud User shall provide a brief justification as to the criticality of the Cloud Service Request and a description of the Error giving rise to the Cloud Service Request, to include a statement of steps necessary to produce the error. Hexagon shall respond to the Cloud Service Request and provide commercially reasonable efforts to aid and address the Cloud Service Request. If Hexagon disagrees with the priority of the Cloud Service Request, it shall discuss the matter with Customer, but Hexagon, in its sole discretion, reserves the right to revise the initially reported priority level of the Cloud Service Request. 8.4 Product Change Requests will be reported in like manner as set forth in Section 8.3. Hexagon will review Product Change Requests and at its sole discretion decide whether to make the requested change to the Cloud Program. Product Change Requests not accepted may be the subject of a separate contract between the Parties. For the avoidance of doubt, to the extent Hexagon agrees to make a requested change to the Cloud Program pursuant to a Product Change Request, any and all IPR resulting from such change or modification is and shall remain the property of Hexagon. 8.5 Customer acknowledges and agrees that, as part of providing Cloud Services Support, Hexagon is permitted to make necessary changes to the Cloud Program without notice if necessary to perform Emergency Maintenance. Hexagon shall be permitted to access the Customer Cloud Environment in the event Hexagon deems Emergency Maintenance is necessary. 8.6 As it relates to, and only to, Local Software which is listed on the Quote, Hexagon shall provide support in like manner as is provided for Cloud Applications except Customer will permit Hexagon Hexagon Principle Contracting Document S108302019PCD Page 30 to electronically access the Local Software in the Local Environment via SecureLinkTM SecureLinkTM is a tool for providing secure, auditable remote access to the Local Software in order for Hexagon support personnel to effectively troubleshoot and address Errors related to Local Software. Support for Local Software listed on the Quote is included within Cloud Services Support except as is otherwise rendered commercially unreasonable due to the Local Software being hosted by Customer. 8.7 Except as otherwise necessary, as determined by Hexagon in its sole discretion, to satisfy the requirements of Sections 8.3 and 8.4, Cloud Services Support does not include: (i) training; (ii) configuration of Cloud Application(s), Cloud Optional Services, Cloud Portal, Third Party Software Products, Software Products, or other components of the Cloud Program; (iii) Customer Cloud Administration; (iv) programming or software development; (v) modifications to the Cloud Applications or Cloud Optional Services not accepted as a Product Change Request; (vi) onsite services; or (vii) services required because Customer has not performed its obligations under the Master Agreement. 8.8 Upgrades or Updates 8.8.1. As part of Cloud Services Support, Customer is entitled to receive all updates and upgrades to the purchased Cloud Application(s) and Local Software that Hexagon makes available. Cloud Consulting Services may be necessary to upgrade or update Cloud Optional Services, which is not part of Cloud Services Support. 8.8.2. From time to time, Hexagon may notify Customer through the Cloud Portal or support website (https://support.hexagonsafetyinfrastructure.com) that Hexagon has developed an upgrade or update for the purchased Cloud Application(s) and intends to deploy said update or upgrade, including any applicable Third Party Software Products. On the date specified in the notification, Hexagon will deploy the update or upgrade to the Cloud Development Environment for Customer testing and review, which Customer shall complete within the time prescribed in the notification of the availability of the update or upgrade, but not less than thirty (30) days thereafter (the "Testing Period"). In the event no Material Adverse Effect is reported by Customer within the Testing Period, then on a subsequently specified date by Hexagon, Hexagon will, at its discretion, deploy the update or upgrade to Customer Cloud Environment for Production. 8.8.3. In the event Customer provides written notice to Hexagon, within the Testing Period, of a Material Adverse Effect as a result of Customer's testing of the upgrade or update in accordance with Section 8.8.2 above, Hexagon shall discuss the matter with Customer and use commercially reasonable efforts to address any reasonable workarounds to such Material Adverse Effect, such agreed upon workaround to be subject to the same protocols set forth in Section 8.8.2 and this Section 8.8.3; provided, however, if Hexagon reasonably finds that no Material Adverse Effect exists, Hexagon may deploy the update or upgrade to the Customer Cloud Environment for Production. 8.8.4 As it relates to implementing updates or upgrades for Local Software that is included within the Cloud Program, Customer shall permit Hexagon to electronically access the Local Software on Customer's System Equipment via SecureLink to implement the Update in conjunction with the updating or upgrading of the Cloud Applications and provide any other reasonable support and cooperation required by Hexagon to upgrade or update the Cloud Program. 9. CUSTOMER RESPONSIBILITIES. 9.1 Customer shall be responsible for all activities that occur in Authorized Cloud User and User accounts, including, but not limited to, its Affiliates' accounts, and for Authorized Cloud Users' and Users' compliance with the Master Agreement. Customer shall: 9.1.1 Have sole responsibility for the accuracy, quality, integrity, reliability and appropriateness of all Customer Data that is placed into the Customer Cloud Environment; Hexagon Principle Contracting Document S108302019PCD Page 31 9.1.2 Use commercially reasonable efforts to prevent unauthorized access to or use of Cloud Program, including preventing utilization of more Credentials than otherwise reflected by the License Key(s) set forth in the quote, and notify Hexagon of any such unauthorized access or use; 9.1.3 Provide and maintain its own System Equipment, third party software, networks, internet access, and communication lines, including any public lines required to properly access the Cloud Portal and use the Local Software, including content or data and ensure such meet the minimum standards required to interoperate with the Cloud Program as communicated by Hexagon to Customer via the Cloud Portal or as otherwise determined by Hexagon; and 9.1.4 Abide by and comply with the Acceptable Use Policy, Documentation, and other requirements of these Cloud Conditions. 10. CLOUD SERVICE PROGRAM FEES, 10.1 Generally. Subject to Section 10:2 below, in consideration of the Cloud Program provided by Hexagon, Customer shall pay to Hexagon the Cloud Program Fees. 10.2 Adjustment. Hexagon may periodically review the Customer's usage of the Cloud Program to determine whether Customer's usage is consistent with the quantity of License Key(s) and/or Cloud Application capacity purchased. If the usage shows the Customer has used more License Key(s) than are specified in the Quote, then Customer shall pay Cloud Program Fees corresponding to the number of License Key(s) used in excess of the purchased quantity. If a Cloud Application is subject to capacity limitations (e.g. a limited number of transactions in a period), as expressly set forth in the applicable Cloud Services Schedule, the Cloud Application may be configured to cease or degrade some or all functions upon Customer reaching those capacity limitations and/or may be configured to permit additional usage for additional fees, all as and if described in the applicable Cloud Services Schedule(s). 97. TERMS OF PAYMENT. The invoice corresponding to the first year of Cloud Program Fees shall be provided to Customer upon Hexagon's issuance of License Key(s) to Customer: For purposes of clarity, once the first License Key(s) is issued for any Cloud Environment, the annual Fee will be due and payable in full. Invoices for subsequent years included within the Cloud Term as specified in the Quote (as may be adjusted pursuant to Section 10.2 above) will be issued prior to the Cloud Anniversary. 12. ACCEPTABLE USE POLICY (AUP). 12.1 The AUP forms part of these Cloud Conditions and is incorporated by reference. It may be found at the following site: https:llwww.hexagonsafetyinfrastructure.com/- /media_/Legal/Hexagon/SI/Policies/AUP/Cloud AUP-L.pdf. The Customer and any Authorized Cloud User or User shall comply with the AUP. A User or Authorized Cloud User will be prompted with review and acceptance of the AUP to gain access to the Cloud Application(s). Any update to the AUP will require each User or Authorized Cloud User to re -accept the modified AUP. Failure to comply with the AUP may result in the suspension of the Cloud Program or termination of the Cloud Program Sale Order as provided in Section 5 of the Master Terms. During any period of suspension, the Customer will still be liable for payment of the applicable Cloud Program Fees. 12.2 Hexagon reserves the right to change the AUP at any time, but to the extent within the control of Hexagon, it will give Customer thirty (30) days' notice in accordance with the Master Terms and the Primary Contracting Document of any such changes by posting notice of the upcoming change in the AUP on the Cloud Portal or as otherwise determined by Hexagon, unless otherwise Hexagon Principle Contracting Document S108302019PCD Page 32 required by law or where a Third Party Service Provider requires a change to be made to the AUP and is unable to provide such period of notice. If a Third Party Service Provider requires a change to be made to the AUP, Hexagon shall provide the equivalent period of notice as is provided by the Third Party Service Provider to Hexagon. 12.3 Without waiver of any other requirement or limitation set forth herein, Customer's use of any third party software in conjunction with the Cloud Application, Cloud Optional Services, and Hexagon Software Products that is not certified by Hexagon to operate in conjunction with the same is solely at Customer's risk. Addressing service requests arising from the use of uncertified third party software is not included within Cloud Services Support or the Cloud Program. 13. OWNERSHIP AND INTELLECTUAL PROPERTY. 13.1. In accordance with Section 6 of the Master Terms, Hexagon owns all right, title and interest in and to Cloud Application(s), Cloud Optional Services, the Software Products, Local Software, Documentation written by Hexagon, and any other data and information provided as part of the Cloud Program (except for data and information being owned by a third party), and all copies of all or any part thereof, are and shall remain vested in Hexagon. Third parties shall retain any and all IPR in and to their intellectual property that may be provided as part of the Cloud Program. Customer and its Affiliates do not have, and shall not attempt to decompile, disassemble, or otherwise attempt to gain access to any source code for the Cloud Application, Cloud Optional Services, any other Hexagon Software Product, or Third Party Software Products. Customer, for itself and its Affiliates acknowledges and agrees the Cloud Program is comprised of trade secrets, proprietary information, and Confidential Information, and that Customer, and its Affiliates shall not use, distribute, copy, perform, amend, alter, modify, create derivative works, reverse engineer, exploit, sublicense, or assign the Cloud Program or any component thereof except as expressly permitted by Hexagon (which permission may in some instances, subject stated limitations, be contained in a Cloud Services Schedule with respect to a particular Cloud Application). Without Hexagon's express, written permission, Customer shall ensure that no User transfers or assigns any Credentials to any other person or entity that is not an employee of Customer. 13.2. Customer and its Affiliates, respectively, shall retain their respective full ownership and all rights associated therewith solely to Customer Data to the extent they owned IPR to said information, as well as work product input or output generated by the Cloud Program. This ownership shall not extend to any formats or other intellectual property provided by Hexagon under the Master Agreement that makes a particular data file intelligent or that structures output, said formats and intellectual property which shall remain the property of Hexagon or the respective third party that owns said format or intellectual property. 14. PERSONAL DATA. 14.1. Hexagon reserves the right, but does not assume the obligation, to investigate any violation of this Exhibit D (Cloud Program Conditions) and/or AUP or misuse of the Cloud Services or Cloud Program. Hexagon may: (a) investigate violations of this Exhibit D (Cloud Program Conditions) and/or AUP or misuse of the Cloud Services or Cloud Program; and (b) remove, disable access to, or modify any content or resource that violates this Exhibit D (Cloud Program Conditions) and/or AUP. Hexagon may report any activity that Hexagon suspects violates any law or regulation to appropriate law enforcement officials, regulators, or other appropriate third parties. Hexagon's reporting may include disclosing appropriate information related to Customer or any User. Hexagon also may cooperate with appropriate law enforcement agencies, regulators, or other appropriate third parties to help with the investigation and prosecution of illegal conduct by providing network and systems information related to alleged violations of this Exhibit D (Cloud Program Conditions) and/or AUP. Hexagon Principle Contracting Document S108302019PCD Page 33 14.2. Unless a Customer Specified Data Center(s) is included in the Cloud Services as identified in the Quote, Hexagon and its Third Party Service Provider shall have sole discretion of the location of the Data Center(s). 15. SECURITY & BREACH NOTIFICATION. 15.1. Hexagon shall take reasonable industry action to prevent, detect, identify, report, track and respond to Security Incidents. 15.2. Hexagon Response to Security Incident. The following will apply in the event of a Security Incident: 15.2.1. Hexagon will provide a Security Incident report to the Customer or its Affiliates (as applicable) via the Cloud Portal, support website, or otherwise. The report shall be provided within twenty-four (24) Business Hours following Hexagon's discovery, confirmation, and investigation of a Security Incident. 15.3. Additional Requirements for Personal Data. With respect to any Personal Data in the possession or under the control of Hexagon, which does not include Customer Data within the Customer Cloud Environment, and in order to protect Personal Data from unauthorized access, destruction, use, modification or disclosure, Hexagon shall: 15.3.1. Develop, implement, and maintain reasonable security procedures and practices appropriate to the nature of the information to Personal Data from unauthorized access, destruction, use, modification, or disclosure; and 15.3.2. Develop, implement and maintain data privacy and security programs with administrative, technical, and physical safeguards appropriate to the size and complexity of Hexagon's business and the nature and scope of Hexagon's activities to protect Personal Data from unauthorized access, destruction, use, modification, or disclosure. 16. WARRANTIES, DISCLAIMER AND INDEMNITIES. 16.1. During the Cloud Term, Hexagon does not warrant the Cloud Application(s) purchased by Customer will meet the Service Level specified in the applicable Cloud Services Schedule. The Cloud Program may be subject to limitations, delays and other problems inherent in the use of the internet, electronic communications, and Customers' IT infrastructures. Hexagon will not be responsible for any delays, delivery failures, or other damage. 16.2. Hexagon does not warrant the Cloud Application(s) and Third Party Software Products accessed via Cloud Services will perform substantially in accordance with the Documentation provided. To the extent an Error should be discovered, Customer shall report such Error to Hexagon as provided in Section 8 of the Cloud Program Conditions and Hexagon will respond as provided therein. 16.3. Cloud Services will use industry standard Virus detection software to avoid transmission to the Customer, its Affiliates, any Viruses (except for any Viruses contained in Customer Data uploaded or Onboarded by Customer). 16.4. Hexagon does not warrant the Cloud Program (to the extent accessed by Customer under the Master Agreement) will meet the Customer's or any of its Affiliate's requirements or that it will run uninterrupted or be Error free. Customer and its Affiliates are responsible for the results obtained from the use of the Cloud Program. 16.5. The warranties set forth herein are in lieu of all other warranties, expressed or implied, and represents the full and total warranty obligation and/or liability of Hexagon 17. ACCESS TO THE MASTER AGREEMENT BY CUSTOMER'S AFFILIATES. Hexagon Principle Contracting Document S108302019PCD Page 34 If an Affiliate accesses or utilizes any or all components of the Cloud Program, the Affiliate shall be deemed to have agreed to be bound by the terms and conditions of these Cloud Program Conditions. The Affiliate, in accessing the Cloud Program (or any part thereof), and Customer, in permitting the Affiliate's access, each represent to Hexagon they have entered into an agreement by which Affiliate is permitted to use the Cloud Program is bound to the terms herein. Except for Affiliates and employees of Affiliates, no other person, including any third parties not authorized by Hexagon, may access the Cloud Program or be provided with Credentials. END OF EXHIBIT D Hexagon Principle Contracting Document S108302019PCD Page 35 EXHIBIT E SUBSCRIPTION TERMS AND CONDITIONS These Subscription Terms and Conditions ("Subscription Terms"), govern the licensing and support for the Subscription. DEFINITIONS. All capitalized terms not otherwise defined herein shall have the meaning set forth in Exhibit G (Common Terms Glossary). 2. SERVICES PROVIDED. 2.1 Access. Subject to an Order for a Subscription License Sale and these Master Terms, including Exhibit A (End User License Agreement), Hexagon will make the Subscription Licenses available to Customer for Customer's use during the Subscription Term. Any renewal or extension of the Subscription Term shall be subject to such terms and product components as reflected in the applicable renewal or extension Quote issued by Hexagon (the "Renewal Quote"). Customer acknowledges and agrees that Customer shall compensate Hexagon for Customer's continued use of a Subscription after expiration or termination of a Subscription Term, at a rate equitably and proportionately calculated based upon the Renewal Quote and based upon the period of such extended use; provided that if no Renewal Quote is issued prior to expiration or termination of the Subscription Term, the initial Quote shall be substituted in the calculations set forth in this Section 2.1. 2.1.1 As it pertains to Metered Licenses, the Customer's right to use the Metered Licenses shall end upon the earlier of: (i) expiration of the Subscription Term, or (ii) Customer's use of its allotment of units of service as set forth in the Quote. 2.2 Maintenance and Support. During the applicable Subscription Term, Hexagon will provide maintenance services and support to the Customer for the Subscription Licenses in accordance with Exhibit B (Maintenance Terms and Conditions) of these Master Terms. 2.3 Services. These Subscription Terms only provide for the licensing and support of the Subscription. If the Customer desires for Hexagon to provide Services for implementation, configuration, training, or other work in relation to the Subscription, then Customer may contract with Hexagon pursuant to these Master Terms for Services under a separate Order. 3. INVOICES. Hexagon shall invoice Customer for the full amount set forth in the Quote upon delivery of or access having been provided for the Subscription Licenses identified in the Quote in any environment. To the extent the Quote includes multiple types of Subscription Licenses, Hexagon shall invoice the Customer once the first type of Subscription License is allowed to be invoiced as provided in this section. 4. CUSTOMER OBLIGATIONS. 4.1 Customer Control. Customer's and its authorized Users of the Subscription shall at all times comply with Exhibit A (End User License Agreement). Customer will be solely responsible for administering and monitoring the use of login IDs and passwords provided by Customer to authorized Users pursuant to the Subscription, or by Hexagon on behalf of Customer. Upon the termination of employment of any authorized User, Customer will terminate that individual's login ID and password. Hexagon is not responsible for any damages resulting from Customer's failure to manage the confidentiality of its login ID and passwords and Customer is responsible for any actions arising out of use or misuse of Customer's login IDs. 4.2 Security. Customer shall take commercially reasonable security precautions to prevent unauthorized or fraudulent use of Hexagon IP by Customer, Customer's employees, consultants, agents, or any other third parties authorized by Customer to access the Subscription on Customer's behalf. Hexagon Principle Contracting Document S108302019PCD Page 36 EXHIBIT F COTS Training Program Terms These terms and conditions ("COTS Training Program Terms") govern the provision of the Training Curricula by Hexagon to Customer under a Fixed Price Project Assignment. Any additional terms in a Training Program Statement also apply; and, notwithstanding the order of precedence stated in the Master Terms, but without otherwise modifying such order of precedence, any conflict between these COTS Training Program Terms and any applicable Training Program Statement shall be resolved in favor of the Training Program Statement. 1. DEFINITIONS. Capitalized terms used and not otherwise defined herein have the meanings assigned in the Common Terms Glossary. 2. SCOPE OF TRAINING PROGRAM. Hexagon will provide the Training Curricula specified in the Quote and purchased by Customer, in accordance with and subject to the provisions of these COTS Training Program Terms and the applicable Training Program Statement(s). The Training Program Statements(s) and Quote shall describe the duration and delivery method for the Training Curricula; provided that if no duration is otherwise stated for a Training Curricula delivered by online means, Customer shall cease use thereof twelve (12) months following the date the Order was placed for the Training Curricula. 3. FEES AND PAYMENT. Unless otherwise expressly provided in applicable Training Program Statement(s) corresponding to the Order, fees for Training Curricula delivered by a live instruction method shall be invoiced as and when the Training Curricula is delivered; and, fees for Training Curricula delivered by an online on -demand method shall be invoiced upon first delivery to Customer of the initial ability to access any portion of the Training Curricula. 4. SPECIFIC ONLINE TERMS. 4.1 Assignment of Credentials. For Training Curricula delivered by an online on -demand method, Customer acknowledges and agrees that: each specific student/user must be assigned individual credentials, thereby consuming one of the overall quantity of credentials available to Customer under the terms of the Order, and student/user credentials may not be shared or used by more than one student/user. Upon request, and subject to processing and any requirements of the Third Party Service Provider, credentials may be subject to reassignment to a new student/user and from a student/user no longer requiring access to the Training Curricula. The period of availability of an online on -demand Training Curricula shall not be extended due to delays in Customer's assignment of available credentials or in any reassignment of credentials. 4.2. Use Restrictions. Customer shall comply, and assure all students/users comply, with terms of use of the Training Curricula and the platform through which it is provided, including without limitation, each of the following: the platform and assets associated therewith shall never be used to perform unlawful activity or activity which interferes with networks, systems, or facilities associated with operation of the platform; the platform shall not be used to store, process, or publish threatening, disparaging, or offensive material, or material that constitutes Spam/E- Mail/Usenet abuse or to create a security risk or an infringement of privacy or intellectual property rights; the platform shall not be used for any activity intended to directly or incorrectly circumvent security measures of the Third Party Service Provider or Hexagon; and, the platform shall be used solely within the use requirements of the Third Parry Service Provider and solely for the purpose of consuming the Training Curricula. Hexagon Principle Contracting Document S108302019PCD Page 37 5. OWNERSHIP AND INTELLECTUAL PROPERTY. In accordance with Section 6 of the Master Terms, Hexagon owns all right, title and interest in and to Training Curricula, and any other data and information provided as part of Training Curricula (except for data and information being owned by a third party), and all copies of all or any part thereof, are and shall remain vested in Hexagon. Third parties shall retain any and all IPR in and to their intellectual property that may be provided as part of the Training Curricula, to include without limitation the Third Party Service Provider's retention of intellectual property associated with the platform through which any online on - demand Training Curricula is provided. Customer and its Affiliates shall not attempt to decompile, disassemble, obtain any source code for, or record Training Curricula, in whole or in part. Customer, for itself and its Affiliates and their respective personnel accessing the Training Curricula, acknowledges and agrees the Training Curricula is comprised of trade secrets, proprietary information, and Confidential Information, and that Customer, and its Affiliates shall not use, distribute, copy, record, perform, amend, alter, modify, create derivative works, reverse engineer, exploit, sublicense, or assign the Training Curricula or any component thereof except as expressly permitted by Hexagon. The Customer acknowledges Hexagon shall retain sole custody and control of the underlying online Training Curricula and any documents and information displayed therein. Unless otherwise set forth in the Training Program Statement, Hexagon shall only provide electronic copies of any specified Documentation. Without Hexagon's express, written permission, Customer shall ensure student/user credentials issued to Customer are only assigned and/or used only by Customer's employees. 6. CUSTOMER OBLIGATIONS. Customer shall at all times be responsible for administering and monitoring the use of Training Curricula by its students/users. Training Curricula shall be used solely for Customer's internal training purposes. Upon the termination of employment of any student/user, Customer will terminate that individual's access to Training Curricula. Customer shall be responsible for supplying all components necessary to supply of the Training Curricula not expressly specified in the Training Program Statement as a deliverable by Hexagon. Depending upon the nature and delivery method of the particular Training Curricula, components to be supplied by Customer may include, by way of example only, computers or software for use by students/users, internet connectivity, or training space at the Customer's site. END OF EXHIBIT F Hexagon Principle Contracting Document S108302019PCD Page 38 MUMIN COMMON TERMS GLOSSARY "Acceptable Use Policy (AUP)" means the Acceptable Use Policy identified as such within Exhibit D (Cloud Program Conditions). "Activity" or "Activities" means a single work activity/event or collection of work activities/events by a Party or by both Parties under a specified Task. "Affiliate" means, for business entities, the parent business entity of a Party and any business entities in which a Party or its parent company directly or indirectly holds a controlling ownership interest. "Affiliates" means, for government entities which are Customers, an entity which has entered into an intergovernmental agreement with Customer which: (i) relates to or addresses the subject matter of the Primary Contracting Document; and (ii) was disclosed to, and acknowledged by, Hexagon (A) prior to the Effective Date for any existing intergovernmental agreements, and (B) prior to any renewal date of such Primary Contracting Document for any intergovernmental agreements entered into after the Effective Date. "Control" for the purposes of this definition means that Customer owns in excess of fifty percent (50%) of the ownership interest of the Affiliate or owns a majority of the voting shares of the Affiliate. For purposes of Section 9 in the General Terms and Conditions, an Affiliate is not a third party. "Authorized Cloud User" means an individual user authorized by the Customer to use an entire Cloud Program on behalf of the Customer and for whom an account is set up by which the Authorized Cloud User can utilize Cloud Services Support and log Cloud service requests and Product Change Requests. "Auxiliary System License" means the license(s) of Software Product made available by Hexagon for select Software Products to augment Production System Licenses. Each Auxiliary System License requires a corresponding Production System License and the term of the Auxiliary System License shall not exceed the term of the applicable Production System License. "Beta Software" means any version of Software prior to a generally available commercial release of such Software. "Business Day" means any day other than a weekend or public holiday in the country listed on the Quote. "Business Hour" means an hour occurring during a Business Day and during the generally recognized eight (8) working hours comprising the Business Day at the Customer's location. "Catastrophic Event" means a rare circumstance in which mass casualties and/or significant property damage has occurred or is imminent (e.g. September 11th, hurricanes, earthquakes greater than 6.1 on the Richter scale). "Change Order" means a document executed or accepted in writing by both Parties that modifies the scope, price, milestones, and/or project schedule of an Order. "Client" means a computing device connected to a Server. "Cloud Anniversary" means the anniversary of the date on which Hexagon provided the License Keys to Customer. "Cloud Application(s)" means the Hexagon software applications, including without limitation application programming interfaces made available by Hexagon through the Cloud Portal as part of the Cloud Program. "Cloud Consulting Services" means Services that relate to the Cloud Program including, but not limited to, implementation, configuration, customization, data conversion, Onboarding, design, training, and or enhancement of the Cloud Program. "Cloud Cutover" means the point in time when Customer first uses the Cloud Program for its generally marketed purpose. Hexagon Principle Contracting Document S108302019PCD Page 39 "Cloud Development Environment" means a logical group of virtual or physical computers comprised within the Cloud Environment to which the Customer will be provided with access and use for the limited purpose of making modifications, as specifically permitted herein, to the Cloud Application. For purposes of clarity, the Cloud Development Environment cannot be used in production or for training purposes. "Cloud Environment" means the collection of remote environments provided to Customer on which the Cloud Application(s) operates that is supported by Hexagon. "Cloud Optional Services" means those certain Hexagon Software Products that provide ancillary functionality or capability to the Cloud Applications, including, but not limited to, interfaces and custom forms and functionality. Unless specific Cloud Optional Services are identified in the Quote with a corresponding purchase commitment from Customer, Cloud Program does not include Cloud Optional Services. "Cloud Portal" means the website through which Customer accesses and uses the Cloud Program. The Cloud Portal provides access to the Cloud Program according to Customer's rights, and further provides access to additional Cloud Services, as made available by Hexagon. "Cloud Program" means the combination of Cloud Services, Cloud Application(s), Local Software, Third Party Software Products, and Cloud Optional Services provided pursuant to the Order Documents. The components of the Cloud Program are specifically identified in the Quote and for purposes of this definition shall mean only those components and not any other components not specifically listed in the Quote. "Cloud Program Fees" means, collectively, any of the fees payable by Customer to Hexagon for the Cloud Program (or any part thereof). Cloud Program Fees shall be in the amount described in the Quote and/or Cloud Services Schedule, and shall be invoiced on an annual basis, except to the extent otherwise expressly provided in the Primary Contracting Document or the Cloud Services Schedule. "Cloud Program Sale" means a type of Order providing access to the Cloud Program for the Cloud Term to the Customer. While a Cloud Program Sale may be the subject of a Quote, SOW, Order Documents, or other instruments which simultaneously address other types of sales, a Cloud Program Sale shall nevertheless always be construed as a separate Order under the Master Terms, i.e. not part of a combined Order along with a sale of Software Product licenses, Services, or other items. "Cloud Program Start Date" means the date on which the first License Key(s) are provided to the Customer. For Cloud Program Fees purposes, Cloud Program use by Customer will be assumed to be for the entire Month in which the Cloud Program Start Date falls regardless of the actual date in such Month that access to the applicable Cloud Application began. "Cloud Service Request" means a request made to the first level support service to diagnose and address an Error in a Cloud Application or to report the purchased Cloud Application(s) is not Available. "Cloud Services" means the services, service levels, Cloud Services Support, Customer Cloud Environment, and Third Party Service Provider's hosting services (which are more particularly described in the Cloud Services Schedule(s) attached to the Quote), for Cloud Application(s), Cloud Optional Services, and Third Party Software Products and ordered by the Customer. "Cloud Services Schedule" means a document(s) titled "Cloud Services Schedule" attached to the Quote containing additional details regarding the Cloud Services being provided to Customer with respect to the applicable Cloud Program components purchased by Customer, including, but not limited to: (i) Customer Data backup frequency, and, (ii) level of redundancy for the Customer Cloud Environment. "Cloud Services Support" means the service specified as such in the Cloud Services Agreement through which Customer can report Cloud Service Requests and Product Change Requests. "Cloud Staging Environment" or "Cloud Testing Environment" means a logical group of virtual or physical computers comprised within the Cloud Environment to which the Customer will be provided with access and use for the limited purpose of testing modifications, as specifically permitted herein, to the purchased Cloud Application(s). For purposes of clarity, the Cloud Staging Environment cannot be used in production or for training purposes. Hexagon Principle Contracting Document S108302019PCD Page 40 "Cloud Term" means the duration of a Cloud Program Sales Order. "Cloud Training Environment" means a logical group of virtual or physical computers comprised within the Cloud Environment to which the Customer will be provided with access and use for the limited purpose of training users on the operation and use of the purchased Cloud Application(s). For purposes of clarity, the Customer shall only be entitled to a Training Environment as part of the Cloud Program if such is purchased by Customer and noted on the Quote. "Confidential Information" means any data or information, tangible or intangible, disclosed or made available by either Party (the "Disclosing Party") to the other Party (the "Receiving Party") that the Disclosing Party considers confidential or proprietary and is not generally known in the industry or to competitors of the Disclosing Party and which shall include: (i) tangible information marked by the Disclosing Party with the word "Confidential" or otherwise identified by an appropriate stamp or legend indicating its confidential nature; (ii) Confidential Information disclosed orally or visually and identified by the Disclosing Party as confidential when disclosed, and confirmed by the Disclosing Party in a written notice within thirty (30) days following disclosure, which notice shall include markings similar to those outlined above; and (iii) all other information that, notwithstanding the absence of markings or designations, would be understood by the Parties, exercising reasonable business judgment, to be confidential. The term Confidential Information does not include information that: (i) is or becomes available in the public domain through no act of the Receiving Party; (ii) has been received on a non -confidential basis from a third party without breach of the Primary Contracting Document, where the Receiving Party has no reason to believe that such third party is bound by any confidentiality obligation to the Disclosing Party; (iii) was developed independently by the Receiving Party without reliance on the disclosed Confidential Information, provided that such independent development can be substantiated; or (iv) is confirmed by the Disclosing Party as not being confidential in writing. "Core" means a physical processor on a computer Server that can respond to and execute the basic instructions that drive the computer. A Central Processing Unit ("CPU") may have one or more Cores, and a given Server may have multiple CPU sockets that may each contain multiple Cores. "COTS" means commercial off the shelf Intellectual Property in the form generally released and distributed to Hexagon's customers and not including any functionality or features requiring source code changes. "COTS Documentation" means commercial off the shelf Documentation in the form generally released and distributed to Hexagon's customers and not including or requiring changes thereto. "Coverage Period" means the period of performance of Maintenance Services with respect to a Covered Product, as stated in the Order Documents. Coverage Periods may differ for discrete Covered Products. "Coverage Period Anniversary" means, in the case where the Coverage Period is greater than one (1) year, the anniversary of the date on which the Coverage Period commenced. "Covered Products" means collectively, Covered Software Products and Covered Third Party Products "Covered Software Product(s)" means Software Product(s) identified in the Order Documents as software for which Maintenance Services are to be provided by Hexagon. Covered Software Products shall not include Third Party Software or any Cloud Program. "Covered Third Party Products" means Software Product(s) identified in the Order Documents as Third Party Software for which Maintenance Services are to be provided by Hexagon. Covered Third Party Products shall not include Software Products or any Cloud Program. "Credentials" means the unique log -in identifier entered via the Cloud Portal by which a person could access the Cloud Program. "Customer" means the non -Hexagon party to the Primary Contracting Document. Hexagon Principle Contracting Document S108302019PCD Page 41 "Customer Cloud Administration" means providing User's access to the Cloud Application(s) purchased by Customer, managing User accounts, providing Credentials to Users, and any system administration beyond User interface. "Customer Cloud Environment" means a logical group of virtual or physical computers comprised within the Cloud Environment and Local Environment to which the Customer will be provided with access and use of as part of the Cloud Program. Except as may be otherwise set forth on the Quote, including the purchase of other Cloud Optional Services, including but not limited to a Training Environment, a Customer Cloud Environment consists of a Cloud Development Environment, Cloud Staging Environment, and Production Environment. "Customer Data" means all electronic data or information: (i) provided by Customer to Hexagon in connection with the Deliverables provided pursuant to an Order; and/or (ii) created by Customer and/or submitted to the Cloud Environment by Customers, Users, and/or Authorized Cloud Users. "Customer Data" shall not mean data which (i) is not peculiar to Customer, and/or (ii) is of value to the general implementation, development, operation, or use of Hexagon products or services for the benefit of other customers. For the avoidance of doubt, Customer Data shall not include the Cloud Application(s), Software Products, Cloud Optional Services, Documentation written by Hexagon, and any other data and information provided as part of the Cloud Program or constituting a Hexagon Deliverable. "Customer Specified Data Center(s)" means a data center used in the provision of a Cloud Environment, whose location has been specified by the Customer and agreed to by Hexagon and identified in the Quote. Additional Cloud Program Fees may be payable for a Customer Specified Data Center. "Customized Software" means those Services Deliverables that are software or computer code, whether in source code or object code. "Cutover" means the point in time in which a Software Product(s) is first used by User for its generally marketed purpose. "Data Center(s)" means the data center(s) from which the Cloud Program (or part thereof) will be stored as determined by Hexagon or its Third Party Service Provider, "Defect" means a reproducible instance of an adverse and incorrect functioning of a Software Product or Cloud Application that impacts the ability to use functionality intentionally integrated in the design of the Software Product, assuming proper usage of the Software Product in its required operating environment. Defects are further classified into four levels as follows: Level ► Level One i Level Two ► Level Three ► Level Four Hexagon Principle Contracting Docurnenl S108302019POD Impact of Defect No workaround available and either. ► Productive use prohibited, or ► Aborts. No workaround available and either. ► Primary purpose compromised, or ► Productive use significantly impacted ► Productive, but incomplete operation Level Three Defects generally have a workaround or do not otherwise substantially impair productive use. ► Defects not qualifying as Level One, Two, or Three, including defects of a cosmetic nature and defects not materially limiting complete productive use Page 42 Customer shall classify a Defect in accordance with the foregoing; provided that, Hexagon shall reclassify the Defect as appropriate following its review thereof. "Deliverable(s)" means all Services Deliverables, software, hardware, Cloud Programs, and other items delivered or to be delivered by Hexagon to Customer and identified in the Order. "Documentation" means, whether in electronic or printed form, User's Guides, Reference Guides, Administrator's Guides, Configuration Guides, and Help Guides made available at the support website (httos_I/support.hexagonsafetyinfrastructure.com) for Software or Cloud Applications provided by Hexagon to the Customer. Not all of the types of Software or Cloud Applications are provided with Documentation or with similar Documentation. "Effective Date" means the date and time the last Party has executed the Primary Contracting Document. "Emergency Maintenance" means all maintenance performed when a Cloud Service Request demands immediate, unplanned attention, as reasonably determined by Hexagon. "Error" means a Defect with a purchased Cloud Application, Cloud Optional Service, or Third Party Software Products causing a purchased Cloud Application to fail to materially conform to its designed functionality or Documentation. Errors are further classified into the same four levels as corresponding to the definition for "Defect," "EULA" means the certain Hexagon End -User License Agreement set forth in these Master Terms as Exhibit A and/or that delivered with Software and which must be accepted prior to Software installation. "Exchanged Product" means a later released Software Product which the Customer will receive pursuant to its Maintenance Contract and supplant the Replaced Product "Fixed Price Project Assignment" means a type of Order where Hexagon will provide Services and/or Software licenses for a fixed price. "Hexagon" means Intergraph Corporation through its Safety & Infrastructure division. "Hexagon iP" means Hexagon or Hexagon Affiliate developed, created, or prepared Intellectual Property, "Installation Guide" means a computer file in a Microsoft Word or Adobe PDF document or a text file that contains information a User may need to install or operate a Software Product. "Intellectual Property" or "IPR" means all forms of intellectual property including, but not limited to, patents, trademarks, copyrights, trade secrets, methodologies, logos, techniques, processes, know-how, formulae, algorithms, logic designs, screen displays, schematics, source and object code computer programs or software, documentation, mask work rights, design, ideas, product information, inventions and improvements thereto (whether or not patentable), and all works of authorship fixed in any medium of expression (including any form of online, digital, or electronic medium), whether or not copyrightable and whether registered or not, "Lapse" means an occurrence of any period of time, regardless of duration, during which (I) a Covered Product is not the subject of an active Order for Maintenance Services or other Maintenance Contract and an active Coverage Period, and/or (ii) payment is past due to Hexagon under a Maintenance Contract. Extension of a Coverage Period and/or payment to Hexagon after the occurrence of a Lapse shall not negate a Lapse, absent Hexagon's express written waiver, "License Key(s)" means certain unique data string(s) verifying authorized access to the Cloud Application(s), which are purchased by the Customer and provided by Hexagon, as set forth on the Quote. "Local Environment" means the collection of environments provided and supported by Customer (e.g. providing System Equipment, etc.) in which the Local Software operates. "Local Software" means software applications incidental to the Cloud Program which are designed to operate natively on devices outside the Cloud Portal and in the Local Environment. Hexagon Principle Contracting Document 8106302019PCD Page 43 "Maintenance Services" means only those services described in the document titled "Maintenance Terms and Conditions for Software" provided by Hexagon with respect to Software and other Deliverables licensed to Customer and identified in the Order Documents as the subject of Maintenance Services. "Material Adverse Effect" means a change that individually or collectively in aggregate with other changes has the impact of (i) negatively and materially reducing the Customer's and/or its Affiliates and/or its/their Authorized Cloud Users' or Users' access and/or usage rights in respect of the Cloud Program and which render the Cloud Program unusable for its primary intended purpose or (ii) making the Cloud Program materially less secure which results in increased risk to Customer Data or other data belonging to other Hexagon customers. For clarity, a Material Adverse Effect is a condition which would render the Cloud Program un-usable or materially less secure for intended users generically, and not merely as a result of individual characteristics associated with Customer or its specific implementation or operation. "Maintenance Contract" means a contract under which Hexagon provides Maintenance Services to Customer in relation to Covered Products and under which Customer is to compensate Hexagon therefor. "Metered License" means a specific type of Subscription License that allows the Customer to use the Subscription License up to the number of hours set forth in the Quote during the Subscription Term. For reference, a Subscription License that is a Metered License shall have the word "Metered" in the Software Product name and/or have the letters "MTR" at the end of the product number for the Software Product instead of the other identifiers corresponding to an unmetered Subscription License referenced in its definition. "Modern Release" means a version of a Software Product published by Hexagon no more than eighteen (18) months prior to Customer's first use thereof in Production. "Month" means, unless otherwise stated in the applicable provision, a calendar month. "Network Requirements" means (i) the minimum requirements, including but not limited to software and/or hardware, internet connection, latency or other requirements, which must be met by Customer in order to access the Cloud Portal and use the Cloud Program; and (ii) network recommendations to the Customer which describe general and specific recommendations for the network connection requirements of the Cloud Program in order to enable the Cloud Program to function as designed. The Network Requirements may be updated from time to time and Customer will be notified of such update via posting in the Cloud Portal or as otherwise determined by Hexagon. "Notice to Proceed" shall mean a written document issued by Customer notifying Hexagon to commence work as specified by an Order. "Off boarding" or "Offboarded" means the process for offboarding the Customer Data (or part thereof) from the Customer Cloud Environment and relocating or facilitating relocation of Customer Data to another Customer -designated location. "Onboarding" or "Onboarded" means the process of loading Customer Data into the Customer Cloud Environment. "Onsite Fee" means a fixed fee encompassing Hexagon's travel expenses for an individual trip (an individual trip means to travel from the Hexagon resource's primary duty station in furtherance with Order and lasting no more than five (5) consecutive days). "Order" means each individual purchase transaction in which the Parties engage, as evidenced by Order Documents. "Order Documents" shall mean written documents, the terms of which include Hexagon's commitment to provide specific products, licenses, and/or services at a specified price, subject to the terms and conditions of the Primary Contracting Document. Order Documents may consist of a single document executed by the parties or a combination of documents that together form an Order. No Order shall be effective unless executed by both Parties. Hexagon Principle Contracting Document S108302019PCD Page 44 "Perpetual License" means a type of license for a Software Product which allows the User to use the Software Product in perpetuity so long as the User does not otherwise violate the terms of the EULA. For reference, a Perpetual License on a Quote is denoted by its absence of either the terms "Subscription," "SaaS," or "Metered" and/or the absence of the letters "SU" or "MTR" at the end of the Software Product number or the letters "HCL" at the beginning of the Software Product number. "Personal Data" means data, including but not limited to criminal justice information, and other information which corresponds to a living individual person defined to be Personal Data under the applicable Personal Data protection laws of the Customer's jurisdiction. "Planned Maintenance" means maintenance planned and communicated in advance by Hexagon to Customer for the maintenance of the Cloud Program. "Primary Contracting Document" means the contract document accepted by the Parties which references and incorporates this Terms Glossary and/or references and incorporates a document to which this Terms Glossary is an exhibit or attachment. "Primary License" means the license(s) of the Software Product provided to Customer for general production use as authorized by the EULA. "Product Change Request" means a request for additional functionality or modification to the purchased Cloud Application(s) or Covered Products. "Production" means, as applicable, where a Subsystem or Cloud Program is used in production/operation with an aim to accomplish one or more of its ultimate intended purposes. Operation solely for testing or training is not Production. "Production Environment" means a logical group of virtual or physical computers comprised within the Cloud Environment to which the Customer will be provided with access and use the purchased Cloud Application(s) in production and for its generally marketed purpose. "Production System License" means the license(s) of Software Product provided to User for general production use. "Product -Specific Terms" modify the EULA, and (ii) in the event of a conflict between the EULA and Product -Specific Terms, Product -Specific Terms shall govern for the applicable Software. In the event of a conflict of terms between the EULA, any prior Product -Specific Terms (including any product -specific terms delivered in the form of an addendum to the EULA), and later Product -Specific Terms, the later Product -Specific Terms shall take precedence over the EULA and any prior Product -Specific Terms regarding the subject Software. "Purchase Order" or "PO" means a document issued by Customer to Hexagon to authorize the delivery of certain Services, Deliverables, or Cloud Programs. "Quote" means a document issued by Hexagon reflecting Services, Maintenance Services, Deliverables, and/or Cloud Programs, which Hexagon offers to provide Customer, as well as the prices and fees therefor, the Customer's name and location, and any applicable Cloud Services Schedule. To the extent any document or information is identified in the Quote with the intention of it being incorporated into the Quote, it will form part of the Quote. "Replaced Product" means an earlier Software Product which will be replaced pursuant to a Maintenance Contract for an Exchange Product. "Security Incident" means an event or set of circumstances resulting in a compromise of the security, confidentiality, or integrity of Customer Data under Hexagon's control. Examples of Security Incidents include: (i) security breaches to Hexagon's network perimeter or to internal applications resulting in compromise of Customer's Data; (ii) severe degradation of, Hexagon's security controls, methods, processes or procedures that result in compromise of the security, confidentiality or integrity of Customer Data; and (iii) the unauthorized disclosure of Customer Data. Hexagon Principle Contracting Document S108302019PCD Page 45 "Server" means a computer or computer program which manages access by Clients to a centralized resource or service in a network. "Server -based Software Product" means Server -based software that is accessed by one or more Clients. "Services" means the work, services, projects, assignments, or tasks Hexagon shall perform pursuant to an Order. Services do not include Maintenance Services or Cloud Programs. "Services Deliverable" means any data, document, information, Customized Software, Third Party Software, or material provided to Customer as a product of Hexagon's performance of Services pursuant to the Primary Contracting Document. Cloud Programs are not Service Deliverables. "Software" means the software owned by Hexagon or an Affiliate and Third Party Software that is licensed to Customer. For the avoidance of doubt, Cloud Programs and their contents are not "Software" as that term is used herein. "Software License Sale" means a type of an Order that involves only the sale of Perpetual Licenses from Hexagon to Customer. This type of Order does not include Services or Cloud Programs. "Software Product" means the Hexagon software product(s) identified in the Order Documents, which includes (i) any associated Hexagon files or media with which the software is provided, (ii) any associated templates, data, printed materials, and "online" or electronic Documentation, and (iii) any Updates or Upgrades of such Software Products not made the subject of a separate license agreement. The term Software Products shall not include, and no rights of use are granted to User for, third party components, Hexagon products, or dependencies unnecessary to operate products made the subject of the Order Documents, but incidentally delivered within the same files or media. Software Product shall not mean any Third Party Software. For the avoidance of doubt, Cloud Programs and their contents are not "Software Products" as that term is used herein. Software Products are subject to all of the terms and conditions of the EULA which the Parties agree will apply to the same; and in the absence of such agreement, then the terms of the EULA provided with the Software Product. "SOW" means a statement of work setting forth the scope of Services being provided pursuant to an Order, "Subscription" means the collection of Subscription License(s) identified on the Quote and or purchased by the Customer. "Subscription License" means a particular type of license to a Software Product that allows a Customer to use the Software Product for a specified period of time identified in the Quote. For reference, a Software Product that is a Subscription License shall have the word "Subscription" in the Software Product name and/or have the letters "SU" at the end of the product number for the Software Product. "Subscription License Sale" means a type of an Order that involves only the sale of Subscription Licenses from Hexagon to Customer. This type of Order does not include Services or Cloud Programs. "Subscription Term" means the period of time during which Users are authorized to use the Subscription License as set forth on the applicable Quote beginning on the date the Subscription Licenses are provided to the User or the User is provided license keys or access to the Subscription License, unless otherwise noted in the Order Documents. "Subsystem" means a Hexagon solution that is designed to provide a specific capability independent of the procurement of any other Subsystem. Hexagon's computer aided dispatch system ("I/CAD"), records management system ("RMS"), field based reporting ("FBR"), G/Technology (G/Tech), In/Service and mobile for public safety ("MPS") are each an example of a Subsystem. "Supplementary License" means a license(s) of the Software Product which is made available by Hexagon for select Software Products to augment Primary Licenses for special purposes. Each Supplementary License requires a Primary License and the term of the Supplementary License shall not exceed the term of the applicable Primary License. Hexagon Principle Contracting Document S108302019PCD Page 46 "System" means a physical or operational location where the Software Product resides and operates on an individual server or where a single operational identification number ('Site ID") has been assigned by Hexagon. "System Equipment" means all computer -related hardware, including but not limited to, servers, workstations, cables, mice, keyboards, cameras, and SAN's; operating system software; database software; and other third party software. "Task" means an Activity or combination of Activities of any nature whether tangible or intangible, whether onsite or remote, or an event, as further identified in an SOW. "Task Acceptance" means the event when the Task Acceptance Criteria has been satisfied in accordance with the Task Acceptance Process. "Task Acceptance Criteria" means the criteria by which a Task will be evaluated for completion as described in an SOW. "Task Acceptance Process" means the process by the Customer and Hexagon verify completion of the Task Acceptance Criteria as further described below. Once Hexagon believes the Task Acceptance Criteria has been successfully completed, Hexagon shall submit for execution by Customer's project manager a sign -off form in substantial conformity with Exhibit C, "Project Deliverable Sign -off Form." Within ten (10) calendar days of receipt of the applicable Project Deliverable Sign -off Form for the completed milestone or Task, Customer's project manager will either: (i) execute the Project Deliverable Sign -off Form provided by Hexagon, or (ii) provide a written description of all deficiencies to Hexagon. If Customer fails to perform either action identified in the preceding sentence within ten (10) calendar days, or if the Deliverable, including the Software contained in the Fixed Price Project Assignment Order, is placed into production or utilized in a live environment, then the Task or milestone shall be deemed accepted. "Term" means the duration of performance under the contract into which this Terms Glossary is incorporated by reference. "Third Party Service Provider" means the third party service provider with whom Hexagon enters into a subcontract with respect to the hosting of a cloud platform, Training Curricula, and/or other services to provide an element of the Cloud Program, Training Curricula, or other service to Customer (if applicable) on behalf of Hexagon. "Third Party Software" means computer software or other technology in which any person or entity, other than Hexagon or Hexagon's Affiliate, has any right, title or interest, including any restrictions or obligations (such as obligations to obtain consents or approvals and restrictions that may be eliminated only by obtaining such consents or approvals) applicable to the computer software or technology, but does not include software embedded in the Software Products by license from third parties. The use of Third Party Software is subject to all of the terms and conditions of the Third Party Terms. "Third Party Software Products" also means, where applicable, pre -requisite third party software products used by Hexagon in order for Customer to receive other components of the Cloud Program or licensed by Hexagon and used by the Customer to use Cloud Application or Cloud Optional Services. "Third Party Terms" means for certain Third Party Software additional terms and conditions provided with the Order Documents and/or cited in the Use Terms, or otherwise made available to the Customer or any User. "Time and Materials Project Assignment" means Hexagon will perform the Services set forth in an Order on an hourly basis until the project is either completed or the authorized hours are exhausted, whichever comes first. "Training Curricula" means one or more training classes or resources provided by Hexagon to Customer as a service over a limited time period. "Training Program Statement" means document(s) titled "Training Program Statement," attached to the Quote and containing additional details regarding the Training Curricula parts being provided to Customer, Hexagon Principle Contracting Document S108302019PCD Page 47 including, but not limited to. whether the training is provided live on -site, live but remotely, or by way of recorded or static online content; and, certain other pertinent details; provided that "Training Program Statement" may alternatively refer to only those specific terms of an SOW containing additional details regarding Training Curricula being provided to Customer, "Update" means any Upgrade, modified version, fix, patch and/or update of the Software Product. Updates not meeting the definition of Upgrades are subject to all of the terms and conditions of the EULA provided with User's then current version of the Software Product. "Upgrade" means each new release of the Software Product. Upgrades require a full installation and may be provided with a separate EULA. Any EULA delivered with the Upgrade will supersede any EULA associated with prior releases of the Software Product. "User" means Customer or an individual employed by Customer and authorized by Hexagon to use a particular Software Product, Cloud Application, Third Party Software Product,. or Cloud [optional Services on behalf of the Customer. A User may also include Customer's contractor who requires temporary use in order to provide services on Customer's behalf. A person can only be authorized and a User if the person is an employee or designee of Customer and Customer has purchased the requisite number of licenses, or in the case of Cloud Programs, the requisite number of License Key(s) to provide Credentials for that User, "Use Terms" means the Hexagon Product Usage Policy and Product Specific Terms accessible from https:/Nvww.hexagonsefetyinfra_structure.com/-Imedia/Legal/Hexapon[SI/Lacenses/LLP/LLP 08-2019 pdf which are incorporated herein. For purposes of clarity, the Use Terms corresponding to the date of the Order shall apply to that specific Order and the Software provided thereunder. "Version Limitation i" is a status reached by a Software Product on the earlier of the (i) the third anniversary of the Customer's first operation of that Software Product in a live production environment or (ii) the fifth anniversary of Hexagon's first actual delivery of the Software Product to the Customer for implementation; provided that each time Customer upgrades the version of the Software Product used in production to a Modern Release, a reset shall occur, such that Version Limitation I shall thereafter be reached upon the third anniversary of the Customer's first operation of such Modern Release in a live production environment. "Version Limitation II" is a status reached by a Software Product on the earlier of (i) the fourth anniversary of the Customer's first operation of that Software Product in a live production environment or (ii) the sixth anniversary of Hexagon's first actual delivery of the Software Product to the Customer for implementation; provided that each time Customer upgrades the version of the Software Product used in production to a Modern Release, a reset shall occur, such that Version Limitation II shall thereafter be reached upon the fourth anniversary of the Customer's first operation of such Modern Release in a live production environment. "Version Limitations" means, separately and collectively, limitations on Services to be provided hereunder based upon a Covered Product reaching Version Limitation I and/or Version Limitation 11. "Virus" means any thing or device (including any software, code, file or program) which may: (i) prevent, impair or otherwise adversely affect the operation of any computer software, hardware or network, any telecommunications service, equipment or network or any other service or device; (ii) prevent, impair or otherwise adversely affect access to or the operation of any program or data, including the reliability of any program or data (whether by rearranging, altering or erasing the program or data in whole or part or otherwise); or (iii) adversely affect the user experience or security, including worms, Trojan horses, viruses and other similar things or devices. "Work" means, as applicable, the performance or providing of Services, Maintenance Services, or Cloud Services. "XML Files" means the XML (Extensible Markup Language) files generated by the Software Product, where applicable. Hexagon Principle Contracting Document S108302019PCD Page 48 "XSL Stylesheets" means the XSL (Extensible Stylesheet Language) presentation of a class of XML Files which, when included with the Software Product, describe how an instance of the class is transformed into an XML (Extensible Markup Language) document that uses the formatting vocabulary. END OF EXHIBIT G Hexagon Principle Contracting Document S108302019PCD Page 49 EXHIBIT H CHANGE ORDER TEMPLATE Hexagon Principle Contracting Document S108302019PCD Page 50 CHANGE ORDER / CHANGE REQUEST CUSTOMER NAME: CUSTOMER ADDRESS: HEXAGON ENTITY: DATE: CHANGE ORDER NUMBER: CHANGE ORDER TITLE: ORIGINAL PO I CONTRACT NUMBER: CURRENT CONTRACT VALUE: REVISED CONTRACT VALUE: CHANGE ORDER PRICE: CURRENCY: OTHER HEXAGON INFORMATION: QUOTE NUMBER: QUOTE & CHANGE REQUEST EXPIRATION DATE PROJECT MANAGER: SALES CONTACT: PROJECT NUMBER: Hexagon Safety & Infrastructure U.S. Dollars HEXAGON S/s Flo TYR INFRASTRUCTL RE Includes Extended Warranty, excludes taxes Includes Extended Warranty, excludes taxes WHEREAS, the customer named above (hereafter "Customer") and the Intergraph Corporation d/b/a Hexagon Safety & Infrastructure (hereafter "Hexagon") have entered into the agreement named above for products and/or services (hereafter "Agreement); WHEREAS, the Customer and Hexagon desire to amend the Agreement, as set forth below in this Change Order/Change Request (hereafter "Change Order" or "Change Request"), in consideration for good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged; NOW THEREFORE, the parties intending to be legally bound, hereby agree as follows: L DESCRIPTION OF CHANGE: This Change Order makes the following revisions to this contract: The detailed technical or functional revisions to the contract are described below or in the separately attached Statement of Work (SOW): Change Order delivery details Delivery date Handling priority Acceptance criteria Required deliverables by Customer Documentation and Training Changes to contract schedule Guarantee and Warranty changes Liability and reliability changes if any Milestone payments as a result of this change order are revised as follows: Page 1 of 4 Check One r This Change Order does affect the contract value. All other Terms and Conditions remain unchanged and all Intellectual Property Rights covered by this Order/Request remain with Intergraph. F- This Change Order does not affect the contract value. Funds in the Customer Credit Balance may be used toward the purchase of future Intergraph software or services. All other Terms and Conditions remain unchanged and all Intellectual Property Rights covered by this Order/Request remain with Intergraph. Page 2 of 4 ll. CHANGE ORDER DETAILS Items Added to Contract: Contract Line Item# ITEM DESCRIPTION Part # CITY UNIT COST TOTAL COST Total of Items Added: Maintenance (or Extended Warranty) of Items Added Above • (if applicable) Contract Line Item# ITEM DESCRIPTION Part # CITY UNIT COST TOTAL COST Total Software Maintenance: Items Removed from Contract: Contract Line Item# ITEM DESCRIPTION Part # CITY UNIT COST TOTAL COST Sub -total of Items Removed: Add Back One-time System Discount of Items Removed (if applicable): Total of Items Removed (Project Credit were applicable) Maintenance (or Extended Warranty) of Items Removed Above • (if applicable) Contract Line Item# ITEM DESCRIPTION Part # CITY UNIT COST TOTAL COST Total Software Maintenance: _ Ill. SUMMARIES: CHANGE ORDER SUMMARY Additions: Removals: Total Change Order Price: Customer Credit Balance Balance after C/O Adjustments: Balance after C/O 1: Page 3 of 4 IV. CHANGE ORDER APPROVAL: IN WITNESS WHEREOF, the parties hereto have signed this Change Order/Change Request as of the date written above. APPROVED BY: APPROVED BY: APPROVED BY: Business Unit: Public Safety Operations_ Hexagon Safety and Infrastructure Authorized Signature Hexagon Safety and Infrastructure Customer Authorized Signature Date: Date: Date: This Agreement may be executed in one or more counterparts, each of which shall be deemed to be original, and all of which together shall constitute one and the same Agreement. A signature delivered by facsimile shall be deemed to be an original signature and shall be effective upon receipt thereof by the other party. Page 4of4 Ver 06/09/2017-3 LEE COUNTY SOUTHWEST FLORIDA Advertise Date: Friday, January 19, 2018 Lee County Board of County Commissioners DIVISION OF PROCUREMENT MANAGEMENT Request for Proposal (RFP) NON-CCNA Solicitation No.: UP180081LKD Computer Aided Dispatch Replacement & Associated Solicitation Interfaces (CAD.) , Open Date/Time: 2/20/2018 Time: 2:30 PM Location: Lee County Procurement Management 1500 Monroe Street 4th Floor Fort Myers, FL 33901 Procurement Contact: Lori DeLoach, CPPB Title Procurement Analyst Phone: (239) 533-8881 Email: LDeLoach @leegovxom Requesting runiic jai Pre -Solicitation Meeting: Type: No meeting scheduled at this time Date/Time: n/a Location: n/a All solicitation documents are available for download at www.leegov.com/procurement Electronic bidding is coming! Visit www.lee2ov.com/bid to stay informed RFP 180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 H , ' ' LEE CO V 1V TY 1/19/2018 S 0 U T I I W E S T F L 0 R I D A Notice to Contractor/ Vendor/ Proposer(s) Solicitation# RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) REQUEST FOR PROPOSAL (RFPI Lee County, Florida, is requesting proposals from qualified individuals/films for Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Then and there to be publicly opened and read aloud for the purpose of selecting a vendor to furnish; all necessary labor, services, materials, equipment, tools, consumables, transportation, skills and incidentals required for Lee County, Florida, in conformance with proposal documents, which include technical specifications and/or a scope of work. Those individuals/firms interested in being considered for (RFP) are instructed to submit, in accordance with specifications, their proposals, pertinent to this project prior to 2:30 PM Tuesday, February 20, 2018 to the office of the Procurement Management Director, 1500 Monroe Street, 4th Floor, Fort Myers, Florida 33901. The Request for Proposal shall be received in a sealed envelope, prior to the time scheduled to receive proposals, and shall be clearly marked with the solicitation name, solicitation number, proposer name, and contact information as identified in these solicitation documents. The Scope of Services for this RFP is available from www.leeQov.com/12rocuremen t. Vendors who obtain scope of services from sources other than www.Leeaov.com/procurement are cautioned that the solicitation package may be incomplete. The County's official bidders list, addendum(s) and information must be obtained from www.LeeQov.com/procurement. It is the proposer's responsibility to check for posted information. The County may not accept incomplete proposals. There will be no Pre -proposal Conference for this RFP It has been determined that the specifications and scope of work within this solicitation are adequate to describe the product or services being requested. A pre -proposal conference and site visit has not been scheduled for this solicitation. Questions regarding this Request for Proposal are to be directed, in writing, to the individual listed below using the email address listed below or faxed to (239) 485 8383 during normal working hours. Lori DeLoach LDeLoac1k&,,LeeGov.com Sincerelll xy 7& Mary G. Tucker, CPPO, FCCM, FCCN Procurement Management Director *WWW.LeeGov.Com/Procurement is the County's official posting site UPI 80081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Terms and Conditions Request for Proposal 1. DEFINTIONS 1.1. Addendum/Addenda: A written change, addition, alteration, correction or revision to a bid, proposal or contract agreement. Addendum/Addenda may be issued following a pre-bid/pre-proposal conference or as a result of a specification or work scope change to the solicitation. 1.2. Approved Alternate: Solicitation documents may make reference of specific manufacturer(s) or product(s). These references serve only as a recommendation and a guide to minimum quality and performance. The references are not intended to exclude approved alternatives of other manufacturer(s) or product(s). 1.3. Bid/Proposal Package: A bid/proposal is a document submitted by a vendor in response to some type of solicitation to be used as a basis for negotiations or for entering into a contract. 1.4. Bidder/Responder/Proposer: One who submits a response to a solicitation. 1.5. County: Refers to Lee County Board of County Commissioners. 1.6. Due Date and Time/Opening: Is defined as the date and time upon which a bid or proposal shall be submitted to the Lee County Procurement Management Division. Only bids or proposals received prior to the established date and time will be considered. 1.7. Liquidated Damages: Damages paid usually in the form of monetary payment, agreed by the parties to a contract which are due and payable as damages by the party who breaches all or part of the contract. May be applied on a daily basis for as long as the breach is in effect. 1.8. Procurement Management: shall mean the Director of Lee County's Procurement Management Department or designee. 1.9. Responsible: A vendor, business entity or individual who is fully capable to meet all of the requirements of the bid/proposal solicitation documents and subsequent contract. Must possess the full capability including financial and technical, to perform as contractually required. Must be able to fully document the ability to provide good faith performance. 1.10. Responsive: A vendor, business entity or individual who has submitted a bid or request for proposal that fully conforms in all material respects to the bid/proposal solicitation documents and all of its requirements, including all form and substance. 1.11. Solicitation: An invitation to bid, a request for proposal, invitation to negotiate or any document used to obtain bids or proposals for the purpose of entering into a contract. 2. ORDER OF PRECEDENCE 2.1. If a conflict exists between the "Terms and Conditions" the following order of precedents will apply: 2.1.1. Florida State Law as applied to Municipal Purchasing in accordance with Title XIX, "Public Business", Chapter 287 "Procurement of Personal Property and Services." 2.1.2. Lee County Procurement Management Division Policy and Ordinances 2.1.3. Special Conditions and Supplemental Instructions 2.1.4. Detailed Scope of Work 2.1.5. These Terms and Conditions 3. RULES, REGULATIONS, LAWS, ORDINANCES AND LICENSES 3.1. It shall be the responsibility of the proposer to assure compliance with all other federal, state, or county codes, rules, regulations or other requirements, as each may apply. Any involvement with the Lee County shall be in accordance with but not limited to: 3.1.1. Lee County Procurement Policy Manual 3.1.2. Pursuant to FL § Section 119.071, Public Records, General exemptions from inspection or copying of public records, sealed bids or proposals received by the County. Pursuant to this, solicitation are exempt from Dublic records reauest (s. 119.07(1) and s. 24(a)_ Art. L of the Florida Constitution) until such time as the agency provides notice of a decision or intended decision (pursuant to s. 119.071(2)) or within 30 days after bid or proposal opening, whichever is earlier. 1kF1`180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 3.1.3. Florida Statute 218 Public Bid Disclosure Act. 3.1.4. Florida Statute 337.168 Confidentiality of official estimates, identities of potential bidders, and bid analysis and monitoring. 3.1.5. FL § Section 607.1501(1) states: A foreign corporation may not transact business in the State of Florida until it obtains a certificate of authority from the Department of State. 3.2. Local Business Tax: If applicable, provide with proposal. 3.3. License(s): Proposer should provide, at the time of the opening of the proposal, all necessary permits and/or licenses required for this product and/or service. 4. RFP — PREPARATION OF PROPOSAL 4.1. Proposals must be sealed in an envelope, and the outside of the envelope must be affixed with the label included in the forms section. 4.2. Submission Format: 4.2.1. Required Forms: complete and return all required forms. If the form is not applicable, please return with "Not Applicable" or "N/A" in large letters across the form. 4.2.2. Execution of Proposal: All documents must be properly signed by corporate authorized representative, witnessed, and where applicable corporate and/or notary seals affixed. All proposals shall be typed or printed in ink. The proposer may not use erasable ink. All corrections made to the proposal shall be initialed. 4.2.3. Should not contain links to other Web pages. 4.3. Preparation Cost: 4.3.1. The Proposer is solely responsible for any and all costs associated with responding to this solicitation. No reimbursement will be made for any costs associated with the preparation and submittal of any proposal, or for any travel and per diem costs that are incurred by any Proposer. RESPONSES RECEIVED LATE 5.1. It shall be the proposer's sole responsibility to deliver the proposal submission to the Lee County Procurement Management Division prior to or on the time and date stated. 5.2. Any proposals received after the stated time and date will not be considered. The proposal shall not be opened at the public opening. Arrangements may be made for the unopened proposal to be returned at the proposer's request and expense. 5.3. The Lee County Procurement Management Division shall not be responsible for delays caused by the method of delivery such as, but not limited to; Internet, United States Postal Service, overnight express mail service(s), or delays caused by any other occurrence. 6. PROPOSER REQUIREMENTS (unless otherwise noted) 6.1. Responsive and Responsible: Only proposals received from responsive and responsible proposers will be considered. The County reserves the right before recommending any award to inspect the facilities and organization; or to take any other necessary action, such as background checks, to determine ability to perform is satisfactory, and reserves the right to reject submission packages where evidence submitted or investigation and evaluation indicates an inability for the proposer to perform. 6.1.1. Proposals may be declared "non -responsive" due to omissions of Negligence or Breach of Contract" on the disclosure form. Additionally, proposals may be declared "not responsible" due to past or pending lawsuits that are relevant to the subject procurement such that they call into question the ability of the proposer to assure good faith performance. This determination may be made by the Procurement Management Director, after consulting with the County Attorney. 6.1.2. Additional sources may be utilized to determine credit worthiness and ability to perform. 6.1.3. Any proposer or sub -proposer that will have access to County facilities or property may be required to be screened to a level that may include, but is not limited to; fingerprints, statewide criminal. There may be fees associated with these procedures. These costs are the responsibility of the proposer or sub -proposer. 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 6.2. Past Performance: All vendors will be evaluated on their past performance and prior dealings with Lee County (i.e., failure to meet specifications, poor workmanship, late delivery, etc.) Poor or unacceptable past performance may result in proposer disqualification. 7. PRE -SOLICITATION CONFERENCE 7.1. A pre -solicitation conference will be held in the location, date, and time specified on the cover of this solicitation. The cover will also note if the pre -solicitation conference is Non -Mandatory or Mandatory. All questions and answers are considered informal. All prospective proposers are encouraged to obtain and review the solicitation documents prior to the pre -proposal so they may be prepared to discuss any questions or concerns they have concerning this project. All questions must be submitted formally in writing to the procurement staff noted on the first page of the solicitation document. A formal response will be provided in the form of an addendum (see "County Interpretation/Addendums" for additional information.) A site visit may follow the pre -proposal conference, if applicable. 7.2. Non -Mandatory: Pre -solicitation conferences are generally non -mandatory, but it is highly recommended that prospective proposers participate. 7.3. Mandatory: Failure to attend a mandatory pre -solicitation conference will result in the proposal being considered non -responsive. 8. COUNTY INTERPRETATION/ADDENDUMS 8.1. Each Proposer shall examine the solicitation documents and shall judge all matters relating to the adequacy and accuracy of such documents. Any inquiries, suggestions or requests concerning interpretation, clarification or additional information pertaining to the solicitation shall be submitted in writing prior to 5:00 PM at least eight (8) calendar days prior to the date when the submission is due. 8.2. Response(s) will be in the form of an Addendum posted on www.leegov.com/procurement. It is solely the proposer's responsibility to check the website for information. No notifications will be sent by Lee County Procurement Management Division. 8.3. All Addenda shall become part of the Contract Documents. 8.4. The County shall not be responsible for oral interpretations given by any County employee, representative, or others. Interpretation of the meaning of the plans, specifications or any other contract document, or for correction of any apparent ambiguity, inconsistency or error there in, shall be in writing. Issuance of a written addendum by the County's Procurement Management Division is the only official method whereby interpretation, clarification or additional information can be given. 9. QUALITY GUARANTEE/WARRANTY (as applicable) 9.1. Proposer will guarantee their work without disclaimers, unless otherwise specifically approved by the County, for a minimum of twelve (12) months from final completion. 9.2. Unless otherwise specifically provided in the specifications, all equipment and materials and articles incorporated in the work covered by this contract shall be new, unused and of the most suitable grade for the purpose intended. Refurbished parts or equipment are not acceptable unless otherwise specified in the specifications. All warrantees will begin from the date of final completion. 9.3. Unless otherwise specifically provided in the specifications, the equipment must be warranteed for twelve (12) months, shipping, parts and labor. Should the equipment be taken out of service for more than forty- eight (48) hours to have warranty work performed, a loaner machine of equal capability or better shall be provided for use until the repaired equipment is returned to service at no additional charge to the County. 9.4. If any product does not meet performance representation or other quality assurance representations as published by manufacturers, producers or distributors of such products or the specifications listed, the vendor shall pick up the product from the County at no expense to the County. The County reserves the right to reject any or all materials, if in its judgment the item reflects unsatisfactory workmanship or manufacturing or shipping damage. The vendor shall refund, to the County, any money which has been paid for same. 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 10. SUBSTITUTION(S)/APPROVED ALTERNATE(S) 10.1. Unless otherwise specifically provided in the specifications, reference to any equipment, material, article or patented process, by trade name, brand name, make or catalog number, shall be regarded as establishing a standard of quality and shall not be construed as limiting competition. If a proposer wishes to make a substitution in the specifications, the bidder shall furnish to the County, no later than ten (10) business days prior to the solicitation opening date the name of the manufacturer, the model number, and other identifying data and information necessary to aid the County in evaluating the substitution. Such information is submitted through the Procurement Management Division. Any such substitution shall be subject to County approval through the issuance of a written addendum by the County's Procurement Management Division. Substitutions shall be approved only if determined by the County to be an Annroved Alternate to the prescribed specifications. 10.2. A proposal containing a substitution is subject to disqualification if the substitution is not approved by the County. Items bid must be identified by brand name, number, manufacturer and model, and shall include full descriptive information, brochures, and appropriate attachments. Brand names are used for descriptive purposes only. An Annroved Alternate product or service may be used. 11. ADDITIONS, REVISONS AND DELETIONS 11.1. Additions, revisions, or deletions to the Terms and Conditions, specifications that change the intent of the solicitation will cause the solicitation to be non -responsive and the proposal will not be considered. The Procurement Management Director shall be the sole judge as to whether or not any addition, revision, or deletion changes the intent of the solicitation. 12. NEGOTIATED ITEMS 12.1. Any item not outlined in the Scope of Services may be subject to negotiations between the County and the successful Proposer. 12.2. After award of this proposal the County reserves the right to add or delete items/services at prices to be negotiated at the time of addition or deletion. 12.3. At contract renewal time(s) or in the event of significant industry wide market changes, the County may negotiate justified adjustments such as price, terms, etc., to this contract with the County, in its sole judgment, considers such adjustments to be in the best interest of the County. 13. ERRORS, OMISSIONS, CALCULATION ERRORS (as applicable) 13.1. Errors/Omissions: Approval by County of the successful proposer's work product for the project shallnot constitute nor be deemed a release of the responsibility and liability of the successful proposer for the accuracy and competency of the successful proposer's designs, drawings, specifications or other documents and work pertaining to the project. Additionally, approval by the County of the successful proposer's work product shall not be deemed to be an assumption of drawings, specifications or other documents prepared by the successful proposer for the project. After acceptance of the final plans by the County, the successful proposer agrees, prior to and during the construction of the project, to perform such successful proposer services, at no additional cost to the County, as may be required by the County to correct errors or omissions on the plans prepared by the successful proposer pertaining to the project. 13.2. Calculation Errors: In the event of multiplication/addition error(s), the unit price shall prevail. Written prices shall prevail over figures where applicable. All proposals shall be reviewed mathematically and corrected, if necessary, using these standards, prior to additional evaluation. 14. CONFIDENTIALITY 14.1. Proposers should be aware that all proposals provided are subject to public disclosure and will U91 be afforded confidentiality, unless provided by Chapter 119 Florida Statute. 14.2. If information is submitted with a proposal that is deemed "Confidential" the proposer must stamp those pages of the proposal that are considered confidential. The proposer must provide documentation as to validate why these documents should be declared confidential in accordance with Chapter 119, "Public Records," exemptions. RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 14.3. Lee County will not reveal engineering estimates or budget amounts for a Droject unless required by grant funding or unless it is in the best interest of the County. According to Florida State Statute 337.168: A document or electronic file revealing the official cost estimate of the department of a project is confidential and exempt from the provisions of s. 119.07(1) until the contract for the project has been executed or until the project is no longer under active consideration. 15. CONFLICT OF INTEREST 15.1. All proposers are hereby placed on formal notice that per Section 3 of Lee County Ordinance No. 92-22: The County is prohibited from solicitation of a professional services firm to perform project design and/or construction services if the firm has or had been retained to perform the project feasibility or study analysis. And: 15.2. A professional services firm who has performed or participated in the project feasibility planning, study analysis, development of a program for future implementation or drafting of solicitation documents directly related to this County project, as the primary vendor/consulting team, cannot be selected or retained, as the primary consultant/vendor or named a member of the consulting/contracting team, to perform project design, engineering or construction services for subsequent phase(s) or scope of work for this project. Pursuant to FS. 5287.057 (17) the firm will be deemed to have a prohibited conflict of interest that creates an unfair competitive advantage. 15.3. Should your proposal be found in violation of the above stated provisions; the County will consider this previous involvement in the project to be a conflict of interest, which will be cause for immediate disqualification of the proposal from consideration for this project. 15.4. Business Relationship Disclosure Requirement: The award hereunder is subject to the provisions of Chapter 112, Public Officers and Employees: General Provisions, Florida Statues. All proposers must disclose with their proposal the name of any officer, director or agent who is also an employee of the Lee County or any of its agencies. Further, all proposers must disclose the name of any County employee who owns directly or indirectly, an interest of five percent (5%) or more in the proposer's firm or any of its branches. 16. ANTI -LOBBYING CLAUSE (Cone of Silence) 16.1. Following Florida Statute Section 287.057(23), Upon the issuance of the solicitation, prospective proposers or any agent, representative or person acting at the request of such proposer shall not have any contact, communicate with or discuss any matter relating in any way to the solicitation with any Commissioner, Evaluation Review Committee, agent or employee of the County other than the Procurement Management Director or their designee. This prohibition begins with the issuance of any solicitation, and ends upon execution of the final contract or when the solicitation has been cancelled. If it is determined that improper communications were conducted, the Proposer maybe declared non- responsible. 17. DRUG FREE WORKPLACE 17.1. Lee County Board of County Commissioners encourages Drug Free Workplace programs. 18. DISADVANTAGED BUSINESS ENTERPRISE (DBE's) 18.1. The County encourages the use of Disadvantaged Business Enterprise Proposer(s) as defined and certified by the State of Florida Office of Supplier Diversity. 18.2. Bidder/Proposer is required to indicate whether the Firm and/or any proposed sub -consultants are Disadvantaged Business Enterprises (DBE). Lee County encourages the utilization and participation of DBEs in procurements, and evaluation proceedings will be conducted within the established guidelines regarding equal employment opportunity and nondiscriminatory action based upon the grounds of race, color, sex or national origin. Interested certified Disadvantaged Business Enterprise (DBE) firms as well as other minority -owned and women -owned firms are encouraged to respond. 19. ANTI-DISCRIMINATION/EQUAL EMPLOYMENT OPPORTUNITY 19.1. The proposer agrees to comply, in accordance with Florida Statute 287.134, 504 of the Rehabilitation Act of 1973 as amended, the Americans with Disabilities Act of 1990 (ADA), the ADA Amendments Act of RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 2008 (ADAAA) that furnishing goods or services to the County hereunder, no person on the grounds of race, religion, color, age, sex, national origin, disability or marital status shall be excluded from participation in, denied the benefits of, or otherwise be subjected to discrimination. 19.2. The proposer will not discriminate against any employee or applicant for employment because of race, religion, color, age, sex, national origin, disability or marital status. The proposer will make affirmative efforts to ensure that applicants are employed and that employees are treated during employment without regard to their race, religion, color, age, sex, national origin, disability or marital status. 19.3. The proposer will include the provisions of this section in every sub -contract under this contract to ensure its provisions will be binding upon each sub -contractor. The proposer will take such actions in respect to any sub -contractor, as the contracting agency may direct, as a means of enforcing such provisions, including sanctions for non-compliance. 19.4. An entity or affiliate who has been placed on the State of Florida's Discriminatory Vendor List (This list may be viewed by going to the Department of Management Services website at hUp://www.dms.myflorida.com) may not submit a bid on a contract to provide goods or services to a public entity, may not submit a bid on a contract with a public entity for the construction or repair of a public building or public work, may not submit bids on leases of real property to a public entity, may not award or perform work as a vendor, supplier, sub -contractor, orconsultant under contract with any public entity, and may not transact business with any public entity. 20. PROPOSER/SUB-PROPOSER/CONSULTANT/CONTRACTOR RELATIONSHIP 20.1. The prime proposer on a solicitation may not also be listed as a sub-proposer/consultant/contractor to another firm submitting a proposal for the same solicitation. Should this occur, all responses from the involved/named firms will be considered non -compliant and rejected for award. Sub- proposers/consultant/contractor may be listed on multiple proposals for the same solicitation. 21. SUB-PROPOSER/CONSULTANT 21.1. The use of sub-proposer/consultant under this solicitation is not allowed without prior writtenauthorization from the County representative. 22. RFP -PROJECT GUIDELINES 22.1. The County has established the following Guidelines, Criteria, Goals, Objectives, Constraints, Schedule, Budget and or Requirements which shall service as a guide to the proposer(s) in conforming the professional services and work to provide pursuant to this Agreement/Contract: 22.1.1. No amount of work is guaranteed upon the execution of an agreement/contract. 22.1.2. Hourly rates and all other negotiated expenses will remain in effect throughout the duration of the agreement/contract period. 22.1.3. This contract does not entitle any firm to exclusive rights to County agreements/contracts. The County reserves the right to perform any and all available required work in-house or by any other means it so desires. 22.1.4. In reference to vehicle travel, mileage and man-hours spent in travel time, is considered incidental to the work and not an extra compensable expense. 22.1.5. Lee County reserves the right to add or delete, at any time, and or all tasks or services associated with this agreement. 22.1.6. Any Single Large Project: The County, in its sole discretion, reserves the right to separately solicit any project that is outside the scope of this solicitation, whether through size, complexity or the dollar value. 23. RFP — EVALUATION 23.1. Ranking Method: Lee County uses the Dense Ranking (1223" ranking). In Dense Ranking, items that compare equal, receive the same ranking number, and the next item(s) receive the immediately following ranking number. This ranking method is used for each individual committee member's scores. Thus if A ranks ahead of B and C (which compare equal) which are both ranked ahead of D, then A is ranked number • 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 1("first"), B is ranked number 2 ("joint second"), Cis also ranked number 2 ("joint second") and D is ranked number 3 ("third"). 23.1.1. Each Ranking is derived by the individual committee member's scores being totaled and then ranked with the highest "score" being "ranked" first with each following in the same manner. For example: a score of 100 would rank 1, a score of 75 would rank 2, and continue until all proposals have been ranked. 23.1.2. Upon completion of this method for each individual committee member the individual rankings are then totaled for an "Over-all Ranking." During the Over-all Ranking process the lowest total would be deemed the highest ranked (1). Example: Proposer A individual rankings totaled 5 and Proposer B individual rankings totaled 7 making "Over-all Ranking" order as Proposer A ranked 1, Proposer B ranked 2. 23.1.3. In the event of a tie, please refer to the tiebreaker section of this solicitation.) 23.2. Evaluation Meeting(s): 23.2.1. Evaluation 1: The first evaluation will rank Proposers based on the scores from the selection criteria point values. 23.2.2. Evaluation 2: Following the initial evaluation process, the short-listed proposer(s) will be required to provide an on -site interview/presentation. 23.2.2.1. Such subsequent evaluations will be accomplished by simply ranking the proposers. Proposers will be ranked in sequential order with one (1) being the highest ranking. Proposers' rankings will then be totaled with the total lowest scores receiving final rank order starting with one (1) - the highest ranking. 23.2.3. Proposed short-list and final selection meeting dates are posted on the Procurement Management web page: www.leegov.com/procurement (Projects, Award Pending.) 24. RFP — SELECTION PROCEDURE 24.1. The selection will be made in accordance with Lee County Procurement Policy. Some or all of the responding proposer(s) may be requested to provide interviews and/or presentations of their proposal, for the ranking process. 24.2. The recommendation to award, negotiated rates and agreement/contract(s) will be submitted to the Board of County Commissioners for approval. 24.3. If a satisfactory agreement/contract(s) cannot be negotiated, in a reasonable amount of time, the County, in its sole discretion, may terminate negotiations with the selected proposer(s) and begin agreement/contract negotiations with the next finalist. 24.4. The Procurement Management Director reserves the right to exercise their discretion to: 24.4.1. Make award(s) to one or multiple proposers. 24.4.2. Waive minor informalities in any response; 24.4.3. Reject any and all proposals with or without cause; 24.4.4. Accept the response that in its judgment will be in the best interest of Lee County 25. RFP — TIEBREAKER 25.1. In the event of a tie, two or more proposers that have the same ranking, the following steps will be taken to determine the highest ranked proposer. This method shall be used for all (RFP) ties. 25.1.1. Step 1: The proposer that has the highest number of 1st place rankings shall be deemed the first ranked proposer. In the event a tie still exists the proposer with the highest number of 2" d' place rankings shall be the first ranked proposer. Should a tie still remain the method used above will continue with each ranking level, 3rd, then 4t1i, then 5tn , etc. rank, will be counted until the tie is broken. 25.1.2. Step 2: At the conclusion of step 1, if all is equal, the proposer having a drug -free work place program, shall be deemed the first ranked proposer. 25.1.3. Step 3: In the event the tie exists then the highest ranked proposer from the first evaluation committee meeting, in which point values were applied, will win the award. One being the highest. 25.1.4. Step 4: At the conclusion of steps 1, 2, 3, if all are equal, the 1st place proposer shall be determined by the flip of a coin. • 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 25.2. When the tiebreaker is determined the highest ranked proposer shall be awarded the contract or receive the first opportunity to negotiate, as applicable. 25.3. If an award or negotiation is unsuccessful with the highest ranked proposer, award or negotiations may commence with the next highest ranked proposer. 26. RFP — EVALUATION/ SELECTION COMMITTEE 26.1. The selection shall be by a Selection Committee consisting of staff representatives from the appropriate County Departments as approved by the Procurement Management Director or designee. 26.2. The Selection Committee will receive and review written proposals in response to this Request for Proposal (RFP). Responses will be evaluated against a set of criteria to determine those Proposers/Finns most qualified and suited for this project. If applicable, the Selection Committee may choose to short-list Proposers/Firms to be interviewed to determine final selection. 27. WITHDRAWAL OF PROPOSAL 27.1. No proposal may be withdrawn for a period of 180 calendar days after the scheduled time for receiving proposals. A proposal may be withdrawn prior to the proposal opening date and time. Withdrawal requests must be made in writing to the Procurement Management Director, who will approve or disapprove the request. 27.2. A proposer may withdraw a proposal any time prior to the opening of the solicitation. 27.3. After proposals are opened, but prior to award of the contract by the County Commission, the Procurement Management Director may allow the withdrawal of a proposal because of the mistake of the proposer in the preparation of the proposal document. In such circumstance, the decision of the Procurement Management Director to allow the proposal withdrawal, although discretionary, shall be based upon a finding that the proposer, by clear and convincing evidence, has met each of the following four tests: 27.3.1. The proposer acted in good faith in submitting the proposal, 27.3.2. The mistake in proposal preparation that was of such magnitude that to enforce compliance by the proposer would cause a severe hardship on the proposer, 27.3.3. The mistake was not the result of gross negligence or willful inattention by the proposer; and 27.3.4. The mistake was discovered and was communicated to the County prior to the County Commission having formally awarded the contract/agreement. 28. PROTEST RIGHTS 28.1. Any proposer that has submitted a formal response to Lee County, and who is adversely affected by an intended decision with respect to the award, has the right to protest an intended decision posted by the County as part of the solicitation process. 28.2. "Decisions" are posted on the Lee County Procurement Management Division website. Proposers are solely responsible to check for information regarding the solicitation. (www.leegov.com/procurement) 28.3. Refer to the `Bid/Proposal Protest Procedure" section of the Lee County "Contracts Manual" for the complete protest process and requirements. The Manual is posted on the Lee County website or you may contact the Procurement Management Director. 28.4. In order to preserve your right to protest, you must file a written "Notice Oflntent To File A Protest" with the Lee County Procurement Management Director by 4:00 PM on the 3d working day after the decision affecting your rights is posted on the Lee County website. 28.4.1. The notice must clearly state the basis and reasons for the protest. 28.4.2. The notice must be physically received by the Procurement Management Director with in the required time frame. No additional time is granted for mailing. 28.5. To secure your right to protest you will also be required to post a "Protest Bond" and file a written "Formal Protest" document within 10 calendar days after the date of "Notice of Intent to File a Protest" is received by the Procurement Management Director. 28.6. Failure to follow the protest procedures requirement within the timeframes as prescribed herein and established by the Lee County Board of County Commissioners, Florida, shall constitute a waiver of your protest and any resulting claims. 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 29. AUTHORITY TO UTILIZE BY OTHER GOVERNMENT ENTITIES 29.1. This opportunity is also made available to any government entity. Pursuant to their own governing laws, and subject to the agreement of the vendor, other entities may be permitted to make purchases at the terms and conditions contained herein. Lee County Board of County Commissioners will not be financially responsible for the purchases of other entities from this solicitation. 30. CONTRACT ADMINISTRATION 30.1. Designated Contact: 30.1.1. The awarded proposer shall appoint a person(s) to act as a primary contact for all County departments. This person or back-up shall be readily available during normal working hours by phone or in person, and shall be knowledgeable of the terms and procedures involved. 30.1.2. Lee County requires that the awarded proposer to provide the name of a contact person(s) and phone number(s) which will afford Lee County access 24 hours per day, 365 days per year, of this service in the event of major breakdowns or natural disasters. 30.2. RFP — Term: (unless otherwise stated in the Scope of Work or Detailed Specifications) 30.2.1. Unless otherwise stated in the scope of work, specifications, or special conditions the default contract term shall be one (1) year with three (3), one (1) year renewals for a total of four (4) years upon mutual written agreement of both parties. 30.2.2. The County reserves the right to renew this contract, or any portion thereof, and to negotiate pricing as a condition for each. 30.2.3. The County's performance and obligation to pay under this contract, and any applicable renewal options, is contingent upon annual appropriation of funds. 30.3. RFP — Basis of Award: 30.3.1. Award will be made to the most responsible and responsive proposer based on the evaluation criteria. 30.4. Agreement/Contract: 30.4.1. The awarded proposer will be required to execute an Agreement/Contract as a condition of award. A sample of this document may be viewed on-line at hllp://www.leegov.com/procurement/forms. 30.5. Records: 30.5.1. Retention: The proposer shall maintain such financial records and other records as may beprescribed by Lee County or by applicable federal and state laws, rules and regulations. Unless otherwise stated in the specifications, the proposer shall retain these records for a period of five years after final payment, or until they are audited by Lee County, whichever event occurs first. 30.5.2. Right to Audit/Disclosure: These records shall be made available during the term of the contract as well as the retention period. These records shall be made readily available to County personnel with reasonable notice and other persons in accordance with the Florida General Records Schedule. Awarded Bidder/Proposer(s) are hereby informed of their requirement to comply with FL § 119 specifically to: 30.5.2.1. Keep and maintain public records required by the County to perform the service. 30.5.2.2. Upon request from the County's custodian of public records, provide the County with a copy of the requested records or allow the records to be inspected or copied within a reasonable time at a cost that does not exceed the cost provided or as otherwise provided by law. 30.5.2.3. Ensure that public records that are exempt or confidential and exempt from public records disclosure requirements are not disclosed except as authorized by law for the duration of the contract term and following completion of the contract if the contractor does not transfer the records to the County. 30.5.2.4. Upon completion of the contract, transfer, at no cost, to the County all public records in possession of the contractor or keep and maintain public records required by the County to perform the service. If the contractor transfers all public records to the County upon completion of the contract, the contractor shall destroy any duplicate public records that are exempt or confidential and exempt from public records disclosure requirements. If the contractor keeps and maintains public records upon completion of the contract, the 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 contractor shall meet all applicable requirements for retaining public records. Allrecords stored electronically must be provided to the County, upon request from the County's custodian of public records, in a format that is compatible with the information technology systems of the County. 30.5.3. Public Record: IF THE VENDOR HAS QUESTIONS REGARDING THE APPLICATION OF CHAPTER 119. FL $ , TO THE VENDOR'S DUTY TO PROVIDE PUBLIC RECORDS RELATING TO THE CONTRACT, CONTACT THE CUSTODIAN OF PUBLIC RECORDS AT 239-533- 22219 2115 SECOND STREET, FORT MYERS, FL 339019 httn://www.lee2ov.com/uublicrecords. 30.5.4. Ownership: It is understood and agreed that all documents, including detailed reports, plans, original tracings, specifications and all data prepared or obtained by the successful proposer in connection with its services hereunder, include all documents bearing the professional seal of the successful proposer, and shall be delivered to and become the property of Lee County, prior to final payment to the successful proposer or the termination of the agreement. This includes any electronic versions, such as CAD or other computer aided drafting programs. 30.6. Termination: 30.6.1. Any agreement as a result of this solicitation may be terminated by either party giving thirty (30) calendar days' advance written notice. The County reserves the right to accept or not accept a termination notice submitted by the proposer, and no such termination notice submitted by the vendor shall become effective unless and until the vendor is notified in writing by the County of its acceptance. 30.6.2. The Procurement Management Director may immediately terminate any agreement as a result of this solicitation for emergency purposes, as defined by the Lee County Purchasing and Payment Procedures Manual (Purchasing Manual), (also known as Appendix "D", "AC-4-l.pdf'.) 30.6.3. Any proposer who has voluntarily withdrawn from a solicitation without the County's mutual consent during the contract period shall be barred from further County procurement for a period of 180 days. The vendor may apply to the Board for a waiver of this debarment. Such application for waiver of debarment must be coordinated with and processed by the Procurement Management Department. 30.6.4. The County reserves the right to terminate award or contract following any of the below for goods or services over $1,000,000: 30.6.4.1. Contractor is found to have submitted a false certification as provided under FL § 287.135 (5); 30.6.4.2. Contractor has been placed on the Scrutinized Companies with Activities in Sudan List or the Scrutinized Companies with Activities in the Iran Petroleum Energy Sector List; 30.6.4.3. Contractor has engaged in business operations in Cuba or Syria; 30.6.4.4. Contractor has been placed on the Scrutinized Companies that Boycott Israel List, or is engaged in a boycott of Israel — beginning October 1, 2016. 31. WAIVER OF CLAIMS 31.1. Once this contract expires, or final payment has been requested and made, the awarded vendor shall have no more than thirty (30) calendar days to present or file any claims against the County concerning this contract. After that period, the County will consider the vendor to have waived any right to claims against the County concerning this agreement. 32. LEE COUNTY PAYMENT PROCEDURES 32.1. All vendors are requested to mail an original invoice to: Lee County Finance Department Post Office Box 2238 Fort Myers, FL 33902-2238 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 32.2. All invoices will be paid as directed by the Lee County payment procedure unless otherwise stated in the detailed specification portion of this project. 32.3. Lee County will not be liable for requests for payment deriving from aid, assistance, or help by any individual, vendor, proposer, or bidder for the preparation of these specifications. 32.4. Lee County is generally a tax exempt entity subject to the provisions of the 1987 legislation regarding sales tax on services. Lee County will pay those taxes for which it is obligated, or it will provide a Certificate of Exemption furnished by the Department of Revenue. All proposers should include in their proposal, all sales or use taxes, which they will pay when making purchases of material or sub -contractor's services. 33. MATERIAL SAFETY DATA SHEETS (MSDS/SDS) (if applicable) 33.1. In accordance with Chapter 443 of the FL §, it is the vendor's responsibility to provide Lee County with Material Safety Data Sheets on bid materials, as may apply to this procurement. 34. DEBRIS DISPOSAL (if applicable) 34.1. Unless otherwise stated, the Proposer shall be fully responsible for the lawful removal and disposal of any materials, debris, garbage, vehicles or other such items which would interfere with the undertaking and completion of the project. There shall not be an increase in time or price associated with such removal. 35. SHIPPING (if applicable) 35.1. Cost of all shipping to the site, including any inside delivery charges and all unusual storage requirements shall be borne by the proposer unless otherwise agreed upon in writing prior to service. It shall be the proposer's responsibility to make appropriate arrangements, and to coordinate with authorized personnel at the site, for proper acceptance, handling, protection and storage (if available) of equipment and material delivered. All pricing to be F.O. B. destination. 35.2. The materials and/or services delivered under the proposal shall remain the property of the seller until a physical inspection and actual usage of these materials and/or services is accepted by the County and is deemed to be in compliance with the terms herein, fully in accord with the specifications and of the highest quality. 36. INSURANCE (AS APPLICABLE) 36.1. Insurance shall be provided by the awarded proposer. Upon request, a certificate of insurance (COI) complying with the attached guide shall be provided by the proposer. 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 36.2. Insurance Guide: ZLEE COUNTY SOUTHWEST FLORIDA Major Insurance Requirements Minimum Insurance Requirements: Risk Management in no way represents that the insurance required is sufficient or adequate to protect the Vendor's interest or liabilities. The following are the required minimums the Vendor must maintain throughout the duration of this Contract. The County reserves the right to request additional documentation regarding insurance provided. a. Commercial General Liability - Coverage shall apply to premises and/or operations, products and completed operations, independent contractors, and contractual liability exposures with minimum limits of: $1,000,000 per occurrence $2,000,000 general aggregate $1,000,000 products and completed operations $1,000,000 personal and advertising injury b. Business Auto Liability - The following Automobile Liability will be required and coverage shall apply to all owned, hired and non -owned vehicles use with minimum limits of: $1,000,000 combined single limit (CSL) or $500,000 bodily injury per person $1,000,000 bodily injury per accident $500,000 property damage per accident c. Workers' Compensation - Statutory benefits as defined by Chapter 440, Florida Statutes, encompassing all operations contemplated by this Contract or Agreement to apply to all owners, officers, and employees regardless of the number of employees. Workers' Compensation exemptions may be accepted with written proof of the State of Florida's approval of such exemption. Employers' liability will have minimum limits of: $500,000 per accident $500,000 disease limit $500,000 disease — policy limit *The required minimum limit of liability shown in a. and b. may be provided in the form of "Excess Insurance" or "Commercial Umbrella Policies," in which case, a "Following Form Endorsement" will be required on the "Excess Insurance Policy" or "Commercial Umbrella Policy." 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Verification of Coverage: 1. Coverage shall be in place prior to the commencement of any work and throughout the duration of the Contract. A certificate of insurance will be provided to the Risk Manager for review and approval. The certificate shall provide for the following: a. The certificate holder shall read as follows: Lee County Board of County Commissioners P.O. Box 398 Fort Myers, Florida 33902 b. "Lee County, apolitical subdivision and Charter County of the State of Florida, its agents, employees, and public officials " will be named as an "Additional Insured" on the General Liability policy, including Products and Completed Operations coverage. Special Requirements: 1. An appropriate "Indemnification" clause shall be made a provision of the Contract. 2. If applicable, it is the responsibility of the general contractor to ensure that all subcontractors comply with all insurance requirements. End of Insurance Guide section 1kF1`180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 37. SPECIAL CONDITIONS These conditions are in relation to this solicitation only and have not been included in the County's standard Terms and Conditions or the Scope of Work. 1. TERM From Notice to Proceed or Purchase Order date, whichever applies, calendar days to substantial completion, 30 calendar days to final completion (estimated timeline 365 total calendar days.) Proposal to be based on this timeline. The county reserves the right to negotiate the timeline with awarded vendor. End of Special Conditions 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 LEE COUNTY, FLORIDA DETAILED SPECIFICATIONS FOR RFP180081LKD Computer Aided Dispatch Replacement and Associated interfaces 1. GENERAL SCOPE OF PROJECT I.I. Lee County is seeking proposals for a turnkey solution that includes installation, implementation, training and maintenance for a system that supports the following: Computer Aided Dispatch (CAD), Mobile Data Computer, and Global Positioning Systems (GPS) Automatic Vehicle Locator (AVL). 2. BACKGROUND 2.1. Lee County Division of Public Safety serves an area of 1,212 square miles including barrier islands, rural, suburban, and urban environments. The County has a full time population of over 700,000. Any system considered will need to be scalable given the projected increase in population (to 979,000 permanent residents with an additional 18% seasonal residents) between the present date and 2030. 2.2. Lee Control is the County -operated E9-1-1 secondary answering point, dispatching a county -wide Emergency Medical Service, two combined Fire - EMS departments, and 19 independent Fire -Rescue departments. 90% of the departments are dispatched by GPS for closest unit and cross boundary response. These departments consist of more than 200 vehicles that exist as resources for emergency response as well as command staff locations and vehicles where these responses are monitored. 2.3. Lee Control currently staffs 11 dispatch positions and one supervisor's position that interface with the Intrado Voice over IP for Emergency Response (VIPER) version 5.1 customer premise equipment, thePowerPhone version 6.1 and MapFlex version 2.1. In 2016 Lee Control processed 209,197 incidents. There is also a training location with four positions, backup location with eight positions, monitoring location with three positions and maintenance location with two positions. Lee Control is accredited with the International Academies of Emergency Dispatch (IAED) as a dual Accredited Center of Excellence (ACE) in both Emergency Medical Dispatch (MPDS) and Fire Emergency Dispatch (FPDS). 2.4. The current system in place is a Motorola Premier CAD system version 7.0.14 and Premier Mobile Dispatch Computer v 6.04. 2.5. Lee Control relies on Public Safety information technology personnel to manage the operation and maintenance of the CAD workstations, County -owned mobile workstations and mobile connectivity. Fire Agency personnel or contractors handle maintenance of non -County -owned mobile workstations and mobile connectivity. Lee County's Information Technology vendor will operate and maintain the core CAD system, server infrastructure and network, proposed in this request. 3. PROJECT OBJECTIVE 3.1. PROJECT MANAGEMENT: 3.1.1. Follow industry standard project management methodology in managing the project. 3.1.2. Track project management detailed milestones in Microsoft Project and Excel or a format acceptable to the County. 3.1.3. Produce documentation in a format approved by Lee County during all phases of the project. 3.1.4.Documentation should include, but is not limited to a communication plan; change management plan; meeting agendas; minutes; workflow diagrams; status reports and risk/issue identification ensuring that stakeholders are well informed of the project details. 3.1.5. Collaborate with County project management staff to establish a structured project schedule that includes: project plan definition, goals, milestones, regular update meetings, status reports and deadlines for deliverables. Specific assignments will be established in advance of each project phase. 3.1.6. Conduct recurring status meetings with the project stakeholders and the project team. 3.2. INSTALL: 3.2.1. The successful completion of the installation of equipment hardware, software, interfaces. Installation is independent of the final configuration of software, which would occur by Go -Live. However, certain RF1`180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 aspects of the installation/interfaces may be dependent on the Go -Live cut -over and shall not be considered complete unless proven operational through alternative means. 3.2.2. The Project Management Plan will detail functional specifications (attached Excel spreadsheet, tabs 1-10) which are included in the installation objectives. 3.3. TRAINING & SUPPORT: 3.3.1. Training is complete when all agreed upon training is delivered and materials and tools related to training and support are available to Lee County and its stakeholders (tabs 11 & 13). End user training should be conducted as close to scheduled Go -Live date as practical (no greater than 60 days prior) so to ensure users retain information and system configuration is near production status. 3.4. GO -LIVE: (Making the software live in the production environment.) 3.4.1. Provide proper hand-off materials of finished project must be acceptable to the County and meet the County's needs to continue and complete remaining installation, test, cut -over. Materials include but are not limited to, up-to-date detailed project plan including schedules and resources, all contacts (vendor, county, constitutional, etc.), communications plan, product information, warrantee, as -built documentation, and cross -over training, sufficient to allow the existing County team to continue and complete remaining installation, test, cut -over. 3.4.2. All Call Taking and Dispatching functions and related interfaces are operational on the proposed system and proposed system is primary system in operation for the County. 3.5. FINAL ACCEPTANCE: 3.5.1. Final acceptance shall mean upon the successful completion and acceptance of the project. 4. PAYMENT AND PERFORMANCE MILESTONES 4.1. Upon completion of each of the following tasks, in the time allocated, application for payment may be made for that item #. Payment applications should not be more frequent than once per month. (TBD shall mean "to be determined" with input from awarded proposer) Timeline may not exceed time specified for this project. Calendar days shall commence upon Notice to Proceed being issued. A timeline, of calendar days, for each milestone shall be established with the awarded vendor. 4.2. Acceptance of Project Management Plan 4.2.1. Project Management Plan Acceptance stage is complete when the initial project management plan is agreed upon to the satisfaction of both parties. 4.3. Installation: 4.3.1. Install stage shall mean upon the delivery and successful completion of the equipment installation. (hardware, software, interfaces, etc.) 4.4. Training and Support: 4.4.1. Training stage is complete when all agreed upon training is delivered and materials and tools related to training and support are available to Lee County and its stakeholders. 4.5. Go -Live: 4.5.1. Go -Live stage shall mean that all Call Taking and Dispatching Functions and related interfaces are operational on the proposed system and proposed system is primary system in operation for the County. 4.6. Final Acceptance 4.6.1. Final acceptance stage is predicated on successful completion of Go -Live, 45-day Reliability Test, all deliverables and all trouble ticket items resolved to the satisfaction of both parties. End of Detailed Specifications Section 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 SUBMITTAL REQUIREMENTS & EVALUATION CRITERIA 1. SUBMITTAL. REQUIREMENTS 1.1. Interested firms shall include the following information in their submittal responses to this solicitation. The following format and sequence should be followed in order to provide consistency in the firm's responses and to ensure each proposal receives full consideration. Use 8 %2 x 11 single sided pages only with minimum font size of 10 points. PLEASE INCLUDE PAGE TABS/SECTION DIVIDERS so that those evaluating your submittal can easily compare each section with others that are submitted. More than one section is permitted on one page unless otherwise indicated below. Undesignated information shall be inserted at the rear of each package. Place page numbers at the bottom of every page, excluding dividers. Proposal documents should not contain links to other web pages; such links will not be reviewed for evaluation purposes. 1.2. If any of the information provided by the Proposer is found to be, in the sole opinion of the Evaluation Committee and Procurement Management Director, substantially unreliable their proposal may be rejected. 1.3. Proposers shall submit one (1) original hard copy (clearly marked as such) and six (6) electronic version(s) on a USB flash drive set(s) containing the proposal submittal in an unlocked PDF format. The County may request specific files be submitted in specialty format (IE: Provide a Project Timeline in Excel format.) Vendor shall accommodate such specialty requests as stated within the submittal requirements describe herein. Should files not be provided in the format or quantity as requested Vendor may be deemed Non -Responsive and therefore ineligible for award. In case of any discrepancies, the original will be considered by the County in evaluating the Proposal, and the electronic version is provided for the County's administrative convenience only. Limit the color and number of images to avoid unmanageable file sizes. 2. MANDATORY MINIMUM REQUIREMENTS Lee County has outlined minimum and recommended requirements of the system in the Microsoft Excel® -based Functional Specifications workbook. While this workbook is an exhaustive list of these requirements, the below provides an abbreviated list for prospective respondents to capture a base set of these requirements. 2.1. System must be able to interoperate with Priority Dispatch Pro Q & A. 2.2. The calltaking component shall be ProQA Paramount -Platinum certified with the Multi -Discipline Launcher. 2.3. The ProQA interface shall automatically insert the initial PDS case information into the CAD Incident upon send and immediately be viewable to the CAD users. 2.4. Information entered into the case after dispatch shall be automatically copied over to the CAD incident and immediately viewable to the CAD users. 2.5. The system will support a multi-agency/jurisdiction model for both Emergency Medical Services and Fire -Rescue districts. 2.6. Response recommendations shall be AVL closest unit, run card, or combined depending on the incident type and primary agency. 2.7. The system will have the ability to recommend units based on defined cross -district boundaries or stay within district boundaries depending on the rules of the agencies. 2.8. The system will assign a unique incident number to each incident. 2.9. Lee Control supports a multi -agency closest unit, cross boundary response method for the fire services as well as a separate near county wide ALS transport service. The medical service and fire service will each need an incident sent to their respective Dispatchers with their own unique sequential run number. 2.10. Associated incidents shall receive all remarks and updates regardless of which incident is updated without additional actions or keystrokes to be taken by the Operator 2.11. The system shall be compatible with or account for interfaces with VIPER® version 5.1. 2.12. The system shall be compatible with or account for interfaces with PowerPhone® version 6.1. 2.13. The system shall be compatible with or account for interfaces with MapFlex® version 2.1. • 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 2.14. The proposer shall have a plan to incorporate Next Generation 911 standards into the proposed system. 2.15. The system shall utilize a Microsoft Windows 2012R2 or newer server operating software. 2.16. The system shall operate within a VMWare 6.x and VMotion environment. 2.17. The system shall utilize Microsoft SQL 2014 or higher. 2.18. The system shall support the Microsoft SQL AlwaysOn offering. 2.19. The system is compatible with ESRI software. 3. EVALUATION CRITERIA & SIJBMiSSION FORMAT Introduction ➢ Project RFP Number & Name ➢ Finn's Name & Address ➢ Finn's Contact Person & Information (phone, fax and email address) ➢ How many years has Proposer been in business under present name? ➢ Under what other former names has your organization operated? TAB 1: Qualifications of Company Proposals will be evaluated on the qualifications and experience of both the primary contractor (Respondent) and all major subcontractors. Respondents should submit sufficient information to enable the County to understand and evaluate the experience of the Respondent on similar projects. At a minimum, the following shall be provided in the appropriate section of the proposal: 1. General Company Information a. Company Profile 1) Identify all company locations 2) Identify the number of employees (a) Employed by the company in total (b) Dedicated to sales (c) Dedicated to technical support (d) Dedicated to research and development b. Company Longevity 1) Indicate the number of years in business 2) Indicate the number of years in business selling the CAD system solution solicited herein (minimum of ten years' experience) 3) Provide details on the company acquisitions in the last five years, including company name and dates; include companies acquired by the Respondent and the Respondent's company being acquired 4) Subcontractors, if applicable, will be required to have a minimum of threeyears of experience in their respective discipline 2. Capacity a. Time is of essence for this project; therefore, the successful Respondent must be able to perform the work in a timely manner. Present an outline of the Respondent's current workload, present capacity for additional work, and projected future workload, demonstrating ability to respond to County project requirements and complete by April 2019. 3. Respondent's Key Personnel a. Respondents must provide information demonstrating the technical knowledge (including all training and certifications) of all key personnel involved in the implementation in the scope of work. b. Respondents must provide resumes of the Respondent's project manager and other key design and implementation personnel (identified on an organization chart) that will be assigned to this project that illustrates their qualifications, educational levels, experience, licenses and/or certificates, technical skills, and availability. For each key person, provide a list of relevant projects they have worked on within the past five years with the following information: 1) Project title and location RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 2) Role, responsibility, and decision authority 3) Point of contact with the customer 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 TAB 2: Company Relevant Experience & Reference ➢ Provide a statement of understanding that your Company recognizes the County reserves the right to evaluate the proposing Company on their past performance and prior dealings with Lee County (i.e., failure to meet specifications, poor workmanship, late delivery, etc.) as part of their experience criteria. ➢ Consideration will be given to input from other clients of the Respondent's solutions and services, including the ability to manage a project of this size and scope, past performance, and the ability to provide the desired solution in the necessary timeframe. The County will also pursue independent means of contact, when available and appropriate. ➢ References a. Respondents must provide a list of all installations that the Respondent has implemented during the past five years that are relevant to the scope ofthis project. Each project reference shall include: 1) Project title and location. 2) Project start and finish dates. 3) Client point of contact (name and title.) 4) Current telephone number and email address of point ofcontact. 5) Description of the work/services provided. 6) Percentage of the overall project actually performed by the Respondent. 7) Initial bid price and final contract amount, including the quantity and dollar value of contract modifications. b. Respondents shall include three client references with active virtual CAD system environments, providing the information above, if different from the projects referenced. c. Provide three client references for the disaster recovery solution proposed, providing the information above, if different from the projectsreferenced. d. Respondents must provide a list of previous implementations utilizing amove up/cover application. e. The County may contact client references to validate the information provided by the Respondent and to determine the client's overall satisfaction with thesolutions and services provided; therefore, it may prove beneficial to the Respondent to contact its referenced clients to ensure their contact information provided is up-to-date and that the reference will be available during the period of time that the County will be validating references (approximately 120 days). f. Respondents may include letters of commendation from customers. ➢ Past Performance a. Respondent 1) Provide a list of any projects completed within the last five years thatwere more than two months behind schedule and an explanation ofwhy. 2) Provide a list of any projects that Respondent failed to complete and an explanation of why. TAB 3: Firm Plan of Approach 1. Submitted Proposal a. Respondents will be evaluated on the quality and responsiveness of the proposed CAD system solution as presented in the response to the RFP. b. Respondents should demonstrate alternative methods of procurement. 1) Procurement methods should include lease or time payments as well as standard purchase. 2) Procurement methods should include per seat, enterprise and tiered pricing models. 3) Respondents should itemize the cost of software, interfaces, modules, support and training offerings in an ala carte fashion. 2. Management Plan a. The proposal should provide sufficient information to evaluate the Respondent's approach to managing, designing, and implementing the project. At a minimum, Respondents must provide the information listed below. 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 1) An organizational chart with information sufficient to understand and evaluate the Respondent's organizational structure. The organizational chart only needs to identify those persons who will be assigned to this project. 2) Describe the portions of the work that will be undertaken directly by the Respondent and that which will be subcontracted (if applicable). Include what percentage of the overall project the subcontractor is responsible for. 3) Provide specifics regarding project management areas such as a communications plan, risk assessment and mitigation, issue tracking, punch list development, change control, and escalation process. 3. Project Schedule a. Respondents must provide a proposed project schedule beginning at the Notice to Proceed and ending at Go -Live (as defined herein). The timeline should be expressed in terms of calendar days or weeks from the issuance of the Notice to Proceed rather than actual dates and should include specific major events, milestones, and deliverables. Identify any assumptions used that support this timeline. 4. Training Plan a. Respondents must provide details regarding the training plan for the CADsolution. 1) Detailed listing of training classes for CAD and mobile data users, including Train -the -trainer classes 2) Detailed listing of classes for system administration training for CAD, interfaces, geographic information system (GIS), mobile data for the startup, configuration, and continued administration of all components 3) Listing of recommended outside training that would be useful for system administration 4) Detailed schedules for training with consideration of maintaining dispatch center staffing requirements (a) Number of classes (b) Class size (c) Class schedule 5. Client -required County Resources a. Respondents must provide a list of all Client -required resources (including staff and materials) required to support the implementation of the CADsolution. b. Respondents must clearly identify tasks that are the responsibility of the Client resources and communicate required completion dates to fulfill the project schedule. A matrix of tasks versus responsibility (e.g., Respondent, County, other) is a preferred approach. c. Respondents must provide a description of the training and skills needed for County resources in order to properly support the system (e.g., DBA level skills, SQL training, Microsoft Active Directory [AD] certification, etc.) 6. Maintenance and Operation a. Proposals will be evaluated on the useful life expectancy of the CAD solution, particularly guarantees against early obsolescence. The County will not accept acquisition of a solution which the Respondent does not intend to support for the next 10-15 years. 1) Provide details regarding the operation and maintenance of the CADsolution 2) Provide details as to how the company deploys and charges for version upgrades, and the frequency of the updates 3) Provide details on what the maintenance plan includes in so far as parts, software, labor, and travel related to all components supplied under this contract and any financial rebates to the County if the terms of the maintenance agreement are not met. 4) Provide details on what the maintenance plan does not include and the frequency in which the County might expect these expenses to occur. 7. Proposed Solution a. Respondents will be evaluated on the quality of the proposed CAD solution, to include, but not limited to: 1) The degree to which the proposal addresses the stated goals 2) Adherence to the solicitation requirements 3) Extent to which the components of the CAD are integrated to provide a single- system appearance to the end users and an integrated solution RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 4) Extent to which the CAD solution incorporates effective processing methods, state-of-the-art technology and programming languages, and well defined system interfaces 5) General ease of use, future modification/expansion, and change 6) Detailed security rights and ease of administration 7) Comprehensiveness of the documentation (e.g., training materials and manuals) 8) Product life expectancy (identify all versions of the CAD solution since inception and any o7n-going research and development efforts) 9) Intuitiveness and aesthetic appeal of the software TAB 4: Functional Specifications 1. Proposals will be evaluated on the responses provided within the Microsoft Excel® -based Functional Specifications workbook. TAB 5: Price Scoring (COMPLETE MANDATORY FORM IA located in excel file " RFP180081LKD Functional_Specs.xlsx", Tab 15-Proposal Form) ➢ The Proposer with the lowest Price Proposal (Grand Total of all items) will be awarded the maximum score of listed in the scoring criteria section. o Note: "To Be Determined" or "ranges of price" are not acceptable entries. If a firm priceis not provided zero points will be earned for this category. ➢ All other proposals will be scored according to the following formula: (Lowest Price Proposal/ Proposer's Price Proposal) x Maximum points. Score o For example, the maximum score available for price is 10. If the lowest proposed Price Proposal is $150,000.00 that Proposer will receive the full 10 points. Another Proposerwith a Price Proposal of $160,000.00 will receive points calculated as follows: $ 150,000.001 $160,000.00 = .9375 TAB 6: Required Forms o Forms 1- 7 Forms, www.Sunbiz.ora print-out, etc. 1. SCORING CRITERIA & WEIGHT CRITERIA CRITERIA DESCRIPTION Qualifications of Company (TAB 1) MAX. POINTS AVAILABLE 5 2 Company Relevant Experience & Reference (TAB 2) 15 3 Firm Plan of Approach (TAB 3) 35 4 Functional Specifications (TAB 4) 35 5 Price Scoring 10 TOTAL POINTS 100 *Additional details and documents found within submittal package, although not located within tabs as listed above, may be reviewed and considered by evaluation committee when scoring Proposers. 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 3. RFP SUBMISSION SCHEDULE Submission Description Date(s) Time Advertise Request for Proposal (RFP) Friday, January 19, 2018 N/A Pre -Proposal Meeting N/A N/A Proposal Question Deadline 8 Calendar days prior to Prior to 5:00 PM submission deadline Submission Deadline Tuesday, February 20, 2018 Prior to 2:30 PM First Committee Meeting Short list discussion Friday, March 16, 2018 1:30 PM Notify Shortlist Selection via e-mail TBD N/A Final Scoring/Selection Meeting ** Thursday, April 5, 2018 10:30 AM Commission Meeting TBD Additional notes on Submission Schedule: *Meeting Locations: * 1500 Monroe Street, Fort Myers FL 33901 **Meeting to be conducted only if evaluation committee requires presentation/interview meeting(s) from shortlisted vendors. TBD: To be determined NOTE: Proposed short-list and final selection meeting dates are posted on the Procurement Management web page at www.leegov.com/procurement (Projects, Award Pending). End of Section 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 REQUIRED FORMS REQUEST FOR PROPOSA 1. (NON-CCN-�i These forms are required and should be submitted with all proposals. If it is determined that forms in this selection are not applicable to your company or solicitation they should be marked "N/A or Not Applicable" across the form in large letters and returned with your submission package. Note: If submitting via hard copy the original must be a manually signed original. Include additional copies, if specified, in the Solicitation documents. Form # Title/Descri tp ion 1 Solicitation Response Form All signatures must be by a corporate authorized representative, witnessed, and corporate and/or notary seal (if applicable.) The corporate or mailing address must match the company information as it is listed on the Florida Department of State Division of Corporations. Attach a copy of the web-page(s) from http://www.sunbiz.org as certification of this required information. Sample attached for your reference. Verify that all addenda and tax identification number have been provided. la Proposal Form This form is used to provide itemization of project cost. A more detailed "schedule of values" may be requested by the County This mandatory form has been included in the attached Excel file RFP180081LKD Functional Snecs.xlsx lb Business Relationship Disclosure Requirement (if Applicable) Sections 112.313(3) and 112.313(7), FL §, prohibit certain business relationships on the part of public officers and employees, their spouses, and their children. If this disclosure is applicable request form "INTEREST IN COMPETITIVE BID FOR PUBLIC BUSINESS" (Required by 112.313(12)(b), Florida Statute (1983)) to be completed and returned with solicitation response. It is the proposer's responsibility to request form and disclose this relationship, failure to do so could result in being declared non -responsive. NOTICE: UNDER THE PROVISIONS OF FL § 9112.317 (1983), A FAILURE TO MAKE ANY REQUIRED DISCLOSURE CONSTITUTES GROUNDS FOR AND MAY BE PUNISHED BY ONE OR MORE OF THE FOLLOWING: IMPEACHMENT, REMOVAL OR SUSPENSION FROM OFFICE OR EMPLOYMENT, DEMOTION, REDUCTION IN SALARY, REPRIMAND, OR A CIVIL PENALTY NOT TO EXCEED $5,000.00. 2 Affidavit Certification Immigration Laws Form is acknowledgement that the proposer is in compliance in regard to Immigration Laws. 3 Reference Survey Provide this form to reference respondents. This form will be turned in with the proposal package. 1. Section 1: Bidder/Proposer to complete with reference respondent's information prior to providing to them for their response. (This is not the Bidder/Proposer's information.) 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 2. Section 2: Enter the name of the Bidder/Proposer; provide the project information in which the reference respondent is to provide a response. 3. The reference respondent should complete "Section 3: 4. Section 4: The reference respondent to print and sign name 5. Reference responses are to be returned with the proposal package. 6. Failure to obtain reference surveys may make your company non -responsive. 4 Negligence or Breach of Contract Disclosure Form The form may be used to disclose negligence or breach of contract litigation that your company may be a part of over the past ten years. You may need to duplicate this form to list all history. If the proposer has more than 10 lawsuits, you may narrow them to litigation of the company or subsidiary submitting the solicitation response. Include, at a minimum, litigation for similar projects completed in the State of Florida. Final outcome should include in whose favor the litigation was settled and was a monetary amount awarded. The settlement amount may remain anonymous. If you have no litigation, enter "None" in the first "type of incident" block of the form. Please do not write N/A on this form. 5 Affidavit Principal Place of Business Certifies proposer's location information. 6 Sub -Contractor List (if applicable) To be completed and returned when sub -contractors are to be utilized and are known at the time of the submission. 7 Public Entity Crimes Form (Required form) Any person or affiliate as defined by statute who has been placed on the convicted vendor list following a conviction for a public entity crime may not submit a bid or a contract to provide any goods or services to the County; may not submit a bid on a contract with the County for the construction or repair of a public building or public work; may not submit bids or leases of real property to the County; may not be awarded or perform works as a contractor, supplier, subcontractor, or consultant under a contract with the County, and may not transact business with the County in excess of $25,000.00 for a period of 36 months from the date of being placed on the convicted vendor list. Proposal Label (Required) Self explanatory. Please affix to the outside of the sealed submission documents. The mailing envelope MUST be sealed and marked with: ✓ Solicitation Number ✓ Opening Date and/or Receiving Date ✓ Mailing Address: Lee County Procurement Management Division 1500 Monroe Street, 4th Floor Fort Myers, FL 33901 Include any licenses or certifications requested (if applicable) It is the Proposer's responsibility to insure the Solicitation Response is mailed or delivered in time to be received no later than the specified opening date and time. (If solicitation is not received prior to deadline it cannot be considered or accepted.) RF1`180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form I — Solicitation Response Form LEE COUNTY PROCUREMENT MANAGEMENT 1 LEE COUNTY SOLICITATION RESPONSE FORM S O U T H W E S T F IL O R I I? A Date Submitted: Deadline Date: 2/20/2018 SOLICITATION IDENTIFICATION: RFP180081LKD SOLICITATION NAME: Computer Aided Dispatch Replacement & Associated Interfaces (CAD) COMPANYNAME: NAME & TITLE: (TYPEDORPRINTED) BUSINESS ADDRESS: (PHYSICAL CORPORATE OR MAILING ADDRESS: T SAME AS PHYSICAL E-M AIL ADDRESS PHONE NUMBER: FAX NUMBER: NOTE REQUIREMENT: IT IS THE SOLE RESPONSIBILITY OF THE VENDOR TO CHECK LEE COUNTY PROCUREMENT MANAGEMENT WEB SITE FOR ANY ADDENDA ISSUED FOR THIS PROJECT. THE COUNTY WILL POST ADDENDA TO THIS WEB PAGE, BUT WILL NOT NOTIFY. In submitting this proposal, Proposer makes all representations required by the instructions to Proposer and further warrants and represents that: Proposer has examined copies of all the solicitation documents and the following addenda: No. Dated: No. Dated: No. Dated: No. Dated: No. Dated: No. Dated: Tax Payer Identification Number: (1) Employer Identification Number -or- (2) Social Security Number: ** Lee County collects your social security number for tax reporting purposes only Please submit a copy of your registration from the website www.sunbiz.org establishing the Proposer/firm as authorized (including authorized representatives) to conduct business in the State of Florida, as provided by the Florida Department of State, Division of Corporations. Collusion Statement: Lee County, Florida The undersigned, as Proposer, hereby declares that no person or other persons, other than the undersigned, are interested in this solicitation as Principal, and that this solicitation is submitted without collusion with others; and that we have carefully read and examined the specifications or scope of work, and with full knowledge of all conditions under which the services herein is contemplated must be furnished, hereby propose and agree to furnish this service according to the requirements set out in the solicitation documents, specifications or scope of work for said service for the prices as listed on the county provided price sheet or (CCNA) agree to negotiate prices in good faith if a contract is awarded. 2 Scrudni7ed Companies Cerdcation: Section 287.135, FL § , prohibits agencies from contracting with companies, for goods or services over $1,000,000, that are on either the Scrutinized Companies with Activities in Sudan List or the Scrutinized Companies with Activities in the Iran Petroleum Energy Sector List. Both lists are created pursuant to section 215.473, FL§. As the person authorized to sign on behalf of Respondent, I hereby certify that the company identified above not listed on either the Scrutinized Companies with Activities in Sudan List or the Scrutinized Companies with Activities in the Iran Petroleum Energy Sector List. I understand that pursuant to section 287.135, FL§, the submission of a false certification may subject company to civil penalties, attorney's fees, and/or costs. R1,'1`180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form#1 — Solicitation Form, Page 2 3 Business Relationshin Disclosure Reiguirement: Sections 112.313(3) and 112.313(7), FL§, prohibit certain business relationships on the part of public officers and employees, their spouses, and their children. See Part III, Chapter 112, FL § and/or the brochure entitled "A Guide to the Sunshine Amendment and Code of Ethics for Public Officers, Candidates and Employees" for more details on these prohibitions. However, Section 112.313(12), FL § (1983), provides certain limited exemptions to the above -referenced prohibitions, including one where the business is awarded under a system of sealed, competitive bidding; the public official has exerted no influence on bid negotiations or specifications; and where disclosure is made, prior to or at the time of the submission of the bid, of the official's or his spouse's or child's interest and the nature of the intended business. The Commission on Ethics has promulgated this form for such disclosure, if and when applicable to a public officer or employee. If this disclosure is applicable request form "INTEREST IN COMPETITIVE BID FOR PUBLIC B USINESS" (Required by 112.313(12)(b), Florida Statute (1983)) to be completed and returned with solicitation response. It is the proposer's responsibility to disclose this relationship, failure to do so could result in being declared non- responsive. Business Relationship Applicable (request form) Business Relationshi NOT A licable 4 Disadvantaged Business Enterprise (DBE) proposer? If yes, please attach a current certificate. Yes 11 No ALL PROPOSALS MUST BE EXECUTED BYANA UTHORIZED A UTHORITY OF THE PROPOSER, WITNESSED AND SEALED (IF APPLICABLE) Company Name (Name printed or typed) Authorized Representative Name (printed or typed) (Affix Corporate Seal, if applicable) Authorized Representative's Title (printed or typed) Witnessed/Attested by: (Witness/Secretary name and title printed or typed) Authorized Representative's Signature Witness/Secretary Signature Any blank spaces on the form(s), qualifying notes or exceptions, counter offers, lack of required submittals, or signatures, on County's Form may result in the submission being declared non -responsive by the County. • 1kF1`180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 %4%V W's unuiz-oi_l! - LICE% iu t rlIMll L.IL =fl it it: r'i11o'C l CIL L Detail by Entity Name Florida Profit Corooration 311's vVidget C--Urpuratruri Filing Information 0 oc tan a rit N urn Der 665565 OMEN Nun le+er 6111111111 Gate tiled DEV27-MQS1 Stae FL Status ACTTWE .ast Event AMENDED AND IDS TATED AR TICLES Event Oae Fled 071Zf2DOB Event Errective Date NCMVE Principal Address %-eeri& either Principal or Maihn� 556 N Main Stoat address 15 On Form 1uur lows USA99ii@Q Chwiged O211i/2 12 Mailing Address $56 N ktmn Steel x1your T'rawrt USA 99999 cnrrnged MJ1112012 Registered Agent Name S Address illy Ragntated Agent 111 Ragh *a§on Road Rags-trtdoon. USAM999 N wTv Ctits rig ad 12A 4 Q(M Address Ctraarged f Zp 1442006 Officer/Director Det 16mrm &Addre'ss TWr P� Pye,tldant. First a[ ALL dommean mu>t be gamed bT the pra t of the cc_ 6% AIi1-M JE 111113311MMAL ror an 1111113710MIJ othan the pretAfuL we'rr2 treed or of W Ar Awwn. USAMM Clle6% tiles aatbmir` m �iP- 1 3 c pporrm�� Zt �� by the Baud of Lhrecmt',, at Tlra V 2 an z t of mtnnsrs. or President Second 3 m am—A,"1 of Vats by ** $oad of Dirvctc>r; 6SS M ENUE If the compazif s nbcle; of mcarprxnaon Ldremlx � pasitioes dw l;sst tie pow to End Anyllovm, USAMM tiff i 1re viu accept tie surIffiff otd�t � fr= tie pul- dew taar e pa�c rob t1at ire C� c¢=is i+aie 1ka r dtff CSr�J. arod the >lt lirl of mr in do ppOOlterer m bad tie [Oa>S r _'.. the atahralky to bind a ]®sled li t iy ca n cowom by FiarA& .- - _6 ntff�bert lase inlsererlt m�oanr ro timed uL :.LG If the preadeat of 3 corperanoa or a 11im4er in aw =-- toember of in LL1= dekrm r1eir aat3�an1'r, � dtk�at�an ;Fsnwt be gent to v LSIl camp�nti• I"eta>i�ad 7.rth the Frir�dmt : ar 1-unzer T'.L3tl3t'.' g McMber ; C EM3. W!t ::*..r=re 1kF1`180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form ]a — Form ]a — Proposal Form (not app&cable for CCNA solicitations) LT E E COUNTY OUN,1.Y Lee County Procurement Management PROPosAL FORM 4 [) F I'll WI; S 'I- F l. 0 k 1 17 A Company Name: Computer Aided Dispatch Replacement and Solicitation # RFP170457LKD Solicitation Name Associated Interfaces ******MANDATORY***** Complete form la located on tab 15 of attached Excel form "RFP180081LKD Functional_Specs.xlsx" Item # I Description I Unit of Measure I I Total Cost R1,'1`180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form 2 — Affidavit Certification of Immigration Laws �; LEE COUNTYAFFIDAVIT CERTIFICATION IMMIGRATION LAWS SOUTHWEST FLORIDA SOLICITATION NO.: RFP180081LKD SOLICITATION NAME: Computer Aided Dispatch Replacement & Associated Interfaces (CAD) LEE COUNTY WILL NOT INTENTIONALLY AWARD COUNTY CONTRACTS TO ANY CONTRACTOR WHO KNOWINGLY EMPLOYS UNAUTHORIZED ALIEN WORKERS, CONSTITUTING A VIOLATION OF THE EMPLOYMENT PROVISIONS CONTAINED IN 8 U.S.C. SECTION 1324 a(e) {SECTION 274A(e) OF THE IMMIGRATION AND NATIONALITY ACT ("INA"). LEE COUNTY MAY CONSIDER THE EMPLOYMENT BY ANY CONTRACTOR OF UNAUTHORIZED ALIENS A VIOLATION OF SECTION 274A(e) OF THE INA. SUCH VIOLATION BY THE RECIPIENT OF THE EMPLOYMENT PROVISIONS CONTAINED IN SECTION 274A(e) OF THE INA SHALL BE GROUNDS FOR UNILATERAL CANCELLATION OF THE CONTRACT BY LEE COUNTY. PROPOSER ATTESTS THAT THEY ARE FULLY COMPLIANT WITH ALL APPLICABLE IMMIGRATION LAWS (SPECIFICALLY TO THE 1986 IMMIGRATION ACT AND SUBSEQUENT AMENDMENTS). Company Name: Signature Title STATE OF COUNTY OF Date The foregoing instrument was signed and acknowledged before me this day of 20 , by who has produced (Print or Type Name) as identification. (Type of Identification and Number) Notary Public Signature Printed Name of Notary Public Notary Commission Number/Expiration The signee of this Affidavit guarantee, as evidenced by the sworn affidavit required herein, the truth and accuracy of this affidavit to interrogatories hereinafter made. LEE CO UNTYRESER VES THE RIGHT TO REOUEST SUPPORTING DOCUMENTATION. AS EVIDENCE OF SERVICES PROVIDED. AT ANY TIME, 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form 3 Reference Survey :tl LEE COUNTYLee County Procurement Management SOUTHWEST FLORIDA RLEFF.RF.NCF.SURVF.Y Solicitation # RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Section I Reference Respondent Information FROM: COMPANY: PHONE #: FAX #: EMAIL: Please return completed form to: Bidder/Proposer: Due Date: Total # Pages: 1 Phone #: Fax #: 1 Bidder/Proposer E-Mail: Section 2 Enter Bidder/Proposer Information . if applicable Similar Performed Project (Bidder/Proposer to enter details of a project performed for above reference respondent) Proposer Name: Reference Project Name: Project Address: Project Cost: Smrmiarize Scope: You as an individual or your company has been given as a reference on the project identified above. Please provide your responses in section 3 below. Sectiona I Indicate: es or o 1. Did this company have the proper resources and personnel by which to get the job done? 2. Were any problems encountered with the company's work performance? 3. Were any change orders or contract amendments issued, other than ownerinitiated? 4. Was the job completed on time? 5. Was the job completed within budget? 6. On a scale of one to ten, ten being best, how would you rate the overall work performance, considering professionalism; final product; personnel; resources. Rate from 1 to 10. (10 being highest) 7. If the opportunity were to present itself, would you rehire this company? 8. Please provide any additional comments pertinent to this company and the work performed for you: Section 4 Reference Name (Print Please submit non -Lee County employees as references Reference Signature RFP 180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) c � •— o v +� n3 a) L CL co E > O C U a) 0 N L O a � N l0 E aJ -0 C � L 4� O a aj ai 3 t O L M aj to > O U L1 Q L N U O U O O Y Q l0 X t aJ 4� 4� U L L O Y C N O� 0 > t W E -0 4�L O aj 0 U -0 v to v O C � � W v to to� v Q l0 � O O 4 L l0 a••' Co Y L (n 41 O C: 4J v C -0 a) U -0 U U c CoCU (IJ U a) a) J O 0 ME O +J (U E L L Q O O -C 4-. C U on O v O c o O v 0 U /E/� `V ^m CL O U a) O� 41 a 3 O f0 O � 3 In U G a c O E tA m Z a) i w U E ,a U v 0 a a 7 O U U a E 3 z aI tA U a a 0 0 a-' U U L a a Y C 0 a a ai « i a LL � � N a o Qj v c a Q1 +� � 'U O v V 0 C v s CL a TZZ: i v H Q 0 m L � i aE Ln Q Ln C) c t O +E U N Y O O + co O O � � O L � o � � O O a L O c t n3 a] Q C: 0 .Z Y > U Q O O_ 0 --C N � O Q O O O_ U L C O -0 t O � � N O E c 0 O C 0 N -0 O 0 � � S to W L fl_ N t C: O O_ O O C) t z Ln L f6 a c O a O_ aI E w O fa O U 0 a *' O i � y o -0 « ao O r O + >. W aJ L Z L 0 V1 Z U U , C v w 0 c +_ o N •L C 3 0 v � m — N w Ln m n E O fl_ +, r 0 O C O (A m CL o E U O •� c 0 0 (6 L Ln E *' Ln+U L 0 a c E +, � L O Q 0 O +, f6 O U a1 iJ a1 in f6 O E f6 0 o O 0- Q O C O Q C Q aJ L o + v ca O c +� O W O -00 � �a v a a E a L C O O O U L o s Ln uO C O 0 7-0 Lli E U GO.O c v .5 0 0 N w U to O U tLo 0 O U U n. - E O O f6 i a U X U W faE L N C) 0 m + b4 L U O O Q a) Q E O c N t v _M O a) a� C Z ++ +� O O E L 0 c 0 U > 0 c E O U O L aa) U 0 .I-- a u a)E w c o o v c Q O E v a 0 D a) O O N t coo � -0 ~ w E v u t .� v �, � E o a a o C i a a Ver 06/08/2017-3 Form 5 - Affidavit Principal Place of Business AFFIDAVIT PRINCIPAL PLACE OF BUSINESS well LEE COUNTY SOUTHWEST FLORIDA Instructions: Please complete all information that is applicable to your firm Company Name: Printed name of authorized signer Authorized Signature Title Date The signee of this Affidavit guarantee, as evidenced by the sworn affidavit required herein, the truth and accuracy of this affidavit to interrogatories hereinafter made. LEE COUNTYRESERVES THE RIGHT TO REQUEST SUPPORTING DOCUMENTATION, AS EVIDENCE OF SERVICES PROVIDED, AT ANY TIME. Notary: State of County of The foregoing instrument was signed and acknowledged before me this 20 Type of ID and number day of who has produced identification (or personally known) Notary Public Signatme Notary Commission Number and expiration Principal place of business is located withinthe boundaries Lee County of: Collier County Non -Local Local Business Tax License # 2. Address of Principal Place of Business: 3. Number of years at this location 4. Have you provided goods or services to Lee County on a regular basis within the past 3 consecutive years 5. Number of available employees for this contract 6. Does your company have a Drug Free Workplace Policy _years *If yes, attach contractual history for _Yes* No past 3 consecutive years Yes No 1k1,'P180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) o � � c o � � U a O � O zw o � a it O o CC :r L7 °' U � w O � x. O w O i. z 0 U eC i. C O U Ver 06/08/2017-3 Form 7. Public Entity Crime Form Page I of 2 This form must be signed and sworn to in the presence of a notary public or other officer authorized to administer oaths. This sworn statement is submitted by (Print name of the public entity) (Print individual's name and title) (Print name of entity submitting sworn statement) whose business address is (If applicable) its Federal Employer Identification Number (FEIN)is (If the entity has no FEIN, include the Social Security Number of the individual signing this sworn statement: On the attached sheet.) Required as per IRS Form W-9. I understand that a "public entity crime" as defined in Paragraph 287.133(1) (g), Florida Statutes, means a violation of any state or federal law by a person with respect to and directly related to the transaction of business with any public entity or with an agency or political subdivision of any other state or with the United States, including but not limited to, and bid or contract for goods or services to be provided to any public entity or agency or political subdivision or any other state or of the Unites States, and involving antitrust, fraud, theft, bribery, collusion, racketeering, conspiracy, or material misrepresentation. I understate that "convicted" or "conviction" as defined in Paragraph 287.133(1) (b), Florida Statutes, means a finding of guilt or a conviction of a public entity crime, with or without an adjudication of guilt, in any federal or state trial court of record relating to charges brought by indictment or information after July 1, 1989, as a result of a jury verdict, nonjury trial, or entry of a plea of guilty or nolo contendere. I understand that "affiliate" as defined in Paragraph 287.133(1)(a), Florida Statutes means: 1. A predecessor or successor of a person convicted of a public entity crime: or: 2. An entity under the control of any natural person who is active in the management of the entity and who has been convicted of a public entity crime. The term "affiliate" includes those offices, directors, executives, partners, shareholders, employees, members and agents who are active in the management of the affiliate. The ownership by one person of shares constituting a controlling interest in another person, or a pooling of equipment or income among persons when not fair market value under an anu's length agreement, shall be a facie case that one person controls another person. A person who knowingly enters into a joint venture with a person who has been convicted of a public entity crime in Florida during the preceding 36 months shall be considered an affiliate. I understand that a "person" as defined in Paragraph 287.133(1) (c), Florida Statutes, means any natural person or entity organized under the laws of any state or of the United States with the legal power to enter a binding contract and which bids or applies to bid on contracts for the provision of goods or services let by a public entity, or which otherwise transacts or applies to transact business with apublic entity. The term "person" includes those officers, directors, executives, partners, shareholders, employees, members, and agents who are active in management of the entity. Based on information and belief, the statement which I have marked below is true in relation to the entity submitting those sworn statement. (Please indicate which statement applies.) Neither the entity submitted this sworn statement, nor any officers, directors, executives, partners, shareholders, employees, members, and agents who are active in management of an entity nor affiliate of the entity have been charged with and convicted of a public entity crime subsequent to July 1, 1989. RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Public Entity Crime Form Page 2 of 2 The entity submitting this sworn statement, or one or more of the officers, directors, executives, partners, shareholders, employees, member, or agents who are active in management of the entity, or an affiliate of the entity have been charged with and convicted of a public entity crime subsequent to July 1,1989. The entity submitting this sworn statement, or one or more of its officers, directors, executives, partners, shareholders, employees, member, or agents who are active in management of the entity, or an affiliate of the entity has been charged with and convicted of a public entity crime subsequent to July 1, 1989. However, there has been subsequent proceeding before a Hearing Officer of the State of Florida, Division of Administrative Hearing and the Final Order entered by the Hearing Officer determined that it was not in the public interest to place the entity submitting this sworn statement on the convicted vendor list. (Attach a copy of the final order) I UNDERSTAND THAT THE SUBMISSION OF THIS FORM TO THE CONTRACTING OFFICER FOR THE PUBLIC ENTITY IDENTIFIED IN PARAGRAPH 1 (ONE) ABOVE IS FOR THAT PUBLIC ENTITY ONLY AND, THAT THIS FORM IS VALID THROUGH DECEMBER 31 OF THE CALENDAR YEAR IN WHICH IS FILED. I ALSO UNDERSTAND THAT I AM REQUIRED TO INFORM THE PUBLIC ENTITY PRIOR TO ENTERING INTO A CONTRACT IN EXCESS OF THE THRESHOLD AMOUNT PROVIDED IN SECTION 287.017, FLORIDA STATUTES, FOR CATEGORY TWO OR ANY CHANGE IN THE INFORMATION CONTAINED IN THIS FORM. (Signature) (Date) STATE OF_ COUNTY OF PERSONALLY APPEARED BEFORE ME, the undersigned authority, (Name of individual signing) who, after first being sworn by me, affixed his/her signature in the space provided above on this day of , 2 (NOTARY PUBLIC) My Commission Expires: 1kFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Sealed Proposal Label Cut along the outer border and affix this label to your sealed solicitation envelope to identify it as a "Sealed Submission/Proposal". PROPOSAL DOCUMENTS • DO NOT OPEN SOLICITATION No.: SOLICITATION TITLE: DATE DUE: TIME DUE: SUBMITTED BY: e-mail address DELIVER TO: RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Tuesday, February 20, 2018 Prior to: 2:30 PM .. (Name of Company) Telephone Lee County Procurement Management 1500 Monroe 41h Floor Fort Myers FL 33901 II Note: proposals received after the time and date above will not be accepted. II Lee County Procurement Management 1500 Monroe Street, 4d'Floor Fort Myers, FL 33901 (239)533-8881 www.lee gov. com/procurement PLEASE PRINT CLEARLY • RFP 180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) LEE COUNTY SOUTH WES F FLOR I DA Date: August 10, 2018 Solicitation No.: RFP180081LKD Procurement Management Department 1.500 Monroe Street 01 Floor Fort Myers, FL 33901 Main Line: (239) 533-8881. Fax Line: (239) 485-8383 Solicitation Name: Computer Aided Dispatch Replacement and Associated Interfaces (CAD) Subject: NOTICE TO PROCEED To: - Intergraph Corporation d/b/a Hexagon Safety & Infrastructure You are hereby notified to commence work in accordance with the Master Agreement dated August 9, 2018. The initial term of the Master Agreement is three (3) years, Physical. work will commence on or before August 30,2018, Work. shall be completed in accordance with the timeline established in approved "Order"(s,) Acceptance of Notice: Receipt of the above Notice to Proceed is hereby acknowledged: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Prime Vendor: Lee County-, is ca �nl I itcIr �02—/ - �' X69A7-Husiz -F Printed Mum and Title 013. ia I's — --5ate— Laurie Victory, CPPB Procurement rviana �= lv�lq—H.1 -- Printed Name and Title bate 6 3 U � W\— _ �� Page 1 of 1 ILEE T. S0UT"FIWEST F L,0RIDA Posted Date: 4/17/2018 Protest Deadline: 4/20/2018 Lee County Procurement Management Division 1500 Monroe Street 4t" Floor Fort Myers, FL 33901 Main Line: (239) 533-8881 Fax Line: (239) 485-8383 www.leegov.com/procurement Notice of Intended Decision Proposal Action Proposal: RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) The Evaluation Committee for the above proposal project met April 10, 2018 for purposes of reviewing/ discussing all proposals/ presentations given by the short-listed firms. At the conclusion of the meeting. the Committee ranked the nronosals as follows - I" Intergraph Co d/b/a Hexagon Safety & Infrastructure 2nd Motorola Solutions Inc 3rd Su erion, LLC Recommendation will be made to the Lee County Commission that the County award to the following top ranked firms : 1" I Intergraph Corn d/b/a Hexagon Safetv & Infrastructure I.' Note: All submitters are furnished this notice. A submitter who has cause to file a Notice of Intent to File a Protest against the award must do so in writing to the Procurement Management Director no later than 4:00 p.m. local time on the third working day (Monday -Friday, excluding legal holidays) following the date of this notice. It must clearly state that it is a protest and must include specific information required by the County Government's current directive. Failure to protest on a timely basis, or to include the required information, will invalidate the protest. WWW.LeeGov.Com/Procurement is the County's official posting site NOIDPA ver 05/01/2016 ILEE COUNTY S()UTHWFST FL0Rf1)A Date: August 10, 2018 Solicitation No.: RF'P180081LKD Procurement Management Department 1500 Monroe Street 4"' Floor Fort Myers, FL 3390.1 Main Line: (239) 533-8881. Fax Line: (239) 485-8383 1VW w.iee xov.corir/ nroC1J 1—mvent Solicitation Name: Computer Aided Dispatch Replacement and Associated Interfaces (CAD) Subject: NOTICE TO PROCEED To: IIntergraph Corporation d/b/a Hexagon Safety & Infrastructure You are hereby notified to commence work in accordance with the Master Agreement dated August 9, 2018, The initial term of the Master Agreement is three (3) years. Physical work will commence on or before August 30, 2018, Work shall be completed in accordance with the timeline established in approved "Order"(s.) Acceptance of Notice: Receipt of the above Notice to Proceed is hereby acknowledged: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Prime Vendor: Lee County: Sf�nntur4- Printed Name and Title ranature afAulWhorimd Of i31 Laurie Victory, CPPB Pr6 rement MAnrt Yeti Printed Name and Title l57a-te _ Date Page 1 oE'I ILEE COUN SOUTHWEST FL,0RIDA Posted Date: 4/17/2018 Protest Deadline: 4/20/2018 Lee County Procurement Management Division 1500 Monroe Street 41h Floor Fort Myers, FL 33901 Main Line: (239) 533-8881 Fax Line: (239) 485-8383 www.leegov.com/procurement Notice of Intended Decision Proposal Action Proposal: RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) The Evaluation Committee for the above proposal project met April 10, 2018 for purposes of reviewing/ discussing all proposals/ presentations given by the short-listed firms. At the conclusion of the meeting, the Committee ranked the proposals as follows: 1st _Intergraph Co d/b/a Hexagon Safet & Infrastructure 2"d Motorola Solutions Inc 3' Su erion, LLC Recommendation will be made to the Lee County Commission that the County award to the following top ranked firm(s): l" I Intergraph Corp d/b/a Hexagon Safety & Infrastructure Note: All submitters are furnished this notice. A submitter who has cause to file a Notice of Intent to File a Protest against the award must do so in writing to the Procurement Management Director no later than 4:00 p.m. local time on the third working day (Monday -Friday, excluding legal holidays) following the date of this notice. It must clearly state that it is a protest and must include specific information required by the County Government's current directive. Failure to protest on a timely basis, or to include the required information, will invalidate the protest. WWW.LeeGov.Com/Procurement is the County's official posting site NOIDPA ver 05/01/2016 HEXAGON NTERGH SAFETY & INFRASTRUCTURE Response to the Lee County Request for Proposals (RFP) for Computer Aided Dispatch Replacement & Associated Interfaces (CAD) February 20, 2018 Introduction Project RFP Number & Name: RFP180081 LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Hexagon Safety & Infrastructure Firm's Name & Address: 305 Intergraph Way Madison, AL 35758 Firm's Contact Person & Allana Williamson, Regional Sales Manager, Southeast Information (phone, fax and Phone: 256-529-0929 email address): Email: Allana.williamson@hexagonsi.com How many years has Proposer been in business under present 28+ years in Public Safety name? Under what other former names Intergraph Corporation has your organization operated? This RFP response includes data that shall not be disclosed outside the Agency and shall not be duplicated, used, or disclosed —in whole or in part —for any purpose other than to evaluate this RFP response. If, however, a contract is awarded to this offeror as a result of —or in connection with —the submission of this data, the Agency shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting contract. This restriction does not limit the Agency's right to use information contained in this data if it is obtained from another source without restriction. #1 HEXAGON SAFETY& INFRASTRUCTURE LEE COUNTY, FL INTERGRAPH RFP FOR CAD REPLACEMENT TABLE OF CONTENTS Cover Letter and Executive Summary.........................................................................................................i TAB 1 - Qualifications of Company..........................................................................................................1-1 TAB 2 - Company Relevant Experience and References..................................................................... 2-1 TAB3 - Firm Plan of Approach............................................................................................................... 3-1 Attachment 3.1 - Sample Project Schedule..................................................................................A3.1-1 Attachment 3.2 - Training Course Descriptions..........................................................................A3.2-1 Attachment 3.3 - Lee County Master Service Agreement(10-13-2017).....................................A3.3-1 Attachment 3.4 - Exceptions to Lee County RFP180081LKD.....................................................A3.4-1 TAB 4 - Response to Functional Specifications Matrix....................................................................... 4-1 Attachment 4.1 - System Configuration Diagram........................................................................A4.1-1 Attachment 4.2 - System Architecture and Stage and Install Assumptions.............................A4.2-1 Attachment 4.3 - Matrix Response 6-096_Location Verification Attach ment_(proprieta ry).... A4.3-1 TAB5 - Price Proposal............................................................................................................................ 5-1 TAB6 - Required Forms.......................................................................................................................... 6-1 Certificate of Authorization - Richard L. Morris.................................................................................6-2 Form 1 - Solicitation Response Form.............................................................................................. F1-1 Form 1 a - Proposal Form........................................................................................................... F1 a-1 Form 1c - Minimum Requirements Table (RFP)....................................................................... F1c-1 Form 2 - Affidavit Certification Immigration Laws.......................................................................... F2-1 Form 3 - Reference Surveys............................................................................................................. F3-1 Form 3 - Lee County RFP Reference —Manatee County, FL.................................................................. Form 3 - Lee County RFP Reference —Martin County, FL...................................................................... Form 3 - Lee County RFP Reference —Plantation, FL............................................................................. 1 HEXAGON AGC]URE LEE COUNTY, FL INTERGRAPH RFP FOR CAD REPLACEMENT Form 3 - Lee County RFP Reference —St. Petersburg, FL...................................................................... Form 3 - Lee County RFP Reference —Huntsville 911, AL...................................................................... Form 3 - Lee County RFP Reference —Mobile, AL.................................................................................. Form 3 - Lee County RFP Reference_ Shelby County, AL..................................................................... Lee County_Additional References.............................................................................................. R-1 Form 4 - Negligence or Breach of Contract Disclosure Form ....................................................... F4-1 Form 5 - Affidavit Principal Place of Business............................................................................... F5-1 Form 6 - Sub -Contractor List (N/A).................................................................................................. F6-1 Form 7 - Public Entity Crimes Form................................................................................................. F7-1 TAB7 - Case Studies.................................................................................................................................7-1 FrederickCounty Case Study...................................................................................................................... Uttar -Pradesh Case Study........................................................................................................................... Swiss Border Guard Case Study................................................................................................................. South Tyrol Civil Protection Agency Case Study......................................................................................... Officeof UCC Case Study........................................................................................................................... Louisville Metro Safe Case Study......................................................................................................... ...... 2 Hexagon Safety & Infrastructure 305 Intergraph Way I HEXAGON INTERGWH ' Madison, AL 35758 SAFETY & INFRASTRUCTURE p: 1.256.730.2000 www.hexagonsafetyinfrastructure.com February 16th, 2018 ATTN: Lori DeLoach, CPPB, Procurement Analyst Lee County Procurement Management 1500 Monroe Street 4th Floor Fort Myers, FL 33901 Reference: RFP180081 LKD — Computer Aided Dispatch Replacement & Associated Interfaces (CAD) To Lori DeLoach and the Reviewing Members of RFP submittals: Intergraph Corporation, doing business as Hexagon Safety & Infrastructure (Hexagon), is pleased to participate in Lee County's solicitation for a Computer Aided Dispatch System (CAD). Our attached proposal is reflective of a Next Generation -compliant, integrated Computer Aided Dispatch (I/CAD) and Mobile Data Computer solution, able to meet the County's need for a state-of-the-art communications platform. As a long-term Public Safety leader of over 28 years, Hexagon's Intergraph products offer a combination of reliable, current functionality, built on non-proprietary hardware, and configured to exploit stable, up-to- date technology. Our I/CAD solution provides a scalable, integrated Public Safety Technology System reflecting best -practice solutions in the industry which easily accommodates PSAPs of all sizes and complexities. Hexagon is a reputable, large -municipality vendor with the proven capability to exceed the County's requirements for a state-of-the-art CAD and Mobile solution. Hexagon's history of technology excellence, customer satisfaction, go -live success rate, and customer -retention achievement are unsurpassed in our ever -evolving and highly competitive industry. We are extremely confident that our solution can fully address all of the County's concerns and objectives. A high-level summary of our solution for the County includes the following products and services: • Software I/CAD Mobile for Public Safety (MPS) I/NetViewer InSight Reporting EdgeFrontier Integration Platform Interfaces d Professional Services Project Management CAD and MPS Implementation Services CAD Interfaces Implementation Services Mapping Services Page 1 s Maintenance: Extended Intergraph Software Warranty Intergraph Software Maintenance A HEXAGON SAFETY & INFRASTRUCTURE Lee County, Florida RFP for CAD Replacement & Associated Interfaces Reporting/Analytics Implementation Services �* Training Services Virtual Server Staging and Installation services Hexagon notes that our proposal response is valid for one -hundred -eighty (180) days from the RFP due date of February 201h, 2018 Thank you for this opportunity to provide highest -value service to the County's residents and visitors. If you have any questions regarding the enclosed information or require any additional information, please contact Allana Williamson by telephone at 256-529-0929 or by email at allana.williamson@hexagonsi.com. Sincerely, Waua W"a.MAn Allana Williamson Regional Sales Manager, Southeast Intergraph/Hexagon Safety & Infrastructure AUTHORIZED INTERGRAPH SIGNATURE Signature: Date: February 161h, 2018 Name: Richard L. Morris, Senior Divisional Counsel Hexagon Safety & Infrastructure Page 2 SASAFEEXAGC]URE LEE COUNTY, FL INTERGRAPH RFP FOR CAD REPLACEMENT EXECUTIVE SUMMARY Understanding the Goals and Desired Outcome for Lee County This Computer Aided Dispatch (CAD) software procurement marks a defining moment in Lee County's history of protecting lives and property. With the replacement of the existing system, the County has an opportunity to positively impact its Fire Rescue strategies and life-saving operations for years to come. The County seeks a modern system compatible with Next Generation 9-1-1 (NG 9-1-1) technologies that will extend its dispatch functionality, reduce response times, and streamline the dispatching process. As the County grows, the CAD and Mobile Data System must be scalable, provide the latest in CAD functionality, improve performance, and better protect the citizens of Lee County. The deployment must be led by an established partner using a proven methodology that reduces project risk, smoothly transitions users to the new system, and provides 911-worthy maintenance and support. The County is looking for a partner that is as invested in the daily operations and overall project success of the 911 program as they are. Hexagon's Intergraph I/CAD System has flawlessly operated at similar sized agencies for over 28 years, and the Hexagon Team is prepared to bring that same reliability and experience to Lee County. Accomplishing Lee County's Objectives with Hexagon's Intergraph CAD and Mobile Solution With Lee County's goal in mind, Hexagon has proposed its Intergraph I/CAD 9.4 suite along with its Intergraph Mobile for Public Safety (MPS) application that will deliver functionality the County needs. I/CAD is trusted by the public safety community worldwide, and supports operations of more than 2,500 agencies in 28 countries. The County can implement applications, interfaces, business rules, and workflows to meet their current needs and future growth needs from single agency to multi -agency hub -and -spoke deployments. In the event Lee County decides to expand the system to include additional agencies, I/CAD 9.4 has the proven capability to grow and handle multiple agencies and multiple jurisdictions. New Functionality for Lee County CAD Users "Hexagon's proven solution provides us with a highly adaptable system, configurable to meet our needs and workflows. With Hexagon's dispatching and mobile software, we are positioned to expand our service offerings through interoperable regional solutions. " Mike Grigsby - Kansas City, MO Police Department Hexagon's I/CAD solution provides new public safety functionality that meets the County's technical requirements, including: 0 Call Handling and Dispatch: With I/CAD, Lee County dispatchers and supervisors benefit from streamlined tools to field calls, create and update events, and immediately manage resources from a single interface. I/CAD will automate key functions and enable users to easily visualize calls, events, and resources. From day-to-day operations to exceptional events, Lee _ HEXAGON SAFETY & INFRASTRUCTURE Executive Summary County users can dispatch services more effectively, monitor events and personnel more comprehensively, and empower responders with more accurate and up-to-date information. Intergraph Mobile for Public Safety will provide Lee County access to critical information to connect Lee County dispatchers and first responders in the field. It will enable the County to deploy mobile dispatch capabilities on laptops with MPS or smartphones and tablets with the optional Mobile Responder product. Features include but are not limited to: updated event details, access to databases, and the ability to send and receive messages. Mappincq° I/CAD provides intelligent maps for effective management of events and resources. Lee County administrators can automate and streamline map creation and updates. Dispatchers and field personnel benefit from feature -rich maps displaying data from many sources. e Reporting and Analysis With InSight Reporting for CAD, the County can create reports on operational data to manage performance and identify trends. With our business intelligence software, the County can access, analyze, and report on large volumes of data, providing the insight to improve operational planning, performance, and decision -making. e Application and Device integration: Hexagon provides Intergraph EdgeFrontier, an enterprise integration platform, to integrate applications, databases, and devices. This capability allows connections to EdgeFrontier to automatically synchronize event and unit information to and from the CAD system. Regionalization: Should the County decide to expand its user -base to include the Sheriff's Office or Fort Meyers Police Department, Hexagon brings more than 28 years of integration experience supporting connectivity between surrounding jurisdictions, including numerous complex, multi -agency, multi -jurisdictional environments similar in size and scope to Lee County. Many surrounding agencies like Manatee County, Sarasota County, and the City of Plantation have a multi -agency call center supporting the disciplines of Fire, Police, and EMS. This approach allows each agency to have their own separate build while still operating on the same platform. Distinguished Components of the Hexagon Solution Calltaking, dispatching, and routing mobile units to a dispatched event is inherent in all CAD and mobile solutions. Hexagon has distinguished itself as the industry leader for system availability and reliability to accommodate customers with a proven and tested solution. rr Lee County Can Invest in an Industry Leader Lee County's CAD procurement is a major, long term investment. Hexagon historically has been and remains to be the leader in the CAD and Mobile industry. Research analytics by IHS MarkitTA°, for 2016's "Command and Control Room" market purports Hexagon (Intergraph) as the #1 firm globally. Hexagon's Intergraph software protects 1 in 10 people worldwide Hexagon has approximately 245 operational sites globally, many of which are largely consolidated and regionalized countries, counties, and entire states Hexagon earns more than $450 million in annual revenue, of which 8% is re -invested in `Research and Development' for future products and enhancements. i/ HEXAGON SAFETY & INFRASTRUCTURE • System Reliability and Performance Executive Summary Hexagon's server solution supports high availability standards using virtualization and server clustering to provide intrinsic redundancy. To support continuous operations during upgrades and/or expansions, Hexagon has built the I/CAD Database access layer and specific standard interfaces to provide seamless application -level failover. This enables the System Administrator to perform seamless hardware or software updates. Chicago O'Hare and Midway International Airports have been long standing customers of Hexagon (Intergraph) for over 20 years. With a combined total of almost 100 million passengers annually, the system has had zero unscheduled downtime. Uttar Pradesh (with 220 million residents, the most populous state in the Republic of India), handles over 200,000 calls per day with 114 online Dispatcher positions and 250 online Call Takers positions. Toronto Police Service, population of over 2.8 million people, has had zero unscheduled downtime in more than 23 years. • Recent Case Study: Hurricane Irma During the weekend of September 9, 2017, Hurricane Irma —one of the largest in U.S. history —made landfall in the Florida Keys on Saturday and moved northwest through the state of Florida. The strength of the hurricane ranged from a Category 2 up to a Category 5 with reported winds sustaining 130 mph and caused widespread damage in many locations. According to MissionCritical Communications, Hurricane Irma affected 28 PSAPs, of which 14 agencies were taken completely down in Florida and the U.S. Virgin Islands. Hexagon is pleased to report that none of our customers experienced such system failure. In addition to our superb system reliability, Hexagon's Customer Support Manager personally contacted customers via email and phone before and after the hurricane. This personal communication to each agency ensured them our Support Desk was staffed and prepared for the duration of the storm in their greatest time of need. In some cases, call volumes quadrupled during the height of the storm and Hexagon's Intergraph I/CAD trounced the increased volume. In follow-up calls it was stated the system worked flawlessly throughout Hurricane Irma and helped immensely in response efforts. Concurrent Licensing Model Our concurrent licensing model is a cost-effective approach for user access to I/CAD for dispatchers, calltakers, and mobile units. Concurrent licensing allows the normal licensed number of users to be logged on during any given shift. Each discipline across PSAP(s) shares the pool of licenses while each user still has their unique permission -based log -in credentials. • Multi -Agency, Multi -Jurisdictional, Multi-PSAP Interoperability with EdgeFrontier Hexagon's integration software, EdgeFrontier, provides our customers interoperability of disparate databases, devices, and other third -party software applications. As the County has requested, EdgeFrontier is our proposed solution for the four (4) CAD to CAD connections with Spillman Technologies, Motorola PremierOne, OSSI Visual CAD, and TriTech, in addition to multiple custom interface requirements. HEXAGON SAFETY & INFRASTRUCTURE Key benefits include: Reduction of interface development time and services delivery Reduces risk associated with interface development and delivery Lowers maintenance costs and decreases total cost of ownership Executive Summary EDGE • FRONTIER Introduces a version -independent platform for integration to internal and external systems Simplifies upgrades and maintenance Hexagon has successfully implemented CAD -to -CAD connectors where other vendors have failed or never tried. Hexagon's history is an excellent predictor of future success and the best guarantor for the County's success. Hexagon maintains hundreds of installations supporting thousands of agencies worldwide and product offerings designed for maximum multi -agency deployment and success. Hexagon solutions around the world support environments exactly like the County, while maintaining the flexibility and configurability needed to support an uncluttered GUI. To learn more about EdgeFrontier through the eyes of a current customer, please see the Frederick County case study in response Tab 7 — Case Studies. Lee County's Ongoing Customer Support & Maintenanc( Hexagon is extremely protective of its 98-percent customer retention achievements across many years of its corporate history, each earned by dedicated service and best -value products for all our customers, small to medium to large. Hexagon has more than 28 years of experience implementing its Intergraph system for many top -tier customers comparable in magnitude and complexity to Lee County. These include some of the largest municipalities, countywide dispatch systems, and major aviation and ground -transportation agencies domestically and around the world. Customers similarly sized like Lee County include but are not limited to: Westchester County, NY Manatee County, FL City of San Diego, CA Washington D.C. City of Plantation PD & Fire, FL Suffolk County, NY Palm Beach County Fire & Rescue, FL Nassau County, NY _ HEXAGON SAFETY & INFRASTRUCTURE Martin County Fire & Rescue, FL Mobile County, AL Salt Lake County, UT Boston Fire & PD, MA City of St Petersburg PD, FL Madison County, AL (Headquarters 911) We urge you to contact any of our customers to independently ascertain their level of satisfaction with our product, implementation, and services. Executive Summary "Over 25 years we have depended on [the] Hexagon CAD system, they have proven to be reliable, flexible and scalable..." Un Lee, Huntsville -Madison County 911 Hexagon is committed to completing Lee County's transition to I/CAD 9.4 using our proven and reliable deployment methodology that has resulted in zero downtime for comparable system migrations. Providing Post Cutover Support to Lee County Beyond our standard implementation, Hexagon ensures a customer support system is in place after cutover and close of the project. Hexagon offers support ranging from 24/7 availability via the toll -free Help Desk, to consistent on -site visits from the Regional Sales Manager, and help from the assigned territory Account Manager stationed at the headquarters in Huntsville, AL. Your Account Manager will have direct access to management, development and Help Desk personnel, and implementers who are instrumental in addressing unresolved issues and open action items. Customer Support Customer Support is an integral part of Hexagon's Warranty and Maintenance program. Hexagon provides this support at no additional cost with the purchase of the system (1 st Year of Maintenance) or with the purchase of additional years of maintenance. The special support requirements for mission -critical Public Safety systems are met by providing the following: Toll -free access to Hexagon Customer Support Center resources "Always -available" support during Extended Warranty and Maintenance Response times monitored by priority Problem resolution based on priority level "Hexagon personnel are professional, hardworking, and easy to work with." Anne Chance, IT Manager — Public Safety Department, Manatee County Government Lee County's system is mission -critical and to meet the County's ongoing needs long after implementation, Hexagon provides error resolution as described above. Hexagon has a documented and successful methodology for error reporting and resolution and a committed sense of urgency to address Lee County's needs. • Regional Sales Manager and Account Manager Support Allana Williamson will continue to act as your Regional Sales Manager (RSM), and will be Lee County's main point of contact throughout the duration of the project and post cutover. Allana will maintain contact with the County's stakeholders, administrators, and be HEXAGON SAFETY & INFRASTRUCTURE Executive Summary responsible for the County's account in its entirety as the conduit for all communication regarding action items. The Account Manager is a second layer of Customer Support reporting directly into the headquarters in Huntsville, AL. The headquarters houses developers, Executive Management, implementers, Help Desk, maintenance department, finance, and administration personnel for the day-to-day operations of Hexagon. The Account Manager will work with your Regional Sales Manager to address any services or software concerns or needs once the County is live in production. 19 Public Safety User's Group "We have had great experiences with their knowledgeable and helpful implementation and support teams. " Frank Ullven, IT Manager — City of St. Petersburg, Police Department The User Group is an active, non-profit organization consisting of nationwide users of Hexagon's Intergraph CAD and RMS. The group has an online presence and annually hosts a National User's Group Conference to collaborate for educational information and training. The mission of the User Group is to: Provide a forum for communicating ideas, resolving problems, and increasing effectiveness of users regarding Hexagon's Intergraph line of Public Safety software products Provide a forum for suggested enhancements, changes, and future development of Hexagon's Intergraph Public Safety software products Provide an internet presence through a world-wide web site and list -server through which information is provided to group members. The domain name hpsug.org has been procured for the organization's use Provide a secure, centralized web -based repository of contact information for Hexagon support personnel and Hexagon customers Conclusion Hexagon respectfully submits our proposal to Lee County and the members of the Evaluation Committee for review and consideration. The County requires the services of a vendor with expertise that will meet and exceed your goals and desired outcomes. With 28 years of proven experience with similar sized agencies, Hexagon has the successful track record to exceed the County's goals. We look forward to adding Lee County Fire and Rescue to our Public Safety community. HEXAGON SAFETY & INFRASTRUCTURE fi�RAPH - QUALIFICATIONS OF COMPANY 11 HEXAGON SAFETY& INFRASTRUCTURE IrvrERGwAPH LEE COUNTY, FL RFP FOR CAD REPLACEMENT NVEEFW- I TAB 1 - QUALIFICATIONS OF COMPANY Intergraph Corporation d/b/a Hexagon Safety & Infrastructure (Hexagon) has included RFP text verbatim in bold, italicized font below. Hexagon responses follow in regular text. 1. General Company Information a. Company Profile 1) Identify all company locations Global Headquarters 305 Intergraph Way Madison Alabama, 35758 United States Columbia Office 10 Columbia Corporate Center 10400 Little Patuxent Parkway, Suite 200 Columbia, MD 21044 Norcross Office 5051 Peachtree Corners Circle, #100 Norcross, GA 30092 2) Identify the number of employees As of May 2017, Intergraph Corporation's employee numbers are as follows: a) Employed by the company in total Worldwide — 4,915 • US — 1,874 • Hexagon Safety & Infrastructure (Worldwide) — 2,047 • U.S. Hexagon Safety & Infrastructure — 1,018 b) Dedicated to sales Hexagon Safety & Infrastructure Sales — 63 c) Dedicated to technical support Hexagon Safety & Infrastructure Technical Support — 527 d) Dedicated to research and development R&D — 191 HEXAGON SAFETY & INFRASTRUCTURE b. Company Longevity 1) Indicate the number of years in business Founded in 1969, Intergraph's history spans 48 years. TAB 1 — Qualifications of Company 2) Indicate the number of years in business selling the CAD system solution solicited herein (minimum of ten years' experience) Intergraph introduced the first map -based computer aided dispatch system in 1989 and has been in the Public Safety industry for 28 years. 3) Provide details on the company acquisitions in the last five years, including company name and dates; include companies acquired by the Respondent and the Respondent's company being acquired N/A - Intergraph Corporation was acquired 7 years ago by Hexagon AB, a Swedish company, in 2010. Company History Intergraph's history spans 48 years, during which the company has grown from a locally owned startup founded by former NASA contractors to a globally based geographical software manufacturer. The company provides spatial management information, infrastructure protection, and integration services to assist users in understanding complex data through visual representation. Today Intergraph's core public safety software protects 1 in 12 people around the world. Founded in 1969 and originally named M&S Computing, Inc., the company initially set out to solve one of the most difficult problems of the time — how to put a man on the moon. In the beginning, M&S Computing focused on developing systems that applied digital computing to real-time missile guidance. The byproduct of this work was the development of computer graphics systems that allowed engineers to display and interact with drawings using the language of the application rather than programming terminology. Our initial software, which began as a portal to underlying data, grew into a powerful visualization solution providing 3D modeling and photorealistic rendering that had enormous potential. The company expanded its product line, extended its platforms to new arenas, and renamed itself Intergraph to represent its entry into the interactive graphics market. Intergraph grew and the demand for graphical representation became even more valuable as a critical decision support and project management solution. In 2010, Intergraph was acquired by Hexagon AB, a Swedish company. In acquiring Intergraph Corporation, Hexagon AB combined its global 3D solutions used for precision design and measurement with Intergraph's geospatial software platform. As stated by Ola Rollen, CEO of Hexagon AB and Intergraph Corporation, "It is our intention that Intergraph's solutions will become Hexagon's core software platform, providing differentiated and vertically focused software solution. By combining Intergraph's technologies with our global resources and technologies, Hexagon will be able to create new and exciting solutions to customers going forward." Today, Intergraph technology enables its customers to make the world safer and create prosperity by using intelligent maps, managing assets, protecting infrastructure, building and operating more efficient plants and ships, and dispatching emergency services. Our mission is to earn the respect and trust of our _ HEXAGON SAFETY & INFRASTRUCTURE TAB 1 — Qualifications of Company customers through total commitment to their success, deep industry expertise, and a long tradition of technical innovation. Intergraph is proud to be a worldwide leader in the Public Safety and Security software market, and our commitment to customers is unparalleled in the industry. Today Intergraph has implemented Public Safety systems in 27 countries using 14 languages. These implementations allow us to incorporate best - of -breed public safety functionality from around the world into our products and bring them back to customers like Lee County in the form of a highly configurable, commercial off -the -shelf (COTS) solution. Public Safety Market Experience Intergraph develops, markets, implements, and supports computer -based solutions for fire departments, emergency medical and rescue units, law enforcement organizations, and other public safety agencies. Intergraph offers technologically advanced solutions designed to capture, integrate, and display complex data using a geospatial platform. Intergraph entered the Public Safety industry in 1989 with the introduction of the I/CAD System, which coupled forms -based dispatching with an interactive map. Following Intergraph's launch of the first "map centric" CAD software, Intergraph's Public Safety & Government Business Unit has consistently built on the I/CAD System technical platform and continued to push CAD technology forward. To date, Intergraph has led the market with some of the following I/CAD releases: 1989, Intergraph introduced the first map -based computer aided dispatch system 1995, Intergraph released the first end -to -end Windows -based CAD platform, employing Windows -based operating systems on both servers and clients 1998, Intergraph introduced CAD web applications 2004, Intergraph's video analysis capability was released, enabling investigators to manage and enhance video images to identify persons engaged in criminal activity This video analysis technology was used in Boston, Massachusetts to identify Tamerlan and DzhokharTsarnaev In 2005, the I/CAD Map was integrated with alarm, video, and sensor data feeds to enhance internal and perimeter security for infrastructure, such as airports, harbor/ports, subways, and tunnels 2007, the release of I/Incident Analyst provided comprehensive map -based reporting 2008, Integrated database reporting functionality took a major step forward with the introduction of Intergraph's Business Intelligence for Public Safety product, selected by APCO as a 2008 "Hot Product" and winning a feature article in Public Safety Communications magazine 2009, the APCO show produced another Intergraph "Hot Product," selection for our Interoperability Framework for CAD product. This selection represented the second consecutive year that an Intergraph application received this prestigious award and was featured in the Public Safety Communications magazine 2012, Intergraph's I/CAD 9.2 product was selected a third time as the year's "Hot Product" 2014, released next -generation communications CAD system 2016, Intergraph released version of I/CAD 9.4 in September with new and enhanced capabilities that will help public agencies deliver even faster responses and a more efficient use of resources _ HEXAGON SAFETY & INFRASTRUCTURE TAB 1 — Qualifications of Company Today, Intergraph maintains a global public safety customer base, which encompasses such diverse organizations as the Toronto Fire Service, Canada; the Washington D.C. Metro Police and Fire; the Police and Fire Services for the country of New Zealand; and Fire and Emergency Medical Services for Bouches-du-Rhone, France. Intergraph Corporation's Hexagon Safety & Infrastructure division (herein after referred to as "Hexagon") has more than 2,000 employees worldwide. Project implementation personnel average 15+ years of public safety experience per employee and 13+ years of experience per employee in our support and services organization. This level of experience ensures that, as the Prime Contractor, Hexagon understands the issues and requirements of the County, as well as long-term business objectives. 4) Subcontractors, if applicable, will be required to have a minimum of three years of experience in their respective discipline N/A — Hexagon has not proposed a subcontractor for the Lee County response. 2. Capacity a. Time is of essence for this project; therefore, the successful Respondent must be able to perform the work in a timely manner. Present an outline of the Respondent's current workload, present capacity for additional work, and projected future workload, demonstrating ability to respond to County project requirements and complete by April 2019. For capacity, please reference page 1 for the number of employees. Hexagon clarifies that Hexagon personnel are committed to support existing customers, ongoing implementations, and potential new customers. Future workload is dependent upon work requested by existing customers and new customers. Hexagon has provided information below under "Respondent's Key Personnel" with regard to personnel availability. While Hexagon is the industry leader and has many ongoing projects, it represents it can perform the proposed project in a timely manner subject to the finalization of the resulting contract by April 2018. Hexagon acknowledges the County's request for details about specific Hexagon Customer projects; however, due to customer confidentiality agreements, Hexagon cannot provide specific details being requested. Hexagon has included a sample project schedule with our proposal that outlines the expected implementation and cutover timeline for the proposed CAD/Mobile system. Hexagon acknowledges the County's desire to completely implement the new system by April 2019. Hexagon realizes that given the County's timeframe for evaluations and short list discussions in March 2018 and final scoring/selection in April 2018, negotiations may not begin until the end of April/early May 2018. Negotiations may be completed during the months that follow. The current proposed sample project schedule includes an expected duration of 15 months. Hexagon assumes the project schedule will be finalized and mutually agreed to during contract negotiations and will work with the County to implement the system in a timely, efficient manner. Hexagon prides itself on working and succeeding in a challenging and consequential industry. Projects of this nature involve both parties performing a variety of tasks that are dependent upon one another. With that type of relationship and the number of tasks involved, from time to time delays occur. However, _ HEXAGON SAFETY & INFRASTRUCTURE TAB 1 — Qualifications of Company Hexagon has a proven track record of working with its customers to navigate and overcome those challenges to successfully implement its public safety software solutions. 3. Respondent's Key Personnel a. Respondents must provide information demonstrating the technical knowledge (including all training and certifications) of all key personnel involved in the implementation in the scope of work. Please refer to the answer to #3b below. Hexagon reserves providing information demonstrating technical knowledge of all Hexagon key personnel to be involved in the implementation and customer references for those personnel until they are committed. b. Respondents must provide resumes of the Respondent's project manager and other key design and implementation personnel (identified on an organization chart) that will be assigned to this project that illustrates their qualifications, educational levels, experience, licenses and/or certificates, technical skills, and availability. For each key person, provide a list of relevant projects they have worked on within the past five years with the following information: 1) Project title and location 2) Role, responsibility, and decision authority 3) Point of contact with the customer Hexagon has nominated a "tentative" Project Team that represents the skills and experience of personnel likely to be assigned to the County's Project. However, Hexagon has numerous projects in various stages of completion, as well as numerous proposals in various stages of evaluation. Because the timeline associated with project evaluation, negotiation, and the schedule is subject to many variables, it is not possible to firmly identify individuals who will be available should Intergraph be selected for the County's Project. However, Hexagon commits to providing an experienced, professional Project Team that will ensure the County's Project success. At the time of award, Hexagon will select the appropriate Project Team based on availability, experience, and nature of the requirements. Once in place, Intergraph agrees key personnel will remain assigned to the County's Project through completion unless unavailable due to death, illness, disability, or termination of the employment relationship. Hexagon has therefore included the following resumes as samples: Project Manager: Beau Elliot CAD Implementation Lead: Mike Kelly CAD Training Lead: Gwen Walker CAD COTS Interfaces Lead: Michael Magliozzi CAD EdgeFrontier Interfaces Lead: Mo Singh Hexagon notes that this is not a commitment to who will be on the project; it is only sample of the experience we have. The final assignments of personnel to the project depends on when the project will start. Depending on further discussions with Lee County of who will be assigned to the project, Hexagon _ HEXAGON SAFETY & INFRASTRUCTURE TAB 1 — Qualifications of Company reserves providing individual customer references for those personnel until the personnel assignments are committed. Resumes begin below. BEAU ELLIOTT Program Manager I QUALIFICATIONS Dr. Elliott has several years of experience in operations planning and providing technical direction and coordination for Public Safety System Contracts. His responsibilities have included managing and directing large-scale development teams, coordinating training, deployment strategies, and management of budgets, personnel and purchasing. TECHNICAL EXPERTISE • Software Expertise JOB HISTORY Hexagon Safety & Infrastructure: Program Manager I, April 2017 — Present University of Alabama in Tuscaloosa, Center for Advanced Public Safety: Deputy Director, August 2014 — March 2017 University of Alabama in Tuscaloosa, Center for Advanced Public Safety: Assistant Research Engineer; December 2006 —August 2014 University of Alabama in Tuscaloosa, Center for Advanced Public Safety: Graduate Research Assistant, August 2004 — November 2006 .NET, C#, JavaScript, HTML, CSS, XSL, SQL, Microsoft Visual Studio, Eclipse, Atom, PowerShell, Microsoft Office suite including Project and Visio. Mac OS 0 Hardware Expertise PCs, workstations, virtual server environments, Macintosh, and servers EDUCATION PhD Computer Science, University of Alabama, Tuscaloosa, AL, 2017 M.S. Computer Science, University of Alabama, Tuscaloosa, AL, 2006 B.S. Computer Science, University of North Alabama, Florence, AL, 2003 PROFESSIONAL SKILLS AND ABILITIES Leadership, time management, well -organized, analytical, problem solving, team player, managing multiple projects/tasks concurrently, and developing positive relationships with customers across multiple stakeholders _ HEXAGON SAFETY & INFRASTRUCTURE PROFESSIONAL EXPERIENCE City of Des Moines, Iowa (2017) TAB 1 — Qualifications of Company The city of Des Moines and the Polk County Sheriff's office upgraded their Intergraph I/CAD and I/Mobile systems to the current versions of these products. Dr. Elliott's responsibilities included: project management and coordination of the delivery of software, training, testing, and implementation support. City of New York, New York (2017) New York City is upgrading its dispatcher workstations and server/SAN infrastructure that supports the Intergraph I/CAD system. Dr. Elliott's responsibilities include: project management and coordination of hardware replacement for both workstation and server hardware. Dr. Elliott coordinated the cutover to production with the new systems. Harford County, Maryland (2017) Harford County is upgrading its OPURSUIT RMS system to the latest version. This upgrade includes upgrading FBR as well. Dr. Elliott's responsibilities include: project management and coordination of the delivery of software, training, testing, and implementation support City of San Jose (2017) The city of San Jose added an interface to their I/CAD system. The interface is an emergency vehicle pre-emption interface that allows the city to interface the CAD system with the city's traffic light vendor TransCore. This will allow emergency vehicle the ability to pre-empt lights and allow the emergency vehicles access through traffic lights around the city. Dr. Elliott's responsibilities included: project management and coordination of the delivery of software, training, testing, and implementation support City of San Jose (2017) The city of San Jose added an interface to their I/CAD system. The interface will allow the I/CAD system to interface with the PulsePoint system the city is currently using. Dr. Elliott's responsibilities included: project management and coordination of the delivery of software, training, testing, and implementation support HEXAGON SAFETY & INFRASTRUCTURE TAB 1 — Qualifications of Company MICHAEL K. KELLY Senior Systems Consultant QUALIFICATIONS Mr. Kelly has eight years of experience in Intergraph Public Safety / Sensor and Video Integration implementation and seven years of experience in on -site support of Intergraph engineering and mapping products for the U.S. Army Corps of Engineers. As a Senior System Consultant for Intergraph, he has led the implementation of CAD and Security solutions in a wide range of challenging customer environments, from airports and mass transit systems, to border security, to military installations with an emphasis on on - site integration. PROFESSIONAL CERTIFICATIONS JOB HISTORY Intergraph Corporation: Senior System Consultant; 2004 - Present Cooper Carry, Inc.: Director of Information Technology; 2001 - 2003 Intergraph Corporation: Senior Systems Engineer; 1990 - 2001 Garfinkel Architects: Project Manager; 1983 - 1988 • Project Management Institute certification - Project Management Professional (PMP) EDUCATION • Bachelor of Science; Architecture; University of Illinois; Champaign, IL; 1981 • 2-Year Coursework; Architecture Program; University of Florida; Gainesville, FL; 1990 PROFESSIONAL EXPERIENCE New York City Police Department — New York, NY As a member of the 24/7 support team for the New York City Police Department CAD system, Mr. Kelly participated in system health checks, tier 1 support for dispatchers using the system, and deployment and testing of system upgrades provided by the development team. Mr. Kelly also provided report writing services to meet the requirements of the agency's statistics department. Metropolitan Transportation Authority — New York, NY As the Lead Implementer of the Metropolitan Transportation Authority of New York City CAD and Integrated Electronic Security System, Mr. Kelly was responsible for implementing a Software Integration Test Lab, a Staging Lab, and the Final system in several customer facilities. He worked with the Prime contractor to provide test plan development and execution. Mr. Kelly continues to consult with MTA on development and implementation of their Security and Dispatch Centers. H EXA N A A G� SAFETY &INFRASTRUCTURE TAB 1 — Qualifications of Company Metropolitan Washington Airports Authority — Washington, DC area As the Lead Implementer for Metropolitan Washington Airports Authority, Mr. Kelly was responsible for implementing the upgrade of the MWAA Intergraph CAD system and integrated intrusion alarm system. His responsibilities included migration of the system from Oracle to Microsoft SQL Server. Baltimore/Washington International Thurgood Marshal Airport As the Lead Implementer for Metropolitan Washington Airports Authority, Mr. Kelly is responsible for implementing a new Intergraph CAD system for Police, Fire, and EMS response. The system will include the integration of intrusion alarms and surveillance video with the CAD system. His responsibilities include data collection, on -site implementation, and coordination of the CAD system with mobile, alarm, video, and Maryland state interfaces. U.S. Army Corps of Engineers CTRC — Wiesbaden, Germany As on -site technical consultant for U.S. Army Corps of Engineers CADD Training and Resource Center (CTRC) in Wiesbaden, Germany (1994-2001), Mr. Kelly worked with Corps of Engineers personnel to establish and staff a training and resource center for Intergraph CAD and mapping products and systems. He, along with the other members of the Center, directly supported all U.S. Army and U.S. Air Force Engineering departments in Europe. Fort Jackson, GA As the Lead Implementer for Fort Jackson, Mr. Kelly was responsible for planning and implementing an Intergraph CAD system for Police, Fire, and EMS response. His responsibilities included new console design and coordination of the move of the communication center equipment and functions to a temporary location in order to maintain 24/7 operations during the communication renovation. JITC Certification of Intergraph Public Safety Products — Fort Huachuca, AZ As the Certification Lead for JITC certification of Intergraph Public Safety products, Mr. Kelly worked with the Army's Joint Interoperability Test Command (JITC) in Fort Huachuca, Arizona to test and certify the products to meet the interoperability and security standards required of systems that connect to the Defense Switching Network. Certification was received in 2007. GWENDOLYN WALKER Technical Instructor QUALIFICATIONS Ms. Walker has more than 25 years of experience in the public safety arena, with over 18 years of experience as a certified instructor training adults and developing training programs for dispatchers and jailers. Ms. Walker is certified by FEMA in the JOB HISTORY Intergraph Corporation: Technical Instructor; 2007 — Present Collierville Police Department: Communications Supervisor; 1997 — 2007 _ HEXAGON SAFETY & INFRASTRUCTURE Management and Supervision of Training and has more than 100 hours of training in FEMA-sponsored courses. TECHNICAL EXPERTISE Software Expertise Microsoft Office applications; GIS; networking Hardware Expertise PCs and workstations PROFESSIONAL CERTIFICATIONS APCO International Telecommunicator Certification APCO Basic Telecommunicator Officer & Telecommunicator Instructor APCO Basic Communications Training Officer, Instructor, and Training Instructor APCO Communication Center Supervisor APCO Disaster Preparedness for Telecommunicator I and Telecommunicator II TBI Basic Operator Certification and Terminal Agency Coordinator JAC) NCI Basic Telecommunicator Officer and Telecommunicator Instructor National Academy of Emergency Medical Advanced Dispatching (NAEMD) FEMA Emergency CERT Train -the - Trainer and Incident Command 100, 200, 300, 400, 700, and 800 CALEA Assessor TAB 1 — Qualifications of Company Collierville Police Department: Communications Training Officer; 1999 — 2007 Collierville Police Department: Communications Dispatcher/Jailer; 1989 — 1997 Girl Scouts of the Mid -South: Collierville Service Unit Manager; 2004 — 2005 Tennessee Emergency Communications Board (ECB): Advisory Training Committee; 2003 —2004 PROFESSIONAL ASSOCIATIONS Collierville Library Advisory Board Leadership Collierville Board of Directors Collierville Crime Stoppers Board of Directors EDUCATION Management of Supervised Training; National Emergency Training Center, FEMA; Emmetsburg, Maryland; 2007 Bachelor of Science in Emergency Management; Jacksonville State University; Jacksonville, Alabama; 2006 Associates of Applied Science in Public Safety Telecommunications; Gadsden State Community College; Gadsden, Alabama; 2004 International Telecommunicator Certification; APCO Virtual College (taught through Jacksonville State University in Jacksonville, Alabama); Daytona Beach, Florida; 2001 _ HEXAGON SAFETY & INFRASTRUCTURE PROFESSIONAL EXPERIENCE Intergraph Corporation (2007— Present) TAB 1 — Qualifications of Company As a Technical Instructor with Intergraph, some of the projects Ms. Walker has worked on successfully are: Genesee County 911 Consortium, a consolidated E911 center located in Flint, Michigan Manchester, New Hampshire Police Department Richmond, Virginia Police Department. All are multi -agency customers. In addition, Ms. Walker counts the New Jersey Transit Police Department, the Manatee, Florida Sheriff's Office, and the Lauderdale, Alabama Fire Department among her customer training experiences. Ms. Walker also worked with City of Amaretto, Texas as the Lead Trainer where the customer consolidated the communications center to handle fire, police, and EMS calls for service. She has also performed training in Glendale, Arizona; El Paso, Texas; Waukesha, Wisconsin; New York, New York; and at many other agencies. Collierville Police Department (1997— 2007) As the Communications Supervisor for the Police Department, Ms. Walker scheduled the Communications staff for daily operations and special events. She was responsible for discipline, training, and performance evaluations. She created the Collierville Communications Training Manual for Dispatching. As a Communications Training Officer, Ms. Walker created the Policy and Procedure Manual and developed accreditation forms for Communications personnel. She also created the Communications Training Officer (CTO) manual and supporting documentation (Daily Observation Report forms). Ms. Walker maintained the Communications training budget, schedules, and performance evaluations. She managed the training and record -keeping for Communications personnel. As a Communications Dispatcher/Jailer, Ms. Walker answered incoming calls for Police, Fire, and Medical emergencies. She provided emergency medical dispatching (NAEMD) when needed. She also performed NCIC transactions to authorized personnel and assisted with training newly hired dispatcher/jailers. Ms. Walker processed prisoners into the Town of Collierville Jail. She maintained documentation for the CALEA accreditation files. Girl Scouts of the Mid -South (2004 — 2005) As the Collierville Service Unit Manager, Ms. Walker managed more than 52 troops and 450+ scouts. She prepared and directed the service unit monthly meeting. Ms. Walker created and implemented growth plans that resulted in a 10 percent increase in membership. Tennessee Emergency Communications Board (ECB) (2003 — 2004) Ms. Walker developed recommendations to improve the training requirement for all emergency dispatchers throughout the State of Tennessee. The recommendations were implemented by the State on January 31, 2006. HEXAGON SAFETY & INFRASTRUCTURE TAB 1 — Qualifications of Company MICHAEL MAGLIOZZI Systems Engineer QUALIFICATIONS Mr. Magliozzi is responsible for the setup, install, configuration, troubleshooting, and implementation of COTS and custom interfaces with Computer Aided Dispatch (CAD) as well as installing and training on Hexagon's EdgeFrontier software. Mr. Magliozzi has over 14 years of service in public safety. PROFESSIONAL CERTIFICATIONS SQL 2008 Certification TECHNICAL EXPERTISE Software Expertise JOB HISTORY Intergraph Corporation: Public Safety; System Engineer; 2016- Present ZOLL Medical: Systems Engineer; 2002 — 2016 Navisite Incorporated: Windows Engineer, Customer Service; 2000 - 2001 Raytheon Corporation: Information Technology; 1986 - 2000 ASP, ASP.NET, Visual Basic, HTML, XML, XSL, SQL, PL/SQL, C++, and C#, XP/7/8/10 SQL Server 2000/2005/2008/2012, and Microsoft Visual Studio.NET, Windows Server 2003/2008/2012 Hardware Expertise Servers, virtual servers, and desktops EDUCATION • Implementation/administration of Server2008 Active Directory; Glow Training Center • Implementation/administration of Network Infrastructure Pinnacle • Implementation/administration of Server2008 and Windows 7; Pinnacle • Implementation/administration of SQL2008, Pinnacle Training Center PROFESSIONAL EXPERIENCE Wayne County NY Installed and configured Mobile Responder and provided training to the customer. Kansas City, MO Installed and configured Mobile Public Safety with customization of the platform. LA _ HEXAGON SAFETY & INFRASTRUCTURE TAB 1 — Qualifications of Company El Paso, TX Participated in the teaching of EdgeFrontier. Aurora, CO Installed and configured Informer to the state for a new system called OFML. 1-13 HEXAGON SAFETY & INFRASTRUCTURE TAB 1 — Qualifications of Company MOHINDER SINGH Master Process Consultant QUALIFICATIONS Mr. Singh has experience in software/hardware implementation and development in networking, graphical user interfaces (GUIs), relational database management systems (RDBMSs), and client/server applications. He has hands-on experience leading all stages of system implementation, and he has excellent analytical and problem -solving skills. Areas of expertise include computer -aided dispatch implementation, Intergraph Interoperability Framework (I IF), Microsoft BizTalk 2009, Intergraph BI for CAD, design and development of client/server applications, network and system security, relational database management systems (data integrity and disaster recovery), and team and project leadership. PROFESSIONAL CERTIFICATIONS Certified Oracle 10g DBA TECHNICAL EXPERTISE Software Expertise: JOB HISTORY Intergraph Corporation: Master Process Consultant; 2006 - Present Intergraph Corporation: Staff Consultant; 2000 - 2006 Intergraph Corporation: Senior System Consultant; 1997 - 2000 Intergraph Corporation: System Consultant; 1991 - 1996 United Charities: LAN System Manager; 1989 - 1991 Lante Corporation: Consultant; 1986 - 1989 Windows 2000/XP/Windows 7 and Linux (Red Hat) operating systems; LAN/WAN configuration and management, VPN, TCP/IP, Network General Sniffer LAN Analyzer, HP OpenView, and Microsoft SMS networking; VB.Net, C++, ASP, ASP.NET, PL/SQL, Transact -SQL, VBScript, Perl, and Microsoft Access languages; Oracle 11 g and Microsoft SQL Server 2008 relational database management systems; Microsoft BizTalk 2009 EDUCATION Master of Science in Computer Science; Illinois Institute of Technology; Chicago, Illinois; 1989 Bachelor of Science in Computer Science; Illinois Institute of Technology; Chicago, Illinois; 1986 PROFESSIONAL EXPERIENCE Clark Regional Emergency Services Agency (CRESA), Washington La HEXAGON SAFETY & INFRASTRUCTURE TAB 1 — Qualifications of Company Mr. Singh developed numerous challenging custom applications that radically enhanced the efficiency and functionality of the base I/CAD System. Primary custom applications provided included Radio Channel Assignment, Custom Paging Module, First Due Notification, and AniAli Phase II Confidence Factor Display. San Jose Emergency Services, California Mr. Singh installed their I/CAD System, performing tasks that included Oracle RDBMS setup for I/CAD servers; CAD capability implementation with interfaces, reporting, data archiving, and networking for Dispatcher workstations; functionality and site acceptance testing; and project implementation. Interface work included Mobile Data Terminals (MDTs), InterCAD (Interface between Intergraph CAD and San Jose County CAD System), Fire Station Alerting/Printing, and Push -To -Talk. Mr. Singh resolved tricky workflow issues with innovative solutions and recommendations, as well as designing and developing custom utilities to meet challenging requirements. He worked with a 2-member project team over a period of four years. San Diego Sheriff, California Mr. Singh installed their dispatch management system, performing tasks that included Oracle RDBMS setup for I/CAD servers; CAD capability implementation with interfaces, reporting, data archiving, and networking for Calltaker and Dispatcher workstations; functionality and site acceptance testing; and project implementation. Interface work included automatic numbering identification/automatic location identification (ANI/ALI) and MDTs. Mr. Singh resolved tricky workflow issues with innovative solutions and recommendations, as well as designing and developing custom utilities to meet challenging requirements. He worked with a 2-member project team over a period of four years. City of Norfolk Police, Fire and Rescue, Virginia Mr. Singh installed their dispatch management system, performing tasks that included Microsoft SQL Server 2005 setup for I/CAD servers; CAD capability implementation with interfaces, reporting, data archiving, and networking for Calltaker and Dispatcher workstations; functionality and site acceptance testing; and project implementation. Interface work included automatic numbering identification/automatic location identification (ANI/ALI) and MDTs, as well as designing and developing custom applications to meet challenging requirements. He worked with a 2-member project team over a period of four years. City of Richmond Police and Fire, Virginia Mr. Singh installed their dispatch management system, performing tasks that included Microsoft SQL Server 2005 setup for I/CAD servers; CAD capability implementation with interfaces, reporting, data archiving, and networking for Calltaker and Dispatcher workstations; functionality and site acceptance testing; and project implementation. Interface work included Mobile Data Terminals (MDTs), InterCAD (Interface between Intergraph CAD and Richmond EMS TriTech CAD System), Fire Station Alerting/Printing, and ANI/ALI. Mr. Singh resolved tricky workflow issues with innovative solutions and recommendations, as well as designing and developing custom applications to meet challenging requirements. He worked with a 2-member project team over a period of two years. Benton County Emergency Services (SECOMM), Washington _ HEXAGON SAFETY & INFRASTRUCTURE TAB 1 — Qualifications of Company Mr. Singh installed their dispatch management system, performing tasks that included Microsoft SQL Server 2005 setup for I/CAD servers; CAD capability implementation with interfaces, reporting, data archiving, and networking for Calltaker and Dispatcher workstations; functionality and site acceptance testing; and project implementation. Interface work included ANI/ALI and MDTs, as well as designing and developing custom applications to meet challenging requirements. He worked with a 2-member project team over a period of three years. HEXAGON SAFETY & INFRASTRUCTURE fi�RAPH TAB 2 - COMPANY RELEVANT EXPERIENCE & REFERENCES 11 HEXAGON SAFETY& INFRASTRUCTURE IrvrERGwAPH LEE COUNTY, FL RFP FOR CAD REPLACEMENT TAB 2 - COMPANY RELEVANT EXPERIENCE AND REFERENCES Intergraph Corporation d/b/a Hexagon Safety & Infrastructure (Hexagon) has included RFP text verbatim in bold, italicized font below. Hexagon responses follow in regular text. Provide a statement of understanding that your Company recognizes the County reserves the right to evaluate the proposing Company on their past performance and prior dealings with Lee County (i.e., failure to meet specifications, poor workmanship, late delivery, etc.) as part of their experience criteria. Hexagon acknowledges that Lee County reserves the right to evaluate past performance and prior dealings with the County. Consideration will be given to input from other clients of the Respondent's solutions and services, including the ability to manage a project of this size and scope, past performance, and the ability to provide the desired solution in the necessary timeframe. The County will also pursue independent means of contact, when available and appropriate. Hexagon acknowledges the above statement. References a. Respondents must provide a list of all installations that the Respondent has implemented during the past five years that are relevant to the scope of this project. Each project reference shall include: 1) Project title and location 2) Project start and finish dates 3) Client point of contact (name and title) 4) Current telephone number and email address of point of contact 5) Description of the work/services provided 6) Percentage of the overall project actually performed by the Respondent 7) Initial bid price and final contract amount, including the quantity and dollar value of contract modifications Please refer to TAB 6, Form 3: Reference Surveys and the "Lee County - Additional References" chart provided for answers to requirements a.1 through a.7 above. Additionally, though not requested as part of the RFP 180081 re-release, Hexagon has included our original RFP 170457 response Form 1 c indicating three customer references at varying stages of implementation. These form responses provide valuable information regarding our experience. Hexagon has included Form 1 c indicating each of these references as part of TAB 6. City of San Diego PD, CA reflects the project of a new customer having recently gone live _ HEXAGON SAFETY & INFRASTRUCTURE TAB 2 — Company Relevant Experience & References County of Salt Lake, UT reflects the project of a new customer in the middle of implementation Manatee County, FL reflects an upgrade project of an existing customer b. Respondents shall include three client references with active virtual CAD system environments, providing the information above, if different from the projects referenced. Please refer to Tab 6, Form 3: Reference Survey responses for the following agencies with active virtual CAD system environments: Manatee County, FL Martin County, FL City of Plantation, FL City of St. Petersburg, FL Madison County, AL (Huntsville 911) Mobile County, AL Shelby County, AL c. Provide three client references for the disaster recovery solution proposed, providing the information above, if different from the projects referenced See answer b. above. d. Respondents must provide a list of previous implementations utilizing a move up/cover application. Hexagon recommends Deccan International's LiveMUM software for move -up functionality, but has not priced the application or Hexagon's interface to it in the solution. Hexagon is willing to solicit a quote for this software if desired. Information regarding Deccan, the product's functionality, and shared customers are listed below. Deccan International is located at 5935 Cornerstone Court West, Suite 230, San Diego, CA 92121. A woman -owned small business (DBE/MBE/WBE), Deccan International is the leading provider of turnkey software solutions and services for public safety strategic and real-time deployment planning. Deccan has pioneered in the development of computer -aided -dispatch analysis software for over 20 years, and continues to develop new and enhanced decision -support tools to help Fire, Emergency Medical Services (EMS) and emergency communication centers operate more efficiently. Deccan's superior customer service and unparalleled level of expertise have resulted in a client base of over 250 throughout the U.S. and Canada, including FDNY (Fire & EMS), Philadelphia FD, Orange County FD (FL), Orange County Fire Authority (CA), British Columbia Ambulance Service (BCAS), Seattle FD, Austin -Travis County EMS, and Prince William County FIR to name a few. Deccan software deployed at client sites throughout the U.S. and Canada currently serves 70 million people in the United States and 1 in 3 in Canada. Deccan offers its clients a support team focused on customer service. Well qualified project managers (PMs), who manage application build projects of all sizes and levels of complexity, comprise the core of the Deccan team. The PMs are supported by expert Operations Research Developers and Industrial Engineers, professionals that are proficient in supporting Fire/EMS clients to help improve operational productivity. In addition, the Deccan team is proud to have ex -public safety personnel on its team who bring in real -world knowledge and experiences. Through data -driven _ HEXAGON SAFETY & INFRASTRUCTURE TAB 2 — Company Relevant Experience & References statistical and geographic analyses using sophisticated algorithms, Deccan's suite of decision -support products offers a business intelligence solution that enables Fire and EMS departments to analyze current response performance and optimize their resources through both real-time and long-term strategic deployment, resulting in faster response times and more efficient use of resources. Deccan International's Move -Up Module (LiveMUM) interprets CAD unit and event data and presents it in an easy to understand, color -coded map format for evaluating coverage of areas by the units. Deccan's Move -Up Module reveals holes in service area coverage and offers recommendations for reallocation of first responder units. LiveMUM monitors I/CAD unit and event information and applies move -up algorithms to determine unit move -up recommendations in real time. The I/Deccan LiveMUM Interface supports a two-way interface between I/CAD and LiveMUM by which dispatchers are notified of move -up needs in I/Dispatcher. The dispatcher can then analyze, change move -up recommendations through LiveMUM and execute the move -up in I/CAD. This relieves the strain placed on the dispatchers to make complex analysis in maintaining the status of coverage in the service areas. With LiveMUM dispatchers can: Get a continuous updated display indicating the status of live engine, ladder, and ALS coverage by accurately analyzing CAD data in real-time. Get color -coded maps that allow dispatchers to instantly view weaknesses and strengths in coverage. Test and evaluate the effectiveness of pre -planned reallocations taking into account the various specific agency criteria set by the agency. Achieve consistency in quality of reallocation across all dispatchers by removing need of personal objectivity. Obtain a log of dispatcher decisions for review. Hexagon has a long-standing partnership with Deccan, and therefore a very mature interface and close working relationship. LiveMUM is currently interfaced with Hexagon CAD systems at over a dozen mutual client sites throughout the U.S. and Canada that include: Louisville FD Fairfax County FR British Columbia Ambulance Service (BCAS) Boston FD Toronto Fire Services Palm Beach County FR Columbus FD Emergency Communications for British Columbia (ECOMM) Cleveland Fire & EMS Napa FD Redwood Empire Dispatch Communications Authority (REDCOM) Clark Regional Emergency Services Agency (WA) El Paso FD HEXAGON SAFETY & INFRASTRUCTURE TAB 2 — Company Relevant Experience & References Edmonton FR (Alberta) DuPage County, IL (currently implementing) Mesa, AZ (currently implementing) e. The County may contact client references to validate the information provided by the Respondent and to determine the client's overall satisfaction with the solutions and services provided; therefore, it may prove beneficial to the Respondent to contact its referenced clients to ensure their contact information provided is up-to-date and that the reference will be available during the period of time that the County will be validating references (approximately 120 days). Hexagon acknowledges the above statement. f. Respondents may include letters of commendation from customers. Please refer to TAB 7 for Case Studies from existing customers. Contact information can be provided at the County's request. Past Performance a. Respondent 1) Provide a list of any projects completed within the last five years that were more than two months behind schedule and an explanation of why. As an industry leader, Hexagon has completed scores of projects over the past five years. As projects of this nature are highly complex and dependent on both parties, occasionally projects encounter delays due to one reason or another. While Hexagon understands the request, due to Customer confidentiality clauses, Hexagon is not in a position to provide all the requested information. Notwithstanding, the customers identified in Tab 6, Form 1c have agreed to permit Hexagon to provide details related to their projects as reflected therein, including a delay in one of those projects. Addressing and Mitigating Potential Risks of the Project Hexagon is experienced in fast track delivery of CAD. We are very aware of the criticality of the timely implementation of the system and sensitive to the County's CAD go live schedule requirement Hexagon will work closely with the County to create a project plan to succeed in this regard. Hexagon's project manager and project team intend to forge a strong partnership with the County's project manager and team, that is focused constantly on solutions and meeting the goals of the project including, the County's critical schedule. In addition, the Hexagon team will have the full support of Hexagon management and follows a very structured and professional project management process. There are a great many checks and balances built into the project at all phases to assess the projects progress, providing early detection and resolution of critical path issues as they arise. CAD implementation speed can be significantly increased when the County dedicates SMEs on their side to the project and complete their tasks expeditiously. Example of customer tasks that impact speed of delivery are: HEXAGON SAFETY & INFRASTRUCTURE TAB 2 — Company Relevant Experience & References Participation in workshops Timely completion of test plans and test cases documentation Timely scheduling of configuration training Review and response of project documentation provided by Hexagon Completing user training as schedule when a project schedule baseline is agreed to Timely completion of system testing during the lifecycle of the project Staging of required HW and environment Completing tasks related to third party interfaces on time, including making available required third party information and participation needed and based on the contracted interfaces Below are the three biggest challenges to a timely implementation and how Hexagon would address them: Timely completion of test plans and test cases documentation by the customer, which sometimes is impacted by our customer's internal priorities and ability to get internal alignment on final test procedures. How to address: Hexagon will provide a sample test plan with test procedures as a starting point and guide the customer to ensure these tasks are done on time Production hardware staging. How to address: Hexagon will provide the required hardware specifications, required timeline, and guide the customer to ensure these tasks are done on time Customer's core team ability to run parallel tasks during the implementation of the project. How to address: Hexagon will provide a detailed project schedule with resource loading and work with the customer during the kickoff meeting to finalize the schedule. Once the schedule is finalized, it will be baselined and the Project Managers (Hexagon and the County's) will manage to the baselined schedule 2) Provide a list of any projects that Respondent failed to complete and an explanation of why. In the last five years, Hexagon has not had any CAD/MPS implementation project terminated for Hexagon's default. HEXAGON SAFETY & INFRASTRUCTURE fi�RAPH TAB 3 - FIRM PLAN OF APPROACH 11 HEXAGON SAFETY& INFRASTRUCTURE IrvrERGwAPH LEE COUNTY, FL RFP FOR CAD REPLACEMENT NVEEFW_ I TAB 3 - FIRM PLAN OF APPROACH Intergraph Corporation d/b/a Hexagon Safety & Infrastructure (Hexagon) has included RFP text verbatim in bold, italicized font below. Hexagon responses follow in regular text. 1. Submitted Proposal a. Respondents will be evaluated on the quality and responsiveness of the proposed CAD system solution as presented in the response to the RFP. Hexagon acknowledges that this proposal will be evaluated based on the quality and responsiveness of the proposed CAD system solution as presented in response to the RFP. b. Respondents should demonstrate alternative methods of procurement. 1) Procurement methods should include lease or time payments as well as standard purchase 2) Procurement methods should include per seat, enterprise and tiered pricing models 3) Respondents should itemize the cost of software, interfaces, modules, support, and training offerings in an ala carte fashion. Regarding question b.1 through b.3 above, Hexagon respectfully clarifies that it has offered a firm, fixed price proposal which includes seat licensing based on concurrency (the maximum number of users expected to be logged into the system per shift). A lease pricing model is not proposed for this effort. Hexagon has itemized costs for software, interfaces, maintenance, and training. Costs for software are not broken out per module. Please refer to Proposal Response TAB 5 — Price Proposal. Hexagon assumes that payment milestones will be finalized and mutually agreed to during contract negotiations. As I/Dispatcher (Hexagon's Intergraph CAD client software) is licensed on a concurrent basis (number of users utilizing the software at a single instance) instead of based upon the number of workstations on which the software is installed (Node -Locked) or the number of user ids created, it is up to the County how it utilizes its allotment of production licenses among its call -takers, dispatchers, system administrators, and other personnel uses. A concurrent licensing model is especially helpful for a multi - agency, multi -jurisdictional system as it allows for instant flexibility. The County can change its allocation whenever it sees fit and circumstances demand. The concurrent licenses can be used from multiple workstations at multiple PSAPs by system administrators, call takers, and dispatchers from multiple agencies. Furthermore, concurrent licenses will add value to Lee County for years to come. Because the licenses are not restricted to workstations or ids created, if the County needed to alter its PSAP site utilizations, it could do so without having to go through the effort of changing workstations or acquiring additional licenses for workstations or ids. Hexagon has proposed our CAD system with concurrent I/Dispatcher licenses to best fit Lee County's needs for a Public Safety solution in a multi-PSAP, multi - agency, multi -jurisdiction, multi -discipline County wide environment. Regarding enterprise (site) licensing, while Hexagon is able to offer a site license, it does not always provide the value a customer desires. The price for Hexagon's site license is a based upon the price for primary licenses reflecting the greatest number of primary license users utilizing the Hexagon software at _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach any one time and a site license conversion fee, which is also predicated upon the number of primary license users. The Hexagon site license would provide the County the ability to increase the number of licenses it uses for the named agencies without purchasing additional like licenses from Hexagon. It would not allow the County to provide licenses under its site license to agencies not otherwise named in the Site License Addendum. This model typically benefits customers who expect substantial organic growth in their department in the next five years. Conversely, it may not provide a customer who expects only marginal organic growth in that period the same level of value. In terms of system expansion, the expandability and scalability of the system is evidenced by the fact that current I/CAD installations range in size from a small, 3-seat configuration located in a rural county to large metropolitan or national sites, such as the Metropolitan Toronto Police with more than 90 I/Dispatcher seats installed and the 5-site, nationwide system installed and operational in Germany. All of Hexagon's customers use the same core software, and this COTS -based strategy allows each customer the benefit of improvements and corrections, while providing significant expansion and growth without having to re -procure a system. As the needs of the County grow, the modular nature of Hexagon's application suite, combined with open architecture, allows for an easily expandable system that accommodates both future growth within the agency and the introduction of new technologies. The proposed subsystems can be expanded to accommodate additional users and additional functional application modules. The system may also be expanded by adding agencies, servers, workstations, as well as increases in the quantity of events, units, and reports. There is no practical limitation on how the system can be scaled upward, by adding hardware, software, and Hexagon licenses. Z. Management Plan a. The proposal should provide sufficient information to evaluate the Respondent's approach to managing, designing, and implementing the project. At a minimum, Respondents must provide the information listed below. fJ An organizational chart with information sufficient to understand and evaluate the Respondent's organizational structure. The organizational chart only needs to identify those persons who will be assigned to this project. The following organizational charts provide sample illustrations of the Hexagon and the County Project Core Teams and identifies typical roles. In addition to the listed team members, Hexagon has many additional resources to call on for subject matter expertise in the areas of Information Technology, database, and system support and maintenance, including internal SMEs. HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach HEXAGON PROJECT TEAM ROLES rProject Roles: Note that the boxes shown above represent project roles rather than static resources. This approach enables Hexagon to efficiently distribute personnel to meet project requirements. For example, Hexagon's bid may integrate the Project Manager and implementation Lead roles for one project, while for another the Implementation Lead and Training Lead roles may be performed by a single resource. For complex projects, roles may be expanded to that one person assumed focused responsibility fora portion of the project. The strategy associated with staffing each project is defined by RFP, scheduling, and configuration requirements, rather than by a "one size fits all" approach. Personnel assigned to the Hexagon Project Manager role assume responsibility for day-to-day operations from project initiation to closure. This includes planning, organizing, and managing the project to ensure that tasks are performed and completed according to the project schedule. The role of the Map/GIS Construction Lead is to assist the County with successful I/CAD Map and data table construction. The Implementation Lead provides the technical expertise to implement the project from start to finish, including the provided workshop -based training. The role of the Training Lead is to provide agency trainer and/or end user training. During implementation, Hexagon's Project Manager is responsible for maintaining project communication with the County's Project Manager in the performance of the project. HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach CUSTOMER PROJECT CORE TEAM ROLES Project Manager Map/GIS r CAD System CAD Subject Matter CAD Agency Trainers Construction Lead Administrator(s) Experts Roles: As previously described for designated Hexagon roles, Hexagon encourages the Customer to combine project roles when possible, rather than attempt to assign static resources- This promotes the efficient use of personnel to meet project requirements. However, the Project Manager, System Administrator(s), and Mlapping/G1S roles may each require an assigned resource for the duration of the project. 2) Describe the portions of the work that will be undertaken directly by the Respondent and that which will be subcontracted (if applicable), Include what percentage of the overall project the subcontractor is responsible for. N/A — Hexagon has not proposed a subcontractor for the Lee County project. 3) Provide specifics regarding project management areas such as a communications plan, risk assessment and mitigation, issue tracking, punch list development, change control, and escalation process. Hexagon has included information on our standard project management and implementation methodologies as follows. Hexagon notes that an overview of project phases and milestones is provided in this section. The estimated timeframe for the implementation is currently 15 months. Hexagon clarifies that a more detailed response regarding phases, milestones, and work effort estimates is included in Attachment 3.1 — Sample Project Schedule with this section. All start and end dates for all tasks are subject to change based on all pricing options selected and based on the Statement of Work (SOW) (to be developed during contract negotiations with the County) and realization of tasks over the course of the project. Hexagon assumes the initial project schedule identifying deliverables and milestone deadlines will be finalized after selection and during contract negotiations. PROJECT MANAGEMENT METHODOLOGIES Schedule Management Hexagon prides itself on working and succeeding in a challenging and consequential industry. Projects of this nature involve both parties performing a variety of tasks that are dependent upon one another. With that type of relationship and the number of tasks involved, from time to time delays occur. However, Hexagon has a proven track record of working with its customers to navigate and overcome those challenges to successfully implement its public safety software solutions. 49 HEXAGON SAFETY & INFRASTRUCTURE Issue Management TAB 3 — Firm Plan of Approach As a vendor with vast experience and capabilities, Hexagon employs best practices within its implementation and on -going support operations, and these practices represent the bid as described above. Lessons learned from implementations are reviewed in debriefs and a formal process improvement methodology is employed to continually hone processes and improve deployment successes. The implementation methodologies employed by Hexagon are based on many years of experience. Within a Best Practices framework, the Hexagon approach is flexible, geared for adaptability to the needs of the customer's agencies, with a strong emphasis on process/workflow analysis and assistance with gap identification and mitigation on the part of Hexagon. The Hexagon commitment to excellence in customer support is evidenced by the investment in state -of -the art customer support technology, such as the implementation of the Siebel system. Typically, all formal communications will occur between the Hexagon Project Manager and the County Project Manager. This communication will be either via email or written memorandum and will, at a minimum, describe in detail the issue, impact, and expected response date. Upon receipt, the receiving Project Manager, Hexagon or the County, will acknowledge receipt via email. The Project Manager will assess the issue, solicit assistance from appropriate parties or resources, test, where appropriate, and respond back to the initiating Project Manager via email or written memorandum. In the event the issue is not able to be resolved, the initiating Project Manager will notify the other Project Manager that the response is inadequate and needs to be escalated. The escalation on the Hexagon side will go from the Hexagon Project Manager to the Hexagon Contract Manager. Communications between the County and the Hexagon Contract Manager will be accomplished via email or written memorandum with the Hexagon Project Manager copied. The escalation on the County side will go from the Hexagon Project Manager to the County Project Sponsor / Contract Manager. Communications between Hexagon and the County Project Sponsor / Contract Manager will be accomplished via email or written memorandum with the County Project Manager copied. Scope Management Scope management is addressed via formal Change Request Orders. Requested tasks that fall outside of the negotiated contract as detailed in the Statement of Work can impact schedules and must be addressed via a formal Change Request Order. If a change request is needed, Hexagon will provide a description of the work to be performed and an estimate of the level of effort and additional costs. The Project Manager may approve and authorize the work to be performed according to a mutually agreeable schedule. The Statement of Work and Project Schedule are then adjusted accordingly. Risk Management Risk is a probabilistic estimate that an event will occur that has either positive or negative consequences for the project. It is composed of two parts: 1) the probability of occurrence and 2) the relative impact if the risk occurs. The purpose of establishing Hexagon's approach to risk is to provide a process for the identification, analysis, prioritization, and mitigation of project risks. The sections below define roles and responsibilities for participants in the risk management process, the risk management activities to be completed, and the techniques used for tracking and monitoring risks. 101 ,jA HEXAGON SAFETY& INFRASTRUCTURE TAB 3 — Firm Plan of Approach Roles and Responsibilities In addition to other duties, the Hexagon project manager acts as the project risk officer. As such, the project manager oversees the risk management process by performing the following: • Facilitating risk identification • Assigning risk items to team members • Coordinating analysis activities and the prioritization of risks • Ensuring mitigation strategies and action plans are in place • Maintaining the project's risk register • Monitoring and controlling risk The project manager assigns each risk to a project team member who assesses the exposure and probability for the risk and reports the results of the analysis to the project manager. The team member to whom the risk item is assigned becomes the "owner" of the risk item. The risk owner is also responsible for developing a mitigation plan for the risk, which must be approved by the project manager. The risk owner is also responsible for executing the mitigation plan and providing status reports to the project manager. Risk Management Process The Hexagon Risk Management process is composed of risk identification, risk analysis and prioritization, risk mitigation planning, and risk monitoring and control. Risk Identification Risk identification occurs at the beginning of the program and on an ongoing basis. It is the responsibility of all team members and stakeholders to identify potential risk. At the beginning of the program, a facilitated workshop and brainstorming session is held with all team members to identify potential risk items. Team members can submit additional risk items at any time throughout the project. Any identified risks are added to the risk register for further analysis. It is the project manager's responsibility to assign a risk owner to be responsible for completing the initial analysis and mitigation strategy. Categories under which risk might be identified: • Technical • Scope • Schedule • Financial • Hexagon/internal (i.e. Hexagon staffing) • Customer/external (i.e. Customer staffing) The risk items for the project will be documented in the Project Risk Register. The Project Risk Register is an Excel spreadsheet that contains the following information about each risk: 3-6 _ HEXAGON SAFETY & INFRASTRUCTURE Project risk item ID (a unique identifier for each risk item) Date of risk identification Risk impact Probability of occurrence Prior trend Current Trend Risk item description Mitigation strategy / action plan Secondary or associated risk Risk category Mitigation status Risk priority Risk owner An example of the risk register format is provided below: TAB 3 — Firm Plan of Approach a� H > = O = i O O = O N — f�6 ~ C "6 G 17 y `� c U y to fC 3 m a U r c o in Ln ¢ N = 244 ° a` 3 O 1 MM/DD/YY Hig Hig I Descripti Mitigati A Schedu In Hig Risk YY h h on of the on descripti le Proces h Own risk Strategy on of an s er / Action associate Plan d risk Risk Analysis and Prioritization The project manager assigns the risk item to a team member who estimates the probability that the risk will occur and the impact if the risk does occur. The team member then reviews their analysis results with the project team at the risk review meeting where agreement on a final assessment will be made. Risk Management Planning After the risk analysis has been reviewed and approved by the project manager, all risk items will be prioritized and a risk mitigation strategy developed as appropriate. The strategies used for negative risks are as follows: Avoid — This strategy attempts to eliminate the risk Transfer — This strategy attempts to transfer the risk to a third party Mitigate — This strategy attempts to reduce the probability and/or impact of the risk Accept — This strategy is used when an attempt to avoid, transfer, or mitigate the risk is not possible and therefore the risk is accepted and dealt with _ HEXAGON SAFETY & INFRASTRUCTURE The strategies used for positive risks are as follows: TAB 3 — Firm Plan of Approach Exploit — This strategy attempts to ensure that the opportunity occurs Share — This strategy attempts to share the opportunity with a third party that is better able to benefit from the opportunity Enhance — This strategy attempts to increase the probability that the opportunity can be realized Accept — This strategy does not proactively increase the probability of the opportunity Risk Monitoring and Control Hexagon conducts internal project reviews at specific periodic intervals throughout the lifecycle of each project. An in-depth review of each project risk is part of each project review. Each project review is conducted by the Project Manager and provides an objective assessment of each risk and the associated risk mitigation plan. If the overall project risk is assessed as medium or high, then the frequency of the internal Hexagon risk review is increased as appropriate to better mitigate the risk to the project. In addition to the internal Hexagon risk review process, the project manager will incorporate project risks into the risk section of the Monthly Progress Report submitted to the County. During each monthly status review, the project manager will review each risk with the County to ensure that all team members are working toward a mutually agreeable mitigation plan. Following Hexagon and the Customer's review and mutual agreement on the status of each project risk, a risk mitigation status may be assigned as follows: Open — The mitigation strategy is under development and/or review Monitor — The mitigation plan is believed to be implemented and the risk continues to be monitored Accepted — The risk is accepted In Process — The mitigation strategy is actively being worked by the project team Closed — The mitigation strategy has been successfully confirmed as completed or the risk has been realized All risks with an active status (open, monitor, accepted, in process) are contained in the primary risk worksheet within the Project Risk Register. All closed risks are retained in a separate worksheet as reference material. PROJECT QUALITY CONTROL AND ASSURANCE Hexagon applies a multi -faceted approach to Project Quality Control. Each Hexagon project is involved in one or more of the following project quality control processes as applicable: Bi-Weekly Risk Management Meetings Monthly Public Safety Operations Executive Reviews Periodic Project Reviews i/ HEXAGON SAFETY & INFRASTRUCTURE Bi-Weekly Risk Management Meetings TAB 3 — Firm Plan of Approach Bi-Weekly Risk Management meetings are held by Hexagon Public Safety Operations management and Hexagon Public Safety Product Center management. The focus of the meeting is to briefly review project issues that require management support for resolution and/or risk mitigation and to discuss the status of the associated action plan. Monthly Public Safety Operations Executive Reviews The monthly Public Safety Operations Executive Review meeting is held by the Hexagon project manager and attended by the Hexagon Public Safety Operations management team to review overall project status. This is an in-depth and comprehensive review designed to reduce risk for all large projects. Periodic Project Reviews Hexagon conducts detailed project reviews at periodic intervals throughout the lifecycle of each project. Project reviews are designed to provide an in-depth assessment of the project, thereby reducing project risk, improving project quality, promoting best practices, and improving overall customer satisfaction. For each project, check points are established at contract award that coincide with key events in the project schedule. At each project checkpoint, the following activities occur: Project documentation is reviewed (i.e. action register, risk register, contract documentation, and so forth) Interviews are conducted with each Hexagon team lead The Hexagon project manager is interviewed The Project Risk Register is updated The Hexagon project manager action list is updated A Project Review Status Report is issued to the Hexagon program manager/project manager, the executive manager of the US Public Safety Project Management Office, and other Hexagon practice management, as appropriate for the project If the overall project risk is assessed as medium or high, then additional Project Reviews are scheduled at an increased frequency as appropriate to better mitigate the risk to the project. COMMUNICATIONS PLAN AND CHANGE CONTROL MANAGEMENT Hexagon has provided a Sample Communications Plan below. Guidelines The Communication Plan provides a framework for capturing the communication approach. This plan is created during the Planning Stage and updated throughout the life of the project since communication needs change overtime. The Communication Plan is comprised of 3 templates: Communication Plan, Register, and Stakeholder Analysis. For all project levels, Communication Plan and Register are required, whereas the Stakeholder Analysis template is an optional template. _ HEXAGON SAFETY & INFRASTRUCTURE This Communication Plan highlights the following: Strategy and constraints Project stakeholders and information needs Meeting schedules and purpose Escalation workflow Content Management logistics TAB 3 — Firm Plan of Approach 0 Refer to Complexity Matrix to determine project level and required templates. Document Filling Instructions • Fill the information in the Text boxes. Do not leave any section blank. If a section is not applicable, then type "Not Applicable" in that section. The cells in the table may be filled in by clicking in the corresponding row/column and typing. To add additional rows to the table, TAB after placing the cursor in the last row and last column. Text enclosed in quotes and displayed in red such as "Tab to add rows" should be deleted before saving the document. When inserting an image, such as a workflow or chart, 1) Click on the image you want to copy, 2) Choose "Edit/Copy" (Ctrl+C or right -click and "Copy") from the menu, 3) Select the appropriate text box you want to paste the image into 4) Select "Edit/Paste" (Ctrl+V or right -click and "Paste") from the menu. After finishing the document, please re -generate the complete Table of Contents to reflect the correct page numbering. (Select the Table of contents; right -click; select "update fields" and select "update page numbers only" command). 49 HEXAGON SAFETY & INFRASTRUCTURE Project Definition Project Identification TAB 3 — Firm Plan of Approach This section provides background information about the organization of the project and project participants. PROJECT TITLE CAD and MPS PROJECT MANAGER TBD Communication Management Approach Describe the communication strategy. Consider core and extended team member (help desk, support teams, user community) and internal and external stakeholders (other agencies, vendors). List any communication constraints that could complicate communications (i.e. decentralized project team, conflicts within the group, access to document repository). Recognizing that communication is critical to the successful outcome of any project, the following Communications Plan will be adhered to throughout the life of the project. Weekly Monthly The first three weeks of each month, the Hexagon Project Manager will transmit via email a weekly status report that will report on the following: i. Project Health Indicator ii. Project Synopsis iii. Tasks completed during the past week iv. Upcoming Tasks V. Project Risks and Proposed Solutions The fourth week of each month, the Hexagon Project Manager will transmit via email a monthly status report that will report on the following: i. Project Health Indicator ii. Project Synopsis iii. Escalation Items iv. Status & Plan Update V. Scope Status vi. Accomplishments vii. Plans for Next month �.J,t�_A,�HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Communications Work Session Management Describe the types of session (i.e. Kick-off, Planning, Management Reviews, Status, Lessons Learned, Transition Planning, Risk, and Issues Management) and their purpose and logistics. MEETING TYPE PURPOSE FREQUENCY PUBLICATIONS OF RESULTS COMMENTS Kick -Off Project Initiation One -Time Weekly Status Information Transfer Weekly Monthly Status Information Transfer Monthly Reporting and Escalation Process Describe the formal reporting structure and escalation process. Alternatively, insert a chart and workflow. Typically, all formal communications will occur between the Hexagon Project Manager and the County Project Manager. This communication will be either via email or written memorandum and will, at a minimum, describe in detail the issue, impact, and expected response date. Upon receipt, the receiving Project Manager, Hexagon or the County, will acknowledge receipt via email. The Project Manager will assess the issue, solicit assistance from appropriate parties or resources, test, where appropriate, and respond back to the initiating Project Manager via email or written memorandum. In the event the issue is not able to be resolved, the initiating Project Manager will notify the other Project Manager that the response is inadequate and needs to be escalated. The escalation on the Hexagon side will go from the Hexagon Project Manager to the Hexagon Contract Manager. Communications between the County and the Hexagon Contract Manager will be accomplished via email or written memorandum with the Hexagon Project Manager copied. The escalation on the County side will go from the Hexagon Project Manager to the County Project Sponsor / Contract Manager. Communications between Hexagon and the County Project Sponsor / Contract Manager will be accomplished via email or written memorandum with the County Project Manager copied. Project Repository Briefly describe where project documentation is stored (i.e., SharePoint, Clarity, etc.). Include link if available. Document repository to be determined at Project Kick -Off. 3-12 r/ HEXAGON SAFETY & INFRASTRUCTURE Change Control Management TAB 3 — Firm Plan of Approach There are many avenues in which changes could be identified during the project. Therefore, it is necessary that the project define a formal method for entering scope changes into the Change Management process. Additionally, a scope change may impact multiple contract baseline elements, such as cost, product, product functionality, and/or schedule, so it is necessary that the change be classified as to which baseline elements the proposed change may impact. Any stakeholder or team member who identifies the need to request a change (including but not limited to, alterations, deletions, additions, deviations, and omissions) to a contract baseline element must present their request to their Project Manager. If the request is determined to be a legitimate change request, the customer's Project Manager will forward the Change Request to the Hexagon Project Manager. A properly prepared Change Request shall be accompanied by sufficient supporting data and information to permit Hexagon to make a reasonable determination without extensive investigation or preparation of additional drawings or specifications. Hexagon's Change Control Board (CCB) that includes representatives from Quality Assurance, Development, Documentation, Support, and Services will meet to address and prioritize Change Requests (CRs) and CRs associated with defects (CR-Ds). All requests are logged, using Hexagon's Siebel Change Request Management (CRM) system. This assures all changes and defects are tracked, fixed (as appropriate), and approved for closure. Hexagon will either accept, request modifications to, or reject any Change Request. If accepted, the Hexagon Project Manager then tasks members of the Hexagon Technical Team to perform an impact evaluation. The impact evaluation documents the estimated impact of the change on the project schedule, cost, quality, and related scope. An impact analysis must consider all the configuration items that will be affected by the change and associated costs. Upon the Hexagon Technical Team's evaluation, the Hexagon Project Manager will prepare updates to the appropriate project documentation (Statement of Work (SOW), schedule, cost, etc.), and will provide a written assessment within a reasonable time identifying the price and schedule impacts of implementing the Change Request. This written assessment will be forwarded, along with the Change Request, to the customer's Project Manager for disposition. The customer's Project Manager will either accept, request modifications, or reject the Hexagon written assessment of the Change Request. The customer's and Hexagon's contracting officers are the only persons with the authority to approve a Change Request. Upon approval of a Change Request, the customer's Project Manager tasks the customer's contracting organization to issue a contract Change Order to the Hexagon Contracting Officer. The Hexagon Contracting Officer shall assist the customer's contracting organization in preparing Change Orders for customer's approval and execution in accordance with the contract agreement. As necessary, Hexagon will prepare a SOW to describe the implementation of products to be added, deleted, or modified from the contract baseline. The Contracting Officers of both parties will then execute a Change Order and revise the appropriate contractual documentation. The Project Managers of both parties then finalize the process by communicating the change to their affected project personnel and stakeholders. If the Change Order results in a cost reduction, Hexagon will provide the customer credits (not refunds), which can be used to purchase additional software products or services. The terms and conditions of the original contract shall apply to all changes executed under the contract. All changes shall be managed and executed in accordance with the contract requirements. _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach If a change request is needed, Hexagon will provide a description of the work to be performed and an estimate of the level of effort and additional costs. The Hexagon Project Manager may approve and authorize the work to be performed according to a mutually agreeable schedule. The SOW and Project Schedule are then adjusted accordingly. In terms of configuration management, as configuration changes are made at a Project site, they are recorded and documented in a Site -Specific Configuration Document. This document functions as a "living breathing" implementation history of changes and is updated throughout the project to document the database set up, hardware, servers, clients, software installed, scheduled tasks, database changes, and other GUI type configurations. During implementation, the document will be accessible to the Customer and is given to the Customer upon the completion of the project. In addition, an Interface Control Document (ICD) will be written for each interface application purchased by the Customer A Site Interfaces Configuration Document is also compiled by the Interfaces Implementation team during the implementation process. This document details each interface application, as configured for the customer, and specifies the server(s) running that interface. All site -specific registry and parameter configurations are documented along with the information concerning any troubleshooting and how each interface is to be maintained by the Customer and the support team. This document is delivered to the Customer and stored in the customer repository at Hexagon's headquarters located in Alabama. The Change Request shall contain the following elements: Title Change Description Requester Change Request Date Category (service, product, product functionality, or schedule) Priority Original Requirement Number (if any) Description of original requirement Description of modified requirement requested Schedule Impact (if known) Other Documents Affected Regression testing is done as part of Hexagon's scrum certification process with each release of the COTS product. r/ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach OVERALL PROJECT IMPLEMENTATION METHODOLOGY During the past 28 years, Hexagon has developed a relevant and reliable system delivery method that incorporates the repeatable activities associated with any public safety project while maintaining the flexibility necessary to address each installation individually. The test bed for Hexagon's Project Methodology has been worldwide, and our resulting approach and philosophy incorporates proven processes while focusing on the challenges of each customer. Fostering Communications and Collaboration via Project Teams In addition to providing experienced and knowledgeable personnel, Hexagon believes that a successful project begins with establishing and maintaining open communications. The Hexagon project approach encourages frank discussion and information exchanges between Hexagon personnel and the County. Hexagon is committed to providing the best solution for the given environment, and to ensuring that common expectations are set, and that mutually agreed results are attained. As a framework for initializing communications, the Hexagon Project Manager uses the Project Kick -Off Meeting to lay out the project approach and schedule so that all parties understand the organization, activities, and the schedule contracted. Hexagon also formalizes critical communication links between these core teams to establish predictable patterns for the timely dissemination of information. However, depending on the size and complexity of a project, Project Core Teams may be expanded to include Subject Matter Experts (SMEs) or team roles may be contracted so that a single person assumes multiple role responsibilities. Using Industry -Proven Methods Hexagon Project Managers apply specific industry -proven methods and Hexagon to implement identifiable components. As an example, a typical Hexagon Public Safety project includes the CAD subsystem, but mapping and interfaces are components of the overall CAD installation, as well as mobile communications and data conversion that may also be included. Furthermore, Hexagon approaches each component of the overall CAD subsystem as a sub -project and brings in subject matter experts when necessary to address component installation. Note that completion of one component may precede completion of the overall subsystem while installation of interfaces may extend beyond subsystem closure, as interface integration may be proposed that cannot be implemented until the entire system is in place. The proposed implementation approach addresses the CAD, CAD Mapping, Mobile, and associated CAD interfaces at the beginning of the project. Whether Hexagon's proposed Project Schedule runs project phases consecutively or concurrently depends on factors stated in the RFP, such as the County's preference, the availability of the County resources, budget constraints, and/or the impending loss of current subsystem support. Currently, Hexagon has proposed to run project phases indicated below consecutively. Within each subsystem and component of the project, a predictable implementation pattern emerges, delineated by identifiable sets of tasks and deliverables. For Public Safety Projects, Hexagon segments activities into the following implementation phases: Planning and Initiating Phase _ HEXAGON SAFETY & INFRASTRUCTURE Staging Phase Configuration Phase Deployment Phase Maintenance Phase TAB 3 — Firm Plan of Approach The following sections provide an overview and examines typical tasks and deliverables associated with each implementation phase. The SOW, developed during contract negotiations, defines the specific tasks associated with the County's Project. Planning and Initiating Phase During the process leading up to selection, the County and Hexagon may have shared information during a benchmark, requirements discussions, and questions and answers exchanges. Upon selection of Hexagon to implement the County's Project, the Hexagon negotiating team and the assigned Hexagon Project Manager, in tandem with the County representatives, negotiate the final contract and develop the SOW, the Project Schedule, and associated appendices. After contract negotiations, Hexagon technical personnel will: Submit questionnaires and data collection templates designed to gather as much preliminary information as possible. This information assists Hexagon technical personnel in accurately assessing the size and complexity of the project and can be useful in mitigating up front project risk. The County controls the amount and detail provided to Hexagon prior to contract signing Begin an assessment of the information known and provided to Hexagon and consult with the County during on -site meetings or conference calls concerning additional data that may be required, such as map data, documented workflows, deployment practices, and third -party interface documentation and points of contact Through this information exchange, the County and Hexagon define and clarify as much functional, process, and staffing data as possible to develop an overall understanding of the current environment and to prepare for activities that follow contract signing, including: Assessing completed questionnaires and data collection templates Conducting the Project Kickoff Meeting Reviewing the SOW with the Project Core Team to ensure a common understanding of the products contracted, the scheduled timelines, the resources required, and the contracted hours Conducting reviews and interviews with the County Subject Matter Experts (SMEs) The table below lists representative tasks conducted during the Planning and Initiating Phase of the County's Project: TYPICAL PLANNING AND INITIATING PHASE TASKS Sign Contract Initiate the Project and Review the Project Schedule during the Project Kick -Off Meeting Customer Orders Hardware 3-16 10, HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Receive and Process Map Data for the Initial Map Build Install and Stage Hardware (If the County procures the hardware outside the Hexagon contract, installation may become the County's task or the task of the hardware provider) Conduct Operational Reviews and Interviews Conduct the Map Workshop Complete and Submit Interface Control Documents for the County's Review and Approval Run Technical Health Check* * Recurring Technical Health Checks are part of Hexagon's Quality Control processes and occur at the end of each phase. Depending on the project, health checks may be run remotely or with minimal County involvement. Staging Phase Following the Planning and Initiating Phase, the project moves into the Staging Phase. Depending on Project and contract requirements, subsystem component implementation may be staged, configured, critiqued, restaged, and redelivered until each subsystem best meets the needs of the environment. To manage the schedule, Hexagon proposes the number of iterative deliveries associated with each system component and documents this number in the SOW. TYPICAL STAGING PHASE TASKS Deliver Production System Build Deliver Initial Map Build (#1) Conduct Core Team Subsystem Workshops Conduct Map Basics Workshop Run Technical Health Check Configuration Phase During the Configuration Phase, the Hexagon team installs and configures the standard interfaces; develops and installs custom interfaces; develops any enhancements and/or reports proposed; and, if data conversion is part of the contract, delivers and tests data conversion scripts. Configuration builds and deliveries focus on system customization. The on -site configuration activities require that the County representatives spend the mornings with the Hexagon Technical Lead identifying and prioritizing changes necessary for Hexagon to execute during the afternoon. Following the final configuration delivery, additional changes may be purchased via change order. HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach I YF'K:AL UUNNUUKA I IUN 1JH Install Standard Interface Products Deliver Interim Map Build (#2) Develop Custom Interfaces Conduct Subsystem Configuration Workshops Deliver System Configuration Deliver Custom Interfaces Run Technical Health Check Deployment Phase Deploying the system includes the delivery of the final contracted configuration followed by training agency representatives selected by the County to provide ongoing end -user training. Hexagon encourages customers to develop and maintain a team of on -site trainers who undergo hands-on instruction in product application and who develop the skills necessary to train others. This approach to training proves to be less costly and ensures that a number of knowledgeable users remain on -site to train future employees and/or to help system administrators analyze the source of a problem. Formal Train -the -Trainer classes also serve to ensure that the system is operating as defined and that final adjustments are made prior to delivery to the end user community. In addition, the Deployment Phase encompasses acceptance testing and cutover to live operations. The Hexagon Team remains engaged throughout these processes. Completion of the reliability period completes the Deployment Phase. TYPICAL DEPLOYMENT PHASE TI Deliver Map Build (#3) Training Perform Acceptance Testing Stage Training Server/System Conduct End User Training per Training Plan Conduct Cutover Readiness Review Conduct Cutover Begin Reliability Period Perform Project Closure 3-18 i/ HEXAGON SAFETY & INFRASTRUCTURE Maintenance Phase TAB 3 — Firm Plan of Approach The Maintenance Phase represents a single on -going task that begins following cutover. At this time, the project status transitions from an active implementation under the care of the assigned Hexagon Project Team to an active County installation supported by Hexagon's Customer Support Center. Conclusion Based on 28 years of experience, the Project Methodology developed by Hexagon maintains the flexibility to address each Project individually while acknowledging the re -occurring activities associated with any Public Safety Project. This methodology uses open communications and collaboration as a pathway to forming partnerships with our customers. From the initial Kick -Off Meeting through the Maintenance Phase of all our projects, Hexagon's approach seeks to identify and implement the best solution for the given environment, ensure common expectations are set and mutually agreed results are met. 3. Project Schedule a. Respondents must provide a proposed project schedule beginning at the Notice to Proceed and ending at Go -Live (as defined herein). The timeline should be expressed in terms of calendar days or weeks from the issuance of the Notice to Proceed rather than actual dates and should include specific major events, milestones, and deliverables. Identify any assumptions used that support this timeline. Please refer to Attachment 3.1 Sample Project Schedule, which begins at the Planning and Initiating Phase of the County's Project as described above and ends after Post Go -Live training and Project Closure. The timeline is expressed in terms of calendar days rather than actual dates and includes specific major events, milestones, and deliverables. The estimated timeframe for the implementation is currently 15 months, including a 30-day reliability period. The Reliability Period is designed to provide the Customer with support for problems, questions, or errors encountered in the 30 calendar days following the Cutover to production use the new Subsystems. The Reliability Period is performed over the course of 30 calendar days (two (2) weeks on site following the week of cutover and two (2) weeks remote). Support is provided Monday through Friday during normal business hours. If desired, Hexagon can provide a Sample SOW at a later date which includes a Sample Acceptance Test Plan for site acceptance testing and issues resolution along with further information on the reliability period. Hexagon's sample schedule timeline is based on the proposed system and services after review of the County's RFP requirements and years of experience implementing CAD solutions for customer sites worldwide. Hexagon assumes the schedule will be finalized and mutually agreed to during contract negotiations. 4. Training Plan a. Respondents must provide details regarding the training plan for the CAD solution. f) Detailed listing of training classes for CAD and mobile data users, including Train -the - trainer classes Every Hexagon project for a Public Safety system includes the implementation workshops and application training classes necessary to ensure that personnel operating and maintaining the Hexagon software have a full understanding and working knowledge of the system configured. Workshops are conducted in _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach a consulting environment while training courses are conducted in a more formal environment, both are provided to appropriate agency personnel. Please refer to Attachment 3.2 Training Course Descriptions with this section for a list of training classes proposed CAD and mobile data users. Implementation Workshops For new system implementations, Hexagon implementation and training personnel will begin the instruction and configuration process with agency personnel by conducting implementation workshops that involve installing the core system, building the necessary site -specific data for the system to function properly, and then configuring the system to meet the customer's workflow and operational needs. In an apprenticeship approach, the customer's System Administrator(s) and other key personnel will be introduced to system data requirements and the data management and configuration tools while learning the steps necessary to gather and organize the data needed. Customer personnel who attend these workshops should include the System Administrator, the Core Team, and other stakeholders as needed (Support Personnel, Command Staff, Trainers, Power Users). Application Training Application training includes course instruction on the proper use of a particular application, as well as courses that instruct administrators and other support personnel in the administration, configuration, and maintenance of the system. Two options are available for application training: Train -the -Trainer and Train -the -User. Train -the -Trainer The Train -the -Trainer approach is included with Hexagon's base pricing and is designed for agency trainers and power users on the overall functionality available within each Public Safety application, as well as techniques to best way Train -the -User. Due to the vast functionality of the system, some application commands or functions may not be of benefit to the customer's operation. The Train -the -Trainer approach involves a level of consultation from Hexagon implementation and training personnel that permits the customer's Core Team, System Administrator(s), and Trainers to learn the full capabilities of the respective systems and determine which commands and/or functions within the system will be used as part of their operation. This training also provides the opportunity to support the customer team responsible for the design and development of the training curriculum for Train -the -User. A soft copy of training documentation is provided to the customer's trainers, which can be modified and customized to meet their site -specific training needs. Train -the -User The program designed for Train -the -User training provides necessary instructions in the basic and essential functions that every operator should know before cutting over to live operations Agency trainers and the core team go through the Train -the -Trainer program to design and develop the contents of the user training curriculum necessary to conduct Train -the -User classes. Hexagon recommends that the agency trainers conduct the courses which helps to ensure knowledge transfer is accomplished and a high level of competency is present once the _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Hexagon -led training is complete. This training will focus on the commands and workflows that will be used most frequently in the Communications Center as identified by the agency trainers. If requested, Hexagon instructors can be available to assist agency trainers with the initial Train - the -User workshop. System Administration Training Hexagon offers System Administrator level courses that provide the necessary training to persons who will assume responsibility for system configuration, support, and maintenance. There are additional courses available regarding configuration tools and techniques, as well as a site -specific administration and maintenance session designed for the customer's specific configuration. Training Details Hexagon offers training courses for system administrators, the Core Team, and other stakeholders as needed (support personnel, command staff, designated trainers, power users). For training classes, industry best practices dictate that the class size should not exceed 12 persons for trainer and user classes, and 6 students for technical classes (system administrator and database level). The workshops typically run 4-6 hours and have 2-4 hours of implementation work followed by the loading of data or configuration. 4- The length of standard coursework varies but assumes an 8-hour day. Class days are typically based upon 8-hour sessions per working day. Classroom and Facility Logistics • Each classroom should have adequate workstations so students are allocated one workstation with necessary monitors. Each instructor must have a workstation with a minimum of two monitors. The instructor workstation must also have an LCD projector and adequate projection surface for each monitor. Implementation workshops are conducted in a collaborative, workshop type environment; therefore, attendance limits and hardware needs are based upon the objectives of the workshop, as well as the facilities available. training Materials Each student will receive a hard copy of the Hexagon COTS documentation for each class. This documentation will include any training guides, handouts, or other materials needed for the class Customer will also receive soft copy of all training materials for purchased classes, in the form of Microsoft Word documents, Microsoft PowerPoint presentations, and any other electronic media generated for the course curriculum. These files will be in Microsoft Office 2010 or later format. Refresher Training Hexagon provides refresher training at customer request. However, the cost of refresher training is bid at the time of the request to address the specific functionally desired. For example, training may be requested when an upgrade is installed and the content and length of the training would depend on the version of software the customer is moving from and upgrading to. Likewise, if a customer requests HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach specific refresher training, the cost of the training depends on the specifics associated with the functionality to be covered and would be bid accordingly at the time the training is requested. PROPOSED APPROACH FOR THE COUNTY Hexagon has proposed a Train -the -Trainer approach at this time as it feels this would be the most economical for the County and it is Hexagon's recommended approach. System Administrator Training is also proposed. Hexagon understands the need for training courses to be scheduled outside of normal working hours based on shifts. In the event of unforeseen circumstances (e.g. public emergency), Hexagon agrees to work with the County to reschedule training in a mutually agreeable manner without additional cost to the County. Hexagon welcomes further discussion concerning the County's training needs during contract negotiations to finalize the exact number of courses desired. Hexagon believes the train -the -trainer methodology will remain the most cost effective for the County, and provide the County trainers an opportunity to get feedback from the vendor on the training they will be conducting, and refine that training to meet the needs of the PSAPs. 2) Detailed listing of classes for system administration training for CAD, interfaces, geographic information system (G/S), mobile data for the startup, configuration, and continued administration of all components Please refer to Attachment 3.2 concerning training course descriptions for a breakout of all courses proposed and their information on recommended class size, duration and method of instruction. 3) Listing of recommended outside training that would be useful for system administration Hexagon schedules "boot camps" which are chargeable events, but provides full training on such topics as CAD System Administrator and Mobile System Administrator. These sessions require pre -registration and are usually held in Huntsville at our Corporate facility. These training sessions provide additional networking with other customers, the ability to train new employees in your organization individually, and allow them to ask specific questions regarding your system. 4) Detailed schedules for training with consideration of maintaining dispatch center staffing requirements (a) Number of classes (b) Class size (c) Class schedule Please refer to Attachment 3.2 concerning training course descriptions for a breakout of all courses proposed and their information on recommended class size, duration and method of instruction. 10, ,gA HEXAGON SAFETY& INFRASTRUCTURE 5. Client -required County Resources TAB 3 — Firm Plan of Approach a. Respondents must provide a list of a# Client -required resources (including staff and materials) required to support the implementation of the CAD solution. Hexagon has included charts showing Implementation staffing levels assumed for the County on the following pages. Staff levels are estimated by percentage of time spent on the overall project duration, not broken out by month. As Hexagon does not have sufficient familiarity with the County's staff, resources, business process, and workflows, Hexagon's estimate may not be fully accurate. Hexagon welcomes further discussion on regarding County -required resources. Position Project Manager (for CAD/Mobile) As Project Manager, the County's representative is responsible for overseeing all on -site project related activities and for assisting the Hexagon Project Manager in developing and managing implementation schedules and coordinating activities and personnel. Position Tasks associated with effective Project Management for the County include, but Description/Responsibilities are not limited to: • Acting as the County's single point of contact for working with Hexagon • Having sufficient authority and responsibility to make decisions on a day-to-day basis about the project • Coordinating the activities of County personnel and resources • Providing sufficient resources to implement operational use of the system • Securing contract change approvals as required Total number of employees Hexagon recommends that the County provide, at minimum, a 100% dedicated Project Manager, with at least a 50% FTE project administrator to support the County's PM. Expected involvement in the following: • Oversight of the County's Project Team members • Initial project requirements review Estimated hours per • Implementation Plan review and approval employee • Training Plan review and approval • Cutover Plan review and approval • I/CAD Acceptance Test Plan review and approval • Interface Design Meeting • Site preparation • Acceptance Testing Recommended Minimum Mandatory Knowledge/Skills/Abilities Project Management Institute training or certification I 3-23 10, HEXAGON A G+4N SAFETY& INFRASTRUCTURE TAB 3 — Firm Plan of Approach Position I/CAD System / Database Administrator The I/CAD System / Database Administrator supervises, monitors, and maintains access security for the I/CAD System as employees are hired or leave the organization. In addition, this individual implements and maintains network and database components, including diagnostics; becomes the central resource for reviewing and analyzing problem reports from operators; and provides subsequent contact with Hexagon Support personnel. The quality of project implementation is directly impacted by the assignment of this resource at the beginning of the contract; and this person should be allowed to attend most training and workshop sessions to become the resource that "knows the most' about the I/CAD System. Tasks associated with maintaining the I/CAD System include, but are not limited to: • Providing off -site data samples for developing and testing conversion workflows, if necessary • Acting as a single point -of -contact for all hardware, software, communications, interfaces, configuration, and general support issues for the installed I/CAD System • Managing system security and access and administering user accounts and passwords • Developing and maintaining system support procedures • Performing routine, daily operational tasks for remedial and preventive hardware maintenance Position • Performing the first level of hardware diagnostics Description/Responsibilities • Acting as liaison with Hexagon software implementation personnel to expedite on -site support and answer complex system, workflow, or configuration questions • Performing routine operational tasks applicable to software maintenance, such as purging system log files, checking database size, and checking the status of interfaces and remote connections • Scheduling and administering backup and recovery of data and configuration files • Changing and customizing screen forms, as requested by Communications Center supervisors or management • Monitoring system loading and providing guidance on the efficient use of hardware and software • Monitoring system operation for peak performance • Performing system data planning • Installing and administering Windows operating system software, utilities, and service packs or upgrades • Managing the network, including assigning TCP/IP addresses and monitoring network activity • Performing Hexagon application software upgrades • Training additional technical staff for backup System Administration duties • Documenting system anomalies for inclusion into periodic site reports • Managing system problems with immediate communications to the Hexagon Customer Support Center, and access to internal developers, systems engineers, and hardware professionals • Providing interfaces to Hexagon for product development to promote future software features that enhance site operations 1 3-24 101 ,gA HEXAGON SAFETY& INFRASTRUCTURE TAB 3 — Firm Plan of Approach Total number of employees Estimated hours per employee Hexagon recommends that this be a full-time dedicated position, but depending upon how the County staffs resources, the System Administrator can also fulfill other system personnel staffing duties. For example, based on site staffing levels at a typical I/CAD site, full-time I/CAD System Administrators could reasonably spend approximately 60 percent of their time as the I/CAD System Administrator, 20 percent as the CAD Database Administrator, and 20 percent performing Hardware/Network maintenance. It is assumed that the System Administrator will also perform the necessary system interface maintenance duties. Expected involvement in: • Initial project requirements review • Implementation Plan review and approval • Training Plan review and approval • Cutover Plan review and approval • I/CAD Acceptance Test Plan review and approval • Interface design meeting • Site preparation Hexagon recommends that I/CAD System/Database Administrator have a B.S. in Computer Science and/or previous work experience with relational databases. In Recommended Minimum addition, this resource should understand the Windows operating system Mandatory environment, networking, and TCP/IP addressing. This person would also benefit Knowledge/Skills/Abilities from prior experience with Microsoft Access, which is used for I/CAD reporting, as well as Visual C++, which is used to make modifications to the I/CAD GUI (graphical user interface). The ability to diagnose and replace hardware is also an advantage. I 3-25 H EXA N A / C� SAFETY& INFRASTRUCTURE TAB 3 — Firm Plan of Approach Position Mapping Technician This resource must know "how I/CAD works." Because the I/CAD Map contains the data to successfully "verify" addresses and because successful execution of "location verification" reduces the steps required to create initial incident data, the I/CAD Map directly impacts the efficiency of the overall system. The Mapping Technician needs to have an operational understanding of the source data for the I/CAD Map, knowledge of the I/CAD validation procedures, and the procedures Position for implementing County map data into the I/CAD Map. Description/Responsibilities In addition to applying updates to the primary map data, the Mapping Technician will add new features, "layers," and other attributes to the I/CAD Map over time. For example, the Mapping Technician may add outlines for landmarks, such as airports or government offices or compounds. Sites with dedicated mapping resources find that the map is frequently updated and improved to address the specific needs of the agencies and operators. The Mapping Technician may also be dedicated to other mapping / addressing functions. Total number of employees Sites with dedicated mapping resources, such as a GIS department, typically assign a GIS technician on a part- to full-time basis to support the I/CAD Map. Other sites without a supporting GIS department, assign a CAD -centric mapping technician as full-time position. Agencies find that the map is frequently updated and improved to address the specific needs of the agencies and operators, but the rate of GIS / map changes needed in the I/CAD Map are also dependent Estimated hours per upon various items such as new road / subdivision construction. The Mapping employee Technician may also be dedicated to other mapping/ addressing functions. During implementation, the Mapping Technician should participate in the following activities: • Initial project requirements review • Implementation Plan review and approval • Cutover Plan review and approval • I/CAD Acceptance Test Plan review and approval • Acceptance testing • Collection of site -specific data elements Recommended Minimum Mandatory GIS background and proposed Hexagon GIS training Knowledge/Skills/Abilities I 3-26 101 ,gA HEXAGON SAFETY& INFRASTRUCTURE TAB 3 — Firm Plan of Approach Position I/CAD Training Lead The County's Training Lead becomes an application expert, providing ongoing training for new personnel and refresher training, as needed. Each supported agency should have a designated Training Lead to support ongoing user needs. Training is a continuous requirement as personnel are hired or leave employment. However, in addition to training tasks, the training lead becomes an application knowledgeable "working level" resource that can evaluate operator Position needs, evaluate the efficiency of the I/CAD user interfaces, design configuration Description/Responsibilities changes, and facilitate communications between the System Administrator and the operators. A dedicated Training Lead also acts as a ready source to evaluate whether a trouble report is a training issue that can be corrected immediately or if there is a system or software problem that needs to be reported to the Hexagon Customer Support Center. The Training Lead also becomes important during the evaluation of major software releases and can assist the System Administrator in comparing changes to the system against agency policies and procedures. Time will also be required to prepare training plans and documents for upgrades across user groups within the County. Total number of employees At least 1 per agency These resources are typically selected for each agency from the most experienced, computer -savvy supervisors. During implementation, designated training resources need to be available to attend classes. Following cutover, Training Leads will be required to evaluate major software releases and the impact of system changes to policies and procedures. The County will also be required to allow the Training Leads to maintain training plans and documents and to provide training as necessary. Estimated hours per During implementation, Training Leads should participate in the following employee activities: • Initial project requirements review • Implementation Plan review and approval • Training Plan review and approval • Cutover Plan review and approval • Interface design meeting • Acceptance testing • Collection of site -specific data elements • System security/user profile definition and administration Recommended Minimum Understanding of basic Public Safety procedures and terminology and of agency Mandatory procedures and workflows. Knowledge/Skills/Abilities NfF 3-27 H EXA N A A C� SAFETY& INFRASTRUCTURE TAB 3 — Firm Plan of Approach Position Hardware/Network Manager The Hardware/Network Manager needs to have, or to develop, competencies in networking and the various hardware component configurations of the I/CAD Position System. Description/Responsibilities Realistically, the County site could require almost daily attention. Added responsibilities include monitoring, controlling, and authorizing outside access to the I/CAD network. Total number of employees Approximately a 20 percent resource requirement. The Hardware/Network Manager needs to have or develop competencies in networking and the various hardware component configurations of the I/CAD System. During implementation, these resources should be available to participate in the following activities: • Initial project requirements review Estimated hours per • Implementation Plan review and approval employee • Cutover Plan review and approval • I/CAD Acceptance Test Plan review and approval • Interface design meeting • Site preparation • Acceptance testing • Collection of site -specific data elements Hexagon recommends that the Hardware/Network Manager have a B.S. in Recommended Minimum Computer Science and/or previous work experience with client/server Mandatory architecture. In addition, this resource should understand the Windows operating Knowledge/Skills/Abilities system environment, networking, and TCP/IP addressing. The ability to diagnose and replace hardware is also critical. I J 3-28 H EXA N A A C� SAFETY& INFRASTRUCTURE TAB 3 — Firm Plan of Approach Position Backup Hardware/Network Manager The backup Hardware/Network Manager is required for the County's site whenever two or more nodes need attention simultaneously and during absences of the primary Hardware/Network Manager. Position Description/Responsibilities The backup Hardware/Network Manager steps in whenever two or more nodes need attention simultaneously and during absences of the primary Hardware/Network Manager. Responsibilities include monitoring, controlling, and authorizing outside access to the I/CAD network. Total number of employees Approximately a 10 percent resource requirement. The Backup Hardware/Network Manager needs to have or develop competencies in networking and the various hardware component configurations of the I/CAD System. During implementation, these resources should be available to participate in the following activities: Estimated hours per • Initial project requirements review employee • Implementation Plan review and approval • Cutover Plan review and approval • I/CAD Acceptance Test Plan review and approval • Interface design meeting • Site preparation • Acceptance testing • Collection of site -specific data elements Hexagon recommends that the Backup Hardware/Network Manager have a B.S. Recommended Minimum in Computer Science and/or previous work experience with client/server Mandatory architecture. In addition, this resource should understand the Windows operating Knowledge/Skills/Abilities system environment, networking, and TCP/IP addressing. The ability to diagnose and replace hardware is also critical. I 3-29 H EXA N A A C� SAFETY& INFRASTRUCTURE TAB 3 — Firm Plan of Approach Interface Developers During implementation this is primarily an Hexagon position. However, Position Hexagon interface developers will need to coordinate with County personnel and third -party vendors as necessary regarding the responsibilities listed below. Therefore, Hexagon has provided this position chart for informational purposes. Interface Developers will be required for each external interface to be developed. This may include Hexagon resources, internal County resources, as well as third - Position party system owners. Description/Responsibilities Interface Developers will be involved in the Interface Requirements Definition, Interface Control Document development, interface development, interface installation, and all phases of testing. Total number of employees Varies per interface Estimated hours per The amount of time required varies per interface. Hexagon has estimated time for employee interfaces in the sample project plan timeline. Recommended Minimum Mandatory Interface developers should possess the skill set necessary to design, implement, Knowledge/Skills/Abilities and test the required interfaces. I 3-30 H EXA N A A C� SAFETY& INFRASTRUCTURE TAB 3 — Firm Plan of Approach Position Integration and Testing Manager Hexagon recommends that The County identify a Manager for all CAD System Testing. Much of the system component testing overlaps. Therefore, the Integration and Testing Manager needs to have strong management skills for tracking tasks, resources, and schedules. They will also play an integral role in reviewing the Acceptance Test Plan provided by the Hexagon Team. Additionally, with all the required interfaces to external systems, this Manager will need to Position coordinate with the various administrators / vendors responsible for the external Description/Responsibilities systems being integrated. The Integration and Testing Manager will be involved in the review of all Acceptance Test Plans and the coordination of all activities and resources associated with Functional, Reliability, and Final System Acceptance Testing, at the component and system -wide levels. Total number of employees Estimated hours per Acceptance Test Plan (ATP) Reviews: approx. 80-120 hours/per ATP. employee During the testing phases of the project: approx. 32 hours/week Recommended Minimum The Integration and Testing Manager should have extensive experience in writing Mandatory system test plans and executing tests for large, integrated systems Knowledge/Skills/Abilities I 3-31 #1 , , HEXAGON SAFETY & INFRASTRUCTURE Position Report Writing Specialists TAB 3 — Firm Plan of Approach Position Hexagon recommends the County have at least three to five Report Writing Description/Responsibilities Specialists who will be trained in the use of InSight Reporting. This person will be responsible for creating and deploying custom reports. Total number of employees 3-5 Estimated hours per Hexagon recommends that report writers attend all CAD InSight Reporting employee training. Expected involvement in report development. Time for report development will depend on the number and complexity of desired reports. Recommended Minimum Ability and background to create custom reports based on defined content Mandatory provided by administrative and supervisory personnel. Report Writing Specialists Knowledge/Skills/Abilities should be familiar with the database structure. Knowledge of SQL would be a definite advantage. b. Respondents must clearly identify tasks that are the responsibility of the Client resources and communicate required completion dates to fulfill the project schedule. A matrix of tasks versus responsibility (e.g., Respondent, County, other) is a preferred approach. Please refer to the charts in answer 5a above and to Attachment 3.1 Sample Project Schedule. Each phase of the schedule will require responsibilities on behalf of Lee County and Hexagon personnel to meet completion timeframes in the schedule. Specific tasks for each phase (including Task Description, Hexagon/Customer Participants, Prerequisites, Deliverables, Hexagon/Customer Responsibilities, and Completion Criteria) are explained in detail in the Statement of Work which Hexagon mutually develops with the Customer during contract negotiations. If desired, Hexagon can provide a Sample SOW at a later date. Hexagon has indicated high level, typical project management responsibilities for both Hexagon and the County below for a CAD/Mobile SOW. The Customer is responsible for providing resources to staff the Core Teams required for a successful System implementation. The Core Teams and roles and responsibilities are described in the following sections. Core Team Roles and Responsibilities: Core Teams must consist of designated agency personnel with the various skill sets, knowledge and backgrounds required to implement the new CAD/MPS systems. The following list identifies the recommended Core Team and its respective roles and corresponding responsibilities: Project Manager — responsible for the day-to-day coordination of project activities with the Customer Core Team and with Hexagon Departmental Sponsors — responsible for making decisions on recommended business process changes and other related items _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach System Administrator Personnel — responsible for all system administration and configuration responsibilities related to the new system, all system interfaces, and the mobile system GIS Administrator — responsible for providing Hexagon Map Lead with source GIS data as documented in the Map Specifications Guide during the project CAD Database Administration Personnel — responsible for routine database administrator tasks Training Personnel — responsible for training other agency personnel `. Subject Matter Experts (i.e. dispatchers, calltakers, supervisory personnel) — responsible for representing end -users' needs Core CAD/MPS Project Team The Customer's Core CAD/MPS Project Team will consist of the following personnel: CAD Lead/Business Analyst Mapping Lead IT/Networking SMEs Communications Operations Leads/SMEs Project Manager Note: Subject Matter Experts can be included in specific meetings pertaining to their functional areas (i.e., Internal Affairs, Risk Management, etc.). Hexagon Project Team Structure Hexagon is responsible for providing resources to staff the Core Teams required for a successful System implementation. The Core Teams and roles and responsibilities are described in the following sections. Core Team Roles and Responsibilities: Core Teams must consist of designated agency personnel with the various skill sets, knowledge and backgrounds required to implement the new CAD/MPS systems. The following list identifies the Core Team and its respective roles and corresponding responsibilities: Executive Sponsor — responsible for resolving issues that have been escalated beyond the project manager's authority Project Manager — responsible for the day-to-day coordination of project activities with the Customer Core Team and with Hexagon CAD Implementation Lead - provides the CAD technical expertise to implement the project from start to finish, including the provided workshop -based training Interface Implementation Lead - provides the interface technical expertise to implement the project from start to finish, including the provided workshop -based training Mapping Lead - to assist the County with successful I/CAD Map and data table construction. Training Lead — responsible for leading Hexagon -led training _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Subject Matter Experts — responsible for advising, troubleshooting, and providing technical health checks throughout the project Hexagon and County Project Management Guidelines Project management occurs throughout the project and is a component of every task. Overall project management activities for Hexagon and the Customer are listed here for reference. Hexagon's project management team responsibilities include the following: Creating a comprehensive baseline schedule, maintaining the schedule, updating completion status based on resources and actuals, and managing the Project with the Customer Maintaining project communications with the Customer's Project Manager through multiple means such as email, telephone calls, etc. The main form of communication will be the status report. The status report will be the document the Hexagon PM will create and submit to the customer PM Managing the efforts of the Hexagon staff and coordinating Hexagon's activities with the Customer's Project Manager Providing agendas one week in advance of all scheduled meetings, unless mutually agreed that an agenda is not necessary Conducting monthly status meetings with the Customer's Project Manager; Hexagon's Executive Sponsor will participate in these meetings as requested by the Customer Conducting weekly project review meetings with the Customer's Project Manager via telephone conference calls Responding to issues raised by the Customer's Project Managers within seven (7) business days Preparing and submitting bi-weekly status reports which include: the accomplishments of the previous month, planned activities, and an updated Project Schedule; in the event that onsite travel is planned for the upcoming month, the status report should include onsite dates, resource requirements and a summary of anticipated outcomes from the trip Preparing and submitting project Change Orders to the Customer's Project Manager Ensuring Hexagon personnel have ample time, resources, and expertise to carry out their respective tasks and responsibilities Customer Project Manager responsibilities include the following: Maintaining communications with the Hexagon Project Manager Managing the efforts of Customer staff and coordinating Customer activities with the Hexagon Project Manager Providing input to Hexagon for creation of the monthly status reports Ensuring Customer personnel have ample time, resources, and expertise to carry out their respective tasks and responsibilities Participating in the status meetings with the Hexagon Project Manager monthly, or as may otherwise be reasonably required, to discuss Project status Participating in the weekly project review meetings with the Hexagon Project Manager via telephone conference calls _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Providing responses to issues raised by the Hexagon Project Manager within ten (10) business days Serving as liaison with all Customer -provided third -party vendors and associated systems Ensuring acceptable Change Orders are approved by authorized signature(s) Ensuring timely payment of invoices Ensuring Hexagon personnel have access to server and network equipment and work areas on a 24x7 basis, with pre -authorization for off -hours Providing workspace for Hexagon personnel, as reasonably requested when on site c. Respondents must provide a description of the training and skills needed for County resources in order to properly support the system (e.g., DBA level skills, SOL training, Microsoft A ctive Directory [A DI certification, etc.) Please refer to the staffing charts for answer 5a. 6. Maintenance and Operation a. Proposals will be evaluated on the useful life expectancy of the CAD solution, particularly guarantees against early obsolescence. The County will not accept acquisition of a solution which the Respondent does not intend to support for the next f0—f5 years. Hexagon has optioned annual maintenance for years 1 through 10 after warranty as part of TAB 5 — Price Proposal. Hexagon clarifies that if a customer has a Hexagon system under Maintenance, Hexagon does not set a limit to the amount of time a product can remain under maintenance, and the Hexagon Customer Support Center will continue to provide phone support on any I/CAD software version that is on an active maintenance agreement. However, "fixes" releases or software patches for major versions are only available on an "n" or "n-1" version release. If the customer is more than one prior version behind, then the customer must upgrade to either version "n" or "n-1" of all applicable software to be able to receive "fixes" releases or software patches. If the County is two or more versions behind the current version of a software product, the County can work with the Regional Sales Manager or Account Manager to submit a request for a quote for Hexagon services to provide a patch, bug fix, or other modification to resolve an error that is materially impacting the County's use. f) Provide details regarding the operation and maintenance of the CAD solution SUPPORT, WARRANTY AND MAINTENANCE Hexagon develops and markets world -class solutions for Public Safety agencies, and provides complete turnkey solutions by combining Hexagon -developed software; third -party products, as required for the total solution; and alliances with quality subcontractors for products and services that Hexagon does not offer. Hexagon realizes the investment made in a Public Safety system and offers a value -add Warranty and Maintenance Program to protect the customer's investment. Hexagon provides full system support and warranty for the following: Hexagon -developed products _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Third -party products provided by Hexagon with pass -through warranties from the provider (these may require additional support costs) Hardware warranties, as provided by the hardware manufacturer, for Hexagon -procured hardware Hexagon provides complete mission -critical system coverage by offering the following Programs: Warranty— Used through successful System Acceptance, which denotes the system is ready for cutover to live operations Extended Warranty— Provides 12 months of warranty beginning at system cutover Maintenance — Commences at the conclusion of Extended Warranty coverage and can be purchased in 12-month increments Hardware Warranty— Pass -through warranty from the manufacturer Warranty During system implementation, Warranty support for the system is provided during normal working hours by the assigned Hexagon implementation team. Once the system is cutover to live operations, support is escalated to an "always available" level that is facilitated by Hexagon's toll -free accessible Customer Support Center. Extended Warranty The "always available" support may exist in two parts —Extended Warranty or Maintenance. Extended Warranty begins at cutover to live operations, and one year of Extended Warranty is included by Hexagon in the base contract agreement. At the conclusion of Extended Warranty, the customer can opt to place the system under the Hexagon Maintenance Program. The services provided are the same for either Program. Hexagon's premium level of service continues indefinitely while the system is covered by either an Extended Warranty or Maintenance agreement. Hexagon requires Extended Warranty to be paid in advance. Maintenance At the conclusion of the Extended Warranty, Maintenance commences if the Customer executes a separate Maintenance agreement with Hexagon. Hexagon requires Maintenance to be paid annually in advance. The services provided are the same for either Program and continue indefinitely while the system is covered by either an Extended Warranty or Maintenance agreement. HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Warranty Extended warranty Maintenance Maintenance Project Duration E TVpicallV t 2 months N. 12 months One year increments until anticipated thereafter cutover Hardware Warranty When third -party products offer special support beyond their normal warranties, Hexagon automatically offers this to the Customer. This special support may result in additional cost if the third -party vendor requires additional maintenance/support fees. Hexagon provides "whole system support" for all products supplied through Hexagon. This level of service provides the customer the satisfaction of knowing they have a single -source contact to address problems for everything purchased through Hexagon. Warranty and Maintenance for products supplied by other vendors beyond this agreement is the responsibility of those vendors, except as separately negotiated with Hexagon. The Warranty and Maintenance program offers service in the following four primary areas: Hexagon Customer Support Center support Hexagon software upgrades Special Support Services (Not proposed) — Hexagon -provided hardware (note: hardware is not currently offered as part of this response) HEXAGON CUSTOMER SUPPORT CENTER The Hexagon Customer Support Center is an integral part of Hexagon's Extended Warranty and Maintenance programs and is provided at no additional cost with the cost of the system (Extended Warranty) or with the purchase of Maintenance. The special support requirements for mission -critical Public Safety systems are met by providing the following: Toll -free access to Hexagon Customer Support Center resources "Always -available" support during Extended Warranty and Maintenance Response times monitored by priority A central single point -of -contact for all problems First level of direct support for all products purchased from Hexagon, including Hexagon software applications, third -party software/hardware, operating system software, database management system, development tools, report writers, productivity tools, networking software, and external interface software _ HEXAGON SAFETY & INFRASTRUCTURE Problem resolution based on priority level TAB 3 — Firm Plan of Approach The main priority of the Hexagon Customer Support Center is to meet the needs of the customer when problems occur and to assist in keeping the system in operation and running smoothly. To that end, the Customer Support Center works problems in a priority order and the more information that can be provided when a problem is reported, the quicker a solution can be found. For the Customer Support Center to be able to expeditiously resolve problems, it is important that the customer's system administrator attempt to isolate the nature of the problem and determine if it is a hardware or software issue. It is also important that circumstances under which the problem occurs are thoroughly documented prior to reporting the problem. When reporting an issue to Hexagon Customer Support, the customer initially determines the priority level of the problem and, in working with the Customer Support Center representative(s), mutual agreement may result in the priority level being raised or lowered, depending on the findings during problem investigation. The Customer Support Center has established the following priority levels for reported problems during Extended Warranty and Maintenance: PRIORITY I PROBLEM DESCRIPTION RESPONSE TIME RESOLUTION TARGETS Level One 0 Loss of data 0 Data corruption 0 Productive use prohibited 0 No workaround available 0 0 Aborts Primary purpose Level Two compromised 0 Productive use significantly impacted 0 Workaround generally not available Level 0 Productive, but incomplete Three operation 0 Workarounds generally available LevelFourl 0 Productive, mainly cosmetic in nature Workarounds or configurable options generally available M-F, 7:OOAM-7:OOPM Central Time — Immediate* or within 30 minutes of notification M-F, 7:OOAM-7:OOPM Central Time — Immediate* or within one hour of notification during normal business hours 12 hours — Program code correction or a procedural work around 48 hours — Program code correction or a procedural work around M-F, 7:OOAM-7:OOPM Central One week — Time — Immediate* or within Procedural eight hours of notification workaround during normal business hours Program code correction in a future software release M-F, 7:OOAM-7:OOPM Central One week — Time — Immediate* or within Procedural eight hours of notification workaround during normal business hours Program code correction in a future software release 10, HEXAGON SAFETY & INFRASTRUCTURE Immediate - Without need to call back in most cases TAB 3 — Firm Plan of Approach Priority Level One and Two problems that have no discernible workaround are escalated, when appropriate, to Hexagon Customer Support Management who participate in the decision -making and resolution process. The Customer Support Center personnel are available, via a single toll -free phone number, between the hours of 7:00 A.M. and 7:00 P.M. CST, Monday through Friday. All after -hour, critical calls will be answered within 30 minutes, ensuring customers have help available when needed. Regardless of the problem or the time of day, customers can reach the Hexagon Customer Support Center through a single phone number. In addition to telephone support, Hexagon offers electronic access to the Customer Support Center via the Hexagon Customer website. Hexagon eService allows our customers to: Report a new issue Update or monitor an outstanding issue Check on issues previously reported Search confirmed issues previously reported by other customers Search the Hexagon knowledge base Review Release Notes for products available to customers Review plans for upcoming releases Review certified environment information about released products or products that will be made available within the next 90 days Hexagon uses Siebel as the Customer Relationship Management (CRM) system for tracking technical support incidents reported by customers. First line support requests are logged into Hexagon's Siebel CRM System, whether the contact is made via a telephone call to the Customer Support Center or through the Hexagon eService website, and incidents are tracked throughout their lifecycle in the Siebel CRM System. The Siebel system is also used to track escalations and reports are run on a regularly scheduled basis to identify escalation problems. Support staff also uses Siebel to review previously reported issues and Hexagon's knowledge base for searching existing problem/solution articles, as well as for accessing internal and external discussion forums. In addition, staff frequently uses WebEx to view customer workflows. In additions, Hexagon uses SecureLink as the remote access tool to connect directly to the customer's system, when required, to assist in troubleshooting and problem resolution. SecureLink, which is provided to customers at no extra change, is Hexagon's preferred method of remote access and diagnosis of customer issues. Using SecureLink, experienced support analysts resolve problems through well-defined diagnostic methods, including application log files or debug tools. If required, assistance from Product Center developer staff is solicited. Remote access to the customer's system is completely under the security controls imposed by the customer. The following table provides problem determinations and resulting actions that may be taken by Hexagon Customer Support Representatives: TAB 3 — Firm Plan of Approach IF HEXAGON DETERMINES THEN THE CUSTOMER SUPPORT REPRESENTATIVE... THAT... Local Hexagon personnel must be Initiates the involvement of those specialists involved On -site software support is Initiates the request for on -site software support personnel necessary Error Reporting and Resolution Hexagon recognizes that our systems are mission -critical, and we provide error resolution accordingly as described above. Hexagon has a documented and successful methodology for error reporting and resolution and uses these standard industry practices for error reporting and resolution in a timely manner. Hexagon will repair or replace software error during the warranty or extended warranty periods, and during any maintenance periods thereafter as specified in Hexagon's Maintenance Agreement. Should the customer request on -site services, these are available at an additional expense. SPECIAL SUPPORT SERVICES Although not proposed, Hexagon can price support and maintenance services over and above those previously described. The services deemed valuable to a customer depend on the level and sophistication of the customer's IT support infrastructure. To help identify gaps in current IT support that need to be addressed as part of the Public Safety Systems rollout, Hexagon can include an optional Support Readiness Assessment to review the current support infrastructure and identify any gaps that may exist between what is in place and what may be required to optimally support the distributed Public Safety environment. This assessment takes into account the support needs for equipment (servers, workstations, and MDTs), networks, system administration, application administration, and end user support. The end report identifies where the current support infrastructure meets the needs of the Public Safety environment and where it may need to be augmented to handle the increased capability and breadth of the new system. Recommendations are included in the report as to how the identified gaps may be closed based either on augmenting current County capabilities or purchasing additional support services from Hexagon or from other suppliers. The assessment takes approximately two calendar months to complete. It involves up to two on -site sessions with Hexagon personnel working directly with the customer's IT team to capture the current support infrastructure and its capacity, as well as working through how new requirements for support of the proposed Public Safety solution may be allocated across that infrastructure, and where the infrastructure may require augmentation. Following the assessment period, Hexagon may advise any of the following additional operational and maintenance resources be added: End -User Support — a dedicated function to provide technical support to the users of the Public Safety solutions. This function may take first call for support coming from the system users and resolve their support issues, or interface with the balance of County IT team for resolution. This _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach focal point for the Public Safety systems ensures responsive support, comprehensive problem logging and tracking, and consistent issue resolutions. Depending on the nature of the client environment, this support may be provided via a phone -based Help Desk, via Desk Side Support technicians, or by a blend of the two MDT Support — a potentially dedicated function to provide support for the deployed base of MDTs, including issue resolutions, MDT repair, MDT image management, and re -imaging. Depending on the customer's environment, this function may also provide Desk Side Support to system users for hardware issue resolution and warranty dispatch coordination. In addition, technicians may be used to deploy applications, participate in testing changes to the system prior to deploying the changes to the Production databases, and in deploying new equipment or moving existing equipment A Technical Site Manager — depending on the scale and complexity of the customer environment and the availability of IT resources, a technical site manager may be recommended to oversee the overall support of the system; coordinate daily activities; manage on -site Hexagon personnel; interface with County IT and Public Safety staff, ensuring rapid issue resolution; and plan incremental enhancements to system functionality and performance Resident System Administrators (RSAs) — depending on the overall complexity of the Project and the level of on -site services provided by the customer's IT staff, Hexagon may propose adding one or more specialized RSAs to oversee third -party system operations, such as an RSA who focuses on providing operating system support. Recommendations for Operating System or application specific system administrators is fully dependent on the complexity of the customer's CAD and Mobile deployment, as well as the availability of skilled local resources to fulfill the support needs HARDWARE WARRANTIES Customers who elect to purchase hardware or third -party software through third party sources are responsible for dealing with the manufacturer on warranty issues. Hardware warranties are separate from the warranties provided for Hexagon -provided software applications. 2) Provide details as to how the company deploys and charges for version upgrades, and the frequency of the updates Software updates are included as part of the proposed maintenance. Services to implement the updates are quoted at the time of request. Software updates are made available for software products for which maintenance has been purchased under and subject to Hexagon's maintenance agreement. These updates contain information on the version overview, usability and interoperability feature enhancements, any licensing/distribution updates, and links to additional information and resources. We respectfully request further dialogue regarding future upgrades for the Hexagon solution before a scope of work for the upgrades can be established. Hexagon would like to discuss options that are tailored to the County's final solution architecture. Pending the final architecture of the solution and an established, mutually agreed upon scope of work, Hexagon can provide a quote for an upgrade. We look forward to the opportunity to devise a plan moving forward to address the County's concerns for future budgetary planning and requirements. Further detail is provided in the following pages regarding software releases. 49 HEXAGON SAFETY & INFRASTRUCTURE HEXAGON SOFTWARE RELEASES TAB 3 — Firm Plan of Approach Hexagon provides two types of software releases: Major and Minor. A Major release is made available to customers approximately every 18 to 24 months and includes significant product enhancements and improvements. Major releases may result in structural changes to the database management system schema. Minor releases are minor incremental releases of the software that contain a limited number of minor enhancements, as well as corrections for problems that have been found internally or reported by customers. Minor releases generally occur three to four times per year and typically do not contain structural changes to the database management system schema. Detailed requirements vary with each patch/software update and the software application to be updated. The information and instructions would be included with the patch/software update release. Hexagon encourages our customers to stay current within two releases of the most current supported version of software (version "n" or "n-1 "). By staying current, customers avoid encountering issues that have been reported by others. All Hexagon software releases must pass a stringent quality assurance testing process before being released for customer use. To the extent a customer desires Hexagon to provide services to implement the upgrade, those services can be quoted upon request at or near the time the County desires for the services to be performed. The timing, frequency, level of effort required by the customer, and impact on the proposed Solution, of updates all vary greatly depending on the actual updates needed, and will be quoted upon request. Please refer to the Hexagon software releases portion of the answer. Occasionally, a customer requires a code change to address a critical P1 or P2 issue on their current release (n or n-1 version), and they cannot wait for the next scheduled base product Minor update release. In these cases, a software patch is created for the particular product on the customer's current n or n-1 version release. When software patches are supplied to the Customer, Hexagon will supply technical instructions on how to install and verify the patch. As with Minor releases, software patches are only available for the most current version (n) and the previous version (n-1). After the system is cut over to live production use, upgrades of Hexagon software and documentation are provided to customers via the Maintenance Program. Customers can evaluate the upgrades and install, or contact Hexagon and request a quote for services to have Hexagon perform the upgrade installation or assist in the upgrade process. As part of the upgrade, a quote for training may be requested through the Customer's Regional Sales Executive. Because delta training is designed to address how commands and workflows used in the customized for the specific site. Consequently, delta training is an added cost that is quoted at the time requested. Upgrades are not included for mass -market (commodity) and third -party products, such as Windows, Microsoft Office, or Microsoft Visual C++. Please note that upgrades are provided for Oracle and Microsoft SQL -Server products purchased through Hexagon. Purchase of third -party upgrades is the customer's responsibility. Hexagon will continue to provide front-line Customer Support Center support for upgraded third -party products and upgraded application software. Hexagon will notify the Customer when updates are made available for any Software Products for which Service has been purchased by way of posting notices (including release summaries) of such to the "Support Notices and Announcements" section on the Customer Support Web Site or applicable local support website or via direct notification by Hexagon. Information contained in the release notes varies but generally contains information on the version overview, usability and interoperability feature enhancements, any licensing/distribution updates, and links to addition information and resources. HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach If applicable, the Customer may also register on the Customer Support Web Site or applicable local support website to automatically receive email notifications when a new release of a Software Product is made available by Hexagon. Updates are shipped to the Customer upon Customer request. Hexagon is not obligated to produce any updates. Hexagon carefully chooses which product enhancements to offer the client base based upon customer site needs and requests and close interaction with the company's Product Center development team. Depending on the type of enhancement needed/developed for a customer site, one client may pay for the new enhancement or multiple agencies may share the costs of the enhancement depending on expected usage of the enhancement. Clients have some say in what enhancements are developed through the following: Hexagon's Product Enhancement Survey, Users Group, and Customer Forum, described in more detail below. PRODUCT ENHANCEMENT SURVEY, USERS GROUP, AND CUSTOMER FORUM The Hexagon goal is to establish a full and continuing partnership with the Customer. Hexagon believes that by working with our customers during a project, as well as maintaining on -going relationships after system acceptance, we can best serve our customers. This approach has enabled Hexagon to establish a 98-percent retention rate throughout its 28 years of service in the Public Safety marketplace. Product Enhancement Survey Hexagon invites customers to influence product enhancements by responding to an annual survey, regardless of release cycle. The electronic Product Enhancement Survey is categorized into logical groupings including a pre -selected list of enhancements. Customers indicate interest in functional categories of the products and specific enhancements by selecting the categories and enhancements that they believe are the most important. Input from this survey is considered by the Product Management team in planning major and minor releases of the products. Hexagon International Users Conference Hexagon encourages users to participate in its Annual International Users Conference. This annual event features technical sessions, guest speakers, demonstrations, and hands-on learning activities. Users are also encouraged to join the public safety users group. Membership is free. Its purpose is to provide the following: A forum for the exchange of information and ideas regarding the working, capabilities, and uses of the underlying nucleus software Information to Hexagon concerning the present and future needs, as well as capabilities of the Public Safety software Information to Hexagon concerning the priority of Software Improvement Requests (SIRS) from the user community and Hexagon A medium of information flow from Hexagon to the user community Additionally, Hexagon also supports and participates in regional users' groups that focus on a smaller, geographic -based set of customers. These regional users' groups have been established throughout the United States, Canada, and around the world. 49 HEXAGON SAFETY & INFRASTRUCTURE Customer Forum TAB 3 — Firm Plan of Approach Finally, Hexagon hosts an interactive online forum expressly for the use of its clients. This allows for direct client -to -client communications, either one-on-one or one -on -many. From the Customer Support Web Page, customers can perform the following tasks: Query the Customer Support Center Knowledge Base Review CAD Software Release Schedules Review CAD Trouble Reports (TRs) Review CAD New Features and Interfaces Review Technical Configuration Details File Service Requests (SRs) File Change Requests (CRs) — requests for product requests/enhancements Review CAD CRs Review Support Information (hours of operation and telephone number) Also, this forum provides the opportunity for customers to ask questions of Hexagon technical personnel or of other customers. 3) Provide details on what the maintenance plan includes in so far as parts, software, labor, and tra vel related to all components supplied under this contract and any financial rebates to the County if the terms of the maintenance agreement are not met. Please refer to the Master Services Agreement included as Attachment 3.3 with this section for detailed maintenance terms and conditions. Hexagon has also provided information on the addition and deletion of products before and after contract signing below. Hexagon clarifies it has not included specific contractual remedies as part of its maintenance agreement or Master Agreement. Addition and Deletion of Products Before and After Contract Signing Adding products, deleting products, and scope of work changes made during contract negotiations or during the project implementation process result in adjustments to the Maintenance costs. Depending on the changes, there could also be services charges for project management, implementation, and/or training. After contract signing, the addition or deletion of products is handled by a structured Change Order process. The periods of Maintenance are provided on a subsystem level, and new products added to an existing subsystem are adjusted so that all system products remain on the same cycle. Should the addition or deletion of a product impact the project schedule, the Maintenance schedule for all is adjusted accordingly. When a customer receives a reissue or upgrade of a product, there is no impact on the existing Warranty and Maintenance Program and no change in status. A product in Warranty remains in Warranty; a product in Extended Warranty remains in Extended Warranty; and a product under Maintenance remains under Maintenance. If the system is under Maintenance, there is no change to the expiration of the Maintenance Period or to the cost for that contractual period. Furthermore, Hexagon does not set a limit _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach to the amount of time a product can remain under maintenance, and the Hexagon Customer Support Center will continue to provide phone support on any I/CAD software version that is on an active maintenance agreement. However, "fixes" releases or software patches for major versions are only available on an "n" or "n-1" version release. If the customer is more than one prior version behind, then the customer must upgrade to either version "n" or "n-1" of all applicable software to be able to receive "fixes" releases or software patches. If the County is two or more versions behind the current version of a software product, the County can work with the Regional Sales Manager or Account Manager to submit a request for a quote for Hexagon services to provide a patch, bug fix, or other modification to resolve an error that is materially impacting the County's use. When a customer has an Hexagon software product that is not under Maintenance, that customer may pay back -maintenance and the applicable reinstatement fee on that product (or re -purchase the licenses) and be eligible to receive upgrades to that product. For these cases, the customer would, after paying back -maintenance, be required to continue to pay normal maintenance through the installation and implementation of the upgraded product. 4) Provide details on what the maintenance plan does not include and the frequency in which the County might expect these expenses to occur. Please refer to the Master Services Agreement included as Attachment 3.3 with this section for detailed maintenance terms and conditions and information on excluded maintenance services. Z Proposed Solution a. Respondents will be evaluated on the quality of the proposed CAD solution, to include, but not limited to: 1) The degree to which the proposal addresses the stated goals Hexagon has read and acknowledges. 2) Adherence to the solicitation requirements Hexagon has read and acknowledges. 3) Extent to which the components of the CAD are integrated to provide a single- system appearance to the end users and an integrated solution CAD and Mobile for Public Safety (MPS) Integration Hexagon provides modular COTS products that allow systems to be architected according to the requirements of the RFP. Used in conjunction with the MPS application, the I/Mobile Data Terminal (I/MDT) interface supports communications between the mobile user and the I/CAD System, including users running I/NetViewer and other mobile data terminals (MDTs) running the MPS application. To this end, the combination of I/MDT and the MPS application extend the range of the I/CAD System, empowering remote personnel with client access to information maintained in the I/CAD Database and to a subset of I/CAD commands for field operations. Furthermore, because the I/MDT and mobile applications are specifically developed to work within the I/CAD environment and are designed to use the _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach data structure of the I/CAD Database, the flow of data between the proposed mobile data communications system and the existing I/CAD System is seamless. Web Based Architecture/Network Technology The CAD system is multi-user compatible and able to operate on a network with simultaneous users. Hexagon provides I/NetViewer for remote view -only access to I/CAD if the customer requires a web - based application. I/Dispatcher can be used if the customer has the connectivity. The recommended host servers' specifications support high availability software and hardware standards, such as clustering and virtualization. Hexagon has proposed host server hardware that uses VMware vSphere Enterprise to support server virtualization for the CAD/Mobile Solution. Hexagon has been in VMware's TAP program since late 2009. Our CAD solution is designated as "VMware Ready". This essentially means that our 911 solution is certified and performs well on a virtualized infrastructure. VMware Ready designates VMware's highest level of endorsement for products and solutions created by our established partners. VMware Technology Alliance Partner members can develop their products and solutions to meet VMware standards and submit them for testing and review. Products and solutions that meet VMware Ready requirements will display the VMware Ready Logo. Hexagon assumes all hardware, OS licenses, database licenses and VMware will be customer -furnished. There is currently not a disconnected mode for the CAD system. The Mobile for Public Safety (MPS) client software is architected to work in an environment where connectivity is intermittent. Messages destined from the server to the mobile client are queued if the client is not immediately reachable or if the client fails to acknowledge the delivery of a message. The same is true for messages destined for the server from the client. Hexagon refers to this as partially connected operations. When the mobile client is disconnected from the server, no functionality that involves data from the server is possible. This includes new queries into the database for unit and/or event status, creation of field events, or remote inquiries for running data via state and federal systems. However, the system map, address verification, and the last known status of events and units all remain available to the mobile user while the client is disconnected. Workflow Capabilities Hexagon's CAD solution provides for a highly configurable, permission -driven environment whereas each agency can maintain individual workflow rules, system preferences, User Interface configuration and access. This supports a true multi -agency, multi -jurisdictional system environment, allowing for an unlimited number of agencies on the system, each with their own configurations and preferences. The configuration and maintenance of system files (the database) is accomplished via the CADDBM utility. CADDBM is designed to be easy to use so that agency supervisors and system administrators can access, create, modify, and maintain the database without programmer support. Information is entered into the database quickly and easily by using dialog boxes. Labeled fields indicate the information required and command buttons help prevent users from deleting the wrong information. Prompts and messages are also displayed for assistance. Completing the dialog boxes in the database maintenance program automatically creates database tables. Tables can be created, reviewed, and changed in the database. No downtime is required when updating tables via the CADDBM utility. Tables include the following: Agency definition, Cataloged alarm, Deployment plans, Deployment plans/pattern definition, Disposition type, Estimated time of arrival table, Event type, Line-up definition, Number table, Out -of - service type, Personnel, Response list, Roster definition, Rotational service definition, Special address definition, Special situation definition, Station definition, Street (primary), Street (alias), Task force definition, Terminal node definition, Unit definition, Update cross streets, Update intersections, User group definition, and Vehicle definition. HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach MPS and Mobile Responder (Optional) Integration with the CAD System Hexagon's Mobile Responder server/client products support mobile functionality for handheld devices. Hexagon has optioned Mobile Responder for the County's consideration. Mobile Responder provides first responder personnel in the field with access to Hexagon's I/CAD System via a smartphone or tablet device. First Responder safety is enhanced by leveraging the integrated GPS capabilities available in a smartphone or tablet device in conjunction with Hexagon's AVL product, I/Tracker. The use of Hexagon Mobile Responder also reduces radio traffic between dispatchers and responders and allows for field event creation, status updates, messaging, and other useful functions. The Mobile Responder and MPS applications extend the power of command and control to all field personnel, improving overall response and increasing public confidence. For a functional comparison of Mobile Responder versus Hexagon's Mobile for Public Safety product, see table below. UF�ETY&XAGON INFRASTRUCTURE tt Hexagon's Intergraph CAD Integration CAD Monitors Event Monitor Mobile.. Q Responder Q Q Q Q Q Dispatch Report Q Q The Unit Monitor Filter Events on Units Q Q Q Q Self -Attach Unit to Event Q Q Actions Q Q Route Unit to Event Event Commands Create Field Event Recall Dispatch Automatic Event Report Add Event Comments Q Q Q Q Q Q Q ❑ Q ❑ Q ❑ Assign Case Number Supervisor Add Event Comments Q ❑ Q ❑ I 3-47 #1 i/ HEXAGON SA FETY & I N F RASTRUCTU R E TAB 3 — Firm Plan of Approach Update Event Information Q ❑ Attach Files to Events & Messages CAD Statuses Q Q Q Q Acknowledge Event Q Q Enroute to Event Q Q Arrive at Event Q Q Clear from Event Q Q Transport from Event Q ❑ Late Run Q ❑ Available on Radio Q ❑ Available on Pager Q ❑ Available on MDT Q ❑ Available in Quarter Q ❑ Available on Foot Q ❑ Available on Event Q ❑ Available First Responder Available Emergency Only Q ❑ Q ❑ Out of Service Q Q InService Q Q Unavailable for Recommend Q ❑ Custom Status Capability Q ❑ Transport Q ❑ Transport Arrive Q ❑ Unit Commands Q Add Unit History Change Unit Location Q ❑ Q ❑ Marking a Location Q ❑ 3-48 #1 ,dA HEXAGON SA FETY & I N F RASTRUCTU R E TAB 3 — Firm Plan of Approach Adding Special Contacts Q ❑ Cancelling Special Contacts Adding a Unit Contact Timer Q ❑ Q ❑ Update Unit Properties Transferring an Employee Q ❑ Q ❑ Supervisor Add Unit History Sign On/Log Off Messaging View Messages Q ❑ Q Q Q Q Q Q Compose Messages Q Q Search Messages Q Q Fetch Unread Message Q ❑ Search Broadcast Messages Q ❑ Relocation Reports Q ❑ Emergency Handling Create or Receive Emergency Alert Emergency Event Creation Q Q Q Q Q Q Receiving Emergency Alerts Q Q NCIC Queries Q Q Query Names Q Q Query Vehicles Q Q Query Article Q Q Query Commands Q Event Search Q ❑ Case Number Search Q ❑ Location of Interest Search Query Pending Events Q ❑ Q ❑ * 1 3-49 #1 J HEXAGON SA FETY & I N F RASTRUCTU R E TAB 3 — Firm Plan of Approach Retrieve Supplemental Info Q ❑ Supervisor Event Search Unit Summary Q ❑ Q ❑ Unit History Search Q ❑ Supervisor Unit History Search Q ❑ Equipment Query Employee Skills Query Q ❑ Q ❑ Find Operator Query Q ❑ Who Query Q Q Tow Commands Q ❑ Request a Tow Q ❑ Canceling a Tow Request Q ❑ Updating an Existing Tow Request Searching Tow Requests Q ❑ Q ❑ Administrative Commands Q ❑ Change Password Q ❑ Adding Log Stamps Lock/Unlock Ping Server Command Q ❑ Q ❑ Q ❑ Display System Information Q ❑ Open Notepad Q ❑ Retrieve Files Q ❑ Retrieve Attachments Q ❑ Opening a Web Page Q ❑ Resyncing Unit and Event Info Q ❑ Mapping Q ❑ 1 3-50 #1 ,dA HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Bing Map Q Q Google Map Q Q Pictometry Q ❑ Create Route Q Q Save/Recall Route Q ❑ Find Address Q ❑ Track Unit Q ❑ Load Cameras Q ❑ Select Item of Interest Support Devices Q ❑ Q Q Windows° PC Q ❑ Windows° Tablets Q Q AppleT"" iPad ❑ Q AppleT"" iPhones AndroidTM Phones ❑ Q ❑ Q AndroidTM Tablets ❑ Q Support OS Platforms Apple° Inc. Devices (iPhone & iPad) Google° AndroidTM Q Q ❑ Q ❑ [� Windows° 10 Q Q Windows° 8.1 Windows° 7 Q Q ❑ Q 4) Extent to which the CAD solution incorporates effective processing methods, state-of- the-art technology and programming languages, and weft defined system interfaces Hexagon has read and acknowledges. I/CAD software development uses C++, C#, and Windows Presentation Foundation (WPF) language/Extensible Application Markup Language (XAML). Those portions of the system accessible by the customer for development use Visual Studio Professional. _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach For interfaces, Hexagon's database standards are ODBC-compliant and the proposed solution also supports the use of other standard middleware connections. In addition, for those running the Hexagon system, we provide a query application called I/Informer (optioned), which is used to query third -party external systems including the State/NCIC, and supports several communication protocols including ODBC, TCP/IP, and WinHTTP. Hexagon recognizes the need to support the industry in which it operates, and serves on the board and working committees in the Integrated Justice Information Systems (IJIS) organization to help drive emerging NIEM standards for interoperability. Hexagon is committed to the use of NIEM-compliant IEPDs where effective and efficient, as a primary means of interoperable communications between compliant public safety systems. Hexagon customers currently using NIEM-compliant interfaces with Intergraph solutions include Fairfax County, and Richmond, Virginia. Additionally, Hexagon's EdgeFrontier integration platform (proposed for various interfaces in this response) can be implemented to support emerging XML-based NIST- and NIEM-compliant exchanges, as acceptable to the third -party system. 5) Genera/ ease of use, future modification/expansion, and change Hexagon has read and acknowledges. CAD GUI Ease of Use The Intergraph solution provides for a highly configurable, permission -driven environment whereas each agency can maintain individual workflow rules, system preferences, User Interface configuration and access. This supports a true multi -agency, multi -jurisdictional system environment, allowing for an unlimited number of agencies on the system, each with their own configurations and preferences. The configuration and maintenance of system files (the database) is accomplished via the CADDBM utility. CADDBM is designed to be easy to use so that agency supervisors and system administrators can access, create, modify, and maintain the database without programmer support. Information is entered into the database quickly and easily by using dialog boxes. Labeled fields indicate the information required and command buttons help prevent users from deleting the wrong information. Prompts and messages are also displayed for assistance. Completing the dialog boxes in the database maintenance program automatically creates database tables, including the following: Agency definition Cataloged alarm Deployment plans Deployment plans/pattern definition Disposition type Estimated time of arrival table Event type Line-up definition _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Number table Out -of -service type Personnel Response list Roster definition Rotational service definition Special address definition Special situation definition Station definition Street (primary) Street (alias) Task force definition Terminal node definition Unit definition Update cross streets Update intersections User group definition Vehicle definition Tables can be created, reviewed, and changed in the database. No downtime is required when updating tables via the CADDBM utility. Future System Expansion In terms of system expansion, the expandability and scalability of the system is evidenced by the fact that current I/CAD installations range in size from a small, 3-seat configuration located in a rural county to large metropolitan or national sites, such as the Metropolitan Toronto Police with more than 90 I/Dispatcher seats installed and the 5-site, nationwide system installed and operational in Germany. All of Hexagon's customers use the same core software, and this COTS -based strategy allows each customer the benefit of improvements and corrections, while providing significant expansion and growth without having to re -procure a system. As the needs of the County grow, the modular nature of Hexagon's application suite, combined with open architecture, allows for an easily expandable system that accommodates both future growth within the agency and the introduction of new technologies. The proposed subsystems can be expanded to accommodate additional users and additional functional application modules. The system may also be expanded by adding agencies, servers, workstations, as well as increases in the quantity of events, units, and reports. There is no practical limitation on how the system can be scaled upward, by adding hardware, software, and Hexagon licenses. 6) Detailed security rights and ease of administration _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Hexagon has read and acknowledges. Information on database and application security for Hexagon's Intergraph CAD system is provided below. DATABASE SECURITY The database is a standard Microsoft SQL Server or Oracle RDBMS using standard RDMBS permissions. The security for the database is user -defined, in accordance with the customer's needs, as part of initial system configuration. APPLICATION SECURITY Security is provided by the Microsoft Windows operating systems, Microsoft SQL Server, or Oracle RDBMS, and the Intergraph application. Standard security is used for Microsoft Windows and the RDBMS. The following paragraphs describe the Microsoft Windows and I/CAD security. I/CAD provide its own security in addition to that of Windows and the RDBMS. I/CAD is a multi -agency dispatch system that allows users from different agencies to share information within the constraints of the agencies security policy. Therefore, application -level security is implemented within the dispatch system. Policies include the ability to restrict the following: Which users can execute the application on which workstation Which Agency/Dispatch Groups can be displayed on a given workstation (for example, which units and events can be seen and/or manipulated) Which commands of the dispatch system a given user can execute For example, in I/CAD, the I/CAD logon serves to establish the user as a call taker, dispatcher, supervisor, or other user. For dispatchers and supervisors, the logon also establishes the dispatch group. Thus, in I/CAD, the logon establishes the privileges allowed and the resources to be used. Within I/CAD, the roles are hierarchical, for example, dispatchers have call taking privileges, and supervisors have dispatching privileges. I/CAD Security The I/CAD Database Maintenance utility (CADDBM) is used to establish and maintain personnel records for the employees of the customer's agencies. The System Access Record section is where the System Administrator establishes the employee's user ID and password. The figure below shows an example of the Personnel dialog in CADDBM. TAB 3 — Firm Plan of Approach Persorinel 'Employee ID: Last Name: First Name: MI: Agency ID: Reset j2035(Cone (Lynda LMPD Close Street Address: City: State: User Group ID: �LMPD Print Pager ID: Blood Type: Alphanumeric Employee ID: App Access (1) J Sync Lineups (1) ... Phone: F— E-Mail Address: Devices (1) Primary ... Trackable Device ID I Alias I Type I Sub -Type J GPS Protocol Yes 2035 GPS Device Default 5... NMEA Modify Notify Name: Address: F— System Access User ID: ICONE CAD Domain: INGRNET Password: Confirm Password: z%%%z %%zz xxzz xxzz x z x z Number of Days Password Valid: 9999 NotifyAfter Days Elapsed: 19998 CADDBM Nodename: r Devices... Phone: City: State: Pos. Command Class .. 49 Supervisor 50 Dispatcher 51 Calltaker 52 MDT Supervisor 53 MDT Operator 54 NetViewer Full Pos. Command Class + 1 Supervisor 2 Dispatcher 3 Calltaker 4 Node Cmd Acces Retrieyr Insert Update Review and)or edit record(s) then select processing command. Retrieve complete. Agency Security Group:: Skills Default Unit ID: i Station: Modify Skills.., Active Employee T— Clear form after Insert and Update Personnel Dialog in CADDBM An Agency Security Groups dialog box within CADDBM is used to create and manage groups of agencies for which users can restrict event comments or access to staging areas. For example, if a user wants to create a staging area and only wants units in agency 1 and 2 to be dispatched to it, he/she might create a group with agencies 1 and 2 in the Agency Security Groups dialog box. Besides staging areas, event remarks can also be restricted by group. They can be set to Common or be restricted to just one agency, but the Agency Security Groups dialog box now lets users specify groups of agencies for restriction. The Restrictions tab on the Event Information dialog box in CAD is used to set such restrictions so that remarks can only be seen by agencies in a specific group. The System Administrator can use the administrative functions without interrupting I/CAD System operations. i/ HEXAGON SAFETY & INFRASTRUCTURE Windows Security TAB 3 — Firm Plan of Approach Before logging into I/CAD, the user must first log into Windows. The following text addresses Windows security. The Windows password policy can set the following limits on user passwords: Enforce password history —specifies how many different passwords a user must use before being allowed to reuse one. With the default setting, a user can immediately reuse an expired password. This setting can be changed to require operators to create from 1 to 24 unique passwords before reusing one Maximum password age — specifies how long a user can use a password without changing it. By default, this setting is 42 days. It can be set to any value from 1 to 999 days, or it can be set to never expire. Advance warnings are supplied Minimum password age — specifies how long a user must wait after changing a password before the user can change it again. By default, operators can change their passwords immediately. This setting can be changed to any value between 1 and 999 days Minimum Password Length — specifies how many characters a password must contain. By default, Windows permits blank passwords. Many System Administrators, however, change this option. A recommended minimum is 6 characters, but it can be as high as 14 characters Password must meet complexity requirements — specifies whether the password will meet the following: Not contain the user's account name or parts of the user's full name that exceed two consecutive characters Be at least six characters in length Contain characters from three of the following four categories: English uppercase characters (A through Z) English lowercase characters (a through z) Base 10 digits (0 through 9) Non -alphabetic characters (for example, !, $, #, %) Complexity requirements are enforced when passwords are changed or created. Password and user name cannot be the same. Store passwords using reversible encryption —specifies whether the encrypted password can be reversed. HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Local Security Policy File Action View Help *I _951LLSII®: Security Settings .1 .,3 Account Policies Password Policy p LA Account Lockout Policy p Ea local Policies p [n Windows Firewall with Advanced Sec, IJ1 Network List Manager Policies p i_"` Public Key Policies Software Restriction Policies Application Application Control Policies IP Security Policies on Local Compute Advanced Audit Policy Configuration Policy 3 Enforce password history Maximum password age Minimum password age j Minimum password length - Password must meet complexity requirements StorE passwords using reversible encryption Local Security Policy in Windows Security Setting 5 passwords remembered 90 days 1 days 8 characters Enabled Disabled Windows provides an account lockout feature. When this feature is enabled, a user account becomes locked if there are a number of incorrect attempts to log on to that account within a specified amount of time. Locked accounts cannot log on. A locked account remains locked until a System Administrator unlocks it or until a specified amount of time passes, depending on how the account lockout feature has been configured. By default, account lockout is disabled. As with the set-up programs used to load new software or update existing software, security administration is GUI -driven. However, rather than stepping the System Administrator through rigid, system -defined security policies, Windows uses combinations of options presented in dialogs or in user windows to establish a system security setup that define the customer's requirements. These utilities set the following: Domain account policies and restrictions, that determine: Maximum and minimum password ages Minimum password length Number of passwords that must be used before a previously used password can be recycled (password uniqueness) Number of invalid log -on attempts prior to enacting account lockout Amount of time the account lockout remains in effect Forcible disconnection of users when a set number of hours expire Forcible user log on prior to changing a password. This option prevents users whose passwords have expired from logging into the system User account policies, such as: HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Whether or not users can independently change passwords or whether password modification requires System Administrator assistance Whether a user account is enabled or disabled. An account may be disabled if an operator is on vacation, for example. If the user no longer works for the customer, however, the user account should be removed Groups the user belongs to Time of day users are entitled to access the system Specific workstation a user is entitled to log on to Group and user account parameters and privileges, that determine: Which user accounts have access to system management privileges, such as: Administrator privileges Server operator privileges Account operator privileges Print operator privileges • Which folders and files a user group may access • Who can log on to the server • Who has authorization to initiate backups of the system. Potentially, operators granted this privilege can carry information off -site Who can set up auditing and security logs Who can take ownership of files or other objects System audit policies and administrator account privileges, such as: Whether or not to audit failed log -on attempts, file and object access, security policy changes, workstation startup and shutdown, and process use Whether or not administrative procedures must be performed from a designated workstation Removal or retention of the Domain Administrator's Group for each workstation File and directory permissions and shares privileges and auditing options such as: Whether or not accessing files or folders will be audited Which groups or users have access to certain files and folders Windows provides the capability of administering usernames/passwords and access to network objects as a single domain or as multiple domains connected through trust relationships. Future releases of the Windows operating system are anticipated to provide a richer set of administration capabilities through its "Active Directory" technology. These techniques will allow the System Administrator to achieve security policies inside the protected network. _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach 7) Comprehensiveness of the documentation (e.g., training materials and manuals) Hexagon has read and acknowledges. Hexagon respectfully clarifies that all documentation provided will be for the COTS software, and not customized based on any configuration changes the County may implement. Editable versions of all documentation (except for product help files) will be provided so the County may edit the content as they see fit. Hexagon respectfully proposes to provide only electronic copies of documentation, which the County may print if so desired. Hexagon respectfully clarifies that all software, content, and documentation including tables, layouts, queries, stored procedures, data dictionaries, and XML schema, developed by Hexagon and provided to the County by Hexagon shall be owned by Hexagon. I/CAD SYSTEM DOCUMENTATION Hexagon proposes its online, commercial off -the -shelf (COTS) technical system, and user documentation for Intergraph products procured under contract agreement. These documents have been developed, updated, and fine-tuned during years of I/CAD implementations. The County can edit the provided online Help file documentation for any site -specific configuration changes, but Hexagon does not recommend customizing Help files as the standard COTS Help files are re -delivered with each Features and Fixes upgrade, which will overwrite any Help files customizations. Hexagon services to customize the online Help files to the County's site -specific configuration, requirements, or functionality developed during the implementation process are not included in this proposal. The following table notes the documents Hexagon proposes to supply during the project. DOCUMENT TYPE PROVIDED HEXAGON COMMENT (YEs/No) User documentation Yes User documentation will be provided Configuration documentation Yes Configuration documentation will be provided Yes Interface documentation Interface documentation will be provided System administration documentation will System administration manuals Yes be provided Yes Application software tutorial Lab exercises are included as part of the training documentation Yes Data dictionaries Hexagon will provide an I/CAD Database schema with a description of each field and table Yes Database setup and maintenance Database setup information is provided in the system administration online Help file. Database maintenance information is included in the I/CAD System Maintenance �.J HEXAGON TAB 3 — Firm Plan of Approach manual, in addition to the Microsoft SQL Server online documentation Entity relationship diagrams Please see Hexagon does not deliver a classic "Entity comment for Relationship Diagram" (ERD). Instead, with clarification the supplied I/CAD Database Utility, a Conceptual Model within the I/CAD Database schema can be generated that will show all associations (relationships) with other database entities, equivalent to an ERD -7System documentation Yes System documentation will be provided. Documentation for web Yes Hexagon will provide web service/interface service/interface definitions definitions First level triaging/troubleshooting for Yes Hexagon will provide first level Agency help -desk triaging/troubleshooting for Agency help - desk Help desk support call escalation Yes Hexagon will provide a help desk support process i call escalation process Because Help files are internal to each application purchased, Help files specifically address the following requested documentation: User documentation Interfaces documentation System Administration documentation, which includes data dictionaries, entity relationship diagrams, system documentation, and troubleshooting information Beyond the Help files, proposed Hexagon documentation includes: A site -specific configuration diagram current at cutover Site -specific System Design documentation User Training Manuals. Training manuals are provided for each course, and each student receives a hardcopy in a binder. A softcopy for reproduction purposes is provided to Agency trainers. Because the content of training materials is copyrighted, Hexagon requests that training materials be passed only to persons who require access to the materials to perform their jobs. Customization changes or updates to the User Training Manuals are the responsibility of the customer. Apart from Interface Control Documents, a current Configuration Diagram, the Statement of Work (SOW), and attachments, site -specific documentation is not offered. HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach 8) Product life expectancy (identify all versions of the CAD solution since inception and any on going research and development efforts) Hexagon has read and acknowledges. Versions of CAD since inception: 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 9.0, 9.1, 9.1.1, 9.2, 9.3 and 9.4. Hexagon has proposed CAD 9.4 for the County's project. As an industry leader, Hexagon recognizes it must continue to invest in and advance its products to meet the dynamic nature of the industry. To that end, Hexagon invests substantial resources and capital into its research and development. Hexagon's technology and industry roadmap is built upon the collective knowledge that Hexagon has gained through interaction with our existing customers, information from incoming RFPs, and ultimately Hexagon's own interaction within the global public safety industry. These data points allow Hexagon to build a comprehensive vision for our products and services that is in alignment with the public safety industry, both in terms of the capabilities and technologies required. This vision takes into account the need to deliver these capabilities in a manner that is adoptable by our current and future clients on a timeline that is consistent with the delivery of the technologies and infrastructures needed to exploit these capabilities. Hexagon is using the following trends as underlying drivers in our forward -thinking roadmap: Need to reduce costs, improve efficiencies, and exploit technology advances Changing the way public safety personnel work Increase in wireless communications bandwidth — reduction in costs Workforce and public mobility creating new paths for "communicating" Continued call for interoperability Sensors, Cameras, Access Control Next Generation 911 /112 Social Networks Standards: NIEM, IA3, CAPS, OGC Upsurge of relevant data to support decision -making processes "How do I make sense of all of this data?" Emergence of analytics as part of public safety "toolkit" Geospatial context increasing importance Predictive and operational use Data ownership issues — Economies of scale — Cost sharing Based on these trends Hexagon is investigating and/or considering solutions and product enhancement in the following areas: IP-based Communications CAD Enablement — VOIP Media Portal Integration _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Hexagon views the delivery of NG9-1-1 capability to be a key driver in the development of CAD -centric workflows to use the new call functions that will be part of NG9-1-1. Hexagon's experience in the delivery of advanced computer telephony integration (CTI) capability will serve as the basis for the delivery of both NG9-1-1 and "pre-NG9-1 -1 " capabilities in the areas of text message processing and well as advance notifications support Interoperability — Enterprise and Regional Levels Hexagon continues to develop enterprise interoperability solutions built around industry standards including NIEM. Hexagon will build upon its experience with its EdgeFrontier technology, to support advanced interoperability solutions across a wide range of devices, standards, and topologies Security Hardening/Assessments and Sensor Fusion — Cameras, Telematics, Bio-Hazard, ITS Hexagon continues to enhance the integration of its Security Framework solution with CAD to meet emerging requirements for public safety management of civil security infrastructures, including video surveillance Business Intelligence and Analytics Hexagon will continue to enhance its BI solutions to include its current CAD platform. Large scale event and emergency planning and response solutions Hexagon recognizes the need for a tighter participation of the CAD solution into the broader Emergency Operations Center environment `Hosted' Applications — Cloud Computing, SaaS, Web apps Hexagon is investigating hybrid solutions that allow on -premise solutions of CAD to operate in a tight integration with hosted components, such as text and or notifications applications. Hexagon continues to investigate how I/CAD and other Hexagon solution components can operate in both public and/or private clouds in the future. Hexagon continues to invest in the delivery of thin/smart clients in areas such as browser -based CAD clients. These solutions will exploit technologies that improve the overall total cost of ownership with increased capability Additional mobile applications on a variety of platforms Hexagon is investing in the delivery of enhanced mobility solutions that recognizes the need to support the delivery of information, dynamically, across a wide range of mobile devices, from the laptop to the Smartphone, across enhanced LTE infrastructures Enhancing the end user experience Hexagon continues to apply industry leading approaches, developed through interaction with experts in man/machine interfaces, to the issue of information display and graphical user interfaces. Hexagon continues to apply technology, including WPF and HTML5 as key levers in the enhancement of data/information displays. _ HEXAGON SAFETY & INFRASTRUCTURE TAB 3 — Firm Plan of Approach Any commercial off -the -shelf product information Hexagon has or will share with its audience during the proposal / contract activities, are to provide an understanding of Hexagon's current expected direction, roadmap or vision and is subject to change at any time at Hexagon's sole discretion. Hexagon does not commit to develop the future features, functions and products discussed in this material beyond that which is specifically committed to be provided by Hexagon as part of the intended contract. The audience of this material should not factor any future features, functions or products into its current buying decision since there is no assurance that such future features, functions or products will be developed. When and if these future features, functions or products are developed, they will generally be available for licensing by Hexagon. 9) Intuitiveness and aesthetic appeal of the software Hexagon has read and acknowledges. HEXAGON SAFETY & INFRASTRUCTURE fi�RAPH ATTACHMENT 3.1 - SAMPLE PROJECT SCHEDULE I i A3.1-1 ID % Task Name Work Days Complete L 0% Lee County, FL CAD Project 303 days 0% 0 days 0% Planning Phase 60 days 0% Draft Project Schedule developed 5 days 0% Review of Deliverables Requirements 1 day 0% Establish Project Organizational Structure 1 day 0% Review of Training Requirements 1 day 0% Review Interfaces and Functions 1 day 0% Deliver Draft Project Schedule to Customer 1 day 0% Customer Review Draft Project Schedule 0 days 0% Project Kickoff 4 days 0% Travel 2.13 days 0% Project kickoff Meeting 2 days 0% Travel Return 1 day 0% Organize and Schedule Project 31 days 0% Deliver Kickoff Meeting Notes to Customer 1 day 0% Hexagon Updates Draft Project Schedule from Project Kickoff Meeting 1 day 0% Deliver Updated Project Schedule to Customer for Approval 0 days 0% Customer Reviews / Approves Updated Project Schedule 3 days 0% Final Project Schedule confirmed 1 day 0% Hexagon Server Accounts Created 0 days 0% Hexagon Orders Software 0 days 0% CAD and Interface Data Gathering 43 days 0% CAD/Interface Requirements Traceability Matrix 5 days 0% Map requirements to CAD 5 days 0% Interface Control Documents 24 days 0% Develop Custom Interface ICD and Interface Questionaires S days 0% Develop Informer ICD 5 days 0% Customer Review ICDs and Questionaires 10 days 0% Update ICDs based on Customer Comments 2 days 0% Customer Review of ICDs S days 0% Finalize ICDs 2 days 0% I/CAD Launch 26 days 0% Travel 1 day 0% I/CAD Launch 4 days 0% Gather Requirement Data 5 days 0% Map Data Gathering 18 days 0% I/CAD MAP Launch 18 days 0% Travel 1 day 0% I/CAD Map Launch Onsite Workshop 2 days 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 Page 1 2 % Complete 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% Task Name Travel Return Gather Map Data Requirements Map Data Analysis Test Plan & Test Case Creation Hexagon Send Sample Test Plans to Customer Customer builds test plan and test cases Hexagon reviews and approves Test plan and test cases Staging phase Map Build 1 Map Build 1 Map Build 1 SR resolution Hardware Staging Onsite hardware Install VM Setup Interface Development COTS Interfaces Informer Development (Optioned) I/CADLink Set up I/FRMS CADLink (Fire Link) ANI/ALI Priority Dispatch I/Page I/PTT I/Fire Station Alerting (I/FSA) I/Fire Station Printing (I/FSP) I/TDD I/Tracker for PLT Custom Interfaces ASAP CAD EF Interface Spillman Flex CAD EF Interface CAD -To -CAD Interface to Tri-Tech CAD -To -CAD Interface to Motorola Premier 1 CAD -To -CAD Inteface to OSSI Visual CAD Econol-ite EF (Consulting Services Only) ASTRO 25 CAD EF Interface Telestaff Import Video Responder Integration Development Support for Linked Event Remarks Updates Software Staging System Build 1 System Build 1 Prep Travel Work Days L 1 day 10 days 5 days 31 days 1 day 20 days 10 days 178 days 6 days 5 days 1 day 25 days 5 days 20 days 178 days 61 days 30 days 1 day 20 days 1 day 1 day 3 days 1 day 1 day 1 day 1 day 1 day 178 days 12 days 10 days 5 days 5 days 5 days S days 5 days 10 days 25 days 3 days 75 days 19.5 days 0.5 days 1 day 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 Page 2 ID % Task Name Work Days Complet L 0% System Build 1 4 days 0% Requirements Gathering 10 days 0% System Build 2 10 days 0% Travel 1 day 0% System Build 2 4 days 0% Requirements Gathering 5 days 0% System Build 3 15 days 0% Travel 1 day 0% System Build 3 4 days 0% System Health Check 9 days 0% Trusted Advisor Health Check Prep - CAD 0.5 days 0% Travel 1 day 0% Trusted Advisor Health Check - CAD 2 days 0% Travel Return 1 day 0% Customer Requirements Gathering 5 days 0% Post System Build SR Resolution 5 days 0% Interface Staging 10 days 0% I/CAD Data Conversion 40 days 0% MPS Overview 16 days 0% MPS Overview Prep 1 day 0% Travel 1 day 0% Onsite MPS Overview 3 days 0% Travel Return 1 day 0% Configuration Phase 183 days 0% Configure CAD 61 days 0% System Configure 1 15 days 0% Travel 1 day 0% System Configure 1 4 days 0% Customer Data Input 10 days 0% System Configure 2 15 days 0% Travel 1 day 0% System Configure 2 4 days 0% Customer Data Input 10 days 0% System Configure 3 43 days 0% Travel 1 day 0% System Configure 3 4 days 0% Customer Data Input 10 days 0% Req 4-029 Alternate Response Plan Crisis Mode 4 days 0% Req 7-144 Sync Training System 2 days 0% Mobile Related Custom Congurations 10 days 0% Advanced GIS Requirements (Intelligent Icons, etc.) 10 days 0% Health Check 6 days 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 Page 3 2 m 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 ask Name Work Days Trusted Advisor Health Check Prep - CAD 0.5 days Travel 1 day Trusted Advisor Health Check - CAD 2 days Travel Return 1 day Post CAD System Configure SR Resolution 10 days Configure MPS 54.5 days MPS Barcode and MagStripe Reader Set up 10 days MPS Workshop 1 34.5 days Travel 1 day MPS Configuration Workshop 1 - Fire/EMS 3 days MPS Configuration Workshop 1 Follow-up S days MPS Workshop 2 9 days Travel 1 day MPS Configuration Workshop 2 - Fire/EMS 3 days MPS Conguration Follow up 2 - Fire/EMS S days Health Check 30.5 days Trusted Advisor Health Check Prep - Interfaces 0.5 days Travel 1 day Trusted Advisor Health Check - Interfaces 2 days Travel Return 1 day MPS Pilot 10 days MPS Pilot Support - (2 Weeks @ 20 Hours Per Week) 10 days 147 0% Post MPS/Interface System Configure SR Resolution - Remote 10 days 0% Map Configuration 140 days 0% Map Build 2 34 days 0% Map Build 2 Prep 1 day 0% Travel 1 day 0% Map Build 2 4 days 0% Map Build 2 SR resolution 3 days 0% Map Build 3 13 days 0% Map Build 3 Prep 1 day 0% Travel 1 day 0% Map Build 3 4 days 0% Map Build 3 SR resolution 3 days 0% Video Responder Implementation 5 days 0% Apply Maintenance Release S days 0% Deployment Phase 302 days 0% Testing Phase 47 days 0% Factory Acceptance Testing 9 days 0% FAT 4 days 0% FAT SR Resolution S days 0% SAT 1 31 days 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 Page 4 ID % Complete 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% Task Name SAT 1 Support Prep SAT 1 Support Onsite SAT 1 SR Resolution Health Check Trusted Advisor Health Check Prep- Interfaces Travel Trusted Advisor Health Check - Interfaces Travel Return SAT 2 SAT 2 SAT 2 SR Resolution Map Maintenance Class Map Maintenance Prep Travel Map Maintenance Class System Configuration LockdokA, Disaster Recovery Document Disaster Recovery Process Test/Vet DR Document and Process Training Phase LMS Training Development CAD Calltacker and Dispatcher Insight Reporting Mobile For Public Safety Netviewer/NetDispatcher I/Sight Map Basics Map Basics for I/CAD Systems (IPST8001) - Prep Map Basics for I/CAD Systems (IPST8001) I/CAD System Administration Intro I/CAD Essentials Trainers I/CAD Essentials for Core Team MPS TTT MPS Administration & Configuration NetViewer/NetDispatcher I/CAD System Administration Core I/CAD System Administration Advanced Insight Reporting for Administrators I/Sight Customer End User Training Go -Live Phase Work Days L 2 days 5 days 10 days 5 days 0.5 days 1 day 2 days 1 day 14 days 4 days 10 days 8 days 1 day 1 day 4 days 0 days 7 days 5 days 2 days 255 days 212 days 60 days 25 days 25 days 13 days 13 days 6 days 1 day 5 days 23 days 15 days 6 days 45 days 6 days 3 days 20 days 10 days 2 days 12 days 30 days 90 days 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 204 208 211 217 221 224 233 238 241 248 249 250 0% Go -Live Readiness Review 53 days Page 5 ID % Complete 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% Task Name Create Go -Live Plan Install CAD Workstations Install MDC Software Readiness Review Go Live Reliability Period Onsite Go -Live Onsite Go -Live Support Post Go -Live Support - Remote Updating/Finalizing Site Config Documents Post Go -Live Training Test/Train Servers Set up Test/Training Servers EdgeFrontier Developer Training EdgeFrontier Developer Training Prep Travel EdgeFrontier Developer Training Project Closure Work Days L 2 days 10 days 10 days 2 days 0 days 30 days S days S days 20 days 0 days 7 days 3 days 3 days 7 days 1 day 1 day S days 1 day 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 Page 6 HEXAGON SAFETY& INFRASTRUCTURE IrvrERGwAPH ATTACHMENT 3.2 - DESCRIPTIONS LEE COUNTY, FL RFP FOR CAD REPLACEMENT TRAINING COURSE Below is a list of proposed Hexagon training courses and their descriptions for this project: On -site Training Offering CAD System Administration Introduction (Qty: 6) CAD System Administration Core (Qty: 4) CAD System Administration Advanced (Qty: 2) I/CAD Essentials for Core Team (Qty: 1) I/CAD Essentials for Trainers (TTT) (Qty: 2) InSight Reporting for Administrators Training (Qty: 1) Mobile for Public Safety (MPS) Administration & Configuration (Qty: 1) MPS for Trainers (TTT) (Qty: 2) I/NetViewer / I/NetDispatcher for Trainers (TTT) (Qty: 1) EdgeFrontier Developer Training (Qty: 1) I/Sight for Users Training (Qty: 3) Mobile Responder Training (Optional) Additionally, Hexagon offers Learning Management Solution (LMS) Online Customized Training for the following: CAD Calltaker and Dispatcher InSight Reporting for Users MPS I/NetViewer I/Sight Training This will allow the County to provide online training for their CAD, Mobile, and IT users when/where appropriate. Hexagon would welcome a discussion with Lee County staff to utilize our Learning Management Solution options to meet their training requirements. Our LMS offering can assist the County by: Lowering training costs Allowing employees to repeat the course as the system goes live Providing flexibility for employee training Providing on -going end user training A3.2-1 _ HEXAGON SAFETY & INFRASTRUCTURE Attachment 3.2 - Training Course Descriptions Hexagon has priced LMS Access for up to 500 active users for one month prior to cutover and LMS access for up to 100 users for 12 months following cutover. Hexagon also provides access to WebEx topical discussions free -of -charge to customers via our Customer website. Additionally, Hexagon provides customers with access to an online support knowledge base with keyword search capability to facilitate a search of the knowledge base to facilitate problem resolution. A softcopy of the user training manual for reproduction purposes is provided to Agency Trainers. Because the content of training materials is copyrighted, Hexagon requests that training materials be passed only to persons who require access to the materials to perform their jobs. A3.2-2 COURSE DESCRIPTION: Attachment 3.2 - Training Course Descriptions Intro to CAD system administration is a three-day class focusing on understanding how Intergraph's Computer Added Dispatcher(CAD) system works. The class will set up and configure Admin client machines and get them up and running in a multiple configuration environment. The class will work with CADDBM and other tools to understand the day to day configuration changes a sys admin would be responsible for making. These include tasks like setting up new users, changing client configurations and parameter settings through CADDBM, and assisting client dispatchers. Students completing the course work should have a good working knowledge of the CAD system and the day to day responsibilities of a CAD System Admin. COURSE/SESSION DURATION: 3 COURSE DAYS (24 HOURS) I DAYS: COURSE PREREQUISITES: FACILITY REQUIREMENTS: DESIRED FACILITY ABILITIES: COURSE/SESSION MATERIALS: COURSE HOURS: Tuesday — Thursday 8:OOam — 5:OOpm MAXIMUM 112 ATTENDEES: Customer Hardware fully staged and available CAD System fully licensed, staged, and available Hexagon credentials (operating system) available Hexagon user account provisioned with local administrator rights on all servers and workstations Customer Data collection spreadsheets completed Standalone CAD VM fully staged and put on each workstation w Training room/facility configured with network access to servers Training room with up to 12 student workstations (Dual Screen) Trainer workstation (Dual Screen) Projector/TV connected to at least one of the trainer's screens 0 Internet access available (Wi-Fi preferred, wired acceptable) • Two Projectors/TVs connect to Trainer's workstation CAD System Administration Manual (hardcopy for each student) Labs Document (hardcopy for each student) A3.2-3 HEXAGON SAFETY & IN FRASTRUCTU RE Attachment 3.2 - Training Course Descriptions REQUIRED ATTENDEES: ! Hexagon Instructor 4: Customer Support Personnel (System Administrators, Support Technicians) OPTIONAL ATTENDEES: Customer Users & Trainers I i A3.2-4 HEXAGON SA F ETY & I N F RASTR UCTU R E Attachment 3.2 - Training Course Descriptions CAD System • • • - 11 COURSE DESCRIPTION: Core System Administration class is a four -day course on how to setup, configure and manage a CAD system. During this class, the students will learn how to create and setup a CAD database. The students will install the CAD server and client products. They will configure and trouble shoot the CAD system. The class goal is to finish the class with a working CAD system. The class will create this system working with tools like: Map Publisher, CADDBM, ISM, ICAD Database Utility, ICAD Parameter Utility, CAD Query Tool, SQL and other products. COURSE/SESSION DURATION: 4 DAYS (32 COURSE DAYS: Monday —Thursday HOURS) COURSE HOURS: 8:OOam — 5:OOpm MAXIMUM 12 ATTENDEES: COURSE PREREQUISITES: Completion of CAD System Administration Training - Introduction • Customer Hardware fully staged and available CAD System fully licensed, staged, and available Hexagon credentials (operating system) available • Hexagon user account provisioned with local administrator rights on all servers and workstations Customer Data collection spreadsheets completed • Standalone CAD VM fully staged and put on each workstation FACILITY REQUIREMENTS DESIRED FACILITY ABILITIES: COURSE/SESSION I MATERIALS: • Training room/facility configured with network access to servers • Training room with up to 12 student workstations (Dual Screen) • Trainer workstation (Dual Screen) • Projector/TV connected to at least one of the trainer's screens • Internet access available (Wi-Fi preferred, wired acceptable) • Two Projectors/TVs connect to Trainer's workstation • CAD System Administration Manual (hardcopy for each student) • Labs Document (hardcopy for each student) A3.2-5 HEXAGON SAFETY & INFRASTRUCTURE Attachment 3.2 - Training Course Descriptions REQUIRED ATTENDEES: I Hexagon Instructor a Customer Support Personnel (System Administrators, Support Technicians) OPTIONAL ATTENDEES: 1 • Customer Users & Trainers A3.2-6 a/ HEXAGON SAFETY & IN FRASTRUCTU RE Attachment 3.2 - Training Course Descriptions CAD System • • • -• 11 COURSE DESCRIPTION: Advance System Administration class is a four -day class on how to customize and extend the CAD functionality through CADDBM, Macros, Visual Studio, CAD workflows and other tools. This class will focus on the customization of the I/Dispatcher interfaces and creating workflows to extend CAD functionality utilizing CAD delivered tools. Utilizing CAD workflows, the class will enhance the delivered CAD functions to better mimic customer workflows. The class goal is to finish the class with a better understanding of the customization possibilities of CAD. COURSE/SESSION DURATION: 4 DAYS (32 -COURSE DAYS: Monday — Thursday HOURS) COURSE HOURS: 8:OOam — 5:OOpm MAXIMUM 12 ATTENDEES: COURSE Completion of CAD System Administration Training - Core PREREQUISITES: CAD System fully licensed, staged, and available Hexagon credentials (operating system) available Hexagon user account provisioned with local administrator rights on all servers and workstations Customer Data collection spreadsheets completed Standalone CAD VM fully staged and put on each workstation FACILITY REQUIREMENTS: DESIRED FACILITY ABILITIES: COURSE/SESSION MATERIALS: REQUIRED ATTENDEES: Training room/facility configured with network access to servers Training room with up to 12 student workstations (Dual Screen) Trainer workstation (Dual Screen) Projector/TV connected to at least one of the trainer's screens Internet access available (Wi-Fi preferred, wired acceptable) • Two Projectors/TVs connect to Trainer's workstation • CAD System Administration Manual (hardcopy for each student) • Labs Document (hardcopy for each student) Hexagon Instructor Customer Support Personnel (System Administrators, Support Technicians) OPTIONAL ATTENDEES: • Customer Users • Customer Trainers A3.2-7 HEXAGON SAFETY & IN FRASTRUCTU RE Attachment 3.2 - Training Course Descriptions • . for • The I/CAD Essentials for Core Team course is presented directly to Customer Core Team personnel to provide a complete overview of the I/CAD, I/NetViewer, and I/NetDispatcher applications. This course familiarizes the Core Team with the basic features of I/CAD including event processing and dispatching, as well as map utilization and inquiries so that the analysis of workflows and testing of data can begin. This course combines Calltaking Essentials, Dispatching Essentials, Advanced I/CAD Functions (where appropriate), I/NetViewer, and I/NetDispatcher course work. MAJOR TOPICS • Call Creation and Update • Performing Law Enforcement Specific • Map View Control Operations — Traffic Stop, Subject Stop • Event and Personnel Inquiries • Performing EMS Specific Operations — Divert Hospital • Sending Messages • Supervisor Specific Commands Recommending and Dispatching Units • Advanced I/CAD Commands Updating Unit Statuses • Interfaces for Users (I/Informer, I/Page, • Modifying Unit Properties I/FSA, and I/MDT for example) • Updating Unit Related Event Information • Interfaces for Users (as needed, if • Querying Unit and Event Data installed interfaces are applicable for Calltakers) • Performing Fire Specific Operations — NetViewer/NetDispatcher Basics Update Alarm, Relocate (Move Up) Units PREREQUISITE, • Assignment to the Customer Core Team • Completion of an introductory Windows course or equivalent knowledge and familiarity with the Windows user interface TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience Dispatchers, Calltakers, CAD Supervisors, CAD System Administrator(s), and CAD Training Personnel Duration 5 Days Student Capacity 12, with a maximum of 1 student per workstation A3.2-8 0 HEXAGON SA F ETY & I N F RASTR UCTU R E Attachment 3.2 - Training Course Descriptions Dispatcher• The I/CAD Dispatcher Essentials for Train -The -Trainer course is presented directly to personnel responsible for training Public Safety Dispatchers. It familiarizes telecommunications personnel with the basic features of workstations, terminology, forms, navigation, and event processing, as well as map utilization and inquiries. Laboratory exercises are included with each module to provide additional experience in workstation operation. Upon completion of this course, attendees will be prepared to train Dispatchers in I/CAD Essentials. MAJOR TOPICS Call Creation and Update • Performing Law Enforcement Specific Map View Control Operations — Traffic Stop, Subject Stop Event and Personnel Inquiries • Performing EMS Specific Operations — Divert Hospital Sending Messages • Supervisor Specific Commands • Recommending and Dispatching Units • Interfaces for Users (I/Informer, I/Page, • Updating Unit Statuses I/FSA, and I/MDT for example) • Modifying Unit Properties • Advanced I/CAD Functions as needed • Updating Unit Related Event Information • Trainer Guidelines and Techniques for • Querying Unit and Event Data I/CAD • Performing Fire Specific Operations — Update Alarm, Relocate (Move Up) Units PREREQUISITES • Knowledge of basic Public Safety terminology • Responsibility for Dispatching An introduction to Windows course or equivalent knowledge and familiarity with the Windows user interface • Completion of I/CAD Build and Configure phases TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience I/CAD Training Personnel 5 Days for the first course, and 4 days for the second course. Hexagon Duration assumes the same students will be at both the first week and the second week. Student Capacity 12 Students, with a maximum of 1 student per workstation IA3.2-9 kPJJ 1 HEXAGON SAFETY & IN FRASTRUCTU RE Attachment 3.2 - Training Course Descriptions InSight Reporting for I/CAD - System Administrator Training (Qt conducted on InSight Reporting for I/CAD offers the ability to perform powerful and interactive reporting and analyses on data available in I/CAD database. InSight Reporting for I/CAD provides capabilities for the user to view and modify reports as needed and conduct ad -hoc queries through a secure web portal. With minimal knowledge of underlying database structures, users can create custom formulae and reports and analyze data using a pre -configured tabular models and cosmetic views designed for easy reporting and built using industry terminology. This course is designed for system and database administrators to familiarize them with the setup and maintenance of Intergraph's InSight Reporting for I/CAD product. It will provide instruction on the setup, site -specific configurations and installations, and administrative tasks needed to maintain the InSight Reporting for I/CAD system. MAJOR TOPICS 4, Overview of Site Setup and Configuration Client Installs and Requirements SSRS Administration InSight Reporting for I/CAD Reports Site Specific Configuration Systems Backups and Troubleshooting Techniques PREREQUISITES Familiar with Windows -based applications, administrative tasks, and agency workflows Familiar with I/CAD databases Familiar with Oracle or SQL Server databases Trainees will need a laptop or computer with Microsoft PowerBI installed TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience I/CAD system administrators, database administrators, and other personnel responsible for administering InSight Reporting for I/CAD. Duration 1 day Student Capacity 12, with a maximum of 1 students per workstation A3.2-10 HEXAGON SAFETY & IN FRASTRUCTU RE Attachment 3.2 - Training Course Descriptions InSight Reporting for I/CAD - Userdiraininu conducted through LMS only InSight Reporting for I/CAD offers the ability to perform powerful and interactive reporting and analyses on data available in I/CAD database. InSight Reporting for I/CAD provides capabilities for the user to view and modify reports as needed and conduct ad -hoc queries through a secure web portal. With minimal knowledge of underlying database structures, users can create custom formulae and reports and analyze data using a pre -configured tabular models and cosmetic views designed for easy reporting and built using industry terminology. This course is designed for the end user or administrator to familiarize them with the use of InSight Reporting for I/CAD product and provides training on creating and editing reports and performing ad - hoc queries and data analyses using InSight Reporting for I/CAD. MAJOR TOPICS Overview of InSight Reporting for I/CAD L Generating Reports in SSRS Generating Reports by leveraging PowerBl Other Client Tools PREREQUISITES • Familiar with Windows based applications Familiar with I/CAD data Familiar with agency workflows Trainees will need a laptop or computer with Microsoft PowerBl installed TRAINING DETAILS Method Conducted through LMS only Target Audience Personnel responsible for reporting and analysis; Future trainers Duration 80 hours available through the LMS A3.2-11 HEXAGON SA F ETY & I N F RASTR UCTU R E Attachment 3.2 - Training Course Descriptions MPS Administration and Configuration The MPS (Mobile for Public Safety) Administration and Configuration course is an intensive course designed for individuals responsible for the technical administration, management, and support of the MPS system. Students receive both classroom training and hands-on experience enabling them to perform advanced functions associated with the setup, configuration, and ongoing maintenance of the MPS system. Please note the stated prerequisites and student capacity, as strict adherence to these is essential for the successful completion of this course. MAJOR TOPICS COM Server Best Practices Review of the CAD Database Tables Reports related to MPS Map Data flow between MPS and the CAD • Options XML files Server • Settings Tool • Discuss: RCM Administration Toolbar buttons iL Update Tool Homepage buttons • Multi -Installer Tool Advance menus • MPS Troubleshooting Status Bar • Logs Monitors PREREQUISITES Adherence to the following prerequisites is mandatory: • Responsibility for the administration, support, and maintenance of the MPS application • Familiarity with I/Dispatcher functionality, use, and workflows • Working knowledge of SQL, XML, XSL, HTML, and ASP • Basic knowledge of Microsoft Visual Studio TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience System administrator(s) and other support personnel Duration 4 days Student Capacity 12 A3.2-12 HEXAGON SAFETY & INFRASTRUCTURE Attachment 3.2 - Training Course Descriptions MPS for Trainers (Qty: 2) AM MPS for Trainers training is designed to train agency trainers in the use of the MPS product. MAJOR TOPICS Using MPS on Mobile Data Computers (MDCs) or laptops Changing unit status Submitting inquiries • Sending and receiving messages • Updating unit properties • Updating events • Using training guidelines and techniques for MPS • I/Informer queries from MPS (if applicable) PREREQUISITES Responsibility for mobile computing training Assignment of at least one person who has been through I/CAD Essentials training to perform necessary dispatching and other I/CAD functions Availability of customer -specific MPS configuration Availability of test or training MPS PCs for use in class TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience Designated MPS Trainers Duration 3 days Student Capacity 12, with a maximum of 1 student per workstation A3.2-13 HEXAGON SAFETY & IN FRASTRUCTU RE Attachment 3.2 - Training Course Descriptions • •for Train -the -Trainer (Qty: 1) I/NetViewer and I/NetDispatcher training is presented directly to personnel responsible for training those personnel who will be accessing CAD information remotely. It familiarizes training personnel with the commands used in the I/NetViewer and/or I/NetDispatcher application during event entry and inquiry operations. Laboratory exercises are included with each module to provide additional experience in workstation operation. Upon completion of this course, attendees will be prepared to train I/CAD Users on the functions and use of the I/NetViewer and I/NetDispatcher products. MAJOR TOPICS • Event Entry Operations • Inquiry Commands • Unit or Crew Operations • Setting User Preferences Other Utilities Trainer Guidelines and Techniques PREREQUISITES Knowledge of appropriate Public Safety terminology Knowledge and familiarity with Windows user interface • Knowledge and familiarity with modern web browsers like Internet Explorer, Chrome, Firefox, or Safari TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience I/CAD Training Personnel Duration 2 Days Student Capacity 12 Students, with a maximum of 1 student per workstation A3.2-14 HEXAGON SAFETY & IN FRASTRUCTU RE Attachment 3.2 - Training Course Descriptions EdgeFrontier Developer Training Course (Qty: 1 This EdgeFrontier training course is designed for customers who have purchased an EdgeFrontier Developer license who have an interest in configuring their own EdgeFrontier Systems (interfaces). The Training class will be comprised of general EdgeFrontier training and API specific training. Students will receive both classroom training and hands-on experience enabling them to build and manage interfaces using EdgeFrontier and the CAD/RMS API. Upon successful completion, trainees will be able to take the core concepts/fundamentals and be able to configure simple -to -moderate interfaces in EdgeFrontier. With the foundational knowledge provided, trainees will be able to continue to use EdgeFrontier and build more complex interfaces over time, as that is the primary way to become a truly proficient user. Please note the stated prerequisites and student capacity, as strict adherence is essential to the successful completion of this course. MAJOR TOPICS General EdgeFrontier Knowledge • Developing and deploying EdgeFrontier Systems • Understanding the Data Structures • Business Rules Implementation • Linking Systems together via Publish/Subscribe and Receive/Inject • Generating / Consuming XML Advanced Knowledge Topics (topics will be customized to address customer interface needs) API Knowledge • Understanding the specific API functionality available • Using EdgeFrontier to communicate to the API • Subscribing to Topics • Subscribing to logs PREREQUISITES Trainees will need a laptop or computer with the .NET 4.0 Framework installed. In addition, strong adherence to the following prerequisites is mandatory: Responsibility for the administration, support, and maintenance of EdgeFrontier and the systems/interfaces built within the application. Technical understanding of databases, XML, XSLT, XSD, and network communications. Working knowledge of Windows. This includes major networking components, including clients, servers, local area networks, network ports, and protocols. TRAINING DETAILS Method Conducted on site by Hexagon Personnel A3.2-15 10, ,OA HEXAGON SAFETY& INFRASTRUCTURE Attachment 3.2 - Training Course Descriptions Target Audience EdgeFrontier User/Implementer Duration 5 days Student Capacity 4-8 A3.2-16 HEXAGON SAFETY & IN FRASTRUCTU RE Attachment 3.2 - Training Course Descriptions I/Sight Administration• (Qty: 3) am A The I/Sight Administration training course provides an overview of administration and maintenance tasks to individuals responsible for the technical administration, management, and/or support of the I/Sigh Video System. Students receive both classroom training and hands-on experience enabling them to perform the basic functions associated with the day-to-day operation and support of the I/Sight Video System. Please note the stated prerequisites and student capacity, as strict adherence is essential to the successful completion of this course. MAJOR TOPICS I/Sight Video System Overview • Location of key System Admin documentation • Local video system architecture • I/Sight Server Service and system parameters • Introduction to I/Security Administration Utility I/Sight Server Configuration Discovering Cameras • Setting Camera Visibility PREREQUISITES Strong adherence to the following prerequisites is mandatory: Responsibility for the administration, support, and maintenance of the I/CAD System Working knowledge of Windows. This includes major networking components, such as clients, servers, local area networks, network adapter cards, drivers, protocols, and network operating systems. Also requires comfort in the ability to use Windows Explorer to locate, create, and manipulate folders and files, create shortcuts, map network drives, and configure the desktop environment TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience System Administrator and Other Support personnel Duration 3 days each (total of 9 days) Student Capacity 12 A3.2-17 HEXAGON SAFETY & IN FRASTRUCTU RE Attachment 3.2 - Training Course Descriptions Mobile Responder for Trainers (Optional) (Qty: 2) Mobile Responder training is designed to train Agency trainers in the use of the Mobile Responder product. MAJOR TOPICS Using Mobile Responder on Smartphone or tablet Changing unit status Submitting inquiries Sending and receiving messages Updating unit properties Updating events I/Informer queries (if applicable) PREREQUISITE, • Responsibility for mobile computing operations Assignment of at least one person who has been through I/CAD Essentials training to perform necessary dispatching and other I/CAD functions • Availability of customer specific Mobile Responder configuration • Availability of test or training Mobile Responder smartphone or tablet for use in class TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience Designed for Mobile Responder Trainers Duration 2 days each (total of 4 days) Student Capacity 12 A3.2-18 HEXAGON SAFETY & INFRASTRUCTURE fi�RAPH ATTACHMENT 3.3 - LEE COUNTY MASTER SERVICE AGREEMENT Ll A3.3-1 HEXAGON SAFETY & INFRASTRUCTURE MASTER PRODUCT AND SERVICES AGREEMENT This Master Product and Services Agreement (the "Master Agreement"), entered into on this day of , 2017, is between Lee County, Florida ("Customer"), and Intergraph Corporation doing business as Hexagon Safety & Infrastructure ("Hexagon") (each a "Party" and collectively the "Parties"). Hexagon will make available to Customer certain proprietary software, including related proprietary documentation, software maintenance services, and professional services, all of which will be provided to Customer pursuant to the terms of this Master Agreement and an Order. Before Hexagon will provide any Software licenses or perform any Services, Customer must execute a corresponding Order. The Parties desire to enter this Master Agreement to govern each Order. The terms of Master Agreement consist of the following: • The General Terms and Conditions • Exhibit A — Services Terms and Conditions • Exhibit B - End User License Agreement • Exhibit C - Hexagon's U.S. Maintenance Terms and Conditions for Software • Exhibit D - Sample Project Deliverable Sign -Off Form Definitions. 1.1 "Affiliate" means, for business entities, the parent business entity of a Party and any business entities in which a Party or its parent company directly or indirectly holds a controlling ownership interest. 1.2 "Beta Software" means any version of Software prior to a generally available commercial release of such Software. 1.3 "Confidential Information" means any data or information, tangible or intangible, disclosed or made available by either party (the "Disclosing Party") to the other party (the "Receiving Party") in relation to this Master Agreement that is of value to the Disclosing Party and is not generally known in the industry or to competitors of the Disclosing Party and which shall include: 1.3.1 tangible information marked by the Disclosing Party with the word "Confidential" or otherwise identified by an appropriate stamp or legend indicating its confidential nature; 1.3.2 Confidential Information disclosed orally or visually and identified by the Disclosing Party as confidential when disclosed, and confirmed by the Disclosing Party in a written notice within thirty (30) days following disclosure, which notice shall include markings similar to those outlined above; and 1.3.3 all other information that, notwithstanding the absence of markings or designations, would be understood by the parties, exercising reasonable business judgment, to be confidential. 1.3.4 technical, financial and business information and models, information relevant to the current or proposed business plans of the Disclosing Party, reports, market projections, analyses, working papers, comparisons, studies, or other documents which contain such information; Hexagon Master Product and Services Agreement Page 1 1.3.5 information disclosed either directly, in oral or tangible form (including, but not limited to, magnetic or electronic form), or indirectly, by permitting the Receiving Party or its employees to observe various operations or processes conducted by the Disclosing Party; 1.3.6 information of the Disclosing Party's Affiliates, employees or agents; and 1.3.7 any material or documents prepared by the Receiving Party that is based on or contains any information disclosed by the Disclosing Party. 1.3.8 Confidential Information does not include information that: 1.3.8.1 is or becomes available in the public domain through no act of the Receiving Party; 1.3.8.2 has been received on a non -confidential basis from a third party without breach of this Master Agreement, where the Receiving Party has no reason to believe that such third party is bound by any confidentiality obligation to the Disclosing Party; 1.3.8.3 was already known by the Receiving Party without any obligation of confidence prior to receipt; 1.3.8.4 was developed independently by the Receiving Party without reliance on the disclosed Confidential Information, provided that such independent development can be substantiated; or 1.3.8.5 is confirmed by the Disclosing Party as not being confidential in writing. 1.6 "COTS" means commercial off the shelf Intellectual Property in the form generally released and distributed to Hexagon's customers and not including any functionality or features requiring source code changes. 1.7 "COTS Documentation" means commercial off the shelf documentation in the form generally released and distributed to Hexagon's customers and not including or requiring changes thereto. 1.8 "Customized Software" means those Services Deliverables that are software or computer code, whether in source code or object code. 1.9 "Deliverable(s)" means all Services Deliverables, software, hardware, and other items delivered or to be delivered by Hexagon to Customer and identified in the Order. 1.10 "Effective Date" means the date and time the last Party is given notice that the last Party has executed this Master Agreement. 1.11 "Fixed Price Project Assignment" means Hexagon will provide the Services and Software licenses for a fixed price. 1.12 "Hexagon IP" means Hexagon or Hexagon Affiliate developed, created, or prepared Intellectual Property. 1.13 "Installation Guide" means a computer file in a Microsoft Word or Adobe PDF document or a text file that contains information a User may need to install or operate a Software Product. 1.14 "Intellectual Property" means all forms of intellectual property including, but not limited to, patents, trademarks, copyrights, trade secrets, methodologies, logos, techniques, processes, know-how, formulae, algorithms, logic designs, screen displays, schematics, source and object code computer programs or software, documentation, mask work rights, design, ideas, product information, inventions and improvements thereto (whether or not patentable), and all works of authorship fixed in any medium of expression (including any form of online, digital, or electronic medium), whether or not copyrightable and whether registered or not. 1.15 "Maintenance Services" means only those services associated with the maintenance of the Software and other Deliverables licensed to Customer identified in the Order Documents for Maintenance Services. 1.16 "Order" means Order Documents that have been executed and/or accepted by both Parties documenting the purchase of any item or service and referencing the Master Agreement. Hexagon Master Product and Services Agreement Page 2 1.17 "Order Documents" shall mean written documents, the terms of which include Hexagon's commitment to provide products, licenses, and/or services at a specified price, subject to the terms and conditions of the Master Agreement. Order Documents may consist of a single document executed by the parties or a combination of documents that together form an Order. 1.18 "Purchase Order" or "PO" means a document issued by Customer to Hexagon to authorize the delivery of certain Services or Deliverables contemplated herein. 1.19 "Quote" means a document prepared by Hexagon reflecting prices for Services, Maintenance Services, and/or Deliverables. 1.20 "Services" means the work, services, projects, assignments, or tasks Hexagon shall perform pursuant to an Order. Services do not include Maintenance Services. 1.21 "Services Deliverable" means any data, document, information, Customized Software, Third Party Software, or material provided to Customer as a product of Hexagon's performance of Services pursuant to the Master Agreement. 1.22 "Software" means the software owned by Hexagon or an Affiliate and Third Party Software that is licensed to Customer. 1.23 "Software License Sale" means an Order that involves only the sale of Software licenses from Hexagon to Customer. This type of Order does not include Services. 1.24 "Software Product" means Hexagon IP delivered as proprietary object code or machine readable program identified in and to be provided by Hexagon to Customer pursuant to an Order placed under the terms of this Master Agreement. Software Product includes all of the following: (i) any associated Hexagon or Affiliate files, disk(s), CD-ROM(s) or other media with which the software is provided, (ii) any associated templates, data, printed materials, and "online" or electronic documentation, and (iii) any Updates or Upgrades of such Software Products provided pursuant to Maintenance Services). Software Product shall not mean any Third Party software, if any, that may be licensed to Customer under a separate license agreement. 1.25 "SOW' means a statement of work setting forth the scope of Services being provided pursuant to an Order. 1.26 "Subsystem" means a Software and hardware solution that is designed to provide a specific capability independent of the procurement of any other Subsystem. Hexagon's computer aided dispatch system ("CAD"), records management system ("RMS"), field based reporting ("FBR"), and mobile for public safety ("MPS") are each an example of a Subsystem. 1.27 "System" means a physical or operational location where the Software Product resides and operates on an individual server or where a single operational identification number ("Site ID") has been assigned by Hexagon. 1.28 "Term" means the duration of performance under this Master Agreement. 1.29 "Time and Materials Project Assignment" means Hexagon will perform the Services set forth in an Order on an hourly basis until the project is either completed or the authorized hours are exhausted, whichever comes first. 1.30 "Third Party Software" means computer software or other technology in which any person or entity, other than Hexagon or Hexagon's Affiliate, has any right, title or interest, including any restrictions or obligations (such as obligations to obtain consents or approvals and restrictions that may be eliminated only by obtaining such consents or approvals) applicable to the computer software or technology, but does not include software embedded in the Software Products by license from third parties. The use of Third Party Software is subject to all of the terms and conditions of the third party's software license or similar agreement ("SLA") provided with the Third Party Software. 1.31 "Update" means any modified version, fix, or patch of the Software Product provided by Hexagon. Hexagon Master Product and Services Agreement Page 3 1.32 "Upgrade" means each new release of the Software Product that is a result of an architectural, major, or minor change to the Software Product provided by Hexagon. 1.33 "User" means Customer or an individual employed by Customer. A User may also include Customer's contractor who requires temporary use of the Software Product to provide services on Customer's behalf. 2 Elements of an Order. 2.1 Order Composition. 2.1.1 Each Order will be comprised of Order Documents. 2.1.2 From time to time, Customer may request from Hexagon or Hexagon may provide Customer a draft Quote and/or SOW for Deliverables. Once the Parties mutually agree upon the contents of the Order Documents, as applicable, the Parties shall execute the Order Documents 2.1.3 Upon mutual execution or acceptance of the Order Documents, Customer will issue a PO or a notice to commence work, unless otherwise specified in the Order Documents. Except as set forth in the Order Documents, Hexagon shall not commence work on the Order until it receives from Customer a PO or notice to commence work. 2.1.4 Notwithstanding the forgoing, Orders for Maintenance Services shall commence on the date specified in the Order Documents regardless of whether Customer has issued a PO or notice to commence work. 2.2 Pricing. The following minimum elements shall be included with the Order Documents associated with the following types of Orders: 2.2.1 For a Software License Sale, a Quote identifying the Software licenses being procured and the total price for the Software License Sale. 2.2.2 For Time and Materials Project Assignments, a Quote setting forth the number of hours allocated for each grade of Hexagon resource to be utilized on the assignment and the hourly rate for each grade of Hexagon. 2.2.3 For Fixed Price Project Assignments, a Quote and SOW shall set forth the price of the work to be performed for and the Deliverables provided for that Order. 2.2.4 For Orders for Maintenance Services, a Quote identify the Software to be maintained and the total price for the associated Maintenance Services. 2.3 Change Control. During the course of Hexagon's performance under the SOW, either Party may request a change in the scope of the SOW in writing, delivered to the other Party's project manager. Any changes in price, schedule, or other terms must be documented either by an amendment, change order, or a replacement of the SOW in question. No change, as contemplated in this paragraph, shall become effective until agreed to by both Parties in a mutually -executed writing. 2.4 Acceptance. Acceptance will occur based upon the following: 2.4.1 For Fixed Price Project Assignments, when the Deliverables in an SOW meets the acceptance criteria described in each task or milestones in the SOW. Once Hexagon believes a corresponding milestone or task has been successfully completed according to the provisions of the applicable SOW, Hexagon shall submit for execution by Customer's project manager a Project Deliverable Sign -off form in substantial conformity with Exhibit D. Within ten (10) calendar days of receipt of the applicable Project Deliverable Sign -off Form for the completed milestone, Customer's project manager will either: (i) execute the Hexagon Master Product and Services Agreement Page 4 Project Deliverable Sign -off Form provided by Hexagon, or (ii) provide a written description of all deficiencies to Hexagon. If Customer fails to perform either action identified in the preceding sentence within ten (10) calendar days, or if the Deliverable, including the Software contained in the Fixed Price Project Assignment Order, is placed into production or utilized in a live environment, then the task or milestone shall be deemed accepted. 2.4.2 For Time and Materials Project Assignments and Maintenance Services, the Services are accepted as performed. 2.4.3 For a Software License Sale, once the Software has been shipped. 3 Composition of the Master Agreement. 3.1 Components. The agreement between the Parties consists of: (1) the Master Agreement (including the General Terms and Conditions and all Exhibits), (2) any amendments to the Master Agreement, and (3) Orders, together with any change orders, that may be delivered, prepared, or issued after the Effective Date. 3.2 Order of Precedence. In the event of any conflict or inconsistency among documents related to this Master Agreement, the following order of precedence shall be used to determine the resolution of the discrepancy, unless both parties mutually agree in writing to an alternative decision. The order of precedence for these documents shall be as follows: (1) Any amendments to this Master Agreement (2) The Master Agreement (excluding exhibits) (3) Exhibits to the Master Agreement; and (4) Orders, as amended or modified by a change order; 4 Invoicing and Payment. 4.1 Invoices. Invoices shall be issued based upon the following: 4.1.1 For Software License Sales, Hexagon shall invoice Customer for the amount set forth in the Quote upon shipment of the Software identified in the Order Documents. 4.1.2 Orders for Fixed Price Project Assignments and Time and Materials Project Assignments shall be billed and invoiced in accordance with Exhibit A. 4.1.3 Orders for Maintenance Services shall be billed and invoiced in accordance with Exhibit C. 4.2 Payment. Customer shall make payment for any invoices issued by Hexagon within thirty (30) calendar days of the date the invoice was issued. 4.3 Late Payment. If Customer does not make timely payment, an interest charge of two percent (2%) per month (or the maximum allowed by law, whichever is less), which shall be compounded on a monthly basis, will be due on any unpaid and overdue amounts. 4.4 Taxes. The purchase price is exclusive of all Federal, State, or Local taxes. Any taxes applied to this sale by a Federal, State, or Local taxing authority will be the responsibility of Customer. Such taxes do not include franchise taxes or taxes based on net income. If Customer is claiming a tax-exempt status, it must submit the proper documentation satisfactory to Hexagon evidencing its tax exempt status. Applicable taxes may be invoiced at any time such taxes become fixed and certain. Hexagon Master Product and Services Agreement Page 5 5 Term and Termination. 5.1 Term. The Term of this Master Agreement shall begin on the Effective Date and remain in effect for a period of sixty (60) consecutive months or until the Master Agreement is earlier terminated pursuant to the terms set forth herein or by mutual agreement of the Parties. An Order that is executed prior to the expiration of the term of this Master Agreement shall be governed by this Master Agreement even if the Master Agreement Term expires during the performance of the Order. 5.2 Termination for Convenience. Except for Orders for Maintenance Services, either Party may terminate this Master Agreement or an Order in its sole discretion at any time upon providing the other Party with thirty (30) days written notice. The coverage period applicable to Orders for Maintenance Services shall be governed by Exhibit C and shall survive termination of this Master Agreement if the Master Agreement is terminated for convenience. In the event of a termination pursuant to this paragraph, Customer agrees to pay Hexagon for the pro rata percentage of work performed based upon the schedule of payments set forth in the SOW, plus the cost of any labor, equipment, or materials ordered in good faith prior to notice of termination that could not be canceled. To the extent a Party exercises its right to terminate a specific Order, that termination shall have no effect upon the remaining Master Agreement, which, along with any other active Orders, shall remain in full force and effect. If a Party desires to terminate the Master Agreement, then the Parties shall proceed to wind down all ongoing work under the respective Orders in effect under this Master Agreement by the termination date. Each Party shall take commercially reasonable steps to bring the work to a close and to reduce its costs and expenditures. 5.3 Termination for Cause. Either Party may terminate this Master Agreement or a specific Order, as the case may be, in the event that other Party materially breaches a material term of this Master Agreement or any Order. 5.3.1 In the event a Party has materially breached an Order, the non -breaching Party may terminate the Order only after providing a sixty (60) calendar day cure period to cure such breach and the breach has not been cured, except for material breaches arising from non-payment. During the sixty (60) day cure period, the Parties shall try to determine a mutually agreeable plan to cure such breach. If such breach cannot be cured or an acceptable plan is not provided within the sixty (60) day cure period, the non -breaching Party may, but does not have the obligation to, terminate the Order. 5.3.2 In the event a Party has materially breached the Master Agreement or multiple Orders, the non -breaching Party may terminate the Master Agreement only after providing a sixty (60) calendar day cure period to cure such breach and the breach has not been cured except for material breaches arising from non-payment. During the sixty (60) day cure period, the Parties shall try to determine a mutually agreeable plan to cure such breach. If such breach cannot be cured or an acceptable plan is not provided within the sixty (60) day cure period, the non -breaching Party may, but does not have the obligation to, terminate the Master Agreement. If the Master Agreement is terminated pursuant to this paragraph, by the termination date, Hexagon will stop all work pursuant to any Orders arising under this Master Agreement. In the event the Master Agreement is terminated for cause, Hexagon shall be entitled to, and Customer agrees to pay Hexagon, payment for Deliverables and Services rendered on all ongoing Orders up to the termination date, including, but not limited to, a pro rats percentage of work performed based upon the schedule of payments set forth in each SOW. 5.3.3 Notwithstanding the foregoing, Hexagon may suspend its performance of or terminate any Order or the Master Agreement for cause if payment is not received within thirty (30) following the date when payment was due. In the event an Order is suspended Hexagon Master Product and Services Agreement Page 6 or terminated for cause, Hexagon shall be entitled to, and Customer agrees to pay Hexagon, payment for Deliverables and Services rendered on said Order up to the suspension or termination date, including, but not limited to, a pro rats percentage of work performed based upon the schedule of payments set forth in each SOW. If Hexagon suspends an Order under this paragraph, then it may thereafter terminate the Order upon giving written notice to the Customer. 5.3.4 Notwithstanding the foregoing, Customer may not exercise a termination pursuant to the terms of Section 5.3 if Hexagon's material breach of the terms and conditions of the Master Agreement or any Order thereunder is caused or partially caused by Customer's negligence or failure to perform its obligations. 6 IP Ownership. Customer acknowledges Hexagon will retain ownership and title of Intellectual Property made at any time while performing any Order. All Hexagon Software provided under this Master Agreement is licensed to Customer in accordance with Exhibit B (End User License Agreement) except as it is inconsistent with the terms set forth herein. Third Party Software is licensed to Customer pursuant to the software license agreement delivered with such Third Party Software product. 7 Warranties. 7.1 Software. The Software provided under the Orders is warranted to substantially conform to the user documentation, free from defects in material and workmanship for a period of thirty (30) days from initial installation. This warranty only applies to Software products that are not already covered by a Maintenance Agreement between Customer and Hexagon. 7.2 Subsystem Warranty Coverage. For, and only for, new Subsystems procured/implemented pursuant to an Order under this Master Agreement, the warranty coverage shall be set forth in the applicable SOW, which shall be in addition to the warranty coverage set forth in Section 7.1. 7.3 Third -party Warranty Coverage. To the extent third -party products are supplied by Hexagon, those products are provided with a pass-thru-warranty from the original manufacturer, if any. 7.4 Disclaimer. Any product information Hexagon has shared with Customer during the proposal and/or contract activities to date was to provide an understanding of Hexagon's current expected direction, roadmap, or vision and is subject to change at any time at Hexagon's sole discretion. Hexagon specifically disclaims all representations and warranties regarding future features or functionality to be provided in any Software or Deliverable. Hexagon does not commit to develop the future features, functions, and/or products discussed in this material beyond that which is specifically committed to be provided by Hexagon pursuant to a valid Order. Customer should not factor any future features, functions, or products into its current decisions since there is no assurance that such future features, functions, or products will be developed. When and if future features, functions, or products are developed, they will be made generally available for licensing by Hexagon. 7.5 Warranty Disclaimer. EXCEPT AS SPECIFICALLY SET FORTH IN THIS ARTICLE 7, HEXAGON DISCLAIMS (TO THE FULLEST EXTENT PERMITTED BY LAW) ALL WARRANTIES ON PRODUCTS FURNISHED PURSUANT TO THIS MASTER AGREEMENT, INCLUDING ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE WARRANTIES SET FORTH IN THIS ARTICLE 7 IS IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED, AND, EXCEPT AS SET FORTH IN ARTICLE Hexagon Master Product and Services Agreement Page 7 ENTITLED "INDEMNIFICATION PROVISIONS" BELOW, REPRESENTS THE FULL AND TOTAL WARRANTY OBLIGATION AND/OR LIABILITY OF HEXAGON. 8 LIMITATION OF LIABILITY IN NO EVENT WILL HEXAGON BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR SPECIAL DAMAGES, LOST PROFITS, LOSS OF USE OR PRODUCTION, LOSS OF REVENUE, LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF HEXAGON HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. UNDER NO CIRCUMSTANCE WILL HEXAGON'S LIABILITY UNDER THIS AGREEMENT EXCEED THE AMOUNT THAT HEXAGON HAS BEEN PAID BY CUSTOMER UNDER THE INDIVIDUAL ORDER UNDER WHICH THE EVENT GIVING RISE TO THE CAUSE OF ACTION HAS OCCURRED. 9 Indemnification Provisions. 9.1 Subject to the limitation of liability provisions in this Master Agreement, Hexagon will defend, at its expense, a third party action, suit, or proceeding against Customer ("Claim"), and indemnify Customer from any judgments, settlements, and reasonable attorney's fees resulting therefrom, to the extent such Claim is (i) attributable to bodily injury, death, or physical damage to tangible property caused by Hexagon's negligent acts or omissions arising under this Master Agreement; or (ii) based upon an allegation that a Software Product, Customized Software, or Services Deliverable as of its delivery date under this Master Agreement, infringes a valid United States patent, copyright, or trademark, or misappropriates a third party's trade secret ("Infringement Claim"). 9.2 Hexagon's defense and indemnification obligations are conditioned upon: 9.2.1 Customer providing prompt written notice to Hexagon in writing of any Claim; 9.2.2 Hexagon having sole control of the defense of any actions and negotiations related to the defense or settlement of any Claim; and 9.2.3 Customer cooperating fully in the defense or settlement of any Claim. 9.3 Hexagon will have no obligation to defend Customer or to pay any resulting costs, damages, or attorneys' fees for any Infringement Claims alleging direct or contributory infringement of the Software Product (i) by the combination of or integration with a product, process, or system not supplied by Hexagon; (ii) by material alteration by anyone other than Hexagon or its subcontractors; (iii) by use after Customer has been notified of possible infringement; (iv) use after modifications are provided to Customer; (v) use after a return for refund as described below is ordered by Hexagon; (vi) the creation of which was pursuant to specifications provided by Customer; or (vii) use other than as specified in the documentation associated with the Software Product. 9.4 In connection with any Infringement Claims, Hexagon, at its own expense and option, may either (i) obtain rights for Customer to continue using Software Product; (ii) replace the Software with a non -infringing alternative, or modify the allegedly infringing elements of Software Product, while maintaining substantially similar software functionality or data/informational content; or (iii) refund to Customer a prorated portion of the license fees paid by Customer for the infringing item(s), based on a five (5)-year, straight-line depreciation basis beginning from the initial date of delivery, in which case Customer will uninstall, cease all use of and return to Hexagon the infringing item(s). 9.5 In no event will the indemnification for Infringement Claims apply to any Beta Software or sample, hot fix, royalty -free, or evaluation software delivered pursuant to the Master Agreement. Hexagon Master Product and Services Agreement Page 8 9.6 Hexagon is not required to indemnify or defend Customer against Claims brought by any Customer affiliate. 9.7 This Article 9 provides the sole and exclusive remedies of Customer and Hexagon's entire liability in the event of a Claim. Customer has no right to recover and Hexagon has no obligation to provide any other or further remedies, whether under another provision of the Master Agreement or any other legal theory or principle in connection with a Claim. 10 Insurance. 10.1 Policies and Coverage Amounts. Hexagon agrees to procure and maintain in force during the term of this Master Agreement, at its own cost, the following policies and amounts of coverage: 10.1.1 Workers' Compensation Insurance as required state statute or regulation 10.1.2 Commercial General Liability Insurance with minimum combined single limits of ONE MILLION DOLLARS ($1,000,000) each occurrence and ONE MILLION DOLLARS ($1,000,000) general aggregate. The policy shall be applicable to all premises and operations. The policy shall include coverage for bodily injury, broad form property damage, and personal injury. 10.1.3 Automobile Liability Insurance with minimum combined single limits for bodily injury and property damage of not less than ONE MILLION DOLLARS ($1,000,000) for any one occurrence, with respect to each of Hexagon's owned, hired or non -owned vehicles assigned to or used in performance of the services or work under this Master Agreement. 10.1.4 Umbrella/Excess Coverage with minimum combined single limits of ONE MILLION DOLLARS ($1,000,000) per occurrence. 10.2 Policy Maintenance. Hexagon shall procure and maintain, and shall cause any subcontractor of Hexagon to procure and maintain, the minimum insurance coverages listed herein. All policies shall be continuously maintained for the term of this Master Agreement. 10.3 Certificate of Insurance. A Certificate of Insurance shall be completed by Hexagon's insurance agent(s) as evidence that policies providing the required coverage amounts, conditions, and minimum limits are in full force. The completed Certificate of Insurance shall be sent to the contact person identified in the notices provision below. 10.4 Insurance Deductible. Hexagon shall be solely responsible for any deductible losses under the policies required above. 11 Dispute Resolution. 11.1 Resolution Protocol. The Parties shall exercise their best efforts to negotiate and settle promptly any dispute that may arise with respect to this Master Agreement or Order made pursuant to this Master Agreement ("Dispute") in accordance with the provisions set forth herein. If either party disputes any provision of this Master Agreement (the "Disputing Party"), or the interpretation thereof, or any conduct by the other party under this Master Agreement, that Party shall bring the matter to the attention of the other party at the earliest possible time in order to resolve the Dispute except for Disputes for non-payment. If such dispute is not resolved by the employees responsible for the subject matter of the dispute within ten (10) business days, the Disputing Party shall be permitted to deliver to the first level of representatives below a written statement ("Dispute Notice") describing the dispute in detail, including any time commitment and any fees or other costs involved. A copy of the Dispute Notice shall also be directed to the non - Disputing Party contact person identified in the section entitled "Notices" below. Receipt by the first level of representatives of a Dispute Notice shall commence the dispute resolution process Hexagon Master Product and Services Agreement Page 9 and a time period within which the respective representatives must exercise their best effort to resolve the dispute. If the respective representatives do not resolve the dispute within the given time period, the dispute shall be escalated to the next higher level of representatives in the sequence as set forth below. Escalation Timetable Calendar Days 0 to 7th 8th to 14th 15th to 21 st Hexagon Representative Project Manager Vice President for Project Operations Vice President and General Manager for Public Safety Client Representative Project Manager 11.2 Mediation. To the extent a dispute is not resolved through the process outlined in the previous section and remains unresolved, the Parties agree to enter into non -binding mediation to resolve the dispute. Within sixty (60) calendar days, of the issuance of the Dispute Notice, or such longer period that is mutually agreeable to the parties, the Parties agree to identify a mutually acceptable mediator who shall mediate the dispute. If after making reasonable efforts to identify a mutually acceptable mediator and no later than fifty (50) calendar days after the issuance of the Dispute Notice, the Parties are unable to identify such a mediator, the Disputing Party shall provide the non -disputing party with a list of five (5) proposed mediators. The non -disputing shall have five (5) business days from receipt of such list from the Disputing Party to identify one proposed mediator on the list to use as a mediator. If the non -disputing party fails to identify and communicate its choice to the Disputing Party in the time allotted, then the Disputing Party shall be permitted to unilaterally identify the mediator from the list of five (5) mediators previously given who shall mediate the Dispute. The mediator shall be an attorney licensed to practice law in the state courts identified in section below entitled "Governing Law". Subject to the mediator's availability, the Parties agree to mediate the dispute within thirty (30) days after the Parties have identified a mediator who has agreed to mediate the dispute. To the extent the mutually identified mediator is unavailable, unwilling, or unable to mediate the Dispute, the Parties shall utilize the same steps listed above to identify a new mutually agreeable mediator. To the extent the Disputing Party had to prepare a list of proposed mediators previously, it shall prepare and transmit a revised list within five (5) business days of receiving notice of the proposed mediator's unavailability. Subject to the mediator's requirements, the Parties agree they shall be permitted to attend the mediation via telephone or video conferencing. The Parties agree to pay in equal shares the mediator's fee and expenses unless otherwise agreed to pursuant to a settlement agreement. 11.3 Prerequisites to Litigation. Except for disputes for non-payment, only after the Parties have endeavored to resolve the dispute through the processes outlined in the immediately preceding two sections may a Party commence litigation to resolve the dispute. 11.4 Injunctive Relief. Notwithstanding the foregoing, either party may, before or during the exercise of the informal dispute resolution procedures set forth above, apply to a court identified in the section entitled "Forum" for a temporary restraining order or preliminary injunction where such relief is necessary to protect its interests pending completion of such informal dispute resolution procedures. Hexagon Master Product and Services Agreement Page 10 12 Notices. All notices given between the Parties shall be in writing and shall be considered properly sent by postage prepaid United States Mail or overnight carrier to the persons identified below, or such substitutes as may hereafter be disclosed by proper notification: <Insert Name> <Insert Title> Lee County, Florida <Insert Address 1> <Insert Address 2> <Insert Address 3> Tel. No. <Insert> Email: <Insert> 13 Force Majeure. Victor S. Vasile Divisional Counsel Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 305 Intergraph Way Madison, Alabama 35758 Tel. No. (256) 730-1516 Email: victor.vasile@hexagonsi.com Neither party shall be deemed to be in default of any provision of this Master Agreement or an Order or be liable for any delay, failure in performance, or interruption of service resulting from acts of war, acts of terrorism, acts of God, acts of civil or military authority, labor disruption, civil disturbance, or any other cause beyond its reasonable control. 14 Place of Performance. To the extent necessary, Customer agrees to provide appropriate work space and work place accommodations; computer equipment; software; access to relevant data, documents, plans, reports, and analyses; and necessary access to Hexagon personnel to perform work on an Order. To the extent work is performed remotely, Customer must provide VPN or secured remote connectivity (including a log -on and password) to all servers and workstations requiring installation/configuration by Hexagon. 15 Amendments. Any and all amendments to this Master Agreement shall specifically reference the fact the amendment is intended to alter the terms and conditions set forth herein. No Order or change order to an SOW shall affect the terms and conditions set forth herein. 16 Confidential Information. The Parties agree not to disclose Confidential Information provided to it by the disclosing party to the maximum extent allowable under applicable law unless if first obtains the disclosing party's written consent to such disclosure. It is further understood and agreed that money damages may not be a sufficient remedy for any breach of this provision of the Master Agreement by the non - disclosing party and the disclosing party may be entitled to seek equitable relief, including injunction and specific performance, as a remedy for any such breach. Such remedies shall not be deemed to be the exclusive remedies for a breach of this provision of the Master Agreement but will be in addition to all other remedies available at law or equity. The covenants set forth herein and the rights and obligations related thereto shall continue for a period of five (5) years from the date of disclosure. 17 Assignment. Neither party shall assign, sublet, or transfer all or any portion of the Master Agreement, nor any interest in the Master Agreement, without the express written consent of the non -assigning party, which consent may be granted or withheld in the sole discretion of the non -assigning party. Hexagon Master Product and Services Agreement Page 11 Notwithstanding the foregoing, Hexagon may assign its rights and obligations under the Master Agreement, without the approval of Customer to: (1) an Affiliate or (2) another business entity in connection with a merger, consolidation, or reorganization of Hexagon or any of its subsidiaries. 18 Export. Hexagon IP, including any technical data related to Software or Services, is subject to the export control laws and regulations of the United States. Diversion contrary to United States law is prohibited. Hexagon IP, including any technical data related to Software or Services, shall not be exported or re-exported, directly or indirectly (including via remote access), under the following circumstances: • To Cuba, Iran, North Korea, Sudan, or Syria, or any national of these countries. • To any person or entity listed on any United States government denial list, including, but not limited to, the United States Department of Commerce Denied Persons, Entities, and Unverified Lists, the United States Department of Treasury Specially Designated Nationals List, and the United States Department of State Debarred List (http://export.gov/ecr/eg_main_023148.asp). • To any entity if Customer knows, or has reason to know, the end use is related to the design, development, production, or use of missiles, chemical, biological, or nuclear weapons, or other unsafeguarded or sensitive nuclear uses. • To any entity if Customer knows, or has reason to know, that a reshipment contrary to United States law or regulation will take place. Customer agrees to hold harmless and indemnify Hexagon and its Affiliates for any causes of actions, claims, costs, expenses and/or damages resulting to Hexagon from a breach of the export restrictions set forth in this Master Agreement by Customer or any User. Any questions regarding export or re-export of the Software should be addressed to Hexagon's Export Compliance Department at 305 Intergraph Way, Madison, Alabama, 35758, USA or at exportcompliance@intergraph.com. 19 Non Solicitation of Employees. Customer agrees that it will not, without the prior written consent of Hexagon, solicit any Hexagon employee, or induce such employee to leave Hexagon's employment, directly or indirectly, during the term of this Master Agreement and for a period of twelve (12) months after the Master Agreement expires or is terminated. Customer agrees that a breach of this provision would cause actual and substantial damages to Hexagon such that it would be difficult or impossible to calculate actual damages. Accordingly, any such breach will entitle Hexagon to recover liquidated damages from Customer in the amount equal to one (1) year of the affected employee's annual salary plus benefits for each such breach, as well as expenses, costs, and reasonable attorneys' fees incurred by Hexagon in seeking enforcement of this provision. Customer agrees that the foregoing amount is intended to be, and in fact is, a reasonable estimate of the actual damages that would be incurred by Hexagon if Customer were to breach this provision, and that this amount is not intended to be, and in fact is not, a penalty. In addition, Hexagon shall be entitled to equitable or injunctive relief to prevent further breaches. For purposes of this section, the term "employee" means employees of Hexagon and/or any Affiliate and/or any of Hexagon's subcontractors who directly support Customer. 20 Miscellaneous. 20.1 Authority. Each Party represents and certifies to the other Party it has the requisite legal authority to enter into and be bound by this Master Agreement and all Orders arising from this Master Agreement. Hexagon Master Product and Services Agreement Page 12 20.2 Survival. The rights and obligations in sections entitled "IP Ownership", "Limitation of Liability", "Dispute Resolution", "Confidential Information", "Export", and the terms of any license granted pursuant to this Master Agreement (including, but not limited to, Exhibit B), shall survive and continue after expiration or termination of the Master Agreement, shall remain in effect until fulfilled, and shall apply to any permitted successors and assigns. Upon termination of the Master Agreement, the provisions of the Master Agreement, including those in the preceding sentence, which by their express terms survive termination, shall remain in full force and effect. 20.3 Waiver. The waiver by either Party of any of its rights or remedies in enforcing any action or breach under this Master Agreement in a particular instance shall not be considered as a waiver of the same or different rights, remedies, or actions for breach in subsequent instances. 20.4 Severability. If any provision of this Master Agreement or an Order is void, voidable, unenforceable, or illegal in its terms, but would not be so if it were rewritten to eliminate such terms that were found to be voidable, unenforceable, or illegal and such rewrite would not affect the intent of the provision, then the provision must be rewritten to be enforceable and legal. 20.5 Counterparts. This Master Agreement may be executed in multiple counterparts, each of which shall be deemed to be original, and all of which together shall constitute one and the same document. A signature delivered by facsimile or via an email containing a scanned, executed Master Agreement shall be deemed to be an original signature and shall be effective upon receipt thereof by the other party. 20.6 Headings. Numbered topical headings, articles, paragraphs, subparagraphs or titles in this Master Agreement are inserted for the convenience of organization and reference and are not intended to affect the interpretation or construction of the terms thereof. 20.7 Governing Law. All legal or equitable disputes between the Parties which may arise from this Master Agreement, including all Orders, shall be subject only to the laws of the State of Florida. All disputes shall be brought either in the appropriate state court or the United States District Court for the Middle District of Florida and the appellate courts to which appeals can be taken from those courts. All parties consent to the exercise by such courts of personal jurisdiction over them and each party waives any objection it might otherwise have to venue, personal jurisdiction, inconvenience of forum, and any similar or related doctrine. The United Nations Conventions on Contracts for the International Sale of Goods shall not apply to this Master Agreement, and the Parties expressly agree not to be governed by the Uniform Computer Information Transactions Act or similar laws. 20.8 Independent Contractor. The Parties agree that Hexagon is an independent contractor, that nothing in this Master Agreement shall be construed as establishing or implying a relationship of master and servant between the Parties, or any joint venture or partnership between the Parties, and that nothing in this Master Agreement shall be deemed to constitute either of the Parties as the agent of the other Party or authorize either Party to incur any expenses on behalf of the other Party or to commit the other Party in any way whatsoever. Hexagon and its agents, employees, or subcontractors shall at no time be deemed to be agents, employees, or subcontractors of Customer, or be deemed to be under the control or supervision of Customer when carrying out the performance of its obligations in this Master Agreement. Without the prior written consent of Customer, Hexagon shall not carry on any activity that could be construed as being on behalf of Customer. 20.9 Limitation on Claims. No claim, regardless of form, arising out of or in connection with this Master Agreement may be brought by Customer more than two (2) years after the event giving rise to the cause of action has occurred. Hexagon Master Product and Services Agreement Page 13 21 Entire Agreement. This Master Agreement constitutes the entire agreement between the Parties with regard to the subject matter hereof. This Master Agreement supersedes any and all prior discussions and/or representations, whether written or oral, and no reference to prior dealings may be used to in any way modify the expressed understandings of this Master Agreement. Any future representations, promises and verbal agreements related to the products, product features, future product enhancements, product functionality, or services covered by this Master Agreement will be of no force or effect unless reduced in writing and made a part of this Master Agreement. This Master Agreement may not be amended or modified unless so done in writing signed by authorized representatives of both Parties. The pre-printed terms and conditions of Customer's PO or any other terms and conditions of a Customer PO that may conflict in any way with the terms and conditions of this Master Agreement shall be void, even if issued subsequent to the effective date of this Master Agreement, and shall not be deemed to constitute a change to this Master Agreement. SIGNATURE PAGE FOLLOWS Hexagon Master Product and Services Agreement Page 14 In consideration of the mutual obligations assumed under this Master Agreement, Customer and Hexagon agree to the terms and conditions set forth herein and attached to this Master Agreement as Exhibits and represent that this Master Agreement has been executed by each Party's duly authorized representative. The signatories represent that they have the authority to bind their respective organizations to this Master Agreement. This Master Agreement may be executed in counterparts or in duplicate originals. Each counterpart or each duplicate shall be deemed an original copy of this Master Agreement signed by each Party for all purposes. AGREED BY: LEE COUNTY, FLORIDA By: Name Title: Date: INTERGRAPH CORPORATION By: Name JENNIFER WILLIAMS Title: DIRECTOR Date: ��:1�:7�►�I_11►1�]�:Z�7��.1[•y�_�el�[•y���r:3�_\►1:�1►���►��[�7►1_\�A'1 Hexagon Master Product and Services Agreement Page 15 HEXAGON SAFETY & INFRASTRUCTURE Exhibit A — Services Terms and Conditions The additional terms and conditions set forth in this this Exhibit constitute the terms and conditions governing the delivery of Hexagon Services to Customer as described in individual Order Documents. Scope of Services. 1.1 Hexagon will provide Services to Customer as stated on the Order Documents. Services as specified will be performed during a standard workweek, based on an eight (8) hour day. 1.2 For Fixed Price Project Assignments, the Services Deliverables will be stated in the Order Documents. 1.3 For Time and Materials Project Assignments, Services will be provided up to the maximum amount of time as stated in the Order Documents. Hexagon shall have no obligation to work beyond the number of hours authorized by Customer. Hexagon cannot commit to firm Services Deliverables, guaranteed results, or a fixed schedule of performance on a time and material Services engagement. Hexagon will apply diligent effort to the stated purpose of the applicable SOW, however, should the Services require more time than estimated, Hexagon will obtain either a change order or new Order or SOW prior to performing additional Services. Except as otherwise stated in an Order, Time and Materials Project Assignment Orders will expire after a duration of six (6) months. 2 Invoicing for Services. 2.1 For time and materials Services, Hexagon will invoice Customer for all hours expended and travel expenses incurred on a monthly basis, or after all purchased hours have been expended, whichever occurs first. Customer agrees to reimburse Hexagon for all travel and travel -related expenses at Hexagon's cost plus a five percent (5%) administrative fee. 2.2 For firm fixed price Services, Hexagon will invoice Customer upon acceptance of a Deliverable (as set out in Section 2.4 ("Acceptance") of the General Terms and Conditions) or in accordance with any billing milestones specified in the Order or SOW. Any necessary travel and travel -related expenses will be included in the firm fixed price. 3 License to Use Services Deliverables. Hexagon grants to Customer a personal, nontransferable, nonexclusive license to use for Customer's internal purposes those Services Deliverables that are not software. Customized Software is licensed for use by Customer pursuant to Exhibit B (Hexagon's End User Software License Agreement). Customer agrees to execute any applicable third party end user license agreement for Third Party Software that is delivered to Customer without an included third party end user license agreement. 4 Intellectual Property Ownership. All Hexagon Services Deliverables and all products of Hexagon Services are Hexagon IP. Any Intellectual Property created by Hexagon during the course of the Services shall be the sole and exclusive property of Hexagon. Customized Software and any Third Party Software furnished to Customer by Hexagon hereunder shall remain the property of Hexagon or the respective third party. All Hexagon IP is Confidential Information and proprietary to Hexagon. Customer shall Hexagon Master Product and Services Agreement Page 16 maintain the confidentiality of all Services Deliverables as it would confidential information/data of its own and shall not disclose same to any third party without the prior written consent of an authorized Hexagon contracts representative. The Services and Services Deliverables provided to Customer pursuant to the Master Agreement are not "work for hire." Except as expressly provided elsewhere in this Exhibit, no direct or indirect ownership interest, license right, or usage right in the Services or Services Deliverables are granted or created by implication. Hexagon may perform the same or similar services for other customers. 5 Maintenance. Customer shall be responsible for the maintaining any Services Deliverables provided. In the event Customer elects to have Hexagon perform such maintenance, such maintenance may be provided pursuant to an additional Order or SOW. 6 Customer Obligations. If any work needs to be performed at Customer's location, Customer agrees to provide, at its own expense, building access (including weekend and after-hours access), appropriate work space accommodations (including access to meeting room facilities), and the use of any machines, documentation, or software which Hexagon deems necessary to perform the Services. Additionally, Customer will review and provide timely feedback to Hexagon on all Deliverables and provide qualified technical personnel to support Hexagon as needed during performance of the Services. Customer is solely responsible for ensuring it systems, software, and data are adequately backed up. Hexagon will not be responsible for lost Customer data. 7 Acceptance and Disclaimer of Warranties. Acceptance for Services Deliverables is set forth in Section 2.4 ("Acceptance") of the General Terms and Conditions. Otherwise, all Services and Services Deliverables are provided "AS IS" and without warranty of any kind. Hexagon does not warrant the type, quality, or results of any Services or Services Deliverable provided. HEXAGON DISCLAIMS (TO THE EXTENT PERMITTED BY APPLICABLE LAW) ALL WARRANTIES ON SERVICES AND DELIVERABLES FURNISHED HEREUNDER, INCLUDING ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE WARRANTY HEREIN IS IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED, AND REPRESENTS THE FULL AND TOTAL OBLIGATION AND/OR LIABILITY OF HEXAGON. 8 Use of Contractors. Hexagon may utilize contractors to perform the Services set forth in any Order or SOW. Hexagon shall be responsible to Customer for the performance by any such Hexagon contractors as if the Services were performed by Hexagon itself. I21041oxelN:*7MMIIAIr_1 Hexagon Master Product and Services Agreement Page 17 HEXAGON SAFETY & INFRASTRUCTURE Exhibit B - END -USER LICENSE AGREEMENT The additional terms and conditions set forth in this End User License Agreement ("EULA") and the General Terms and Conditions shall govern the Software Products provided by Hexagon to Customer as described in Order Documents. If Customer does not agree to the terms of this EULA, Customer is not authorized to, and Customer shall not, download, install, or use a Software Product. Customer agrees to timely pay all charges due and payable for Customer's use of any Software Product. 1.1 "Core" means a physical processor on a computer server that can respond to and execute the basic instructions that drive the computer. A Central Processing Unit ("CPU") may have one or more Cores, and a given server may have multiple CPU sockets that may each contain multiple Cores. 1.2 "Desktop -based Software Product" means a self-contained application that runs from a local drive and does not require network connectivity to operate. 1.3 "Installation Guide" means a computer file in Microsoft° Word or Adobe° PDF format or a text file that contains information a User may need to install or operate a Software Product. 1.4 "Primary License" means the license(s) of the Software Product provided to Customer for general production use as authorized by this EULA. 1.5 "Supplementary License" means a license(s) of the Software Product which is made available by Hexagon for select Software Products to augment Primary Licenses for special purposes. Each Supplementary License requires a Primary License and the term of the Supplementary License shall not exceed the term of the applicable Primary License. 1.6 "Web -based Software Product" means a Webservices-based Software Product that is accessed by Users solely over the World Wide Web, Internet, or intranet. 1.7 "XML Files" means the XML (Extensible Markup Language) files generated by the Software Product, where applicable. 1.8 "XSL Stylesheets" means the XSL (Extensible Stylesheet Language) presentation of a class of XML Files which, when included with the Software Product, describe how an instance of the class is transformed into an XML (Extensible Markup Language) document that uses the formatting vocabulary. 2 LICENSE GRANT. 2.1 Provided Customer is not in breach of any term or condition of this EULA or the applicable Order for a Software Product, Hexagon hereby grants Customer a limited, non-exclusive license to install and use the Software Product, in object code form only, strictly for Customer's internal use and strictly in accordance with this EULA. The license is non -transferable, except as specifically set forth in this EULA. Customer assumes full responsibility for the selection of the Software Product to achieve Customer's intended results, and for the installation, use, and results obtained from the Software Product. Hexagon Master Product and Services Agreement Page 18 2.2 Minimum Requirements. The Software Product may require Customer's System to comply with specific minimum software, hardware, and/or Internet connection requirements. Hexagon will append the applicable minimum requirements to Order Documents for Software License Sale under which a Software Product is purchased. 2.3 License Type and Mode. Software Products are licensed as either Primary Licenses or Supplementary Licenses. There are two (2) types of Primary Licenses and seven (7) types of Supplementary Licenses as described below. Depending on Customer's license, a license may be used in either Concurrent -Use mode or Node -Locked mode. The license type and mode for the Software Product Customer subscribed to or obtained will be designated (per the abbreviations set forth below) in the product description set forth on the proposal, quote, SOW, or packaging provided with the Software Product, and, if an electronic license manager tool is incorporated in the Software Product, verified by the Hexagon license system. If not otherwise indicated, Customer's license type and mode will be a Node -Locked Primary License. Each license of the Software Product is subject to the terms of this EULA. 2.3.1 Primary Licenses are described below: (a) Concurrent -use mode (CC) allows for the checking in and checking out of the total available licenses of the Software Product for Users. At any point, Customer may run as many copies of the Software Product as Customer have licenses. If the Software Product is enabled to be run in a disconnected mode, as set forth in the Installation Guide, a User may check out a license from the System for mobile or home use, thus reducing the total number of licenses available in the license pool until the license is checked back in to the System. If the Software Product is not enabled to be run in a disconnected mode, the mobile or home computer will require a Node -Locked License. If the anticipated number of Users of the Software Product will exceed the number of applicable licenses, and in the absence of a license manager tool incorporated in the Software Product, Customer must use a reasonable mechanism or process to assure that the number of persons using the Software Product concurrently does not exceed the number of licenses. Customer consents to the use of a license mechanism, license files, hardware keys, and other security devices in connection with the Software Product and agree not to attempt to circumvent, reverse engineer, or duplicate such devices. (b) Node -Locked mode (NL) allows a single copy of the Software Product to be stored on hard disk and loaded for execution on a single designated workstation, or, for software designed for use on a handheld device, for execution on a single designated handheld device. 2.3.2 Supplementary Licenses are described below: (a) Backup License (BCK) is licensed solely for "cold standby" when manual switchover of the Software Product to the Supplementary License is required in the event of failure of the Primary License. (b) Developer's License (DEV) is a license of a Web -based Software Product that is delivered solely in connection with the Primary License of such Software Product for the purposes of developing and testing Customer's website built only with the Software Product. Developer's Licenses shall not be used for production purposes (i.e. a fully deployed website). (c) Load Balancing License (LOB) is a license of a Web -based Software Product solely for use as a second or successive license on a web cluster to balance the load with the Primary License on multiple servers represented by one (1) IP address. Hexagon Master Product and Services Agreement Page 19 (d) Redundant License (RDT) is licensed solely for "hot standby" when automatic switchover of the Software Product to the Supplementary License is required in the event of failure of the Primary License. (e) Test License (TST) is licensed solely for testing purposes. However, Hexagon also allows a Test License to be used to conduct no -cost training on test servers for a maximum of thirty (30) days per year. (f) Training License (TRN) is licensed solely for training purposes. (g) Secondary License (SEC or TFB) is licensed for non -productive use for training, development, testing, failover, backup, etc. Number of Secondary Licenses cannot exceed the number of purchased Primary Licenses. 2.4 Updates and Upgrades. If the Software Product is an Update or Upgrade to a previous version of the Software Product, Customer must possess a valid license to such previous version in order to use the Update or Upgrade. The Software Product and any previous version may not be used by or transferred to a third party. All Updates and Upgrades are provided to Customer on a license exchange basis. Updates are subject to all of the terms and conditions of the EULA applicable to the Software Product. By using an Update or Upgrade, Customer (i) agrees to voluntarily terminate Customer's right to use any previous version of the Software Product, except to the extent that the previous version is required to transition to the Update or Upgrade; and (ii) acknowledges and agrees that any obligation that Hexagon may have to support the previous version(s) of the Software Product will end upon availability of the Update. If an Update is provided, Customer will take prompt action to install such Update as directed by Hexagon. If Customer fails to do so, Customer acknowledges the Software Product may not work correctly or Customer will not be able to take advantage of all of the Software Product's available features. In any event, Hexagon will not be liable for additional costs Customer incurs as a result of Customer's installation or failure to install an Update. The EULA delivered with the Upgrade may supersede any EULA or signed license agreement associated with prior releases of the Software Product. Customer and Hexagon acknowledge: that allowing an Upgrade to be licensed on the same terms as a prior release may create unintended consequences, such as, without limitation, a failure to bind a user to terms necessitated by new functions or content of the Upgrade; and, that mandating an Upgrade be licensed on terms delivered with the Upgrade may create unintended consequences, such as, without limitation, a heightened risk that new terms may apply to the user without the user's normal diligent scrutiny thereof. It is the expectation of the Parties to formally and expressly agree upon license terms to be applied to an Upgrade; provided that in the absence of express license terms evidenced in writing, an Upgrade shall be licensed on the same terms of the prior release, but subject to such superseding terms of the EULA delivered with the Upgrade as a commercially reasonable software vendor would require in order to accommodate any attributes of the Upgrade which differentiate it from the prior release. 3 RIGHTS AND LIMITATIONS. Please see specific exceptions and additional terms related to GeoMedia Viewer Software, Beta Software, Evaluation Software, and Educational Software set forth at the Addendum to this EULA. 3.1 THE FOLLOWING ARE PERMITTED FOR YOUR LICENSE: 3.1.1 Customer may make one copy of the Software Product media in machine readable or printed form and solely for backup purposes. Hexagon retains ownership of all User created copies. Customer may not transfer the rights to a backup copy unless Customer transfers all rights in the Software Product and license as provided for in Section 3.1.2. Any other copying of the Software Product, any use of copies in excess of the number of copies Customer have been authorized to use and have paid for, and any distribution of Hexagon Master Product and Services Agreement Page 20 the Software Product not expressly permitted by this EULA, is a violation of this EULA and of federal or applicable governing law. 3.1.2 Customer may transfer the Software Product and license within Customer's company (intra-company transfer), subject to the Hexagon Software Transfer Policy ("Software Transfer Policy") and the terms of this EULA. The Software Transfer Policy is available from Hexagon upon request. If Customer transfers the Software Product, Customer must at the same time either transfer all copies, modifications, or merged portions, in whatever form, to the same party, or Customer must destroy those not transferred. 3.1.3 For a Web -based Software Product: (a) Customer may run multiple Websites and provide multiple Webservices to Customer's client users with a single license. (b) Customer may distribute client side web page plug -ins (e.g., ActiveX controls, Java applets and applications, Enhanced Compressed Wavelet (ECW) plug INS) to Users. (c) Customer may load this Web -based Software Product on multiple machines within a cluster that is acting as a single web server, provided Customer has obtained the applicable number of Load Balancing Licenses or number of Cores from Hexagon and the total number of map servers or number of Cores deployed do not exceed the quantity licensed. (d) Customer may only copy and distribute the Java script source files to support the Web -based Software Product's output vector map type and Customer's associated websites, and Customer may prepare derivative works solely for Customer's internal use. 3.1.4 Unless otherwise stated in the Installation Guide, for Software Products which contain XSL Stylesheets for presenting XML Files, Customer may only use the XSL Stylesheets and derivative works thereof for the purpose of presenting XML Files and derivative works thereof (collectively, "XML Products") for Customer's enterprise. Customer may not distribute the XSL Stylesheets or XML Products on a stand-alone basis. XSL Stylesheets may not be used in the production of libelous, defamatory, fraudulent, lewd, obscene or pornographic material, or any material that infringes upon any third party intellectual property rights, or otherwise in any illegal manner. All XSL Stylesheets supplied with the Software Product are and will remain the property of Hexagon. 3.1.5 Unless otherwise stated in the Installation Guide, for Software Products that are delivered with an Application Programming Interface ("API") and/or configuration set-up, Customer may use the API(s) to write Customer's own extensions to the Software Products, and Customer may use configuration setup to configure the Software Product, but only to the extent permitted by the API(s) and/or configuration setup. Insofar as Hexagon does not transfer to Customer any rights in its Intellectual Property by allowing Customerto write Customer's own extensions using the API(s) or to configure the software via the configuration set-up, Customer hereby agrees and acknowledges that Hexagon retains all rights in its Software Product, API(s), and configurations. Except where otherwise provided for in writing, Hexagon does not make any representations or warranties with respect to such extensions and/or configurations and to the maximum extent permitted by applicable law, Hexagon and its suppliers disclaim all warranties, either express or implied, relating to such extensions and/or configurations, including, but not limited to, implied warranties of merchantability, fitness for a particular purpose, high risk use and non -infringement. Subject to the forgoing, Customer's use of such extensions and/or configurations is solely at Customer's own risk, and Customer hereby agrees to Hexagon Master Product and Services Agreement Page 21 indemnify and hold harmless Hexagon and its suppliers with respect to such extensions and/or configurations. 3.1.6 Customer is responsible, and bears the sole risk, for backing up all systems, software, applications, and data, as well as properly using the Software Product. 3.1.7 At all times, Customer must keep, reproduce and include all copyright, patent, trademark and attribution notices on any copy, modification or portion of the Software Product, including, without limitation, when installed, used, checked out, checked in and/or merged into another program. Ec���a��il��i��d/l►[e1_1:7��:Z�laly����l7ila'[�1�J:»[�l��ty� 3.2.1 Customer may not sell, rent, license, lease, lend, or otherwise transfer the Software Product, or any copy or modification, to another company or entity or person. Any such unauthorized transfer will result in automatic and immediate termination of the license. 3.2.2 Customer may not, and Customer may not authorize anyone else to, decompile, disassemble, or otherwise reverse engineer the Software Product. 3.2.3 Customer may not, and Customer may not authorize anyone else to, work around any technical limitations in the Software Product. 3.2.4 Customer may not, and Customer may not authorize anyone else to, publish the Software Product for others to copy or use. 3.2.5 Customer may not, and Customer may not authorize anyone else to, use, copy, modify, distribute, disclose, license or transfer the Software Product, or any copy, modification, or merged portion, in whole or in part, except as expressly provided for in this EULA. 3.2.6 Customer may not, and Customer may not authorize anyone else to, re -use the component parts of the Software Product with a software product other than the Software Product Customer is licensed to use. Customer may not, and Customer may not authorize anyone else to, re -use the component parts of the Software Product on different computers, servers, or devices. The Software Product is licensed as a single product. 3.2.7 Customer may not, and Customer may not authorize anyone else to, circumvent any license mechanism in the Software Product or the licensing policy. 3.2.8 Customer may not, and Customer may not authorize or allow anyone else to, use or view the Software Product for any purposes competitive with those of Hexagon. 3.2.9 Customer may not, and Customer may not authorize anyone else to, use the Software Product except as expressly set forth in this EULA. 3.2.10 For a Desktop -based Software Product that is Node -Locked: (a) Customer may not run the Software Product for Web -based applications. (b) Customer may not allow the Software Product to be used by multiple Users on a single workstation at the same time. 3.2.11 Customer may not, and Customer may not authorize or allow anyone else to, use the Developer's License for production purposes (i.e., a fully -deployed website). 3.2.12 Customer may not, and Customer may not authorize or allow anyone else to, publish to a third party any results of benchmark tests run on the Software Product. The sample and demo data set(s) and related script(s) delivered with some Software Products Hexagon Master Product and Services Agreement Page 22 (the "Sample Data") are provided solely for the purpose of instructing the User on how to use the Software Product with which the Sample Data are delivered. The Sample Data are licensed in conjunction with the Software Product and are not to be redistributed, licensed, sold, transferred, used, or otherwise dealt with in a production solution without Hexagon's prior written consent. 3.2.13 The Software Product is not one hundred percent (100%) fault -tolerant. The Software Product is not designed or intended for use in any situation where failure or fault of any kind of the Software Product could lead to death or serious bodily injury of any person, or to severe physical, property, or environmental damage ("High Risk Use"). Customer is not licensed to use the Software Product in, or in conjunction with, any High Risk Use. High Risk Use of any Software is STRICTLY PROHIBITED. High Risk Use includes, for example, the following: operation of aircraft or other modes of human mass transportation, nuclear or chemical facilities, and Class III medical devices. Customer hereby agrees not to use the Software Product in, or in connection with, any High Risk Use. High Risk Use shall not mean any use of the Software Product for purposes it is regularly marketed and sold (e.g., computer aided dispatch software may be used to dispatch emergency services). 3.2.14 For a Web -based Software Product: (a) Customer may not use the Web -based Software Product to operate software as a service or hosting without the prior written consent of Hexagon. (b) Customer may not use a Load Balancing License (LOB) of the Web -based Software Product detached of its Primary License. (c) Customer may not use Primary Licenses (and their allocated Load Balancing Licenses) ordered or delivered under a single part number (e.g. "product name — WORKGROUP") for other entities or organizations or at a different physical geographic address. (d) Core Restrictions for Hexagon APOLLO Software Product: License fees and installation restrictions for Hexagon APOLLO Software Products may be based on the number of Cores present in the server on which the Hexagon APOLLO Software Products are installed. The license type for APOLLO will be designated in the product descriptions set forth on the proposal, quote or packaging provided with the Software Product. If Customer's APOLLO Software Products are Core based, this section will apply. Each product can be licensed in multiples of four (4) Cores, up to a maximum thirty-two (32) Cores. Customer are responsible for determining the number of Cores on Customer's host server and ordering the appropriate number of Core licenses. Each license of a Hexagon APOLLO Software Product must be installed only on a single server. For example, an 8-Core license does not permit Customer to install two copies of a component, each on a 4-Core server. In a virtualized data processing environment, where hyper -threading, "virtual machine" technology or other similar techniques create "virtual processors" which do not necessarily correspond to the physical Cores present on the server, Customer's usage rights depend on the relationship between the number of Cores for which Customer is licensed, the number of physical Cores present on the host server, and the number of processors available to the Hexagon APOLLO Software Product in the virtualized environment, as follows: if the number of Cores for which Customer is licensed equals or exceeds the number of physical Cores present on the host server, then additional virtual processors created by hyper -threading or other methods of multi -tasking a physical Core do not violate Customer's licensing restriction. However, if Customer wishes to install the Hexagon APOLLO Software Product on a host server having a greater Hexagon Master Product and Services Agreement Page 23 number of physical Cores present than the number of Cores for which Customer is licensed, Customer must operate the Hexagon APOLLO Software Product only within a "guest" virtual machine that accesses a maximum number of processors (whether virtual, physical or both) that is less than or equal to the number of Cores for which Customer is licensed. 3.3 Indemnification by Customer. Customer agree to hold harmless and indemnify Hexagon for any causes of action, claims, costs, expenses and/or damages resulting to Hexagon from a breach by Customer or any User of any of the limitations or prohibited actions set forth in this EULA. 4 TERM. This EULA is effective until terminated or until Customer's software subscription or lease expires without being renewed. This EULA may be terminated (a) by Customer, by returning to Hexagon the original Software Product or by permanently destroying the Software Product, together with all copies, modifications and merged portions in any form; (b) by Hexagon, upon Customer's breach of any of the terms hereof or Customer's failure to pay the appropriate license or subscription fee(s); (c) upon Customer's installation of an Upgrade that is subject to a new applicable license agreement covering the Software Product Upgrade; or (d) by expiration of the applicable license files, if this is a temporary license. Customer agree upon the earlier of the termination of this EULA or expiration of Customer's software subscription to cease using and to permanently destroy the Software Product (and any copies or modifications of the Software Product in any form, and all of the component parts of the Software Product) and certify such destruction in writing to Hexagon. 5 AUDIT. Hexagon shall have the right, during Customer's normal business hours, to audit Customer's use of the Software Product and Customer's compliance with the provisions of this EULA. Hexagon will provide Customer with thirty (30) days prior written notice of an audit. The right of audit shall be limited to twice per calendar year. Prior to the start of an audit, Hexagon's personnel will sign a reasonable non -disclosure agreement provided by Customer. During the audit, Customer shall allow Hexagon's personnel to be provided reasonable access to both Customer's records and personnel. The cost of the audit shall be paid by Hexagon unless the results of the audit indicate that Customer has underpaid fees to Hexagon, in which case, Customer agrees to promptly pay Hexagon such fees at the price previously agreed to for the Software Product license or software subscription plus interest on such underpayments from the original due date at the lesser of two percent (2%) per month or the highest rate allowed by applicable law, and Customer further agrees to bear all costs associated with the audit. In addition to the foregoing provisions related to general auditing, Hexagon shall have a right to obtain certain documentation from you, as follows. If the SOFTWARE 7 PRODUCT includes logging mechanisms intended to track usage volume or quantity, you shall not intentionally interfere with such mechanisms, and you shall transmit log files associated therewith to Hexagon upon Hexagon's demand and in accordance with Hexagon's reasonable transmission instructions. Hexagon shall not demand the transmission of usage tracking log files more frequently than four (4) times in any calendar year. If log files establish an underpayment of fees to Hexagon, such underpayment will Hexagon Master Product and Services Agreement Page 24 be addressed on the same basis as an underpayment discovered as a result of a general audit. 6 INTELLECTUAL PROPERTY. 6.1 Ownership of Software. ALL SOFTWARE PRODUCTS ARE PROPRIETARY PRODUCTS OF HEXAGON AND THIRD PARTIES WHERE SUCH THIRD PARTIES ARE IDENTIFIED BY HEXAGON, AND ARE PROTECTED BY COPYRIGHT LAWS AND INTERNATIONAL TREATIES. TITLE TO SOFTWARE PRODUCTS AND ALL COPIES, MODIFICATIONS AND MERGED PORTIONS OF A SOFTWARE PRODUCT SHALL AT ALL TIMES REMAIN WITH HEXAGON AND SUCH THIRD PARTIES. Software Products are licensed pursuant to this EULA, not sold. Hexagon and additional third parties retain all right, title and interest in and to all Software Products, including, but not limited to, all Intellectual Property rights in and to each Software Product. All rights not expressly granted to Customer by this EULA or other applicable Third Party Software license agreement or terms and conditions are reserved by Hexagon and such third parties. No source code is deliverable hereunder unless otherwise expressly agreed to in writing by Hexagon. A list of registered patents associated with the Software Products, is available at www.intergraph.com/patents. 6.2 Ownership of Intellectual Property. Customer acknowledges and agrees that Hexagon and third party manufacturers, as applicable, own all rights in and to Hexagon's and the applicable third party manufacturer's trade names, and no right or license is granted to Customer pursuant to this EULA to use such trade names. Customer also acknowledges and agrees that Hexagon and third party manufacturers, as applicable, own all right, title and interest in and to all Intellectual Property relating to and for the Software Product. If Customer brings a patent claim against Hexagon or any third party manufacturer over patents Customer claim are being infringed by the Software Product, Customer's patent license from Hexagon and any applicable third party manufacturer(s) for the Software Product automatically ends. 6.3 Intellectual Property Infringement Indemnification by Customer. In the event any proceeding (suit, claim, or action) is based (in whole or in part) on modifications, enhancements or additions made by Customer or any person or entity on Customer's behalf, or Customer's use of the Software Product in combination with other products not furnished by Hexagon, Customer agrees to hold harmless and defend, at Customer's sole cost and expense, all of Hexagon's right, title and interest in and to the Software Product, as well as Hexagon's goodwill and reputation both in good faith and at a standard as if the claim is made against Customer. Customer shall reimburse Hexagon any defense expenses inclusive of reasonable attorneys' fees expended by Hexagon in defense of said claim, and pay any judgment rendered against Hexagon. Customer shall make such defense by counsel of Customer's choosing and Hexagon shall reasonably cooperate with said counsel at Customer's sole cost and expense. Customer shall have sole control of said defense, but Customer shall allow Hexagon to reasonably participate in its own defense and Customer shall reasonably cooperate with Hexagon with respect to the settlement of any claim. Notwithstanding the foregoing, Hexagon may at any time decide to take over any defense of Hexagon at Hexagon's cost and expense and Customer shall render full cooperation and assistance to transfer such defense to Hexagon and with respect to such defense. 7 RESTRICTIONS. 7.1 United States Government Restricted Rights. If the Software Product (including any Updates, Upgrades, documentation or technical data related to such Software Product) is licensed, purchased, subscribed to or obtained, directly or indirectly, by or on behalf of a unit or agency of the United States Government, then this Article 7 also applies. Hexagon Master Product and Services Agreement Page 25 7.1.1 For civilian agencies: The Software Product was developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with the Federal Acquisition Regulations ("FAR") 52.227-19 (a) through (d) (Commercial Computer Software — Restricted Rights). 7.1.2 For units of the Department of Defense: The Software Product was developed at private expense and is "commercial computer software" submitted with restricted rights in accordance with the Defense Federal Acquisition Regulations ("DFARS") DFARS 227.7202-3 (Rights in commercial computer software or commercial computer software documentation). 7.1.3 Notice: This Software Product is "Commercial Computer Software" as defined in DFARS 252.227-7014 (Rights in Noncommercial Computer Software) and FAR 12.212 (Computer Software), which includes "technical data" as defined in DFARS 252.227-7015 (Technical Data) and FAR 12.211 (Technical Data). All use, modification, reproduction, release, performance, display or disclosure of this "Commercial Computer Software" shall be in strict accordance with the manufacturer's standard commercial license, which is attached to and incorporated into the governing Government contract. Hexagon and any applicable Third Party Software manufacturer(s) are the manufacturer. This Software Product is unpublished and all rights are reserved under the copyright laws of the United States. 7.1.4 Government Reserved Rights: MrSID technology incorporated in the Software Product was developed in part through a project at the Los Alamos National Laboratory, funded by the U.S. Government, managed under contract by the University of California (the "University"), and is under exclusive commercial license to LizardTech, Inc. It is used under license from LizardTech. MrSID technology is protected by U.S. Patent No. 5,710,835. Foreign patents pending. The U.S. Government and the University have reserved rights in MrSID technology, including without limitation: (a) The U.S. Government has a non-exclusive, nontransferable, irrevocable, paid -up license to practice or have practiced throughout the world, for or on behalf of the United States, inventions covered by U.S. Patent No. 5,710,835 and has other rights under 35 U.S.C. § 200-212 and applicable implementing regulations; (b) If LizardTech's rights in the MrSID technology terminate during the term of this EULA, Customer may continue to use the Software Product. Any provisions of this license which could reasonably be deemed to do so would then protect the University and/or the U.S. Government; and (c) The University has no obligation to furnish any know-how, technical assistance, or technical data to users of MrSID technology and makes no warranty or representation as to the validity of U.S. Patent 5,710,835 nor that the MrSID technology will not infringe any patent or other proprietary right. For further information about these provisions, contact LizardTech, 1008 Western Ave., Suite 200, Seattle, WA 98104. 7.2 Export Restrictions. Software Products, including any technical data related to Software Products, are subject to the export control laws and regulations of the United States, including, but not limited to the U.S. Export Administrations Act. Diversion contrary to United States law is prohibited. This Software Product, including any technical data related to this Software Product and any derivatives of this Software Product, shall not be exported or re-exported, directly or indirectly (including via remote access), under the following circumstances: • To Cuba, Iran, North Korea, Sudan, or Syria, or any national of these countries. • To any person or entity listed on any United States government denial list, including, but not limited to, the United States Department of Commerce Denied Persons, Entities, and Unverified Lists(www.bis.doc.gov/compIianceandenforcement/Iiststocheck.htm), the Hexagon Master Product and Services Agreement Page 26 United States Department of Treasury Specially Designated Nationals List (www.treas.gov/offices/enforcement/ofac/), and the United States Department of State Debarred List (http://www.pmddtc.state.gov/compliance/debar.html). • To any entity if Customer knows, or have reason to know, the end use is related to the design, development, production, or use of missiles, chemical, biological, or nuclear weapons, or other unsafeguarded or sensitive nuclear uses. • To any entity if Customer knows, or have reason to know, that an illegal reshipment will take place. If the Software Product Customer received is identified on the media as being ITAR-controlled, this Software Product has been determined to be a defense article subject to the U.S. International Traffic in Arms Regulations ("ITAR"). Export of this Software Product from the United States must be covered by a license issued by the Directorate of Defense Trade Controls ("DDTC") of the U.S. Department of State or by an ITAR license exemption. This Software Product may not be resold, diverted, or transferred to any country or any end user, or used in any country or by any end user other than as authorized by the existing license or ITAR exemption. Subject to the terms of this EULA, this Software Product may be used in other countries or by other end users if prior written approval of DDTC is obtained. Customer agree to hold harmless, indemnify and defend Hexagon for any causes of actions, claims, costs, expenses and/or damages resulting to Hexagon from a breach by Customer or any User of the export restrictions set forth in this EULA. Any questions regarding export or re-export of the Software Product or concerning ITAR restrictions, if applicable, should be addressed to Hexagon's Export Compliance Department at 305 Intergraph Way, Madison, Alabama, United States 35758 or at exportcompliance@intergraph.com. 7.3 Territorial Use Restriction. Unless otherwise specifically permitted in writing by Hexagon, use of the Software Product outside the country in which it is licensed is strictly prohibited. 7.4 Use Outside the United States. If Customer is located outside the United States, then the provisions of this section shall also apply: (i) Les parties en presence confirment leur volonte que cette convention de meme que tous les documents y compris tout avis qui s'y rattachent, soient rediges en langue anglaise (Translation: "The parties confirm that this agreement and all related documentation is and will be in the English language."); and (ii) Customer is responsible for complying with any local laws in Customer's jurisdiction which might impact Customer's right to import, export or use the Software Product, and Customer represents that Customer has complied with any and all regulations or registration procedures required by applicable law to make this EULA fully enforceable. 7.5 Survival. The provisions of this EULA which require or contemplate performance after the expiration or termination of this EULA shall be enforceable notwithstanding said expiration or termination. THE REMAINDER OF THIS PAGE IS LEFT BLANK INTENTIONALLY Hexagon Master Product and Services Agreement Page 27 HEXAGON SAFETY & INFRASTRUCTURE I:I*:I_IrZ9]ki121kiU111111&121:»[a] Ell ki&9Wive] :7Ell ;I►yil21kikl ADDENDUM FOR CERTAIN PRODUCTS This Addendum is applicable to Customer in the event that the Software Product is one that also makes use of the products identified below. If applicable, this Addendum ("Addendum") sets forth the terms of the Customer's use of the Software Product in addition to the terms of the END - USER LICENSE AGREEMENT ("EULA") provided to the Customer at the time of purchase. This Addendum shall only apply to Customer if Customer use any of the products identified below. To the extent not inconsistent with this Addendum, all terms of the EULA shall apply to the use of the Software Product. In the event of a conflict of terms between the EULA and this Addendum, this Addendum shall take precedence over the EULA. 1 Geospatial Desktop Program. This Article only applies if the Software Product is that particular bundle of applications known as the "Geospatial Desktop Program." 1.1 Definitions. 1.1.1 "Effective Addendum Date" shall mean the later of (i) the date of delivery of the License Key(s) to Licensee, (ii) the date the Geospatial Desktop Program goes into production, or (iii) such later date as specified in the Quote. 1.1.2 "Existing Products" - any Hexagon software products held by Customer prior to entering into this addendum that are duplicative of one or more components of the Geospatial Desktop made the subject of this Addendum. 1.1.3 "License Key" shall mean the unique key provided to the Licensee by Hexagon for the run-time use of the Software Product 1.1.4 "Licensee" shall mean an individual or single legal entity authorized by Hexagon to utilize the Software Product pursuant to the EULA and this Addendum. 1.2 License Grant. Provided Customer is not in breach of any term or condition of the EULA or this Addendum Hexagon hereby grants Customer a limited, non-exclusive license to install and use the Software Product, in object code form only, strictly for Customer's internal use and strictly in accordance with the EULA and this Addendum. The license is non -transferable, except as specifically set forth in the EULA. Customer assumes full responsibility for the selection of the Geospatial Desktop Program to achieve Customer's intended results, and for the installation, use, and results obtained from the Geospatial Desktop Program. 1.2.1 License type and Mode: The Geospatial Desktop Program licensed pursuant to this Addendum shall be concurrent -use mode (CC) as defined in the EULA. 1.3 Term. This Addendum and the rights granted to Licensee pursuant to this Addendum and the EULA shall begin upon the Effective Addendum Date and remain in effect for a period of twelve (12) months. This Addendum may be renewed as set forth herein. New License Keys and/or installation media will be issued annually upon renewal of this Addendum. Approximately thirty (30) days prior to the end of the license term, Hexagon may submit a renewal Quote to the Licensee to renew the license(s) for the next subscription period at the prices provided in the renewal Quote. If the license(s) are not renewed at the end of the term, Licensee Hexagon Master Product and Services Agreement Page 28 acknowledges that all rights and license grants provided by this EULA and this Addendum shall terminate upon expiration of the term described in the section immediately above. 1.4 Customer's Existing Products. Any Existing Products held by Customer are not a part of this Addendum. 1.4.1 Any Existing Products must be subject to a separate Hexagon maintenance agreement. Customer may choose to not renew maintenance for Existing Products only at the expiration of the term of any maintenance agreement applicable to Existing Products. Early maintenance termination is not permitted for Existing Products under this Addendum. 2 Geospatial SDK. This Article only applies if the Software Product is the Geospatial Portal SDK. 2.1 License Limitations for Sencha Products. Customer shall not distribute the Sencha Products in stand-alone form. Customer shall not provide license rights, consulting, training, or other services with the standalone functionality of the Sencha Products. Customer shall not allow third parties to develop or use the Sencha Products on a standalone basis. Copies of the Sencha Products are licensed and not sold. Customer may not: (a) modify the Sencha Products or permit or permit any third party to do so; (b) rent, lease or sell or otherwise provide temporary access to the Sencha Products to any third party; (c) use the Sencha Products in any manner to assist or take part in the development, marketing, or sale of a product competitive with the Sencha Products; (d) modify, remove or obstruct any copyright or other proprietary rights statements or notices contained within the Sencha Products; (e) distribute the Sencha Products except as provided herein; (f) allow, assist or permit any others to do any of the foregoing. Customer agrees to not reverse engineer, decompile, disassemble, or otherwise attempt to discover the source code of the Sencha Products. Customer may only make a single copy of the Sencha Products for back-up purposes only. 2.2 Limitations on Use. Customer may only use the Geospatial Portal SDK and Sencha Products in combination with the Geospatial Portal Software Product. For the avoidance of doubt, "Customer" in this Addendum means an individual person. Only one person may use the Geospatial Portal SDK per license. Customer is the only authorized user of this licensed copy of the Geospatial Portal SDK and Customer may not allow anyone other than itself to use the Geospatial Portal SDK. 3 Remote Content Management. This Article only applies if the Software Product is Remote Content Management and makes use of DotNetZip Library. 3.1 "Contributor" shall mean any person that distributes its contribution under this license. 3.2 If Customer brings a patent claim against any contributor over patents that Customer claims are infringed by the software, Customer's patent license from such contributor to the software ends automatically. 4 IMAGINE GeoPDF PUBLISHER. This Article only applies if the Software Product is the IMAGINE GeoPDF PUBLISHER product. 4.1 Warranty Disclaimer. Notwithstanding anything to the contrary herein, no warranty is provided with respect to the performance of IMAGINE GeoPDF PUBLISHER. For greater clarity IMAGINE GeoPDF PUBLISHER is provided on an "AS IS" basis. 4.2 Limitation of Liability. Hexagon, its licensors or its suppliers shall not be liable for any claims relating to or arising out of IMAGINE GeoPDF PUBLISHER, regardless of form, in connection with Customer's use of IMAGINE GeoPDF PUBLISHER. Hexagon Master Product and Services Agreement Page 29 4.3 Acceptance. IMAGINE GeoPDF PUBLISHER shall be deemed accepted upon Customer's installation of the same. 4.4 Use Restrictions. Customer may use the GeoPDF PUBLISHER only for Customer's internal business use, and Customer may not use IMAGINE GeoPDF PUBLISHER to render any files other than GeoPDF files. 5 Euclideon technology. This Article only applies if the Software Product is APOLLO, ERDAS IMAGINE, Geospatial Portal, or GeoMedia WebMap. These Software Products have Euclideon technology embedded within the final products and the intellectual property rights of such third -party technology remain with Euclideon. By installing and using these Software Products, Customer agrees that Customer will not modify, reverse engineer, disassemble or decompile any Euclideon software, that Customer will not remove, obscure or alter any notice of patent, trademark, copyright or trade name. 6 mTransformer. mTransformer by myVR Software AS is delivered with the Hexagon Geospatial Provider Suite and Platform Suite products. mTransformer may be installed on any machine and used within an organization that has a valid license for any product from the Provider Suite or the Platform Suite. 7 GeoMedia Viewer Software — Additional Terms. The software license specifically for GeoMedia Viewer permits copies to be stored on hard disk and loaded for execution on one or more workstations. The GeoMedia Viewer software may be freely copied, transferred, and loaned both inside and outside Customer's company. 8 Beta Software - Additional Terms. If the Software Product Customer received with this EULA is Beta Software, then the following additional terms apply. To the extent that any provision in this Article is in conflict with any other terms or conditions in this EULA, this Article shall supersede such other terms and conditions with respect to the Beta Software, but only to the extent necessary to resolve the conflict. Customer shall hold all information concerning Beta Software and Customer's use and evaluation of such information and the Beta Software (collectively, "Beta Software Information") in confidence and with the same degree of care Customer uses to keep Customer's own similar information confidential, but in no event shall Customer use less than a reasonable degree of care; and Customer shall not, without the prior written consent of Hexagon, disclose such Beta Software Information to any person or entity for any reason at any time; provided, however, it is understood that Customer may disclose any Beta Software Information to those of Customer's representatives who actually need such information for the purpose of participating in the proposed evaluation and testing ("Beta Testing") of the Beta Software, on the condition that, prior to such disclosure, such representative has been made aware of the terms of this EULA. Customer shall not use any Beta Software Information for any reason or purpose other than as necessary for Beta Testing. Customer agrees to make no other use of the Beta Software Information or to incorporate any Beta Software Information into any work or product. Customer acknowledges that the Beta Software is a pre-release, beta version, does not represent final product from Hexagon, and may contain bugs, errors and other problems that could cause system or other failures and data loss. THE BETA SOFTWARE IS PROVIDED TO YOU "AS -IS", AND HEXAGON DISCLAIMS ALL WARRANTY AND LIABILITY OBLIGATIONS TO YOU OF ANY KIND. Customer may use the Beta Software only for evaluation and testing. Production use of Beta Software is strictly prohibited. Customer acknowledges that Hexagon has not promised or guaranteed to Customer that Beta Software or any portion thereof will be announced or made available to anyone in the future, Hexagon has no express or implied obligation to Customer to announce or introduce the Beta Software and that Hexagon may not introduce a product similar to or compatible with the Beta Software. Accordingly, Customer acknowledges that any research or development that Customer performs regarding the Beta Hexagon Master Product and Services Agreement Page 30 Software or any product associated with the Beta Software is done entirely at Customer's own risk. During the term of this EULA, if requested by Hexagon, Customer will provide feedback to Hexagon regarding Beta Testing, including error or bug reports. Upon receipt of a later unreleased version of Beta Software or release by Hexagon of a publicly released commercial version of the Software Product, Customer agrees to return or permanently destroy all earlier Beta Software received from Hexagon. Customer agrees that Customer will return or destroy all unreleased versions of the Beta Software within thirty (30) days of the completion of Beta Testing when such date is earlier than the date for Hexagon's first commercial shipment of the publicly released commercial software. 9 Evaluation Software - Additional Terms. If the Software Product Customer has received with this EULA is provided specifically for evaluation purposes ("Evaluation Software"), then this Article applies until such time that Customer purchases a license of the full retail version of the Software Product. To the extent that any provision in this Article is in conflict with any other term or condition in this EULA, this Article shall supersede such other terms and conditions with respect to the Evaluation Software, but only to the extent necessary to resolve the conflict. Customer may use the Evaluation Software only for evaluation and testing and not for general production use. Customer acknowledges the Evaluation Software may contain limited functionality and/or may function for a limited period of time. Hexagon is licensing the Evaluation Software on an "AS -IS" basis, solely for Customer's evaluation to assist in Customer's purchase decision. If the Evaluation Software is a timeout version, then the program will terminate operation after a designated period of time following installation (the "Time Out Date"). Upon such Time Out Date, the Evaluation Software license will cease operation and Customer will not be able to use the Software Product, unless Customer purchases a license for a full retail version of the Software Product. Customer acknowledges such Evaluation Software shall cease operation upon the Time Out Date and accordingly, access to any files or output created with such Evaluation Software or any product associated with the Evaluation Software is done entirely at Customer's own risk. 10 Educational Software Product — Additional Terms. If the Software Product Customer has received with this EULA is Educational Software Product (where either an education price is paid for the Software Product, or the Software Product is received by virtue of Customer's participation in an Hexagon program designed for educational or research institutions, or is received through an education grant from Hexagon), Customer is not entitled to use the Software Product unless Customer qualifies in Customer's jurisdiction as an Educational End User. Customer may use the Educational Software Product only for educational and research purposes. Commercial and general production use of Educational Software Products is specifically prohibited. Additional terms and conditions, as well as the definition of an Educational End User, are detailed in Hexagon's Education Policy which is available from Hexagon upon request. 11 ImageStation and Geospatial SDI Software — Additional Terms. Some Software Products of the ImageStation and Geospatial SDI product families contain one or more dynamic link libraries (DLLs) that were built at least partially from open source code subject to the Code Project Open License (CPOL) 1.02 which may be found at http://www.codeproject. com/info/cpo110.aspx. By installing and using these Software Products, Customer agrees the terms of the CPOL license apply to the portions of such DLLs built with CPOL-licensed open source code. 12 ECW Browser Plug-in — Additional Terms. The Enhanced Compression Wavelet (ECW) browser plug-in Software Product ("Browser Plug-in") is designed to be used as a browser plug- in to view, within the Microsoft Internet Explorer, Google Chrome and Mozilla Firefox browsers (the "Browsers"), images created using ECW image technology. Browsers are not included with the Browser Plug-in. Customer may make and install as many copies of the Browser Plug-in as Customer needs, as plug -ins to lawfully licensed Browsers on computers that Customer owns or controls. If Customer has a valid license to use Hexagon Enhanced Compression Wavelet Hexagon Master Product and Services Agreement Page 31 (ECWP) server Software Product ("ECWP Server Software"), Customer may also distribute copies of the Browser Plug-in to others whom Customer wish to authorize to access images residing on Customer's ECWP server, provided Customer includes this EULA with the distributed copies. All copies of the Browser Plug-in authorized as described herein are considered to be authorized copies. Customer may install and use the Browser Plug-in only to enable the Browsers to display images that are created with ECW image technology, and that are accessed via Customer's licensed ECWP Server Software. The Browser Plug-in is licensed only for research, commercial, governmental, and educational purposes and is not licensed, and shall not be used, for personal, family, or household purposes. 13 AAIC and RINAV - Limits on use. Customer may not use a single license of AAIC or RINAV for more than four (4) simultaneous jobs. Customers desiring to execute AAIC or RINAV simultaneously on more than four (4) cores may purchase additional licenses. END OF EXHIBIT B Hexagon Master Product and Services Agreement Page 32 HEXAGON SAFETY & INFRASTRUCTURE Exhibit C - Hexagon U.S. Maintenance Terms and Conditions The additional terms and conditions set forth in this Exhibit C shall govern the Maintenance Services provided by Hexagon to Customer for the Covered Products identified in individual Orders issued pursuant to the Master Agreement. Terms not defined in this Exhibit C will have the meaning ascribed to them in the General Terms and Conditions or Exhibit B (the End User License Agreement). DEFINITIONS 1.1 "Maintenance Agreement" means the combined terms and conditions applicable to an Order for Maintenance Services, to -wit: the terms set forth in this Exhibit, the General Terms and Conditions of the Master Agreement, and the applicable Quote for Maintenance Services. 1.2 "Coverage Period" means the period of performance of Maintenance Services set forth in the applicable Quote. 1.3 "Covered Products" means the software listed on the Quote for which Maintenance Services are to be provided to Customer by Hexagon. Covered Products shall also include additional copies of software (i) where the software is already a Covered Product under an existing Maintenance Agreement and (ii) additional licenses are purchased or otherwise obtained by Customer during the Coverage Period. Covered Products may include Software Products and Third Party Software. 2 AUTHORIZATION OF SERVICES Following execution of the Master Agreement, Customer authorizes Hexagon to provide the Maintenance Services for Covered Products during the Coverage Period in accordance with the Maintenance Agreement by one of the following means: a) returning a signed Quote for Maintenance Services; b) submitting a signed purchase order referencing a Quote for Maintenance Services; c) paying any charges as set forth on a Quote for Maintenance Services; or d) accepting delivery of Maintenance Services as set forth on a Quote for Maintenance Services. The Maintenance Services will be provided by Hexagon in accordance with the Scope of Coverage as set forth elsewhere in this Exhibit. 3 TERM AND RENEWALS OF A MAINTENANCE AGREEMENT 3.1 The Maintenance Agreement shall begin, retroactively (if applicable), on the first calendar day of the first month of the applicable Coverage Period, and shall expire at the end of the Coverage Period unless terminated earlier pursuant to the terms of the Master Agreement, or renewed by mutual agreement of the parties in accordance with the terms of this Exhibit. The Coverage Period shall be for whole months only. 3.2 Approximately ninety (90) days prior to the expiration date of any Coverage Period, Hexagon will submit to Customer a renewal Quote that includes pricing for the upcoming Coverage Period. The immediately preceding Article entitled "AUTHORIZATION OF SERVICES' shall apply mutatis mutandis to the formation of a renewed Maintenance Agreement based on the renewal Quote. If the Maintenance Agreement is not renewed for an additional annual Coverage Hexagon Master Product and Services Agreement Page 33 Period based on the renewal Quote, Hexagon, after the preceding Coverage Period has expired, shall be entitled to discontinue Maintenance Services for the affected Covered Products, including access to system support or knowledge base, and/or end the ability of Customer to log or check support requests. 4 LAPSE AND REINSTATEMENT OF MAINTENANCE SUPPORT COVERAGE 4.1 Lapse in Maintenance Coverage. To reinstate Maintenance Services after any termination or suspension thereof, Customer must pay a reinstatement fee. The Coverage Period for any reinstated Maintenance Services (the "Renewal Coverage Period") shall begin on the first day after the expiration or termination of the last paid -in -full Coverage Period and extend until the next purchase anniversary date of the lapsed Covered Products. The reinstatement fee will equal twenty-five percent (25%) of the past due maintenance charges (rounded up to whole months only) for the Renewal Coverage Period, and shall be in addition to the total maintenance charges due for the Renewal Coverage Period, all calculated at the current maintenance list price. Upon request of Customer, Hexagon will provide a Quote for the Renewal Coverage Period, to include the reinstatement fee, which is applicable only for reinstatement made in the then -current month. 4.2 Failure to Obtain Maintenance Coverage. In the event Maintenance Services were not purchased at the time that the Covered Product was originally purchased, in order to obtain Maintenance Services, Customer must pay one hundred twenty-five percent (125%) of all maintenance payments from the date the original Covered Product was purchased up to the date the Maintenance Services are actually purchased, plus one hundred percent (100%) of the remaining Coverage Period that expires upon the anniversary date of the original Covered Product purchase, all calculated at the current maintenance list price. The Coverage Period for such Covered Products will begin on the first day of the month in which the Covered Products were originally purchased. E•& We] Zilto] aKe]LV/21:Lfflel: a 2 150]:at101a rTd/_1:7: a Zil:Z0]9IN] 0& Maintenance Services described in this Article apply to Software Products only. Hexagon offers two levels of Maintenance Services for Software Products included in the Covered Products: Standard Support and Premium Support. Under both levels of Maintenance Services, Hexagon shall provide reasonable commercial efforts to aid in the diagnosis and correction of defects in and provide general advice as to the use of the Software Products included in the Covered Products. The level of Maintenance Services will be set forth on the Quote and will include the following: 5.1 Standard Support: Standard Support will include and be limited to the following: 5.1.1 Help Desk Support. Out -of -the -box functionality support via the Help Desk (telephone or eService via Hexagon's Customer Support Web Site where available at http://esupport.intergraph.com). Phone support for all priority levels of software errors is available on Monday through Friday from 8 AM — 5 PM at Customer's local time, excluding Hexagon -observed holidays. Local variances in support hours will be posted on the Customer Support Web Site or applicable local support website, or can be determined by contacting Customer's local Hexagon office. 5.1.2 Updates. Access to all available Updates of Software Products included in the Covered Products. Hexagon will notify Customer when Updates are made available for any Software Products for which Service has been purchased by way of posting notices of such to the "Support Notices and Announcements" section on the Customer Support Web Site or applicable local support website or via direct notification by Hexagon. If applicable, Customer may also register on the Customer Support Web Site or applicable Hexagon Master Product and Services Agreement Page 34 local support website to automatically receive email notifications when a new release of a Software Product is made available by Hexagon. Updates are shipped to Customer upon Customer request. Hexagon is not obligated to produce any Updates. 5.1.3 Knowledge Base. Twenty-four-hour-per-day/seven-day-per-week access to problem Knowledge Base, an on-line self-help tool. 5.2 Premium Support: Premium Support will include all of the features available under Standard Support. Additionally, when the software error is considered to be critical (meaning production is down), then phone support is also available after-hours and on Hexagon -observed holidays. 5.3 Hexagon may not provide both levels of support for all Software Products in all countries. Customer may choose any level of Maintenance Services offered, however, all interrelated or identical Software Products included in the Covered Products under the Terms and Conditions must have the same level of Maintenance Services when available. 5.4 Defect correction Maintenance Services are only available for the current version and the one version prior to the current version of a particular Software Product, except in system down cases and in cases wherein Hexagon otherwise elects. Diagnostic Maintenance Services are available regardless of version. Maintenance Services are limited to the specific Software Products listed on the Quote and functioning on the appropriate Hexagon -supported operating system. 6 MINIMUM SYSTEM REQUIREMENTS; CUSTOMER'S OBLIGATIONS Performance of Maintenance Services by Hexagon is specifically conditioned upon the following minimum system requirements and fulfillment by Customer of the following obligations (collectively, minimum system requirements and customer obligations hereinafter referred to as "Customer Obligations"): 6.1 Customer's hardware and operating system software must meet the minimum system requirements specified by Hexagon and made available to Customer upon request. 6.2 Customer's system must have input and output devices that enable the use of Hexagon's diagnostic programs and supplemental tests. The specifications of such devices shall be made available to Customer by Hexagon upon request. 6.3 Customer will be responsible for any required adjustments or updates to its hardware and/or operating system software required to accommodate Updates of Covered Products. 6.4 Customer will ensure availability of its own system technical support personnel so that Hexagon can fulfill its Service obligations. 6.5 When reporting problems to Hexagon's Help Desk, Customer will provide a complete problem description, along with all necessary documents and information that is available to Customer and required by Hexagon to diagnose and resolve the problem. Customer will grant all necessary access to all required systems as well as to the Covered Products, and any other reasonable assistance needed. 6.6 Customer will carry out any reasonable instructions on troubleshooting or circumvention of the problem provided by Hexagon through an Authorized Contact (as defined below) immediately and in conformity with these instructions, and will install any necessary patches, defect corrections or new versions from Hexagon. 6.7 Customer is solely responsible for assuring the compatibility of non -Hexagon products with products provided by Hexagon. Hexagon Master Product and Services Agreement Page 35 6.8 Customer is solely responsible for ensuring its systems, software, and data are adequately backed up. Hexagon will not be liable for lost data. 6.9 In addition, Customer shall provide for any other requirements reasonably specified by Hexagon and related to the rendition of the Maintenance Services to be met. 7 EXCLUDED SERVICES 7.1 Maintenance Services for the following are outside the scope of the Maintenance Agreement and may be available under separate agreement at an additional charge (collectively "Excluded Maintenance Services"): • Installation of any Covered Product, Update, Upgrade, or interface software • Network configuration • Configuration or customization of Covered Products to Customer requirements. • System -level tuning and optimization and system administration support • Programming or software development • Training • Maintenance Services required because the Authorized Contact is not available or is not trained in accordance with this Exhibit • On -site Services of any sort • Maintenance Services outside of the regular business hours associated with the applicable level of Maintenance Services • Maintenance Services required due to modifications of Covered Products by Customer except where such modifications are required by Hexagon. In the case of Hexagon software modules which assist in the creation and use of Customer software, the performance of Maintenance Services under the Maintenance Agreement is restricted to unmodified components of these Covered Products. • Maintenance Services required due to use other than in the ordinary manner intended for the Covered Products, or use in a manner that contravenes terms hereunder, or Customer's disregard of the installation and operating instructions according to the documentation provided with the Covered Products • Maintenance Services required due to failure of software or hardware not supplied by Hexagon and not covered in the Maintenance Agreement. • Maintenance Services required due to Customer's use of hardware or software that does not meet Hexagon specifications or failure of Customer to maintain or perform industry standard maintenance on Customer's hardware or software • Maintenance Services required due to software or portions thereof that were incorrectly installed or configured, or use in an environment inconsistent with the support environment specified by Hexagon, or use with peripherals, operational equipment, or accessories not conforming to Hexagon's specifications • Maintenance Services required due to cases of force majeure, acts of God, lightning strikes, fire, or flood or other events not caused through Hexagon's fault. • Customer's failure to materially fulfill the Customer Obligations set forth in this Exhibit • Maintenance Services required due to faulty or incomplete Customer data. 7.2 When ordered by Customer, Excluded Maintenance Services or other software maintenance support services that are outside the scope of the Maintenance Agreement will be billed by Hexagon at the then -current hourly rates and material prices at the time such service is performed. Hexagon Master Product and Services Agreement Page 36 8 SYSTEM SUPPORT TECHNICIAN 8.1 Customer will appoint a minimum of two and a maximum of three contact people who are each authorized to make use of the Maintenance Services ("Authorized Contacts"). 8.2 Customer must make sure that the Authorized Contacts have adequate expertise and experience to make possible a targeted and professionally accurate description of malfunctions and make it possible for Hexagon to handle them efficiently. Authorized Contacts must have successfully completed Hexagon product training or complete it at the next available scheduled opportunity, for those products for which formal training is available. Customer will bear the cost of this training. Customer is obligated to select only those personnel for this task who are suitable for it by means of training and function, and who have knowledge of Customer's operating system, network, and hardware and software systems. Customer agrees to promptly notify Hexagon of any replacement of an Authorized Contact. 9 REMOTE ACCESS Customer will permit Hexagon to electronically access Customer's system via SecureLinkTM SecureLinkTM is a tool for providing secure, auditable remote access to Customer's system in order for Hexagon support personnel ("Customer Support") to effectively troubleshoot critical or complex problems and to expedite resolution of such issues. The Authorized Contacts should be available to assist Hexagon Customer Support as needed during this entire process. Customer Support will only access Customer's system with the knowledge and consent of Customer. For local variances specific to the use of remote access tools other than SecureLinkTM, Customer should contact the local Hexagon support office. 10 THIRD PARTY SOFTWARE 10.1 Support and Updates of Third Party Software shall be provided in the fashion and to the extent or duration that Hexagon is authorized to provide such by the third party manufacturer of the Third Party Software, and such Third Party Software Maintenance Services may be subject to additional terms and conditions of the third party manufacturer of the Third Party Software. 10.2 Maintenance Services and Updates for any Third Party Software that are not listed on the Quote must be obtained from the third party owner of the products or their designated representative. 11 REQUIRED COVERAGE 11.1 Multiple or Interdependent Licenses. Customer may not decline Maintenance Services for individual licenses of a Covered Product for which Customer has multiple copies installed at one site or for Covered Products that are being used interdependently regardless of installation locations, except in accordance with the relinquishment process described in Section 12.2, below. 11.2 Prerequisite Licenses. All prerequisite Hexagon software licenses that are necessary to operate the Covered Products for which Customer desires Maintenance Services under the Maintenance Agreement must also be included as Covered Products and Hexagon undertakes to list these on the Quote. 12 ADDITIONS AND REMOVALS OF COVERED PRODUCTS 12.1 Additions of Covered Products to Maintenance. 12.1.1 Additional Software Products from Hexagon. In the event Customer purchases additional licenses of Software Products from Hexagon during the term of this Maintenance Agreement, Hexagon will provide Customer with a written extension Quote that reflects the additional licenses, the effective date of service, and charges for the additional licenses, pursuant to the Master Agreement. Hexagon Master Product and Services Agreement Page 37 12.1.2 Additional Software Products from a third party. In the event Customer obtains additional licenses of Software Products from an authorized reseller or by any other means, Customer agrees to promptly notify Hexagon in writing about the newly acquired Software Products, and upon receipt of such notice, Hexagon will provide Customer with a written extension Quote that reflects the additional licenses, the effective date on which Hexagon may commence the Maintenance Services with respect to the copies of the Software Product pertaining to the additional licenses, and the charges that would be due in return for these Maintenance Services pursuant to the Maintenance Agreement. 12.1.3 Section 2 shall apply mutatis mutandis to the expansion of the Maintenance Agreement based on the extension Quote(s) submitted to Customer pursuant to the terms of this Article. If the Maintenance Agreement is not expanded based on the extension Quote, then the terms and conditions set forth in this Exhibit regarding reinstatement of Maintenance Services will apply to the additional licenses of Software Products. If, however, the additional Software Products are multiple, interdependent, or prerequisite licenses as described in this Exhibit above, Maintenance Services may not be declined and Maintenance Services and the appropriate monthly charges will begin on the effective date as shown on the extension Quote. 12.1.4 Additional Software Products via Software Transfer Policy. Customer shall purchase Maintenance Services on all additional licenses of Software Products for a site obtained via software license transfer. Any such software license transfers shall be in accordance with the then -current Hexagon Software Transfer Policy and the EULA or other applicable software license agreement delivered with the Software Product. 12.2 Removal of Covered Products from Maintenance. Either party may provide written notice to the other party at least sixty (60) calendar days prior to the end of any Coverage Period of its intent to remove any individual Covered Products from the Maintenance Agreement for the renewal period. Neither party may remove Covered Products except upon Coverage Period renewal. Customer may not remove individual software licenses of a Covered Product for which Customer has multiple copies under Service at one site or for Covered Products that are being used interdependently at a single site unless Customer has first certified to Hexagon on a Software Relinquishment Agreement (to be provided to Customer by Hexagon upon request) that the copies of the Covered Product for which Customer desires to cease Maintenance Services (the "Relinquished Licenses") for the renewal Coverage Period have been uninstalled and removed from its system(s). Should Customer desire to reinstate Maintenance Services for the Relinquished Licenses at a later date, Customer must re -purchase the licenses at the then current list price. 13 PAYMENT 13.1 Terms of Payment. Charges for the Maintenance Services are due and payable annually and in advance. For Customers desiring to pay quarterly and in advance instead of annually and in advance, Customer must request a revised Quote which shall include a convenience fee increase of fifteen percent (15%) of the total annual charges, which convenience fee Customer agrees to pay. The convenience fee shall be prorated and charged to the four quarterly invoices. All charges for Maintenance Services are due net thirty (30) calendar days from the date of invoice or prior to the beginning of the applicable Coverage Period, whichever is earlier. Charges for Maintenance Services associated with Covered Products added during a Coverage Period shall be prorated to the remaining months of the Coverage Period, in whole month increments only, and such charges shall be due and payable in full upon Customer's receipt of invoice. 13.2 Past Due Accounts. HEXAGON RESERVES THE RIGHT TO REFUSE SERVICE TO ANY CUSTOMER WHOSE ACCOUNT IS PAST DUE. At the discretion of Hexagon, Customers Hexagon Master Product and Services Agreement Page 38 who have not paid any charges when due (i) under this Master Agreement, (ii) under any other agreement between the parties, or (iii) under any agreement between Hexagon and Customer's parent and/or subsidiary at least fifty percent (50%) owned by Customer, may not be rendered Maintenance Services until all past due charges are paid in full. The start of the Coverage Period shall not be postponed due to delayed payment of any charges. If Hexagon is required to use a collection agency or attorney to collect money owed by Customer, Customer agrees to pay the reasonable costs of collection. These collection costs include, but are not limited to, any collection agency's fees, reasonable attorneys' fees, and court costs. 14 CUSTOMER WARRANTIES During the Coverage Period, Customer shall commit to the following: 14.1 Subject to Section 12.2 above, Customer warrants that for all Covered Products supported under the Master Agreement, all licenses of a Covered Product for which Customer has multiple copies in its possession and that are located at the site referenced on the Quote, and all prerequisite licenses necessary to operate Covered Products, are listed on the Quote. If all like Covered Products or prerequisite software licenses are not listed on the Quote, Customer agrees to notify Hexagon so that Hexagon may issue a revised Quote to Customer. 14.2 Customer warrants that Maintenance Services provided herein shall be utilized only for the quantity of Covered Products licenses listed on the Quote. 14.3 Customer shall, and Customer shall cause each of Customer's employees and representatives to, comply with each and every term and condition of the EULA and/or SLA applicable to the Covered Products supported under the Maintenance Agreement. IiV2919C7[01[0L6 15.1 United States Government Restricted Rights. If a Covered Product (including any Updates, Upgrades, documentation, or technical data related to such Covered Products) is licensed, purchased, subscribed to, or obtained, directly or indirectly, by or on behalf of a unit or agency of the United States Government, then this Article also applies. 15.1.1. For civilian agencies: The Covered Product was developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with the Federal Acquisition Regulations ("FAR") 52.227-19 (a) through (d) (Commercial Computer Software — Restricted Rights). 15.1.2. For units of the Department of Defense ("DoD"): The Covered Product was developed at private expense and is "commercial computer software" submitted with restricted rights in accordance with the Defense Federal Acquisition Regulations ("DFARS") DFARS 227.7202-3 (Rights in commercial computer software or commercial computer software documentation). 15.1.3 Notice: The Covered Product is "commercial computer software" as defined in DFARS 252.227-7014 (Rights in Noncommercial Computer Software) and FAR 12.212 (Computer Software), which includes "technical data" as defined in DFARS 252.227-7015 (Technical Data) and FAR 12.211 (Technical Data). All use, modification, reproduction, release, performance, display or disclosure of this "commercial computer software" shall be in strict accordance with the manufacturer's standard commercial license, which is attached to and incorporated into the governing Government contract. Hexagon and any applicable Third Party Software manufacturers are the manufacturers. This Covered Product is unpublished and all rights are reserved under the copyright laws of the United States. Hexagon Master Product and Services Agreement Page 39 16 ADDITIONAL TERMS 16.1 Third Party Providers. Hexagon reserves the right to provide Maintenance Services through a third party provider, subject to Hexagon's assurance of performance, and the provider meeting Customer requirements, as applicable to Hexagon. 16.2 The use of Updates is subject to all of the terms and conditions of the EULA or SLA provided with Customer's current version of the Covered Products. 16.3 Upgrades require a full installation and may be provided with a separate EULA or SLA. Any EULA or SLA delivered with the Upgrade may supersede any EULA or SLA associated with prior releases of the Covered Products. It is acknowledged and agreed that allowing an Upgrade to be licensed on the same terms as a prior release may create unintended consequences, such as, without limitation, a failure to bind a user to terms necessitated by new functions or content of the Upgrade; and, that mandating an Upgrade be licensed on terms delivered with the Upgrade may create unintended consequences, such as, without limitation, a heightened risk that new terms may apply to the user without the user's normal diligent scrutiny thereof. It is the expectation of the Parties to formally and expressly agree upon license terms to be applied to an Upgrade; provided that in the absence of express license terms evidenced in writing, an Upgrade shall be licensed on the same terms of the prior release, but subject to such superseding terms of the EULA delivered with the Upgrade as a commercially reasonable software vendor would require in order to accommodate any attributes of the Upgrade which differentiate it from the prior release.) END OF EXHIBIT C Hexagon Master Product and Services Agreement Page 40 EXHIBIT D *41 'd A HEXAGON SAFETY &INFRASTRUCTURE PROJECT DELIVERABLE SIGN OFF FORM CUSTOMER NAME, ANYWHERE USA - PROJECT NAME Submission Date: Month/Day/Year Sign -Off Target Date: Month/Day/year Submitted By: Hexagon Contact Name Submitted To: Customer Contact Name Customer Contract #: Customer Contract Number Customer/Project #: Hexagon Project Number TYPE OF DELIVERABLE ❑ SOW Tasks ❑ Payments ❑ Plans/Designs ❑ Training ❑ Other DELIVERABLE INFORMATION DELIVERABLE DESCRIPTION $AMOUNT OF PYMT THIS SECTION DESCRIBES THE DELIVERABLE (If applicable) With the deliverable described above complete, the Customer shall have ten (10) working days after receipt of a written request from Hexagon, to either sign -off that the deliverable has been met or state in writing to Hexagon the reason the deliverable has not been met. Sign -off of the deliverable shall be based solely upon the deliverable meeting the requirements stated in the Agreement between Hexagon and CUSTOMER NAME dated Month/Day/Year and shall be indicated by the Customer signing the Project Deliverable Sign -off Form. If the Customer does not provide such sign -off or rejection within the ten working day period then the deliverable will be deemed to have been signed off. The signature below acknowledges that the deliverable described in the Agreement and listed above meets all of the appropriate criteria and supersedes all prior requirements for this item. Customer acknowledges completion of this payment milestone according to the Contract Payment Milestone Schedule and provides authorization to invoice this milestone. Authorized Customer Representative Customer Contact Name SIGNATURE DATE Hexagon Master Product and Services Agreement Page 41 HEXAGON SAFETY& INFRASTRUCTURE IrvrERGwAPH LEE COUNTY, FL RFP FOR CAD REPLACEMENT ATTACHMENT 3.4 - EXCEPTIONS TO LEE COUNTY RFP180081 LKD Intergraph Corporation d/b/a Hexagon Safety & Infrastructure (Hexagon) has included RFP text verbatim in bold, italicized font below. Hexagon responses follow in regular text. Terms and Conditions 9. Quality GuaranteeMarranty (as applicable) 9.1. Proposer will guarantee their work without disclaimers, unless otherwise specifically approved by the County, for a minimum of twelve (12) months from final completion. To the extent this section is intended to address the type and level of warranty that is to be provided once the CAD system cuts over to live production, Hexagon agrees to warrant that for one year following cutover the system will operate in material conformity with the specifications. If the County intended for this provision to have an alternate meaning, Hexagon welcomes discussion of such during contract negotiations. 9.2. Unless otherwise specifically provided in the specifications, all equipment and materials and articles incorporated in the work covered by this contract shall be new, unused and of the most suitable grade for the purpose intended. Refurbished parts or equipment are not acceptable unless otherwise specified in the specifications. All warrantees will begin from the date of final completion. Hexagon incorporates its response to section 9.1 above. 9.3. Unless otherwise specifically provided in the specifications, the equipment must be warranteed for twelve (12) months, shipping, parts and labor. Should the equipment be taken out of service for more than forty- eight (48) hours to have warranty work performed, a loaner machine of equal capability or better shall be provided for use until the repaired equipment is returned to service at no additional charge to the County. 9.4. If any product does not meet performance representation or other quality assurance representations as published by manufacturers, producers or distributors of such products or the specifications listed, the vendor shall pick up the product from the County at no expense to the County. The County reserves the right to reject any or all materials, if in its judgment the item reflects unsatisfactory workmanship or manufacturing or shipping damage. The vendor shall refund, to the County, any money which has been paid for same. For 9.3 and 9.4, Hexagon intends to only provide software as part of this RFP process. To the extent the County desires for Hexagon to also provide hardware, Hexagon will welcome further discussion of how that hardware will be supported. Until circumstances change, Hexagon believes this section is not applicable to Hexagon's proposal and proposes it be omitted from the resulting contract. A3.4-1 HEXAGON SAFETY & INFRASTRUCTURE Attachment 3.4 - Exceptions to Lee County RFP180081 LKD 22. RFP — Project Guidelines 22.1. The County has established the following Guidelines, Criteria, Goals, Objectives, Constraints, Schedule, Budget and or Requirements which shall service as a guide to the proposer(s) in conforming the professional services and work to provide pursuant to this Agreement/Contract: 22.1.2. Hourly rates and all other negotiated expenses will remain in effect throughout the duration of the agreement/contract period. As Hexagon must account for increases to labor and other costs, Hexagon respectfully proposes that it only be obligated to maintain the software unit and labor prices for those items listed in the resulting contract for a period of 1 year (software) and 90 days (labor) following contract execution, respectively. 30. Contract Administration 30.2.1. Unless otherwise stated in the scope of work, specifications, or special conditions the default contract term shall be one (1) year with three (3), one (1) year renewals for a total of four (4) years upon mutual written agreement of both parties. Hexagon respectfully proposes the term for the project be the conclusion of the 1-year warranty, (the "Extended Warranty") in lieu of a specific time frame as the project is likely to span multiple years. 30.2.2. The County reserves the right to renew this contract, or any portion thereof, and to negotiate pricing as a condition for each. Reflecting Hexagon's belief that the term of the project should be driven upon completion of the project instead of a set time period and that the resulting contract will be a firm fixed price contract, Hexagon proposes this provision be omitted. 30.4.1. The awarded proposer will be required to execute an Agreement/Contract as a condition of award. A sample of this document may be viewed on-line at http://Www.lee-gov.com/Procurementlforms. Hexagon agrees that if awarded the contract to execute a mutually agreeable contract/agreement. Hexagon respectfully proposes that its enclosed Master Agreement serve as the basis for the resulting contract as it is specifically designed for procurements of enterprise software solutions such as what Hexagon is proposing to license and implement for the County. 30.5.4. Ownership: It is understood and agreed that all documents, including detailed reports, plans, original tracings, specifications and all data prepared or obtained by the successful proposer in connection with its services hereunder, include all documents bearing the professional seal of the successful proposer, and shall be delivered to and become the property of Lee County, prior to final payment to the successful proposer or the termination of the agreement. This includes any electronic versions, such as CAD or other computer aided drafting programs. As a software vendor, a core interest of Hexagon relates to maintaining its ownership of intellectual property it has developed. As this section appears to adversely affect that core interest, Hexagon respectfully takes exception to this section and proposes it own all intellectual property developed by Hexagon and provided to the County. A3.4-2 i/ HEXAGON SAFETY & INFRASTRUCTURE Attachment 3.4 - Exceptions to Lee County RFP180081 LKD 31. Waiver of Claims 31.1. Once this contract expires, or final payment has been requested and made, the awarded vendor shall have no more than thirty (30) calendar days to present or file any claims against the County concerning this contract. After that period, the County will consider the vendor to have waived any right to claims against the County concerning this agreement. Hexagon respectfully proposes this section apply in equal fashion to both parties 37. Special Conditions These conditions are in relation to this solicitation only and have not been included in the County's standard Terms and Conditions or the Scope of Work. From Notice to Proceed or Purchase Order date, whichever applies, JMcalendar days to substantial completion, Mcalendar days to final completion (estimated timeline 365 total calendar days.) Proposal to be based on this timeline. The county reserves the right to negotiate the timeline with awarded vendor. In light of collaborative and dependent requirements of a project of this nature, Hexagon proposes the parties discuss this topic during negotiation to ensure both parties understand the timeline ramifications. Accordingly, Hexagon reserves comments until such time. Detailed Specifications 3. Project Objective 3.4 Go -Live 3.4.1. Provide proper hand-off materials of finished project must be acceptable to the County and meet the County's needs to continue and complete remaining installation, test, cut -over. Materials include but are not limited to, up-to-date detailed project plan including schedules and resources, all contacts (vendor, county, constitutional, etc.), communications plan, product information, warrantee, as -built documentation, and cross -over training, sufficient to allow the existing County team to continue and complete remaining installation, test, cut -over. Hexagon respectfully clarifies that it will provide an electronic copy of its commercial off the shelf documentation to the County, which the County may modify as it deems appropriate and provide to its employees. 4. Payment and Performance Milestones 4.1. Upon completion of each of the following tasks, in the time allocated, application for payment may be made for that item #. Payment applications should not be more frequent than once per month. (TBD shall mean "to be determined" with input from awarded proposer) Timeline may not exceed time specified for this project. Calendar days shall commence upon Notice to Proceed being issued. A timeline, of calendar days, for each milestone shall be established with the awarded vendor. A3.4-3 HEXAGON SAFETY & INFRASTRUCTURE Attachment 3.4 - Exceptions to Lee County RFP180081 LKD 4.2. Acceptance of Project Management Plan 4.2.1. Project Management Plan Acceptance stage is complete when the initial project management plan is agreed upon to the satisfaction of both parties. 4.3. Installation: 4.3.1. Install stage shall mean upon the delivery and successful completion of the equipment installation. (hardware, software, interfaces, etc.) 4.4. Training and Support: 4.4.1. Training stage is complete when all agreed upon training is delivered and materials and tools related to training and support are available to Lee County and its stakeholders. 4.5. Go -Live: 4.5.1. Go -Live stage shall mean that all Call Taking and Dispatching Functions and related interfaces are operational on the proposed system and proposed system is primary system in operation for the County. 4.6. Final Acceptance 4.6.1. Final acceptance stage is predicated on successful completion of Go -Live, 45-day Reliability Test, all deliverables and all trouble ticket items resolved to the satisfaction of both parties. Regarding all items indicated in 4. Payment and Performance Milestones, Hexagon respectfully proposes that during contract negotiations the parties develop mutually agreeable payment milestones based upon the specifically scoped project in lieu of the milestones set forth in section 4. Hexagon also proposes this provision be modified to reflect that Hexagon's right to the milestone payment is not foreclosed upon if the milestone is not completed in "the time allocated." Submittal Requirements & Evaluation Criteria 3. Evaluation Criteria 1. General Company Information 2. Capacity a. Time is of essence for this project; therefore, the successful Respondent must be able to perform the work in a timely manner. Present an outline of the Respondent's current workload, present capacity for additional work, and projected future workload, demonstrating ability to respond to County project requirements and complete by April 2019. While Hexagon is the industry leader and has many ongoing projects, it represents it is able to perform the proposed project in a timely manner subject to the finalization of the resulting contract by April 2018. Hexagon acknowledges the City's request for details about specific Hexagon Customer projects, however, due to customer confidentiality agreements, Hexagon cannot provide specific details being requested. A3.4-4 i HEXAGON SAFETY & INFRASTRUCTURE Attachment 3.4 - Exceptions to Lee County RFP180081 LKD Proposal Cost Form 1A Draw Schedule Items Draw Schedule based on the following. I Project Management Plan Acceptance: 80% of line item #1 2Installation: 80% of line item #2 3 Training: 80% of line item #3 4 Go -Live: 80% of line item #4 5 Final Acceptance: 20% of line item 14. 100% of line item #5 Alternate(s): Paid as indicated by Unit of Measure and/or as negotiated Hexagon agrees to include a mutually agreeable payment milestone schedule in the resulting contract. Hexagon proposes that payment milestone schedule, which does not include retainage, be developed during contract formation in lieu of the included draw schedule reflected in the RFP and pricing forms. A3.4-5 HEXAGON SAFETY & INFRASTRUCTURE fi�RAPH TAB 4 - RESPONSE TO FUNCTIONAL SPECIFICATIONS MATRIX Note: Hexagon respectfully clarifies that regarding answers marked "Alternate", the detailed explanations are included in the "Explanations" column cells that apply to those particular requirements; therefore, a separate numbered addendum to the end of each tab section is not necessary for the "Alternate" items as part of this response. Both a PDF version of the matrix response and an Excel version of the matrix response are included on the flash drives for the County so that each matrix tab's answer column may be easily filtered, if desired. a� } O z a m c a Q c o _ 0 - 'o � p a a 3 o c Y a O 2 0 a)_ a) co —m CF 3 > o O_ — N c N .2 cu 'Na) C Y _ a) C N L C •• N N ) C C C a) O > V p Z a) _T a) C a) E _T m o N C y- Y m 3 Y N C O C a C O a)C d U U E T N U C m a) E a) YCOL C-O C N a a) C O a) C m Y — N N O) E ° C_ c .T O m a) a a N c a N a) O p U (p C O D_ N C C Y O p C O — C C O C .r — c N C a c a) a C N a) o c a) a Y a o E a) c m o v_ c E E o U C N O d C O m '= N a) a) Mn U N C C U O N C p N N O T a) a)c Y> a) U a1 ()� -O a)a1 a) C— N a1 — L I -C C T C O Y 0 m C O a1 t+ m m a w C a) E j U O o a y a) a) C o w a a) Y C C a) a) L N C C C L T U Y �EO°7E�,NL�E�� C m T m — a7 cc C ca r ID a)W U c'op �7 0 E a) a) y Y a7 a1 0 L p N C N a) E a) a) m C O U y C CU O > y O O L a) p N L Y N C C C— E _ � (6 _ C C_ E c E +L-' N C >. E U o O a)3 O O N> N a N a �p y N C_ c a o m m y0_ C a) r N c a O `O a) C N E > ° a) a) L °a -07o E o w aN 3 CE m E a E c� c 0 m a a c o OQ >, c O> y y U >. a) C ,o 3 C- a) a1 (U a) C c ..2 O T C (6 to w c o) 0 3: -0 N o - mom c o m 0 Y m a o a) m ff o a E m a a) w �° C E'° o y y Y E a) o a! a aa) N T a C v o °- o) 3 C C a) y o a) •• o U Q p N vT, r '� tC.• a a) O C_ N p a C H a) a) al C_ O a) U O w E a > O_ O NO J L a Q a)a) C •O U C C_ .0 O a) y — L U O a) m U N C C a) L a) p a) a a) N a) G~ L` C O O O a) O w 0 y v N p a N o Y N>> a`>-$Z.9 -07a) pa)2m:5:5< a°H N M &O co h 00 Z O O O O O O O O O O O O O O O O W Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Mandatory Requirements Number 1-001 1-002 1-003 1-004 1-005 1-006 1-007 1-008 1-009 1-010 1-011 No responses will be entered on this page. Each response will be provided in the section/question noted to the right and will auto fill into this form. This page is only a summary of the responses provided. Response Explanation Note: These are Mandatory Requirements. Responses not meeting these requirements, other than "Yes", may not be move forward for evaluation. System must be able to interoperate with Priority Dispatch Pro Q & A (See 8- Yes The I/Dispatcher product interfaces with Priority Disp Pro Q & A tab forparticulars) The calltaking component shall be ProQA Paramount -Platinum certified with Yes Hexagon is currently Priority Dispatch ProQA Param the Multi - Disci line Launcher. The ProQA interface shall automatically insert the initial PDS case information into the CAD Incident upon send and immediately be viewable to the CAD Yes The information sent from Paramount to CAD is imm users. Information entered into the case after dispatch shall be automatically copied Yes Afterthe initial event is created and the ProQA case over to the CAD incident and immediately viewable to the CAD users. The system will support a multi-agency/jurisdiction model for both Emergency Yes I/CAD is a multi-agency/jurisdiction CAD system. Medical Services and Fire -Rescue districts. Response recommendations shall be AVL closest unit, run card, or combined Yes Hexagon interprets the term run card to mean a list o dependinq on the incident type and primary agency. The system will have the ability to recommend units based on defined cross - district boundaries or stay within district boundaries depending on the rules of Yes When building a response plan, the County may use the agencies. The system will assign a unique incident number to each incident. Yes Hexagon's CAD system assigns a unique incident nu Lee Control supports a multi -agency closest unit, cross boundary response method for the fire services as well as a separate near county wide AILS transport service. The medical service and fire service will each need an Yes what agencies attend a specific event is determined incident sent to their respective Dispatchers with their own unique sequential run number. Associated incidents shall receive all remarks and updates regardless of which incident is updated without additional actions or keystrokes to be taken by the Yes Hexagon has included development services in our p Operator 1-Mandatory Requirements 5-130 8-001 8-022 8-010 4-217 4-218 4-216 3-052 4-215 3-072 2 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Mandatory Requirements Number 1-012 1-013 1-014 1-015 1-016 1-017 1-018 1-019 1-020 No responses will be entered on this page. Each response will be provided in the section/question noted to the right and will auto fill into this form. This page is only a summary of the responses providec+ Response Explanation The system shall be compatible with or account for interfaces with VIPER® Yes Hexagon considers this interface to be accounted for version 5.1. The system shall be compatible with or account for interfaces with Yes Hexagon considers this interface to be accounted for PowerPhone® version 6.1. The system shall be compatible with or account for interfaces with MapFlex® Yes Hexagon considers this interface to be accounted for version 2.1. The proposer shall have a plan to incorporate Next Generation 911 standards Yes Hexagon is actively working on its vision to deliver I/ into the proposed system. The system shall utilize a Microsoft Windows 2012R2 or newer server Yes Microsoft Server 2016 is the proposed operating syst operating software. The system shall operate within a VMWare 6.x and VMotion environment. Yes The proposed configuration utilizes VMware ESXi 6.x The system shall utilize Microsoft SQL 2014 or higher. Yes Microsoft SQL 2016 is the proposed/required databa The system shall support the Microsoft SQL AlwaysOn offering. Yes Hexagon clarifies that SQL Server 2016 Enterprise is The system is compatible with ESRI software. Yes Hexagon clarifies that ESRI file formats are supporte 5-262 5-263 5-264 5-265 10-042 10-043 10-045 10-046 6-331 1-Mandatory Requirements 3 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-cno-ene-i ve ansrzon Item CAD General Response Explanation Number 2-001 e system should ave an Emergency or Overtlow queue to stack calls when emergency responders are unable to or at reduce response levels. (Such as during a hurricane). This queue is separate from the primacy pending event queue. There should be a switch to activate the queue and shunt incidents to it automatically while letting the Call Taker override The I/CAD solution does provide for the ability to place events on and send to primary pending. At the end of the emergency period Telecommunicator should HOLD, thus removing them from the pending queue. does not 2-002 be able to release all or some of the incidents based on a criteria to the primary pending No overflow have the ability to support separate emergency ovew pending queue. There should also be the capability to have 'overflow' Telecommunicators work the incidents independently,close, assign or release to primary g p ry pending. Every CAD workstation queue. should have to ability to activate and use the Overflow Queue depending on the Telecommunicators needs. This queue will not be workstation based, but rather the same across the entire system The time, position ID number, User ID number, and CAD mode (live or training) shall be Hexagon clarifies that the time appears in the status bar, the user ID 2-003 displayed discreetly in the work area at all times while a workstation is logged on. No appears in the title bar. The live or training environment will be denoted based on the VM the user is accessing. Hexagon respectfully clarifies that Hexagon's response parameters are not guarantees of specific performance criteria as many factors outside of Hexagon's control can influence the System's performance. Forthe/CAD subsystem, performance standards are based on the following assumptions: - The I/CAD System is configured and maintained according to Hexagon recommendations for workstation, system, and application Under all conditions the system response time shall not exceed 2 seconds measured from the configuration, as well as for database maintenance 2-004 time a Telecommunicator completes a keyboard entry to the time of full display of the system No -Anti-virus scanning software installed by the NWCDS on the response at any position where a response is required. (NFPA 1221: 10.6.4`) I/CAD System must be configured according to Hexagon's Best Practice Guide for Anti -Virus Settings for CAD - Minimum network speed between I/CAD Database Server#1 and I/CAD Database Server#2 = 100Mb/sec -A maximum average round-trip latency exists (as measured by "ping") of <_ 10ms between I/CAD Database Server#1 and I/CAD Database Server #2, and <_ 30ms between call taker/dispatcher workstations and the database servers Fields that are updated should be highlighted the first time they are pulled up for review by any Hexagon clarifies that I/CAD shows updated data with colored text, the 2-005 workstation. Alternate color of which is configurable by the County. The fields are not highlighted. 2-CAD-General 4 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-CAD�e .i ver: 8r1512o17 Item CAD General Response Explanation Number The I/CAD system and its associated mobile client, Mobile for Public Safety, store configuration information in a multitude ofways. Some configuration information is stored in the form database tables such as static data, I/CAD parameters, and the visual environment (GUI). Other parts of configuration are stored as XML, XSL, ASP, or other files stored locally on a mobile laptop, web server, or application server. Hexagon has proposed a TEST system which can be used to test any of the user defined configurations prior to deploying them to production. The method in which the configuration is deployed to 2-006 Changes to user defined configurations shall have the ability to be staged and then activated Alternate production will vary depending on the type of configuration done and on a manual or scheduled command transparent to the user. where that configuration information is stored. In all cases, the configuration change could be done manually or on a scheduled basis using a variety of methods like PowerShell scripting, etc. It is not possible to state that all configuration changes will be transparent to the user. Some configuration changes may require users to restart their application (such a GUI changes), others may require the user to refresh their application to obtain new settings (such as a parameter change). In no case are there configuration changes which must be deployed to production without being tested in a pre -production environment first. 2-007 The CAD Incident will have a single tracking number and the ability to make copies of the Yes System default functionality. The user is the sys admin user incident to be sent and acted on different workstations as configured by the user. 2-008 The keyboard function keys will be configurable to system commands Yes System default functionality with configuration. This configuration is included in the standard implementation services proposed. 2-009 Provide the ability to open multiple sessions using the same user login. No The I/CAD solution does not permit a single user account to be logged into multiple alications. Provide a system that allows for customization to the display interface by agency and also System default functionality with configuration. This configuration is 2-010 allows for different field selection and modification to extract data according to the agency's Yes included in the standard implementation services proposed. needs. 2-011 Provide a system that allows queries for active calls and closed/history calls by any field. Yes System default functionality - Event Search 2-012 The system must provide at least 9 levels priority for field response. Yes System default functionality 2-013 The system must allow multi agency responses with minimal keystrokes required. Yes System default functionality 2-014 Provide a system that provides an automatic syntax -help display for command line functions. No Hexagon clarifies that the command line is defined in the command topic of the help. Provide a system that allows browse -based "view only" access to incident and unit This feature is provided I/NetViewer which is included in the Hexagon 2-015 summaries, as well as incident data, which prevent the user from having "dispatch Yes proposal to the County. capabilities", for use b administrative staff. 2-CAD-General 5 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-cnD�e .l ver: 8r15r2017 Item CAD General Response Explanation Number Provide a system which supports dispatch by closest/best route by using the nearest address System default functionality -Beats, AVL, Closest unit using ESZs in 2-016 and events in proximity and provides updating and selection of street segments, response Yes conjunction with map data districts, and countyboundaries. Provide a system so -designed as to give immediate access to CAD incident data upon The I/CAD solution uses Microsoft SQL Server to store all event and 2-017 completion (closing) of "active" incidents by means of non-proprietary, industry -standard Yes unit related data. This data is available for query purposes in near real - applications & methods, or equivalent user approved vendor -supplied conduits. time via read-only SQL Server AlwaysOn asynchronous replica. 2-018 Provide the ability for CAD data and AVL data to be integrated in one display. Yes The I/CAD map display simultaneously shows CAD data for events and units, and updates units locations based on incoming AVL data. The system must allow the freeing up a workstation, mobile device by remote logging off a Hexagon would like to clarify that remotely logging off an application is 2-019 Alternate limited only to the Mobile for Public Safety (MPS) clients. I/Dispatcher, user. NetViewer, and clients cannot be remotely logged off. The system must allow System Administrators to define text appearing on menu buttons Hexagon clarifies that the Agency must purchase the Advance I/CAD 2-020 based upon agency terminology and/or preference. Yes System Administration course to facilitate the necessary skills required to make these modifications. Hexagon understands this requirement to mean using our applications to see the resulting work production from call takers and dispatchers in The system must allow the monitoring of the work of Call Takers and Dispatchers in a real real time, such as seeing a new event created by a call taker, or 2-021 time manner. Yes seeing the result of dispatching units to an event by a dispatcher. There are no facilities in the I/CAD solution to "see" in real-time the call taker or dispatchers screens for things like monitoring what they type, or what they view, etc. 2-022 At the application level, the system shall secure access to the following: 2-023 . CAD commands. Yes System default functionality 2-024 . Function or hot keys. Yes Hexagon clarifies that access to function and hot keys is controlled by what command is assigned to that function or hot key. Hexagon clarifies that access to individual interfaces is sometimes controlled via command class assigned to a user account. For 2-025 . Individual interfaces. Alternate example, the ability to access the (/Informer interface to query names and license plates is controlled via command class, but the ability for users to see AVL data provided by the I/Tracker interface has no controlled access. 2-026 IThe following search functions must be supported: 2-027 1 . Search for string and use of wildcards. Yes System default functionality using the W Idcard "W symbol 2-CAD-General 6 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-CAD�e .i ver: 8n5121317 Item CAD General Response Explanation Number Hexagon clarifies a e term a used in the oun y s requiremen is too broad. Given the varied and wide ranging search options the I/CAD solution provides, it is not possible to provide a Yes response to this requirement. Hexagon would like to stipulate that our search abilities are robust and geared to the job functions of each application. 2-028 • Search capability for all formatted fields. Alternate The I/Dispatcher application used by communications center personal is more robust and has more search options that those search facilities provided by the Mobile for Public Safety (MPS) client, and MPS has more search facilities than our hand held mobile client, Mobile Responder (optioned). It is our belief that our search functions are tailored in such a way to meet the needs of end -users of the system exagon can 10ilhat the term a used In the oun y s requirement is too broad. Given the varied and wide ranging search options the I/CAD solution provides, it is not possible to provide a Yes response to this requirement. Hexagon would like to stipulate that our search abilities are robust and geared to the job functions of each application. 2-029 • Search capability for all text fields, (including all original and supplemental narratives). Alternate The (/Dispatcher application used by communications center personal is more robust and has more search options that those search facilities provided by the Mobile for Public Safety (MPS) client, and MPS has more search facilities than our hand held mobile client, Mobile Responder (optioned). It is our belief that our search functions are tailored in such a way to meet the needs of end -users of the system hagpd on their role Hexagon understands this requirement to be asking for the ability to search a field or fields based on a True or False value. The I/CAD 2-030 • Boolean Values Supported (separately or in combination). Alternate applications used by end -users do not provide this type of search feature. The InSight Reporting products being proposed do support Boolean search features. The system shall provide the user with a highly integrated set of application modules offering The user interfaces with product groupings (those products used by 2-031 a consistent user interface in order to minimize user training and system administration. Yes communications center personnel, by field personnel, by administrators, by report writers) all maintain a similar user experience. 2-032 The system shall provide command line as well as screens forms for user entry. Yes Hexagon would like to clarify that a command line only exists in the I/Dis atcher product. All commands should be entered in a user defined order without the need for special System default functionality with minor configuration. This 2-033 command identifiers. For instance, a command to Enroute a unit might be entered in as 1A11 Yes configuration is included in the standard implementation services EN. Where 1A11 is the unit ID and EN is the user defined status for Enroute. proposed. 2-CAD-General 7 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-cnD�—.i ver: 8n5i2017 Item CAD General Response Explanation Number Hexagon clarifies that a command keyin (EN in the County's example) Commands should be entered in any order. For instance, the above unit status command and the unit ID (1A11 in the County's example) or the event number 2-034 could be entered in as 1A11 EN or EN 1A11. Yes can be keyed in any order (EN 1A11 or 1A11 EN) but all other command parameters are fixed in their order, and that order is determined by the ountV during configuration workshops. 2-035 The user shall be able to enter a command on the command line without disturbing operations Yes System default functionality in the work areas. 2-036 The system shall utilize an "intelligent command line" such that it will prompt the user for valid No Not currently supported formatting of the command. 2-037 The system shall provide standard GUI items like drop down menus to make selection easier Yes System default functionality for frequently used fields such as incident types, disposition codes, agency Us. The system shall support pre -fill fields in appropriate pre -formatted screens, eliminating 2-038 redundant data entry. For instance, a specific agency might want the city field to be always No Not currently supported filled in. 2-039 Quick entry methods shall minimize the keystrokes required to perform incident initiation, Yes System default functionality incident dispatch, and unit status changes. 2-040 The system shall provide the user with standard editing capabilities at a minimum to include: 2-041 . Cut Yes W ndows functionality, CTRL+X 2-042 . Copy Yes Windows functionality, CTRL+C 2-043 . Paste Yes Windows functionality, CTRL+V 2-044 . Cut/Copy/Paste between forms Yes Windows functionality Hexagon would like to clarify that very little information in the I/CAD 2-045 . Delete Yes solution can be deleted. Information that is removed is generally only marked as deleted in the database to prevent it from being visible, but the data remains in the database. 2-046 . Sort Yes Hexagon clarifies that only in those forms and displays that contain multiple columns of information, is sorting supported. 2-047 . Insert Yes System default functionality -Windows based platform 2-048 . Print screen Yes System default functionality -Windows based platform 2-049 . Tab through the form fields Yes System default functionality -Windows based platform 2-050 . Back -tab through the form fields Yes System default functionality -Windows based platform 2-051 . Move windows Yes System default functionality -Windows based platform 2-052 . Resize windows Alternate Hexagon would like to clarify that not all windows present in all I/CAD applications can be dynamically resized by the operators. 2-053 . Find No Not currently supported 2-054 1 . Replace No INot currently supported 2-055 1 . Ability to use the numeric keypad for number entry Yes System default functionality -Windows based platform 2-CAD-General 8 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-cno�ene.i ver: 8r15r2017 Item CAD General Response Explanation Number 2-056 . Ability to use an external numeric keypad for number entry Yes System default functionality -Windows based platform 2-057 . Point and click Yes System default functionality -Windows based platform 2-058 . Drag and drop Yes System default functionality -Windows based platform 2-059 . Drop -down lists Yes System default functionality -Windows based platform 2-060 . Vertical scroll bar, when the vertical display is larger than the defined area Yes System default functionality -Windows based platform 2-061 . Word wrap, when the horizontal display is largerthan the defined area Yes System default functionality -Windows based platform 2-062 . Word wrap configured with line breaks between words, not within words Yes System default functionality -Windows based platform 2-063 . Ability to engage spell check on narrative fields as selected by an operator No Not currently supported 2-064 Users shall have the ability to move forward and backward to complete data fields. Yes System default functionality 2-065 When hovering the mouse over a command or field a tooltip should: 2-066 . appear naming or explaining it No Not currently supported 2-067 . have defaults values No Not currently supported 2-068 . be user configurable No Not currently supported 2-069 . have the ability to be turned off or on per user No Not currently supported 2-070 Users shall be able to correct command line errors using edit keys and resubmit the Yes System default functionality command without having to put the cursor at the end of the command. 2-071 The system shall provide the user with standard form navigation. Yes System default functionality - Windows functionality 2-072 The cursor shall return to the first position of the first field following completion of a command No The I/Dispatcher cursor returns to the command line after a command line function. is successful executed. 2-073 The CAD user interface shall provide the ability to handle the variety of transactions that a Yes System default functionality Dispatcher must handle almost simultaneously. 2-074 The CAD work areas shall operate independently —a command or function in one area should No Not currently supported not disturb the command or function in the other area. 2-075 The system shall support multiple command lines. Yes System default functionality 2-076 The system shall support multiple work areas. For instance, the Call Taker should be able to Yes System Default Functionality -Add Event Dialogue/Delete Event have two or more incident initiation forms displayed at the same time. Dialo ue The system shall support a split screen capability that provides the display and use of multiple The solution, specifically the I/Dispatcher application, is a separate work areas and command lines on a single or multiple monitors. These work areas Windows based software application. It behaves in a manner shall operate independently and allow the user to perform the same or separate functions consistent with other Windows applications the County may be familiar 2-077 from each area. Alternate with. I/Dispatcher supports an unlimited number of command lines and an unlimited number of (/Dispatcher Event Information Forms. These command lines and Event Information Forms, based on our understanding of a work area as used in this RFP, constitute work areas in I/Dis atcher. 2-CAD-General 9 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-CADS—.i ver: 8r1512o17 Item CAD General Response Explanation Number The user shall be able to move easily from one work area to the other via the mouse or Consistent with our description of the work environment provided in 2-078 keyboard. Alternate item 2-077, users can move between command lines using the mouse or function key, and between I/Dispatcher Event Information forms using the mouse command line or function key. Hexagon would like to clarify that command line functions are not 2-079 The user shall have a choice of using keyboard, mouse, or a combination to enter all data, Yes always fully executed solely on the command line. There are many commands, and functions. command line entries that simply begin a process by invoking a form, and require form completion to fully execute. 2-080 The system shall allow multiple CAD functions to be in progress at the same time. Yes System Default Function - CAD commands can be tied to produce multiple results while doing functions in the background The system shall allow the user to enter a command, then move to another work area or Consistent with our description of the work environment provided in command line and submit another transaction, then return to the previous function and item 2-077, users can move between command lines without affecting 2-081 resume where they left off Yes the contents of the command lines, thus allowing them to begin one command, move to another command line and complete a command, and return to the previous command line to complete command entry and execution. 2-082 The system shall have available formatted screens for initiating database inquiries. Yes System Default Functionality - Various 'search' dialog and 'inquiry' dialog functions available as delivered The system shall handle errors in a consistent manner with the display of a clear english System Default Functionality with configuration option -A message 2-083 message that indicates the problem. Yes box displays failures and success will appear in the bottom frame of the main Dispatch window Ifthe error was generated due to a failed command line entry, the operator can use the up arrow to return to the failed command, make 2-084 Yes revisions and resubmit. If the error was generated due to invalid data in form, the form will not dismiss and will remain displayed allowing the The system shall provide editing capabilities for correction of errors. operator to make the necessary edits to allow form submission. 2-085 The system shall automatically place the cursor on the field in error and display a descriptive No Not currently supported error message when errors are encountered within a data entry form. 2-086 The system should be able to recall multiple incidents with one click. No Not currently supported 2-087 the system shall support combined Call Taker/Dispatcher functions at a single workstation. Yes System default functionality based on user permissions 2-088 the system shall support separate Call Taker/Dispatcher functions at separate workstations. Yes System default functionality based on user permissions The incident definition will include a discrete field for a matching NEMSIS\EMSTARS Code. Hexagon assumes this is a list of custom codes that will be provided 2-089 This code will be attached to the incident record for later reporting or passing to an agency's Yes by the County, chosen by operators at event creation, and stored in the RMS I/CAD database. The proposed standard implementation services support this. 2-CAD-General 10 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-cno-ene-i ve ansrzon Item CAD General Response Explanation Number Hexagon assumes this is a list of custom codes that will be provided 2-090 The incident definition will include a discrete field for a matching NFIRS Code. This code will Yes by the County, chosen by operators at event creation, and stored in the �support be attached to the incident record for later reporting or passing to an agency's RMS I/CAD database. The proposed standard implementation services this. 2-091 2-092 The system shall support user -defined windows or monitor sets for dynamically updated views Yes System supports various user profile layouts that can be changed by of ongoing incident, unit, and interface activities operator. The status monitor shall allow the user to page via keystrokes or utilize the mouse to scroll to Hexagon would like to clarify that the dynamic unit and event status subsequent screens to view more incidents or vehicles than will fit on a single window monitors support scrolling. Operators may scroll using the mouse and 2-093 Alternate the scroll bar, the mouse scroll wheel (if present), or by clicking once in the list of monitor contents and using the arrow keys to move up and down through the dis play. 2-094 Incident monitors shall be able to display active/pending incidents by area and incident status. Yes System default functionality set by agency. Hexagon would like to stipulate that operators may position available The status monitor shall support the ability for System Administrators, groups, or each windows at their discretion. Within the unit and event status monitors, 2-095 individual to configure the layout of the workstation screen(s), depending on the number of Yes operators may control the column order, sort order, column widths, monitors at the workstations, so workstation windows for pending queues, active units display, and font size of the text. Operators may not add columns that are not active incidents, etc., are not "hard -coded". re- ro rammed to be available. Hexagon would like to stipulate that these settings must be decided 2-096 Yes and agreed upon by the agencies using the system. They cannot be The status monitor shall make use of color, sound (.audio files), and flashing in addition to controlled by individual operators. The user is defined as the sys textual information to enhance status recognition. These assignments shall be user -definable. admin 2-097 Yes System default functionality all columns are ascending descending Filtering and sort order of data shall be configurable per monitor set. sortable. Hexagon clarifies that context menus (menus that appear when right 2-098 Yes clicking on a row of data) are configurable and are chosen by the CAD commands and functions shall be programmable as mouse functions uniquely for each County during the configuration phase of the project. Individual users individual status monitor. cannot make these choices. 2-099 The mouse functions shall support setting default values (for example in building common Yes System allows for mouse functions to support default values and when status changes) or prompt the user to enter a value. needed prompt userto enter a value 2-100 When using the mouse functions within the status monitor the functions shall use the unit ID Yes System default functionality, when using mouse acts on previously or incident the user has selected and not require them to re-enter this data. selected unit or incident. 2-CAD-General 11 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-cno-ene-i v— a1srzn11 Item CAD General Response Explanation Number Hexagon clarifies that the column content of the dynamic unit and event status monitors is decided upon by the County during the 2-101 Yes configuration workshops. Individual users may hide existing columns the user shall be able to select the fields, the length of the fields, and the order of the fields to but they may not add columns that are not already present. We be displayed when configuring a status monitor. interpret the term length to be the width of the column. 2-102 2-103 The system shall have the ability to send and receive messages to: 2-104 • Personnel. Yes System default functionality 2-105 • Workstations. Yes System default functionality 2-106 • Predefined groups (all users, all personnel in zone, etc.). Yes System default functionality 2-107 • Any combination of user -defined groups, such as personnel, workstations, and MDCs. Yes System default functionality 2-108 • Either individuals or specific devices. Yes System default functionality 2-109 The messaging system shall be an internal part ofthe CAD system. Yes System default functionality The system shall support the creation of dynamic messaging groups (i.e., when users sign on, Hexagon would like to stipulate that message groups of this type are the system shall determine what groups they are members of, based on rules that are static groups. The agency may build any number of message groups managed by the System Administrator or Designated Users s). they wish, and the members of those message groups can be 2-110 Alternate personnel, terminals, pagers, stations, other groups, or any combination thereof. There are dynamic message groups in the I/CAD solution. The members of those dynamic groups change based on system status, but the County cannot add additional dynamic groups. The system should have the ability to send notification and recurring messages. Messages Hexagon would like to stipulate that scheduled messages can be sent 2-111 should be able to be defined for sending a prescribed number of times per hour, day, week, or Yes at a minimum of once every minute. mo nth. 2-112 The system shall support unlimited logging of messages. Yes System Default Function - Messages are stored in the system and can be retrieved at any time 2-113 The system shall support the ability for users to: 2-114 • Create free -form messages. Yes Default Send Message function supports freeform messages . Display messages via a single command Hexagon would like to stipulate that messages in I/Dispatcher are displayed in a Message Monitor which looks very much like an email 2-115 Yes inbox. The message monitor may be displayed with a single command, but messages must be selected to see the content of the messa e. This selection is via mouse click. 2-CAD-General 12 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-CADS—.i ver: 8r1512o17 Item CAD General Response Explanation Number • Have audible and visual signaling of received messages. System Default Function - Located on the System Information Toolbar, 2-116 Yes the Message indicator button notifies operators when a new message has been received. Audio can be configured by system administrator 2-117 • Forward, reply to, and delete messages. Yes System Default Function - CAD Message Monitor • Send certified mail (i.e., sends an automatic message back to the sender when the mail Hexagon would like to stipulate that in I/CAD this type of message is is opened). called a Critical message. When a critical message is sent and then 2-118 Yes viewed by the recipients, the sender is notified via a message acknowledgement. It is important to note that `every` recipient in group messages will send this acknowledgement. 2-119 • Send priority messages. Yes System Default Function - Send Message Dialog Priority drop down or Command Line SM with additional options The system shall allow messages to be routed to any system printer. Hexagon would like to stipulate that any message may be printed to 2-120 Yes any network printer configured to be accessible by the receiving terminal. Messages in I/NetViewer are printed via standard web browser rint functions. The system shall differentiate between CAD messages and messages returning from the Hexagon assumes the "switch" to mean messages from a remote 2-121 message switch. Alternate database inquiry. Those messages are routed to our I/Informer client (optioned) which is entirely separate from the I/CAD messaging function. The system should allow messages to be added to an incident history Hexagon would like to stipulate that this is by standard windows copy 2-122 Yes and paste functionality. Operators would copy the desired text from a message and then past that into the remarks entry form. 2-123 The system should allow messages to be sent from the command line Yes System Default Functionality - Default command line SM with additional options 2-124 The system shall allows messages to accept attachments. Yes System Default Functionality - Send Message dialog box The system shall support a central Address Book for storing contacts, businesses and Hexagon would like to stipulate that the I/CAD address book is used numbers to be used to address messages and look up information only in send message and broadcast functions and lists only 2-125 Alternate destinations available to I/CAD such as personnel configured for access to I/CAD, terminals configured to run I/CAD, stations configured in I/CAD with a printer, or pagers defined in I/CAD. Personnel shall be automatically added to the address book for access to emergency contacts Hexagon stipulates that personnel added to I/CAD are automatically 2-126 and numbers Alternate part of the address book, but emergency contacts for those personnel must be accessed via the Who command, and are not part of the address book. 2-127 The system shall support the creation of multiple address books No Not currently supported 2-128 The system shall support assigning security to address books No Not currently supported 2-129 The system shall support the creation of custom fields for address book entries No Not currently supported 2-CAD-General 13 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-cno-ene-i ve ansrzon Item CAD General Response Explanation Number 2-130 The system shall support searching address books from a form and command line No INot currently supported 2-131 The system shall support key word searching for address book entries No Not currently supported 2-132 The system shall support attaching documents and hyperlinks to address book entries No Not currently supported 2-133 Messages can be sent from a single workstation to all other workstations and mobile devices. Yes Default system functionality The system can send automatic email event notifications using email lists based on agency, Hexagon stipulates that this function is part of the I/Page product and 2-134 location, and event type. Yes requires that the County provide access to an SMTP gateway for the sending of emails from I/Pa e. The system can send automatic text event notifications using lists based on agency, location, Hexagon stipulates that this function is part of the I/Page product and 2-135 and event type. Yes requires that the County provide access to an SMTP gateway for the sending of emails from I/Pa e. 2-136 Messages can be sent and received by any addressable parameter (e.g., personnel name, Yes System default functionality user ID, unit ID). Hexagon stipulates that this function is part of the I/Page product and requires that the County provide access to an SMTP gateway for the The system can send Short Message Service (SMS) and Multimedia Messaging Service sending of emails from I/Page. All SMS and MMS messages are sent 2-137 (MMS) messages to 1 G-digit "non -carrier specific" phone numbers. Yes via the devices email address. For example, a Verizon wireless device with a phone number of 555-555-1212 would have an email address of 5555551212@vtext.com -the ability to natively send SMS and MMS from I/CAD does not exist. The system sends a message to user -definable social networking websites. This message will Hexagon would like to clarify that this function is possible with a 2-138 simultaneously be logged in the event history. This function can be restricted by role, user ID, No customer interface, but is NOT included in this proposal. Hexagon and workstation. welcomes to the opportunity to further define the County's needs in this regard. Hexagon would like to clarify that this function is possible with a 2-139 The system allows the agency to send a message to a social networking website and restrict No customer interface, but is NOT included in this proposal. Hexagon by user ID. welcomes to the opportunity to further define the County's needs in this regard. 2-140 Messages are displayed in a separate area dedicated to messaging. Yes System Default Functionality -The CAD Message Monitor lets you read and respond to a message sent to your workstation. 2-141 Messages, both sent and received, are displayed using the word wrap feature without word Yes System Default Functionality -The CAD Message Monitor lets you break. read and respond to a message sent to your workstation. 2-142 Receipt of messages does not interfere with CAD functions (e.g., call taking, dispatching). Yes System default functionality 2-143 Pop up messages do not cover the active work area. No It is possible for pop-up dialogues or messages to cover parts of the area being used by an operator. 2-CAD-General 14 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-cno-ene-i ve a1sizn11 Item CAD General Response Explanation Number An operator is notified of the receipt of a message with an audible (optional through system System Default Function - Located on the System Information Toolbar, 2-144 configuration) and visual alert. Yes the Message indicator button notified when a new message has been received. And audio via system administrator setup 2-145 Messages can be designated as urgent by the message sender. Yes System Default Functionality - Based on Priority of message Hexagon would like to draw a distinction in functionality for purposes of clarity. Administrative messaging, using the I/CAD Send Message Messages can be designated as urgent by the system when the message contains a pre- functions do not support this requirement. However (/Informer is our 2-146 established keyAlternate word (e. g., gun, knife, hazmat). product that queries local, stated, and federal databases for license plates, names, articles, etc. I/Informer has been optioned in the response. Should a "hit' be returned to I/Informer via these queries, it can be configured to be a higher priority return. Hexagon would like to draw a distinction in tunctionality tor purposes o clarity. Administrative messaging, using the I/CAD Send Message functions do not support this requirement. However (/Informer is our 2-147 Messages can be designated as urgent by the system when the message contains a pre- Alternate product that queries local, stated, and federal databases for license established phrase (e.g., threatened crew). plates, names, articles, etc. I/Informer has been optioned in the response. Should a return contain a keyword, as defined by the County, those words are highlighted in the return but the priority the return is not chan ed. 2-148 A message can be designated as urgent, which will enable that message to be placed at the Yes System Default Functionality - Send Message Dialog, select Critical or top of a message queue fora particular workstation. via command line with other options 2-149 The message notification alert can be defined by the agency. Yes Hexagon clarifies that the alert is a colored button, colored text, and visual alteration of the message in the list of waiting messages. The system allows all unread messages associated with a workstation to be deleted using a Hexagon stipulates that to delete all messages operators must first 2-150 single command. The deletion of a message does not remove the log entry. Yes select all messages in the list using CTRL+A or a combination of mouse functions and use the delete button. 2-151 2-152 The system stores and tracks user, operational, and field personnel associated with the CAD Yes Default event and unit tracking and status logging in the system system. Hexagon stipulates that I/CAD permissions are based on command 2-153 The system associates CAD system access and operational security rights with the personnel Yes class. Every command in the system is assigned a command class. record. Operators are then assigned one more command class, thus defining what system functions the have access to. 2-154 At a minimum, the following data is associated with the personnel record: 2-CAD-General 15 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-CAD�e .i ver: 8/1512o17 Item CAD General Response Explanation Number 2-155 . Employee ID Yes System Default Functionality - Personnel - Complete dialog in CADDBM 2-156 . Unit ID Yes System Default Functionality -Once Personnel information is created, can the be assi ned to a Unit ID 2-157 . Telephone number Yes System Default Functionality - Personnel - Complete dialog in CADDBM 2-158 . Emergency contact information Yes System Default Functionality - Personnel - Complete dialog in CADDBM Hexagon will configure a custom column to store this information in 2-159 . Shift assignment Yes our personnel (persl) table. The proposed standard implementation services include this configuration. 2-160 . Special skills Yes System Default Functionality - Personnel Complete dialog in CADDBM - Skill list created in CADDBM and offered in drop down list Hexagon stipulates that I/CAD permissions are based on command 2-161 • CAD functional security information (e.g., password history, allowed functions, allowed Yes class. Every command in the system is assigned a command class. module access). Operators are then assigned one more command class, thus defining what system functions they have access to. 2-162 . Email Address Yes System Default Functionality - Personnel - Complete dialog in CADDBM 2-163 . Status -Active or Inactive Yes System Default Functionality - Personnel - Complete dialog in CADDBM Hexagon stipulates that this information is stored as a terminal named 2-164 . Status - On -Duty or Off -Duty Yes that the operator would be logged into, should they be on duty. This information is viewed via the Who command within all products. The I/CAD personnel (persl) table stores a creation data for a 2-165 . Start Date Yes personnel record (persl.cdts), but this data is not modifiable by the County. 2-166 . End Date No Not currently supported 2-167 . User Name Yes System Default Functionality - Personnel - Complete dialog in CADDBM 2-168 . First Name Yes System Default Functionality - Personnel - Complete dialog in CADDBM 2-169 . Last Name Yes System Default Functionality - Personnel - Complete dialog in CADDBM 2-170 . Middle Initial Yes System Default Functionality - Personnel - Complete dialog in CADDBM 2-171 . Suffix Yes As part of the last name field. 2-CAD-General 16 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-cno-ene-i ve a1srzn11 Item CAD General Response Explanation Number 2-172 Personnel data records are searchable from all CAD workstations (e.g., rolodex) based on the Yes Hexagon stipulates that this is access via the Who command. security ofthe user. 2-173 The system supports a central unit table for the creation of unit IDs. System Default Functionality - Unit Definition dialog in CADDBM to 2-174 Yes create and maintain DB records for the units belong to each agency defined. The agency can create and maintain unit types. System Default Functionality - Unit Types maintained in CADDBM can 2-175 Yes define the list of unit types applied to units when they are defined, logged on updated and recommended 2-176 At a minimum, the following data is associated with the unit record: 2-177 . Agency ID Yes System Default Functionality - Unit Definition dialog in CADDBM Hexagon clarifies that vehicles are created as separate entities from 2-178 . Vehicle ID Yes units. When a unit is logged into service, the vehicle being used by that unit is defined. This relationship can also be defined in advance via a Lineup. 2-179 . Unit ID (no less than 4 characters) Yes System Default Functionality - Unit Definition dialog in CADDBM 2-180 . Permit ID No Not currently supported 2-181 . License ID No Not currently supported 2-182 . Model No Not currently supported 2-183 . Make No Not currently supported 2-184 . Year No Not currently supported 2-185 . Resource No Not currently supported 2-186 . Category No Not currently supported 2-187 . Kind No Not currently supported 2-188 . Component No Not currently supported 2-189 . Type Yes System Default Functionality - Unit Type dialog in CADDBM 2-190 . Other No Not currently supported Hexagon stipulates this as a unit attribute. There are 255 unit 2-191 . Minimum Capabilities Yes attributes that can be configured by the agency to represent capabilities. Hexagon clarifies that this is a calculated value based on the number 2-192 . Number of personnel assigned to the unit Yes of people logged into a unit. This value can be displayed in unit status monitors if desired. 2-193 . Personnel assigned ID Yes System Default Functionality -Vehicle Definition / Unit Definition dialog n CADDBM 2-CAD-General 17 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-cno-ene-i ve mii-rill Item CAD General Response Explanation Number 2-194 . Push -to -talk ID Yes System Default Functionality -Vehicle Definition / Unit Definition dialog in CADDBM 2-195 . Mobile device ID Yes System Default Functionality -Vehicle Definition / Unit Definition dialog in CADDBM 2-196 . Radio talkgroup No Not currently supported 2-197 . Special equipment Yes System Default Functionality -Vehicle Definition / Unit Definition dialog in CADDBM 2-198 . Area designation Yes Hexagon stipulates that this is the units beattstation assignment def unit.lev3 Hexagon stipulates that a beat can be defined as having a zone 2-199 . Zone designation Yes assignment. When a unit is assigned to that beat, the zone assignment is im lied. 2-200 . Home assignment Yes Hexagon stipulates that this is the units station assignment def unit.station 2-201 . Controlled/Uncontrolled No Not currently supported 2-202 . Notes No Not currently supported 2-203 The system supports the ability to assign an unlimited number of capabilities to a unit. Alternate There are 255 unit attributes that can be configured by the agency to represent capabilities. 2-204 2-205 The system allows an event disposition code to be added to an event on event closing. Yes System default functionality. 2-206 The disposition code can be a required parameter depending on the event type. No The I/CAD disposition codes are a cumulative list and are valid for all event -types. 2-207 The disposition codes are created and maintained by the respective agency. Yes System Default Functionality 2-208 Remarks can be added to the disposition entry by an operator. Yes System Default Functionality 2-209 Disposition codes have to be related to the event type. No The I/CAD disposition codes are a cumulative list and are valid for all event -types. 2-210 The system can restrict the addition of a specific disposition code based on event type. No The I/CAD disposition codes are a cumulative list and are valid for all event -types. On closing an event, the system can send a request to the unit or officers mobile device to If a disposition code is required for an event -type, the operator cannot 2-211 add the event disposition. Alternate close the event or the last unit cannot clear the event until at least one valid disposition code has been provided. 2-212 Multiple disposition codes may be associated with an event (e.g., event, transported). Yes System Default Functionality 2-213 The system supports the ability to add unlimited dispositions per incident. Yes Default system functionality 2-214 The system allows the entry of an event disposition before closing the event. Yes Default system functionality 2-CAD-General 18 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 2-cno-ene-i v— ansrzon Item CAD General Response Explanation Number Hexagon clarifies that events (by type) can be configured to require a disposition code. If multiple units are assigned to an event, and one 2-215 The last unit cleared from an event requires the declaration of an event disposition. Yes unit clearing the event provides a disposition code, the last unit clearing will not be required to provide a disposition code, but always has the option to do so. System Default Functionality - Disposition Codes IF set as required, will pop up the form it not entered on command line. If NOT required, event may be cleared without one, but the end user has the ability to 2-216 A disposition can be required for an event based on nature code, by agency. Yes always add one. If restricted, they would be restricted to the entire command and not by each event type / signal code as requested here within. 2-217 The system can auto -generate a case number based on disposition as determined by an Yes System Default - Can also be configured to prompt for Case Number agency. at Clear Event/Unit commands An event disposition may be changed after the event is closed by an authorized user. The 2-218 operator ID and workstation ID of the person adding the disposition to a closed event is Yes System Default - Change Disposition Code Command recorded. 2-CAD-General 19 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 3-Call Taking Ver: 8/15/2017 Item Number Call Taking Response Explanation 3-001 3-002 3-003 3-004 3-005 3-006 3-007 3-008 3-009 3-010 3-011 3-012 3-013 3-CalFaking The system shall import and attach/append,automatically upon phone pick Hexagon has proposed our standard Ani/Ali interface up or user command, automatic number information (ANI) and automatic Yes (included as part of the CAD system) to meet this location information ALI to a call for service. requirement. The system should import (automatically) external alarm data that conforms to the APCO/CSAA (Central Station Alarm Association) published ANS; Yes Hexagon has proposed our EdgeFrontier interface to ASAP. and, [The system shall/The system should] generate a call for service upon recempt of a new alarm notification The system shall import (automatically) a call for service received from Hexagon has proposed EdgeFrontier CAD -to -CAD interfaces another CAD system. Yes required to import calls from other CAD systems as indicated in this response (Spillman, Motorola TriTech OSSI . The system shall import (automatically) a call for service generated on an Yes Calls generated on MDTs automatically update into system. MDC. The system should import and attach/append information received from an Hexagon would like to clarify that this type of interface may be Automatic Crash Notification (ACN) or Advanced Automatic Crash No possible, but is not currently included in our proposal. We Notification (AACN) system to a call for service welcome the opportunity to further clarify the requirements with the County - The system shall allow the Call Taker to alter or change any information Alternate Hexagon stipulates that remarks, once entered, cannot be imported into the call for service changed. The system shall allow for System Administrator defined CAD incident types Yes Hexagon system allows the CAD system administrator to or nature codes. define CAD incident tVpes nature codes The system shall allow a the same incident type code to be used across all Yes Hexagon system allows use of same incident type code to be agencies and service types. used across all agencies and service types. The system shall allow system users to modify the incident type and provide Hexagon system allows system administrative users to modify new/updated response plan information/suggestions based on the new Yes incident types and provide new /updated response plan incident type. information/suggestion based on the new incident types The system shall provide the capability to create an event, assign a unit, and close the event with a disposition without going through the dispatch Yes This is the Accept Closed Event function in CAD. process steps. The system should provide the capability to flag a call for service as an "Information Yes This is the Accept Advised Event function in CAD. Only -No Dispatch" separate from the incident type/nature code. The system shall enable the user to enter supplemental (new) information Hexagon's CAD system allows users to enter new information into the call for service event record of one or more user specified CAD Yes into the call for service record or records. events. The system shall display a notification of the event update at each Hexagon stipulates that event update notifications are made appropriate CAD position whenever an active event record is updated, as Yes to all terminals running I/Dispatcher with the specific events determined by the s stem's configuration. agency and dispatch group in cover mode. 20 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Number 3-014 3-015 3-016 3-017 3-018 3-019 3-020 3-021 3-022 3-023 3-024 3-Ca[Faking Call Taking 3-Call Taking Ver: 8/15/2017 Response Explanation The system should have a configuration to determine if update flags should No Event types do not support being flagged as exempt from be displayed based on incident type updates. The system shall create an automatic time/date stamp for every transaction related to an event, and shall/should store the responsible Yes Default system functionality Telecommunicator's identification (ID), the console ID, and the nature of the chance. The system shall audit records to the event history or store audit records in Hexagon stipulates that this audit type data is stored the CAD system's audit log file in chronological order; and, the system shall Yes 1 multiple tables of the I/CAD relational database, but all data 1 provide a complete historical audit of all event activity e. p p y ( g., comments, unit can be related back to the event. status chances, license plate information field updates). The system shall store old entry information, with the appropriate date, time, All time stamps are stored and kept in chronological order, Telecommunicator ID, and console stamps if the new entry replaces existing Yes including the newer updates and the original data. information in the event record. The system shall enable the audit information to be retrieved and printed in Each iteration of an event and its associated data can be both summary and detailed formats when incident information is displayed. Alternate displayed, but there is only one print style for that information. It is not summary vs. detailed. The system shall create a permanent audit trail for all information recorded Hexagon has permanent audit trail for all information related tc related to an event, whether or not that information is later modified or Yes deleted. event. The system shall support ease of entry for supplemental event information Yes Add event remarks function and the Add supplemental data and changes to existing event information. Ifunctions. The system shall allow the user to display a supplemental data entry screen Yes Data entry screen can be displayed by specifying the event or by specifying either the event number or a unit assigned to the event. unit assigned to the event. The system shall allow the user to display a data entry screen to change Data entry screen can be displayed by specifying the event or information previously entered into a CAD event by specifying either the Yes unit assigned to the event. event number or a unit assigned to the event. The system shall provide agency definable visual and audible alerts to notify exas s I a e au I eat s or field units and other appropriate CAD system users, including users of fa to only gone . events fall into only two categories. There are either standard systems interfaced to CAD such as Mobile Data computers, of event event updates and notifications emergency event updates changes and supplemental information. The use of these alerts will be Alternate and notifications. The agency may decide what color the alert configurable based on incident type, scene safety, or Telecommunicator buttons should be, and they may define what audible alert is discretion. played. These are the only types of configuration that are The system shall allow the user to add supplemental information and/or Yes I Hexagon allows users to add supplemental information and/or I change active events. update active events. 21 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Number Call Taking 3-025 3-026 3-027 3-028 3-029 3-030 3-031 3-032 3-033 3-Call Taking Ver: 8/15/2017 Response Explanation The system shall allow the user to update any field in the call for service does not allow operators to change remarks once they event record (except user designated fields, such as application generated are entered, nor can they can change any of the original times and date stamps, Telecommunicator identification information, No date/time stamps. Operators may add a manual time but it is ANI/ALI information, and CAD position that completed a CAD transaction). stored in addition to the original date/time - not a replacement The system shall document all changes and supplemental information in the Yes Hexagon Event Chronology function event history. Hexagon stipulates that the screen to create an event is the The system shall provide an event update/change data entry screen. Yes same screen used to update/change an event. It is referred to as the I/Dis atcher Event Information window. The system shall allow the user to update or change a unit's most recent Select active event function can use any unit currently event by entering the unit's identification or any unit that is currently Yes assigned to an event. If unit is no longer active on event then assigned. the Display Event function will pull up Unit and last event it was assned. on y a ows e addition o remar s, case number The system should require confirmation from the user when attempting to assignment, and addition of disposition codes to closed update any field in a closed event. No events. No other information is allowed to be changed on a closed event. Users are not warned that they are adding information to a closed event - The system shall if configured provide the user with acknowledgement that I/Dispatcher provides an operator feedback area in the lower an update to a CAD event record was successfully completed. Yes portion of the I/CAD mainframe. This unobtrusive feedback area will show successful completion of commands. The system shall allow the user to supplement and/or change active events. Yes Hexagon system allows user to supplement and or change active events The system shall allow the user to supplement and/or change any field of a The system will allow user to supplement comments, and closed event without having to change the state of the event. No disposition of a closed event without changing state of the event. Any other fields require the Reopen Event function. Besides times mentioned elsewhere the call taking process shall record the Hexagon stipulates that I/CAD stores the event start following times: First Keystrokes/Data Import, Location Verification, Incident Yes date/time. This is defined as the date/time of the first send to dispatch (accepted) keystroke in the location line or the selection of an event -type, whichever occurs first. 3-CallTaking 22 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Number Call Taking 3-034 3-035 3-036 3-037 3-038 3-039 3-040 3-041 3-042 3-043 3-044 3-045 3-Call-Faking 3-Call Taking Ve 8/15/2017 Response Explanation purpose of providing a way for the Priority Dispatch key questions and answers along with the determinant code into Besides times mentioned elsewhere the call taking process should record the event remarks as well as setting an event -type, sub -type, the following times: Time into PSAP (9-1-1), Pick Up Time, ProQA process No and alarm level based on the determinant. I/CAD does not started, ProQA process ended, Phone Hang Up record the start and end of Priority Dispatch cases. That information is stored in the Priority Dispatch database and is related to the I/CAD event by the Priority Dispatch case Phase two wireless locations shall automatically appear on the Call Takers Yes Hexagon has proposed its Ani/Ali Interface to meet this map when loaded into the calltaking form requirement. This is included as part of I/Executive-HA. Other addresses shall appear on the Call Taker's map at location Yes Hexagon displays on the calltaker map at location verification, verification regardless if the call is accepted or not. call does not need to be accepted The system shall automaticly or manually (configurable) verify an Hexagon verifies address/location on entry in call taking from address/location (match to geofile) on entry to the call taking form, before Yes before entering call accepting the call. The minimin information needed to create an incident shall be characters in Yes Hexagon minimum for event is location information, and valid the address field and valid calltype. call type. The system shall allow for the by passing of the location varification process Yes Hexagon system allows for creating event at unverified in the creation of an incident location. The system should have the ability to receive and respond to Text Hexagon would like to clarify that this type of interface is Messages and automatically copy a transcript of the conversation to the No possible, but is NOT included in our proposal. We welcome incident record the opportunity to further clarify the requirements with the County. The system shall have the ability to receive and respond to TDD and Yes Hexagon has proposed the I/TDD interface for this automatically copy a transcript of the conversation to the incident record requirement. The system should have the ability to receive and respond to Internet based Hexagon would like to clarify that this type of interface is verbal/messagingprograms i.e. Sk a and automatically co a transcript p g ( yp) y copy p No possible, but is NOT included in our proposal. We welcome n of any written conversations to the incident record the opportunity to further clarify the requirements with the County. The system shall have the ability to identify duplicate calls before the current Yes Hexagon's Duplicate Call functionality identifies potential call is accepted duplicate calls before call is accepted The system shall have the ability to display information about any premises or location based on information available to the system before the current Yes Hexagon Location of Interest functionality call is accepted The system shall have the ability to display any previous incidents at an Hexagon Location of Interest functionality includes Premise address or location before the current call is accepted. This shall be Yes history configurable by call type and time frame. 23 if 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Number 3-046 3-047 3-048 3-049 3-050 3-051 3-052 3-053 3-054 3-055 3-056 3-057 3-CallTaking Call Taking 3-Call Taking Ver: 8/15/2017 Response Explanation The system shall be Phase II Wireless 9-1-1 Compliant. Yes Via the ANI/ALI interface shall handle ALI input in any NENA format. Yes Via the ANI/ALI interface exagon s Ipu a es that the location description Is a location comment and is added to the location entry area by a colon shall allow for entry of an Incident location, caller location and a location Alternate delimeter. For example 100 W MAIN ST: THIS IS A HOUSE - description, all in separate fields. everything after the colon is a comment and stored in a separate field of the database but is not entered or displayed ppnprq exagon s Ipu a es Ma e oca Ion description Is a location comment and is added to the location entry area by a colon The system shall provide a location description field that is free -form. Alternate delimeter. For example 100 W MAIN ST: THIS IS A HOUSE - everything after the colon is a comment and stored in a separate field of the database but is not entered or displayed The system shall allow for multiple incident close dispositions Yes Hexagon system supports multiple incident close dispositions. The call for service intake form shall have a method of flagging scene safety Yes Hexagon stipulates that this is the I/CAD special situation information for any incident. functionality. shall assign a unique incident number to each incident Yes Hexagon's CAD system assigns a unique incident number to each incident. The system shall allow each agency to define whether its incident numbers Hexagon allows system administrator to define whether are automatically reset daily, monthly, or yearly. Yes incident numbers are automatically reset daily, monthly, or earl Incident numbering formats should be user -defined. For instance, one Hexagon support agency defined formats that can differ in agency might want the incident number formatted as "year -month -day- Yes sequence number" and another agency might want "day -sequence number" sequence. The incident number should have the ability to support the Julian Date in the No This is not currently supported. format. The system shall automatically detect and assign the appropriate source of the call for the following instances: 9-1-1 call; Field initiated incident (radio); Yes Hexagon Call source field displays the listed sources of the mobile client initiated incident; Alarm interface -text message; internet; other call CAD system The system shall automatically transfer the ALI reporting party location field The operator must manually choose to spill the ALI data into into the incident location field on the incident initiation form if the user does No the event information form unless the Auto ANI/ALI parameter not enter an incident location is enabled. 24 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Number 3-058 3-059 3-060 3-061 3-062 3-063 3-064 3-065 3-066 3-067 3-068 3-069 3-CaIFFaking Call Taking 3-Call Taking Ver: 8/15/2017 Response Explanation The system should support the definition of an unlimited number of incident Yes Hexagon does not limit the number of incident types in the types in the incident a database. database The incident type field shall be long enough to hold all MPDS incident types Hexagon stipulates that the event -type is fixed at 16 including suffixes Yes characters and cannot be increased. The sub -type is fixed at 16 characters and cannot be increased. The system shall allow the use of the same incident call type code across all Yes Hexagon support same incident type code across all agencies agencies and service types and service es. The system shall afford the user the ability to select an incident type from a Yes Hexagon supports ability to select an incident type from a dro drop -down menu available from the initiation form down menu on the Event initiation form. The system should allow the incident type configuration to specify that only No All disposition codes are available for all event -types. certain dispositions are valid for a specific incident e. e oca Ion ot Interestunction checks or prior If an address is validated, CAD shall automaticly checks and flag for events at all validated locations and provides notification to previous incidents that have occurred at the location. If present, previous Yes the operator that prior events exist. The notification is in the incidents must display in a separate work area so as not interrupt the form of a colored button. Operators click the button when Incident workflow. they are ready to view the prior event information so as not to The system should support an expandable comments field that dynamically The remarks control can be configured during implementation grows to a reasonable level if more text is entered than can be displayed on No but once determined, that size is fixed and not operator the screen. configurable and does not grow or shrink based on content. The system shall allow the transfer of pending incidents from one Yes Hexagon supports transfer of pending incidents from one Dispatcher to another. dis atcher to another. exagon s Ipu a esthat any number OT operators may be viewing an event and entering new remarks, supplemental The system shall not limit the number of users that can review and update a Yes persons and vehicles, but only one operator may have an single incident at the same time event in update mode at one time for changing key items such as event location, event -type, sub -type, calling party infornnntmon The system shall have the ability to clone incidents. Incident cloning allows for the creation of cloned (or linked) incidents after a parent incident has Yes This is the I/CAD copy event function. been created. Each cloned incident shall have its own incident number. Yes On Hexagon system each cloned incident has its own incident number Cloned incidents must maintain the current date and time as well as the date and time of the original incident, for the purposes of reporting incident No Copied events have their own creation date/time stamps response time data. 25 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Number Call Taking 3-070 3-071 3-072 3-073 3-074 3-075 3-076 3-077 3-078 3-079 3-080 3-Ca[Faking 3-Call Taking Ver: 8/15/2017 Response Explanation The system shall have the ability for Call Takers to manually enter Hexagon system allows for creating an event at unverified area/zone information in unverified incidents or overwrite them in verified Yes location Call takers can manually enter Area/Zone incidents The system shall have the ability to associate previously unrelated incidents (i.e. two incidents are entered that are found to be the same call for service. Yes This is the I/CAD cross reference command. One is associated to the other, copying all the information over, then one can be closed while the other is left o en. Hexagon has included development services in our proposal to support the functionality indicated in this requirement (i.e. t Associated incidents shall receive all remarks and updates regardless of cover for standard default columns and any custom columns which incident is updated without additional actions or keystrokes to be Yes that may get added). Location and event -type changes should taken by the Operator be added as remarks to the cross-referenced events. Via the Server Command utility for CAD, all remarks and caller information will be propagated to the cross-referenced events. If multiple incidents are created when multiple agencies respond to the Hexagon supports associated incidents across multiple same call for service these incidents will show as associated and share all Yes incidents. information The system shall support incident creation from the command line, creation Hexagon stipulates that from the map, only the initiation of form, and from the mapping application via a point -and -click or drag -and- Yes location verification can be done. The remainder of event drop method. creation must be completed via the form. The incident initiation form should be customizable to order fields and Hexagon Incident creation form is configurable by System present only those fields that are needed for the Division of Public Safety's Yes Administrator to match agencies business process. business rocesses. The system shall perform a check for duplicate incidents once the location Yes Hexagons Duplicate Call functionality can identify potential has been verified duplicate calls at address verification The system shall check incidents for duplicate calls based on a true radius Hexagons Duplicate Call functionality uses radius search in search in a user -definable distance from a coordinate in the geographic Yes system admin defined distance from coordinate in the area ofthe incident being initiated. aeoaraDhic area ofthe incident being initiated. The system shall have the option of searching closed as well as open calls Yes Hexagons Duplicate Call functionality can optionally search f for a duplicate check. closed as well as open calls for a duplicate check. Hexagons Duplicate Call functionality identifies potential The system shall display potential duplicate incidents in a separate work Yes duplicate calls before call is accepted. In a separate window. area so as not to cover the Incident form or interrupt the Incident workflow Operator must via keyboard, mouse of function key select duplicate or not before acceptona call Onto system - The system should have the ability to immediately display potential duplicatE Yes Hexagons Duplicate Call functionality display at address incident information during the incident entry process verification and or at when accept event 26 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 3-Call Taking Ver: 8/15/2017 Item Number Call Taking Response Explanation 3-081 KII1k3'% 3-083 3-084 3-085 3-086 3-087 3-088 3-089 3-090 Hexagon stipulates that operators may add an apartment CAD shall provide subcomponents of an address (suite, front/rear, etc.). Yes number (5 characters), building number (5 characters), and location comment 80 characters to the event location. exagon s Ipu a es a opera ors , no UL the apaltillelli. an building as part of the location using delimeters.. The comma (,) is used to delineate an apartment, and the semi -colon (;) is Suite/apartment number should be contained in its own field Yes used to delineate a building. Apartment must be entered first, following by building. For example, 100 W MAIN ST,12;B would be 100 W MAIN ST building B, apartment 12. Building ID should be contained in its own field Yes Hexagon system has own field for Common Names (Building Ids Floor number should be contained in its own field Alternate Hexagon stipulates that floor would be stored as a location comment using the colon delimeter. Hexagon clarifies that the County must provide a GIS polygon Subdivision should be contained in its own field Yes feature that contains the names of all sub -divisions so this information can be stored in a custom field via the I/CAD of on attributes feature. Room should be contained in its own field. Alternate Hexagon stipulates that room would be stored as a location comment using the colon delimeter. Any searches done by CAD by address shall use both the street address Yes Hexagon system supports use of both street address and apt and apartment number to determine a direct hit or nearby hit number in address verification rocess a re I Is perorme vla e p one sys em, when up a e ANI/ALI data is delivered to I/Dispatcher the Ani/Ali and Loc 9-1-1 Rebid requests shall not overwrite the call received or phone pick up Call buttons highlight. If the operator wishes to only update Yes the location information, they click the Loc Call button. If the time stamp. operator wishes to fully spill all new ANI/ALI data, they click the ANI/ALI button and confirm their choice via the pop-up ncidents shall have the ability to be scheduled to come due at a future fate/time Yes Feature supported. 3-Ca[Faking 27 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Number Call Taking 3-091 3-092 3-093 3-094 3-095 3-096 3-097 3-098 3-099 3-100 3-Ca[Faking 3-Call Taking Ver: 8/15/2017 Response Explanation eAccept Scheduled event does not allow for specifying a unit for the event to be assigned in the case of Incidents shall have the ability to be scheduled by unit ID Alternate creating a single scheduled event. However, accepting an event and then placing that event on hold for a specific unit is supported. If the Agency is creating a recurring scheduled Scheduled Incidents not yet due shall be able to be displayed in their own Yes Hexagon system has a held filter which can display upcoming window scheduled events in separate window. When a Scheduled Incident becomes due it should have the option to Hexagon's system supports moving the scheduled event to appear in the pending window. Yes the pending display at due time. This is performed automatical no o tion exist for this not to occur When scheduling a due time the CAD system will check and inform the Call No Functionality not available Taker if there are an other incidents scheduled near that time. The due time of a Scheduled Incident shall be able to be changed after the Yes Hexagon system supports editing of scheduled events due incident is created time after event is created. Hexagon assumes this IS the scheduled even There will be a reminder given to the CAD workstation responsible for functionality. Scheduled events are held in a special status assigning the scheduled incident a user defined time before the incident Alternate until a defined period of time before their due time. At the tim becomes due. the event becomes due the event is placed into the covering dispatchers pending queue as a new event. In this fashion It he ccep c e u e even oes no a ow or specifying a unit for the event to be assigned in the case of The system allows a unit to be automatically assigned to a scheduled event. Alternate creating a single scheduled event. However, accepting an event and then placing that event on hold for a specific unit is supported. If the Agency is creating a recurring scheduled Hexagon stipulates that unit assignment to a scheduled event The system allows for a unit to be manually assigned to a scheduled event. Yes is only possible after the event has transitioned from scheduled to pending. If a unit is automatically assigned to a scheduled event, the system requires No Not currently supported an acknowledgement from the unit to acknowledge the new status. The system allows scheduled events to occur on a recurring basis. Yes Hexagon system schedule event function allows operator to define events on recurring basis. 28 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-001 4-002 4-003 4-004 4-005 4-006 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation I/CAD can recommend units via Beats/Backup-Beats which is often referred to as "station order" recommendations. It can also recommend via street network, which is determining the best route for a unit The system will have the ability to recommend a blend of AVL closest units Yes or units to the event. The best route can be either the and non-AVL equipped units based on station or post to fill out a run card. shortest distance or the fastest time. There is a default recommend method set for the given agency/dispatch group. The default method can be overridden in the response plan for any given requirement group thus supporting a blended recommendation mode. When viewing the list of recommended units the operator can choose to dispatch all recommended Dispatch recommendations can be either accepted, modified, or refused by units, use the mouse to de -select some recommended the Dispatcher; Dispatchers may elect to assign vehicles without requesting Yes units, or ignore the recommendation altogether and a recommendation dispatch units manually. In addition the operator can add specific units to the recommendation or add an additional entire response plan (ad -hoc response plans) Ability to base unit recommendations based for definable calls based on a Yes Unit Recommend functionality and Response plan combinations of user definable factors (See below for must have factors) editor Ability to base unit recommendations based for definable calls based on a Yes Unit Recommend functionality and Response plan combination of workload calls & standbys) editor e response planning feature is extremely robust. The County defines requirements, and then Ability to base unit recommendations based for definable calls based on a Yes places requirements into groups, and groups into a combination of Unit / Personnel Capabilities response plan. A requirement can consist of unit type, vehicle equipment, unit attributes, personnel skills, or e response p anning feature allows theCounty' Ability to base unit recommendations based for definable calls based on a to define a maximum tolerance for distance, time, or combination of Travel Cost of Unit Location to Incident Yes beat(station) depth that when exceeded causes the requirement group to fail thus employing a travel cost from unit location to event. 4-Dispatching-Cmd & Control 29 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-007 4-008 4-009 4-010 4-011 4-012 4-013 4-014 4-015 4-016 4-017 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation Provide a system which supports dispatch by closest/best route by using Hexagon does not fully understand this requirement the nearest address and events in proximity and provides updating and No and seeks clarification on what the County desires in selection of street segments, response districts, and county boundaries. the form of "updating selection of street segments, response districts and county boundaries" System Default Functionality - will be logged and if The System will track unit recommendations for an incident Yes System remarks are turned on, will show in the remarks area of the event and in the chronology The System will track unit recommendations for an incident and show if the System Default Functionality - will be logged and if Recommendation was used including Telecommunicator Name & Position Yes System remarks are turned on, will show in the remarks area of the event and in the chronology The System will track unit recommendations for an incident and show if the System Default Functionality - will be logged and if Recommendation was modified including Telecommunicator Name & Yes System remarks are turned on, will show in the remarks Position area of the event and in the chronology The System will track unit recommendations for an incident and show if the Recommendation was not used including Telecommunicator Name & Yes This is a configuration option Position e recommend unit service has a defined unit Dispatch recommendations should be based on the capabilities present search area. The recommend search area can be within all agencies or a single agency, thereby allowing a multi -agency Yes Dispatch Group, Agency, Zone, or Loaded. This allows response if necessary the County to determine where units can be found to fulfill the re uirements in a response plan. When a call has been held in pending for x amount of time (variable based on original priority) the system will increase the priority of the incident, by a No Not currently supported user determined amount, to move it up in the pending queue Have the ability to track non -call related tasks, such as stand bys, special Yes I/CAD Out of Service codes details, on duty training and report on them. Track and report on where and what a unit was doing when dispatched to a Yes I/CAD Unit History call. on standby, in station, available in district, etc: Have the ablility to issue Agency specific Report Numbers either by one per Yes Based on agency needs, this may require the use of incident or one for each unit dispatched CAD Server Commands to issue case numbers. Have the ability to recognize a foreign unit (not a member of the primary Based on agency needs, this may require the use of agency for an incident) and automatically issue a Report Number for that Yes CAD Server Commands to issue case numbers. unit's agency. 4-Dispatching-Cmd & Control 30 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-018 4-019 4-020 4-021 4-022 4-023 4-024 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation Hexagon stipulates that MaxDistanceTo Recommend The AVL search radius for recommendable units shall be configurable Alternate parameter is a fixed value for the system, and is not based on agency, area and/or incident type. 9 Y, Yp configurable per event type orgeographic area, but is 9 p Yp configurable bv a enc . The system shall route an incident based on the agency, type of incident, When va i a es a location a coordinate is and its location. From this information, CAD determines the proper obtained. Via a point -in -polygon process that jurisdiction and agency. The incident is then routed to the appropriate coordinate is determined to be in an ESZ (emergency position(s) covering the area that the incident resides in. Yes service zone). That ESZ is configured to be in a given agency and dispatch group. Based on that agency and dispatch group assignment, the event is routed for handling to the terminal(s) that have cover access for in The system shall be able to route to all positions signed on to cover the en va i a es a a i ocon a coordinate is area of response, or positions covering the override area. More than one obtained. Via a point -in -polygon process that Dispatcher, as well as Dispatch Supervisors, must be able to monitor the coordinate is determined to be in an ESZ (emergency various activity or calls at any time. Yes service zone). That ESZ is configured to be in a given agency and dispatch group. Based on that agency and dispatch group assignment, the event is routed for handling to the terminal(s) that have cover access for When a properly formatted dispatch command is entered on the command line, the ENTER key is the A single key shall be used to dispatch a unit or units to an incident when Yes only key necessary to dispatch the units. For example: the specified incident number and unit or unit ID's are typed on the D,E1234,E1 E2 E3 -would cause Engines 1, 2, and 3 to command line. be dis atched to event number E1234. A single key shall be used to retrieve the oldest, highest -priority incident in the user's pending queue and display the dispatch recommendation form. Yes System Default Functionality - As requested by agency An Incident Dispatch form shall provide the means to display and dispatch Yes System Default Functionality - Event Information Dialog recommended units. The system shall support the ability to dispatch additional units to an System Default Functionality - Hexagon delivered incident from the command line, and incident dispatch form, or using drag Yes COTS features and drop functionality. 4-Dispatching-Cmd & Control 31 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-025 4-026 4-027 4-028 4-029 4-030 4-031 4-032 4-Dispatching-CMD & Ver: 8/15/2017 Control Response Explanation The dispatch recommendation shall be configurable to display both available and unavailable units in the response area of the incident. Unavailable units shall be highlighted with an identifier or by color -coding to Yes Hexagon stipulates that unavailable units are denoted indicate that they are busy but recommendable. The system shall allow the in the recommend unit list by the unit status column. dispatch recommendation feature to be disabled system -wide, if an agency If the dispatch recommendation is acceptable, the units should be able to Hexagon stipulates that the recommend unit display be dispatched with a single keystroke. shows all units required to fulfill the response plan associated with the events agency, event -type, and sub - Yes type. When the recommendation is displayed (on - demand) the operators click the OK button to dispatch all units, or press the enter key, with focus on the recommendation window, to dispatch all selected units. The Dispatcher shall be able to override the system's unit recommendation. System Default Functionality - Can override within the Yes Unit Recommend Dialog or manually on the command line Only units on duty shall be recommended for dispatch. Yes System Default Functionality The system shall support alternate dispatch recommendations for different System Default Functionality - combination of Define types of crisis modes (severe weather, special events, etc.). Yes Condition dialogue, Response Plan in CADDBM. And Preset deployment plans for predefined crisis modes The system shall log the recommendation displayed for the user in the Yes System Default Functionality incident's history. Units recommended for an incident shall be based on the geographic area Yes System Default Functionality of the incident the incident type, and the units' capabilities. If AVL is available, the Dispatcher shall have the option of using an AVL Inclusive of the Hexagon response to requirement 4- (closest unit) recommendation or a geographic area recommendation. 001, the operator can change the recommendation mode in real-time using the options radio buttons on the Yes Recommend Unit display. The choices are Beats (Station Order), Street Network (Closest or fastest units based on a real route from unit location to event), or Closest which ignores the response plan and shows a list of the 10 closest units regardless of type. 4-Dispatching-Cmd & Control 32 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-033 4-034 4-035 4-036 4 -0 37 4-038 4-039 4-040 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation Units recommended for fire and EMS incidents shall be based on the Kesponse plans are assigned o event-types/sub- location of the incident, the incident type, the fire zone, any known premise type/alarm level combinations. The response plan information, and the capabilities of both the apparatus and the staff. assigned to any given event-type/sub-type/alarm level can be overridden for a specific location based on Yes known premise information (such as a structure fire at a hospital vs. a structure fire at any other commercial structure). Response plan requirements use unit type, unit attributes, personnel skills, and vehicle equipment, There shall be no limit to the number of units that may be dispatched to an Yes System Default Functionality incident. The system shall track all the units individually. It shall be possible to dispatch a responding unit to another incident of Hexagon stipulates that if the operator chooses to higher priority. The system shall have the option of either allowing the return the preempted event to pending, it is not flagged original incident to drop into a configurable call "stack" or have the original Alternate as having been previously dispatched, but the incident return to a pending status. If sent to a pending status, the incident information recorded in the event makes it clear that it was reviousl assi ned. The system shall be able to return the freed incident to the pending queue When pre-empting the last assigned unit on an event, with minimal user intervention. Yes the operator is prompted for action on the event. It can be returned to pending, dispatch assigned to the unit, or held for the unit. Users shall have the ability to dispatch multiple units to a single incident Yes System Default Functionality - DSPU or configured simultaneously from the command line. command with options Units may be "pre -assigned" to incidents. When a unit clears its Hexagon stipulates that this is the dispatch assign assignment, it may automatically dispatched to the next "pre -assigned" Yes functionality incident. The system shall record intermediate stops made by a unit Enroute to Hexagon is not entirely clear on the goal of this another call for service. requirement but clarifies that I/CAD tracks all AVL equipped units all of the time. Should a unit make a Yes stop while enroute to an assigned event, that information will be part of the stored AVL data. If this refers to a traffic stop or subject stop, this information can also be recorded via the event traffic stop The system should allow off -duty units to be placed on duty and their status Yes System default functionality. tracked for off duty employment 4-Dispatching-Cmd & Control 33 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-041 4-042 4-043 4-044 4-045 4-046 4-047 4-048 4-049 4-050 4-051 4-Dispatch ing-Crr 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation The system shall have the ability to display and update incident Hexagon stipulates that any number of operators may information. There shall be no limit to the number of Designated Users that be viewing an event and entering new remarks, may review or update the same incident. Yes supplemental persons and vehicles, but only one operator may have an event in update mode at one time for changing key items such as event location, event- tvpe. sub -type, callona party information, The system shall allow an unlimited number of updates and comments to Yes System Default Functionality each incident. The system shall support a feature to alert the user when supplemental System Default Functionality - System Information information is added to an incident, without requiring user action. The alert Yes Toolbar, Update button notifies the controlling can then be cleared by the user after reviewing the update. workstation of an event update. This is cleared if that workstation reviews that event Users shall be able to add comments to any incident record, including System Default Functionality - Remarks can be added closed incidents. Yes via various dialogue boxes or command line based on o en/closed event The system shall maintain timers for each incident and alert the user if the System Default Functionality - Alert Timers section in incident has "timed out." Timers are based on the priority of the Yes CADDBM, number of minutes can be entered to initiate incident. Pending incidents are timed by the priority of the incident. Timers an Alarm in Various fields. The system shall support a function to reset timers for incidents that have Once an event has reached its overdue state, there is timed out. No no way to reset the overdue timer. The event must be dispatched, dispatch assigned, or placed on hold to clear the overdue status. The system shall record in Incident History time-out and the time-out reset Yes System includes event timers, and Incident command timers. The CAD system users shall be able to recall incidents for review, enter System Default Functionality - Remarks can be added update information, or dispatch additional units. Yes via various dialogue boxes or command line based on open/closed event - Select Event, Recommend or via command line The system should allow an incident to be displayed or updated by entering System Default Functionality - Various options for either the fewest number of significant digits or the unit I D of any unit Yes command line entry and configurations the incident. shall support incident recall using either the command line or Yes System Default Functionality d screen. Fincident earch results shall be able to be sent to the printer. Yes System Default Functionality - Print option on various screens and various command line functions 34 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-052 4-053 4-054 4-055 4-056 4-057 4-058 4-059 4-060 4-061 4-062 4-063 4-064 4-065 4-066 4-067 4-068 4-069 4-070 4-Dispatching-CMD & Ver: 8/152017 Control Response Explanation The system shall be able to clear all units from an incident at closure and Yes System Default Functionality - command line, command assi n a final dis osition code. drop down or dialogue box The system shall respond to the initial dispatch by: • Automatically assigning the dispatched units to the incident. Yes System default functionality • Automatically removing the incident from the pending queue. Yes System default functionality • Automatically updating the incident in the incident status display. Yes System default functionality • Automatically starting the status timers for the dispatched units. Yes System default functionality • Automatically logging the dispatches in the incident history. Yes System default functionality • Automatically stamping time, Telecommunicator, and position for all Yes System default functionality actions. Incident searches should be performed interactively using: • Incident number. Yes System default functionality in the Event Search function • Range of dates. Yes System default functionality in the Event Search function • Range of times. Yes System default functionality in the Event Search function • Geographical area or radius from a specific location. No Not currently supported • Incident type. Yes System default functionality in the Event Search function • Assigned unit. Yes System default functionality in the Event Search function • Assigned Personnel Yes System default functionality in the Event Search function • Disposition. Yes System default functionality in the Event Search function • Call Taker I D. Yes System default functionality in the Event Search function • user I D. Yes System default functionality in the Event Search function 4-Dispatching-Cmd & Control 35 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-071 4-072 4-073 4-074 4-075 4-076 4-077 4-078 4-079 4-Dispat0ing-CMD & Ver: 8/152017 Control Response Explanation The system shall allow the Call Taker to dispatch the call based on the The County has stipulated the Call Taker in this CAD system/AVL unit recommendation. requirement. Hexagon's I/Call taker product (not No proposed) has no unit functions available. Hexagon has proposed I/Dispatcher for calltaking and dispatching functionality. An I/Dispatcher client must be used to dispatch units or see unit recommendations. The system shall be highly configurable and must support: • Agency -defined response zones/beats/boxes I/CAD can store an ESZ, beat, zone, and district as part Yes of all events. Only ESZ and beat have a role to play in unit recommendation and response planning. • Agency -defined station order responses Yes System Default Functionality via deployment planning and the backup beat list • Agency -defined responses Yes System Default Functionality via response planning • Agency -defined location or premise classifications Yes System Default Functionality via special address common place name type and sub -type functionality. • Agency -defined equipment or apparatus types Yes System Default Functionality - Vehicle and Unit Definition Dialogue in CADDBM. The system shall provide the means to identify a "Split Crew" which is a single crew assigned to operate two pieces of equipment. For example, if Hexagon stipulates that this is the I/CAD shared crew or the hazardous materials van leaves the station, the system should put the Yes station crew functionality. corresponding engine out of service. This should be done automatically First responder recommendations shall be configurable within the system. ys em Default Functionality - Define Requirement Dialogue, Response Plan Dialogue, Run Card Dialogue, Deployment plan dialogue, Beats Dialogue Yes are all CADDBM functions. Using the Additional Recommend Unit function, the dispatcher can choose a change in the type of response and also, can manually overrode via command lone. 4-Dispatching-Cmd & Control 36 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-080 4-081 4-082 4-083 4-084 4-085 4-086 4-087 4-088 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation The system shall include the ability to configure and designate mutual aid bystem Default Functionality - Define Requirement responses. Dialogue, Response Plan Dialogue, Run Card Dialogue, Deployment plan dialogue, Beats Dialogue Yes are all CADDBM functions. Using the Additional Recommend Unit function, the dispatcher can choose a change in the type of response and also, can manually Special equipment requests shall be configurable based on response and Yes System Default Functionality -Ad Hoc response incident type. planning. Special equipment requests shall be designated with the Incident Dispatch Yes System Default Functionality - Ad Hoc response function to support on -the -fly requests from the field. planning. The system shall support a feature to handle a temporary change of quarters for Fire/EMS units to cover for a station that is low on resources. Yes System default functionality - Relocate Unit Fire units put into a covering status shall be recommended from the station Yes System default functionality - Relocate Unit for which they are covering. The system shall allow Dispatch Supervisors to view all pending incidents Yes System Default Functionality based on terminal node system wide definition Users shall have the ability to transfer a created incident from one area to System Default Functionality - An event and all its another. Yes associated assigned units to another dispatch group regardless of status. Can all transfer an unassigned event to another agency The user shall have the option of assigning a different disposition to each System Default Functionality - Disposition code to an unit clearing an incident. Yes event or select the unit on the event and assign the code The system shall allow "incident close" and "unit clear" commands. For supports a clear event command which will clear example, the incident close command would close out the incident with a all units assigned to an event and close the event. single disposition, regardless of how many units were on the assignment. Operators may assign disposition codes during the The unit clear command would only clear the unit specified in the command Yes clear event process. Clear unit commands will clear a from the incident. Once the last unit has been cleared from the incident, the unit or units off the event, but unless the unit(s) being incident would close. This would allow Dispatchers to clear individual units cleared are the last units assigned, the event will from the incident yet keep the incident open should other units still be remain open. Operators can provide disposition codes 4-Dispatching-Cmd & Control 37 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-089 4-090 4-091 4-092 4-093 4-094 4-095 4-096 4-097 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation Incidents should automatically route to the proper area based on a verified When validates a location a coordinate is address. obtained. Via a point -in -polygon process that coordinate is determined to be in an ESZ (emergency Yes service zone). That ESZ is configured to be in a given agency and dispatch group. Based on that agency and dispatch group assignment, the event is routed for handling to the terminal(s) that have cover access for The system shall have the ability to send updated incident information to a Hexagon system updates the mobile devices mobile device as soon as the incident is updated, and vice versa. Yes dynamically as incident is updated and same if updated from the mobile cad sees dynamically. The system shall have the ability to assign stacked or pending calls to a Hexagon stipulates that pending events are assigned to zone and not just a unit or personnel. an agency, dispatch group, and beat. "Stacked" is an No undefined term, and therefore exempted from our response. Hexagon could assume that means a dispatch assigned event, in which case dispatch assmaned events are only assmaned to a unit. The system shall support attaching images and files to an Incident from Yes System Default Functionality - Attachments Dialogue both the CAD client and the mobile client. box. All attachments shall be viewable from within the Incident record Provided that the client computer has the necessary software installed to view the attachment. For example, Yes a compatible PDF viewer must be installed to view .pdf files, a compatible image viewer must be installed to view .jpg, .gif, .tiff etc. Attachments can be of any type, but viewing them requires the proper software installed. The CAD Command Line shall support prompting the user for the next parameter required for each command. Users shall be able to turn this No Not currently supported feature on and off. If more information is entered on the Command Line than can be displayed Hexagon stipulates that this is only available in the on a single line, the command line must wrap to display the entire string whole typona Yes multi -line command line. The system shall have the ability to track units through status changes. I Yes lSystem Default Functionality The system shall support a central unit table for the creation of Unit IDs Yes System Default Functionality - CADDBM Unit and Vehicle Definition - schema 4-Dispatching-Cmd & Control 38 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-098 4-099 4-100 4-101 4-102 4-103 4-104 4-105 4-106 4-107 4-108 4-109 4-110 4-111 4-112 4-Dispa1ch inng-C 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation The system shall have the ability to assign capabilities to units\personnel Hexagon stipulates that units have attributes, vehicles for dispatch recommendation purposes. Yes have equipment, and personnel have skills. These terms may be collectively referred to as capabilities. The system shall have the ability to assign capabilities to the units No Not currently supported consistent with NIMS typing. • Resource No Not currently supported • Category No I Not currently supported • Kind No Not currently supported • Component No Not currently supported • Type Yes Default system functionality • Other No Not currently supported • Minimum Capabilities Yes Hexagon stipulates that this is unit attributes. I/CAD has 255 available configurable unit attributes. Users shall have the ability to update a unit's functionality in real time by Hexagon stipulates that this is unit attributes. I/CAD either adding or removing capabilities. Yes has 255 available configurable unit attributes. Unit attributes can be changed by the dispatcher, via the I/Dis atcher client only. Designated Users should have the ability to update a unit's functionality in real time via MDC or other remote interface by either adding or removing No Not currently supported capabilities The system should allow units assigned to an incident to be updated with a location other than the location of the incident without affecting the original Yes System Default Functionality - Change location incident location. An audit record (including time of change) should be command The system shall allow comment information to be entered during unit System Default Functionality - Command line command status updates. This comment information shall be logged in the unit history Yes options with status change and in the incident record if the unit is assianed to an incident. Unit status should be capable of being updated using a command, form, Yes System Default Functionality Mobile mouse action or function key. The user shall have the ability to transfer units from one geographic area to System Default Functionality - Transfer Unit to lend a another. Yes unit to another dispatch group. If the parameter is set properly you can also lend a unit to another agency The system shall allow dispatching and tracking of multiple units or Yes I System Default Functionality - The command line ";" & multi Ie unit statuses at the same time. use can allow multiple unit status at the same time 39 of 186 Company: Item Number 4-114 4-115 4-116 4-117 4-118 4-119 4-120 4-121 4-122 4-123 4-124 4-125 4-126 Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Dispatching -Unit Command & Control 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation The system shall allow the County to define the following types of unit statusparameters: • Special status colors. Yes Through CADDBM status colors can be defined by System Administrator • Allowing a unit to be available for dispatch while in a status. If a unit is assigned to an event and is in one of the Yes event related unit statuses, the dispatcher must use the "available on event" command to make the unit available to be dispatched to another event. • Allowing a unit to be available for recommendation while in a status. Yes Unit status parameter table, AvailableForRecommend setting. • Time allowed in a status. Yes Timers can be set in CADDBM based on Status • Status code Yes Through CADDBM status codes can be defined by System Administrator The system is capable of establishing an enroute geofence for a location Hexagon stipulates this is the Halo capability used with (e.g., fire station). Alternate I/Tracker and assumes the units have GPS equipment. Unit enroute status can be automatically set when a vehicle moves a predetermined distance (geofence) from the location when dispatched (e.g., Alternate Hexagon stipulates this is the Halo capability used with the fire vehicle moves 50 feet from the station after being dispatched). I/Tracker and assumes the units have GPS equipment. The system is capable of establishing an arrived geofence for a location Hexagon stipulates this is the Halo capability used with (e.g., incident location, other locations). Alternate I/Tracker and assumes the units have GPS equipment. Unit arrived status times may be automatically set when the unit assigned Hexagon stipulates this is the Halo capability used with to a call enters a proximity zone (geofence) of the location of the incident. Alternate I/Tracker and assumes the units have GPS equipment. Unit arrived status times may be automatically set when the unit assigned to a call enters a proximity zone (geofence) of a location (e.g., jail, No Not currently supported hospital), The size of the proximity zone is determined by the agency. Hexagon stipulates this is the Halo capability used with Alternate I/Tracker and assumes the units have GPS equipment. Unit status records are exportable to an interfaced RIMS module. Yes Hexagon has proposed the I/FRMS-CADLink and I/CADLink interfaces to provide the unit information. 4-Dispatching-Cmd & Control 40 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-127 4-128 4-129 4-130 4-131 4-132 4-133 4-134 4-135 4-136 4-137 4-138 4-139 4-Dispatch ing-C 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation Unit status records are exportable to a Comma Separated Variable format Hexagon stipulates that Microsoft SQL Server file. Yes Management Studio must be used to generate this list. The system shall track time in status for each unit separately and shall Yes System allows time in status tracking, and can by allow each unit to bedynamically assigned different time-out values. dynamically assigned. The system shall alert the user when each unit has timed out. Yes System Default Functionality - Unit Alarm on the System Information Toolbar When a unit is put into a status, the system shall assign a default timer Hexagon stipulates that only the default unit status defined for each status. codes support timers. Custom unit status codes Yes created by the County do not support automatic timers, but manual timers may be added by the operators as a secondary step to placing a unit in that custom status. The system shall support a function to reset timers for units that have timed Yes System Default Functionality - Unit Alarm Dialogue or out. the command line The system shall support a function that allows unit timers to be reset to a Hexagon stipulates that operators must supply the default value for a given status. No value to which the timer shall be reset when using the contact unit command. The system shall support a function that allows unit timers to be set automatically based upon not only the status but also the priority of the Hexagon system in CADDBM allows system incident to which units are responding. For example, an Enroute time to a Yes administrator to set Unit status timers per event type low -priority incident has more allowable time than Enroute time to a high- code. Which allows for workflow described The following timers are provided by the system: • Elapsed time of an event in the pending list Yes System Default Functionality - CADDBM Event Type Dialogue settin • Dispatcher initial event view to dispatch of first unit No Not currently supported • Initial dispatch to first unit to arrive on -scene Hexagon stipulates that this is a unit timer, and is Yes unique to each unit assigned to the event. There is no event level timer that tracks this information. • Elapsed time of units on -scene (Personnel Accountability Report System Default Functionality - CADDBM Event Type [PAR] check) Yes Dialogue setting or timer in Incident command dialogue . Elapsed time a unit is on -scene without communication to dispatch System Default Functionality - CADDBM Event Type (responder safety) & Control Yes Dialogue setting or timer in Incident command dialo g g gNeof 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-140 4-141 4-142 4-143 4-144 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation The system allows the creation of agency -defined time stamps. supports timers in two primary areas, even pending time (overdue), and unit status times. Event pending times are defined by priority or event-type/sub- type. Unit times are defined by priority, or event - Yes type/sub-type. The status timers available for a unit are Dispatched, Acknowledged, Enroute, Arrived, Transport, and Transport Arrived. "Note that transport and transport arrived are defined globally for an agency and are not configurable by priority or event-type/sub- The system allows the creation of agency -defined timers using defined time PeAsupports timers in two primary areas, even stamps. pending time (overdue), and unit status times. Event pending times are defined by priority or event-type/sub- type. Unit times are defined by priority, or event - Yes type/sub-type. The status timers available for a unit are Dispatched, Acknowledged, Enroute, Arrived, Transport, and Transport Arrived. "Note that transport and transport arrived are defined globally for an agency and are not configurable by priority or event-type/sub- A respective agency can determine the length of time that a timer will be PeAsupports timers in two primary areas, even active before notifying the operator. pending time (overdue), and unit status times. Event pending times are defined by priority or event-type/sub- type. Unit times are defined by priority, or event - Yes type/sub-type. The status timers available for a unit are Dispatched, Acknowledged, Enroute, Arrived, Transport, and Transport Arrived. "Note that transport and transport arrived are defined globally for an agency and are not configurable by priority or event-type/sub- provides an audible (optional through system configuration) System Default Functionality - CADDBM and System otification to an operator when an event timer exceeds a Yesed settings Pvisual time eriod in a status.Configuration otification for the event timer is displayed on the event's map No Not currently supported 4-Dispatching-Cmd & Control 42 of 186 Company: Item Number 4-145 4-146 4-147 4-148 4-149 4-150 4-151 4-152 4-153 4-154 4-155 4-156 4-157 4-158 Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Dispatching -Unit Command & Control 4-Dispat0ing-CMD & Ver: 8/152017 Control Response Explanation The event status timer's time periods are established and maintained by the Yes System Default Functionality - CADDBM Event Type agency. Dialogue settin Event status timer can vary by event type code. Yes System Default Functionality - CADDBM Event Type Dialogue setting Event status timer can vary by event priority. Yes System Default Functionality - CADDBM Event Type Dialogue setting The system allows an operator to reset the timer operation for any event- or unit -related timer, with the following conditions: • The timer restarts at 0. I/CAD provides for the ability to reset unit timers to a value determined by the operator when issuing the contact unit command. Event pending timers cannot be Alternate reset. Once an event has become overdue, it remains overdue until it is dealt with. It can be dealt with by dispatching a unit to the event, placing the event on hold, or dispatch assigning the event to a unit. • Notifications are reset. Yes System Default Functionality - Contact Unit • An operator can select a default time period or specify a time period. Hexagon stipulates that operators must supply the No value to which the timer shall be reset when using the contact unit command. • Timer resets are recorded in the event history. Alternate Unit timer resets are recorded in the units history, not the event history. The system allows an operator to disregard the timer operation for any event- or unit- related timer, with the following conditions: • The timer continues to run. Yes System Default Functionality - Contact Unit • Future notifications can be turned off. Yes System Default Functionality - Contact Unit with a timer value of zero • Future notifications can be reset (snooze). Hexagon stipulates that operators must supply the Yes value to which the timer shall be reset when using the contact unit command. The system tracks time in status for each unit separately. Yes System Default functionality The system allows each unit to be dynamically assigned different time-out Yes System Default Functionality - Contact Unit values. 4-Dispatching-Cmd & Control 43 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-159 4-160 4-161 4-162 4-163 4-164 4-165 4-166 4-167 4-168 4-169 4-170 4-171 M, I rX 4-173 4-174 4-175 4-176 4-Dispat0ing-CMD & Ver: 8/1512017 Control Response Explanation The system provides an audible (optional using system configuration) and System Default Functionality - Contact Unit Alarm visual notification to an operator when a unit exceeds a predetermined time Yes functions The following unit status timers are enabled: • Dispatched — the length of time in the dispatched status to marking Yes System Default Functionality - CADDBM Event Type enroute or arrived/on-scene Dialogue setting • Enroute — from dispatch to arrived/on-scene Yes System Default Functionality - CADDBM Event Type Dialo ue setting • Arrived — the length of time from on -scene to clear Yes System Default Functionality - CADDBM Event Type Dialogue setting • Unit safety/well-being timer — length of time established by the agency Yes System Default Functionality - CADDBM Event Type Dialogue setting • PAR check Yes System Default Functionality - CADDBM Event Type Dialo ue setting or Incident Command timer setting • Operator -enabled timers Yes System Default Functionality - Contact Unit Visual notification for the unit timer is displayed for the unit's map icon. No Not currently supported Visual notification for unit timer triggering includes blinking of the unit ID or No Not currently supported map icon. Unit status timer time periods are established and maintained by the Yes System Default Functionality - CADDBM Event Type agency. Dialo ue setting If a mobile device is associated with the unit and a wellness check unit timer trigger is activated for that unit, the system passes the notification to No Not currently supported the mobile device of the associated unit. Unit status timer can vary by event type code. Yes System Default Functionality - CADDBM Event Type Dialo ue setting Unit status timer can vary by unit status code. Hexagon clarifies that the following unit status codes have timers automatically: Dispatched, Acknowledge, Yes Enroute, Arrive, Transport, and Transport arrive. Operators may create a unit timer manually for any other unit status at any tome for any duration. An operator can reset the timer for any unit. Yes System Default Functionality - Contact Unit • The timer restarts at 0. Yes System Default Functionality - Contact Unit • Notifications are reset. Yes System Default Functionality -Contact Unit An operator can disregard the timer for any unit. Yes System Default Functionality - Contact Unit 4-Dispatching-Cm on ro o 186 Company: Item Number 4-177 4-178 4-179 4-180 4-181 4-182 4-183 4-184 4-185 4-186 Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Dispatching -Unit Command & Control 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation • The timer continues to run. Yes System Default Functionality - Contact Unit • Future notifications can be turned off. Yes System Default Functionality - Contact Unit • Future notifications can be reset (snooze). Hexagon stipulates that operators must supply the Yes value to which the timer shall be reset when using the contact unit command. The system shall allow an assigned unit to be exchanged for another unit. Hexagon stipulates that using the exchange unit command is an exact swap of the two unit statuses. For example if unit El is assigned to an event and enroute Yes to 100 W MAIN ST and E33 is out of service for training and the exchange unit command is used for El and E33, E33 will assume the dispatch status to 100 W MAIN ST and E12 will go out of service training. e system shall provide the ability to include odometer reading when a unit goes on duty, goes off duty, and at unit status changes. Yes Via an update to unit properties The system shall allow units to be placed on duty from a preformatted Yes System Default Functionality - Logon command or drop screen or command line. down menu The on -duty entry should include assignment. Yes Hexagon assumes that "assignment" refers to the unit's station assi nment. Users shall have the ability to make changes in the on -duty unit status. Yes System Default Functionality - command line The name of a ride -along should be capable of being entered at unit sign- Hexagon stipulates that this is the "Third -Rider" unit on. Multiple rider names can be added to a unit. property. Third rider begin and end times are recorded Alternate in the unit history using the RB and RE unit status codes. The names of third riders are recorded in the unit history comment which is limited to 200 characters The system should have the ability to assign vehicles to individual Vehicles are assigned to the unit, and personnel are personnel and maintain that vehicle assignment through shift changes. assigned to the unit. If a unit consists of a single Alternate person, then this requirement would be a Yes - as the vehicle is associated with a person through the definition of a unit. 4-Dispatching-Cmd & Control 45 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-187 4-188 4-189 4-190 4-191 4-192 4-193 4-194 4-195 4-196 4-197 4-198 4-199 4-200 4-201 4-202 4-203 4-Dispat0ing-CMD & Ver: 8/152017 Control Response Explanation If an ID number being assigned to a unit already has an assignment, then Hexagon assumes that "I D number" in this requirement the system shall prompt the user to either change the badge number to the refers to a specific person. When an operator tries to new assignment or maintain the old assignment. assign personnel to a unit that are already assigned to Alternate another unit, they are simply told that the personnel are already assigned and they are told to what unit. Operators must then take separate action to remove the person from the other unit, or leave the assignment as When an assignment is closed, the system shall maintain the personnel ID Yes System Default Functionality - written to the DB and numbers associated with the assignment for audit purposes. part of the unit and event history The system shall provide a means to schedule groups of units to bring on Hexagon stipulates that the Iogon group command can duty at the same time. Yes be scheduled provided that the lineup has been created in advance and the name of the line up is known when the command to loa it on is scheduled. Ability to create shift schedules including the following data: • Unit ID (alphanumeric) Yes Default Lineup Functionality • Personnel ID (one or more people per unit) Yes Default Lineup Functionality • Response area Yes Default Lineup Functionality • Vehicle ID Yes Default Lineup Functionality • Radio ID Yes Default Lineup Functionality • Date and time scheduled for on -duty Yes Lineup start date/time. • Date and time scheduled for off -duty Yes Lineup shift duration • Shift designator Yes As part of the name/title of the lineup • Special equipment or response capabilities Yes Default Lineup Functionality Ability to schedule shift/roster information up to 12 months in advance Yes System Default Functionality - Lineup Ability to upload shift/roster information to CAD based on scheduled shift Hexagon assumes this to refer to creating a lineup in start time Yes advance, and then logging that lineup into service at a pre -determined time. This would be accomplished with default lineup functionality and scheduled commands. Ability to modify shift/roster information up to scheduled shift start time Yes System Default Functionality - Logon Group or Unit Ability to automatically (without user intervention) notify responsible No Not currently supported Dispatcher of a new shift read to be logged -on 4-Dispatching-Cmd & Control 46 of 186 Company: Item Number 4-204 4-205 4-206 4-207 4-208 4-209 4-210 4-211 4-212 4-213 4-214 Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Dispatching -Unit Command & Control 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation Ability to pre-program and override shift change information (e.g., hours of No Not currently supported shift The system shall support the creation of Unit Groups for messaging and Yes System Default Functionality - CADDBM System Admin status changes. configuration The system shall support a temporary unit feature (with a minimum six- Logon Unit functionality, combined with Macro feature character unit number), allowing units that are not predefined in the system Yes to Logon unique unit and dispatch to specified event or not on duty to be placed on duty and dispatched via a single function by with one command line Once the units complete the activity, they should be automatically taken out Yes Hexagon stipulates that the operator must still the log of service and removed from the system. the unit off. The system shall display area -specific units separately from roaming units. Yes System can display units separately by area and from roaming units Designated Users shall have the ability to add units to the master units table. At minimum, a master unit record shall support the following fields: Yes Default CADDBM functionality eight -character unit number, area designation, zone designation, and unit The system must continually poll units and must alert the Dispatcher that a closer unit has become available and should be sent in place of another Yes Real time recommend monitor functionality unit. The system should automatically assign units a working tac channel as NO Auto -assignment of units to a working tac channel dictated b the call type. dictated by call type is not currently supported. The system should notify the Dispatcher when at a certain saturation level. The system does not notify the Dispatcher when at a Lee County EMS, by percentage or number of resources busy and the No certain saturation level. res onse Ian changes. The system must understand cross staffing and put a unit Out of Service Yes Hexagon system supports cross staffing and shared automatically when the personnel is busy on another unit. crew workflows. Field Units need to be able to create a call for a walk in patient and assign Yes This is a default mobile feature (self initiated calls). themselves to the call. 4-Dispatching-Cmd & Control 47 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure NItem Dispatching -Unit Command & Control 4-215 4-216 4-217 4-218 4-Dispatching-CMD & Ver: 8/1512017 Control Response Explanation two things, the location of the event and the type of event. Upon location verification I/CAD determines all of the emergency service zones that location falls Lee Control supports a multi -agency closest unit, cross boundary response within. For each agency defined in I/CAD that has an method for the fire services as well as a separate near county wide ALS ESZ that covers this location CAD returns that ESZ transport service. The medical service and fire service will each need an Yes number to the application. Then upon choosing an incident sent to their respective Dispatchers with their own unique event type CAD further determines what agencies have sequential run number. Explain how your system meets this need. that event -type or aliased event -types defined for it to decide which agencies should attend. When the call - taker accepts the event with one agency event is created for every agency that should be respond to that When building a response plan, the County may use Ability to recommend units based on defined cross -district boundaries or built in requirement settings to determine if the stay within district boundaries depending on the rules of the agencies. requirement should come from a specific agency or any agency. The system will support a multi-agency/jurisdiction model for both I/CAD is amulti-agency/jurisdiction CAD system. Emergency Medical Services and Fire -Rescue districts Hexagon interprets the term run card to mean a list of stations defined in the order that they should be Response recommendations shall be AVL closest unit, run card, or searched. Unit recommendations can be based on combined depending on the incident type and primary agency. street network (actual calculated drive time/distance - from unit location to event location), or beats/backupbeats (run card) or a combination of both 4-Dispatching-Cmd & Control 48 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-Interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-001 5-002 5-003 5-004 5-005 5-006 5-007 5-008 Sl nterfaces Test, Training, Redundant, and Backup copies are available for all proposed interfaces; however, implementation is subject to the customer's ability to provide connection to the applicable system. Not all interfaces support automatic failover. Hexagon welcomes further discussion on this requirement. Connections to all interfaces shall be redundant and automatically fail over with no NO disruption to service. Hexagon clarifies that for all COTS and EdgeFrontier interfaces proposed, certain assumptions and limitations apply. Hexagon welcomes further discussion with the County regarding all interfaces and can provide detailed interface descriptions/assumptions at a later date to be included in a mutually developed and agreed to Statement of Work as part of Interface Implementation tasks. If any interface or connected system/device fails notification should be made to the Requires access by the I/CAD External System Message Dispatch Supervisor. Yes Display (ESMD) program to an SMTP email server; notifications are sent bV email If any interface or connected system/device fails notification should be made to the System Yes Requires access by the I/CAD ESMD program to an SMTP Administrator or designee- email server notifications are sent by email The system should have standard data connectivity such as ODBC Yes All 1/CAD generated data is stored in a Microsoft SQL Server 2016 database which is ODBC compliant - The system should have a SMTP interface to allow each CAD workstation the ability to This can be accomplished by using 1/Page and an SMTP send or receive emails. There should be an ability to include a defined subset of the CAD Alternate gateway provided by the County, I/CAD can send emails. incident record automatically in anV email. I/CAD cannot receive email. The system should have a SNPP interface to allow each CAD workstation to send alpha Yes This can be accomplished by using I/Page with SNPP numeric pages either free hand or a definable subset of the CAD incident record. I/CAD takes all time from the Windows operating system. The system will interface to a Spectracom Netclock or NTP Time Server and keep all Hexagon assumes the County has a time synchronization servers and workstations sync Yes strategy for its workstations and servers that will be part of the I/CAD solution. Hexagon has also included a quote for PresenTense software to support this re uirement. I/CAD takes all time from the Windows operating system. The system will interface to a Spectracom Netclock or NTP Time Server and keep all mobile Hexagon assumes the County has a time synchronization devices synced. Yes strategy for its workstations and servers that will be part of the I/CAD solution. Hexagon has also included a quote for PresenTense software to support this re uirement. 49 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-009 5-010 5-011 5-012 5-013 5-014 5-1 nterfaces Hexagon's Intergraph AniAli Server supports NENA Format Versions 1 and 2 (Fixed Length ASCII), NENA version 3 The system shall have the ability to interface to 9-1-1 systems Yes (Tagged Delimited) and NENA version 4 (XML). These Formats are documented in NENA documents NENA 02-010 v9 now "Legacy Data formats for ALI, MSAG &GIS" and NENA 04-001 v2 now "E9-1-1 PSAP Equipment". for Cellular 911 calls. The I/CAD system supports the creation of events based on a geographic coordinate location. The ANI/ALI packets for Phase II Wireless 911 calls include the coordinates (in lat/long or other standard coordinate The E-9-1-1 interface shall adhere to all NENA Phase I and If requirements for the receipt Yes system, as dictated by the NENA standard or FCC of Wireless 9-1-1 information. requirements), and uses this information to create an event at the caller's geographic coordinate location and show the location on the map. The nearest civic address can also be estimated and displayed. The exact format of this data in the ANI/ALI packet must be supplied by the customer (in The system shall display the caller's address, name, and phone number anytime an Hexagon stipulates that the caller's naM,Nddress, and phone incident is displayed. Additional NENA 05-002 information shall be easily accessed for the Alternate number are captured and displayed. However, the NENA incident by using function key. information is not available from a function key. However, this data is ca tured in the database- A— c an Ies a u er IMU11101.1UH Is needed prof to saying Yes to this item as "any" is a broad, undefined requirement. Although not currently proposed, Hexagon offers a product called Intergraph Communications Controller (ICC) The system shall comply with any NextGen 9-1-1 standards adopted at the time of contract. No which provides NextGen 9-1-1 telephony support with the WesUlntrado system. However, further review of the NextGen 9-1-1 standards to be adopted at the time of the contract is necessary to determine if ICC will fully support the County's The system shall have the ability to transfer event (incident) and audit records from CAD Hexagon assumes this is to transfer event and unit related through trigger configuration. These transfers will be completed in near real time. Alternate data to an external RMS system. Hexagon has proposed I/CADLink and I/FireRMS CADLink interfaces to support this. The system shall have the ability to query external databases to get access to information; Alternate Hexagon has optioned our COTS query interface I/Informer to Federal State and/or Local. support queries to the state/NCIC. 50 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-015 5-016 5-017 5-018 5-019 5-020 5-021 5-022 5-023 5-024 5-025 5-026 5-027 5-1 nterfaces If Lee County decides to take on the role and tasks associated with creating, editing, and maintaining the query structures-, The system shall also support the ability to create, edit, and maintain the query structures. Yes and at the request of the customer, Hexagon can offer a customized training course to train Lee County developers in how to create, edit, and maintain the query structures at an add tonal cost The system shall be integrated with an ad hoc report writer that allows a user to create Yes InSight Reporting uses Microsoft SSRS and Power BI. Both reports from incident data. allow ad hoc reporting - The system shall have a report scheduler that can schedule reports to be automatically run Yes Microsoft SSRS used by InSight Reporting allows at user defined times. subscriptions for scheduled reports - The system should be able to send the same information to multiple receivers at the same Microsoft SSRS subscriptions used by InSight Reporting time Yes allows multiple email recipients and email groups to be defined. Reports should be publishable to an intranet or internet. Yes Per above SSRS define subscriptions for email can be local or internet. The system should have the ability to send selected data to separated Database Servers Hexagon clarifies that InSight Reporting does not send data to close to realtime for RIMS and Dashboard purposes. No other databases. It does support Tabular Models that can be used to support dashboards. Hexagon assumes this is to transfer event and unit related The system shall have the ability to map exported data fields to pre-existing database fields data to an external RIMS system. I/CAD data is provided in of different names. Yes defined formats. It is the responsibility of the consuming RIMS vendor to translate and map that data to the formats necessary bV theirs stem. The system provides the capability to complete Patient Care Reports (PCRs) in the field. No Not a function of MPS or Mobile Responder (optioned). The system can interface with ImageTrend Elite. Yes Using I/CADLink Hexagon welcomes further discussion on this In er ace. Hexagon clarifies that ESO wrote their side of the initial interface and so Hexagon's stance is that ESO may need to The system can interface with ESO Healthcare Solutions ePCR HER version 5. Alternate update their interface to the Hexagon CAD if changes have been made. Hexagon offers a COTS interface I/CADLink which can interface to ESO. Hexagon assumes that ESO will The incident definition will include a discrete field for a matching NEMSIS\EMSTARS Code. Hexagon clarifies that services are included as part of the This code will be attached to the incident record for later reporting or passing to an Modification overall implementation services to support a customization to agency's RIMS the CAD database to add a column for capturing the code and customization to add the field for this. The system supports, at a minimum, the capture/transfer from CAD of the following data elements for each CAD event: . Incident number or Report Number Yes "Incident Number" is a COTS (system default functionality) feature Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-Interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-028 5-029 5-030 5-031 5-032 5-033 5-034 5-035 5-036 5-037 5-038 5-039 5-040 5-041 5-042 5-043 5-044 5-045 5-046 5-047 5-048 5-049 5-050 5-051 5-052 5-053 5-1 nterfaces • Report number Yes Hexagon assumes this is the same as the Case Number- This is a COTS feature- • Street Direction Yes COTS/system default functionality • Street Number Yes COTS/system default functionality • Street Name Yes COTS/system default functionality • Street Type Yes COTS/system default functionality • Postal Code Yes Hexagon assumes this is the same as zip code, which is COTS/stem default functionality • Unit ID Yes COTS/system default functionality • Vehicle ID Yes COTS/system default functionality • Agency ID Yes COTS/system default functionality • Remarks Yes COTS/system default functionality • Call location Yes COTS/system default functionality • Call type - initial Yes COTS/system default functionality • Time first unit arrived Yes COTS/system default functionality • PSAP time Modification Hexagon has included as part of overall implementation services a level of effort to be able to capture this information in CAD and be able to transfer it- • Time dispatched Yes COTS/system default functionality • Time enroute Yes COTS/system default functionality • Time arrived Yes COTS/system default functionality • Time arrived patient Yes Assumes this will be time going into Transport Arrive status • Time departed for transport Yes Assumes this will be time going into Transport status • Destination hospital Yes COTS/system default functionality • Time at hospital No Not currently supported • Time clear from hospital Modification Hexagon has included as part of overall implementation services a level of effort to add a custom unit status to CAD for this requirement - • Patient Priority Modification Hexagon has included as part of overall implementation services a level of effort to add this data element to CAD for this r uirement- • Time available Yes Hexagon's CAD system offers multiple statuses for "available" • Time cleared Yes COTS/system default functionality CAD event data is available for transfer to the ePCR system while the event is active or closed- Yes This is met via a configuration workshop included as part of proposed implementation services- 52 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-054 5-055 5-056 5-057 5-058 5-059 5-060 5-061 5-062 5-063 5-064 5-065 5-066 5-067 5-068 5-069 5-070 5-071 5-072 5-073 5-074 5-075 5-076 5-1 nterfaces The system supports, at a minimum, the capture/transfer from CAD of the following data elements for each unit logged on during a shift: • Unit ID Yes COTS/system default functionality • Vehicle ID Yes COTS/system default functionality • Agency ID Yes COTS/system default functionality • Unit in-service times Yes COTS/system default functionality • Unit out -of -service times Yes COTS/system default functionality • Personnel assigned Yes Assumes "assigned" means units dispatched to the same event - Hexagon clarifies that it has proposed I/CADLink for interfaces System must provide a close to real time feed to several Firehouse, IPCREMS, to ImageTrend, ESO Solutions and iPCR and I/FRMS- ImageTrend, ESO solutions, RMS databases- If the vendor currently does not have a CAD Yes CADLink to FIREHOUSE FIRMS and configuration services to Module for your product include a separate line item to develop an interface- interface with multiple FIREHOUSE RMS databases- Hexagon welcomes further discussion on this requirement - The incident definition will include a discrete field for a matching NFIRS Code- This code Hexagon has included as part of overall implementation will be attached to the incident record for later reporting or passing to an agency's RMS Modification services a level of effort to customize the CAD database to add a column for capturing the code and add a field for this - All run data required for initiating and completing incident reports is available to an Assumes "all run data" to mean what has been configured authorized user at any time- A unit will not have to wait until an event is closed before the Yes within our interface - The system supports, at a minimum, the capture/transfer from CAD of the following data elements for each CAD event: • Incident number Yes Assumes this to be the event number in I/CAD • Report number Yes Assumes this to be the case number in I/CAD • Call location Yes COTS/system default functionality • Street Direction Yes COTS/system default functionality • Street Number Yes COTS/system default functionality • Street Name Yes COTS/system default functionality • Street Type Yes COTS/system default functionality • Beat Yes COTS/system default functionality • Call type - initial Yes COTS/system default functionality • Call type - final Yes COTS/system default functionality • Alarm levels Hexagon has proposed to add Alarm levels for data Modification capture/transfer as part of the overall implementation services bid- • Caller location Yes COTS/system default functionality 53 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-Interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-077 5-078 5-079 5-080 5-081 5-082 5-083 5-084 5-085 5-086 5-087 5-088 5-089 5-090 5-091 5-092 5-093 5-094 5-095 5-096 5-097 5-098 5-099 5-100 5-101 5-102 5-103 5-104 • Fire district Yes Hexagon assumes Fire District to mean either the municipality of the event the events bea station area),zone or district- • Caller name Yes COTS/system default functionality • Alternate call back number Modification Hexagon has proposed to add "Alternate call back number'for data capture/transfer as part of the overall implementation services bid- • Call priority Yes COTS/system default functionality • Call back field (date and time) Yes COTS/system default functionality • Remarks Yes COTS/system default functionality • Disposition (unlimited) Yes Default system functionality • Time call received Yes COTS/system default functionality • Time dispatched Yes COTS/system default functionality • Time first unit responded Yes Assumes Unit History and this status is the Acknowledge status in I/CAD • Time first unit arrived Yes Assumes Unit History • Time first unit cleared Yes Assumes Unit History • Time last unit cleared Yes Assumes Unit History The system supports, at a minimum, the capture/transfer from CAD of the following data elements for each unit logged on during a shift: • Unit ID Yes COTS/system default functionality • Vehicle ID Yes COTS/system default functionality • Agency ID Yes COTS/system default functionality • Unit in-service times Yes COTS/system default functionality • Unit out -of -service times Yes COTS/system default functionality • Personnel assigned Yes Assumes "assigned" means units dispatched to the same event - The system supports, at a minimum, the capture/transfer from CAD of the following data elements for each event to which a unit was assigned: • Unit ID Yes COTS/system default functionality • Vehicle ID Yes COTS/system default functionality • Agency ID Yes COTS/system default functionality • Time dispatched Yes COTS/system default functionality • Time acknowledged Yes COTS/system default functionality • Time enroute Yes COTS/system default functionality • Time arrived Yes COTS/system default functionality 5-1 nterfaces 54 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-Interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-105 5-106 5-107 5-108 5-109 5-110 5-111 5-112 5-113 5-114 5-115 5-116 5-117 5-118 5-119 5-120 5-121 5-122 5-123 5-124 • Agency -defined milestones (e.g., staging, fire under control, fire knocked down, rescue complete, PAR) Yes Assumes Fire MPS - Incident Command form • Time departed for transport Yes Assumes this will be time going into Transport status • Time arrived for transport Yes Assumes this will be time going into Transport Arrive status • Destination hospital Yes COTS/system default functionality • Time at hospital No Not currently supported • Patient Offload Hexagon has proposed as part of overall implementation Modification services a level of effort to add this custom unit status to CAD. • Time clear from hospital Hexagon has proposed as part of overall implementation Modification services a level of effort to add this custom unit status to CAD. • Time available Yes COTS/system default functionality • Time cleared Yes COTS/system default functionality Provide a list of what RMS's the proposed system has existing interfaces to. Yes ESO, Firehouse, ImageTrend, Emergency Reporting The system shall provide user interfaces, meaning command line and forms in support of the following modules and interfaces: • Security Yes All security permissions are maintained through CADDBM on _ The proposed interfaces do not support Command Line. Hexagon does offer an Incident Command feature in MPS for • Incident Management No Fire. Buttons with various Fire Command statuses are included-, however, there is not a full blown Incident Manaciement interface. • Unit Management Alternate Yes for both CAD & MPS for user interfaces. However, Command line is not available in Mobile for Public Safe . • Status Monitors Alternate Yes for both CAD & MPS for user interfaces. However, Command line is not available in Mobile for Public Safe . • Contractor Rotation Yes All contract rotations are defined and maintained through CADDBM on . • Email Yes Assumes this is via I/Page using SMTP • Location and mapping pp g Alternate Yes for both CAD & MPS for user interfaces. However, Command line is not available in Mobile for Public Safe . • Toning and Paging Alternate Yes, for CAD. However, there is no toning from MPS • Radio interface No Not currently supported 5-1 nterfaces 55 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-Interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-125 5-126 5-127 5-128 5-129 5-130 5-131 5-132 Sl nterfaces I/CAD has no offline mode. The I/CAD database must be available, and connectivity to that database available from all • Offline Module No clients for the system to function. Hexagon has proposed a highly redundant and highly available solution to support the Coun 's needs. • External System Interfaces Yes Assume this is via (/Informer (optional) and Ani/Ali (included as art of CAD The system supports interfaces to external databases (Le., databases not directly hosted Yes Assumes this is via I/Informer (optional) and EdgeFrontier within the CAD network) - The system supports the capability for client -created interfaces. Yes Hexagon has proposed our EdgeFrontier Developer Engine and associated traininq course to support this re uirement- I/CAD has no offline mode. The (/CAD database must be The system shall have the ability to allow users to create/modify incident data if the available, and connectivity to that database available from all connection to the CAD server is lost (offline) for any reason and to upload the data into No clients for the system to function. Hexagon has proposed a CAD after the connection is reestablished. highly redundant and highly available solution to support the Coun 's needs. System must be able to interoperate with Priority Dispatch Pro Q & A (See 8-Pro Q & A tab Yes The I/Dispatcher product interfaces with Priority Dispatch for particulars) ProQA user can have more than one case active on a different Priority Dispatch Paramount discipline (Fire/Medical/Police). On one discipline, there should still be only one case active. If Priority Dispatch Paramount suggests another discipline is The interface to Pro CIA shall allow for the smooth transition out of one discipline to another NO needed for the call, the recommended discipline information is during the same call displayed within a Priority Dispatch Paramount message. The call taker creates a new event and clicks the associated ProQA button and/or menu to start the second case. If the first case has not been completed when the second case is started, the location, caller name, and phone number are sent to the second discipline when the call taker beings the second Every release of (/CAD is certified with a specific version of the The ProQA interface shall be able to handled the most current release of Priority Dispatch's Paramount application. I/CAD 9.4 is certified with Paramount Medical, Fire and combined ProQA products Alternate version 5.0.0.677. The protocol versions in use are independent of the (/CAD solution and can be updated as necessary- Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-133 5-134 5-135 5-136 5-137 5-138 5-139 5-140 5-141 5-142 5-143 5-144 5-1 nterfaces Unless replacing the Mobile Infrastructure is requested as part of your proposal the System Hexagon has proposed our UMDT to the Motorola Premier must interoperate with Motorola's Premier Mobile Data Computer System (See 9-Mobile Yes Message Switch to support this requirement. Tab for particulars If replacing the Mobile Infrastructure is part of your proposal the System should still be able Hexagon has proposed our UMDT to the Motorola Premier interoperate with Motorola's Premier Mobile Data Computer System side by side with your Yes Message Switch to support this requirement. s stem See 9-Mobile tab for particulars) Mobile or Public Satety Is a modern, feature rich mobile application that requires modern connectivity solutions such as If replacing the Mobile Infrastructure the system shall be able to work with both Netmotion, NO 3G, 4G, and 4G LTE. The Motorola Data-Tac system does RadiolP GPS Director, and Motorola Data-Tac not provide enough bandwidth for the MPS application to operate without a significant reduction in functionality resulting in unsatisfied user ex eienexagon currently pronsaIn a ace o numerous radio system platforms for the purpose of processing push -to -talk The system shall have the ability to interface with Lee Control's current and planned radio bannering and radio emergency processing. It is not possible systems which group radios to provide an effective method for radio communications Alternate to state, without equivocation, that our solutions will support between Dispatchers and field personnel any planned radio infrastructure without the plans being shared in sufficient detail with Hexagon as to formulate a The system shall have the ability to group radios into talkgroups so the same No I/PTT supports talkgroups but does not create them. communication can go to all at one time. The system shall have the ability to send alerts and alarms over the radio. Yes Assumes this is via the proposed I/PTT interface The system shall have the ability to display and search for radio assignment information. No Not currently supported The system shall display Push -to -Talk information from the radio system on the CAD status Hexagon clarifies that we have an add -in to I/Dispatcher that monitors. Alternate displays radio push -to -talk information, called I/Banner. It is not art of the status monitors. The system shall support radio alias synchronization with the Motorola radio system to NO The UCAD solution has no method to interact with the radio avoid duplicate maintenance of radio IDs_ stem for the maintenance of radio aliases. The UCAD solution can interface with P25 radio systems in a The system can interface with an Association of Public -Safety Communications Officials myriad of ways. However, Hexagon has not proposed an (APCO) Project 25-compliant radio system. No interface to a P25 radio system at this time. Hexagon welcomes the opportunity to discuss the County's specific needs. The I/CAD solution can interface with GPS-enabled portable The system supports the ability to interface with GPS-enabled portable radios that include Yes radios. Hexagon has proposed its (/Tracker interface and messaging capabilities. EdgeFrontier ASTRO 25 component to support person -level trackina with radios. The system supports radio alias synchronization with the Motorola radio system to avoid NO The I/CAD solution has no method to interact with the radio duplicate maintenance of radio IDs_ stem for the maintenance of radio aliases. 57 of 186 Company: Intergraph Corporation dlbla Hexagon Safety & Infrastructure 5-Interfaces Ver: 811512017 Item Number Interfaces Response Explanation 5-145 5-146 5-147 5-148 5-149 5-150 5-151 5-152 The I/CAD solution has the ability to interface with the radio system to provide alerts and alarms. However, Hexagon has The system can send alerts and alarms over the radio. No not proposed an interface to a specific radio system at this time. Hexagon welcomes the opportunity to discuss the Coun 's specific needs. The system can display and search for radio assignment information. No Not currently supported The system can perform radio assignments based on incident type and agency. No Not currently supported In addition to Station and Unit data, FSA can be configured to pass information from the following CAD tables in a dispatch message packet: The interface between The system and the radio system is capable of communicating the Yes AGENCY —EVENT STAGING data required to annunciate Locution event information. _AREA COMMON EVENT COMMON_ EVENT_ CALL EVCOM (Event Comments) Fire Station Alerting does not, however, support Relay Through the radio system interface, the system can display unit radio call signs (Push -to- Hexagon clarifies that we have an add -into (/Dispatcher that talk) on the CAD monitor screen when the field unit depresses the transmit key. displays radio push -to -talk information, called I/Banner. It isor not part of the status monitors. On activation of the field radio emergency button function, the radio system interface Hexagon clarifies that we have an add -in to I/Dispatcher that provides the field unit's radio call sign and last known location to all dispatch group Yes displays radio push -to -talk information, called I/Banner. It is workstations. not part of the status monitors. TDD Hexagon assumes this Is the current In a ace o e Intrado system using the "External TDD/TTY Interface with Power 911 Intelligent WorkStation - rev 2 May 31,2004" The system shall interface to a TDD device and allow Telecommunicators to converse on Alternate interface. The customer needs to contact their vendor to any line, E9-1-1 trunk seven digit, or IP based via a TDD window at their CAD Workstation. verify that their Power 911 consoles support this interface. All TDD conversation takes place in the phone application, not I/CAD. I/Dispatcher supports an interface to West TDD for 5-1 nterfaces 58 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-interfaces Ver: 811512017 Item Number Interfaces Response Explanation 5-153 5-154 5-155 5-156 5-157 5-158 5-159 5,-160 5-I1r49L'es The system supports an interface to a TDD device. Hexagon assumes this Is the current interrace to the Intrado system using the "External TDD/TTY Interface with Power 911 Intelligent WorkStation - rev 2 May 31,2004" Alternate interface. The customer needs to contact their vendor to verify that their Power 911 consoles support this interface. All TDD conversation takes place in the phone application, not I/CAD. I/Dispatcher supports an interface to West TDD for t_n.f.rria(Lthp Tr) The system attaches the TDD dialog to the event record. Hexagon assumes Is Is a curren In a He o e Intrado system using the "External TDD/TTY Interface with Power 911 Intelligent WorkStation - rev 2 May 31,2004" Alternate Interface. The customer needs to contact their vendor to verify that their Power 911 consoles support this interface. All TDD conversation takes place in the phone application, not I/CAD. I/Dispatcher supports an interface to West TDD for The TDD interface window displays the caller and operator's conversation separately as itom Hexagon assumes Is Is a curren In a aceTo e takes place (real-time). Intrado system using the "External TDD/TTY Interface with Power 911 Intelligent WorkStation - rev 2 May 31,2004" Alternate interface. The customer needs to contact their vendor to verify that their Power 911 consoles support this interface. All TDD conversation takes place in the phone application, not I/CAD. I/Dispatcher supports an interface to West TDD for The TDD interface window displays the caller and operator's conversation as different text No Not currently supported colors. The TDD interface window contains all the user pre -programmable messages grouped into Hexagon assumes this Is the current interface to the related categories. Intrado system using the "External TDD/TTY Interface with Power 911 Intelligent WorkStation - rev 2 May 31,2004" Alternate Interface. The customer needs to contact their vendor to verify that their Power 911 consoles support this interface. All TDD conversation takes place in the phone application, not I/CAD. 1/Dispatcher supports an interface to West TDD for Tone and Voice Paging The system shall have the ability to send tones and/or messages to individual pagers and groups of pagers and/or Fire Station toningsystems- Yes Hexagon has proposed the I/Page interface to send messages to the individual pagers or groups of pages - When CAD is interfaced with a toning/paging system, the following features are desired: The system shall have automatic and manual dispatch notification (toning). Yes Assumes I/Fire Station Alerting (I/FSA) Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-Interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-162 5-163 5-164 5-165 5-166 5-167 5-168 5-169 5-170 5-171 5-172 5-173 5-174 Sl nterfaces The system should have visual indication of when Public Announcement (PA) systems are No Hexagon assumes this is the function of Locution or other fire activated for broadcasts during toning sequences station alerting vendor - The system should have manual control of Fire station bay doors and other toning system No Control of the bay doors is a function of Fire Station Alerting devices system - The system should have automatic resetting of status lights on the control panels of the NO Hexagon assumes this is a function of the Fire Station Alerting toning/pagingsystems system - The system should have the ability to send text messages of incident details to Fire Station Yes Hexagon has proposed I/Fire Station Printing to meet this printers Tear & Run requirement - The system provides an interface with the existing radio system to perform tone alert Yes Hexagon assumes the existing radio system is one of the paging, if the capabilitV exists in the radios stem- systems we support Locution Zetron WestNet Mach Alert With a shared CAD system, the system interfaces with the radio console of each PSAP to Yes Hexagon assumes the existing radio system is one of the perform tone alert paging- sVstems we support Locution Zetron WestNet Mach Alert The system provides an interface with a dedicated programmable encoder to perform tone Hexagon requires additional information prior to committing to alert paging followed by a voice message, if the capability exists in the radio system- a Yes answer on this requirement- Hexagon assumes the No interface to the existing radio system is through one of the systems Hexagon currently supports (Locution, Zetron, The tone alert interface issues tone alert commands from CAD automatically: . Based on event type Hexagon clarifies that this may be dependent on the Fire Station Alerting system supporting this functionality- If using Yes Locution, FSA accumulates unit dispatch information for a particular event for a configurable amount of time and then sends that accrued stations and unit data to Locution . Based on units dispatched Hexagon clarifies that may this be dependent on the Fire Station Alerting system supporting this functionality- If using Yes Locution, FSA accumulates unit dispatch information for a particular event for a configurable amount of time and then sends that accrued stations and unit data to Locution . Based on station due Hexagon clarifies that this may be dependent on the Fire Yes Station Alerting system supporting this functionality- If using Locution this is configured as the First Due Station Alerts . Based on any combination of the above conditions Yes Hexagon clarifies that this may be dependent on the Fire Station Alerting s stem supporting this functionality - When the system is interfaced with a toning/paging system, the following features are available: 60 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-Interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-175 5-176 5-177 5-178 5-179 5-180 5-181 5-182 • Automatic and manual dispatch notification (toning) 5-1 Hexagon clarifies to manually generate a tone, the user needs to set up a pager definition for each FSA controller type. Then Yes select the FSA controller type as a pager. A dispatcher can use Send Message to manually trigger the tone. • Visual indication of when Public Announcement (PA) systems are activated for No This is a function of the third -party Fire Station Alerting broadcasts during toning sequences s stem. • Automatic resetting of status lights on the control panels of the toning/paging systems Hexagon assumes this is a function of the third -party Fire No Station Alerting system. The tone alerting interface can require some type of user interaction so the dispatcher can This is a function of the third -party Fire Station Alerting make the determination to send tones. No system. Note that you can manual send tones. See above for Details. The tone alerting interface allows the tone encoding of a unit from the command line (e.g., Hexagon clarifies that this is through the third -party Fire encode ENG1). No Station Alerting system. Note that a user can manually send a tone to a controller by setting up a paging definition. See ahnvp The tone alerting interface recognizes recommended multiple units with identical tones (such as multiple units from a single station) and only sends a single set of tones for those Hexagon assumes that is the function of the fire station units. No alerting vendor. Hexagon is able to configure the same alert address for multiple units/bays. The tone alerting interface provides the capability for tone signaling to initiate and monitor No This is a function of the third -party fire station alerting or the paging progress for call notification of responding personnel- paging s stem. The system provides a method to allow the training module to simulate the function of the Test, Training, Redundant, and Backup copies are available tone alerting interface, providing feedback but not actually performing activations. for all proposed interfaces; however, implementation is subject to the customer's ability to provide connection to the applicable system. Hexagon is able to install I/Page and/or UFSA in a test/training No environment; however, training licenses are not proposed for these at this time. Whether or not the tones are actually activated would be a function of the fire station alerting vendor. Hexagon welcomes further discussion on this requirement- nterfaces 61 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Interfaces Number 5-183 5-184 5-185 5-Interfaces ver: 811512017 Response Explanation tone alerting interface can operate in live, test, and training modes simultaneously. Test, Training, Redundant, and Backup copies are available for all proposed interfaces-, however, implementation is subj/ to the customer's ability to provide connection to the applicable system. Hexagon is able to install I/Page and/or I/FSA in a test/training No environment-, however, training licenses are not proposed for these at this time. Whether or not the tones are actually activated would be a function of the fire station alerting vendor. Hexagon welcomes further discussion on this requirement. External Feeds dependent on the third party features and APIs. Hexagon has proposed consulting services to discuss interface design for an interface to Econolite - Automated Traffic Management System (ATMS) with the County. Specific functionality would The system should be able to have an interface to pass Unit ID, Starting Point, Incident be determined during the design phase of the overall project. location (ending point), recommended travel directions, Run status to Lee County Once the design is mutually agreed upon by Hexagon and the Department of Transportation. This is to be used to control traffic control devices to assist No County, additional scope to develop and implement the the unit in reaching its destination while using Lights and Sirens and minimizing distruption interface can be determined and Hexagon can quote to normal traffic flow. development/implementation services for the interface at that time. Hexagon welcomes further discussion on this interface. Hexagon has experience with interfacing with traffic control devices for this purpose — (for example, at Palm Beach SI nterfaces 62 of 186 Company: Intergraph Corporation dlbla Hexagon Safety & Infrastructure 5-interfaces Ver: 811512017 Item Number Interfaces Response Explanation 5-186 5-187 5-188 5-189 5-190 5-191 5-192 5-15terfaces dependent on the third party features and APIs- Hexagon has proposed consulting services to discuss interface design for an interface to Econolite - Automated Traffic Management System (ATMS) with the County- Specific functionality would be determined during the design phase of the overall project - The system should receive traffic flow data from Lee County Department of Transportation Once the design is mutually agreed upon by Hexagon and the to assist CAD in determining the optimal unit to respond to an incident- No County, additional scope to develop and implement the interface can be determined and Hexagon can quote developmentlimplementation services for the interface at that time- Hexagon welcomes further discussion on this interface - Hexagon has experience with interfacing with traffic control devices for this purpose — (for example, at Palm Beach The system should be able to have an interface to State, County, and Municiple Traffic Further discussion is required and further information is Operation Center's Systems- This interface should allow permissions based access to each No needed on the various systems prior to providing a level of others' incident records with the abilitV to enter remarks based on localguidelines- effort for an interface to support this requirement - Hexagon welcomes further discussion with the County Either can or has the ability to interact with the following standards No regarding this requirement- Further information may be needed depending on the level of interaction desired with regard to these standards - Hexagon welcomes further discussion with the County 1512-2006 - IEEE Standard for Common Incident Management Message Sets for Use by No regarding this requirement- Further information may be Emergency Management Centers needed depending on the level of interaction desired with re and to these standards - Hexagon welcomes further discussion with the County National Transportation Communications fo ITS Protocol (NTCIP) No regarding this requirement- Further information may be needed depending on the level of interaction desired with regard to these standards - The mobile environment has an Real-time Live Video interface- No Hexagon clarifies that a video interface is not provided through Video Res onder for the mobile environment- FI exagon as proposed its VSight Server and Video Responder product to meet this requirement- Hexagon The Real-time Live Video module will interface with closed circuit television (CCTV) assumes a video plug-in is built for the camera system and Yes available for the Hexagon products to access- This proposal cameras- includes integration with only one video management system (VMS) of the County's choosing; any additional VMS would reou re add t onal scoop and or The video feed is accessed via hyperlink from a camera icon on the integrated map- Yes Hexagon clarifies video can be retrieved from a camera icon on the CAD map using Video Responder- 63 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-Interfaces Ver: 811512017 Item Number Interfaces Response Explanation 5-194 5-195 5-196 5-197 5-198 5-199 5-200 5-201 5-202 5-203 Sl nterfaces Hexagon clarifies this is dependent on the hardware and The Real-time Live Video component delivers video without buffering. No network components and capabilities of the third party vendor's video management s stem. The Real-time Live Video component adapts to situational bandwidth availability. No Hexagon notes that this is the responsibility of the third party vendor's video management system/network- Hexagon clarifies that using Video Responder, multiple The Real-time Live Video component allows video sharing among fixed resources. Alternate dispatchers can access a camera for viewing but only one user can control a camera at a time. The Real-time Live Video component allows video sharing among mobile clients. No Video Responder does not support a mobile environment. The Real-time Live Video component adapts to hardware capabilities of the mobile client. No Video Responder does not support a mobile environment. Hexagon can create a plug-in if the third party vendor provides an API/SDK that allows for the integration. The CAD system can integrate directly with IP cameras as well as Video Management Systems using Video Responder. Hexagon notes that further information is required on all of the third The Real-time Live Video component supports private, third -party sources. No party video management systems requiring integration with the CAD system before implementation of the product can begin. Hexagon welcomes further discussion with the customer on this requirement. This proposal includes integration with only one video management system (VMS) of the County's choosing, any additional VMS would require The system will have the ability to display on the map the location of of fixed security Yes For Video Responder, the location of fixed security cameras cameras. can be displayed as map icons on the CAD map. The system will have the ability to allow the Telecommunicator (Call Taker -Dispatcher- Yes This requirement can be supported assuming Hexagon has Dispatch Supervisor) to view the camera video. access to a video plug-in built for the videosystem- The system will present a single or common camera interface regardless of camera system Yes This requirement can be supported assuming Hexagon has type access to a video lu -in built for id the veorj7s stem. The system will have the ability to display video from in -car video systems Mg e UITITS, can display video from in -car video systems assuming Hexagon has access to a video plug-in built for the video system. Further discussion is needed on all video No management systems requiring integration with the CAD system prior to implementation of Video Responder to support video management system requirements. This proposal includes integration with only one video management system (VMS) of the County's choosing, any additional VMS would 64 of 186 Company: Intergraph Corporation d/bla Hexagon Safety & Infrastructure 5-Interfaces Ver: 811512017 Item Number Interfaces Response Explanation 5-204 5-205 5-206 5-207 5-208 5-209 5-210 5-211 5-212 5-213 5-214 5-215 5-216 5-217 5-1 nterfaces The system will have the ability to allow mobile users access to video from fixed or mobile sources. No Not currently supported. This may require a customization at additional cost not currently proposed. Hexagon welcomes further discussion on this requirement - Hexagon has proposed an EdgeFrontier interface for ASAP alarm integration. If interfaces to other alarm monitoring The system has a bi-directional interface to external alarm monitoring companies. Yes companies are required, these would require additional services at additional cost not currently proposed. Hexagon welcomes further discussion on this reauirement. The external alarm monitoring company interface utilizes the most recently developed Yes Hexagon has proposed an EdgeFrontier interface for ASAP Automated Secure Alarm Protocol ASAP specification. alarm integration. Automatic Vehicle Location Hexagon assumes this is the I!f racker interface and that the Data from the AVL module can be used to determine real-time unit location. Yes GPS devices provide the AVL data in one of the supported formats. Hexagon assumes this is the 1/17racker interface and that the Data from the AVL module is integrated with the CAD system. Yes GPS devices provide the AVL data in one of the supported formats. Data from the AVL module is available to all agencies, jurisdictions, and units on the Hexagon assumes the proper sharing permissions and inter - system. Yes agency agreements are in place. This would not be Inte ra h's i)olicv to im dement. Hexagon assumes a e Ir party mobile solution Is the Motorola Premier Message Switch indicated and that the Data from the AVL module can be shared with third party applications, (e.g., Third Party proposed I/MDT to the Motorola Premier Message Switch will Mobile Data Solutions). Yes meet this requirement. If another third party mobile solution requires an interface, it may require additional services at additional costs not currently proposed as some .trk files will The system allows AVL data to be restricted from sharing based on agency, jurisdiction, Alternate The "AVL data" will be stored in a secure location and the user role and unit by an authorized user. hosting agency would be the entity to allow/disallow access. The system allows the AVL component to be implemented by: Hexagon assumes this is the (/Tracker interface and that the • Unit Yes GPS devices in the Unit is providing the AVL data in one of the supported formats. • Group Yes Hexagon assumes this is in reference to Polling Groups • Agency Yes Hexagon assumes this filtering of the map and monitors based on dispatch group and agency- AVL can be toggled on/off by an authorized user at the agency's discretion. Yes Hexagon clarifies that this is through the Interface Service Mana er. 65 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-Interfaces Ver: 811512017 Item Number Interfaces Response Explanation 5-218 5-219 5-220 5-221 5-222 5-223 5-224 5-225 5-226 5-227 Sl nterfaces Unit AVL data is used in unit recommendations by agency/group, implemented by an Yes This would be via configuration of CADDBM parameters, MDT authorized agency user. server and MPS included as art of this ro osal e nl ecommen a Ion ervIN Is cons an y Deing updated with the current state of the system including event The system will continuously re -poll for a closer resource meeting the resource needs and, Yes status, unit status, unit location, unit properties, etc. The real - if available, re -recommend a more appropriate unit until the arrival of a unit on- scene. time recommendation monitor can alert dispatchers to conditions that may require the re -allocation of units to higher or or tv events or rp-d rprt un ts to events they are closer to The (/Tracker interface product provides the interface between a 3rd party AVL controller/message switch and the CAD Unit AVL data is used in vehicle routing. Yes system to display the location of the units on the map. Note that the AVL information provided may be used in the CAD system in the Recommend Unit rocessin . The (/Tracker interface product provides the interface between a 3rd party AVL controller/message switch and the CAD Unit AVL based positions are displayed on the integrated CAD workstation map. Yes system to display the location of the units on the map. Note that the AVL information provided may be used in the CAD system The (/Tracker interface product provides the interface between a 3rd party AVL controller/message switch and the CAD Unit AVL based positions are displayed on the integrated CAD mobile workstation map. Yes system to display the location of the units on the map. Note that the AVL information provided may be used in the CAD The ([Tracker interface product provides the interface between a 3rd party AVL controller/message switch and the CAD Unit AVL based positions are updated on the map automatically. Yes system to display the location of the units on the map. Note that the AVL information provided may be used in the CAD system in the Recommend Unit rocessin . The frequency of AVL updates can be adjusted by unit, status, speed, and time elapsed. Yes This is through Mobile for Public Safety (MPS) and Hexagon con5cluration of pursuit mode in MPS. The system can interface with the AVL application independent of the mobile data Hexagon assumes that the third -party AVL devices can infrastructure. Yes provide the GPS data in one of the currently supported protocols - The AVL module can be toggled on and off without degradation of CAD system Yes Hexagon clarifies that this is through the Interface Service responsiveness- Mana er ISM that is art of the CAD s stem. r I es can e p aye ac m our rac er ay ac The system supports AVL playback function for units on a map based on user, role, application (included as part of I/Tracker). Access to security. Alternate I/TrackerPlayback isn't restricted based on user, role or security pre se but can be installed in a secure location so the aaency can allow/disallow access. 66 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-Interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-228 5-229 5-230 5-231 5-232 5-233 5-234 5-235 5-236 5-237 5-238 5-239 5-240 5-241 Sl nterfaces The system interfaces with the AVL application to produce event and unit playback activity Hexagon clarifies that this is using the I/TrackerPlayback using the existing CAD mapping module. Alternate application which uses the I/CAD map to display the unit activities. The system interfaces with the AVL application to capture unit data regarding current and This is dependent on they protocol being used and whether it conditions (e.g., status of emergency lights and sirens). No is supported. Additional information on the GPS device and protocols is needed. The system interfaces with the AVL application to capture unit data to enable the following reports: • Vehicle activity Yes Hexagon assumes "vehicle activity" means AVL positioning re orts. • Speed Yes Assuming the necessary protocol is used. • Location Yes Hexagon assumes this location based on the provided AVL position reports Routing within CAD and the mobile unit is depended on the • Vehicle routing Yes Unit location and if the information is provided by the AVL position re orts. • Deviation of Best -Path Routing Yes Assuming this to mean, if the unit takes an alternate route the mobile client AVL will update using that route. CAD -to -CAD Interface Hexagon has proposed multiple CAD -to -CAD interfaces via its The system provides an interface to connect with non-native CAD systems for dispatching, Yes EdgeFrontier integration platform to support this requirement information sharing, and situational awareness. (interfaces to Spillman's CAD, TriTech's CAD, Motorola CAD, and OSSI CAD) - Hexagon has proposed multiple CAD -to -CAD interfaces via its The CAD -to -CAD interface is bi-directional. Yes EdgeFrontier integration platform to support this requirement (interfaces to Spillman's CAD, TriTech's CAD, Motorola CAD, and OSSI CAD) - Hexagon has proposed multiple CAD -to -CAD interfaces via its The CAD -to -CAD interface facilitates the transfer and receipt of incident data between the Yes EdgeFrontier integration platform to support this requirement interfaced systems. (interfaces to Spillman's CAD, TriTech's CAD, Motorola CAD, and OSSI CAD) - The CAD -to -CAD interface facilitates assignment and tracking of the closest available Hexagon has proposed multiple CAD -to -CAD interfaces via its resource to an event, even though the resource is not within the official jurisdiction of the Yes EdgeFrontier integration platform to support this requirement dispatching agency. (interfaces to Spillman's CAD, TriTech's CAD, Motorola CAD, and OSSI CAD) - Hexagon has proposed multiple CAD -to -CAD interfaces via its The CAD -to -CAD interface provides CAD incident data to all mobile units assigned to the Yes EdgeFrontier integration platform to support this requirement incident, regardless of home agency. (interfaces to Spillman's CAD, TriTech's CAD, Motorola CAD, and OSSI CAD). 67 of 186 Company: Intergraph Corporation dlbla Hexagon Safety & Infrastructure 5-Interfaces ver: 811512017 Item Number Interfaces Response Explanation 5-242 5-243 5-244 5-245 5-246 5-247 5-248 5-249 In order to meet this requirement, Hexagon has proposed our EdgeFrontier Developer product and associated training The vendor will provide the ability for future CAD -to -CAD interfaces. Yes services for Lee County to create its own interfaces. If the County desires Hexagon to create these, then additional information is required at the time of request and additional The CAD -to -CAD interface provides the ability for connected CAD systems to share, at a minimum: Hexagon has proposed multiple CAD -to -CAD Interfaces via Its • Events Yes EdgeFrontier integration platform to support this requirement (interfaces to Spillman's CAD, TriTech's CAD, Motorola CAD, and OSSI CAD) - Hexagon has proposed multiple CAD -to -CAD interfaces via its • Units Yes EdgeFrontier integration platform to support this requirement (interfaces to Spillman's CAD, TriTech's CAD, Motorola CAD, and OSSI CAD) - Hexagon has proposed multiple CAD -to -CAD interfaces via its • AVL information Yes EdgeFrontier integration platform to support this requirement (interfaces to Spillman's CAD, TriTech's CAD, Motorola CAD, and OSSI CAD) - Hexagon has proposed multiple CAD -to -CAD interfaces via its • Premises information Yes EdgeFrontier integration platform to support this requirement (interfaces to Spillman's CAD, TriTech's CAD, Motorola CAD, and OSSI CAD). Further clarification is needed on this requirement prior to • Security profiles No Hexagon being able to indicate that it can be supported by the proposed interface. Hexagon welcomes further discussion on this requirement - Further clarification is needed on this requirement prior to • Audit log entries No Hexagon being able to indicate that it can be supported by the proposed interface. Hexagon welcomes further discussion on this r uirement. SI nterfaces 68 of 186 Company: Intergraph Corporation dlbla Hexagon Safety & Infrastructure 5-Interfaces Ver: 811512017 Item Number Interfaces Response Explanation 5-250 5-251 5-252 5-253 5-254 5-255 5-256 5-257 5-1 nterfaces exagon nas proposed multiple UAU-tO-UAU interfaces via its EdgeFrontier integration platform to support this requirement (interfaces to Spillman's CAD, TriTech's CAD, Motorola CAD, and OSSI CAD). Messages received are supported assuming . Messaging Yes that the third party CAD systems know and use Hexagon's CAD terminal addresses. Messaging is dependent on the ability for Hexagon to look up and route messages from the Hexagon CAD system to the third party systems. The destination terminals for messages must be included as part Hexagon has proposed multiple CAD -to -CAD interfaces via its EdgeFrontier integration platform to support this requirement . Radio channel designations Yes (interfaces to Spillman's CAD, TriTech's CAD, Motorola CAD, and OSSI CAD). Hexagon assumes the radio channel is stored in the event portion of the CAD database. The CAD -to -CAD interface enables authorized users of the connected CAD systems to: This can be supported, but Hexagon must have agreement from all of the third party vendors of the CAD systems and . Dispatch units from connected agencies Yes those vendors must also be able to support this requirement. This is based upon agreed upon rules between Hexagon and the third party CAD vendors. This can be supported, but Hexagon must have agreement from all of the third party vendors of the CAD systems and . Combine units from connected agencies on a single event Yes those vendors must also be able to support this requirement. This is based upon agreed upon rules between Hexagon and the third a CAD vendors. is can a suppo e u exagon must nave agreement from all of the third party vendors of the CAD systems and . Perform closest unit dispatching using AVL/GPS location Yes those vendors must also be able to support this requirement. This is based upon agreed upon rules between Hexagon and the third party CAD vendors. The third party vendors must be i in a exagon sys em, exagon s ores a um an event chronology so this requirement can be supported for . Report listing statistics from all units associated with an event Yes any units assigned to Hexagon CAD system events. Any Hexagon units assigned to third party CAD system events would be indicated in the Unit History tables in the Hexagon CA system The system will notify the home agency when units are dispatched by other than the home Yes This can be supported, but specific business rules will need to agency- be defined during the design phase of the proiect. 69 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-intern— ver: 8/15/2017 Item Number interfaces Response Explanation 5-258 5-259 5-260 5-261 5-262 5-263 Personnel/Staffing Interface The system can interface with third -party personnel scheduling software (e.g., Telestaff, Modification Hexagon has proposed to develop an EdgeFrontier interface Aladtec). to TeleStaff to support this requirement. The system provides a vendor -developed personnel scheduling module. No A Personnel scheduling module is not included as part of the CAD system. E-9.1.1 Interfaces -Hexagon considers this interrace to be accounted or In the proposed solution via our ANI/ALI interface (included as part of I/Executive HA for the CAD system). This is based on the The system shall be compatible with or account for interfaces with VIPER® version 5.1. Yes County's response in Addendum, #1 Q&A 3. Hexagon understands that per Addendum, #1 Q&A 3, the County's interest is that the proposed system can receive and process E-9-1-1 information from the West Corp (Intrado) VIPER Hexagon considers this interface to be accounted for in the proposed solution via our ANI/ALI interface (included as part of I/Executive HA for the CAD system). This is based on the County's response in Addendum, #1 Q&A 4. The system shall be compatible with or account for interfaces with PowerPhonee version Yes Hexagon understands that per Addendum, #1 Q&A 4, 6.1. PowerPhone is a colloquialism for West Corp (Intrado) Power 9-1-1, and an interface to software solutions by the vendor PowerPhone is not desired. Hexagon understands the County's interest is that the proposed system can receive and process E-9-1-1 information from the West Corp (Intrado) Power 9-1-1 system- 5-1 nterfaces 70 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 5-intenaces ver: 8/15/2017 Item Number interfaces Response Explanation 5-264 5-265 proposed solution. Hexagon's 1/CAD system has a fully integrated map solution capable of displaying landline, phase 1 wireless, and phase 2 The system shall be compatible with or account for interfaces with MapFlex® version 2.1. Yes wireless callers on the map. Based on the County's responses in Addendum #1, Q&A 2 concerning the MapFlex interface, Hexagon understands that if a bidder has the map fully integrated between the two systems, then this interface is being accounted for. The proposer shall have a plan to incorporate Next Generation 911 standards into the Hexagon is actively working on its vision to deliver I/CAD proposed system. Yes System's integrating functionality related to emerging NextGen 9-1-1 technologies and standards 5-Interfaces 71 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 14.. w. Number 6-001 6-002 6-003 6-004 6-005 6-006 6-007 6-008 6-009 6-010 6-011 GIS Response Explanation Unit Routing Changes made to the Routing component shall not have to be re-entered after a map Hexagon assumes the "routing component" to update. Yes mean the status of roads as open, closed, or restricted. Changes made to the Routing component shall only have to be made at one Hexagon assumes the "routing component" to workstation/server and be propagated across the entire system Yes mean the status of roads as open, closed, or restricted. The ability to make changes to the routing component (close or open streets) shall be based Hexagon clarifies that security is defined at on security levels. Yes the command class and during im lementation this can be configured. Hexagon clarifies that an intersection itself The routing component shall have a method for fully or partially closing intersections. No cannot be closed. The segments leading into an intersection can be restricted. I/CAD provides a Schedule Restriction The routing component should have a method for scheduling the closing and reopening of Yes command. Users can enter for example, a intersections or street segments scheduled date and time, frequency, day of the week and/or time of the day. Unit routing uses the street network. Within I/CAD the Initiate Router command Yes loads the routing data into memory and use street network information. Unit routing assistance is adjusted due to active road closures. Yes I/CAD takes into consideration road closures when routing to an incident. Unit routing is adjusted (rerouted) due to real-time changes in global positioning system If the unit is GPS equipped, then Mobile for (GPS) position. Public Safety takes into consideration GPS Yes data when routing a unit to the incident. The Recommend Unit function can take into consideration the closest unit. The system utilizes a unit's AVL location as the starting point for unit routing. If the unit is G PS equipped, the Mobile for Yes Public Safety takes into consideration GPS data when routing a unit to the incident. The system supports unit routing based on both shortest distance from a unit's location to Within Mobile for Public Safety routes are the assigned event location. based on either shortest time, shortest Yes distance, risk (ex. one-way streets, turns, speed limits, restrictions, number of turns), or fewest intersections. 6-GIS 72 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-ciS ver: 8/15/2017 It em GI$ Number 6-012 6-013 6-014 6-015 6-016 6-017 6-018 6-019 6-020 6-021 6-022 6-023 6-A�24 Response Explanation The system supports unit routing based on fastest driveable route from a unit's location to Within I/CAD routes are based on either the assigned event location. shortest time, shortest distance, risk (ex. one - Yes way streets, turns, speed limits, restrictions, number of turns), or fewest intersections. The system supports unit routing with operator -designated start and end point. Users can specify way points or stops (addresses) on the route. Within Mobile for Yes Public Safety if a user enters only one waypoint then a route is generated from the unit's location to the location the user entered. The system supports the creation and maintenance of traffic detours due to road Yes Hexagon stipulates that this would be road construction or other events. restrictions. Unit routing accounts for detours. Yes I/CAD takes into consideration road closures when routing to an incident. Unit routing accounts for road attributes (e.g., speed limits, one-way streets). I/CAD takes into consideration road Yes restrictions such ad speed limit and direction when routing to an incident. The system is capable of incorporating turn restrictions from ESRI Network Analyst. Yes I/CAD uses a blockage mask to represent this information. The system highlights the calculated route on the map. The map displays the route once the user Yes selects to OK in I/CAD or Route waypoints in Mobile for Public safety. The mobile system supports annunciated turn -by -turn directions between any two points on Yes Users within Mobile for Public Safety can turn the map on mobile devices. off or on the verbal routing capability. Annunciated turn -by -turn directions may be toggled on and off at an operator's discretion. Yes Users within Mobile for Public Safety can turn off or on the verbal routing capability. The routing module can reset the route based on the current unit location. If the unit deviates from the current route, Yes Mobile for Public Safety will adjust the routing. When a route is reset, the system annunciates based on the reset route. If the unit deviates from the current route, Yes Mobile for Public Safety will adjust the routing. e ability o have the CAD system send recommendation requests Tor best path routing to the mapping applications including road conditions (e.g., closures, hazard warnings), then No Not currently supported display the recommendations to the Dispatcher. The ability to report when responding unit deviates from best path routing. I No Not currently supported 73 of is Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GiS ver: 8/15/2017 Item GAS Response Explanation Number e ability o sendnotification o designated users when responding unitdeviates from es 6-025 path routing. No Not currently supported 6-026 6-027 6-028 6-029 6-030 6-031 6-032 6-033 6-034 6-035 6-036 6-037 6-038 6-039 6-040 6-041 6-042 6-043 6-044 6-045 s-(G--046 Mapping The Geofile shall: • Validate that the street name is an actual street in the service area Yes Hexagon assumes this is the current 'location verify" functionality within the CAD system. Hexagon clarifies that if the location cannot be • Resolve ambiguities while accounting for spelling variations and duplications Yes resolved a list of possible matches are displayed for the user to select from. • Validate Intersections Yes Default system functionality • Relate common place names to actual addresses Yes Default system functionality • Relate X/Y/Z coordinates to an actual address Alternate The I/CAD system does not store Z coordinates, only X/Y. • Transform latitude and longitude to map coordinates for display Yes Default system functionality • Translate call location to agency reporting areas Yes Default system functionality • Translate alias names to actual street names Yes IDefault system functionality AVL Data, Lat/Longs, should geo code and send a text location to the Unit Status Monitor as Yes Default system functionality well as track the unit on the workstation map. GIS or Geofile updates to CAD shall not disrupt live CAD operations. Yes Default system functionality The existing map datasets and/or map layers must be able to be loaded and utilized by the Yes Default system functionality CAD system, at a minimum The system shall have ability to have user defined map layers for information, at a minimum the following: • Digital orthophotography Yes Default system functionality. Imagery must be provided by the County. • Pictometry Hexagon stipulates that we only interface to Yes the Electronic Field Study (EFS) application for Pictometry, CAD EFS Mobile ActiveX. • Parcel Yes Default system functionality • Roadways Yes Default system functionality • Parks Yes Default system functionality • Building footprints Yes Default system functionality • Agency -developed map layers Yes Default system functionality 74 of 18 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS Ver: 8/15/2017 14--- Number 6-047 6-048 6-049 6-050 6-051 6-052 6-053 6-054 6-055 6-056 6-057 6-058 6-059 6-060 6-GIS GIS Response Explanation • Waterways Yes Default system functionality • Agency -developed polygons (e.g., fire districts, geographical service areas) Yes Default system functionality • Political boundaries Yes Default system functionality • Neighborhoods Yes Default system functionality • Hydrants Yes Default system functionality • Railroad lines Yes Default system functionality • Communication towers (e.g., cell phone, commercial broadcast) Yes Default system functionality • Live CATV camera locations (e.g., traffic cameras, security cameras). Yes Default system functionality The GIS administrator shall have the capability to add, delete, change, update map datasets Yes Default system functionality and/or map layers on the CAD system as needed in order to meet all agency needs. The system shall accept all map data in ESRI formats (Enterprise (SDE) Geodatabase, Personal or File Geodatabase, shapefile, map layers) and perform any necessary Yes Default system functionality conversions. The system is capable of displaying map layers that are updated live from external sources, at a minimum: Hexagon stipulates that this may be possible with additional customization, but this feature • Traffic No is not included in our proposal at this time. Additional services may be required at additional cost. Hexagon welcomes further discussion on this re uirement. Hexagon stipulates that this may be possible with additional customization, but this feature • Weather (live updates) No is not included in our proposal at this time. Additional services may be required at additional cost. Hexagon welcomes further discussion on this re uirement. Hexagon stipulates that this may be possible with additional customization, but this feature • Flooding (live updates) No is not included in our proposal at this time. Additional services may be required at additional cost. Hexagon welcomes further discussion on this re uirement. 75 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GiS ver: 8/15/2017 Item GAS Response Explanation Number 6-061 6-062 6-063 6-064 6-065 6-066 6-067 6-068 6-069 6-070 6-071 6-072 6-073 6-074 6-075 6-076 6-077 6-078 Hexagon stipulates that this may be possible with additional customization, but this feature • Out -of -service hydrants (live updates) via ESRI Map service No is not included in our proposal at this time. Additional services may be required at additional cost. Hexagon welcomes further discussion on this re uirement. When unit or event icons are too close to be displayed accurately, the individual tags are Unit and Incident Icons will not stack on each other, but will cascade with a pointer showing Alternate replaced with a group tag. When hovered the item's location on the map. over, the group tag contains a tooltip that shows the units or events contained in the aroup to . The Geofile shall have the capibility to search for duplicate incidents based on distance from Yes Default system functionality the new incident location The search distance shall be configurable by the user Alternate Hexagon stipulates that this is an agency wide setting,not per user. The search distance should be configurable by area, roadway name/type, and incident type No Not currently supported shall have the ability to maintain a geographic database which includes: Hexagon clarifies that high and low cross • Street records (high, low, cross -streets) Alternate streets are not stored. We store the names of the nearest cross streets to each location. • Common place names Yes Default system functionality • Aliases Yes Default system functionality • Intersections Yes Default system functionality • Latitude/longitude and state plane coordinates Yes Default system functionality • Map references (zone, grid) Yes Default system functionality • Jurisdiction Yes Default system functionality • Geographic service area boundaries (e.g., patrol beat, sub beat) Yes Default system functionality • Water based response districts Yes Default system functionality • Zip code Yes Default system functionality • Sub -division names Yes Default system functionality • Report Districts Yes Default system functionality 6-6--079 Location Validation 76 of 18 Company: Item Number 6-081 6-082 6-083 6-084 6-085 6-086 6-087 6-088 6-089 6-090 6-091 6-092 6-093 6-094 6-095 6-096 6-097 6-098 6-099 6-100 6-101 Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 GIS Response Explanation The system shall have the ability to validate all location entries against a master geofile Yes Default system functionality Ability to support the following location entries: e Exact address (including''/2 addresses) Yes Default system functionality e Apartment number (e.g., ''/2, #5, 2D, D2) Yes Default system functionality e Apartment building name or number Yes Default system functionality e Block range Yes Default system functionality e Street name Yes Default system functionality e Common place name Yes Default system functionality e City Yes Default system functionality e Intersections Yes Default system functionality e Partially spelled or misspelled street names Yes Default system functionality e Street alias Yes Default system functionality e Street abbreviation Yes Default system functionality • Limited access roadways and highways Yes Default system functionality • Mile marker locations Yes Default system functionality In a separate attachment vendor shall describe in detail the location validation process Yes Hexagon has included a document detailing the location validation process as an attachment with our response. Please see Attachment 4.3. Location Validation functionality apply to all CAD users (e.g., PSAP based, mobile). Yes Default system functionality The system utilizes the progressive filtering of the possible street names on entry of the characters in the street name field beginning with the first character entered. No Not currently supported The system shall have the ability to enter a valid street name and be presented with a list of cross streets and associated address ranges Yes Hexagon stipulates that the operators must provide the first street name, followed by a slash (/) followed by the percent sign (%) to indicate wildcard intersection search. The system shall have the ability to enter a partial street name and be presented with a list of possible matches Yes Default system functionality The system shall have the ability to enter a misspelled street name and be presented with a list of possible matches Yes Default system functionality 6-GIS 77 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 It em GI$ Number 6-102 6-103 6-104 6-105 6-106 6-107 6-108 6-109 6-110 6-111 6-112 6-113 6-114 6-115 6-GIS Response Explanation The system shall have the ability to enter a unique building and unit number to clearly identify Hexagon stipulates that operators input the the location (e.g., 100 Marshal ST, Bldg. 5, Unit 13) apartment and building as part of the location using delimeters. The comma (,) is used to Yes delineate an apartment, and the semi -colon (;) is used to delineate a building. Apartment must be entered first, following by building. For example, 100 W MAIN ST,12;B would be 100 W MAIN ST building B, apartment 12. The system shall have the ability to enter common street alias and abbreviations instead of Yes Default system functionality the actual street name i.e. MLK for Martin Luther King Blvd. Addition of the address number adds to the filter for location validation, further focusing the Yes Default system functionality search. The results of the progressive filtering process are displayed as a drop down list. No I/CAD does not provide progressive filtering. The system generates a list of possibilities from which to pick if an exact match is not found Yes Default system functionality during location validation. An operator can pick a possibility from the list to continue the location validation process or Yes Default system functionality continue entry of the location manually. The system previews possible location matches by displaying cross streets, responder No Not currently supported information and displaying the location points on the integrated map. The system accurately processes complex street names (e.g., East North Broadway Street). Hexagon stipulates that in this example, and any other similar occurrence, "East' must be Yes the prefix (segme.dirpre) and "North Broadway" must be the feature name st cd.feanme . The system accurately processes street numbers with fractions (e.g., 32'/z E North Hexagon clarifies that our location verification Broadway St). Yes routine will accept 1/2 addresses, but it does not affect the interpolation of the location along the center line. The system accurately processes a location with an apartment number. Yes Default system functionality The system accurately processes a location from a point -and -click on the integrated map. Yes Default system functionality The system validates a location without creating an event. Yes Default system functionality The system can use a hot key to display an entry form. Yes Default system functionality In this case, the system will process the location and return the recommendations without Yes Default system functionality creating an event. Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS Ver: 8/15/2017 Item GAS Response Explanation Number 6-116 6-117 6-118 6-119 6-120 6-121 6-122 6-123 6-124 6-125 6-126 6-127 6-128 6-129 6-130 6-131 6-132 6-GIS If an event location is changed, the system automatically initiates the location validation Yes Default system functionality rocess. It is possible to bypass or override the automatic location validation process. Yes Default system functionality When an event is processed with an overridden location, the system presents a challenge No Not currently supported question to an operator to ensure the correct override is selected. When an event is processed with an overridden location, the event is flagged for later Yes Default system functionality reporting. When an event is processed with an overridden location, the system will provide a No Not currently supported notification message to a designated user account. The system can process an event without a validated location, which will then use a designated response area entered by an operator to route the event to the appropriate Yes Default system functionality dis atch workstation. The system processes location verification using an algorithm starting with address point and Yes Default system functionality continuing in a prioritized, systematic manner. When processing for location verification, the system can reference map layers in a Yes Default system functionality hierarchical method to obtain location information. The system can perform address validation when CAD is down. No Not currently supported A Soundex function is available when entering a location for validation. Yes Default system functionality Upon location validation, the system displays location on the map. Yes Default system functionality Upon location validation, the system displays the valid address with Common Place name, Yes Default system functionality when applicable. The system shall have the ability to override geofile by entering valid response area data Yes Default system functionality The system shall have the ability to override geofile for addresses outside the geofile limits Yes Default system functionality The system shall have the ability to generate a report of geofile overrides including all data, Yes Default system functionality Telecom municator ID date time Telecommunicator position The system shall have the ability to display geofile data when location is validated, including: . High and low cross streets Hexagon stipulates that I/CAD displays the names of the two nearest cross streets to any Yes validated location. For example 100 W MAIN ST would show cross streets of 1ST AVE W and 2ND AVE W 79 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 16 GIS Number 6-133 6-134 6-135 6-136 6-137 6-138 6-139 6-140 6-141 6-142 6-143 6-144 6-145 Response Explanation • City Hexagon stipulates that City names must not Yes contain any spaces. If City names have spaces, they must be replaced by underscores during map build processing. • Neighborhood Hexagon clarifies that the County must provide a GIS polygon feature that contains Yes the names of all neighborhoods so this information can be stored in a custom field via the I/CAD polygon attributes feature. • Common place or business name Yes Default system functionality • Response area Yes Default system functionality • Map page Hexagon clarifies that the County must provide a GIS polygon feature that contains Yes the names of all map pages so this information can be stored in a custom field via the I/CAD Polygon attributes feature. • Premise warnings or hazards by exact address, including bld & apt numbers Yes Default system functionality • Premise warnings or hazards within a configurable radius Yes Default system functionality • Prior incidents at exact address within a configurable period of time Yes Default system functionality • Jurisdiction/Agency Yes Default system functionality • Customized point in a polygon Yes Default system functionality • Mobile Park lot number Yes I Default system functionality Intersections maybe entered in any order (i.e. Main/1st or 1st/Main). The order of the entry shall not be altered. For example, if the user entered Main/1st, the CAD shall not convert the Yes Default system functionality entry to 1st/main. CAD should be able to verify an address by a street address range (e.g., entering " 100 S" Hexagon stipulates that a minimum of three would display all streets that have a 100 block and that start with "S"). characters are required in a feature name to Alternate get a list, or the operator must type a percent sign (%) to indicate the desire for a wildcard search. 6-GIS 80 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 Item GAS Response Explanation Number 6-146 6-147 6-148 6-149 6-150 6-151 6-152 6-153 6-154 6-155 6-156 6-157 6-158 6-159 6-160 6-161 CAD shall be configurable to allow entry of an address by a common place (e.g., entering "L" Hexagon stipulates a a minimum ot three would display all common places that start with "L"). characters are required in a common place name to get a list, or the operator must type a Alternate percent sign (%) to indicate the desire for a wildcard search. Further, operators must designate the at (@) symbol in the location line to tell I/CAD that they are providing a CAD shall be able to verify an address by an intersection (e.g., entering "L/S" would display Hexagon stipulates that a minimum of three all streets that start with "L" that intersect with a street that starts with "S"). characters are required in a feature name to Alternate get a list, or the operator must type a percent sign (%) to indicate the desire for a wildcard search. CAD shall allow the user to choose to bypass an unverifiable location to a valid location for 'urisdictional Yes Default system functionality purposes of assignment. If the location is bypassed to another valid location, the system should keep the unverified Hexagon stipulates that the operator would be location as the Incident Location and note the location used for verification as a note in the No responsible for adding the unverified location Incident History as a remark to the event. The system shall allow the agency to be able to configure whether non -verified locations Hexagon stipulates that all unverified locations shall be flagged. No are flagged. This cannot be changed. Ability to display the incident location in relation to other active incidents on the map during Yes Default system functionality the incident entry process The following are valid verifiable locations: . Civic address Yes Default system functionality . Longitude and latitude coordinates Yes Default system functionality • From 9-1-1 data Yes Default system functionality • From map click Yes Default system functionality • Direct entry Yes Default system functionality • In the following formats: Degrees, minutes, seconds Yes Default system functionality Degrees, decimal minutes Yes Default system functionality Decimal degrees Yes Default system functionality 6-GIS 81 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 It em GIS Number 6-162 6-163 6-164 6-165 6-166 6-167 6-168 6-169 Response Explanation • Military grid reference system (MGRS) Hexagon c ari ies that the County must provide a GIS polygon feature that contains that MGRS and the valid grid identifiers. The centroid point of each grid will be used as part Yes of the map build process to create special address points at each centroid, with the common place name for the point being a County designated value, such as @MGRS- • United States National Grid (USNG) exagon clarifies a e County must provide a GIS polygon feature that contains that USNG and the valid grid identifiers. The centroid point of each grid will be used as Yes part of the map build process to create special address points at each centroid, with the common place name for the point being a County designated value, such as @USNG- All • Intersection Yes Intersections are entered using the 'T' as a delimiter. • Cell towers Yes Hexagon assumes this is via Ani/Ali. • Block Yes Block style locations are entered with the - BLK designation. • Common name I/CAD supports the use of common name Yes locations. If more then one location is associated with the common name a dialog aopears with a lost of possible matches, • Apartment complex Yes Hexagon assumes this is a Common Place name. • Apartment building name or number The various address elements the system lets you enter include: Number, Direction, Street Yes name, Type, Suffix (direction), Area (for example, county or parish), Municipality, and 6-GIS 82 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 Item GIS Response Explanation Number 6-170 6-171 6-172 6-173 6-174 6-175 6-176 6-177 6-178 6-179 6-180 6-181 6-182 6-183 6-184 6-185 6-186 6-187 6-188 6-189 6-190 6-GIS • Mile markers Yes Hexagon clarifies that the County must provide a GIS point feature layer that provides these mile markers with appropriate attribution so as to have them named as common place names in I/CAD - for example @180 NB AT • Point from the integrated map Yes Default system functionality • Current location of an officer using coordinates Yes Default system functionality • Emergency call boxes on trails and highways Yes Hexagon clarifies that the County must provide a GIS point feature layer that provides these call boxes with appropriate attribution so as to have them named as common place names in I/CAD - for example @SOUTH • Interstate (limited access roadway) Yes Default system functionality • Interstate exits Yes Default system functionality The following are valid elements of a location eligible for location validation: • Directional prefix Yes Default system functionality • Numeric address, including fraction Yes Default system functionality • Hundred block Yes Default system functionality • Customized numeric range Yes Default system functionality • Street name Yes Default system functionality • Alias street name Yes Default system functionality • Street type Yes Default system functionality • Directional suffix Yes Default system functionality • Apartment number (separate field) Yes Default system functionality • Including 1/2 apartment numbers (e.g., 32 1/2) Yes Default system functionality • Alphanumeric (e.g., 2D) Yes Default system functionality • Building I D (separate field) Yes Default system functionality • Mobile Park lot number Yes Hexagon stipulates that this would be an apartment number and stored as such • Floor number (separate field) Yes Hexagon stipulates that floor number would be stored as a location comment after the colon delimeter in the location entry. 66 of 16 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 It em GIS Number 6-191 6-192 6-193 6-194 6-195 6-196 6-197 6-198 Response Explanation • Subdivision (separate field) Hexagon clarifies that the County must provide a GIS polygon feature that contains Yes the names of all sub -divisions so this information can be stored in a custom field via the I/CAD polygon attributes feature. • Neighborhood Hexagon clarifies that the County must provide a GIS polygon feature that contains Yes the names of all neighborhoods so this information can be stored in a custom field via the I/CAD Polygon attributes feature. • Municipality Yes Default system functionality • Mile marker Hexagon clarifies that the County must provide a GIS point feature layer that provides Yes these mile markers with appropriate attribution so as to have them named as common place names in I/CAD - for example @180 NB MM AR • Exit number Hexagon clarifies that the County must provide a GIS point feature layer that provides Yes these mile markers with appropriate attribution so as to have them named as common place names in I/CAD - for example @180 NB Exit The system validates the location associated with a self -initiated event (e.g., supervisor .88 Yes Default system functionality response). The system performs location validation on a location entered on the mobile device. Yes Default system functionality The system can generate a report of location overrides including all data, operator I D, date, Hexagon stipulates that overridden locations time, and workstation ID. exist as part of the event record. The event Yes record contains the operator ID, date, time, and workstation I D that created the event - but the data is not specific to the overridden 6-GIS 84 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 It em GI$ Number 6-199 6-200 6-201 6-202 6-203 6-204 6-205 6-206 6-207 6-208 6-209 6-210 6-211 6-212 6-GIS Response Explanation More than one operator at a time can update event data on the same event record. Hexagon stipulates that any number of operators may be viewing an event and entering new remarks, supplemental persons Yes and vehicles, but only one operator may have an event in update mode at one time for changing key items such as event location, event -type, sub -type, calling party information. The system records location changes resulting from wireless caller location and rebid results. Hexagon clarifies that the operator must Yes accept the rebid ANI/ALI data into the event and allow the location to be changed in order for this data to be channed The system can accept and process location information in Presence Information Data No Not currently supported Format - Location Ob'ect PI DF-LO format. The system can accept and process location information in United States Civic Location No Not currently supported Data Exchange Format NENA-STA-004. The system meets applicable NENA Next Generation 9-1-1 (NG9-1-1) capabilities of Not currently supported accepting and processing location protocol (PIDF-LO) and various data (e.g., text, video, No audio X/Y coordinates) as resented to the CAD/9-1-1 network interface. Premises - Display and Storage of Premises Hazards, Alerts, and Histories Upon location validation, the system automatically checks for premises history, hazards, and Yes Default system functionality alerts. The system will base the inquiry on: . An exact match of the location Yes Default system functionality . Type of premises data Yes Default system functionality . Distance parameter established by the agency between the location of the event and Hexagon stipulates that I/CAD only checks for the location of the premises data (e.g., 1000-foot search for police premise, 500-foot No special situations via a radius search. The search for inoperable hydrants, 1500-foot search for street closures) radius search is set per event -type and a alobal fallback value . Distance parameter established is adjustable by the agency Yes Default system functionality When information is associated with a displayed location, the system will: e Create an audible (optional using system configuration) and visual alert to the operator, Audible alerts are not available for special as Alternate situations. defined by the aaency ss of is Company: Item Number 6-213 6-214 6-215 6-216 6-217 6-218 6-219 6-220 6-221 6-222 6-223 6-224 6-225 6-226 6-227 6-228 6-229 6-230 6-231 6-232 6-233 6-234 6-V235 Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 GIS Response Explanation • Create a link to the premises information Yes Default system functionality Alerts can be designated as urgent. Yes Default system functionality Alerts can be designated as urgent by the system when the premises information contains a pre -established key word (e.g., gun, knife). No Hexagon stipulates that the priority of a special situation is set manually when the system administrator creates the special situation Alerts can be designated as urgent by the system when the premises information contains a pre -established phrase (e.g., threatened police). No Hexagon stipulates that the priority of a special situation is set manually when the system administrator creates the special situation When an urgent message is associated with an event record, the message will display as the CAD event is viewed. Yes Default system functionality The system visually differentiates the premises notification between "in the area of match and an exact location match. No Not currently supported An event does not have to be created to access premises information associated with a location. Yes Default system functionality The premises information is available to the mobile device. Yes Default system functionality The premises information displays in a new work area. The display of the premises information does not replace the from which the display command was initiated. Yes Default system functionality Premises information can be entered, stored, retrieved and displayed by: a Civic address Yes Default system functionality . Intersection No Not currently supported . Apartment complex Yes Default system functionality . Single block range Yes Default system functionality . Multiple block range Yes Default system functionality e Common Place or Business name Yes Default system functionality e Building number Yes Default system functionality e Individual apartments Yes Default system functionality e Agency -defined radius from the specified location Yes Default system functionality e Map polygon Yes Default system functionality e Street segment Yes Hexagon stipulates that this would be the same as an address range, limited to only a sin le se ment as broken in the GIS data. • Contact name No Not currently supported • Contact telephone number No Not currently supported 86 of 18 Company: Item Number 6-236 6-237 6-238 6-239 6-240 6-241 6-242 6-243 6-244 6-245 6-246 6-247 6-248 6-249 6-250 6-251 6-252 6-253 6-254 6-255 6-256 6-257 6-258 6-GIS Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 GIS Response Explanation Premises information displayed includes: . For history associated with the location: • Event number Yes Default system functionality • Event type code Yes Default system functionality • Date/time of event Yes Default system functionality • Location (when displayed with radius) Yes Default system functionality • Disposition No Not currently supported • Hyperlink to the event record Yes Hexagon stipulates that it is not a hyperlink, but a double click to view the event details . For Alerts and Hazards associated with the location: • Date/time of entry Yes Default system functionality • ID of person entering the alert entry Yes Default system functionality • Message Yes Default system functionality • Expiration date/time Yes Default system functionality • Last Update date/time No Not currently supported • File attachment No Not currently supported • Automated external defibrillator (AED) location Yes Hexagon stipulates that this would a specific s ecial situation type. • Weapons on the property Yes Default system functionality • Gate codes Yes Default system functionality • Key holder/contact information Yes Default system functionality The system will record in the event record when an operator views the premise data. Yes Default system functionality The agency can determine the timeframe of how far back the system will search for premises history, by device (a portable device time frame can be different than the timeframe of workstations). No Not currently supported Premises history, hazards, and alerts are available for display for mobile users. Yes Default system functionality The system associates files of pre -plan information (e.g., building plan, store numbers, contact information) to Common Place via hyperlink or other methods of association. Yes Hexagon stipulates that links to these files are placed into special situations. The files themselves must be stored on an accessible network share to all workstations and mobile devices that need access to the file. The application required to view the file type must be installed on the workstation or mobile Company: Item Number 6-259 6-260 6-261 6-262 6-263 6-264 6-265 6-266 6-267 6-268 6-269 6-270 6-271 6-272 6-273 6-274 6-275 6-276 6-277 6-278 6-279 6-280 6-281 6-282 6-283 6-284 6-285 6-286 6-287 6_(fi-�288 Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-ciS ver: 8/15/2017 GIS Response Explanation The pre -plan files are available to the operator with a minimum number of mouse clicks. Yes Default system functionality Premises hazards and alert information can be entered remotely by agency. Yes Default system functionality Premises hazards and alert information can be maintained by agency. Yes Default system functionality Premises hazards and alert information can be restricted to display by: • Agency Yes Default system functionality • For all agencies Yes Default system functionality • User groups No Not currently supported • User ID No Not currently supported • Role No Not currently supported • Agency Yes Default system functionality • Discipline No Not currently supported • Viewing device No Not currently supported The creation of premises records is by authorized users only. Yes Default system functionality The system captures and maintains premises information in user -defined categories or tVpes. Yes Default system functionality The system defines criteria for automatic premises information purges. No Not currently supported The system activates or deactivates the automatic premises purge feature as determined by an age . No Not currently supported The system defines valid date ranges for time -limited premises information at a given location e.g., information valid between <start date> and <end date> . No Not currently supported The following maintenance functions can be utilized with stored hazards and alerts: • Add Yes Default system functionality • Modify Yes Default system functionality • Delete Yes Default system functionality Information will include: • Hazard, alert, history narrative Yes Default system functionality • Links to attached files (e.g., photographs, hazard substance lists) Yes Default system functionality • Location Yes Default system functionality • ID of person authorizing the information Yes Default system functionality • ID of person entering the information Yes Default system functionality • Date and time when entered Yes Default system functionality • Expiration date and time Yes Default system functionality • Date and time range of a time limited premises information No Not currently supported as of 18 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-ciS ver: 8/15/2017 Item GAS Response Explanation Number 6-289 6-290 6-291 6-292 6-293 6-294 6-295 6-296 6-297 6-298 6-299 6-300 6-301 6-302 6-303 6-304 6-305 6-306 6-307 6-"08 The system is capable of sending a notification message to designated system accounts Default system functionality across all agencies when a hazard or alert is added and changed at the discretion of the Yes agency. The system is capable of tracking when a hazard or alert is about to expire for inclusion in a Hexagon clarifies that the system is capable report. The agency can define the timeframe for the notification message. of tracking this information. Any report Yes required to show this information and disseminate it would be written by the County after training on our InSight Reporting product Premises history is automatically created and associated with a location on event entry with Yes Default system functionality a verified location. The premises history record is available for viewing by an operator on location verification. Yes Default system functionality At a minimum, the following data is included with premises history: • Incident number Yes Default system functionality • Event type code Yes Default system functionality • Caller name and contact information Yes Hexagon stipulates that only when viewing the event detail not in the summary screen. • Date and time Yes Default system functionality • Disposition Yes Hexagon stipulates that only when viewing the event detail not in the summary screen. • Hyperlink to the full event description Yes Hexagon stipulates it is not a hyperlink but a double click to see the event details. Ability to display premise and hazard information either requested from the CAD client or Yes Default system functionality from the Map. Ability to configure premise and hazard information notifications based on the premise type e. ., building, location,person) including: • Font Color No Not currently supported • Font Size No Not currently supported • Background Color No Not currently supported • Placement on screen No Not currently supported • Audible (e.g. special beep tone) alarm No Not currently supported the system shall have the ability to automatically send premise and hazard information to No Not currently supported assigned units via text message or SMS. then system shall have the ability to configure the requirement for acknowledgement of call NO Not currently supported taker when remise or hazard information is resented. 89 of 18 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 Item GAS Response Explanation Number 6-309 6-310 6-311 6-312 6-313 6-314 6-315 6-316 6-317 6-318 6-319 6-320 6-321 6-322 6-323 6-324 6-325 6-326 6-327 6-328 6-GIS the system shall have the ability to configure the requirement for acknowledgement of No Not currently supported dispatcher when premise or hazard information is presented. the system shall have the ability to present notification when premise or hazard information is No Not currently supported acknowledged by mobile users. the system shall have the ability to configure notification when premise or hazard information No Not currently supported is not acknowledge by call taker, dispatcher and units assigned to incident. the system shall have the ability to export and report on premise information. Yes Default system functionality Road Closures The map shall accept the closing and opening of roads. Yes Default system functionality A road closure is visually represented on the map. Yes Default system functionality Hexagon stipulates that road restrictions show No up in I/Dispatcher, but do not show up on the map in Mobile for Public Safety or Mobile Road closure updates are represented on all system workstations and devices in real-time. An authorized user can enter a road closure using CAD functions. Yes Default system functionality An authorized user can schedule a road closure (e.g., parade route, special events). Yes Default system functionality An authorized user can discontinue the road closure using CAD functions. Yes Default system functionality Hexagon stipulates that road restrictions show NO up in I/Dispatcher, but do not show up on the Entry of road closures is automatically shared by the system with all workstations and mobile map in Mobile for Public Safety or Mobile devices. Hexagon stipulates that road restrictions show NO up in I/Dispatcher, but do not show up on the The system is capable of updating workstations and mobile devices with road closure data map in Mobile for Public Safety or Mobile immediately after entry. Road closures can be of any duration. Yes Default system functionality Unit recommendations are adjusted due to active road closures. Yes Default system functionality The routing component should have a method for scheduling the closing and reopening of Yes Default system functionality intersections or street segments the scheduling functionality can be configured by Designated Users . Yes Default system functionality the scheduling can be made for recurring dates with a start time/date and end time/date Yes Default system functionality the scheduling can initiate a reminder to users of the pending end of the road closure I No INot currently supported the scheduling can be made for start time/date without end time/date I Yes I Default system functionality 90 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 14.. w. Number GIS Response Explanation During road closure the user shall e able to designate it an intersection sou a treated as 6-329 .open" so support crossing by public safety personnel. No Not currently supported 6-330 6-331 6-332 6-333 6-334 6-335 6-336 GIS Interface The system is compatible with ESRI software. Hexagon clarifies that ESRI file formats are supported as the source for GIS data, but all ESRI formats are processed by I/Map Editor Yes for ArcGIS (using a plug-in) into I/CAD proprietary format for loading into I/CAD in support of location validation and graphic The system supports ESRI file formats. Hexagon clarifies that ESRI file formats are supported as the source for GIS data, but all ESRI formats are processed by I/Map Editor Yes for ArcGIS into I/CAD proprietary format for loading into I/CAD in support of location validation and graphic representation. The system supports a direct interface to ESRI native file structures for import to CAD. Hexagon clarifies that ESRI file formats are supported as the source for GIS data, but all ESRI formats are processed by I/Map Editor Yes for ArcGIS into I/CAD proprietary format for loading into I/CAD in support of location validation and graphic representation. All GIS-related files can be maintained by the agency. Yes Default system functionality GIS files can be imported to CAD by the agency using built-in system utilities. Hexagon clarifies that ESRI file formats are supported as the source for GIS data, but all ESRI formats are processed by I/Map Editor Yes for ArcGIS into I/CAD proprietary format for loading into I/CAD in support of location validation and graphic representation. A GIS report writing module is included (e.g., Python for ArcGIS) No Not currently supported 6-&B337 I Other Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS Ver: 8/15/2017 14.. w. Number 6-338 6-339 6-340 6-341 6-342 6-343 6-344 6-345 6-346 6-347 6-348 6-349 6-350 6-351 6-GIS GIS Response Explanation Require consistantly accurate AVL recommendations regardless of the number of users Yes Default system functionality logged on and being tracked. The system shall retain the previous version of the geofile with the functionality of easily Yes Default system functionality switching back to it. GIS and GIS design should use national standards such as NENA NG9-1-1 US Civic Yes Hexagon conforms to the US Postal Standard. Location Exchange Format. Hexagon would like to clarify that this type of functionality is best suited in a Fire Records Authorized agency users can update the service status (in-service/out-of-service) of hydrants No Management system and an interface to that on the hydrant layer. system for status of hydrants can be created. Hexagon welcomes the opportunity to discuss the Count 's re uirements further. exagon s ipu a es that the camera Teed mus be accessible via Web Browser and the unique camera URL's programmed into the When clicking on a camera location icon on the CATV camera location map layer, the Yes intelligent camera icon on the I/CAD map. system is capable of displaying the live camera stream of that camera in a pop-up window. The County must also provide a GIS point feature layer that contains the latitude and longitude of each camera, and the unique The map system operates with the same keyboard and mouse function as CAD. Yes Default system functionality The map displays pending events. Yes Default system functionality The map symbols representing events and units are configurable by the agency. Yes Default system functionality The map system displays all units within the map view. Yes Default system functionality The map system displays the live location of all units within the map view. Yes Default system functionality The map symbols distinguish between service (fire, EMS, etc.), events, and units by color Hexagon stipulates that units are represented and shape. Alternate by bitmap icons on the map and the color of the units is used to denote the unit status. The ma symbols representing units distinguish unit status e. p y p g g ( g., enroute, arrived, available). Alternate Hexagon stipulates that color is used to represent unit status. Unit status representations (e.g., color, symbology) on the map match status representations Yes Default system functionality used on the CAD status monitors. u An operator can display the coordinates of a map location by a mouse click on the desired Yes Default system functionality ,map position. 92 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS Ver: 8/15/2017 It em GI$ Number 6-352 6-353 6-354 6-355 6-356 6-357 6-358 6-359 6-360 6-361 6-362 6-363 6-364 6-365 6-366 6-367 6-GIS Response Explanation An operator can perform event -related functions (e.g., update event information, add remarks) from an event form by selecting the representative event icon displayed on the Yes Default system functionality map. The system support the ability to visually notate available premises information and link to Hexagon wishes to clarify that this feature and appropriate documents via a single map click. No function is available, but it is not via a single map click. The system supports the ability to select unit(s) and have the map automatically size to Yes Default system functionality display the requested units' icons within the map. An operator can perform a map location lookup based on the following: . Validated civic address Yes Default system functionality . Validated intersection Yes Default system functionality . Geographic coordinates (e.g., latitude/longitude) Yes Default system functionality . Mouse click on the map Yes Default system functionality . Validated Common Place name Yes Default system functionality The system can print the map display. Yes Default system functionality The system can perform a screen capture and save a snapshot of the current map display. Yes Hexagon stipulates that this is via standard windows print screen functionality. Hexagon stipulates that this is via standard The system is capable of sharing the screen capture file via email. Yes Windows email and file attachment functionality. Updates to the map only require the deltas to be uploaded and integrated with the map No Not currently supported rather than the entire map file. Authorized agency users can update the mapping system. Yes Default system functionality er addendum 2 issued by the County on 10/24/2017, Hexagon understands this the scheduling functionality can be configured by Designated Users . Yes requirement to pertain to the ability to schedule the restriction and un-restriction of road segments. I/CAD provides this functionalit . era en um 2 ssue y the County on 10/24/2017, Hexagon understands this the scheduling can be made for recurring dates with a start time/date and end time/date Yes requirement to pertain to the ability to schedule the restriction and un-restriction of road segments. I/CAD provides this functionality. 93 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 It em GIS Number 6-368 6-369 6-370 6-371 6-372 6-373 6-374 6-375 6-376 6-377 6-GIS Response Explanation Per addendum 2 issued by the County on 10/24/2017, Hexagon understands this the scheduling can initiate a reminder to users of the pending end of the road closure No requirement to pertain to the ability to schedule the restriction and un-restriction of road segments. I/CAD does not provide this functionalit . era en um 2 issued by the County on 10/24/2017, Hexagon understands this requirement to pertain to the ability to the scheduling can be made for start time/date without end time/date No schedule the restriction and un-restriction of road segments. I/CAD does not provide this functionality. Scheduled road restrictions must Hexagon assumes is requirement o be to display a native ESRI map within the CAD application. The I/CAD Multi -Source map Yes allows this. The County is wholly responsible for the creation of WMS, WMTS, or ArcGIS web services that can be consumed by the Multi -Source Map. The web services must be CAD shall have a mapping display that utilizes and ESRI based map. oubloc static services Hexagon stipulates that any such data must Yes be provided by the County as a GIS point The system shall have ability to create links from the geofile to specific documents for layer feature with all necessary attribution to locations or map points. This may include Excel, Word, PDF, photos. facilitate retrieval of the file. Hexagon stipulates that any such data must Yes be provided by the County as a GIS point layer feature with all necessary attribution to The system shall have the ability to create links to the Web via points on the map. facilitate retrieval of the file. The updates to the map must not affect CAD operations. Yes Default system functionality CAD shall provide a tightly integrated mapping application that shows incident and unit Yes Default system functionality location. The maps shall be resident on the CAD workstation for optimal local, wireless, and remote Yes Default system functionality performance. IMapping may be utilized in a wireless mode to support in -car mapping. Yes Default system functionality IMapping shall graphically depict all active incident and unit information for the position. Yes Default system functionality 94 of 16b Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS ver: 8/15/2017 It em GI$ Number 6-378 6-379 6-380 6-381 6-382 6-383 6-384 6-385 6-386 6-387 6-388 6-389 6-390 6-GIS Response Explanation Mapping shall utilize the same coloring and textual information as CAD. For instance, if The system displays "EN" and a green color for Enroute, the mapping application will do the Yes Default system functionality same. The s stem and the ma dis la shall utilize the same ESRI eofiles sources. Yes Default system functionality e map zoom eve s s ou a user defined y agency. or instance, Agency A wants t e map zoomed to 1000 feet when recalling a dispatch, while Agency B wants the map zoomed Yes Default system functionality to 2000 feet for the same function. The map zoom levels should be defined by operator (e.g., Operator A wants the map zoomed to 1,000 feet when recalling a dispatch, while Operator B wants the map zoomed to No Not currently supported 2,000 feet for the same function). Mapping shall support CAD command and mouse operations of zoom and pan functions Yes Default system functionality An operator can zoom using the scroll button on the mouse. Yes Default system functionality Mapping shall support unattended operations that cause the map to perform a function when The system performs a function requiring map operations. For instance, when a call is Yes Default system functionality displayed, dispatched, updated; the map is automatically zoomed Hexagon stipulates that if the operator When initiating an event from a mouse click on the map, the system will present the operator invokes the graphic location entry command choices of the closest valid addresses to the map click location to choose as the address to No clicks on the map, CAD will determine the validate, but the point on the map will remain at the point selected. Please describe the location of the mouse click and display an process used to interpolate addresses both along street segments and in open areas. estimated address for that click. Operators are not aiven a choice. The system toggles feature annotation. Yes Default system functionality Annotations are built for specific zoom scales and apply to several zoom scales. The font The map feature annotation (e.g., street names) font size automatically adjusts with map associated with a street name may look ideal focus to maintain a consistent size. Alternate at one zoom scale, but a slightly high zoom scale the font may look slightly too large, but then reset to a more normal view one more zoom scale hoaher. The map icons' font size automatically adjusts with map focus to maintain a consistent size. No Not currently supported Map symbology can be defined and changed by the agency. Yes Default system functionality Hexagon stipulates that route display is only Mapping shall display the best route to an incident, including road conditions (e.g., closures, Yes done on demand using the generate route hazard warnings). feature. 95 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS Ver: 8/15/2017 14.. w. Number 6-391 6-392 6-393 6-394 6-395 6-396 6-397 6-398 6-399 6-400 6-401 6-402 6-403 6-404 6-405 6-406 6-GIS GIS Response Explanation The ability to export shortest path routes for every viable assigned unit to a separate system in a standard format. i.e. XML, Shape Files No Not currently supported Hexagon stipulates that route display is only Mapping should provide distance and direction of travel information from any point to any Yes done on demand using the generate route point in the Geofile feature. Mapping shall provide a method to track and report specific common place locations to be used in the incident create process that allows the Telecommunicator to create an incident Yes Default system functionality without searching for the physical address for the common place location. The tactical map shall interact with the system in the following manner: The map should zoom in to the incident location when an incident is initiated or updated. Yes Default system functionality Each unit's status will display as users update units on the CAD system. Yes Default system functionality Hexagon stipulates that operators may only use the graphic location entry feature to Yes choose a location for event creation. The event information form must be used to User may initiate incidents utilizing a "point and click' on the map. complete the event entry process. Users may update a unit's status from the map Yes Default system functionality Users may update, recall, or dispatch an incident from the map Yes Default system functionality Hexagon stipulates that any such data must Yes be provided by the County as a GIS point Users may select Icons on the map and link to Web pages. For instance, an Icon might layer feature with all necessary attribution to display a weather map of an area by linking to the local new channels weather radar facilitate retrieval of the URL User may select layers of the map to turn on and off. For instance, displaying parcels or Yes Default system functionality hydrant locations when needed The ability to pan the map by grabbinga map point with the mouse and moving it Yes Default system functionality The ability to select unit(s) and have the map automatically size to display the requested units within the map Yes Default system functionality With AVL the map will automatically an to follow the selected units in a separate window No Not currently supported The ability to have the CAD system send recommendation requests for best path routing to Hexagon stipulates that route display is only the mapping applications including road conditions (e.g., closures, hazard warnings), then No done on demand using the generate route display the recommendations to the Dispatcher. feature. Hexagon stipulates that instead of double - Alternate clicking on the event or unit, right -click The ability to double click on incidents and units to display additional detail as appropriate commands are used. 96 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 6-GIS Ver: 8/15/2017 It em GI$ Number 6-407 6-408 6-409 6-410 6-411 6-412 6-413 6-414 6-415 6-416 6-417 Response Explanation Hexagon stipulates that the map is either in feet or meters as a base unit of measurement. Yes However, using the unit conversion parameter table, operators can measure distance on the map in any number of units of measure The ability to support both meters and feet distances. including miles, kilometers, feet, meters, etc. The ability to have maps at any appropriately configured workstation local and/or remote. Yes Default system functionality CAD shall have the ability to display location details, including premise and hazard Yes Default system functionality information either requested from the CAD client or from the Map. The system accepts location information based on Federal Communications Commission Yes Default system functionality (FCC) Wireless Phase I and Phase II standards. The system shall be able to obtain Latitude and Longitude by pointingto a point on the map Yes Default system functionality The system shall have a local setting to change between displaying Lat/Long in Decmial No Not currently supported Degrees or Degrees, Minutes, Seconds The system shall support automatic updating of Phase 11 locations, upon receipt of re -bid Yes Default system functionality information from the 9-1-1 system. The user should be able to send a E9-1-1 Rebid command from the map No Not currently supported CAD shall support the ability to configure the polling frequency of AVL equipped vehicles Yes Default system functionality either by Agency, Unit Status or Vehicle Type. The user shall be able to initiate a "Poll" or refresh of the units AVL location from the map at Yes Default system functionality any time. Hexagon clarifies that the I/Tracker Playback application (included as part of I/Tracker) Yes must be used to view AVL data playback. It is NOT included in the I/Dispatcher, Mobile for Public Safety, Mobile Responder (optioned), AVL playback shall be available to the authorized user from their map. 6-GIS 97 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-001 7-002 7-003 7-004 7-005 7-006 Response Explanation The system will have a command to review runcard response recommendations without No Not currently supported creating an incident. The system will have a command to review AVL based response recommendations without No Not currently supported creating an incident. Due to the critical nature of the software solutions that The vendor shall provide the list of all aspects of hardware and software that satisfy the Hexagon provides, we do not publish minimum requirements of the system minimally. No specifications. Hexagon provides required, detailed hardware specifications. These are included as part of the system configuration diagram, Attachment 4.1. Hexagon has included a system configuration diagram The vendor shall provide the list of all aspects of hardware and software that satisfy the as part of the proposal response (Attachment 4.1) requirements of the system optimally. Yes which identifies the required, detailed hardware and q y p y. software specifications to optimally support the proposed CAD/Mobile solution. The vendor shall discuss its plans how they plan to deal with the new emergency The I/CAD system has been an interoperable capable communication capabilities have been defined by the Department of Homeland Security system for over 15 years. our EdgeFrontier integration (DHS); the evolution of data interoperability that will facilitate exchanges between similar platform is capable of complying with the Federal NEIM and disparate systems has become a legitimate expectation for every communications Acknowledge standards they apply to event and information sharing. Whhile the system is 100 % capable of this type center, and information sharing in real time to best serve incident command staff, field of data sharing, Hexagon has not proposed any specific responders of all disciplines and the public is no longer a luxury feature. interface to accomplish this data sharing. Ability to create reports based on any available CAD data Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 98 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/1512017 Item Miscellaneous Items Number 7-007 7-008 7-009 7-010 7-011 Response Explanation Ability to create a standard Incident Detail Report by a single command, that includes all Hexagon clarifies that we have proposed our Insight data associated with a specific incident formatted in an easy -to -read, professional style Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. Ability to view, query and archive CAD logging data from a PC Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. Reports Ability to generate the following standard reports: sActivity analysis by day of week Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. TMisc 99 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-012 7-013 7-014 7-015 Response Explanation .Activity analysis by geographic area or any agency -defined layer Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. eActivity analysis by hour of day Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. eActivity analysis by shift Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .Incidents — by geographic area by hour of day Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 100 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-016 7-017 7-018 7-019 Response Explanation •Response time by method of receipt Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Response times by geographic area Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Response times by type of call/priority Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .Total and average time on call — by day of week Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 101 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-020 7-021 7-022 7-023 Response Explanation .Total and average time on call - by geographic area Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .Total and average time on call - by hour of day Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .Total calls for service by date by nature or disposition Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .Total incidents by date by nature or disposition Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 102 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/1512017 Item Miscellaneous Items Number 7-024 7-025 7-026 7-027 Response Explanation •Total reports by date by disposition Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. sAgency-defined query Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. Ability to record and create reports using the following information: .Alarm type and alarm company code Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 103 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-028 7-029 7-030 7-031 Response Explanation eAII associated geofile information Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .ANI/ALI data including address and phone number Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. eAvailable mobile to available at station Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. eAvailable mobile to unavailable Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 104 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-032 7-033 7-034 7-035 Response Explanation •Business or premise name Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Call Taker/Dispatcher I D Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Comments/narrative (unlimited) Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Commonplace name (e.g., parks, streets, schools) Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 105 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-036 7-037 7-038 7-039 Response Explanation •Date and time call received by 9-1-1 Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Date and time incident entered Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SOL Server Reporting and Analysis services, and Microsoft PowerBl. •Date and time of held incidents Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Date range Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 106 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-040 7-041 7-042 7-043 Response Explanation •Disposition Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .Geographical areas defined by the user Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Incident number Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •I ncident type Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 107 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-044 7-045 7-046 7-047 Response Explanation •Incident type/priority Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .Location address, description, supplemental location Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SOL Server Reporting and Analysis services, and Microsoft PowerBl. •On -scene to close of call by personnel who arrive at scene Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •On -scene to transporting Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 108 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-048 7-049 7-050 7-051 Response Explanation •Premise and prior information flag Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .Premise type (e.g., building, location, person) Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Priority Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Reporting areas Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 109 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-052 7-053 7-054 7-055 Response Explanation .Reporting party information, including name, address and phone Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Reporting zone Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Responding to on -scene Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .Source (e.g., 9-1-1 or 10-digit, radio, other codes as defined by PPD) Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 110 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-056 7-057 7-058 7-059 Response Explanation .Time range (any time -stamped event to any other time -stamped event) Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. •Unit/Personnel I D Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .User name and ID of all users associated with the incident Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. .Workstation I D associated with all CAD functions performed on incident Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 111 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/1512017 Item Miscellaneous Items Number 7-060 7-061 7-062 7-063 Response Explanation Ability to print chronological incident and/or incident report listing Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. Ability to query and print incident details, including: • Incident entry or incident number Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Date/time received Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 112 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-064 7-065 7-066 7-067 Response Explanation • Reporting zone Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. • Activity code/incident type Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. • Location or partial location Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. • All incidents in a geographical region defined by the user Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. 7-Misc 113 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-068 7-069 7-070 7-071 Response Explanation • Priority Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Reporting party/complainant/caller name Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Phone number Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Narrative Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 114 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-072 7-073 7-074 7-075 Response Explanation • Vehicle description Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. • License plate Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. • Cancelled call Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. • Disposition Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. 7-Misc 115 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-076 7-077 7-078 7-079 Response Explanation • Personnel/units assigned Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Time dispatched Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Enroute time Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • On -scene time Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 116 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-080 7-081 7-082 7-083 Response Explanation • Available time Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Personnel reporting Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • All Call Taker/Dispatchers handling incident Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Any time -stamped event Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 117 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/1512017 Item Miscellaneous Items Number 7-084 7-085 7-086 7-087 Response Explanation Ability to query using partial names and wild cards in any field within the incident Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. Ability to generate daily listing of incidents and personnel assigned: • Incident number Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Unit ID Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 118 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-088 7-089 7-090 7-091 Response Explanation • Personnel name (if available) Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. • Personnel ID Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. • Disposition Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. • Location Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBI. 7-Misc 119 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/1512017 Item Miscellaneous Items Number 7-092 7-093 7-094 7-095 Response Explanation • Date/time received Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. Ability to print audit report of changes to incident records: • Date/time of change Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Workstation/terminal I D Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 120 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-096 7-097 7-098 7-099 Response Explanation • Call Taker/Dispatcher ID Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Transaction type (deletion, edit, etc.) Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Field modified (saving previous information) Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Incident location Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 121 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/1512017 Item Miscellaneous Items Number 7-100 7-101 7-102 7-103 7-104 7-105 7-106 Response Explanation • Actual dispatch location Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Ability to direct inquiry results to any printer Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Ability to view requested reports prior to printing Hexagon clarifies that we have proposed our Insight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Ability to restrict user actions by: • Warning of the number of records found No Not currently supported • Using prompts to continue/refine/alter the query No Not currently supported The reports have a formatted header, which is customizable but can include as a minimum the following: 7-Misc 122 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-107 7-108 7-109 7-110 Response Explanation .Agency name Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. . Agency logo Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Datefrime Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Event type Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 123 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mimo ver. 8/15/2017 Item Miscellaneous Items Number 7-111 7-112 7-113 7-114 Response Explanation • Event number Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Response area Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Responding crew(s) Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Author of the report Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. 7-Misc 124 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-115 7-116 7-117 7-118 7-119 7-120 7-121 TM isc Response Explanation • Unit ID(s) Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Vehicle ID(s) Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. • Event location Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Yes proposed any services to create or generate custom reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services, and Microsoft PowerBl. The system will have the ability to accept and associate with the CAD incident any relevant No Not currently supported electronic media received from the NG9-1-1 network The vendor commits to adhere to NENA i3 standards in a reasonable time frame as new Depending on the levels of effort required, additional features are added to i3. Alternate services at additional cost may be needed that are not currently proposed. The system will have a seamless workflow to accept multimedia electronic media from the No Not currently supported NG9-1-1 network The system will have the ability to have the NG9-1-1 telephony user screens resident on the No Not currently supported same workstation as the CAD 125 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-122 7-123 7-124 Response Explanation In the configuration proposed, database redundancy is provided via implementation of the Disaster Recovery (DR) site using a Microsoft AlwaysOn Cluster. Hexagon's recommended configuration provides a high availability (HA) solution and is based on our evaluation of the RFP and several decades of experience with public safety customers. Our database (DB) recommendation is based on the usage of SQL AlwaysOn using SQL Enterprise for DB high availability (HA). SQL Enterprise is recommended to reduce downtime for maintenance tasks since many DB maintenance functions can only be performed online when using SQL Enterprise. The 4 9's in the contract to ensure maximum 'up -time' Alternate Whenever HA is desired for any portion of our application Hexagon recommends a minimum of two (2) nodes at a primary location and a tertiary node at a second location. This allows for easy failover at the primary site for server maintenance and the potential to manually failover to a secondary location when required. The calculation of system availability is dependent upon many requirements, some of which are not within Hexagon's scope of management. System availability is dependent upon the following: Power source including UPS, PDUs Physical infrastructure including servers, switches, network cabling Doing an Incident Recall search should produce results (practically )instantaneously Due to the varied nature of incident recall searches No (number of parameters searched on, date/time range searched) Hexagon cannot agree to this requirement of near instantaneous search results. The call number and incident number being different, the one that resets at midnight should No Not currently supported be able to be used even after the call is closed to recall the incident. 7-Misc 126 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-125 7-126 7-127 Response Explanation The Incident Audit feature needs to be at least as informative as what we have now, not less so. No Not being familiar with what the County has now or the specifics of the Incident Audit, Hexagon cannot agree to this requirement at this time. Hexagon welcomes further discussion on this requirement. Instead of depending on the Vendors statistics, we require actual data from users in re to Hexagon acknowledges that the County indicated in downtime and crashes. Addendum #2 in response to a question on 7-126, "Lee County would like to see data from installed production systems rather than Vendor estimates based on development or test systems on system reliability. This would include statistics that indicate downtime or No "crashes" that are scheduled or unscheduled with systems that operate like a proposed Lee County system." Hexagon welcomes further discussion with the County regarding this requirement prior to providing the ndicated data. Hexagon clarifies that we have proposed our InSight Reporting for I/CAD solution, that contains standard (canned) reports and a reporting universe that will support additional report creation. Hexagon has not Provide a system that allows for the output of a document that is ready for release as public Yes proposed any services to create or generate custom information by isolating certain user defined data fields. reports for the County, but has proposed computer - based training for the County on the use of InSight reporting, which is built upon industry standard technologies like SQL Server Reporting and Analysis services and Microsoft PowerBl. 7-128 ITraining System 7-Misc 127 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-129 7-130 7-131 7-132 7-133 Response Explanation Ability to simultaneously operate a 'Training" system. The training system shall have The proposed training environment does not impact the identical functionality as the live system, but be available for training and scenarios. production environment. The training environment (with regard to the CAD database and applications) will be the same in function, but sized to handle a smaller load. Yes Hexagon clarifies that Test, Training, Redundant, and Backup copies are available for all proposed interfaces, however, implementation is subject to the customer's ability to provide connection to the applicable system. Interface training licenses are at additional cost not currently proposed. Hexagon welcomes further discussion on this requirement. The system shall provide an on-line training database for testing that does not impact the The proposed training environment does not impact the live database. Yes production environment. The training system uses a separate database from production. The training environment will be the same in function as the production environment. The training environment (with regard to the CAD database and applications) will be the same in function, but sized to handle a smaller load. The Training Mode shall have full access to all components of the CAD system, including Yes Hexagon clarifies that Test, Training, Redundant, and the current live GIS files, maps Backup copies are available for all proposed interfaces; however, implementation is subject to the customer's ability to provide connection to the applicable system. Interface training licenses are at additional cost not currently proposed. Hexagon welcomes further discussion on this requirement. The Training Mode shall be configurable independent of the live or production mode Yes The proposed training environment does not impact the production environment. The selection of a workstation working with either the live or training system is performed at Yes Workstations can be configured to connect to eitherthe the workstation. production or training environment. 7-Misc 128 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-134 7-135 7-136 7-137 7-138 7-139 7-140 7-M isc Response Explanation The system used for training is equivalent to the live system. The training environment (with regard to the CAD database and applications) will be the same in function, but sized to handle a smaller load. Hexagon clarifies that Test, Training, Redundant, and Alternate Backup copies are available for all proposed interfaces, however, implementation is subject to the customer's ability to provide connection to the applicable system. Interface training licenses are at additional cost not currently proposed. Hexagon welcomes further discussion on this requirement. Operating the training system does not impact the live system. Yes The proposed training environment does not impact the production environment. The training system can operate concurrently with the live system without system response The proposed training environment does not impact the degradation. Yes production environment. The proposed server hardware configuration is sized to allow the proposed systems to run concurrently. The selection of a workstation working with either the live or training system is performed at Yes Duplicate of 7-133 the workstation. The workstation can be switched between the training and live system without impacting the workstations can be configured to connect to eitherthe live system. Yes production or training environment without impacting the production server environment. The training system can train on the full suite of CAD and mobile functions. The training environment (with regard to the CAD database and applications) will be the same in function as the production environment, but sized to handle a smaller load. Yes Hexagon clarifies that Test, Training, Redundant, and Backup copies are available for all proposed interfaces, however, implementation is subject to the customer's ability to provide connection to the applicable system. Interface training licenses are at additional cost not currently proposed. Hexagon welcomes further discussion on this requirement. The training workstations can be physically separate from the live system. Yes Workstations can be configured to connect to eitherthe production or training environment. 129 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-141 7-142 7-143 7-144 7-145 7-146 7-147 7-148 7-149 7-150 7-151 7-152 7-M isc Response Explanation The training environment should be able to be accessed from CAD and mobile clients from The training environment can be accessed from any any location that has network access to the training CAD servers. location with functional network access that is consistent with the proposed requirements. Hexagon clarifies this is in reference to the CAD applications only and not all interfaces. Yes Hexagon clarifies that Test, Training, Redundant, and Backup copies are available for all proposed interfaces, however, implementation is subject to the customer's ability to provide connection to the applicable system. Interface training licenses are at additional cost not currently proposed. Hexagon welcomes further discussion on this requirement. The training system can be operated and maintained from a remote location. The training environment can be operated and Yes maintained from any location with functional network �requirements.. access that is consistent with the proposed The training system stays current with the versions of all components of the live system to Yes The training environment will be the same in function stay insync. The agency is able to synchronize the live and training systems. as the production environment. The Training Mode have the ability to copy the live or production mode to its self with a Yes The training environment will be the same in function simple command or process as the production environment. The agency can clear all incidents from training databases and reset the incident and case Yes The incidents and case numbering can be reset in the numbering sequences for the training system. training environment. The training system can be updated and restarted without impacting the live system. Yes The proposed training environment does not impact the j2roduction environment. The training system can be used as a test system for upgrades and updates to CAD Updates and upgrades can be performed and tested in operations, mapping, and tables. Yes the training environment prior to the production environment. The vendor provides a simulation module to simulate receiving live 9-1-1 calls. No Function not available. The system operates with a third -party simulation application to simulate receiving live 9- 1-1 No Function not available. calls. The training system accepts a live data dump from CAD to facilitate training with historic Yes The training environment will be the same in function data. as the production environment. Test System Ability to simultaneously operate a "Test" system. The test system shall be available to test The proposed test environment does not impact the system changes prior to their implementation to the training or live systems. FYes production environment. Changes can be tested before they are applied to production. Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-153 7-154 7-155 7-156 7-157 7-158 Response Explanation The system shall provide an on-line database for testing that does not impact the live The proposed test environment does not impact the database. Yes production environment. The test system uses a separate database from production. The test environment (with regard to the CAD database and applications) will be the same in function as the production environment. This does not apply to interfaces. The Test system shall have full access to all components of the CAD system, including the Hexagon clarifies that Test, Training, Redundant, and current live GIS files, maps Yes Backup copies are available for all proposed interfaces, however, implementation is subject to the customer's ability to provide connection to the applicable system. Interface test licenses are at no additional cost for software, but may require additional services at additional cost. Hexagon welcomes further discussion on this requirement. The Test System shall be configurable independent of the live or production mode Yes The proposed test environment does not impact the production environment. The system can test all vendor -provided updates and patches prior to implementation on the Yes Updates and patches can be tested before they are lives stem. applied to production. The system used for testing is equivalent to the live system. The testing environment (with regard to the CAD database and applications) will be the same in function as the production environment, but sized to handle a smaller load. Hexagon clarifies that Test, Training, Redundant, and Alternate Backup copies are available for all proposed interfaces, however, implementation is subject to the customer's ability to provide connection to the applicable system. Interface test licenses are at no additional cost for software, but may require additional services at additional cost. Hexagon welcomes further discussion on this requirement. Testing updates and patches do not impact the live system. Testing can operate The proposed test environment does not impact the concurrently with the live system without system degradation. Yes production environment. The proposed server hardware configuration is sized to allow the proposed systems to run concurrently. 7-Misc 131 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-159 7-160 7-161 7-162 7-163 7-164 7-165 7-166 7-167 Response Explanation The testing system can be physically separate from the live system. The proposed test environment can be physically separate from the production environment. The Yes environment must meet the required hardware and network specifications and may increase costs depending on the location. The selection of a workstation working with either the live or test system is performed at the Yes Workstations can be configured to connect to either the workstation. production or test environment. The testing system stays current with the versions of all components of the live system. The Yes The test environment will be the same in function as agency is able to synchronize the live and testing systems. the production environment. The Training Mode have the ability to copy the live or production mode to its self with a The test environment will be the same in function as simple command or Yes the production environment. Hexagon assumes this process meant to read "Test Mode". The testing system can be updated and restarted without impacting the live system. Yes The proposed test environment does not impact the production environment. The agency has full control of the maintenance of the testing system. Yes IThe agency has full control after implementation. Hospital Destination Coordination Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The system provides a method for creating and maintaining a list used for rotating external at this time. I/CAD, specifically the Mobile for Public services (e.g., hospital destination rotation plans). No Safety product, provides for the ability of field users to ask for the nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The hospital destination rotation cycle list can utilize destination capabilities as a parameter at this time. I/CAD, specifically the Mobile for Public of selection (e.g., trauma, stemi). No Safety product, provides for the ability of field users to ask for the nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. 7-Misc 132 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-168 7-169 7-170 7-171 Response Explanation Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public Hospital capabilities are stored and maintained in the hospital rotation dataset. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public The agency can create and maintain a list of hospitals to include on the rotation plan. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The system allows for the development of a separate hospital recommendation plan based at this time. I/CAD, specifically the Mobile for Public on hospital coverage polygons. No Safety product, provides for the ability of field users to ask for the nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The system allows for the development of a separate hospital recommendation plan based at this time. I/CAD, specifically the Mobile for Public on closest destination with desired capabilities. No Safety product, provides for the ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. TMisc 133 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-172 7-173 7-174 7-175 Response Explanation Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public Hospital destination rotation plans can be based on location. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The system can automatically recommend a hospital from the hospital destination rotation at this time. I/CAD, specifically the Mobile for Public list. No Safety product, provides for the ability of field users to ask for the nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public Hospital destination assignment can be made from a mobile device. No Safety product, provides forthe ability of field users to ask for the nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The system can establish a "destination request' button on a mobile device event form to at this time. I/CAD, specifically the Mobile for Public initiate the hospital destination rotation recommendation function. No Safety product, provides for the ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. TMisc 134 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-176 7-177 7-178 7-179 Response Explanation Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The system will send a confirmation message to the requesting mobile device when a at this time. I/CAD, specifically the Mobile for Public recommendation is confirmed using a "destination confirmed" button. No Safety product, provides for the ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The destination selection is based on a hospital rotation cycle as determined by the at this time. I/CAD, specifically the Mobile for Public transportation guidelines as well as hospital status. No Safety product, provides for the ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public The system can display the hospital destination rotation list when requested by an operator. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public An operator may override the recommended hospital destination selection. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. TMisc 135 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-180 7-181 7-182 7-183 Response Explanation Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The system allows an operator to remove/suspend a hospital destination from the rotation at this time. I/CAD, specifically the Mobile for Public list for an agency -determined period of time. No Safety product, provides for the ability of field users to ask for the nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The system allows an operator to select if a hospital destination stays at top of a rotation or at this time. I/CAD, specifically the Mobile for Public select a hospital destination to go to the bottom of the rotation list, depending on No Safety product, provides for the ability of field users to circumstances. ask for the nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The system allows a hospital to remain on the top of the list if a previously assigned at this time. I/CAD, specifically the Mobile for Public transport is cancelled during the event. No Safety product, provides for the ability of field users to ask for the nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public The system creates an audit log entry for hospital destination assignments. No Safety product, provides forthe ability of field users to ask for the nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. TMisc 136 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-184 7-185 7-186 7-187 Response Explanation Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public An operator can print the hospital destination assignment logs. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public An operator can electronically deliver (email) the hospital destination assignment logs. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No The system can establish a link to the hospital destination contact telephone number and at this time. I/CAD, specifically the Mobile for Public dials the company if the telephone link is selected by an operator. No Safety product, provides for the ability of field users to ask for the nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public The system allows an operator to manually assign/override hospital destination selection. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. TMisc 137 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 7-Mist ver: 8/15/2017 Item Miscellaneous Items Number 7-188 7-189 7-190 7-191 Response Explanation Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public The system supports a module for rotating resources. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public The system supports the temporary removal of a resource from a rotation. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public The system supports the request for a resource from a person or vehicle record. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. Hexagon has read and interpreted this section of requirements to the best of our ability. Given what we can obtain from the requirements, we must answer No at this time. I/CAD, specifically the Mobile for Public The system supports the ability to cancel a resource request. No Safety product, provides forthe ability of field users to ask forthe nearest destination based on a type (i.e. Hospital, Burn Unit, Jail, Cardiac Care Center, etc.) but does not have any ability to "rotate" these recommendations. TMisc 138 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 8-Pro Q&A Ver: 8/15/2017 Item Number pro Q & A Response Explanation 8-001 8-002 8-003 8-004 8-005 8-006 8-007 8-008 8-009 8-010 8-011 8-Pro Q & A The calltaking component shall be ProQA Paramount -Platinum certified with Hexagon is currently Priority Dispatch ProQA the Multi -Discipline Launcher Yes Paramount -Platinum certified with the Multi -Discipline Launcher. The calltaking component should be ProQA Paramount -Titanium certified with the Multi - Disci line Launcher No Not currently supported The system should support interface to Priority Dispatch Paramount SMS Textin No Not currently supported The Priority Dispatch Paramount (ProQA) I/CAD Priority Dispatch Paramount's Key Questions and Description Essentials Interface will support colorization (adorned text) of should be dis sdisplayed in color within the Dispatch Narrative. p y p Alternate ProQA Key Questions and PersonNehicle Information. However, Description Essentials are displayed in re ularblacktext. The Priority Dispatch Paramount (ProQA) I/CAD Priority Dispatch Paramount's Key Questions and Description Essentials Interface will support colorization (adorned text) of should be displayed in color within the MDC/MDT display. Alternate ProQA Key Questions and PersonNehicle Information. However, Description Essentials are displayed in re ularblacktext. All ProQA information is contained in the remarks of the event. If events are sent to a pager and remarks Compared to Dispatch/Notes narrative, the system should send unique ProQA Yes are included, ProQA information is sent to a pager. It information to Text Message/Pager is important to note that due to limitations on text messaging/paging, not all remarks can be included in messages sent to these devices. Compared to Dispatch/Notes narrative, CAD shall send unique ProQA All ProQA information is contained in the remarks of information to MDC/MDT Yes the event. Event remarks are sent to Mobile for Public Safety,the Hexagon mobile client software. Compared to Dispatch/Notes narrative, the system should send unique ProQA All ProQA information is contained in the remarks of information to Record Management Systems Yes the event. Event remarks can be sent to an RMS system. Any information entered into PROQA Paramount that indicate a scene safety I/CAD supports the ability to highlight keywords. The issue when transferred to CAD shall be strongly emphased when presented to Yes County can define a list of keywords or phrases that are contained in ProQA that they wish to have emphasized any receiver in the remarks. After the initial event is created and the ProQA case Information entered into the case after dispatch shall be automatically copied continues to evolve, information is sent from over to the CAD incident and immediately viewable to the CAD users. Yes Paramount to CAD. When the Paramount case is completed the final information packet is sent from Paramount to CAD and the CAD event is updated. The ProQA case number should be linked to the CAD incident in a searchable format Yes Default system functionality 139 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 8-Pro Q&A Ver: 8/1512017 Item Number pro Q & A Response Explanation 8-012 8-013 8-014 8-015 8-016 8-017 8-018 8-019 8-020 8-021 8-022 8-Pro Q & A The system will interface with the Priority Dispatch ProQA Paramount system to enable standardized caller interrogation between the caller and call taker, and provide a set of pre -arrival instructions to assist with emergency call Yes Default system functionality processing. The system automatically initiates the ProQA dialog upon selection by the call No Hexagon stipulates that operators must click the ProQA taker of a nature code associated with the discipline. button to begin the ProQA Case. Requires the County to use ProQA determinants as The resulting dispatch determinant is automatically incorporated into the Yes either the event -type or sub -type for events. This nature code of the active event. requires the mapping of ProQA determinants to CAD event t es/sub-t S. The system should utilize the determinant as the nature code for unit Yes Requires the County to use ProQA determinants as recommendation. either the event -type or sub -type for events. The system should record the determinant as part of the event record. Yes The determinant code is recorded in the remarks of the event. The system interfaces with Priority Dispatch ProQA Paramount for Medical. Yes Default system functionality The system interfaces with Priority Dispatch ProQA Paramount for Fire. Yes Default system functionality Hexagon clarifies that I/CAD does not send any data to Aqua. Aqua reports solely on the information entered All event record data is available for export to Priority Dispatch AQUA 5.1.1.16 Alternate by the user via the Paramount application. To the QA/QI module knowledge of Hexagon, Priority Dispatch does not supply a programming interface to their Aqua database or product. Programs that CAD interfaces with, such as Priority Dispatch ProQA should have both a Function key and a clickable button built into the CAD interface to Yes Default system functionality call the program. Hexagon stipulates that the County must choose to use System must contain field in the CAD user interface that is able to both support ProQA determinant codes as their event -types or sub - and display to the dispatcher the entire Priority Dispatch Code including the Yes types. The ProQA determinant code is written to the Protocol number, Level, Determinant Code, and all assigned suffixes. remarks. All ProQA determinant codes must be mapped per a parameter to CAD event types/subtypes. The ProQA interface shall automatically insert the initial PDS case information The information sent from Paramount to CAD is into the CAD Incident upon send and immediately be viewable to the CAD Yes immediately viewable to anyone who views the event users. I lassurning that the event is accepted. 140 of 186 Company: Intergraph Corporation Vb/a Hexagon Safety B Infrastructure s-rnou�ie ver ensrzor� Item Number Mobile - MDC Response Explanation 9-001 9-002 9-003 9-004 9-005 9-006 9-007 9-008 9-009 9-010 9-011 9-012 9-015 9-Mobile Ifvendor's mobile option is not used by all stakeholders provide a system that works with the Hexagon has proposed our to the Motorola Premier Message Switch to support this existing Motorola data radio infrastructure, and which will work with future broadband systems, Yes requirement. or simultaneous) with both es ofsystems. The mobile data application provides incident data from CAD to the mobile device associated Yes COTS Mobile for Public Safety (MPS) functionality to the units dispatched to an incident. The in -vehicle mobile data application can restrict administrative rights to designated The Mobile Data Terminal (MDT) Command Table has a column for Security Level. This column authorized users. Alternate contains the security level that governs access to the command. Restricting administrative rights to the MPS application itself is a function of the agency. The mobile data application is a single, integrated application forthe delivery and viewing of Yes COTS MPS functionality. With regard to NCIC queries, these are through the use of I/Informer events, mapping, messaging, NCIC inquires, hazards, and alerts. (optioned in the response). The system supports real-time event, status, and map updates to the mobile device. Yes COTS MPS functionality The event data displayed on the mobile device is forms -based. Yes Hexagon assumes that the reference to "forms -based" means that MPS provides forms, receives input from the user and sends this in put out to a particular destination. The event forth can be configured by an authorized user. Hexagon clarifies that an authorized user would need to know how to code in HTMUXML/JavaScript to configure the form. So while an authorized user can configure the Event form, ifthey do not have Yes sufficient coding knowledge/experience with the above, it is possible configuration issues with the forth may occur. Hexagon welcomes further discussion regarding the event form configuration requirements for end users. If the County desires Hexagon to configure event forms per user instead, this will require The system shall have the ability to use a NetMotion VPN client Yes Other customers have used this with MPS in the past. The system shall have the ability to use Go To Assist or other remote support application of Yes MPS itself does not restrict what remote support tool is used. If the remote user can access Windows, ourchoice he y have access to MPS. The system shall have the ability to use AirWatch Mobile Data Management software to Alternate Hexagon uses Remote Content Manager (RCM) for MPS updates. It is included as part of the proposal deploy the application and updates response. The system shall have the ability to perform updates to applications or support files (i.e. maps) Yes Hexagon uses Remote Content Manager (RCM) for MPS updates. It is included as part of the proposal overthe network, silently. response. Hexagon assumes this is in reference to the MDT Server only and that it meets current hardware/software recommendations at the time of implementation. There is no need to run this O/S The system should utiize a Microsoft Windows 2016 server operating software. Yes on the MPS client. Windows Server 2016 Datacenter is recommended for each physical host server. Licensing for Windows Server 2016 is per core, sold in 2- core packs. All cores on the host must be licensed. Licensing a single two -processor host server with Windows Datacenter allows as many Virtual Machines (VMs) as can be allocated to a single host server to run on the host. Hexagon assumes this is in reference to the MDT Server only and that H meets current The system shall utilize a Microsoft Windows 2012R2 or newer server operating software. Yes hardware/software recommendations at the time of implementation. There is no need to run this O/S on the MPS client See answer above. The system shall operate within a VMWare 6.x and VMotion environment. Yes The system can operate with a VMware 6x and Vmotion environment. Hexagon assumes this means forthe database servers which interact with the MDT servers and that it The system should utilize Microsoft SQL 2016 Enterprise Cluster database software. Yes meets current hardware/software recommendations at the time of implementation. There is no need to run this on the MPS client. Hexagon recommends Microsoft SQL Server2016 EE for database servers. Hexagon assumes this means for the database servers which interact with the MDT servers and that it The system shall utilize Microsoft SQL 2014 or higher. Yes meets current hardware/software recommendations at the time of implementation. There is no need to mn this on the MPS client. Hexagon requires Microsoft SQL Server 2016 EE for database servers. The system shall support the Microsoft SQL AlwaysOn o0ering. Yes Mobile will support this if that is how the CAD database servers are setup. 141 of 186 Company: Intergraph Corporation Vb/a Hexagon Safety & Infrastructure Item Number Mobile - MDC 9-018 9-019 9-020 9-021 9-022 9-024 9-025 9-026 9-027 9-9cb,18 9-Mobile Ver &151201] Response Explanation MPS requires Windows O/S. However, Mobile Responder (optional) is O/S neutral and supports the following: - Apple® Inc. devices (iPhoneS and iPadS) with 10STM 9.0 or greater (Tested using iPhone 6, iPad The system should be OS neutral. (Windows, Android, iOS) Alternate Mini, and iPad Pro) - Google® Inc. Android T" devices with OS versions 5.0 or greater (Tested using Galaxy S6, LeEco Let, Moto G2, and OnePlus One) -Microsoft Surface Tablet@with Windows 10(-Tested using Surface Pro 2 and Surface Pro 3 The software can be licensed based on site or enterprise. Alternate Hexagon welcomes the opportunity to discuss its licensing model with the County after selection. A site license is not proposed at this time. Please refer to the explanation in TAB 3 - Finn Plan of Approach. The software can be licensed based on concurent users. Yes Concurrent user licenses are proposed for MPS. The system should have an iOS application that is available through the Apple Store Alternate his is supported in Mobile Responder (optioned) only. MPS requires Windows O/S and is not app based. The system should have a Windows application that is available through the Microsoft Store Alternate his is supported in Mobile Responder (optioned) only. MPS requires Windows O/S and is not app based. The system should have an Android application that is available through the Google Play Alternate his is supported in Mobile Responder (optioned) only. MPS requires Windows O/S and is not app Store based. The system should be adaptable to run on laptops, tablets, smart phones, and desktops Alternate MPS runs only on laptop and Mobile Responder (optioned) runs on tablets and/or smartphones. MPS ill not ada pt to a smarthone and Mobile Responder will not adapt to a desktop. The system shall be able to pass all incident information (i.e. address, calltype) to other No Further discussion is needed regarding "other application" prior to committing to a Yes answerto this applications on the same device. requirement. In the configuration proposed, database redundancy is provided via implementation ofthe Disaster Recovery (DR) site using a Microsoft AlwaysOn Cluster. Hexagon's recommended configuration provides a high availability (HA) solution and is based on our evaluation ofthe RFP and several decades of experience with public safety customers. Our database (DB) recommendation is based on the usage of SQL AlwaysOn using SQL Enterprise for DB high availability (HA). SQL Enterprise is recommended to reduce downtime for maintenance asks since many IDS maintenance functions can only be performed online when using SQL Enterprise. Whenever HA is desired for any portion of our application Hexagon recommends a minimum of two (2) nodes at a primary location and a tertiary node at a second location. This allows for easy failover at the primary site for server maintenance and the potential to manually failover to a secondary location when The system should be capable of achieving 99.999 % availability. No required. The calculation of system availability is dependent upon many requirements, some ofwhich are not within Hexagon's scope of management. System availability is dependent upon the following: -Power source including UPS, PDUs - Physical infrastructure including servers, switches, network cabling - Disk storage, local storage, SAN, direct attached storage, etc. -Operating system - Relation Database software The applications being supported hile it is possible to configure Hexagon's application for high availability, Hexagon cannot contractually commit to 99.99xq uptime because Hexagon does not support all ofthe items listed The system database backups shall be performed online without DBMS downtime Yes MDT Server utilizes the same database as CAD The system Data stored within the RDBMS shall be secured. Describe how. Alternate Security ofthe Data stored is a function of the agency and theirsecurity policies. fi 186 Company: Intergraph Corporation ilb/a He gw Safely & Infrastructure Item Number Mobile - MDC 9-029 9-030 9-031 9-032 9-033 9-034 9-035 9-036 9-037 9-Mobile 9-Mobile Ver &151201] Response Explanation The system should support database replication. Yes MDT Server utilizes the same database as CAD. This is supported in the Mobile system if this is configured for CAD. The system shall record all database changes as well as other events in the system that may not result in a database change. Every change to the data within the database must be No Not currently supported. recorded in the Auditing System. The Hexagon CAD password system allows for the following County defined settings. On the personnel record, number of days the password is valid. Via parameters, EncryptionType, Algorithm name for the symmetric encryption used for some password fields. See MSDN documentation on CryptoConfig for a complete list of valid names. I Password First, In the parameter's Value field, enter a generic password to be used when creating new user accounts. Then, when a new user account is created in the Personnel dialog box, this password should be entered in the Password field. After the user signs on to the application for the first time using this temporary password, the application will inform the user to change their password to a password oftheir choice. The persl record will The system shall provide a Lee County configurable password management system. Yes automatically be updated with the users new password. The Reset Password command returns a Passwords must be configured for expiration, minimum length, character types and numbers. users password to the default, generic value entered for Password First. I Password Hashld, Default Hash used on passwords. 1 - MD5, 2 - SHA512 I PasswordHistory, Determines the number of unique new passwords that have to be associated with a user account before an old password can be reused. PasswordMinAge, Minimum number of days before the password can be changed. PasswordMinAlpha, Minimum number of characters from : A - Z, a - z I PasswordMin Digits, Minimum number of characters from : 0 -9 1 Password Min Length, Minimum # of characters required for a password. I Password Min Lower, Minimum number of characters from : a-z I PasswordMinSpecial, Minimum number of characters from :'-!@#$ % A&*O_+-={}�[]\:".'<>? /spaced PasswordMin Upper, Minimum number of characters from : A -Z The system should include a browser based administration tool for all configuration and Alternate Hexagon offers CADDBM as part of the CAD system. It is not browser based. provisioning activity. The system should process management in real time. This means any parameter change or MPS does not process parameter changes in real time globally, nor will it process parameter changes database change the system should be done while the system is online. The change should No while MPS is being used. Depending on the change, it could require an update and MDT and MPS to take effect immediately be restarted. The system shall have the ability of roaming across a variety of networks, to give the userthe Alternate Hexagon assumes this is the function of NetMotion, not MPS. most constant and reliable connectivity. The system shall provide Designated Users the ability to configure Mobile GUI to their Hexagon offers a limited MyMenu feature as part of Mobile. Depending on the level of configuration specifications. Yes desired, additional services may or may not be required at additional cost. Hexagon welcomes further discussion with the County regarding their configuration needs. Designated user is the sys admin The mobile system's function keys should be customizable, giving easy access to frequently Yes COTS MPS functionality used functions. Hexagon assumes this means (/Informer queries. (/Informer has been optioned in the proposal. The Mobile queries shall be customizable by the agency No Depending on the types and amounts of customizations, additional services may or may not be required at additional cost. Hexagon's current I/Informer optioned bid supports Person, Vehicle, Article and Gun queries. 143 d186 Company: Intergraph Corporation Vb/a Hexagon Safety & Infrastructure Item Number Mobile - MDC 9-038 9-039 9-040 9-041 9-042 9-043 9-044 9-045 9-046 9-047 9-048 9-049 9-050 9-051 9-052 9-053 9-054 9-055 9-056 9-057 9-058 9-059 BJd ,b Vey_ W-017 Response Explanation The system shall include commonly used pre -defined reports and an ah-hoc report wrfling Alternate MPS does not provide an ad -hoc reporting tool. Users are able to print limited and specific MPS tool. reports, but MPS data captured in the CAD database can be accessed by InSi ht Reporting. The system should have the ability to operate in a "window Ake" environment to support Navigating to a different screen within MPS will cause the userto be taken away from the initial working concurrent processing (e.g., invoke a hazard inquiry using a different "window" without losing No initial working screen). screen. The system shall have the ability to install third -party programs on the MDC. Yes MPS itself does not restrict agencies from installing third -party programs on the client workstations. Hexagon should be consulted to confirm those programs will not cause a conflict prior to installation. The system shall have the ability to accurately timestamp all field and dispatch transmissions to Yes es, as long as the County IT ensures their hardware is time -synced with the CAD/MDT servers. and from MDC. The system shall have the abilityto support local and network printing. Yes MPS has the abilityto pdnt some reports locally and through the network, but network pdnting does depend on the customers network and ifthey allow ft. The system shall have the abilityto log all mobile activities (e.g., chats, messages, uploads/downloads offield reports) b the following .MDC Yes II of the below are logged in MPS, either in log files, database columns, or the raw XML files sent to and from the server. .Case number Yes See answer above. .Date and time of transmission Yes See answer above. .Incident number Yes See answer above. .IPAddress Yes See answer above. .Radio device ID Yes See answer above. .Terminal ID Yes See answer above. .Unit call sign Yes See answer above. .User ID Yes See answer above. .User name Yes See answer above. The system shall have the ability to provide a home page with the following items: .Current/active calls Yes MPS offers an Event Monitor .Pending calls Yes MPS offers an Event Monitor .District summary Yes MPS offers a Event & Unit Monitors that can be sorted The system shall have the ability to log and display all times in military (24 hour) clock format. Yes The system can be configured to display military time instead ofthe normal computertime. This configuration is currently not proposed. Hexagon welcomes further discussion on this requirement. The system shall have the ability to provide an acknowledgement to all received transmissions. No If configured, officers in the vehicle will be required to acknowledge receiving the dispatch messages using a status Code of Acknowledge. Any messages marked as critical within the Send Message module requires an acknowledgement. 9-Mobile 144 of 186 Company: Intergraph Corporation /b/a Hexagon Safety & Infrastructure Item Number Mobile - MDC 9-060 9-061 9-062 9-063 9-064 9-065 9-066 9-067 9-068 9-069 9-070 9-071 9-072 9-073 9-074 9-075 9-IEA466 BJAobile Vey_ &15I201] Response Explanation status bar is displayed within Mobile for Public Safety. A section of the status bar displays green when network traffic occurs and red when network traffic fails. Status Indicators: Display network transmission and reception information. These flash green when network traffic occurs and red when network traffic fails. • Rx: Flashes to indicate if server transmission is received. •Tx : Flashes to indicate transmission to the server. The system shall have the ability to indicate when CAD is unable to receive a transmission. Alternate • Er. Flashes when a transmission to the server fails. • Network status display: Displays the current client -to -server connection status: • Green = online • Red = offline If enabled for your site, a sound plays within in the MPS client when it goes offline and comes back online. The system should have the ability to have a command line in Mobile for commonly used No A command line is not available in MPS. functions The system shall have the ability to limit all commands to only one or two key strokes for functions including, but not limited to: This would need to be configured, which may or may not require additional services at additional cost. It .Logon/logo0 No is possible that it could be configured as part of the configuration workshops currently proposed. Hexagon welcomes further discussion on this requirement. This would need to be configured, which may or may not require additional services at additional cost. It .Access to web links No is possible that it could be configured as part of the configuration workshops currently proposed. Hexa on welcomes further discussion on this requirement. .Using mapping features No This is dependent on the map features. Not all may be able to support this. This would need to be configured, which may or may not require additional services at additional cost. It .Clear incident call No is possible that it could be configured as part of the configuration workshops currently proposed. Hexagon welcomes further discussion on this requirement. .Look up premise history Alternate Searching premise history may require entering in location information, thereby using more keystrokes. The system shall have the ability to accelerate routine data entry tasks (i.e. workflow, functionalft with the following: .Drop -down lists Yes MPS has dropdown lists. .Auto-fill/auto-search Alternate Most of the dropdown lists will autofill entries, but not all. .Keyboard macros No There are no keyboard macros in MPS for data entrytasks The system shall have the abilityto perform the following tasks at any MDC: .Remote printing (user definable) Yes his is dependent on how the customer has their network set up. If the network is set to support this and printers are available in the vehicles then this can be supported. .CAD Database inquiries Yes COTS MPS Functionality .Electronic messaging between two or more MDCs Yes COTS MPS Functionality .Electronic messaging between all MDCs Yes COTS MPS Functionality 145 1 186 Company: Intergraph Cwpwation llb/a Hexagon Safety & Infrastructure Item Number Mobile - MDC 9-077 9-078 9-079 9-080 9-081 9-082 9-083 9-084 9-085 9-086 9-087 9-088 9-089 9-090 9-091 9-092 9-093 9-094 9-095 9-096 9-0017 BJAobile Vey_ W-017 Response Explanation -Electronic messaging between MDCs and CAD Yes COTS MPS Functionality Hexagon assumes this means (Wormer queries. I/Informer has been optioned in the proposal. .Inquiries to designated local, state and national databases Alternate Depending on the types and amounts of inquiries, addifional services may or may not be required at additional cost. Hexagon's current I/Informer bid supports Person, Vehicle, Article and Gun queries. Hexagon assumes that "electronic maps" means Google or Bing maps only. If some other electronic .Access and display of electronic maps Yes map is meant, then the response to this item will need to be re-evaluated. The customerwould be responsible forthe purchase of any 3rd party licenses necessary to support this (Le. Google). •Access and display of electronic photos Yes COTS MPS Functionality .Query specific unit status Yes COTS MPS Functionality .Query specific unit location Yes COTS MPS Functionality Hexagon assumes this is referencing Drivers License photos from I/Informer queries. However, it is Hexagon's understanding that the current FCIC message switch does not support image responses, .Display thumbnail photos on MDC No so queries for image returns, though available, have not been quoted in this response. Hexagon welcomes further discussion on this requirement as more information from the state will be needed riortobein abletoothe rio rement. u s epon s and forwhatis needed. MPS currently supports a magne is stripe reader capability, namely the MagTek P/N 21040110, which has a USB interface that support a "Keyboard Emulation Software Interface." MPS also supports the L-Tron TraCS 4810 2D barcoded .Read magnetic stripes in unit for information retrieval Modification scanners via an emulated RS232 port and the PDF417 format using a model E-seek 250. Hexagon assumes the device to be used is one Hexagon already supports. If not, additional services may be required at additional cost. Hexagon has proposed services as part of implementation to support configuration of ether a magnetic stripe reader or barcode reader. If both are required, additional services ma be r uired at additional cost. isdependson a ce o e evlus an or what is needed. MPS currently supports a magnetic stripe reader capability, namely the MagTek P/N 21040110, which has a USB interface that support a "Keyboard Emulation Software Interface." MPS also supports the L-Tron TraCS 4810 2D barcoded .Read Bar/QR Codes for information retrieval Modification scanners via an emulated RS232 port and the PDF417 format using a model E-seek 250. Hexagon assumes the device to be used is one Hexagon already supports. If not, additional services may be required at additional cost. Hexagon has proposed services as part of implementation to support configuration of ether a magnetic stripe reader or barcode reader. If both are required, additional services may be reauired at additional cost. The system shall have the abilityto support touch -screen functionality. Yes COTS MPS Functionality The system should have the abilityto support voice activated (voice command) functionality. Alternate This is supported in Mobile Responder only. Mobile Responder is optioned in this response. The system shall have the ability to perform commands using any ofthe following methods: .Easy access toolbar Yes COTS MPS Functionality .Right mouse click No No right mouse click options in MPS .Agency defined function keys (hot keys) Yes COTS MPS Functionality •Unlimited command lines No No command line in MPS .Touch screen Yes COTS MPS Functionality The system shall have the abilityto use the following to invoke a function (e.g., status change, send message, etc. .Command entries on a command line No No command line in MPS -Function keys (one touch keys) Yes COTS MPS Functionality .Point -and -click devices (i.e., mouse, trackball, touch pad) Yes COTS MPS Functionality 146 If 186 Company: Intergraph Cwpwation llb/a Ha gon Safety & Infrastructure Item Number Mobile - MDC 9-098 9-099 9-100 9-101 9-102 9-103 9-104 9-105 9-106 9-107 9-108 9-109 9-110 9-111 9-112 9-113 9-114 9-115 9-116 9-117 9-118 9-119 9-120 9-121 9-122 9-123 9-124 9-125 s rtloa&6 BJA Nb Vey_ &15 017 Response Explanation •Touch screen Yes COTS MPS Functionality The system should have the abilityto provide a command line continuously on the MDC screen. No No command line in MPS The system shall have the ability to move the cursor forward and backward to complete data Yes COTS MPS Functionality fields without having to retype the entire field e.., insert and delete, cut and paste). The system shall have the ability to page up and down. Yes COTS MPS Functionality The system shall have the ability to scroll up and down. Yes COTS MPS Functionality The system should have the ability for user to prompt for additional information or to No Not currently supported. review/repeat information with one keystroke. The system shall have the ability to require both user identification and password or user code. Yes MPS supports username & password The system shall have the ability to temporarily disable access to the mobile data device with a Yes Restricting access to the "mobile data device" is the function of hardwareloperating system security. single keystroke and unlock the unit by entering a password to return to normal. MPS offers the ability to lock the application itself and unlock it using by entering a password. The system shall have the ability to log -on multiple (6) individuals per unit. Yes COTS MPS functionality. The system shall have the ability to automatically log -off current users upon entry of a new log- No Not currently supported. on command by a new user. The system should have the ability, when there are multiple users logged onto one MDC, to Alternate As long as the person logging off is not the Primary user. allow one responder to log -off the system while allowing the others to remain logged on. The system shall have the ability to support an automatic download of software/files at log -on Updating MPS via the Remote Content Manager (RCM) tool at logon requires that MPS not be in use without interfering with operational performance (background application). No at the time. Users are prompted at logon. They can select to delay the updates and manually update later. The system should have the ability to automatically update CAD or other systems unit roster Yes Hexagon assumes that in the context of this requirement, "Roster' refers to the units currently logged information based on MDC log -on information. into service. This may be able to be accomplished by adding a custom status not currently proposed. This would The system shall have the ability to separate MDC log offfrom designating status as off -shift. No require additional services at additional cost. Hexagon welcomes further discussion on this re quirement. This may be able to be accomplished by adding a custom status not currently proposed. This would The system shall have the ability to separate MDC log on from designating status as on -shift. No require additional services at additional cost. Hexagon welcomes further discussion on this re quirement. The system shall have the ability to display the following information on the screen during normal operations: .Shall have the ability of wireless connectivity, where available Yes COTS MPS Functionality .Communication verification and other MDC operational status Yes COTS MPS Functionality .Current status of defined units Yes COTS MPS Functionality .Incident number Yes COTS MPS Functionality .Message alert Yes COTS MPS Functionality .Radio talk group (if assigned) Alternate If captured in CAD. .Unit ID Yes COTS MPS Functionality .Vehicle location Yes COTS MPS Functionality The system shall have the ability to support agency -defined hot keys and programmable function keys with the following agency configurable functions and statuses: .Arrived/unit on -scene Yes COTS MPS Functionality .Retrieve call information Yes COTS MPS Functionality .Clear/available Yes COTS MPS Functionality .At Hospital Yes COTS MPS Functionality If 186 Company: Intergraph Cwpwation Vb/a H—gon Safety & Infrastructure Item Number Mobile - MDC 9-127 9-128 9-129 9-130 9-131 9-132 9-133 9-134 9-135 9-136 9-137 9-138 9-139 9-140 9-141 9-142 9-143 9-144 9-145 9-146 9-147 9-148 9-149 9-150 9-151 9-152 9-153 9-Mob i$4 9Jdobile Vey_ W-017 Response Explanation -Display message Yes COTS MPS Functionality .Disposition call No Further discussion is needed regarding this requirement. .Emergency Yes COTS MPS Functionality This may be able to be accomplished by adding a custom status not currently proposed. This would .Enroute to station No require additional services at additional cost. Hexagon welcomes further discussion on this re quirement. .Enroute/unit responding Yes COTS MPS Functionality .In-service Yes COTS MPS Functionality .In-service/report writing Yes COTS MPS Functionality •Maps Yes COTS MPS Functionality .Out -of --service Yes COTS MPS Functionality .Premise information Yes to perform a Location of Interest (LOI) search .Secure terminal (easyto lock and unlock) Yes COTS MPS Functionality .Store/recall Alternate Recall only This may be able to be accomplished by adding a custom status not currently proposed. This would .Unit status No require additional services at additional cost. Hexagon welcomes further discussion on this re auirement. This may be able to be accomplished by adding a custom status not currently proposed. This would .Unit status OK (Y/N) No require additional services at additional cost. Hexagon welcomes further discussion on this re quirement. .Units assigned to call Yes user can see this information on the Dispatch Report and access the Dispatch Report via a programmable hot key - This may be able to be accomplished by adding a custom status not currently proposed. This would .Enroute Hospital No require additional services at additional cost. Hexagon welcomes further discussion on this re uirement. Hexagon clarifies that additional definitions would need to be further clarified prior to Hexagon providing .Additional definitions as necessary No additional LOE to support this requirement as the definitions may require customizations. The LOE would be at additional cost. The system shall have the ability to initiate an emergency message transmission from a touch Yes COTS MPS Functionality screen button or hot key. The system shall have the ability to Automatically transmit the following information in an emergency situation: .User name Alternate he message would have to be modified to include this information. MPS uses the Unit ID in the Emeroencv message, but a user can go to the Unit Monitor and see all Unit/User information. .User ID Alternate he message would have to be modified to include this information. MPS uses the Unit ID in the Emergency message, but a user can go to the Unit Monitor and see all Unit/User information. .Location Yes It will display the last known location or current GPS location if available. .Reference to incident Yes Hexagon assumes this is the Event Number. The system shall have the ability to send to all mobile and CAD users (except the sender) an The system has the ability to send a message to either everyone currently logged into the system or emergency notification with unit ID and location (if known) when the emergency key is Yes everyone in that particular Units Dispatch Group. The user that pressed the Emergency button will also activated. receive a message. The system shall have the ability to prevent emergency notification from appearing on the No his may require a customization that is not currently proposed, which would require additional services sender's screen. at additional cost. Hexa on welcomes further discussion on this requirement. The system shall have the ability forthe MDC screen to revert to its priorview after the user Yes COTS MPS Functionality dismisses an emergency message. The system shall have the ability to view pending calls. I Yes ICOTS MPS Functionality The system shall have the ability to view active calls. I Yes ICOTS MPS Functionality 1 166 Company: Intergraph Corporation Vb/a Hexagon Safety 8lnfrastructum Item Number Mobile - MDC 9-155 9-156 9-157 9-158 9-159 9-160 9-161 9-162 9-163 9-164 9-165 9-166 9-167 9-168 9-169 9-170 9-171 9-172 9-173 9-174 9-175 9-176 9-177 9-178 9-179 9-180 9-181 9-182 9-183 9-Mobile 9Jd ,b Vey_ W-017 Response Explanation The system shall have the abilityto receive dispatches on the MDC. Yes COTS MPS Functionality The system shall have the abilityto provide visual oraudible alertto indicate that a dispatch Yes COTS MPS Functionality has arrived. The system shall have the ability to pmvide a distinguishable visual and audible alert for high Yes COTS MPS Functionality prioritycalls as defined b the a enc The system shall have the ability to access and read all call comments associated with a call. Yes COTS MPS Functionality The system shall have the ability to configure comments to be in chronological order or last Yes COTS MPS Functionality entered on to The system shall have the ability to display and buffer the following dispatch information upon dispatch of unit to an incident: .Assisting unit(s) Yes COTS MPS Functionality .Building plans Yes Hexagon configures this using LOI data associated with an address (part of the proposed im lementation). .Comments/narrative (unlimited) Yes COTS MPS Functionality .Complainant Name/Contact Info/Address Yes COTS MPS Functionality .Date and time incident entered Yes COTS MPS Functionality •Document associated with a particular location Yes Hexagon assumes that these would be pre -plans and/or special situations information .Incident location with cross streets Yes COTS MPS Functionality .Incident priority (e.g., user -defined or defined by incident code) Yes COTS MPS Functionality .Incident type Yes COTS MPS Functionality .Map page Modification Hexagon has proposed a level of effort to add a map page field as part of overall implementation services. .New or developing information in free form Yes Hexagon assumes this means the ability to enter event remarks .Phone number at incident location (if different) Yes he Dispatch Report can show the Callers Phone Number. There is also a "Supplemental Contact" forth that can be used to in put information on who to contact when a user is onsite. .Premise and prior information flag Yes All listed on the Dispatch Report, Location of Interest (LOI) section. .Premise history information Yes All listed on the Dispatch Report, LOI section. .Recommended route Yes There is a "Route to Event" function that will plot a route from the user's current location to the location of the Event. .Reporting party name, phone number, address Yes There is both the "Caller" info section and a "Supplemental Contact" form for this information. .Attachments such as photos, audio recording, or streaming video No Streaming video is not supported. However, files can be attached. The system shall have the ability to receive supplemental incident information (e.g., location, here is a "Supplemental Information" section on the Dispatch Report. suspect, vehicle or other information, etc.) without interupting/ovedaying current screen. Yes The system shall have the ability to receive notification of Dispatcher -initiated changes to an COTS MPS Functionality incident (e.g., supplemental information, unit reassignments, incident cancellation, preempting Yes off call etc.) without interrupting/oveflayinq current screen. The system shall have the ability for mobile screen to update automatically as new information Yes COTS MPS Functionality is added to a call. The system shall have the ability to transmit status information to the CAD system in real time. Yes COTS MPS Functionality MPS does not let the user change the Event status from "Active" to something like "Held" or "Pending", The system shall have the ability to update call status from field. Alternate however, the system can be configured to close the Event when the last unit clears from the Event. The system shall have the ability for changes and updates to be made interactively and Yes COTS MPS Functionality instantly transmitted to or from the CAD system. 186 Company: Intergraph Corporation llb/a Hexagon Safety & Infrastructure Item Number Mobile - MDC 9-184 9-185 9-186 9-187 9-188 9-189 9-190 9-191 9-192 9-193 9-194 9-195 9-196 9-197 9-198 9-199 9-200 9-Mobile &Mobile Vey_ &1512017 Response Explanation The system shall have the ability to sort information and toggle back and forth among his would need to be configured globally, which may or may not require additional services at windows. No additional cost. It is possible this could be configured as part ofthe configuration workshops currently proposed. Hexagon welcomes further discussion on this requirement. The system shall have the ability to advise user of data entry or command errors with clear and concise messages. Yes The system provides clear Error messages. This would require a customization at additional cost not currently proposed. Hexagon can possibly The system shall have the ability, with appropriate supporting map/AVL technology, to indicate No create a one-shot (one key stroke) Field Event of a specific Event type and the system, using the Units unit location when initiating an on -view incident with a function key. GPS location, will know where that Unit is at. Hexagon welcomes further discussion on this re uirement. The system shall have the ability to validate on -view location at the dispatch level (to avoid Yes MPS can use the "Verify Location" command to confirm if that location is in fact an address in the hang-ups in the field). system. The system should have the ability automatically change to an arrive status by comparing Yes Hexagon assumes this to mean a Halo around the location. incident location and vehicle location The system should have the ability to initiate any query with a single key stroke. No Not currently supported. Hexagon assumes this in in reference to certain queries using I/Informer (optioned). Hexagon's current The system shall have the ability to use predefined data entry formstscreens (masks) to Alternate option supports Person, Vehicle, Article, and Gun queries. Depending on the transactions desired for minimize data transmitted dudng queries. his, additional services may or may not be required at additional cost. Hexagon welcomes further discussion on this requirement. The system shall have the ability for agency to create standard screen formats for all agency Hexagon assumes this is via the optioned I/Informer queries mentioned above. Depending on the "all" inquiries. Alternate transactions desired, may not be able to be supported. Hexagon welcomes further discussion on his re quirement. The system shall have the ability to perform agency -defined pertinent CAD query or update The MDT Command Table has a column for Secudty Level. This column contains the security level that functions subject to access privileges (e.g., adding miscellaneous text comments to a call; Yes governs access to the commands. adding disposition code to a call etc.. MPS does offer a few Su pervisor level features out of the box (e.g. Supervisor Add Comments). Ability to configure premise and hazard information notifications including: Hexagon may be able to configure this as part ofthe existing implementation services bid depending on .Font Color No he level of configuration desired and also depending on whether configuration is at the user or agency level. Additional services at additional cost may or may not be required. Hexagon welcomes further discussion on this requirement. Hexagon may be able to configure this as part ofthe existing implementation services bid depending on .Font Size No he level of configuration desired and also depending on whether configuration is at the user or agency level. Additional services at additional cost may or may not be required. Hexagon welcomes further discussion on this requirement. Hexagon may be able to configure this as part ofthe existing implementation services bid depending on .Background Color No he level of configuration desired and also depending on whether configuration is at the user or agency level. Additional services at additional cost may ormay not be required. Hexagon welcomes further discussion on this requirement. Hexagon may be able to configure this as part ofthe existing implementation services bid depending on .Placement on screen No he level of configuration desired and also depending on whether configuration is at the user or agency level. Additional services at additional cost may ormay not be required. Hexagon welcomes further discussion on this requirement. Hexagon may be able to configure this as part ofthe existing implementation services bid depending on .Audible (e.g. special beep tone) alarm No he level of configuration desired and also depending on whether configuration is at the user oragency level. Additional services at additional cost may ormay not be required. Hexagon welcomes further discussion on this requirement. The system shall have the abilityto drill down into query returns regarding a potentially Yes COTS MPS Functionality hazardous substance, and/or location to find the details of that hazard. The system shall have the abilityto select results from queries and drill down for detailed Yes I COTS MPS Functionality. When event information is returned you can drill down for additional information. information. 150 of 186 Company: Intergraph Corporation Vb/a Hexagon Safety 8lnfrastructure s-naoe�ie ver W1s 017 Item Number Mobile - MDC Response Explanation 9-201 9-202 9-203 9-204 9-205 9-206 9-207 9-208 9-209 9-210 9-212 9-213 9-214 9-215 9-216 9-217 9-218 9-219 9-220 9-221 9-222 9-223 9-224 9-225 9-226 9-227 9-Mobile The system shall have the ability to differentiate between call data and query results (e.g., Yes Call data (a Dispatch Report) goes to a different Inbox than a query result. color, font, screen location). The system shall have the ability to query unit status by: .Geographic area (e.g., area, beat, district, division, etc.) Yes Unit Monitor filters .Dispatch group Yes Unit Monitor filters .Unit ID Yes A Who Report will show the userthat Unit's status and the Unit Monitor will show that Unit's status. .Date and time range Yes Unit History .Call/event type Yes Event Monitor filters .Location Yes Unit Monitor filters .Incident type Yes Event Monitor filters .Unit status Yes Unit Monitor filters The system shall have the ability user to chose which group and division messages to receive. No Not currently supported. MPS itself does not store messages for later viewing except keeping them in MPS until either manually The system shall have the ability to store messages for later viewing. No deleted or the user logs off. Messages are stored in the database for auditing but cannot be retrieved later. The system shall have the ability to store for later recall messages over an agency -defined time Users can retrieve a Dispatch report using the Recall Dispatch command in Mobile for Public Safety if period that were delivered during a log -on session. Alternate they are assigned to the event and have erased the dispatch report. Messages are retained in Mobile for Public Safety until the user logs off, the user deletes it. The system shall have the ability for host computerto store unread messages when userlogs Yes Hexagon assumes by "host computer' that this means the host server. Off. The system shall have the ability to sort stored messages based on priority and then by No Messages stored on the server are not sorted by priority. date/time. The system shall have the ability for messages to be able to be sorted by most recent or first Yes The headers in that Inbox are clickable which allow users to sort based on the most recent or first call received. received. The system shall have the abilityto move a return containing a stolen vehicle to the front ofthe message queue. No Hexagon does not prioritize incoming Informer query responses The system shall have the ability for user to decide what types of messages are automatically Users can decide what messages to save and delete for that logged on session. There is no automatic saved (e.g. dispatch, query returns, administrative, etc.). Alternate saving of messages to a location outside of MPS (other than the CAD database and users have no control over that . The system shall have the ability to add and maintain Premise information with permissions. Alternate Premise information is modified through the CADDBM application in CAD. Special Situation information can be entered in the I/Dis patcher application. The system shall have the ability to support AVL functionality. Yes COTS MPS Functionality The system should support the definition of multiple unit display that is available to each user Yes Use of Monitor/Map filters on their mobile map by the System Administrator The system shall have the ability to support GPS functionality. Yes Same as requirement #9-220 above The system shall have the ability to cache map layers to minimize the amount of data Alternate MPS map files are stored locally so there is no need to transmit map data wirelessly transmitted wireless) . The system shall have the ability to support full touch screen capThe system shall have the Hexagon assumes this requirement meant to read, "The system shall have the abilityto support touch ability. Yes screen capabilities." Hexagon notes that this is also dependent on the hardware purchased for mobiles. The system shall have the ability to select and use static and non -static mapping formats. Yes Assuming this means the use of Google maps and Hexagon's built-in CAD map. The customer would be responsible for purchasing any necessary third party licenses (i.e. Google) to support this. The system shall have the ability to support user -definable symbols based on: .Class of features Yes Hexagon clarifies that by "user" it stipulates the user to be the map administrator, not individual field users. 151 of 186 Company: Intergraph Cwpwation Vb/a H—gon Safety & Infrastructure Item Number Mobile - MDC 9-228 9-229 9-230 9-231 9-232 9-233 9-234 9-235 9-236 9-237 9-238 9-239 9-240 9-241 9-242 9-243 9-244 9-245 9-246 9-247 9-248 9-249 9-250 9-251 9-252 9-253 9-254 9-255 9-256 9-257 9-258 9-259 9-RIo� 0 9-Mobile Ver W-017 Response Explanation •Postscript fonts (point data) Yes Hexagon clarifies that by "user" it stipulates the user to be the map administrator, not individual field users. .Icons Yes Hexagon clarifies that by "user" it stipulates the user to be the map administrator, not individual field users. The system shall have the ability to support data developed on an ESRI GIS-based platform, Hexagon confirms for only those items indicated in this requirement (street centerline, address points, "including, including, but not limited to: street centerlines, address points, buildings. Yes and buildings). Further discussion is needed regarding defining those items that fall under but not limited to". The system shall have the ability to display County maps with agency -defined features (i.e., Yes Based on the GIS data Hexagon's system receives. street names, block ranges, terrain features, common places, etc-). The system shall have the ability to provide the same navigation functionality as for CAD Alternate While the MPS map and CAD map use some of the same filestmap data they are not functionally mapping- identical. The system shall have the ability to zoom in and zoom out on map. Yes COTS MPS Functionality The system shall have the ability to zoom by click with reenter. Yes MPS has a function that does this by clicking the screen when in zoom mode The system shall have the ability to zoom in/out to fixed extents. Yes The Zoom In/Zoom Out work by zooming in/out to certain levels The system shall have the ability to pan by scraping across screen. Yes COTS MPS Functionality The system shall have the ability to identify layer attributes. Yes COTS MPS Functionality The system shall have the ability to support dynamic labeling of layers. No Labeling is done at fixed levels that turn on and off based on zoom scale. The system shall have the ability to support scaled dependencies for layers. Yes COTS MPS Functionality The system shall have the ability to support hyperlinks to files, URL's and other documents Alternate Files can be attached to the event information and part of the Dispatch report. (emergency Tans, hazmat . The system shall have the ability to locate address information by address point or street Yes COTS MPS Functionality centerline. The system shall have the ability to display map legend. No Not currently supported. The system shall have the ability to display compass direction between two user selected Alternate If map rotation is enabled, the compass direction displays in the top left comer of the CAD Map points. The system shall have the ability to display distance in standard measurements between two Yes Only on the Directions Tab when generating a Route. user selected points. The system shall have the ability to graphically display street network for a desired coverage area. Yes COTS MPS Functionality based on the GIS data the system receives The system shall have the ability to access and display specific map layers (e.g., apartment Yes COTS MPS Functionality based on the GIS data the system receives complexes, special structures, etc.). The system shall have the ability to display maps with the following features, including, but not limited to: .Streets, intersections and freeways Yes Based on the GIS data the system receives. .Street names Yes Based on the GIS data the system receives. .Block ranges Yes Based on the GIS data the system receives. .Business name Yes Based on the GIS data the system receives. .Major buildings orfacilities Yes Based on the GIS data the system receives. •Parcel Yes Based on the GIS data the system receives. .Map page or reference numbers Yes Based on the GIS data the system receives. .Reporting districts Yes Based on the GIS data the system receives. .Parks Yes Based on the GIS data the system receives. .Schools Yes Based on the GIS data the system receives. .Police / Sheriff/EMS/ Fire stations Yes Based on the GIS data the system receives. .Response areas Yes Based on the GIS data the system receives. .Map or terrain features (e.g., rivers) Yes Based on the GIS data the system receives. 1186 Company: Intergraph Corporation Vb/a Ha gon Safety & Infrastructure s-Moe�ie ver W1s 0t7 Item Number Mobile - MDC Response Explanation 9-261 9-262 9-263 9-264 9-265 9-266 9-267 9-268 9-269 9-270 9-271 9-272 9-273 9-274 9-275 9-276 9-277 9-278 9-279 9-280 9-281 9-282 9-283 9-284 9-285 9-286 9-287 -Photo oveday Yes Based on the GIS data the system receives. .Common places (i.e., point coverage) Yes Based on the GIS data the system receives. .Agency -defined layers Yes Based on the GIS data the system receives. The system shall have the abilityto center map display on: -Current vehicle location (with AVL) Yes COTS MPS Functionality .Dispatch location Yes COTS MPS Functionality .Location of cursorwhen mouse button is clicked No There should be standard Windows functions that can accomplish this and users do not need to rely on the mobile Droduct to support this. .Specified geographic area Yes Based on what the map given to Hexagon by the GIS department looks like, a user could see what geographic location their unit is at. .Station location Yes If the address is searched The system shall have the abilityto display location at cursorwhen mouse button is clicked No There should be standard Windows functions that can accomplish this and users do not need to rely on the mobile product to support this. The system shall have the ability for an apartment complex map to "pop up" when user clicks on the location for the apartment complex (assuming user -created map layer containing site maps) - No Map pop-up attachments are not supported. The system shall have the ability to add and/or delete bookmarks. Yes Assumes this is the Mark Location point of interest marker in MPS The system shall have the ability to center the map on a verified location and mark the location Yes COTS MPS Functionality with a unique icon. The system shall have the ability to automatically link and display map data for a dispatched Yes Assumes this is the Show on Map feature in MPS location. The system shall have the ability to display active incidents and unit statuses on the map. Yes COTS MPS Functionality The system shall have the ability to filterthe display of active incident and unit status based on alternate Filtering is not based on map scale. It is done using the Monitor/Map filter options. ma scale. The system shall have the abilityto support quickest -time routing for all dispatches. Yes COTS MPS Functionality, based on the GIS data Hexagon receives. The system shall have the abilityto calculate directions to incident/specified location. Yes COTS MPS Functionality, based on the GIS data Hexagon receives. The system shall have the abilityto recalculate directions to incident/specified location on the Within MPS while Guidance is on, the userwill hearthe steps of the route spoken aloud. Ifthe unit fy. Yes strays significantly from the route, the mute is automatically recalculated, and the new directions are automatically spoken. The system shall have the abilityto display shortest route from point -A to point-B (Le., street network routing), and highlight quickest route, including directions based upon Yes COTS MPS Functionality, based on the GIS data Hexagon receives. roadway/access availability e.., construction, detours). The system shall have the abilityto view other unit locations and last known locations. Yes COTS MPS Functionality The system shall have the abilityto displayvehicle location on a map and view progress Yes COTS MPS Functionality toward incident location. The system shall have the abilityto display direction oftravel of units. Yes If Unit History is turned on The system shall have the abilityto automatically rotate map so that unit is automatically Yes COTS MPS Functionality displayed moving the same direction. The system shall have the ability to highlight on the map the recommended route from current Yes COTS MPS Functionality location to a dispatched incident site. The system shall be highly user configurable allowing the County to define parameters either No Hexagon welcomes further discussion on this requirement and depending on the level of configurabiity, for all or indivival Agencies. additional services may be required at additional cost. The system shall provide a logging feature that logs adds, changes and/or deletes to any No Hexagon clarifies that changes to the Mobile configuration are not logged configuration item. - 9-Mobile 153 of 186 Company: Intergraph Corporation Vb/a Hexagon Safety & Infrastructure Item Number Mobile - MDC 9-288 9-289 9-290 9-291 9-292 9-293 9-294 9-295 srn 'u ver: aisrzo17 Response Explanation The system shall process data in real time. This means any parameter change or database change is done while the system is on-line. For instance, if a change is wanted to add a new er Remote Content Manager RCM wil prompt the user when to on rfthe want to update their g p p logging y p field to track the when water is put on the fire, they can do this while the Mobile is in -use. The No MPS application. The user can manually update it. field change takes effect upon the next auto synchronization or on a manual synchronization request. The system shall not require a shutdown or logoff of the system or the Mobile clients for No This depends on the configuration change. Some files are read into memory/cached and require a configuration changes. restart of MPS in order to refresh. The system shall have the ability to use a NetMotion VPN client Yes This is one option several of our customers use to get access to the CAD servers from the field. The system shall retain the last known good location for display and recommendation COTS MPS Functionality purposes when a GPS unit logs off, goes under cover, or otherwise stops sending GPS data Yes to the system The system shall save all GPS reports for later use. Yes GPS reporting is stored in Ark and log files or in the database. The system shall have a user interface optimized for daytime and nighttime use. Yes COTS MPS Functionality Based on Unit/Personnel permission there shall be an ability to become part of an incident Yes COTS MPS Functionality (self -dispatch) from the mobile. The system shall have the ability to configure the requirement for acknowledgement of mobile No Acknowledgement is when dispatched, not when premise or hazard information is presented. userwhen premise orhazard information is presented. 9-Mobile 154 of 186 Com parry: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 10-syst— Ver W15/2011 Item Number Systems Response Explanation 10-001 10-002 10-003 10-004 10-005 10-006 10-007 10-008 10-009 10-010 i[rIIr71i 10-012 10-013 10-014 10-015 10-016 10-017 10-018 10-019 10-020 10-021 10-022 10-023 10-024 Transaction Log (Audit Log) The system will maintain a complete audit trail of all user actions including: Date and time of each user login and log off Yes Recorded in the database User History (ushis) table. Date and time of reports printed. No Not currently supported. Date and time of records and/or forms accessed No Not currently supported. Ability to audit at anytime and anyone who views an incident. No Not currently supported. The data capture for this type of audit run in the "background" so that the user's workflow is Yes Supported by default. not unduly impacted The System Administrator or Designated Users shall have the ability to choose whether to No Not currently supported. use this feature on a function basis The system shall have ability to export from the log file. No Not currently supported. Maintain a complete audit trail of all changes to CAD records, database records or forms changed, including • Identification of the user making the change. Yes Requires the use of the CAD Database Management utility (CADDBM) (included with I/CAD). Changes made outside of Hexagon provided software products are not audited • Identification of the record changed Yes Requires the use of the CAD Database Management utility (CADDBM) (included with I/CAD). Changes made outside of Hexagon provided software products are not audited • Old and new value of the field changed. No Not currently supported. • Date and time (YYYYMMDD/HH:MM:SS) Alternate Hexagon uses a proprietary date/time format YYYYMMDDHHMMSS • Location from which the changes were made. Yes Requires the use of the CAD Database Management utility (CADDBM) (included with /CAD). Changes made outside of Hexagon provided software products are not audite • Tra nsactio n Type No Not currently supported. System transaction logs can be searched and retrieved by any parameter stored with the No Not currently supported. transaction. Retention time for the system transaction logs is defined by the agency. Yes This is a system wide setting and configurable by the customer and not by individual agency. System transaction logs can be sorted by any parameter stored with the transaction. No Not currently supported. The system maintains transaction logs for each transaction across all modules. No Not currently supported. Viewing of events is recorded in the audit log and includes the operator ID and workstation I No Not currently supported. from which the event is viewed Executing the historic playback feature is recorded in the audit log and includes the operatoi No Not currently supported. ID and workstation ID initiating the playback functior The system allows the agency to specify and toggle on/off the types of transactions that are No Not currently supported. I recorded in the transaction log Fully audit each user and provide interrogate as to what was created, accessed and/or No Not currently supported. changed. 10Systems 155 of 186 Com parry: Intergraph Corporation d/b/a Hexagon Safety 8lnfraslructure 10-syst— ver W15/2011 Item Number Systems Response Explanation 10-025 10-026 10-027 10-028 10-029 10-030 10-031 10-032 10-033 10-034 10-035 Diagnostics All proposals must include a statement describing diagnostics that are automatically run by the system: • How often is this done and is this time user definable? No There are no automated or routine system diagnostics performed by any I/CAD application • What is the effect on system resources? No There are no automated or routine system diagnostics performed by any I/CAD application • Will the system delay or skip a scheduled diagnostic run if the system is heavily loaded? No There are no automated or routine system diagnostics performed by any I/CAD application CAD shall provide the following administrative reports: • System Failure. No Hexagon stipulates that while system failures are recorded in application level log files, no reporting on those errors is available. • System Errors. No Hexagon stipulates that while system errors are recorded in application level log files, n reporting on those errors is available. • User Logging In/Out with time and date. gg g No While it is possible to turn on auditing using Active Directory to track windows logins an outs, no reporting is available • System modifications made by users. No This is not supported. • System updates and service packs with the date and time. I Yes lHexagon stipulates that this uses standard Windows application monitoring. 10-036 lRequirements Specify any required software, hardware, configurations, interfaces, or other considerations 10 037 not included in uote or scope of work Yes Agency provided network, hardware, VPN, WAN, LAN, client hardware, power 10Systems 156 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 10-syste Ver W15/2017 Item Number Systems Response Explanation 10-038 10-039 10-040 10-041 10-042 10-043 10-044 10Systems In the configuration proposed, database redundancy is provided via implementation ofthe Disaster Recovery (DR) site using a Microsoft AlwaysOn Cluster. Hexagon's recommended configuration provides a high availability (HA) solution and is based on our evaluation of the RFP and several decades of experience with public safety customers. Our database (DB) recommendation is based on the usage of SQL AlwaysOn using SQL Enterprise for DB high availability (HA). SQL Enterprise is recommended to reduce downtime for maintenance tasks since many DB maintenance functions can only be performed online when using SQL Enterprise. Whenever HA is desired for any portion of our application Hexagon recommends a minimum o two (2) nodes at a primary location and a tertiary node at a second location. This allows for easy failover at the primary site for server maintenance and the potential to manually failovert The system must be capable of achieving 99.999 % availability No a secondary location when required. The calculation ofsystem availability is dependent upon many requirements, some of which ar not within Hexagon's scope of management. System availability is dependent upon the following: -Power source including UPS, PDUs - Physical infrastructure including servers, switches, network cabling - Disk storage, local storage, SAN, direct attached storage, etc. - Operating system - Relation Database software -The applications being supported While it is possible to configure Hexagon's application for high availability, Hexagon cannot contractually commit to 99.99xq uptime because Hexagon does not support all of the items I/CAD supports "Single Sign On". Assume a user logs into windows with a usemame o ASMITH. If enabled, Single Sign On allows UCAD to use the ASMITH user ID for windows as the user ID for I/CAD products. However there must be an I/CAD personn Users should have to only sign in once. The workstation sign in should pass through to all No record created in the I/CAD database with a matching user ID (ASMITH in our example applications. Credentials should be kept on an Active Directory server that defines the permissions for ASMITH in I/CAD. If there is an ASMITH user account found in the I/CAD personnel database when an I/CAD application is launched, it will be signed in automatically using the ASMITH permissions. Hexagon has answered no to this requirement as the credentials are not entirely stored in the Active Directory. The system shall operate on County standard equipment and in accordance with County Yes Provided that the County standard equipment and County standards adhere to the standards requirements of the mission critical applicationsHexagon is deliverinc The system should utilize a Microsoft Windows 2016 server operating software. Yes Microsoft Server 2016 is the proposed operating system for the server environment. The system shall utilize a Microsoft Windows 2012R2 or newer server operating software. Yes Microsoft Server 2016 is the proposed operating system for the server environment. The system shall operate within a VMWare 6.x and VMotion environment. Yes The proposed configuration utilizes VMware ESXi 6.x for the server environment. Hexagon clarifies that SQL Server 2016 Enterprise is supported and that AlwaysO The system should utilize Microsoft SQL 2016 Enterprise Cluster database software. Yes Availability Groups are utilized in production, but the I/CAD solution databases required stand alone instances not part of any other SQL instance 157 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure to-syst— ver W15/2017 Item Number Systems Response Explanation 10-045 10-046 10-047 10-048 10-049 10-050 10-051 10-052 10-053 10-054 10-055 10-056 10-057 10-058 10-059 10Syste— The system shall utilize Microsoft SQL 2014 or higher. Yes Microsoft SQL 2016 is the proposed/required database software for the CAD environment. Hexagon clarifies that SQL Server 2016 Enterprise is supported and that AlwaysO The system shall support the Microsoft SQL AlwaysOn offering. Yes Availability Groups are utilized in production, but the I/CAD solution databases required stand alone instances not part of any other SQL instance The system requires proprietary hardware No The required hardware specifications (included in the system configuration diagram attached with this TAB 4) can be met by multiple hardware vendors The system shall, upon detection of faults or failures, send an appropriate message to th Hexagon recommends a third party such as SolarWinds be used to meet thi! Dispatch Supervisor and Designated Users s, accompanied by visible and audible No requirement, this software is not included as part of the proposal response. Hexagon is indications. NFPA 1221: 10.8.2.2 wiling to solicit a quote from SolarWinds for software to support this if desire( A system shall be available to automatically notify support staff when component failures or Hexagon recommends a third party such as SolarWinds be used to meet thi: other predefined system events occur. No requirement, this software is not included as part of the proposal response. Hexagon is wiling to solicit a quote from SolarWinds for software to support this if desire( If any component of the system fails notification should be made to the System Administratc r Hexagon recommends a third party such as SolarWinds be used to meet thi: or designee. No requirement, this software is not included as part of the proposal response. Hexagon is wiling to solicit a quote from SolarWinds for software to support this if desire( If any component of the system fails notification should be made to the Dispatch Supervisor Hexagon recommends a third party such as SolarWinds be used to meet thi! or designee. No requirement, this software is not included as part of the proposal response. Hexagon is wiling to solicit a quote from SolarWinds for software to support this if desire( All lookup tables, agency defined values, configuration settings, etc. are to be fully controlle and maintained by the District and/or participating agencies System Administrators, not by Yes The agency will provide system administrators to perform these tasks. the vendor's personnel at a cost for each change All proposals must include a list of all the failure types and/or codes that the system may Hexagon considers this information proprietary and cannot share it as part of o t. incur. Also, include the user's knowledge base website or wiki if applicable Alternate proposal response. Hexagon will be happy to provide this information when selected a a contract finalized with the County. All proposals must include a statement describing all methods and procedures used t Hexagon considers this information proprietary and cannot share it as part of ot. detect, diagnose, and report potential and actual component problems and failures in the Alternate proposal response. Hexagon will be happy to provide this information when selected a proposed system. a contract finalized with the County. All proposals must include a statement of the average downtime of all its customers when a Alternate For customers with properly configured redundant configurations that suffer a major main server fails. server failure there is no down time All proposals must include a statement showing any special hardware requirements to meet All requirements are included in the system configuration diagram included as an the promised system reliabilityYes attachment with this TAB 4 response All proposals must include a statement showing limitations to the system's scalability and The system is scalable to over 500 calltakers/dispatchers. Scaling may require reliability. Such as maximum number of users, maximum number of incidents, and how erro Yes adjustments to server CPU and memory or additional servers. For the Mobile servers, routines handle attempted violations of the limitations. each server can handle up to 250 users (MPS clients) and 500 MR clients per 1 I/MDT instance and 1 I/Tracker instance Most failure of major components do not require an immediate response from the user All proposals must include a statement showing recommended user response to failure of The system will failover to the redundant server automatically. For other items Hexagon major component(s) on the system. Such as the servers and network. Alternate considers this information proprietary and cannot share it as part of our proposal response. Hexagon will be happy to provide this information when selected and a contract finalized with the County. All proposals must include a statement showing the cost and specifications of extra serve( It is Hexagon's understanding that vendors are not expected to include hardware costs needed for backup, data storage, archive data for analysis, web server, and other purposes part of the overall response. Hexagon has included hardware specifications for servers All proposals should include specifications for server layout, hardware requirements (spec's Alternate needed for backup, data storage, and archiving in the system configuration diagram including memory, cpu, storage, etc). This should include estimated storage requirements t attached with this TAB 4 response. accomodate backups of all resources for this im lemenatior f 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure to-syst— Ver W15/2017 Item Number Systems Response Explanation 10-060 10-061 10-062 10-063 10-064 10-065 Hexagon clarifies that this must be further discussed with the County at a later date a All proposals must include all the power requirements (voltage, frequency, phase, and Hexagon is not providing the hardware for this procurement and the necessary power amperage) for the proposed system. No requirements will be dependent on the hardware that is selected for use. Hexagon has provided hardware specifications as part of the system configuration diagram included an attached with this TAB 4 response All proposals must include problems and failures automatically transmitted to a remote No There are no automatic transmissions of problems or failures. maintenance facility and if so the additional cost for this service All proposals must include recommendations for hardware and software not included in the This may require additional services at additional cost not currently proposed for sit proposal which is needed to enhance network, server, and client architecture within the 9-1- No surveys to determine any additional hardware and software needed based on what the center and provide secure connectivity to outlying user sites. County currently has/intends to purchase. Hexagon welcomes further discussion on thi requirement with the County Hexagon will provide our requirements as part of this proposal, but image IeVE All proposals must include if applications or programs including server, storage and (snapshot) backups are not supported. VMWare clearly states that image/snapshot workstation environments are certified to run on VMWare 6.x Optimal configurations and Alternate backups should not be used on database virtual servers as connection to the network limitations shall also be included. Image level backups must be supported. and storage is lost during the snapshot. It is Hexagon's experience that this connection interruption causes a database failover. CAD system design will include any enhancements needed for security of any internet Without detailed information provided by the County on the full architecture of the access which may include firewalls, VPN's, inscription, and authentications. Alternate network, including all hardware devices, software and firmware versions, Hexagon cannot provide this type of information with its proposal If the proposal does not include a Firewall, all proposals must provide a statement describin at least two types (with specifications) of Firewalls (hardware, software, and/or combination Alternate Hexagon systems do not require specific Firewall makes or models. that are best suited for the CAD system 10Systems 159 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 10,S st— ver W15/2017 Item Number Systems Response Explanation 10-066 10-067 The configuration and maintenance ofsystem files (the database) is accomplished via the CADDBM utility CADDBM is designed to be easy to use so that agency supervisors and system administrators can access create, modify, and maintain the database vsthout programmer support. Information is entered into the database quickly and easily by using dialog boxes. Labeled fields indicate the information required and command buttons help prevent users from deleting the wrong information. Prompts and messages are als displayed for assistance. Completing the dialog boxes in the database maintenance program automatically creates database tables including the following: Agency definition - Cataloged alarm Deployment plans/pattern definition - Disposition type Estimated time of arrival table - Event type Proposals must describe how the CAD system's administrator subsystem is used particular) Line-up dable en fini regarding system tables and file maintenance. Yes - Nu f-s i out--ef-service type - Personnel Response list - Roster definition Rotational service definition - Special address definition Special situation definition - Station definition Street (primary and alias) - Task farce definition Terminal node definition - Unit definition Update cross streets and Update intersections - User group definition Vehicle definition Hexagon sets up a SQL Server maintenance plan to take a full back of the user am Provide a listing of any hardware or software necessary to accomplish back-ups for the CA system databases once per day, and transaction log backups of the I/CAD database system to allow for recovery of data in case of catastrophic event and which of the items will Acknowledge every 15 minutes. The County is responsible for moving these backups off of local be the District's responsibility to provide. Software must be able to co open files for P Y P PY P storage and onto remote storage as the County see's fit. A directory level backup of th 9 9 tY ry P backup. This should be based on the image level backup of the Virtual Machines. I/CAD delivery node that stores delivered software and the County's site specific configurations is also required to support system restoral after a catastrophic failure 10Systems 160 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure to-syste ver W15/2017 Item Number Systems Response Explanation 10-068 10-069 10-070 10-071 10-072 10-073 10-074 10-075 10-076 10Systems Hexagon clarifies that monitoring management software is not included as partof this proposal response. Hexagon recommends third party SC1L Server tools and third party software such as SolarWinds be used performance monitoring of the system, network, and database. Hexagon is willing to solicit a quote forthis software if desired. Hexagon's CAD system can provide some monitoring capabilities using the Interface Service Manager (IS an External System Message Display (ESMD) in the system. With regard to interface monitoring, the ISM manages Hexagon Public Safety interfaces and service. Features beyond what Microsoft Windows offers provided, including support for failing over a service to anothermachine and providing for specific ordering the services startup. The following failure types are supported by ISM: Interface failure —An interface failure is the failure (exit) of a given instance of an interface. ISM detects when an interface terminates abnormally and attempts to re -spawn a new instance of that interface in its place. ISM assumes that if an interface has not exited, the interface is capable of performing its duties. Provide a lisfing of proposed software that will allow the monitoring of the CAD system, Hardware failure — ISM peer requests all interfaces restart on the redundant site as the primary. network, and database (including monitoring or other process hangs which may affect Acknowledge system performance). Concerning EdgeFrenfier interfaces, EdgeFronfier includes tools such as the following: Timer- Provides the ability to raise an event each time an interval (or period) of time elapses. Resource Monitor- Provides the ability to monitor computer system attributes and capture each poll attempt. Network Monitor- Provides the ability to monitor computer network adapters. File Monitor- Provides the ability to monitor a directory forfles that are created, changed, renamed, or deleted from the device. Scheduler- Provides the ability to fire an event at a precise date and time, the event can be set to occu once, or manytimes, recurring fora specified number of iterations. EdgeFronfier can indicate if a network is lost orfound, if a port has changed, if an IP address has change whether the EdgeFrontier Runtime Engine is connected, if an interface is connected (when the operator connect an EdgeFrontier clienttothe EdgeFrontier Runtime Engine, and more. The system must allow administrators to control, modify or update the system without The proposed system allows for failoverto allow a system to be updated without affecting the user's ability to do their work Yes application downtime The system must allow administrators to define user levels. No Feature not supported at this time. Please refer to the security information included in response Tab 3. The system administrator, however, can set user account Drivilege The system must allow System Administrators to define text appearing on menu buttons No Not available based upon agency terminology and/or preference Hexagon understands this requirement to mean using our applications to see th resulting work production from call takers and dispatchers in real time, such as seeing a The system must allow the Dispatch Supervisors/Division Administrators to monitor the worl new event created by a call taker, or seeing the result of dispatching units to an event b of Call Takers and Dispatchers in a real time manner. Alternate a dispatcher. There are no facilities in the UCAD solution to "see" in real -lime the call taker or dispatchers screens for things like monitoring what they type, or what they vie etc. The system must have a module to allow users to enter (Back In) calls and data after syster i downtime(Catch-Up module). Yes Feature available. The system indicates in the event record when event data is entered in catch-up mode. Yes Feature available. Unit status and times may be recorded with an event that is being entered in catch-up mode Yes Feature available. The system allows the agency to reserve a block of event numbers for use with entering event records in catch-up mode Yes Feature available. 161 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure to-syst— Ver W15/2017 Item Number Systems Response Explanation 10-077 10-078 10-079 10-080 10-081 10-082 10-083 10-084 10-085 10-086 10-087 10-088 10-089 10-090 10-091 10-092 10-093 10Syste— The system allows the agency to reserve a block of case numbers for use with entering eve Yes Feature available. records in catch-up mode The event record number is automatically assigned to the catch-up event from a pool of Yes Feature available. unassigned numbers set aside for this purpoSE Records entered in catch-up mode are flagged as such. Yes Feature available. The system should allow Emailing or faxing of incident details (manually and automatically). No Feature not available. The system should not require static I addresses to identify and authenticate workstatior The Hexagon I/CAD solutions requires static IP address assignments and does n( onto the system. If static I Ps are needed the system should be able to recognize remote No support NAT. The network must be fully IPv4 or IPv6, not intermixed, and must be fully workstations coming in via VPN or other dynamically addressed networks and update the routable and support UDP broadcast, UDP unicast, and TCP/IP. Mobiles and other workstation record to allow access and functionali devices connecting via VPN are acceptable The failure of any single component shall not disable the entire system. (NFPA 1221: 10.8.1) Yes The proposed configuration includes redundant systems to maintain application availability The system shall have the ability to transfer alternate Districts and Beats/Response areas Yes Feature available. from the test or training system to the lives stem Hexagon has interpreted this requirement to mean that a supervisor wants to effective The system must allow for the Dispatch Supervisors to take over the screens and workload become the controlling dispatcher or become a calltaker. Using I/Dispatcher terminal of Call Takers and Dispatchers if necessary. Yes node definition the supervisor workstation can become the controlling dispatcher for an combination of agency's and dispatch groups. Supervisors are calltakers at all times when running I/Dis atcher. The system shall have an extensive on-line help system that accurately reflects the state of Yes Hexagon stipulates that the online help is for the default system. Help does not reflect the software in its current version any configurations that may be made specifically for the County The system shall have the ability to limit and allow operational capabilities by the physical Hexagon stipulates that this only applies to the agency and dispatch groups the client h location of the client. Alternate access to. Features and functions within the client are controlled by user command cla assignment. The vendor must provide software upgrades at no additional cost, as part of maintenance Please refer to response TAB 3 - Firm Plan of Approach regarding software release! agreement. In addition the vendor must inform the administrator following: 1) Time frame N0 and upgrades and Attachment 3.3 Master Services Agreement concerning maintenanc allowed before the upgrade(s). 2) Impact of the upgrade(s) on the system. 3) Point of conta terms and conditions. The majority of upgrades, including all services to support them, doing the upgrade(s) along with date and time are offered at cost at time of request. Vendor will automatically notify System Administrator of upgrades when they become Hexagon makes all new software release announcements via our website. Customer available along with release notes. Alternate on a valid maintenance agreement have free access to the release notes for all release software on maintenance. Notifications are not automatic Vendor must provide patches to problems on current version of product being used by the Hexagon cannot commit to this requirement. The Hexagon product center has an N-1 Center, even though fixes may be put into a more current version. No support platform. The current major release of software is supported as is the -1 releas version. The current release of software is 9.4, so support is provided for 9.4 and 9.3. All proposals must include a statement showing the typical response time to a critical syster I Yes Please referto TAB 3 - Firm Plan of Approach with regard to maintenance and failure. resolution targets All proposals must include a list of the maintenance activities that require any user Yes Please refer to response TAB 3 - Firm Plan of Approach, Attachment 3.3 Master involvement and to what extent Services Agreement concerning maintenance terms and condition! All proposals must provide a list of alerts and/or alarms that warn users and/or administrator Hexagon recommends a third party such as SolarWinds be used to meet thi: that maintenance is required. No requirement, this software is not included as part of the proposal response. Hexagon is wiling to solicit a quote from SolarWinds for software to support this if desire( All proposals must list the maintenance activities that will cause all users to be logged off of There is no maintenance activity that requires the users to be logged off the system the system and the typical downtime associated with each. Acknowledge Major version upgrades are the only case where the system will experience total downtime. f 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure IMs to ver W15/2017 Item Number Systems Response Explanation 10-094 10-095 10-096 10-097 10-098 10-099 10-100 10-101 10-102 10-103 10-104 10-105 10-106 Please refer to response TAB 3 -Firm Plan of Approach regarding software release! The maintenance contract(s) will include Upgrades/Fixes to software currently under license N0 and upgrades and Attachment 3.3 Master Services Agreement concerning maintenanc to the user at no additional costs. (Parts and Labor) terms and conditions. The majority of upgrades, including all services to support them, are offered at cost at time of request. Promised uptime and reliability shall be part of the contract and subsequent maintenanc contracts. It will be in a percentage indicating a yearly standard and considered to mean for No Please refer to answer 10-038 above. both system u time and availability for use of its primary mission The system is designed with flexibility to allow for the addition of future interface! Provide the type of system architecture that will allow the incorporation of current and future Alternate Obviously it is impossible to plan for all future technology but the solution proposed doe external systems support future growth and expansion. Please also refer to TAB 3 - Firm Plan of Approach. The system shall have as part of it configuration a back-up system which will allow disaster Hexagon recommends that third party hardware/software such as Avamar be used t( recovery that are compatible with Lee County practices- 30 cycles (roughly 30 days) of VM No support this requirement. This hardware/software is not included as part of the proposal backups on disk and then 3 years retention on tape (once a month). response. Hexagon welcomes further discussion on this requirement and is willing to solicit a quote for Avamar hardware/software if desired The system design will include in its configuration any enhancement need for data While the system is manageable remotely some of the items requested (like centralize( communications, centralized network administration and security, and ability to remotely No Network Administration) are not included. Network related items in general are not trouble shoot or network to clients for maintenance assistance included as part of this response, Hexagon assumes the network is the responsibility of the Coun . The system must be able to configure/re-configure the individual Dispatcher's and Call Yes Feature available. Taker's displays on the fly and according to the needs of the a enc, Provide a system that allows for user-friendly edittupdate table manipulation. The data shou Yes Feature available. not require for it to be re -typed while being insertec Provide complete data dictionary, including all keys, controls, securities, relations, etc. Alternate Hexagon stipulates that this is available, but only after contract award as this is proprietary data. All proposals must provide a statement describing the specifications of servers and softwar that will be used. If the system does not include server(s), then list server specifications and Yes Refer to System Configuration Diagram included as Attachment 4.1. software that are best suited for the system Provide a listing of any hardware or software necessary to accomplish back-ups for the CAC Any Commonly available COTS backup application currently in use by the County shou system to allow for recovery of data in case of catastrophic event and which of the items wit Acknowledge be able to meet this requirement. It is recommended that the backups be stored outside be the County's responsibility to provide. Software must be able to copy open files for of the SAN or replicated to the other site for redundancy. Backup space and software backup. are not included in the proposed solutior All proposals must include a statement showing the cost and specifications of extra servers Hexagon clarifies that per the County's request, hardware is not proposed as part of thi needed for backup, data storage, archive data for analysis, web server, and other purposes No response. Hardware specifications are provided in the system configuration diagram Attachment 4.1. All lookup tables, agency defined values, configuration settings, etc. are to be fully controlle and maintained by the District and/or participating agencies System Administrators, not by Yes The agency will provide system administrators to perform these tasks. the vendor's personnel at a cost for each change The system shall have the ability to perform all operations, dependant on user rights, at any Yes Feature available. client location, including simultaneous identical operations at one tim 10Systems 163 of 186 Com parry: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 10-syst— ver W15/2017 Item Number Systems Response Explanation 10-107 10-108 10-109 10-110 10-111 10-112 10-113 10-114 10-115 10-116 10-117 10-118 10Systems System Administrator tasks associated with maintaining the I/CAD System include, but are not limited to: L Providing off -site data samples for developing and testing conversion workflows, if necessary I Acting as a single point -of -contact for all hardware, software, communications, interfaces, configuration, and general support issues for the installed I/CAD System L Managing system security and access and administering user accounts and passwords I Developing and maintaining system support procedures I Performing routine, daily operational tasks for remedial and preventive hardware maintenance All proposals must include a list of the maintenance activities that require any user L Performing the first level of hardware diagnostics involvement and to what extent. Yes I Acting as liaison with Hexagon software implementation personnel to expedite on -site support and answer complex system, workflow, or configuration questions L Performing routine operational tasks applicable to software maintenance, such as purging system log files, checking database size, and checking the status of interfaces and remote connections I Scheduling and administering backup and recovery of data and configuration files L Changing and customizing screen forms, as requested by Communications Center supervisors or management I Monitoring system loading and providing guidance on the efficient use of hardware and software L Monitoring system operation for peak performance L Performing system data planning I Installing and administering Windows operating system software, utilities, and service All proposals must contain a statement that describes the type(s) of Database Management Hexagon requires SQL Server 2016. We require Enterprise Edition in order to meet thi System(s) used and the one that is best suited for the CAD system proposed. Yes desire system availability. I/CAD is also compatible with Oracle, but requires Enterpris edition and DataGuard. All proposals must contain a statement that describes the limits on the number of user Yes There are no limits. records, street segment records, and response area records that the system can support. The CAD application must use standard Windows printing and not require special print Yes Feature available. functions Database backups must be performed online without DBMS downtime Yes IFeature available. The system provides a means to perform regular (e.g., daily, weekly) backups. Yes Feature available. Backups can be complete or incremental, as determined by the agency. Yes Feature available. Backups include: • Static data files Yes All static data is stored in the database • Working data files Yes All working data is stored in the database. Performing the backup procedure does not degrade system performance. This should be Yes Feature available. based on the hardware requirements and the backup process that is in plac, The system reports on the status of the backup process, if successful or not successful. Yes Feature available. 164 of 186 Com parry: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 10-syste ver W15/2017 Ite Numberm Systems Response Explanation 10-119 10-120 10-121 10-122 10-123 10-124 10-125 10-126 10-127 10-128 10-129 10-130 10-131 10-132 10-133 10-134 10-135 10-136 10-137 10-138 11154M The system includes a method to test the viability of the backup on a regular basis (e.g., Yes Feature available. monthly, quarterly) The system has the capability to roll -back to the date of the last backup. Yes Feature available. The system has the capability of point -in -time recovery. Yes Feature available. The system can replicate data between a minimum of two databases for redundancy. Yes Feature available. The system shall support SQL AlwaysOn. Yes The proposed configuration utilizes SQL AlwaysOn for the production environment. Hot standby database servers have been proposed. However, interface and reporting The system supports backup servers in hot standby mode to take over operation should No servers do not support hot standby mode as some of the interfaces requested do not primary servers fail. support a hot standby configuration. Hexagon welcomes further discussion on this requirement. The system supports VMware failover. Yes Provided that no IP address or machine name changes take place as a result of the failover. Backup servers can be updated and maintained without degradation to primary system Yes This is dependent upon the backup solution implemented. operation. If placed off-line, backup servers come on-line automatically and synchronize without No Not currently supported. degradation to primary system oeration The switch to the backup servers is seamless and transparent to workstation operators. No Some of the servers can failover seamlessly; others, the users will notice. Database failovers are normally seamless when the environment is properly configure The system delivers a system message to selected workstations (e.g., supervisor, No Not currently supported. administrator) that primary operations have been switched to the backup s sten The switch from the backup servers to the primary servers is seamless and transparent to No Some of the servers can failover seamlessly; others, the users will notice. Database workstation operators failovers are normally seamless when the environment is properly configure The system operates on backup servers without degradation to services or response time. Yes The Backup system database servers have been bid to meet the same performance requirements as the primary site The system can be switched between the primary and backup servers on a regular basis an J Yes The primary system and backup system are both designed to operate at the same level operate on either system indefinitely of performance and duration provided that proper maintenance is performec The system shall be highly -configurable by non -technical users, to allow the system to me, most agency technical, operational and functional specifications without major software Yes Hexagon's CAD supports this requirement. development or hard -coding of parameters by technical personne The system shall allow users to configure their operational database files. Yes Hexagon's CAD supports this requirement. The system shall include commonly used pre -defined reports and an ah-hoc report writing Yes Via InSight Reporting. tool. Due to the overly broad nature of this requirement, Hexagon is unable to answer Yes The system database shall process data in real time. This means any parameter change or We are confident that our solution meets the underlying goals of this requirement in tha database change is done while the system is on-line. For instance, if a change is wanted to the I/CAD system is never required to be taken offline to support a parameter or data add a new status code to track a units administrative time spent at "HQ", they can do this Alternate table change, nor is the I/CAD system required to go offline to put the change into effec while the CAD is in -use. The parameter change takes effect upon the next auto However, there are several areas of I/CAD configuration, static data, parameter synchronization or on a manual synchronization request. changes, etc. that require a specific application or service to be re -started. Hexagon welcomes the opportunity to further discuss the County's needs and desires during presentations. Configuration changes shall not require a shutdown or logoff of the system or the CAD clien Hexagon stipulates that some code table changes require an operator to log out. Thes workstations. Alternate are code tables that are loaded into memory at application startup to facilitate quick o eration. Including but not limited to event -types and sub -types Ability to create and maintain support data files used in dispatch center operations, Includin • Street closures Yes Hexagon's CAD supports this requirement. 165 1 Com parry: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Systems Number 10-140 10-141 10-142 10-143 10-144 10-145 10-146 10-147 10-148 10-149 i[raiNY4 10-151 10-152 10-153 10-154 10-155 10-156 10-157 10-158 i[I]S 10-160 10-161 10-162 10-163 10-164 10-165 10-166 I ay rws 16syst— Ver W15/2017 Response Explanation • Special equipment file Yes Hexagon stipulates that this is the I/CAD scratch pad which is only accessible from I/Dis atcher clients. • Telephone number lists Yes Hexagon stipulates that this is the I/CAD scratch pad which is only accessible from I/Dis atcher clients. • Notification lists Yes Hexagon stipulates that this is the I/CAD scratch pad which is only accessible from I/Dis atcher clients. • Personnel file Yes Hexagon's CAD supports this requirement. • Special skills (e.g., foreign language, K-9) Yes Hexagon's CAD supports this requirement. • Public agency referral lists (e.g., Board of Water Supply) Yes Hexagon stipulates that this is the I/CAD scratch pad which is only accessible from /Dis atcher clients. • Special resource files Yes Hexagon stipulates that this is the I/CAD scratch pad which is only accessible from I/Dis atcher clients. • Files necessary for unit recommendation Yes Hexagon's CAD supports this requirement. Ability to create and maintain premise information Yes Hexagon's CAD supports this requirement. Ability to capture and maintain premise information in user defined categories or types. Yes Hexagon's CAD supports this requirement. Ability to define valid date ranges for time limited premise information at a given location (e.g., information valid between <start date> and <end date>) and notify Designated Users No Not currently supported. pending expiration dates Ability to define criteria for automatic premise information purges and activate or deactivate No Not currently supported. this feature Ability to create sign -on messages for subsequent shifts or individuals No Not currently supported. Ability to create and maintain automatic reminders of scheduled activities (radio tests, etc.): • Daily Yes Hexagon's CAD supports this requirement. • Weekly Yes Hexagon's CAD supports this requirement. • Monthly Yes Hexagon's CAD supports this requirement. .Annually Yes Hexagon's CAD supports this requirement. • Muftiple activities or reminder per time slot Yes Hexagon's CAD supports this requirement. Static Table data can be migrated from the current Motorola Premier CAD to the Proposer's Static table data can be migrated, provided that the County can provide the data in a CAD system. Yes delimited file format and a mapping of the data elements to the Hexagon I/CAD database. Command Line The CAD commands shall be customizable by the agency Hexagon's CAD supports this requirement. If the agency desires Hexagon to perform th Yes customizations instead, then depending on the level of effort required, additional servic may be needed at additional cost The CAD command identifiers and the order in which they are entered shall be customizabl Yes Hexagon's CAD supports this requirement. bV the a enc The CAD commands shall allow certain parameters to have default values Yes Hexagon's CAD supports this requirement. Commands entered on the command line are stored and available for reuse. Yes Hexagon's CAD supports this requirement. An operator may use the backspace, delete, or arrow key functions to edit commands from Yes Hexagon's CAD supports this requirement. the command line. Command line processing supports positional command parameters. I Yes Hexagon's CAD supports this requirement. Command line processing supports parameter processing using field identifiers. I Yes Hexagon's CAD supports this requirement. 166 I Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Systems Number 10-168 10-169 10-170 10-171 10-172 10-173 10-174 10-175 10-176 10-177 10-178 10-179 10-180 10-181 10-182 10-183 10-184 10-185 10-186 10-187 10-188 10-189 10-190 10-191 10-192 1—y—t 16sy ti Ver W15/2017 Response Explanation The order of parameters on the command line is customizable by the agency. Yes Hexagon's CAD supports this requirement. Command parameters can be entered in any order. For instance, a command to update the status of unit M1 could be entered in as M1 EN or EN M1 Yes Hexagon's CAD supports this requirement. The command line has "word wrap" capability. Yes Hexagon stipulates that this only exists in the multi -line command line. The system provides a guided command line entry experience that prompts an operator for the next required parameter as command line typing progresseE No Not currently supported. The guided command line entry experience may be toggled ontoff by an operator. No Not currently supported. The system allows unlimited characters when entering remarks from the command line. Yes Hexagon's CAD supports this requirement. The system allows multiple command lines to be active simultaneously. Yes Hexagon's CAD supports this requirement. Security System access can be controlled by an authorized user/system administrator. Yes Hexagon's CAD supports this requirement. Single Sign -on is supported in CAD. Enabling single sign -on is a workstation specif setting, by configuration override. So some workstations could be using it, and others could not be using it. Those that do not use it would simply log in using the user ID and password created for them in the CAD personnel database. System access should be controlled via Active Directory User Groups for permissions. No Authentication requests or traffic arenot sent to an Active Directory server. The CAD system can check if the currently logged -in windows user has an account in the CAD personnel database tables with the same user ID and domain. If yes, then the user can be logged in and given the same permissions associated with the user account in the CAD personnel table. System access can be controlled by workstation. Yes Hexagon's CAD supports this requirement. Agency system administrators are capable of adding and removing devices (e.g., Yes Hexagon's CAD supports this requirement. workstations,printers) to/from the system The system provides the ability to protect Health Insurance Portability and Accountability Ac Yes Hexagon's CAD supports this requirement. (HIPAA) information from view or access on unauthorized monitors or in unsecured reports. The system utilizes MS AD for user login coordination. No See answer in 10-177 above. The system is capable of incorporating multiple MS ADs for user log -in coordination. No See answer in 10-177 above. The system supports multi -level security features. Yes Hexagon stipulates that we assume this to mean command classes and assigning feature access to users via command class. Access to proposed system functions can be granted/restricted by authorized users/system Yes Hexagon's CAD supports this requirement. administrator. Access to proposed system functions can be granted/restricted per workstation. No Not currently supported. Access to proposed system functions can be granted/restricted per individual. Yes Hexagon's CAD supports this requirement. The system logs each login attempt, whether successful or not successful. Yes Hexagon's CAD supports this requirement. orizations can be assigned by individuals and by groups. No Not currently supported. can be associated with multiple security groups. No Not currently supported. d operator accounts are security -/password -protected. Mpasswords Yes Hexagon's CAD supports this requirement. ccounts are required to have a unique ID. Yes Hexagon's CAD supports this requirement. s are stored in encrypted form. Yes Hexagon's CAD supports this requirement. am Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 10-syste Ver W15/2017 Item Number Systems Response Explanation 10-193 10-194 10-195 10-196 10-197 10-198 10-199 10-200 10-201 10-202 10-203 10-204 10-205 10-206 10-207 10-208 10-209 10-210 10-211 10-212 10-213 10-214 100-'215 1Rylem6s The system allows operators to change their own passwords. Yes Hexagon's CAD supports this requirement. The system can require operators to change their passwords at regular intervals, which are Yes Hexagon's CAD supports this requirement. determined by the agency The system is configured with a single operator security table across all modules. Yes Hexagon's CAD supports this requirement. Operator accounts and passwords are synchronized across all system modules. Yes Hexagon's CAD supports this requirement. The system provides single sign on capability across all system vendor applications. Yes Hexagon's CAD supports this requirement. Individual accounts and passwords for the system are controlled by the agency, wher operator IDs, passwords, and security accounts can be created, modified, and deleted by a Yes Hexagon's CAD supports this requirement. authorized agency operator The system must provide a customer -configurable password management system. Yes Hexagon's CAD supports this requirement. Passwords may be configured for expiration, minimum length, character types, and number . System data access rules allow each user agency to define agency -specific security Yes Hexagon's CAD supports this requirement. parameters. The system provides the ability to log all database transactions and track by operator ID, Yes Hexagon's CAD supports this requirement. workstation ID date/time and transaction descri tior There are no default accounts configured in the system. Yes All accounts configured for access to the system in any way will be documented and provided to the customer There are no hidden or "backdoor" accounts configured in the system. Yes All accounts configured for access to the system in any way will be documented and provided to the customer Each vendor access account must be disclosed to the agency. Yes All accounts configured for access to the system in any way will be documented and provided to the customer Security for each account has a lock -out provision that will lock -out access to an account Yes This is dependent upon the AD configurafion. after an agency -defined number of unsuccessful log -in attempt An account that has been locked -out may be reset by an operator with the appropriate Yes This is dependent upon the AD configurafion. security setting The system provides a configurable screen saver with password protection for desktop and Yes This is dependent upon the AD configurafion. This is not a recommended practce wireless devices The individual agency maintains all security aspects of the system, without reliance on the Yes Hexagon's CAD supports this requirement. vendor to perform security functons The system supports remote maintenance by the vendor. Yes Hexagon's CAD supports this requirement. The system supports remote maintenance by the County. Yes Hexagon's CAD supports this requirement. The application is compatible with anti -virus software for workstatons and servers. Yes Hexagon stipulates that compliance with our Anti -Virus exclusions is not optonal. The workstation software operates with ant -virus software without conflict or performance degradation. Specifications should be provided for any exclusions for AN for both Yes Hexagon stpulates that compliance with our Anti -Virus exclusions is not optional. Workstations and Servers so that these can be accomodated for The operator is prevented from logging off when the operator has sole responsibility for Yes Hexagon's CAD supports this requirement. events or units that will not be handled on to off. A system message will be generate An operator (#2) can log in to an actve workstation without requiring the current operator (# to perform the log -off function, the system will automatically log -off the current operator (#1) Yes Hexagon's CAD supports this requirement. The system does not require events or resources to be transferred to a different dispatcher during the to in process (e.g., a change operator function The system design will include any enhancements needed for security of any internet acces No Network configuration or modifications are not included in this response. which may include firewalls VPN's inscription, and authentication The system must be able to assign access and capabilites according to user profiles No lNot currently supported. IM Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure IMs t— ver W15/2011 Item Number Systems Response Explanation 10-217 10-218 10-219 10-220 10-221 10-222 10-223 10-224 10-225 10-226 10-227 10Syste— Provide a system with all data owned and accessible at an appropriate level by the clien such data to include but be not limited to "live" CAD data, CAD data for completed incidents Yes All data is maintained in a SQL Database. Proprietary tools are not required to access (history), support data such as tables, matrixes, conduits etc. without having to purchase said data. additional software licenses If the proposal does not include a Firewall, all proposals must provide a statement describin at least two types (with specifications) of Firewalls (hardware, software, and/or combination) Alternate Hexagon systems do not require specific Firewall makes or models. that are best suited for the CAD system The CAD system must allow the administrators to designate special privileges to an inclividu yes Hexagon's CAD supports this requirement. only without the need of giving that user full access to the s sten The system shall have the ability to limit and allow operational capabilities by the physical No Not currently supported. location ofthe client The proposed system shall allow users to change their own password at any time. Yes Hexagon's CAD supports this requirement. The system must allow the System Administrator to generate log reports of Yes Hexagon's CAD supports this requirement. unauthorized/failed log in attempts into the s sterr The system must allow Dispatch Supervisors and System Administrators to log off a user. No Not currently supported. The system must allow the administrators to designate special privileges to an individual onl V yes Hexagon's CAD supports this requirement. without the need of giving that user full access to the s sten e Hexagon CAD password system allows for the following County definedsettings On the personnel record, number of days the password is valid. Via parameters, EncryptionType, Algorithm name for the symmetric encryption used for some passwor fields. See MSDN documentation on CryptoConfig for a complete list of valid names. PasswordFtrst, I n the parameter's Value field, enter a generic password to be used when creating new user accounts. Then, when a new user account is created in the Personnel dialog box, this password should be entered in the Password field. After the user signs on to the application forthe first time using this temporary password, the application will inform the user to change their password to a password of their choice. The persl record will automatically be updated with the user's new password. The Res The system shall provide a configurable password management system. Passwords must b Yes Password command returns a user's password to the default, generic value entered for configured for expiration, minimum length, character types and numbers. Password First. I PasswordHashld, Default Hash used on passwords. 1 - MDS, 2 - SHA512 I PasswordHistory, Determines the number of unique new passwords that have to be associated with a user account before an old password can be reused. PasswordMinAge, Minimum number of days before the password can be changed. PasswordMinAlpha, Minimum number of characters from : A -Z, a -z PasswordMinDigits. Minimum number of characters from : 0- 9 1 PasswordMin Length Minimum # of characters required for a password. PassworclM in Lower. Minimum number of characters from : a -z PasswordMinSpecial, Minimum number of characters from : ' — ! @ # $ % A &' () _+ _ { } I [ I \ : " ' ' I ? , . / space I PasswordMinUpper, Minimum number of characters from: A -Z Disaster Recovery Site The system supports regular disaster recovery failover tests, switching operations from th primary to the disaster recovery site. This would need to be based on the DR Environment The proposed solution will support users being at the live or DR location with servers Yes that Lee County has implemented. In most cases to do a failover test requires the being live at either location. roduction\livesystem to be taken down to fully validate. 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item Systems Number 10-228 10-229 10-230 10-231 10-232 10-233 10-234 10-235 10-236 10-237 10-238 10-239 10-240 10-242 10-243 10-244 10-245 10-246 10-247 10System 16sy ti Ver W15/2017 Response Explanation The disaster recovery system can be operated and maintained from a remote location. Yes Remote access to all systems is available if the network is properly configured. The disaster recovery system functions as a hot standby disaster recovery site. No Hexagon has proposed a cold backup disaster recovery site. Please also refer to Attachment 4.2 System Architecture and Stage and Install Assumptions Switching operations to the disaster recovery facility can be performed by an authorized usE r. Yes Hexagon's CAD supports this requirement. Switching operations from the disaster recovery facility to the primary facility can be Yes Hexagon's CAD supports this requirement. performed by an authorized user The system at the disaster recovery facility can be switched to run as the primary CA[ The proposed solution will support users being at the live or DR location with servers system provider, with the workstations at the failover facility and primary facility operating a. Yes being live at either location. live CAD workstations The workstations at the disaster recovery facility can be configured to operate on the primar Yes The proposed solution will support users being at the live or DR location with servers system as additional workstations being live at either location The disaster recovery failover does not require system shutdown and restart. Yes While some aspects of the failover may require Administrator intervention a shutdown o restart is not required Hexagon stipulates that the network connectivity available between the primary site an Events active priorto the disaster recovery failover are available as active events after the Yes the DR site must be sufficient to support a synchronous replica of the I/CAD database v failover activation with no loss of data. AlwaysOn technology as stipulated by Microsoft for successful use of a synchronous replica. Event numbering can continue in sequence after the failover. Yes Provided a synchronous replica is available at the DR site as proposed. Event numbering can be manually set after the failover by an authorized user. Yes Supported if desired, but this is not required. Switching operations from the disaster recovery site to the primary site does not require a Yes While some aspects of the failover may require Administrator intervention a shutdown o system shutdown and restart restart is not required The restoration process in moving operations from the disaster recovery to the primary site No This process is an online process since the DB server at the DR location will need to can be performed off-line. synchronize with the primary site DB servei If connection is lost to the disaster recovery site, the system sends a notification message tc Hexagon recommends a third party such as SolarWinds be used to meet thi! designated positions and send an email to designated recipients. No requirement. SolarWinds software is not included as part of this response. Hexagon is wiling to solicit a quote for SolarWinds software if desired Identify how primary and back-up site shall maintain current data for the potential fail ove from primary to secondary system to be achieved while transparent to users. May be similar Yes This is obtained via SQL Server AlwaysOn and a DR synchronous replica. to transaction logs or other method Provide fail over procedures for the System Administrator to accomplish activating the bacl up CAD system from the primary system. Identify all actions necessary to maintain data Yes Hexagon stipulates that this information will be provided after contract award. updates between primary and back-up servers which include any actions necessary to maintain similar configurations between the primary and back-up system! The system must have the capability to operate at full capacity at all locations including I Provided that the County has sufficient network capacity including high bandwidth and satellite and redundant locations in the event of a disaster which may make the primary site Yes low latency connectivity to all locations. unavailable Data Warehouse Capability The system maintains a separate external database outside the CAD network, secure, but Yes This is supported. Hexagon assumes this is met by the Archive database server. accessible to CAD users and authorized non -CAD external user! The system supports writing CAD record data to the Data warehouse automatically, real - No The Archive database is at least 5 minutes behind the production CAD system. time, as entered in the CAD system The system provides a method to write the final version of the CAD record data to the Data Yes Hexagon's CAD supports this requirement. warehouse on event closure 0 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure to-syste Ver W15/2017 Item Number Systems Response Explanation 10-248 10-249 10-250 10-251 10-252 10-253 10-254 10-255 10-256 10-257 10-258 10-259 10-260 10-261 10System The Data warehouse stores all data associated with the event record (e.g., event, unit, Yes Hexagon's CAD supports this requirement. remarks). The system supports Data warehouse security that allows view -only rights to the data. Yes Hexagon's CAD supports this requirement. All external CAD data inquiries can be directed to the Data warehouse. Yes Hexagon's CAD supports this requirement. The Data warehouse platform and storage utilize commercial off -tile -shelf (COTS) Yes The platform is SQL Server and does not utilize any Proprietary solutions. applications. The Data warehouse platform and storage utilize Microsoft SQL Server as the database Yes The platform is SQL Server and does not utilize any Proprietary solutions. management system. The Data warehouse supports automatic requests for data from external, previously- Yes Hexagon's CAD supports this requirement. approved applications The Data warehouse supports record- and field -based security to restrict viewing of record and fields based on the assigned role, discipline, and jurisdiction at login (e.g., the Data warehouse security features allow data related to a Law Enforcement jurisdiction to be No This is not currently available. accessible only to operators that log in to the Data warehouse with that role and department clearly defined). Public Access Portal The system can export data to an external database used as a publicly accessible web- No Hexagon stipulates that this is possible using a multitude of technologies, but Hexagon based portal. has not proposed any such services or technology. Data exported to the public access facility is at intervals determined by the agency. No Hexagon stipulates that this is possible using a multitude of technologies, but Hexagon has not proposed any such services or technology. The data set exported to the public access facility is determined by the agency. No Hexagon stipulates that this is possible using a multitude of technologies, but Hexagon has not proposed any such services or technology. Web -based Interface users can: -View the current activity and status of all units. -View information about pending and active events. -View events and units on an interactive map. - Retrieve historical information about individual units and events. For example, you can get a list of all the activities of a particular unit for the past two weeks, or find how many traffic accidents were reported during a given month. - Create an event, which will initiate a Call for Service if it is appropriate. The system supports a web -based interface to CAD. Yes -Search foroperational information, such as which personnel are on duty, what special equipment is in their vehicles, and any special training or skills they have, such as being bilingual- - Send messages and pages to any user on the system, including mobile units. -Change personnel lineups. - Place a unit in or out of service. -Manage facility diversions. - View the latest status of a facility. - Display units that are transporting to a facility entrance. - View the history of a diversion for a service type associated with an facility entrance. The web -based CAD workstation can be a full function CAD workstation performing call Alternate Hexagon has proposed our I/NetViewer product to support this requirement. See above takingand dispatching functions171, 186 Company: Intergraph Corporation d/b/a Hexagon Safety 8lnfraslructure to-syste ver W15/2017 Item Number Systems Response Explanation 10-262 10-263 10-264 10-265 10-266 10-267 10-268 10-269 10-270 10-271 10-272 10-273 10-274 10-275 10-276 10-277 10-278 10-279 10-280 10-281 10-282 10-283 10-284 10-285 10-286 10-287 10-288 10-289 10Syste— The web -based CAD solution supports full functionality on any mobile device (e.g., phone, tablet). No I/NetViewer requires a laptop/workstation. The web -based CAD workstation can perform inquiry and reporting functions. Yes Hexagon has proposed our I/NetViewer product to support this requirement. See above Web -based access to CAD can be restricted to Inquiry only. Yes Hexagon has proposed our I/NetViewer product to support this requirement. See above Web -based access to CAD can be restricted to View only. Yes Hexagon has proposed our I/NetViewer product to support this requirement. See above Web -based access can be restricted to data warehouse access only. No Web -based access to CAD can be restricted to only view event and status monitors. Yes Hexagon has proposed our I/NetViewer product to support this requirement. See above The web -based interface utilizes user -associated security as network -based clients. Yes Hexagon has proposed our I/NetViewer product to support this requirement. See above Network The proposed system meets Lee County and State of Florida security requirements. No Without access to the full text of the County and State requirements, Hexagon cannot answer yes to this requirement. Hexagon stipulates that AD management pertains only to the Windows operating syste The proposed system utilizes MS AD management tools. Alternate and associated group policies. The I/CAD applications do not interface or interact with AD. Hexagon stipulates that AD management pertains only to the Windows operating syste The proposed system interfaces with local agency MS AD domain. Alternate and associated group policies. The I/CAD applications do not interface or interact with AD. The proposed system is firewalled from external access. Yes The County must provide the firewalls. The proposed system is IP-based. Yes The system utilizes TCP/IP and UDP Date and Time System time can be displayed as a 24hour format. Yes Hexagon's CAD supports this requirement. System time will auto -adjust for Daylight Saving Time (DST) without impacting system operations. Yes Hexagon's CAD supports this requirement. The date is displayed as YYYYMMDD. Yes Hexagon's CAD supports this requirement. The time is displayed as HH:MM:SS. Yes Hexagon's CAD supports this requirement. The date display is configurable by agency. Yes Hexagon's CAD supports this requirement. The time display is configurable. Yes Hexagon's CAD supports this requirement. All times are displayed as local time. Yes Hexagon's CAD supports this requirement. The system shall use and display the same date and time formats across all applications. Yes Hexagon's CAD supports this requirement. The system shall be able to time sync with an NTP time server or other device such as a Netclock Yes Hexagon's CAD supports this requirement. The system shall issue all timestamps from the primary CAD server No Time stamps are all generated by the client, with the exception of mobile and web devices. The system shall use and display the same date and time formats across all applications. Yes Hexagon's CAD supports this requirement. The following time stamps are recorded and associated with an event, at a minimum • Time call received (ring time) Yes Hexagon's CAD supports this requirement. • Time call received at the PSAP Yes Hexagon's CAD supports this requirement. f 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure to-syst— ver: any/zoi/ Item Number Systems Response Explanation 10-290 10-291 10-292 10-293 10-294 10-295 10-296 10-297 10-298 10-299 10-300 10-301 10302 10303 10304 10-305 10306 10307 10308 10-309 10310 10-311 10312 • Time call answered at the PSAP Yes Hexagon's CAD supports this requirement. • Start of event entry form Yes Hexagon's CAD supports this requirement. • Addition of an event to the pending list Yes Hexagon's CAD supports this requirement. • Transfer of the call Yes Hexagon's CAD supports this requirement. • First view of event by dispatcher Yes Hexagon's CAD supports this requirement. • Digital voice announcement start time No Not currently supported. • Unit dispatch time Yes Hexagon's CAD supports this requirement. • Unit status changes Yes Hexagon's CAD supports this requirement. • Time of patient contact Yes Hexagon's CAD supports this requirement. • Advanced Life Support (ALS) on -scene Yes Hexagon's CAD supports this requirement. • Water on the fire Yes Hexagon's CAD supports this requirement. • Fire under control Yes Hexagon's CAD supports this requirement. • Event under control Yes Hexagon's CAD supports this requirement. • Time event closed Yes Hexagon's CAD supports this requirement. • Each time a change is made to the event Yes Hexagon's CAD supports this requirement. • Time that call entered into automated dispatching program No Not currently supported. • Event dispatch time Yes Hexagon's CAD supports this requirement. • Event status charges Yes Hexagon's CAD supports this requirement. • Each time a remark is added to the event Yes Hexagon's CAD supports this requirement. • Each time a remark is added to the unit Yes I Hexagon's CAD supports this requirement. • Each time a timer is activated Yes Hexagon's CAD supports this requirement. • Each time a timer is reset Yes Hexagon's CAD supports this requirement. • Premises information viewed Yes Hexagon's CAD supports this requirement. 10Systems 173 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 11-Training ver: 8/15/2017 Item Number Training Response Explanation 11-001 11-002 11-003 11-004 11-005 11-006 11-007 11-008 11-009 11-010 11-011 11-012 11-013 11-014 11-015 11-Training The offering should provide asynchronous (self -directed, self -paced) computer based training on system features and functionality tailored for: a Dispatch System Administrator No Not currently proposed .Dispatch System Manager/Supervisor No Not currently proposed Hexagon will build an online course based on Lee County's system and the I/Dispatcher software .Call Takers Yes (proposed for both dispatching and calltaking requirements). The course will be provided via a Learning Management System Hexagon will build an online course based on Lee .Dispatchers Yes County's system and the I/Dispatcher software. The course will be provided via a Learning Management System .Database Manager No Not currently proposed .Technical Support Staff No Not currently proposed .Mobile Administrators No Not currently proposed .Mobile Manager/Supervisors No Not currently proposed Hexagon will build an online course based on Lee County's system, the Mobile for Public Safety mobile .Mobile Users Yes software, and the Mobile Responder software (optional). The course will be provided via a Learning Management System The offering shall provide 3 days of onsite vendor instructor -facilitated training tailored for: Training is provided; see course descriptions and a Dispatch System Administrator Yes duration provided in the Proposal Training section (Attachment 3.2) Training is provided, see course descriptions and duration provided in the Proposal Training section .Dispatch System Manager/Supervisor Yes (Attachment 3.2). Training is not tailored for system managers and supervisors. Hexagon assumes system managers and supervisors will attend dispatcher training. Training is provided, see course descriptions and .Call Takers Yes duration provided in the Proposal Training section (Attachment 3.2) Training is provided, see course descriptions and .Dispatchers Yes duration provided in the Proposal Training section (Attachment 3.2) 174 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure >> -Training ver: 8/1512017 Item Number Training Response Explanation 11-016 11-017 11-018 11-019 11-020 11-021 11-022 11-023 11-024 11-025 11-026 11-027 11-Training I/CAD uses Microsoft SQL Server 2016. Hexagon does not provide database administrator training. Database .Database Manager No administrator training for Microsoft SQL Server is available from multiple sources, including Microsoft itself. Training is provided, see course descriptions and •Technical Support Staff Yes duration provided in the Proposal Training section Attachment 3.2 Training is provided; see course descriptions and .Mobile Administrators Yes duration provided in the Proposal Training section Attachment 3.2 Training is not tailored for managers and supervisors. *Mobile Manager/Supervisors No Hexagon assumes managers and supervisors will attend Mobile Train -the -Trainer course. .Mobile Users No Hexagon has bid Mobile Train -the -Trainer. The offering shall provide 3 days of onsite vendor instructor -facilitated train the trainer training tailored for: Dispatch system administrator training is provided *Dispatch System Administrator No directly to system administrators and is not provided as a train -the -trainer course. Training is provided, see course descriptions and duration provided in the Proposal Training section •Dispatch System Manager/Supervisor Yes (Attachment 3.2). Training is not tailored for system managers and supervisors. Hexagon assumes system managers and supervisors will attend dispatcher training. Training is provided, see course descriptions and .Call Takers Yes duration provided in the Proposal Training section Attachment 3.2 Training is provided, see course descriptions and .Dispatchers Yes duration provided in the Proposal Training section Attachment 3.2 I/CAD uses Microsoft SQL Server 2016. Hexagon does not provide database administrator training. Database .Database Manager No administrator training for Microsoft SQL Server is available from multiple sources, including Microsoft tself. Technical support staff training is directly to system •Technical Support Staff No administrators and is not provided as a train -the -trainer course. 175 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure >> -Training ver: 8n512017 Item Number Training Response Explanation 11-028 11-029 11-030 11-031 11-032 11-033 Mobile administrator training is provided directly to *Mobile Administrators No system administrators and is not provided as a train -the - trainer course. Training is not tailored for mobile managers and •Mobile Manager/Supervisors Yes supervisors. Hexagon assumes mobile managers and supervisors will attend mobile user train -the -trainer courses. Training is provided, see course descriptions and .Mobile Users Yes duration provided in the Proposal Training section (Attachment 3.2) The offering should provide training on systems and features tailored for the various user Training is provided, see course descriptions and with specific operational requirements at a vendor determined location. groups p p G Yes duration provided in the Proposal Training section (Attachment 3.2) Training Manuals and Agendas will be provided with the The offering shall make available training documentation templates and curriculum for each courses; however, these are not customized for specific Yes user groups. Please refer to the information on Training user group. in Tab 3 - Firm Plan of Approach and Attachment 3.2 Training Course Descriptions. The offering should provide four user registrations for vendor user conference as part of on- Hexagon has not included these at this time but going support and maintenance agreements.. No Hexagon welcomes further discussion on this equirement. 11-Training 176 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item project Management Number 12-001 12-002 12-003 12-004 12-005 12-006 12-007 12-0011 12-009 12-Project Ma 12-Project Management Response Ver: 8/15/2017 Explanation The offering shall provide and maintain an agreed upon Project Management Plan including Hexagon's Project Management Office (PMO) follows project charter, scope, schedule, cost, quality, human resource, communication, risk, and Yes the standard project management established by issue mana ement within 60 days of contract signing. Hexagon for this type of project delivery. The offering shall ensure that all data, including but not limited to, references, documents, pictures, recordings and spreadsheets whole or in part prepared for Lee County and any The Hexagon delivery team will adhere to all security data compiled during the course of this project are not removed, copied, published or Yes and data access requirements formally established between Hexagon and Lee County otherwise distributed without written authorization from Lee County. The offering shall provide Project Management onsite services that includes a kickoff meeting, project management plan acceptance, and at least one quarterly session until Yes The Hexagon Project Manager will be on site for the s stem ao-live. listed tasks. The offering shall provide a monthly Project Management executive summary outlining The Hexagon Project Manager will provide a status milestone achievements, issues, risks, and recommendations. Yes report that will have an executivesummarythatoutlines the status of the project The Hexagon Project Manager will supply a status The offering shall provide and maintain communication matrix regarding project status, report to the customer that will provide all the necessary escalation procedures, change requests and all facets related to the communication between Yes information to the customer. This includes risk register, the vendor and the County. risk management/mitigation, change request .management, and project status Hexagon's PMO Executive Director hires highly qualified project managers to manage all projects in the United States. Project Manager assignments are based The offering should offer Lee County input on the vendor's choice of Project Manager. The on when a project starts, current commitments to active vendor will make an attempt to grant any reasonable request on assignment. No projects and availability of PMO resources. Hexagon's PMO avoids disruptions of active and committed projects, new projects will be staffed with a qualified Project Manager, but Hexagon will not entertain customers selecting Project Managers on demand. The Hexagon Project Manager will provide the County when possible a 30 day notice of any vendor personnel The offering shall provide County no less than 30 day notice, when possible, on any Yes change. There are certain situations where this is not assignment change of key vendor personnel for this project. possible and when these situations occur, the Hexagon Project Manager will notify the County's Project Manager as soon as possible. The offering shall provide an onsite system and operational review and assessment report The schedule will reflect a project kickoff meeting within 30 days of contract signing. Yes (which will include an assessment and operational review) within 30 days of the contract signing The offering shall follow an industry standard project management methodology in managing The Hexagon PM follows Hexagon established project the ro'ect. Yes methodologies, which are aligned with industry standards Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Item project Management Number 12-010 12-011 12-012 12-013 12-014 12-015 12-016 12-Project Ver: 8/15/2017 Management Response Explanation The Hexagon Project Manager will supply a status The offering shall track project management detailed milestones in a format acceptable to report to the customer that will provide all the necessary the County. Yes information to the customer. This includes risk management, change request management, and roject status The offering shall produce documentation in a format approved by Lee County during all Hexagon has already established project documentation phases of the project. No templates that are aligned with the Hexagon delivery methodology and Industry standards. The offering shall include the expected level of effort required by County Subject Matter The Hexagon Project Manager will include tasks related Experts (SME's) in the project plan to be delivered. Higher consideration will be given to Yes to the County in the project schedule. This will indicate lower reliance on County SME's as they are engaged in maintaining the County's business the type of resource needed and the amount of effort on a daily basis. required to accomplish this task. The offering shall incorporate vendor costs, all other project costs and a cost comparison to No Hexagon does not provide cost breakdown for firm fixed similar initiatives at other City or County entities into the budgetary estimate to be delivered. price contracts The Hexagon Project Manager and the County Project The offering shall conduct recurring status meetings with the project stakeholders and the Yes manager will determine the necessary recurring meeting project team. schedule for the project and ensure that all necessary parties from each side are present and accounted for. The offering shall provide a solution that does not require proprietary software to manage the No Hexagon's Intergraph software is proprietary and County's business or allow transfer of software ownership to the County at no charge. Hexagon will not give the County ownership of our SW. The offering shall ensure that all data, including but not limited to, references, documents, pictures, recordings and spreadsheets whole or in part prepared for Lee County and any Hexagon agrees that data will not be removed, copied, data compiled during the course of this project are not removed, copied, published or Yes published or fro wise distributed without written authorization from Lee County. otherwise distributed without written authorization from Lee County. 12-Project Management 178 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 13suppol ver: 8/15/2017 Item Support & Maintenance p p Number pp Response Explanation 13-001 13-002 13-003 13-004 13-005 13-006 13-007 13-008 13-009 13-Support Maintenance Agree men ts/Con tracts The offering shall include on the pricing pages the costs of maintenance over a three and five Hexagon has provided the costs of maintenance over a year period Yes three and five year period as part of the pricing response. Please refer to the Master Services Agreement included The offering shall provide a list of items and period of coverage for all items under warranty. Yes as part of this proposal response as Attachment 3.3 with TAB 3 - Firm Plan of Approach. Hexagon has offered a one time system discount as The offering shall include any discounts for purchasing multi -year maintenance options Alternate part of the price proposal, which includes a discount on Extended Warranty, but not out years of maintenance. The offering shall provide a copy of standard maintenance contract or an explanation of what Please refer to the Master Services Agreement included is included in it. If there are limits to the number of or version jumps of software upgrades Yes as part of this proposal response as Attachment 3.3 with covered under maintenance these should be pointed out. TAB 3 - Firm Plan of Approach. Documentation & Knowled ebase Hexagon respectfully clarifies that all documentation provided will be for the COTS software, and not customized based on any configuration changes the County may implement. Editable versions of all documentation (with the exception of product help files) will be provided so the County may edit the content as The offering shall provide and maintain current and accurate product documentation. Errata they see fit. Hexagon respectfully proposes to provide sheets along with the documentation are acceptable as long as there is a clear cross Yes only electronic copies of documentation, which the reference shown between the correction and document. County may print if so desired. Hexagon respectfully clarifies that all software, content, and documentation including tables, layouts, queries, stored procedures, data dictionaries, and XML schema, developed by Hexagon and provided to the County by Hexagon shall be owned by Hexagon Hexagon cannot identify specific individuals of every agency using the system. However, Hexagon has The offering should provide a list of users on a similar system as being proposed for reference Alternate provided reference surveys with points of contact and and on site visits. an additional reference chart as part of TAB 6 - Required Forms identifying customers which are currently on maintenance. The offering shall make available all documentation, including manuals, procedures, and Hexagon respectfully proposes to provide only training material in a standard digital format (PDF preferred) with permission to print or Yes electronic copies of documentation, which the County distribute as needed for training or other legitimate needs. may print if so desired. Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 13suppol ver: 8/15/2017 Item Support & Maintenance p p Number pp Response Explanation 13-010 13-011 13-012 13-013 13-014 13-015 13-016 13-017 13-018 13-019 Hexagon makes all new software release The offering shall have a mechanism in place to automatically notify Lee County of new announcements via our website. Customers on a valid version releases, including patch sets, and availability to the release notes as soon as they Alternate maintenance agreement have free access to the release are published notes for all released software on maintenance. Notifications are not automatic. Hexagon provides access to WebEx topical discussions The offering shall provide a web -based knowledgebase to allow the Lee County support staff free -of -charge to customers via our Customer website. the ability to find articles to assist in the running and maintaining the system. This should Yes Additionally, Hexagon provides customers with access include a known problem list with work arounds and estimated dates of patch availability to an online support knowledge base with keyword search capability to facilitate a search of the knowledge base to facilitate problem resolution. Support & Issue Management 24/7/365 support is offered. The Customer can call the The offering shall provide a 24/7/365 toll -free non -machine phone number to report any after-hours support number provided, leave a message Issues with the system. Alternate and the call will be returned within 30 minutes time. The Hexagon Support Manager may also be contacted directly. Hexagon clarifies that issues are reported through The offering shall provide an email address to report any issues with the system. Alternate Hexagon's customer support website, or via phone call to the Hexagon Help Desk, not via email. The offering shall provide a web -based interface to report any issues with the system and to check the status of existingissues previouslyreported with the system. Yes Hexagon agrees to meet this requirement. The offering shall provide a primary support contact. The County will have input on the vendor's choice of this primary support contact. The vendor will make an attempt to grant any Alternate Hexagon clarifies that the primary support contact is the reasonable request on assignment. Hexagon Support Manager. The offering shall provide County no less than 30 day notice, when possible, on any assi nment chance of keyvendor personnel related to the support of this project. Yes Hexagon agrees to meet this requirement. The offering shall provide a 24/7/365 escalation process for issues that require urgency for Hexagon's Support manager is available around the resolution. Yes clock to escalate issues to the appropriate contact User support for the system must be available, with critical support available on a 24/7/365 24/7/365 support is offered. The Customer can call the basis. Alternate after-hours support number provided, leave a message and the call will be returned within 30 minutes time. 13-020 Pre -Acceptance Project Support & Issue Management 13-Support 180 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety R Infrastructure 13support ver 8/15/2017 Item Support & Maintenance P P Number pp Response Explanation 13-021 13-022 13-023 13-024 13-025 13-026 13-027 13-028 13-029 13-030 13-Support The offering shall provide a primary a 24/7/365 non -machine phone number to report any 24/7/365 support is offered. The Customer can call the Issues with the system. Alternate after-hours support number provided, leave a message and the call will be returned within 30 minutes time. Customers shall report any issues through the Siebel The offering shall provide a primary email address to report any issues with the system. Alternate customer portal by filing a support request. Support Manager's email will be provided for alternate access. The offering shall provide a web -based interface to report any issues with the system and to check the status of existingissues previouslyreported with the system. Yes Hexagon agrees to meet this requirement. The offering shall provide a primary support contact prior to acceptance. The County will have input on the vendor's choice of this primary support contact. The vendor will make an attempt Yes Primary support contact shall be the Support Manager to grant any reasonable request on assignment. The offering shall provide County no less than 30 day notice, when possible, on any assignment change of key vendor personnel related to the support of this project. Yes Hexagon agrees to meet this requirement. The offering shall provide an escalation process that includes 24/7/365 accessible contacts Yes Hexagon's Support manager is available around the for issues that require urgency for resolution. clock to escalate issues to the appropriate contact The offering shall provide voice contact within one hour of voice notification to support center when total system failure occurs. Total System Failure occurs when the system is not functioning and there is no workaround. Examples of this are the primary server is down or Customer issues are addressed by priority level and when the workflow of the entire center is not functioning. This level is meant to represent a Yes targeted resolution times will be provided to the customer. major issue that results in an unusable system, subsystem, product or critical features. No work arounds or immediate solutions are available The offering shall provide voice contact within three hours of initial voice notification to support center when Critical Failure occurs. Critical process failure occurs when a crucial element in the system that does not prohibit continuance of basic operations is not functioning and there Yes Hexagon agrees to meet this requirement. is not a suitable work around. This applies to intermittent problems only if they occur 50% of the time the function is used The offering shall provide voice contact within four business hours of notification to support center when non -critical failure occurs. A non -critical part or component fails or is not functioning. The system is useable for its intended purpose or a reasonable workaround is No See matrix in TAB 3 - Firm Plan of Approach for issue found. These are minor issues that do not prevent the use of the system, subsystem, products response and resolution targets. or critical features. The offering shall provide voice contact within two business days of notification to support center when an inconvenience is reported. Inconvenience is a minor disruption in how the See matrix in TAB 3 - Firm Plan of Approach for issue tasks are performed, but do not stop the workflow. These are non -process issues such as Alternate response and resolution targets. We will respond cosmetic, usage questions, and documentation clarification. System upgrade requests fall within that response time however the response may be provided through the Help Desk Siebel platform. under this level. Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 13suppol ver: 8/15/2017 Item Support & Maintenance p p Number pp Response Explanation 13-031 The offering shall make necessary number, level and type of staff available for the go -live yes Hexagon agrees to meet this requirement. date so to adequately support all aspects of the system. 13-Support 182 of 186 Company: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure 14-Coin Deny ver_ W15/2017 Item Number Company 14-001 14-002 14-003 14-004 Response Explanation Hexagon confirms that a minimum 10 CAD systems At the time of proposal submittal, Respondents must have a minimum often CAD systems are installed and currently operationanit l, with at least one installed and currently operational, with at least one CAD system that is currently operating on CAD system currently operating on the same version the same version and platform as the system proposed. Respondents must have a multi- Yes and platform as proposed. The CAD system is designed jurisdictional, multi -discipline CAD project comparable in size, or larger, to the proposed to be multi -jurisdictional and multi -discipline. Please also system. refer to TAB 6 - Required Forms for Form 3 Reference Surveys and additional references. Hexagon agrees that personnel ultimately assigned to the project shall have the experience necessaryto perform services as proposed for this RFP and shall complete a background check. Hexagon has nominated a "tentative" Project Team that represents the skills and experience of personnel likely to be assigned to the County's Project. However, Hexagon has numerous projects in various stages of completion, as well as numerous proposals in various stages of evaluation. Respondents must have sufficient, competent, and skilled staff, with experience in performing Because the timeline associated with project evaluation, the services described in this RFP, who are able to pass a mandatory criminal background negotiation, and the schedule is subject to many check before they are allowed enter onto the premises. If the County determines in good faith Yes variables, it is not possible to firmly identify individuals that any such individual is not so qualified, the successful Respondent shall substitute such who will be available should Hexagon be selected for the County's Project. However, Hexagon commits to individual with a qualified replacement subject to the County's review and approval. providing an experienced, professional Project Team that will ensure the County's Project success. At the time of award, Hexagon will select the appropriate Project Team based on availability, experience, and nature ofthe requirements. Once in place, Hexagon agrees key personnel will remain assigned to the County's Project through completion unless unavailable due to death, illness, disability, or termination of the employment relationship. Respondents must have installed, active client sites configured in a virtual environment for Hexagon confirms that it has installed, active clients system servers, databases, data storage, and interfaces. Respondents must provide a list of sites configured in a virtual environment for system virtual environment client sites, with contact information and a description of the Yes servers, databases, data storage, and interfaces. implementation. Please refer to TAB 6 -Required Forms, Form 3 Reference Surveys and the Additional References chart. Respondents must have active client sites in a multi -agency, multi -jurisdictional and multi- Hexagon confirms that it has active client sites in a multi- discipline (fire, EMS) environment, with the ability to share information based on agency, role agency, multi -jurisdictional and multi -discipline (fire, and discipline, and, with a distributed system administration capability across the agencies. Yes EMS) environment, with the ability to share information Respondents must provide a list of client sites that meet the above criteria, with contact based on agency, role and discipline. Please refer to TAB 6 - Required Forms, Form 3 Reference Surveys information and a description of the implementation. and the Additional References chart. 14-Company 183 of Form ]a —Proposal Form (not applicable for CCNA solicitations) LEE COUNTY SOUTHWEST FLORIDA Lee County Procurement Management PROPOSALFORM Company Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Solicitation # RFP180081LKD soucnauon Name: uom user Aiaea uis atcn rce iacemeni ana Hssociaiea inierraces Having care u y examine a erms an on i ions , and the "uetailed Specifications", all of which are contained herein, propose to furnish the following, which meet these specifications. From Notice to Proceed or Purchase Order date, whichever applies, 335 calendar days to substantial completion, 30 calendar days to final completion (estimated timeline 365 total calendar days.) Proposal to be based on this timeline. The county reserves the right to negotiate with awarded vendor. Draw Schedule based on the following: 1 Project Management Plan Acceptance: 80% of line item #1 2 Installation: 80% of line item #2 3 Training: 80% of line item #3 4 Go -Live: 80% of line item # 4 5 Final Acceptance: 20% of line item 1-4. 100% of line item #5 For evaluation purposes "To Be Determined" or "ranges of price" are not acceptable entries. If a firm rice is not provided zero POITITS will De earned for this evaluation category. Item # Description Unit o Measure Total Cost 1 Project Management Plan Acceptance Lump Sum $ Included in 5a 2 Installation (tabs 2-11) Lump Sum $ Included in 5a 3 Training and Support (tabs 12 & 14) Lump Sum $ Included in 5a 4 Go -Live Lump Sum $ Included in 5a 5 Final Acceptance Lump Sum $ Included in 5a 5a Project Services Lump Sum $ $1 353 257 5b Project Software Lump Sum $ $1,164,401 6 Sub -Total line items 1-5 $ > Tabs referenced on Proposal Form refer to Excel Document "Functional Specs" Alternate: 7 Hourly Rate for Additional Services Hourly $ N/A 8 Support and Maintenance Year 1 Annually $ 12-month warranty period included in base purchase price and begins at sub -system cutover to live operations 9 Support and Maintenance Year 2 Annually $ $259,636 10 Support and Maintenance Year 3 Annually $ $272,618 15-Proposal Form 184 of 186 Company Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Solicitation # RFP180081LK ) Solicitation Name: Computer Aided Dispatch Replacement and Associated Interfaces 11 Support and Maintenance Year 4 Annually $ $286,249 12 Support and Maintenance Year 5 Annually $ $300,561 13 Support and Maintenance Year 6 Annually $ $315,589 14 Support and Maintenance Year 7 Annually $ $331,368 15 Support and Maintenance Year 8 Annually $ $347,936 16 Support and Maintenance Year 9 Annually $ $365,333 17 Support and Maintenance Year 10 Annually $ $383,600 18 Software Updates Year 1 Annually $ Refer to Pricing Note 8 19 Software Updates Year 2 Annually $ Refer to Pricing Note 8 20 Software Updates Year 3 Annually $ Refer to Pricing Note 8 21 Software Updates Year 4 Annually $ Refer to Pricing Note 8 22 Software Updates Year 5 Annually $ Refer to Pricing Note 8 23 Software Updates Year 6 Annually $ Refer to Pricing Note 8 24 Software Updates Year 7 Annually $ Refer to Pricing Note 8 25 Software Updates Year 8 Annually $ Refer to Pricing Note 8 26 Software Updates Year 9 Annually $ Refer to Pricing Note 8 27 Software Updates Year 10 Annually $ Refer to Pricing Note 8 28 Sub -Total (items 7-27) $2,862,890 Grand Total items 6+28 $ $5,380,549 Grand Total Five million three hundred eighty thousand five hundred forty-nine dollars Form Note: 1. Line 5a & 5b were added to represent project services and project software, Hexagon does not price Pricing Notes: 1. Customer is responsible for the purchase, installation, and configuration of all required hardware. 2. Hexagon requires remote access to the customer's servers to complete this effort as quoted. 3. An overall system discount has been provided for this opportunity. Changes to scope of the final contract may change the discount amount. Also, any credits given for line items as part of a Change Order will include a reduction for the line prorated amount of the one-time system discount. Items removed after contract signing will result in a contract credit for future Intergraph software and services being established, not a contract reduction. This discount is based on the acceptance of Hexagon's standard Terms and Conditions. 4. Pricing is valid for 180 days from date of submission. 15-Proposal Form 185 of 186 Company Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Solicitation # RFP180081LKD Solicitation Name: Computer Aided Dispatch Replacement and Associated Interfaces 5. Sales tax is not included in this quote. Final sales tax billed will reflect the applicable tax rates at time of sale as required by law. 6. All Intergraph Products have first year warranty included in SW purchase price; warranty period starts at cut over to live operations 7. Test/Training Interfaces are dependent on the ability of each external system to support interface connectivity for the Test Environment. Due to the fact that the Test Environment does not bear the client load of the Production Environment, load balancing in the Test Environment is not necessary. 8. Regarding Form 1a line items 18 through 27, software updates are included as part of the proposed maintenance. Services to implement the updates are quoted at the time of request. Software updates are made available for software products for which maintenance has been purchased under and subject to Hexagon's maintenance agreement. These updates contain information on the version overview, usability and interoperability feature enhancements, any licensing/distribution updates, and links to additional information and resources. We respectfully request further dialogue regarding future upgrades for the Hexagon solution before a scope of work for the upgrades can be established. Hexagon would like to discuss options that are tailored to the County's final solution architecture. Pending the final architecture of the solution and an established, mutually agreed upon scope of work, Hexagon can provide a quote for an upgrade. We look forward to the opportunity to devise a plan moving forward to address the County's concerns for future budgetary planning and requirements. 15-Proposal Form 186 of 186 HEXAGON SAFETY & INFRASTRUCTURE fi�RAPH ATTACHMENT 4.1 -SYSTEM CONFIGURATION DIAGRAM 1 A4.1-1 TIUBLEOFCONTENTS Page t Physlral CbmPbrim6 Pager Mma1=envlmr.nem Pages Pages CAD T.—dalni�e�lonMeits Pages Re"bvey en..m-- Pagel Page. Nr DI.— Pages eS Page t n��on rend evade on me as lazeie Mncaln i �nosm9 oases aM vMo4m a encwmgetl to tllsN Wte the wo�kbatl xross v'inual hosts. Note It a prBible to separate tlAabaseseners between the PSAPs. Havever, ims ace accent on.—noun-4 between saes am bnd CAD Total ERe"gve Seats Calculator Dispatcher # +Caltlaker # + ((SU M (MPS, NetViewer, NetD,SW.hery5)) N-t—Ua b,", aM a to servesmtlr— the to Ing: tlanisa r k"P s rvg a=coa gankupsFailover rvers (a�gt�lon, mtaraze, ire servNg ihesame Nncfiars wtlhin greh server group, Lee County, FL CAD/Mobile Configuration SYS— overview February 2Di8 m Icno SOS A1,NSYmn CI—) " VA+b l#1(SOLAlw O,,Cluste) Appl cation Server#la ib IRe]unOaMl InSigM R yortmg fe CAD DatabaselHppliwti"n server ttla r ing workstations may . I¢atetl at --t sites antl sell . — to access the ring envim--.-d at Ne I,— sge p—C. Ney have a vxure.—M norm—n to the T- WTrai tlataha am.,,=—Cn rovers. Proprietary and Confidential DDOP�n o-a serrer�oxs serveaa TER vear (DR)exvlRoxl�xr: Sratane� ma' gar e. serve a2 CAD DR VIRTUAL ENVIRONMENT VCAD as ICADSQLAN,.y nCwetep az IZU SOL A,w On Cluster b lApPll"a . Several" 1b1 ReO maryl 2b IRe0 nmaryl hnSSMgM Reporting roreCAD ozwm:eaiAPPII"aEon st m" Color Leg—d Black — Base products Red —Optional products Green — Customer-fu—hed products Pulple— Virtual Specifications HEXAGON SAFE,ra INI RAST—TORE Lee County, FL CAD/Mobile Configuration ce ,,,eett.mu Physical Components and Hardware Specifications February 2018 1Pr erverco R. S'.0 eeHu�R..� ompuR..p.rRcompuRrRoomHxoM Physical Host= Servers 1M- CPU vSp— Ent p-6 x (x2) Two (2). 22 re P«asors POB 16GBCF—HBAS 11 ua vosupplies 6vears or2axT SUPp. Qty: 3f RECOMMENDED HARDWARE SPECIFICATIONS rtla LCB ewlm to.hh d >gonswikn^c pwrstles l6 pMs�acry ff. a tletScatM UPS tsce u�; exrega� guralion aN s¢etl at NA time aty: 1-Prams— E...om.em es(1)R.--Host I Proud,- SAN 11T ConilguSretl omge v sing to 32000 lops st csPerc eesoltlm2- repacY�salromsoatren«t misce Rec e.eeuraeom erairg avrgk twogmcawr Host FC 450E SAN �rwnn wirmows Batxenterallows as 14)16GB FC Pons pn contrdler many VMs ascanceNl«alai to asingk rv�t (21)aroGBSs saverto mntheU A 5Veers 24x] Premium S_n oq'of re—kS relutr mary: 66 taty: 1 for P,.u.,-Ennronment — —11. CABPCIren¢ Bls Query UKof wSh—hpatl rn LCB : 'T'tch (1 PProvitles l6 pMs) ch gy 411.111gm PDus Ean u . a tleNcatetl wikt. Ex«t r«eptaPDck elkatMUUPSUe nrnentotlle�rwl tllon aM s¢e0 at ifial time oH: 1 for DR. Enwonmer8 -(1)Re0 I l ksiug plsaster Recovery SAN 6 5TB f C.N'—g'� t« csperk eewWm2- orepxks.AllrcoresonirervwimusiBe erNirg asingk twogr«asor Host r wkry winnows Ba 1S,5BB lops Rec rrecorm9umtion: Oenn uM3wF SAN (4)16 NS Perc«imller many VMs ascan be albcatal to aslingk BOY sever to mn on tie �oA. f14)moGB SS SVears 24x] Premmm Support pry of re—ks-ukee to O.R.: ba QN: 1 for DR. Envlraemae Color Legend Black —Base products Red —Optional products Green — Customer -famished products Purple — Virtual specifications Proprietary and Confidential 2 1114 HEXAGON SAFETY&INFRASTRUMRE Lee County, FL CAD/Mobile Configuration Maregement Environment February 2g1 B Protlucti- Management Environment S'�QI L- Hexagon Doman I I ✓` I �m a Server., I I g�aam Cemmlle DNS Servers, messo�serv�m'zo�s �I� ,gel I � Posg,es<,_I,ml�w vCeecrl I aewsserve, - I - IGB I I ovn oem II SServera2 I I I oW I sy:rem managemem serverat I '" '° I I I Disaster Recovery Management Errvi--t nt��LServe�r A166 ess(mchayel PosgreS(Y (izlutletl wiN vCemer) sys a¢naganera server N2 Proprietary and Confidential Hexagon Domain I I I I I I I I I I �gNs I I gaaamCemmll ServerN3 I Iwwewsserve, I I� I I � I m�..r m.mym metre. �nue I----wbaeN�--- —I Color Le —d Black — Base products Red —Optional products Green — Customer- —hed products Purple — Virtual Specifications HEXAGON --& INFNasT—TUNE Lee County, FL CAD/Mobile Configuration CAD Protldction Environment February 2gi g CAD Pmd..ton Environment CAD MS SQL AtwaysOn Cluster I I I I I Ao me,taCe�Cemm nba �ens:ederg,a I se oaA-1 .eras (cao soLalwaysonrcwa>) I �eE be M,emH6GLserve,zg,6E,= o ;a� a-,0000a ce I P l) I iiF A�gaESA) Pr�mre(ufsP, I II (.Ao soLAlwaywn clues>) I ItCAn - ,esoma�eePGR I Ifm I Mr..mHSGL Server2m6 EE GB ° I-FlRD,GpsE i M � yp-�5)gFl Vtlm ®-,0000a _ _ _ _ _ _ _ _ _I I z6(fe,` bPzsGPs-AULPe�nLevel CA,} �`e�b�pill�nTe�M1�diesGon � Arctlive MS SQL AlwaysOn Cluster �I n- I I cc o59vsualCAova20a i nSMPlarmintrface Arcbn�e5erve� IA.h snLAlway CI.—) I L�erve,m,6EE IM I I I a@-a000ca Lo_----------I Proprietary and Confidential bbdle Com serve ma s In$Igbt Repmgngg Da--pp—I. 65gM RepNiig FE (!-mre wl Ixerte) Color Le —d Black — Base products Red —Optional products Green — Customer -famished products Purple — Virtual Specifications HEXAGON - -& IFlERAST—TORE Lee County, FL CAD/Mobile Configuration CAD Testantl Training Environments February 21318 Integmt d CAD Integ.t d CAD Testing Envi--t Training Environment ae-Hn Re-m Leenx( Au (irlunetl— v6x-HA) Ed3eFromc Runtime Eigrre Res L�iue) EegeFra oev per Eigiire(1' hsal) Sight Se eer Res s( er(res nse) oTke(I- IN— (D, s) I=D gatabase halnlrq Server Proprietary and Confidential 1 o!✓ —DI . T—i Saver Color Le —d Black — Base products Red —Optional prod, cts Green — Customer- —hed products Purple — Virtual Specifications HEXAGON SAFETY&IN FFAST—TUFE CAD MSSQL AM,.—s On Cluster I I - I I I I I I Ilrr,00araba,eSerVer�, I I� I I MKr�115aLserver�,16FE I I wN I °a oe -,00 B L------------ ------------ Archive MS SQL Alwayson Cluster I I I � I meµ_ wm APpD—serveratc (Amt,_WL AIwaYZOn CI—) I w serve, II e �Ir>,rS�M�„eellree.�l �k�ro�soLserver anfi rf i reaismeR-7soe I I sl°w ��Ba.e" 11-3 -� Lee County, FL CAD/Mobile Configuration Disaster Recovery Envi—DI February 2e1 B CAD DR Environment MIN C,anmunl rl (B-P) Savas Nic R tig(IIFS� Proprietary and Confidential (RaluneanrroP mary�enM1bEII�e Server #Lai (IIMDT MPS ,,°iAULlmefia�el. ur,a«e, (Pillmenael. tpu —,. gecntal grwnn. Color Legend Black -Base products Red -Optional products Green-Customer-f°mished products Purple - Virtual Specifications HEXAGON SAFE— IMFRAsT—TURE Lee County, FL CAD/Mobile Configuration :] cuenta February 2pt B Mnpafcher Workstations Mnpatcher Workstations (Production) (Test) . m+wm, e.eaU+•e•�••+••a•ta Mnpafcher Workstatons MaP Maintenance Web -Based Workstations (Backup) Workstation pispatMerworkstatlans prciudes pispatMer Worksfatims onal (66bn( system aamrnlstmtor omn vow sra (rr.�eowmree( wortsufans) mi�p or�re�r-re(pN. a �sl w.•�•re rmows coal (steal wroriry ospRacn �ra�l pispatcM1erworkstatians <rore a�ree rom� umeoR espo�aer�ap tint rmowsts ofesswral �staiq MaP Maintenancewarlatmlm weelaasee worlotabms ((AYfl1 (aY- reoresl ro�a6neow a(neea moael R Dal (steal oral(stanl (�N- Imea o f R 1 er✓ vmeoa� um(pNs eeoresl PDisPe(cher Workstabon ��� an r(cagpe r roof IR(Gysmrcurrem carer eenmsl � tTremrng) meow I�s�v�reR^m=t1 (pry: s vroaoai.Ireoresl v(pN: 66—.p Iced ) Hexagon nines tom we r— pmPnvsl Hexagon h. proposal concunem user l lcensa Uased on ourcurrem understanding of Dunk for Vtlm ReswcllxaM maxi'— ncunrentopaatons using Ne wommations for CAD a; �ywrval time TM1e pmderto qwn "ceotclem user l¢enseswlll M1e atljazEtl to retlec Irsageat time nc�naz�c11 aponderclmt plspatMer Workst�Ims otnego4�ron. p6patcrrer. tlorvever, Vidm ro nt.ume rmawato ( ( R�tn: w.xa�eco�mav rave as main UackaP N - - apoma Oren vove - tGalses merearev r - t-e xnvciem kennesmast not ag n r par�ner (N.( lo�sl exceed tnenuml»rorpred fi t- _ /papatcrrer coca rc�e Ri«ny pspryatM1 Pararro Hexagonodesh. tre nu �s(tornemote cap v-1tV, (py-eT sl naliNaz Han--PmcTN a-t-..I NnresPe b")regmred 5oasea on V (p9Re Tim( mecusmmersdeclsion and is negome. Client Hardware Specifirati ons pispat—WOMstatims(Includes Map MainW.—Workst . ons svemnadminisba raining, an rMUPWOMstat—) o r o srer 2G Emerxt 9 Ememet Tss rewlur wah z56wro 4s iwa (zl proresaorialzarkM1 rromo nee (31 wmesaooalzan<h room pw arne pry: Tap Proprietary and Confidential Mobile Environment IMOGle pats pomPaRrs I m rop o�l(s and I IWme,rorrwn�saeNrco�mremuse�Ke�s ien icanreslpy-la( I�eeom�����tlfi�a i�g�tatio�a, I p I I 13 r' I a a g oz pN: ap IGIIeRespoMerTadelsorSnunPM1orces I Mal I Color Legend Black - Base products Red -Optional products Green-Customer-fumished products Purple - Virtual Specifications HEXAGON sar-ETra lruF—TaucTURr Lee County, FL CAD/Mobile Configuration Network Emig — I F.b..W 2018 1 If the m- are connected Na dedicated filbe, t,- that filbe, is ­--d by the Orange line I. the drawing. If the sites are connected A. I NEC W-1, ib-- ,i- t,- this is -­--d by the ­.. line. It I, —pfi— —,ilble that both scenarios will exirt within the city network. 8-- NICt—mg is not functional I. Windows 10will be spli b— —6e, bmn Toaswncnes bmn Toaswncnes pz& ---­ I. the -- of . —itch f.H.re. Proprietary and Confidential C.I., L.g. ,d Black -Base products Red -Optional products Green -Customer -famished products Purple -Virtual Specifications HEXAGON SA—& INFRASTRUCTURE Lee County, FL CAD/Mobile Configuration Notes February 213118 1. Color mpmsentatbn in thb mnfg.ration tliiram b as follows_ BIs k—Base Pm ducts Red — Optional Pm ducts (Budgetary Estimates and RO Ms do not indude options) Green— Customer Furnished Products 2_ Hexagon assumes that the Local Area Netwoik TAN),N. witle area network (WAN), Active Directory, antl any Microsoft Exchange Serverinfmstmcture a.0 be provitl.tl antl stag.d bythe Customer. Minimum agency WAN Connection = 10o Mbps_ 3_ Hexagon assumes Nat nelwotic communications provide bytheCustomer(.-snot. sites will support the blowing bantlwitlih requirements. -Each..Ii (ion mining the VD ispatcher diem software re quires a minvnum the, itlih availabAAYof2%Kbps - Each remote woticstation... h the VN.M,spatcher or VNelViewer client software requimsa mininum bantlwitlih availability of 128Kbps_ - Each laptop mining Mobile for Public Safety requires a minimum bantlwitlih availab,idy of 12BKbps_ 4. All workstations, PCs, laptops, antl speci(tl peripheral hartlwam pmvitletl by the Cusomer are.... tl to meet the specitustions ddineatetl on the d gram_ 5_ During implementation, Hexagon unpbmentab., personnel build 5 CAD tlienl wotlrsiffiions antl 5l1 w11 providing indallation instructions so that the Custom., s system sdminist-ator(s)milt have the Imowl.dg. mquiretl to install add Atonal client software_ Fdbwing N. hi Cusomer personnel will be expected to b.d all remaining client-ft.:_Th. approach ensures that, following the clover, Customer personnel will have the sW sd necessary to bu Atl new client ha Nwam_ 6_ Hexagon assumes that the Customer wAl p—d. WAN —hi ications, indutling wireless network communications, that will support the bantlwidh citetl in ft— 3 above_ ]_ Anyatltlilional inter( ce nd specs( ally inclutletl in the configuration will incuran adddbnal cost_ Hexagon is not responsible for costs assocated wdh d.-I.ping the ihiN-pmty portion of.. interface_ 8_ This Conftgumibn Diagram illustrates the proposetl haNware antl software mnfgumtion at the ten.ds.Ihhhsbm During nnpi..., ation, the Hexagon Implementation Team,ora. Hexagon subcodracbr, may after N. configuration to reflect the negotiatetl system or R.Th. bcatbn of software to take ativantage of.ffii, cies d.teth inetl following submission. 9. Hexagon's con figuration does not indude fa mitu-.,n.tworkservices, firewalls, or Micosoft Exchange S...rimpl.—tst-services Sery.... d client worksisibn hartlwam,anti-vims software, backup stmage hardware, and Active Directory may have been optioned in the proposal response. If purchased, it is the Cust—i-s-asp—iibility to maintain these items after implementatbn antl cutov.rof the system_ 10_ If.Training Environment s bid, Hexagon appl-t—are provitletl at redua:tl cost Hexagon applications are pi —id tl at no cost for the Test.nvimnment 11. Test tartac. licenses a-, available forp-.posed interfaces.How.v.-implementation is subject to Cust—i-s ability to th—id. connection to the applicable system_ All flirhpatly external interface connections roquiretl f.,T...g antl/.-Test Envimnmenis are the responsibility of the Customer antl/.,tIi ventlor(s)_ Proprietary and Confidential Color!- p.hd Black — Base products Red —Optional prducts Green — Customer -famished products Purpl.— Virtaal Specifications HEXAGON --& INFBA T—TUBE HEXAGON SAFETY& INFRASTRUCTURE IrvrERGwAPH LEE COUNTY, FL RFP FOR CAD REPLACEMENT ATTACHMENT 4.2 - SYSTEM ARCHITECTURE AND STAGE AND INSTALL ASSUMPTIONS PROPOSED SYSTEM ARCHITECTURE Due to the number of virtual machines required to support the PSAPs, multiple physical servers will be required at the primary and the backup sites. However, it is not necessary for each PSAP to have their own local server to synchronize data. All the servers communicate via TCP/IP. Assuming proper network configuration meeting the specified bandwidth and latency requirements, separate physical locations should not be an issue. Data is synchronized using SQL AlwaysOn. Please see https://msdn.microsoft.com/en-us/library/ff877884(v=sgl.130).aspx for more detail. Each PSAP on the system will be simultaneously operating from the same databases in a high availability, redundant environment. Through configuration settings, this environment allows for each PSAP to access agency -specific Event Types and share as much or as little information with each other as desired. The permission driven access architecture provides PSAPs with the ability to operate as though they are individual centers functioning with unique system configuration, preferences, permissions, and user interfaces (if desired). CAD Database Maintenance (CADDBM) Configuration Specifics Hexagon's solution provides for a highly configurable, permission -driven environment whereas each agency can maintain individual workflow rules, system preferences, User Interface configuration and access. This supports a true multi -agency, multi -jurisdictional system environment, allowing for an unlimited number of agencies on the system, each with their own configurations and preferences. The configuration and maintenance of system files (the database) is accomplished via the CADDBM utility. CADDBM is designed to be easy to use so that agency supervisors and system administrators can access, create, modify, and maintain the database without programmer support. Information is entered into the database quickly and easily by using dialog boxes. Labeled fields indicate the information required and command buttons help prevent users from deleting the wrong information. Prompts and messages are also displayed for assistance. Completing the dialog boxes in the database maintenance program automatically creates database tables, including the following: Agency definition • Cataloged alarm • Deployment plans • Deployment plans/pattern definition • Disposition type • Estimated time of arrival table • Event type Rotational service definition Special address definition Special situation definition Station definition 6, Street (primary) • Street (alias) • Task force definition A4.2-1 HEXAGON SAFETY &INFRASTRUCTURE • Line-up definition • Number table 0 Out -of -service type Personnel a Response list • Roster definition 4.2 - System Architecture and Stage and Install Assumptions • Terminal node definition • Unit definition e Update cross streets Update intersections User group definition ® Vehicle definition Tables are located in the database and can be created, reviewed, and changed. No downtime is required when updating tables via the CADDBM utility. Overall CAD System Configuration The proposed host servers support high availability software and hardware standards, such as clustering and virtualization. Hexagon has proposed host server hardware that uses VMware vSphere Enterprise to support server virtualization for the CAD/Mobile Solution. Because access to information in the I/CAD Database is cardinal to sustaining system operability, Hexagon configures fully redundant I/CAD Database Servers to prevent disruption of operations in the unlikely event of a complete server failure. Hexagon's proposed system provides 24/7 operations for the core I/CAD System. Please note that Hexagon defines reliability/availability as the continuous operation of the system needed to maintain mission -critical call taking and dispatching activities, exclusive of scheduled downtime. SQL Server AlwaysOn Availability Groups can provide high availability and disaster recovery for the I/CAD database. AlwaysOn is an Enterprise Edition feature that provides server -based replication of the primary database to one or more secondary replica databases, automatic failover if the primary database fails, and automatic resynchronization of the former primary after a failover. In the proposed I/CAD System configuration, the primary database, a synchronous secondary replica database with automatic failover, archive database and production clients are all located at the main site. A secondary replica database with automatic failover and backup clients is located at an alternate site. The alternate site may be used for normal operations or it may be used for disaster recovery. It is recommended to locate the file share witness at a third location to act as the witness in the event of a total site failure at either location. The diagram on the following page depicts an archive database maintained by DBCopy (I/Backup). To ensure good performance on the live system, Hexagon recommends having an archive database that maintains all historical data, while keeping a minimum of data in the production environment. A4.2-2 HEXAGON SAFETY & IN FRASTRUCTU RE 4.2 - System Architecture and Stage and Install Assumptions site 2 Site 2 Environment Environment Sync 'onou aO Secondary t Replica as second Automatic �ailav� Wide Area Network Users Update Data Workstations Clusfer File Share Witness Workstations This configuration provides high availability (via the secondary replica with automatic failover) as well as disaster recovery (via the synchronous secondary database). If the primary database goes down, the synchronous replica database at the primary site will change roles to the primary. If something were to happen to the secondary replica at the primary site then the database would failover to the secondary replica at the secondary site. All clients at any site run against the active database without changes being made to the clients; this is a feature and benefit of SQL AlwaysOn. Since the clients at the main site are connected to a local database, and since the replica at the alternate site is synchronous, the network between the two sites is critical since the primary and failover partners are split across sites. This requires high bandwidth, low latency and a highly redundant network between sites. If there are multiple agencies, having one CAD system provides a common operational picture. A single CAD system also reduces the hardware, software and maintenance costs. With the customer having a disaster recovery site, this option allows them to have a replica database at that site configured for automatic failover. Since that replica is maintained using AlwaysOn, the customer can use the same AlwaysOn administrative tools to manage the replica and perform failovers. Great high availability and disaster recovery solution with a single CAD system A4.2-3 HEXAGON SAFETY & IN FRASTRUCTU RE 4.2 - System Architecture and Stage and Install Assumptions The DR site as proposed is a warm site. Databases are part of the replication process and data can be maintained in real time and configured for automatic failover. CAD clients will automatically connect to the active CAD Database. Interfaces and Reporting applications require intervention to failover to the DR location. To enhance the failover functionality provided by SQL Server, the I/CAD Database access layer has been improved to provide seamless application -level failover. Following a failover, the Hexagon software automatically reconnects to the new principal and replays any in -progress transactions, so no user action is required during a failover. Once the principal re-establishes communication and determines that the servers are ready, SQL Server automatically handles re -synchronizing the databases. The resynchronization process runs seamlessly in the background, without interrupting live operations. Within the communications/interface environment, adding the Redundant Communications/Interface Server configuration enables redundancy for eligible service applications using the Hexagon Interface Service Manager (ISM), which runs as a normal Windows service on each communications server. If redundancy for eligible interfaces is exercised by the Customer, ISM accepts signals instructing each eligible interface and its redundant counterparts to begin in active or standby mode, and to switch from standby to active mode when designated parameters are met. Because a process running in standby mode maintains memory of the current system state, it can switch to active mode much more quickly than starting a fresh process (cold backup). In the redundant interfaces configuration, Communications/Interface Server #1a acts as the primary communications server and the Communications/Interface Server #1 b (Hot Failover) and Communications/Interface Server#1c (Cold Backup) provide the redundant counterparts. ISM coordinates processes between these servers for eligible Hexagon service applications. Primary communication takes place over the normal network path, but Hexagon recommends a second communication channel, which can be a network connection or a serial link, for this communications connection. Once communications are established, the copies of ISM determine which copy of each interface service should be started in active mode and which in standby. If load balancing becomes necessary as interfaces are added in the future, it is possible to configure some of the interface services to be normally active on one server, and other interface services to be normally active on the others. Once ISM is configured, if an active eligible interface service fails, the copy of ISM on that machine immediately signals a redundant copy of ISM to switch from standby to active mode. Then ISM restarts the original interface service in standby mode. If an entire Communications/Interface server fails, a secondary copy of ISM detects the loss of communications with its peer and switches all standby interface services to active mode. Timeout for loss of communications is configurable, with a typical range of time between 5 and 60 seconds. Shorter times lead to unnecessary process switches due to momentary communication delays, while longer times lead to unacceptable outage durations in the case of actual failures. Hexagon has expended considerable effort in designing the redundant capability of the I/CAD System to suit the operational imperatives of the Public Safety mandate. The aim of the architecture is to provide continuous operation of the core I/CAD Database servers using SQL Server AlwaysOn Availability, in concert with the enhanced I/CAD Database access layer software and redundant hardware. However, even by adding the Redundant Communications/Interface server and implementing ISM and redundant A4.2-4 HEXAGON SAFETY & IN FRASTRUCTU RE 4.2 - System Architecture and Stage and Install Assumptions network links, as described above, not all interfaces can be reproduced. Implementation of redundant, test, training, and backup interfaces is subject to the customer's ability to provide connections to the applicable systems and the ability of each external system to support interface connectivity. ISM notifies users if access to an interface or interface network is unavailable. Concerning EdgeFrontier and custom interfaces, redundant, test, training and backup copies are available for all proposed interfaces; however, implementation is subject to the customer's ability to provide connection to the applicable system. Additionally, while a redundant instance of the EdgeFrontier Runtime Engine could automatically takeover during a failover, there may be features of an EdgeFrontier interface that require additional configuration time at additional cost to support automatic failover. Backup Requirements CAD requires that the database be backed up, as well as the configuration and software delivery items. Hexagon will set up and configure SQL Server Maintenance Plans that backup the CAD database to local disks inside the database servers. Customers are responsible for using their existing enterprise level backup technologies to then take that backup and store it in an alternate location. For the configuration and software delivery items, customers can simply include their location in the standard enterprise level backup plans already in use. All system functions for all applications being proposed are available during backup. Backups can be scheduled to occur automatically and be performed unattended, if desired. Routine backup will ensure a full backup of the database. Backing up the full system (all the settings on the server, programs, registry settings and files) is the client's responsibility. The SQL Server maintenance plan is comprised of multiple jobs. One job backs up the transaction logs every 15 minutes. One job backs up the entire database (complete backup) once per day, and the other jobs are used to maintain the backups stored on the disk. Retention period of backups is configured based on customer desires. There is no impact to live operations or use of the system during any of the backup jobs. Time to complete the transaction log and complete database backups are dependent on the transaction volume and data retention schedule for the customer. However, transaction log backups are usually performed in seconds, and the complete backup in less than five minutes. System backup is a System Administrator task. Benefits to the Client Hexagon has proposed fully redundant I/CAD Database Servers at the primary site with synchronous replicas for secondary failover at an alternate site to prevent disruption of operations in the unlikely event of a complete server failure. Please refer to the above responses concerning the proposed high availability configuration. In the configuration (one synchronous replica at the primary and those at the secondary site), operations for one of the I/CAD Database servers can be suspended or fail without affecting the other database. As long as one of the synchronous replicas and the file share witness are available the database will be available. Due to issues with WAN connectivity Hexagon does not recommend that only one failover partner be located at a remote location. If a critical part of the server goes down rendering the database on that server unavailable, the replica will take a matter of milliseconds to take over. Within a second, the failover would be complete. Once the A4.2-5 HEXAGON SAFETY & IN FRASTRUCTU RE 4.2 - System Architecture and Stage and Install Assumptions failure reason has been identified and corrected, and the primary system is returned to service, the primary and replicated secondary databases will automatically resynchronize and return to a fully redundant state. No user intervention is required for this to occur. The amount of time required for resynchronization of the databases depends on the amount of time the failed server was down. Synchronization is automatic; however, whatever database that is online when the other database comes online will stay active. The Administrator will have to manually fail the database back over to the primary Database. This process is simple and invisible to the clients. Clarification on Virtual Server Stage and Install Assumptions Hexagon clarifies that the services for virtual server staging and installation are included in Hexagon's base pricing. Services for physical server staging and installation are not included in this proposal response as Hexagon assumes hardware will be procured by the County separately. Hexagon assumes the following: The Customer will perform debris removal, discarding of shipping boxes and pallets Services to stage/install mobile workstations or devices are not included Services to stage/install extended cabling are not included The Customer has sufficient space, power and KVM connections for servers Console modifications such as installation of monitor trees are not included Stage and installation services for optional Servers are at additional cost, when requested and delivered at the same time as the primary servers Equipment will be staged at the client site Electrical Requirements for Servers Minimum/maximum electrical requirements will be provided once all servers have been concretely identified. However, the optioned server electrical requirements are typical of Tier 1 server manufacturers. Published environmental requirements for servers are as follows: Operating Temperature: 10' to 35°C (50' to 95°F) Storage Temperature: -40' to 65°C (-40° to 149°F) Operating Relative Humidity: 10% to 90% Storage Relative Humidity: 5% to 95% Hexagon agrees to provide recommendations concerning upgrades to existing facilities. However, Hexagon does not assume responsibility for enumerating site preparation tasks required to comply with electrical and environmental requirements, inspecting and approving upgrades completed by the County, or supporting the cost of physical or environmental alterations or modifications required to support system installation following work performed by the County. In support of the Site Preparation tasks, the County is responsible for configuring, providing, and installing the following: HVAC, as required by the hardware manufacturer for the servers prior to installation Electrical power with proper receptacles for each device prior to installation A4.2-6 HEXAGON SAFETY & IN FRASTRUCTU RE 4.2 - System Architecture and Stage and Install Assumptions Network drops and patch cables for each connection Tabular documentation of floor plans of the installation locations Engineering or systems administrator support during the pre -installation walkthrough All telephony hardware, server hardware and client hardware provided by the County (workstations, PCs, and/or mobile hardware). Hexagon agrees to configure provided hardware to print to existing network printers supported under the proposed operating system. A4.2-7 HEXAGON SAFETY & INFRASTRUCTURE fi�RAPH TAB 5 - PRICE PROPOSAL Form ]a —Proposal Form (not applicable for CCNA solicitations) LEE COUNT" SOUTHWEST FLORIDA Lee County Procurement Management PROPOSALFORM Company Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Solicitation # RFP180081LKD soucnauon Name: uom user Hiaea uis atcn rce iacemeni ana Hssociaiea inierraces Having care u y examine a erms an on i ions , and the "Lietailed Specifications", all of which are contained herein, propose to furnish the following, which meet these specifications. From Notice to Proceed or Purchase Order date, whichever applies, 335 calendar days to substantial completion, 30 calendar days to final completion (estimated timeline 365 total calendar days.) Proposal to be based on this timeline. The county reserves the right to negotiate with awarded vendor. Draw Schedule based on the following: 1 Project Management Plan Acceptance: 80% of line item #1 2 Installation: 80% of line item #2 3 Training: 80% of line item #3 4 Go -Live: 80% of line item # 4 5 Final Acceptance: 20% of line item 1-4. 100% of line item #5 For evaluation purposes "To Be Determined" or "ranges of price" are not acceptable entries. If a firm rice is not provided zero POITITS will De earned for this evaluation category. Item # Description Unit o Measure Total Cost 1 Project Management Plan Acceptance Lump Sum $ Included in 5a 2 Installation (tabs 2-11) Lump Sum $ Included in 5a 3 Training and Support (tabs 12 & 14) Lump Sum $ Included in 5a 4 Go -Live Lump Sum $ Included in 5a 5 Final Acceptance Lump Sum $ Included in 5a 5a Project Services Lump Sum $ $1 353 257 5b Project Software Lump Sum $ $1,164,401 6 Sub -Total (line items 1-5) $2,517,659 Tabs referenced on Proposal Form refer to Excel Document "Functional Specs" Alternate: 7 Hourly Rate for Additional Services Hourly $ N/A 8 Support and Maintenance Year 1 Annually $ 12-month warranty period included in base purchase price and begins at sub -system cutover to live operations 9 Support and Maintenance Year 2 Annually $ $259,636 15-Proposal Form 1 of 3 Company Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Solicitation # RFP180081LK ) Solicitation Name: Computer Aided Dispatch Replacement and Associated Interfaces 10 Support and Maintenance Year 3 Annually $ $272,618 11 Support and Maintenance Year 4 Annually $ $286,249 12 Support and Maintenance Year 5 Annually $ $300,561 13 Support and Maintenance Year 6 Annually $ $315,589 14 Support and Maintenance Year 7 Annually $ $331,368 15 Support and Maintenance Year 8 Annually $ $347,936 16 Support and Maintenance Year 9 Annually $ $365,333 17 Support and Maintenance Year 10 Annually $ $383,600 18 Software Updates Year 1 Annually $ Refer to Pricing Note 8 19 Software Updates Year 2 Annually $ Refer to Pricing Note 8 20 Software Updates Year 3 Annually $ Refer to Pricing Note 8 21 Software Updates Year 4 Annually $ Refer to Pricing Note 8 22 Software Updates Year 5 Annually $ Refer to Pricing Note 8 23 Software Updates Year 6 Annually $ Refer to Pricing Note 8 24 Software Updates Year 7 Annually $ Refer to Pricing Note 8 25 Software Updates Year 8 Annually $ Refer to Pricing Note 8 26 Software Updates Year 9 Annually $ Refer to Pricing Note 8 27 Software Updates Year 10 Annually $ Refer to Pricing Note 8 28 Sub -Total (items 7-27) $ $2,862,890 Grand Total items 6+28 $ $5,380,549 Grand Total Five million three hundred eighty thousand five hundred forty-nine dollars Form Note: 1. Line 5a & 5b were added to represent project services and project software, Hexagon does not price at the task level Pricing Notes: 1. Customer is responsible for the purchase, installation, and configuration of all required hardware. 2. Hexagon requires remote access to the customer's servers to complete this effort as quoted. 15-Proposal Form 2 of 3 Company Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Solicitation # RFP180081LKD Solicitation Name: Computer Aided Dispatch Replacement and Associated Interfaces 3. An overall system discount has been provided for this opportunity. Changes to scope of the final contract may change the discount amount. Also, any credits given for line items as part of a Change Order will include a reduction for the line prorated amount of the one-time system discount. Items removed after contract signing will result in a contract credit for future Intergraph software and services being established, not a contract reduction. This discount is based on the acceptance of Hexagon's standard Terms and Conditions. 4. Pricing is valid for 180 days from date of submission. 5. Sales tax is not included in this quote. Final sales tax billed will reflect the applicable tax rates at time of sale as required by law. 6. All Intergraph Products have first year warranty included in SW purchase price; warranty period starts at cut over to live operations 7. Test/Training Interfaces are dependent on the ability of each external system to support interface connectivity for the Test Environment. Due to the fact that the Test Environment does not bear the client load of the Production Environment, load balancing in the Test Environment is not necessary. 8. Regarding Form 1a line items 18 through 27, software updates are included as part of the proposed maintenance. Services to implement the updates are quoted at the time of request. Software updates are made available for software products for which maintenance has been purchased under and subject to Hexagon's maintenance agreement. These updates contain information on the version overview, usability and interoperability feature enhancements, any licensing/distribution updates, and links to additional information and resources. We respectfully request further dialogue regarding future upgrades for the Hexagon solution before a scope of work for the upgrades can be established. Hexagon would like to discuss options that are tailored to the County's final solution architecture. Pending the final architecture of the solution and an established, mutually agreed upon scope of work, Hexagon can provide a quote for an upgrade. We look forward to the opportunity to devise a plan moving forward to address the County's concerns for future budgetary planning and requirements. 15-Proposal Form 3 of 3 Customer: Lee County, Florida Quote Number: New Internal_USPS Lee County_$020218$cw Rev. #: Quote Date: February 16, 2018 Expiration Date: August 15, 2018 CAD -Mobile Part Number IPS0035NC DescriptionSoftware I/Backup(No Charge) (IPS0035NC) 2 0.00 $0.00 IPS0042I I/NetViewer (IPS0042I) 5 2,148.85 $10,744.24 IPS2301 Intergraph lnSight Reporting for l/CAD (IPS2301) 1 12,423.42 $12,423.42 ANI-ALI ANI-ALI (Included with I/Executive) 5 0.00 $0.00 IPSOOOIHA I/Executive for High Availability NL 1 72,253.40 $72,253.40 3ptbds-6 Site license of PresenTense Time Client NT. Supports unlimited servers or workstations in t 1 1,053.00 $1,053.00 IPS0008 I/Push To Talk (IPS0008) 1 10,745.69 $10,745.69 IPS0012 I/Page (IPS0012) 3 21,472.90 $64,418.69 IPS0018 I/Telephone Device for Deaf - Zetron NL (IPS0018) 1 10,745.69 $10,745.69 IPS0048 I/FRMS-CADlink NL (IPS0048) 1 10,745.69 $10,745.69 IPS0051 I/CADLink NL (IPS0051) 1 10,745.69 $10,745.69 IPS0052 I/Fire Station Alerting (IPS0052) 1 10,745.69 $10,745.69 IPS0053 I/Fire Station Printing NL (IPS0053) 1 10,745.69 $10,745.69 IPS1018 I/Sight Server NL (IPS1018) 1 11,050.61 $11,050.61 IPSCADCUST Econolite Consulting Services -Automatic Traffic Management System(ATMS) (IPSCADCUS 1 4,498.00 $4,498.00 IPSCADCUST-2 Video Responder Interface to TBD Camera System (IPSCADCUST-2) 1 40,340.80 $40,340.80 IPSCADCUST-3 Interface to Telestaff (IPSCADCUST-3) 1 11,666.56 $11,666.56 IPS3042 EdgeFrontier Runtime Engine (IPS3042) 1 19,860.90 $19,860.90 PSA1002 ASAP CAD EF Interface (PSA1002) 1 8,849.28 $8,849.28 PSA1002DS Interface -specific Custom Development Services 1 13,663.60 $13,663.60 PSA1014 Spillman Flex CAD EF Interface (PSA1014) 1 8,849.28 $8,849.28 PSA1014DS Interface -specific Custom Development Services 1 8,996.00 $8,996.00 PSA1018 InterCAD CAD EF Interface (PSA1018) 1 8,849.28 $8,849.28 PSA1018DS Interface -specific Custom Development Services 1 4,498.00 $4,498.00 PSA1018-1 InterCAD CAD EF Interface (PSA1018-1) 1 8,849.28 $8,849.28 PSA1018-1DS Interface -specific Custom Development Services 1 4,498.00 $4,498.00- PSA1018-2 InterCAD CAD EF Interface (PSA1018-2) 1 8,849.28 $8,849.28 PSA1018-2DS Interface -specific Custom Development Services 1 4,498.00 $4,498.00 PSA1017 ASTRO 25 CAD EF Interface (PSA1017) 1 8,849.28 $8,849.28 PSA1017DS Interface -specific Custom Development Services 1 4,498.00 $4,498.00 IPS3042-RDT EdgeFrontier Runtime Engine - Redundant License (IPS3042-RDT) 1 13,903.92 $13,903.92 IPSOOOBRDT I/Push To Talk - Redundant License (IPSOOOBRDT) 1 7,513.18 $7,513.18 IPS0012RDT I/Page- Redundant License (IPS0012RDT) 3 15,034.14 $45,102.43 IPSOO18RDT I/Telephone Device for Deaf - Zetron NL - Redundant License (IPSOOIBRDT) 1 7,513.18 $7,513.18 IPS0048RDT I/FRMS-CADlink NL - RDT License (IPS0048RDT) 1 7,522.42 $7,522.42 IPS0051RDT I/CADLink NL - Redundant License (IPS0051RDT) 1 7,522.42 $7,522.42 IPS1018RDT I/Sight Server NL - Redundant License (IPS1018RDT) 1 7,744.18 $7,744.18 IPS0009 I/Mobile Data Terminal NL (IPS0009) 1 47,262.69 $47,262.69 IPS0009A I/Mobile Data Terminal NL -Additional License (IPS0009A) 2 4,868.49 $9,736.98 IPS1183 Intergraph Remote Content Management CC (IPS1183) 1 0.00 $0.00 IPS0015 I/Tracker (IPS0015) 1 26,827.98 $26,827.98 IPS0015A I/Tracker-Additional License (IPS0015A) 3 3,173.66 $9,520.98 IPS0001HATST I/Executive for High Availability NL-Test License 1 0.00 $0.00 IPS0042ITST I/NetViewer - Test License 5 0.00 $0.00 IPS3042-TST EdgeFrontier Runtime Engine -Test License (IPS3042-TST) 1 0.00 $0.00 IPS3042DEV EdgeFrontier Developer Engine (IPS3042DEV) 1 14,897.80 $14,897.80 IPS0009TST I/Mobile Data Terminal NL -Test License (IPS0009TST) 1 0.00 $0.00 IPS0015TST I/Tracker-Test License (IPSOOISTST) 1 0.00 $0.00 IPS1018TST I/Sight Server NL - Test License (IPS1018TST) 1 0.00 $0.00 IPSOOOIHATRN I/Executive for High Availability NL- Training License 1 43,194.94 $43,194.94 IPS0042ITRN I/NetViewer - Training License 5 1,268.46 $6,342.32 IPS3042-TRN EdgeFrontier Runtime Engine - Training License (IPS3042-TRN) 1 11,949.03 $11,949.03 IPS0009TRN I/Mobile Data Terminal NL- Training License (IPS0009TRN) 1 27,891.35 $27,891.35 IPS0015TRN I/Tracker-Training License (IPS0015TRN) 1 15,821.01 $15,821.01 IPS101STRN I/Sight Server NL - Training License (IPS1018TRN) 1 6,647.96 $6,647.96 IPS2301BCK Intergraph lnSight Reporting for I/CAD - BCK (IPS2301BCK) 1 0.00 $0.00 IPSOOOIHABCK I/Executive for High Availability NL- Backup License 1 0.00 $0.00 3ptbds-6 Site license of PresenTense Time Client NT. Supports unlimited servers or workstations in t 1 1,053.00 $1,053.00 IPS3042-BCK EdgeFrontier Runtime Engine - Backup License (IPS3042-BCK) 1 0.00 $0.00 IPSOOO8BCK I/Push To Talk - Backup License (IPSOOO8BCK) 1 0.00 $0.00 IPS0012BCK I/Page - Backup License (IPS0012BCK) 3 0.00 $0.00 IPSOO18BCK I/Telephone Device for Deaf - Zetron NL - Backup License (IPSOOI8BCK) 1 0.00 $0.00 IPS0048BCK I/FRMS-CADlink NL - Backup License (IPS0048BCK) 1 0.00 $0.00 IPS005IBCK I/CADLink NL - Backup License (IPS0051BCK) 1 0.00 $0.00 IPS0052BCK II/Fire Station Alerting - Backup License (IPS0052BCK) 1 0.00 $0.00 I PS0053BCK I/Fire Station Printing NL - Backup License (IPS0053BCK) 1 0.00 $0.00 IPS101SBCK I/Sight Server NL - Backup License (IPS1018BCK) 1 1 0.00 1 $0.00 IPSPRCMDL_$031315$(Master) - 1 of 3 IPS0009RDT I/Mobile Data Terminal NL- Redundant License (IPS0009RDT) 1 33,088.63 $33,088.63 IPS0009ARDT I/Mobile Data Terminal NL -Additional Redundant License (IPS0009ARDT) 1 3,403.03 $3,403.03 IPS1183RDT Intergraph Remote Content Management CC - Redundant License (IPS1183RDT) 1 0.00 $0.00 IPS0015RDT I/Tracker- Redundant License (IPS0015RDT) 1 18,800.70 $18,800.70 IPS0015ARDT I/Tracker- Additional Redundant License (IPS0015ARDT) 3 2,215.46 $6,646.37 IPS0042IBCK I/NetViewer - Backup License 5 0.00 $0.00 IPS0002 I/Dispatcher (IPS0002) 6 17,716.31 $106,297.85 IPS1128 ProQA Paramount I/CAD Interface (IPS1128) 6 445.16 $2,670.96 IPS1024 Video Responder NL (IPS1024) 6 1,119.90 $6,719.40 IPS0002TST I/Dispatcher-Test License (IPS0002TST) 1 0.00 $0.00 IPS0084 I/Map Editor for ArcGIS NL (IPS0084) 1 3,297.19 $3,297.19 IPS0082 Map Administration Utility (IPS0082) 1 10,237.61 $10,237.61 IPS0002TST I/Dispatcher-Test License (IPS0002TST) 4 0.00 $0.00 IPS112STST ProQA Paramount I/CAD Interface - Test License (IPS1128TST) 4 0.00 $0.00 IPS1024TST Video Responder NL -Test License (IPS1024TST) 4 0.00 $0.00 IPS0002TRN I/Dispatcher-Training License (IPS0002TRN) 4 10,451.69 $41,806.77 IPS112STRN ProQA Paramount I/CAD Interface - Training License (IPS1128TRN) 4 264.16 $1,056.64 IPS1024TRN Video Responder NL- Training License (IPS1024TRN) 4 681.16 $2,724.62 IPS0002BCK I/Dispatcher- Backup License (IPS0002BCK) 6 0.00 $0.00 IPS1128BCK ProQA Paramount I/CAD Interface - Backup License (IPS1128BCK) 6 0.00 $0.00 IPS102413CK Video Responder NL - Backup License (IPS1024BCK) 6 0.00 $0.00 IPS0080 Mobile for Public Safety CC (IPS0080) 1S0 1,110.66 $199,918.80 MPSCUSTO M 18F MPS Custom Build for Fire (MPSCUSTOMI8F) 1 3,234.00 $3,234.00 Software Subtotal:1 $1,164,401.36 Part Number Implementation Services Description Project Management Services 1 177,724.86 $177,724.86 SME 1 43,660.00 $43,660.00 GIS 1 67,216.80 $67,216.80 CAD Implementation Services 1 277,438.00 $277,438.00 Interface Implementation Services 1 253,523.20 $253,523.20 BU Devlopment 1 1 67,760.00 $67,760.00 BU Devlopment2 1 11,487.20 $11,487.20 Training 1 244,310.40 $244,310.40 Virtual Machine Stage and Install 1 12,357.90 $12,357.90 Travel 1 163,614.00 $163,614.00 Project Services 1 1,319,092.36 $1,319,092.36 Shipping and Insurance 1 165.00 $165.00 Implementation Subtotal: $1,319,257.36 3 ptbds-7 Hexagon LMS Per User Training Monthly Access (available for 30 consecutive days priorto 500 20.00 $10,000.00 3ptbds-8 Hexagon LMS Per User Training Yearly Access (available for 12 consecutive months beginn 100 240.00 $24,000.00 Training Subtotal: $34,000.00 Software Tota 1: $1,164,401.36 Services Total: $1,319,257.36 Training Total: $34,000.00 Subtotal: $2,517,658.72 1. Customer is responsible for the purchase, installation, and configuration of all required hardware. 2. Hexagon requires remote access to the customer's servers to complete this effort as quoted. 3. An overall system discount has been provided for this opportunity. Changes to scope of the final contract may change the discount amount. Also, any credits given for line items as part of a Change Order will include a reduction for the line prorated amount of the one-time system discount. Items removed after contract signing will result in a contract credit for future Intergraph software and services being established, not a contract reduction. This discount is based on the acceptance of Hexagon's standard Terms and Conditions. 4. For items included in the options section, project management services and implementation services are not included. Maintenance is also not included unless noted. Hexagon services are valid for 6 months and Hexagon product pricing is valid for one year after contract signing. Hexagon can provide a fixed quote when optional items are selected. 5. Pricing is valid for 180 days from date of submission. 6. Sales tax is not included in this quote. Final sales tax billed will reflect the applicable tax rates at time of sale as required by law. 7. All Intergraph Products have first year warranty included in SW purchase price; warranty period starts at cut over to live operations 8. Test/Training Interfaces are dependent on the ability of each external system to support interface connectivity for the Test Environment. Due to the fact that the Test Environment does not bear the client load of the Production Environment, load balancing in the Test Environment is not necessary. IPSPRCMDL_$031315$(Master) - 2 of 3 Optional Price Items 0 First Year Intergraph Software Maintenance after Warranty 1 259,636.20 • $259,636.20 0 Second Year Software Maintenance 1 272,618.00 $272,618.00 0 Third Year Software Maintenance 1 286,249.00 $286,249.00 0 Fourth Year Software Maintenance 1 300,561.00 $300,561.00 0 Fifth Year Software Maintenance 1 315,589.00 $315,589.00 0 Sixth Year Software Maintenance 1 331,368.00 $331,368.00 0 ISeventh Year Software Maintenance 1 347,936.00 $347,936.00 0 Eighth Year Software Maintenance 1 1 365,333.00 $365,333.00 0 INinth Year Software Maintenance 1 1 383,600.00 $383,600.00 Optional Software Subtotal: $2,862,890.20 BWnal cl- M��ric- IPS3206 Intergraph Mobile Responder Server (IPS3206) 1 0.00 Extended Price $0.00 IPS3204 Intergraph Mobile Responder Client (IPS3204) 10 512.00 $5,120.00 IPS0004-A I/Informer Custom Query Interface to FCIC/NCIC (IPSCADCUST-IPS0004-A) 1 32,624.00 $32,624.00 IPS0004 I/Informer (IPS0004) 1 32,289.00 $32,289.00 IPS0004TRN I/Informer-Training License (IPSCADCUST-IPS0004TRN) 1 18,910.00 $18,910.00 IPS0004TST I/Informer -Test License (IPSCADCUST-IPS0004TST) 1 0.00 $0.00 IPS0004BCK I/Informer - Backup License (IPS0004BCK) 1 0.00 $0.00 IPS0004RDT I/Informer- Redundant License (IPS0004RDT) 1 1 1 22,594.00 1 $22,594.00 Optional 1st Year Software Maintenance Subtotal:l 111,537.00 IPSPRCMDL_$031315$(Master) - 3 of 3 HEXAGON -'1NTERGRAPH SAFETY & INFRASTRUCTURE TAB 6 - REQUIRED FORMS Steven Cost President Intergraph Corporation . .�Hexagon Safety � Infrastructure HEXAGON 305 Intergraph Way SAFETY & INFRASTRUCTURE Madison, AL 35758, USA CERTIFICATE OF AUTHORIZATION I, Steven Cost, President of Hexagon, Safety & Infrastructure Division of Intergraph Corporation, a Delaware corporation ("Corporation"), do herby certify that Richard Morris, who signed this Agreement on behalf of Hexagon, Safety & Infrastructure, is Senior Divisional Counsel of said Corporation acting within the scope of his Corporate powers. Steven Cost President Intergraph Corporation Hexagon, Safety & Infrastructure Date: October 18, 2016 Ver 0610812017-3 Form I Solicitation Response Form LEE COUNTY PROCUREMENT MANAGEMENT E E E COUNTY SOLICITATION RESPONSE FORM S f) 11 '1' 11 W I? S '1- 1' L (P R 1 17 n Date Submitted: 2/16/2018 Deadline Date: 2/20/2018 SOLICITATION IDENTIFICATION: RFP 180081 LKD SOLICITATION NAME: Computer Aided Dispatch Replacement & Associated Interfaces (CAD) COMPANY NAME: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure (Hexagon) NAME & TITLE: (TYPED ORPRINTED) Allana Williamson, Regional Sales Manager BUSINESS ADDRESS: (PHYSICAL 305 Intergraph Way, Madison, AL 35758-7567 CORPORATE OR MAILING ADDRESS: N SAME AS PHYSICAL Same as Business (Physical) Address AnnRFss MtisT MATCH SUNsrz.nRG Confirmed. Address matches Sunbiz.org registration E-MAIL ADDRESS: Allana.williamson@hexagonsi.com PHONE NUMBER: 256-529-0929 FAX NUMBER: 256-730-8608 NOTE REQUIREMENT: IT IS THE SOLE RESPONSIBILITY OF THE VENDOR TO CHECK LEE COUNTY PROCUREMENT MANAGEMENT WEB SITE FOR ANY ADDENDA ISSUED FOR THIS PROJECT. THE COUNTY WILL POST ADDENDA TO THIS WEB PAGE, BUT WILL NOT NOTIFY. In submitting this proposal, Proposer makes all representations required by the instructions to Proposer andfurther warrants and represents that: Proposer has examined copies of all the solicitation documents and the following addenda: 'T7. I Dated: 1/31/2018 No. 2 Dated: 2/8/2018 _ _ No. 3 Dated: 2/14/2018 1. Dated: No. Dated: Tax Payer Identification Number: 63-0573222 No. Dated: (1) Employer Identification Number -or- (2) Social Security Number: ** Lee County collects your social security number for tax reporting purposes only Please submit a copy of your registration from the website www.sunbiz.ora establishing the Proposer/firm as authorized (including authorized representatives) to conduct business in the State of Florida, as provided by the Florida Department of State, Division of Corporations. 1 Collusion Statement: Lee County, Florida The undersigned, as Proposer, hereby declares that no person or other persons, other than the undersigned, are interested in this solicitation as Principal, and that this solicitation is submitted without collusion with others; and that we have carefully read and examined the specifications or scope of work, and with full knowledge of all conditions under which the services herein is contemplated must be furnished, hereby propose and agree to furnish this service according to the requirements set out in the solicitation documents, specifications or scope of work for said service for the prices as listed on the county provided price sheet or (CCNA) agree to negotiate prices in good faith if a contract is awarded. 2 Scrutinized Companies Certification: Section 287.135, FL § , prohibits agencies from contracting with companies, for goods or services over $1,000,000, that are on either the Scrutinized Companies with Activities in Sudan List or the Scrutinized Companies with Activities in the Iran Petroleum Energy Sector List. Both lists are created pursuant to section 215.473, FL§. As the person authorized to sign on behalf of Respondent, I hereby certify that the company identified above not listed on either the Scrutinized Companies with Activities in Sudan List or the Scrutinized Companies with Activities in the Iran Petroleum Energy Sector List. I understand that pursuant to section 287.135, FL§, the submission of a false certification may subject company to civil penalties, attorney's fees, and/or costs. i RFP18008ILKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form#1 — Solicitation Form, Page 2 3 Business Relationship Disclosure Requirement: Sections 112.313(3) and 112.313(7), FL§, prohibit certain business relationships on the part of public officers and employees, their spouses, and their children. See Part IIl, Chapter 112, FL § and/or the brochure entitled "A Guide to the Sunshine Amendment and Code of Ethics for Public Officers, Candidates and Employees" for more details on these prohibitions. However, Section 112.313(12), FL § (1983), provides certain limited exemptions to the above -referenced prohibitions, including one where the business is awarded under a system of sealed, competitive bidding; the public official has exerted no influence on bid negotiations or specifications; and where disclosure is made, prior to or at the time of the submission of the bid, of the official's or his spouse's or child's interest and the nature of the intended business. The Commission on Ethics has promulgated this form for such disclosure, if and when applicable to a public officer or employee. If this disclosure is applicable request form "INTEREST IN COMPETITIVE BID FOR PUBLIC BUSINESS" (Required by 112.313(12)(b), Florida Statute (1983)) to be completed and returned with solicitation response. It is the proposer's responsibility to disclose this relationship, failure to do so could result in being declared non- responsive. Business Relationship Applicable (request form) Business Relati nship NOT A l'cable 4 Disadvantaged Business Enterprise (DBE) proposer? If yes, please attach a current certificate. Yes I " I No ALL PROPOSALS MUST BE. EXECUTED BYANAUTHORIZED AUTHORITY OF THE PROPOSER WITNESSED AND SEALED (IFAPPLIr_ ARC F) Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Company Name (Name printed or typed) Richard L. Morris Authorized Representative Name (primed or typed) ii Senior Divisional Counsel Authorized Represe Title Utrimed or typed) o'//Z__ Authorized Representative's Signature K• sa 4.j (Afrtx t'orsntate §cdN, if Abplicabtej Karen Rozak, Administrative Assist4rol ' a� Witnessed/Attested by: (Witness/Secretary.- '}(•jv"yifdifortyped) Witness/Secretary Signatu Any blank spaces on the form(s), qualifying notes or exceptions, counter offers, lack of required submittals, or signatures, on County's Form may result in the submission being declared non -responsive by the County. �sit$i� te n R0Z o.. . ,QTA� w ` • w A • RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) 1/18/2018 Detail by FEI/EIN Number DIVISION OF CORPORATIONS "'j r!�r ,r�i:. ,,,, ',arts "j J i:ur.flt �. • i, rt: Department of State / Dkisim 4LCorporatiorls / Search Records / D 11 By Document Number / Detail by FEVEIN Number Foreign Profit Corporation INTERGRAPH CORPORATION -CAD SYSTEMS Cross Reference Name INTERGRAPH CORPORATION Filing Information Document Number P05699 FEI/EIN Number 63-0573222 Date Filed 04/17/1985 State DE Status ACTIVE Last Event CORPORATE MERGER Event Date Filed 12/30/1994 Event Effective Date NONE Principal Address 305 INTERGRAPH WAY MADISON, AL 35758-7567 Changed: 04/22/2015 Mailing Address 305 INTERGRAPH WAY 1 NORTH - TAX MADISON, AL 35758-7567 Changed: 04/22/2015 Re ig stered Agent Name & Address THE PRENTICE-HALL CORPORATION SYSTEM, INC. 1201 HAYS STREET SUITE 105 TALLAHASSEE, FL 32301 Name Changed: 07/22/1996 Address Changed: 07/22/1996 Officer/Director Detail Name & Address I Title President, CEO, Director hftp://search. sunbiz. org/Inquiry/CorporationSearch/SearchResultDetail?inquirylype=FeiNumber&directionType=Initial&searchNameOrder=630573222... 1 /3 1 /18/2018 Detail by FE ON Number COST, STEVEN 305 INTERGRAPH WAY MADISON, AL 35758-7567 Title S ZANA, ANTHONY P 305 INTERGRAPH WAY MADISON, AL 35758-7567 Title Asst. Secretary Menke, Brian M 305 INTERGRAPH WAY MADISON, AL 35758-7567 Annual Reports Report Year Filed Date 2015 04/22/2015 2016 03/31 /2016 2017 03/28/2017 Document Images 03/28/2017 —ANNUAL REPORT View image in PDF format 03/31/2016 — ANNUAL REPORT View image in PDF format 04/22/2015 — ANNUAL REPORT View image in PDF format 03/03/2014 -- ANNUAL REPORT View image in PDF format 03/25/2013 -- ANNUAL REPORT View image in PDF format (14/2012012 — ANNUAL REPORT View image in PDF format 04/12 011 -- ANNUAL REPORT View image in PDF format 0,3/29/2010 -- ANNUAL REPORT View image in PDF format 04/15/2009 -- ANNUAL REPORT 04/09/2008 — ANNUAL REPORT 0411912007 -- ANNUAL REPORT 05/0112006 -- ANNUAL REPORT 05/02/2005 -- ANNUAL REPORT 03/22/2004 — ANNUAL REPORT 04/07/2003 -- ANNUAL REPORT 04124/2002. -- ANNUAL REPORT 03/08/2001 -- ANNUAL REPORT 0510212000--ANNUAL REPORT g412111999 -- ANNUAL REPORT 04/15/1998 -- ANNUAL REPORT 04/30/1997 — ANNUAL REPORT 05/01/1996 -- ANNUAL REPORT 04/1111995 — ANNUAL REPORT View image in PDF format View image in PDF format View image in PDF format l View image in PDF format View image in PDF format View image in PDF format View image in PDF format View image in PDF format View image in PDF forma View image in PDF format A View image in PDF format View image in PDF format J View image in PDF format A View image in PDF format View image in PDF forma http://search.sunbiz.org/Inquiry/CorporationSearch]SearchResultDetail?inquirytype=Fe!Number&di rectionType=l nitial&search NameOrder=630573222... 2/3 Form ]a —Proposal Form (not applicable for CCNA solicitations) LEE COUNT" SOUTHWEST FLORIDA Lee County Procurement Management PROPOSALFORM Company Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Solicitation # RFP180081LKD soucnauon Name: uom user Hiaea uis atcn rce iacemeni ana Hssociaiea inierraces Having care u y examine a erms an on i ions , and the "Lietailed Specifications", all of which are contained herein, propose to furnish the following, which meet these specifications. From Notice to Proceed or Purchase Order date, whichever applies, 335 calendar days to substantial completion, 30 calendar days to final completion (estimated timeline 365 total calendar days.) Proposal to be based on this timeline. The county reserves the right to negotiate with awarded vendor. Draw Schedule based on the following: 1 Project Management Plan Acceptance: 80% of line item #1 2 Installation: 80% of line item #2 3 Training: 80% of line item #3 4 Go -Live: 80% of line item # 4 5 Final Acceptance: 20% of line item 1-4. 100% of line item #5 For evaluation purposes "To Be Determined" or "ranges of price" are not acceptable entries. If a firm rice is not provided zero POITITS will De earned for this evaluation category. Item # Description Unit o Measure Total Cost 1 Project Management Plan Acceptance Lump Sum $ Included in 5a 2 Installation (tabs 2-11) Lump Sum $ Included in 5a 3 Training and Support (tabs 12 & 14) Lump Sum $ Included in 5a 4 Go -Live Lump Sum $ Included in 5a 5 Final Acceptance Lump Sum $ Included in 5a 5a Project Services Lump Sum $ $1 353 257 5b Project Software Lump Sum $ $1,164,401 6 Sub -Total (line items 1-5) $2,517,659 Tabs referenced on Proposal Form refer to Excel Document "Functional Specs" Alternate: 7 Hourly Rate for Additional Services Hourly $ N/A 8 Support and Maintenance Year 1 Annually $ 12-month warranty period included in base purchase price and begins at sub -system cutover to live operations 9 Support and Maintenance Year 2 Annually $ $259,636 15-Proposal Form 1 of 3 Company Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Solicitation # RFP180081LK ) Solicitation Name: Computer Aided Dispatch Replacement and Associated Interfaces 10 Support and Maintenance Year 3 Annually $ $272,618 11 Support and Maintenance Year 4 Annually $ $286,249 12 Support and Maintenance Year 5 Annually $ $300,561 13 Support and Maintenance Year 6 Annually $ $315,589 14 Support and Maintenance Year 7 Annually $ $331,368 15 Support and Maintenance Year 8 Annually $ $347,936 16 Support and Maintenance Year 9 Annually $ $365,333 17 Support and Maintenance Year 10 Annually $ $383,600 18 Software Updates Year 1 Annually $ Refer to Pricing Note 8 19 Software Updates Year 2 Annually $ Refer to Pricing Note 8 20 Software Updates Year 3 Annually $ Refer to Pricing Note 8 21 Software Updates Year 4 Annually $ Refer to Pricing Note 8 22 Software Updates Year 5 Annually $ Refer to Pricing Note 8 23 Software Updates Year 6 Annually $ Refer to Pricing Note 8 24 Software Updates Year 7 Annually $ Refer to Pricing Note 8 25 Software Updates Year 8 Annually $ Refer to Pricing Note 8 26 Software Updates Year 9 Annually $ Refer to Pricing Note 8 27 Software Updates Year 10 Annually $ Refer to Pricing Note 8 28 Sub -Total (items 7-27) $ $2,862,890 Grand Total items 6+28 $ $5,380,549 Grand Total Five million three hundred eighty thousand five hundred forty-nine dollars Form Note: 1. Line 5a & 5b were added to represent project services and project software, Hexagon does not price at the task level Pricing Notes: 1. Customer is responsible for the purchase, installation, and configuration of all required hardware. 2. Hexagon requires remote access to the customer's servers to complete this effort as quoted. 15-Proposal Form 2 of 3 Company Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Solicitation # RFP180081LKD Solicitation Name: Computer Aided Dispatch Replacement and Associated Interfaces 3. An overall system discount has been provided for this opportunity. Changes to scope of the final contract may change the discount amount. Also, any credits given for line items as part of a Change Order will include a reduction for the line prorated amount of the one-time system discount. Items removed after contract signing will result in a contract credit for future Intergraph software and services being established, not a contract reduction. This discount is based on the acceptance of Hexagon's standard Terms and Conditions. 4. Pricing is valid for 180 days from date of submission. 5. Sales tax is not included in this quote. Final sales tax billed will reflect the applicable tax rates at time of sale as required by law. 6. All Intergraph Products have first year warranty included in SW purchase price; warranty period starts at cut over to live operations 7. Test/Training Interfaces are dependent on the ability of each external system to support interface connectivity for the Test Environment. Due to the fact that the Test Environment does not bear the client load of the Production Environment, load balancing in the Test Environment is not necessary. 8. Regarding Form 1a line items 18 through 27, software updates are included as part of the proposed maintenance. Services to implement the updates are quoted at the time of request. Software updates are made available for software products for which maintenance has been purchased under and subject to Hexagon's maintenance agreement. These updates contain information on the version overview, usability and interoperability feature enhancements, any licensing/distribution updates, and links to additional information and resources. We respectfully request further dialogue regarding future upgrades for the Hexagon solution before a scope of work for the upgrades can be established. Hexagon would like to discuss options that are tailored to the County's final solution architecture. Pending the final architecture of the solution and an established, mutually agreed upon scope of work, Hexagon can provide a quote for an upgrade. We look forward to the opportunity to devise a plan moving forward to address the County's concerns for future budgetary planning and requirements. 15-Proposal Form 3 of 3 Required form I c Minimum Requirements Table (form may be expanded or duplicated as needed) Proposer Name: Intergraph Corporation Relevant Projects: Provide (prefer minimum of 3), similar in scope projects within the last 5 years. Provide a client completed Form 3 reference response for each of the projects referenced. (Additional projects and letters of recommendation may also be attached) Were any projects, within the past five years, completed more than two months beyond the initial scheduled time? (if yes, attach a statement of explanation) X yes No Projec"Owner Manatee County 911 Summary of Project Scope: Name: Project Address: 2101 47th Terrace E . Existing customer with I/CAD upgrade within the last 5 years • Population of 351,746 and 743 sq. miles Bradenton, FL 34203 Project IT Manager —Ms. Anne Chance Representative: I/Dispatcher, I/MDT, (200) MPS Units, Ani-Ali, I/ Tracker, I/PTT, I/Page, I/NetViewer, I/Fire Station Representative 941-749-3500 ext 8107 Telephone: Alerting, I/ FRMS (Fire Records), EdgeFrontier ASAP to PSAP Representative anne.chance(a�mymanatee.org E-Mail: • The project was extended due to issues regarding Records Percentage Completed by: 100 % by Proposer %bysub- 0 Management and the I/CAD cutover was delayed. contractor(s) Project Cost: Initial $ Call Customer Directly Final Project Schedule: Planned 365 days ale ndar days) Actual 480 days (calendardays) Project Detail (virtual CAD, Disaster recovery, move er) Virtual CAD, Disaster Recovery Project/Owner Name: Project Address: Project Representative Representative Telephone: San Diego Police Department sum 1401 Broadway, MS 746 San Diego, CA 92101 Program Manager Mr. Chris Haley • 619-531-2401 Representative chaley@pd.sandiego.gov E-Mail: F entage Completed by 100 % by Sub- 0 by Proposer Contractor(s) Project Cost: Initial )4.2Milllon Final $4.7 million Project Schedule: Planned 660 days (calmdardays) Actual 660 days (calendardays) Project detail (virtual CAD, Disaster recovery, Virtual CAD, Disaster moveup/cover) Recovery RFP170457 Computer Aided Dispatch System (CAD) Of New customer within 5 years that has cutover and currently live Population of 1381 million and 372.4 sq. miles I/Dispatcher, I/MDT, (400) MPS Units, Ani-Ali, I/ Informer — CAL State Suites, Nested Queries, Pre- defined queries/favorites, I/Tracker, I/PTT, I/Page, I/ NetViewer and Business Intelligence Premium. EdgeFrontier custom interfaces to key third -parties such as Omega Dashboard, ARJIS, AutoReturns, Records/ Missing Alerts, CRMS, and PENotify The City of San Diego issued a purchase order dated 12/24/2015 During the Planning phase, the selected Cutover day was October 17, 2017 Customer went live on October 17, 2017 as planned Proposer Name: Intergraph Corporation Project/Owner Name: Salt Lake Valley Emergency Communications Center summary of Project scope: • New customer undergoing implementation within the Project Address: 5360 South Ridge Drive West Valley City, UT 84118 last 5 years Project Representative: Executive Director Mr. John Morgan • Population of 1.092 million and 807 sq. miles Representative • I/Dispatcher, I/MDT, (630) MPS Units, Ani-Ali, I/ Telephone: 801-554-0437 Tracker, I/PTT, I/Pa e I/NetViewer, I/NetDis atcher, I/ g p Representative CADLink, I/Fire Station Alerting, I/ FRMS (Fire jmorgan(aDvecc9-1-1 .com Records), EdgeFrontier custom interfaces to third -parties E-Mail: • The Comity of Salt Lake issued a purchase order dated Percentage Completed by 100 M by Sub- 0 8/12/2016 by Proposer Contractor(s) • During the Planning phase, the selected Cutover day is 3/19/2018 Project Cost: Initial $ 6 million Final $ 6.1 million • Customer still undergoing implementation Project Schedule: Planned 575 days (calendar days) Actual N/A (calendardays) Project detail (virtual CAD, Virtual CAD, Disaster Disaster recovery, moveup/cover) Recovery Project/Owner Name: Summary of Project Scope: Project Address: Project Representative: Representative Telephone: Representative E-Mail: Percentage Completed by % by Sub- by Proposer Contractor(s) Project Cost: Initial S Final $ Project Schedule: Planned (calendar days) Actual (calendar days) Project detail (WrtuaicnD, Disaster recovery, move up/cover) Proposed Project Team: (proposed for this Lee County project) Name Years Experience Project Director Refer to Proposal Response Section 1 - Qualifications of Company (Management) Proiect ManaEer Refer to Proposal Response Section 1 - Oualifications of Companv RFP170457 Computer Aided Dispatch System (CAD) 4 Ver 06/08/2017-3 Form 2 — Affidavit Certification of Immigration Lcnvs AFFIDAVIT CERTIFICATION IMMIGRATION LAWS .; LEE COUNTY SOUTHWEST FLORIDA SOLICITATION NO.: RFP180081LKD SOLICITATION NAME: Computer Aided Dispatch Replacement & Associated Interfaces (CAD) LEE COUNTY WILL NOT INTENTIONALLY AWARD COUNTY CONTRACTS TO ANY CONTRACTOR WHO KNOWINGLY EMPLOYS UNAUTHORIZED ALIEN WORKERS, CONSTITUTING A VIOLATION OF THE EMPLOYMENT PROVISIONS CONTAINED IN 8 U.S.C. SECTION 1324 a(e) f SECTION 274A(e) OF THE IMMIGRATION AND NATIONALITY ACT ("INA"). LEE COUNTY MAY CONSIDER THE EMPLOYMENT BY ANY CONTRACTOR OF UNAUTHORIZED ALIENS A VIOLATION OF SECTION 274A(e) OF THE INA. SUCH VIOLATION BY THE RECIPIENT OF THE EMPLOYMENT PROVISIONS CONTAINED IN SECTION 274A(e) OF THE INA SHALL BE GROUNDS FOR UNILATERAL CANCELLATION OF THE CONTRACT BY LEE COUNTY. PROPOSER ATTESTS THAT THEY ARE FULLY COMPLIANT WITH ALL APPLICABLE IMMIGRATION LAWS (SPECIFICALLY TO THE 1986 IMMIGRATION ACT AND SUBSEQUENT AMENDMENTS). Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Senior Divisional Counsel 02/16/2018 Signature Title Date STATE OF Alabama COUNTY OF Madison The foregoing instrument was signed and acknowledged before me this I today of February 20 18 , by Richard L. Morris who has produced (Print or Ty pe Name) �t 0 0 a as identification. (Type of Identification and Number) Notary Public Sig ature Karen Rozak Printed Name of Notary Public Expires 02/16/2021 Notary Commission Number/Expiration The signee of this Affidavit guarantee, as evidenced by the sworn affidavit required herein, the truth and accuracy of this affidavit to interrogatories hereinafter made. LEE COUNTY RESERVES THE RIGHT TO REQUEST SUPPORTING DOCUMENTATION, AS EVIDENCE OF SERVICES PROVIDED AT ANYTIME. RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form 3 Reference Survey LEE COUNTY Lee County Procurement Management 1 � SOUTHWEST FLORI D A REFERENCE SURVEY Solicitation # RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Section 1 Reference Respondent Information Please return completed form to: FROM: Anne Chance Bidder/Proposer: Intergraph Corporation COMPANY: Manatee County Government Due Date: 2/20/2018 PHONE #: 941-749-3500 x8107 Total # Pages: 1 FAX #: Phone #: 256-529-0929 Fax #: 256-730-8608 EMAIL: Anne.chance@mymanatee.org Bidder/Proposer E-Mail: Allana.williamson hexa onsi.com Section 2 Enter Bidder/Proposer Information, if applicable Similar Performed Project (Bidder/Proposer to enter details of a project performed for above reference respondent) Proposer Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Reference Project Name: Prcj ect Address: Project Cost: AD/MPS Upgrade for consolidated agency 101 47'b Terrace E., Bradenton, FL 34203 Call customer directly Summarize Scope: Virtual CAD Environment; CAD and MPS Software and related CAD interfaces for County PD, Fire, and EMS; 18 dispatchers; 7 Call - Takers; 110 MPS concurrent licenses You as an individual or your company has been given as a reference on the project identified above. Please provide your responses in section 3 below. e ion .3 1 Indicate: es or o 1. Did this company have the proper resources and personnel by which to get the job done? es 2. Were any problems encountered with the company's work performance? No 3. Were any change orders or contract amendments issued, other than ownerinitiated? o 4. Was the job completed on time? Yes 5. Was the job completed within budget? Yes 6. On a scale of one to ten, ten being best, how would you rate the overall work 9 performance, considering professionalism; final product; personnel; resources. Rate from 1 to 10. (10 being highest) 7. If the opportunity were to present itself, would you rehire this company? Yes 8. Please provide any additional comments pertinent to this company and the work performed for you: Hexagon personnel are professional, hardworking, and easy to work with. Section 4 Anne Chance Reference Name (Print) Please submit non -Lee County employees as references Customer prefers to be contacted directly in lieu of providing a signature Reference Signature I*P18008ILKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form 3 Reference Survey Lee County Procurement Management LEE COUNTY S () I i 1 11 W F S f F I. () R 1 0 A REFERLy_CLSuRLU Solicitation # RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Section 1 Reference Respondent Information Please return completed form to: FROM: Robert Harding Bidder/Proposer: Intergraph Corporation COMPANY: Martin County BOCC Due Date: 2/20/2018 PIIONE #: 772-219-4944 Total #Pages: 1 FAX #: Phone #: 256-529-0929 Fax #: 256-730-8608 EMAIL: bharding@martin.fl.us Bidder/Proposer E-Mail: Allana.williamson a)hexa onsi.com Section 2 Enter Bidder/Proposer Information , if applicable Similar Performed Project (Bidder/Proposer to enter details of a project performed for above reference respondent) Proposer Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Reference Project Name: Project Address: Project Cost: Fire CAD and MPS 401 S.E. Monterey Road, Stewart, FL 34996 Call customer directly Summarize Scope: irtualized CAD environment, 60 MPS concurrent licenses, 3 Dispatch seats, Fire only You as an individual or your company has been given as a reference on the project identified above. Please provide your responses in section 3 below. eC lollIndicate: es or o 1. Did this company have the proper resources and personnel by which to get the job done? es 2. Were any problems encountered with the company's work performance? No 3. Were any change orders or contract amendments issued, other than ownerinitiated? o 4. Was the job completed on time? Yes 5. Was the job completed within budget? Yes 6. On a scale of one to ten, ten being best, how would you rate the overall work 8 performance, considering professionalism; final product; personnel; resources. Rate from 1 to 10. (10 being highest) 7. If the opportunity were to present itself, would you rehire this company? Yes 8. Please provide any additional comments pertinent to this company and the work performed for you: The latest project we did with Intergraph/Hexagon was our addition of Mobile for Public Safety and EdgeFrontier. We have been a satisfied user of I/Dispatcher (CAD) since 1992. Section 4 Please submit non -Lee County employees as references RFP 180081 LKD Computer Aided Dispatch Replacement &Associated Interfaces (CAD) Ver 06/08/2017-3 Form 3 Reference Survey I's LEE COUNTY SOUTHWEST FLORI D A Lee County Procurement Management REFERENCE SURVEY Solicitation # RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Section 1 Reference Respondent Information Please return completed form to: FROM: Nancy Paul Bidder/Proposer: Intergraph Corporation COMPANY: Plantation Police Department Due Date: 2/20/2018 PHONE #: 954-797-2702 Total # Pages: 1 FAX #: Phone #: 256-529-0929 Fax #: 256-730-8608 EMAIL: NPaul(Wpsd.plantation.org Bidder/Proposer E-Mail: Allana.williamson-ahexa onsi.com Section 2 Enter Bidder/Proposer Information, if applicable Similar Performed Project (Bidder/Proposer to enter details of a project performed for above reference respondent) Proposer Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Reference Project Nam e: Project Address: Project Cost: CAD/MPS Upgrade for Fire and Police 51 NW 70a' Terrace, Plantation, FL 33317 Call customer directly Smmmarize Scope: Virtual CAD environment, 70 Fire MPS units, 2 Dispatchers/Calltakers You as an individual or your company has been given as a reference on the project identified above. Please provide your responses in section 3 below. eC lon.3 I Indicate: es or o 1. Did this company have the proper resources and personnel by which to get the job done? YES 2. Were any problems encountered with the company's work performance? NO 3. Were any change orders or contract amendments issued, other than ownerinitiated? YES 4. Was the job completed on time? YES 5. Was the job completed within budget? YES 6. On a scale of one to ten, ten being best, how would you rate the overall work g performance, considering professionalism; final product; personnel; resources. Rate from 1 to 10. (10 being highest) 7. If the opportunity were to present itself, would you rehire this company? YES 8. Please provide any additional comments pertinent to this company and the work performed for you: Section 4 Nancy Paul Reference Name (Print) Please submit non -Lee County employees as references Reference Signature RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form 3 Reference Survey lLEE COUNTY SOUTHWEST FLORI D A Lee County Procurement Management REFERENCE SURVEY Solicitation # RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Section 1 Reference Respondent Information Please return completed form to: FROM: Frank L. Ullven Bidder/Proposer: Intergraph Corporation COMPANY: City of St. Petersburg, Police Department Due Date: 2/20/2018 PHONE #: (727) 892-5232 Total # Pages: 1 FAX #: (727) 893-7799 Phone #: 256-529-0929 Fax #: 256-730-8608 EMAIL: Frank.Ullven(&/stpete.org Bidder/Proposer E-Mail: Allana.williamson-ahexa onsi.com Section 2 Enter Bidder/Proposer Information , if applicable Similar Performed Project (Bidder/Proposer to enter details of a project performed for above reference respondent) Proposer Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Reference Project Nam e: Project Address: Project Cost: CAD/MPS for City PD 1300 1st Ave N., St. Petersburg, FL 33705 Call customer directly Smimiarize Scope: 21 dispatchers, 100 MPS concurrent licenses You as an individual or your company has been given as a reference on the project identified above. Please provide your responses in section 3 below. Section a I Indicate: es or o 1. Did this company have the proper resources and personnel by which to get the jobdone? Yes 2. Were any problems encountered with the company's work performance? No 3. Were any change orders or contract amendments issued, other than ownerinitiated? o 4. Was the job completed on time? Yes 5. Was the job completed within budget? Yes 6. On a scale of one to ten, ten being best, how would you rate the overall work 9 performance, considering professionalism; final product; personnel; resources. Rate from 1 to 10. (10 being highest) 7. If the opportunity were to present itself, would you rehire this company? Yes 8. Please provide any additional comments pertinent to this company and the work performed for you: We have had great experiences with their knowledgeable and helpful implementation and support teams. (Section 4 Frank L. Ullven Reference Name (Print) Reference Signature Please submit non -Lee County employees as references RFP18008ILKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form 3 Reference Survey lLEE COUNTY SOUTHWEST FLORI D A Lee County Procurement Management REFERENCE SURVEY Solicitation # RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Section 1 Reference Respondent Information Please return completed form to: FROM: Un Lee Bidder/Proposer: Intergraph Corporation COMPANY: Huntsville -Madison County 911 Due Date: 2/20/2018 PHONE #: 256-722-7345 Total # Pages: 1 FAX #: Phone #: 256-529-0929 Fax #: 256-730-8608 EMAIL: unlee@madco9l Lcom Bidder/Proposer E-Mail: Allana.williamson hexa onsi.com Section 2 Enter Bidder/Proposer Information, if applicable Similar Performed Project (Bidder/Proposer to enter details of a project performed for above reference respondent) Proposer Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Reference Project Name: ject Address: Project Cost: AD 9.4 Upgrade P27Oakwood Rd., Huntsville, AL 35806 $230,000 Summarize Scope: Upgrading CAD system from version 9.2 to 9.4 You as an individual or your company has been given as a reference on the project identified above. Please provide your responses in section 3 below. CC ion.3 I Indicate: es or o 1. Did this company have the proper resources and personnel by which to get the job done? es 2. Were any problems encountered with the company's work performance? No 3. Were any change orders or contract amendments issued, other than ownerinitiated? o 4. Was the job completed on time? Yes 5. Was the job completed within budget? Yes 6. On a scale of one to ten, ten being best, how would you rate the overall work 10 performance, considering professionalism; final product; personnel; resources. Rate from 1 to 10. (10 being highest) 7. If the opportunity were to present itself, would you rehire this company? Yes 8. Please provide any additional comments pertinent to this company and the work performed for you: Over 25 years we have depended on Hexagon CAD system, they have proven to be reliable, flexible and scalable through numerous challenges. (Section 4 Un Lee Reference Name (Print) Customer prefers to be contacted directly in lieu of providing a signature Reference Signature Please submit non -Lee County employees as references RFP18008ILKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form 3 Reference Survey lLEE COUNTY SOUTHWEST FLORI D A Lee County Procurement Management REFERENCE SURVEY Solicitation # RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Section 1 Reference Respondent Information Please return completed form to: FROM: Charlie McNichol Bidder/Proposer: Intergraph Corporation COMPANY: Mobile County Communications District Due Date: 2/20/2018 PHONE #: 251-639-2360 Total # Pages: 1 FAX #: 251-639-2370 Phone #: 256-529-0929 Fax #: 256-730-8608 EMAIL: cmcnichol@mccd911.com • Bidder/Proposer E-Mail: Allana.williamson ,hexa onsi.com Section 2 Enter Bidder/Proposer Information , if applicable Similar Performed Project (Bidder/Proposer to enter details of a project performed for above reference respondent) Proposer Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Reference Project Name: Project Address: Project Cost Consolidated dispatch agency for County -wide Fire, 7340 Ziegler Blvd., Mobile, AL 36608 Call customer directly County -wide EMS, City PD and SO Summarize Scope: Currently on CAD 9.2 and soon to upgrade to CAD 9.4; 200 MPS users; using I/Page, I/Fire Station Alerting, I/Fire Station Printing, BI Direct You as an individual or your company has been given as a reference on the project identified above. Please provide your responses in section 3 below. CC ion . Indicate: es or o 1. Did this company have the proper resources and personnel by which to get the job done? es 2. Were any problems encountered with the company's work performance? No 3. Were any change orders or contract amendments issued, other than ownerinitiated? o 4. Was the job completed on time? Yes 5. Was the job completed within budget? Yes 6. On a scale of one to ten, ten being best, how would you rate the overall work 10 performance, considering professionalism; final product; personnel; resources. Rate from 1 to 10. (10 being highest) 7. If the opportunity were to present itself, would you rehire this company? es 8. Please provide any additional comments pertinent to this company and the work performed for you: (Section 4 Charlie McNichol Reference Name (Print) QSL�� 1 v'[.74 Reference Signature Please submit non -Lee County employees as references RFP18008ILKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Ver 06/08/2017-3 Form 3 Reference Survey lLEE COUNTY SOUTHWEST FLORI D A Lee County Procurement Management REFERENCE SURVEY Solicitation # RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) Section 1 Reference Respondent Information Please return completed form to: FROM: Alan Campbell Bidder/Proposer: Intergraph Corporation COMPANY: Shelby County 911 Due Date: 2/20/2018 PHONE #: 205-439-6911 Total # Pages: 1 FAX #: 205-439-6927 Phone #: 256-529-0929 Fax #: 256-730-8608 EMAIL: acampbell(&/shelby9l Lorg Bidder/Proposer E-Mail: Allana.williamson(a-),hexa onsi.com Section 2 Enter Bidder/Proposer Information , if applicable Similar Performed Project (Bidder/Proposer to enter details of a project performed for above reference respondent) Proposer Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Reference Project Name: ject Address: Project Cost: CAD/MPS PO4County Services Drive, Pelham, AL 35124 Call customer directly Smimiarize Scope: Virtual CAD environment, 11 dispatchers, approximately 10 remote dispatchers, 36 MPS concurrent licenses for PD, Fire, and EMS You as an individual or your company has been given as a reference on the project identified above. Please provide your responses in section 3 below. SectionSectiona I Indicate: es or o 1. Did this company have the proper resources and personnel by which to get the job done? Yes 2. Were any problems encountered with the company's work performance? No 3. Were any change orders or contract amendments issued, other than ownerinitiated? o 4. Was the job completed on time? Yes 5. Was the job completed within budget? Yes 6. On a scale of one to ten, ten being best, how would you rate the overall work g performance, considering professionalism; final product; personnel; resources. Rate from 1 to 10. (10 being highest) 7. If the opportunity were to present itself, would you rehire this company? Yes 8. Please provide any additional comments pertinent to this company and the work performed for you: (Section 4 Alan D. Campbell Reference Name (Print) Please submit non -Lee County employees as references RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) J m r O O W N m 0 N N N N o M m e d v d� d tD m ry dl N oS .A d� d .A ts E co co co co m m u�Oi co co � H � o m v O N r o m c c o k c -o °o E `o E Q S `o w QE o N m U c o .E t -° E - c E N m ¢ o or o.� °'o o.E m Em °m _= 3 ry o f m 'E `o c m ma-°` c c�ULY c� ¢ U m= c c c o~� O m `m S'� Z' '� ¢ c 9a o c N= E E "' `o L o �' T E __ ow E= E o E EU ° °m °-°`o E❑ €O �¢ -of ° UFO 4 Uy o. a=t9� a m W. N Q o Um m 007 Ow U �= Q a Um o Y U� o UU .N Q� m -"°° OF o Y U� r N H� m m UU Eo U� o U� o o=~ UQ o ❑mod S- o �� OQ A E EEE.E .E .E .E .EE m EE N E EE .E m E .E N E O' NI RR m mn C t0 N W E N W W u�i u�i a N ry M C c N M W E o r t0 E N O O O O — o o j W o o — c° O O o E vEE-E cm °E IL _ n WEE o o m r°'iE aci W NE c E E o 'E N _ N m0 _ N �? C N N 6 C C tp r No. N E n YMl 6 N N W m U U _ o o❑ -2 °� ° N d ° o � O LL m 'o c01i u uo o E m m 0 rm o 0 o._ m 0 rm 0 0 o._ y °r°.L°. _ u, m m o a 2_ U m m a m o mE u_ °1 o N u y a` c 0 J ol T N N I. O T o. � a N O N I. I. "O O o. NC 1 a o ° rNWi T yNj N M T 'NO ° T "NO O v IS o. N O N T W C (aOW (O C C V M N d C N N t0 C N tp N C 10 G J o O w lz 10 - .. ol a a U m a J Q J LL o J 0 0 p J 0 c m a U o - o m c U o m o o c a m 01- t mo S -O m r " :n N. 'r " - c c c 3 o a` aJ m a U iq y m` y U o z U O iq iq a z m U m o m 0 mo o 0 U ° a a °--' c -mo a A c U c c Jo _ O n o E _ m o o o. o c .o c U c'o U — N ° o m A c ° .x 3 '> m .o a ° o m c c a c U Jo - U U c o o .'10-' oo _ o z aJ m a in E in E U o U T U - m c ° _ a` '°° U _ m m `o 0 0 o r T n o r T n m a x 'c `° c c r � m 0 N 3 E ,F o= ° m E 'o m ii o m� a - ° o a `- U U U UO UOO cl z O U O O a iqO mQ y N H J z o m m � oZ �r i E m z C m a O U 4 � O O v 3 a O a b0 T C LL U U a � oq U • rW. •Q QO U LC y • ca cOa .4' s, o • o W a ., ,.; is p m a��i ❑a U 3yy c3 m .O N 7 p W Q 'Cl °•' a U•° F °��° C Q Cc, ¢' .,�`—, •- p to E a o o .y b a G ro o s m a U o o. v i A 4 o G m U 0 ti a o o a�i a U u N O a` U W o . o = cC � ❑U❑ O U V�i M U F � U U tC • � Y� • Si y U pxs� 0 v� o w 0 0 tlu 0 -C,U m u�o v m O M N � y N � M p CD Z O N v O O o O U w o a °� •Y s, ca C. 3 o o U -o � •• o o ,� � y A O N o N � N LL 0 6 C O i0 o L U U C. N 13 U ~ 0 0 � � � � cc�CC O .� �',� ,O � a N O o •„�_,� c� F N c� •� � � ,� � � �, o a�i � � � — '_" � 0 "d m o > ai u n ca .-. > Lam' i '0 • � a °� '� to ' � .° -6 o 0 o N � o °` U 'o � N a°'i � � � o ° ,� � � oN ca `� o b > ° a m a. O o l m cd a u B o o w [ �°�° w 3 w o Ao p w m o o a t4 o Q cn U so, °-0 s >, >,>, Lam. W o W �� .P '� W sue. O %„ a� a o m S m O cd U .�-� U .�-� .°° ca a o z o }}++ m '' C CI O o m o a� O m CU .p Q O ,�`�„ O N >C N ca O U o W o 'S N W` '0 0 0.i F 0' .., o m o to 0 3 o 0 0 0 0 0 -o o u •� p o C7 o p o 0 0 0 0 F o C7 .. C7 o s, s, s. C7 sip•, 4 0 0• "' O p o a�i o xt ro � U 2 o y 3 O s o 0 •� yy.�. .a 'C p '� � .O p O N w '� y a❑osi y�� F CJ o U WUw ¢� U A O f7 0 Ut�P.UU pN �•o � 'ozNO " w U w ou �w �b o > o y� 0 0 o N S N N NY�i U � � p to z R w U U w W 0 U 0 U C Y• p U U o w p -t� o m p w t 'ia ca r to o � Id I'd¢ o'o oo� o u _ O U � GU is o y ❑ C sue, y 'O O p o�o .� a P3 J� ws.° L) cd .o °o .0 ^oo 0 m C QI v T cu `° of 0 3 m E c N a) N -p Y 0 C ? m C c U Y O 0 o f Y�0 p > N 0 O U ° E mN v �o 3 ° a E c o o Oa a o E as c E a a) y a s c a `o m c a m 0 Y N +S O y C a _ . 0 o_O °-00 0 c m t m¢ a Q cu O 0 Q +� T L w c N 0 v 0 0 3 3 w j a) s 00 a T O 7 ^ O t t O '0 + Ea to o E E Ln y c S O v u O p y 0 N -0 00 m C c a) U N m 00 f0 y J N c 6 Y 6 w L d C L o Q � N m Y E E O O O ° N W muE So T 0 a v 0 0 Y N a) m u .0 O O N t 3 m> w N a E al c ° p u a) c U b0 T T cu a) a @ ~ O c EE m 0 u as O z v v c c y c o a 0 E 0 o f O F -cv m v p c c E v -oo a w °O a d a .m c ° 0 a s 7 O m 0 m C2 T ' *' E Q N Z p 2 Y v z � m u Z -0 c c E Q @ ° m o3 v Nm@° v° c .0 0 w c ° ^ E Q E O ° c Y m O v v o c — 0 > ° N -0 u v: T E v a v 'Q a O, C '6 O 'O m u c m c a) v 0 .. Q c -O m h E m E a) U E a N° E 7 m m a v w z a, m e E v a c a m° O `p m 0 cv f° m �- 2N N u a E a s a V er 06/08/2017-3 Form 5 - Affidavit Principal Place of Business AFFIDAVIT PRINCIPAL PLACE OF BUSINESS LEE COUNTY SOUTHWEST FLORIDA Instructions: Please complete all information that is applicable to your firm Company Name: Intergraph Corporation d/b/a Hexagon Safety & Infrastructure Richard L. Morris Printed name of authorized signer Au[hnnr. Signature Senior Divisional Counsel Datc a 1&11% The signee of this Affidavit guarantee, as evidenced by the sworn affidavit required herein, the truth and accuracy of this affidavit to interrogatories hereinafter made. LEE COUNTY RESERVES THE RIGHT TO REQUEST SUPPORTING DOCUMENTATION, AS EVIDENCE OF SERVICES PROVIDED. AT ANYTIME. Notary: Karen Rozak State of Alabama County of Madison The foregoing instrument was signed and acknowledged before me this day of February 20 18 by Richard L. Morris 10 and number � Ww Notary Public Signature 1. Principal place of business is located within the boundaries of: Local Business Tax License # 2. Address of Principal Place of Business: 3. Number of years at this location 4. Have you provided goods or services to Lee County on a regular basis within the past 3 consecutive years 5. Number of available employees for this contract 6. Does your company have a Drug Free Workplace Policy who has produced as identification (or persona I�yteMq r rr .`a.•••••°� `'• • �`! ` • N/A - Expires 02/16/2021 • • IBM - Notary Commission Number and expiration w U800 Lee County •. s�9 ••...•..•••�,P�� �r;, Collier County ,, ,T''``,�� X Non -Local N/A 305 Intergraph Way, Madison, AL 35758 48 years *If yes, attach contractual history for _Yes* X No past 3 consecutive years _ U.S. Hexagon Safety & Infrastructure - 1,018 X Yes No RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) w iv o nc v =wCOO z zw U ^� C q ¢ z i O o u ' ."i :a C y ¢ O U n O v a o •Q i Q z 3 0 y � Q z z O Q z V er 06/08/2017-3 Form 7: Public Entity Crime Forin Page 1 of 2 This form must be signed and sworn to in the presence of a notary public or other officer authorized to administer oaths. This sworn statement is submitted to Lee County, FL (Print name of the public entity) by Richard L. Morris, Senior Divisional Counsel (Print individual's name and title) for Intergraph Corporation d/b/a Hexagon Safety & Infrastructure (Print name of entity submitting sworn statement) whose business address is 305 Intergraph Way, Madison, AL 35758 (If applicable) its Federal Employer Identification Number (FEIN) is 63-0573222 (If the entity has no FEIN, include the Social Security Number of the individual signing this sworn statement: On the attached sheet.) Required as per IRS Form W-9. 2. I understand that a "public entity crime" as defined in Paragraph 287.133(1) (g), Florida Statutes, means a violation of any state or federal law by a person with respect to and directly related to the transaction of business with any public entity or with an agency or political subdivision of any other state or with the United States, including but not limited to, and bid or contract for goods or services to be provided to any public entity or agency or political subdivision or any other state or of the Unites States, and involving antitrust, fraud, theft, bribery, collusion, racketeering, conspiracy, or material misrepresentation. I understate that "convicted" or "conviction" as defined in Paragraph 287.133(1) (b), Florida Statutes, means a finding of guilt or a conviction of a public entity crime, with or without an adjudication of guilt, in any federal or state trial court of record relating to charges brought by indictment or information after July 1, 1989, as a result of a jury verdict, nonjury trial, or entry of a plea of guilty or nolo contendere. 4. I understand that "affiliate" as defined in Paragraph 287.133(1)(a), Florida Statutes, means: 1. A predecessor or successor of a person convicted of a public entity crime: or: 2. An entity under the control of any natural person who is active in the management of the entity and who has been convicted of a public entity crime. The term "affiliate" includes those offices, directors, executives, partners, shareholders, employees, members and agents who are active in the management of the affiliate. The ownership by one person of shares constituting a controlling interest in another person, or a pooling of equipment or income among persons when not fair market value under an arm's length agreement, shall be a facie case that one person controls another person. A person who knowingly enters into a joint venture with a person who has been convicted of a public entity crime in Florida during the preceding 36 months shall be considered an affiliate. 5. I understand that a "person" as defined in Paragraph 287.133(1) (c), Florida Statutes. means any natural person or entity organized under the laws of any state or of the United States with the legal power to enter a binding contract and which bids or applies to bid on contracts for the provision of goods or services let by a public entity, or which otherwise transacts or applies to transact business with a public entity. The term "person" includes those officers, directors, executives, partners, shareholders, employees, members, and agents who are active in management of the entity. 6. Based on information and belief, the statement which I have marked below is true in relation to the entity submitting those sworn statement. (Please indicate which statement applies.) X Neither the entity submitted this sworn statement, nor any officers, directors, executives, partners, shareholders, employees, members, and agents who are active in management of an entity nor affiliate of the entity have been charged with and convicted of a public entity crime subsequent to July 1, 1989. RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) V er %/OW017-3 Public Entity Critne Form Page 2 of 2 The entity submitting this sworn statement, or one or more of the officers, directors, executives, partners, shareholders, employees, member, or agents who are active in management of the entity, or an affiliate of the entity have been charged with and convicted of a public entity crime subsequent to July 1, 1989. The entity submitting this sworn statement, or one or more of its officers, directors, executives, partners, shareholders, employees, member, or agents who are active in management of the entity, or an affiliate of the entity has been charged with and convicted of a public entity crime subsequent to July 1, 1989. However, there has been subsequent proceeding before a Hearing Officer of the State of Florida, Division of Administrative Hearing and the Final Order entered by the Hearing Officer determined that it was not in the public interest to place the entity submitting this sworn statement on the convicted vendor list. (Attach a copy of the final order) I UNDERSTAND THAT THE SUBMISSION OF THIS FORM TO THE CONTRACTING OFFICER FOR THE PUBLIC ENTITY IDENTIFIED IN PARAGRAPH 1 (ONE) ABOVE IS FOR THAT PUBLIC ENTITY ONLY AND, THAT THIS FORM IS VALID THROUGH DECEMBER 31 OF THE CALENDAR YEAR IN WHICH IS FILED. I ALSO UNDERSTAND THAT I AM REQUIRED TO INFORM THE PUBLIC ENTITY PRIOR TO ENTERING INTO A CONTRACT IN EXCESS OF THE THRESHOLD AMOUNT PROVIDED IN SECTION 287.017, FLORIDA TUTES, FOR CATEGORY TWO OR ANY CHANGE IN THE INFORMATION CONTAINED IN THIS FO STATE OF Alabama COUNTY OF Madison (Signature) a.l I& I Is (Date) PERSONALLY APPEARED BEFORE ME, the undersigned authority, Richard L. Morris (Name of individual signing) who, after first being sworn by me, affixed his/her signature in the space provided above on this day of February , 2 018 . (NOTARY P LIC) My Commission Expires: 02/16/2021 �.•` yen RO,> .i. aOTA�p�, + w � ~ • owe— • r q STATS P •• 41111a11'A RFP180081LKD Computer Aided Dispatch Replacement & Associated Interfaces (CAD) HEXAGON -'1NTERGRAPH SAFETY & INFRASTRUCTURE TAB 7 - CASE STUDIES HEXAGON SAFETY & INFRASTRUCTURE CASE STUDY _ FR E D E R I C K► Connecting Data & Agencies with EdgeFrontier° Consolidating and centralizing 911 call -taking and dispatch services is a COUNTY growing trend among governments in the U.S. It saves tax dollars for other MARYLAND initiatives, fosters inter-agencycommunication,andeliminates duplicate services. Yet for all the benefits, consolidation comes with challenges. United States With disparate information systems from multiple agencies, the biggest hurdles facing centralized communications centers are data integration and accuracy. When minutes count and lives are at stake, having the abilityto quickly collect and route emergency incident information to first responders is critically important. One agency using innovation to address these data challenges is Frederick County, Maryland's Division of Emergency Management. Serving 12 incorporated municipalities and three federal installations in suburban Washington, D.C., the division's Emergency Communications Center is a busy dispatch operation. Working around the clock, the center supports emergency and non -emergency dispatching needs for all federal, state, county, and municipal agencies within the county. The center also works closely with neighboringjurisdictions, providing mutual aid to eight counties and four states. "Each agency we serve has different incident data needs and different information systems," said Jack Markey, director of emergency management, Frederick County. "Our biggest challenge was finding the data we needed in our CAD database and then accurately translatingthat information into data schemas, workflows, and interfaces that other agencies could use. And when those agencies' information needs changed, it was very difficult to create and fund custom code development." To better serve public safety agencies and citizens across Frederick County, leaders at the emergency management division identified the need to implement a data integration and workflow solution.The solution had to be intuitive enough for non -technical personnel to use with minimal training. BETTER DATA EXCHANGE In a consolidated and centralized dispatch operation, emergency and non -emergency call volumes are high. In an average year, the Frederick County Emergency Communications Center receives more than 400,000 calls and dispatches federal, state, county, and municipal agencies to more than 300,000 incidents, using Hexagon Safety & Infrastructure's Intergraph° Computer -Aided Dispatch (I/CAD) and mobile solutions. Frederick County selected Hexagon to help the center achieve even more efficient data sharing by synchronizing computer -aided dispatch (CAD) information exchanges and workflows across multiple information systems operated by different agencies within the county. Using Hexagon's EdgeFrontier°, an integration platform that enables rapid, affordable interface development tailored to the needs of an organization, and CAD Connect for EdgeFrontier, a pre -built interface for I/CAD, the communications center is able to quickly query and accurately translate call data from its CAD system into a data structure other agencies' information systems can understand. "With EdgeFrontier and CAD Connect, the hard work is already done for you," said Markey. "It makes searching for and selecting CAD data easier, it translates the data for you, and then sends that data to the applications you've designated; it really is as simple as deciding what data you want to send and where you want to send it." CONFIGURABLE WORKFLOWS & NOTIFICATIONS The communications center is responsible for more than just routing and dispatching emergency and non - emergency calls; it is also responsible for gathering other relevant public safety information and pushing out notifications to agencies it serves. With EdgeFrontier, the communications center is able to create special workflows by call type and location. Notifications are sent automatically to agencies that have requested them, based on predefined parameters. EdgeFrontier also allows dispatchers to notify and post active 911 events to emergency operations applications; road closure events to intelligent transportation systems, geographical information systems and public web portals; storm damage events to local utility providers; and severe weather warnings to dispatch groups.The center has the flexibility to push notifications on a one -to -many, one -to -several, or one-to-one basis. " Every public safety agency should be using EdgeFrontier." 2 1 CASE STUDY Frederick County, Maryland "With our specific workflows and different notifications, we're able to have greater situational awareness for all of the areas our agencies are responsible for," said Markey. "With all of the different federal, state, county, and municipal agencies in the area, having this capability has helped de -conflict different public safety interests and jurisdictions, improving operational efficiency and response" REDUCED COST & COMPLEXITY Developing and maintaining custom, point-to-point interfaces can be time consuming, costly, and risky. They can become quickly incompatible and out-of-date as new versions of software and databases are released. With EdgeFrontier, the communications center has minimized or eliminated custom software code and created interfaces that are configurable, adaptable, and reusable. Because of its compatibility with the center's existing I/CAD, EdgeFrontier reduces the total cost of ownership for I/CAD and interfaces and eases the upgrade processes when new versions of I/CAD are released. "Interoperability starts with people, but it's enabled by technology. It's one thing to want to share data. It's another thing to be able to actually do it in a cost- effective, secure, and efficient way," said Markey. Because EdgeFrontier is accessible and usable by non -technical division personnel, the agency can develop workflows and interfaces at its own pace — without having to manage large and costly development projects. In fact, technical managers from the center and divisional IT staff were quickly up and running with EdgeFrontier after a single training session. "Every public safety agency should be using EdgeFrontier," said Markey. "Before implementing it, there were always data integration and information workflow projects that we wanted to do, but we could never cost -justify bringing in a developer. Now we have the flexibility, frameworks, and power to develop custom data fields, interfaces, and workflows all on our own." About Hexagon Safety & Infrastructure Hexagon Safety & Infrastructure provides mission -critical and business -critical solutions to governments and service providers. A global leader, proven innovator, and trusted partner, our software and industry expertise help improve the lives of millions of people through safer communities, better public services, and more reliable infrastructure. Visit hexagon safetyinfrastructure.com. Hexagon Safety & Infrastructure is part of Hexagon (Nasdaq Stockholm: HEXAB; hexagon.com), a leading global provider of information technologies that drive productivity and quality across geospatial and industrial enterprise applications. ©^017Inter graph Corporation o'/b/o Hexagon Safety & Infrastructure. Hexagon Safety & Infrastructure is part of Hexagon. All rights reserveo'. Hexagon Safety & Infrastructure and the Hexagon Safety & Infrastructure logo are trademarks and Intergraph and Eage Frontier ore registered trademarks of Hexagon or its subsidiaries in the Uniteo'States anoin other countries. 1/17 HEXAGON SAFETY & INFRASTRUCTURE CASE STUDY _ UTTAR India's Largest Emergency Response System PRA D ES H Uttar Pradesh Police is the largest police force in India and among the largest in the world, with 250,000 police officers in 75 districts. The organization POLICE serves a largely rural population of more than 220 million spread across 243,000 square kilometers. India Previously, police response activities were organized at the district level. Districts had separate public safety answering points and different control rooms for urban and rural areas. Only four cities were served by computer - aided dispatch (CAD) systems. Often, citizens would visit the local police station to report incidents. "Each district had different levels of service because they were managed by different people, software, and processes," said Additional Director General of Police Anil Agarwal. "Over a period of time, local cultures developed, which lead to differentiation in the standards of service provided to citizens" Since there was no standardized, coordinated system in place to ensure timely response, Uttar Pradesh Police set out to revolutionize public safety through UP 100, a comprehensive response system that would serve the needs of the entire state. LAYING A FIRM FOUNDATION Uttar Pradesh Police officials were very clear from the beginning that UP 100 would only feature best -in -class technologies. Central to the project would be a scalable and reliable incident management system — one that was already proven in the field by a large number of agencies and users. "We looked at the best systems in the world when we were desigring our system,"said Agarwal."Our requirements were easily one of the most comprehensive" Three major systems integrators responded to the request for proposals, and each one included Hexagon Safety & Infrastructure as the vendor to best meet the police force's CAD requirements. A team led by M ah i nd ra Defence Systems Limited, featuring Hexagon Safety & Infrastructure and its Intergraph° Computer -Aided Dispatch (I/CAD) suite, was selected for UP 100. The police force established a centralized communications center in the capital, Lucknow, to receive all calls for service and dispatch responders directly from across the state. Police also set up a disaster recovery center in Bangalore and two mirrored operational centers at Noida and Allahabad, which operate at 15 percent capacity of the main facility. In addition to the core call -taking and dispatching applications, Hexagon deployed applications for district supervisors and field officers, including Hexagon's Intergraph Mobile Responder° add, which provides mobile dispatching functionality on smartphones and tablets. Hexagon also developed other applications, such as a patrol management application and a citizen mobile app. Because of shortcomings in state digital mapping, the citizen add allows users to register important locations and contacts to aid responders. All We believe what we have done here is worth a look for any police organization that wants to upgrade its own operations." "The CAD system allows you to see all the registered points of interest of the citizen who has registered with the police. When the call lands at the communication officers' desks, and if the person says,'There is a problem at my parents' house,' he doesn't have to explain anything else. The communication officer simply picks the location that is already registered by the user, and then the help is provided.You are saving practically two minutes of time," said Agarwal. Hexagon also configured I/CAD user interfaces in English and Hindi, to aid system usability and acceptability. "This hasn't been done before," said AgarwaL "This is probablythe first time we have an entire CAD, end -to -end, being done in a bilingual manner.This has been an extremely important feature for us" Since only three percent of the state was mapped in a geographic information system, police also undertook a massive digital mapping exercise to support the response system. More than 11,500 police officers contributed, creating more than three million points of reference. 21 CASE STUDY Uttar Pradesh Police TRANSFORMING PUBLIC SAFETY Equipped with these innovations, 250 call -takers — all civilian, women communication officers — use I/CAD to collect information from landline and mobile calls, VoIP, SMS, e-mail, social media, and the mobile application. Citizens can upload pictures, texts, and videos. Call -takers support all dialects of Hindi, other major Indian languages, English, and even some foreign languages (thanks to the use of language volunteers, whose availability is noted in the system). Those with special needs can connect through video calls where sign language interpreters transcribe their concerns. All voice calls are recorded for future reference, and all issues are documented automatically, which creates a detailed digital trail of activities. Call -takers create events in the system and transfer this information to 150 police dispatchers who dispatch the nearest police response vehicles and also inform the local police station. The UP 100 center controls a police fleet that will ultimately include 3,200 cars and 1,600 motorcycles. Police have a targeted 15-minute response time in city areas and 20 minutes in rural areas. The police response vehicles attend to victims, isolate crime scenes, and then hand over the scenes to local police stations for further action. About 500 detailed standard operating procedures (SOP) have been laid out for different situations, aimed at standardization of services across geographical areas. This process eliminates from consideration local police resource constraints or discretion. " This is probably the first time we have an entire CAD, end -to -end, being done in a bilingual manner." "This is a huge step in terms of our transparency and accountability to the citizens," said Agarwal. IMPROVING RESPONSE The. UP 100 system is empowering in many ways. Most fundamentally, it is citizen -centric. It is designed to ensure citizens receive service in an impartial manner The proof of its success is in the results. Before UP 100, police received around 3,500 calls per day across the 250 call -takers — all civilian, women communication officers — use I/CAD to collect information from landline and mobile calls, VoIP, SMS, e-mail, social media, and the mobile application. entire state. Now call volume is about 100,000 per day, and police expect it to greatly expand as the system becomes more familiar to citizens. During the Hoh celebration, police handled more than 25,000 incidents in a day, and more than 50,000 calls over three days. Before, we were not in a position to help those who were needing our services," said Raghvendra Dwivedi, state radio officer, Uttar Pradesh Police. "Now, technology has helped us serve more people. Technology has made us accountable and transparent." Rural areas are benefitting the most, where response times have been cut in half. Citing examples of three -to five-minute response times in urban areas to prevent attempted suicides and murders and 15-minute responses deep in rural areas, Agarwal said, "That is the kind of penetration and awareness we have been able to achieve. This is marvelous, tremendously satisfying." Because of these successes, the system has proven its worth internally as well, among district supervisors, some of whom initially expressed reservations. "Now, if I ask any district chief of police whether I should take away this system, he won't accept this. It has becomes an essential part of the police organization at the district level," said Agarwal. EXPANDING CAPABILITIES Moving forward, Uttar Pradesh Police plan to leverage the wealth of data now available for crime and incident analysis to further improve operational efficiency and 31 CASE STUDY Uttar Pradesh Police The organization will also integrate fire and ambulance services into the system, as well as traffic management. citizen safety. The organization will also integrate fire and ambulance services into the system, as well as "In terms of the complexity of the technology traffic management. implementation, the scale, and the size, UP 100 is now already the role model," said Agarwal. "We hope to "We'll provide mobile data terminals (MDT) to fire replicate the same system across many states yet to stations, and we'll define an SOP for fire- related migrate to a modern policing system. We believe what we events," said Dwivedi. `Whenever a fire event comes to have done here is worth a look for any police organization us, we'll dispatch that event directly to the M DT, and that wants to upgrade its own operations." we'll ensure accountability and transparency for fire - related issues also." With the system generating such positive results for Uttar Pradesh, other state officials in India are looking to UP 100 as an example to follow. About Hexagon Safety & Infrastructure Hexagon Safety & Infrastructure provides mission -critical and business -critical solutions to governments and service providers. A global leader, proven innovator, and trusted partner, our software and industry expertise help improve the lives of millions of people through safer communities, better public services, and more reliable infrastructure. Visit hexagon safetyinfrastructure.com. Hexagon Safety & Infrastructure is part of Hexagon (Nasdaq Stockholm: HEXAB; hexagon.com), a leading global provider of information technologies that drive productivity and quality across geospatial and industrial enterprise applications. ©^017Inter graph Corporation o'/b/o Hexagon Safety & Infrastructure. Hexagon Safety & Infrastructure is part of Hexagon. All rights reserveo'. Hexagon Safety & Infrastructure and the Hexagon Safety & I nfrastructure logo are trademarks and Intergraph and Intergraph Mobile Responder registered trademarks of Hexagon or its subsidiaries in the United States onoin othercountries. 7117 HEXAGON SAFETY & INFRASTRUCTURE SWISS BORDER 0jo. A Safe Choice for Switzerland CASE STUDY _ Counterfeit identity documents, drug and custom offenses, stolen vehicles, and illegal GUARD immigration arejust some of the challenges facingthe Swiss Border Guard,the largest Switzerland national civil security agency in Switzerland. An armed and uniformed corps, the Border Guard protects national borders and enforces a multitude of laws, acts, and conventions to ensure the safety and security of the Swiss public. As part of the Swiss Federal Customs Administration, the Swiss Border Guard fulfills an extensive range of tasks, including prevention, intervention, and suppression in customs and migrations matters. It works closely with the cantons of Switzerland and Frontex, the European border and coast guard agency, to provide vital support for Swiss and Schengen Area safety measures at national borders, airports, railway stations, and during international operations. On an average day, Border Guard officers discover up to 55 Swiss customs and/or VAT regulation violations, detect 40 offenses against immigration and asylum laws, apprehend 40 wanted persons, and seize 7 pounds of drugs and 5 forged documents. The Border Guard's operational environment has drastically changed in recent years, creating new demands that require a more closely linked operational structure to enable effective cooperation with partnering organizations. The abilityto coordinate responders over wide distances and deploy resources is increasingly important as emergency personnel become more mobile. A study on behalf of the Swiss Federal Customs Administration predicted Border Guard operational efficiency could increase with a new IT system. As a result of these findings, the Swiss Border Guard selected Hexagon Safety & Infrastructure's integrated suite of public safety solutions for its new command support and incident management system to improve coordination between personnel, better exploit digital information, and meet new and ever-increasing challenges. CLOSER COORDINATION FOR BETTER RESPONSE The Swiss Border Guard implemented Hexagon's industry -leading incident management software - Intergraph" Computer -Aided Dispatch (I/CAD) - at its four command and control centers in three different linguistic and cultural regions. I/CAD enhances geographical flexibility during the strategic planning of patrols. Used in 26 workstations by 100 users, the I/CAD system integrates with approximately 1,000 automated vehicle location devices and personnel trackers, 2,000 digital radio devices, and several hundred cameras.The four command and control centers expect to create 50,000 events and perform one million data queries each year with the new system. 66 Hexagon's solutions provide us with a common operational picture for the Border Guard's entire operational area:' Border Guard command staff stay up to date on the current location of all available field personnel via a highly topical common operational picture provided by Hexagon's incident command system application, Intergraph Planning & Response. This application promotes fast, well-informed decision -making. During major incidents and events, Intergraph Planning & Response enables the centralized management of all available resources. With this comprehensive, integrated system, unified operational information can be quickly shared to keep personnel updated at all times. "Hexagon's solutions provide us with a common operational picture for the Border Guard's entire operational area," said Jurg Noth, vice director of the Swiss Federal Customs Administration and head of the Swiss Border Guard. "The four command and control centers in three linguistic regions — German, French, Italian — can now optimally support the demanding tasks carried out by the Swiss Federal Customs Administration" AN INTEGRATED SYSTEM FOR GREATER EFFICIENCY Hexagon's software supports diverse aspects of the Swiss Border Guard's resource planning and command center cooperation. An example is the automated display of traffic cameras. If a wanted vehicle is caught on camera anywhere, it is displayed in I/CAD, allowing the operator to promptly create an event and manage resources in real time from a single interface. This procedure is similar for alarms triggered by other detection systems, and enables faster investigations and issuing of warrants. The synchronized systems improve the management of incoming alerts, lower processing time, and free up About Hexagon Safety & Infrastructure resources for new operations. At the same time, I/CAD provides additional users, such as emergency services and supervisors, with an up-to-date operational picture via a web viewer. Moving forward, more departments of the Swiss Federal Customs Administration will be integrated into the solution, which will improve planning processes across the federal agency. Integrating these teams will greatly enhance the command and control centers' ability to respond, and continue to boost the Swiss Border Guard's efficiency overtime. Hexagon Safety & Infrastructure provides mission -critical and business -critical solutions to governments and service providers. A global leader, proven innovator, and trusted partner, our software and industry expertise help improve the lives of millions of people through safer communities, better public services, and more reliable infrastructure. Visit hexagonsafetyinfrastructure.com. Hexagon Safety & Infrastructure is part of Hexagon (Nasdaq Stockholm: HEXAB; hexagon.com), a leading global provider of information technologies that drive productivity and quality across geospatial and industrial enterprise applications. OO 2017 I nt=_igraph Coroo ration d/b/o Hexagon Safety &Infrastructure. Hexagon Safety & I nfrastructure is part of Hexagon. All rights reserved. Hexagon Safety & Infrastructure and the Hexagon Safety & Infrastructure Logo are trademarks and Intergraph a registered trademarkofHexagon or its subsidiaries in the United States and in other countries. linage courtesy of Eidgenossische Z.entrolverwaltung EZV 8117 CASE STUDY _ HEXAGON SAFETY & INFRASTRUCTURE ' ZIVILSCHUTZ PROTEZ/ONE CIVILE PRUTEZION ZIVILA CIVIL 00.Rescue is Routine in the Alpine Region The Autonomous Province of Bolzano — South Tyrol is Italy's northernmost PROTECTION province, with 520,000 citizens. Located in the Alps, South Tyrol is popular with AGENCY families and outdoor enthusiasts. "In an emergency, both citizens and tourists must be able to rely on fast and efficient assistance," said Rudolf Pollinger, head of South Tyrol's Civil Protection Autonomous Province of Bolzano — South Tyrol, Italy Agency. "It is therefore crucial for response to be flawlessly coordinated: To meet that need, public safety agencies in South Tyrol rely on Intergraph° Computer -Aided Dispatch (I/CAD), Hexagon Safety & Infrastructure's industry - leading incident management software. INTEGRATED COMMAND & CONTROL The Civil Protection Agency's Regional Emergency Call Center leverages I/CAD to centrally dispatch first responders from its command and control center in Bolzano. Dispatchers at eight seats process about 130,000 calls and 66,000 incidents per year, supporting the Bolzano Professional Fire Brigade and numerous other fire and rescue services. "With I/CAD, the South Tyrolean rescue forces and the fire brigades can put the complex nationwide alarm plans into action and arrive at the event location within the specified time limit of ten minutes," said Markus Rauch, deputy director of the Department of Civil Protection at the Civil Protection Agency. The list of responding personnel, equipment, and vehicles is extensive. It includes 140 firefighters from the Bclzano Professional Fire Brigade; 306 voluntary fire brigades with 16,000 members; three company fire brigades; 55 mountain rescue squads from the Alpine Club South Tyrol and the National Alpine and Cave Rescue Corps; seven emergency response physicians; four water rescue services; four search dog squads; and two helicopters. The White Cross Rescue Association of South Tyrol also relies on a separate installation of I/CAD that exchanges incident data with the Civil Protection Agency's system via interfaces. The state rescue association dispatches 36 White Cross and Italian Red Cross ambulances from its own control center, with nine dispatcher seats handling about 150,000 calls and 125,000 incidents each year. HIGH QUALITY & QUICK ACTION I/CAD allows dispatchers to quickly locate the incident site and create an event in the system. They then alert the nearest and most suitable personnel according to pre -defined plans to ensure quick response. Incident guidelines also support standardized and transparent decision-making.The organizations involved benefit from the joint deployment of I/CAD, saving resources and enabling smooth operations. " With I/CAD, the South Tyrolean rescue forces and the fire brigades can put the complex nationwide alarm plans into action." "A shared server for data storage and provisioning reduces costs, while the ability to coordinate information and response within the same system ensures civil protection tasks are carried out efficiently," said Rauch. "All systems are configured with redundancyto ensure continuous availability." ADAPTABLE TO CHANGES Buildingfrom this successful foundation, the Civil Protection Agency worked with Hexagon and Frequentis to upgrade and expand its integrated command and control center. The upgrade features state-of-the-art I P technologythat exploits the full potential of digital radios, while a bilingual user interface permits dispatchers to work in German or Italian. The entire range of fully integrated software from Hexagon and Frequentis is implemented on avirtual platform to reduce hardware requirements and support business functions. The new IP-based solution equips the province's emergency services with tools to face future challenges, such as the establishment of 112 as the national standard emergency call number for Italy.The systems can also adapt to operational changes within the integrated command and control center. About Hexagon Safety & Infrastructure Hexagon Safety & Infrastructure provides mission -critical and business -critical solutions to governments and service providers. A global leader, proven innovator, and trusted partner, our software and industry expertise help improve the lives of millions of people through safer communities, better public services, and more reliable infrastructure. Visit hexagon safetyinfrastructure.com. Hexagon Safety & Infrastructure is part of Hexagon (Nasdaq Stockholm: HEXAB; hexagon.com), a leading global provider of information technologies that drive productivity and quality across geospatial and industrial enterprise applications. ©^017Inter graph Corporation o'/b/o Hexagon Safety & Infrastructure. Hexagon Safety & Infrastructure is part of Hexagon. All rights reserveo'. 1,exogon Safety & Infrastructure and the Hexagon Safety & I nfrostructure logo are trade. morks and Intergraph a registered troo'emark of L exagon or its subsidiaries in the UniteoStates ano' in other countries. 8117 HEXAGON SAFETY & INFRASTRUCTURE CASE STUDY _ OFFICE OF Hexagon Safety & Infrastructure Mobile Dispatch Extends Incident Management to District's UNIFIED First Responders COMMUNICATIONS Washington, D.C:s Office of Unified Communications (OUC) is tasked with call -taking, dispatching, radio communications, and first responder U ) l(OUC) command -and -control functions from the Unified Communications Center (UCC).The UCC, which opened in 2006, is one of the nation's premier call centers Washington, D.C., USA and emergency response facilities, encompassingthe Metropolitan Police Department (MPD), Fire and Emergency Medical Services (FEMS), and other public services.This consolidation of personnel, equipment, and technology has enhanced coordination among the numerous municipal and federal public safety entities operating in Washington, D.C. Already a long-time user of Hexagon Safety & Infrastructure's Computer -Aided Dispatch (CAD), the District had other legacy mobile applications, with limited functionality, and was searching for a true enterprise mobile solution. Mobile communications and automatic vehicle location (AVL) were not seamlessly integrated with CAD, and required separate logins for each application layer. This method also resulted in wireless communications bills from several companies each month, which was not cost-effective. The OUC needed a mobile solution that would not only streamline the process with a single login and simplified billing, but also improve response by providing first responders with access to the same geographically aware, map -based interface dispatchers have in the command center. a" OVERCOMING CHALLENGES • Implement an all -encompassing mobile dispatch solution that would consolidate mobile applications for police, fire, and emergency medical responders • Give first responders access to the same intelligent map -based interface, routing capabilities, geographical positioning system (GPS), and other tools dispatchers use in the command center • Provide a more effective means of communication between first responders and dispatchers, and among first responders in the field • Improve efficiency and save costs by providing a single application for all mobile dispatch operations REALIZING RESULTS The OUC's successful history with its Hexagon CAD solution played a major part in its choice of Hexagon's mobile technology. Hexagon's mobile solution is seamlessly integrated with CAD, which enables dispatchers and first responders to share the same intelligent map -based interface. This was an important consideration for the UCC, whose goal is to ensure timely and accurate communications for fast and appropriate response. With the help of Hexagon's support team, including an Hexagon resident engineer, the OUC began its implementation with the District's fire and emergency medical services.The mobile solution is now fully deployed in fire and emergency medical vehicles, and the process is underway at the MPD. A well -planned schedule of around -the -clock installation, training, and practice is in place to ensure all officers are trained on the system, while access to the legacy system is still available to officers who have not yet been trained. Accord i ng to OUC chief technology officer Teddy Kavaleri, "The OUC is already experiencing benefits from [Hexagon's] mobile solution. Field officer productivity has increased and radio traffic has been reduced.The incorporation of an improved graphic map with District -supplied spatial features, such as building footprints, alleys, sidewalks, etc., provides a mobile map, resulting in greater situational awareness. AVL, along with better field communications, helps officers easily locate one another and assist officers in distress. Plus, self-service lookup of license tags and location -of -interest information is readily available without intervention from the communications center." The mobile system has already demonstrated its success in the District's challenging public safety environment. For example, Hexagon's CAD and mobile technologies successfully managed a record influx of nearly 10,000 calls associated with the inauguration of United States President Barack Obama. During the event, mobile technology extended incident management capabilities to remote field and mobile units stationed near the event area. Bydoingthis, response time was reduced as dispatchers were able to swiftly deploy field personnel on foot and bike. Officers have responded favorably to the new capabilities. "[Hexagon's] mobile solution improves the relationship between the dispatcher and the first responder, because they're literally looking at the same page," says James Callahan, OUC CAD manager. "It also provides another avenue for responders to talk to one another. We've received a lot of positive feedback from the field." 21CASE STUDY UCC MOVING FORWARD The OUC will continue to upgrade its Hexagon software as appropriate to ensure field officers gain the benefits of new features and enhancements as they become available. " [Hexagon's] mobile solution improves the relationship between the dispatcher and the first responder, because they're literally looking at the same page. " About Hexagon Safety & Infrastructure Hexagon Safety & Infrastructure provides mission -critical and business -critical solutions to governments and service providers. A global leader, proven innovator, and trusted partner, our software and industry expertise help improve the lives of millions of people through safer communities, better public services, and more reliable infrastructure. Visit hexagon safetyinfrastructure.com. Hexagon Safety & Infrastructure is part of Hexagon (Nasdaq Stockholm: HEXAB; hexagon.com), a leading global provider of information technologies that drive quality and productivity improvements across geospatial and industrial enterprise applications. ©^015Inter graph Corporation o'/b/o Hexagon Sotety & Infrastructure. Hexagon Safety & Infrastructure is part of Hexagon. All rights reserveo'. Hexagon Safety & Infrastructure and the Hexagon Safety & I nfrostructure logo are trade. marks of Hexagon or its subsidiaries in the UniteoStates and in othereountries. 11/15 HEXAGON SAFETY & INFRASTRUCTURE LOUISVILLE JEFFERSON COUNTY M ETROSAFE Louisville Metro Area, Kentucky, USA CASE STUDY _ Louisville Metro Area Achieves Regional Public Safety Interoperability In 2003,the City of Louisville, Kentucky, and Jefferson County were merged into one, becoming Lou isvilleJefferson County Metro, one of the largest cities in America by population. Given the urgent immediate homeland security and daily operational need to develop interoperabilityfor the Metro's first responders, Mayor Jerry Abramson formally introduced an initiative to create "MetroSafe," a unified communications system for all emergency response agencies in the community, including police, fire, EMS, the health department, local hospitals, and others. When Louisville Jefferson County Metro merged governments, it had nine separate dispatch centers covering the community, each with its own different radio frequencies. After merging four of the dispatch centers in 2005, MetroSafe opened a state-of-the-art consolidated communications center to handle dispatch for Louisville Metro Police, Louisville Fire & Rescue, and Metro EMS. The need for a single dispatch system soon became apparent, as there was no compatibility between the three agencies' computer -aided dispatch (CAD) systems. This prevented the agencies from talking to each other, even when they responded to the same scenes. The new system needed to support a large number of agencies while allowing each to maintain its own unique emergency response procedures. It also had to offerthe flexibilityto integrate communications with other organizations outside of MetroSafe. In addition, the new CAD had to be GIS-based and provide compatibility with in -vehicle mobile solutions and records management functionality. OVERCOMING CHALLENGES Implement an interoperable CAD system that would serve as a unified communications system for all emergency response agencies in the community Enhance coordination of joint responses within the Metro area • Maintain each agency's unique emergency response procedures REALIZING RESULTS After interviewing CAD users representing several large public safety operations, MetroSafe selected Hexagon Safety & Infrastructure's Intergraph CAD system based on its capabilities and Hexagon's excellent track record with large CAD implementations. Currently, Intergraph CAD is successfully handling all911 calls for Louisville Metro Police, Louisville Metro Emergency Medical Services, Louisville Metro Fire Department, and 18 suburban fire districts. Less than six months after implementation of the new unified Intergraph CAD system, MetroSafe was experiencing interoperability and improved coordination amongthe major public safety agencies responsible for the greater Louisville Metro area. For the first time, all Louisville Metro 911 call -takers and emergency dispatchers work on a unified computer system that allows each to "see" the responding and available police, fire, and EMS units simultaneously and manage the emergency response accordingly. The most significant enhancements in operations relate to the speed and efficiency with which emergency calls are now routed to the appropriate responders. Anothervital capability of Intergraph CAD is it has been programmed with the response procedures for each individual agency. For instance, one fire and rescue department may send an ambulance and a truck to every injury call, while another may dispatch only the ambulance. This enables the CAD to make a response recommendation to the appropriate dispatcher based on protocol. Ultimately, the dispatcher decides which resources to send to the scene. Call -takers, dispatchers, and personnel in the field agree that the GIS-based 'map -centric' nature of the new system has been a huge leap forward in efficiency compared with the older text -based CADS. Dispatchers no longer have to know every street and alley in the city. The map shows them the incident location. In addition, the map helps the dispatchers visualize where their crews are at any given time. Out on the streets, Louisville police officers, fire crews, and emergency medical technicians have seen a positive impact from the new CAD system as well. Specifically, they have more information at their fingertips. Hexagon has equipped 600 emergency vehicles with its I/Mobile application that runs on mobile data terminals (VDTs) right in the cab.The I/Mobile package interfaces directly with Intergraph CAD to displaythe CAD map, incident location, and call details onscreen for the crews to review en route. This minimizes radio chatter by showing the driver the best route to the scene and providing a textual synopsis of all details recorded by the call -taker. At It's a streamlined, team - oriented approach to emergency communications that will speed our response and save more lives. " 21 CASE STUDY Lou isvi Ile Jefferson County MetroSafe Plans are being made to equip another 800-1 200 emergency vehicles with the MDTs,alreadyequipped with built-in G PS for automatic veh icle tracking (AVL). Local fire and EMS agencies are now making plans to activate the AVL functionality in the near future, which will send vehicle status and location information wirelesslyto the CAD. "With this investment, we're putting the'one' in 911," Louisville Mayor Jerry Abramson said. "For the first time, your emergency call comes into one place, you deal with one call -taker and your information is relayed through one computer system that all our emergency dispatchers can use to help you. It's a streamlined, team -oriented approach to emergency communications that will speed our response and save more lives" MOVING FORWARD On a pilot basis, MetroSafe has implemented Hexagon's I/LEADS records management system with a Citrix server to extend reporting and data capture capabilities to officers in the field. In the interest of enhanced efficiency, MetroSafe has asked Hexagon to integrate a resource management module from Deccan International into the CAD, enabling it to continuously monitor the allocation of available emergency vehicles and personnel across Louisville. Additionally, Intergraph CAD has become the centerpiece of a pilot project occurring in the Louisville Emergency Operations Center. MetroSafe can establish emergency response plans and contingency strategies in advance and assign responsibilities to participating agencies, even those only temporarily on scene. With interoperability among participating Louisville Metro agencies achieved, the next step is to take advantage of the new CAD's flexibility to extend access to other organizations outside of MetroSafe, including public safety access points (PSAPs) in surrounding counties. Talks are under way to integrate some aspects of their communications and dispatching operations into the central CAD so their emergency activities can be monitored in Louisville as needed, especially in the case of a regional event. About Hexagon Safety & Infrastructure Hexagon Safety & Infrastructure provides mission -critical and business -critical solutions to governments and service providers. A global leader, proven innovator, and trusted partner, our software and industry expertise help improve the lives of millions of people through safer communities, better public services, and more reliable infrastructure. Visit hexagon safetyinfrastructure.com. Hexagon Safety & Infrastructure is part of Hexagon (Nasdaq Stockholm: HEXAB; hexagon.com), a leading global provider of information technologies that drive quality and productivity improvements across geospatial and industrial enterprise applications. ©^016Inter graph Corporation o'/b/o Hexagon Safety & Infrastructure. Hexagon Safety& Infrastructure is part of Hexagon. Ali rights reserveo'. Hexagon Safety & Infrastructure and the Hexagon Safety & I nfrostructure Logo are trade. marks of Hexagon or its subsidiaries in the UniteoStates and in othereountries. 1/16 PDF Page 1 HEXAG�]UN ELEE COUNTY, FL INTERGRApH RFP FOR CAD REPLACEMENT RESPONSES TO RFP180081 LKD CAD EVALUATION 2 QUESTIONS Ownership: 1. The language below is identified as required contractual language. Specifically acknowledge you have no issues complying. - All County related information/data such as records, notes, computer files, data bases, reports, etc. specifically prepared, developed, or managed by the PROVIDER (referred to as "materials' is the property of the COUNTY and shall be subject to confidentiality obligations set forth in this agreement (Needs to be defined as part of overall agreement). - In the event of a dispute regarding payment the parties shall negotiate in good faith to resolve. Under no circumstances shall the PROVIDER withhold access to any materials so as to adversely affect the COUNTY or any of the COUNTY'S operations. - Upon completion or termination of the Agreement, all of the above materials to the extent requested by the COUNTY, shall be delivered to the COUNTY or to any subsequent provider within to (10) calendar days in a format acceptable to the COUNTY (or subsequent provider) and when multiple acceptable formats exist agreed between the parties. The PROVIDER shall deliver these materials at no additional cost or expense to the COUNTY to allow the COUNTY to conduct operations uninterrupted and to be available for general access and reporting going forward. -Where possible the PROVIDER shall deliver the materials in a non-proprietary format. If unavoidable to supply in a proprietary format, then a perpetual license shall be granted by the PROVIDER to the COUNTY to access and use, and report on the County's materials. - The PROVIDER, at its expense, can make and retain copies of all materials only as permitted and required by law. The PROVIDER shall at all times remain subject to confidentiality obligations set forth in this agreement (or other governing agreement) Hexagon acknowledges the provisions within section 1 (Ownership) and will comply with them. 1; PDF Page 2 HEXAGON SAFETY& INFRASTRUCTURE Responses to RFP180081 LKD CAD Evaluation 2 Questions Intearation: 2. Briefly describe high-level architectural vision of how the CAD solution integrates with P25, NG-911, ATMS (DOT), other public works solutions (i.e. street lighting) Integration with P25: For the P25 radio system, integration is dependent on the radio system vendor. Hexagon supports a Push to Talk interface (Hexagon's I/PTT) to the Motorola MCC 7500 Protocol version 7.15. Hexagon also supports an interface to the Harris Radio Symphony and MaestrolP systems. I/PTT is used to communicate with the radio system and interfaces with the CAD system's Banner application, which has three message lists that are enabled by default: I/Informer messages (for queries) Radio messages sent from I/PTT Crew Status changes from I/Mobile Data Terminal (I/MDT As messages are received, they are added to the dialog box display and are scrolled when necessary to ensure that the latest messages are visible. I/MDT and I/PTT are included in Hexagon's base pricing, and I/Informer is included in pricing options. The County can configure the Banner dialog box to scroll either vertically or horizontally. You can also configure the maximum number of messages stored in the message list as well as filter talk groups. Informer Radia I Additionally for P25 radio integration, Hexagon has software products that will read GPS information from Motorola P25 and Harris P25 systems and use it for tracking individuals as part of Person -Level Tracking (PLT). It is an EdgeFrontier based product known as ASTRO 25 and requires a separate instance of I/Tracker. Hexagon has included both items in base pricing. Integration with NG-911 telephony support, For NG-911 CAD support, many of the requirements are for the Radio and Telephony system. The NG- 911 CAD requirements have not been finalized. Rest assured, Hexagon is monitoring the progress of these requirements. NG-911 integration for 911 calls and Text is dependent on the telephony system the County is using. Please reference Q&A #3 for detailed information regarding Text-to-9-1-1. Integration with ATMS (DOT) and public works solutions Hexagon has extensive interface experience with DOT and advanced traffic control devices. For over 5 years, Palm Beach County Fire has been live with a bi-directional interface to Naztec/TrafficWare, which communicates Hexagon CAD and mobile routing data with traffic signals to ensure consistent green lights for a dispatched Fire unit. PDF Page 3 HEXAGON. SAFETY& INFRASTRUCTURE Responses to RFP180081 LKD CAD Evaluation 2 Questions In addition to traffic control, New York State Police interfaces Hexagon CAD with the New York Department of Transportation. Since go -live in 2010, this bi-directional interface allows DOT to instantly create events in NY State Police CAD for tow truck removal of traffic obstructions. With a daily commuter population increase of over 1.5 million people, the interface is responsible for alleviating major traffic events safely and efficiently for continuous flow of rush hour traffic, saving the city and surrounding areas extensive time and money. For ATMS (DOT) and other public works solutions integration, Hexagon has proposed our EdgeFrontier product and consulting services to discuss the County's interface design for Econolite - Automated Traffic Management System (ATMS). Hexagon and the County will collaborate on specific functionality during the design phase of the overall project and a formal scope of work and level of effort will be provided for the County's consideration. Hexagon is excited about the prospect of designing an ATMS interface unique to Lee County's desired results. 3. Briefly describe the ability to integrate/use of text messages (ICIS Message and SMS text from citizens) into the system. Hexagon has two paths the County may take for Text-to-9-1-1. The first path relies solely on the telephony provider to handle the text conversation. Sarasota County and Manatee County currently receive and respond to text messages with this approach. With West/Intrado, the text conversation is handled through VIPER 911 (A9C). The Dispatcher creates an event in I/CAD and adds remarks as necessary regarding the texts, but the actual text conversation remains archived on the West system. The second path is an integrated solution using Intergraph Communications Controller (ICC), but is not currently proposed. ICC is a call control solution where the existing telephone software application is replaced with ICC to handle routine telephony tasks such as answering, holding, transfer, directory features, and integrated text-to-9-1-1 call handling. This solution is currently only compatible with the West/Intrado VIPER telephone system and requires the use of an A9C and services from West (not currently proposed). A secondary option to this second path is to implement Intergraph Communications Controller Text Only which is a paired down feature set limited to handling Text-to-9-1-1 callers only. This option is still a West/Intrado only solution which requires services and hardware from West/Intrado (not currently proposed). Data Transfer: 4. How is the data within the proposed solution stored? All data the I/CAD system uses to function (static data) and all data the I/CAD system creates through its use (dynamic data) is stored in the I/CAD SQL Server 2016 Enterprise Edition database. 5. And does the proposed solution allow for ad -hoc queries of the data contained within the CAD system? Yes, the proposed CAD and Mobile solution allows for ad -hoc queries of the data contained within the CAD system. Using SQL Server Management Studio or the Hexagon application, CAD Query Tool, ad - hoc queries may be run against the I/CAD database. Hexagon cautions Customers to not run ad -hoc queries against the production database unless necessary. Running queries against the archive database is the preferred method for non -Hexagon applications to access I/CAD data. 6. Is text to 911 supported or what else must be implemented to support text to 911? Please refer to Q&A #3. 1; PDF Page 4 HEXAGON. SAFETY& INFRASTRUCTURE Responses to RFP180081 LKD CAD Evaluation 2 Questions 7. Are photo and video capture supported? Yes, I/CAD supports the ability to store photo and video files. These files can be received via the I/CAD 'Send Message' function, which is included as part of the proposed solution. Once the file is at the workstation, it can be attached to an event and it is stored in the I/CAD database. Mobile for Public Safety (MPS) also supports the ability to attach photos and video files. Additionally, the location of fixed security cameras can be displayed as map icons on the CAD map. Hexagon has proposed the I/Sight server and Video Responder client allowing video feed to be retrieved from a camera icon on the map. The solution requires that a video plug-in is built for the camera system and available for the Hexagon products to access. This proposal includes integration with one video management system (VMS) of the County's choosing; any additional VMS would require additional scope and price. 8. How does the proposed solution interface with social media? Social media, such as Twitter and Facebook, are untapped resources for a wealth of Public Safety - relevant data and intel. Hexagon has proposed our integration toolkit, EdgeFrontier and EdgeFrontier Developer Training, for Lee County to build their own desired social media interfaces quickly and easily to I/CAD. With the EdgeFrontier Developer kit, Hexagon puts the power of interface development in the hands of Lee County to minimize vendor services and creatively and uniquely interface agencies with the County's citizens via social media. Should the County prefer Hexagon to write the interface instead, Hexagon is happy to discuss further. 9. Briefly describe the technical implementation of the proposed solution (on -premises, cloud based, specific hardware requirements) and service level commitments (including high availability approach). Hexagon's proposed CAD and Mobile solution is an on -premises solution. Specific non-proprietary hardware and software requirements for the proposed solution are noted in the attached system configuration diagram, Lee County, FL Configuration_2-16-2018 (pages 11 through 19 of this PDF). Hexagon has proposed the use of SQL Server AlwaysOn Availability Groups to provide high availability and disaster recovery for the I/CAD database. AlwaysOn is an Enterprise Edition feature that provides server -based replication of the primary database to one or more secondary replica databases, automatic failover if the primary database fails, and automatic resynchronization of the former primary after a failover. Hexagon has proposed fully redundant I/CAD Database Servers at the primary site with synchronous replicas for secondary failover at an alternate site to prevent disruption of operations. Licensing: Given the background information (section 2.): For Lee County's convenience for questions 10 through 18, Hexagon has provided summarized pricing for software, services, training, and license counts in the attached Lee County, Price Proposal (Hexagon Pricing Template) (pages 26 through 28 of this PDF). i PDF Page 5 HEXAGON. SAFETY& INFRASTRUCTURE Responses to RFP180081 LKD CAD Evaluation 2 Questions 10. Is licensing based on concurrent users? Yes, the proposed client licenses for Hexagon CAD, Mobile, and I/NetViewer are based on concurrent users. Therefore, a license count is based on the maximum number of users that may be logged on at any given time. Hexagon's concurrent licensing model is a cost-effective approach for user access to CAD for Dispatchers, Call -Takers, and mobile units. By not restricting licenses to workstations, this approach provides flexibility to the County for future growth and will add value for years to come. 11. How many dispatcher licenses are included with this proposal? What is the cost for additional licensing? • (6) Concurrent I/Dispatcher production licenses Current unit pricing for I/Dispatcher in the proposed pricing is $17,716.31 per production license. • (4) Concurrent I/Dispatcher test licenses Hexagon offers test licenses for I/Dispatcher at no additional cost with the purchase of I/Dispatcher production licenses up to the quantity of the production licenses. 12. How many call taker licenses are included with this proposal? What is the cost for additional licensing? Hexagon's proposed I/Dispatcher licenses in Q&A #11 above support both call taking and dispatching functionality. 13. How many mobile client licenses are included with this proposal? What is the cost for additional licensing? 0 (180) Concurrent Mobile for Public Safety (MPS) client licenses Current unit pricing for MPS in the proposed pricing is $1,110.66 per license. w Optioned: (10) Concurrent Mobile Responder client licenses Current unit pricing for Mobile Responder in the proposed pricing is $512 per license. 14. How many training licenses? What is the cost for additional licensing? • (4) I/Dispatcher training licenses Current unit pricing for I/Dispatcher in the proposed pricing is $10,451.69 per training license. Hexagon offers training licenses for I/Dispatcher up to the quantity of the I/Dispatcher production licenses. 15. How many backup center licenses? What is the cost for additional licensing? • (6) I/Dispatcher backup licenses Hexagon offers backup licenses for I/Dispatcher at no additional cost with the purchase of I/Dispatcher production licenses, up to the quantity of the production licenses. 1; PDF Page 6 HEXAGON. SAFETY& INFRASTRUCTURE Responses to RFP180081 LKD CAD Evaluation 2 Questions 16. Is the mobile client licensing independent\interchangeable with the operating system? 10 ICIS clients + 10 Windows clients = 20 Windows clients = 12 windows clients + 8 ICIS clients = 14 windows clients + 2 ICIS clients + 4 Android clients Hexagon's MPS client product supports 64-bit Windows 7, Windows 8.1 or Windows 10 on laptops only and is not considered independent/interchangeable with the operating system. Hexagon's Mobile Responder product (optional) is independent/interchangeable with the operating system and can support the following operating systems and devices: • Apple@ Inc. devices (iPhone@ and iPad@) with iOSTM 9.0 or greater (Tested using iPhone 6, iPad Mini, and iPad Pro) • Google@ Inc. AndroidTm devices with OS versions 5.0 or greater (Tested using Galaxy S6, LeEco Le2, Moto G2, and OnePlus One) • Microsoft Surface Tablet® with Windows 10 (Tested using Surface Pro 2 and Surface Pro 3) 17. Is there a mobile client site license option available? What is the cost for additional licensing? Yes, a mobile client site license option is available. While Hexagon can option a site license, it does not always provide the value a customer desires. This model typically benefits customers who expect substantial organic growth in their department in the next five years. Conversely, it may not provide the same level of value for a customer who expects only slight organic growth. The price for Hexagon's site license is based upon the maximum anticipated growth of production licensed end -users operating the Hexagon software at any one time. A site license conversion fee applies, which is also predicated upon the number of production licensed end -users. 18. If not a site license price, will the vendor sell licenses directly to the organization's needing mobile clients and how is that managed within the Lee County system? What is the cost for additional licensing? Hexagon's CAD/Mobile solution is designed to support multiple agencies (or PSAPs) sharing a common hosted CAD System. We refer to this configuration as "hub and spoke." One "hub" system is accessed across a wide area network (WAN) by any number of "spoke" agencies. If not using a site license, Hexagon is able to sell licenses directly to the organizations needing mobile clients. Lee County can choose how those mobile licenses are managed within the County's CAD/Mobile system. For example, the organizations could have their own mobile configurations as "spokes" of the County's CAD/Mobile "hub" system, or the County and organizations could form an agreement to use the County's mobile configurations. Current unit pricing for MPS in the proposed pricing is $1,110.66 per license. 19. How is licensing handled for hot, live back-up site? From a server standpoint, Hexagon has proposed the use of SQL Server AlwaysOn Availability Groups to provide high availability and disaster recovery for the I/CAD database. Hexagon has proposed fully 1; PDF Page 7 HEXAGON. SAFETY& INFRASTRUCTURE Responses to RFP180081 LKD CAD Evaluation 2 Questions redundant I/CAD Database Servers at the primary site with synchronous replicas for secondary failover at an alternate site to prevent disruption of operations. Hexagon assumes the SQL Server Enterprise Edition licenses will be provided by the County. Test, Training, Redundant, and Backup copies are available for all proposed standard and custom interfaces; however, implementation is subject to the customer's ability to provide connection to the applicable system. On each Interface /Communications Server we use a product called ISM (Interface Service Manager). ISM manages Hexagon's Intergraph Public Safety interfaces and services to provide features beyond what Microsoft Windows provides, including support for failing over a service to another machine. It also provides a convenient user interface for managing the interfaces and services by delegating interface responsibilities to another instance of the interface in the case of a failure. Interfaces are peered between servers via ISM. ISM monitors the state of a service or interface on a given server. One server is set to start the interface in primary mode and the other is configured for secondary. Having the service run as secondary means that it is not actively interacting with CAD but is ready to take over when needed. If that interface fails on the primary server then that interface it made active on the peered server. ISM addresses the following two failures: • Interface failure - An interface failure is the failure (exit) of a given instance of an interface. ISM detects when an interface terminates abnormally and attempts to re -spawn a new instance of that interface in its place. • Hardware failure - In this scenario, a node has failed. The ISM peer requests all interfaces to proceed to the primary state. ISM resolves both types of failures by communicating with its peer and coordinating the transfer of control between the interfaces and services executing on each server. Not all interfaces support this functionality. As shown in Lee County, FL Configuration _2-16-2018 (pages 11 through 19 of the PDF), interfaces that fail on Interface/Communication Server 1 a and have a peer on Server 1 b, will switch over to Server 1 b. Licenses listed on Interface/Communications Server la in the primary environment, but not listed on the Interface/Communications Server 1 b are available as cold backup licenses in the Backup site at no cost, if desired. From a client standpoint, if the County is planning to use the I/Dispatcher clients at the disaster recovery site for simultaneous use with the primary production site, then the I/Dispatcher licenses must be production licenses for both sites. If the County is not planning to use the clients at the disaster recovery site for simultaneous use with the primary production site, then the County can reserve the production licenses for use at the primary site and use I/Dispatcher backup licenses at the disaster recovery site. Svstem Reauirements: 20. Does your offering require proprietary hardware? If so, attach a list of hardware with specifications. Proprietary hardware is not required. Hexagon does not have a hardware platform preference. So long as hardware models can meet the required server and workstation hardware specifications (included in the diagram Lee County, FL Configuration _2-16-2018), they may be supported. However, Hexagon recommends that the hardware be Dell or HP compatible. Hexagon has previously deployed systems using HP hardware and Dell hardware. 1; PDF Page 8 HEXAGON. SAFETY& INFRASTRUCTURE Responses to RFP180081 LKD CAD Evaluation 2 Questions 21. Does the proprietary hardware install in an N-Series TeraFrame® Gen 3 Network Cabinet? Hexagon's solution is hardware agnostic and the proposed hardware specifications are compatible with an N-Series TeraFrame® Gen 3 Network Cabinet. 22. Does the GIS support native ESRI shape files or will it require data file manipulation or converters? If so, are these converters included as a line item in the offering? If not, provide pricing. The I/CAD map build tools (I/Map Editor for ArcGIS) can consume native ESRI shape files as the source for building the I/CAD map, but I/CAD itself does not use the ESRI shape files in the application. The shape files can be loaded into the GIS and the attributes added. I/Map Editor for ArcGIS is used to convert the ESRI data to our .map file and is included in Hexagon's pricing. Support: 23. What types of alerts are there to notify technical support staff when CAD components are approaching capacity (i.e. number of transactions per minute nearing upper limit of system's ability to handle), components are not receiving expected data (i.e. AVL data was not present for x number of previous closest unit recommendations), or applications have failed (i.e. server handling cad traffic to mobile units has crashed.) The County requires a system that is robust, scalable, and sized to deal with the myriad of operating conditions in which the County may find themselves. Hexagon specifications for hardware account for potential surges in production use based on external and environmental factors (widespread weather events, civil disturbances, etc.). It is clear that the County has a vested interest in knowing if the solution is approaching the capacity for which it was designed. The I/CAD database runs in Microsoft SQL Server 2016 Enterprise edition. Microsoft provides a number of performance objects that can be monitored within SQL Server and subsequent alerts can be built on those objects. Database mail can then be used to alert operators when the alerts are raised. Hexagon has not proposed any services to configure such alerts, but those services can be added at additional cost if the County desires. To address the County's desire to monitor data flow and make notifications when components are not receiving expected data, Hexagon has proposed our EdgeFrontier integration platform, the EdgeFrontier Developer kit, and EdgeFrontier Developer training. Using these components the County may write systems to monitor data flow between components and make desired alerts when data flow goes outside desired thresholds. The County has also expressed a desire to know when system components or services experience a state transition (become unavailable, fail, or failover to a peer). Hexagon includes External System Message Display (ESMD) with all I/CAD systems. ESMD is used to monitor the state of Hexagon applications in the I/CAD solution. When those services go through transitions in state they broadcast a message which is received by ESMD. ESMD can be filtered to display specific messages the County is interested in and when those messages are received, alerts can be sent via SMTP to any email address the County desires. 1; PDF Page 9 HEXAGON. SAFETY& INFRASTRUCTURE Responses to RFP180081 LKD CAD Evaluation 2 Questions 24. What will on -site presence be during the implementation phase? What is the hourly rate should additional time be necessary? On -site Presence: Hexagon personnel remain on -site to assist and guide the County throughout multiple phases of the project implementation. For Public Safety Projects, Hexagon segments activities into the following implementation phases: • Planning and Initiating Phase • Staging Phase • Configuration Phase • Deployment Phase • Maintenance Phase (two weeks on -site and two weeks remote) While each project phase involves various remote and on -site tasks (identified in Lee County CAD Project -Sample Project Schedule, pages 20 of 25 of the PDF), Hexagon conducts the majority of the overall project on -site. • During the Planning and Initiating Phase, project kickoff, I/CAD Launch, and the I/CAD Map Launch occur on -site. • During the Staging Phase, the system builds, system map builds, hardware staging and installation, CAD System Administration training, I/CAD Essentials for Core Team training, CAD Data Conversion, and a system technical health check occur on -site. • During the Configuration phase, the CAD system configurations, MPS overviews, MPS configuration workshops, and testing and vetting Disaster Recovery documents and processes occur on -site. • During the Deployment Phase — Testing Stage, Factory Acceptance Testing and Site Acceptance Testing occur on -site. • During the Deployment Phase — Training Stage, all proposed training courses occur on -site. • During the Deployment Phase — Cutover stage, System Readiness Review, CAD Administrator Refresher training, cutover, and system technical health checks all occur on -site. • The Maintenance Phase represents a single on -going task that begins following cutover. At this time, the project status transitions from an active implementation under the care of the assigned Hexagon Project Team to an active County installation supported by Hexagon's Customer Support Center. Hexagon has proposed a 30-day reliability test during which Hexagon will provide the County with support for problems, questions, or issues encountered in the 30 calendar days following the Cutover to production use the new Subsystems. For the reliability period, two (2) weeks are on -site following the week of cutover and two (2) weeks are remote. Hourly Rate: Should additional time be necessary, the Hexagon Project Manager and Account Manager will work with Lee County's team to determine the additional hours required to complete the task. After there is mutual agreement on the scope and level of effort, either an hourly rate or a firm fixed price will be optioned for the customer's consideration. The hourly rate will be dependent on the task and the resource needed. 1; PDF Page 10 HEXAGON. SAFETY& INFRASTRUCTURE Responses to RFP180081 LKD CAD Evaluation 2 Questions 25. What will on -site presence be during go live? What is the hourly rate should additional time be necessary? On -site Presence: Prior to go -live, Hexagon personnel will be on -site for a Readiness Review of the system. During the Readiness Review, Hexagon lead technical resources, the Hexagon Project Manager, and the Lee County team will meet and determine if the System is ready for production use. The Hexagon Subject Matter Experts (SMEs) remain on -site to install the production ready system. During go -live, several key Hexagon team members will be on -site. Key resources will include the Project Manager, Lead Technical Architect, CAD Implementer, Interface Engineer, and Customer Support Engineer. These resources provide critical responsibilities to ensure a smooth transition and cutover. Following go -live, Hexagon has proposed a 30-day Reliability Test during which Hexagon will provide the County with support for problems, general question and discussion, and issues encountered in the 30 calendar days following the cutover. For the reliability period, two (2) weeks are on site following the week of cutover and two (2) weeks are remote. Hourly Rate: Should additional time be necessary, the Hexagon Project Manager and Account Manager will work with Lee County's team to determine the additional hours required to complete the task. After there is mutual agreement on the scope and level of effort, either an hourly rate or a firm fixed price will be optioned for the customer's consideration. The hourly rate will be dependent on the task and the resource needed. 26. Confirm pricing is all-inclusive in regard to training (i.e. mileage, air fare, accommodations, per diem, etc.) as identified page 8, section 22. Hexagon's training pricing is inclusive of the associated travel costs indicated above (mileage, air fare, accommodations, and per diem). 1; vase 1 TIUBLEOFCONTENTS Plyew wnponenn Paeez Mma1=CADT.ae"oveyenvimr.nem Paeea vaeea aln�na�.n�re vases en..m-- Paees Page n DI.— Page e N..S Page s n��on rend a rsde on me asmne Mncal n � se�rvenosm9x oas � aM vMo4m a encwmgetl to tlisN Wte the wo�kbatl xross v'inual hosts. Note It a prBible to separate tlAabaseseners between the PSAPs. Havever, ims ace ancent on.—noun-4 between saes am bnd CAD Total Eff-. a Seats Calculator Dispatcher # +Caltlaker # + ((SU M (MPS, NetViewer, NetDlspalChery5)) N-t—Ua b,", aM a to servesmtlr— the to Ing: tlaniSa r k"P s rvg a=coa eankupsFailover rvers (a�qt�ion, mtertaze, ire servNg ihesame Nncfiars wehin greh server group, Lee County, FL CAD/Mobile Configuration Svsrem overview February 2Di8 m Icno SOL AN SYmn CIust" VA+b l#1(5DLAIw OnCluste) Appl cation Server#1a ib IRe]unOaMl IeSigM R vortine fe CAD DatabaselHppllwti"n server 41. p ing workstations may . I¢atetl at --t sites antl sgll . ads to access the ring envim--.-d at Ne I,— see p—C. Ney have a vxure n— noun—n to the Test am Trai tlataha am.,, =—Cn rovers. Proprietary and Confidential DDOP�n o-a serve �oxs serveaa TER vear (DR)exviaoxl�xT: sratmnelu --serve a2 CAD DR VIRTUAL ENVIRONMENT VCAD as ICADSQLAN,.y nCwstep az IZU SOL A,w On Cluster b lAppii"ation several" 1'1 ReO maryl 2b IRe0 rtmaryl hnlasagM Reporting roraCN� UaWbasealAppiira0on 5 tetvbeP a1" PDF Page 11 Color Leg—d Black — Base products Red —Optional products Green — Customer-fu—hed products Pulple— Virtual Specifications HEXAGON SAFET, a INI RAST—TORE Lee County, FL CAD/Mobile Configuration ce ,,,eett.mu Physical Components and Hardware Specifications February 2018 1Pr erverco R. S'.0 eeHu�R..� ompuR..p.rRcompuRrRoomHxoM Physical Host= Servers 1M- CPU vSp— Ent p-6 x (x2) Two (2). 22 re P«asors POB 16GBCF—HBAS ual powersupplies 6 Veers ot24x] SappM Qty: 3f RECOMMENDED HARDWARE SPECIFICATIONS rtla LCB ewlm to.hh d >gonswikn^c pwrsds l6 pMs�acry ff. a tletScatM UPS tsce u�; exrega� guralion aN s¢etl at NA time aty: 1 for Proeu— Eml.. es(1) RetlwtlaN Host I Proud,- SAN 11T ConilguSretl omge v sing to 32000 lops st csPerc eesomm2- repacY�salromsoatren«t misce Rec etleeuraeom erairg avrgk twogmcawr Host FC 450E SAN �rwnn wirmows Batxenterallows as 14)16GB FC Pons pn contrdler many VMs ascan ce NI«alai to asingk rvo9 121) aroGB 5s saverto mn on the U�. 5 Veers 24x] Premmm S_n oq'of —kS relutr mary: 66 taty: 1 for P,.u.,-Environment PDF Page 12 — —11. CABPCIren¢ t� Bls Query UKof wSh—hpatl rtl LCB : 'T'tch (1 Ppovitles l6 pMs) ch gy 411.111gm PDus Ean u . a tleNcatetl wikt. Ex«t r«eptaPDck elkatMUUPSUea-r totlre�rwl moo aM s¢e0 at ifial time oy: 1 for DR. Enwonmer8 Z.- I l ksiug pisaster Recovery SAN 6 5TB f C.N'—g'� t« csperk eewWm2- orepxks.A11rcoresonirervwimisiBe erNirg asingk twogr«asor Host r wkn winnows Ba 1$SBB lops Rec rrecorm9umtion: OeeP, SAN (4)16 —Nsparc«Volier many VMs ascan be albcatal to aslingk BOY sever to mn on tie �oA. 114)moGBss11, 5 Vees 24x] Premmm Suppwl pry of repxks requkee to o.R.: as Oty: 1 for O.R. Emlm— Color Legend Black —Base products Red —Optional products Green — Customer -famished products Purple — Virtual specifications Proprietary and Confidential 2 HEXAGON SAFETY&INFRASTRUMRE Lee County, FL CAD/Mobile Configuration Marepement Environment February 2g1 B Protlucti- Management Environment S'�QI L- Hexagon Doman I I ✓` I �m a seer., I I ganam Cemmlle DNS server#1 menso�serv�zo�s �I� ,gel I � Posg,esal,�cl�w vCeecrl I aewsserve, I I I I gan Cem II sservera2 I I oW I sy:rem manapemem serverat I '" '° I I I Disaster Recovery Management Errvi--t nt��LServe�r A166 ess(mchayel PosgreS(Y (izlutletl wiN vCemer) eY— n¢naparrern server N2 Proprietary and Confidential Hexagon Domain I I I I I I I I I I �gNs I I ganamCemmll serverNa I Iwwewsserve, I I� I I � I m�..r m.mym metre. �nue I----wbaeN�--- —I PDF Page 13 Color Le —d Black — Base products Red —Optional products Green — Customer- —hed products Purple — Virtual Specifications HEXAGON --& INFNasT—TUNE Lee County, FL CAD/Mobile Configuration CAD Protldction Environment February 2gi g CAD Pmd..ton Environment CAD MS SQL AtwaysOn Cluster I I I I I Ao m—Cemm nba Ien—,a I oaA-1 se.eras Icao soLalwaysonrcwa>) I �eE be I �al�ae�y lnu) M romHMLserverzo,6EE a-,0000a I P (rAP) A�gaESA) PmreofPr M I II ICAO soLAlwaywn clues>) I ItCAn - ,esoma�eeP�R I - I Mr..mH SOL Server2m6 EE " I-FlRD,opsE i M yp-5)�V ®-,0000a _ _ _ _ _ _ _ _ _I I z6(fe,` bPzsGPs-AULPe�nLevel CA,} �`e�b�pill��Te�M1�diesCAn Arctlive MS SQL AlwaysOn Cluster �I n- I I cc o597sualCAova20a i nSMPlarmintrface Arcbn�e5erve� 1A.h nLAlway C1.—) I L�erve,m,6EE IM I I I a@-a000ca ----�-------I Proprietary and Confidential bbdle Com serve ma s PDF Page 14 In$Igbt Repmgngg Da --pp—,. (b(4 a Rey11FE mre wllrxrte) Color Le —d Black - Base products Red -Optional products Green - Customer -famished products Purple - Virtual Specifications 4 HEXAGON -EWE IFlERASTRUCTURE Lee County, FL CAD/Mobile Configuration CAD Testantl Training Environments February 21318 Integmt d CAD Integmt d CAD Testing Envi--t Training Environment ae-Hn Re-m Leenx( Au (irlunetl— VExx-HA) Ed3eFromc Runtime Eigrre Res L�iue) EegeFra oev per Eigiire(1' hsal) Sight Se eer Res s( er(res nse) oTke(I- IN— (D, s) I=D gatabase halnlrq Server Proprietary and Confidential 1 !✓ uCAg CanmunraaenvlmMace Training Saver PDF Page 15 Color Le —d Black — Base products Red —Optional prod, cts Green — Customer- —hed products Purple — Virtual Specifications HEXAGON SAFETY&IN FFAST—TUFE CAD MSSQL AM,.—s O.Cluster I I - I I I I I I Ilrr,00araba,eSerVer�, I I� I I MKr�115aLserver�,16FE I I wN I °a oe -,00 B L------------ ------------ Archive MS SQL AlwaysG. Cluster I I I � I meµ_ wm APpD—serveralc (Amt,_WL AIwaYZOn CI—) I w serve, II e �Ir>,rS�M�„eellree.�l �k�ro�soLserver anfi rf i reaismeR-7soe I I sl°w ��Ba.e" 11-3 -� Lee County, FL CAD/Mobile Configuration Disaster Recovery Envi—DI February 2e1 B CAD DR Environment MIN C,anmunl rl (B-P) Savas Nic R tig(IIFS� Proprietary and Confidential (RaluneanrroP mary�enM1bEII�e Server #Lai (IIMDT MPS ,,°iAULlmefia�el. ur,a«e, (Pillmenael. tpu —,. gecntal grwnM1. PDF Page 16 Color Legend Black -Base products Red -Optional products Green-Customer-f°mished products Purple - Virtual Specifications HEXAGON SAFE— IMFRAsT—TURE Lee County, FL CAD/Mobile Configuration :] cuenta February 2p1 B Mnp•fcher Workstations Mnpatcher Workstations (Production) (Test) . m+wm, e.na<N+•e•�••+••a•ra Mnp•fcher Workst•dnns M•P Maintenance Web -Based Workstations (Backup) Workstation plspatMerworkstatlans prciudes plspatMer Workstations oval (66bn( system aamrnlstmtor omn vow sra (rr.�eowmoae( wortsufans) mi�p or�re�r-re(pN. a �sl w.•�•re rmows coal (staal Rromv ospRacM1 Pawl plspatcM1erworkstatlans <rore a�ree rom� umeoR espo�aer�ap tint rmowstN ofessw�al �saaiq MaP Maintenancewarlatmlan weelaasee worlotaaans ((AYfl1 ((hY- reoresl ro�a6M1Qow a(neea moael R Dal (stool oral(stanl (�N- Imea o f R 1 er✓ vdeoa m(pryee ) n PDisPe(eher Workstabo� an r(cagpe r roof /N(Gysmrcurrem carer eenmsl tTrernrnp) ( easur� s arer�m=t1 (pry: a vroaoai.INeoresl v(pN: e—.p Iced 6) Hexagon nines tt—Nave PmPosm Hexagon Naz Proposal concunem user l lcensa Nosed on ourcurrem understandlrg of Dunk for Vtlm Razpatc= - maxl--cunentopa pnators using Ne wommatiors for CAD a'�yazgrval time TNe pmderto quan ceotclem user lkenseswlll Ne atljusEtl to relict usageat time c�Naz�cN aponderciknt plspatMer Workst�Ians otnegoNAron. p¢patcrrer. Haaever, Vldm ro - t nt. rare r�mwato ( ( N��n: w.ka�eco�mav Nave as marN NackNP N - - aPoma Oren cove - tkalses merearev r - t-e kavclem kernesmast not ag par�M1er (N.( lo�sl exceed tnenuml»rorpred a t- _ /plspatcNer coca ncr�e Rrorny psp tM1 Pararro Hexagon odes th. t. nu NeNewer.— (torremote CAp v-1tV, (py-eT sl nalnyaz ran--PmcNN a-tlonally resPecvvmy)regmred 5oazea on (pyeT�mI tnecusmmersdedslon and is negotieme. Client Hardware Specifirati ons plspatl:M1er WOMstatlons(Incluaes Map MalnW.—Workst . ons svemnaeminlsba ralnlna, an rMUPWorkstat—) o r o srer 2G Emerxt 9 Ememet T68 rewlur wnhzwwro 4s iwa (zl ProresaorialzarkM1 r�oono rce(3) Profesvmul zoom mono ow a uR me pry: TBD Proprietary and Confidential Mobile Environment IMOGle pats pomPaRrs I m rNR o l(sn) I IWme,rorrwn�sareNrco�mremuse�Ke�s ien icanreslaly-la( I�eeom�����tlN�a i�g�tatio�s, I p I I, ozNa:a g� �eo� I pN Tap IGIIeRespoMerTaElelsor5nurlPMr.s I Mal I e�epop� —3) ap I PDF Page 17 Color Legend Black - Base products Red -Optional products Green - Customer--u had products Purple - Virtual Specifications HEXAGON sar-ETva lruF—TaucTURr PDF Page 18 Lee County, FL CAD/Mobile Configuration Network Dimg— I F.b..W 2018 1 If the m- are connected A. dedicated fiber then that fiber is ­--d by the Orange line I. the lowing. If the sites are connected A. I — W-1, between ,i- then this is -­--d by the ­.. line. It is complete ­ible that both --ib, ill —t ithi. the city .—I, 8-- NICt—mg is not functional I. Windows 10will be split b— tches bmn Toaswacnes bmn T" swacnes pz& ---­ I. the --of . —itch failure. Proprietary and Confidential C.I., Legend Black -Base products Red -Optional products Green -Customer- —hed products Purple -Virtual Specifications HEXAGON Wl-& INFRASTRU—IRE PDF Page 19 Lee County, FL CAD/Mobile Configuration Notes February 213118 1. Color mpmsentatbn in thb--.radon tliiram is as follows_ BIs k—Base Pm ducts Red — Optional Pm ducts (Budgetary Estimates and RO Ms do not indude options) Green— Customer Furnished Products 2_ Hexagon assumes that the Local Area Netwoik (LAN), the witle area network (WAN), Active Directory, antl any Microsoft Exchange Serverinfmslmcture a.0 be provitletl antl stagetl by the Customer. Minimum agency WAN Connection = 10o Mbps_ 3_ Hexagon assumes Nat nelwotic communications provide bytheCustomer(. moot. sites will support the bllowing bantlwitlih requirements. - Each wotlrstation mining the VD ispatcher diem software requires a minunum bantlwitlih availabAAY of 2%Kbps - Each remote wotlrsistion mnningihe VNet0ispatcher or VNelViewer client software requimsa minunum bantlwklih availability of 128Kbps_ - Each laptop mining Mobile for Public Safety requires a minimum bantlwitlih availab,idy of 12BKbps_ 4. All workstatbns, PCs, laptops, antl specif tl peripheral hartlwam pmvitletl by the Cusomer are assumetl to meet the specif scions ddineatetl on the d gram_ 5_ During implementation, Hexagon in pbmentation pemonnd buib 5 CAD diem wotlrstah— antl 5l1 wh Ae prov itling III I stion instructions so that the Custom efs system sdmI Istrator(s)mll have the Imowledge mquiretl to install add Atonal clbnt software_ Fdbwing N. hi Cusomer personnel will be expected to batl all remaining client softwan:_Th. approach ensures that, bllowing the clover, Customer pemonneI will have the sW sal necessary to build new client ha Nwam_ 6_ Hexagon assumes thatihe Customer will provitle WAN —hi ications, indutling wireless network communications, that will supporl the bantlwidh citetl in ft— 3 above_ ]_ Anyatltlitional inter( ce nd sih—f ally inclutletl in the configuration will incuran addd...l cost_ Hexagon is not responsible; for costs accocbted wdh tleveloping the ihiN-pmty portion ofany interface_ 8_ This Configuration Diagram illusirabs the proposetl haNwam antl softwaremnfgumtion at the tune dsubmissiom 0uring un plementation, the Hexagon lmpbmentation Team,ora. Hexagon sub con tractor, may ah., N. configuration to reflect the negotiatetl system or aflerihe bcatbn of software to take ativantage ofefficiencies tleteth inetl following submission. 9. Hexagon's con figuration does not indude fa miture, networkservices, firewalls, or Microsoft Exchange Serverimpl—ftsb-services Servera.d client worksisibn hartlwam,anti-vims software, backup simage hardware, and Active Directory may have been optioned in the proposal response. If purchased, it is the Cust—i-s responsibility to maintain these items after implementatbn antl cutoverof the system_ 10_ Ifa Training Environment s bid, Hexagon applications are provitletl ffi ietlucetl —t Hexagon applbatbns ate provitletl at no cost Wti Test environment 11. Test intertace licenses are available for proposed interfaces. However implementation is subject to Cust—i-s ability to th—itle connection to the applicable system_All ihirhpatlyexternal interface connections mquiretl forT...g antl/or Test Envimnmenis are the responsibility of the Customer antl/orihi ventlor(s)_ Proprietary and Confidential Color!- p.hd Black — Base products Red —Optional prducts Green — Customer -famished products Purple — Virtaal Specifications HEXAGON --& INFBA T—TUBE I e 20 0 0 T 18 iE 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 % Task Name Work Days Complet 0% Lee County, FL CAD Project 303 days 0% Execute SOW 0 days 0% Planning Phase 60 days 0% Draft Project Schedule developed 5 days 09/0 Review of Deliverables Requirements 1 day 0% Establish Project Organizational Structure 1 day 0% Review of Training Requirements 1 day 0% Review Interfaces and Functions 1 day 0% Deliver Draft Project Schedule to Customer 1 day 0% Customer Review Draft Project Schedule 0 days 0% Project Kickoff 4 days 0% Travel 2.13 days 0% Project kickoff Meeting 2 days 0% Travel Return 1 day 0% Organize and Schedule Project 31 days 0% Deliver Kickoff Meeting Notes to Customer 1 day 0% Hexagon Updates Draft Project Schedule from Project Kickoff Meeting 1 day 0% Deliver Updated Project Schedule to Customer for Approval 0 days 0% Customer Reviews / Approves Updated Project Schedule 3 days 0% Final Project Schedule confirmed 1 day 0% Hexagon Server Accounts Created 0 days 0% Hexagon Orders Software 0 days 0% CAD and Interface Data Gathering 43 days 0% CAD/Interface Requirements Traceability Matrix 5 days 0% Map requirements to CAD 5 days 0% Interface Control Documents 24 days 0% Develop Custom Interface ICD and Interface Questionaires 5 days 0% Develop Informer ICD S days 0% Customer Review ICDs and Questionaires 10 days 0% Update ICDs based on Customer Comments 2 days 0% Customer Review of ICDs S days 0% Finalize ICDs 2 days 0% I/CAD Launch 26 days 0% Travel 1 day 0% I/CAD Launch 4 days 0% Gather Requirement Data S days 0% Map Data Gathering 18 days 0% I/CAD MAP Launch 18 days 0% Travel 1 day 0% I/CAD Map Launch Onsite Workshop 2 days Page 1 PDF Paae 21 D % Complet 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% Task Name Travel Return Gather Map Data Requirements Map Data Analysis Test Plan & Test Case Creation Hexagon Send Sample Test Plans to Customer Customer builds test plan and test cases Hexagon reviews and approves Test plan and test cases Staging phase Map Build 1 Map Build 1 Map Build 1 SR resolution Hardware Staging Onsite hardware Install VM Setup Interface Development COTS Interfaces Informer Development (Optioned) I/CADLink Set up I/FRMS CADLink (FireLink) ANI/ALI Priority Dispatch I/Page I/PTT I/Fire Station Alerting (I/FSA) I/Fire Station Printing (I/FSP) I/TDD I/Tracker for PLT Custom Interfaces ASAP CAD EF Interface Spillman Flex CAD EF Interface CAD -To -CAD Interface to Tri-Tech CAD -To -CAD Interface to Motorola Premier 1 CAD -To -CAD Inteface to OSSI Visual CAD Econol-ite EF (Consulting Services Only) ASTRO 25 CAD EF Interface Telestaff Import Video Responder Integration Development Support for Linked Event Remarks Updates Software Staging System Build 1 System Build 1 Prep Travel Work Days 1 day 10 days 5 days 31 days 1 day 20 days 10 days 178 day 6 days 5 days 1 day 25 days 5 days 20 days 178 days 61 days 30 days 1 day 20 days 1 day 1 day 3 days 1 day 1 day 1 day 1 day 1 day 178 days 12 days 10 days 5 days 5 days 5 days 5 days 5 days 10 days 25 days 3 days 75 days 19.5 days 0.5 days 1 day 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 Page 2 PDF Page 22 D % Complete 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% Task Name System Build 1 Requirements Gathering System Build 2 Travel System Build 2 Requirements Gathering System Build 3 Travel System Build 3 System Health Check Trusted Advisor Health Check Prep - CAD Travel Trusted Advisor Health Check - CAD Travel Return Customer Requirements Gathering Post System Build SR Resolution Interface Staging I/CAD Data Conversion MPS Overview MPS Overview Prep Travel Onsite MPS Overview Travel Return Configuration Phase Configure CAD System Configure 1 Travel System Configure 1 Customer Data Input System Configure 2 Travel System Configure 2 Customer Data Input System Configure 3 Travel System Configure 3 Customer Data Input Req 4-029 Alternate Response Plan Crisis Mode Req 7-144 Sync Training System Mobile Related Custom Congurations Advanced GIS Requirements (Intelligent Icons, etc.) Health Check lWork Days 4 days 10 days 10 days 1 day 4 days 5 days 15 days 1 day 4 days 9 days 0.5 days 1 day 2 days 1 day 5 days 5 days 10 days 40 days 16 days 1 day 1 day 3 days 1 day 183 days 61 days 15 days 1 day 4 days 10 days 15 days 1 day 4 days 10 days 43 days 1 day 4 days 10 days 4 days 2 days 10 days 10 days 6 days 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 Page 3 PDF Page 23 ID % Complete Task Name Work Days 125 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% Trusted Advisor Health Check Prep - CAD Travel Trusted Advisor Health Check - CAD Travel Return Post CAD System Configure SR Resolution Configure MPS MPS Barcode and MagStripe Reader Set up MPS Workshop 1 Travel MPS Configuration Workshop 1 - Fire/EMS MPS Configuration Workshop 1 Follow-up MPS Workshop 2 Travel MPS Configuration Workshop 2 - Fire/EMS MPS Conguration Follow up 2 - Fire/EMS Health Check Trusted Advisor Health Check Prep - Interfaces Travel Trusted Advisor Health Check - Interfaces Travel Return MPS Pilot MPS Pilot Support - (2 Weeks @ 20 Hours Per Week) Post MPS/Interface System Configure SR Resolution - Remote Map Configuration Map Build 2 Map Build 2 Prep Travel Map Build 2 Map Build 2 SR resolution Map Build 3 Map Build 3 Prep Travel Map Build 3 Map Build 3 SR resolution Video Responder Implementation Apply Maintenance Release Deployment Phase Testing Phase Factory Acceptance Testing FAT FAT SR Resolution SAT 1 0.5 days 1 day 2 days 1 day 10 days 54.5 days 10 days 34.5 days 1 day 3 days 5 days 9 days 1 day 3 days 5 days 30.5 days 0.5 days 1 day 2 days 1 day 10 days 10 days 10 days 140 days 34 days 1 day 1 day 4 days 3 days 13 days 1 day 1 day 4 days 3 days 5 days 5 days 302 days 47 days 9 days 4 days 5 days 31 days 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 Page 4 PDF Pa D % Complete 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% Task Name SAT 1 Support Prep SAT 1 Support Onsite SAT 1 SR Resolution Health Check Trusted Advisor Health Check Prep- Interfaces Travel Trusted Advisor Health Check - Interfaces Travel Return SAT 2 SAT 2 SAT 2 SR Resolution Map Maintenance Class Map Maintenance Prep Travel Map Maintenance Class System Configuration Lcr�,An a Disaster Recovery Document Disaster Recovery Process Test/Vet DR Document and Process Training Phase LMS Training Development CAD Calltacker and Dispatcher Insight Reporting Mobile For Public Safety Netviewer/NetDispatcher I/Sight Map Basics Map Basics for I/CAD Systems (IPST8001) - Prep Map Basics for I/CAD Systems (IPST8001) I/CAD System Administration Intro I/CAD Essentials Trainers I/CAD Essentials for Core Team MPS TTT MPS Administration & Configuration NetViewer/NetDispatcher I/CAD System Administration Core I/CAD System Administration Advanced Insight Reporting for Administrators I/Sight Customer End User Training Go -Live Phase Go -Live Readiness Review Work Days 2 days 5 days 10 days 5 days 0.5 days 1 day 2 days 1 day 14 days 4 days 10 days 8 days 1 day 1 day 4 days 0 days 7 days 5 days 2 days 255 days 212 days 60 days 25 days 25 days 13 days 13 days 6 days 1 day 5 days 23 days 15 days 6 days 45 days 6 days 3 days 20 days 10 days 2 days 12 days 30 days 90 days 53 days 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 204 208 211 217 221 224 233 238 241 q248 249 250 Page 5 e 24 PDF Page 26 Customer: Lee County, Florida _ ` _� Quote Number New Internal_USPS Lee County_$020218$cw INTERG Rev. #: ,[R�YI/ijY�r] Quote Date: February 16, 2019 Expiration Date: August 15, 2018 CAD -Mobile Part Number IPS0035NC Software Description 1/Backup• (No Charge) (IPS0035NC) 2 0.00 $0.00 IPS00421 I/NetViewer (IPS00421) 5 2,148.85 $10,744.24 IPS2301 Intergraph ln5ight Reporting for l/CAD (IPS2301) 1 12,423.42 $12,423.42 ANI-ALI ANI-ALI (Included with I/Executive) 5 0.00 $0.00 IPS0001HA I/Executive for High Availability NL 1 72,253.40 $72,253.40 3ptbds-6 Site license of PresenTense Time Client NT. Supports unlimited servers orworkstations in t 1 1,053.00 $1,053.00 IPS0008 I/Push To Talk (IPS0008) 1 10,745.69 $10,745.69 IPS0012 I/Page (IPS0012) 3 21,472.90 $64,418.69 IPS0018 I/Telephone Device for Deaf- Zetron NL(IPS0018) 1 10,745.69 $10,745.69 IPS0048 I/FRMS-CADlink NL (IPS0048) 1 10,745.69 $10,745.69 IPS0051 I/CADLink NL (IPS0051) 1 10,745.69 $10,745.69 IPS0052 I/Fire Station Alerting (IPS0052) 1 10,745.69 $10,745.69 IPS0053 I/Fire Station Printing NL (IPS0053) 1 10,745.69 $10,745.69 IPS1018 I/Sight Server NL (IPS1018) 1 11,050.61 $11,050.61 IPSCADCUST Econolite Consulting Services- Automatic Traffic Management System(ATMS) (IPSCADCUS 1 4,498.00 $4,498.00 IPSCADCUST-2 Video Responder Interface to TBD Camera System (IPSCADCUST-2) 1 40,340.80 $40,340.80 IPSCADCUST-3 Interface to Telestaff (IPSCADCUST-3) 1 11,666.56 $11,666.56 IPS3042 EdgeFrontier Runtime Engine (IPS3042) 1 19,860.90 $19,860.90 PSA1002 ASAP CAD EF Interface (PSA1002) 1 8,849.28 $8,849.28 PSA1002DS Interface -specific Custom Development Services 1 13,663.60 $13,663.60 PSA1014 Spillman Flex CAD EF Interface (PSA1014) 1 8,849.28 $8,849.28 PSA1014DS Interface -specific Custom Development Services 1 8,996.00 $8,996.00 PSA1018 InterCAD CAD EF Interface (PSA1018) 1 8,849.28 $8,849.28 PSA1018DS Interface -specific Custom Development Services 1 4,498.00 $4,498.00 PSA1018-1 InterCAD CAD EF Interface (PSA1018-1) 1 8,849.28 $8,849.28 PSA1018-IDS Interface -specific Custom Development Services 1 4,498.00 $4,498.00 PSA1018-2 InterCAD CAD EF Interface (PSA1018-2) 1 8,849.28 $8,849.28 PSA1018-2DS Interface -specific Custom Development Services 1 4,498.00 $4,498.00 PSA1017 ASTRO 25 CAD EF Interface (PSA1017) 1 8,849.28 $8,849.28 PSA1017DS Interface -specific Custom Development Services 1 4,498.00 $4,498.00 IPS3042-RDT EdgeFrontier Runtime Engine - Redundant License (IPS3042-RDT) 1 13,903.92 $13,903.92 IPS0008RDT I/Push To Talk- Redundant License (IPS0008RDT) 1 7,513.18 $7,513.18 IPS0012RDT I/Page - Redundant License (IPS0012RDT) 3 15,034.14 $45,102.43 IPS0018RDT I/Telephone Device for Deaf - Zetron NL- Redundant License (IPS0018RDT) 1 7,513.18 $7,513.18 IPS0048RDT I/FRMS-CADlink NL -RDT License (IPS0048RDT) 1 7,522.42 $7,522.42 IPS0051RDT I/CADLink NL- Redundant License (IPS0051RDT) 1 7,522.42 $7,522.42 IPS1018RDT I/Sight Server NL- Redundant License (IPS1018RDT) 1 7,744.18 $7,744.18 IPS0009 I/Mobile Data Terminal NL (IPS0009) 1 47,262.69 $47,262.69 IPS0009A I/Mobile Data Terminal NL- Additional License (IPS0009A) 2 4,868.49 $9,736.98 IPS1183 Intergraph Remote Content Management CC (IPS1183) 1 0.00 $0.00 IPS0015 I/Tracker (IPS0015) 1 26,827.98 $26,827.98 IPS0015A I/Tracker-Additional License (IPS0015A) 3 3,173.66 $9,520.98 IPS0001HATST I/Executive for High Availability NL - Test License 1 0.00 $0.00 IPS0042ITST I/NetViewer - Test License 5 0.00 $0.00 IPS3042-TST EdgeFrontier Runtime Engine - Test License (IPS3042-TST) 1 0.00 $0.00 IPS3042DEV EdgeFrontier Developer Engine (IPS3042DEV) 1 14,897.80 $14,897.80 IPS0009TST I/Mobile Data Terminal NL - Test License (IPS0009TST) 1 0.00 $0.00 IPS0015TST I/Tracker-Test License (IPS0015TST) 1 0.00 $0.00 IPS1018TST I/Sight Server NL - Test License (IPS1018TST) 1 0.00 $0.00 IPS0001HATRN I/Executive for High Availability NL- Training License 1 43,194.94 $43,194.94 IPS00421TRN I/NetViewer- Training License 5 1,268.46 $6,342.32 IPS3042-TRN EdgeFrontier Runtime Engine- Training License (IPS3042-TRN) 1 11,949.03 $11,949.03 IPS0009TRN I/Mobile Data Terminal NL-Training License (IPS0009TRN) 1 27,891.35 $27,891.35 IPS0015TRN I/Tracker- Training License (IPS0015TRN) 1 15,821.01 $15,821.01 IPS1018TRN I/Sight Server NL- Training License (IPS1018TRN) 1 6,647.96 $6,647.96 IPS230IBCK Intergraph ln5ight Reporting for I/CAD - BCK (IPS2301BCK) 1 0.00 $0.00 IPS0001HABCK I/Executive for High Availability NL - Backup License 1 0.00 $0.00 3ptbds-6 Site license of PresenTense Time Client NT. Supports unlimited servers or workstations in t 1 1,053.00 $1,053.00 IPS3042-BCK EdgeFrontier Runtime Engine - Backup License (IPS3042-BCK) 1 0.00 $0.00 IPS0008BCK I/Push To Talk - Backup License (IPS0008BCK) 1 0.00 $0.00 IPS0012BCK I/Page - Backup License (IPS0012BCK) 3 0.00 $0.00 IPS0018BCK I/Telephone Device for Deaf - Zetron NL- Backup License (IPS0018BCK) 1 0.00 $0.00 IPS0048BCK I/FRMS-CADlink NL-Backup License (IPS0048BCK) 1 0.00 $0.00 IPS0051BCK I/CADLink NL- Backup License (IPS0051BCK) 1 0.00 $0.00 IPS0052BCK I/Fire Station Alerting - Backup License (IPS0052BCK) 1 0.00 $0.00 IPS00536CK I/Fire Station Printing NL - Backup License (IPS0053BCK) 1 0.00 $0.00 IPS10186CK I/Sight Server NL - Backup License (IPS1018BCK) 1 0.00 $0.00 IPSPRCMDL_$031315$(Master) - 1 of3 PDF Page 27 IPS0009RDT I/Mobile Data Terminal NIL - Redundant License (IPS0009RDT) 1 33,088.63 $33,088.63 IPS0009ARDT I/Mobile Data Terminal NL- Additional Redundant License (IPS0009ARDT) 1 3,403.03 $3,403.03 IPS1183RDT Intergraph Remote Content Management CC - Redundant License (IPS1183RDT) 1 0.00 $0.00 IPS0015RDT I/Tracker- Redundant License (IPS0015RDT) 1 18,800.70 $18,800.70 IPS0015ARDT I/Tracker-Additional Redundant License (IPS0015ARDT) 3 2,215.46 $6,646.37 IPS0042IBCK I/NetViewer- Backup License 5 0.00 $0.00 IPS0002 I/Dispatcher (IPS0002) 6 17,716.31 $106,297.85 IPS1128 ProQA Paramount I/CAD Interface (IPS1128) 6 445.16 $2,670.96 IPS1024 Video Responder NIL (IPS1024) 6 1,119.90 $6,719.40 IPS0002TST I/Dispatcher-Test License (IPS0002TST) 1 0.00 $0.00 IPS0084 I/Map Editor for ArcGIS NIL (IPS0084) 1 3,297.19 $3,297.19 IPS0082 Map Administration Utility (IPS0082) 1 10,237.61 $10,237.61 IPS0002TST I/Dispatcher-Test License (IPS0002TST) 4 0.00 $0.00 IPS1128TST ProQA Paramount I/CAD Interface -Test License (IPS1128TST) 4 0.00 $0.00 IPS1024TST Video Responder NIL -Test License (IPS1024TST) 4 0.00 $0.00 IPS0002TRN I/Dispatcher- Training License (IPS0002TRN) 4 10,451.69 $41,806.77 IPS1128TRN ProQA Paramount I/CAD Interface -Training License (IPS1128TRN) 4 264.16 $1,056.64 IPS1024TRN Video Responder NIL -Training License (IPS1024TRN) 4 681.16 $2,724.62 IPS0002BCK I/Dispatcher- Backup License (IPS0002BCK) 6 0.00 $0.00 IPS1128BCK ProQA Paramount I/CAD Interface - Backup License (IPS1128BCK) 6 0.00 $0.00 IPS1024BCK Video Responder NIL - Backup License (IPS1024BCK) 6 0.00 $0.00 IPS0080 Mobile for Public Safety CC (IPS0080) 180 1,110.66 $199,918.80 MPSCUSTOM18F MPS Custom Build for Fire (MPSCUSTOM18F) 1 3,234.00 $3,234.00 Software Subtotal: 1 $1,164,401.36 Part Number Implementation Services Description Project Management Services 1 177,724.86 $177,724.86 SME 1 43,660.00 $43,660.00 GIS 1 67,216.80 $67,216.80 CAD Implementation Services 1 277,438.00 $277,438.00 Interface Implementation Services 1 253,523.20 $253,523.20 BU Devlopment 1 1 67,760.00 $67,760.00 BU Devlopment 2 1 11,487.20 $11,487.20 Training 1 244,310.40 $244,310.40 Virtual Machine Stage and Install 1 12,357.90 $12,357.90 Travel 1 163,614.00 $163,614.00 Project Services 1 1,319,092.36 $1,319,092.36 Shipping and Insurance 1 165.00 $165.00 Implementation Subtotal: $1,319,257.36 3ptbds-8 I Hexagon LMS Per User Training Yearly Access (available for 12 consecutive months beginni 100 240.00 $24,000.00 Training Subtotal: $34,0.0.00 Software Tota 1: $1,164,401.36 Services Total: $1,319,257.36 Training Total: $34,000.00 Subtotal: $2,517,658.72 1. Customer is responsible for the purchase, installation, and configuration of all required hardware. 2. Hexagon requires remote access to the customer's servers to complete this effort as quoted. 3. An overall system discount has been provided for this opportunity. Changes to scope of the final contract may change the discount amount. Also, any credits given for line items as part of a Change Order will include a reduction for the line prorated amount of the one-time system discount. Items removed after contract signing will result in a contract credit for future Intergraph software and services being established, not a contract reduction. This discount is based on the acceptance of Hexagon's standard Terms and Conditions. 4. For items included in the options section, project management services and implementation services are not included. Maintenance is also not included unless noted. Hexagon services are valid for 6 months and Hexagon product pricing is valid for one year after contract signing. Hexagon can provide a fixed quote when optional items are selected. 5. Pricing is valid for 180 days from date of submission. 6. Sales tax is not included in this quote. Final sales tax billed will reflect the applicable tax rates at time of sale as required by law. 7. All Intergraph Products have first year warranty included in SW purchase price; warranty period starts at cut overto live operations 8. Test/Training Interfaces are dependent on the ability of each external system to support interface connectivity for the Test Environment. Due to the fact that the Test Environment does not bear the client load of the Production Environment, load balancing in the Test Environment is not necessary. IPSPRCMDL_$031315$(Master) - 2 of3 PDF Page 28 Optional Price Items tYear Intergraph Software Maintenance after Warranty 1 259,636.20 $259,636.20 ond Year Software Maintenance 7.7ss,ixth 1 272,618.00 $272,618.00 rd Year Software Maintenance 1 286,249.00 $286,249.00 rth Year Software Maintenance 1 300,561.00 $300,561.00 h Year Software Maintenance 1 315,589.00 $315,589.00 Year Software Maintenance 1 331,368.00 $331,368.00 0 Seventh Year Software Maintenance 1 347,936.00 $347,936.00 0 Eighth Year Software Maintenance 1 365,333.00 $365,333.00 0 Ninth Year Software Maintenance 1 383,600.00 $383,600.00 Optional Software Subtotal:l $2,962,990.20 l NUM IPS3206 Intergraph Mobile Responder Server (IPS3206) 1 0.00 $0.00 I PS3204 Intergraph Mobile Responder Client (IPS3204) 10 512.00 $5,120.00 I PS0004-A I/Informer Custom Query Interface to FCIC/NCIC (IPSCADCUST-IPS0004-A) 1 32,624.00 $32,624.00 IPS0004 I/Informer (IPS0004) 1 32,289.00 $32,289.00 IPS0004TRN I/Informer- Training License (IPSCADCUST-IPS0004TRN) 1 18,910.00 $18,910.00 IPS0004TST I/Informer-Test License (IPSCADCUST-IPS0004TST) 1 0.00 $0.00 IP500046CK I/Informer- Backup License (IPS0004BCK) 1 0.00 $0.00 IP50004RDT I/Informer- Redundant License (IPS0004RDT) 1 22,594.00 $22,594.00 Optional 1st Year Software Maintenance Subtotal:) $111,537.00 l IPSPRCMDL_$031315$(Master) - 3 of3 U) z O H Q O a O U LL O z O U) r.1 U L ca i / (D E E ca CO z 5 0 U LL LL w ry Z) U) LL E: 06 w LL z O w 2 CY) ti LO LO N N O O W O N N O N N CIO z 1 _ O � H � O U U Q ti O N w J N (Y) Cfl L O� E L 0 3 O a +� p O a1 jL O z — ca Z 21) L i a w IL w U) LLw U U H w LL Ch Ch 24 >Q 00 LO 2 a Lo M �a c� LUz w0 zZ) LOM o2co �0� z O cv Q C,4 Cfl LO O>Q oa � M i O = P U QM�E .� a�Q Ez �w zz = m �zU) E w_ow C) z oQw o —M2LL0 i U L c^ Wu + ^ U) W E cu z U) I 0 U LL tl E� vJ Ln c 0 L O Q L O U w 0 c 0 w O A: ai E L Q ai (6 O LL a) m z c w a N r) 44 �i 1 IS, Z •A 00 1 ml cu z clw T i U N cn U O U U Of O 0 0 U 0 c a 0 0 a� a ml 0 cn``�^1 (w n/ G w_ w C G cn cn N Q o N 0 Q CO �_ w o G� U n ti p� o LU z z z O r O O o A� w U O N 0 a co o 0 0 0 z Z Q Q %ry ' •� O O �+ .� Co O De E Q- O z O W o U m U o E am m 0 N U 2 _ _ ++ > i >+ 0 a 0 z E � a Q L Q U o= z w m Q •— c� c� _ �' Of (If Ez — > 0 w Q LU o~ O H O W m+ + m > > 0 L- z U z IL 0 LL 0 U) N J W W a m a N_ W m aw co Ln 0 Q EL 0 u a m 05 m 0 m 0 w 0 (D u) 0 a N N Z A c LU A N r) 2 W z LO O co ti LO ti i 00 LO ti LO M I O WE LO 0 N N N_ O a� m WA 2 W z LO O cy') H 0 z T- r-- (.0 Ltd ti i 00 LO ti LO M J Q z O 0 LO 0 N N N_ O a� m WA U z W H (n (n z O F- ry O 0- 0/ O J J i W H z W a W W W U) U) a 0 N L 0 f o N 0 rn N N N U m 0 w LZ J LL Lli LLI Q J Q C14ti ti o -6 N v m o a, c U) o o C o d a)U L d O N z W W o 2 Q (� ~ z 0 cn z Q o z F- c) (Y, ti CD Ltd ti i LO ti LO co z O co m CO O N_ W m 0) (9 LS O O_ d O I I a m 05 m (a 0 w 0 o u) 0 0- a) E m z �c w A N 0 16 16 16 16 16 (6 16 E E E E E E E O O O O O O O LL LL LL LL LL LL LL 0 0 0 0 0 N N N N N N N .3E E E E E E E N N N N N N N M O > > > > > > > m O O O N N N >- LLO Z} LLO � N w w w w w w w Z N N N Q ti a Q I M M a a a a a 00 LO _ LO li o 0 o w w w w w w w 2 ti a 2 ti } a Lo ca W a Lo Enl Q Q Q Q Q Q Q O a cn a L z z z z z z z C 2 CI Q Q Q Q Q Q Q _ H _ � ; Z w Z A. Q w z o rn W r- c9 Ln (� a Z O U) Z Z O is i o 0 0 0 0 0 0 Q U) Q Q O E N N N N N N N z LO Q ) w Lo Q C C , N N u N N N O N c\ N CD CD CD v H N M 2E H Cn cM Q N N N p o 0 0 0 0 0 0 0 n a) E m z �c w A N 0 16 16 (6 (6 (6 C6 (6 (6 (6 16 16 (6 16 (6 16 (6 (6 (6 O O O O O O O O O O O O O O O O O O LL LL LL LL LL LL LL LL LL LL LL LL LL LL LL LL LL LL 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 a) a) a) a) a) a) a) a) a) a) a) a) a) a) a) a) a) a) 0) I) 0) = 0) = I) 0) = 0) 0) 0) 0) cm 0) cm cm 0) m m m az az cu m az co az m m az m m m m az E E E .E .E .E .E .E .E E .E .E E E E E E E m m m m m ai m m m m m m m m m > >m m m > > > > > > > > > > > > > > > > O O O O O O O O O O O w w w w w w w w w w w J J J J J J J J J J J Q Q a Q Q Q Q Q Q Q Q > > > > > > > > > > > z z z z z z z z z z z z z z z z z z z z z z Q Q Q Q Q Q Q Q Q Q Q M N O O 00 I— CD LO ',I - CD O O O O O O O O O O O O O O O O N N N N N N N N N N N co LO � m m LO m m coL!) O CA O LD O O � N N CD N — N — O — O O N M M 4 4 M 4 4 4 li7 Liz M CD O CDO O CD CD CD O CD CD a a a a 0 a 0 0 a Q Q Q a Q Q Q Q Q z z z z z z z z z Q Q Q Q Q Q Q Q Q co N O O M r— (D m O O O O m O Cn Cn O O O O O O O O O O N N N N ti It 000 N - Lf O O N O O N M O 4 4 M L!� 4 4 LC) O O O O O O O O O m a N_ W m 0) (D Ln O O_ d O I I a m 05 m (a 0 w 0 o Ln 0 0-