Loading...
The URL can be used to link to this page
Your browser does not support the video tag.
Home
My WebLink
About
Back-Up Documents
ACCESSING COMPETED CO-OP and GOVERNMENTAL CONTRACTS CHECK LIST CONTRACT NO.: RFP 21-02 PROCUREMENT CONTRACTING OFFICER: Richard n cLaren DATE SUBMITTED: 08/16/2022 TITLE: P99ye k a P e Ca Sheriff's Office RFP 21-02 INTERGRAPH CORPORATION through Hexaga., Safety, ',restructure & Geaspat.., D.--- Access i rag Coops 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 n Award Summary Form for Director � or City Manager tanager (if applicable) n Resolution Item Summary Form (for Commission Approval — if applicable) n (Resolution (for Commission Approval — if applicable) n Copy of this checklist signed by the Director Co-op/Governmental Agency Documents — to be included in Approval Package 01 Z COPY 02 Z Copy 03 Z Copy 04 Z COPY 05 Z COPY NOTES: of Tally/Evaluation Results (score sheets, ranking or summary) of Contract?s Advertisement & Distribution information of Contract/Solicitation Being Accessed of Award Sheet/Approval Documents of Proposal/Bid 8 APPROVED as a contract which was entered into pursuant to a competitive process in compliance with pity laws, poi icies and procedures. ❑ NOT APPROVED as a contract laws, policies and procedures. which was entered into pursuant to a competitive process in compliance with City Annie Perez, CPPO Director, Department of Procurement 10/8/1 PINELLAS COUNTY SHERIFF'S OFFICE PRIME INTER -OFFICE MEMO DATE: March 9th, 2022 Q ‘#.&:='.N.)--‘47`'4Illki TO: Sheriff Bob Gualtieri FROM: Director Thomas Lancto, 54077 m PRIME \'' SUBJECT: Proposal Evaluation and Recommendation for RFP 21-02 The award recommendation for the above -referenced Request for Proposal is submitted for your review and concurrence. HISTORY On May 28th, 2021, the Purchasing Division solicited a Request for Proposal (RFP) for a Computer -Aided Dispatch (CAD), Records Management System (RMS), and Mobile Data Terminal (MDT) solution. The objective of the RFP was to contract with a qualified and experienced company to provide a singular, regional, comprehensive, configurable, fully integrated CAD, RMS, and MDT solution to increase efficiencies by reducing repetition of data entry and saving time in an emergency. The RFP was issued with evaluation criteria and a supplemental Requirements Matrix answered by the Respondents to ensure the objective was met. The Respondents were scored on; (1) Vendor Related Information; (2) Technology Requirements; (3) Implementation Requirements; (4) Functional Requirements; and (4) Pricing, Cost Elements and Total Five -Year Cost. Purchasing Manager Eric Vincent opened the Proposals on August 16th, 2021. Of the six (6) Proposals received, all were responsive; however, CentralSquare was not evaluated due to the Pinellas County Sheriffs Office, Clearwater Police Department, and Largo Police Department's prior experience with the company. Additionally, CentralSquare's abysmal customer service and lack of responsiveness to the needs of the organizations led to the decision not to proceed with that company. The responsive companies evaluated were: • Hexagon • Mark43 • Tyler Technologies • Soma Global, Inc • Motorola Solutions PROPOSAL EVALUATION PROCESS The Proposals were evaluated by a cross -agency team, including the Pinellas County Sheriff's Office, Pinellas County Safety and Emergency Services, Pinellas Fire Chief's Association, Clearwater Police Department, Largo Police Department, Pinellas Park Police Department, St. Petersburg Police Department, Belleair Police Department, and the Tarpon Springs Police Department. Additionally, the Purchasing Division evaluated each Proposal for responsiveness/compliance and cost. After careful evaluation and thoughtful consideration of the five Proposals, the Committee invited all vendors to demonstrate their products. Members asked the vendors to address specific questions and concerns relating to product functionality, support, training, data migration, implementation, and costs. The Committee had discussions immediately after each vendor completed their demonstrations. These week-long vendor demonstrations were conducted from October 18`h, 2021, through December 10th, 2021. On December 10th, 2021, the Committee held a public meeting to "short-list" vendors. During this meeting, the Committee decided it would no longer consider Mark43 because they could not adequately support 911, Fire, and EMS requirements. Mark43 also lacked the functionality needed by the law enforcement component of the Committee. The law enforcement group of the Committee decided it would no longer consider Motorola due to their on -premise, legacy product not meeting the needs of the law enforcement side of the Consortium. However, 911, Fire, and EMS did not share that concern and felt the product could meet their needs. The Committee voiced additional concerns about Soma Global and its ability to complete a project of our magnitude. Later, I spoke with Soma Global's references about the product and determined that two similar -sized organizations to ours were not "live" with the Soma Global solution after years of work. Neither agency recommended we proceed with Soma Global. Soma Global is a small, new company of sixty-eight employees. Soma Global's size, lack of product maturity for the 911/Fire/EMS group, and lack of a live organization of our size presented significant risk and were of concern to the Committee. On January 27th, 2022, the Committee met to discuss which remaining vendors to bring back for a hands-on lab. The Committee discussed Tyler Technologies, and the majority of the group did not wish to bring Tyler Technologies back for a lab environment because of their legacy software and lack of a clear roadmap to move to a browser -based solution. In addition, there was concern about putting staff through the change resulting from this CAD/RMS/Mobile implementation and the impending change the Consortium would have to put their team through a second time if Tyler Technologies updated their platform. After considerable discussion, the Committee invited Hexagon to provide a hands-on lab for Consortium members on January 20th and 21 S`. Committee and team members were afforded one hour of training and explored the system for three hours. The general feedback from participants was that the software seemed easy to use, and they particularly liked the Records Management System. Finally, the Committee brought Hexagon back on February 8th and 9th, as well as February 15th and 16th, to review the RFP requirements matrix where they answered, "No," or, "Yes, but requires customization and cost." Many of the items previously marked "No" organically changed to "Yes" because the product had matured and the current version met the requirement. Hexagon verbally agreed to update their software to meet items of significant concern to Committee members. SCORING The average score method for final scoring was used based on the evaluation criteria outlined in the RFP. Hexagon scored the highest, obtaining 77 of a possible 100 total points. Copies of each vendor's individual and entire committee scoring sheets are attached. The vendors scored as follows: Scoring - Commissary Vendor Related Information Technologyimplementation Requirements Requirements Functional Requirements Pricing, Cost Elements and Total Fne-Year Cost Total 0 - 15 Points 0. 15 Points 0 - 20 Points 0 - 40 Points 0 - 10 Points 0 - 100 Points Intergraph Corporation (Hexagon) 12 12 16 31 6 77 Mark43,lnc. 9 10 12 22 5 58 Tyler Technologies, Inc. 10 9 15 27 7 68 Soma Global, Inc 7 10 10 20 6 54 Motorola Solutions, Inc 9 8 13 24 7 61 COSTS: Based on submitted materials, the cost of Hexagon for year one is approximately $10,345,618.00, with a five-year total cost of ownership (TCO) estimated to be $20,755,078.00. The following chart summarizes the TCO for five years. Vendor Year 1 Year 2 Year 3 Year 4 Year S S-Vinar Tyler Technologies Motorola Soma Global Mark43 Hexagon $ 10,345,618.00 5 2,602,365.00 5 2,602,365.00 $ 2,602,365.00 S 2,602,365.00 5 20,755,078.00 530.000 000 00 S25.000,000.00 520,000,000.00 515,000,000.00 S10.000.000 00 $5.000.000 00 CAD/RMS 5-Near TCO RECOMMENDATION Hexagon outscored all vendors in all areas except Pricing, Cost Elements, and Total Five -Year Costs. As shown above, Hexagon's pricing was mid -point of other vendors and not unreasonable. On March 9th, 2022, the PRIME Board held a public meeting to hear the scoring results and recommend a vendor award for the Countywide CAD/RMS/Mobile project. The board of directors voted unanimously to move forward with Hexagon. After a thorough evaluation by the Committee, I recommend an award be made to Hexagon. While other Respondents also offered good overall Proposals, Hexagon can provide a modern, mobile - first, cloud -first technology platform that best fits the needs of all the Consortium agencies. In addition, Hexagon's company size can provide services, training, and support with expertise at a comparable overall cost. Based on their Proposal and experience, Hexagon offers the best value in support of the countywide CAD/RMS/Mobile project. Intergraph Corporation (Hexagon' Vendor: Intergraph Corooration (Megaton' 1 Vendor Related Information PCSO 12 0-15 points CPD 1LS PPPD LPD TSPD SPPD BPD FD R911 Avg 10 11 12 12 10 13 13 12 2 Technology Requirements PCSO 14,, 0-15 poln s CPD 11.25i PPPD 11 LPD TSPD SPPD BPD FD R911 9 14 14 10' 12.5 11 Avg 12 3 PCSO CPD PPPD Implementation Requirements 18 0-20 points 16.25 LPD 15 TSPD SPPD BPD FD R911 15 8 15 17 15 Avg 16 PCSO CPD PPPD LPD 'TSPD SPPD BPD FD R911 1._ 35 Avg 31 4 Functional Requirements Mark43. Inc.. Vendor. -Mark43. lnc., 1 Vendor Related Information PCSO 9 0-15 points CPO 10.5 PPPD 9 (PI) 9 TSPD 10 SPPD BPD FD R911 Avg PCSO '"CPD PPPD LPD TSPD SPPD BPD FD R911 Ave 11 2 Technology Requirements 0-15 points Tyler Technolo,IeF, Inc. 1 Vendor: Tyler Technologies. Inc. PCSO CPD PPPD 1.1,0 TSPD SPPD BPD FD R911 Avg 1 Vendor Related Information 12 11 2 Vendor: 0-15 points 1 Some Gh&bal. Inc Soma Gyp'. Inc Vendor Related Information PCSO CPD PPPD LPD TSPD SPPD BPD FD 2 0-15 points 5.5 7 13 13 11 4 2 Technology Regolrements PCSO 9 415 points CPD PPPD LPD 8.5 11 12 TSPD 11 SPPD 3 Implemen atlon Requirements BPD 7 12 FD 5 PC50 12 "0-20 point's CPD 12.25 PPPD LPD TSPD 14 SPPD BPD 11 12 FD 8.5 32 0-40 points 32 35 29 26 32 25 35.5 R911 vg 2 4 Functlo PCSO CPD PPPD LPD TSPD SPPD BPD FD .R911 Avg 5 Pricing, Cost Elements and Total Five -Year Cot PCSO 8 0-10 pain s PCSO CPD 4 CPD PPPD 6 -- PPPD LPD 6 LPD TSPD 2 TSPD SPPO 10 SPPD BPD 5 BPD 8 FD 8 R911 FD R911 Avg Total 7 Avg al Requirements 0-40 points R911 Avg PCSO CPD PPPD LPD TSPD SPPD BPD FD R911 Avg R911 Avg PCSO CPD PPPD lPD TSPD SPPD BPD FO R911 2 Technology Requirements 14 0-15 points 12 8 15 14.5 12 9 4.5 Avg 37 implementation Requirements _ 1620 points 4 Functional Requirements PCSO 30 0-40 points CPD PPPD LPD TSPD SPPD BPD 5 Pricing, Cost Elements and Total Five -Year Total I 0-10 points FD R911 Avg PCSO cP0 PPPD LPD TSPD SPPD BPD FD R911 Avg 18 35 30 29.5 26 30 11 30 27 Pcs0 CPD PPPD LPD TSPD SPPD BPD FD R911 Avg 3 Implementation Requirements 4 Motorola Solutions, Inc Vendor: Motorola Solutions, Inc 1 PCSO CPD PPPD LP0 TSPD SPPD BPD FD R911 Avg Vendor Related Information 10 0-15 points 6.25 12 2 Technology Requirements • PCSO 1 0-15 points CPD PPPD (P0 TSPD SPPD BPD .90 R911 Avg 3 Implementation Requirements 0-20 points PCSO 11 0-20 points CPD PPPD LPD TSPD SPPO BPD FD R911 Avg Functional Requirements PCSO .CPD "_PPPD LPD 'TSPD SPPD BPD FD R911 Avg 5 Pricing, Cost Elements and Total Five -Year I 0-10 points PCSO CPO PPPD 6 5 7 3 10 3 9 7 15 27 30 32 30 30 5 11' 20 0-40 points PCSO CPD PPPD LPD TSPD SPPD 8PD FD R911 Avg 5 Pdcng, Cost Elements and Total Five -Year S 0-10 points 9CSO 5 CPD 7 PPPD LPD 9t Total L "7 TSPD LPD TSPD 4 Functional Requirements 20 15.5 27 31 27 13 15 35.5 33 24I 0-40 points PCSO Clw PP PD Largo PP FD EMS 911 EMS 5 Pricing, Cost Elements aad Total five -Year Cost 8 0-10 points 6 6 51 SPPD BPD FD R911 10 Avg 3 4.5 Total SPPD BP0 FD R911 Avg Total 8 7.5 9 61 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS 12 PROPOSER NAME Hexagon EVALUATION COMMITTEE MEMBER: ChiefJ. Young/ Tarpon Springs Police Department 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score 12.00 Comments: History with larger and multiple jurisdictions. Connectivity issues during mobile and RMS demo. Good references., however. no live cloud based customers. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 14. Comments: Not live yet, uses Azure which is preferable to AWS. Supports all major browsers. Support modern operating systems, cloud based, no specific server requirements 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 15.00 Comments: Project management team presented PM practices and discussed PMO. Project management team reviewed change management procedures. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 26. Comments: User interface has a lot of white space, command line issues, shortcut codes lacking. System not in production. System administration re• uires IT, and has a global config for the consortium. Allows to save redactions to system. Machine learning AI with analytics not available. Analytics does not include interactive dashboards which can be viewed within CAD or RMS. Personnel would have to be provided OnCall AnalvticsNiewer or Analytics/Author privileges. No help file in command line. No 2nd in route notifications. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: 0 —10 POINTS - Score 2 TOTAL 69.00 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Mark43 EVALUATION COMMITTEE MEMBER: ChiefJ. Young/ Tarpon Sprints Police Department 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 10. Comments: Fire/EMS lacking. Interface was "clunky", non -intuitive during onsite RMS demonstration. Good law enforcement references, live cloud based customers 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 14. Comments: Live cloud platform, uses AWS not as preferable as Azure. Supports all major browsers. Client supports modern operating systems, cloud based, on-prem server requires Linux, mobile iOS app not released yet (Android approved) 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 14 Comments: 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 28 Comments: No day/night mode. Not all features live yet. Lack of fire/ems functionality. Allows to save redactions to system. Cannot attach picture to CAD event. No iOS mobile app released vet. No 2nd in route notifications. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: 0 — 10 POINTS - Score 2.5 TOTAL 68.50 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Tyler Technologies EVALUATION COMMITTEE MEMBER: ChiefJ. Young/ Tarpon Springs Police Department 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score 12. Comments: In use locally. Demos were very user friendly. Good, local/area law enforcement references; however, no live cloud based customers 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 11. Comments: Not live yet, uses AWS not as preferable as Azure, cloud platform requires users to connect to on-prem infrastructure. CAD is not browser based. Support modern operating systems, cloud based, CAD thick client may depend on client OS features. Architecture relies on prem infrastructure. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 14. Comments: 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 29.5 Comments: Interface is user friendly, configurable; however, users need to open separate applications to navigate system. Does not allow to save redactions to system. Ability to cache map for offline use. No 2nd in route notifications. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: 0 —10 POINTS - Score 3. TOTAL 69.50 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Soma Global, Inc EVALUATION COMMITTEE MEMBER: ChiefJ. Young/ Tarpon Springs Police Department 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 13. Comments: Fire/EMS and property/evidence workflow lacking. History with larger and multiple jurisdictions, in use locally. CAD demo very user friendly, geofencing not complete. RMS demo very user friendly, customizable. Good law enforcement references, live cloud based customers 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 14.5 Comments: Live cloud platform, uses AWS not as preferable as Azure. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 14. Comments: 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 30. Comments: Interface is user friendly and configurable, but no day mode for CAD. Not all features live yet, e.g. geofencing, street closing. Lack of fire/ems functionality. Allows to save redactions to system. ESRI platform, direct connection to enterprise GIS. No 2nd in route notifications. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: 0 — 10 POINTS - Score 10 TOTAL 81.50 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Motorola Solutions EVALUATION COMMITTEE MEMBER: ChiefJ. Young/ Tarpon Springs Police Department 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 10. Comments: No cloud based solution. Highest number of no responses. User interface not friendly, difficult to navigate. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 11 Comments: Proposal is for on-prem solution. CAD is not browser based. Lists Chrome, Edge, & Firefox support. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 14. Comments: 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 27 Comments: Have to have admin rights to change any screens. Geofencing in development. Machine learning Al with analytics not available. Custom reporting only within preset criteria. Current CAD mobile map is different. One command line per screen 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: 0 —10 POINTS - Score 5 TOTAL 67. SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Hexagon EVALUATION COMMITTEE MEMBER: Brett Schlatterer 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 13 Comments: RFP was very well put together and articulated all needs appropriately. Had multiple supporting documents, had the best fire based RMS system solution 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 12.5 Comments: Although the cloud solution is not deployed anywhere yet. they have a firm foundation with many customers switching over and the demo proved the flexability and capabilities in their system 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 17 Comments: Hexagon had some of their customers review their system and discussed how the implementation went which proves they can do the same for us. They also have their Custom Rules Engine (CRE) that allows for many agency defined interfaces 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 35.5 Comments: They had the most versatile and customizable platform that satisfies the entire consortium and individual agency requirements 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 8 Comments: Click here to enter tc:i. SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS TOTAL 86 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Mark43 EVALUATION COMMITTEE MEMBER: Brett Schlatterer 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 7.5 Comments: Clck: here enter text. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 6 Comments: Although it was a cloud based solution, the system was very static and did not have some of the simple configurations such as display settings, layout and day/night mode 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 8.5 Comments: Flick here to enter text, 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 17.5 Comments: Was lacking in many for the fire deployment capabilities such as AVL and the ability to do condition level change dispatching 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: Click here to enter text 0 —10 POINTS - Score 6 TOTAL 45.5 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Tyler Technologies EVALUATION COMMITTEE MEMBER: Brett Schlaterer 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score 4 Comments: Well organized but did not included a Fire/EMS RMS solution. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 5 Comments: System appeared to just be an on-prem product that has been migrated to the cloud. Possible limited customization, does not appear as fluid. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 7 Comments: Previous Fire/EMS industry experience with product and RMS side indicated potential challenges. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 1 1 Comments: \o Fire/EMS RMS presented. Is same provider of Mobile Eyes, but does not allow for map layer preplans and live preplan update from inspection actions and changes. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 3 Comments: Difficult to determine without Fire/EMS RMS product TOTAL 30 SCORING SHEET R.F.P. 21-02 — CAD/MobileIRMS PROPOSER NAME Soma Global, Inc EVALUATION COMMITTEE MEMBER: Brett Schlatterer 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 4 Comments: FD Proposals were not detailed, included mostly a list of interfaces and leaning on the Polk implementation 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 — 15 POINTS - Score 4.5 Comments: Although they can most likely build a Fire solution. they had no proven content and no one on their staff to lead the development 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 -- 20 POINTS - Score 4.5 Comments: There have been no major fire department deployments and phone calls to like sized agencies caused flags in their implementation ability 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score I I Comments: Most of their system was all integration and required custom building from our end 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: C lk k here ¢o enzer'ex�. 0 — 10 POINTS - Score 4.5 TOTAL 28.5 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Motorola Solutions EVALUATION COMMITTEE MEMBER: Brett Schlatterer 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score 10.5 Comments: Although the RFP was well written, is technically was not for a cloud based solution 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 9 Comments: Solution was an on prem with consideration to moving to cloud based in the future which would cause another comprehensive look at the system and compatibility of the system 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 15 Comments: Motorola is a proven solution and should have no issues transferring out system over 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 35.5 Comments: Motorola's package was very appealing for the fire service, especially the integration with the radios. They had one of the best demonstrations and all their products worked as intended during the demo 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: Okk here ¢o enter text. 0 —10 POINTS - Score 7.5 TOTAL 77.5 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Hexagon c,ZiAc 3,4 cc gw.W J 1%9 EVALUATION COMMITTEE MEMBER: Clic here to enter text. 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score Click Comments: Click here to enter text. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score Click he Comments: Click here to enter text. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, confidence that the vendor can deliver. Comments: Click here to enter text. er text. xt. 0 — 20 POINTS - Score cliff er t. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, interfaces, requirements matrix, disaster preparedness, will the agency requirements be met. 0 — 40 POINTS - Score CI' . held text. Comments: Click here to enter text. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: Click here to enter text. 0 —10 POINTS - Score Clic i -Renter text. SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Mark43 EVALUATION COMMITTEE MEMBER: � i 'IfreYo triter text. G !' "Ao 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score Comments: Click here to enter text. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, compatibility, simple to use, easily mobile, flexibility. 0 —15 POINTS - Score click h Comments: Click here to enter text. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, confidence that the vendor can deliver. 0 — 20 POINTS - Score clic Comments: Click here to enter text. 4. Functional Requirements - Factors to be considered in the score: customer site visits, interfaces, requirements matrix, disaster preparedness, will the agency requirements be met. 0 — 40 POINTS - Score Comments: Click here to enter text. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score cup Comments: Click here to enter text. xt. ter text. SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Tyler Technologies EVALUATION COMMITTEE MEMBER: Click ere t-o enter texs, ia. 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. �/� 0 -15 POINTS - Score k'he ee fs-1 xt. Comments: Click here to enter text. 2. Technology Requirements - Factors to be considered in the score: is their solutio future proof, compatibility, simple to use, easily mobile, flexibility. 0 —15 POINTS - Sco Comments: Click here to enter text. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, confidence that the vendor can deliver. Comments: Click here to enter text. nter text. 0 — 20 POINTS - Score Click ter text. 4. Functional Requirements - Factors to be considered in the score: customer site visits, interfaces, requirements matrix, disaster preparedness, will the agency requirements be met. 0 — 40 POINTS - Score dick nter text. Comments: Click here to enter text. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score Click Comments: Click here to enter text. TOTAL r text. SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Soma Global. Inc ,e f ,ate✓ 44+ci$�� c PD EVALUATION COMMITTEE MEMBER: lic ere to enter text. 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score Click Comments: Click here to enter text. 4M0ext. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, compatibility, simple to use, easily mobile, flexibility. 0 —15 POINTS - Score cfic Comments: Click here to enter text. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, confidence that the vendor can deliver. 0 — 20 POINTS - Score Click Comments: Click here to enter text. 4. Functional Requirements - Factors to be considered in the score: customer site visits, interfaces, requirements matrix, disaster preparedness, will the agency requirements be met. Comments: Click here to enter text. r text. 0 — 40 POINTS - Score C ick r enter text. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: Click here to enter text. 0 —10 POINTS - Score cis TOTAL ter text. SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Motorola Solutions Nth )AX•f;IfsMierie,C,eleVRoliKe4 EVALUATION COMMITTEE MEMBER: Click here to enter text. 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score clic Comments: Click here to enter text. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, compatibility, simple to use, easily mobile, flexibility. 3.7.5- 0 —15 POINTS - Score Clic e er text. Comments: Click here to enter text. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, confidence that the vendor can deliver. 0 — 20 POINTS - Score cli. her nter text. Comments: Click here to enter text. 4. Functional Requirements - Factors to be considered in the score: customer site visits, interfaces, requirements matrix, disaster preparedness, will the agenc requirements be met. 0 — 40 POINTS - Sco er text. Comments: Click here to enter text. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score ci►" ere to enter text. Comments: Click here to enter text. TOTAL SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Hexagon EVALUATION COMMITTEE MEMBER: Michael McDonald — St. Petersburg PD 1. Vendor Related Information - Vendor's overall response to the R.F.F. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 12 Comments: Hexagon was one of the top presenters overall. The presenters knew from a top level their product extremely well. When the presenters did not know an answer, they were quickly able to get an answer from other team members not on site. The RFP was presented in an organized manner and was easy to follow. It was disappointing to leam the CAD product was not being utilized in a `live' environment anywhere. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 14 Comments: The platform Hexagon uses, web -based running in the cloud, is the current platform most service providers in LE, as well as non -LE companies, use. It would be nice if their CRE custom rule engine allows for API integration and would allow us to build our own modules/custom features. The technology stack they have adopted will be fine long term. The robustness of the solution and their decision to roll COTS as a feature will benefit them on the backend, but once the footprint of the install base increases, workflow/module customization requests will start to impact all users. Through all engagements with this vendor, it sounded like they were prioritizing the enhancements based on the size of the implementation. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 18 Comments: Hexagon has a lot of experience in implementing multi agency configurations as well as having a large support staff to assist during implementation. Training should be done by a Hexagon staff member while train -the -trainer will continue after implementation. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 32 Comments: The Hexagon product covers a ton of functional needs that all agencies have for their work flows, user experience, interfaces, etc.. The RMS product is probably the strongest of all vendors. However, the SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS CAD/MOBILE product is still far away from being ready and functional in a live environment to meet RFP requirements. Based on the roadmaps shared and projected roadmaps, there is hope that by the time we would implement that the CAD/MOBILE applications would see significant improvements to make the product more functional. DR/BR will be from Hexagon's side of things, but we need to put some work in on our end in creating redundant Internet access, both internally (multiple providers to the building and perhaps some dedicated connections between agencies (i.e. PPPD loses their fiber to the Internet, but can redundantly get to CAD through PSCO/SPPD etc, through some well thought out infrastructure. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 — 10 POINTS - Score 10 Comments: Pricing, post RFP response was much more realistic. I think the fees are fine, expected even, just need to make sure we get what we can covered under the site licenses, i.e. currently purchased applications, proposed middleware on their roadmap and perhaps integrations between them and other top tier vendors. So, if they decide in a couple years to integrate directly into Motorola radios, we should get that per our contract. TOTAL 86/100 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Mark43 EVALUATION COMMITTEE MEMBER: Michael McDonald — St. Petersburg PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 11 Comments: Mark 43 did not go through the RFP bullet points during their presentation as requested. I think they were well organized, had team members available to answer questions and were very professional and honest on where their product currently is. Their products lacked maturity and so many of the asks on our RFP were "Roadmapped" items. I think their products and technology stack would eventually meet our needs, but not within the timeframe of this project. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 12 Comments: I think their technology stack is fine, though still in the early stages of development. It was clear that they were looking to cover a lot of agency needs (mobile, web, CAD, Records. etc.) in a short amount of time, so while their implementation was stable, it was lacking features. I think their API implementation was solid and provided great, accessible documentation 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 11 Comments: Given their technology stack, implementation would have been relatively quick, with the majority of the work falling on us from configuration and network redundancy. Mark 43 is one of the smaller vendors in terms of support capability. They have smart people that seem to embrace the challenges of improving their product and being able to implement their services, but do they have enough support staff to support a consortium of this size? They do not have enough large deployments with multi agency configurations such as ours, to have much confidence in this vendor. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 20 Comments: Both their CAD/MOBILE and RMS products are functional. However, they are functional in the most basic forms of the word. It can perform the SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS consortium's base functions and needs but their products seemed to lack the flexibility, customization, and advanced features that some of the other vendors offered. Maybe in 5 years they will have a fully-fledged product with more customization and integration. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 — 10 POINTS - Score 8 Comments: Their pricing was mostly adequate for what they were demoing but given that a large number of features we were looking for were not included in their current solution, perhaps it was not. TOTAL 62/100 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Tyler Technologies EVALUATION COMMITTEE MEMBER: Michael McDonald — St. Petersburg PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 11 Comments: They walked through some of the RFP items, they have a lot of references and experience with like sized implementations. They covered most of the elements that were needed. During the demonstration, they called upon a current Tyler client (Pinellas Park) to explain how a lot of the product features work and what it is capable of. They should have brought the staff members along with them who had the knowledge of the product and not rely on one of our agencies to show the product. They had some of the better analytics dashboards. Clearly a large enough organization to support the consortium's needs. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 7 Comments: This is NOT modern technology; their technology stack was the most dated of all the vendors. User interface was very outdated and difficult to look at. It can be compatible with the hundreds of programs they have bought to integrate into their product but how does the integrated applications work together? It was clear that acquiring software that did the job was more important than presenting a cohesive looking solution. Looks aside, it did meet most of the requirements and did work during the demo. If we went with this solution, on -site IT staff would have to grow in order to support the many applications needed. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 18 Comments: Due to their size, I have no doubts they could both implement and support an installation of our size. Their references appeared to be roughly the same order of magnitude as ours, with multiple agencies and high user load. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 26 Comments: Functionally, they checked most of the requirements. The demos were adequate and the staff knowledgeable. DR/BR plans were as good as could SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS be expected given their technology stack and would likely keep us at 99% uptime in the event of a large-scale issue as they are one of the few vendors with on premise product solutions. Their UI/UX was overwhelmingly the worst of the vendors we reviewed and it was clear they were working from the perspective that investment in codebase should be expected to last 15+ years or more. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 10 Comments: Price seemed fine, with site licenses being offered. TOTAL 72/100 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Soma Global, Inc EVALUATION COMMITTEE MEMBER: Michael McDonald — St. Petersburg PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 11 Comments: They didn't go through the RFP bullet points as requested. The presenter was very unlikeable, and I think that hurt the demonstration of the product. They did however respond to some big questions the consortium had and even called in additional help when things weren't going as planned. Soma is a very small company with very few employees. They should invest in hiring a trainer/presenter to showcase their product instead of having the owner present. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 12 Comments: This was the best use of technology that we saw from any vendor. The potential with so much flexibility, customization and API integration was beautiful to watch. Extremely future proof, simple to use and they give you access to their schema builder. They also brought in using technologies none of the other vendors did, smart watches (for panic buttons), Apple's CarPlay for example. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 8 Comments: There are HUGE concerns with implementation with an organization of this size. They have less than 70 total employees and it is very unlikely they would be able to hire enough staff to be able to support a consortium of this size. There are also concerns of SOMA being bought out by bigger vendors. They didn't have many if any at all other like size deployments that we could count on to give confidence in their abilities to implement and deploy their product. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 30 Comments: The product was very functional and with the abilities to mold the platform into what we needed it to be was a huge plus. This also could be a negative as well as the product that was shown was not a fully built product SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS with full modules and interfaces for a live agency. They were one of the few vendors that showed their offline mode for disaster preparedness. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 10 Comments: Cost presented was adequate. I could see the price going up with this product as the implementation progressed. TOTAL 71 / 100 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Motorola Solutions EVALUATION COMMITTEE MEMBER: Michael McDonald — St. Petersburg PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 7 Comments: They have the most NOs of any other vendor and they do NOT offer a cloud solution. Their responses in the RFP were clearly not quality checked and was poorly written. The presenter indicated that we "don't know what we want" which is not a good way to start a presentation. They are however experienced with like size facilities and vendor references 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 6 Comments: Technology stack was extremely dated. While all the induvial parts functioned and worked together well given their technology choices, they weren't as open a platform as we would have liked. I saw no new innovative features and the product is worse than applications built and developed 10 years ago. They had some canned integrations but were not overly clear how much we could do ourselves. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 12 Comments: Motorola has a large band of employees, support, and resources that could help then in implementing their product with a consortium of this size. However, hearing some of the stories of clients who have worked with them in the past is not encouraging. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 13 Comments: The product can perform maybe the simplest of base functions for the consortium. It is not easy to use for the user, the interface lacks configurability and advanced features, and they did not meet the requirements of the RFP matrix. Overall, I feel they were the worst response for demo, UX/UI, requirements response and average for DR/BR given their technology stack. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 5 Comments: They would be most expensive in the long run given their licensing model. Additionally, we would be in the same mode of having to go to the vendor for everything and not be able to build/customize our own product. Given their size I feel they would have the resources to implement and support a project our size TOTAL 43/100 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Hexagon EVALUATION COMMITTEE MEMBER: Thomas Lancto 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like -sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 12 Comments: The vendor's proposal was clear and concise. I contacted several references, and they all spoke positively about Hexagon and their support. Hexagon has implemented many multi jurisdictional, consortium -style entities with positive results. The on -site demonstrations were thorough and informative; however, the presenter struggled with the command line functionality during the CAD demonstration. The vendor had plenty of resources on -site and remotely to answer questions throughout the RFP process. The vendor has not gone live with the OnCall CAD in any locations at this time. They are scheduled to go live in April in a nearby county. Additionally, Hexagon appears to have ample resources to support the consortium. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 14 Comments: Hexagon's product is mobile -first cloud -first as requested in the RFP. They have a browser -based application and also have a powerful app that runs on smartphones. The application seems easy to use and intuitive enough to require minimal training. The application runs in the Microsoft Azure Government cloud in six data centers across the U.S. Hexagon's platform appears to be well suited for the future. The browser -based, cross -platform application is easily accessible from anywhere. The mobile app further enhances the mobile -first requirement, providing all the features of OnCall Mobile in a smartphone application. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 18 Comments: Hexagon is a very large organization with strong financial backing. They have implemented other large organizations like the consortium and there is a strong confidence they can deliver a working product to the consortium. Hexagon is partnering with a third party to conduct data conversion. The SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS third party's primary function is to conduct data conversion and integration. Hexagon appears committed to making the consortium project a success; however, they do not have the product live for members to experience. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 32 Comments: Hexagon's product appears to be the best solution for the consortium, not just one agency or discipline. While there were enhancements the consortium would like to see, there were no "show stoppers" that would preclude the vendor from delivering a useful product. Speaking with other agencies using Hexagon's RMS or 9.4 CAD product, they were very satisfied with the product and with Hexagon's support. The application appears intuitive and easy to use. Since the application is redundant and resilient in data centers across the U.S., it will likely support a disaster situation. There were concerns from members about the layout of the mobile screen in laptop mobile environment. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 8 Comments: Hexagon's proposal included true unlimited site -license pricing, which was not the case with other vendors. Although the first year appears expensive compared to others, the ongoing annual maintenance fees are lower, resulting in a five year TCO which fell in the middle compared to other submissions. Being a large organization, Hexagon appears to have the resources necessary to meet the consortium's needs. TOTAL 84 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Mark43 EVALUATION COMMITTEE MEMBER: Thomas Lancto (V 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score 9 Comments: The vendor's presentation was well organized, albeit they did not follow the scenarios as requested. Mark43 is a small company that recently contracted with a large entity overseas. There was concern from members that Mark43 could deliver the product with all the items needed by the consortium. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0-15POINTS -Score 12 Comments: Mark43 built their product in the cloud. Their product is believed to be scalable and architecturally ready for the future. The product was compatible with Chrome and Edge, and many members commented that it appeared easy to use. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 12 Comments: Mark43 is a small company with the longest projected implementation period. Due to their limited number of like -sized multi jurisdictional organizations, there were concerns with Mark43's ability to implement and train our tier-1 consortium. Mark43 has limited experience with tier-1 multi jurisdictional implementations like the consortium. Consortium members were concerned with resource contention regarding a new contract overseas. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 19 Comments: Mark43's product was underdeveloped. It did not meet the needs of the consortium as a whole and was especially lacking in the Fire Department space. Simple functions such as attaching a picture to a message or call ticket were not available. Also, the critical function of adding custom fields to the RMS system was also not available. Many of the items the consortium needed were "coming" or on a roadmap but not currently available. The vendor had a significant number of "no"s in the requirements matrix. SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS There were concern over the configurability of the CAD screens and the settings were consortium wide rather than agency specific. There was limited functionality in the mobile. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 — 10 POINTS - Score 5 Comments: Mark43 was the second most expensive of the submittals. The shortcomings of the product, coupled with the price, were not the best value for the consortium. With a recent contract overseas, there were concerns the vendor would have resources to meet the needs of the consortium. TOTAL 57 SCORING SHEET R.F.P. 21-02—CAD/Mobile/RMS PROPOSER N AME Tyler Technologies EVALUATION COMMITTEE MEMBER: Thomas Lancto 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 11 Comments: During on -site demonstrations, the vendor did not appear to know the product as well as some of the consortium members in the audience. The presenter was corrected on several occasions about certain functionality of the system. The vendor did follow the scenarios supplied. Tyler is a large organization and has done other like -sized implementations. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 — 15 POINTS - Score 9 Comments: Tyler provides a hosted solution rather than a solution built in the cloud, which means the legacy client -server model has simply shifted to a hosted model. Tyler's thick client requires IT resources to support the installation and maintenance of the product. Tyler provided little information with regard to the roadmap of the system, indicating that they were approximately five years away from a web -based product. Because the product is client -server -based, it is not flexible. Tyler, however, has a smartphone application that appeared to work well. Tyler had the highest number of "no"s, or "yes, but requires customization and cost" to interfaces. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 17 Comments: Tyler is a large company with what we believe to be ample resources to implement and train consortium members, although their thick client install requires additional IT resources. Tyler is a large organization and has done other like -sized implementations. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 30 Comments: The Tyler suite is a series of noticeably different applications brought together as a package. The suite lacks synergy and gives the appearance of using other applications rather than a single product. The product's user interface needed significant upgrades and was clearly dated. The analytics SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS package, however, from a third party was impressive. The smartphone application appeared easy to use and well developed. The Tyler suite covered a wide range of application functionality. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 6 Comments: Tyler's five-year total cost of ownership pricing was mid -range of the submissions evaluated. Tyler is a large company with what we believe to be sufficient financial stability to support the project. TOTAL 73 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Soma Global, Inc EVALUATION COMMITTEE MEMBER: Thomas Lancto 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score 2_ Comments: During the on -site demonstrations, the presenter (co-owner) was very unorganized and hard to follow as he jumped from topic to topic in no particular order and did not follow the suggested scripts. The vendor has not gone live with any like -sized tier -one organizations like the consortium. Furthermore, the vendor's references from larger organizations were not favorable to Soma Global. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 — 15 POINTS - Score 14 Comments: Soma Global's product was built in the cloud and is highly scalable. The approach Soma Global has taken steps to future -proof their product. The application is cross -browser cross -platform compatible. The application appeared very easy to use and supported the mobile -first cloud - first desire of the consortium. The mobile application for smartphones needs further development. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 9 Comments: Based on Soma Global's web -based application platform, the implementation should be straightforward; however, there were concerns from the consortium that Soma Global's small number of employees would negatively impact the implementation. Reference checks supplied by Soma Global were not favorable to the company. There are no installations in similar sized tier -one organizations like the consortium. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 15 Comments: Soma Global presented what appeared to be an easy -to -use application. Members especially liked adding custom fields and creating forms and workflows easily. Unfortunately, the application is not mature and is missing many components, and offers little to 911/Fire/EMS. The application was lacking functionality for property and evidence. SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 5 Comments: Soma Global was the most expensive of the submissions evaluated and had the lowest number of "no"s checked in the requirements matrix. TOTAL 45 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER `ti AME Motorola Solutions EVALUATION COMMITTEE MEMBER: Thomas Lancto r� 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POI`+TS - Score 10 Comments: Motorola had a large complement of people on -site to present and answer questions which led us to believe they have resources to support the effort. Additionally, Motorola has experience with like -sized organizations similar to the consortium. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0-15POINTS - Score 5 Comments: Motorola was the only vendor to propose an on -premise solution, which opposes the mobile -first, cloud -first desire of the consortium. The solution architecture offered production servers in a single organization with a backup server at an off -site location, requiring manual intervention to bring online. Motorola's vision for the future was clouded by a conflicting statement of the Motorola team. A high-ranking member of Motorola indicated they did not support the cloud because they were not ready for it. The R.F.P. response stated, "This solution will expand as cloud solutions become more mature and reliable." A different Motorola representative indicated they were three to five years away from a web -based CAD/Mobile solution. The application was clearly dated and did not appear to bring many new features to the consortium, and in some cases, it was a step backward. Motorola did have integration with the radio system which 911 and the Fire Department liked. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 15 Comments: Motorola is a very large organization with ample resources. There is little doubt the vendor can deliver the product as presented. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 20 Comments: Motorola had a large team on -site for the vendor demonstrations. The team answered questions of consortium members and were professional in SCORIN G SHEET R.F.P. 21-02 — CAD/MobilefRMS their presentation. They were the only vendor to indicate they would complete all interfaces requested. The product user interface was the least impressive of the vendor offerings. The product was dated and the solution was not what we were looking for. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 — 10 POINTS - Score 8 Comments: Motorola answered "yes" to all requested interfaces. They were the second lowest priced vendor proposal. TOTAL 58 PROPOSER NAME Hexagon EVALUATION COMMITTEE MEMBER: Chief Doyle - Belleair PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 10 Comments: Appeared to have confusion with Initial response, clarified in subsequent meetings. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 10 Comments: Technology being brought has yet to be live. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 15 Comments: I feel they can implement but have concerns about thier timing to bring this live. 4. Functional Requirements - Factors to demonstrations, user experience, interfaces, will the consortium requirements be met. Comments: Product looks good, but again functional in a timely manner. be considered in the score: customer requirements matrix, disaster preparedness, 0 — 40 POINTS - Score 25 unable to determine if new version will be 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 — 10 POINTS - Score 5 Comments: Had to "reprice" the product after the demonstration. Backed by a larger foreign corporation that is not focused on public safety. Concerns they will spin off this business and we end up with a new company to work with for the future. TOTAL 70 PROPOSER NAME Mark43 EVALUATION COMMITTEE MEMBER: Chief Doyle - Belleair PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 8 Comments: I don't feel they have the size/support for our needs 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 10 Comments: Built in cloud, tech appears good, not far enough developed for our needs. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 12 Comments: Too small and new to handle our needs, haven't demonstated doing a large consortium venture and fire was not supported 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 20 Comments: Could not attach photo to message, weak on key functions 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 5 Comments: 2nd most expensive with little function TOTAL 55 PROPOSER NAME Tyler Technologies EVALUATION COMMITTEE MEMBER: Chief Doyle - Belleair PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 12 Comments: Experienced in our field, it's what they do as the core part of their business. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 12 Comments: Appears antiquated, it would be nicer if they were more future thinking and demonstative in their thinking. Develop more for the future anticipated needs of public safety. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 18 Comments: Understand our needs, have local contract, have the organizational structure to support our needs in the future 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 30 Comments: Did not bring fire product forward (New World), experience in Pinellas Park has been good with functionality 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 — 10 POINTS - Score 9 Comments: Priced fair, most solid public safety company with little fear of acquistion/takeover by any other company. It's their core business. TOTAL 81 PROPOSER NAME Soma Global, Inc EVALUATION COMMITTEE MEMBER: Chief Doyle - Belleair PD 1. Vendor Related Information - Vendor's overall response to the R.F.F. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 5 Comments: Appear too new 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 9 Comments: Poor presentation 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 10 Comments: Too small of an organization 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 5 Comments: Product does not appear fully built 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 3 Comments: Most costly, for an inferior product TOTAL 32 PROPOSER NAME Motorola Solutions EVALUATION COMMITTEE MEMBER: Chief Doyle - Belleair PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource avai labi I ity. 0-15POINTS - Score ? Comments: Well known, better in radio than software for our needs. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 7 Comments: appears equal or subpar to what we have today. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 13 Comments: Large organization, well staffed. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 15 Comments: Not fully in the cloud yet, but functional like our system today. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 8 Comments: Priced well but appears to have many add ons that can build the cost. TOTAL 50 SCORING SHEET R.F.P. 21-02 — C1 DiMobilefRMS PROPOSER NAME Hexagon EVALUATION COMMITTEE MEMBER: i',AWN, ?PAL - &sr CNisF 1. Vendor Related Information - !'endor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 10 Comments: The products demonstrated are in implementation stage and not in actual production 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 11 Comments: Solution was basic with several third party integrations required 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 14 CominentS: According to the sales lead, implementation is 24 months away. Currently there is no implementation phase with proof of concept to any customers. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces. requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POIN Ts - Score 35 Comments: 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 — 10 POINTS - Score 6 Comments: Offered a 40 percent discount after the initial proposal was provided. There is also a large cost for one year on site support. TOTAL 76 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Mark43 EVALU,\TIO\ COMMITTEE MEMBER: P2M /9Str4fir' 4/4„11./ 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the propoal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references. experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POIr TS - Score 9 Comments: 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility. simple to use, easily mobile, flexibility, security. 0 — 15 POINTS - Score 10 Comments: Limited customization with the multitude of technology 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 14 Comments: Currently has clients on the platform and functioning as demonstrated 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces. requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 32 Comments: Robust open API 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 — 10 POI N Ts - Score 8 Comments: TOTAL 73 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER "' AME Tyler Technologies EVALUATION COMMITTEE MEMBER: RNMAS A/tIC. — Asir ego-, Lail 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor' references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score if 10 Comments: Demonstrated a live and functioning system. Showed references to support con*ortium s. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0-15POINT.-Score 113 tt Comments: Proposed a complete solution to include citations,crashes,court integration/narcotics/ana lytics. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 15 Comments: 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 35 Comments: 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated how's for implementation enough or will it cost more). Comments: 0 —10 POINTS - Score 8 TOTAL 8s3 1 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER \ AME Soma Global, Inc EVALUATION. COMMITTEE MEMBER: aPurrf4.vss AGAR- 4S1 1 /Sir Air it 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 7 Comments: Inability to deliver based on the reference feedback 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 — 15 POINTS - Score 8 Comments: Inabiliry to deliver based on the reference feedback 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments. confidence that the vendor can deliver. 0 — 20 POINTS - Score a Comments: Lack of confidence in ability to deliver a product to the consortium 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 30 Comments: 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel cost.), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: 0-10POI N Ts - Score? TOTAL 61 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER N AM E Motorola Solutions EVALUATION COMMITTEE MEMBER: RA Usti Alr.r e 'I6 /4./ff 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be conbidered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 6 Comments: Lacked the requirement of the cloud in the RFP 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0-15POINTS - Score ? Comments: Does not future proofing for the consortium 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 10 Comments: No comparable and reputable consortiums provided as a reference 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces. requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 27 Comments: Comparable to all current systems with the consortium group 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 — 10 POINTS - Score 6 Comments: TOTAL 56 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER N AME Hexagon EVALUATION COMIVII'11LE MEMBER: Michael Loux — Largo PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score 11 Comments: Click here to enter text. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 9 Comments: Click here to enter text. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 15 Comments: Click here to enter text. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 29 Comments: Click here to enter text. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 6 Comments: Click here to enter text. TOTAL 70 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Mark43 EVALUATION COMMITTEE MEMBER: Michael Lou0LarRo PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score 9 Comments: Click here to enter text. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 11 Comments: Click here to enter text. 3. implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 15 Comments: Click here to enter text. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 26 Comments: Click here to enter text. 5. Pricing, Cost EIements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: Click here to enter text. 0 —10 POINTS - Score 5 TOTAL 66 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Tyler Technologies EVALUATION COMMITTEE MEMBER: Michael Loin Largo PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score 13 Comments: Click here to enter text. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. Comments: Click here to enter text. 0 —15 POINTS - Score 12 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 16 Comments: Click here to enter text. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 30 Comments: Click here to enter text. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: Click here to enter text. 0 —10 POINTS - Score 7 TOTAL 78 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Soma Global, Inc EVALUATION COMMIT"1hE MEMBER: Michael Loin' Largo PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score 13 Comments: Click here to enter text. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 15 Comments: CIck here to enter text. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 18 Comments: Click here to enter text. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 32 Comments: Click here to enter text. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: Click here to enter text. 0—lOPOINTS -Score if TOTAL >'��J SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Motorola Solutions EVALUATION COMMITTEE MEMBER: Michael Loux tM — Largo PD 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 -15 POINTS - Score 12 Comments: Click here to enter text. 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 10 Comments: Click here to enter text. 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 17 Comments: Click here to enter text. 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 31 Comments: Click here to enter text. 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 8 Comments: Click here to enter text. TOTAL 78 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER AME Hexagon EVALUATION COMMITTEE MEMBER: Fogarty 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 13 Comments: Presented current versions as well as proposed future versions of platforms. Their example agency presented on the first week was not ideal but subsequent presentations showed product successfully 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility. simple to use, easily mobile, flexibility, security. 0--15POINTS -Score Comments: Still some untested systems but many are scheduled to be in service by May in Lee County 1 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 15 Comments: ii ° . hk.n. eat ,nt er Qc 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 35 Comments: R2k. °Ito% t LnL r k t 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: Q rn wa o rn. r 0 —10 POINTS - Score 8 TOTAL 8a SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Mark43 EVALUATION COMMITTEE MEMBER: Foaart 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references. experience with like sized facilities, responsiveness to questions. on -site demonstration, resource availability. 0-15POINTS - Score 5 Comments: The vendor had a focus on Law Enforcement and did not offer much for the R911 and Fire/EMS disciplines. From this perspective they were Tess than ideal 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 — 15 POINTS - Score 6 Comments: The met the requirements from the LE perspective but fell short on RMS. scheduling and interfacing with platforms used by Fire and EMS industry 3. Implementation Requirements - Factorsto be considered in the score: project management, training. data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 8 Comments: No comments on this factor 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 10 Comments: N of really ready to present live and functional components for a Fire/EMS perspective although the did will from the LE perspective 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: Total Cost of ownership view 0 — 10 POINTS - Score 5 TOTAL 34 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Soma Global. Inc EVALUATION COMMITTEE MEMBER: Fo art 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities, responsiveness to questions, on -site demonstration, resource availability. ,h�? 0 - 15 POINTS - Score Vj Comments: Comments: The vendor had no major implementations and no combined LE, R911 and Fire/EMS disciplines. From this perspective they were not an acceptable vendor 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score /10 Comments: Most of their products remain in development for combined Fire/EMS/LE and of scale and scope for Pinellas County 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score igig Comments: The company is too small, too inexperienced and is overextaded already to take on a major project that they have not yet created or tested in a major system 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POIN TS - Score gv Comments: N o demonstrated product available to review. Vendor is not acceptable 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 4 Comments: Most expensive cost of ownership TOTAL SCORP G SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Motorola Solutions EVALUATION COMMITTEE MEMBER: F 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor' s references, experience with like sized facilities. responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score Comments: k hock ikt 60 ,rots¢ 4�et 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility, simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 9 Comments: (h her rt...r tee 3. Implementation Requirements - Factors to be considered in the score: project management. training, data migration and conversion, experience implementing like size deployments, confidence that the vendor can deliver. 0 — 20 POINTS - Score 14 Comments: k,P,t. to 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 33 Comments: e ,r u� i 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included • price and its component charges, fees, etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). 0 —10 POINTS - Score 9 Comments: ht. e crate a� a TOTAL 80 SCORING SHEET R.F.P. 21-02 — CAD/Mobile/RMS PROPOSER NAME Tyler Technologies EVALUATION COMMITTEE MEMBER: Fogarty 1. Vendor Related Information - Vendor's overall response to the R.F.P. The response should address all points in the proposal, be well organized, clear, and include all requested and supporting information. Other factors to be considered in the score: vendor's references, experience with like sized facilities. responsiveness to questions, on -site demonstration, resource availability. 0 - 15 POINTS - Score 10 Comments: ( BRA b r 2. Technology Requirements - Factors to be considered in the score: is their solution future proof, system architecture, compatibility. simple to use, easily mobile, flexibility, security. 0 —15 POINTS - Score 9 Comments: h k hi r 3. Implementation Requirements - Factors to be considered in the score: project management, training, data migration and conversion, experience implementing like size deployments. confidence that the vendor can deliver. 0-20POI,TS-Score ii Comments: Be °R. ae ,.roao 4. Functional Requirements - Factors to be considered in the score: customer demonstrations, user experience, interfaces, requirements matrix, disaster preparedness, will the consortium requirements be met. 0 — 40 POINTS - Score 30 Comments: °a2. Boo , u 5. Pricing, Cost Elements and Total Five -Year Cost - Proposal response included price and its component charges. fees. etc. which are adequately explained and documented. Response included quality control and assurance programs. Response identified sufficient stability and resources to meet obligations to the agency. Other factors to be considered in the score: variability in pricing (ex. travel costs), potential variability (ex. stated hours for implementation enough or will it cost more). Comments: (..0 ler tie 0 —10 POINTS - Score TOTAL 70 Intergraph Corporation (Hexagon) vendor: Intergraph Corporation (Hexagon( 1 Vendor Related Information Avg Avg Avg Avg Avg Total 12 11.5 10 11 12 12 10 13 13 12 0-15 points 2 Technology Requirements 14 11.25 11 9 14 14 10 12.5 11 12 0-15 points 3 Implementation Requirements 18 16.25 14 15 15 18 15 17 15 16 0-20 points 4 Functional Requirements 32 32 35 29 26 32 25 35.5 35 31 0-40 points 5 Pricing, Co t Elements and Total Five -Year Cost 4 6 6 2 10 5 6 0-10 points Mark43 Inc. Vendor: Mark43, Inc. 1 Vendor Related Information Avg Avg Avg Avg Avg Total 9 10.5 9 9 10 11 8 7.5 5 9 0-15 points 2 Technolog Requirements 12 9.5 10 11 14 12 10 6 6 10 0-15 points 3 Implemen ation Requirements 12 12.25 14 15 14 11 12 8.5 8 12 0-20 points 4 Functional Requirements 19 26.5 32 26 28 20 20 17.5 10 22 0-40 points 5 Pricing, Co t Elements and Total Five -Year Cc 5 4 8 5 2.5 8 5 6 5 0-10 points Tyler Technologies, Inc. Vendor: Tyler Technologies, Inc. 1 Vendor Related Information Avg Avg Avg Avg Avg Total 11 10.5 10 13 12 11 12 4 10 10 0-15 points 2 Technology Requirements 9 8.5 11 12 11 7 12 5 9 9 0-15 points 3 Implementation Requirements 17 15 15 16 14 18 18 7 11 15 0-20 points 4 Functional Requirements 30 18 35 30 29.5 26 30 11 30 27 0-40 points 5 Pricing, Co t Elements and Total Five -Year Cr 6 5 8 7 3 10 9 3 9 7 0-10 points Soma Global, Inc Vendor: Soma Global, Inc 1 Vendor Related Information Avg Avg Avg Avg Avg Total 2 5.5 7 13 13 11 5 4 2 7 0-15 points 2 Technolog Requirements 14 12 8 15 14.5 12 9 4.5 4 10 0-15 points 3 Implementation Requirements 9 9 9 18 14 8 10 4.5 4 10 0-20 points 4 Functional Requirements 15 27 30 32 30 30 11 4 20 0-40 points 5 Pricing, Co t Elements and Total Five -Year Cc 5 5 7 9 10 10 3 4.5 4 6 0-10 points Motorola Solutions, Inc Vendor: Motorola Solutions, Inc 1 Vendor Related Information Avg Avg Avg Avg Avg Total 10 6.25 12 10 7 7 10.5 14 9 0-15 points 2 Technolog Requirements 5 3.75 7 10 11 7 9 9 8 0-15 points 3 Implemen ation Requirements 15 10 17 14 12 13 15 14 13 0-20 points 4 Functional Requirements 20 15.5 27 31 27 13 15 35.5 33 24 0-40 points PCSD Clw PP PD Largo Tarpon Spr St Pete eelleair PP FD EMS 911 EMS 5 Pricing, Co t Elements and Total Five -Year Cost 5 5 7.5 9 7 0-10 points Scoring -Commissary Vendor Related Information Technology Requirements Implementation Requirements Functional Requirements Pricing, Cost Elements and Total Five -Fear Cost Total 0 - 15 Points 0 - 15 Points 0 - 20 Points 0 - 40 Points 0 - 10 Points 0 - 100 Points Intergraph Corporation (Hexagon) 12 12 16 31 6 77 Mark43, Inc. 9 10 12 22 5 58 Tyler Technologies, Inc. 10 9 15 27 7 68 Soma Global, Inc 7 10 10 20 6 54 Motorola Solutions, Inc 9 8 13 24 7 61 RFP 21-02 Vendor List Vendor Contact Email Address Axon Tiffany Van De Berg - Strategic Solutions Specialist Manager ,Andrew Grayson - National Director tvdberg@axon.com Agrayson@axon.com Cody Systems Maggie Riker mriker@codysystems.com Mark43 Steve Devries - Strategic Account Executive stephen.devries@mark43.com sookie.pyo@mark43.com Motorola Spillman - channel parter EMC Inc Karen DiMarco kdimarco@emciwireless.com rob.richardson@motorolasolutions.com ProPhoenix Fred Jenkins - Southeast Regional Business Manager fred.jenkins@prophoenix.com RapidDeplopy KIONA MILLICAN - Business Development Representative bids@rapiddeploy.com Soma Global Shawn Carpenter - Proposal Manager proposals@somaglobal.com shawn@somaglobal.com Tyler Craig Campbell - Public Safety Account Executive Craig.Campbell@tylertech.com Serial Number 21-02640N Business Crnserver Published Weekly Clearwater, Pinellas County, Florida COUNTY OF PINELLAS STATE OF FLORIDA Before the undersigned authority personally appeared Kelly Martin who on oath says that he/she is Publisher's Representative of the Business Observer a weekly newspaper published at Clearwater, Pinellas County, Florida; that the attached copy of advertisement, being a Request for Proposal in the matter of No. 21-02: Computer -Aided Dispatch et al in the Court, was published in said newspaper in the issues of 5/28/2021 Affiant further says that the said Business Observer is a newspaper published at Clearwater, Pinellas County, Florida, and that said newspaper has heretofore been continuously published and has been entered as periodicals matter at the Post Office in Clearwater in said Pinellas County, Florida, for a period of one year next preceding the first publication of the attached copy of advertisement; and affiant further says that he/she has neither paid nor promised any person, firm or corporation any discount, rebate, commission or refund for the purpose of securing this advertisement for publication in said newspaper. *This Notice was placed on the newspaper's website and floridapublicnotices.com on the same day the notice appeared in the newspaper. Kelly Martin Sworn to and subscribed, and personally appeared by ph ., resence before me, 28th day of May, 2021 A.D. by K who is Et* ft% rsonally known to me. Notary Publ, State of Florida EAL) PamelaACox Comm.8GG251785 ires: Aug. 23, 2022 Thru Aaron Notary REQUEST FOR PROPOSAL TO: ALL INTERESTED PARTIES SEALED PROPOSALS will be received by the Pinellas County Sheriff's Offic provide a Computer -Aided Dispatch & Records Management System & Mobile I Terminal until 3.00 p.m. EST„ August 16, 2021. A non -mandatory pre -prop conference will be held on July 14, 2021. Submittals must be sealed and mai 'Request For Proposal No. 21-02 and the closing date". Proposal specificad forms and instructions may be obtained in the Purchasing Division, 14400 Street, Clearwater, FL 33762 or at the Sheriff's Office web site at http://w pcsoweb.00m/administration/purchasing-materials/bid-schedule PINELLAS COUNTY SHERIFFS OFFICE Eric ymcent, Purchasing Manager May 28, 2021 21-0264 A HEXAGON PRIMARY CONTRACTING DOCUMENT This Primary Contracting Document together with the Master Terms referenced below constitutes a Master Agreement by and between PINELLAS COUNTY SHERIFF'S OFFICE ("Customer") and INTERGRAPH CORPORATION through its Hexagon Safety, Infrastructure & Geospatial division and is binding upon the Parties on the Effective Date. RECITALS WHEREAS, the Customer issued Request for Proposal 21-02 for the Computer Aided Dispatch & Records Management System & Mobile Data Terminal (the "RFP"); WHEREAS, Hexagon and vendors submitted responses to the RFP; WHEREAS, Hexagon proposed to provide in response to the RFP: • Services to implement a Cloud Program that included its computer aided dispatch solution, its law enforcement records management solution, its analytics solution (the "Hexagon Solution"), • Services to implement and rights to use fire records management solution provided by ImageTrend, WHEREAS, after conducting diligence on the various proposals, the Customer found Hexagon's proposal to be the most advantageous proposal to the Customer and it now desires to enter into this Agreement and Orders with Hexagon; NOW, THEREFORE, in consideration of the mutual covenants and agreements herein contained, the parties agree as follows: 1. Those Master Terms and Conditions ("Master Terms") attached hereto are incorporated into this Primary Contracting Document as if fully set forth herein. 2. All capitalized terms in this Primary 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: Pinellas County Sheriff's Office Attn: Safety, Infrastructure & Geospatial Legal Department 10750 Uimerton Rd 305 Intergraph Way Largo, FL 33778 Madison, Alabama 35758 tlancto@pcsonet.com victor.va site @h exa go n si.com 727-582-6719 (256) 730-2000 4. Unless otherwise specified in an Order, the following agencies ("Agencies") are the only agencies permitted to use the Software and/or Cloud Program: Pinellas County Sheriff's Office Town of Beiieair Police Department City of St. Petersburg Police Department Town of Indian Shores Police Department with Redington Shores City of Clearwater Police Department Pinellas County Schools Police City of Largo Police Department City of Pinellas Park Fire Department City of Pinellas Park Police Department Pinellas County Fire Department City of Tarpon Springs Police Department City of Petersburg Fire Department City of Gulfport Police Department City of Clearwater Fire Department City of Treasure Island Police Department City of Largo Fire Department City of Kenneth City Police Department City of Dunedin Fire Department City of Gulfport Fire Department City of MadreBeach Fire Department Pinellas Suncoest Fire Control District City of�IOldsmar Fire Department City of Safety Harbor Fire Department Palm Harbor Dire Control District City of St. Pete Beach Fire Department City of South Pasadena Fire Department City of Seminole Fire Department City of Tarpon Springs Fire Department Lealman Special Fire Control District City of Treasure Island Fire Department Airport Crash Rescue (existing as part Board of County Commissioners) of the State Attorney's Office for only the Sixth Judicial Circuit (existing es of the Effe dive Date) East Lake Fire Control District Regional 911 Pinellas County EMS 5. In executing this Primary Contracting Document, the Parties simultaneously accept, without need to execute any other �IOrder Documents, the Orders reflected in the SOW for the HxGN OnCall Dispatch & Records Cloud Hosted Implementation and the SOW for the Development of Enhancements. The summary pricing for all Orders being accepted through this Primary Contracting Document is reflected below and described in more particularity in the respective Order Documents. Any Change Order to those Order Documents affecting price shall also simultaneously change the information in the table below without the need to separately execute an Amendment. Order Name Description Fee Order 1 One Time Implementation Fee for Order 1 $7,060,826 Cloud Program Fee during Implementation $1,081,487 Order 2 One Time Implementation Fee for Order 2 $1,557,512 S�btota� One Tine Fees $9,699,825 Cioud Program, Order Recurring Fees Year 1 Cloud Program Fee $1,858,035 Year 2 Cloud Program Fee $1,858,035 Year 3 Cloud Program Fee $1,858,035 Year 4 Cloud Program Fee $1,858,035 Year 5 Cloud Program Fee $1,858,035 Subtotal for Cloud Program Fee $9,290,175 TOTAL PRICE $18,990,000 6. In consideration of the mutual obligations assumed under this Primary Contracting Document, Customer and Hexagon agree to the terms and conditions set forth herein and represent that this Primary Contracting Document 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 Primary Contracting Document. This Primary Contracting Document may be executed in counterparts or in duplicate originals. Each counterpart or each duplicate shall be deemed an original copy of this Primary Contracting Document sign. ; by each Party for all purposes. AGREED TO BY: PINE - - - • Y SHERFICE By: Name: Bob Gualtieri Title: Sheriff Date: aNci 4- INTERGRAP. ORATION By: / Name: Richard Morris Title: VP of Global Contracts Date: July 22, 2022 lye A HEXAGON MASTER TERMS AND CONDITIONS These Master Terms and Conditions (the "Master Terms") govern transactions and relations between Customer and Hexagon (each a "Party" and collectively the "Parties"). Hexagon will make available to Customer certain proprietary software, including related proprietary Documentation, software maintenance services, Equipment/Content; DevTools, Cloud Programs; and professional services, and other items, which will be provided to Customer pursuant to these Master Terms and an Order. Before Hexagon will provide any items or 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 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 — DELETED. • Exhibit B — DELETED. • Exhibit C — Sample Project Deliverable Sign -Off Form; • Exhibit D — Cloud Program Conditions; • Exhibit E — OMITTED. • Exhibit F — Standard Training Program Terms; and • Exhibit G — Common Terms Glossary. • Exhibit H — Data Processing Addendum • Exhibit I — Hexagon Cloud Services — Acceptable Use Policy • Exhibit J — Florida CJIS Security Policy • Exhibit L — Criminal Justice Agency and Contractor/Vendor CJIS Network Agreement 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). Words used herein in the singular, where the context so permits, shall be deemed to include the plural, and vice versa. 2 Elements of an Order. 2.1 Order Composition. Each Order will be comprised of Order Documents, including any applicable Schedule(s). An Order is formed only once both Parties accept the Order Documents, which the Customer shall do by executing the Order Documents and/or issuing a PO in connection with the Order Documents. Orders shall be effective as of the date both Parties accept the Order Documents except where the Order is for a term -based offering (e.g., Subscription License), in which case the Order shall commence as of the date specified in the Order Documents, if provided. 2.2 Schedules. Any Schedules applicable to Products or items purchased in an Order are incorporated and are either included in the Order Documents or, in the absence thereof, accessible via hyperlinks contained within Exhibit G. If a Product or item is not listed in the document(s) accessed via hyperlinks provided in Exhibit G, and related Schedule(s) are not otherwise included in the Order Documents, then that Product or item does not have a corresponding Schedule. 2.3 Pricing. Order Documents shall describe basic pricing and include other details relevant to the offerings included in the Order. 2.4 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. 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 set forth in a mutually executed writing. 2.5 Acceptance. Acceptance will occur based upon the following. 2.5.1 For Fixed Price Project Assignments, not governed by Exhibit F, acceptance shall occur has been satisfied in accordance with the Task Acceptance Process. 2.5.2 For Ti me and Materials Project Assignments and Maintenance Services, the Services are accepted as performed. 2.5.3 For a Cloud Program, acceptance occurs when the License Keys are provided to Customer. 2.5.4 For all Orders not described more specifically above, acceptance occurs once the ordered item has been delivered or access to the ordered item has been provided. 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 Schedules and 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 Schedules; (4) These Master Terms (excluding Exhibits); (5) Exhibits to these Master Terms; and (6) Order Documents, if any, in addition to items specifically identified in this Section 3.2 above. 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 4.1 Invoicing and Payment. Invoices. Invoices shall be issued based upon the contents of the Order. 4.1.1 For Fixed Price Project Assignments Hexagon may invoice Customer upon completion of a payment milestone identified in the Order Documents, or when applicable, in accordance with Exhibit F; provided however, if this type of Order also includes Subscription Licenses or Cloud Program(s), the fees for such shall be due in accordance with Exhibits E and D, respectively. 4.1.2 For within an Order for a Fixed Price Project Assignment or otherwise more specifically addressed in this Section 4, Hexagon may invoice Customer for the full amount set forth in the Quote in addition to any applicable freight shipping charges upon delivery of or access having been provided to any of the Product(s) or items identified in the Order Documents. 4.1.3 Time and Materials laterials Project Assignments shall be billed and invoiced monthly 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 Maintenance laintenance Services not included within an Order for a Fixed Price Project Assignment or Product Order shall be billed and invoiced in accordance with Exhibit B. 4.1.5 Cloud Program(s) (even if included within a Fixed Price Project Assign ment) shall be billed and invoiced in accordance with Exhibit D. 4.2 Payment. Customer shall make payment for any invoices issued by Hexagon in accordance with the Florida Prompt Payment Act, Fla. Stat. §218.70 et seq. 4.3 Late Payment. If Customer does not make timely payment, an interest charge of two percent (2%) per Month lonth (or the maximum allowed by law, whichever is less), compounded monthly, 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. As it pertains to Equipment, Hexagon shall retain a security interest in the Equipment. If Customer is late or otherwise in default of its payment obligations for Equipment, then Hexagon may, in addition to any other remedies available, exercise remedies of a secured party regarding the Equipment. 4.4 Taxes. The purchase price is exclusive of all federal, state, and/or local taxes. Any taxes applied to this sale by a federal, state, and/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 laster Agreement shall begin on the Effective Date and remain in effect for a period of eighty-four (84) consecutive Months lonths or until the Master laster Agreement is earlier terminated pursuant to the terms set forth herein orb by mutual agreement of the Parties. An Order�pthat is executed prior to the expiration of the term of the Master laster Agreement shall be governed by the Master laster 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 laster Agreement shall terminate upon completion of all Orders executed hereunder regardless of the amount of time remaining in the 5.2 Termination for Convenience. Either Party may terminate the Master laster Agreement or an Order in its sole discretion at any time upon providing the other Party with one hundred twenty (120) days written notice. In the event of a termination pursuant to this paragraph, Customer agrees to pay Hexagon for the Work performed and Product(s) or items delivered and provided, plus the cost of any labor and/or Product(s) or items 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 Product(s) or items. Hexagon is entitled to retain all amounts paid under any Order prior to termination. To the extent a Party exercises its right to terminate a specific Order, that termination shall have no effect upon the remaining Master laster Agreement, which, along�pwith any other active Orders, shall remain in full force and effect. If a Party desires to terminate the Master laster Agreement, then the Parties shall proceed to wind down all ongoing work under the respective Orders in effect under the Master laster 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.2(a) In the event sufficient budgeted funds are not available to complete an Order, the Customer shall notify Hexagon of such occurrence and the Order or Order(s) shall terminate on the last day of the current fiscal period without penalty to the Customer provided that it shall pay Hexagon for all Work performed and Product(s) or items provided. 5.3 Termination for Cause. Either Party may terminate the Master laster Agreement or a specific Order, as the case may be, in the event the other Party materially breaches a material term of the Master laster Agreement or any Order. 5.3.1 In the event a Party materially (breaches 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 materially breaches 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. 5.3.3 If the Master Agreement or any one or more Orders is terminated pursuant to paragraphs 5.3.1 or 5.3.2, Hexagon will stop all Work with respect to impacted Orders as soon as practicable and shall be entitled to payment for all Work performed as well as Product(s) provided on all impacted Orders up to the termination date, less amounts previously paid by Customer under the affected Orders. 5.3.4 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/or Product(s) delivered/eon said Order up to the suspension or termination date, less amounts previously paid by Customer under the affected Orders. Hexagon is entitled to retain all amounts paid under any Order prior to its termination. If Hexagon suspends an Order under this paragraph, then it may thereafter terminate the Order upon giving written notice to Customer. 5.3.5 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 Ownership. 6.1 Customer acknowledges Hexagon will retain ownership and title of Hexagon IP made or provided pursuant to any Order. All Softw a/rre (including Software embedded within Equipment) 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, including any Software developed by a third party embedded within Equip /moment, is licensed to Customer pursuant to Third Party Terms or as otherwise specified in the applicable E/l.. Schedule. /� 6.2 As it pertains to any Equipment, and only Equipment, provided to Customer under an Order, the Customer shall receive title to and ownership of the Equipment identified in the Order Documents, excluding any IPR pertaining to the Equipment and Software provided with the Equipment, FOB place of origin and subject to Customer's payment of all amounts owed for the Equipment. 6.3 Customer shall among other things, facilitate Hexagon's performance of its obligations. 7 Warranties. 7.1 Software. OMITTED. to, 7.2 Subsystem Warranty Coverage. For, and only for, new Subsystems (excluding Cloud Applications) procured implemented pursuant to an Order under these Master Terms, the warranty coverage shall be set forth in the applicable Order Documents, which shall be in lieu of the warranty coverage set forth in Section 7.1 7.3 Equipment Warranty Coverage. If Equipment supplied by Hexagon is provided with a warranty or other Equipment support, then the extent of the Equipment support is provided within the corresponding E/C Schedule or other Order Documents. 7.4 Third -party Warranty Coverage. To the extent no warranty or Equipment support is described in the applicable E/C Schedule or other Order Documents, third -party products supplied by Hexagon, are provided with a pass -through -warranty from the original manufacturer, if any. Hexagon will be the point of contact for all such warranty claims/work for the Customer with any such third -party providers. 7.5 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(s). 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.6 Warranty Disclaimer. For Non -Cloud Programs, 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, DURABILITY, FITNESS FOR A PARTICULAR PURPOSE, HIGH RISK USE, AND NON -INFRINGEMENT. ALL WARRANTIES PROVIDED PURSUANT TO THIS MASTER AGREEMENT ARE VOID IF FAILURE OF A WARRANTED ITEM RESULTS DIRECTLY OR INDIRECTLY FROM AN UNAUTHORIZED USE OR MISUSE OF A WARRANTED ITEM, INCLUDING, WITHOUT LIMITATION, USE OF A WARRANTED ITEM UNDER ABNORMAL OPERATING CONDITIONS OR UNAUTHORIZED MODIFICATION OR REPAIR OF A WARRANTED ITEM OR FAILURE TO ROUTINELY MAINTAIN A WARRANTED ITEM. THE WARRANTIES SET FORTH IN THIS ARTICLE 7 ARE IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED, AND, EXCEPT AS SET FORTH IN ARTICLE TITLED "INDEMNIFICATION PROVISIONS" BELOW, REPRESENT 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. IF THE EVENT GIVING RISE TO THE CAUSE OF ACTION OCCURRED PRIOR TO CLOUD CUTOVER (AS DESCRIBED IN ORDER 1), THEN UNDER NO CIRCUMSTANCE WILL HEXAGON'S LIABILITY UNDER THIS MASTER AGREEMENT EXCEEDTHE AMOUNT THAT HEXAGON HAS BEEN PAID BY CUSTOMER UNDER THIS AGREEMENT. IF, HOWEVER, THE EVENT GIVING RISE TO THE CAUSE OF ACTION OCCURRED AFTER CLOUD CUTOVER (AS DESCRIBED IN ORDER 1), THEN UNDER NO CIRCUMSTANCE WILL HEXAGON'S LIABILITY EXCEED THE AMOUNT 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) 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 reasonable notice to Hexagon of any Claim, 1 For clarity, an Agency does not constitute a third party in this context. 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 Unless caused by Hexagon, 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.2 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) TThe aggregate. The policy shall be applicable to all premises and operations. I he 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 U with minimum combined single limits of ONE MILLION DOLLARS ($1,000,000) per occurrence. Certificate of Insurance. If required or requested. 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, and, the completed Certificate of Insurance shall be sent to the contact person identified in the Primary Contracting Document. 10.3 Insurance De policies required above. Hexagon shall be solely responsible for any deductible losses under the 11.1 Hexagon shall take reasonable industry action to prevent, detect, identify, report, track and respond to Security Incidents. Notwithstanding anything to the contrary, Hexagon shall notify Customer promptly via email andp the Designated Portal in the event that it learns or has reason to believe that there has been any Security Breach affecting Customer Data, or that any person who has had access to Customer Data has violated or intends/�to violate the terms of the Master Agreement. Hexagon shall, at its own expense, cooperate with Customer in investigating and responding to the foregoing provided such cooperation is not inconsistent with direction provided by responding law enforcement agencies, any applicable insurance carriers, or cyber security breach consultants retained by or on behalf of Hexagon; notifying customers or other affected individuals as required by law, and take reasonable measures consistent with this section. 12 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, the Disputing 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's 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 nonbinding 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 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,p'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 To the extent necessary, Customer agrees to provide appropriate workspace and workplace accommodations, computer equipment, software; access to relevant data, documents, plans, reports, and analyses, and necessaryaccess for Hexagon personnel to perform work on an Order. To the extent work Customer performed remotely, Customer must provide VPN or secured remote connectivity (including a login, password, and multi -factor authentication) to all servers and workstations requiring installation configuration by Hexagon. /In turn, Hexagon agrees to comply with the current version of the Florida Department of Law Enforcement Criminal Justice Security Policy found in Exhibit J as it pertains to software development and implementation vendors. Hexagon agrees to comply with requirements emanating from Exhibit J related to unescorted system access and related requirements. 16 Amendments. Any and all amendments to the Master Agreement shall be in writing specifically reference the fact the amendment is intended to alter these Master Terms and executed by authorized representatives of both Parties. No Order or Change Order shall affect these Master Terms, unless expressly stated in such document. 17 Confidential Information. Unless prohibited by law, the Parties agree not to disclose Confidential Information provided to it by the Disclosing Party unless it first obtains the Disclosing Party's written consent to such disclosure, or as required by a court of competentjurisdiction. It is further understood the Receiving Party and the Disclosing Party may seek equitable relief, including injunction and specific performance, as a remedy for any such breach if the elements to bring same are met. 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. Section 119.0701, Florida Statutes (2016) requires that all contractors comply with i Florida s public record laws with respect to services performed on behalf of the Sheriff. Specifically, the statute requires that all contracts entered into or amended after July 1, 2016 shall contain the following statement in at least 14-point boldfaced type: If the contractor has questions regarding the application of Chapter 119, Florida Statutes, to the contractor's duty to provide public records relating to this contract, contact the custodian of public records at: Pinellas County Sheriff's Office 10750 Ulrnerton Rd. Largo, FL 33778 Ph.: 727-582-6200 contractor@pcsonet.com Additionally, all contracts are required to contain the following. 1. Keep and maintain public records required by the public agency to perform the service. 2. Upon request from the public agency's custodian of public records, provide the public agency 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 this chapter 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 for the duration of the contract term and following completion of the contract if the contractor does not transfer the records to the public agency. 4. Upon completion of the contract, transfer, at no cost, to the public agency all public records in possession of the contractor or keep and maintain public records required by the public agency to perform the service. If the contractor transfers all public records to the public agency 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 contractor shall meet all applicable requirements for retaining public records. A11 records stored electronically must be provided to the public agency, upon request from the public agency's custodian of public records, in a format that is compatible with the information technology systems of the public agency. Failure to comply with these provisions is considered an immediate breach of contract. 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 The applicable data protection laws. I he 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. I o the extent that: (a) Personal Data of Users or Authorized Cloud Users /provided by the Customerto Hexagon pursuant to the MasterAgreementis 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, Exhibit H, 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 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,/hand 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 in Exhibit H, 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. 20 Cooperative Purchasing. 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. Product(s) and services 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 20 to place Orders under the 21 Export. Equipment/Content, and Hexagon IP, including any technical data related to Software, Services, Maintenance Services, orCloud Programs, are subject to the export control laws and regulations of the United States. Diversion contrary to United States law is prohibited. Equipment/Contentand/or Hexagon Cl oud including any technical data related to Software, Services, Maintenance Services, or 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 Department of Statet�Debarred List (http.//export.gov/ecr/eg_ main_023148.a sp); • 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; and/or • 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 comply with all applicable export control laws and regulations. User shall not request information or documentation where the purpose of such request is to support, give effect to or comply with a boycott of any country that is not sanctioned by the United States, including but not limited to the Arab League boycott of Israel. 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 exportcompliance1intergraph.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, such Software 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. 22 Non -Solicitation of Employees. Customer and Hexagon agree they will not, without the prior written consent of Hexagon and Customer, solicit any Hexagon employee or Customer employee, or induce such employees to leave Hexagon's or Customer's employment, directly or indirectly, during the Term and for a period of twelve (12) Months after the Master Agreement expires or is terminated. 23 Miscellaneous. 23.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. The Sheriff or his/her designee shall provide a list of persons authorized/�to bind and do bind the Customer under an Order or Amendments made hereto. By issuance of a Quote to Customer without the word "DRAFT" or similar markings 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. 23.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, Exhibit E, and/or Exhibit F), 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. 23.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. 23.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. 23.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. 23.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 relating to the Master Agreement shall be instituted in either the appropriate state courts located in Pinellas County, Florida or the United States 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 as to the interpretation 23.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. 23.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. 23.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. 23.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, and the method of making payment to Hexagon as provided hereunder is not in violation of the law of any applicable jurisdiction. Either Party has the right to terminate Agreement upon any violation of the FCPA or similar laws by the other Party. a. Customer requires personnel providing Services which involve unescorted access to Customer's System or facilities to comply with background investigations and/or security checks. These background investigations may require the personnel to be fingerprinted, and will be performed by the Customer at no charge to Hexagon. Customer reserves the right to disallow the use of any individual who is deemed to pose a security risk. Hexagon shall provide to the Customer a written list of the names and addresses of all employees and the positions of said employees who are to perform the Work outlined in the Order for which unescorted access is necessary. b. Hexagon shall use all reasonable care consistent with its rights to manage and control its operation not to employ any persons, use any labor, use or have any equipment, or permit any condition to exist which may cause, or be conducive to, any complaint, trouble, dispute or controversy which interferes or is likely to interfere with the operation of the Customer. The Customer shall have and exercise full and complete control over granting, denying, withholding, withdrawing, or terminating clearances for employees. c. Hexagon shall comply with all Federal, State and local laws, executive orders, and rules and regulations applicable to the Work provided that any change in the Laws may necessitate a change in scope for ongoing Orders up to one hundred twenty (120) hours per twenty-four (24) months beginning upon Cloud Program Start Date. If such a request is received by Hexagon from Customer, then Hexagon will evaluate the mandated change and provide the Customer an estimate of the scope to develop and implement such change, which the Customer shall authorize prior to Hexagon performing any development or d. Hexagon's personnel shall immediately report all accidents or unusual incidents occurring on Customer's premises to the Sheriff's designee for the work. Unusual or catastrophic events involving personnel or equipment covered by this Master Agreement shall, within three (3) business days, be followed by a written email notification to the Customer contract monitor detailing the circumstances surrounding the event and the actions taken or to be taken by e. E-VERIFY: In accordance with Florida Statute §448.095, Hexagon agrees to: i. Have registered and use the E-Verify system to verify the work authorization status of all newly hired employees, ii. If a subcontractor provides labor, supplies or services for an Order, to obtain and maintain the required affidavit(s), iii. if terminated pursuant to this section is not a breach of contract and shall not be considered as such, and (iv) be liable for any additional costs incurred by the Sheriff as a result of a termination pursuant to this section subject to those damages being proven and the Limitation of Liability in Section 8. 23.12 Public Entity Crimes. Hexagon shall comply with the Florida Public Entity Crime Act §287.133, Florida Statutes in all respect during the Ter 23.13 Americans with Disabilities. Customer complies with the ADA, and upon appropriate notification will make reasonable accommodation to permit individuals with disabilities to participate in solicitations by 23.14 Third Party Beneficiary. PRIME is the only third party beneficiary to this Agreement. 24 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, p and no reference to prior�pdealings may be used to in any way modify the expressed understandings of the Master lasterAgreement. The Master laster 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 otherterms and conditions of a Customer PO shall be void, even if issued subse�gpuenttothe effective date of the Master laster Agreement, and shall not be deemed to constitute a change to the Master laster Agreement. EXHIBIT A OMITTED. END OF EXHIBIT A EXHIBIT B OMITTED. END OF EXHIBIT B 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: Contact Name Submitted To: Customer Contact Name Customer Contract #: Customer Contract Number Customer/Project #: Hexagon Project Number TYPE OF DELIVERABLE SOWTasks 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) Business Days after receipt of a written request from Hexagon, to either sign -off that the Task Acceptance Criteria has been satisfied or state in writing to Hexagon the reason the Task Acceptance Criteria has not been satisfied. Contract of the Task shall be based solely upon satisfaction of the Task Acceptance Criteria 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) Business Days after delivery then the Task will be deemed to have been accepted. The signature below acknowledges that Task Acceptance Criteria described in the Statement of Work and listed above has been satisfied and the Task is accepted. Authorized Customer Representative Customer Contact Name SIGNATURE END OF EXHIBIT C DATE 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 Order. Any additional terms in any Cloud Services Schedule(s) also a pply. 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 gon will provide Customer access to the Customer to use the Cloud Program subject to the provisions of these Cloud Conditions provided that Hexagon may as described in Order Documents provide limited access to the Cloud Program for implementation purposes only as part of a project and prior to the commencement of the Cloud Term. In such a case and prior to the commencement of the Cloud Term, the Customer shall be permitted to use the Cloud Program for implementation purposes only and shall be subject to the other obligations and restrictions set forth herein that would otherwise apply during the Cloud Term. 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 For, and only for, the initial Order for the Cloud Program under this Master Agreement, the Cloud Term commences on Cloud Cutover of the respective Subsystem. In all other circumstances, the Cloud Program 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 Order and/or Offb oa rd e d. 4.2 Upon request by the Customer, made not less than thirty days prior to the effective date of termination, Hexagon shall make available to the Customer for download a file of Customer Data in SQL generated bacpac file format along with attachments in their native format at no additional charge. Hexagon recommends that the Customer downloads a copy of this file before the expiry of the Retention Period. Hexagon will provide to Customer or to any vendor selected by Customer as successor vendor of similar or replacement services ("Successor Vendor"), at Customer's sole cost and expense, assistance reasonably requested by Customer in order to effect the orderly transition of the applicable Services, in whole or in part, to Customer or to 4.3 Successor Vendor (the "Transition Assistance Services") during the ninety (90) calendar day period prior to the expiration or termination of this Agreement (the "Transition Assistance Period") provided that the Customer does not separately renew the Cloud Program under this or a separate agreement. Hexagon and Customer shall negotiate price and scope of Hexagon's provisioning of Transition Assistance Services prior to the beginning of the Transition Assistance Period. Transition Assistance Services may include. • Development of a plan for the orderly transition of the Services being transitioned from Hexagon to Customer or a Successor Vendor. • Use of commercially reasonable efforts to assist Customer, at Customer's sole cost and expense, in acquiring any necessary rights to legally and physically access and use any third -party services, technologies and documentation then being used by Hexagon in connection with the Services. • Other activities to which the parties may agree. In addition to the rights and remedies set forth in the Master Terms, once notified in writing of an 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 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. 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.4 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 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 and successfully logging in. 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 "Ex,tio.,(0"). 6. CRITICAL SERVICE LEVELS. The purchased Service Level classifications are set forth in the Cloud Service Schedule. "Service Operational Tin,e" 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 l00 an Exception 7. SERVICE CREDITS. 7.1 7.2 7.3 7.4 If in any Month the Service Operational Time in a Cloud Environment for Production falls below (a "Servi re Inoide.,t"), not as a result of an outage, a "Return to Green Plan" shall be initiated for the Customer's Production Environment. Hexagon shall have twenty one (21) days to return does not rise to the applicable Schedule will be applied against each Month in which below such Service Level. 7.3.1 Only as specified within the applicable 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 applicable Cloud Services Schedule ("Green"); and 7.3.5 Only where Customer is compliant with the AUP. 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. 7.5 8. CLOUD SERVICES SUPPORT. 8.1 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 Designated Portal, 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 Designated Portal. 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. Hexagon acknowledges, however, that any unscheduled Emergency Maintenance that causes unavailability will not be excluded from calculation of Availability provided the Emergency Maintenance does not arise or relate to other exclusions from Availability parameters. 8.(. 6 Hexagon will provide no less than two (2) weeks notice for any planned downtime. 8.7 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 Secure Access Tool. 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.8 Except as otherwise necessary,sasp determined/eby Hexagon in its sole discretion, to satisfy the requirements of Sections/e8.3 and 8.4, Cloud Services Support does not include. (i)Ttraining; (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 no/t�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.9 Updates. may be Is to the Cloud part of 8.9.2 From time to time, Hexagon may notify Customer through the Designated Portal that Hexagon has developed an Update for the purchased Cloud Application(s) and intends to deploy said update, including any applicable Third Party Software � Products. On the date specified in the notification, Hexagon will deploy/the Update 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, 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 or a subsequently specified date by Hexagon, Hexagon will, at its discretion, deploy the update to Customer Cloud Environment for Production. 8.9.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 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 / Cloud finds that no Material Adverse Effect exists, Hexagon may deploy the Update to the Customer Environment for Production after notification to the Customer. 8.9.4 As it relates to implementing Updates for Local Software that is included within the Cloud Cu stomer ustomer shall permit Hexagon to electronically access the Local Software on Customer's System Equipment via Secure Access Tool to implement the Update in conjunction with the updating of the Cloud Applications and provide any other reasonable support and Cl oud required by Hexagon to update the Program. 8.9.5 Hexagon shall reasonably cooperate with Customer as it pertains to Planned Maintenance. 9. CUSTOMER RESPONSIBILITIES. 9.1 Upon receiving access to the Cloud Applications, even if prior to the Cloud Term, the Customer shall be responsible for all activities that occur in Authorized Cloud Users' and Users' 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 requiredto interoperate with the Cloud Program as communicated by Hexagon to Cl oud via the Portal or as otherwise determined by Hexagon; and 9.1.4 Abide by and /comply with the Acceptable Use Policy, Documentation, and other Customer of these Cloud Conditions. C 9.2 ustomer shall reasonably cooperate with Hexagon as it pertains to Planned Maintenance. The Parties agree that Hexagon can agree to schedule maintenance events that are expected to have an impact or cause unavailability of the Software between 4:00 a.m. U.S. Eastern Time on Tuesdays and 8:00 a.m. U.S. Eastern Time on Tuesdays provided Customer notifies Hexagon of such request as scheduled maintenance Is arranged between the Parties. The delivery of Updates and Planned Maintenance are included within the Customer's Cloud Program Fees. 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. It is the Customer's responsibility to monitor its usage of License Key(s) and/or Cloud Application capacity it has purchased. Hexagon will 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 or is projected to use 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, as described in the applicable Cloud Services Schedule(s). 10.3 Hexagon will provide Customer with Cloud usage, monitoring, and notification tools that will alert and advise customer of usage or projected usage of more License Key(s) that specified in the Quote prior to exceeding any service thresholds that would incur additional costs over and above those set forth in the specified Quote.. These tools include the ability to monitor whether the Customer is exceeding inbound or outbound allotted network bandwidth, CPU/RAM usage, storage or file size limits or API calls. All notifications will be sent by email or otherwise made available to the License Administrators when a service threshold has reached 90% of the allotted amount over one (1) year. 11. TERMS OF PAYMENT. The invoice corresponding to the first year of Cloud Program Fees shall be provided to Customer upon or following Cloud Cutover. For purposes of clarity, once Cloud Cutover for a Subsystem occurs, the annual Cloud Program Fee corresponding to that Subsystem 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 in Exhibit I provided that in the event the Third Party Service Provider adopts additional or different rules or requirements in the use of its cloud platform, then Customer shall reasonably agree to amend this Master Agreement to reflect such updated terms and requirements. The Customer and any Authorized Cloud User or User shall comply with the AUP at all times in which it has access to the Cloud Environments. 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 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 AUPand 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 C party software is not included within Cloud Services Support or the loud Program. 13. OWNERSHIP AND INTELLECTUAL PROPERTY. 13.1 In accordance with Section 6 of the Master Terms, Hexagon 13.2 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 C all IPR in and to their intellectual property that may be provided as part of the loud 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 . 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 to 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. Customer and its Affiliates, respectively, shall retain their respective full ownership and all rights associated therewith solely to Customer Data to the extent they own 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 15 SECURITY & BREACH NOTIFICATION. 15.1 Hexagon shall take reasonable industry action to prevent, detect, identify, report, track and respond to Security Incidents. Hexagon shall take reasonable industry action to prevent, detect, identify, report, track and respond to Security Incidents. Notwithstanding anything to the contrary, Hexagon shall notify Customer promptly via email and the Designated Portal in the event that it learns or has reason to believe that there has been any Security Breach affecting Customer Data, or that any person who has had access to Customer Data has violated or intends tom violate the terms of the Master Agreement. Hexagon shall, at its own expense, cooperate with Customer in investigating and responding to the foregoing provided such cooperation is not inconsistent with direction provided by responding law enforcement agencies, any applicable insurance carriers, or cyber security breach consultants retained by or on behalf of Hexagon; notifying customers or other affected individuals as required by law, and take reasonable measures consistent with this section. 15.2 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.2.1 Develop, implement, and maintain reasonable security procedures and practices appropriate to the nature of the information to protect Personal Data from unauthorized access, destruction, use, modification, or disclosure, and 15.2.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 Cloud Services will use industry standard Virus detection software to avoid transmission/� to the Customer and its Affiliates any Viruses (except for any Viruses contained in Customer Data uploaded or Onboarded by Customer). Customer 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 Affiliates' 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 theCloud Program. 16.3 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 Customer's 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 theCloud Program and 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 EXHIBIT E OMITTED END OF EXHIBIT E EXHIBIT F Standard Training Program Terms These terms and conditions ("Standard 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 Standard 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 specified in the Quote and purchased by Customer, in accordance with and subject to the provisions of these Standard Training Program Terms and the applicable Training Program State ment(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 4.2 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 Customers assignment of available credentials or in any reassignment of credentials. 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 IPR; the platform shall not be used for any activity intended to directly or indirectly 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 Party Service Provider and solely for the purpose of consuming 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 t/oo decompile, disassemble, obtain any source code for, or record Training Curricula, in whole or in part. Customer, for itself and its Affiliatesand 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 TrainingCurricula Customer media beyond itself and the Agencies 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 TrainingProgram Customer Hexagon shall only provide electronic copies of any specified Documentation, which Customer may copy for Customer training use for itself and the Agencies. 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 /CCurricula. Customer shall be responsible for supplying all components necessary to supply of the Training Curricula not expressly specified in the Training Program Statement Curricula, 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 EXHIBIT G COMMON TERMS GLOSSARY C "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" iate71 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 hold a controlling ownership interest. "Affiliates" means, for government entities which are Customers, an entity which has entered into an intergovernmental/v 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 T the General Terms and Conditions, an Affiliate is not a third party. /� /� "Authorized Cloud User"rmeans an individual user authorized by the Customer to use an entire/�Cloud Program one behalf of the Customer and for Cloud 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.�l "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 Product prior to a generally available commercial release of such Software Product. "BusinessDay" means any day other than a weekend or public holiday in the country listed on the Quote. "BusinessHour" 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 greater than Category 2 on the Saffir'Simpson scale, 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. "C loud oud Anniversary77 means the anniversary of the date of the cloud Program Start Date. "Cloud Application(s)" means the Hexagon�lsoftware applications, including without limitation application programming interfaces made available by Hexagon through the Cloud Portal as part of the Cloud Program. C Cloud Application(s) are subject to loud Services Schedules. "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 oud Cutover17 means the point in time when customer first uses a Cloud Application for its generally marketed purpose, commonly referred to as "go -live." "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 and that is supported by�I 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 Portal77 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. "C loud Program17 means the combination of Cloud Services, Cloud Application(s), Local Software, Third Party Software , 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 Start Date" means the date of Cloud Cutover. For�pCloud Program Fees purposes, Cloud Program use by Customer will be assumed tobefor the entire Month lonth in which the Cloud Program Start ate falls regardless of the actual date in such Month lonth that access to the applicable Cloud Application bega n. "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 OUd Services11 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)), for Cloud Application(s), Cloud Optional Services, and Third Party Software and ordered by the Customer. "Cloud Services Schedule" means a document(s) titled "Cloud Services Schedule" included in Order Documents related to one or more Cloud Application(s) that contains additional details regarding the Cloud Services being provided to Customer with respect to the applicable Cloud Program components purchased by Customer. "Cloud Services Support" means) the service specified as such in the Cloud Conditions 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 purposes of testing modifications and training, as specifically permitted herein, to the purchased Cloud Application(s). For purposes of clarity, the Cloud Staging Environment cannot be used in Production. "Cloud oud Term11 means the duration of a Cloud Program Order. "Confidential Information" means any data or information, tangible or intangible, disclosed or made 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) 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; (iv) was within the Receiving Party's possession prior to its being furnished by the Disclosing Party, where the Receiving Party has no reason to believe that such third party was bound by any confidentiality obligation to the Disclosing Party, or (v) is confirmed in writing by the Disclosing Party as not being confidential. "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. Documentation" means commercial off the shelf Documentation in the form generally released and distributed to Hexagon's customers and not includingorrequiring changes thereto. "Coverage Period" means the period of performance of Maintenance laintenance 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 the anniversary of the date on which the Coverage Period commenced. "Covered Products" "Covered Software Product(s)" pmeans Software Prod uct(s) and Developer Tools identified in the Order Documents as software for which IV laintenance 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 Products) identified in the Order Documents as Third Party Software for which Iv laintenance Services are to be provided by Hexagon. Covered Third Party Products shall not include Software Products or any Cloud Program. "Credentials" s1f means the unique log in identifier by which a person could access a service or benefit, such as, without limitation, a Cloud Program or Training Curricula. "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. A Customer Cloud Environment consists of a Cloud Development Environment and Production Environment. "Customer Data17 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 particular 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, DevTools, Content, Equipment and Software intentionally designed and embedded with Equipment or Special Purpose Items, and any other data and information provided as part of the Cloud Program or constituting a Hexagon Deliverable. "Customer Data Rights" means: (i) the right to use Customer Data that contains Customer's Confidential Information to perform Hexagon's obligations within the Order; (ii) the right to use, alter, modify, and disclose Customer Data that does not include Customer's Confidential Information to perform Hexagon's obligations and other business purposes for which the information may be disclosed to third parties, and (iii) except as otherwise provided in the EULA or Developer Tools Schedule, a worldwide, royalty -free, irrevocable license to use, replicate, sell, modify, enhance, and distribute any works created by the Customer through its use of Developer Tools. "Customer Specified Data Center" 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 Software71 means those Services Deliverables that are software or computer code, whether in source code or object code. 0 Cutover1f 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. Under no circumstances shall data centers Cl oud Customer Data for its Program be located outside the continental United States of America. "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 or Cloud Application, assuming proper usage of the Software Product or Cloud Application in its required operating environment. Defects are further classified into four levels as follows. Level Impact of Defect ► Level One ► Level Two ► Level Three ► Level Four 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 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 Customer shall classify a Defect in accordance with the foregoing, provided that, Hexagon shall reclassify the Defect as appropriate following its review thereof. If after Hexagon renders its final decision pertaining to the Defect and the Customer disagrees with it, the Customer may initiate the Defect Escalation Process for such Defect. "Defect Escalation Process" mean that certain process initiated by Customer regarding Hexagon's decision on a Defect and proceeds as follows. If within ten (10) Business Days following Hexagon's decision on a Defect as reflected in the CRM tool Customer disagrees with it, it may request, by providing notice in accordance with Section 13 above, Hexagon's Director or Vice President most directly responsible for the HelpDesk ("HelpDesk Director") to reconsider such decision based upon facts set forth in Customer's request. If after the HelpDesk Director has provided a decision the Customer continues to disagree with the decision, then it may within ten (10) Business Days following the rendering of the HelpDesk Director's decision, provide a written request to Hexagon's Vice President responsible for North America Public Safety to reconsider such decision pertaining to the Defect. "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. "Designated Portal" means the portal(s), website(s), platform(s), or other similar channels designated by Hexagon from time to time to be used for specific collaboration(s), information dissemination(s), or com munications(s). "Developer Tools" or "DevTools" means any software software for (a) redistribution, or (b) interfacing two or more intended for use by developers to create (i) of the following. Software, Cloud Applications, E/C; or (ii) specific customizations for which the Developer Tool Developer Tools are subject to Developer Tools Schedules. is intended a n d "Developer Tools Schedule" or "DevTools Schedule" means a document designed. contained within the Order Documents relating to certain DevTools provided by Hexagon listed in the OrderDocumentsthat identifies particular details, limitations, licensing, and other parameters relating to the DevTools. "Documentation" ocumentation means, whether in electronic or printed form, any users guides, reference guides, administrators guides, configuration guides, release guides, installation guides, and help guides made available through the Designated Portal. Not all of the types of Software Products 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. "Emergency Maintenance" means all maintenance performed when a Cloud Service Request demands immediate, unplanned attention, as reasonably determined by Hexagon. "Equipment" means tangible, personal property to be provided by Hexagon identified in Order Documents, including, but not limited to computing hardware, computer -related equipment, computer devices, furniture, sensors, equipment, unmanned aerial vehicles, and instruments. 'E/C"or"Equipment/Content" means digital content identified in an E/C Schedule and/or any Equipment supplied by or through Hexagon. For purposes of clarity, the term "E/C" excludes Maintenance Services, Cloud Program, Software (except Software intentionally designed and embedded with Equipment), and Services. E/C is subject to E/C Schedules. E/C Schedule" means a document contained within the Order Documents relating to certain E/C provided by Hexagon listed in the Order Documents that address some or all of the following depending upon the offering being addressed. licensing requirements for any embedded Software, maintenance parameters and limitations, warranty, and support provisions. "Error" means a Defect Software 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 is 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 supplants the Replaced Product. "Fixed Price Project Assignment" means a type of Order where Hexagon will provide Services with or without accompanying Product(s) for a fixed price. "Hexagon" means the entity that is a member of the Hexagon Group of companies that is identified in the Order Documents; provided however, as used in the EULA, "Hexagon" means Intergraph Corporation. Hexagon P" means Hexagon or Hexagon Affiliate developed, created, or prepared Intellectual Property. Additional information regarding Hexagon patents, including a list of registered patents associated with the Software Products, is available at www.intergraph.com/patents and/or www.uspto.gov. "Intellectual " 11 Property"or 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, declaring code, implementing code, Documentation, mask work rights, digital data content, design, ideas, product information, inventions and improvements thereto, 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. Cloud 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 Software11 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 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. "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 to data belonging to other customers. For clarity, a Material Adverse Effect is a condition which would render the Cloud unusable or materially less secure for intended users generally, and not merely as a result of individual characteristics associated with Customer or its specific implementation or operation. " etereLicense" 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. "Minimal Operations Levels" means operation of a Software Product without a Level One "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 Requirements17 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 twork 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 offb oa rdi ng 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 En v l ron m e nt. "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 an Order and lasting no more than five (5) consecutive days). "Order" er1f 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 specificproducts, licenses, and/or services at a specified price, subject to the terms and conditions Contracting 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. Any Schedule applicable to the Order is incorporated into the Order Documents as if fully set forth therein. "Perpetual License77 means a type of license for 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," "UB," "CLD," or "MTR" at the end of the Software Product number or the letters "HCL" at the beginning of the Software Product number. Persona Data77 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 Common Terms Glossary and/or references and incorporates a document to which this Common Terms Glossary is an exhibit or attachment. "Product Change Request" means a request for additional functionality or modification to the purchased Cloud Application(s) or Covered Products. "Product uct Order" means a type of an Order that involves only the sale of Products from Hexagon. Product Order may include the sale of Maintenance Services or maintenance for Equipment so long as the subject of the services is also included in the Product Order. This type of Order does not include Services or Cloud Programs. "Product(s)" means either or the combination of Software (including Subscription Licenses), E/C, or other goods, and excluding Services, Maintenance Services, or a Cloud Program. "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 lice nse(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 Prod uct'Spe dfic Terms (including any product's pecific terms delivered in the form of an addendum to the EULA), and later Prod uct'Specific Terms, the later Product -Specific Terms shall take precedence over the EULA and any prior Product'Specific Terms regarding the subject Software. "Purchase ase Order" " 77 or means a document issued by Customer to Hexagon to authorize the delivery of certain Product(s), Services, Deliverables, or Cloud Programs. "Quote" means a document issued by Hexagon reflecting Product(s), 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 Schedule(s). 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 Exchanged Product. "Schedule" means one or more of: E/C Sc Training ProgramSta to ment(s), and/or Special Purpose Schedule(s). "Secure AT Access Tool is a tool designated by Hexagon for providing secure, auditable remote access to Customer utilized environments in order for Hexagon support personnel to effectively perform services. "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 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 CBents 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, Cloud Programs, or XaaS (anything as a service). "S ervices 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 an Order. Cloud Programs are not Services Deliverables. "Software" means the software and Dev ools 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 Product" means the Hexagon or Hexagon Affiliate software product(s) identified in the Order Documents, which includes (i) any associated Hexagon files, sample data, demo data, or media with which the software is provided, (ii) any associated templates, data, printed materials, and "online" or electronic Documentation, and (iii) any Updates 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. For avoidance if doubt, Software Product does not include Developer Tools. 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. "SOW11 means a statement of work setting forth the scope of Services being provided pursuant to an Order. "Special Purpose Item" means an item identified in Order Documents as due to be delivered by Hexagon, which item is subject to certain unique terms, conditions, restrictions, or requirements identified in a Special "Special Purpose Schedule" means a document identifying terms, conditions, and restrictions applicable "S ubscription" 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 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" systemf1 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" or "OnCall Dispatch"), records management system ("RMS" or "OnCall Records"), and G/Technology (G/Tech) are each an example of a Subsystem. "System" means a physical or operational location where the Software 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. "T ask cceptance71 means the event when the Task Acceptance Criteria has been satisfied in accordance "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) Business 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-1to Hexagon. If Customer fails to perform either action identified in the preceding sentence within ten (10) Business 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 Common 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. "T hird arty 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, 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. Unless otherwise specified in the Order Documents, a Time and Materials Project Assignment shall end six (6) months after formation of the Order. "Training Curricula" means one or more training classes or resources provided by Hexagon to Customer as a service over a limited time period. Training Curricula are subject to Training Program Statements. "Training Program Statement" means document(s) titled "Training Program Statement" 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 as contained within the Order Documents. "Update" means any upgrade, modified version, new release, fix, patch and/or update of the Software. Updates can require full installation and a new License Key. Updates are subject to all of the terms and conditions of the EULA provided with User's then current version of the Software; provided that if a new EULAis delivered with an Update, acceptance thereof is a requirement for its use. "User" means Customer and/or an individual employed by Customer and authorized by Hexagon to use a particular Software, Cloud Application, Third Party Software, 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 requisites number of licenses, or in the case of Cloud Programs, the requisite number of License Key(s) to provide Credentials for that User. "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, providedthateach 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 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 Sery Services. "XML Files" means the XML (Exte where applicable. generated by the Software Product, "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 EXHIBIT H DATA PROCESSING ADDENDUM 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 1. DEFINITIONS AND CONSTRUCTION 1.1 Definitions "EU Mode, Cie 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 Legis,ation" 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. "Part„" 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). "Supervisor„ 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 Con stru Cti on 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 it appears, the term "including" shall mean "including without limitation". 2. SPECIAL UNDERTAKINGS OF THE PARTIES 2.2 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 2.1.3 Schedule 1 attached hereto and to the extent it is necessary for the fulfilment of Hexagon's obligations under this DPA or the Agreement. 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. 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) (c) 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; Take all measures required pursuant to GDPR, Article 32; (d) (e) (f) 2.3.1 2.3.2 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, 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 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. Hexagon shall immediately inform the Customer if, in its opinion, a Customer instruction infringes the EU Personal Data Legislation. 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). 3. SUBCONTRACTORS 3.1 3.2 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, Criminal Justice Security Policy, and audit obligations as Hexagon under this DPA. 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 4.2 Personal Data Legislation. 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 4.4 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. 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 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 subcontractors 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- 5.1.3 6. REMUNERATION 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. 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.1 The remuneration for Hexagon's undertakings under this DPA shall, unless otherwise stated in 6.2 6.3 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. 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. The payment terms for the adjusted remuneration shall be governed by the provisions regarding payment in the Agreement. 7. TERM AND TERMINATION 7.1 7.2 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. 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 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. 9. 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] SCHEDULE 1 Data DESCRIPTION OF THE PROCESSING OF PERSONAL DATA 1. Subject matter. The subject matter of the data processing under this DPA is Customer 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. SCHEDULE 2 EU MODEL CLAUSES Commission Declslon 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) And Name of the data importing organisation. The entity identified as "Hexagon" in the DPA (the data importer) each a "party"; together "the parties", HAVEAGREED 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 l personal data specified in Appendix 1. For the purposes of the Clauses. (a) (d) (e) (f) Clause 1 Definitions 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; the data exporter' means the controller who transfers the personal data; '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; '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; 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; 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. 1. Clause 3 Third -Party Beneficiary Clause The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third -party beneficiary. 2. 3. 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 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. 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) (b) (g) 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; 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 exporters behalf and in accordance with the applicable data protection law and the Clauses; that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 to this contract; 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; that it will ensure compliance with the security measures; 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; 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) (i) (J) 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, that, Clause the event of subprocessing, the processing activity is carried out in accordance C with lause 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 Importer2 The data importer agrees and warrants. (a) to process the personal data only on behalf of the data exporter and in compliance with its (b) 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, 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, that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred, that it will promptly notify the data exporter about. 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, any accidental or unauthorised access, and any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so, 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, 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 2 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. (g) (h) (i) (J) 1. 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, 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 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; that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent, that the processing services by the subprocessor will be carried out in accordance with Clause 11; to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter. Clause 6 Liability 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. 3. 1. The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities. 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. Theliability 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) (b) to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; to refer the dispute to the courts in the Member lember State in which the data exporter is established. 2. The parties agree that the choice made by the data subject will not prejudice its substantive 1. or procedural rights to seek remedies in accordance with other provisions of national or international law. Clause 8 Cooperation with Supervisory Authorities 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 Cl auses lauses shall be governed by the law of the Member lember 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. 1. Clause 11 Subproces sing 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 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 4. 1. 2. to in paragraph 1 shall be governed by the law of the Member lember State in which the data exporter is established. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporters 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. 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. 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. 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. 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 provisionsof 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, a description of the likely consequences of the personal data breach; and 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. 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 GDPRor 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 im porter. 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. EXHIBIT I ACCEPTABLE USE POLICY CLOUD SERVICES — ACCEPTABLE USE POLICY A. 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/Cloud the usability C of the loud Services. This AUP is designed to protect the image and reputation of all Customers, the loud Services,/�and Hexagon as a responsible service provider, by taking care of confidentiality and availability of t/Cloud Cloud Services. The rules in this AUP are rules for the acceptable use of the Cloud Services. All Customers and Authorized Users of the Services must at all times comply withthis 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 B. OBLIGATIONS 1. You MUST understand your security obligations within your role and abide by them. Cl oud Your use of the 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 PRIORto uploading them to the Cloud Program. Under no circumstance are files corrupted with viruses Cl oud malware to be uploaded to the 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 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. C. 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. Cloud 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. D. AGREEMENT By accessing and/or using the Cloud Program you accept and agree to/ be bound and abide by this AUP. CIf you do not want to agree to this AUP, you must not access or use the Cloud Program. EXHIBIT J FEDERAL BUREAU OF INVESTIGATION CRIMINAL JUSTICE INFORMATION SERVICES SECURITY ADDENDUM Legal Authority for and Purpose and Genesis of the Security Addendum Traditionally, law enforcement and other criminal justice agencies have been responsible for the confidentiality of their information. Accordingly, until mid-1999, the Code (NCIC) policy paper approved December 6, 1982, exchange of criminal justice information be performed by a criminal justice agency or, in certain circumstances, by a noncriminal justice agency under the management control of a criminal justice agency. In light of the increasing desire of governmental agencies to contract with private entities to perform administration of criminal justice functions, the FBI sought and obtained approval from the United States Department of Justice (DOJ) to permit such privatization of traditional law q enforcement functions under certain controlled circumstances. In the Federal Register of May lay 10, 1999, the FBI published a Notice of Proposed Rulemaking, announcing as follows. 1. Access to CHRI [Criminal History Record Information] and Related Information, Subject to Appropriate Controls, by a Private Contractor Pursuant to a Specific Agreement with an Authorized Governmental Agency To Perform an Administration of Criminal Justice Function (Privatization). Section 534 of title 28 of the United States Code authorizes the Attorney General to exchange identification, criminal identification, crime, and other records for the official use of authorized officials of the federal government, the states, cities, and penal and other institutions. This statute also provides, however, that such exchanges are subject to cancellation if dissemination is made outside the receiving departments or related agencies. Agencies authorized access to CHRI traditionally have been hesitant to disclose that information, even in furtherance of authorized criminal justice functions, to anyone other than actual agency employees lest such disclosure be viewed as unauthorized. In recent years, however, governmental agencies seeking greater efficiency and economy have become increasingly interested in obtaining support services for the administration of criminal justice from the private sector. With the concurrence of the FBI's Criminal Justice Information Services (CJIS) Advisory Policy Board, the DOJ has concluded that disclosures to private persons and entities providing support services for criminal justice agencies may, when subject to appropriate controls, properly be viewed as permissible disclosures for purposes of compliance with 28 U.S.C. 534. We are therefore proposing to revise 28 CFR 20.33(a)(7) to provide express authority for such arrangements. The proposed authority is similar to the authority that already exists in 28 CFR 20.21(b)(3) for state and local CHRI systems. Provision of CHRI under this authority would only be permitted pursuant to a specific agreement with an authorized governmental agency for the purpose of providing services for the administration of criminal justice. The agreement would be required to incorporate a security addendum approved by the Director of the FBI (acting for the Attorney General). The security addendum would specifically authorize access to CHRI, limit the use of the information to the specific purposes for which it is being provided, ensure the security and confidentiality of the information consistent with applicable laws and regulations, provide for sanctions, and ( contain such other provisions as the Director of the FBI (acting for the Attorney General) may require. The security addendum, buttressed by ongoing audit programs of both the FBI and the sponsoring governmental agency, will provide an appropriate balance between the benefits of privatization, protection of individual privacy interests, and preservation of the security of the FBI's CHRI systems. The FBI will develop a security addendum to be made available to interested governmental agencies. We anticipate that the security addendum will include physical and personnel security constraints historically required by NCICsecurity practices and other programmatic requirements, together with personal integrity and electronic security provisions comparable to those in NCICUser Agreements between the FBI and criminal justice agencies, and in existing Management lanagement Control Agreements between criminal justice agencies and noncriminal justice governmental entities. The security addendum will make clear that access to CHRI will be limited to those officers and employees of the private contractor or its subcontractor who require the information to properly perform services for the sponsoring governmental agency, and that the service provider may not access, modify, use, or disseminate such information for inconsistent or unauthorized purposes. Consistent with such intent, Title 28 of the Code of Federal Regulations (C.F.R.) was amended to read. § 20.33 Dissemination of criminal history record information. a) Criminal history record information contained in the Interstate Identification Index (III) System and the Fingerprint Identification Records System (FIRS) may be made available. 1) To criminal justice agencies for criminal justice purposes, which purposes include the screening of employees or applicants for employment hired by criminal justice agencies. 2) To noncriminal justice governmental agencies performing criminal justice dispatching functions or data processing information services for criminal justice agencies, 3) To private contractors pursuant to a specific agreement with an agency identified in paragraphs (a)(1) or (a)(6) of this section and for the purpose of providing services for the administration of criminal justice pursuant to that agreement. The agreement must incorporate a security addendum approved by the Attorney General of the United States, which shall specifically authorize access to criminal history record information, limit the use of the information to the purposes for which it is provided, ensure the security and confidentiality of the information consistent with these regulations, provide for sanctions, and contain such other provisions as the Attorney General may require. The power and authority of the Attorney General hereunder shall be exercised by the FBI Director (or the Director's designee). This Security Addendum, appended to and incorporated by reference in a government -private sector contract entered into for such purpose, is intended to insure that the benefits of privatization are not attained with any accompanying degradation in the security of the national system of criminal records accessed by the contracting private party. This Security Addendum addresses both concerns for personal integrity and electronic security which have been addressed in previously executed user agreements and management control agreements. Agovernment agency may privatize functions traditionally performed by criminal justice agencies (or noncriminal justice agencies acting under a management control agreement), subject to the terms of this Security Addendum. If privatized, access by a private contractors personnel to NCIC data and other CJIS information is restricted to only that necessary to perform the privatized tasks consistent with the government agency s function and the focus of the contract. If privatized the contractor may not access, modify, use or disseminate such data in any manner not expressly authorized by the government agency in consultation with the FBI. EXHIBIT K USE TERMS PRODUCT USAGE POLICY AND PRODUCT -SPECIFIC TERMS These Use Terms, including Product -Specific Terms included in this document, apply to Software licensed to User by Hexagon pursuant to the EULA, including any version of EULA that is part of any other agreement between User and Hexagon that references the Use Terms and/or subject to Third Party Terms identified herein. 1.0 DEFINITIONS. Capitalized terms not otherwise defined herein shall have the meanings set forth in the Common Terms Glossary. 2.0 AUTHORIZED LICENSE AND ACTIVATION. U Products will contact license servers to conduct a license activation and/or validity check to determine whether the license is authorized and authentic and associate it with a certain device. Depending upon the application, license servers may be within or outside the Customer site. During this contact the transmission of certain data will occur. During activation and validity check, the Software Product may determine that the license is invalid or has expired. In the case of an invalid or expired license, User may receive a prompt informing User of such. Although no personal information is transmitted between User and Hexagon during the license activation and check, User's use of the Software Product provides User's continued consent to the transmission of the necessary data for license activation and validity check. Unless otherwise provided by Hexagon, User may not bypass the license activation process, as doing so will invalidate User's license and is considered a violation of these Use Terms. 3.0 LICENSING METRICS. Software Products are licensed as either Production System Licenses or Auxiliary System Licenses. In some Hexagon documents Production System Licenses may be referred to as "Primary Licenses," and Auxiliary System Licenses may be referred to as "Supplementary Licenses." In those instances, please interpret references to "Primary Licenses" as "Production System Licenses," and references to "Supplementary Licenses" as "Auxiliary System Licenses." There are two (2) types of Production System Licenses and seven (7) types of Auxiliary System Licenses as described below. Depending upon User's license, a license may be used in either Concurrent -Use mode or Node -Locked mode. If an electronic license manager tool is incorporated in the Software Product, the license type will be verified by the Hexagon license system. If not otherwise indicated, User's Client license type and mode will be a Concurrent -Use Production System License. Each license of the Software Product is subject to the EULA, Use Terms, and Order Documents. 3.1 Production System Licenses are identified, and applicable terms described, below. 3.1.1 Concurrent -Use mode (CC) is a type of Client license that allows for the checking in and checking out of the total available licenses of the Software Product for Users. At any point, User may run as many copies of the Software Product as User has Client licenses. If the Software Product is enabled to be run in a disconnected mode, as set forth in the Documentation, a User may check out a license from the System for disconnected use, thus reducing the total number of licenses available in the license pool until the license is checked back into the System. User is responsible for assuring the number of Users using the Software Product concurrently does not exceed the number of licenses User has purchased, even if the Software Product contains no license manager mechanism. User consents to the use of a license mechanism, license files, hardware keys, and other security devices in connection with the 3.1.2 Node -Locked mode (NL) is a type of license that allows a single copy of either a Client or Server -based Software Product to be stored on a hard disk and loaded for execution on a single designated workstation, device, or Server. 3.2 Auxiliary System Licenses are identified, and applicable terms described, below. 3.2.1 Passive Disaster Recovery License (BCK) is licensed solely for temporary use when manual switchover of the Software Product to the Auxiliary System License is required in the event of failure of the Production System License. This license may be used in the Production system only during the period of failure of the Production System License. In some Hexagon documents, this type of license may be referred to as a "Backup License." In those instances, please interpret references to "Backup License" as "Passive Disaster Recovery License." 3.2.2 Development System License (DEV) is a license of a Server -based Software Product that is delivered solely in connection with the Production System License of such Software Product for the purposes of developing and testing User's website built only with the Software Product. Development System Licenses shall not be used for Production purposes (i.e., a fully deployed website). In some Hexagon documents, this type of license may be referred to as a "Developer's License." In those instances, please interpret references to "Developer's License" as "Development System License." 3.2.3 Active Disaster Recovery License (RDT) is licensed solely for temporary use when automatic switchover of the Software Product to the Auxiliary System License is required in the event of failure of the Production System License. This license may be used in the Production system only during the period of failure of the Production System License. In some Hexagon documents, this type of license may be referred to as a "Redundant License." In those instances, please interpret references to "Redundant License" as "Active Disaster Recovery License." 3.2.4 Test System, License (TST) is licensed solely for testing and development purposes. A Test System License may not be used for training purposes. 3.2.5 Training System, License (TRN) is licensed solely for training purposes. 3.2.6 Load Balancing License (LOB) is licensed solely to distribute the traffic evenly among multiple Servers. 3.2.7 Secondary License (SEC or TFB) is licensed for nonproductive use for training, development, testing, failover, backup, etc. The total quantity of Secondary Licenses cannot exceed the quantity of purchased Production System Licenses. 4.0 RIGHTS AND LIMITATIONS. 4.1 Unless otherwise stated in the Documentation, for a Software Product that is delivered with an Application Programming Interface ("API") and/or configuration set-up, User may use the API(s) to write User's own extensions to the Software Product, and User may use the 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 User any rights in Hexagon's Intellectual Property (as that term is defined in the EULA and/or any other agreement between User and Hexagon that references the Use Terms) by allowing User to write User's own extensions using the API(s) or to configure the Software Product via the configuration set-up, User hereby agrees and acknowledges that Hexagon retains all rights in its Software Product, API(s), and configuration setup. 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. User's use of such extensions and/or configurations is solely at User's own risk, and subject to applicable law. User hereby agrees to indemnify and hold harmless Hexagon and its suppliers with respect to such extensions and/or configurations. In general, User may not allow the Software Product to be used by multiple Users on a single workstation at the sametime. However, if the license is Node -Locked license with remote access, it is intended to allow Clients Clients to connect to the application Server and does not count the number of connections. 4.3 4.3.1 With a single license, User may run multiple websites and provide multiple webservices to User's client users, provided all websites and webservices reside on the licensed Server. 4.3.2 License fees and installation restrictions for Software Products may be based on the number of Cores present in the Server on which the Software Products are installed. If User's Software Products are Core based, this section will apply. User is responsible for determining the number of Cores on User's host Server and ordering the appropriate number of Core licenses. Eachlicense/�of a Software Product must be installed only on a single Server. For example, a4 Core license does not permit User to install two copies of a component, each on a 2-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, User's usage rights depend upon the relationship between the number of Cores for which User is licensed, the number of physical Cores present on the host Server, and the number of processors available to the Software Product in the virtualized environment. Such rights are determined as follows. if the number of Cores for which User 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 User's licensing restriction; however, if User wishes to install the Software Product on a host Server having a greater number of physical Cores present than the number of Cores for which User is licensed, User must operate the Software Product only within a 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 User is licensed. User may load a Server -based Software Product on multiple machines�lwithin a cluster that is acting as a single web Server, provided User has obtained from Hexagon the appropriate quantity of licenses for the number of Cores, and the total number of Cores deployed do not exceed the quantity licensed. 4.3.3 User may not use a Software Product's java script code for any purpose other than the application for which it was written. 4.3.4 Unless otherwise stated in the Documentation, for Software Products which contain XSLStylesheets for presenting XML Files, User 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 User's enterprise. User may not distribute the XSLStylesheets 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, nor in 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 Intellectual Property of Hexagon. 4.3.5 User may not use the Server -based Software Product to operate software -as -a - service or hosting services without the prior written consent of Hexagon. 4.3.6 User may not, and User may not authorize or allow anyone else to, use the Development System License for Production purposes (i.e., a fully deployed website). 5.0 SPECIAL LICENSE SCENARIOS. 5.1 United States Government Restricted Rights. If the Software (including any Updates, Documentation, or technical data related to such Software) is licensed, purchased, Government, to, or obtained, directly or indirectly, by or on behalf of a unit or agency of the United States Government, then this Section 5.1 also applies. 5.1.1 For civilian agencies: The Software 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). 5.1.2 For units of the Department of Defense: The Software 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). 5.1.3 Notice: This Software 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 is unpublished and all rights are 5.2 Beta Software. If the Software Product is Beta Software, then the following additional terms apply. To the extent that any provision in this section is in conflict with any other terms or conditions in the Order Documents, this section shall supersede such other terms and conditions with respect to the Beta Software, but only to the extent necessary to resolve the conflict. User shall hold all information concerning Beta Software and User's use and evaluation of such information and the Beta Software (collectively, "Beta Software Information") in confidence and with the same degree of care User uses to keep User's own similar information confidential, but in no event shall User use less than a reasonable degree of care; and User 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 User may disclose any Beta Software Information to those of User'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 these terms. User shall not use any Beta Software Information for any reason or purpose other than as necessary for Beta Testing. User agrees to make no other use of the Beta Software Information or to incorporate any Beta Software Information into any work or product. User 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 USER "AS -IS", AND HEXAGON DISCLAIMS ALL WARRANTY AND LIABILITY OBLIGATIONS TO USER OF ANY KIND. User may use the Beta Software only for evaluation and testing and not for general Production use, unless otherwise expressly agreed in writing by Hexagon. User acknowledges that Hexagon has not promised or guaranteed to User 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 User to announce or introduce the Beta Software and that Hexagon may not introduce a product similar to or compatible with the Beta Software. Accordingly, User acknowledges that any research or development that User performs regarding the Beta Software or any product associated with the Beta Software is done entirely at User's own risk. If requested by Hexagon, User will provide feedback to Hexagon regarding Beta Testing, including error or bug reports. Hexagon Customer own any and all Beta Software feedback from Customer and/or User and all Beta Software Information and shall retain full rights to leverage the same for improvement or development of Products; provided further that User and/or Customer shall deliver any assignments or documentation necessary to effect such rights. Upon receipt of a later unreleased version of Beta Software or release by Hexagon of a publicly released commercial version of the Software Product, User agrees to return or permanently destroy all earlier Beta Software received from Hexagon. User agrees to return or destroy all unreleased versions of the Beta Software no later than the date earlier of (i) thirty (30) days of the completion of Beta Testing, or (ii) Hexagon's first commercial shipment of the publicly released commercial software. 6.0 PRODUCT -SPECIFIC TERMS. The following are applicable to User if User has obtained from Hexagon Software identified in this section 6.0. 6.1 One or more of the following Software shall be sublicensed to User by Hexagon pursuant to the EULA plus the Third Party Terms that follow (as evidenced by the individual hyperlinks). Please note that any of the Microsoft products licensed in this section 6.2 are licensed to User pursuant to the latest available version of the Microsoft product as of the date of the Order Documents. For Microsoft SQL Server, User may downgrade and install a prior version of SQL Server that is compatible with their Hexagon system. 6.1.1 Clevest Software See Schedule 1 to this Exhibit SIG032022 SCHEDULE 1 CLEVEST SOFTWARE ADDENDUM to the End User License Agreement for Clevest Software This addendum ("Addendum") is applicable to User in the event User has obtained from Hexagon software products of IFS Canada, Inc. f/k/a Clevest Solutions, Inc. ("Clevest"). With regard to Clevest Software (as defined below), (i) this Addendum modifies the EULA between User and Hexagon related to Clevest Software, and (ii) in the event of a conflict between the EULA and this Addendum, this Addendum shall take precedence over the EULA and any other EULA addendum regarding the subject hereof. The EULAand this Addendum constitute the terms and conditions applicable to Clevest Software. Capitalized terms not defined herein shall have the meaning ascribed to them in the EULA. "Clevest Software" is defined as (i) Clevest's Mobile Work Force Management platform, and (ii) other software applications made available by Clevest, along with any updates thereto. "Clevest Documentation" means all manuals, toolkits, integration tools, guides and other instructions, including information in computer readable format, pertaining to or used in connection with the Clevest Software including all addenda, supplements, additions and modifications to the Clevest Documentation. Clevest Documentation shall also include all instructions, data and other matters included by Clevest in the Clevest Software or on any CD, DVD or other storage media which can be read or printed. Subject to the terms and conditions of this Addendum and the EULA, Clevest grants User a limited, non- exclusive, non -transferable license (the "License") during the term of the EULA to: (i) use the functionality of the Clevest Software for User's internal business purposes only; and (ii) make copies of the Clevest Software and Clevest Documentation solely for non -production, archival or backup purposes, but only if User ensures that all copies User makes of the Clevest Software and Clevest Documentation under this paragraph include all proprietary or intellectual property notices recorded on the Clevest Software. User acknowledges and agrees that this Addendum does not grant User any rights with respect to the source code of the Clevest Software. User covenants andagrees not to translate, create derivative / works of, reverse engineer, decompile or disassemble the Clevest Software in whole or in part. User will not (i) alter, modif/ modify, enhance, adapt, rearrange, reverse engineer, decompile, disassemble, make works derived from the Clevest Software or attempt to generate or access the source code for the Clevest Software, whether by converting, translating, decompiling, disassembling or otherwise, or (ii) enter or manipulate data or information within the database underlying the Clevest Software other than via the Clevest Software. User will not attempt to aggregate users or circumvent Clevest's licensing restrictions via technical means, including, but without limitation, the use of any interface � between the Clevest Software and another program with functionality substantially similar to the Clevest Clevest. User may not modify the Clevest Software without the prior written authorization of User may not sell, loan, lease, rent, license, sublicense, grant a security interest in, distribute or otherwise transfer/�rights to or possession of the Clevest Software in whole or in part to any person or entity, or use Cl evest levest Software in any service bureau or time sharing arrangement, facility management or third party training arrangement or any other arrangement whereUser processes the data of a third party. / User acknowledges and agrees that, as between User and Clevest, Clevestowns and will retain title and / ownership of all intellectual property rights and other interests in and to the Clevest Software and Clevest Documentation (and all copies thereof) including, but not limited to, any improvements thereto whether designed, created and/or developed by Clevest, User or User's agents or contractors, subject to the license rights specifically granted to User in this Addendum. User hereby assigns to Clevest any and all right, title and interest User may have in and to any such improvements and all intellectual property rights therein. Subject to the following sentence, Clevest warrants that the Clevest Software will operate substantially in accordance with the Clevest Documentation and published materials of Clevest except for cases where Cl evest levest Software is not used properly according to the user and installation Clevest Documentation provided by Clevest. The warranties set out in this paragraph are void to the extent User or Clevest third party changes or modifies the Clevest Software in a manner contrary to this Addendum, the Documentation or Clevest's advance written direction. Notwithstanding the foregoing, use of the configuration features of the Clevest Software shall not void any warranty. The warranty afforded by Clevest is not a warranty of Hexagon's installation and/or implementation services. THE FOREGOING WARRANTIES ARE IN LIEU OF ALL OTHER REPRESENTATIONS, WARRANTIES OR CONDITIONS. EXCEPT AS PROVIDED IN THE FOREGOING PARAGRAPH, CLEVEST MAKES NO OTHER REPRESENTATION, WARRANTY OR CONDITION, EXPRESS OR IMPLIED, AND EXPRESSLY EXCLUDES ALL IMPLIED OR STATUTORY WARRANTIES OR CONDITIONS OF MERCHANTABILITY, MERCHANTABLE QUALITY, DURABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND THOSE ARISING BY STATUTE OR OTHERWISE IN LAW OR FROM A COURSE OF DEALING OR USAGE OF TRADE WITH RESPECT TO THE CLEVEST SOFTWARE. CLEVEST DOES NOT MAKE ANY REPRESENTATIONS OR WARRANTIES OF ANY KIND TO USER WITH RESPECT TO ANY HARDWARE OR THIRD PARTY SOFTWARE. IN NO EVENT WILL CLEVEST BE LIABLE TO USER FOR INCIDENTAL, PUNITIVE, EXEMPLARY, AGGRAVATED, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES (INCLUDING BUT NOT LIMITED TO LOST BUSINESS REVENUE, LOST PROFITS, ECONOMIC LOSS, PECUNIARY LOSS, FAILURE TO REALIZE EXPECTED SAVINGS OR LOSS OF BUSINESS OPPORTUNITY), LOSS OF DATA OR PROCUREMENT COSTS, EVEN IF CLEVEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. CLEVEST'S ENTIRE LIABILITY FOR DAMAGES UNDER THIS ADDENDUM SHALL IN NO EVENT EXCEED THE LESSER OF: (I) THE TOTAL AMOUNTS PAID BY USER TO HEXAGON FOR CLEVEST SOFTWARE IN THE 12 MONTHS IMMEDIATELY PRECEDING THE DATE THE CLAIM FOR DAMAGES FIRST AROSE; AND (II) US$500,000. User will comply with all export laws, restrictions and regulations having application to User, whether of Canada, the United States or any foreign agency or authority, and have not and will not export, re-export or otherwise transmit, download or use, directly or indirectly, any software, information, data or other materials received under this Addendum in violation of any such applicable restrictions, laws or regulations. Clevest is a third party beneficiary of this Addendum. C levant-S I G052021 Exhibit L Criminal Justice Agency and ContractorNendor CJIS Network Agreement This document constitutes an agreement between the Pinellas County Sheriff's Office FL0520000 (Criminal Justice Agency) (ORI) AND (ContractorNendor) Hereinafter referred to as the vendor. The criminal justice agency (CJA) and the vendor have a written agreement in which the vendor will provide services to access the Ronda Criminal Justice network (CJNet), National Cnme Information Center (NCIC), the Florida Cnme Information Center, and the Interstate Identification Index (III) all hereafter referred to as FCIC, via network connectivity to the Florida Department of Law Enforcement (FDLE). Agency provides purpose and scope of services of vendor. The vendor, who performs criminal justice functions shall abide by all aspects of the Federal Bureau of Investigations CJIS Security Policy, CJIS Security Addendum, and the rules and regulations set forth by FCIC and the terms and conditions of the Criminal Justice User Agreement, both executed by FDLE. The vendor shall meet the same training and certification criteria required by governmental agencies performing a similar function and be subject to the same extent of audit review as are local user agencies. All private contractors who perform criminal justice functions shall acknowledge, via signing of the CJIS Security Addendum Certification page, which is presented in Appendix H. Modifications to the CJIS Security Addendum shall be enacted only by the FBI. A copy of Appendix H is attached and made part of this agreement. The vendor shall maintain a list of personnel with access to CJI and provide a copy to the Criminal Justice Agency. The vendor shall also maintain a current network topology diagram to meet the FBI CJ1S Security Policy requirements and provide a copy to the Criminal Justice Agency. The Criminal Justice Agency reserves the right to terminate this agreement, with or without notice, upon determining the vendor has violated any applicable law, rule of regulation or has violated the terms of this agreement. IN WITN + ER , the parties have executed this agreement as of the date set forth. /S/ Victor S. Vasile CJA Signature Contractor/Vendor Signature ob CA)44 `e s Vendor Address: Print Name Victor S. Vasile Print Name July 21, 2022 Date Date Hexagon Master Terms and Conditions SIG062021 a -MT Page 70 Sheriff Bob Gualtieri Pinellas County Sheriff's Office "L TAW Fol A S+ 1)441,4° REQUEST FOR PROPOSAL COMPUTER -AIDED DISPATCH & RECORDS MANAGEMENT SYSTEM & MOBILE DATA TERMINAL PAGE 1of 54 PAGES DATE ISSUED: May 28, 2021 R.F.P. 21-02 The Pinellas County Sheriffs Office is seeking proposals from qualified companies to provide a comprehensive, configurable, fully integrated Computer Aided Dispatch (CAD), Mobile Computing (Mobile), and Police Records Management System (RMS) solution. Sealed proposals subject to the 14400 th terms and conditions of this request will be received at the Purchasing and Material ivision, Street N., Door #FPW 4, Clearwater, FL 33762 until 3:00 p.m. EST August 16, 2021. Only the names of the firms submitting proposals will be read aloud at the formal opening. The Sheriff is not subject to the provisions of sec. 287.057 Fla. Stat. The process the Sheriff's Office intends to use is attached to this letter. A Non -Mandatory Pre -Proposal Conference will be held on Jul„ 15, 2021 at 8:30 a.m. EST at the Pinellas County Sheriff's Office Administration Building, 10750 Ulmerton Rd., Largo, Florida, 33778. See paragraph 1.05 of Section A for further information concerning the conference. To be eligible for consideration, the proposing firm must be capable of supplying the services as noted herein and must also meet all other criteria outlined in this proposal. No proposal may be withdrawn for a period of one hundred twenty (120) calendar days after the scheduled time for the opening of proposals. Any proposals submitted after the specified time and date of opening will not be considered. The Pinellas County Sheriffs Office reserves the right to reject any or all proposals received if it is felt to be in the best interest of the Sheriff to do so. Sincerely, Eric Vincent Purchasing Manager 10750 Uimerton Road P.O. Drawer 2500 - Largo, FL 33779 (727) 582-6200 www.pcsoweb.com 1 R.F.P. 21-02 SECTION A GENERAL CONDITIONS 1_0 INTENT The Pinellas County Sheriff's Office (PCSO), in conjunction with a consortium of regional law enforcement agencies, is requesting proposals from qualified vendors to implement a fully integrated Computer Aided Dispatch (CAD), Mobile Computing (Mobile), and Records Management System (RMS) to be utilized by multiple law enforcement agencies in Pinellas County, with the Pinellas County Sheriff's Office serving as the Host Agency. The intent is to purchase a robust, reliable, and modern CAD/Mobile/RMS suitable for a multi -agency deployment to serve the law enforcement agencies of Pinellas County. 1.01 CAUTION NOTICE Any proposal submitted as a result of this Request for Proposal (R.F.P.) shall advise, in writing, of any agreement or understanding currently in effect or intended to compensate a third party for their efforts in securing the award of any contract resulting from this solicitation; i.e., consultants, lobbyists or other individuals not normally employed by the company submitting the proposal, in a sales capacity. Failure to reveal any such arrangement, irrespective if the compensation is monetary or otherwise, shall be grounds to reject your proposal as irreparably defective and may eliminate you as a prospective contractor. Any contract awarded as a result of this R.F.P. where it is subsequently revealed the successful supplier did not provide notice of an agreement to compensate a third party for their assistance in securing the contract shall be grounds to terminate the contract. 1.02 PREPARATION OF PROPOSALS A. Proposals must be submitted one (1) signed original plus nine (9) copies (total of ten proposals), and one (1) electronic version in Microsoft Word Office 2013 or later format and must be in the Purchasing Division prior to the proposal opening time and date which is 3:00 p.m. EST August 16, 2021. Proposals may be hand -delivered or mailed ONLY VIA UPS OR FEDEX WITH SIGNATURE REQUIRED to the Pinellas County Sheriff's Office, Attn: FPW Purchasing Division, 14400 49th Street N., Door #FPW 4, Clearwater, FL 33762. To prevent inadvertent opening, the pre -addressed mailing labels provided with this package must be attached to the outside of your proposal envelope or box. Proposals received after proposal opening time will be returned unopened. B. Proposal information shall be entered in ink or typewritten. Mistakes may be crossed out and corrections inserted before submission of your proposal. Corrections shall be initialed in ink by the person signing the proposal. The vendor is responsible for any errors or omissions. Minor informalities or irregularities readily apparent from the proposal as submitted may be corrected at the discretion of the Sheriff. C. Proposals must be signed by an authorized officer and employee of the vendor. Once received, proposals may not be withdrawn, changed, or modified. The individual signing 2 the proposal shall have the legal authority to bind the vendor to a contract. Any proposal submitted by an agent shall have a current power of attorney attached, certifying the agent's authority to act on behalf of the vendor. D. The standardized "R.F.P. Response Form" provided herein shall be properly signed and included with your proposal response. Failure to comply may disqualify your proposal. 1. All documents, reports, proposals, submittals, working papers, or other materials prepared by the vendor pursuant to this proposal shall become the sole and exclusive property of the Pinellas County Sheriff and shall not be the property of the vendor. Vendors are advised that all information disclosed as part of the R.F.P. process will be interpreted pursuant to the laws of the State of Florida. The Sheriff will make the sole determination whether any submitted documents contain "proprietary confidential business information, regardless of Vendor's opinion of( the "proprietary" or confidentiality of the submitted documents. The PCthe reserves the right to reproduce the submitted proposals for the purpose of evaluation. 2. Use the Excel workbook provided in Attachment A — System Requirements Survey to indicate how the Proposer can satisfy the functional requirements. The Proposer should complete the spreadsheet but should not modify or alter the workbook format in any manner except to provide responses where requested. A blankkresponse will indicate that the Proposer cannot meet the requirement. Modification or alteration of the workbook format may result in the rejection of the proposal. The Proposer should include the workbook in electronic format on a flash drive or other portable electronic storage device in this section. a. The Proposer should leave the workbook as an Excel file and not convert it to .pdf. If the Proposer wants to provide a .pdf version of the Excel file, it should do so in a file separate from the main functional proposal document. b. All detailed requirements in Attachment A —System Requirements Survey are numbered in the left-hand column. These identification numbers should not be changed or omitted in the proposal. 1.03 INTERPRETATIONS/CLARIFICATIONS No oral interpretations will be made to any vendors as to the meaning of any item(s) contained in this document. Every request for such an interpretation must be in writing via email only, addressed to Eric Vincent, Purchasing Manager at hvincent1@pcsonet.com. pcsonet.com. All inquiries must be received no later than 5:00 p.m. on June 14, 2021. Significant interpretations or clarifications will be made by an addendum to the R.F.P. document, which will be sent as promptly as is practicable to all persons to whom the specifications have been issued by the Sheriff's Office and i will also be posted on the Purchasing Divisions official website at http://www.pcsoweb.comiad ministration/purchasing-materials/bid-schedule. All such 3 addenda shall become part of the contract documents. The Purchasing Division shall not respond to questions received after the specified time frame. It shall be incumbent upon the vendor to detail any/all deficiencies or oversights in the content of this R. F.P. and to incorporate them into their proposal. The PCSO will not be financially responsible for items not specifically detailed in any proposal submitted. Information and data provided throughout this R.F.P. are believed to be reasonably accurate. The vendor shall thoroughly acquaint themselves with the proposed project specifications, any addenda, and all State statutes and regulations relating to the execution of the proposal. The vendor will not be allowed additional compensation for their failure to be informed. 1.04 CONSIDERATION OF PROPOSALS It is the Sheriff's intent to conduct a thorough evaluation of all proposals. Every effort shall be made to conduct this evaluation on an expedited basis; however, in the interest of fairness, this review may require substantial time. Accordingly, proposals must be valid for a period of one hundred twenty (120) days from the date of proposal due date. 1.05 NON -MANDATORY PRE -PROPOSAL CONFERENCE/TOUR Prospective vendors are invited to attend a Non -Mandatory Pre -Proposal Conference. The conference will be held on July 15, 2021 starting at 8:30 a.m. EST at the Pinellas County Sheriff's Office Administration Building, 10750 Ulmerton Rd., Largo, FL 33778. The purpose of this conference is to answer and explain any questions concerning the specifications of the R.F.P. Attendance must be confirmed by sending the names of the attendees via email only, addressed to Eric Vincent, Purchasing Manager at hvincentl @pcsonet.com. 1.06 INSURANCE The successful vendor must provide a Certificate of Insurance in accordance with Insurance Requirements, Section C, prior to execution of a contract or commencement of any work hereunder. 1.07 LICENSES AND PERMITS Contractual services performed for the PCSO will require licenses and permits in the same manner as private projects within the county. The successful vendor shall secure, at his/her expense, all licenses and permits and shall comply with all applicable laws, regulations, and codes as required by the State of Florida, Pinellas County, or the municipality of his/her principal place of business. The successful vendor must fully comply with all federal and state laws, county and municipal ordinances, and regulations in any manner affecting the performance of the work. PCSOwill not agree to an arbitration clause or to waive the right to trial by jury. 4 1.08 CONTRACT After approval by the Sheriff of Pinellas County, a written contract incorporating the pertinent terms and conditions provided in the R.F.P., the proposal submitted and other documents named herein will be negotiated and executed between the successful vendor and the PCSO. The laws of the State of Florida shall govern in connection with the formation, performance, and the legal enforcement of any contract resulting from this R.F.P. 1.09 GRIEVANCE TO CONTRACT/PURCHASING R.F.P. POLICY Any complaint or grievance concerning a question of fact arising out of the R.F.P. process or award of this contract, not otherwise/Idisposed of by agreement, shall be committed to writing and submitted to the Purchasing Manager. The Purchasing Manager shall investigate the validity of the complaint and present his/her findings in writing to the vendor. If the vendor is dissatisfied with the remedies provided by the Purchasing Manager, the vendor may appeal in writing to the Sheriff of Pinellas County. The decision of the Sheriff in this matter shall be final. 1.10 EXCEPTIONS TO CONDITIONS AND SPECIFICATIONS A. The Sheriff's Office may consider any specific exceptions to the required specifications and conditions of the Request for Proposal. All exceptions shall be clearly identified as such on the proposal form or by separate enclosed correspondence. The nature of a Request for Proposal permits the Evaluation Committee to consider and accept these exceptions if solely within their judgment they are beneficial and in the best interest of the Sheriff's Office and the intent of this proposal. B. It is the intent of this Request for Proposal to receive competitive proposals. It is the responsibility of vendors who receive this Request for Proposal to advise the Purchasing Manager, in writing, of any language or requirements that may inadvertently restrict or limit competition to a single source. 1.11 RIGHTS OF PINELLAS COUNTY SHERIFF IN R.F.P. PROCESS In addition to all other rights of the Sheriff's Office under Florida law, the Sheriff's Office specifically reserves the following. A. The Pinellas County Sheriffs Office reserves the right to rank and negotiate with firms. Negotiation with an individual vendor does not require negotiation with others. B. The Pinellas County Sheriff's Office reserves the right to select the proposal that it believes will serve the best interest of the Sheriff's Office. C. The Pinellas County Sheriff's Office reserves the right to cancel the entire Request for Proposal. D. The Pinellas County Sheriff's Office reserves the right to remedy or waive insignificant technical or immaterial errors in the Request for Proposal or in proposals submitted. E. The Pinellas County Sheriff's Office reserves the right to request any necessary clarifications or proposal data without changing the terms of the proposal. 5 F. Vendors are hereby advised, although this solicitation permits discussions/negotiations, the Sheriff reserves the right to make an award without holding discussions. Therefore, Vendors are cautioned to make their initial proposal a complete and thoughtfully prepared offer. G. The Pinellas County Sheriffs Office reserves to itself the right to adopt or use for its benefit, any concept, plan, or idea contained in any proposal. H. The Pinellas County Sheriff's Office reserves the right to delay the scheduled due dates and start dates if necessary. There shall be no additional costs assessed by vendors due to these delays, should any occur. 1.12 DISQUALIFICATION/REJECTION OF PROPOSALS A. The Pinellas County Sheriff reserves the right to disqualify proposals before or after opening with evidence of collusion, intent to defraud, or other illegal practices on the part of the vendor. B. The Sheriff may reject a proposal if. C. 1. The vendor misstates or conceals any material fact in the proposal. 2. The proposal does not strictly conform to the law or requirements of the proposal. The Sheriff may reject any or all proposals whenever it is deemed in the best interest of the PCSO to do so. He may reject any part of a proposal unless the proposal has been otherwise qualified by the vendor. He may also waive any minor informalities or irregularities. 1.13 VENDOR PRESENTATION Selected vendors who have submitted responsive proposals may be asked to conduct an onsite evaluation committee presentation. Vendors will only be allowed to attend their own presentation, and should be prepared to demonstrate all aspects of the CAD, RMS, and Mobile Solution, including components of the system that are referenced in Attachment A System Requirements Survey. Changes to the proposal will not be permitted during any onsite presentation. 1.14 BEST AND FINAL OFFER The PCSO reserves the right to request Best and Final Offers and to enter into competitive negotiations with selected vendors. 1.15 CONTRACT PERIOD Any contract awarded as a result of this R.F.P. shall remain in effect for a period of five (5) years. Contract start date shall be the date of execution by both parties, or as specifically stated in said contract. 6 1.16 OPTION TO RENEW Upon expiration of the initial five (5) year contract term, the contract will automatically renew in one (1) year increments unless terminated. If the parties agree upon a renewal term for a period other than one (1) year, the revised term will be memorialized in a signed amendment. 1.17 TERMINATION CLAUSE The Pinellas County Sheriff, in his sole discretion, and with or without cause therefore, may terminate the contract at any time by giving written notice of such termination and specifying the effective date thereof, at least thirty (30) days before the effective date of such termination. Upon receipt of written notice of termination of the contract, the parties hereto shall mutually review, within thirty (30) days, all outstanding commitments and other matters relative to the services contemplated by the contract. 1.18 TERMINATION FOR DEFAULT The Sheriff's Office may, by written notice of default to the contractor, immediately terminate in whole or in part, the contract, should any one of the following circumstances occur: A. If the contractor fails to perform the services as requested or specified within the time required, therefore; or B. If the contractor fails to perform or adequately perform any of the other provisions of the contract and fails to commence and diligently and continuously q pursue a cure within a period of five (5) days after receipt of notice from the Contract Monitor lonitor providing notice of such defect or deficiency. 1.19 PAYMENTS/INVOICES The contractor must provide invoicing for services with support documentation to demonstrate the provision of services sufficient to meet the minimum requirements for fiscal accountability. t is the contractor's responsibility to submit accurate invoices. The contractor is responsible for immediately notifying the Purchasing Division of any company name change, which would cause invoicing to change from the name used at the time of award of contract. Payment will be made, in arrears, in accordance with Fla. Stat. § 218.70, et. seq., the Florida Prompt Payment Act. 1.20 PERFORMANCE GUARANTY Within thirty (30) days of contract award, the successful vendor will file with the Pinellas County Sheriffs Office a performance bond/guaranty with a corporate surety licensed by the Department of Insurance in the State of Florida equal in value to ten (10) percent of the R.F.P. cost submitted. The surety shall have a rating classification of ''A' and a financial category of Class XI as evaluated in the current BEST's Key Rating Guide, Property Liability. The performance bond/guaranty shall be effective for the entire contract period and serve as security for the faithful performance of the contract and as security for the payment of all persons performing labor and furnishing materials in connection with the contract. 7 1.21 FISCAL NON -FUNDING CLAUSE In the eventvrsufficientebudgeted fundsare not available for a new fiscal period, the Pinellas County Sheriffs Office shall notify the contractor of such occurrence, and the contract shall terminate on the last day of the current fiscal period without penalty or expense to the PCSO. 1.22 ADDENDA All vendors shall acknowledge receipt of any addenda to this Request for Proposal. Addenda shall be signed by the vendor and included with the proposal response. Failure to acknowledge receipt of any addenda may render the proposal to be non -responsive. Any related addenda to this R.F.P., including written answers to questions, will be sent as promptly as is practicable to all vendors to whom the specifications have been issued by the Sheriff's Office and will be posted on the Purchasing Division s official website at www.pcsoweb.com/administration purchasing-materials/bid-schedule. It is recommended that any vendor submitting a proposal check the website daily for addenda and updates after the release date. Vendors shall print out, sign, and return addenda acknowledgement(s) with their R.F.P. 1.23 CONTRACTOR'S PERSONNEL STANDARDS A. The Pinellas County Sheriff requires personnel providing contract services to comply with background investigations and/or security checks. These background investigations may require the personnel to (be fingerprinted, and will be performed by the PCSO at no charge to the contractor. The PCSO reserves the right to disallow the use of any individual (under the terms of any contract awarded as a result of this R.F.P.) who is deemed to pose a security risk. The contractor shall provide to the PCSO a written list of the names and addresses of all employees and the positions of said employees who are to perform the work outlined in the contract. B. The contractor shall use all reasonable care consistent with its rights to manage and control its operation not to employ any persons, use any labor, use or have any equipment, or permit any condition to exist which may cause, or be conducive to, any complaint, trouble, dispute or controversy � which interferes or is likely to interfere with the operation of the PCSO. The Pinellas County Sheriff shall have and exercise full and complete control over granting, denying, withholding, withdrawing, or terminating clearances for employees. C. The contractor shall comply with all Federal, State and local laws, executive orders, and rules and regulations applicable to the work. i D. The contractors personnel shall immediately report all accidents or unusual incidents occurring on PCSO premises to the Sheriff's designee for the work. Unusual or catastrophic events involving personnel or equipment covered by the contract shall, within three (3) business days, be followed by a written email notification to the PCSO contract monitor detailing the circumstances surrounding the event and the actions taken or to be taken by the contractor. 8 E. E-VERIFY: In accordance with Florida Statute §448.095, if this contract is to provide labor, supplies or services, Vendor must agree: (a) You have registered and you use the E-Verify system to verify the work authorization status of all newly hired employees; (b) If a subcontractor provides labor, supplies or services for this contract, you will obtain and maintain the required affidavit(s); (c) A contract terminated pursuant to this section is not a breach of contract and shall not be considered as such; and (d) You shall be liable for any additional costs incurred by the Sheriff as a result of a termination pursuant to this section. 1.24 SUBCONTRACTORS The contractor will be fully responsible for all acts and omissions of subcontractors and of persons directly or indirectly employed by them and may be liable to the same extent as if they were employed by him. Nothing in the contract documents shall create any contractual i relationship between any subcontractor and the Sheriffs Office or any obligation on the part of the Sheriff's Office to pay or to see to the payment of any monies due to any subcontractor, i except as may otherwise be required by law. The Sheriffs Office may furnish to any subcontractor, to the extent practicable, evidence of amounts paid to the contractor for specific work completed. All vendors shall include with their response a list of subcontractors to be used in the performance of the work requested. 1.25 PUBLIC RECORDS LAW Section 119.0701, Florida Statutes (2016) requires that all contractors comply with Florida's public record laws with respect to services performed on behalf of the Sheriff. Specifically, the statute requires that all contracts entered into or amended after July 1, 2016 shall contain the following statement in at least 14-point boldfaced type: If the contractor has questions regarding the application of Chapter 119, Florida Statutes, to the contractor's duty to provide public records relating to this contract, contact the custodian of public records at: Pinellas County Sheriffs Office 10750 Ulmerton Rd. Largo, FL 33778 Ph.: 727-582-6200 contractor pcsonet.com Additionally, all contracts are required to contain the following: 1. Keep and maintain public records required by the public agency to perform the service. 9 2. Upon request from the public agency's custodian of public records, provide the public agency 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 this chapter 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 for the duration of the contract term and following completion of the contract if the contractor does not transfer the records to the public agency. 4. Upon completion of the contract, transfer, at no cost, to the public agency all public records in possession of the contractor or keep and maintain public records required by the public agency to perform the service. If the contractor transfers all public records to the public agency 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 contractor shall meet all applicable requirements for retaining public records. the records stored electronically must be provided to the public agency, upon request from the public agency's custodian of public records, in a format that is compatible with the information technology systems of the public agency. Failure to comply with these provisions is considered an immediate breach of contract. 1.26 ASSIGNMENT The contractor will not assign, transfer, convey or otherwise dispose of this contract or any part thereof, or of its right title or interest therein, or its power to execute this contract or any amendment or modification hereto, to any person, company, or corporation, without the prior written consent of the Sheriff or his designee. Sale of a majority of corporate stocks, filing for bankruptcy, or reorganization shall be considered an assignment. 1.27 NOTICES All notices required under the terms of this contract shall be delivered by certified or registered mail with a return receipt request to the physical address provided by each party. 1.28 PUBLIC ENTITY CRIMES Vendors are directed to the Florida Public Entity Crime Act, §287.1 33, Florida Statutes, and the i Sheriffs requirement that the successful vendor complies with it in all respects prior to and during the term of this contract. 1.29 AMERICANS WITH DISABILITIES (ADA) The Pinellas County Sheriff's Office complies with the ADA and, upon appropriate notification, will make reasonable accommodations to permit individuals with disabilities to participate in solicitations issued by this office. 10 1.30 INDEMNIFICATION, PATENTS & COPYRIGHTS A. The first ten dollars ($10) of compensation received by the successful vendor shall hold harmless and indemnify the Sheriff and shall also pay all costs of defense, including attorneys fees, in connection with any and all suits, actions, demands, or claims of any kind relating to, arising out of, or resulting from the vendor s and the vendor s officers , employees , agents , i or representatives negligent acts, wrongful acts, omissions, or performance or failure to perform the services, responsibilities, or duties the vendor has agreed to perform in the contract. B. The successful vendor agrees to indemnify the Sheriff and hold him harmless from and against all claims, liability, loss, damage, or expense, including attorneys fees, arising from or by reason of any actual or claimed trademark, patent, or copyright infringement or litigation based thereon, used in the performance of this contract. If the vendor uses any design, device, or materials covered by a patent, trademark, or copyright, it shall be mutually understood and agreed without exception that the proposal prices shall include all royalties or costs arising from the use of such design, device, or materials in any way involved in the work. 11 R.F.P. 21-02 SECTION B SPECIFICATIONS COMPUTER -AIDED DISPATCH, RECORDS MANAGEMENT SYSTEM, AND MOBILE DATA TERMINAL 2_0 INTRODUCTION In late 2019, representatives from the Pinellas County Sheriff's Office, Pinellas County municipal police departments, and the Pinellas County Regional 9-(1�-1 (R911) Center met to explore a consolidated Computer -Aided Dispatch (CAD), Mobile Computing (Mobile), and Police Records Management System (RMS) solution, hereafter referred to as System and formed a collective group referred to as the Consortium. The Consortium agreed to transition to a highly reliable, tightly integrated System that will provide immediate access to cross -jurisdictional information at any time, on any device, to increase officer safety, improve data sharing, and reduce community crime and victimization. On May 7, 2021, the Pinellas County Sheriff's Office, Clearwater Police Department, Pinellas Park Police Department, Largo Police Department, St. Petersburg Police Department, and Springs P of ice Department executed a Letter of Intent to explore a mutual benefit of these agencies and the citizens and communities Tarpon consolidated System for the they support. Additionally, the Letter of Intent affirmed the Consortium's desire for the Pinellas County Sheriffs Office to serve as the Host Agency to publish an RFP for the System. If a vendor selection occurs, the PCSOwill serve as the lead agency contracting with and managing the vendor relationship. Upon contract execution, the Consortium intends to establish a governance structure to be the decision- s making body that oversees the selected solutions configuration, implementation, operation, and cost, while adhering to change management best practices for modification and change. As a result, the Pinellas County Sheriff's Office seeks proposals from qualified companies to provide a comprehensive, configurable, fully integrated System. The System shall be used in all organizational areas, supporting multiple law enforcement agencies in Pinellas County, Florida. Ahosted web -based application with mobile device capability is preferred and should include the following modules: • Call Taking • Dispatch • CAD Administration • Reports Management • Offense/Incidents • Supplements • Property and Evidence Management • Crime Analysis 12 • Case Management • Intelligence and Narcotics • Affidavit • Pawn • Florida Uniform Citations • Traffic and Crash Scene Management • Personnel Skills/Qualifications (e.g., drug recognition expert, dive team member, multi- lingual, and other capabilities) Optional, but preferred, modules include. • Subpoena Management • Scheduling • Training/Certifications • Internal affairs/Complaint/Use of Force • Tracking of agency issued equipment • Canine (e.g., logging successful catches drug smells, and training) • FTO Training Module Services associated with implementing the System shall include. • Project management • System architecture, design, and configuration • Software customization to meet specifications • Data migration services • Interface development • Systems integration, testing, and implementation • Training • Organizational Change Management If the Proposer cannot offer a complete solution, the Consortium Team will consider vendors who partner to provide the most comprehensive solution and best -in -breed component solutions. However, the solicitor will contract with a single vendor who brings a complete solution to them as the prime integrator. The Consortium will not act as the prime integrator. The Consortium is additionally interested in an integrated 911, Fire, and EMS Computer -Aided Dispatch system, with Fire Records Management. Although not incorporated in this RFP, the System should be scalable to integrate some or all of these components for use by the Pinellas County Regional 9-1-1 Center. R911 currently supports 120 consoles, and 600 mobiles. 13 2.1 BACKGROUND / KEY METRICS Pinellas County is a peninsula located on the west coast of Florida, west of Tampa Bay. Pinellas County is 38 miles long and 15 miles at its broadest point, for a total of 280 square miles with 588 miles of coastline. The most densely populated county in Florida, Pinellas County, has more than 983,867 residents. Pertinent to this RFP, there are twelve (12) law enforcement agencies in Pinellas County serving 24 cities. The Pinellas County Sheriff's Office is the largest law enforcement agency in the county. It provides the primary law enforcement services for approximately 398,085 people that reside in unincorporated areas of Pinellas County and the cities of Belleair Beach, Belleair Bluffs, Belleair Shores, Dunedin, Indian Rocks Beach, Madeira Beach, North Redington Beach, Oldsmar, Palm Harbor, Redington Beach, Safety Harbor, St. Pete Beach, Seminole, and South Pasadena. The Pinellas County Sheriff's Office also provides dispatch services for Belleair, Gulfport, Indian Shores, Kenneth City, and Treasure Island Police Departments. The following law enforcement agencies serve the collective population of more than 983,867 as shown in the following chart: Law Enforcement Agency Population Served Pinellas County Sheriff's Office 398,085 St. Petersburg Police Department 270,623 Clearwater Police Department 118,017 Largo Police Department 85,000 Pinellas Park Police Department 53,000 Tarpon Springs Police Department 25,937 Gulfport Police Department 12,598 Treasure Island Police Department 6,930 Kenneth City Police Department 5,145 Belleair Police Department 4,095 Indian Shores Police Department with Redington Shores 3,661 Pinellas Schools Police N/A 14 The following table describes the primary Consortium member• s staffing levels. Law Enforcement Agency Sworn Law Enforcement Civilians Volunteers Pinellas County Sheriffs Office 842 1,050 30 St. Petersburg Police Department 585 293 70 Clearwater Police Department 245 153 40 Largo Police Department 157 60 20 Pinellas Park Police Department 106 24 9 Tarpon Springs Police Department 53 10 - Gulfport Police Department 32 4 4 Treasure Island Police Department 19 5 - Kenneth City Police Department 15 2 0 Belleair Police Department 22 4 0 Indian Shores Police Department with Redington Shores 14 2 0 Pinellas County Schools Police 39 9 0 Total 2,127 1,615 173 2_2 CURRENT CAD ENVIRONMENT Across the twelve (12) law enforcement agencies mentioned above, there are six (6) different Computer -Aided Dispatch systems. The Pinellas County Sheriffs Office and Clearwater Police Department separately�gcontract with CentralSquare using the Enterprise Computer -Aided Dispatch and Mobile lobile products. This systemis shared with six other municipal police departments through inter -local agreements with the Pinellas County Sheriff's Office. The Largo Police Department contracts with CentralSquare, formerly Superion, using One Solution, which is nearing obsolescence. Of the Consortium members, the Largo Police Department has the most acute need for a replacement. The St. Petersburg Police Department uses Hexagon, formerly Intergraph, the current release of which is nearing the end of support and is in need of a full release upgrade or system replacement. The current Computer -Aided Dispatch products in use by law enforcement agencies in Pinellas County are as follows. 15 CADVendor Law Enforcement Agency CentralSquare (TriTech) — Enterprise v.21.1.2.1 Pinellas County Sheriff's Office Tarpon Springs Police Department Gulfport Police Department Treasure Island Police Department Kenneth City Police Department Belleair Police Department Indian Shores Police Department Hexagon (formerly Integraph) v. 9.2 M R6 S. Petersburg Police Department CentralSquare (TriTech) — Enterprise v5.8.38.2 Clearwater Police Department CentralSquare (formerly Superion) ONESolution v20.3.0 Largo Police Department Tyler - New World Public Safety v. 2018.4 Pinellas Park Police Department CORE CAD (developed in-house) Pinellas County Regional 911 Calls for law enforcement services are generated from 911 calls, calls to law enforcement agency non -emergency lines, or self -initiated activity by law enforcement personnel. R911, the county's primary public safety answering point (PSAP), initially answers all 911 calls where the call is screened to determine the nature (police, fire, or EMS) and jurisdiction. If the call requires a law enforcement response, the call may be transferred from R911 to one of five secondary PSAPS (Pinellas County Sheriff, St. Petersburg Police, Clearwater Police, Largo Police, Pinellas Park Police) operated by municipal law enforcement agencies. Currently, R911 CAD data can only be sent to the Pinellas County Sheriff's Office via CAD -to -CAD interface; other CAD systems in the county do not interface with the R911 CAD. In 2019, R911 transferred over 252,000 law enforcement -related 911 calls to secondary PSAPS. The number of 911 calls transferred and the total number of CAD events by each law enforcement agency are shown in the following chart. 16 Law Enforcement Agency # of 911 calls for service # of non- emergency inbound calls # of total CAD events Pinellas County Sheriffs Office 109,579 420,000 408,064 St. Petersburg Police Department 71,073 338,620 298,534 Clearwater Police Department 31,119 139,067 175,940 Largo Police Department 20,274 126,002 91,270 Pinellas Park Police Department 10,140 77,226 104,248 Tarpon Springs Police Department 4,232 12,923 Included with PCSO Gulfport Police Department Included with PCSO Included with PCSO Treasure Island Police Department Included with PCSO Included with PCSO Kenneth City Police Department Included with PCSO Included with PCSO Belleair Police Department Included with PCSO Included with PCSO Indian Shores Police Department with Redington Shores Included with PCSO Included with PCSO Total 246,417 1,113,838 1,078,056 2_3 CURRENT RMS ENVIRONMENT The Pinellas County Sheriffs Office currently utilizes ACISS Systems for records management. This system is shared with multiple law enforcement agencies in Pinellas County, including the Clearwater Police Department, Tarpon Springs Police Department, Gulfport Police Department, Treasure Island Police Department, Kenneth City Police Department, Belleair Police Department, and Indian Shores Police Department through inter -local agreements. The St. Petersburg Police Department uses Hexagon (Intergraph I LEADS). The Largo Police Department uses CentralSquare's One Solution, and the Pinellas Park Police Department uses Tyler Technologies. The current systems support criminal reports, non -criminal reports, field interview reports, the management of tips and tasks, latent reports, crime scene reports, gang activity reports, intelligence reports, property and evidence management, supplement reports, crash reports, 17 citation reports, use of force reports, and others. Crime analysis is often accomplished through third -party software. The Record Management System in use and the volume of reports generated in 2019 are shown in the following chart. Law Enforcement Agency RMS Vendor # of reports in 2019 Pinellas County Sheriff's Office ACISS Systems v2.65 337,643 St. Petersburg Police Department Hexagon / ACISS v09.00.0200.00075 115,830 Clearwater Police Department ACISS Systems v2.65 64,674 Largo Police Department Central Square ONESolution RMS v20.3.0 12,927 Pinellas Park Police Department Tyler Technologies, New World Public Safety v2018.4 9,820 Tarpon Springs Police Department ACISS Systems v2.65 Included with PCSO Gulfport Police Department ACISS Systems v2.65 Included with PCSO Treasure Island Police Department ACISS Systems v2.65 Included with PCSO Kenneth City Police Department ACISS Systems v2.65 Included with PCSO Town of Belleair ACISS Systems v2.65 Included with PCSO Indian Shores Police Department with Redington Shores ACISS Systems v2.65 Included with PCSO Total 540,894 2_4 SYSTEM ARCHITECTURE The Consortium expects the Proposer to provide the software, infrastructure specifications, recommendations, and requirements, as well as services necessary to implement the System successfully. All the software needed for a fully functioning and fully integrated System is expected at the time of implementation completion. The System must fully comply with the current Florida Department of Law Enforcement CIS Security Policy. Proposers are responsible for providing a System with sufficient capacity and performance capabilities to support the requested licenses and volumes, plus a margin for expected growth. Proposers shall provide an appropriate response for each of the following. 18 A. It is preferred that the System architecture conforms to a mobile -first, cloud -first model. Describe the architecture necessary to provide connectivity to the application(s) across all Consortium members and locations. B. Describe how the System can be cloud -based while providing on -premise edge technology to prevent outages if connectivity to the Internet is unavailable. C. Provide a diagram of the proposed system architecture. The diagram should include an overall representation of the servers (application, database, Web, reporting), network (internal, external, and inter -agency connectivity), peripherals, workstations, mobile data components, and interface points, as well as a representation of the System environments Training/Testing). Backup, and I raining I esting). D. Are there any parts of the System that are not cloud -based? Please describe. E. Describe your hosting model, including hosting, integration, help desk, provision and desktop management capabilities, deployment model (dedicated servers, shared environment, etc. , and any 3ra party partners that may be involved in service delivery. F. Describe the bandwidth requirements for CAD, RMS, and Mobile. G. Provide the total number of clients and the corresponding number of end -users of hosted systems currently supported by your company. H. Describe your proposed service level agreement, including any tiered service levels, response times, and standard metrics. I. Describe your support model, including cost structure for support calls and all items covered in Section 2.20 K - Pre- and Post -Implementation Support Plan (below). J. Describe your data center and storage facilities, including locations, staffing, physical security, environmental controls (including redundant power), redundancy load balancing capabilities, data backups, and disaster recovery capabilities. K. Describe your logical security, including firewall security, authentication controls, and data encryption capabilities. L. Describe your change management, upgrade, and patch management policies and practices to include dot releases and full release upgrades, including frequency of required updates. M. Describe your systems administration management capabilities, including monitoring of performance measures, intrusion detection, and error resolution. N. If the System is not cloud -based: 1. Does the System run in a virtualized environment? The current architecture environment should be VMware 6.5 or higher. 2. Describe the approach for maintaining the current version of VMware. 19 3. The System should be fault -tolerant for high availability and disaster recovery. Describe which components cannot be virtualized, if any, and provide an explanation why. 4. Do operations automatically failover to the High Availability environment should operations in the production environment fail? 5. What steps, degree of user intervention, and time is required to return operations to the primary environment? 0. Describe how the System scales with no performance degradation to function across the six Consortium's geographically dispersed Communication Centers. P. If a Consortium agency's Communication Center location becomes inoperable, from a System perspective, describe how members of that Communication Center can move to an alternate location and resume System functions. Q. Describe the Proposer's history in serving multiple PSAP locations (e.g., primary and multiple secondary PSAPs), ensuring consistently optimized system performance at all locations. 2_5 PERFORMANCE AND RELIABILITY A. Describe the proposed System High Availability (HA) model and plan. B. Describe any impact to the System (e.g., system shutdown, reboot) and System use that will occur during. 1. Server upgrades 2. Software Upgrades/Updates C. All System components are expected to operate concurrently. How will Proposer ensure concurrent operations of all System components without any System degradation? D. The System is expected to be available 99.99 percent of the time. Describe how the Proposer will guarantee this level of System availability both initially and during the life of the agreement. 2_6 SYSTEM BACKUP A. Describe the Proposer's recommended approach for System backup, data options, and availability. B. How will the Proposer's recommended System backup affect the live operation of the System? 20 C. Are all System functions available during backup? of the System function during backup. If not, explain the level of availability D. Will the Proposer's recommended approach for System backup enable a full backup of the System? If so: 1. What is the maximum time a full backup will take? 2. Can the full backup be performed unattended? 2.7 SYSTEM RECOVERY A. Describe the proposed method of restoring data files. B. Describe the process for recovering the system to a particular point in time. How will the Proposer support a fifteen -minute or less Recovery Point Objective (RPO)? C. During the restore process, will any functionality be lost or limited? 2_8 OPERATING SYSTEM A. The Consortium and partner agencies have standardized on Microsoft Windows Server 2019 and Windows 10 for clients. Does the proposed solution comply with this standard? B. How does the Proposer intend to maintain currency with Windows operating systems? C. Provide the name and version number of the current proposed Operating Systems (servers and clients). D. Provide proposed timelines for keeping the System current with standard Operating Systems over the next five years. E. If the Proposer's recommended operating system incorporates any proprietary or non- standard components, provide justification for the component (server and clients). 2_9 SOFTWARE LICENSE AGREEMENT The Consortium cannot overemphasize the importance of enterprise licensing (site license) for the System. Although there may be restrictions and limitations, unlimited use of the System throughout the Consortium is preferred. Devices: Law Enforcement Workstation Mobile Smartphone Agency 21 Pinellas County Sheriff's Office 25 1,252 1,026 St. Petersburg Police Department 15 175 698 Clearwater Police Department 15 282 300 Largo Police Department 9 140 160 Pinellas Park Police Department 7 109 120 A. Include copies of the proposed standard software licensing agreement. B. Does the Proposer provide the preferred site license option(s) for all System components proposed? If not, please identify those components for which site licensing is not an option and indicate why a site license would not be the most cost-effective option. C. What type of licensing agreement is proposed (e.g., concurrent, named, etc.), and the number of licenses proposed for each application. 1. CAD 2. Mobile 3. RMS 2.10 CYBERSECURITY/INFORMATION SECURITY A. Describe to what level of depth security and permissions may be controlled within an application module (e.g., field, module, application, or system, etc.). 1. Describe the security requirements for the Intelligence module 2. Describe the security requirements for the Narcotics module 3. Describe the security requirements for the Property and Evidence module B. Describe the cybersecurity deployed with the solution 1. Infrastructure 2. Application (data encryption, tokenization, etc.) 3. Transport 22 C. Describe your cybersecurity posture and your compliance with relevant security standards (e.g., NIST, ISO-27000, CJIS). D. What cybersecurity features prevent unauthorized access to the System or system data? E. What cybersecurity features prevent computer viruses, hidden "logic bombs," "back doors," or any other such code that could be activated inadvertently or otherwise at a later date or time? F. What cybersecurity features prevent ransomware from encrypting System data? What guarantees against successful ransomware attacks are provided? G. Describe what security functions are supported by security within the application software versus those provided by system software or the operating system. H. Describe how the proposed System manages unsuccessful log -on attempts. 1. Can the Consortium establish the number of log -on attempts allowed? 2. What is the reporting or alerting mechanism used to communicate unauthorized access? 3. Describe how the System allows users to reset their passwords. 4. Describe how the system administrators can manage the passwords of their users without impacting other Consortium agencies. I. Can users log onto all proposed applications with one login? J. Can users be imported updated from Active Directory? K. Does the System support multi -factor authentication? If so, describe the types of multi - factor authentication supported (e.g., SIVIS/text message, facial recognition, smartcard, "bingo cards biometrics, etc."). 2.11 SYSTEM ADMINISTRATION A. What periodic System management functions should be performed to maintain System performances B. How much System Administrator time is needed per week, broken down by activity type? C. Identify the resources required to provide ongoing support for the system after implementation. Include a description of the Consortium personnel and roles required to manage the proposed system post -implementation. D. Do any applications require a restart and/or additional login for configuration changes to take effect? 23 CE. Describe how Consortium members will maintain global system configurations. F. Describe how CConsortium members will maintain local system configurations. G. Describe how Consortium agencies can maintain their users within the System without impacting other organizations. H. Describe how global configuration changes will not impact or overwrite local configurations. 2.12 GENERAL FUNCTIONALITY The applications within this proposed system must be fully integrated and meet all the minimum technical, functional, and performance requirements stated within the attachments. A. The Consortium requires multiple external database queries in a single transaction, such as FCIC/NCIC, RMS, Odyssey, and the Affidavit System. Describe the proposed approach to meeting this requirement and any limitations to querying multiple databases in a single transaction. B. What is the limit to the number of databases that can be queried in a single transaction? C. Describe the process for generating identification numbers for calls for service, incidents, and cases. Are these numbers part of a single, chronological list, or do they follow different numbering sequences? 1. Are incident numbers the same as case numbers? 2. Is any year-end maintenance required to update case numbers to the new year? 3. Does every Consortium agency call or incident receive a unique number? If not, please explain. 4. The Consortium currently uses incident numbers for all CAD calls for service but only assigns case numbers to incidents resulting in a police report. Describe the proposed approach to adding case numbers to closed incidents. Would CAD and Mobile users have the ability to create multiple case numbers for a single incident (e.g., police report and warrant request)? 5. The Consortium intends to standardize the report number format across the various agencies, however, if agencies require different report number formats, describe how this can be accomplished. D. The Consortium expects the future System to maintain compliance with both federal and state -mandated changes. Describe the process by which the Proposer will ensure that the software currently meets and will continually meet evolving requirements. 24 E. Describe theSystem s ability to work with tablet and smartphone devices. Specifically: 1. What type of hardware is supported (e.g., Apple, Android, Windows products)? 2. What type of operating systems are supported (e.g., iOS, Android, Windows, etc.) 3. How do these devices access the application (e.g., web -based, app downloaded from an app store)? 4. Describe the level of functionality available for tablet and smartphone devices. F. Describe all supported peripheral device types such as in -car printers, driver S license readers (magstripe, 2D barcode), biometric identification, and any other devices that interact with the System. G. Describe how the System supports multiple Active Directory Tenants in various Consortium domains. What is the Proposer's recommended approach? H. Describe how the System supports a mix of Azure Active Directory and on -premise Active Directory. I. Provide future -state roadmaps of upcoming functionality and features on the 1-3 year horizon. 2.13 CAD/MOBILE The applications within this proposed system must be fully integrated and meet all the minimum technical, functional, and performance requirements stated within the attachments. A. Describe the options available for users of the CAD system to access CAD with no local client installation specifically. 1. What web browsers are supported? 2. What information can mobile devices (e.g., smartphones, iPads) access? 3. Is the foitiiat/display layout configurable (e.g., portrait or landscape, "zoom in" capable, display fields, "buttons," and pages)? Please explain. 4. What historical CAD information can be queried from the mobile device? 5. Are separate licenses required for mobile access? If so, please describe. B. Which databases can be queried directly from CAD (e.g., RMS, interfaced systems)? C. Can CAD query returns be redacted through a native system tool to prevent confidential, sensitive information from being disclosed when responding to a public information request? 25 D. Describe how historical information associated with a CAD location can be displayed on real-time maps (e.g., address, owner resident, preplans, gate codes, floorplans). Describe how historical data related to maps are stored. E. Explain how the System displays historical officer safety information on the map? For example, an officer responds to a call at a mobile home park. How does the System show hazards and warnings for surrounding locations? F. Information sharing and officer safety considerations are paramount for the Consortium. Describe how the System supports Consortium agencies viewing units, resources, and calls for service from CAD and Mobile and the ability to assign resources to all law enforcement incidents in the System. G. Does the solution provide any notifications or alerts when a GPS signal has not been received after a certain interval, such as time elapsed? H. Does the system(�support automatic unit status updates via AVL (e.g., en route, on -scene)? If so, can the Consortium configure unique status update rules? I. Are user -defined dashboards available in the mobile environment (e.g., to receive an at -a - glance indication of recent activity)? If so, please describe. J. Describe how the mobile dispatching and RMS systems work in an environment if wireless connectivity is unavailable. 1. Does work in progress automatically save? 2. How can a deputy officer start a report? 3. Will the System automatically transfer a report when connectivity is re-established? K. Describe the difference between the RMS functionality on a desktop compared to a mobile device. L. Describe how the CAD and Mobile clients query the registered owner's driver's license after executing a license plate query. M. The Consortium expects the Mobile client to interact with the operator, similar to a smart assistant. Describe how the Mobile client communicates with the operator for the following. i 1. When the operator queries a drivers license or vehicle license plate. 2. How the Mobile client alerts the operator of "Hot Files," including stolen vehicles, wanted subjects, and expired or suspended driver's licenses. 3. When the Mobile client receives a new message from a CAD workstation or other Mobile clients. 26 4. When the Mobile client receives a query response. 5. When the operator is assigned to a call. 6. When the operator receives a call update. N. Describe how officer(safety information (e.g., Caution Notes for locations, typically embedded within a CAD Database, and Alerts" for persons, typically embedded within an Taker, Database) may be consolidated and presented to a Call I aker, Dispatcher, or Mobile user based upon either event location or subject's name. 2.14 RMS The applications within this proposed system must be fully integrated and meet all the minimum technical and functional requirements stated within the attachments. A. Describe how the RMS is scalable to allow the use or creation of new data fields that are required after implementation. How is data validation applied to these fields? B. Describe the case management workflow from CAD call to RMS report disposition. This should include report creation, assignment, approval, supplements, updates, additional approvals, and closure. C. Describe how the RMS documents the collection, submission, management, auditing, and tracking of property and evidence. D. Describe how the System audits actions taken in the System for security compliance. E. Describe how the System manages intelligence information, including. 1. How the System restricts user access to intelligence files. 2. How propriety records and information is protected from unauthorized access within the system and logs unauthorized access attempts. 3. How System Administrators' access to classified or privileged information within multi -agency installations is limited. 4. How partitions and controls have been configured in previous system deployments ensures only authorized persons can access restricted information. 5. How the identities of Confidential Informants are protected within the System. 6. How the System classifies information (e.g., tip, intelligence submission, intelligence file). 7. How the System manages retention, review, validation, and purging of records. 27 8. How the System provides alerts to the case agent to review a record scheduled to purge. 9. How the System complies with Federal (28 CRF Part 23) and Florida State Statute 119.01. F. How is historic information maintained and tracked when master index records are modified (e.g., updated address) and/or merged? G. How does the System prevent users from entering duplicate master records? If duplicate master records are entered, describe the process by which they are identified and ultimately consolidated? H. How are alarms and ordinance violations tracked within the System? Does the system support an escalating cost formula based on the number of violations that have occurred? I. How would the False Alarm Billing vendor be made aware of False Alarm information originating in CAD in the proposed system? J. How are incident reports assigned to individuals in the RMS application? K. How does the CAD/Mobile/RMS solution identify when a report must be written? Is this configurable at the agency level? L. Can the System generate reports of outstanding and missing reports as needed? If so, describe the process. M. Can Records develop a report that notes what reports are outstanding across the agency? Can this report be filtered to show a specific individual or beat? Please describe. N. Describe how the System restricts sensitive reports from unauthorized users and agencies? 0. Describe the process for submitting FIBRS/N IBRS data to the State of Florida to include the validation process for FIBRS and alerts to fields containing errors. P. Describe any experience working with Crime Reports.com, LexisNexis, or other third -party crime analysis applications. Q. Does the System have integrated tools to redact reports? If so, please describe. 2.15 INTERFACES AND INTEGRATION A. Describe the Proposer's specific experience with the interfaces listed in Attachment A — System Requirements Survey. B. Describe the proposed approach to application integration. The Consortium standard is for APIs or REST/Web services. 28 C. How is the proposed solution extensible, allowing for future changes? D. Does the System incorporate open data sharing models and standards such as the Global Justice XML Data Model (GJXDM) or the National Information Exchange Model (NIEM)? If so, what version numbers? E. The Consortium anticipates desiring interfaces to new systems and applications as technology develops and needs change over time. How can data stored in the System be made accessible to external systems in a cost-effective manner? F. Will vendor engagement be required to develop future interfaces/extracts? If so, explain the process. G. Describe how the Consortium can use APIs to extract data from the System. What data can be extracted? H. Describe how the System supports PowerBI. I. The Consortium collects and saves digital media from a number of external sources. The Consortium desires to store this media in the future System. 1. What file types can be natively saved and supported in the System? 2. What file types can be natively viewed and supported in the System? 3. Is the Consortium able to limit the types of digital media files that are allowed into the System to a subset of those file types that are supported? 4. Can the System convert digital video media to a standardized video format? If so, describe the process for file conversion. If not, is an alternative approach recommended to enable viewing video content saved in non-standard, unsupported file types. 2.16 GEOGRAPHIC INFORMATION SYSTEMS A. Describe the methodology for ingesting, validating, correlating, using, storing, and displaying location data and information, respectively, throughout the proposed solution. B. Describe the mapping and situational awareness solution to be available on each client CADterminal, including dispatching terminals and mobile clients available to field officers. C. Describe features that can be displayed across the CAD/RMS/Mobile environments. For example, floorplans, gate codes, caution notes, alerts, etc. D. Does the proposed solution require pre -loading of geospatial data and maps? If so, please detail the process of uploading, updating, and distributing such assets across all clients, desktop and mobile. 29 E. The Consortium's basemap layers are managed separately through each entity's organization. The Consortium desires to centralize enterprise GIS management. 1. How would the proposed system use geodata, maps, and geospatial functionality available through theConsortium S Enterprise I 2. Conversely, how would the proposed system pass location information to the Consortium'S Enterprise GIS? 3. Is a local copy of the GIS data and maps required for the client mapping software? If so, please describe the format in which such assets are to be locally stored, whether or not the user could make changes, and the update and synchronization processes. 4. Does the proposed system utilize OGC (Open Geospatial Consortium) Standard Web Services (e.g., WMS — Web Map Services, WFS - Web Feature Services, etc.), and/or RESTfu1 APIs, or does it depend on a special file format such as a "geofile" or the ESRI shapefile? 5. If the System requires a specific file format, are RMS, CAD, and Mobile able to share the same file, or will they need separate files? 6. If the solution requires a separate RMS file for GIS data, describe how the RMS application ensures RMS address verification consistent with addresses in the existing CAD file. 7. Describe the software and administration workflows required to create, update, and maintain the necessary GIS data, e.g., a Common Places dataset.. 8. Are there a maximum number of layers supported within the GIS data? If so, how many? 9. Is there a maximum data size supported for individual layers for the entire layer? If so, what size? 2.17 ANALYTICS The Consortium believes that responsible data analysis is an integral part of investigations, reducing crime, and responding to increasing security threats. It is imperative for the Consortium to collaborate and share information taking a proactive approach to crime and threats. A. Describe the System's ability to analyze and show crime patterns. B. Describe how users are able to use the `'ystem s map to plot, filter, and view crime data on an ESRI-based map. C. If applicable, describe how the System uses machine -learning (Al) with analytics. 30 D. Describe how the System can allow analysts to use cross -jurisdictional data for their analysis. E. Describe how the System's analytics can help staff identify crime patterns and develop responses for the targeted areas. F. Describe how data can be extracted from the RMS to be used on public -facing crime maps or in third -party analytic tools? G. Describe how the System can provide analytical information and updates to mobile devices, field units, and other jurisdictions (e.g., dashboards). H. Describe how the System allows users to create individual and custom reports. I. Describe how the System manages. 1. Crime Intelligence Analysis 2. Tactical Crime Analysis 3. Strategic Crime Analysis 4. Administrative Crime Analysis 2.18 DATA CONVERSION/MIGRATION The Largo Police Department currently uses CentralSquare's OneSolution for CAD/RMS. The Largo Police Department wants to convert legacy CAD/RMS data into the proposed System, or is seeking recommendations from a third party for storing and searching legacy data. There are over 1,020,738 CAD records, averaging 70,000 per year, contained in databases approximately 339 GB. A. Provide an explanation of the proposed data conversion process or third -party recommendation. B. Describe how Consortium personnel would access the historical data. C. Provide a separate line item cost, if applicable, for this data conversion. The St. Petersburg Police Department wants to import Property and Evidence data only. A. Describe how the Proposer will import Property and Evidence data from the Hexagon (Intergraph I LEADS) RMS into the new system. There are approximately 135,500 items in the current system. B. Describe how Consortium personnel would access the historical data. C. Provide a separate line item cost, if applicable, for this data conversion. 31 2.19 SYSTEM TESTING AND ACCEPTANCE A. The Consortium requires a review process to verify the Proposer's responses to all of the functional requirements and to confirm that the proposed software meets defined user requirements prior to commencing software implementation. Describe the proposed approach to confirming requirements, determining modifications necessary to meet the Consortium's specifications, and then addressing those modifications. B. Provide a comprehensive Acceptance Test Plan that incorporates these requirements at each Consortium member location. The Consortium will consider as non -responsive any vendor that does not provide an Acceptance Test Plan, or at a minimum, a sample of the plan that illustrates the process and parameters underlying its test approach, including, but not Iimited to. 1. How each of the functional specifications in the RFP will be tracked, documented, and tested prior to System Application Component Acceptance and Final Acceptance 2. How interfaces will be tested. 3. How System reliability will be tested. 4. How System performance and speed will be tested. 5. How the integration of System and System Components will be verified. 6. What are the remediation procedures for failed tests and found errors? 7. Detail the processes and actions that will be taken if system testing reveals a failure in meeting the minimum technical or functional requirements or requirements as specified within the SOW. 8. The delineation of testing tasks between the Consortium and Proposer personnel. 2.20 OBJECTIVES A. I r„ plernantation Project Plan The Proposer shall provide the Consortium an actual implementation schedule and actual deliverable schedule from the most recent comparable project to include verifiable initial milestones and actual completion dates. The Proposer shall provide the Consortium with a detailed Implementation Project Plan that, at a minimum, includes the following components: 1. Project Background: This section includes a description of the project background. 2. Project Objectives: This section includes overall project objectives. 32 3. Project Deliverables and Milestones. This section includes a list of deliverables and milestones of the project. With each deliverable or milestone, this section shall describe exactly what will be provided to meet the needs of the Consortium and how it will be achieved. 4. Project Schedule (MS Project): This section of the Project Plan shall identify the dates associated with deliverables and milestones of the Project Plan. In addition, the Project Plan shall reflect project predecessors, successors, and dependencies. 5. Project Assumptions and Assumed Responsibilities: This section shall include a list of all the presumptions(�and assumed responsibilities regarding the vendor, project, and the Consortium. 6. Project Management Processes. a) b) c) d) e) Resource Management. This section of the Project Plan describes the Consortium resources, vendor resources, overall project team structure, and organizational chart. Each role shall be identified for the vendor and any subcontractors, as well as the Consortium staff. Also, include a description of the responsibilities related to the identified project role as well as the communication process for each party. Scope Management: This section of the Project Plan should describe the approach the vendor will use in order to manage project scope and the process used to request changes to the project scope. It is the desire to use the proposed CAD/RMS solution with the necessary configuration and customization to meet the needs of the Consortium and user agencies. Any changes must be reviewed and approved by the Consortium. Schedule Management: This section of the Project Plan shall describe the approach the vendor will use in order to manage the project schedule and the The used to submit requested changes to the schedule. I he vendor must ensure that the project schedule is kept current and report any potential revisions to the timeframe for projected milestones to the Consortium. Risk Management: This section of the Project Plan shall describe the approach the vendor will use to document existing project risks, report them to the team, and provide recommendations for mitigating the risk. Quality Management: This section of the Project Plan shall describe the vendor s approach to assure that all written deliverables have been properly vetted for quality, accuracy, and functionality before being submitted to the Consortium. 7. Detailed Methodology for Implementing Third -party Software: Methodology shall include an estimated timeframe, overview of phases and milestones, presumptions, and assumed responsibilities. 8. Changes to the Project in terms of Project Schedule, Assumptions, Vendor Team Roles, Responsibilities, Resources, Scope, Overall Plan, and Methodology shall be first reviewed and approved by the Consortium. 33 B. Iran p lementation and Testing Methodology C. Business process workflows, data conversion, and training have the potential to pose the highest level of risk to the Consortium's implementation project. As part of theR.F.P. response, the vendor shall provide a description of its proposed implementation methodology covering these particular aspects of the project. Describe methodologies for multiagency deployment. Project Team Organizational Structure As part of the R.F.P. response, the vendor must specify all personnel required for each of the implementation stages depicted in a Project Team Structure Diagram. The diagram shall include (at a minimum) the following Key Personnel: Engagement Manager, Project Manager, Implementation functional area leads, and technical staff. Resumes are required for current and future Key Personnel project team members. Any change of Key Personnel supplied � by the successful vendor after contract approval must be reviewed and approved by the Consortium. The Proposer will make reasonable accommodations to ensure the Project Manager will be assigned for the duration of the project. 1. Vendor Team Roles and Responsibilities As part of the R.F.P. response, the vendor shall provide a detailed explanation of the roles and responsibilities the vendor anticipates providing to address the ' R.F.P. Th e s requirements in this he vendor shall clearly indicate which vendor staff member (either by name or position team) will be responsible for the overall project and for each key role responsibility within the project implementation plan. It is the Consortium's expectation that the vendor provides project management services related to the vendor's implementation approach. This will include, but not be limited to, the development and maintenance of the deliverables, training, data conversion, and testing services, and serving as a single point of contact for the Consortium's project manager. As such, the vendor's project manager must be an expert user of the software program and have significant experience managing a project of this size. The project manager must also have the authority necessary to make decisions relating to key project tasks in order to keep the project moving forward. Vendors should keep this approach in mind as they develop their cost and project approach. It is expected that the vendor will recommend and offer additional services such as business analysis or organizational change management if identified as necessary for the successful completion of the project. The vendor shall have past experience implementing large-scale projects and shall have worked within a law enforcement or government and public sector environment. The vendor shall identify the total number of hours that members of their team will be involved in each phase of the project and estimate how many hours on -site for each phase. The response will provide hourly estimates by functional area for seven (7) a) phases of the project, including: Project kickoff (review SOW, project readiness assessment, technical review, process mapping, equipment hardware review, upgrade schedule, etc.) 34 b) c) d) e) f) g) Requirements and Design; Configuration and Setup; Property and Evidence Data Conversion / Migration, mplementation; Testing, and Training and Project Closure. 2. Consortium Team Roles and Responsibilities: As part of the R.F.P. response, the vendor shall provide an anticipated representation of the resource requirements that will be expected of Consortium and user agencies during this project. The Consortium will provide the vendor with workspace, VPN access, and troubleshooting services for connectivity to the existing Consortium networks. The vendor shall identify the staffing requirements and the total number of expected hours that members of the Consortium team will be involved in each phase of the project. The response will provide hourly estimates by functional area for the seven (7) phases of the project as listed in section C (1) above. 2.21 SCOPE OF SERVICES A. Software Customization Plan While the Consortium intends to utilize the vendor system's existing capabilities and embedded best -practice business processes, we recognize that some critical work processes may require some software customization or atypical system configuration. As part of this project plan, the vendor will provide a detailed software customization plan that includes anticipated customizations and their impact on the overall project schedule, budget, and final success. This software customization plan shall describe the process that Consortium and the i vendor will engage in for accepting the software modifications. B. Busimess Process VVor kflows The Consortium requires the vendor to identify the business process workflows that are included with the system implementation. To ensure the successful implementation of the system, an assessment of the Consortium business processes "as -is" and future state is expected. The vendor should describe how various Consortium business processes are to be analyzed and implemented in the proposed system. Changes in businesspprocesses are expected to be incorporated into Section G. Organizational Change Management plans (see below). C. Report Development Provide a complete list of all "canned" reports available, and describe capabilities of individual agencies to search all data fields and create custom reports within the System as well as export data for agency analytics, ad hoc reports, data sharing, and public records requests. 35 D. Quality Assurance & Testing Plan The vendor shall develop a Quality Assurance Plan that describes how the desired levels of quality and software testing will be achieved throughout implementation. The Plan should identify resources from both the vendor and Consortium who will be involved in the processes of quality planning, quality assurance, and quality control regarding data, configuration, and software testing. The Proposer shall document any and all deficiencies identified during testing and the manner in which they will be resolved and retested. The system will not be accepted until all deficiencies have been resolved and final acceptance testing has been approved by Consortium. E. Organizational Change Management lanagement Vendors shall provide a description of their change control methodology during implementation and post -implementation. The change management plan should address. 1. Overall description of the change management strategy during implementation and post -implementation. 2. Process for identifying change management issues throughout the engagement. 3. Anticipated roles and responsibilities of the Consortium team, the software firm, and the implementation firm. 4. Strategy for communicating business process changes. 5. Strategy for business process re -engineering. 6. Tools for facilitating the development of business process maps based upon best practices. 7. (Strategy for mitigating change management issues. 8. Communication plan for milestones, schedule adherence, issues, etc. 9. Optimum team design and governance design for a successful change management program. 10. Strategy and process regarding any change of a Key Personnel after contract approval. 11. All associated estimated costs for any change in proposed methodologies. H. Budget and Staffing Plan Based on vendor experience with similar organizations, explain the extent to which the Consortium should include a contingency factor for additional work effort in its project budget and staffing plan. 36 I. Interfaces J. The vendor shall provide a list of 3rd party vendors used by the Consortium that already interface with their system. Hardware, Equipment, and Technical Architecture The vendor shall provide requirements regarding sizing and performance of all hardware needed to implement the complete solution. The vendor shall be responsible for the satisfactory performance of the software included in the proposal. The vendor shall provide an architecture proposal document that describes the completed System topology and various systems interactions (preferably a Visio diagram). The Consortium prefers to avoid pursuing unique data definitions and proprietary systems wherever possible. The Consortium would like the System to have interoperability and ability with equipment available from other vendors, thus ensuring the proposals provide a maximum choice of equipment. Refer/Respond to Attachment A — System Requirements Survey. K. Pre- and Post' Impiementation Support Plan The vendor must provide a Pre- and Post -implementation Plan that describes the approach to software support during the implementation and after go -live. Vendors shall describe what level of support is available under their proposed fee structure. If varying levels of support are available, this section of the vendor's response should clarify these potential services and highlight the level of support that has been proposed. The plan shall address: 1. Pre -implementation support (e.g., number of months of on -site support to include the Proposer's Business Analysts and trainers). 2. Transition plan from project to ongoing operational support. 3. Organizational change management. 4. Post -implementation support (e.g., number of months of on -site support after go - live). 5. Telephone support (e.g., include toll -free support hotline, hours of operation, availability of hotline twenty-four (24) hours per day and seven (7) days per week). 6. Special plans defining "levels" of customer support (e.g., gold, silver, etc.). Define what level of support is being proposed. 7. Response time for, and definition of, various types (levels of severity) of problems reported to the support network (e.g., critical issue response time). 8. The delivery method of future upgrades and product enhancements, including historical frequency of upgrades by module. 9. Product road maps detailing anticipated changes to the system over the next 3-5 years. 10. Availability of user groups and their geographic areas. 37 11. Problem reporting and resolution procedures, including a timeline for resolution. 12. Bug fixes and patches release frequency. 13. Additional consultants or personnel available for the proposed support level. 14. Other support (e.g., on -site, remote dial -in, website access to patches, fixes, and knowledge base). 15. If there is to be a separate maintenance contract, the vendor should attach an example of such a contract, if applicable. Training Plan It is the Consortium's intention that the selected vendor will coordinate the in -person training of all participating agency personnel in the use of their application and that satisfactory implementation of an approved training plan will be a key component of this project s deliverables. The vendor must provide a detailed plan for training. This training plan must include the following. 1. The role and responsibility of the software and/or implementation vendor in the design and implementation of the trainingn�plan (e.g., development of customized training materials, delivering training to Consortium end -users) 2. A detailed organizational change management plan to help members in the Consortium organizations adapt to the new System. 3. The role and responsibility of Consortium staff in the design and implementation of the training plan. 4. Overview of proposed training plan strategy, including options for on -site or off - site training services for the core project team, end -users, and technology personnel. 5. The proposed training schedule for Consortium personnel of various user and interaction levels to include shiftwork. 6. Descriptions of classes courses proposed in the training plan - the vendor should specify the unit of measure for its training, e.g., units, classes, days, etc., and define the number of hours associated with these units of measure. The vendor must be very clear about exactly what training courses are included in the cost of the proposal. 7. The knowledge transfer strategy proposed by the software and/or implementation vendor to prepare Consortium staff to maintain the system after it is placed into production. 8. A detailed description of system documentation and resources that will be included as part of the implementation by the vendor including, but not limited to, detailed system user manuals, "Quick Reference" guides, Online support, Help -Desk support, Entity Relationship Diagrams, user group community resources, and others as available. 38 9. The ongoing training support post -implementation provided, should the software be M. upgraded and continue to change (online documentation, manuals available, etc.). Third -Party Products The vendor shall explicitly state the name of any third -party products that are part of the proposed solution for Consortium. For each third -party product, there shall be a statement about whether the vendor contract will encompass the third -party product and/or whether the Consortium will have to contract on its own for the product. The successful vendor shall be responsible for the implementation, integration, and satisfactory performance of any third -party software included in the vendor's proposal. The proposal must describe any products, features, or other value-added components recommended for use with the proposed system that has not been specifically requested in this R.F.P. The vendor shall also provide proof that it has access to the third -party software source code (owned or in escrow) and that the vendor has the ability to provide long-term support for the third - party software components of its system. Consideration of these product features(�or other value-added components will be given where they may be of value to the Consortium. Vendors must include all costs of any third -party products, including the software license cost, maintenance, implementation, integration, training cost, estimated hardware costs, and any other related costs (operating system, database, layered products, etc.), including third -party software in the total cost of this proposal. Vendors must also include how many times they have integrated with the respective third -party products. The vendor must still meet all necessary Project Plan schedules, requirements and abide by all of the Consortium's R.F.P. requirements, regardless of whether they utilize a third -party product. N. Contract Type and Pricing 1. 2. The proposed contract is for a fixed price. The Consortium will not consider time and materials pricing. The vendor shall provide firm and fixed pricing based on the functionality described. For each item, indicate if the cost is one-time, annual, or other. 3. The vendor shall provide price information for each separate component of the proposed solution, as well as the costs of any modifications necessary to fully comply with the R.F.P. specifications. 4. In the event the product or service is provided at no additional cost, the item should be noted as no charge or wording to that effect. 5. In the event the product or service is not being included in the vendor's proposal, the item should be noted as not included. 6. Vendors shall provide all pricing alternatives in their cost sheets, including hourly rates for additional support, training, and API development. 7. Vendors shall describe how Change Orders will be priced and managed. 8. Vendors shall provide prices in U.S. dollars. 39 9. Vendors shall make clear the rationale and basis of calculation for all fees. 10. Vendors shall show separate subtotals for the required elements of the proposed solution and for any layers of optional elements. O. Software License Costs Software license costs will include all costs related to licensing the software application and include third -party software license fees where applicable. In presenting software license fees, the vendor shall. 1. Explain all factors that could affect licensing fees. 2. Make clear what type of license is offered for each price (named user, concurrent user, installed copies, processor -based, etc.). 3. Indicate which product versions, operating platform(s), are included for each price. 4. IIndicate whether a product is for "server" or "client," as applicable. 5. Make clear the extent of any implementation services that are included in the license fees (installation, configuration, training, etc.). To the extent possible, the vendor shall show any applicable discounts separately from the prices for products and services. The Consortium requests that the vendor provide separate prices for each functional area module in the proposed solution. In addition, the Consortium expects software maintenance costs will not increase in the first five (5) years upon live operation. P. I r„ p lamentation Service Costs Implementation service costs include all costs related to implementation, configuration, data conversion, customization, and training. Typically, implementation service costs are provided as "not to exceed" estimates, and the Consortium will be charged for services as incurred. The Consortium will provide payments associated with software license fees and implementation on a milestone basis; for instance, Project Kick -Off and Project Plan Approval, Interface Development Completion, and Acceptance. following. Please note the 1. The Consortium will not consider time and materials pricing. Vendors shall provide firm and fixed pricing based on the functionality described. For each item, indicate if the cost is one-time, annual, or other. 2. The vendor shall provide price information, including details on the number of hours used and miscellaneous costs associated with each separate component of the proposed solution, as well as the costs of any modifications. 3. In the event the product or service is provided at no additional cost, the item should be noted as no charge. 4. In the event the product or service is not being included in the proposal, the item should be noted as not included. 40 5. The vendor shall make clear the basis of calculation for all fees. All travel, printing and other expense costs must be included in the vendor s fixed price cost. The Consortium will not make a separate payment for reimbursable expenses. Per Force IVlajeure, the Consortium shall not be liable for additional travel costs incurred due to any reason outside Consortium's control. Q. Annual Maintenance laintenance Hosts Annual maintenance costs include the annual maintenance and support fees for the application environment. For example, the�+annual maintenance fees associated with a particular module will be paid upon the Consortium's acceptance of the project phase The with that particular module. I he Consortium will not pay maintenance fees on functional areas until sign -off has beenprovidedto approve live operation for one (1) The after final System acceptance. I he Consortium expects software maintenance costs will not increase in the first five (5) years upon live operation. The Consortium expects to work with the selected vendor to methodically implement the System across all Consortium entities closely. multi -agency staggered deployment. R. Source Code S. Describe the fee schedule as it relates to Selected vendors shall place source code for the software modules licensed by the Consortium in escrow with an independent(�third-party (with whom a separate escrow agreement will be entered into by the Consortium at no additional cost). The sources�code shall be kept current with the releases version of the software in use at the Consortium agencies. The source code shall revert to the Consortium for the Consortium(�s use if the vendor files for bankruptcy or protection from creditors in a court of law. The Consortium shall then have full rights to use source code for any purposes other than resale. Within thirty (30) calendar days of the vendor going out of business or no longer supporting the software being licensed, the vendor shall provide appropriate source code to the Consortium. The same appliesifthe vendor is merged or acquired and the software is no longer supported. Once the Consortium obtains the source code, it shall be a perpetual license, and there shall not be any additional fees due, even if additional licenses are deployed. Client References & On -Site Visits The vendor must provide at least five (5), but not more than ten (10) references meeting the following criteria: 1. At least three (3) references should be for systems installed within the last three (3) years. 2. At least two (2) references should be for systems installed more than three (3) years ago. 3. At least three (3) references should include installations of similar configuration proposed for the Consortium. 41 4. At least three (3) references should reflect similar Consortium population and call for service levels. The references should include, at a minimum, the following information. 1. Facility Name, Address, and Owner of Project; 2. Contact person at a facility that is familiar with the system and its operation, including their title, phone number, and email address; 3. Details of the Project type, size, and operations, 4. Initiation and Completion dates of the Project; 5. Length of contract, 6. Summary of unanticipated delays or obstacles that were encountered. In addition, the Consortium requests a listing of all law enforcement clients. If possible, at least one (1) of these references should be a vendor -hosted solution. T. Exceptions and Deviations If the vendor finds it impossible or impractical to adhere to any portion of these specifications and all attachments, it shall be so stated in its proposal, with all deviations grouped together in a section entitled, "exceptions/deviations from proposal requirements" and submitted with the R.F.P. Response Form. This section will be all- inclusive and will contain a definition statement of each and every objection or deviation with adherence to specific R.F.P. sections. Objections or deviations expressed only in other parts of the proposal, either directly or by implication, will not be accepted as deviations, and the vendor, in submitting a proposal, will accept this stipulation without recourse. 42 2_3 R.F.P. SCHEDULE Distribution of Request for Proposals May 28, 2021 Written Questions Due from Vendors June 14, 2021 Response to Questions Posted July 6, 2021 Non -Mandatory Pre -Proposal Conference July 15, 2021 Additional Questions as result of Conference Due July 19, 2021 Response to Questions Posted August 2, 2021 Proposal Due August 16, 2021 On -Site Demonstrations Starting the week of Oct 11, 2021 Off -Site or Virtual -Site Visits (current customer sites) Starting the week of Nov 15, 2021 Vendor Selection Starting the week of Dec 20, 2021 Notice of Award January 10, 2022 Contract Negotiations January 17, 2022 Contract Execution Date March 7, 2022 2.4 AWARD AND EVALUATION A. EVALUATION COMMITTEE Subject to the rights and limitations set forth above, qualifying proposals will be reviewed by an Evaluation Committee. The Evaluation Committee will evaluate whether the proposal conforms to the R.F.P., which proposal appears to best meet the needs of the Consortium as reflected by the requirements of this R.F.P., and evaluation criteria and scoring stated below. Further interviews/discussions with vendors who have been identified as potential candidates for contract awards may be conducted. The purpose of the interviews/discussions will be to ensure full understanding of, and responsiveness to, the project requirements. B. EVALUATION CRITERIA This section specifies the criteria that will be used by the Consortium to evaluate and score responsive and qualified proposals. Vendors shall include sufficient information to allow the Consortium to thoroughly evaluate and score their proposals. The following criteria will be used to evaluate R.F.P. responses and to make a recommendation for award to the Pinellas County Sheriff: 43 Evaluation Criteria Weight Vendor Related Information 15% Technology Requirements 15% Implementation Services 20% Functional Requirements 40% Pricing, Cost Elements, and Total Five -Year Cost 10% Total: 100% C. POST -PROPOSAL DISCUSSIONS WITH VENDORS The Consortium reserves the right to conduct post -closing discussions with any vendor who has a realistic possibility of a contract award including, but not limited to, request for additional information or walk-throughs of similar projects for which the vendor has designed and provided services, competitive negotiations, and best and final offers. 2_5 PROPOSAL FORMAT To enable the Evaluation Committee to fairly evaluate each proposal, the vendor shall use the following proposal format. Please include the following information with your proposal in the order as listed: A. Transmittal Letter: The transmittal letter should be brief and must be signed by a person authorized to commit the organization to perform the work specified in the R.F.P. It shall identify all materials and enclosures that comprise the proposal. The letter must also i identify the individual who will serve as the vendors representative in all matters relating to this R.F.P. B. Table of Contents. The vendor shall provide a table of contents with corresponding page C. numbers relating to each section of its proposal. The vendor shall also provide a schedule of appendices, if applicable. The proposal shall be in an electronically searchable format Vendor Qualifications. The vendor shall outline the company's background, including a i brief history of the vendor and a description of the vendors present organizational structure, describe how you are investing in your current and future product lines, and describe the company s research and development capabilities. The vendor shall provide information concerning the personnel who will be assigned to this contract. This section must include the experience, education, and professional qualifications each employee has in developing and implementing training programs specifically for the System. The vendor shall provide a list of subcontractors to be used in the performance of the work requested. Along with the above, vendor shall provide the following in the proposal response: • System Customer retention for 2018, 2019, and 2020; • Number of organizations that have uninstalled the System in part, or total; 44 • Total full-time employees in the company for 2018, 2019, and 2020. • Total full-time employees employed in the division of the company that includes the System for the same years. • Total full-time employees on the software development team that support the version of the software the Consortium will implement. • Total full-time trainers and implementors. D. Project Objectives and Scope of Services - The vendor shall provide a fully detailed and complete plan of how these processes shall be accomplished to include. Implementation Project Plan, Implementation Methodology, Project Team Organization Structure, Software Customization Plan, Data Conversion Plan, Business Process Workflows, Report Development, Implementation Testing Plan, Quality Assurance & Testing Plan, Organizational Change Management, Budget and Staffing Plan, Interfaces, Hardware, Equipment and Technical Architecture, �IT Pre- and Post -Implementation Support Plan, Training Plan, Third -Party Products, and Application Hosting. This section shall include every detail as required in the Specifications section. E. Submittals: Vendors shall include specification sheets on all equipment proposed, as well as a solution overview document and System template document screenshots that clearly define all of the functions of the system as they relate and adhere to the system specifications and infrastructure specifications provided within this RFP. This section shall also include the required RFP Surveys (Attachment A- System Requirements Survey). Submittals shall be in an electronically searchable format. F. Contractual Obligations: Describe current or anticipated contractual obligations that have been awarded, which may coincide with the terms of this contract. G. Litigation, Claims, and Regulatory Actions: Vendor must indicate if they have had any Litigation, Claims, or Regulatory Action. Vendor shall provide detailed information relating to any circumstances and status. Any omission within this item may result in disqualification from the bid process. H. Proposal Pricing: The vendor proposal pricing section must include all costs related to the following: price information for each separate component of the proposed solution, as well as the costs of any modifications necessary, software license costs, implementation service costs, annual maintenance costs, and security escort costs. The pricing schedule shall include every detail as required in the Specifications section. �. Financial Statements: Provide audited financial statements for the most recent two (2) J. year period. If the vendor is a wholly -owned subsidiary of another company or corporation and does not possess audited financial statements, unaudited financial statements for the subsidiary for a two (2) year period must be submitted as supplemental information to the i company s financial statements in order to meet this requirement. These documents should be affixed to the "original" bound proposal only, submitted by the vendor. R.F.P. Response Form: To include all Remarks and Exceptions to Proposal (Section D). K. Federal Debarred List Certification: Certification Regarding Debarment, Suspension, Proposed Debarment, and Other Responsibility Matters (Section E). 45 R.F.P. 21-02 SECTION C INSURANCE AND INDEMNIFICATION REQUIREMENTS MINIMUM INSURANCE REQUIREMENTS FOR LOW RISK CONTRACTS A. Prior to the time Contractor(�is entitled to commence any part of the project, work or services under this Contract, Contractor shall procure, pay for and maintain at least the following insurance coverage's and limits. Said insurance shall be evidenced by delivery to the Pinellas County Sheriff's Office of (1) certificates of insurance executed by the insurers listing coverages and limits, expiration dates and terms of policies and all endorsements whether or not required by the PCSO, and listing all carriers issuing said policies, and (2) upon request a certified copy of each policy, including all endorsements. The insurance requirements shall remain in effect throughout the term of this Contract. In addition, the PCSOreserves the right to request physical evidence of this coverage by requesting the policy declaration page. 1. 2. Workers Compensation in at least the limits as required by law, Employers Liability Insurance of not less than $100,000 for each accident. Comprehensive General Liability Insurance including, but not limited to, Independent, Contractor, Contractual, Premises/Operations, Products/Completed Operation and Personal Injury covering the liability assumed under indemnification provisions of this Contract, with limits of liability for personal injury and/or bodily injury, including death, of not less than $500,000, each occurrence, and property damage of not less than $100,000, each occurrence. (Combined Single Limits of not less than $500,000, each occurrence, will be acceptable unless otherwise stated). Coverage shall be on an occurrence basis, and the policy shall include Broad Form Property Damage coverage, and Fire Legal Liability of not less than $50,000 per occurrence, unless otherwise stated by exception herein. 3. Comprehensive Automobile and Truckliability covering owned, hired and non - owned vehicles with minimum limits of $300,000 each occurrence, for bodily injury including death, and property damage of not less than $100,000, each occurrence. (Combined Single Limits of not less than $300,000, each occurrence, will be acceptable unless otherwise stated). Coverage shall be on an occurrence basis, such insurance to include coverage for loading and unloading hazards. 4. Professional Liability Insurance (including Errors and Omissions) with minimum limits of $500,000 per occurrence, if occurrence form is available, or claims made form with tail coverage extending three (3) years beyond completion and acceptance of the PROJECT with proof of tail coverage to be submitted with the invoice for final payment. In lieu of "tail coverage, CONSULTANT may submit annually to the PINELLAS COUNTY SHERIFFS OFFICE a current Certificate of Insurance proving claims made insurance remains in force throughout the same three (3) year period. 5. Comprehensive — 3D, or equivalent, in the amount of at least $500,000.00 protecting assets of the Pinellas County Sheriff's Office in the form of currency, coin, checks, 46 securities and other valuables while(�in the care, custody or control of Contractor, and as provided in the terms of this Contract. B. Each insurance policy shall include the following conditions by endorsement to the policy. 1. Each policy shall require that thirty (30) days prior to expiration, cancellation, non - renewal or any material change in coverage's or limits, a notice thereof shall be given to the Sheriff's Office by certified mail to: Pinellas County Sheriffs Office Purchasing Division, P.O. Drawer 2500, Largo, Florida 33779-2500. Contractor shall also notify the Sheriff's Office, in a like manner, within twenty-four (24) hours after receipt, of any notices of expiration, cancellation, non -renewal or material change in coverage received by said Contractor from its insurer, and nothing contained herein shall absolve Contractor of this requirement to provide notice. 2. Companies issuing the insurance policy, or policies, shall have no recourse against the Sheriff for payment of premiums or assessments for any deductibles which all are at the sole responsibility and risk of Contractor. 3. The term "Sheriffs Office" or "Pinellas County Sheriff's Office" or "Sheriff' shall include all Authorities, Bureaus, Divisions, Departments and offices of the Pinellas County Sheriffs Office and individual members, employees thereof in their official capacities, and/or while acting on behalf of the Pinellas County Sheriffs Office. 4. The Pinellas County Sheriffs Office shall be endorsed to the required policy or policies as an additional insured. 5. The policy clause Other Insurance" shall not apply to any insurance coverage currently i held by County to any such future coverage, or toCounty s elf -Insured Retentions of whatever nature. II MINIMUM INSURANCE REQUIREMENTS FOR HIGH RISK CONTRACTS OVER $100,000.00 A. For selected high risk contracts over $100,000.00 aggregate value, the Pinellas County Sheriffs Office may require an insurance certificate, policy declaration page and required endorsements. These required items shall be received by the Pinellas County Sheriff's Office after formal award and prior to execution of contract. Failure to provide required insurance documentation may cause your company to forfeit award. B. There may be certain projects or services less than $100,000.00 in aggregate value that would be an exception and must be treated the same way as those services of $100,000.00 and greater i.e. services involving obvious potentially dangerous conditions. Examples of such services would be any contracts involving construction, alterations, renovations, painting, spraying, roofing, mowing, scaffolding, excavation, demolition, environmentally sensitive work and any other conditions that appears to be dangerous in nature. 47 R.F.P. 21-02 SECTION D R.F.P. RESPONSE FORM INSTRUCTIONS FOR SUBMITTING PROPOSALS The undersigned understands that this Proposal must be signed in ink and that any unsigned Proposal will be considered incomplete and subject to rejection by the Pinellas County Sheriff's Office. A. REMARKS & EXCEPTIONS TO PROPOSAL: All vendor deviations are to be grouped together in a section entitled, "exceptions/deviations from proposal requirements" and submitted with this R.F.P. Response Form as listed in Paragraph V — Exceptions and Deviations. This section must be all-inclusive and will contain a definition statement of each and every objection or deviation with adherence to specific R.F.P. sections. The undersigned certifies that any exceptions to the proposal are noted as attached. All conditions not noted thereon are as requested. The undersigned also understands that any exceptions presented after the award, may be cause for cancellation of award. B. VENDOR INFORMATION C. Vendor Name Federal Taxpayer Identification (Last 4-digits only) Address Person to Contact Regarding this Proposal Telephone Number Fax Number E-Mail Address AUTHORIZED SIGNATURE - All proposals shall be signed in ink by authorized principals of the firm. The undersigned affirms and declares: 1. That vendor has read and understands the requirements of this Request for Proposal #21-02 and, that as the vendor, will comply with all requirements, and that I am duly authorized to execute this proposal/offer document and any contract(s) and/or transactions required by award of this R.F.P.; 2. That this proposal is made without understanding, agreement or connection with any person, firm or corporation making a proposal for the same purpose, and is in all respects fair and without collusion or fraud; 48 3. That this proposal shall remain open for an evaluation period of one hundred twenty (120) calendar days following the opening of proposals. Please Print or Type: BY: TITLE: SIGNATURE: DATE: 49 R.F.P. 21-02 SECTION E FEDERAL DEBARRED LIST CERTIFICATION Certification Regarding Debarment, Suspension, Proposed Debarment, and Other Responsibility Matters (Dec 2001) (Date) Pinellas County Sheriff's Office Purchasing Division 14400 49th St. N., Door #FPW 4 Clearwater, FL 33762 In accordance with the Federal Acquisition Regulation, 52.209-5: (a) (1) The Offeror certifies, to the best of its knowledge and belief, that- (1) The Offeror and/or any of its Principals - (A) (B) (C) (check one) Are ( ) or are not ( ) presently debarred, suspended, proposed for debarment, or declared ineligible for the award of contracts by any Federal agency; (The debarred list (List of Parties Excluded from Federal Procurement and Nonprocurement Programs) is at http://epls.arnet.gov on the Web.) (check one) Have ( ) or have not ( ), within a three-year period preceding this offer, been convicted of or had a civil judgment rendered against them for: commission of fraud or a criminal offense in connection with obtaining, attempting to obtain, or performing a public (Federal, state, or local) contract or subcontract; violation of Federal or state antitrust statutes relating to the submission of offers; or commission of embezzlement, theft, forgery, bribery, falsification or destruction of records, making false statements, tax evasion, or receiving stolen property; and (check one) Are ( ) or are not ( ) presently indicted for, or otherwise criminally or civilly charged by a governmental entity with, commission of any of the offenses enumerated in paragraph (a)(1)(i)(B) of this provision. (ii) The Offeror (check one) has ( ) or has not ( ), within a three-year period preceding this offer, had one or more contracts terminated for default by any Federal agency. (2) "Principals," for the purposes of this certification, means officers; directors; owners; partners; and, persons having primary management or supervisory responsibilities within a business entity (e.g., general manager; plant manager; head of a subsidiary, division, or business segment, and similar positions). This Certification Concerns a Matter Within the Jurisdiction of an Agency of the United States and the Making of a False, Fictitious, or Fraudulent Certification May Render the Maker Subject to Prosecution Under Section 1001, Title 18, United States Code. 50 (b) The Offeror shall provide immediate written notice to the Contracting Officer if, at any time prior to contract award, the Offeror learns that its certification was erroneous when submitted or has become erroneous by reason of changed circumstances. (c) A certification that any of the items in paragraph (a) of this provision�exists will not necessarily nl result in withholding of an award under this solicitatio . I lowever,the certification will be considered in connection with a determination of the Offeror's responsibility. Failure oftheOfferor to furnish a certification or provide such additional information as requested by the Contracting Officer may render the Offeror nonresponsible. (d) Nothing contained in the foregoing shall be construed to require establishment of a system of records The order to render, in good faith, the certification required by paragraph (a) of this provision. I he knowledge and information of an Offeror is not required to exceed that which is normally possessed by a prudent person in the ordinary course of business dealings. (e) The certification in paragraph (a) of this provision is a material representation of fact upon which reliance was placed when making award. If it is later determined that the Offeror knowingly rendered an erroneous certification, in addition to other remedies available to the Government, the Contracting Officer may terminate the contract resulting from this solicitation for default. Firm Email Address Address Signature Phone Print Name Print Title Fax Federal Taxpayer ID Number 51 Below is an example of the information required on your Proposal package. You may use this as a label if you wish. PINELLAS COUNTY SHERIFF'S OFFICE PURCHASING DIVISION 14400 49`h STREET NORTH, DOOR #FPW 4 CLEARWATER FL 33762 PROPOSAL PACKAGE SUBMITTAL R.F.P. # 21-02 OPENING DATE/TIME: AUGUST 16, 2021 @ 3:00 PM EST 52 R.F.P. 21-02 ATTACHMENT A SYSTEM REQUIREMENTS SURVEY 1. Functional Requirements There is an attached Functional Requirements worksheet to collect vendor responses for the applications and/or modules required by each of the seventeen functional groupings. The intent of the worksheet is to identify the various components or functionalities of the proposed System; therefore, some of the statements listed on the form are mutually exclusive, and are not to be construed as "requirements" of the PCSO. 2. Vendor Responses The worksheet provides four (4) options for the vendor to indicate a single response to each question or statement, plus an opportunity for the vendor to provide, in narrative form, additional information, or explanation. PCSO requests that vendors indicate the single response with an " 77 X in the selected column. 3. Explanation of Options For Single Response Each of the four optional answers provided in the worksheets is defined below. The same language and colors presented below are used in the Functional Requirements worksheets. 4. Instructions For Responses Vendors may select only one option as an answer or response to each question or statement. The absence of a selection or the presence of an indication that a vendor has selected more than one option may be interpreted by the Selection Committee to mean, "No. The functional requirement is not available in this version of the proposed software.? 53 YES, included in the baseline system design. Performs the stated task, without exceptions, modifications, or required costs. YES, because of our integrated product service solution. YES, because of our integrated product service solution. We have proposed an integrated solution that will satisfy this requirement and provide the stated functionality without exceptions, modifications, or costs that have not been proposed in this response. Our solution provides a seamless integration using the product or service identified and described in the Information and/or Explanation11 section below. YES, but requires customization and cost. The functional requirement can be designed into the system based on PI.SO's specification. If there is a COST associated with this customization then state "Additional Cost" in the 11 Information and/or Explanation" section below, and show the actual cost for the customization. If there is no COST associated with this customization then state 11No Cost" in the "Information and/or Explanation" section below. NO The functional requirement is not available in this version of the proposed software. Or? The functional requirement is scheduled to be added to the baseline design within the next 12 months. Or? We have chosen to comment (or not) in the "Information and/or Explanation" section below. nformation and/or Explanation Note: Row height in the spreadsheet will be properly adjusted when <alti'Enter is inserted as hard returns. 54 Sheriff Bob Gualtieri Pinellas County Sheriff's Office „ TA Wei FolASe{,(4PwU March 10, 2022 To: All Proposers for RFP 21-02 Thank you for your participation and response to RFP 21-02 ? Computer -Aided Dispatch p & Records Management System Mobile Data Terminal. After careful analysis of all relevant information, Sheriff Gualtieri has decided to begin contract negotiations for award of these services to Hexagon. On behalf of Sheriff Gualtieri and the members of the Evaluation Committee, I want to express our sincere appreciation for the time and effort you and your staff have taken to respond to our solicitation for this project. Sincerely, Eric Vincent Eric Vincent Purchasing Manager Al HEXAGON Hexagon Response to Pinellas County, FL RFP for Computer Aided Dispatch (CAD), Records Management System (RMS) and Mobile Data Terminal RFP N. 21-02 August 16, 2021 40 HEXAGON ©2021 Intergraph Corporation by and through its Hexagon Safety, Infrastructure, and Geospatial division ("Hexagon'). Hexagon is a part of Hexagon AB. All rights reserved. Hexagon and the Hexagon logo are trademarks of Hexagon AB or its subsidiaries in the United States and in other countries. Except in accordance with applicable statutory public records laws, 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, T 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. Any commercial -off -the -shelf (COTS) product information provided by Hexagon in this RFP response, is intended 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. Except as set forth in a resulting contract, Hexagon does not commit to develop the future features, functions, and products discussed in this material. The Agency 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 unless specified in the resulting contract. A HEXAGON Hexagon 305 Intergraph Way Madison, AL 35758 p: 1.256.730.2000 h exa go n.com August 16, 2021 Pinellas County Sheriffs Office 10750 Ulmerton Rd., Largo, Florida, 33778 Re: RFP 21-02 Dispatch & Reee�d� Mat,aget„et,t Systern& Mobile Data Ter.,,inai Please accept the enclosed information on behalf of Intergraph Corporation through its Hexagon Safety, Infrastructure & Geospatial division ("Hexagon") as its response to Pinellas County, Florida, Request for Proposal 21- 02. Starting with our founding as Intergraph in Huntsville, Alabama in 1969, we have a proven history of providing the best possible technology solutions for government agencies and helping them address their biggest challenges. Hexagon has provided a detailed response with our OnCall Cloud product suite and proven track record with large multi-agency/multi-site customers including DuPage County, Illinois and El Paso County Texas, both of which serve large multi -agency environments. Hexagon is looking forward to working with Pinellas County Sheriff's Office and the Consortium to provide a single, comprehensive, reliable, proven cloud -first implementation as well as interoperability, ease of use, and data sharing with all agencies to see the total picture during day-to-day operations and in any emergency. Hexagon has responded to RFP requirements as instructed, and has enclosed 10 (ten) total hardcopies of the proposal and one digital copy of the proposal that includes the completed system requirements survey spreadsheet. If you have any questions regarding the enclosed information or require any additional information, please contact Trent D. Lowe by telephone at (772) 559-6489 or by email at Trent.lowe@hexagon.com. Sincerely, Trent D. Lowe Name: Signature: AUTHORIZED HEXAGON SIGNATURE Debra T. Huser — North Americas Finance Director 305 Intergraph Way Madison, AL 35758 fileo i • Date: Email: Debra.huser@hexagon.com Phone: (256) 730-1572 A HEXAGON Executive Su m m a ry Intergraph Corporation d/b/a Hexagon Safety, Infrastructure & Geospatial division (Hexagon) is a Delaware corporation with offices around the world in America, Europe, Asia Pacific, Canada, India and South America. Hexagon's US headquarters and the headquarters of our global Public Safety organization is located in Huntsville, Alabama. Regional Sales Manager Trent D. Lowe is the Hexagon contact for Pinellas County Sheriffs Office. His contact information is included in the letter of transmittal in this proposal. Hexagon's Understanding of Pinellas County Sheriff's Office Intent and Objectives The past several years have brought complex challenges in a scale and frequency previously unknown across America. Horriblep mass shootings at places like Pulse Nightclub in Orlando and Marjory Stoneman Douglas High School in Broward County; the urgency to mitigate a global pandemic, the effort to manage evolving public expectations for Law Enforcement —these challenges (among others) have ushered public safety professionals into an unprecedented time that shows no signs of slowing down. Moreover, the "normal challenges" continue, from disasters like hurricanes and tropical storms to the daily emergencies and incidents ranging from traffic accidents to noise complaints. This new era presents every public safety agency and community with a necessity for new and better ways to operate, to share information, and to ensure their public safety technology is resilient, redundant, and adaptable to whatever the next challenge may be. (CAD), Records Management System (RMS) and Mobile Data Terminal solution. These are never easy projects or decisions, but given where we find ourselves today this effort clearly marks a defining moment in the ability of Pinellas County to dramatically enhance the safety, security, and resiliency of Consortium agencies as well as the communities, residents, and visitors they serve. Technology is only one component of the newer, more integrated, more connected public safety ecosystem this RFP will help create. Even more important is selecting the right vendor to deliver that new technology as a partner in creating a better public safety future. Hexagon is a partner with the ability to support, adapt, and evolve alongside you --not just with continuously evolving and improving technology, but with a supportive, consultative relationship which does not end at installation or the payment of your maintenance bill. The Hexagon team has over 31 years of public safety experience. We serve hundreds of agencies, many of whom face the same challenges you do. We have invested in relationships with those customers to ensure our products and processes can meet your needs for the long term. That is why agencies from London to Washington DC, NYPD, EI Paso, New Zealand, the Sonoma Valley, and to Lee County Florida trust us to help them navigate the challenges of today — and tomorrow. It is from this perspective that Hexagon shares our proposal for what this new shared environment will look like. Hexagon understands the Consortium's goal to partner with a trusted vendor to implement a cloud based system that will not only connect multiple agencies and disciplines with multiple PSAPs, but will provide seamless interoperability throughout the County to all Consortium agencies. The Consortium can be assured that they are investing in a system that has been tried and tested within agencies of similar size and scope. Hexagon's focus aligns with the Consortium's need to improve users' overall access to information and benefit from advanced functionality with a modern system architecture. Hexagon will provide the solution that improves data -flow as an active part of first responder operations, Response to RFP 21-02 for CAD/RMS/Mobile Title Page & Cover Letter, pg. 1 / HEXAGON enabling fast, successful, repeatable responses by the Consortium's agency personnel. Hexagon has a history of implementing large complex agencies and our suite of products are built to handle the stress of large incidents requiring all disciplines (Law, Fire, EMS) to access critical information simultaneously, regardless of the number of users. Hexagon's Legacy Working with Public Safety Hexagon's history is an excellent predictor of future success and the best guarantor for the Consortium's successful implementation of new CAD, RMS and Mobile systems. With literally hundreds of installations supporting thousands o/f� agencies worldwide —we have successfully installed our public safety solutions in small cities like Vail, Colorado and one the largest and most complex dispatch centers in the world like Uttar Predesh, India which takes over 50,000 calls per day. Our product offerings are designed for multi - agency, multidiscipline, multi-PSAP deployments such as DuPage County, Illinois, NYPD; South Sound 911; and EI Paso, TX. Specifically, DuPage County 911 System serves a population of almost one million people and consolidated more than 40 law, fire and EMS agencies using 8 PSAPs to a single Hexagon CAD, Mobile, Records and Analytics Solution operating/�in 3 PSAPs. Other Hexagon solutions around the worlds support environments similar in scale to the Consortium. The Consortium desires enhanced interoperability and improved efficiency in public safety dispatching and data intelligence that will bring all agencies into Next -Gen 9-1-1 compliance. Hexagon answers that goal by providing a reliable, state-of-the-art CAD, RMS, Mobile and Analytics solution from a vendor that has successfully deployed and operated its public safety systems at many agencies around the world and throughout the United States. In addition, you can expect Hexagon to be invested in the daily operations of the overall project success and have/�a proven Southeastern -based team to deliver that same reliability and cutting -edge experience to the Consortium project. Hexagon's Solution for the Pinellas County Sheriff's Office In the attached proposal response, Hexagon is pleased to present the OnCall Cloud solution powered by ourworld-class OnCall Suite. The proposed system is led by our latest OrCall Dispatch CAD solution and OnCall Records RMS solution along with our Mobile Unit application, Mobile Responder smartphone and tablet application, and OnCall Analytics reporting tools. We will expand your OnCall Dispatch system with Advanced Mapping and Resource Management capabilities to yield powerful mapping, geo-location, staging, and data -driven responses for your agencies. Response to RFP 21-02 for CAD/RMS/Mobile Title Page & Cover Letter, pg. 2 A HEXAGON Pinellas County Consortium Solution Diagram Call -takers and dispatchers Pinellas County Sheriff PSAP St Petersburg PSAP Clearwater PSAP Large PSAP Pinellas Park PSAP Dispatch users, vehicles, smart devices Records users hexagon.com Esri Map 1 Esri Map 2 Esri Map 3 Esri Map 4 CN OnCall re Cloud ch I Mobile I / Integration / lytics / ilable production, ment, staging, g, hot disaster recovery RP11 Primary PSAP CommSys FOLEY NCIC Clevest FIBRS ! NIBRS Other interfaces (an -premises and cloud) is HEXAGON Hexagon's out -of -the -box integrated next -generation solution can be configured to meet the Consortium's specific needs. The Consortium can also implement applications, interfaces, business rules, and workflows. Support Pinellas County Consortium and Consolidation HxGN OnCa ii products can be deployed together or independently to provide the holistic insights and coordinated capabilities needed to advance the efficiency and effectiveness of the Consortium public safety efforts, including. • County dispatch and interoperability across multiple PSAPs, multiple agencies and disciplines • Expedite communications throughout the Consortium /� • Highly configurable systems designed to meet the needs of the Consortium agencies • Resiliency through "browser -based" products • Quicker decision making through an easy -to -use analytics package • Work -from -anywhere. With our browser -based technology, the user can operate from the office, home, a/�different PSAP or at an emergency remote field command center • On_all Cloud provides 99.95% uptime, high availability with CJIS secured Micro sift Azure Gov - Cloud. The Production environment includes two Production environments deployed in distinct, separate Azure Government paired regions with each Production environment configured to be highly available and distributed across three physical datacenters providing the Consortium with both HA and a Hot -Hot DR configuration • Site License. The Consortium will have security, reliability, and scalability with our cloud offering no matter the use case. There are no Hexagon user count restrictions for Call Takers, Response to RFP 21-02 for CAD/RMS/Mobile Title Page & Cover Letter, pg. 3 A HEXAGON Dispatchers, Record users and Mobile users. The site license includes usage for the twelve (12) agencies (six (6) Consortium PSAPs • Staggered PSAP cutovers. Hexagon is proposing to take two PSAPs live every four weeks. Hexagon has vast experience with multiagency, multidiscipline, multi-PSAP, multi -application cutovers Summary Hexagon respectfully submits our proposal to the Consortium for review and consideration. As one of the major county sheriffs offices in North America, Pinellas County Sheriffs Office faces challenges each day of protecting its citizens, workers, and visitors in a complex and ever -changing world. The Consortium requires a strategic partner with a range of expertise and experience that goes beyond traditional computer-aided � dispatch and mobile computing. The Hexagon solution will provide the following unique benefits to the Consortium. • Reduced Transition Ri s k: As the Consortium moves from a custom and aging architecture to a modern solution, there is inherent transition risk. However, Hexagon has extensive experience in effectively deploying CAD solutions in large, complex environments. This experience best positions our team to successfully manage and implement the Consortium's project. • Unparalleled Record: Hexagon is proud to be the world leader in the Public Safety software market with an unparalleled record for successful implementations in large agencies. We have implemented highly reliable solutions for more than 2,500 agencies in 26 countries. This allows us to continuously incorporate best -of - breed Public Safety functionality and technology into our products and deliver them to our clients in the form of a highly configurable solution. HEXAGON SAFETY & INFRASTRUCTURE HELPS PROTECT 1,N12 12 PEOPLE WORLDWIDE Providing, supporting, and maintaining complex, mission -critical public safety systems is very specialized. With over 31 years of demonstrable experience with financial stability, Hexagon has a successful track record of implementing demanding projects while focusing resources on the next generation of Public Safety software. We combine today's leading -edge Public Safety technology with next -generation advances for Pinellas County Sheriff's Office and the Consortium — an organization that strives to better equip its personnel to serve its citizens and protect all who venture there. As the Consortium evaluates Hexagon's proposal, it is important that the evaluation go beyond functional objectives and consider the strengths represented by our history of technology excellence and customer satisfaction. Through Hexagon's proposal, the Consortium will see how Hexagon OnCaii Cloud meets the strategic objectives set forth in RFP 21-02. Response to RFP 21-02 for CAD/RMS/Mobile Title Page & Cover Letter, pg. 4 A HEXAGON Table of Contents Section 1 — Vendor Qualifications T.L. 1 Section 2 — Project Objectives and Scope of Services Tab 2 Section 2.4 — System Architecture Te b 3 Section 2.5 — Performance and Reliability -Feb 4 Section 2.6 — System Backup Tab 5 Section 2.7 — System Recovery Tab 6 Section 2.8 — Operating System -Feb 7 Section 2.9 — Software License Agreement Te b 8 Section 2.10 — Cybersecurity/Information Security -Feb 9 Section 2.11 — System Administration Te b 10 Section 2.12 — General Functionality Tab 11 Section 2.13 — CAD/Mobile Tab 12 Section 2.14 —RMS Tab 13 Section 2.15 — Interfaces and Integration Tab 14 Section 2.16 — Geographic Information Systems Te b 15 Section 2.17 — Analytics Tab 16 Section 2.18 — Data Conversion/Migration Tab 17 Section 2.19 — System Testing and Accept. nce -Feb 18 Section 2.20 — Objectives -Feb 19 Section 2.21 — Scope of Services Te b 20 Section 3 — Submittals T.L. 21 Section 4 — Contractual Obligations T.L. 22 Section 5— Litigation, Claims and Regulator„ Tab 23 Section 6 — Proposal Pricing T.L. 24 Section 7 — Financial Statements T.L. 25 Section 8 — R.F.P. Response Form T.L. 26 Exceptions and Deviations from the Proposal Tab 26 Attachment A — Section D RFP Response Form (signed) Te b 26 Section 9 — Federal Debarred List Certificat, , T.L. 27 Attachment B— Section E Federal Debarred List Cert,f,cebon Form (signed) Tab 27 Appendix A — Third Party SOWs T.L. 28 Response to RFP 21-02 for CAD/RMS/Mobile HEXAGON Attachment C — White Box SOW Tab 28 Attachment D — Trancite SOW Tab 28 Attachment E — TDC SOW Tab 28 Appendix B — Hexagon Product Descriptions Tab 29 Appendix C — System Configuration Diagram Tab 30 Attachment F — Pinellas Consortium SOi tior, Overview Diagra rn Tab 30 Attachment G — Pinellas System Configure. Die gre m Tab 30 Appendix D — Addendum Acknowledgement Tab 31 Attachment H — Addendum Acknolwedgement Form (signed) Ta b 31 Appendix E — Hexagon Master Terms and Conditions Tab 32 Attachment I — Hexagon Master Terms and Conditions Ta b 32 Appendix F — Hexagon Cloud Specifications Tab 33 Attachment J — HxGN OnCall Suite Cloud System Specifications Tab 33 Appendix G — Hexagon Annual Reports Tab 34 Attachment K — Hexagon 2019 Annual Report Ta b 34 Attachment L — Hexagon 2020 Annual Report Ta b 34 Respot,se to RFP 21-02 for CAD/RMS/Mobile / HEXAGON Appendix A— Third Party SOWs Appendix A.1 — White Box SOW Appendix A.2 — Trancite SOW Appendix A.3 — TDC SOW Response to RFP 21-02 for CAD/RMS/Mo bile Appendix A: Third Party SOWS, pg. 1 � A HEXAGON Appendix A.1 — White Box SOW [Attachment C begins on the following page] Response to RFP 21-02 for CAD/RMS/Mobile Appendix A: Third Pert,, SOWS, pg. 2 � A HEXAGON Appendix A.2 — Trancite SOW [Attachment D begins on the following page] Response to RFP 21-02 for CAD/RMS/Mobile Appendix A: Third Pert,, SOWS, pg. 3 � A HEXAGON Appendix A.3 — TDC SOW [Attachment E begins on the following page] Response to RFP 21-02 for CAD/RMS/Mobile Appendix A: Third Pert,, SOWS, pg. 4 � A HEXAGON Appendix B — Hexagon Product Descriptions Hexagon has answered the technical questions provided within the RFP. To provide additional clarity on the proposed products, Hexagon has included product descriptions in this appendix for the following. • HxGN OnCall Dispatch • HxGN OnCaii Records • HxGN OnCall Analytics • HxGN Connect Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 1 A HEXAGON HxGN® OnCall Dispatch Accessed via a browser and mobile app, HxGN OnCall Dispatch is easy to administer and maintain and adapts to rapidly changing demands and technologies faster and more cost-effectively than legacy CAD systems. It delivers comprehensive capabilities via a range of role -based products and optional modules so agencies can assign the right tools to every type of user. OnCall Dispatch's streamlined workflows reduce operator workload, increase productivity, and boost PSAP capacity. Situational awareness and coordination keep responders safe and let teams take effective action sooner for better response and outcomes. HxGN OnCaLL Dispatch I Advantage features optimized screen layouts, visual displays, and user interaction shaped by extensive UX research and testing. Agencies also benefit from improved public trust with OnCall Dispatch, which enhances performance, lowers costs, and generates data for greater oversight, governance, and community engagement. Benefits Transforms Call -Taker & Dispatcher Experience As PSAPs modernize, adding contact channels and sensors, workstations, and workflows has become increasingly complex, making it hard for operators to assess information and take timely action. Shaped by usability studies with call -takers and dispatchers and decades of public safety partnerships, OnCall Dispatch's intuitive design delivers an exceptional user experience (UX) that transforms workflows and offers richer situational awareness without overloading the operator. For example, dynamic data filtering and an adaptive user interface (UI) give users the information and tools most relevant to their assignment. Streamlined workflows require fewer mouse clicks to perform vital tasks, speeding operations and reducing workloads. OnCall Dispatch can also integrate ICCS, CCTV, and other third -party data and capabilities, further reducing user input and eliminating the need to switch between multiple interfaces and input devices. Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 2 A HEXAGON Connects Roles for Better Safety & Efficiency An interactive common operating picture (COP) integrates contextual mapping, real-time data, and external feeds (i.e., weather map overlays) to improve awareness a n d coordination. Apps from OnCall Dispatch ensure safe, efficient, and effective response by connecting field responders with control rooms and supervisors for optimal awareness, communication, and coordination. Advantage delivers rich situational awareness without overwhelming the operator: By quickly leveraging insights in the field, responders can take safe, effective action and keep control The informed of their status and location no matter where they are. I he ability to update records and run searches also reduces dispatcher workload, increasing productivity and raising PSAP capacity. Improves Multi -Agency Collaboration OnCall Dispatch meets multi -agency and multijurisdictional CAD deployment needs, allowing users to The resources to optimize performance, increase resilience, and lower costs. I he suite strengthens communication and data sharing between agencies to provide faster, more effective response and coordination during incidents and major events. By supporting roles beyond police, fire, and emergency medical services (EMS), OnCall Dispatch sparks collaboration across a wide responder community through shared insights and resources. Supports Agile Organizations & Sustainable IT OnCall Dispatch's web architecture and administrative tools help public safety agencies become more agile and their CAD systems more sustainable over time. The suite simplifies application deployment and maintenance, training, and support by delivering configuration -based customization and centralized administration of browser clients and apps. OnCall Dispatch is easy to configure, update, and adapt to new requirements. Extensive configuration capabilities allow administrators to control and make changes without coding. Agencies also enjoy lower capital costs as HxGN OnCaii Dispatch removes high -specification client needs, makes more efficient use of server capacity, and enables flexible hosting options. With HxGN OnCall Dispatch, organizations can rest easy knowing their systems are safe, reliable, and highly configurable for the future. The HxGN OnCaii Dispatch solution for the Customer includes. • OnCall Dispatch I Advantage • OnCall Dispatch I Call -taker (included with Advantage) Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 3 A HEXAGON • OnCaii Dispatch I Viewer • OnCall Dispatch I Mobile Unit • OnCall Dispatch I Mobile Responder OnCall Dispatch Advantage HxGN OnCaii Dispatch I Advantage helps agencies modernize contact to better meet changing public expectations and make smart decisions for the future. It improves coordination and collaboration between the PSAP, units, and field personnel and supports multi - agency deployment. With a browser client that simplifies administration, Advantage's configuration -based customization options allow agencies to adapt the software for different roles and changing needs. Advantage includes all the functionality � of OnCall Dispatch I Call- I aker and features OnCall Dispatch I Dashboard for dynamic visual summaries of events, units, The event board within Advantage provides a dynamic, visual summary of and workloads. It offers flexible events, units, and workloads. licensing with specialized extensions and products that deliver subsets of its capabilities, including. • Advanced Mapping option pack, which provides the ability to view the whereabouts of the officer when they leave their unit on foot by interfacing with GPS enabled devices such as phones or radios assigned to employees. • Resource Management option pack, which provides support for advanced unit recommendation such as balance of alarm and staging functionality. Resource Management provides users with the unit recommendation features that allow them to define more complex unit recommendation and staging areas for fire agencies. • (Available but not included in this proposal) Scheduling & Facilities Management option pack, which provides the ability to define a transporting unit, recommend a facility such as a hospital, and manage the status of a facility. Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 4 A HEXAGON 0nCall Dispatch Call -Taker aker (included with Advantage) HxGN OnCaii Dispatch I Call -Taker provides a common user experience for processing calls for service using a variety of communications modalities in support of Next Generation 911. It includes additional features to streamline and enhance the call -taking process, such as a call -taker create event dialog, receiving ANI/ALI and caller location information, populating fields automatically on the dialog, and showing caller locations on the map. Features • ANI/ALI • Initiating Create Event form when a call is answered (if integrated to capable telephony system) • Populating the create event form with data from ANI/ALI and other call -taking sources when integrated • Ability to trigger basic Call -Handling functions such as Answer, Hang-up and Dial out from within the OnCall Dispatch application (if integrated to capable telephony system) In addition to the above features, Call -Taker aker provides the backend framework and user interface for additional key Call -Taking integrations such as: • Receive SMS/MMS and Instant Messaging (refer to configuration guide for compatible IM products) calls from the public • /A�ccura to Mobile Location compatibility • Call Handling (telephony integration) O nCall Dispatch Viewer HxGN OnCaii Dispatch I Viewer is an easy -to -use browser client that provides access to OnCall Dispatch information and basic functions. It allows users outside the control room to view live operations, search live and historic information, and create non -emergency events.. When deployedwith the OnCall Dispatch I Call - Taker module, it provides an efficient and effective solution for agencies who support call - taking and dispatching with separate teams. Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 5 A HEXAGON Viewer provides a simple, cost-effective way to extend access to live dispatch information and basic capabilities to users outside of the control room, while taking pressure off PSAP staff. It can also be used with option packs, to support roles including dedicated call -taking and alarm management. Features • Enables self -serve inquiry • Supports non -emergency workflows inside and outside the call center • Supports management and supervisory roles • Supports dedicated call -taking (used with OnCall Dispatch I Call -Taker) QnCall Dispatch Mobile lobile Unit HxGN OnCaii Dispatch I Mobile based client of O nCall Dispatch optimized for in - vehicle use. It offers role -based workflows, screen layouts for smaller form factors, and night time a n d high -contra st display. Chat - style messaging, group notifications, and automated alerts also enhance communications. User updates and live feeds from the field, including person -level tracking, ensure control rooms are aware of personnel status and location no matter where they are. Mobile Unit enables users to: • Monitor live operations via event and unit monitors • Run searches and queries • Receive events and alerts from the control room • Self -attach to events • Update status and event information • Message units, individuals, groups, and dispatchers • Make, update, and cancel tow requests Agencies can easily configure Mobile Unit using the same simplified administration tools for office -based clients. Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 6 A HEXAGON 0nCall Dispatch Mobile lobile Responder The HxGN OnCaii Dispatch I Mobile Responder mobile app provide access to streamlined response and law enforcement workflows to field personnel using hand-held tablets or smartphones. Optimized for smaller form factors, it ensures information is clear and agencies can operate tools quickly and accurately. It connects to the same live operational views and messaging, allowing responders operating away from their vehicle to stay on top of event changes and share consistent situational awareness with the control room. The Mobile Responder Overview page displays the Status drop -down list and a list of active events. The Map page displays the locations and details of active events and units. The Units page displays all active units and lets you search for specific units. Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 7 A HEXAGON HXGN® OriCaii Records HxGN OnCaii Records is a cloud -deployable records management system that serves all facets of law enforcement operations and administration. Accessed via browsers and mobile apps, it provides reliable access to comprehensive information and tools. Out of the box, I IxGN OnCall Records can help Agencies: • Streamline records capture and • Comply with laws and regulations management e Adapt to change and agency needs • Reduce administrative burdens • Support on -premises and cloud • Enhance data quality • Harness complete information • Enable real-time, rules -based alerts • Integrate with computer -aided dispatch • Provide visual reports and analytics all roles can use deployment • Lower total cost of ownership and mobile system Scalable for single - and multi -agency use, it serves all facets of law enforcement operations and administration. OnCall Records allows agencies to streamline records capture and administration, harness data to inform investigations, effectively manage resources, and enhance community safety. A flexible solution suite, it offers simple centralized administration and configuration of clients and embedded interfacing. Increase Speed & Flexibility Agencies must be able to quickly access and capture records data from anywhere to complete investigations and improve community safety. Our premier solution. • Combines the advantages of an enterprise system with the benefits of a secure, browser -based solution • Offers simplified central/administration of browser and mobile app clients • Supports access from PCs, laptops, tablets, and smartphones • Increases agility with configuration -based customization and built-in interfacing capabilities • Offers robust application and data security Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 8 A HEXAGON • Supports on -premises and cloud deployment on Microsoft® Azure and other platforms Benefits for A11 Facets of Law Enforcement 0nCall Records serves all facets of law enforcement operations, including field and office reporting, patrols, investigations, custody, and administration. Unified workflows and data remove manual and duplicative tasks to streamline data capture and administration, while improving overall quality. Accessed via browsers and mobile apps, it provides reliable access to This information and tools. I his powerful enterprise system. • Supports incident response, traffic stops, field interviews, crime analysis, asset and fleet management, human resources, reporting, and more • Delivers a complete workflow solution for case management and investigative processes • Links people, property, places, and related records into one central database, dramatically increasing law enforcement efficiency and effectiveness • Provides greater insight by running a single search across themes and powerful, easy -to - use visual reports and analyses • Integrates seamlessly with Hexagon or other third -party computer -aided dispatch (CAD) and mobile systems for fast, easy data access and query without the need for redundant data entry IixON OnCall Records serves all facets of law enforcement operations, Including field and office reporting, patrols, investigations, custody, and administration. The ability to search and update frank the field is essential to enhance awareness, speed workflow'', and increase efficiency. • Supports government reporting requirements (such as NIBRS, Stats Canada UCR, and UCR ensure accuracy, prevent audits, and improve internal reporting • Integrates with multimedia, such as images and document workflows, resulting in faster identification and improved officer and citizen safety • Ensures data security, simplifies auditing, and enables appropriate confidentiality (such as for Juvenile records) • Easily maintains evidence records and complete chain of custody with electronic signature capture • Delivers automated notifications via alerts as data is captured or changes occur during the investigative processes Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 9 A HEXAGON Available Modules lodules Modularity is a simple concept that significantly impacts the organizational efficiency of the system. The OnCall Records modular design isolates system informational components, then uses these components to create a functional software module. The major modules of the system are: • Accident • Incident • Alarm • Arrest • /� • Asset Management • Juvenile Contact • B.O.L.O. (APB) • Juvenile Court Document • Booking • / • /Calls For Service • Lineup • Case Management •Master Location • • Master Name • •Master Vehicle ▪ Driving Under the Influence (DUI) • Missing Person • Employee • Permits/Licensing • Employee Info • Property • Evidence • SScheduled Event • Group Intte rview•I raining • Tracking • • Impound/Tow • Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 10 A HEXAGON HXGN® O.,Call Analytics HxGN OnCaii Analytics takes raw, fragmented, incomplete, or incorrect data and converts it into usable reports and dashboards, so agencies can better assess performance, allocate resources, and improve operations. By creating a single source of truth to explore, analyze, and share, the software suite quickly turns knowledge into action and helps agencies respond more effectively to incidents and major events. OnCall Analytics is more than a standard reporting solution — its a suite of public safety data visualization and analytics products. With it, users have the information and tools they need for evidence -based reporting, analysis, and decision -making. Built for organizations of all sizes, OnCall Analytics delivers clear insights to improve community relations and support programs and policies in the field. It allows agencies to make better decisions and easily explore complex data and its relationships. OnCall Analytics prepares more staff to use reports and analyses to solve complex business problems, freeing analysts' time and reducing delays. It also makes cities better places to live, work, and visit by removing data silos and giving managers the insights they need to make communities safer and more resilient. Benefits Unlocks Valuable Data Assets A city can only reach its full potential when its citizens feel safe and secure. With data mining capabilities from OnCall Analytics, agencies can transform complex, unintelligible data into clear business reports and dashboards that are easy to understand and use across multiple groups. Built for diverse organizations and data sets, the suite gives agencies a solid foundation for accurate and reliable reporting and analysis. This allows users agency -wide to confidently run reports and analyses and leadership to make thoughtful decisions and improve public trust. Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 11 A HEXAGON Empowers Public Safety Staff & Leaders Data visualization and analytics carry enormous potential. For agencies of all sizes, a data -driven enterprise ensures decisions are based on facts and users can spot hidden patterns and insights that might otherwise go unnoticed. OnCall Analytics offers easy -to -use, business -ready content and visual reports that leverage Hexagon's Analytics allows users agencywide to confidently run reports and analyses and leadership to make thoughtful decisions and improve public trust. CADand RMS systems and other data sources for monitoring events, aligning resources to demand, supervising PSAP performance, maintaining governance and oversight, and much more. By allowing more employees to visualize data, run reports, and conduct analysis, the suite empowers organizations to improve performance and productivity. Builds Tr. & Transparency The digital age has changed the way the public perceives and responds to service providers. Today, citizens, government authorities, and the news media want instant answers and access to broader information. Public safety agencies must be prepared to meet these demands to increase transparency and awareness of important issues. With OnCall Analytics, organizations can easily find and share robust information using clear reports and analyses to enhance public trust, dispel misconceptions, demonstrate compliance, and Justify funding requests. Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 12 A HEXAGON Features Interactive Reports & Dashboards OnCall Analytics helps organizations be more productive from the start and meet specific agency and user requirements. With it, departments can access pre -built dashboards that address diverse business challenges or build their own reports with subject - area data models and self-service, drag -and -drop tools. Agencies can also easily refine and adapt out -of -the - box content for assessing, reporting, and optimizing emergency response tasks. Spatial Analysis & Playback Better understand event sequences and incident patterns with spatial analysis, visualization, and playback capabilities. In OnCall Analytics, map controls include plotting location - based information, pin and hotspot mapping, dynamic clustering, geofencing (geospatial filtering), and more. Powerful Data Warehouse flagging errors and inconsistences and replacing obscure database codes with relevant business themes, the data warehouse enhances data quality and query performance. It creates a single source of truth all staff can understand and use, ensuring operators can quickly explore, analyze, and share data through interactive reports and dashboards. Ensure your data is clean, easy to understand, and business -ready with OnCall Analytics' data warehouse. By An cs gives agenc es the bars and insights theyneed to assess perfarcraance and improve rtec lion-makrrig- Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 13 A HEXAGON OnCall Analytics I Records Data Models lodels and Reports OnCall Analytics I Records Data Models and Reports is the managed service (SaaS) version of HxGN OnCall Analytics that that serves as the foundation for reporting, business intelligence, and analytics for OnCall Records managed service customers, as well as prebuilt Power BI report templates. OnCaii Analytics I Records Data Models & Reports includes 15 data models that insulate users from underlying database complexities by converting the raw OnCall database fields into industry terminology and logically grouping that data in reporting subject areas. In addition, it also calculates new fields on -the -fly (called measures) that are essential to creating The reports and conveying information to stakeholders. I he Records data models serve as the data source of all reports delivered and built with OnCall Analytics. OnCall Analytics I Records Data Models & Reports also includes 28 interactive Power BI report OnCall Analytics I Dispatch Data Models lodels and Reports OnCall Analytics I Dispatch Data Models and Reports is the managed service (SaaS) version of HxGN OnCall Analytics that provides the Dispatch data models that serve as the foundation for reporting, business intelligence, and analytics for HxGN OnCaii Dispatch managed service customers. OnCall Analytics I Dispatch Data Models & Reports includes17 data models that insulate users from underlying database complexities by converting the raw OnCall database fields into industry terminology and logically grouping that data in reporting subject areas. In addition, it also calculates new fields on -the - fly (called measures) that are essential to creating meaningful reports and conveying information to stakeholders. The Dispatch data models serve as the data source of all reports delivered and built with OnCall Analytics. OnCall Analytics I Dispatch Data Models & Reports also includes 22 interactive Power BI report templates. OnCall Analytics I Dispatch Data Models and Reports also includes capabilities for spatial visualization, analysis, and playback capabilities, including Automatic Vehicle Location (AVL). Reports include the following: OnCall Analytics I Viewer HxGN OnCaii Analytics I Viewer is a concurrent user license for the SaaS version of HxGN OnCaii Analytics that allows a user access, run, and interact with reports that have been published to the SaaS OnCall Analytics web portal. OnCall Analytics I Author HxGN OnCaii Analytics I Author is a concurrent user license for the SaaS version of HxGN OnCall Analytics that allows a user to create and publish content to the OnCall Analytics SaaS web portal, as well as access, run, and interact with reports that have been published to the SaaS OnCall Analytics web portal. Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 14 AA HEXAGON OnCall Analytics I Author license includes access to the map and playback Power BI controls (known as The Visuals in the on -premises version of OnCall Analytics). I he map( The playback controls can be leveraged to create advanced, interactive reports without having to be a GIS professional. I he map control provides enhanced geospatial analysis, including heat -maps, dynamic clustering, and geofence filtering. The playback control enables playback -over -time capabilities (including support for multi -unit AVL playback). Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 15 A HEXAGON HXGN® Connect Hexagon has not included this product in the proposal for the Consortium, but pricing is available upon request. Since there were a few requirements that could be met with this product, Hexagon has included a description of HxGN Connect. Hexagon is willing to discuss adding this product to the Consortium's solution, if desired. HxGN Connect is a scalable SaaS solution that bridges information and communication gaps, removes data silos, and enhances collaboration between diverse roles, organizations, and sectors. Cross - functional collaboration. Shared awareness. Coordinated action. These are significant hallmarks of resilient communities and organizations. However, challenges arise from technical and operational gaps between diverse organizations that have their own cultures, budgets, geographic areas, and ways of working. HxGN Connect is a pragmatic, effective solution that connects operational functions, organizations, and sectors via an easily deployed, collaborative space. By enabling shared awareness and coordinated action, it improves efficiency, performance, and safety of operations. And because it's scalable, it promotes real-time collaboration in all matters, transitioning seamlessly from day-to-day tasks to large- scale emergencies and crisis management. Bridging the Gaps As societies and economies become more reliant on complex webs of services and infrastructure, there is a pressing need to bridge the operational gaps between providers. A global recession and growing impacts from natural disasters reinforce this need. An enhanced level of collaboration and shared awareness solves problems for not only the affected organizations, but also the communities they serve. Within most cities and organizations, individual departments work independently, even though their actions and decisions often impact other departments, organizations, and the public. Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 16 A HEXAGON This lack of coordination creates problems within other areas of an operation, including missed opportunities to enhance planning and improve safety, efficiency, and performance. Other issues include. • Inconsistencies: Manual approaches to awareness and wider communication that are slow, unreliable, and error -prone • (Delays: A slower response in identifying and resolving issues • Conflicts: One or more groups performing tasks that are inefficient or unsafe Breaking Down Silos Organizations and departments are aware of the need to collaborate more widely, but they rarely have the solutions, capabilities, and resources at their disposal. Persuading other partners to collaborate can be a fruitless venture, especially if they lose control over their data or ultimately pay for a system they don't own. While some areas of operation utilize collaborative tools, they only extend to a limited number of users and organizations. The wider picture is one of siloed data, systems, and workflows. These silos, whether internal or external, require manual communication that is slow, unreliable, and often forgotten. This leads to isolated bubbles, each serving a small number of users performing similar tasks for similar departments or organizations. HxGN Connect, which leverages Hexagon's Xalt data integration platform, breaks down these silos between not only technology and organizational data, but also organizations and citizens. The end result is greater shared awareness and efficiency among collaborators. Key Features Collaborate Across Multiple �p lultiple Sectors The success of collaborative solutions depends on the level of benefit to the partners. HxGN Connect ensures all partners gain value from the solution, while removing technological and data -sharing barriers preventing involvement. Retain Data Ownership HxGN Connect allows partners to retain data ownership, including defining what data sources each partner sees. Stringent controls mean information can be shared with confidence because only approved users can access data. Enhance G0 mmunicati on HxGN Connect doesn't just share data; it promotes and enhances coordinated action by ensuring data is current, reliable, and definitive. It connects to trusted sources and enables communication with users across roles and organizations. Support Diverse Roles The solution allows users to communicate and collaborate with those from other functions, roles, and organizations — including internal departments and external partners — to obtain information and act on it. It easily integrates with existing systems to provide new or alternative capabilities. Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 17 A HEXAGON HxGN Connect allows users to communicate and collaborate with those from other functions, roles, and organizations - including internal departments and external partners - to obtain information and act on it. Because it's scalable. HxGN Connect promotes rev? -time co4Labaration, transitioning seamlessly from day-to-day tasks to large- scale emergencies Re flooding caused toy a significant storm_ Above: Users can see automatic updates via channels, which honor data -sharing rules_ HxGN Connect alloys collaborating organizations to post -their own messages, images. and videos to Inform users about current conditions_ Right: Another feature of 1-UGN Connect is the obi [Ay to send and receive alarms about dangerous and potentially life -threatening conditions Like rising water levels. The alarm also provides the level of priority. Location of the emergency, and a primary point of contact. Benefits HxGN Connect makes collaboration attractive and achievable by removing barriers to participation and offering broader value to all partners. Because of its richer operational insights, flexibility, and universal user experience (UX), HxGN Connect supports more users and use cases. It simplifies data integration, allowing organizations to decide what information to contribute while retaining both ownership and control. Specifically, HxGN Connect: • Helps organizations manage incidents, share data, and coordinate action with a visual method of engagement and collaboration not available elsewhere • Assures ease of operation by diverse user profiles with minimal training and seamlessly transitions from routine tasks to crisis mode • Provides a unified, rollup view that enables both day-to-day, ad hoc engagement and formal methods • Removes technical and organizational barriers to collaboration through SaaS deployment • Allows collaborating partners to retain ownership and control of their data lower cost of ownership and faster return on investment through simplified data integration, system deployment, and maintenance Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 18 HEXAGON In addition to emergencies, organizations can use HxGN Connect to plan large events Like a citywide summit. Channels provide a collaborative space for all participating organizations. For example, as the city's public works department beautifies the city, they can receive and upload photos of potholes and graffiti to the channel. The public works department, using the channel, can then notify repair crews about the issue. The public works department can also receive real-time updates about work orders. Response to RFP 21-02 for CAD/RMS/Mobile Appendix B: Hexagon Product Descriptions, pg. 19 iff A HEXAGON Appendix C — System Configuration Diagram Per RFP requirements, Hexagon has included a system configuration diagram for the Consortium's CAD/RMS/Mobile OnCall solution. This diagram indicates proposed software and specs for recommended hardware. Hexagon has also included a solution overview diagram below. [Attachment F begins on the following page] Response to RFP 21-02 for CAD/RMS/Mobile iff A HEXAGON [Attachment G begins on the following page] Response to RFP 21-02 for CAD/RMS/Mobile � A HEXAGON Appendix D — Addendum Acknowledgement Hexagon has completed the addendum acknowledgement form provided with Addendum 1 for this RFP. [Attachment H begins on the following page] Response to RFP 21-02 for CAD/RMS/Mobile Appendix D: Addendum A. A HEXAGON Appendix E — Hexagon Master Terms and Conditions The Cloud Subscription terms are provided in Hexagon's Master Terms, which are available at the link below, and incorporated by reference herein. /He xa gon/SI/Sales/MT/US-MT06-2021. pdf [Attachment begins on the following page] Response to RFP 21-02 for CAD/RMS/Mobile Appendix E: Hexagon Master Terms & Conditions, pg. 1 / HEXAGON Appendix F — Hexagon Cloud Specifications [Attachment.) begins on the following page] Response to RFP 21-02 for CAD/RMS/Mobile Appendix F: Hexagon Cloud Specifications, pg. 1 A HEXAGON Appendix G — Hexagon Annual Reports As discussed in Section 7 of this proposal. Hexagon has included two years of financial data in the financial reports linked below. These reports include audited financial statements for Hexagon's parent company, Hexagon AB, a publicly traded corporation on the NASDAQ Stockholm exchange. • 2019 Annual Report: https://vp20p0.alertir.com/afw/files/press/hexagon/202004021243-1.pdf • 2020Annual Report: https://vp200.alertir.com/afw/files/press/hexa gon/202103311974-1.pdf Hexagon acknowledges the requirement to include hardcopies of these reports in the signed original copy of the proposal. Those documents are included below. Response to RFP 21-02 for CAD/RMS/Mobile Appendix G: Hexagon Annual Reports, pg. 1 A HEXAGON Hexagon AB 2019 Annual Report [Attachment K begins on the following page] Response to RFP 21-02 for CAD/RMS/Mobile Appendix G: Hexagon Annual Reports, pg. 2 A HEXAGON Hexagon AB 2020 Annual Report [Attachment L begins on the following page] Response to RFP 21-02 for CAD/RMS/Mobile Appendix G: Hexagon Annual Reports, pg. 3 A HEXAGON Section 1 —Vendor Qualifications The vendor shall outline the company's background, including a brief history of the vendor and a description of the vendor's present organizational structure, describe how you are investing in your current and future product fines, and describe the company's research and development capabilities. Hexagon Response: Company Background and Brief History Hexagon's Safety, Infrastructure & Geospatial division develops, markets, implements, and supports computer -based solutions for law enforcement organizations, fire departments, emergency medical and rescue units, and other public safety agencies. An acknowledged leader in the industry, Hexagon offers technologically advanced solutions designed to capture, integrate, and display complex data using a geospatial platform. Hexagon's entrance into Public Safety started in 1989 with the introduction of the I/CAD System, which coupled forms -based dispatching with an interactive map. Following Hexagon's launch of the first "map centric" CAD software, Hexagon's Public Safety Business Unit has consistently built on the I/CAD System technical platform and continued to push CAD technology forward. To date, Hexagon has led the market with some of the following CAD releases: s 1989, Hexagon introduced the first map -based computer aided dispatch system • 1995, Hexagon released the first end -to -end Windows -based CAD platform, employing Windows - based operating systems on both servers and clients • 1998, Hexagon introduced CAD web applications • 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, tunnels, and so forth • 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 Hexagon'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 Hexagon "Hot Product," selection for our Interoperability This for CAD product. I his selection represented the second consecutive year that an Hexagon application received this prestigious award and was featured in the Public Safety Communications magazine 2012, Hexagon'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, Hexagon released I/CAD 9.4 with enhanced features for call handling and dispatching, intelligent mapping, field communications, data reporting and analysis, and application integration • 2019, Hexagon released OnCall, the next -generation web -based CAD system Response to RFP 21-02 for CAD/RMS/Mobile /HEXAGON Today, Hexagon 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. Hexagon project implementation personnel average 15 years of Public Safety experience per employee, and 13 years of experience per employee/ein our Support and Services organization. This level of experience/�ensures that, as the Prime Contractor, Hexagon understands the issues and requirements of the Consortium, as well as long-term business objectives. Present Organizational Structure Steven Cost President Hexagon Safety & I nfrastructure Bill Campbell Senior VP of Hexagon Safety & Infrastructure Ben Ernst VP of Public Safety John Whitehead VP of U_S_ PS Sates Account Sales Executives Blair Jacks CFO Debra Huser Americas Finance Director Richard Morris Senior Divisional Counsel Victor Vasile Regional Divisional Counsel Response to RFP 21-02 for CAD/RMS/Mobile Section 1: Vendor Qualifications, pg. 2 A HEXAGON Current and Future Product Lines Several key trends are fundamental to and drive our technology strategy. • Our customers demand ever greater operational efficiencies. Informed by 31+ years' experience with 350 agencies and scientifically optimized with call -takers and dispatchers, Hexagon's OnCall suite offers users exceptional situational awareness and streamlined operation to meet this need. The result is reduced operator workload, increased productivity, and enhanced safety for citizens and responders. • Public safety agencies are using cloud capabilities to respond to threats faster and help save lives. Hexagon's OnCall suite is optimized for the cloud. Deployed in the Microsoft Azure cloud environment, HxGN OnCaii as a managed service is easily configurable and accessed via browsers and mobile apps. Unlike other solutions on the market, its full -featured, modern user experience and modular design reduce the total cost of ownership and help organizations adapt more quickly to changing situations. • Our customers focus on integration and interoperability. The challenge of every organization is to pull together disparate systems and integrate data and workflows within departments, across systems, and between Jurisdictions. Our intention is to enable agencies to participate across boundaries in the public safety and intelligence community. • Our customers need to convert collected data into actionable intelligence. The OnCall Dispatch and OnCall Records systems are used operationally every day to manage incidents, assets, and organizational resources, and the data generated provides a wealth of transactional information that can be used to aid in decision -making efforts both operationally and strategically within the enterprise. Systems that can assist with organizing and prioritizing this information are in demand. Hexagon continues to enhance the ability to turn data into actionable information through the use of a revolutionary OnCall Analytics solution. Through our Public Safety -specific crime analysis solutions, Hexagon clients can quickly deploy and exploit business intelligence capability for operational and analytical reporting. • The rapid emergence of geospatial platforms has changed the landscape and accessibility of GIS products. Within the span of several years, these systems have become significant platforms that provide real value for enterprise users, extending the GIS awareness beyond that provided in the GISdata set. To respond to this trend, OnCall Dispatch does not use its own proprietary map source— it uses the technology of other next -generation geospatial platforms to provide a highly available, dynamic mapping system. • Increasing bandwidth, both wired and wireless, continues to drive change within the enterprise. The concept of "access from anywhere" is in demand by both officers in the field and command staff at home. The dramatic increase of technology options and application platforms is, in itself, driving change. Advances, such as rich Internet application architectures and new classes of mobile devices, create opportunities to deliver valuable capabilities that simply did not exist a short time ago. Research and Development Capability As an industry leader, Hexagon recognizes it has to continue to invest in and advance its products in order to meet the dynamic nature of the industry. To that end, Hexagon invests substantial resources and capital into its research and development. Hexagon welcomes further discussion, if necessary, during contract negotiations. Response to RFP 21-02 for CAD/RMS/Mobile Section 1: Vendor Qualifications, pg. 3 A HEXAGON The vendor shall provide information concerning the personnel who will be assigned to this contract. This section must include the experience, education, and professional qualifications each employee has in developing and implementing training programs specifically for the System. Hexagon acknowledges this request for information about the experience and qualifications of personnel who will be assigned to this contract. Hexagon has included this information for a tentative project team in Section 2.20 - Objectives, Item C "Project Team Organizational Structure". The vendor shall provide a list of subcontractors to be used in the performance of the work requested. Hexagon Response: Hexagon has established relationships with trusted third party partners to support a successful implementation of the OnCall system for customers such as the Consortium. These partners have proven experience in the public safety industry. • White Box • CommSys • Tra ncite • Telecommunications Development Corporation (TDC) Along with the above, vendor shall provide the following in the proposal response: • System Customer retention for 2018, 2019, and 2020; • Number of organizations that have uninstalled the System in part, or total; Hexagon Response: Hexagon is proud of the strength, resiliency and performance of its public safety software solutions and our customer's continued use of our software to protect their citizens. While we believe we have a strong customer retention and satisfaction, from time -to -time Customers make choices to go in a different direction, and we do not have that information as requested above. However, many customers who previously departed the Hexagon -family of customers have since returned to using Hexagon software after trying out other vendors' software such as San Angelo, Texas; Jefferson County, Missouri; and Manatee County Sheriff's Office. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON • Total full-time employees in the company for 2018, 2019, and 2020. Hexagon Response: See the below chart for the distribution of employees across Hexagon divisions for the past three years. "Hexagon" refers to Hexagon AB (parent company) and includes totals for all divisions. "SIG" refers to Hexagon Safety, Infrastructure & Geospatial division only. "R&D" refers to employee resources dedicated to Research and Development. Year H—g.,, SIG Hexagon, R&D SIG R&D 2018 5737 2495 1668 464 2019 5741 2502 1812 557 2020 5720 2395 1788 503 • Total full-time employees employed in the division of the company that includes the System for the same years. Hexagon Response: Hexagon's Safety, Infrastructure, and Geospatial division will be responsible for implementing the System. Employees in 2020 totaled 2,395 individuals. • Total full-time employees on the software development team that support the version of the software the Consortium will implement. The employee database Hexagon maintains is not able to drill down to a total for the employees on the software development team for Just the proposed OnCall products. Hexagon has provided the number of employees classified as Research & Development, which includes the OnCall development team. In 2020, there were 503 employees classified as R&D for Hexagon SIG. • Total full-time trainers and implementors. Hexagon Response: Hexagon has one employee who is a full time dedicated trainer for the OnCall suite of products. That is because Hexagon's best practice is to equip its implementation team members to be trainers and technical experts. This way the individuals leading the Customer's training classes will be better able to speak to how the system was designed and the practical ways it can be used. Hexagon has more than 30 Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON full-time implementers for OrCall Dispatch product and 13 for OnCall Records product in North America, with many more globally. Response to RFP 21-02 for CAD/RMS/Mobile Section 1: Vendor Qualifications, pg. 6 /HEXAGON Section 2 — Project Objectives and Scope of Services The vendor shall provide a fully detailed and complete plan of how these processes shall be accomplished to include: Implementation Project Plan, Implementation Methodology, Project Team Organization Structure, Software Customization Plan, Data Conversion Plan, Business Process Workflows, Report Development, Implementation Testing Plan, Quality Assurance & Testing Plan, Organizational Change Management, Budget and Staffing Plan, Interfaces, Hardware, Equipment and Technical Architecture, Pre- and Post -Implementation Support Plan, Training Plan, Third -Party Products, and Application Hosting. This section shall include every detail as required in the Specifications section. Hexagon Response: The information requested as a response to RFP "Section B Specifications" is included hereinafter. Hexagon clarifies the information provided in sections "2.0 Introduction", "2.1 Background/Key Metrics", "2.2 Current CAD Environment", and "2.3 Current RMS Environment" seem to relay information rather than request a response. Hexagon acknowledges the information provided in those sections. Hexagon's response below begins with section "2.4 System Architecture". Response to RFP 21-02 for CAD/RMS/Mobile Section 2: Objectives and Scope of Services, pg. 1 A HEXAGON Section 2.4 — System Architecture The Consortium expects the Proposer to provide the software, infrastructure specifications, recommendations, and requirements, as well as services necessary to implement the System successfully. All the software needed for a fully functioning and fully integrated System is expected at the time of implementation completion. The System must fully comply with the current Florida Department of Law Enforcement CJIS Security Policy. Proposers are responsible for providing a System with sufficient capacity and performance capabilities to support the requested licenses and volumes, plus a margin for expected growth. Proposers shall provide an appropriate response for each of the following: A. /t is preferred that the System architecture conforms to a mobile -first, cloud -first model. Describe the architecture necessary to provide connectivity to the application(s) across all Consortium members and locations. The OnCall architecture is a scalable, flexible architecture designed to leverage both Container technology and Microsoft Azure Platform services to provide the ability to both scale up and out as needed. The OnCall architecture is a distributed message -based solution that includes the OnCall web application built using React and Node.,s.N ET technology stacks. OnCall includes asset of .NET microservices that use the Azure Message Service Bus for communication. Azure SQL Service hosts the OnCall database providing availability, geo-replication, and auditing capabilities. OnCall leverages Azure Kubernetes Service (AKS) to manage the hosted Kubernetes environment, making it quick and easy to deploy and manage containerized applications. Using containers eliminates the burden of ongoing operations and maintenance/�by provisioning, upgrading, and scaling resources on demand, without taking applications offline. Containerization allows for greater modularity. Rather than run an entire complex application inside a single container, the application can be split into modules (such as the database, the application front end, and so on). Applications built in this way are easier to manage because each moduleisrelatively simple, and changes can be made to modules without having to rebuild the entire application. Because containers are so lightweight, individual modules (or microservices) can be instantiated only when they are needed and are available almost immediately. B. Describe how the System can be cloud -based while providing on premise edge technology to prevent outages if connectivity to the Internet is unavailable. Hexagon's OnCall system does provide functionality described above. Hexagon OnCall Dispatch I Mobile Unit is designed to work in a partially disconnected modems due to the mobility of the workforce. Mobile Units will remain logged on if connectivity is temporarily lost. Certain offline actions are available in the Mobile products to allow for continued use of the applications for some commands. Examples would include, if a unit has been assigned to an event, unit statusing, event Remarks, and add supplemental information. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON C. Provide a diagram of the proposed system architecture. The diagram should include an overall representation of the servers (application, database, Web, reporting), network (internal, external, and inter -agency connectivity), peripherals, workstations, mobile data components, and interface points, as well as a representation of the System environments (Production, Backup, and Training/Testing). Hexagon Response: Per the requirements above, Hexagon has included a system configuration diagram of the proposed solution for the Consortium. Please refer to Appendix C for that diagram. D. Are there any parts of the System that are not cloud -based? P/ease describe. Hexagon Response: Hexagon has proposed a system with components that are not cloud -based. Please refer to the system configuration diagram in Appendix C.The I he diagram legend indicates what parts of the system are on - premise and what parts of the system are cloud -based. One example of a component that is not cloud -based is the Communications/Interface Server #la in the CADproduction environment. This server contains the connection to third party CommSys ConnectClC product that facilitates NCIC/FCIC and related CAD and RMS transactions. E. Describe your hosting model, including hosting, integration, help desk, provision and desktop management capabilities, deployment model (dedicated servers, shared environment, etc.), and any 3rd party partners that may be involved in service delivery. Hexagon Response: The OnCall application suite is a combination of Cloud native frameworks and Cloud PaaS services that together provide availability, stability, and elasticity in the Cloud environment. OnCall leverages Azure Kubernetes Service,/Cloud Active Directory and Azure SQL Service across Availability Zones coupled with Azure Security Center to provide our customers with the best of breed solution. Hosting The proposed OnCall SaaS is an Azure hosted solution provisioned provides a managed service offering of our OnCall product suite. The managed service offering is provided by Hexagon's Cloud Operations group and includes various services. that Cloud Monitoring, Alerting and Repo/ruing are important parts of maintaining the reliability, availability, and performance of cloud infrastructure. Continuous monitoring ensures the cloud environment is running smoothly and everything is working as expected. Different types of metrics are aggregated in one place to get full visibility of highly dynamic services as they scale and evolve. Monitoring allows Hexagon to efficiently investigate potential issues and is organized into the following three categories: (1) Health of the cloud infrastructure, (2) Health of the applications deployed in the cloud, (3) Security. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.4: System Architecture, pg. 2 4 A HEXAGON Health monitoring provides alerts and guidance when cloud service issues may impact either the cloud infrastructure or applications running in the cloud. Health monitoring includes both proactive and reactive monitoring leveraging a combination of tools such as Azure Service Health Alerts, Azure Monitor, Azure Advisor, and other Azure services. Proactive monitoring prepares for planned maintenance or changes that may impact the availability of cloud resources. Reactive monitoring is used to understand the impact of service issues. Monitoring services are provided for the customer's cloud environment for end -to -end visibility,/ performance degradation, and managing user experience of business -critical applications. Cloud resources will be monitored based on a standard set of parameters. Changes to metrics monitored may be implemented as a continual proactive improvement process. Performance tuning and preventative services differ by application workload and include scanning the solution stack to check for possible issues and reviewing the resource health status and may include the following tasks. • Capacity, demand, and utilization review and improvement planning • Review & application of OS updates • Evaluate data characteristics (movement trends, speed, and behaviors) to identify if the system is regularly performing within data thresholds and to determine if any adjustments are required • Storage assessment for the desired level of performance to identify if adjustments are required to accommodate the workload • Benchmark and monitor workload performance, against predefined metrics • Monitoring application system parameters to identify any recommended actions to ensure system relia bility Monitoring services using tools such as Azure Security Center are provided for tracking and managing security compliance over time to identify opportunities to strengthen the security posture and improving security by configuring recommended controls based on the customer -specific network topology. This may include (1) firewall monitoring and support to cloud -compatible firewalls connected to the Customer's Azure environment and (2) threat intelligence -based filtering in support of threat detection and prevention by enabling firewall alerts and denying traffic from/to known malicious IP addresses and domains. Integration Hexagon's proposed approach to application integration includes RestAPl and HxGN OnCaii Integration Engine (OIE). RestAPI For requirements that go beyond the scope of configuration, OnCall Dispatch enables direct integration via a RESTful API. The API allows the creation of customized messages, notifications, components, and microservices using standard development tools and methods. OnCall Dispatch's API and microservice architecture make the writing, delivery, and maintenance of custom code easier, more efficient, and less disruptive. Granular, self-contained functional modules allow independent manipulation or modification of individual services and supporting service infrastructure. Reducing the interdependency between services allows agencies to quickly implement and deploy component changes without unplanned impacts on other services. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON OnCall Integration Engine Hexagon OnCall Integration Engine is a server component that acts as a broker, an orchestration platform and a data aggregator facilitating OnCall interface support and development with a consistent API, secure endpoints and flexible workflow that leverage standard integration patterns and standards. OnCaii Integration Engine provides first responder personnel in the field access to Hexagon's OnCall computer -aided dispatch (CAD), OnCaii record management (RMS), and third -party RMS systems via a handheld smartphone or tablet running OnCall Mobile apes. This part will be hosted in a Microsoft Azure environment. Help Desk provided as part of the cloud subscription. 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 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 • Problem resolution based on priority level 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, following investigation, the priority level being raised or lowered, depending on the findings during problem investigation. Provision and Desktop Management lanagement Capabilities Hexagon has proposed an optional Resident System Administrator (RSA) to provide on -site support, including support for day-to-day desktop management types of tasks and responsibilities. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.4: System Architecture, pg. 4 A HEXAGON Deployment Model lodel The OnCall solution deployment is an automated repeatable process that does not require human intervention or manual steps. The automation of the deployments serves to provide consistency, auditable events, and the reduction of any human error. 3rd Party Partners Hexagon has proposed the following third -party partners to provide services in coordination with Hexagon's implementation team: available in Appendix A. Conn mSys for Co/n�nectClC/ASAP consulting • TDC will provide Cha nqe Management sere F. Describe the bandwidth requirements for CAD, RMS, and Mobile. Hexagon Response: OnCall runs as a website in Microsoft IIS with supporting core services. Each web client connection consumes roughly 20 Kbps, so the network between the clients and the web server must have sufficient capacity to handle all concurrent clients. The Workstation used to access the website should be on a network with a minimum of 1Mbps or higher of bandwidth. Network connectivity for Mobile Unit requires, at a minimum, 3G, or 4G connection. The application also supports wireless speeds supported by the operating system. Radio network may be supported, but radio networks have significant impact on application functionality and performance for system updates, query and report submission, and response times, and do not support the performance metrics stated within this proposal. G. Provide the total number of clients and the corresponding number of end -users of hosted systems currently supported by your company. Cloud -based CAD and RMS is cutting edge technology. Hexagon is in the process of implementing multiple cloud systems, however, there are currently no cloud systems who have completed cutover. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.4: System Architecture, pg. 5 A HEXAGON H. Describe your proposed service level agreement, including any tiered service levels, response times, and standard metrics. Hexagon Acknowledges the Consortium's request for 99.99%�system uptime. Hexagon's proposed C architecture will support a 99.95% system uptime per the loud Services Schedules, which will be provided as part of the resulting contract. Hexagon clarifies that up time in the context of this and other requirements means the ability to connect/�to the Cloud Portal, connect to the production environment, launch the application, and access Customer data. When reporting an issue to Hexagon Customer Support, the customer initially determines the priority level of the problem and, following investigation,/the priority level being raised or lowered, depending on the findings during problem investigation. The Customer Support Center has established the following priority levels and metrics for reported problems during Maintenance: PRIORITY PROBLEM DESCRIPTION RESPONSE TIME Level One Level Two Level Three Level Four • Loss of data • Data corruption • Productive use prohibited • No workaround available • Aborts • Primary purpose compromised • Productive use significantly impacted • Workaround generally not available • Productive, but incomplete operation M-F, 7:OOAM-7:OOPM Central Time — Immediate* or within 30 minutes of notification • Workarounds generally available • Productive, mainly cosmetic in nature • Workarounds or configurable options generally available M-F, 7:OOAM-7:OOPM Central Time — Immediate* o• r within one hour of notification during normal business hours M-F, 7:OOAM-7:OOPM Central Time — Immediate* o• r within eight hours of notification during normal business hours M-F, 7:OOAM-7:OOPM Central Time — Immediate* o• r within eight hours of notification during normal business hours Immediate -Without need to call back in most cases Priority Level One Errors that have no discernible workaround are escalated, when appropriate, to Cu stomer ustomer Support Management who participate in the decision -making and resolution process. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.4: System Architecture, pg. 6 A HEXAGON I. Describe your support model, including cost structure for support calls and all items covered in Section 2.20 K - Pre- and Post -Implementation Support Plan (below). Hexagon Response: Hexagon develops and markets world -class solutions for Public Safety agencies and provides integrated 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 Maintenance Program to protect the customer's investment. Hexagon provides full system support for the following: • Hexagon -developed products • Cloud services Hexagon provides complete mission -critical system coverage by offering the following Program: • • Software Upgrades • Cu stonier Support Center Cloud Services Support Cloud Services Support commences when the Consortium has been provided licenses to the Cloud software and will continue for the duration of the subscription period. Hexagon requires the subscription Cl oud to be paid annually in advance. Services Support includes access to Software Upgrades and Customer Support as described in those sections below. Software Upgrades Hexagon software feature updates are generally released on a bi-annual basis for CnCall. Upgrades of Hexagon software and documentation are provided to customers via its Cloud subscription. As part of the proposed C/ Cloud Services Support, the Consortium is entitled to receive all updates and upgrades to the Cl oud loud Application(s) and Local Software that Hexagon makes available. Cloud Consulting Services may be necessary to upgrade or update interfaces on the local interface server (i.e. CommSys), Cl oud are not part of Services Support. From time to time, Hexagon may notify the Consortium through the Cloud Portal or support website (https://support. hexagonsafetyinfrastructure.com) that Hexagon has developed an upgrade or update for the purchasedCloud 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 Cl oud or upgrade to the Development Environment for Consortium testing and review, which the Consortium shall complete within the time prescribed in the notification of the availability of the update or upgrade. In the event no material adverse effect is reported by Customer during that testing period, then on a subsequently specified/fidate by Hexagon, Hexagon will, at its discretion, deploy the update or upgrade to Consortium Cloud Environment for production. All Hexagon software releases must pass a stringent quality assurance testing process before being released for customer use. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.4: System Architecture, pg. 7 A HEXAGON Customer Support Center The Hexagon Customer Support Center is an integral part of Hexagon's Maintenance Program and is provided at no additional cost with the cost of a cloud subscription. 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 Maintenance • Response times monitored by priority Acentral 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 • Problem resolution based on priority level 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, following investigation, the priority level being raised or lowered, depending on the findings during problem investigation. The Customer Support Center has established the priority levels for reported problems during Maintenance. Those are listed above in response to Item H. Helpdesk Procedures Our Helpdesk is structured as a Tiered system. Tiered support. • Level 1 — Triage: Live helpdesk 24/7 — no recordings or callback numbers Level 2 — Americas Support: Out -of -the -box functionality support/software errors Level 3 — Global Product Center Support: Core code support including Defects or Enhancements Response to RFP 21-02 for CAD/RMS/Mobile Section 2.4: System Architecture, pg. 8 � A HEXAGON 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 a Customer Relationship Management (CRM) system for tracking technical support incidents reported by customers. First line support requests are logged into Hexagon's 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 CRM System. The system is also used to track escalations and reports are run on a regularly scheduled basis to identify escalation problems. Support staff also use the CRM 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 teleconference to view customer workflows. J. Describe your data center and storage facilities, including locations, staffing, physical security, environmental controls (including redundant power), redundancy/load balancing capabilities, data backups, and disaster recovery capabilities. Hexagon Response: Data Center and Storage Facilities 0nCall is hosted in the Azure Government Cloud. The Azure Government Cloud delivers a dedicated cloud that enables government agencies and their partners top transform mission -critical workloads to the cloud. The data center controls are maintained by Microsoft. By default, Azure SQL Database stores data in geo-redundant storage blobs that are replicated to a paired region. This helps to protect against outages impacting backup storage in the primary region and allows restoration of the server to a different region in the event of a disaster. Hexagon is bidding a hot/hot configuration that will provide seamless disaster recovery to an Azure paired Region. Locations Hexagon uses Azure Availability Zones to maintain availability. An Availability Zone is a high -availability offering that protects applications and data from datacenter failures. Availability Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there's a minimum of three separate zones in all enabled regions. The physical separation of Availability Zones within a region protects applications and data from datacenter failures. Zone -redundant services replicate your Response to RFP 21-02 for CAD/RMS/Mobile Section 2.4: System Architecture, pg. 9 A HEXAGON applications and data across Availability Zones to protect from single -points -of -failure. The OnCall solution will be deployed to the Azure US Government Cloud region paired with Virginia (currently Texas, but expected to move to Arizona by Microsoft). Staffing Microsoft Azure Government has Fed RAMP High and Department of Defense (DoD) Impact Level 4 accreditation. 5.6.2.2 of the DoD Cloud Computing Security Requirements Guide (SRG): • The minimum background investigation required for CSP personnel having access to Level 4 and 5 information based on a "noncritical -sensitive" (e.g., DoD's ADP-2) is a National Agency Check with Law and Credit (NACLC) (for "noncritical -sensitive" contractors), or a Moderate Risk Background Investigation (MBI) fora "moderate risk" position designation. • US citizenship - Verification of US citizenship. • Microsoft cloud background check (every two years) - Social Security number search, criminal history check, Office of Foreign Assets Control list (OFAC), Bureau of Industry and Security list (BIS), Office of Defense Trade Controls Debarred Persons list. • National Agency Check with Law and Credit (every five years) - Adds fingerprint background check against FBI databases. For additional information go here. • Criminal Justice Information Services (CJIS) - CJIS is a state, local and FBI government screening which processes fingerprint records and validates criminalhistories on operational staff who could be provided access to critical criminal justice information (I/CI) data. Each state does their own background check and subsequent approval of all employees with potential access to CJ I . Physical Security Response to RFP 21-02 for CAD/RMS/Mobile HEXAGON Respoo se to RFP 21-02 for CAD/RMS/Mo bile A HEXAGON Redundancy/Load Balancing Capabilities The OnCall solution is deployed to an Azure Kubernetes (K8s) cluster managed by Azure (a platform as a service (PaaS) resource). Kubernetes is an open -source container orchestration platform that enables the operation of an elastic web server framework for cloud applications. Kubernetes also automatically manages service discovery, incorporates load balancing, tracks resource allocation, and scales based on compute utilization. And, it checks the health of individual resources and enables apps to self -heal by automatically restarting or replicating containers. Data Backups Azure SQL service. This tier model is based on a cluster of database engine processes. This architectural model relies on a fact that there is always a quorum of available database engine nodes and has minimal performance impact on your workload even during maintenance activities. The hyperscale service tier is currently only available for Azure SQL Database (not SQL Managed Instance), and is a highly scalable storage and compute performance tier that leverages the Azure architecture to scale out the storage and compute resources for a database � in Azure SQL Database substantially beyond the limits available for the General Purpose and Business Critical service tiers. Azure upgrades and patches the underlying operating system, drivers, and SQL Server database engine transparently with the minimal down -time for end users. Premium availability is enabled in Premium and Business Critical service tiers and it is designed for intensive workloads that cannot tolerate any performance impact due to the ongoing maintenance operations. Compute and storage is integrated on the single node in the premium model. High availability in this architectural model is achieved by replication of compute (SQL Server database engine process) and Response to RFP 21-02 for CAD/RMS/Mobile � A HEXAGON storage (locally attached SSD) deployed to a four node cluster, using technology similar to SQL Server Always On availability groups. Both the SQL Server database engine process and underlying .mdf/.Idf files are placed on the same node with locally attached SSD storage(�providing low latency to your workload. High availability is implemented using technology similar to SQL Server Always On availability groups. Every database is a cluster of database nodes with one primary database that is accessible for customer workloads, and three The processes containing copies of data. I he primary node constantly pushes changes to the secondary nodes in order to ensure that the data is available on secondary replicas if the primary node fails for any reason. Failover is handled by the SQL Server database engine — one secondary replica becomes the primary node and a new secondary replica is created to ensure there are enough nodes in the cluster. The workload is automatically redirected to the new primary node. In addition, Business Critical cluster has built-in Read Scale -Out capability that provides free -of charge built-in read-only node that can be used to run read-only queries (for example reports) that should not affect performance of your primary workload. K. Describe your logical security, including firewall security, authentication controls, and data encryption capabilities. Response to RFP 21-02 for CAD/RMS/Mobile / HEXAGON The two types of service principals used by Hexagon are: Application This type of service principal is the local representation, or application instance, of a global application object in a single tenant or directory. In this case, a service principal is a concrete instance created from the application object and inherits certain properties from that application object. A service principal is created in each tenant where the application is used and references the globally unique app object. The service principal object defines what the app can actually do in the specific tenant, who can access the app, and what resources the app can access. When an application is given permission to access resources in a tenant (upon registration or consent), a service principal object is created. When you register an application using the Azure portal, a service principal is created automatically. Graph, can also create service principal objects in a tenant using Azure PowerShell, Azure CLI, Microsoft Graph, and other tools. Managed identity This type of service principal is used to represent a managed identity. Managed identities eliminate the need for developers to manage credentials. Managed identities provide an identity for applications to use when connecting to resources that support Azure AD authentication. When a managed identity is enabled, a service principal representing that managed identity is created in your tenant. Service principals representing managed identities can be granted access and permissions, but cannot be updated or modified directly. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON L. Describe your change management, upgrade, and patch management policies and practices to include dot releases and full release upgrades, including frequency of required updates. Hexagon Response: Monthly maintenance, patches, and upgrades to cloud infrastructure will be performed by Hexagon's Managed Service Cloud Operations Team (GPC). Hexagon software feature updates are generally released on a bi-annual basis for OnCall. Upgrades of Hexagon software and documentation are provided to customers via its Cloud subscription. As part of the proposed Cloud/Services Support, the Consortium is entitled to receive all updates and upgrades to the Cl oud loud Applications) and Local Software that Hexagon makes available. Cloud Consulting Services may be necessary/�to upgrade or update interfaces on the local interface server (i.e. CommSys), C which are not part of loud Services Support. From time to time, Hexagon may notify the Consortium through the Cloud Portal or support website (https://support(. Cloud that Hexagon has developed an upgrade or update for C the purchased loud 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 Cl oud or upgrade to the Development Environment for Consortium testing and review, which the Consortium shall complete within the time prescribed in the notification of the availability of the update or upgrade. In the event no material adverse effect is reported by Customer during that testing period, then on a subsequently specified date by Hexagon, Hexagon will, at its discretion, deploy the update or Cl oud to Consortium Environment for production. All Hexagon software releases must pass a stringent quality assurance testing process before being released for customer use. M. Describe your systems administration/management capabilities, including monitoring of performance measures, intrusion detection, and error resolution. Hexagon leverages a combination/�of Azure Security Center and Log Analytics to monitor our systems and services. Azure Security Center is a unified infrastructure security management system that provides advanced threat protection for workloads in the cloud. The Azure Log Analytics agent collects telemetry from /Windows and Linux virtual machines in any cloud, on -premises machine, and those monitored by System Center Operations Manager and sends its collected data to Log Analytics workspace in Azure Monitor. The Log Analytics agent also supports/p insights and other services in Azure Monitor such as Azure Monitor for VMs, Azure Security Center, and Azure Automation. Currently in Preview, Azure Monitor Agent will be leveraged once it reaches General Availability. The Azure Monitor agent (AMA) collects monitoring data from the guest operating system of virtual machines and delivers it to Azure Monitor. The Azure Monitor Agent replaces the following agents that are currently used by Azure Monitor to collect guest data from virtual machines: Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON • Log Analytics agent - Sends data to Log Analytics workspace and supports Azure Monitor for VMs and monitoring solutions. • Diagnostic extension - Sends data to Azure Monitor Metrics (Windows only), Azure Event Hubs, • In addition to consolidating this functionality into a single agent, the Azure Monitor Agent provides the following benefits over the existing agents: • Scope of monitoring: Centrally configure collection for different sets of data from different sets of VMs. • Linux multi -homing: Send data from Linux VMs to multiple workspaces. • Windows event filtering: Use XPATH queries to filter which Windows events are collected. Improved extension management: Azure Monitor agent uses a new method of handling extensibility that is more transparent and controllable than management packs and Linux plug -ins in the current Log Analytics agents. N. if the System is not cloud -based: 1. Does the System run in a virtualized environment? The current architecture environment should be VMware 6.5 or higher. Hexagon Response: N/A — Hexagon has proposed a cloud -based solution. 2. Describe the approach for maintaining the current version of VMware. Hexagon Response: N/A — Hexagon has proposed a cloud -based solution. 3. The System should be fault -tolerant for high availability and disaster recovery. Describe which components cannot be virtualized, if any, and provide an explanation why. Hexagon Response: N/A — Hexagon has proposed a cloud -based solution. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON 4. Do operations automatically failover to the High Availability environment should operations in the production environment fail? N/A — Hexagon has proposed a cloud -based solution. 5. What steps, degree of user intervention, and time is required to return operations to the primary environment? N/A — Hexagon has proposed a cloud -based solution. O. Describe how the System scales with no performance degradation to function across the six Consortium's geographically dispersed Communication Centers. Hexagon OnCall suite is comprised of web -based applications, users with an active account may log in from a supported browser and device at any location within the Consortium. P. /f a Consortium agency's Communication Center location becomes inoperable, from a System perspective, describe how members of that Communication Center can move to an alternate location and resume System functions. Hexagon Response: In this scenario Consortium members could move to a workstation at any alternate location and log in to resume system functions with the same access to features and information as they had at their original location. Q. Describe the Proposer's history in serving multiple PSAP locations (e.g., primary and multiple secondary PSAPs), ensuring consistently optimized system performance at all locations. Hexagon does have experience serving multi-agency/multi-PSAP Customers. With the OnCall suite access in the cloud is not limited by physical location of the system. Users from multiple PSAPS and agencies who have been granted access to the system may login and use the system from any location. This provides flexibility and reliability that customers such as the Consortium would benefit from. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Section 2.5 — Performance and Reliabilitv A. Describe the proposed System High Availability (HA) model and plan. Hexagon uses Azure Availability Zones to maintain availability. An Availability Zone is a high -availability offering that protects applications and data from datacenter failures. Availability Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there's a minimum of three The zones in all enabled regions. I he physical separation of Availability Zones within a region protects applications and data from datacenter failures. Zone -redundant services replicate your applications and data across Availability Zones to protect from single -points -of -failure. To achieve comprehensive business continuity on Azure, our application architecture uses the combination of Availability Zones with Azure region pairs. Azure Region 5, ME Availability Zone T =11m97 Availability Zone 3 Availability Zone 2 B. Describe any impact to the System (e.g., system shutdown, reboot) and System use that will occur during: 1. Server upgrades N/A - Hexagon's cloud solution eliminates the burden of downtime during server upgrades. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.5: Performance and Reliability, pg. 1 � A HEXAGON 2. Software Upgrades/Updates Hexagon Response: Hexagon's cloud solutions require minimal scheduled downtime. The Consortium can expect downtime to happen during the following events: • Monthly maintenance of Hexagon applications and patches received from Microsoft are applied to Hexagon cloud environments. • The two major OnCall releases per year are deployed. These deploy as parallel upgrades to reduce or eliminate downtime. Hexagon endeavors to provide advance notice of any intended downtime, however, in emergency maintenance circumstances, Hexagon may not be able to provide such advance notice. C. All System components are expected to operate concurrently. How will Proposer ensure concurrent operations of all System components without any System degradation? Hexagon Response: OnCall Dispatch and OnCall Records are part of a unified full suite of products built upon Hexagon's 30+ years of public safety experience that are used throughout the world. These CAD, RMS, mobile and analytics products are optimized to work in tandem without system degradation. All OnCall products utilize web -based technologies. OnCall Dispatch and Mobile Unit use the same technology code base. Mobile Responder is a different code base since it is app-based — however, Mobile Responder is fully integrated with the OnCall suite through industry -standard Rest APIs. Similarly, OnCall Records uses a different code base but has full integration with the other OnCall products. Hexagon's Global Product Center (GPC) and its technical leadership and product owners collaborate with every feature and product release with governance provided by an architectural review board. D. The System is expected to be available 99.99 percent of the time. Describe how the Proposer will guarantee this level of System availability both initially and during the life of the agreement. Hexagon Response: Hexagon supports 99.95% uptime per the Cloud Services Schedules, which will be provided as part of the resulting contract. Hexagon clarifies that up time in the context of this and other requirements means the ability to connect to the Cloud Portal, connect to the production environment, launch the application, and access Customer data. 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: Response to RFP 21-02 for CAD/RMS/Mobile Section 2.5: Performance and Reliability, pg. 2 / HEXAGON Hours of Cloud Program Ave Hours of Cloud Program Availability + downtime hours for such Month which are not related to an Exception x 100 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. If the Service Operational Time does notwrise to the applicable Service Level within the Go Green Period, C then the Service Credit provided in the loud Service Schedule will be applied against each Month in which the Service Operational Time remains below such Service Level. • Only as specified within the Cloud Services Schedule, • Only to the extent that the affected Customer Environment is used in Production; • In strict accordance/�with response � to item c above • 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 ▪ Only where Customer is compliant with the AUP. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.5: Performance and Reliability, pg. 3 A HEXAGON Section 2.6 — System Backup A. Describe the Proposer's recommended approach for System backup, data options, and availability. Hexagon Response: How do you maintain availability between the various azure regions? Hexagon uses Azure Availability Zones to maintain availability. An Availability Zone is a high -availability offering that protects applications and data from datacenter failures. Availability Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there's a minimum of three The zones in all enabled regions. I he physical separation of Availability Zones within a region protects applications and data from datacenter failures. Zone -redundant services replicate your applications and data across Availability Zones to protect from single -points -of -failure. To achieve comprehensive business continuity on Azure, our application architecture uses the combination of Availability Zones with Azure region pairs. Availability Zone 1 Azure Region WWI 4r ®* Availability 'Lane 3 Availability Zone 2 Azure SQL Service and Backup Azure SQL Database is the relational database service built for the cloud. It is evergreen and always up to date, with AI -powered and automated features that optimize performance. Serverless compute and Hyperscale storage options automatically scale resources on demand scheduling backups and retention time. By default, Azure SQL Database stores data in geo-redundant storage blobs that are replicated to a paired region. This helps to protect against outages impacting backup storage in the primary region and allows restoration of the server to a different region in the event of a disaster. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.6: System Backup, pg. 1 /HEXAGON Storage redundancy mechanisms store multiple copies of your data so that it is protected from planned and unplanned events, including transient hardware failure, network or power outages, or massive natural disasters. The configured backup storage redundancy is applied to both short-term backup retention settings that are used for point in time restore (PITR) and long-term retention backups used for long-term backups (LTR). System backups are included in the technology stack leveraged on the Azure cloud. The OnCall solution leverages an Azure SQL Database which use SQL Server technology to create full backups every week, differential backups every 12-24 hours, and transaction log backups every 5 to 10 minutes. The frequency of transaction log backups is based on the compute size and the amount of database activity. These backups enable database restore to a point in time within the configured retention period. The backups are stored as RA-GRS storage blobs that are replicated to a paired region for protection against outages impacting backup storage in the primary region. B. How will the Proposer's recommended System backup affect the five operation of the System? Hexagon Response: Due to the architecture and the PaaS resources used within the OnCall application, system backups are not required. Hexagon has proposed a highly available configuration which includes the OnCall solution deployed in Cl oud. data centers on the Azure Government Data centers within a region provide a latency - defined perimeter and connected through a dedicated low -latency network. An Availability Zone is a high availability offering that protects the OnCall applications and data from datacenter failures. Availability Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there is a minimum of three separate zones in all enabled regions. The physical separation of Availability Zones within a region protects applications and data from datacenter failures. Zone -redundant services replicate applications and data across Availability Zones to protect from single -points -of -failure. There is no need to provide a system back-up with this configuration as there is redundancy built into the deployment architecture. In addition to the use of Availability Zones, Hexagon is proposing a Hot/Hot configuration with traffic routed and balanced between the two Azure Paired Regions. Failing to the paired Region in this case will be seamless. The combination of spreading the OnCall solution across multiple datacenters within each Region will provide the Consortium the availability and resilience required for a public safety solution. Hexagon OnCall includes the Business Critical tier of Azure SQL Service which uses SQL Server technology to create full backups every week, differential backups every 12-24 hours, and transaction log backups every 5 to 10 minutes. The frequency of transaction log backups is based on the compute size and the amount of database activity. When a database is restored, the service determines which full, differential, and transaction log backups need to be restored. (RTO) Recovery Time Objective RTOis less than 5 minutes. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.6: System Backup, pg. 2 A HEXAGON (RPO) Recovery Point Objective (in hours) RPOis less than 5 minutes. C. Are all System functions available during backup? If not, explain the level of availability of the System function during backup. Hexagon Response: All System functions are available during backup activities. No affect. D. Will the Proposer's recommended approach for System backup enable a full backup of the System? If so: 1. What is the maximum time a full backup will take? 2. Can the full backup be performed unattended? System backups are included in the technology stack leveraged on the Azure cloud. The OnCall solution leverages an Azure SQL Database which use SQL Server technology to create full backups every week, differential backups every 12-24 hours, and transaction log backups every 5 to 10 minutes. The frequency of transaction log backups is based on the compute size and the amount of database activity. The backup tasks are automated and are performed in the background and are performed unattended. These backups enable database restore to a point in time within the configured retention period. The backups are stored as RA-GRS storage blobs that are replicated to a paired region for protection against outages impacting backup storage in the primary region. Storage redundancy mechanisms store multiple copies of your data so that it is protected from planned and unplanned events, including transient hardware failure, network or power outages, or massive natural disasters. The configured backup storage redundancy is applied to both short-term backup retention settings that are used for point in time restore (PITR) and long-term retention backups used for long-term backups (LTR). Response to RFP 21-02 for CAD/RMS/Mobile Section 2.6: System Backup, pg. 3 A HEXAGON Section 2.7 — System Recovery A. Describe the proposed method of restoring data files. System backups are included in the technology stack leveraged on the Azure cloud. The OnCall solution leverages an Azure SQL Database which use SQL Server technology to create full backups every week, differential backups every 12-24 hours, and transaction log backups every 5 to 10 minutes. The frequency of transaction log backups is based on the compute size and the amount of database activity. These backups enable database restore to a point in time within the configured retention period. The backups are stored as RA-GRS storage blobs that are replicated to a paired region for protection against outages impacting backup storage in the primary region. B. Describe the process for recovering the system to a particular point in time. How will the Proposer support a fifteen -minute or less Recovery Point Objective (RPO)? Hexagon has proposed a Highly Available (HA) Production Configuration which/�includes instances of the OnCall solution executing in multiple data centers in the Azure Government Cloud. The instances provide redundancy in the case of one of the instances goes down. The three data centers are connected via a dedicated low -latency network to ensure the instances are synchronized. In addition to the use of Availability Zones, Hexagon has proposed a Hot -Hot configuration with an additional zonally aware instance of OnCall running in a paired Region of Azure. These instances will both be operational with Azure Traffic Manager (ATM) routing the traffic between the OnCall instances, providing a hot failover to the Secondary instance if the Primary were to be unavailable. The Business Critical Azure SQL Service included in the Hexagon solution leverages the Premium availability model, which integrates compute resources (sqlservr.exe process) and storage (locally attached SSD) on a single node. High availability is achieved by replicating both compute and storage to additional nodes creating a three to four -node cluster. The SQL Managed Instance use SQL Server technology to create full backups every week, differential backups every 12-24 hours, and transaction log backups every 5 to 10 minutes. The frequency of transaction log backups is based on the compute size and the amount of database activity. By default, SQL Database and SQL Managed Instance store data in geo-redundant storage blobs that are replicated to a paired region. Geo-redundancy helps to protect against outages impacting backup storage in the primary region and allows you to restore your server to a different region in the event of a disaster. (RTO) Recovery Time Objective RTOfor the solution is under 5 minutes. (RPO) Recovery Point Objective (in hours) The RPO is under 5 minutes, less than one hour. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.7: System Recovery, pg. 1 A HEXAGON C. During the restore process, will any functionality be lost or limited? Hexagon Response: No, because Hexagon is bidding a Hot -Hot configuration, there is no restoration required as the secondary system is fully operational at all times. This proposed configuration guards the Consortium against any loss of functionality during a restore process. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.7: System Recovery, pg. 2 A HEXAGON Section 2.8 • Operating System A. The Consortium and partner agencies have standardized on Microsoft Windows Server 2019 and Windows 10 for clients. Does the proposed solution comply with this standard? Hexagon Response: Yes, Hexagon's proposed solution is optimized for Windows 10 clients. While Windows Server 2019 is Hexagon's standard for on -premise systems, Hexagon's proposed cloud system utilizes Microsoft Azure. B. How does the Proposer intend to maintain currency with Windows operating systems? Hexagon Response: N/A Hexagon's proposed solution is optimized for Windows 10 clients. While Windows Server 2019 is Hexagon's standard for on -premise systems, Hexagon's proposed cloud system utilizes Microsoft Azure. C. Provide the name and version number of the current proposed Operating Systems (servers and clients). Hexagon Response: N/A Hexagon's proposed solution is optimized for Windows 10 clients. Hexagon's proposed cloud system utilizes Microsoft Azure. D. Provide proposed timelines for keeping the System current with standard Operating Systems over the next five years. Hexagon Response: N/A since Hexagon is proposing a cloud -based solution. Hexagon's proposed solution is optimized for Windows 10 clients. Hexagon's proposed cloud system utilizes Microsoft Azure. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.8: Operating System, pg. 1 A HEXAGON E. /f the Proposer's recommended operating system incorporates any proprietary or non-standard components, provide justification for the component (server and clients). Hexagon Response: Hexagon has not proposed any proprietary or non-standard components for the operating system. The OnCall application suite is a combination of Cloud native/frameworks and Cloud PaaS services that together provide availability, stability, and elasticity in the (�Cloud environment. OnCall leverages Azure Kubernetes Service,/Cloud Active Directory and Azure SQL Service across Availability Zones coupled with Azure Security Center to provide our customers with the best of breed solution. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.8: Operating System, pg. 2 A HEXAGON Section 2.9 — Software License Agreement The Consortium cannot overemphasize the importance of enterprise licensing (site license) for the System. Although there may be restrictions and limitations, unlimited use of the System throughout the Consortium is preferred. A. include copies of the proposed standard software licensing agreement. Hexagon has includeda link to Master Terms in Appendix E of this proposal. The Master Terms provide Cl oud provisions for the subscription as well as services. B. Does the Proposer provide the preferred site license option(s) for all System components proposed? if not, p/ease identify those components for which site licensing is not an option and indicate why a site license would not be the most cost-effective option. Hexagon Response: Hexagon's Enterprise/Site License is licensed by defined agencies, products, and size of the cloud environment. Our Hexagon Enterprise/Site License does not have user counts restrictions for Hexagon's products. The cloud � environment is sized based on the number of users described in the RFP. However, as provided in the Cloud Schedules within the resulting contract, there are certain parameters on the Cloud applications, such as database Consortium would purchase the additional capacities. The Hexagon Enterprise/Site License is licensed to, and only to, the following agencies: • Pinellas County Sheriff's Office Secondary PSAP with Redington shores • St. Petersburg Police Department Secondary PSAP • Clearwater Police Department Secondary PSAP • Largo Police Department Secondary PSAP • Pinellas County Regional 9-1-1 Communications Center Primary PSAP* Response to RFP 21-02 for CAD/RMS/Mobile Section 2.9: Software License Agreement, pg. 1 A HEXAGON *Hexagon Enterprise/Site License includes the annual usage of Onl..a 11 for the R911 Primary PSAP for the Fire/EMS functionality requested in Addendum 1 for this RFP. Additional items related to that addendum will be forthcoming as part of Hexagon's Fire/EMS proposal response. Hexagon has included a system configuration diagram in Appendix C that depicts items included in the site license. The following system components are not included in the site license. • Third party products below are not included in the site license. These products are subject to licensing terms of the third parties and are subject to variables Hexagon can not control, including the number of Consortium personnel who will need to use or access these products. CommSys ConnectCll • Dynamo eLearning licenses are not included in the site license because these licenses incorporate third party services and they are licensed according to a named user model. Hexagon has proposed a bucket of these Dynamo licenses for the Consortium to use for training with our C. What type of licensing agreement is proposed (e.g., concurrent, named, etc.), and the number of licenses proposed for each application: 1. CAD 2. Mobile 3. RMS Hexagon Response: Hexagon has proposed a site license for each of these products as described in the response to item B above. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.9: Software License Agreement, pg. 2 A HEXAGON Section 2.10 — Cybersecurity / Information Security A. Describe to what level of depth security and permissions may be controlled within an application module (e.g., field, module, application, or system, etc.). 1. Describe the security requirements for the Intelligence module 2. Describe the security requirements for the Narcotics module 3. Describe the security requirements for the Property and Evidence module Hexagon Response: OnCall Records provides administrators with the ability to create agencies and subordinate to each agency, users, groups, and roles are created. Each role allows administrators to define security for read and write access, through custom security rights by table. OnCall Records provides the ability to leverage the/�configurations for each agency within the system. Each agency can manage and maintain Screen Customizations, Field Label Customizations, Workflows, Alerts, and Permission Groups. However, at the time of implementation, agencies will determine whether key Master Modules will be shared between the B. Describe the cybersecurity deployed with the solution 1. Infrastructure Hexagon Response: The security of our cloud hosted applications is of the utmost importance to Hexagon. To ensure the security of our products and our hosted environments, a set of policies and best practices are adhered to and combined with a series of controls, monitoring tools, and analytics that are put in place to ensure compliance, auditing, issue transparency, and expedient resolution in the event of an incident. The polices and controls are a shared responsibility between the cloud hosting vendor, the customer, and Hexagon. Azure provides a logical isolation of the cloud dedicated to a subscription or resource group via Virtual Network (VNet) or Virtual Private Cloud (VPC). Each VNet you create has its own CIDR block, and can be linked to other VNets or VPC as well as on -premises networks as long as the CIDR blocks do not overlap. Control of DNS server settings for and segmentation of these private networks into subnets. With the use of VPC and VNet each OnCall environment can be secured and isolated from the other. The ability to add an additional layer of security to data at rest in the cloud is available via data encryption capabilities available in storage and database services. Provided key management options allow for management of any encryption keys. Azure provides several security capabilities and services to increase privacy and control network access. These include: Response to RFP 21-02 for CAD/RMS/Mobile Section 2.10: Cybersecurity/Information Security, pg. 1 � A HEXAGON • Network firewalls built into VPC • Web application firewall capabilities in WAF let you create private networks and control access instances and applications • Connectivity options that enable private, or dedicated encrypted connections Customer 2. Application (data encryption, tokenization, etc.) Hexagon Response: Hexagon uses its DevCloud platform to ensure its applications ands their developers follow industry best practices for code development, security, and test coverage. DevCloud is acombination of Azure DevOps for managing the Continuous -Integration Continuous -Delivery (CI -CD) pipeline, including automated build processes that include integrated tools and containerized build environments. Azure DevOps includes the code repositories, the workflow and work management tools in a scalable available distributed globally accessible environment. DevCloud uses SonarQube to automate code reviews and security scans and enforce test code coverage thresholds. Using SonarQube to automate the enforcement of coding standards and security best allows lead engineers to focus their code reviews on more complex code issues and architectural standards. If during the build process any of the scans fails, the build itself is denied until the issues identified during the scan are addressed. DevCloud includes using BlackDuck scans in the release process. BlackDuck reviews code repositories and build and release artifacts, and identifies any vulnerabilities associated with the use of third -party libraries and Open Source Software (OSS). Identified vulnerabilities can include both license and security issues. Using the Hexagon DevCloud and its automated enforcement of quality and security best practices has greatly improved our CI -CD processes and the quality of our released products. The CAD system is developed following an ISO9001 quality management system and application security program based on ISO27001 and ISO270034. Hexagon also follows an audited GDPR-compliance program. The CAD SaaS offering follows an operational process based on SSAE 16 controls. OnCall is hosted in the Azure Government Cloud. The Azure Government Cloud delivers a dedicated cloud that enables government agencies and their partners to transform mission -critical workloads to the cloud. Azure Government services handle data that is subject to certain government regulations and requirements, such as FedRAMP, NIST 800.171 (DIB), ITAR, IRS 1075, DoD L4, and CJIS. In order to provide customers with the highest level of security and compliance, Azure Government uses physically isolated datacenters and networks (located in U.S. only). Response to RFP 21-02 for CAD/RMS/Mobile Section 2.10: Cybersecurity/Information Security, pg. 2 A HEXAGON 3. Transport Hexagon Response: The data will be encrypted in transit within Azure Government cloud. Data in transit to and from the Azure Government cloud can be encrypted using TLS, or a dedicated VPN connection can be utilized as an option if desired. C. Describe your cybersecurity posture and your compliance with relevant security standards (e.g., NIST, /SO 27000, CJIS). Hexagon Response: Hexagon has been approved by Lloyd's Register to the following standards. ISO/IEC 27001:2013. Issue date: 30 September 2020, expiry date 29 September 2023. OnCall is hosted in the Azure Government Cloud. The Azure Government Cloud delivers a dedicated cloud that enables government agencies and their partners to transform mission -critical workloads to the cloud. Azure Government services handle data that is subject to certain government regulations and requirements, such as FedRAMP, NIST 800.171 (DIB), ITAR, IRS 1075, D0D L4, and CJIS. In order to provide customers with the highest level of security and compliance, Azure Government uses physically isolated datacenters and networks (located in U.S. only). Microsoft signs a CJIS Management Agreement with state CISOs that satisfies the CJIS requirements for audits and background check so that every law enforcement agency in a state can leverage the Microsoft cloud platforms to manage criminal justice information while meeting its own CJIS obligations. Through this agreement —which also includes the CJIS Security Addendum — Microsoft contractually commits to implementing all of the controls and processes required under the CJIS Security Policy. D. What cybersecurity features prevent unauthorized access to the System or system data? Hexagon Response: The OnCall solution leverages multiple layers of security and secure processes to ensure that only authorized access to the system is allowed. There are typically seven layers of cybersecurity concerns when it comes to protecting mission critical systems. The OnCall solution secures the seven layers in the following manner: Physical/Perimeter Security is managed by Microsoft at the Azure Government Data centers. Microsoft takes a layered approach to physical security, to reduce the risk of unauthorized users gaining physical access to data and the datacenter resources. Datacenters managed by Microsoft have extensive layers of protection: access approval at the facility's perimeter, at the building's perimeter, inside the building, and on the datacenter floor. Layers of physical security are: • Access request and approval. You must request access prior to arriving at the datacenter. You're required to provide a valid business justification for your visit, such as compliance or auditing purposes. All requests are approved on a need -to -access basis by Microsoft employees. A need - Response to RFP 21-02 for CAD/RMS/Mobile Section 2.10: Cybersecurtty/Information Security, pg. 3 A HEXAGON to -access basis helps keep the number of individuals needed to complete a task in the datacenters to the bare minimum. After Microsoft grants permission, an individual only has access to the discrete area of the datacenter required, based on the approved business justification. Permissions are limited to a certain period of time, and then expire. • Facility's perimeter. When you arrive at a datacenter, you're required to go through a well-defined access point. Typically, tall fences made of steel and concrete encompass every inch of the perimeter. • Building entrance. The datacenter entrance is staffed with professional security officers who have undergone rigorous training and background checks. • Inside the building. After you enter the building, you must pass two -factor authentication with biometrics to continue moving through the datacenter. If your identity is validated, you can enter only the portion of the datacenter that you have approved access to. You can stay there only for the duration of the time approved. • Datacenter floor. You are only allowed onto the floor that you re approved to enter. You are required to pass a full body metal detection screening. To reduce the risk of unauthorized data entering or leaving the datacenter without our knowledge, only approved devices can make their way into the datacenter floor. When you exit the datacenter floor, you again must pass through full body metal detection screening. To leave the datacenter, you're required to pass through an additional security scan. Network Security is provided by both the Azure Platform and the OnCall solution architecture. Azure provides the tools for securing the network, and OnCall takes advantage of them. The OnCall solution is protected by a combination of Firewalls, Application Gateways, Network Security Groups (NSG), Virtual Networks (Vnet) and AAD managed Service Principles. Using the Azure tools, the OnCall solution provides multiple layers of network protection which is validated and verified via 3rd party penetration tests for every major OnCall cloud release. Endpoint Security is provided the OnCall cloud architecture leveraging the existing Network security mechanisms such as closed Vnets andfirewalls combined with Application Gateways and any endpoints that are exposed are secured via OIDC tokens. Additionally, OnCall uses Azure Security to monitor end- points and fire alerts for any unusual network traffic or multiple failed endpoint access attempts. Data Security is provided in multiple ways within the OnCall Solutions. Data in motion is secured through TLSencryption at the transport layer to the Azure platform, and then because Hexagon leverages Azure Government Cloud, traffic on the Azure platform behind the gateway between the Azure services and OnCall deployed resources is also encrypted. Data at rest is secured at the Database level using TDE and by ensuring there is no access provided to the Production Database unless approved by the Agency and their security team. Access keys and tokens to the Database are secured using a combination of Azure Key Vaults and AAD service principles. Application Security is provided in a multi -facet approach. Hexagon leverages Azure DevOps for configuration management and build and deploy pipelines. Azure DevOps uses Azure Storage as the primary repository for service metadata andcustomerdata. Depending on the type of data and the storage and retrieval needs, we use Azure Blob (binary large objects) storage and Azure SQL data storage. Administrators can manage access to resources by granting or restricting permissions on user identities or groups. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.10: Cybersecurity/Information Security, pg. 4 � A HEXAGON Azure DevOps uses federated authentication of user identities via Azure Active Directory (Azure AD) and Microsoft Accounts (MSA, formerly LivelD). During authentication, the user is routed to the authentication provider (Azure AD or MSA) where they provide their credentials. Once the authentication provider has verified the users credentials, Azure DevOps issues an authentication cookie to the user, which allows them to remain authenticated against Azure DevOps. In this way, the users credential information is never shared directly with Azure DevOps. For each Azure DevOps resource that the user attempts to access, permissions are validated based on the user's explicit permissions as well as permissions inherited through group membership. Azure DevOps leverages many of the Azure storage features to ensure data availability in thecase of hardware failure, service disruption, or region disaster. DevOps personnel who manage the Cl/CI pipeline are provided access to only those assets they have need to use to complete their job. All DevOps tools and utilities are secured, and only authorized personnel have access to the appropriate level of authority required to do their job. All code repositories are secured using Azure Active Directory coupled with defined permissions to read, edit and approve code merges. Azure DevOp security groups and their actions are audited within the Azure DevOps ecosystem, with access to the underlying logs via Azure DevOps ODATA API. Leveraging Azure Container Registry (ACR) allows the DevOps team to manage the configuration of apps isolated from the configuration of the hosting environment. Images are kept safe by authenticating and managing access with Azure Active Directory. Hexagon's DevOps platform includes integrated Static Application Security Testing (SAST) executed at the Build level that if not passed, will block the code from being merged into the code repository. Open Source Software (OSS) vulnerability scans are performed on a weekly basis. Dynamic Application Security Tests (DAST) are performed prior to software release and all web facing applications undergo a Penetration Test by a 3rd party vendor prior to every major release. Human Security is provided with a combination of AAD permissions, access control and security processes. All the OnCall cloud deployments are automated with no need for Human intervention. Additionally, all credentials, keys or secrets are stored in Azure Key Vault and are managed by the deployment process itself. The keys are rotated on a predetermined interval and are managed by the Azure Government Cloud. Because the deployments are automated, there is no need to share credentials with the Operational team that will manage and monitor your OnCall cloud solution. The AAD accounts used by Hexagon personnel are elevated AAD accounts (P2). P2 has Identity Protection, which allows the management of conditional access to apps. Secondly, P2 also provides Privileged Identity Management (PIM). Mission Critical Assets is the innermost layer, and it encompasses the assets that are critical to the Consortium. This layer is protected by the 6 layers described above. E. What cybersecurity features prevent computer viruses, hidden "logic bombs," "back doors, "or any other such code that could be activated inadvertently or otherwise at a later date or time? Hexagon Response: Hexagon uses its DevCloud platform to ensure its applications and their developers follow industry best practices for code development, security, and test coverage. DevCloud is acombination of Azure DevOps for managing the Continuous -Integration Continuous -Delivery (CI -CD) pipeline, including automated build processes that include integrated tools and containerized build environments. Azure Response to RFP 21-02 for CAD/RMS/Mobile Section 2.10: Cybersecurtty/Information Security, pg. 5 � A HEXAGON DevOps includes the code repositories, the workflow and work management tools in a scalable available distributed globally accessible environment. DevCloud uses SonarQube to automate code reviews and security scans and enforce test code coverage thresholds. Using SonarQube to automate the enforcement of coding standards and security best allows lead engineers to focus their code reviews on more complex code issues and architectural standards. If during the build process any of the scans fails, the build itself is denied until the issues identified during the scan are addressed. DevCloud includes using BlackDuck scans in the release process. BlackDuck reviews code repositories and build and release artifacts, and identifies any vulnerabilities associated with the use of third -party libraries and Open Source Software (OSS). Identified vulnerabilities can include both license and security issues. Using the Hexagon DevCloud and its automated enforcement of quality and security best practices has greatly improved our CI -CD processes and the quality of our released products. The CAD system is developed following an ISO9001 quality management system and application security program based on ISO27001 and ISO270034. Hexagon also follows an audited GDPR-compliance program. The CAD SaaS offering follows an operational process based on SSAE 16 controls. F. What cybersecurity features prevent ransomware from encrypting System data? What guarantees against successful ransomware attacks are provided? Hexagon Response: OnCall leverages Azure Security Center which includes multiple tools, monitors and alerting that are integrated with the deployed OnCall solution which enables continuous 24x7 oversight and protection. Security Center assesses your environment and provides status views of resources, and whether they are secure. It protects against threat by assessing your workloads and raises threat prevention recommendations and security alerts. Security Center also provides real-time threat protection for containerized environments and generates alerts for suspicious activities. At the cluster level, the threat protection is based on analyzing Kubernetes' audit logs. Hexagon Cloud Operations uses these alerts and monitoring features to ensure our solution and your deployment is secure and protected. Security Center analyzes data from the following sources to provide visibility into your security state, identify vulnerabilities and recommend mitigations, and detect active threats. • Azure services: Uses information about the configuration of Azure services you have deployed by communicating with that service's resource provider. ® Network traffic: Uses sampled network traffic metadata from Microsoft's infrastructure, such as source/destination IP/port, packet size, and network protocol. • Partner solutions: Uses security alerts from integrated partner solutions, such as firewalls and antimalware solutions. • Your machines: Uses configuration details and information about security events, such as Windows event and audit logs, and syslog messages from your machines. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.10: Cybersecurity/Information Security, pg. 6 A HEXAGON G. Describe what security functions are supported by security within the application software versus those provided by system software or the operating system. Hexagon Response: Application Security Records OnCall Records security does not rely on underlying operating systems to provide access control. In addition to enforcing user IDs and passwords, the OnCall Records(`security system allows system administrators to control system and data access for Users and Groups by locking individual modules, tabs, records, and attachments. Proper use of the built-in security functions allows the system administrator(s) to fine-tune a system in which sensitive data is available only to authorized users. To facilitate security management, OnCall Records provides an interactive utility that allows administrators to establish an unlimited number of Security Gr oups, Using the Administration > Users, and Roles utilities, administrators can assign the capabilities (Roles) allowed for each Security Permission Group, for every module, tab, and individual record in the system. In addition, administrators can control access to any attachments (documents, photos, videos, and so forth) linked to module records. When a new user account is established, that user will be assigned to a Permission Group and the account will inherit all security Roles applied to that Group. There is no limit to the number of Permission Groups or the number of users that can be assigned to the group. Administrators can give users and/or groups one of the following access options for modules, tabs, attachments, data sheets, and other features. • None. No access • Read: Read-only access • Write. Read and edit access • /Amin. Read, edit, and delete access • l..ustom: Specify an access option for each module and attachment type and tab By implementing security down to tab and feature levels, administrators can render any sensitive content invisible to any user. For example, a department administrator may require that a group of data entry users be able to access the Employee Module in order to keep employee records up to date. However, confidential data such as compensation, disciplinary actions, and associated paperwork can be made invisible to those users. OnCall Records provides additional security features. OnCall Records permits the ability to establish access rights down to the specific Attachment type within a record. For example, Users may have access to Evidence Images but not Autopsy Photos. Attachment access is governed at the overall Permission Group level. However, extended features support the ability for an investigator or officer to selectively secure an attachment to specific permission groups manually to accommodate special Case Investigators and officers are also provided the ability to secure an Incident or Case report to specific Permission Groups manually when the record contains sensitive information. In the event that Response to RFP 21-02 for CAD/RMS/Mobile Section 2.10: Cybersecurity/Information Security, pg. 7 � A HEXAGON the Incident or Case is not secured, an investigator or an officer can use the OnCall Records Alerts feature to be notified when a user accesses a particular record. OnCall Records provides access security. The application supports the CJIS Strong password requirements. Additional CJIS user policies are met such as password renewal, password re -use, restrictions on multiple user sessions, and limited logon failure attempts. Encryption of the data outside of the sites' secured LAN is through their network or cellphone provider. Data -at -rest on the laptop requires the site to use the Encrypting File System feature or a third -party product such as Symantec PGPWhole Disk Encryption, Lumension, or Check Point Fun Disk Encryption. Iwo -factor authentication is performed through the operating system and assumes the use of Active Directory centralized user access management. OnCall Di s patcln Designed around groups and roles, HxGN OnCall Dispatch defines the following basic concepts to explain security levels and permissions in the system. • Users - A user is an individual authorized to access the HxGN OnCall Dispatch system. • Groups - A group is set of users. Groups can contain users, otheroIgroups, or both. A group has an associated action role and data role. A user has a default HxGN OnCall Dispatch group. • Roles - A role defines a set of permissions. Roles can inherit permissions from other roles. There are two types of rolesaction roles and data roles. • Permissions - A permission is a specific command or level of access that a role grants. Permissions come in two forms. action permissions and data permissions. Action permissions let users run specific commands, such as Create Event and Dispatch Unit. Action permissions are associated with action roles. Data permissions let users view data for agencies and dispatch groups. For example, being able to cover a specific dispatch group is a data permission. Data permissions are associated with data roles. When a user logs into HxGN OnCaii Dispatch, the system calculates the effective set of permissions for that user, based on that users default group and that group s action role and data/role (specified in the UserGroup table). After logging into HxGN OnCall Dispatch, the user can run the Change Role comman to switch to another group. Users have both an action role and data role at any time. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.10: Cybersecurity/Information Security, pg. 8 A HEXAGON Set up user permissions and roles in the User and Group management page in OnCall Dispatch Administrator tool. System Security Hexagon's security policy is to proactively develop, implement, and enforce security practices that meet regulatory, industry, and customer requirements applied to Hexagon personnel, business practices, and infrastructure management. Development, Support, and Professional Services employees receive mandatory security education and training. Product Center applications follow security testing requirements that include Attack Surface Analysis, Static Analysis Security Testing (SAST), Dynamic Analysis Security Testing (DAST), and penetration testing, where appropriate. Hexagon implements system and network security practices to provide a security -conscious, managed environment for our secured application lifecycle management process. The security of our cloud hosted applications is of the utmost importance to Hexagon. To ensure the security of our products and our hosted environments, a set of policies and best practices are adhered to and combined with a series of controls, monitoring tools, and analytics that are put in place to ensure compliance, auditing, issue transparency, and expedient resolution in the event of an incident. The polices and controls are a shared responsibility between the cloud hosting vendor, the customer, and Hexagon. Azure provides a logical isolation of the cloud dedicated to a subscription or resource group via Virtual Network (VNet) or Virtual Private Cloud (VPC). Each VNet you create has its own CIDR block, and can be linked to other VNets or VPC as well as on -premises networks as long as the CIDR blocks do not Response to RFP 21-02 for CAD/RMS/Mobile Section 2.10: Cybersecurity/Information Security, pg. 9 � A HEXAGON overlap. Control of DNS server settings for and segmentation of these private networks into subnets. With the use of VPC and VNet each OnCall environment can be secured and isolated from the other. The ability to add an additional layer of security to data at rest in the cloud is available via data encryption capabilities available in storage and database services. Provided key management options allow for management of any encryption keys. Azure provides several security capabilities and services to increase privacy and control network access. These include. • Network firewalls built into VPC • Web application firewall capabilities in WAF let you create private networks and control access instances and applications • Connectivity options that enable private, or dedicated encrypted connections Customer H. Describe how the proposed System manages unsuccessful log -on attempts. 1. Can the Consortium establish the number of log -on attempts allowed? Hexagon Response: Yes. The OnCall system includes an account lockout feature that is disabled by default. The Consortium can enable this feature and configure it to lock an account after a specified number of login attempts. It is further assumed that Azure Active Directory (AAD) will be used to provide authentication, password management rules and account access management. 2. What is the reporting or alerting mechanism used to communicate unauthorized access? Hexagon Response: Azure Active Directory Domain Services (Azure AD DS) security audits lets Azure stream security events to targeted resources. These resources include Azure Storage, Azure Log Analytics workspaces, or Azure Event Hub. After you enable security audit events, Azure AD DS sends all the audited events for the selected category to the targeted resource. You can archive events into Azure storage and stream events into security information and event management (SIEM) software (or equivalent) using Azure Event Hubs, or do your own analysis and using Azure Log Analytics workspaces from the Azure portal. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.10: Cybersecurity/Information Security, pg. 10 � A HEXAGON 3. Describe how the System allows users to reset their passwords. Hexagon Response: Below is an example of how a user might change a password in OnCall Dispatch. • The user may enter existing login credentials and check the "Change Password after Login" box. Checking this option will prompt the user to enter a new password and confirm it after logging in. • If a user's password is expired, the system will prompt the user to enter a new one after logging in. • Alternately, the system administrator may email the user a password reset link. In OnCall Records only the users with the Ability to reset User's Pas sword system right can reset passwords. Users with permissions can reset passwords via the User IVlanagement>Pas sword Setup screen. 4. Describe how the system administrators can manage the passwords of their users without impacting other Consortium agencies. Hexagon Response: The OnCall solution includes multiple API's that are leveraged for interfacing with 3rd party systems and Vendors. The Records and Dispatch products include Rest APIs that securely expose service endpoints that can be used to export or import data. The OnCall solution also provides an Analytics product that includes a warehouse with Data Models that are intended to provide access to OnCall users to insights and to important Data in the system. Because there is the inclusion of Read-only replicas with the Business Critical tier of Azure SQL Service, the agency can use these replicas to view and extract Data. 1. Can users log onto all proposed applications with one login? Hexagon Response: Yes. J. Can users be imported/updated from Active Directory? Hexagon Response: must support many different customer authentication scenarios, there are also many different configurations available for AAD. Users can be imported and updated from Active Directory and they can by synchronized via Azure AD sync too. Hexagon looks forward to working with the Consortium to design and implement the AD configuration that best meets the Consortium's needs. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON K. Does the System support multi -factor authentication? /f so, describe the types of multi -factor authentication supported (e.g., SMS/text message, facial recognition, smartcard, "bingo cards biometrics, etc.'). Yes. Hexagon's OnCall Managed Service solution utilizes Azure Active Directory (AAD). AAD is Microsoft's cloud -based identity and access management service which provides single sign -on and multi -factor authentication that is configurable by the Customer. Azure AD Multi -Factor Authentication works by requiring two or more of the following authentication methods. • SMS/text message • • OATH Hardware token • Microsoft Authenticator app • Smartcard Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Section 2.11 — System Administration A. What periodic System management functions should be performed to maintain System performance? Hexagon Response: Since Hexagon has proposed a managed service solution, system performance monitoring is handled by Hexagon through Microsoft Azure. Azure Cloud uses Azure Application Insights and Browser Developer tools the following to monitor performance. B. How much System Administrator time is needed per week, broken down by activity type? Hexagon Response: Since Hexagon has proposed a managed service solution, System Administrator duties would generally be limited to functions like managing user accounts, permissions, etc. Maintenance of the actual system would be handled by Hexagon. Additionally, Hexagon has proposed an optional full-time on -site Resident System Administrator (RSA) to perform these duties, so the Consortium's resource time would be minimal if it exercises the option. The RSA's duties include the following: • Provide general Hexagon System administration duties • Perform Hexagon OnCall configuration • Develop and maintain Hexagon System Support procedures as needed • Perform initial diagnostics for failures and Errors, identifying hardware or software problems • Change, configure, and manage user configurable forms for the OnCall software (where possible) • Assist Consortium training staff in development of workflows, operating procedures to improve dispatcher efficiency, deploy new functionality, and assist Consortium training staff in limited and technically focused overviews • Administer user accounts and passwords as directed by the Consortium's system administrator • Aid in installation of Hexagon Local Software upgrades (software supplied under separate Software Maintenance Agreements). Hexagon can also provide quotes for these services as needed. • Train the Consortium's technical staff for backup Hexagon System Administration duties via hands-on, daily work apprenticeships • Document any system anomalies in Hexagon's CRM tool and for inclusion into periodic site reports as requested • Provide support of Consortium IT team efforts to certify patches and updates • Support the Consortium in OnCall application update testing Response to RFP 21-02 for CAD/RMS/Mobile ii A HEXAGON • Coordinate activities for the deployment of updated Hexagon software. • Provide complex issue troubleshooting and resolution• /� Assist with managing users in Hexagon GovCloudC Azure AD as part of the loud Program • Travel within the Consortium within their scope of duties • Provide support for the entire suite of Hexagon -provided products C. Identify the resources required to provide ongoing support for the system after imp/ementation. Include a description of the Consortium personnel and roles required to manage the proposed system post -implementation. Below is a list of Consortium resources Hexagon recommends after cutover. If the Consortium elects to exercise its option with regard to the RSA, the Consortium's effort would be reduced. • Systen, Administrator — to establish, configure, and manage user accounts, security controls, workflow definitions, and other system configuration parameters • Integration and Testing Manager — should have extensive experience in writing system test plans and executing tests for large, integrated systems • SME. — 1-2 SMEs per key functional area; SMEs should have in-depth knowledge of the current business processes for their functional area, as well as knowledge of all systems currently in use by their functional area • Training Manager — should be experienced in developing, implementing, and coordinating training classes for relevant agency personnel. The training manager should have an understanding of basic Public Safety procedures and terminology and agency procedures and workflows • Client Hardware / Network Administrators —should be members of the IT Staff who have in- depth knowledge of the IT infrastructure D. Do any applications require a restart and/or additional login for configuration changes to take effect? Hexagon Response: All Hexagon applications proposed are browser based, so a user would log off and log in for configuration changes to take effect. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON E. Describe how Consortium members will maintain global system configurations. Hexagon Response: For OnCall Dispatch, configurations would be maintained through the OnCall Dispatch I Administrator tool. Administrator is a web client that enables centralized administration, control, and customization of the OnCall Dispatch system. It provides centralized control of broad areas of system operation and behavior without the need for coding including, access control and security, business rules and logic, workflows, configuration of the user interface, and data presentation. For OnCall Records, system and environment configurations, national reporting standard, password requirements, calls for service sharing/not sharing between agencies, master index (name, vehicle, and location modules) sharing/not sharing between agencies, multiagency, regional codes and agency specific codes display, code filtering by agency, menu labels, custom fields, and master indices UI customizations are configurable at the global level and are handled via the OnCall Records Administrator tool. F. Describe how Consortium members will maintain local system configurations. For OnCall Dispatch, Hexagon is recommending the Consortium use a single dispatch configuration. For OnCall Records, field configurations, custom screens, workflows/alerts, code tables, and security permissions are all configurable at the agency level. These are also handled via the OnCall Records Administrator tool. G. Describe how Consortium agencies can maintain their users within the System without impacting other organizations. Hexagon Response: OnCall uses groups and roles to maintain security levels and permissions in the system. Users can be added to that particular group for each agency, and it would not impact another agency with its users. H. Describe how global configuration changes will not impact or overwrite local configurations. Hexagon Response: For OnCall Records, there are no global changes that impact what can be changed at the agency level. However, global changes dictate what can/cannot be done at the agency level. For example, you cannot add a new custom field at the agency level, only at the global level, and then that field is available at all agency levels, which can hide or rename as they see fit. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Section 2.12 — General Functionality The applications within this proposed system must be fully integrated and meet all the minimum technical, functional, and performance requirements stated within the attachments. A. The Consortium requires multiple external database queries in a single transaction, such as FCIC/NC/C, RMS, Odyssey, and the Affidavit System. Describe the proposed approach to meeting this requirement and any limitations to querying multiple databases in a single transaction. Hexagon Response: Hexagon provides external database queries and transactions via the proposed OnCall Informer and interfaces to the external systems. Assuming the multiple databases will allow and support a single transaction query from the OnCall Records system, the proposed OnCall Informer and associated services for query interfaces can support this requirement. Checkboxes are included on various forms where multiple destinations apply and are used to define the destinations. All checkboxes can be specified by the user. Based on the checkboxsettings, OnCall Records generates the transaction information bound for each external database. OnCall Informer provides the transaction formatting and connectivity to each system, and responses received are routed to OnCall Records. B. What is the limit to the number of databases that can be queried in a single transaction? Hexagon Response: Assuming the multiple databases will allow and support a single transaction query from the OnCall Records system, the proposed OnCall Informer and associated services for query interfaces can support this requirement. Checkboxes are included on various forms where multiple destinations apply and are used to define the destinations. All checkboxes can be specified by the user. Based on the checkboxsettings, OnCall Records generates the transaction information bound for each external database. OnCall Informer provides the transaction formatting and connectivity to each system, and responses received are routed to OnCall Records. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON C. Describe the process for generating identif/cat/on numbers for calls for service, incidents, and cases. Are these numbers part ofa single, chronological list, or do they follow different numbering sequences? Hexagon understands "incidents" to be interchangeable with what we call events. Every event (Calls for Service) created in OnCall Dispatch is assigned a unique Event ID number. When a multi -agency event is created, a unique Event ID is given for each agency defined to access that event, as a separate event will Therefore, created for that agency. I herefore, data unique to each agency can be added and altered for the event independent of the other agency events created for that multi -agency event. Other added data is generally kept separate using the agency definition and overrides such that an individual agency can add data or edit the layout or settings of the system without altering the data or settings for other agencies. The numbering system allows for each agency's number (case or incident) to follow different numbering sequences and even formats with identifiers as to which agency Incident or case number belongs to. 1. Are incident numbers the same as case numbers? Hexagon Response: Event numbers are different than case numbers. Use Assign Case Number feature to assign or override a case number for an event. Case numbers are useful when reports are filed for events. You can identify the report by giving it a case number, and then link the event and report together by assigning the case number to the event. Multiple case numbers can be assigned to a single Event. When the Event in OnCall Dispatch is created it can have multiple agencies respond but when a Case Number is generated in CAD it will be associated with the reporting agency. 2. /s any year-end maintenance required to update case numbers to the new year? Hexagon Response: No year-end maintenance is required. Case numbers can have rollover numbers daily, monthly or yearly as shown in the screenshots below of menus from the OnCall Administrator tool. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.12: General Functionality, pg. 2 A HEXAGON 3. Does every Consortium agency call or incident receive a unique number? if not, please explain. Hexagon Response: Yes. Every call receives a unique number. 4. The Consortium currently uses incident numbers for all CAD calls for service but only assigns case numbers to incidents resulting in a police report. Describe the proposed approach to adding case numbers to closed incidents. Would CAD and Mobile users have the ability to create multiple case numbers for a single incident (e.g., police report and warrant request)? Hexagon Response: Yes. Case numbers can be assigned incidents using the Assign Case Number function. If a user wants to assign aate case number to a closed incident, the user must first run the Reopen Event function. Then the Assign Case Number function will be available. These can both be done by command line or dialog. Yes CAD and Mobile users can pull multiple case numbers for a single incident. 5. The Consortium intends to standardize the report number format across the various agencies; however, if agencies require different report number formats, describe how this can be accomplished. This is accomplished in OnCaii Dispatch Administrator tool. CAD incident Number setup and Case Number setup for the various agencies is defined in one area. The System Administrator can standardize this, but if desired it can still have unique agency identifiers. Each agency can specify its own number format based on the Consortium's needs. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.12: General Functionality, pg. 3 A HEXAGON D. The Consortium expects the future System to maintain compliance with both federal and state - mandated changes. Describe the process by which the Proposer will ensure that the software currently meets and will continually meet evolving requirements. Hexagon attempts to maintain compliance with security standards (such as CJIS) by monitoring the release of policy documentation. Hexagon strives to incorporate changes to federal crime reporting requirements in the latest versions of software released. Hexagon subject matter experts review the latest guidance to determine if a change to the software will be made, however, certain changes may be developed subject to a separate Order or Change Order. Any costs associated with changes that are required due to evolution of federal or state changes are to be borne by the Customer. Hexagon designs and develops its software in accordance with the quality standard dictated by ISO 9001:2015. Please note that updates are not automatically provided to meet changes in federal and state requirements as Hexagon has no way to predict the frequency of changes required. New software for new federal and state requirements can be provided at an additional cost. The updates are determined by the type of request(s) and necessary product upgrades (if any). The updates will require a change order and involve a new statement of work (SOW), developed at the time of the request. E. Describe the System's ability to work with tablet and smartphone devices. Specifically: 1. What type of hardware is supported (e.g., Apple, Android, Windows products)? The Mobile Responder App works with Android and IOS tablets and smartphones. The OnCall Records and OnCall Dispatch systems are browser based and will work on a Tablet format however not designed due to form factor to work on smart phones. 2. What type of operating systems are supported (e.g., iOS, Android, Windows, etc.) Hexagon Response: Android and iOS are supported for our Mobile Responder application on smartphones and tablets. Windows is supported for OnCall Mobile Unit which can be accessed on Windows -based tablets and MDTs. OnCall Dispatch and OnCall Records are browser -based applications. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON 3. How do these devices access the application (e.g., web -based, app downloaded from an app store)? Hexagon Response: OnCall Records, OnCall Dispatch and Mobile Unit are web -based applications and can be accessed via a supported browser on PC or Tablet. Mobile Responder can be accessed via app downloaded from app stores on Android or 10S devices including smartphones and tablets. 4. Describe the level of functionality available for tablet and smartphone devices. Hexagon Response: HxGN OnCaii Dispatch - Mobile Responder provides continuous access to the OnCall system for field personnel. Available as a native app for Phones, Pads, and Android devices, Mobile Responder incorporates native device capabilities, such as push notifications, GPS, and the camera. The use of Mobile Responder also reduces radio traffic between dispatchers and responders and allows for field event creation, incident detail views, status updates, message receiving and acknowledgement, and other useful functions. Mobile Responder extends the power of command and control to all field personnel, improving overall response and increasing public confidence. HxGN OnCall Dispatch I Mobile lobile Responder Mobile Responder connects first responders to the PSAP via a smartphone or hand-held tablet. Fully integrated with HxGN OnCaii Dispatch, the mobile app helps public safety agencies make smarter decisions and improve safety and efficiency in the field. The solution enables users to: • Run searches and queries • Receive events and alerts from the control room • Self -attach to events • Update status and event information • View positional information on a map Monitor each responder's location With Mobile Responder, responders can work away from their unit, stay updated during event changes, and shareconsistent situational awareness with the control room. HxGN On/aii Dispatch I Mobile Responder features modern, easy -to -read dashboards and unit boards. From the Dashboard, users can quickly create events using the green + Add Event button. Users can also self -attach to events with a swipe. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.12: General Functionality, pg. 5 A HEXAGON F. Describe all supported peripheral device types such as in -car printers, driver's license readers (magstripe, 2D barcode), biometric identification, and any other devices that interact with the System. Hexagon applications work with numerous peripheral devices. Essentially, if the device is supported by Windows and works without special software or adaptation then it should work with our applications. As an example, Hexagon utilizes the Windows print spooler for printing, so if the printer is accessible by Windows then it should function for our applications. Similarly, scanners and other input devices that are recognized by Windows should also function within our applications. G. Describe how the System supports multiple Active Directory Tenants in various Consortium domains. What is the Proposer's recommended approach? Active Directory provides multiple configurations in support of the many different authentication scenarios customers can have. On -premise Federation (ADFS) can be supported by the OnCall solution. Another configuration that can be would be to leverage AAD connect to an AAD tenant that is set up to provide pass -through authentication only. AAD also support a B2C configuration whereas AAD acts as the aggregator for the various domains with the ability to support on -premise, gov-cloud and commercial - cloud tenants with one end -point for authentication. H. Describe how the System supports a mix of Azure Active Directory and on -premise Active Directory. Hexagon Response: Active Directory provides multiple configurations in support of the many different authentication scenarios customers can have. On -premise Federation (ADFS) can be supported by the OnCall solution. Another configuration that can be would be to leverage AAD connect to an AAD tenant that is set up to provide pass -through authentication only. AAD also support a B2C configuration whereas AAD acts as the aggregator for the various domains with the ability to support on -premise, gov-cloud and commercial - cloud tenants with one end -point for authentication. I. Provide future -state roadmaps of upcoming functionality and features on the 1-3 year horizon. Hexagon Response: 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. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.12: General Functionality, pg. 6 A HEXAGON 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 RFP., 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 This both in terms of the capabilities and technologies required. I his 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. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.12: General Functionality, pg. 7 A HEXAGON Section 2.13 — CAD/Mobile The applications within this proposed system must be fully integrated and meet all the minimum technical, functional, and performance requirements stated within the attachments. A. Describe the options available for users of the CAD system to access CAD with no local client installation specifically: I. What web browsers are supported? Hexagon Response: 2. What information can mobile devices (e.g., smartphones, iPads) access? Hexagon Response: Hexagon has proposed its Mobile Unit and Mobile Responder products for the Consortium to perform CAD functions in the field. Mobile Unit provides access to OnCall Dispatch features from an in -car / laptop, a Windows tablet with a supported browser, an Pad with Safari browser or an Android tablet with Chrome browser. Mobile Responder app can run on Android or Apple !OS smartphone and tablet devices. HxGN OnCaii Dispatch I Mobile Unit is a browser -based client of OnCall Dispatch optimized for in -vehicle use. It offers role -based workflows, screen layouts for smaller form factors, and night time and high - contrast display. Chat -style messaging, group notifications, and automated alerts also enhance communications. User updates and live feeds from the field, including person -level tracking, ensure control rooms are aware of personnel status and location no matter where they are. The solution enables users to. • Monitor live operations via event and unit monitors Run searches and queries • Receive events and alerts from the control room • Self -attach to events • Update status and event information • Message units, individuals, groups, and dispatchers • Make, update, and cancel tow requests HxGN OnCall Dispatch I Mobile Responder connects first responders to the PSAP via a smartphone or hand-held tablet. Fully integrated with HxGN OnCall Dispatch, the mobile app helps public safety agencies make smarter decisions and improve safety and efficiency in the field. The solution enables users to: • Run searches and queries Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 1 /HEXAGON • Receive events and alerts from the control room • Self -attach to events • Update status and event information • View positional information on a map • Monitor each responder's location 3. Is the format/display layout configurable (e.g., portrait or landscape, "zoom in" capable, display fields, "buttons," and pages)? Please explain. Hexagon Response: II Mobile Unit. 4. What historical CAD information can be queried from the mobile device? From a mobile device, users can query unit history, broadcast history, event history, previous incidents at location, premise alerts at location, and supplemental data including Persons, Vehicles, Property, Contacts, and Location information. 5. Are separate licenses required for mobile access? if so, please describe. Hexagon Response: Typically, yes. Separate concurrent user licenses are required for users who want to access OnCall mobile products. However, Hexagon acknowledges the Consortium's request for a site license and has proposed a site license that includes OnCall Dispatch I Mobile Unit and Mobile Responder. Refer to Section 2.9 Software License Agreement for details about the proposed site license. B. Which databases can be queried directly from CAD (e.g., RMS, interfaced systems)? Hexagon Response: CADusers can query OnCall Records, NCIC, FCIC and various other interfaced systems (depending on the defined needs of the interface) via Hexagon's proposed Informer product. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 2 A HEXAGON C. Can CAD query returns be redacted through a native system tool to prevent confidentia/, sensitive information from being disclosed when responding to a public information request? Hexagon Response: Query returns are stored in a separate CJIS compliant encrypted area of database, so returns do not appear on a public information request. D. Describe how historical information associated with a CAD location can be displayed on real- time maps (e.g., address, owner/resident, preplans, gate codes, floorplans). Describe how historical data related to maps are stored. Hexagon Response: The map display in OnCall includes the ability to add a layer and show special situations, including preplans, gate codes and a URL location link to show location with floorplans. ALayer with special situations can be displayed on the map display. The operator can select details from the map, or (as shown in the example below) display the event details at the School. The operator can then select View More to show additional details. If there are attachments the operator can click on the hyperlinks to open the graphic. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 3 HEXAGON Respo.,se to RFP 21-02 for CAD/RMS/Mobile Sector, 2.13: CAD/Mobile, pg. 4 A HEXAGON E. Explain how the System displays historical/officer safety information on the map? For example, an officer responds to a call at a mobile home park. How does the System show hazards and warnings for surrounding locations? OnCall Dispatch can display the symbol of the special caution (such as a Hazmat icon) so the operator can see the caution on the map in relation to the location of call. An Officer can also see hazards on the event display within the agency -defined nearby radius. As shown in the example above, the Officer can drill down in the event to get more information regarding the hazard. F. Information sharing and officer safety considerations are paramount for the Consortium. Describe how the System supports Consortium agencies viewing units, resources, and calls for service from CAD and Mobile and the ability to assign resources to all law enforcement incidents in the System. Hexagon Response: Both OnCall Dispatch and OnCall Mobile Unit share the same basic components (Map, Event Panel, and Unit Panels) which show live updates. When a dispatcher assigns a unit to an event, the mobile unit gets a notification and can see the event details pane. Mobile officers can put themselves out on events from the Mobile Unit software. Map view Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 5 HEXAGON Unit Board view Event Board view Respor,se to RFP 21-02 for CAD/RMS/Mobile Sector, 2.13: CAD/Mobile, pg. 6 A HEXAGON G. Does the solution provide any notifications or alerts when a GPS sign/ has not been received after a certain interval, such as time elapsed? Hexagon Response: OnCall Mobile Unit has an indicator bar in the lower right of the screen that shows GPS signal strength. However currently not Time elapsed. H. Does the system support automatic unit status updates via AVL (e.g., en route, on -scene)? /f so, can the Consortium configure unique status update rules? Hexagon Response: Yes, the system supports automatic unit statusupdates via AVL. Yes, the Consortium can configure update rules in the HxGN OnCaii Dispatch IOnCall Administrator tool. I. Are user -defined dashboards available in the mobile environment (e.g., to receive an at -a glance indication of recent activity)? If so, please describe. Hexagon Response: By use of the My Patrol tab, officers can select to enter information for traffic stops and view a map of the immediate area, nearby active events, and nearby units, or queue of Events that they have been assigned. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 7 � A HEXAGON Use the example above with the following table to become familiar with the parts of the My Patrol tab. Use the Button Bar to send messages, view events from the last 24 hours, and more. The Button Bar also contains the Smart Button, which is used to quickly update your unit status. The following tabs are available. • Map - displays a map of your immediate area. • Nearby Events - displays the closest events to your location. • Nearby Units - displays the units in your immediate vicinity. • Queues - Displays events you have been assigned to. Use the Traffic Stop section to enter license plate numbers during traffic stops. For more information, see the Traffic Stop topic. The Shift History section displays your units history for the past 12 hours, that is, all events to which your unit was assigned. Click an event to view the unit status changes for that event. a Open events display the event location, and closed events display the event ID. The Status Bar displays your unit ID, status, location, and more. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 8 HEXAGON Respo.,se to RFP 21-02 for CAD/RMS/Mobile Sector, 2.13: CAD/Mobile, pg. 9 A HEXAGON J. Describe how the mobile dispatching and RMS systems work in an environment if wireless connectivity is unavailable. 1. Does work in progress automatically save? Hexagon Response: HxGN OnCa allows officers to work offline. Officers will remain logged in if connectivity is lost. All data that is performed will be cached and updated once connectivity is re- established. In HxGN OnCall Records if connectivity is lost, users can save field reports locally then upload them to the server to begin the approval process when connection is restored. 2. How can a deputy/officer start a report? Hexagon Response: This is not available offline in OnCall Records. 3. Will the System automatically transfer a report when connectivity is re-established? Hexagon Response: This is not available offline in OnCall Records. K. Describe the difference between the RMS functionality on a desktop compared to a mobile device. Hexagon Response: There is no difference. Hexagon has proposed OnCall Records which is a browser based application that can be used on a desktop or on mobile devices in the field. L. Describe how the CAD and Mobile clients query the registered owner's driver's license after executing a license p/ate query. This can be done when query of plate is done by nested query capability in OnCall Dispatch system with HxGN OnCaii Dispatch) Informer Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 10 A HEXAGON M. The Consortium expects the Mobile client to interact with the operator, similar to a smart assistant. Describe how the Mobile client communicates with the operator for the following: 1. When the operator queries a driver's license or vehicle license plate. Hexagon Response: The screenshots below are an example of what an officer may see after entering a license plate number and selecting Run in OnCall When the return comes back, the system notifies the officer of the returns. The officer can then choose to display and review the results. There may be more than one result as it queries the RMS, NCIC and FCC and also the CAD for BOLOS. If a vehicle is stolen, Hit Detection will alert the officer immediately so the officer can see that return first. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 11 A HEXAGON 2. How the Mobile client alerts the operator of "Hot Fi/es, "including stolen vehicles, wanted subjects, and expired or suspended driver's licenses. Hexagon Response: For hot files, if a vehicle is stolen Hit Detection will alert officer immediately upon receiving return and the officer can select to see that return first. 3. When the Mobile client receives a new message from a CAD workstation or other Mobile clients. This is included in OnCall's core functionality. The Messages tab provides users with an internal messaging system in order to easily communicate with one another and share information about events. It also enables users to send messages to entire dispatch groups, roles, etc. Listed below are the various ways by which a user can navigate to the Messages Board. Figure 6: Ways to navigate to Messages Board Performing one of these actions opens the Messages Board, pictured as follows. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 12 HEXAGON Figure 7: Messages Board To view messages, select the message from the list. The selected message populates the right side of the screen. Unread messages appear in bold with a green marker. Use the search bar to search through messages. Users can also filter the option to have the newest messages on top or the oldest messages on top. Notifications lets you know when a message has been received. This is presented as a pop-up notification before being stored in the Notification s List section. 4. When the Mobile client receives a query response. Hexagon Response: When a return notification pops up, the officer can simply click on the notification and it will take him directly to result. Alternatively, the officer can go to Queries Conducted by You pane which displays a list view of Informer query responses. Unread responses are listed in bold. The officer then selects from the list to display a return and can scroll through if there are multiple returns. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 13 � A HEXAGON 5. When the operator is assigned to a call. The operator gets a popup notification when assigned to a call. The display on the My Patrol dashboard shows the Map with a route to the call and a detailed Event Panel with key information about the Event. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 14 � A HEXAGON 6. When the operator receives a call update. Hexagon Response: The operator will receive a notification of the update. Comments show dynamically in the event panel, whatever updates highlight icons to indicate information the paper clip icon indicating 2 attached files. This action displays the file summary so users can click to see. N. Describe how officer safety information (e.g., "Caution Notes" for locations, typically embedded within a CAD Database, and 'Alerts" for persons, typically embedded within an RMS Database) may be consolidated and presented to a Call Taker, Dispatcher, or Mobile user based upon either event location or subject's name. 0 nCall Dispatch allows a user to view event details that include remarks about an event. The remarks can include caution notes for locations, or other details to maintain awareness for dispatched units. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 15 A HEXAGON The event card is an abbreviated view of the event panel. This displays pertinent remarks that can be added by a call -taker at the time of the call, a dispatcher at the time of dispatch, or units in the field who encounter new information. Premise information is referred to as location of interest (LOI) in OnCall Dispatch. The LOI process runs automatically whenever an event is accepted or updated. LOI searches for premise history at the event location, in addition to special situation flags showing any situations that exist at the location that may impede or affect a response. Only locations that are successfully verified go through the LOI process. The LOI icon is found on the left side of the Event Panel, pictured below. Left -clicking the icon will reveal two tabs, Events and Special Situations. Data collected from the events will be placed in these tabs correspondingly. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 16 HEXAGON Premise information (location of interest) in OnCall Dispatch event panel. If there is a person of interest related to the event, a broadcast may be created for that person of interest. That broadcast may be attached to an event or multiple events. Users who access the event details will see the person of interest information. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.13: CAD/Mobile, pg. 17 A HEXAGON Section 2.14 - RMS The applications within this proposed system must be fully integrated and meet all the minimum technical and functional requirements stated within the attachments. A. Describe how the RMS is scalable to allow the use or creation of new data fields that are required after implementation. How is data validation applied to these fields? Yes. OnCall Records provides COTS custom fields that can be used by agencies, along with the ability to re -label and re -purpose fields within OnCall Records. OnCall Records product also allows the user, with appropriate privileges, to add as many fields and/or tabs to store the new custom fields to the system as desired. For example, Code, Date, Number, Text, Boolean, Long Text, and Date�lTime fields can be added. After custom field creation, the fields are available to run reports on. If Hexagon customizes the system to add new fields, then the ability to search these fields will be included. Such customizations may be subject to additional services or cost. Data validation can be done on individual entry items through restrictions on the type of data entered as well as the requirement to complete a particular field. OnCall Reports also has a fully integrated, highly robust NIBRS validation engine that allows the reporting officer to check any report for proper entry before submitting it to the workflow process for approval. B. Describe the case management workflow from CAD call to RMS report disposition. This should include report creation, assignment, approval, supplements, updates, additional approvals, and closure. Hexagon Response: for events, call location information, call type and priority, and unit date/time stamps with statuses. Case Management functionality is provided within the OnCall Records system through the Case Management module. It allows for the assignment of officers/investigators, tasks, with assignment, narratives, evidence, and additional links to modules in the OnCall Records system. The module provides various tabs and tools that allow investigators to manage criminal cases and investigations. Cases are assigned a type based on the Incident Offenses involved, and multiple Incident records, as well as other record types can be linked to the Case Management record. Data entry includes the investigators assigned, status, activity, clearance, attorneys, buys, and so forth. OnCall Reports Workflow allows an agency to setup document process tasks for users, groups, and specific modules, including Case Management. This Workflow Process may include the following steps: 1 A user creates a draft record by saving the initial record. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 1 � A HEXAGON 2 That user later adds more information and links other records before submitting the record for approval. 3 The record is assigned as an Available Task to all members of the Supervisor Group. 4 A Supervisor pulls the Workflow Task, reviews the record and rejects it, sending it back to the user who submitted it (and appears in the submitting users My Tasks Inbox tab, as pictured in the following image). 5 The creating user is reassigned tine Task to correct the record, the user corrects the record and resubmits it. 6 The Supervisor is reassigned the Task, reviews the record again, and approves it. 7 The approved record is sent as an Available Task to all members of the appropriate Administrator Group. 8 An Administrator pulls the Task, reviews the record, and approves it. (Note that it could also be rejected back to the Supervisor). 9 Upon Administrator approval, the Workflow Task progression is complete and the Incident report is flagged as Approved. Each Workflow Task assigned to a specific user appears in their Inbox upon login. Any available Workflow Tasks that can be claimed by that User (as a member of a specific Group) are found under an Available Tasks tab. Once a User claims a Task from their My Tasks or Available Tasks tab, they are redirected to the Workflow Approval Process panel for that record. The History for a Workflow Process displays all steps completed, including the user who completed the step, the date/time, and any comments entered during the completion of the step. C. Describe how the RMS documents the collection, submission, management, auditing, and tracking of property and evidence. Hexagon Response: OnCall Records supports Property and Evidence management. The Master Property Index serves as an index of all property not in custody, such as property that is missing, lost, stolen, and so forth. Property types range from drugs and money to equipment and livestock. A Currency tab is available for recording money as property. The Master Property Index also serves as an index of all items currently (and previously) held in custody, usually as evidence for a criminal case. The Details fields available are generated based on the category selected. Other information collected include Case Review, Storage/Custody, Chain of Custody (COC), Storage History, Disposition, and Caution Codes. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 2 � A HEXAGON All items are tracked for COC and storage, and a complete history of this data is recorded on the Chain of Custody and Storage History tabs. Bulk Intake provides the ability to perform bulk check -in to the same location for an unlimited number of evidence items simultaneously. ASignature Capture panel is available on both the Storage/Custody transfertab and the Bulk Update screen. The signature is available and read-only on each corresponding COC record. Signature Capture is provided to support COC transactions for internal users (employees) and external users (Prosecutors, Courts, Public/Owners, etc.) The Evidence Management features support the ability to automatically notify officers of Evidence Items that require review via the My Review Items feature. This functionality supports the ability to prompt officers responsible for collected Evidence Items to review and take appropriate action concerning whether to maintain or dispose of the item. D. Describe how the System audits actions taken in the System for security compliance. There are several tracking components built into the solution to ensure compliance to local policies. Our system fully audits all changes made to records and keeps a PDF of finalized reports so internal review can ensure the records have not been tampered with. System Administrators can use an Audit History feature that allows searches of the following user and administrative actions within OnCall Records: insert, update, delete, view, datasheet view, password change, password change failure, login, login failure, logout. However, nearly any action that affects a database table can be audited, provided the user is familiar with the OnCall Records database structure and table names. OnCall Records Audit trail captures users' actions and maintains the data both before and after changes. The audit trail tracks the changes on a per record basis for every record in the database. All data changes to a record are maintained in the audit trail. E. Describe how the System manages intelligence information, including: I. How the System restricts user access to intelligence files. System Administrators use a flexible security utility to manage control and access to information within OnCall Records. Access control is provided via. • User roles, which can be defined as having None, Read, Write, and Delete access • Record Locking, which restricts access to specific records Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 3 � A HEXAGON Hidden tabs / data fields, which allows information within a module that is considered sensitive to be inaccessible Hidden records, which supports the ability to "hide" records from search results for specific user groups on a per module basis 2. How propriety records and information is protected from unauthorized access within the system and logs unauthorized access attempts. Hexagon Response: See response to item E.1 above. System Administrators can use an Audit History feature that allows searches of the following user and administrative actions within OnCall Records: insert, update, delete, view, datasheet view, password change, password change failure, login, login failure, logout. However, nearly any action that affects a database table can be audited, provided the user is familiar with the OnCall Records database structure and table names. 3. How System Administrators' access to classified or privileged information within multi - agency installations is limited. Hexagon Response: OnCall Records provides administrators with the ability to create agencies and subordinate to each agency, users, groups, and roles are created. Each role allows administrators to define security for read and write access, through custom security rights by table. OnCall Records provides the ability to leverage the customizations for each configure/dam agency within the system. Each agency can manage (and maintain Screen Customizations, Field Label Customizations, Workflows, Alerts, and Permission Groups. However, at the time of implementation, agencies will determine whether(`key Master Modules will be shared between the agencies (e.g. Master Names, Master Vehicles, etc.). Global system administrator can restrict access so that agency administrators only see their own agencies. 4. How partitions and controls have been configured in previous system deployments ensures only authorized persons can access restricted information. OnCall Records provides configurable permissions to restrict or grant access to confidential information. These permissions are managed by the System Administrator. Rights are assigned to a Role, a Role is assigned to a Group, and Users are assigned to the Group. Users can be excluded from the module entirely or given certain view/edit rights, etc. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 4 � A HEXAGON 5. How the identities of Confidential informants are protected within the System. Hexagon Response: OnCall Records has the capability to secure individual records to groups of people. Anyone outside of the secure groups cannot see these records. Some customers will set up confidential task force information within its own agency within OnCall Records to take the security one step further. 6. How the System classifies information (e.g., tip, intelligence submission, intelligence file). The OnCall Records Case Management module allows for several internal fields to help personnel properly classify information received out -of -the -box. OnCall Records is richly customizable to fit local business practices, so the Consortium would be able to build your own classification tracking elements. There is currently no specific section of the OnCall Records application dedicated to tracking tips. There are a few areas, however, where that information could logically be stored. If the tip is specific to a known gang or group, the tip could be listed in the Activity Log of the group record. Other tips with less specific information could be added as a record in the Miscellaneous Service module as a tip. Custom reports could be written against that data to produce meaningful intelligence documents. 7. How the System manages retention, review, validation, and purging of records. Hexagon Response: The OnCall Records fully supports the ability top seal and/or expunge information within Incidents, Juvenile Contacts (Arrests), Arrests, Booking, Juvenile Booking, Inmates, and Citations. Purging data in bulk is not supported nor required. Configuring how sealing and expunging records is managed within the application is a System Administrator task. For example, expungements may be configured to allow for the removal or retention Bi rth, Race, Sex, Date of Citizenry, and/or Ethnicity data that would be used for analyses. System Administrators may also configure the expungement functionality to be backed up to a secured file directory and then determine whether the information is encrypted. Users allowed to view expunged records or expunged charges can also be designated by the System Administrator within the application. The OnCall Records also supports the ability to seal a Name record, which severs the association of the record to one of the above listed modules and replaces the data with an anonymous name (e.g. "SEALED PERSON") for reporting purposes. Furthermore, charges contained within Arrests, Booking, Juvenile Booking, and Juvenile Contact modules may be expunged by on a charge- by -charge basis. Each charge supports capture the associated Court Ordered Expungement information along with the Date, Time, and the Judge ordering the expungement. Users without permission to view expunged records can view an Arrest, Juvenile Contact, Booking, or Juvenile Booking record containing expunged charges in addition to valid charges, but the expunged charges will not be visible. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 5 A HEXAGON The Master Names, Master Vehicle, and Master Location modules support validation against existing names during entry. Linking of MNI, MVI, and MLI data is inherent to OnCall Records and how it associates records with these modules upon involvement and reported occurrences (Incidents, Accidents, and so forth). OnCall Records Data Validation is supported via IBRS reporting validations and drop -down code values configured by the System Administrator. 8. How the System provides alerts to the case agent to review a record scheduled to purge. Hexagon Response: OnCall Records supports automatic and manual Alerts in several key modules to notify the user triggering the alert but also to alert subscribers that something has occurred with a record they are interested in. Alerts can provide an internal notification as well as an external e-mail notification, outside of 0nCall Records application. Alerts can be created within each OnCall Records module to provide notifications to defined user groups or individual users based upon specific scenarios or changes in data. Alerts may be limited by agency based on the user group settings or made available system -wide. While the capability to create alerts is available as described above, the 0nCall Records system does not have purge functionality. Instead, the system supports sealing and expunging records. 9. How the System complies with Federal (28 CRF Part 23) and Florida State Statute 119.01. Hexagon Response: Yes, Hexagon complies with 28 CFR Part 23. Hexagon maintains PDF copies of all reports generated that can be issued to the public after redaction of appropriate information is made. 0nCall Records includes several native fields on tracking appropriate information related to requests such as these. F. How is historic information maintained and tracked when master index records are modified (e.g., updated address) and/or merged? All changes are tracked via auditing when a change is made to a master index record. Data contained within the master records to be merged can be selected for storage in the Master record history for Names and Vehicles only. Name records provide the option for a user to select which information will be maintained for an MNI record for historical reference. History information is denoted as being updated by a Master Combination. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 6 A HEXAGON G. How does the System prevent users from entering duplicate master records? /f duplicate master records are entered, describe the process by which they are identified and ultimately consolidated? OnCall Records provides key features to assist a user in avoiding the creation and duplication of records within the system. Names, Vehicles, and Locations use type -ahead features to quickly identify existing Names, Locations, and Vehicles that already exist in the system. During MNI data entry, in addition to the type ahead feature the system will notify the user if a name already exists with the same SSN and/or driver's license number. During MVI data entry, in addition to the type ahead feature the system will notify the user if a vehicle already exists with the same plate and plate state and/or VIN number. As part of the ongoing master indices maintenance the system has a combine records tool that provides the agency with highly flexible duplicate detection search capabilities. This feature allows the agency to search the system on a combination of fields to locate and provide the opportunity to bulk merge names and vehicles. The master name duplicate check can be done on any combination of the following fields. SSN, DL number, Local ID, SID, SRS#, FBI#, last name, first name, middle name and DOB. Once a list of duplicates is located, the agency can select which names to merge using multi -select at which point merged criteria will be stored in the name history. Similar to the master name duplicate check, the master vehicle duplicate check can be done on any combination of the following fields: vehicle category, VIN, make, model, color, plate and plate state. H. How are alarms and ordinance violations tracked within the System? Does the system support an escalating cost formula based on the number of violations that have occurred? Hexagon Response: OnCall Records has a robust alarm tracking and billing system that, depending on the availability of data, can be automatically populated or manually configured to track all alarm data in the system. OnCall Records has a detailed set of rules that can be designed to match the agency's standard procedures to track the number and type of alarms and adjust fees as appropriate. Our billing configuration can have different rules depending on the type of alarm, it can have additional fees tacked on, it can allow for late charges, and it can be configured to various time cycles. The OnCall Records Citations module can be used to enter data for a code enforcement violation. Different types of citations can be distinguished using the type of citation and entering the Ordinance violation from a picklist that is populated from the statute code list. With UI customization it is possible to track other data specific to code enforcement if needed. A Citation can be linked to location, name, vehicle, DUI, Accident, Incidents, as well as other linked records in the screenshot below: Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 7 / HEXAGON Linked Records Yes, OnCall Records currently supports escalating fee rules. I. How would the Fa/se A/arm Billing vendor be made aware of False Alarm information originating in CAD in the proposed system? Alarms and Alarm based Incidents with dispositions are tracked in the Alarm and the Incident tables. OnCall Records fully supports False Alarm Billing functions. If the Consortium requests it, Hexagon can discuss options for an interface to bring the data over from the CAD system to the RMS or for an interface to a third party alarm billing software provider such as Crywolf. J. How are incident reports assigned to individuals in the RMS application? Hexagon Response: When a task is assigned to a user, that user will receive a notification in their OnCall Records Inbox, containing a link to the Task record. K. How does the CAD/Mobile/RMS solution identify when a report must be written? /s this configurable at the agency level? This is determined by department policy, not by the CAD/Mobile/RMS system. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 8 A HEXAGON L. Can the System generate reports of outstanding and missing reports as needed? if so, describe the process. Hexagon Response: OnCall Records supports the running of SSRS reports directly from the application. We provide a number of COTS reports for many functions, and the agency has rights to tailor reports out -of -the -box or to create their own reports to adapt to a local business need. Any reports generated within the SSRS component can be built to have filters to allow refined searches. Hexagon has also proposed OnCall Analytics for additional reporting functionality. The Consortium will receive training to better understand the reporting features in both OnCall Records and OnCall Analytics. M. Can Records develop a report that notes what reports are outstanding across the agency? Can this report be filtered to showa specific individual or beat? Please describe. Hexagon Response: OnCall Records supports the running of SSRS reports directly from the application. We provide a number CO TSOTS reports for many functions, and the agency has rights to tailor reports out -of -the -box or to create their own reports to adapt to a local business need. Any reports generated within the SSRS component can be built to have filters to allow refined searches. Hexagon has also proposed OnCall Analytics for additional reporting functionality. The Consortium will receive training to better understand the reporting features in both OnCall Records and OnCall Analytics. N. Describe how the System restricts sensitive reports from unauthorized users and agencies? Hexagon Response: The ability to view sensitive reports is an explicit permission within a Role. An agency would set up access rights for users in the system. OnCall Records runs on web browsers but is still an intranet-based system. This means a user must be inside of the hosting agency's firewalled domain. An unauthorized user would have to access the domain and then have a valid log -in to either the application or the database server. Administrators will be able to define user permissions by module that will determine what modules and fields a user has access to. OnCall Records security does not rely on underlying operating systems to provide access control. In addition to enforcing user IDs and passwords, the OnCall Records(`security system allows system administrators to control system and data access for Users and Groups by locking individual modules, tabs, records, and attachments. Proper use of the built-in security functions allows the system administrator(s) to fine-tune a system in which sensitive data is available only to authorized users. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 9 � A HEXAGON To facilitate security management, OnCall Records provides an interactive utility that allows administrators to establish an unlimited number of Security Groups. Using the Administration > Groups, Users, and Roles utilities, administrators can assign the capabilities (Roles) allowed for each Security Permission Group, for every module, tab, and individual record in the system. In addition, administrators can control access to any attachments (documents, photos, videos, and so forth) linked to module records. When a new user account is established, that user will be assigned to a Permission Group and the account will inherit all security Roles applied to that Group. There is no limit to the number of Permission Groups or the number of users that can be assigned to the group. Administrators can give users and/or groups one of the following access options for modules, tabs, attachments, data sheets, and other features: • None: No access • Read: Read-only access • Write: Read and edit access • Amin: Read, edit, and delete access • Custom: Specify an access option for each module and attachment type and tab By implementing security down to tab and feature levels, administrators can render any sensitive content invisible to any user. For example, a department administrator may require that a group of data entry users be able to access the Employee Module in order to keep employee records up to date. However, confidential data such as compensation, disciplinary actions, and associated paperwork can be made invisible to those users. OnCall Records provides additional security features. OnCall Records permits the ability to establish access rights down to the specific Attachment type within a record. For example, Users may have access to Evidence Images but not Autopsy Photos. Attachment access is governed at the overall Permission Group level. However, extended features support the ability for an investigator or officer to selectively secure an attachment to specific permission groups manually to accommodate special /� situations. Investigators and officers are also provided the ability to secure an Incident or Case report to specific Permission/� Groups manually when the record contains sensitive information. In the event that the Incident or Case is not secured, an investigator or an officer can use the OnCall Records Alerts feature to be notified when a user accesses a particular record. OnCall Records provides access security. The application supports the CJIS Strong password requirements. Additional CJIS user policies are met such as password renewal, password re -use, restrictions on multiple user sessions, and limited logon failure attempts. Encryption of the data outside of the sites' secured LAN is through their network or cellphone provider. Data -at -rest on the laptop requires the site to use the Encrypting File System feature or a third -party product such as Symantec PGPWhole Disk Encryption, Lumension, or Check Point Full Disk Encryption. Two -factor authentication is performed through the operating system and assumes the use of Active Directory centralized user access management. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 10 A HEXAGON O. Describe the process for submitting F/BRS/N/BRS data to the State of Florida to include the validation process for F/BRS and alerts to fields containing errors. Hexagon Response: Incident/Arrest data is entered and verified in OnCall Records, data can then be made available for the NIBRS Reporting Client through data transfer to the NIBRS database. Throughout the course of an investigation, the initial Incident/Arrest data may need updating in OnCall Records. For example, a new victim may come forward or a new piece of property may be located. These items will be added to the original Incident record in OnCall Records. Therefore, it is possible that an Incident/Arrest record marked as NIBRS Valid can become Invalid, during the course of an investigation. This is why a separate NIBRS application is required to perform final NIBRS validations prior to data submission to the FBI. Data entered in the Incident/Arrest module can be transferred to the NIBRS database one record at a time, or periodically by a scheduled Windows Service (such as when the user has installed the NIBRS Transfer Service). Typically, OnCall Records data will be transferred to the NIBRS database by the NIBRSTransfer Service, and a user can make updates to records in OnCall Records. For example, an investigation uncovers additional victims and updates the Incident by adding the victims to the OnCall Records record. This newly added data affects the NIBRS validation process. Instead of waiting for the NIBRSTransfer Service to transfer the updates, the user can transfer and validate the record immediately by clicking NIBRS Validate on the Incident/Arrest in OnCall Records. The data is then available in the NIBRSdatabase for the NIBRS Reporting Client to process for submission. The NIBRS Reporting Client is a reporting application used to validate and generate flat files for NIBRS data transferred from OnCall Records schema to NIBRS schema. Using this NIBRS Reporting Client application, a user can: • Process a single month's data (Incident & Arrest) with prior month's data (which is not yet submitted or needs to be resubmitted) • View the record counts for categories of Valid records, Invalid records, Not Validated records, and Valid with Warnings records for the selected month • View the records by applying filters for: Validation status Records for selected month/records that are prior to the reporting month • Validate/revalidate an individual record • Validate all qualified records for the selected month Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 11 A HEXAGON P. Describe any experience working with Crime Reports.com, LexisNexis, or other third -party crime analysis applications. Hexagon Response: Hexagon has experience interfacing to many common third -party crime analysis systems, such as RAIDS Online, Crime Reports, etc. and can provide pricing upon request. Q. Does the System have integrated tools to redact reports? If so, please describe. The "attachment manager" tool, available in the incident and case management modules, can be used to compile data sheets and attachments in a report into a single output file. This utility includes an option to create a merged .pdf document. Hexagon incorporates a third -party tool into OnCall Records at the server level to achieve this and this tool includes redaction capability. When generating a merged document, the user can enter words or phrases to be removed from the document in the Redacted Text ext area. Each word or phrase can be entered on a separate line in the text box and the output file shows a black, blanked out value where a match is found. This is an exact match function, and the redaction capability does require that the text in the original attachment can be machine read during the generation of the .pdf document. A non -redacted copy of the final document can also be generated with the redacted file for internal use. Aconfiguration option exists that automatically attaches a copy of the resulting compiled file to the original record. Current redaction capabilities are limited to the attachment manager tool, and that tool is only available from the Incident and Case Management modules. Even when the tool is used, the redaction is only available if the user elects to merge all documents into a PDF (the third -party tool operates on PDF files only). If more complex redaction capability is required, such as redacting text on images or graphics, most agencies would typically export the report to PDF, use the Adobe Acrobat Pro Redact tool, and then reattach the modified report to OnCall Records. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.14: RMS, pg. 12 A HEXAGON Section 2.15 — Interfaces and Integration A. Describe the Proposer's specific experience with the interfaces listed in AttachmentA — System Requirements Survey. Hexagon Response: Experience is described next to each of the interfaces listed below from Attachment A— System Requirements Survey. INTERFACE HEXAGON EXPERIENCE Tyler Odyssey - Pinellas County Court system (e.g., Evidence disposal, Subpoena Management, Case Management) Yes LPR Readers (e.g., Flock, Vigilant, etc.) Yes Cop Logic (included in solution preferred) Yes Tra CS Crash Reporting/Citation system (included in solution preferred) Yes FCIC Interface Postings, FCIC Interface Queries, NCIC Yes Mug shots (Dataworks Plus host at the County Sheriff's Office) Yes �/Pinellas LnX (http s://www. of p. g ov/ncjrs/virtual- library/a bstra cts/I a w-e nforce ment- i nfor m ati o n-e xc h a n g e-li nx) Yes Citations to Pinellas County Clerk of Court Not with this specific application, but Hexagon does have experience developing interfaces to comparable applications. IAPro (Internal Affairs) No FIBRS/NIBRS Hexagon has implemented federal NIBRS and other state NIBRS RAPIDPawn System No - OnCaii Records does not have a pawn module. Response to RFP 21-02 for CAD/RMS/Mobile / HEXAGON INTERFACE HEXAGON EXPERIENCE D.A.V.I.D. (FDLE driver and vehicle database - https.//david.flhsmv.gov/) Yes ELVIS(Florida Electronic License and Vehicle Information System - https.//www. elvisflonda.org/ We have not implemented an RMS interface with ELVIS, but we do have experience querying similar systems. CITY ORACLE (Employee Information) No experience with this specific application, but Hexagon does have experience developing interfaces to comparable applications with similar functionality (telestaffing). SPECIAL EVENTS (Off -Duty Detail) MANAGEMENTsystem (Included in system preferred). Examples. SEMS and CYAUSA (Rol1Koll) Hexagon requires additional information from the Consortium in order to determine if we have experience with this interface. Upon initial review, Hexagon has no experience with this specific application. Field Training LEO/LEAPS (Included in system preferred) Hexagon requires additional information from the Consortium in order to determine if we have experience with this interface. Equipment Room (e.g., Fleet, Inventory, Logistics, Weapons) Hexagon requires additional information from the Consortium in order to determine if we have experience with this interface. Kronos/Payroll No experience with this specific application, but Hexagon does have experience developing interfaces to comparable applications with similar functionality (telestaffing). CADintegration with VESTA (same as ANI/ALI integration) Yes Hexagon has experience with ANI/ALI integration CADintegration with Motorola Push - To -Talk and GPS tracking Yes CAD NG911 Hexagon's previous and current CAD solutions are NG911 compliant. Yes, we have experience with this. Dataworks Plus Facial Recognition No AADM(in-house developed citation application. Included in system preferred)) No experience with this specific application, but Hexagon does have experience developing interfaces to comparable applications with similar functionality. Pinellas County 911 CAD (in-house developed application) Yes (general CAD to CAD experience) VIPAR(PCSO in-house written arrest affidavit system) No experience with this specific application, but Hexagon does have experience developing interfaces to comparable applications with similar functionality. Response to RFP 21-02 for CAD/RMS/Mobile � A HEXAGON INTERFACE HEXAGON EXPERIENCE GTL- Offender Management systems (OMS) No experience with this specific application, but Hexagon does have experience developing interfaces to comparable applications with similar functionality. Everbridge Yes LEO-Level GPS Tracking (e.g., Radio, Smartphone, laptop, tablet.) Yes RAPID SOS (cell phone) integration into CAD Yes B. Describe the proposed approach to application integration. The Consortium's standard is for APIs or REST/Web services. Hexagon Response: Hexagon's proposed approach to application integration includes RestAPI and HxGN OnCaii Integration Engine (OIE). Re stAPI For requirements that go beyond the scope of configuration, OnCall Dispatch enables direct integration via a RESTful API. The API allows the creation of customized messages, notifications, components, and microservices using standard development tools and methods. OnCall Dispatch's API and microservice architecture make the writing, delivery, and maintenance of custom code easier, more efficient, and less disruptive. Granular, self-contained functional modules allow independent manipulation or modification of individual services and supporting service infrastructure. Reducing the interdependency between services allows agencies to quickly implement and deploy component changes without unplanned impacts on other services. OnCaii Integration Engine Hexagon OnCall Integration Engine is a server component that acts as a broker, an orchestration platform and a data aggregator facilitating OnCall interface support and development with a consistent API, secure endpoints and flexible workflow that leverage standard integration patterns and standards. OnCaii Integration Engine provides first responder personnel in the field access to Hexagon's OnCall computer -aided dispatch (CAD), OnCall record management (RMS), and third -party RMS systems via a handheld smartphone or tablet running OnCall Mobile apps. This part will be hosted in a Microsoft Azure environment. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON C. How is the proposed solution extensible, al/owing for future changes? Hexagon Response: The OnCall architecture is a scalable, flexible architecture designed to leverage both Container technology and Microsoft Azure Platform services to provide the ability to both scale up and out as needed. Additionally, Hexagon incorporates RestAPI and OnCall Integration Engine to facilitate system integration with third party software. Hexagon believes these integration standards provide the Consortium with a system that is extensible and allows for future changes/addition of interfaces. Should the Consortium identify a need for additional interfaces in the future (after Hexagon system cutover), then the Consortium would make the request with your designated Hexagon account manager who will work with the Consortium and provide a quote to accommodate the Consortium's request. D. Does the System incorporate open data sharing models and standards such as the Global Justice XML Data Model (GJXDM) or the National Information Exchange Model (NIEM)? If so, what version numbers? 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 Informer, which is used to query third -party external systems including the State/NCIC, and supports several communication protocols including ODBC, TCP/IP, and Win HTTP. 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 Hexagon solutions include Fairfax County, and Richmond, Virginia. Hexagon has also implemented NIEM-compliant IEPDs as part of its CAD -to -CAD Interoperability Framework in support of the National Capital RegionData Exchange Hub (DEH). Hexagon has also deployed a NIEM-compliant IEPDs in support of the Central Station Alarm Association (CSAA) external Alarm interface for the direct processing of third party alarms into the Hexagon CAD solution, without operator intervention. Hexagon diligently monitors the ongoing development of the N-DEX standards for RMS information exchange as part of our involvement in IJIS and plans to support these standards in the future. Hexagon is an active participant in the IJIS Institute and has held working committee positions on the CAD NIEM Working Committee. If export and/or import of GJMXL data is desired then an interface will be necessary and is not currently included in the proposed solution. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON E. The Consortium anticipates desiring interfaces to new systems and applications as technology develops and needs change over time. How can data stored in the System be made accessible to external systems in a cost-effective manner? OnCall Dispatch enables direct integration via a RESTfoi API. The API allows the creation of customized messages, notifications, components, and microservices using standard development tools and methods. OnCall Dispatch's API and microservice architecture make the writing, delivery, and maintenance of custom code easier, more efficient, and less disruptive. Please note due to cloud security, Hexagon will be required to develop any desired interfaces, which are not included in the proposed solution and quotes can be provided upon request. F. Will vendor engagement be required to develop future interfaces/extracts? If so, explain the process. Hexagon Response: If the Consortium requires Hexagon to provide an interface to a third party product that is not included in the original agreement, then yes, Hexagon would need to be engaged in that process in order to develop the interface. If this work was needed prior to the system cutover, then a change order would be required. If this work was needed during the first contract term, but after system cutover, then a new Order would be required under the existing Master Terms. G. Describe how the Consortium can use APIs to extract data from the System. What data can be extracted? The OnCall solution includes multiple API's that are leveraged for interfacing with 3rd party systems and Vendors. The Records and Dispatch products include Rest APIs that securely expose service endpoints that can be used to export or import data. The OnCall solution also provides an Analytics product that includes a warehouse with Data Models that are intended to provide access to OnCall users to insights and to important Data in the system. Because there is the inclusion of Read-only replicas with the Business Critical tier of Azure SQL Service, the agency can use these replicas to view and extract Data. H. Describe how the System supports PowerB/. Hexagon Response: Hexagon's data intelligence solution, OnCall Analytics, integrates Power BI out -of -the -box. OnCaii Analytics offers easy -to -use, business -ready content and visual reports that leverage Hexagon's CAD and RMSsystems and other data sources for monitoring events, aligning resources to demand, supervising Response to RFP 21-02 for CAD/RMS/Mobile � A HEXAGON PSAPperformance, maintaining governance and oversight, and much more. By allowing more employees to visualize data, run reports, and conduct analysis, the suite empowers organizations to improve performance and productivity. Additionally, the process to move the data from OnCall Dispatch and OnCall Records into the OnCall Analytics data warehouse is configured to automatically happen at a time interval determined by the Consortium. When creating and interacting with the reports, the system automatically queries the data warehouse for the requested information. O nCali Analytics includes 22 inter active Power BI report templates for OnCall Dispatch and 28 interactive Power BI report templates for OnCall Records. I. The Consortium collects and saves digital media from a number of external sources. The Consortium desires to store this media in the future System. 1. What file types can be natively saved and supported in the System? Hexagon Response: Dispatch users can add attachments to Events, Scheduled Events, Messages, Special Addresses, and Special Situations (premise alerts). The Administrator can configure a customized whitelist to allow only specified file types in OnCall Dispatch and OnCall Mobile Unit. There is a default whitelist included with OnCall Dispatch that includes the following file formats for attachments, by default: • png • •Jpg .• svg • .gif • .txt • .html • .wav • .pdf • .mp3 • .mp4 OnCall Records provides the ability for agencies to attach images, videos, and audio files directly to RMS records using the Image/Media Viewer. In addition, users can attach from a file or scan documents directly into the Document Viewer component within nearly every module in the RMS. Administrators can set secured access to specific record types to restrict access to confidential attachments. Virtually any type of attachments are supported. These include Images (JPG, BMP, PNG), documents (XLS, DOC, PDF, TIFF) audio (WAV, AVI) and video (MPEG, MPEG4, etc.). There is no restriction on the file type format, however the user will need the appropriate application and/or codec to support viewing and playback of audio and video media files. Response to RFP 21-02 for CAD/RMS/Mobile � A HEXAGON 2. What file types can be natively viewed and supported in the System? Hexagon Response: As described above, both OnCall Records and Dispatch allow for attachments, which would be downloaded, opened, and viewed in their native formats. 3. /s the Consortium able to limit the types of digital media fi/es that are allowed into the System to a subset of those file types that are supported? Yes. For example, in OnCall Dispatch the Consortium can configure a customized whitelist if there are This certain file types that should be accepted as attachments. I his can be configured by the System Administrator. If limits are configured, when a user attempts to upload a file with an extension outside of the defined list, the upload fails. For OnCall Records, the system provides a system administrator configuration to limit the size of the media file in MB that may be attached. 4. Can the System convert digital video media to a standardized video format? If so, describe the process for file conversion. /f not, is an alternative approach recommended to enable viewing video content saved in non-standard, unsupported file types. Hexagon Response: OnCall does not convert video media to different formats. However, video content can be attached and viewed via the attachment feature in each product as described above. The user will need the appropriate application and/or codec to support viewing and playback of audio and video media files. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Proposed Interfaces and Assumptions Overview OnCall Dispatch's out -of -the -box capabilities, configuration and integration tools, and Rest API enable systems to be quickly and sustainably tailored to agency and user needs with less coding. Reducing the maintenance burden of custom code makes it easier to update the system and adapt it to new requirements. OnCall Dispatch reduces the need to code by providing out -of -the -box interfaces (linking OnCall Dispatch to Hexagon's public safety analytics and records management systems, third -party capabilities, and interoperability standards) and a powerful low -code / code -free interoperability framework for creating custom integrations. The interoperability framework builds intelligent connectivity between OnCall Dispatch andother applications, devices, and sensors via enterprise integration and edge computing This I his secure and powerful yet lightweight integration platform replaces costly, slow to change, and fragile point-to-point integration with flexible, standards -based integration. By separating product and interfaces, it also provides a buffer against changes in the underlying system, making integrations more robust and reducing maintenance effort. Hexagon's proposed systems are capable of interfacing with third -party applications, providing the flexibility and customization our Customers need to operate. Hexagon interfaces are categorized as follows. • Cu stor„Off the Shelf (COTS) — these interfaces are designed to perform with little configuration. Our COTS interfaces enable functionality such as integrated paging and notifications, alarms, and third party database queries. • Standard — these interfaces are designed to connect Customers to frequently -requested third party software or another CAD system. • Custom — these interfaces are designed according to the Customer's needs. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON OnCall Dispatch Interfaces Proposed CAD COTS Interfaces ANI/ALI Hexagon has proposed our COTS ANI/ALI interface to meet this requirement. Description. OnCall Dispatch supports FCC Phase II requirements for cellular 911 calls and 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 system, as dictated by the NENA standard or FCC requirements), and uses this information to show the callers geographic coordinate location on the map. The nearest civic address can alsobe estimated and displayed. The exact format of this data in the ANI/ALI packet must be supplied by the Customer (in conjunction with their phone system supplier). The ANI/ALI interface works with the Call -taker component of OnCall Dispatch Advantage to provide Next Generation support for solicited multimedia data associated with a call. Call -Taker is designed to support new modes of communication, such as SMS and MMS text (photos and video) and allows the addition of new call types going forward. It provides global support for handling Next Generation data processed by the PSAP. As a site transitions to a full Next Generation implementation, Hexagon's Call -Taker GUI will provide a seamless transition for the call -taker. Assumptions. • Hexagon assumes that the Customers ANI/ALI controller supports NENA Format Versions 1 and 2 (Fixed Length ASCII), NENA version 3 (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". • The ANI/ALI interface component of the OnCall Dispatch System /will provide the interface to an ANI/ALI controller, and will accept ANI/ALI packets containing ASCII, tagged delimited, or XML data via an Ethernet Network (TCP/IP) or an RS-232 connection • Hexagon assumes that the ANI/ALI protocol packet provides the number, address and answering position of the call when answered. • The FCC order released June 3, 2005 requires that all VoIP vendors, serving U.S. customers, must offer service to route 911 V0IP calls through the current E-911 infrastructure. This means that all VOIP 911 calls from registered subscribers will be received through the PSAP's 911 trunks and handled by their ANI/ALI Controller. The PSAP is responsible for ensuring that their ANI/ALI Controller is capable of handling the ALI Database lookup for these calls. ANI/ALI packets for VoIP calls will be received by the CAD system, over the same CAD link, from the ANI/ALI Controller, as the landline and cellular calls. VoIP calls with a caller's address will be handled like landline calls and VoIP calls with a location specified by coordinates will be handled like Phase II cellular calls. • If the center requires an interface to a method of receiving ANI/ALI or other Data for VoIP calls other than the Customer must provide complete specifications of the device or service providing the data. Response to RFP 21-02 for CAD/RMS/Mobile iff A HEXAGON • Given the current uncertainty in the telephony provider market on how SMS/MMS information will be transmitted, Hexagon assumes that the SMS/MMS information is being provided through the external SMS provider. Constraints. • The Customer is also responsible for the maintenance and support of any hardware, software, or cabling required to provide the physical interface between the ANI/ALI Communications Server and the ANI/ALI Controller. Hexagon's demarcation point, for responsibility for the ANI/ALI stream, is at the port or socket on the communications server. • The Customer must supply a complete and accurate description of the ANI/ALI controller interface and data it provides for CAD field mapping. HxGN OnCall Dispatch I Informer • NCIC/FCIC • LnX • Odyssey • Pinellas County Criminal Justice System Pinellas County Sheriffs Office Arrest Booking/Jail Hexagon has proposed our standard OnCall Dispatch I Informer interface to meet this requirement. Description. Informer provides a set of forms designed to run queries on local, provincial, regional, and/or national crime information databases, such as the National Crime Information Center (NCIC), or to databases associated with external applications. 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 OnCaii 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. These services are orchestrated to route requests and responses between OnCall and the external systems. Response to RFP 21-02 for CAD/RMS/Mobile 10e. A HEXAGON 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: Person (wanted, missing, driver's license) 2. Vehicle (stolen, registration) 3. 4. Boat (hull number, registration number) 5.Gun (serial number, caliber, make) 6. Hazmat (United Nations Number) 7. Lojack (lojack id, reply code) 8. Additional OnCall dialogs, request messages, and response displays can be developed through extra services at additional cost. Informer includes three providers that can be configured to communicate with external systems. These are. 1. Open Database Connectivity (ODBC) 2. Com mSys 3. OnCaii 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 • flit 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. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Assumptions. • Implementation of the CommSys provider requires at a minimum the purchase of the CommSys ConnectCIC module and its data -mining feature (which is included in this proposal). 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 at additional cost. • 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. Lin/, Odyssey, Pinellas CJS, Pinellas Booking/Jail Assumptions: • The following inquiries are iinncluded in this bid. Person Inquiry by (NAM, DOB, SEX) or (OLN), State Vehicle Inquiry by (LIC), State Gun Inquiry by SER, MAKE, Caliber, Model Article/Property Inquiry by SER, MAKE, MODEL NOTE: 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. • The system supports an ODBC connection, SQL -based inquiries. NOTE: 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 • The inquiries will be supported from the Person, Vehicle and Gun forms that are included in the interface for OnCall Dispatch Informer 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 beings. Response to RFP 21-02 for CAD/RMS/Mobile iff A HEXAGON • 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. HxGN OnCall Dispatch I Call -Taker Interface • For Text-to-911 and RapidSOS to meet this requirement. Description. OnCall Dispatch I Call -Taker Interface is the product that enables customers to connect the OnCall Dispatch I Call -Taker product to various external systems to receive additional important call information and/or utilize other third -party tools. Once Call -Taker Interface is connected to these external systems the data is presented neatly and streamlined in the OnCall Dispatch I Call -Taker product. ACall -Taker license provides OnCall Dispatch with the user interface to use the tools, but a Call -Taker Interface license is required for each interface that the system connects to. A Call -Taker Interface license is required for each of the following external system connections. • SMS/MMS systems (example being Text to 911) • Location Accuracy systems (examples being Ra pidSOS and AML) Assumptions. • Call -Taker interface requires OnCall Dispatch I Call -Taker (included as a component of Dispatch Advantage) as a prerequisite. Text to 911 Hexagon assumes: • Design of interface and components imported are subject to the limitations offered by the Vesta i3 Log Events interface. • The interface conforms to NENA i3 Version 2 specifications. HXGN Or,Call as patch I ALPR Interface • For Flock, Vigilant Assumptions. • Assumes information will be received from ALPR vendor in XML or JSON Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON HXGN OnCall Dispatch I PTT (push to talk) • For Motorola Radios Hexagon has proposed our standard OnCall Dispatch I PTT (push to talk) interface to meet this requirement. Description. PTTinterfaces to a radio system controller over a network connection (TCP/IP) or a serial (RS-232) connection to provide PTT information to a dispatcher workstation. Each time a radio unit in the field transmits to the dispatch environment, the identification of the transmitting unit is displayed within OnCall Dispatch. PTT also supports a Unit Emergency signal from a PTT radio. PTTincludes Push to Talk Bannering and an Emergency Button. An emergency alarm triggers the CAD Unit Emergency command, which notifies all dispatcher positions (and optionally all call taker positions) of the emergency. CAD operators are alerted by enabling the Unit Alarm button (the text font color changes to RED), and an audible warning. PTT will also display a Unit Emergency notification dialog box. The radio ID provided by the vendor is mapped to the Unit ID. When PTT is activated by a radio user, the radio ID is used to query the database and display configurable unit information in the Banner window. Assumptions. • OnCall Dispatch I PTT interface supports the following radio systems. Motorola MCC7500 — MCC7500 Console Motorola Centracom (being replaced by the MCC7500) — Centracom Gold Elite (MCGE) Console Motorola Sims II — SIMS II CADI • Hexagon assumes that the Customer has access to the necessary port on the radio system and that the Customer will supply the SDK necessary to provide the interface between PTT and the radio system. • If the site has more than one PSAP the other PSAP will be running the same radio system. • One license of PTT is required per site and can connect to multiple radio systems. • To support redundancy, the radio system controller must support multiple connections. This is done through network connections (TCP/IP) or by multiple physical connections (RS-232). Constraints. • The Customer is responsible for any software licensing required by the radio vendor to provide console connectivity by PTT. • The Customer is responsible for providing any hardware/software and licenses on the radio system as required for implementation of this interface to the radio system. • The Customer is also responsible for providing complete and accurate documentation on the radio system interface, which is assumed to be over an RS-232 or TCP/IP connection. • The Customer is responsible for providing any specific SDK necessary to implement the interface. Response to RFP 21-02 for CAD/RMS/Mobile ig A HEXAGON • At a minimum, PTT packets received from the radio system must include the talk group/channel being used and the radio ID. Please ensure that the communications server has sufficient RS-232 serial ports. • 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. Prcpcsad CAD Standard Interfaces CAD to CAD OnCall Dispatch Interface • Pinellas County Regional 9-1-1 Communications Center CAD Hexagon has proposed CAD to CAD OnCaii Dispatch Interface to meet this requirement. Description. The CAD to CAD Interface is based on a rules -driven, real-time transfer of unit and event information to and from Hexagon OnCall System and third -party CAD systems. Assumptions. • The third -party CAD vendor is expected to conform to the Hexagon XML message format specification. Constraints/ • The Customer is responsible for any software/hardware/data required to implement communications with the external systems. • Customer is responsible for coordinating with the third -party CAD vendor and other PSAPs RapidSOS OnCall Call -Taker Interface Hexagon has proposed RapidSOS OnCall Call -Taker Interface to meet this requirement. 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. Assumpttions. • Call-ta ker interface requires Onl..all Dispatch I Call-Ta ker (included as a component of Dispatch Hexagon has also included pricing for the "connector" between RapidSOS and the Call -Taker Interface API (HxGN OnCaii Dispatch I Call -Taker Interface) • Customer must obtain RapidSOS credentials before interface can be tested. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Dispatch Alerts OnCaII Interface • For Everbrid ge Description. The Dispatch Alerts OnCall Interface is an Xalt-based integration that 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. 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. ExternaI Alarms OrCaii Dispatch Interface • For ASAP to PSAP Description. The APCO ASAP Sta nd/�ard is supported with this interface ass an Xalt Integration based application usi ru the External Alarms Onrall Dispatch Interface. It allows OnCaii to interface with the APCO International Automated Secure Alarm Protocol (ASAP) Alarm System (also called "ASAP to PSAP"). The Automated Secure Alarm Protocol (ASAP) by the Central Station Alarm Officials (APCO Intl). 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. Assumptions. • The Customer is responsible for coordinating deployment with the Monitoring Association directly. • The XML format required by the external systems must be provided to Hexagon. • For import interfaces and bi-directional interfaces created using Xalt, data will be provided via either a shared directory on the agency's network or via a web service where the data can be pulled. • For export interfaces, the export will create XML information and pass it to a web services provided by the vendors for the external systems. Only COTS fields will be exported by the interfaces. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Con straints. • 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. PLT Radio OnCall Dispatch Interface • For tracking Motorola radios Description: The PLT Radio OnCall Dispatch Interface is an nterface 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. • The XML format required by the external systems must be provided to Hexagon. • For import interfaces and bi-directional interfaces created, data will be provided via either a shared directory on the agency's network or via a web service where the data can be pulled. • For export interfaces, the export will create XML information and pass it to a web services provided by the vendors for the external systems. Only COTS fields will be exported by the interfaces. • The Hexagon PLT Radio Interface connects to the Motorola ASTRO P25 GPS data via the Motorola MUPS feed as defined in the SDK provided to Hexagon Con straints. • 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. OnCall Records Interfaces NIBRS Description: OnCall Records provides for incident data -capture and includes a NIBRS tool for the State/Federal reporting manager to translate and validate NIBRS data against federal reporting standards and codes prior to submitting it to the FBI. If desired, the translation and validation tool can be customized to support Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON State IBR requirements. Once translated/validated, this data can then be compiled into a report for submission to the appropriate system. Hexagon will provide services to install and configure NIBRS in Development, Staging, and Production environments. This will include time to provide patch updates that may be released during the project before Cutove r. Hexagon has proposed access to Federal and Florida State NIBRS in this response. Coplogic Record s Interface/� Hexagon has proposed Coplogic Records Interface to meet this requirement. Description. /� Hexagon will install the standard Coplogic interface that will monitor a shared directory for XML files liThe by Coplogic system. I he interface will import the data into the incident Records. Assumptions. • has worked with the Coplogic system before and assumes that file formats and the data exchange will be the same as in the past. • Data will be provided via either a shared directory on the Customer's network or via a web service where the data can be pulled. • It is expected that the interface will require an on -premise component (i.e. Windows Service) that C will need to be able to connect to the loud hosted interface. 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. Custom Interface for RMS Informer 1 ran s actions • For NCIC/FCIC, LinX, Odyssey, Pinellas County CJS, Pinellas County Booking/Jail Assumptions. /� • Dependent on Informer json returns being able to be displayed in OCR Twithout additional effort • The Informer Server & CommSys must have the ability to process the transaction • Atest state server must be available -that can be used unaccompanied by vendor personnel • Not all transactions are available in all modules. Response to RFP 21-02 for CAD/RMS/Mobile ILA HEXAGON Custorr, Interface to Datawork s Mug sInots Direction: 1-Way Import Module(s): Booking/Arrest, Court Document, Inm Format: XML services, API, FTP Hexagon will create an interface to import information from the GTL Offender Management System into OnCall Records. Assumptions. • It is assumed that data passed from the GTL system will be imported into the relative module • It is expected that the interface will require an on -premise component (i.e. Windows Service) that C will need to be able to connect to the loud hosted interface. Custom Interface to GTL — Offender Management System (OMS) Direction: 1-Way Import Module(s): Booking, Master Name Format: TBD Exchange: File drops to shared directory Hexagon will create an interface that will import mugshot images. These images will be attached to the related booking and/or name record in the OnCall Records environment. Assumptions. • It is assumed these images will be exported by Dataworks to a shared directory. • Hexagon will create an interface that will monitor for these files and will import these into the OnCall Records system. • It is expected that the interface will require an on -premise component (i.e. Windows Service) that C will need to be able to connect to the loud hosted interface. Custom Interface to VIPAR Direction: Bi-directional Module(s): Court Document Format: XML, Delimited, Fixed Length, JSON, etc. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Exchange: File share, API, FTP, etc. Hexagon will create an interface that will import affidavit information supplied by the VIPAR system and that will export updates to the arrest/affidavit information and send to the VIPAR system. Assumptions. • It is assumed that the data will be provided in a common format (i.e. XML, delimited, fixed length, JSON, etc). • It is also assumed that the data will be exchange using a common exchange method (i.e. share directory, API, FTP, etc). • It is expected that both interfaces require an on -premise component (i.e. Windows Service) that will need to be able to connect to the Cloud hosted interfaces. Cu store Interface to AADM (in-house citation application) Direction: 1-way import into RMS Module(s): Citation, Court Document/JUV Court Document Format: N/A AADM SQL Database Hexagon will create an interface that will pull citation information from AADM's SQL database. Assumptions. • It is assumed that an on -premise component (i.e. windows service) will query AADM's SQL database for citation, warning, and ordinance violation information. • The on -premise component will connect to the cloud hosted component of the interface and import the data into the citation module in OnCall Records. • Hexagon will create/�a separate interface to import Notice to Appear information into the Court Document/Juv Court Document modules. Other Interfaces Hexagon acknowledges the County's request for the interfaces listed below. While the proposed OnCall system is capable of such interfaces, Hexagon requires additional information and clarification on desired functionality before an accurate bid can be provided for each of the below. For a few of these, Hexagon did not bid interfaces per the responses in the Interface Questions spreadsheet and the answers we received to vendor questions which noted interfaces as optional. • IAPro (Internal Affairs) Hexagon can provide this interface, but it was not included at this time because the Consortium identified it as optional. Hexagon is willing to discuss this requirement upon request. The existing functionality in OnCall may be sufficient without this interface. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.15: Interfaces and Integration, pg. 20 HEXAGON • Rapid Pawn System Hexagon OnCall Re • DAVID/ELVIS pawn module to interface to. Hexagon Consortium provide interfaces to query DAVID and ELVIS, but those have not been included since the Consortium identified these as optional and said they were not needed at this time. Hexagon is willing to discuss this requirement upon request. • City Oracle This interface is not included. Hexagon would need to discuss this requirement with the Consortium to understand if we can provide the necessary interface. • Special /Events (off -duty detail) Management system The Consortium indicated this interface is optional. Hexagon is willing to discuss this requirement upon request. • Field Training LEO/LEAPS The Consortium indicated this interface is optional. Hexagon is willing to discuss this requirement upon request. • Equipment Room (e.g., Fleet, Inventory, Logistics, Weapons) The Consortium indicated this interface is optional. Hexagon is willing to discuss this requirement upon request. • Kronos/Payroll The interface spreadsheet indicated this requirement was to send hours and schedule information from CAD to payroll. This functionality is not currently available in OnCall, but other Kronos telestaffing functionality is available. Hexagon would need to discuss this requirement with the Consortium to understand if we can provide the necessary interface. • Dataworks Plus Facial Recognition Hexagon does not support facial recognition, however, we understood per the interfaces spreadsheet provided by the Consortium that this Dataworks requirement was the same as the Dataworks mugshots interface which we did provide a bid for. Hexagon would need additional information to determine if we can meet this requirement. • Pinellas County Clerk of Court Upon initial review of this requirement, Hexagon believes we may meet this requirement without a separate interface and we have not proposed an interface at this time. Hexagon has proposed an interface/�to AADM system and we assume AADM will export the citation information to the Clerk of Court. • TraCS Hexagon has provided the ability to prepopulate crash reports, tickets, and field interviews with NCIC/FCIC data in the Consortium's TraCS mobile data environment. Note, this is not a full interface involving import or export of reports. If the Consortium requires additional integration with TraCS that can be discussed to determine what additional services or costs may be associated. Hexagon assumes the following. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.15: Interfaces and Integration, pg. 21 A HEXAGON The user will execute an OnCall Dispatch/OnCall Mobile Unit command that will raise a notification identifying the Stete/NCIC data needing to be shared with the third -party system. The third -party system will receive this notification via a connection to the OnCall Dispatch CAD Notification Service (CNS). The third -party system will use thee notification data to make a OnCall Dispatch RestAPl call to retrieve the full State/NCIC data. The data returned from this REST call is in JSON format. The Consortium is responsible for its connection to the third party system. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.15: Interfaces and Integration, pg. 22 A HEXAGON Section 2.16 — Geographic Information Systems A. Describe the methodology for ingesting, validating, correlating, using, storing, and displaying location data and information, respectively, throughout the proposed solution. Hexagon Response: OnCall Dispatch supports native integration with Esri's GIS technology. By extension, any mapping format that can be ingested into the Esri GIS system can be visualized within OnCall Dispatch. The geocoder should serve appropriately attributed street centerline data, point address data and gazetteer -modeled common names. Esri supports many geocoding models. The Router will require street centerlines with appropriate attribution and topologic connectivity. The map display is at the discretion of the project to determine. OnCall Dispatch consumes GIS services and data provided by the Consortium. Based on our review of the RFP, the Consortium appears to utilize ESRI technologies to create, manage, and publish GIS-related services. OnCall Dispatch can natively consume those services. However, this system requires a separate, high -availability set of servers dedicated to the public safety environment. Those servers can use the same datasets and locator setups described by the Consortium, provided the same content is available for defining and publishing those locators. ESRI's locator technology requires the "rebuild" of the locator to reflect updated data. Actual capabilities of the locator services, quality of the data, etc., are all based on the Customer's available data and the ESRIlocators themselves. Because OnCall is using ESRI services to perform geocoding, OnCall does not support real-time updates. It is important to note that OnCall Dispatch, as a modern CAD software platform, does not house or otherwise contain its own CAD Mapping System. OnCall Dispatch utilizes a published map tile service for map display in WMS, WMTS, or ArcGIS/REST formats. OnCaii Dispatch utilizes ESRI published web services for geocoding, reverse geocoding, and routing, making use of the FindAddressCandidates, Suggest, etc. Location suggestions and validation can be done against centerlines via interpolated coordinates against an address range, point addresses (parcels), aliased street names, common place/point-of-interest names, etc, all using native ESRI locator technologies. OnCall Dispatch provides integrated mapping. Maps are displayed on demand, drawing data from the mapping source (GIS server), which will allow the Consortium to avoid a conversion/import routine. OnCall Dispatch can display all standard ESRI map layers and can display a variety of web -based map layers, including Open Streets, Bing, and more. OnCall Dispatch is an "available anywhere" solution, delivered via web browser. Components of OnCaii Dispatch (including all mapping components) are hosted in a server environment and delivered to a client when accessed. Map files are neither pre -loaded nor permanently stored on a client. Like OnCall Dispatch, the mapping subsystem must be set up in a highly available configuration to ensure mapping services are always available. Some commercial providers, such as Bing Maps, already implement a highly available service. It is strongly recommended that mapping subsystem implemented be dedicated only to supporting OnCall Dispatch because. Response to RFP 21-02 for CAD/RMS/Mobile HEXAGON • /Performance and availability requirements must meet mission critical standards ® Change control management is essential Bing does not apply to commercial online providers such as Maps Map Overview The main window for OnCall Dispatch is the Map View, which includes a series of interactive icons with menus and a workspace layout with the option to display different types of data. OnCall is designed to display all the relevant data a Dispatcher needs to perform most efficiently using a combination of the map view, event board, and unit board. The screenshot below shows the common icons/actions when using the map. Figure 1: Map View of OnCall Response to RFP 21-02 for CAD/RMS/Mobile Section 2.16: Geographic Information Systems, pg. 2 / HEXAGON Figure 2: Explanation of Map View in Figure 1 When there are too many events or units in one place to be displayed on the map, the individual icons are combined into clusters of shapes with a number indicating how many are present (see figure 3). The color of the icon is the color of the highest priority event in that cluster. Rgere 3: Numberof clestered event5iunt5 Icons on the Ma There are numerous icons found on the map. The following chart contains some of the default event and unit icons. These may vary based on each system's individual configurations. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.16: Geographic Information Systems, pg. 3 A HEXAGON Figure 4: Default Event and Unit icons Event Icons Double-click event icons to open the Event Panel. Each event icon has a diamond attached to it. The color of that diamond indicates the events priority level. If one or more units are assigned to an event, the number of assigned units is indicated by a circle at the bottom left of the event icon. The following are examples of events with various priority levels and assigned units. Figure 5: Event /con example Unit Ions Double-click unit icons to open the Unit Panel. Units have circular images attached to the bottom right of the icon that indicates the unit's availability status. The table below shows three basic units and their associated statuses. Figure 6: Unit /con example Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Map Layers Use the Map Layers icon in the top left of the Map View to change the predefined Base Layers and • Base Layers. the lowest, most basic level of the Map View. Only one Base Layer may be selected at one time. • Overlay Layers: An optional source of map data that can be integrated into the base Map View. Multiple Overlay Layers may be selected at one time. All changes made using Map Layers are saved automatically and applied the next time the user logs in. To select a new layer, click the Layers icon in the top left corner of the Map View to open the Layers Panel. Base Layers The Base Map Layer is changed by toggling different predefined sources on and off, picturedp as follows. For example, if the Base Map Layer is currently OpenStreets but the user wants to use MapBox, this change can be made through the toggle feature. Only one base layer source can be used at a time. Figure 7: OnCall map base layers Overlay Layers Overlay Layers are optional sources of map data that can be integrated into the map's base layer. Examples of these data sources may include imagery, weather, projections, polygons, or special situations. Polygon layers may include beats, agencies, and units. The following image shows the application of polygon layers to the map. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Figure 8: Polygon overlay map layer Map Filters If enabled by a system administrator, the Map View may be filtered. Unit filters are distinct from event filters, and both may be enabled at once. If filters are enabled, the user can access them by clicking the Filter icon to open the Map Filters menu, pictured as follows. The blue bar shows how many units and events are currently showing on the map. Figure 9: OnCall map filters Response to RFP 21-02 for CAD/RMS/Mobile Section 2.16: Geographic Information Systems, pg. 6 � A HEXAGON Unit Filtering There are 2 ways to filter units on the map. • Sync with Unit Board. The unit markers on the map are dynamically filtered based on the filters the user sets in the Unit Board. If a user changes a filter on the Unit Board or types in the search field, the resulting filtered units are shown on the map. • Sync with named filter. The user selects a saved filter to filter the units on the map. The user may create saved filters on the Unit Board. Event Filtering There are 3 ways to filter events on the map. • Sync with Event Board: The event markers on the map are dynamically filtered based on the filters the user sets in the Event Board. If a user changes a filter on the Event Board or types in the search field, the resulting filtered events are shown on the map. • Sync with Event Board Tab: The user selects an Event Board tab to filter the events on the map. The user may create filtered tabs on the Event Board. • Sync with Event List: From the Event Board, the user may select an Event List to filter the events on the map or create their own Event List. figure 10,' Draw grapfr,2s panel Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Drawing on the Ma lap The Draw r. Graphics panel lets users view, add, and edit map graphics. Any graphics already associated with the selected event also display on the map and in the Associated Graphics panel. These graphics allow the user to highlight important areas relative to the selected event. Any graphics created and saved for an event are only visible while that event is selected. From the map, right -click an event to show the Radial Context Menu. Click More Options and then Draw Graphics. This prompts the Draw Graphics panel on the right side of the map (figure 10). Create Map Graphics The Draw Graphics panel lets users create, delete, and select graphics. To create a graphic, the user is given 6 options: Shape selector, Draw rectangle, Draw line, Draw polygon, Add point, and Draw circle. For example, in the following image, the event shown is a parade. The user has drawn a rectangle around the relevant areas to indicate the parade route. Figure 11: Graphic drawn on map of parade route Geofencing The County can also use Geofences to denote specific areas on the Map. Dispatch Advantage users can create, modify, and remove geofences as needed. After a geofence is created, notifications are sent when other Map elements interact with the geofence perimeter (for example, when units enter or exit the perimeter or when events are created within the perimeter). Response to RFP 21-02 for CAD/RMS/Mobile Section 2.16: Geographic Information Systems, pg. 8 A HEXAGON Geofence Editor in OnCall Dispatch Using the Geofence Editor, users can create, delete, and modify geofences by updating their properties. Available geofences are presented in a list on the left side of the editor. Selecting a geofence populates the right-hand pane with information about that geofence. On the Map, users can select the geofence icon in the upper -left corne of the map to open the Geofences management panel that lets you choose the geofences to display, adjust their opacity, show active geofences, and control whether geofence labels are hidden. After a geofence is created, notifications are automatically sent when other map elements interact with the geofence perimeter (for example, when units enter or exit the perimeter or when events are created within the perimeter). As part of core functionality, Mobile Unit users can receive notifications The activity involving the geofence. I he Administrator or Dispatcher who creates the geofence configures who will receive the notifications. Users have the option to toggle certain geofences on and off by opening the Geofences pane from the geofence icon on the map (see figure to right). When the geofences feature is turned on, users receive notifications when elements on the map interact with the geofence parameter. For example, users receive notifications when units enter or exit the geofence parameter or when an event is created within the geofence. Geofence pane in OnCall Mobile Unit Response to RFP 21-02 for CAD/RMS/Mobile Section 2.16: Geographic Information Systems, pg. 9 A HEXAGON Staging Areas The Map displays staging areas when the Staging Areas layer is turned on in the Layers panel. Staging areas are represented on the map by the icons indicated in the example below. Staging Areas on the Map Each icon features a color -coded circle on its lower -right side that indicates the current status of the staging area. B. Describe the mapping and situational awareness solution to be available on each client CAD terminal, including dispatching terminals and mobile clients available to field officers. Hexagon Response Since OnCall is browser based, all clients can see the same data with the ability to filter based on user agencies and roles. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.16: Geographic Information Systems, pg. 10 A HEXAGON C. Describe features that can be displayed across the CAD/RMS/Mobile environments. For example, floorplans, gate codes, caution notes, alerts, etc. Hexagon Response: OnCall contains a special situation layer with attachments showing floorplans and cameras. Gate codes, caution notes and alerts are supported based on the agency's configured data layers. D. Does the proposed solution require pre -loading ofgeospatia/ data and maps? /f so, p/ease detail the process of uploading, updating, and distributing such assets across all clients, desktop and mobile. OnCall Dispatch is an "available anywhere" solution, delivered via web browser. Components of OnCaii Dispatch (including all mapping components) are hosted in a server environment and delivered to a client when accessed. Map files are neither pre -loaded nor permanently stored on a client. OnCall consumes and displays GIS data subject to the limitations of the Consortium's GIS provider(s). E. The Consortium's basemap layers are managed separately through each entity's organization. The Consortium desires to centralize enterprise GIS management. Hexagon Response: Hexagon understands several agencies are using Esri Enterprise GIS. Hexagon proposes to unify the Consortium's GIS around the existing Esri system. Providing each Consortium entity's Esri instance resides in a VPN, Hexagon will provide a gateway connection for the data to be consumed and displayed within the OnCall system. Hexagon assumes all entities within the Consortium will be responsible for purchasing any necessary licenses and hardware to configure their mapping connections to the OnCall system. 1. How would the proposed system use geodata, maps, and geospatia/ functionality available through the Consortium's Enterprise GIS? Hexagon has proposed to provide a gateway for the Consortium's existing Esri Enterprise GIS to access the OnCall system via VPN connection. This would make it possible for unique GIS data to be displayed from each agency while maintaining a single, shared solution. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON 2. Conversely, how would the proposed system pass location information to the Consortium's Enterprise GIS? Hexagon Response: Event data, including spatial content, is stored in database -standard formats and could be easily exported for loading and analysis in GIS systems. 3. Is a local copy of the GIS data and maps required for the client mapping software? /f so, please describe the format in which such assets are to be locally stored, whether or not the user could make changes, and the update and synchronization processes. No. Core dispatch functions of map display, geocoding, and routing consume web services from a high - availability, load -balanced server configuration. Ancillary data (deployment polygons, special situations, and other OnCaii internal table content) is stored in OnCall's database tables in database standard formats. 4. Does the proposed system utilize OGC (Open Geospatial Consortium) Standard Web Services (e.g., WMS - Web Map Services, WFS - Web Feature Services, etc.), and/or RESTful APIs, or does it depend on a special file format such as a "geofile" or the ESRI shapefile? Hexagon Response: Yes. OnCaii can consume services from OGC (WMS/WMTS) or AreGIS REST endpoints, as well as Azure/Bing maps and open source products, such as Valhala. 5. /f the System requires a specific file format, are RMS, CAD, and Mobile able to share the same file, or will they need separate files? OnCall Dispatch, Mobile and OnCaii Records all use the same geocoding systems. The Address Server in OnCall Records is a web service that is separate from OnCall Dispatch, but it uses the same geocoding systems and underlying data as OnCall Dispatch. All systems consume ESRI-standard file formats, with RMSrequiring Shapefile content to facilitate its geocoding services Response to RFP 21-02 for CAD/RMS/Mobile Section 2.16: Geographic Information Systems, pg. 12 A HEXAGON 6. if the solution requires a separate RMS file for GIS data, describe how the RMS application ensures RMS address verification consistent with addresses in the existing CAD file. HexagonResponse: The OnCall Dispatch and OnCall Records utilize Leaflet display and can use same base map. 7. Describe the software and administration workflows required to create, update, and maintain the necessary GIS data, e.g., a Common P/aces dataset. Service -based solutions are managed in a highly -available, load -balanced server setup, architected to minimizedowntime. Service maintenance is performed using standard ArcGIS tools (ArcMap, ArcGIS Pro, ArcCatalog). Ancillary data (deployment polygons, special situations,(aand other OnCall internal table content) is managed in GIS and converted to OnCall formats via SQL scripting. 8. Are there a maximum number of layers supported within the GIS data? /f so, how many? Hexagon Response: This depends on the GIS data provider. There is not a technical limitation with OnCall for how many layers may be supported; however, Esri may have a practical limit. 9. Is there a maximum data size supported for individual layers for the entire layer? If so, what size? Hexagon Response: No. Larger geographies require larger tile sets, which take up more storage, and increase tile generation times. Those factors are the only practical limit to system coverage. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.16: Geographic Information Systems, pg. 13 A HEXAGON Section 2.1 7 - Analytics The Consortium believes that responsible data analysis is an integral part of investigations, reducing crime, and responding to increasing security threats. It is imperative for the Consortium to collaborate and share information taking a proactive approach to crime and threats. A. Describe the System's ability to analyze and show crime patterns. Hexagon has proposed OnCall Analytics for the Consortium. HXGN OnCaii Analytics takes raw, fragmented, incomplete, or incorrect data and converts it into usable reports and dashboards, so agencies can better assess performance, allocate resources, and improve operations. By creating a single source of truth to explore, analyze, and share, the software suite quickly turns knowledge into action and helps agencies respond more effectively to incidents and major events. OnCall Analytics is more than a standard reporting solution — its a suite of public safety data visualization and analytics products. With it, users have the information and tools they need for evidence -based reporting, analysis, and decision -making. OnCall Analytics incorporates data models that insulate users from underlying database complexities by converting the raw OnCall database fields into industry terminology and logically grouping that data in reporting subject areas. In addition, it also calculates new fields on -the -fly (called measures) that are essential to creating meaningful reports and conveying information to stakeholders. TheDispatch and Records data models serve as the data source of all reports delivered and built with OnCall Analytics. The Consortium's solution would include: s HxGN OnCaii Analytics I Dispatch Data OnCall Analytics I Dispatch Data Models & Reports includes 20 data models and 22 OnCall Analytics I Dispatch Data Models and Reports also includes capabilities for spatial visualization, analysis, and playback capabilities, including Automatic Vehicle Location (AVL). • HxGN OnCaii Analytics I Records Data Models and Reports OnCaii Analytics I Records Data Models & Reports includes 23 ® HxGN O Call Analytics I Author Allows a user to create and publish content to the OnCall Analytics SaaS web portal, as well as access, run, and interface with reports that have been published to the web portal • HxGN OnCaii Analytics I Viewer Allows a user to access, run, and interface with reports that have been published to the SaaS OnCall Analytics web portal • HxGN OnCaii Analytics I Power Visuals Allows users to assess priorities and tactical impacts, profile problem areas, identify patterns and hot spots, and determine areas at higher risk for future problems. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.17: Analytics, pg. 1 A HEXAGON B. Describe how users are able to use the System's map to plot, filter, and view crime data on an ESRI-based map. Hexagon Response: OnCall Analytics can help the Consortium better understand event sequences and incident patterns with spatial analysis, visualization, and playback capabilities. In OnCall Analytics, map controls include plotting location -based information, pin and hotspot mapping, dynamic clustering, geofencing (geospatial filtering), and more. Hexagon supports these capabilities via plug -ins to Esri ArcGIS Maps for Power BI and Microsoft's Bing Maps API. C. /f applicable, describe how the System uses machine -learning (Al) with analytics. Hexagon Response: Hexagon does not currently offer machine learning/AI features for Analytics in the Cloud. D. Describe how the System can allow analysts to use cross jurisdictional data for their analysis. Hexagon has proposed a single solution for the Consortium and its agency y members that make up different jurisdictions within Pinellas County. Agencies who are using the Consortium system will be able to access data from the system, which includes data from the different agencies/jurisdictions that make up the Consortium. Hexagon clarifies the proposed system does not currently support combining third party data with the data in the OnCall Analytics data warehouse. If the Consortium requires the ability to use data from jurisdictions that are not within the Consortium, then that functionality is not available at this time. E. Describe how the System's analytics can help staff identify crime patterns and develop responses for the targeted areas. Hexagon Response: OnCall Analytics includes pre -configured reports that can show crime patterns. For example, a report could be generated to show what specific event type(s) occurred in a given geographic area or point(s) in time. Other reports could be generated to show trends in unit response time or workload. An analyst might see in one report an upward trend in a specific event type (such as a car accident) at a specific location and time of day. In another report, the analyst might see that response times are slower and/or unit workloads are higher than average in that same location or time of day. This could indicate that more unit availability is needed at that time of day/location. It could also mean there should be a regular presence in that location to understand what is causing the upward trend in car accidents. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.17: Analytics, pg. 2 A HEXAGON F. Describe how data can be extracted from the RMS to be used on pub/ic-facing crime maps or in third -party analytic tools? Hexagon Response: Hexagon has experience interfacing to many common third -party crime analysis systems, such as RAIDS Online, Crime Reports, etc. and can provide pricing upon request. Crime maps are available in OnCall Analytics. G. Describe how the System can provide analytical information and updates to mobile devices, field units, and other jurisdictions (e.g., dashboards). Hexagon Response: OnCall Analytics does include interactive dashboards within the application, but these are not viewed from within the CAD and RMS applications. The Consortium may assign OnCall Analytics I Viewer or OnCall Analytics I Author privileges to personnel from different agencies so that the data and dashboards are accessible across Jurisdictions. H. Describe how the System allows users to create individual and custom reports. OnCall Analytics reports can be configured by individuals within the Consortium who are assigned OnCall Analytics I Author privileges. By modifying copied reports, users can quickly create custom reports to advance insights and expand their exploration of data. With ad -hoc reports, users can build custom reports with business -ready data and self-service, drag -and -drop tools. Users can also work on copies of pre -built reports to quickly and easily explore themes and develop personal insights. System Administrators can set up and customize the system to suit their organization's requirements. I. Describe how the System manages: 1. Crime Intelligence Analysis Looking ahead to determine how your agency may respond to future challenges can help you prepare now. For example, a heat map report indicates the frequency of calls or response to a certain part of a community, which may inform future resource allocations. Patterns in the number of calls during certain times of day, week, and year can help leaders optimize future staffing plans. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.17: Analytics, pg. 3 � A HEXAGON 2. Tactical Crime Analysis Hexagon Response: Real-time access to dispatch and records data gives leaders and personnel the flexibility to make spur-of- the-moment adjustments as needed. Geospatial and playback reports can provide a new level of insights and give responders the ability to plot location -based information. Live reporting can also provide information on call volumes, available units, and response times. 3. Strategic Crime Analysis Hexagon Response: Historic reports offer a unique view into how processes have either improved or declined based on prior trends. You can drill down deeper on specific events, from location and priority to how the event was handled. They can even be used as a crimefighting tool. 4. Administrative Crime Analysis Hexagon Response: information to support administrative decisions related to resource allocation and to support budget requests and decisions. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.17: Analytics, pg. 4 A HEXAGON Section 2.18 — Data Conversion / Migration The Largo Police Department currently uses CentralSquare's OneSolution for CAD/RMS. The Largo Police Department wants to convert legacy CAD/RMS data into the proposed System, or is seeking recommendations from a third party for storing and searching legacy data. There are over 1,020,738 CAD records, averaging 70,000 per year, contained in databases approximately 339 GB. A. Provide an explanation of the proposed data conversion process or third party recommendation. Hexagon Response: Largo RMS Conversion Hexagon has proposed historical RMS data conversion and migration from Largo's existing Central Square One Solution to OnCall Records through a partnership with third party White Box. This effort includes conversion of up to 35 source data tables from the source system database (lookup tables, code tables, and other source database tables that contain a minimal number of data fields and primarily exist for database normalization purposes do not count against this limit), used to build the conversion logic and code. A White Box SOW is provided in Appendix A of Hexagon's proposal response. Largo CAD Conversion Migrating "static" non -historical CAD data from the legacy system into OnCaii Dispatch is included within the proposed implementation services. This is a separate effort from converting historical event/incident data. Static CAD data conversion is performed as part of the project implementation and includes such data as Agency ID, Station Definitions, Personnel Definitions, Unit Types, Unit Definitions, Vehicle Hexagon has included scope for CAD historical data conversion, which includes up to 20 tables or 250 elements for Largo only. The process is described as follows. The Hexagon CAD Data Conversion process begins with an analysis of the legacy database to be converted into OnCall Dispatch. This analysis allows Hexagon to produce an initial mapping of legacy data fields to the corresponding fields in the OnCall Dispatch database tables. To produce the analysis, Hexagon will work with the Consortium, gathering information about the legacy database by: • Interviewing subject matter experts (SMEs) • Viewing legacy data in the current system to see where it might fit in the OnCall Dispatch database • Demonstrating various parts of the Hexagon system to SMEs to facilitate discussion of possible areas where data might be converted • Examining documentation and sample data from the legacy system(s) At the conclusion of the analysis, Hexagon will develop a Data Conversion Study document that contains. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.18: Data Conversion/Migration, pg. 1 A HEXAGON • Identification of the functional areas of the legacy system that are considered good candidates for conversion and those areas that are not considered good candidates, along with reasons why the functional areas are classified as "good" or "not good" candidates for conversion • The historical time frame of the data to be converted • An assessment of the adequacy and availability of required data based on its location After discussing the pros and cons associated with the overall conversion project, Hexagon will begin mapping the legacy data to OnCall Dispatch�ldata fields and will continue to make modifications as necessary after completing this task. Hexagon will use a spreadsheet, which will be incorporated into the Data CConversion Study document, to develop a matrix mapping legacy data fields to corresponding fields in OnCall Dispatch database tables. On the mapping matrix, the legacy data file layout will be listed as The • information, along with the field size, format, and a short description. I he matching field name of the target OnCall Dispatch table, its data type, and a comment field for noting missing or unmatched data, translation requirements, or other general comments will be identified for each source data field. During the development of the mapping matrix, Hexagon�land the Consortium will hold discussions to resolve issues and field mapping/�questions. Once Hexagon has completed a draft of the mapping matrix, Hexagon will provide it to the Consortium for review. Hexagon and the Consortium will hold a joint design review meeting via a conference call to review the proposed mapping matrix and jointly agree on necessary changes. Hexagon will then incorporate the changes into the final mapping matrix for inclusion in the Data Conversion Study. Once theData Conversion Study is updated, Hexagon and the Consortium Project Manager, along with Conversion • Data Conversion Lead, will discuss a schedule for moving forward with data conversion. Note that although Hexagon is not responsible for the quality of any legacy data Consortium for resolution. Converted data will initially be loaded to the Archive/Report/Web Server, and as data continues to be entered and moved to the server, will be gradually off-loaded to the External Storage Array. Standard OnCall Dispatch system queries and reports can successfully extract the data from either source. CAD Data Conversion — Scripting The objective of this task is to create scripts based on the data mapping completed in the Data Conversion Analysis and Mapping/� Task, run the scripts, reconcile any discovered script discrepancies, and provide feedback to the Consortium so it can start making corrections to legacy data necessary to facilitate data conversion to the Hexagon system. These scripts may include coding to reformat dates and/or parse name and address data, but will not include any type of legacy data cleanup, such as reformatting free -form text fields or eliminating duplicate names. CAD Data Conversion — Audit Conversion The AuditConversion focuses on uncovering any legacy data or conversion script issues. Prior to this Consortium • the Consortium will need to provide Hexagon with a sample of legacy data large enough to allow Hexagon and the Consortium to perform a quality audit on the imported data. During this task, Hexagon will convert the representative sample of legacy data into the OnCall Dispatch application. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.18: Data Conversion/Migration, pg. 2 A HEXAGON B. Describe how Consortium personnel would access the historical data. Hexagon Response: Consortium personnel would be able to access the historical data within the OnCall Records and OnCall Dispatch systems through the data conversion proposed. C. Provide a separate line item cost, if applicable, for this data conversion. Hexagon has included cost details as requested in Section 6 — Proposal Pricing. The St. Petersburg Police Department wants to import Property and Evidence data only. A. Describe how the Proposer will import Property and Evidence data from the Hexagon (Intergraph /LEADS) RMS into the new system. There are approximately 135,500 items in the current system. Hexagon Response: As St. Petersburg Police Department is a current Hexagon customer, the migration of Property and Evidence data from the department's current I/LEADS system to the new shared OnCall system will be managed and performed by Hexagon. COTS I/LEADS Fields Data Conversion Hexagon resources will convert the COTS Property and Evidence data in the I/LEADS database schema (a single database) by executing the conversion application. The St. Petersburg must provide its I/LEADS database to Hexagon via a secured encrypted hard drive. Hexagon will restore the full I/LEADS database backup provided by the St. Petersburg into the Hexagon virtual cloud which is a secured and CJIS compliant environment. Only those Hexagon employees that are CJIS security cleared by St. Petersburg access their data will be allowed access to this environment. Hexagon will analyze the incoming data and convert it to ILEADS 9.0 version to facilitate the conversion to HxGN OnCall Records schema format. Hexagon resources will then execute the COTS conversion scripts on the I/LEADS RMS database to convert the COTS Property and Evidence data fields to the HxGN OnCall Records Evidence format (Data Run 1). Hexagon resources will validate the data in HxGN OnCall Records based on general knowledge of the applications. It is important, however, for the St. Petersburg to perform their own data verification and validation. St. Petersburg will report data mapping and/or migration errors to Hexagon in a timely manner. Hexagon will resolve priority issues prior to the final data conversion. St. Petersburg Roles and Responsibilities • Provide full database backup to Hexagon • Consult with Hexagon regarding any data migration questions Response to RFP 21-02 for CAD/RMS/Mobile Section 2.18: Data Conversion/Migration, pg. 3 A HEXAGON • Clean data verification and validation of I/LEADS data C • lean up and/or merge any duplicate data prior to the first data conversion run Final Data Conversion Hexagon resources will have executed the conversion application/scripts reflecting the ability to convert the COTS Property and Evidence fields in the I/LEADS database schema (a single database). Through this task, Hexagon will execute the application and scripts for the final time to port all existing data within I/LEADS into the HXGN OnCaii Records Production Environment (Data Run 4). This task would occur immediately prior to cutover. St. Petersburg Roles and Responsibilities • Consult with Hexagon regarding any data migration questions • Perform data verification and validation B. Describe how Consortium personnel would access the historical data. Hexagon Response: Consortium personnel would be able to access the historical data for the data referenced above pertaining to Largo and St. Petersburg within the OnCall Records system. Conversion of other agencies' historical data is not included within the scope. C. Provide a separate line item cost, if applicable, for this data conversion. Hexagon has included cost details as requested in Section 6 — Proposal Pricing. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.18: Data Conversion/Migration, pg. 4 A HEXAGON Section 2.19 — System Testing and Acceptance A. The Consortium requires a review process to verify the Proposer's responses to all of the functional requirements and to confirm that the proposed software meets defined user requirements prior to commencing software implementation. Describe the proposed approach to confirming requirements, determining modifications necessary to meet the Consortium's specifications, and then addressing those modifications. Hexagon interprets this requirement as a Fit & Gap analysis. In Hexagon's experience, this process adds both time and cost to the overall project. In the pre -proposal conference and in the RFP it was stated that the project duration is of critical importance to the Consortium and there is an "acute need" for a new system in agencies like Largo PD who is using a product that is nearly obsolete. It is also Hexagon's belief that the level of review that typically happens during our implementation may be sufficient for the Consortium, though it would not meet the requirement exactly as stated above. For those reasons, Hexagon has not proposed a Fit & Gap analysis at this time. Hexagon clarifies we have provided Fit & Gap analysis for multiple customers and would be able to provide this for the Consortium. As a vendor with proven experience deploying large, multi -agency systems, it is Hexagon's recommendation that this requirement may be revisited should the Consortium desire it be included in the project, understanding it may affect the schedule and scope of the Project. B. Provide a comprehensive Acceptance Test Plan that incorporates these requirements at each Consortium member location. The Consortium will consider as non -responsive any vendor that does not provide an Acceptance Test Plan, or at a minimum, a sample of the plan that illustrates the process and parameters underlying its test approach, including, but not limited to: 1. How each of the functional specifications in the RFP will be tracked, documented, and tested prior to System Application Component Acceptance and Final Acceptance 2. How interfaces will be tested. 3. How System reliability will be tested. 4. How System performance and speed will be tested. 5. How the integration of System and System Components will be verified. 6. What are the remediation procedures for failed tests and found errors? 7. Detail the processes and actions that will be taken if system testing reveals a failure in meeting the minimum technical or functional requirements or requirements as specified within the SOW 8. The delineation of testing tasks between the Consortium and Proposer personnel. Hexagon Response: Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Hexagon's Test Plan Methodology includes multiple levels of formal testing to include: • Test Plan & Test Cases Development Prior to system cutover to live operations, Hexagon will work in conjunction with Customer to conduct the Test Plan and Cases Development and Functional Acceptance Test. Test Plan & Test Cases Development 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 Subsystem. Every software requirement (Benchmark Criteria) should have at least one Test Case; some Benchmark Criteria may have several 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 clear 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. The Test Plan is the set of Test Cases that will serve as the basis of testing the fully configured Subsystem, including interfaces. However, the Customer will not need a fully configured Subsystem to create the Test Plan and Test Cases. Hexagon will provide sample Test Cases to the Customer. Customer will review and can add additional site -specific scenarios and tests, as long as the scenarios and tests comply with Customer's original functional requirements. Upon return of the Test Plan, Hexagon will review all site -specific scenarios and tests added by Customer, and Hexagon and Customer will mutually agree upon the final Test Plan. Hexagon acknowledges the Consortium's specific requirements in items B.1 through B.4 above for a plan to test interfaces, reliability, performance and speed. Hexagon clarifies that since the final test plan will be created by the Customer, these items can be addressed in the test plan at the Consortium's discretion subject to those being commitments within the technical matrix and no additional testing processes or protocols being included. Functional Acceptance Test Following installation of the Software and completion of Configuration Tasks, the Customer, with remote support from Hexagon, will conduct formal Final Acceptance Tests on each subsystem to verify that commands work as intended within Customer -developed test scenarios in the Test Plan The Customer will conduct Functional testing ("Testing Period"). 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 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 Response to RFP 21-02 for CAD/RMS/Mobile Section 2.19: System Testing and Acceptance, pg. 2 ig A HEXAGON existence of a Permissive Error shall not preclude or be a condition of completion of any subsequent Tasks. 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 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 �IError was caused by Customer hardware,�lNetwork Infrastructure, or Third Party Software not provided by Hexagon, or non- conformance with Hexagon provided specifications, then Hexagon will provide such information to the /H Customer for the ustomer to resolve and the Blocker Error will be closed and regarded as complete. As part of resolution efforts, Hexagon may provide a procedural or programmatic workaround, a configuration/�change, or provide an Update. Once the Block/ear 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"). After the Functional Testing, Hexagon will) enforce a code freeze. No configurations or modifications will be allowed to the System by Hexagon or Customer, except those required to resolve any Blocker Error. Upon addressing Blocker Errors, the System is a "Production Ready System." A Production Ready System signifies completion of all configuration and Joint testing tasks. At this point, Hexagon will enforce a System -wide code freeze. Any System/Subsystem modifications will be handled via Change Order. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.19: System Testing and Acceptance, pg. 3 A HEXAGON Section 2.20 - Objectives A. Implemeritatiori Project Plan The Proposer shall provide the Consortium an actual implementation schedule and actual deliverable schedule from the most recent comparable project to include verifiable initial milestones and actual completion dates. Hexagon Response: Due to customer privacy and the fact the Consortium's desired project and scopes�is unique, Hexagon has not included a schedule from a recent project. However, we encourage the Consortium to reach out to our references to discuss their implementation experience with us, as well as the project schedule for their particular projects. The Proposer shall provide the Consortium with a detailed Implementation Project Plan that, at a minimum, includes the following components: 1. Project Background: This section includes a description of the project background. Hexagon Response: During the past 32 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. 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 Consortium. 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. 2. Project Objectives: This section includes overall project objectives. Hexagon Response: Pinellas County Sheriff along with the Consortium agencies is requesting a cloud -first system to bring all agencies together and take down the separate silos of communication, data and resource sharing. Hexagon is providing an integrated system from one vendor to create interoperable, reliable, proven, cloud -based system to eliminate the barriers of data sharing and provide thecommunity with the quickest most efficient responses possible. Hexagon/�is providing a Microsoft Azure CJIS secured government cloud running the Hexagon OnCall Cloud product suite. Hexagon is focused on high availability, disaster recovery and cybersecurity spreading the data over multiple data centers while minimizing downtime and Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 1 A HEXAGON maximizing redundancy. Anyone from anywhere can work on the Hexagon OnCall Cloud, this is the focus for the Pinellas County. 3. Project Deliverables and Milestones: This section includes a fist of deliverables and milestones of the project. With each deliverable or milestone, this section shall describe exactly what will be provided to meet the needs of the Consortium and how it will be achieved. Hexagon Response: Hexagon proposes during contract negotiations we work with the Consortium to develop a mutually agreed -upon Statement of Work (SOW) that details each task in the project with task descriptions, assumptions, deliverables, and Consortium/Hexagon participation/responsibilities. Hexagon has provided a sample project schedule below in addition to our proposed implementation methodology as part of this response. We have significant experience with large, complex, multi -agency implementations and have used our lessons learned from these to shape our best -practice implementation methodology. 4. Project Schedule (MS Project): This section of the Project Plan shall identify the dates associated with deliverables and milestones of the Project Plan. In addition, the Project Plan shall reflect project predecessors, successors, and dependencies. Hexagon Response: A sample project schedule is below which reflects Hexagon's staggered implementation approach and accounts for system software proposed. Hexagon clarifies this schedule is subject to change and will not be considered final or binding until a resulting contract has been negotiated and executed. TASK NAME DURATION Pines la County, FL OnCall Di patch and OnCall Records (Hosted) Project Initial Operation Capability (IOC) Plea se Project Kickoff Meeting OnCall Dispatch Map Overview COTSInterface Questionnaire Completion CAD System Build 1 Hexagon Transition of Cre IOC Phase Completion 496.63 days 35.88 days 12 days 1 day 12.75 days 4.75 days 12 days 12 days 2.63 days 0 days Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 2 HEXAGON Final Operation Capability (FOC) Phase 474.63 Gathering Custom Interface Requirements Gathering 52.97 days Connectivity to Cloud Program 2.25 days On Premise Interface Server VM Creation 1 day Hexagon creates Internal Template VM 2.5 days CAD System Build 2 9 days CAD System Build 3 9 days OnCall Dispatch Map Service Configuration and Consulting Services 2 days OnCall Records Link to OnCall Dispatch 1.5 clays OnCall Records Address Server Mapping Workshop 8.25 days HxGN OnCall Dispatch Fundamentals for Core Team 4.5 days OnCall Dispatch Configuration Consulting Session 15.5 days Customer Rules Engine Configuration Consulting Session 16 days OnCall Dispatch Configuration Session 2 15 days /Consulting OnCall Dispatch Configuration Consulting Session 3 15 days OnCall Dispatch I Mobile Unit Police Configuration Consulting Session 13.5 days OnCaii Dispatch I Mobile Responder— Law Configuration Consulting Session 5.5 days OnCall Records Business Process Analysis (BPA) Workshop 5 days OnCall Records Core Team System Administrator/User Training 5 days OnCall Records System Configuration Workshop 1 16 days OnCall Records system Configuration Workshop 1 Follow-up Session 5 days OnCall Records System Configuration Workshop 2 19 days OnCall Records system Configuration Workshop 2 Follow-up Session 5 days OnCall Records System Configuration Workshop 3 16 days OnCall Records system Configuration Workshop 3 Follow-up Session 5 days State NIBRS Deployment 24.75 days COTS Interface Product Installation and Configuration 21 days Informer Setup (Com mSys) 1.5 days Custom Interface Development and Custom �nterface Product Installation and Configuration 256.74 days Standard Interface Product Installation and Configuration 12.5 days COTS Interface Product Installation and Configuration 2 days CAD Data Conversion 35 days Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 3 00 HEXAGON Develop Test Plan and Test - On/Call Dispatch 15.13 days /Cases TT Develop Test Plan and Test - OnCall Records 15.13 days Cases Internal System Review - OnCall Dispatch 5 days Internal System Review - OnCall 25 days Records Customer Functional Testing - On/Call Dispatch 15 days Testing Customer Functional I esting - OnCall Records 21 days Hexagon -Led Training 60.75 days Customer Led End User Training (30 calendar days) 20 days oud loud Environments Cl 5 days Additional Agencies Cloning 27.5 days Cloud Cutover Plan 8.38 days Cloud Program Readiness Review for PSAP #1 7 days Cloud Cutover to Production Use for PSAP #1 17 days Cloud Program Readiness Review for PSAP #2 7 days Cloud Cutover to Production Use PSAP #2 17 days Cloud Program Readiness Review for PSAP #3 7 days Cloud Cutover to Production Use PSAP #3 17 days Cloud Program Readiness Review for PSAP #4 7 days Cloud Cutover to Production Use PSAP #4 17 days Cloud Program Readiness Review for PSAP #5 7 days Cloud Cutover to Production Use PSAP #5 17 days 5. Project Assumptions and Assumed Responsibilities: This section shall include a list of all the presumptions and assumed responsibilities regarding the vendor, project, and the Consortium. Hexagon Response: Hexagon proposes during contract negotiations we work with the Consortium to develop a mutually agreed -upon SOW that details each task in the project with task descriptions, assumptions, deliverables, and Consortium/Hexagon participation responsibilities. Hexagon has provided a sample project schedule in addition to our proposed implementation methodology as part of this response. In this section Hexagon has also identified anticipated responsibilities of the Hexagon and the Consortium project teams. We have significant experience with large, complex, multi -agency implementations and have used our lessons learned from these to shape our best -practice implementation methodology. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 4 A HEXAGON 6. Project Management Processes: a. Resource Management: This section of the Project Plan describes the Consortium resources, vendor resources, overall project team structure, and organizational chart. Each role shall be identified for the vendor and any subcontractors, as well as the Consortium staff Also, include a description of the responsibilities related to the identified project role as well as the communication process for each party. 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�l these core teams to establish predictable patterns for the timely dissemination of information. However, Teams on the size and complexity of a project, Project Core I eams may be expanded to include Subject Matter Experts (SMEs), including subcontractor SMEs, or team roles may be contracted so that a single person assumes multiple role responsibilities. The following organizational charts provide sample illustrations of the Hexagon and the Consortium 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 and subcontractor SMEs. HEXAGON PROJECT TEAM ROLES Project Manager CAD/RMS Technical Leads CAD/RMS Implementation Leads / r CAD/RMS Training Leads Project Subcontractors 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 for a portion of the project. The strategy associated with staffing each project is defined by RFP, scheduling, and configuration requirements, rather than by a 'nne 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. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 5 A HEXAGON The Hexagon Technical Leads provide the technical oversight, ensuring Hexagon best practices are used throughout the project as a whole. The implementation Leads provide the technical expertise to implement the project from start to finish, including the provided workshop -based training. The role of the Training Leads is to provide agency trainer and/or end user training. Project Subcontractors provide Subject Matter Experts (SMEs) for installing and training subcontracted elements of the proposed configuration. During implementation, Hexagon's Project Manager is responsible for maintaining project communication with the Consortium's Project Manager in the performance of the project. Mapping Lead CUSTOMER PROJECT CORE TEAM ROLES Project Manager CAD/RMS System Admsnistrator(s) CAD/RMS Agency Trainers CAD/RMS Subject Matter 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 Administrotor(s), and Mapping/GIS roles may each require an assigned resource for the duration of the project. The Consortium Project Manager provides a single point of contact for working with Hexagon and maintains sufficient authority within the project to make day-to-day decisions concerning the Consortium personnel and material resources. In multi -agency implementations, the consortium of agencies should designate one Project Manager that represents all participating agencies. The Consortium Mapping Lead assumes responsibility for maintaining the master GIS database and graphics. The Consortium System Administrator(s) collaborates with Hexagon's Implementation Lead to configure the servers and interfaces and to define systemic operations such as backups, recovery, and archiving in addition to configuring the servers and interfaces. Following project closure, the designated System Administrator(s) becomes the point of contact for user/�questions/problems,/�for troubleshooting problems, and for acting as the liaison between the Hexagon Customer Support Center and their user community. The Agency Trainers become the system experts that provide ongoing training for incoming personnel. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 6 ii A HEXAGON The Consortium Subject Matter Experts provide agency information concerning specifications, workflow, and data definitions required to configure the system. During the implementation process, Hexagon, its subcontractors, and the Consortium work collaboratively and iteratively to design and build the configuration that best meets the Consortium's needs within the bounds defined in the Statement of Work (SOW) as agreed upon during contract negotiations. b. Scope Management: This section of the Project P/an should describe the approach the vendor will use in order to manage project scope and the process used to request changes to the project scope. It is the desire to use the proposed CAD/RMS solution with the necessary configuration and customization to meet the needs of the Consortium and user agencies. Any changes must be reviewed and approved by the Consortium. Scope management is addressed via formal Change Request Orders. Requested tasks that fall outside of the negotiated contract as detailed in the SOW 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 subject to mutual execution of a change order by the Consortium and Hexagon. The SOW and Project Schedule are then adjusted accordingly. c. Schedule Management: This section of the Project Plan shall describe the approach the vendor will use in order to manage the project schedule and the process used to submit requested changes to the schedule. The vendor must ensure that the project schedule is kept current and report any potential revisions to the timeframe for projected milestones to the Consortium. Hexagon Response: 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. d. Risk Management: This section of the Project Plan shall describe the approach the vendor will use to document existing project risks, report them to the team, and provide recommendations for mitigating the risk. Hexagon Response: 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 Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 7 HEXAGON 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. 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 doing 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 occurs at the beginning of the project and continues on an ongoing basis. It is the responsibility of all team members and stakeholders to identify potential risk. At the beginning of the project, the Hexagon Project Manager will work to build a list of potential risk items and then coordinate with the Customer Project Manager so that they can be discussed during the initial Kickoff Meeting. The risk items for the project will be documented in a Project Risk Register. The Project Risk Register is an Excel spreadsheet that contains information about each risk. Any identified risks are added to the risk register for further analysis. It is the Hexagon Project Manager's responsibility to assign a risk owner to be responsible for completing the initial analysis and mitigation strategy. During the project life cycle, the Hexagon Project Manager will publish the list of risk items that are being monitored and the status of each. This clear communication of risks will allow the entire project team (both Hexagon and Customer) the ability to track and minimize each risk item. 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. 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 Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 8 ii /HEXAGON 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 Customer. During each monthly status review, the Project Manager will review each risk with the Customer 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. 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. e. Quality Management: This section of the Project P/an shall describe the vendor's approach to assure that all written deliverables have been properly vetted for quality, accuracy, and functionality before being submitted to the Consortium. Hexagon Response: 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 Exec Periodic Project Reviews Bi-Weekly Risk Management Meetings 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 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: Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 9 ii /HEXAGON • Project documentation is reviewed (i.e. action register, risk register, contract documentation, and so forth) • Interviews are conducted with each Hexagon team lead • I he Hexagon project manager is interviewed • • 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 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. Hexagon is committed to an excellent and strict quality control program that has been approved by Lloyd's Register Quality Assurance to the following Quality Management System Standards: ISO 9001:2015 (certificate available upon request). I his �(uality Management System ensures our: • • (Operating policies and procedures are standardized Quality processes are repeatable and quality -driven • Process improvements are continuous actions that are monitored to completion • Performance meets and exceeds the clients' objectives Quality Control The quality control program of Hexagon is managed by a team of experts wino are applying and maintaining our standard operation procedures to ensure our customers are receiving the highest quality services and software. Maintaining this level of control ensures the ultimate quality of our customized products and services. 7. Detailed Methodology for Implementing Third party Software: Methodology shall include an estimated timeframe, overview of phases and milestones, presumptions, and assumed responsibilities. Hexagon Response: Hexagon proposes during contract negotiations we work with the Consortium to develop a mutually agreed -upon Statement of Work/(SOW) that details each task in the project with task descriptions, assumptions, deliverables, and Consortium/Hexagon participation/responsibilities. This SOW will include third -party software tasks. Hexagon has provided our proposed implementation methodology as part of this response, which includes third -party software. We have significant experience with large, complex, multi -agency implementations and have used our lessons learned from these to shape our best -practice implementation methodology. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 10 A HEXAGON 8. Changes to the Project in terms of Project Schedule, Assumptions, Vendor Team Roles, Responsibilities, Resources, Scope, Overall Plan, and Methodology shall be first reviewed and approved by the Consortium. Hexagon proposes during contract negotiations we work with the Consortium to develop a mutually agreed -upon SOW that details each task in the project with task descriptions, assumptions, deliverables, and Consortium/Hexagon participation/responsibilities. After contract execution, any changes to the Project will be agreed upon by the Consortium and Hexagon through the Change Request process. B. Implementation and Testing Methodology Business process workflows, data conversion, and training have the potential to pose the highest level of risk to the Consortium's implementation project. As part of the R.F.P. response, the vendor shall provide a description of its proposed implementation methodology covering these particular aspects of the project. Describe methodologies for multiagency deployment. Hexagon Response: During the past 31 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 implementation 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. Hexagon proposes this same methodology to configure, test, validate, and deploy a proven CAD and RMS solution for the Customer. Hexagon segments implementation activities into the following phases: Initial Operating Capability and Final Operating Capability. Initial Operating Capability (IOC) Phase Planning and Initiation During the process leading up to selection, the Customer and Hexagon may have shared information during a benchmark, requirements discussions, and questions and answers exchanges. Upon selection of Hexagon to implement the Customer's Project, the Hexagon negotiating team and the assigned Hexagon Project Manager, in tandem with the Customer representatives, negotiate the final contract and develop the SOW, the Project Schedule, and associated appendices. Once the SOW has been executed the following activities occur: • 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 • Drafting and updating the project schedule for Customer approval after Project Kickoff Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 11 HEXAGON Staging During this phase, the/�Hexagon team conducts Cloud �I Typical activities (data collection, validation, C and creation of the loud Environment). Additionally, Hexagon installs and configures the virtual on - premise servers, as required. I ypical staging tasks include. • Cloud onboarding activities to include deploying the Cloud Application with all HxGN contracted hosted applications • Coordinating• with the Customer to confirm their network connectivity to the Cloud Program • VMserver installation and configuration for supporting any on -premise products• /� Once Hexagon has provided the Consortium with access to the Implementation loud Environment the ImplementationCloud Environment subscription term begins and runs through Cutover to production use. • The Implementation Cloud Environment/�for the proposed solution is provided for a term of up to 24 months. If for any reason the Consortium has not cutover at its first PSAP site by the second anniversary of the commencement of the Cloud Term, erm, then the Consortiumis required to pay for additional pre-cutover Cloud Program subscription for the Implementation Cloud Environment beyond the initial 24- month period. • Annual Hexagon Cloud Program Subscription Fees Final Operating Capability (FOC) Phases Configuration MO' During Configuration, Hexagon will provide a series of configuration consulting workshylops. This includes a system/training review for the setups that will be covered. The workshops focus on Hexagon providing Cl oud services to ensure the Customer has the tools they need to configure the Program. Typical configuration tasks include: • • • OnCall Analytics I Dispatch Data Models • OnCall Analytics I Records Data Models • NIBRS installation and training • System administration workshops/training • Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 12 / HEXAGON Deployment Deploying the Cloud Program is divided into two (2) parts: training/testing and cutover. It includes the delivery of the final contracted configuration followed by the Acceptance Test Plan and training agency representatives selected by the Customer 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 cutover to live operations. The Hexagon Team remains engaged throughout these processes. Typical deployment tasks include: • System code freeze • Hexagon and Customer -led training • Replicating Cloud Environments • Cloud Plan creation C /loud Program Readiness Review • Cloud Cutover to production • Post-cutover support Hexagon has proposed to implement a highly available hosted solution with the following environments: production, training, test/development, and staging in the Microsoft Azure cloud. The cloud -hosted solution will support disaster recovery. Business Process Workflows Hexagon has proposed organizational change management services be provided by third party partner TDC in coordination with Hexagon's implementation team. A full TDC SOW is available in Appendix A. TDChas identified three phases to its change management approach. • Discovery / Planning Methodology related to identifying changes to business processes and communicating those effectively is included in TDC's scope of work. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 13 iij HEXAGON Data Conversion Hexagon has proposed data conversion services be provided by a combination of third party and Hexagon resources. Largo PoliceDepartmentrequires historical CAD and RMS data conversion. Hexagon has proposed third party White Box provide the records data conversion. A Full White Box SOW is available in Appendix A that discusses implementation methodology. Hexagon has proposed its own services team provide CAD data conversion. HistoricaI CAD Data Conversion Hexagon has included scope for CAD historical data conversion for Largo, which includes up to 20 tables or 250 elements. The process is described as follows. The Hexagon CADData Conversion process begins with an analysis of the legacy database to be converted into OnCall Dispatch. This analysis allows Hexagon to produce an initial mapping of legacy data fields to the corresponding fields in the OnCall Dispatch database tables. To produce the analysis, Hexagon will work with the Consortium, gathering information about the legacy database by: • Interviewing subject matter experts (SMEs) • Viewing legacy data in the current system to see where it might fit in the OnCall Dispatch database • Demonstrating various parts of the Hexagon system to SMEs to facilitate discussion of possible areas where data might be converted • Examining documentation and sample data from the legacy system(s) At the conclusion of the analysis, Hexagon will develop a Data Conversion Study document that contains. • Identification of the functional areas of the legacy system that are considered good candidates for conversion and those areas that are not considered good candidates, along with reasons why the functional areas are classified as "good" or "not good" candidates for conversion The historical time frame of the data to be converted • An assessment of the adequacy and availability of required data based on its location After discussing the pros and cons associated with the overall conversion project, Hexagon will begin mapping the legacy data to OnCall Dispatch data fields, and will continue to make modifications as necessary after completing this task. Hexagon will use a spreadsheet, which will be incorporated into the Data CConversion Study document, to develop a matrix mapping legacy data fields to corresponding fields in OnCall Dispatch database tables. On the mapping matrix, the legacy data file layout will be listed as source information, along with the field size, format, and a short description. The matching field name of the target OnCall Dispatch table, its data type, and a comment field for noting missing or unmatched data, translation requirements, or other general comments will be identified for each source data field. During the development of the mapping matrix, Hexagon and the Consortium will hold discussions to resolve issues and field mapping/�questions. Once Hexagon has completed a draft of the mapping matrix, Hexagon will provide it to the Consortium for review. Hexagon and the Consortium will hold a joint design Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 14 A HEXAGON review meeting via a conference call to review the proposed mapping matrix and jointly agree on necessary changes. Hexagon will then incorporate the changes into the final mapping matrix for inclusion in the Data Conversion Study. Once theData Conversion Study is updated, Hexagon and the Consortium Project Manager, along with Conversion Data Conversion Lead, will discuss a schedule for moving forward with data conversion. Note that although Hexagon is not responsible for the quality of any legacy data supplied by the Consortium, Hexagon will report any discovered data errors or omissions to the Consortium for resolution. Converted data will initially be loaded to the Archive/Report/Web Server, and as data continues to be entered and moved to the server, will be gradually off-loaded to the External Storage Array. Standard OnCall Dispatch system queries and reports can successfully extract the data from either source. CAD Data Conversion — Scripting The objective of this task is to create scripts based on the data mapping completed in the Data Conversion Analysis and Mapping/� Task, run the scripts, reconcile any discovered script discrepancies, and provide feedback to the Consortium so it can start making corrections to legacy data necessary to facilitate data conversion to the Hexagon system. These scripts may include coding to reformat dates and/or parse name and address data, but will not include any type of legacy data cleanup, such as reformatting free -form text fields or eliminating duplicate names. CAD Data Conversion — Audit Conversion The AuditConversion focuses on uncovering any legacy data or conversion script issues. Prior to this Consortium the Consortium will need to provide Hexagon with a sample of legacy data large enough to allow Hexagon and the Consortium to perform a quality audit on the imported data. During this task, Hexagon will convert the representative sample of legacy data into the OnCall Dispatch application. Training Hexagon has outlined its proposed training plan in Section 2.21 — Scope of Services, Item L "Training Plan". As it relates to implementation methodology, Hexagon will provide Train the Trainer classes to Consortium trainers during the project implementation before the first PSAP cutover begins. Hexagon will complete Train the Trainer classes so that the Consortium trainers will be prepared to lead user training for each PSAP at least one week prior to that PSAP's scheduled cutover (go -live). To help facilitate the Consortium -led end -user training, Hexagon has proposed licenses for our eLearning platform, Dynamo. Multi -Agency Deployment Hexagon is no stranger to multi -agency consortiums. We have successfully implemented one of the largest complex multi -agency consortiums in the world with DuPage County, IL, where we successfully consolidated 32 agencies and provided a remarkable cutover that included both CAD and RMS on the same day. The highly experienced staff that you will have access to during this go -live plan will be very similar to DuPage. Hexagon has proposed a staggered implementation approach as requested in the RFP documents. Hexagon has prepared a sample project schedule that accounts for five separate cutover phases (1 cutover per each PSAP)). Leading up to the first cutover, Hexagon's implementation team will work collaboratively with all Consortium agencies to plan and carry out early tasks. As each PSAP prepares to Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 15 A HEXAGON begin cutover, Hexagon will have implementers on -site with each to address any tasks unique to that PSAP's cutover. C. Project Team Organizational Stri.icturc As part of the R.F.P. response, the vendor must specify all personnel required for each of the implementation stages depicted in a Project Team Structure Diagram. The diagram shall include (at a minimum) the fo/lowing Key Personnel: Engagement Manager, Project Manager, Implementation functional area leads, and technical staff. Resumes are required for current and future Key Personnel project team members. Any change of Key Personnel supplied by the successful vendor after contract approval must be reviewed and approved by the Consortium. The Proposer will make reasonable accommodations to ensure the Project Manager will be assigned for the duration of the project. Hexagon has nominated a "tentative" Project Team that represents the skills and experience of personnel likely to be assigned to the Customer'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 Hexagon be selected for the Customer's Project. However, Hexagon commits to providing an experienced, professional Project Team that will ensure the Customer's Project success. At the time of award, Hexagon will select the appropriate Project Team based on availability, experience, nature of the requirements, and input from the Customer. Once in place, Hexagon agrees that key personnel will remain assigned to the Customer's Project unless unavailable due to death, illness, disability, or termination of the employment relationship. Hexagon thereby proposes the following individuals for the Customer's Project. Project Manager — Tatiana Alvarez CAD Implementation Lead — TK !vie CAD Technical Lead — Dee Irwin CAD Training Lead — Lisa Pearce Mobile/Interfaces Technical Lead — Angela Fine Mobile/Interfaces Implementation Lead — Ryan Blackwell RMS Implementation Lead — Janine Musnit RMS Technical Lead — Cindy Sepulveda RMS Training Lead — Tammy Barger Resumes for the above project team are included below. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 16 A HEXAGON Tatiana Alvarez Program Manager QUALIFICATIONS JOB HISTORY implementation experience. She has been working on the delivery of hardware and software applications for Public Safety System Projects. Mrs. Alvarez is currently managing a variety of CAD, MPS, and RMS implementations. Aspiring to apply her learned knowledge and continued growth in the discipline of Project Management. Comfortable in fast paced and deadline -oriented environments that require strong organizational and communication skills. Reliable, ethical and committed to learning and growing in order to advance professionally as well as advance the organization. • Hexagon Safety & Infrastructure, Program Manager (05/2019— Present) • Protect Manager (11/2013— 05/2019) • CentralSq ua re Technologies, Project Coordinator (11/2011— 10/2013) PROFESSIONAL CERTIFICATIONS Project Management Professional (PMP), Project Management Institute, March 16, 2018 EDUCATION 2006 PROFESSIONAL EXPERIENCE Hexagon Safety and Infrastructure, Program Manager (May 2019— Present) City of Aurora, IL (2019 - 2020) The City of Aurora went live with OnCaii Records on January 14, 2020. Mrs. Alvarez' responsibilities included project management and coordination of the delivery of the OnCall Records software, installation, training, testing and implementation support for this new logo. Mrs. Alvarez is currently leading the reliability period as well as coordinating additional interfaces and support services. County of Maui, HI (2019 - 2020) The County of Maui upgraded CAD/MPS to 9.4 and migrated from I/LEADS to OnCaii Records. Mrs. Alvarez led both projects and her responsibilities included the coordination of the delivery of the software, installation, training, testing and implementation support for these upgrades. Their Go Live date was December 8, 2020. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 17 A HEXAGON Knoxville County, TN (2019 — 2020) Knoxville County upgraded CAD 9.2 and MPS to CAD 9.4. Mrs. Alvarez led this effort and her responsibilities included the coordination of the delivery of the software, installation, training, testing and implementation support for this project. Their Go Live date was September 15, 2020. CentralSquare Technologies, Sr. Project Manager (11/2013 — 05/2019) • Execute and maintain project management processes and disciplines in the areas of project planning, execution and quality management, communications management, human resource management, cost management, risk / issue management and change management. • Carry and execute approximately 4 to 6 medium to large sized projects ($250K - $1.8M in services); currently handling a $5,300,000 portfolio of remaining revenue. • Coordinate required resources and services, providing direction on implementations of911 Computer Aided Dispatch, Records Management, and Mobile software products, managing teams of 5-10 resources. • Responsible for weekly revenue forecasting. • Escalate issues in a timely manner, follow documented PMO methodology to ensure quality delivery, facilitate resolution of identified implementation issues. • Prepare and present presentations for project kickoff and during project execution. • Effectively organize and lead project teams by consistently demonstrating ability to establish and provide direction and communicate common goals throughout the project life cycle. • Mentor Project Coordinators and new Project Managers in our PMO methodology and encourage best practices in project planning and delivery. • Communicate with Stakeholders in weekly or biweekly meetings to provide project updates. • project budget, execute and maintain project accounting methodologies. • contract closure processes and customer transition to Support services. • coordination of all implementation tasks that involve third -party vendors. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 18 A HEXAGON Tonya (TK) Ivie Senior Systems Consultant QUALIFICATIONS JOB HISTORY With a background in public safety communications, Ms. Ivie is able to offer Hexagon customers her technical CAD and prior experience as a CAD system administrator, calltaker, dispatcher, and dispatch supervisor. Ivie brings a combination of her industry knowledge and technical understanding that can assist customers through the complexities of establishing or upgrading a public safety system. • Hexagon Safety Vc �nfra sire CLu re. �ystems Consultant; 2006 - Present • Positron Public Safety Systems: CAD Configuration Specialist; 2005 - 2006 • City of Arlington, Texas: Dispatcher Supervisor and Accreditation Manager; 1994 - 2005 • City of Arlington, Texas: Dispatcher, 1992 - 1994 • City of Arlington, Texas: 9-1-1 Calltaker; 1991 -1992 TECHNICAL EXPERTISE • Windows Server 2012, Windows Server 2008/R2, Windows 8.1, Windows 7, Windows Vista, Windows XP, Windows 2003 Server; Hexagon CAD; Tiburon CAD; Positron PowerCAD and Power911; Visual Studio (multiple versions), SQL Server 2005, 2008, 2012, HTML, C/C++, Java, VB,COBOL, and other languages. • Hardware Expertise PCs, workstations, and servers EDUCATION • Working towards Master degree in Data Analytics at Southern New Hampshire University • Bachelor of Arts in Computer Science; Lakeland College; Sheboygan, Wisconsin; May 2005 • Bachelor of Arts in English (specializing in Technical Writing); Texas Tech University; Lu bbo Texas; May 1991 PROFESSIONAL EXPERIENCE Mari County, California Hexagon CAD system for Marin County, CA. Bo sion, Massachusetts Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 19 1ff A HEXAGON Hexagon CAD system for the City of Boston, MA for Police, Fire, and EMS. Waukesha County, Wi soon si n iron s olidated Di s patch Center Ms. Ivie was the primary implementer of the Hexagon CAD system for Waukesha. This implementation included 37 fire agencies and 46 law agencies. Numerous 9.x Upgrades Ms. Ivie has done numerous 9.x upgrades for various customers since coming to work for These I�'`hese customers include both Oracle and SQL Server customers. North Dakota State Radio, North Dakota Ms. Ivie was the primary implementer of the Hexagon CAD system for the state radio dispatch center. City of Amarillo, Tex. exas Ms. Ivie was the primary implementer of the Hexagon CAD system for the City of Amarillo consolidated dispatch center. This implementation included the police, fire, and EMS agencies and also involved integration of ProQA Medical, Law, and Fire to the CAD system. Cleveland Police, Fire, and EMS Services, Ohio Ms. Ivie is involved in the installation and implementation of the Hexagon CAD system for the Cleveland Police Department, while concurrently upgrading the Cleveland Fire/EMS Hexagon CAD system and combining the two into a joint system. Genesee County Consortium, Michigan Ms. Ivie implemented the Hexagon CAD for the Genesee County Consortium. The 9-1-1 Communications Center dispatches for 31 Police departments, 27 Fire departments, and 9 Emergency Medical Ambulance services. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 20 e A HEXAGON Deirdre A. Irwin Senior Systems Consultant QUALIFICATIONS JOB HISTORY With a diverse professional background, Ms. Irwin brings technical and consultative skills to Hexagon. Her primary focus for Hexagon has been the implementation of the Hexagon CAD solution. Present responsibilities include CAD implementation on both Oracle Data Guard and SQL Server HAplatforms, as well as migration of customers from one database vendor to another. Ms. Irwin has provided support and issue resolution skills for both new and existing sites. She also has experience implementing the pseudo -CAD solution for the Records Management only customers. Ms. Irwin has been the lead on data conversion efforts for new customers. In addition to implementation skills, she has led numerous workshops for business remodeling and Business Intelligence reporting. • Hexagon Safely & Infra situ ciu re. Senlor Systems Consultant, SG&I; 2003 - Present • Convergent Grou p/Sc hl u m b erg erSema. Project Engineer; 1999 - 2002 Management Consultant Practice; 1998 - 1999 • Intergraph Corporation. Senior Technical Consultant, 1981 - 1998 TECHNICAL EXPERTISE • Sofiwa re Ex peril se Windows 2012, 2106 and 2019 Server, Windows 2008/R2 Server, Windows 2003 Server UNIX, and MS-DOS operating systems; Hexagon CAD; Oracle Data Guard, SQL Server Database Mirroring and AlwaysOn, WPF, Visual Studio.NET, and C++ applications, BI and Power BI s Hardware EX peril se PCs, workstations, and servers VM PROFESSIONAL EXPERIENCE Boone County, Kentucky (2013 & 2020) Ms. Irwin migrated the site from Oracle to SQL Server and upgraded to the latest CAD solution. In preparation for the most recent upgrade, Ms. Irwin provided a Delta Workshop. Ms. Irwin served as the Technical Lead during the recent CAD 9.4 project upgrade. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 21 A HEXAGON City of Garland, Texas (2013, 2019) Ms. Irwin worked with the City of Garland to upgrade them to Oracle Data Guard and the latest CADsolution. 2019 migration from Oracle Data Guard to SQL Server Always On as part of the CAD 9.4 upgrade City of Laguna Beach, California (2016) Ms. Irwin provided Business Intelligence Direct training for System Administrators City of Richmond, Virginia (2016) Ms. Irwin conducted a CAD Reassessment workshop following their CAD upgrade. City of San Jose, California (2016) Ms. Irwin is currently working with San Jose to upgrade them to the latest CAD solution. She has conducted a Delta workshop to inform them of the changes in the software. City of Thornton, Colorado (2008, 2013, 2020) Ms. Irwin implemented the CAD solution for the City of Thornton Police and Fire. This was a SQL Server solution. She assisted with their upgrade to the latest solution and conducted a Delta Workshop during the course of the upgrade. Ms Irwin conducted the OnCaii Analytics workshop for the City's CAD report writers. City of Tucson, Arizona (2011, 2018) Ms. Irwin implemented the CAD solution for the City of Tucson Police and Fire. This is a SQL Server High Availability solution. Ms. Irwin has conducted consulting workshops throughout the course of the implementation. Ms. Irwin conducted the Delta Workshop as the lead in to the 9.4 CAD upgrade. She served as Technical Lead for the duration of the project. DuPage County, IL (2017-2019) Ms. Irwin worked with DuPage County to bring the 62 agencies, 3 PSAPs over to the new Hexagon solution. This entailed numerous data build and configuration workshops for Police, Fire and the Sheriff's office. Flagstaff Police Department, Arizona (2007, 2016, 2021) Ms. Irwin upgraded the CAD solution for the Flagstaff Police Department. She recently worked with them to upgrade to the latest service pack for CAD. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 22 /HEXAGON migrating them from Oracle to SQL Server AlwaysOn. Hilton Head, South Carolina (2014, 2016) Ms. Irwin has provided remote consulting for Hilton Head's upgrade to the latest CAD solution. She has assisted in the configuration of the system to support ProQA Paramount. Manatee County, Florida (2006, 2013, 2019) Ms. Irwin assisted in the upgrade of the CAD solution for Manatee County. Ms. Irwin worked with the City of Manatee to upgrade them to the latest CAD solution and Oracle Data Guard. Manchester Fire end Police, New Hampshire (2007, 2016) Ms. Irwin assisted in the Deployment Workshop consulting and also provided upgrade support. She worked with the site to upgrade to the latest service pack release for CAD. Minnesota State Patrol (2018, 2020) Ms. Irwin worked with Minnesota State Patrol to initially bring them up to the 9.2 CAD solution and subsequently to the 9.4 CAD solution. The 9.2 upgrade involved migration of the Oracle Database to Data Guard. During the 9.4 upgrade, the site was migrated from Oracle DataGuard to SQL Server AlwaysOn configuration. Ms. Irwin served as both the primary CAD implementer and technical lead. Montgomery County, Pennsylvania (2013, 2020-2021) Ms. Irwin assisted with CAD Reassessment prior to their upgrade to the latest CAD solution. Ms. Irwin is actively engaged with the site to migrate them to the latest web -based solution. Overland Perk, Kansas (2006, 2016) Ms. Irwin assisted in the upgrade of the CAD solution for Overland Park, a hub and spoke solution. She also assisted in the integration of an additional agency into the overall solution. Ms Irwin is currently working on migrating the site from Oracle to SQL Server High Availability solution and upgrading them to the latest CAD solution. San Francisco Airport, California (2016) Ms. Irwin conducted a CAD Reassessment workshop. Sonoma County, California (2015, 2020) Ms. Irwin assisted in the configuration and upgrade of Sonoma County's system. This upgrade involved Police, Fire, EMS, and the Sheriff's department. She worked with the site to migrate them from Oracle to SQL Server High Availability and to the latest CAD solution. Ms Irwin served as the Technical Lead for the upgrade of the site to CAD 9.4 solution. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 23 A HEXAGON Suffolk County PD, New York (2011, 2020-2021) Ms. Irwin assisted with the configuration and cutover of Suffolk County PD to CAD 9.1. This is a SQL Server High Availability site. Ms. Irwin is actively engaged with multiple agencies which will join Suffolk County PD as spokes. Sedgwick County, Kansas /� Ms. Irwin upgraded the pseudo -CAD solution for the Sedgwick County RMS. Tennessee Highway Patrol, Nashville, Tennessee (2016) Ms. Irwin conducted a CAD Delta workshop to support their upgrade. Vail Police Department, Colorado (2005, 2008, 2020-2021) Ms. Irwin assisted in the initial implementation and subsequent upgrade for the Vail Police Department. She provided on -site consultation for issue resolution and provided Delta training prior to the latest upgrade. Ms. Irwin provided on -site support for their latest upgrade to CAD 9.2. Ms. Irwin conducted an OnCall Analytics workshop for records/crime analyst. Ms. Irwin is currently engaged as the Technical Lead for the CAD 9.4 upgrade. Washington County, Pennsylvania � (2016) Ms. Irwin upgraded the site to SQL Server High Availability and the latest CAD solution. Westmoreland, Pennsylvania (2016) Ms. Irwin provided Business Intelligence Direct training for System Administrators and End Users. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 24 fvoll HEXAGON Lisa Pearce Public Safety Technical Trainer QUALIFICATIONS JOB HISTORY Lisa Pearce is the assigned technical trainer with the I/CAD Delivery team, with a specialty in training and user consulting for I/CAD. Ms. Pearce brings 18 years of experience with Hexagon's ICAD solutions, both as an end user and a trainer. She assists with the development of and delivers the training curriculum for the Hexagon Public Safety suite of software, including CAD, I/N etViewer-I/N etDi s patc h er, Mobile for Public Safety (MPS), and Mobile Responder (MR). Training duties include courseware preparation, podium delivery and remote training, focused on the application, user audience, as well as technical personnel such as System Administrators and technical support. Ms. Pearce, as lead trainer, works closely with the implementors on the team to ensure configurations are working and to properly QA the customer end product. Ms. Pearce also has operational experience as a Firefighter/EMT-Paramedic in the State of Florida. She also held an APCO Trainer certificate while working as a 911 Dispatcher (Training Officer) at a customer site in Palm Beach County Florida. Ms. Pearce was asked to work as part of the Planning/IT department to QA the newly integrated Intergraph(`CAD system (at the time), where she learned GIS (both GeoMedia and ESRI). She also received training with various Sys Admin roles.rMs. Pearce was assigned the duties of assisting the County Engineering department with updates to all addressing functions, as well as performing the Map Rolls. Hexagon Safety & Technical Trainer; 2018 - Present Hexagon Safety & Infrastructure: Pre -Sales team Application Engineer; 2013 - 2018 (Hexagon): Senior Technical Trainer (contract) NYPD; 1997 - 2006 Palm Beach bounty Public Defender —Criminal Defense Investigator; 2011 Palm Beach County Fire Rescue: GIS Tech; 2007 — 2011 Palm Beach County Fire Rescue: 911 Dispatcher/Training Officer; 2004 - 2007 Palm Beach County Fire Rescue: 911 Dispatcher; 2002 - 2004 DOD Edwards AFB: 911 Dispatch Supervisor; 1999 - 2000 TECHNICAL EXPERTISE Development Applications: MS Visual Studio (Base knowledge and familiarity) Languages: SQL, HTML, XML (Base knowledge and familiarity) EDUCATION • WESTERN GOVERNORS UNIVERSITY: Bachelor of Science, Cloud System Administration (Curre nt) • PALM BEACH STATE COLLEGE: State Certifications (Firefighter / EMT- Paramedic) Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 25 A HEXAGON PROFESSIONAL EXPERIENCE Cumberland County, Pennsylvania (August 2020) Cumberland County PA is a new customer to Hexagon. Ms. Pearce the -Trainer for I/Dispatcher, I/NetDis patcher, Mobile for Public Safel Chicago International Airport, Chicago Illinois (March 2020) Upgraded project. Ms. Pearce provided a combined CAD Essentials ITT / CAD Delta training. Boone County, Kentucky (March 2020) Upgrade project. Ms. Pearce provided CAD Delta Workshop training to Sys Admin and Dispatch Supervisor. Office of Unified Communications, Washington D.C. (May 2020) Upgrade project provided CAD Delta Workshop Dispatch Supervisors and Trainers. Ms. Pearce support on -site to meet contractual demands. Lee County, Florida (2019) Lee County, Florida is a new customer to Hexagon. Ms. Pearce was assigned to conduct all the end user training for Train -the -Trainer for I/Dispatcher, I/NetViewer, Mobile for Public Safety and Mobile Responder. Ms. Pearce also shadowed the CAD Implementer and the MPS Implementers for the full project, in order to strengthen her Sys Admin knowledge. This included all config workshops. Monroe County, New York (2019) Monroe County, New York is a new customer to Hexagon. Ms. Pearce was assigned as a second instructor, to conduct the MPS Train -the -Trainer for the Fire Department agencies, to meet scheduling needs. City of Richmond, Virginia (2019) Upgrade project. Ms. Pearce provided CAD Delta Workshop training to Sys Admin and Dispatch Supervisors. Minnesota State Highway Patrol (2019) Upgrade project, Ms. Pearce shadowed the Lead CAD Implementor for additional Delta Training and provided MPS Train -the -Trainer. City of Corpus Christi PD, Texas (2019) new Sys Admin persons. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 26 A HEXAGON DuPage County, I11inois (2019) DuPage County, Illinois is a new customer to Hexagon. Ms. Pearce was assigned assist with the final cutover for this Customer. Ms. Pearce spent 2 weeks onsite during this period to meet customer contract requirements. San Francisco International Airport, San Francisco California (2018) Upgrade project. Ms. Pearce provided MPS End User Training to end users on a rotational schedule to accommodate customers scheduling needs City of San Angelo (PD), Texas (2018) Upgrade project. Ms. Pearce was assigned to conduct all the end user training for Train -the - Trainer for I/Dispatcher and I/NetViewer. City of Santa Clara, California (2018) e -Train er for I/Dispatcher, I/N etViewer, Mobile for Public Safety and Mobile Responder. Lisa was also the only Trainer assigned North Memorial, Minnesota (2018) North Memorial EMS, Minnesota is a new customer to Hexagon. Ms. Pearce was assigned to conduct the end user training for Train -the -Trainer Mobile for Public Safety. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 27 A HEXAGON Angela Fine System Engineer III, U.S. Public Safety QUALIFICATIONS JOB HISTORY Ms. Fine is responsible for the setup, install, configuration, troubleshooting, and implementation of COTS and custom interfaces with Computer Aided Dispatch (CAD) and other 3rd party vendors. Interfaces include but are not limited to: ANI/ALI, IFRMS-Cadlink, I/InterCAD, I/FireStationAlerting, I/ActiveFSP, I/MDT, MPS, I/Tracker, I/Page, I/Alarm, IFCAD, I/Informer and associated Informer links WebRMS.) EDUCATION • Intergraph Corporation — Houston, TX; System Engineer III; 07/2015 to Present • Be11 Count„ Communications — Belton, TX; CAD Administrator; 05/2009 to 7/2015 • City Of Killeen — IT Dept. — Killeen, TX; IT Helpdesk/Computer Tech.; 02/2007 to 05/2009 • Internal Revenue Service — Austin, TX, Tax Examiner, 01/2006 to 01/2007 • U.S. Army — 1st Infantry Division Band — Bamberg, Germany, Training Coord. /Operations Asst. /Supply Sup. /Unit Funds Mgr. /Travel Good. /Resource Mgr., 07/2002 to 07/2005 • U.S. Army — 4th Infantry Division Band — Ft Hood, TX, Library Clerk/Unit Status Report Rep/Finance Mgr. /Ad min Clerk, 05/1999 to 06/2002 • SAINT LEO UNIVERSITY — Saint Leo, FL; Bachelor's Degree - Accounting, 2006 PROFESSIONAL CERTIFICATIONS • The Computer Technology Industry Association - Austin, Texas • Intergraph I/CAD Administrator Certification Program Certification Intergraph CAD Sysadmin Boot Camp — Huntsville, AL Com puter-Aided Dispatch (CAD) Certificate Program MPS Bootcamp - Huntsville , AL (Leads RMS Certificate program Edge Frontier Train the Trainer Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 28 A HEXAGON PROFESSIONAL EXPERIENCE Be11 County Communications Ms. Fine's responsibilities with Bell County Communications were as follows: Project Manager/Implementer of CAD Upgrade from v8.1.3 to latest v9.3, conversion from Oracle 10g to SQL Server 2012 • Manage/Administer SQL Server 2012 High Availability Cluster including 3 Computer Aided Dispatch (CAD) servers, archive server, and training server within a VMWare environment ▪ Administer dual Computer Aided Dispatch (CAD) databases and archive database, with dual training databases within a Citrix environment • Setup, install, troubleshoot, and train on Computer Aided Dispatch (CAD)/Mobile/Ileads RMS systems • Manage personnel access for Computer Aided Dispatch (CAD), TLETS/NCIC, units, lineups, and response plans for 60+ agencies • Administer global controls over Computer Aided Dispatch (CAD)/Mobile systems • Audit actions regarding Computer Aided Dispatch (CAD) system for compliance • Workflow analysis for Computer Aided Dispatch (CAD) system • Implemented integration between VOIP phone system, CAD, and recorder (VPI) • Edge Frontier developer training for custom interface development • Priority Dispatch ProQA/AQUA, installer/administrator • Manage paging system of over 600+ users • VPI (VOIP), EXACOM (Analog phone and Radio) 911 recording retrieval software administrator • Manage Communications server interfacing with 30+ outside agencies • Netmotion installs //& troubleshooting (client and server) • Implemented NextGen 911 VOIP Phone system, integrating it into our existing infrastructure including both main and backup sites s Experience with Oracle 10g, 11 g, SQL 2005,2008,2012, MySQL and SQL Express databases • Used Visual Studio2005 w/ C++ and 2012 w/C++ for software customization • Create, customize & modify reports/applications using XML, HTML, XHTML, VBScript and JavaSeript • Experienced with setup and deployment of Windows Server 2003, 2008, 2008-R2, 2012 • Knowledgeable in use of Office Professional 2003, 2007, 2010, 2013 City Of Killeen — IT Dept. Ms. Fine's responsibilities in her time at the City of Killeen IT Department were as follows: Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 29 A HEXAGON • Program/Manage Cisco VOIP phone system. (700+) • Manage 350+ cell phone lines and data cards • Experienced with setup and deployment of Windows Server 2003 • Managed FireRMS SQL databases, EMS billing software including mobile applications • Administered Domain access through Active Directory and maintained MS Exchange 2003 • Experienced with workstatiOn O/S—XP, Vista 32/64 bit • Knowledgeable in use of Office Professional 2003, 2007 Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 30 / HEXAGON Ryan Blackwell Systems Engineer QUALIFICATIONS JOB HISTORY Mr. Blackwell brings innovative and technical skills that benefit Hexagon and the customers it serves. Mr. Blackwell's implementation experiences include integrating a wide variety of customer requirements into a complete solution for MPS, I/Tracker, I/Informer, I/Page, I/CADLink, and other products. Hi responsibilities include interface implementation, with duties involving both standard and custom implementations. • Hexagon Safety & Infrastructure. Systems Engineer, 2011 — Present • lien, 2011 TECHNICAL EXPERTISE EDUCATION • •Windows XP, 7, and Vista • Applications and Languages: SQL Server, Microsoft Office, C++, C#, ASP, Visual Basic, HTML, XML, XSL, and Microsoft Visual Studio.Net Administration (MIS); University of Alabama; 2011 PROFESSIONAL EXPERIENCE — PUBLIC SAFETY Gallatin County — City of Bozeman 911 Communications, Bozeman, Montana When Gallatin Countyupgraded their CAD system, Mr. Blackwell configured and implemented County for the City and County Police and Fire agencies. Mr. Blackwell also upgraded and provided technical support for I/Informer and other I/CAD interfaces. Mr. Blackwell also provided post - upgrade support for these interfaces. City of Memphis, Tennessee When Memphis upgraded their CAD system, Mr. Blackwell upgraded and provided technical support for I/Informer and other I/CAD interfaces. Mr. Blackwell also provided post -upgrade support for these interfaces. Town of Vail, Colorado When Vail upgraded their CAD system, Mr. Blackwell configured and implemented MPS for Police and Fire agencies. Mr. Blackwell also upgraded and provided technical support for I/Informer and other I/CAD interfaces. Maricopa County Sheriff's Office, Arizona When the MCSO purchased a new CAD solution from the primary I/CAD Interface engineer assigned to the project. He configured and supported interfaces Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 31 /HEXAGON such as MPS, I/Informer, I/Page, ANI/ALI, and I/Push to Talk. Mr. Blackwell also provided post - upgrade support for these interfaces. Tennessee Valley Authority When the TVA purchased a new CAD and mobile solution from Hexagon, Mr. Blackwell was the primary I/CAD Interface engineer assigned to this project. He configured and supported interfaces such as MPS and I/Informer. He also designed and implemented a custom solution to interface existing surveillance hardware with Hexagon's I/Security solution. Mr. Blackwell also provided post - upgrade support for these interfaces. Howard County, Maryland When Howard County upgraded their CAD system, Mr. Blackwell upgraded and implemented I/Mobile for Police and Fire agencies. Mr. Blackwell also upgraded and provided technical support for I/Informer and other CAD interfaces. EI Paso County, Texas When El Paso upgraded their CAD system, Mr. Blackwell implemented MPS for Police and Fire agencies. Mr. Blackwell also upgraded and provided technical support for I/Informer and other CAD interfaces. Knox County, Tennessee When Knox County purchased a new CAD and mobile solution from was the primary I/CAD Interface engineer assigned to the project. He configured and supported interfaces such as MPS, I/Tracker, I/Informer, I/Page, ANI/ALI, and FIRELINK. Mr. Blackwell also provided post -upgrade support for these interfaces. City of Garland, Texas When the City of Garland upgraded their CAD system, Mr. Blackwell implemented MPS for Police and Fire agencies. Mr. Blackwell also upgraded and provided technical support for I/Informer and other CAD interfaces. City of Newport News, Virginia Mr. Blackwell worked with the City of Newport News identifying areas for improvement with software and workflow, and providing custom solutions. City of Mountain View, California Mr. Blackwell worked with the City of Mountain View identifying areas for improvement with software and workflow, and providing custom solutions. Benton County, \IVa s hi ngton led their CAD system, Mr. Blackwell implemented MPS for Police and also upgraded and provided technical support for I/Informer and other CADinterfaces. San Francisco Airport (SFO) When SFO upgraded their CAD system, Mr. Blackwell implemented MPS for Police and Fire agencies. Mr. Blackwell also upgraded and provided technical support for I/Informer and other CAD interfaces. Lauderdale County, Alabama Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 32 /HEXAGON Mr. Blackwell worked with Lauderdale County identifying areas for improvement with software and workflow, and providing custom solutions. City of Plantation, FL p When the City of Plantation upgraded their CAD system, Mr. Blackwell implemented MPS for Bl ackwell and Fire agencies. Mr. also upgraded and provided technical support for I/Informer and other CAD interfaces. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 33 A HEXAGON Janine Musnit System Engineer QUALIFICATIONS JOB HISTORY Ms. Musnit graduated from University of Alabama in Huntsville with an Information Systems degree as well as a double major in Management. She has a diverse technical experience emphasizing in database management, system analysis, and software troubleshooting. She has been working with Police RMS system for almost 3 years • Hexagon. System Engineer Jan 2018 - Present • GE FIS/IT Intern; Jan 2017 — Nov 2017 • San mina Corporation: IT Collaborations Intern, June 2016 — Jan 2017 TECHNICAL EXPERTISE • MS SQL Server • Windows Server • Visual Studios 2017 • Crystal Reports EDUCATION • B.S. in Information System and Management; University of Alabama in Huntsville, 2017 PROFESSIONAL EXPERIENCE Implementer— Hexagon As an implementer, Ms. Musnit performs installation, configuration, and troubleshooting of OnCall Records product suites. In addition, she coordinates efforts with Support and Product Center to identify defects and feature enhancement needed to continuously improve the product D�Page Co.nt„ RSA Supported one of the largest deployment rollouts for the RMS, this 36-agency deployment supports over 2000 sworn and non -sworn users. This deployment included the Hexagon CAD, as well as 39 custom interfaces. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 34 A HEXAGON Cynthia K. Sepulveda Senior Manager - Technical QUALIFICATIONS JOB HISTORY Ms. Sepulveda brings 37 years of law enforcement knowledge and experience combined with 23 years of technical experience to Hexagon. She has implemented, trained, supported, and administered a wide variety of law enforcement systems including RMS, JMS, CAD, mugshot, document imaging, and scheduling software. Ms. Sepulveda has implemented the Hexagon and Intergraph OnCall Records, RMS, JMS, and IFR products, integrating a wide variety of customer requirements into a cohesive automated solution. Present responsibilities include OnCall Records implementation and conversion for single and multi -agency sites, with duties involving both standard implementation as well as some custom development. • • Hexagon: Senior Manager — Technical; 2019 - Present Consultant, Support Services; 2006 - Present a City of San Bernardino: Systems Analyst, IT Department; 1998 - 2006 • San Bernardino Police Department: Dispatch Supervisor; 1984 - 1998 TECHNICAL EXPERTISE • Software Expertise Windows 2019 Server —Windows NT Server (all versions in between), Windowsl0 - Windows 95/98/NT (all versions in between), UNIX, and MS-DOS operating systems; Hexagon OnCall Records (WebRMS) and FBR, Intergraph I/LEADS RMS, JMS, and IFR, other RMS, JMS, and CAD systems; SQL Server 2000 — 2019, SQL Server Cluster, SQL Server High Availability/Always On, Oracle, Oracle Fail Safe, Oracle RAC; Microsoft Cluster Services; IIS; SQLServer Reporting Services; Microsoft Office applications, FileNet, various Mugshot systems; variety of other software applications. • Hardware Expertise PCs, workstations, servers, document imaging scanners, variety of peripheral hardware devices. EDUCATION Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 35 A HEXAGON PROFESSIONAL EXPERIENCE Implementation duties can include, but is not limited to, installing and configuring database software, conversion of database�lfrom Oracle to SQL, creation of database instances, scripts, installation and configuration of Hexagon OnCall Records software and certain interfaces, Intergraph I/LEADS software and certain interfaces, conducting technical and user classes, issue tracking and resolution. Adams County Communications, Commerce City, Colorado (Jul 2008 — Feb 2010) Ms. Sepulveda upgraded and provided support of I/LEADS RMS for Adams County. She performed full facility JMS implementation for Adams County Sheriff Office. Adams County is a multi -agency consortium site. Alameda County Sheriff's Office, California (O0t-De0 2006, Feb - De. 2014) Ms. Sepulveda performed I/LEADS RMS implementation, upgrade, and support duties for the Alameda County Sheriffs Office. This is a large multi -agency site encompassing the entire County, jails, and courts within the County jurisdiction. Amarillo Police Department, Texas (June 2009, Mar 2018 — Mar 2020) Ms. Sepulveda provided OnCall Records implementation, conversion, training, and support duties and I/LEADS RMS implementation support for Amarillo Police Department. Amtrak, Pennsylvania (Mar-Abg 2016, Mar -Apr 2017) I/LEADS RMS upgrade in the conversion from I/LEADS to WebRMS. Arvada Police Department, Colorado (Jul 2007 — Mar 2008, Jan 2014) Ms. Sepulveda upgraded and provided support of I/LEADS RMS for the Arvada Police Department. Athens -Clarke County Police, Athens, Georgia (Jun 2008 — Jun 2009, Jan 2014 — Apr 2014) Ms. Sepulveda performed I/LEADS RMS implementation and support duties for Athens` -Clarke County. This is a multi -agency site that includes the Police, Sheriff, and University of Georgia Athens. Bell County Communications, Belton, Texas (Nov 2008 — Oct 2009, Apr 2014 — June 2015) Ms. Sepulveda upgraded and provided support of I/LEADS RMS for Bell County. Bell County is a multi -agency consortium site. She assisted in the upgrade and migration from I/LEADS to WebRMS. BiPin/Kennewick County, Washington (Aug 2012 — March 2013, Feb — Dec 2015) Ms. Sepulveda performed I/LEADS RMS implementation, upgrade, and support duties for BiPin/Kennewick County. This is a multi -site agency. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 36 A HEXAGON Brea Police Department, California (Apr — Jul 2007, Mar — Apr 2008, Sep — Nov 2009) Ms. Sepulveda performed early I/LEADS RMS implementation duties for the Brea Police Department. Cedar Rapid. P.1 . Sheriff, Iowa (Sept 2011 — Feb 2012, May 2012 — Feb 2013, May —Jun 2014) Ms. Sepulveda provided Oracle to SQL migration support for Cedar Rapids Police Department. She provided custom JMS training for Linn County Police. This is a multi -agency site. Coconino County Sheriff's Office / Flagstaff P.1 0 Flagstaff, Arizona (Sept 2011 — Aug 2012, Oct 2016 — August 2020) Ms. Sepulveda performed conversion and implementation duties of OnCall Records RMS and JMS for the Coconino County Sheriffs Office. This included conversion from Oracle to SQL; data conversion assistance from I/LEADS to OnCaii Records; implementation, configuration, and training of the OnCall Records system. She also upgraded and provided support of I/LEADS RMS on prior upgrades. This is a multi - agency site that includes multiple police agencies including Flagstaff Police, the Consortium Sheriff, and Northern Arizona University. Corpus Christi Police Department, Texas (Sept 2006 — Feb 2007, Jun — Sept 2007) Ms. Sepulveda performed I/LEADS RMS implementation and support duties and Pawnshop data support for the Corpus Christi Police Department. She provided name merging support of the master name file for the agency. DC Metro Police Department, Washington DC (Jan 2013 — Aug 2015) Ms. Sepulveda performed a variety of implementation, training, and support duties for DC Metro Police Department. Des Moines Police Department, Iowa (April 2009 — Feb 2010, July 2012 — June 2014) Ms. Sepulveda has upgraded and provided support of I/LEADS RMS and JMS for the Des Moines Police Department two times. She implemented IFRLE during the second upgrade. This is a multi - agency site that provides RMS, JMS, and IFRLE to the Polk County -Des Moines area and surrounding cities. El Paso Police Department, Texas (May 2009 — Sept 2010, May 2017 — Nov 2020) Ms. Sepulveda performed conversion and implementation duties of OnCall Records RMS and JMS for the Coconino County Sheriff's Office. This included data conversion assistance from I/LEADS to OnCall Records; implementation, configuration, and training of the OnCall Records system. El Paso is a large, multi -agency site. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 37 /HEXAGON Ms. Sepulveda performed I/LEADS RMS implementation upgrade support and Pawnshop data support for the El Paso Police Department. She provided name merging support of the master name file for the agency. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 38 e A HEXAGON Tamera T. Barger Records Management System Consultant QUALIFICATIONS JOB HISTORY Having been involved with the computer automation of Law Enforcement agencies throughout her career, Ms. Barger brings both technical expertise as well as Law Enforcement specific experience to Hexagon. She has experience administering CAD, RMS, and Mobile products, as well as integrating a wide variety of customer requirements into a cohesive automated solution. With an extensive knowledge of the CAD/RMS data structures, she has addressed specific customer issues. Present responsibilities include RMS implementation. Ms. Barger has been involved in the development of Business Intelligence for Public Safety as a resource specialist and implementer. Along with those duties, she has performed several database migrations. • e • • • • • Hexagon Safety & Infrastructure: RMS Senior System Consultant, RMS Implementation Services, 2019 — Present Hexagon Safety & Infrastructure: RMS Services, 2014 — 2019 Hexagon Safety & Infrastructure: RMS Resident Engineer, 2010 - 2014 Intergraph Corporation: RMS System Consultant, RMS Implementation Services, 2008 - 2010 Tiburon, Incorporated: RMS Resource Specialist, Resource & Training Department, 2003 - 2007 City of Melbourne: System Administrator, IS Department, 1999 - 2003 City of Melbourne: Crime Analyst, 1992 - 1999 City of Melbourne: Personal Computer Technician, 1990 — 1992 City of Melbourne: Communications Technician, 1988 - 1990 TECHNICAL EXPERTISE • Software Expertise Windows 2000/2003/2008/2012/2016 Windows XP Windows NT Workstation and Server Windows 95/98 UNIX MS-DOS Operating Systems CAD and RMS applications • Hardware Expertise PCs, Workstations, and Servers Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 39 A HEXAGON Oracle and SQL Server Business Objects — Business Intelligence Microsoft Power BI — Report Builder EDUCATION • Bachelor of Arts Degree in Computer Information Systems; Rollins College, Brevard Campus; • Melbourne, Florida, 1997 1992 PROFESSIONAL EXPERIENCE Maui County Police Department, Hawaii (December 2020) Ms. Barger supported Maui's OnCall Records implementation by providing assistance during the migration and upgrade, and training. Ms. Barger provided customer with training with remote Train the Trainer, including specialized Address Server. Ms. Barger was primary onsite cutover support due to limitations of travel. Amarillo Police Department, Texas (February 2020) Ms. Barger supported Amarillo's OnCall Records implementation by providing assistance during the migration and upgrade, as well as training. Ms. Barger provided customer with specialized training with System Admin, Address Server, and Reports and Deployment, onsite cutover support and post cutover support. EI Paso Police Department, Texas (November 2020) Ms. Barger supported El Paso's OnCall Records implementation by providing assistance during the migration and upgrade. Ms. Barger provided customer with specialized installation and configuration for Multi -Agency Address Server and remote cutover support. Garland Police Department, Texas (November 2020) Ms. Barger supported Garland's OnCall Records implementation by providing assistance during the upgrade. Ms. Barger provided customer with specialized installation and configuration Address Server, Reports and Deployment, and System Administration Training. Coconino County/Flagstaff, Arizona (August 2020) Records implementation by providing assistance during the migration and upgrade. Ms. Barger provided customer with specialized installation and configuration for Multi -Agency Address Server and onsite cutover support. She also provided specialized Reports Training with OnCall Analytics for Records. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 40 1ff A HEXAGON Thornton Police Department, Colorado (August 2020) Ms. Barger supported Thornton Police Department with an add on Specialized Training by providing Reports Training with OnCall Analytics for Records. Eagle County / Vail, Colorado (October 2019) Ms. Barger supported Eagle County / Vail's OnCall Records implementation by providing assistance during the migration and upgrade. Ms. Barger provided customer with specialized installation and configuration for Multi -Agency Address Server and onsite cutover support. She also provided specialized Reports Training with OnCall Analytics for Records and their previous version of Reports and Deployment. City of Cedar Rapids, Iowa (March 2019) Ms. Barger supported the City of Cedar Rapid's CAD cutover Support implementation by updating I/LEADS Link and Address Server to allow communication after CAD Upgrade. She also upgraded Informer during the cutover to allow communication to the State Interface. DuPage County, Illinois (June 2019) Ms. Barger supported the County of DuPage's WebRMS implementation by providing support during their upgrade. She provided specialized training in the areas of Reports and Deployment, Business Intelligence, and Train the Trainer. San Angelo Police Department, Texas (November 2018) Ms. Barger supported San Angelo's I/LEADS implementation by providing assistance during the migration and upgrade, and training. Ms. Barger provided customer with I/MARS assistance, onsite cutover support, and post cutover support. Shelby County, Alabama (August 2018) Ms. Barger supported Shelby County's CAD cutover Support implementation by updating I/LEADS Link and Address Server to allow communication after CAD Upgrade. She also upgraded Informer during the cutover to allow communication to the State Interface. St Petersburg Police Department, Florida (March 2018) Ms. Barger performed updated their CAD/I/LEADS and migrated their database from Oracle to SQL and also upgraded their I/LEADS application. The upgrade was performed by Ms. Sepulveda, but the migration was completed by Ms. Barger. The cutover was supported by both implementers during the onsite cutover. Amtrak Police Department— Multiple Locations (April 2017) Ms. Barger supported Nationwide Amtrak's WebRMS implementation by providing specialized training. Ms. Barger provided customer with BI Training at multiple sites through the North East and Central United States. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 41 A HEXAGON Temple Police Department, Texas (May 2017) Ms. Barger supported Temple's WebRMS implementation by providing support during their upgrade by assisting in the final migration at cutover. She provided consultations during the implementation process, specialized GIS training, and application testing. Ms. Barger also provided customer support and resolution to service requests post cutover. Thornton Police Department, Colorado (October 2016) Ms. Barger supported Thornton's WebRMS implementation by providing support during their upgrade by assisting in the final migration at cutover. She provided consultation during the implementation process. De pariment, Texas (August 2018) Ms. Barger supported Wichita Falls' CAD cutover Support implementation by updating I/LEADS Link and Address Server to allow communication after CAD Upgrade. Bell County Sheriff's Office, Texas (June 2015) Ms. Barger supported Bell County's WebRMS implementation by providing support during their upgrade by assisting in the final migration at cutover. She provided consultation during the implementation process. Manatee County Sheriff's Department, Florida (June 2014) Ms. Barger supported Manatee County's I/LEADS implementation by providing support during their CAD/IFR/I/LEADS upgrade by assisting in the final cutover. She provided support for the I/LEADS upgrade and support onsite during the cutover process. Nassau County Police Department, New York (April 2010 — March 2014) Ms. Barger supported the Nassau County's I/LEADS Records Management and Jail Management Systems as system administrator during implementation and after cutover. She provided daily consultation to the agencies' Team regarding various system topics. Ms. Barger also provided first line customer support and resolution to service requests to include installation of system patches. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 42 tury A HEXAGON 1. Vendor Team Roles and Responsibilities As part of the R.F.P. response, the vendor shall provide a detailed explanation of the roles and responsibilities the vendor anticipates providing to address the Consortium's requirements in this R.F.P. The vendor shall clearly indicate which vendor staff member (either by name or position/team) will be responsible for the overall project and for each key role/responsibility within the project implementation plan. It is the Consortium's expectation that the vendor provides project management services related to the vendor's imp/ementation approach. This will include, but not be limited to, the development and maintenance of the deliverables, training, data conversion, and testing services, and serving as a single point of contact for the Consortium's project manager. As such, the vendor's project manager must be an expert user of the software program and have significant experience managing a project of this size. The project manager must also have the authority necessary to make decisions relating to key project tasks in order to keep the project moving forward. Hexagon Response: The following organizational chart provide sample illustrations of the Hexagon Core Team and identifies typical roles. Sample team members have been provided above in Section C. Project Team Organizational Structure. 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 and subcontractor SMEs CAD/RMS Technical Leads HEXAGON PROJECT TEAM ROLES Project Manager CAD/RMS Implementation Leads r CAD/RMS Training Leads Project Subcontractors 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 for a 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. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 43 /HEXAGON 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 Hexagon Technical Leads provide the technical oversight, ensuring Hexagon best practices are used throughout the project as a whole. The Implementation Leads provide the technical expertise to implement the project from start to finish, including the provided workshop -based training. The role of the Training Leads is to provide agency trainer and/or end user training. Project Subcontractors provide Subject Matter Experts (SMEs) for installing and training subcontracted elements of the proposed configuration. During implementation, Hexagon's Project Manager is responsible for maintaining project communication with the Consortium's Project Manager in the performance of the project. Project Manager tanager Role & Responsibilities Hexagon follows the Project Management Methodologies set forth by the Project Management Institute. Our PMO ensures all projects go through a review for applicable implementation of the PMBOK's 42 processes for project management and when applicable, ITIL's 23 processes for IT service management, all while maintaining compliance with ISO 9001:2015. Our PMO ensures that these standardized processes are in place for total project management from managing risks, to planning schedules, to managing communications, to delivering services, and more. The Project Manager has the overall authority and responsibility for managing and executing this project according to this approved Project Plan and its Subsidiary Management Plans. The project team will consist of personnel from the implementation group, quality control/assurance group, project delivery group, training group, and subcontract partners. The project manager will work with all resources to perform project planning. All project and subcontract management plans will be reviewed and approved by the project sponsor. Any delegation of approval authority to the project manager should be done in writing and be signed by both the project sponsor and project manager. The project team will be a "matrix," meaning that team members from each organization continue to report to their organizational management throughout the duration of the project. The project manager is responsible for communicating with organizational managers on the progress and performance of each project resource. 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. • Managing the efforts of the Hexagon staff and coordinating Hexagon's activities with the Customer's Project Manager • Providing agendas in advance of all scheduled meetings, unless mutually agreed that an agenda is not necessary Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 44 A HEXAGON • Monthly Project Status Meetings and Formal Status Reports — Once a month, a comprehensive Status Meeting is held and a formal Status Report is submitted, documenting project progress during the past month and listing upcoming activities and events. In addition, both teams jointly review the program schedule, identify and assess risks, and discuss any outstanding issues • Project Management Weekly Status Meetings — During a weekly teleconference, both Hexagon and the Consortium will review a rolling three-week plan that addresses. Tasks completed during the previous week, including the identification of any unfinished tasks and corrective actions or recovery plans Tasks scheduled to be completed during the upcoming week to ensure that responsibilities and deliverables are clearly understood Tasks scheduled for the following week to ensure that appropriate preparations are made to line up resources and synchronize dependencies Summary Status Meetings — When Hexagon technical staff is on site conducting Build and Configure Workshops, a Summary Status Meeting with relevant Consortium technical personnel will be held each working day to ensure that the technical personnel involved understand the goals associated with the daily activities, upcoming tasks, and that progress is tracked Responding to issues raised by the Customer's Project Managers • Preparing and submitting biweekly status reports which include: the accomplishments of the previous month, planned activities, and an updated Project Schedule 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 Vendors should keep this approach in mind as they develop their cost and project approach. It is expected that the vendor will recommend and offer additional services such as business analysis or organizational change management if identified as necessary for the successful completion of the project. The vendor shall have past experience implementing large-scale projects and shall have worked within a law enforcement or government and public sector environment. Hexagon has proposed/� organizational change management services as part of the implementation strategy for the Consortium. Hexagon has experience implementing large-scale projects for law enforcement and public safety agencies, including multi -agency consortiums such as Pinellas County. In Section 2.21, Item S "Client References & On -Site Visits" Hexagon has included customer references that are similar in size and scope to the Consortium. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 45 HEXAGON The vendor shall identify the total number of hours that members of their team will be involved in each phase of the project and estimate how many hours on -site for each phase. The response will provide hourly estimates by functional area for seven (7) phases of the project, including; a. Project kickoff (review SOW, project readiness assessment, technical review, process mapping, equipment hardware review, upgrade schedule, etc.) b. Requirements and Design; c. Configuration and Setup; d. Property and Evidence Data Conversion /Migration; e. Implementation; f. Testing; and g. Training and Project Closure. Hexagon Response: Hexagon takes exception to proposing a breakdown by hours. 2. Consortium Team Roles and Responsibilities: As part of the R.F.P. response, the vendor shall provide an anticipated representation of the resource requirements that will be expected of Consortium and user agencies during this project. The Consortium will provide the vendor with workspace, VPN access, and troubleshooting services for connectivity to the existing Consortium networks. The vendor shall identify the staffing requirements and the total number of expected hours that members of the Consortium team will be involved in each phase of the project. The response will provide hourly estimates by functional area for the seven (7) phases of the project as listed in section C (1) above. It is Hexagon's experience that each agency is unique in how it supports implementation, administers the system, and supports the system. As such, Hexagon is not in a position /tto provide an hourly breakdown by phases. Hexagon expects during contract negotiations to identify the Consortium roles required for each Task, so the Consortium may plan accordingly. The project is a highly collaborative project with each party relying on the other. Appreciating the Consortium's experience/�With IT projects and its workflows, personnel dynamics, training, and processes, ultimately, the Consortium will decide the amount of its efforts to reach its intended outcomes. Hexagon recommends during the Project that the Consortium develop a Core Team, that consists of designated agency personnel with the various skill sets, knowledge and backgrounds required to Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 46 /HEXAGON 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 Consortium Core Team and with Hexagon • Departmental Sponsors — responsible for making decisions on recommended business process changes and other related items • S„=Len, Administrator Per=onnei — responsible for all system administration and configuration responsibilities related to the new system, all system interfaces, and the mobile system • Training Per�onnei — responsible for training other agency personnel • Integraiicn and Testing Manager — should have extensive experience in writing system test plans and executing tests for large, integrated systems • Subject Matter Experts (SMEs) (i.e., record clerks, dispatchers, supervisory personnel) — responsible for representing end -users' needs • Report Writing Specialists - Hexagon recommends 3-5 Report Writing Specialists who will be trained in the use of OnCall Analytics and will be responsible for creating and deploying custom reports Response to RFP 21-02 for CAD/RMS/Mobile Section 2.20: Objectives, pg. 47 A HEXAGON Section 2.21 — Scope of Services A. Software Customization Plan While the Consortium intends to utilize the vendorsystem's existing capabilities and embedded best practice business processes, we recognize that some critical work processes may require some software customization or atypical system configuration. As part of this project plan, the vendor will provide a detailed software customization plan that includes anticipated customizations and their impact on the overall project schedule, budget, and final success. This software customization plan shall describe the process that Consortium and the vendor will engage in for accepting the software modifications. Hexagon Response: Hexagon OnCall software is designed to be configurable while remaining COTS software. Any desired configuration should be accomplished/during our proposed configuration workshops and time allotted thereafter. Hexagon will work with the Consortium and, as part of the workshops, teach the Consortium how to configure the system as desired. For any software customization requests that go beyond configuration, the Consortium would work with the Project Manager to request/qa change to the core product. The Project Manager would then go through the documented Change Management process and work with Hexagon Global Product Center to review this request.s�To the extent the customization is approved by both parties, then it would be documented in a Change Order. Including any scope, schedule, and/or pricing adjustments. B. Business Process Workflows The Consortium requires the vendor to identify the business process workflows that are included with the system implementation. To ensure the successful implementation of the system, an assessment of the Consortium business processes "as -is" and future state is expected. The vendor should describe how various Consortium business processes are to be analyzed and implemented in the proposed system. Changes in business processes are expected to be incorporated into Section G. Organizational Change Management plans (see below). Hexagon Response: Hexagon understands that business process workflows are likely to change with the deployment of a new, multi -agency CAD, RMS and mobile solution. Hexagon's project team will work with the Consortium to identify and communicate such changes as described above. To facilitate this, Hexagon has proposed change management services be provided by third party, TDC. Related details are included in responses to the organizational change management section below. Additionally, we have proposed dedicated business process workshops to address this request. Onliaii Records BPA Workshop Overview Hexagon will conduct a Business Process Analysis (BPA) session early in the RMS portion of the project. The purpose of the BPA session is to enable Hexagon to gain an understanding of the current business Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 1 HEXAGON processes in place within the Customer environment related to law enforcement records. Additionally, this session is designed to help Hexagon and the Customer begin to determine the most effective and efficient use of the proposed solution before it is implemented. • Onl.all Records Overview Module Review— Based on legacy RMS Module usage and the statement of work Working with Address Server— Planning for Data Prep and Setup ▪ Preparing for Workflows — Planning For / Building Definitions and Administration • Working with Alerts — Planning for Data Prep and Setup • Questionnaires — Planning for Data Prep and Setup • •Regional System Setup Needs • Agency Specific Setup Needs • Department Data Flows • RMS/CAD Integration 0nCall Dispatch Configuration Consulting Sessions Hexagon resources provide a forum that allows Hexagon CAD personnel to obtain essential information for the initial configuration of the delivered CAD system. Hexagon has included three (3) of these four (4) day workshops. This time will be used to discuss the Consortium's CAD workflows, similar to a Business Process Analysis workshop. C. Report Development Provide a complete list of all "canned" reports available, and describe capabilities of individual agencies to search all data fields and create custom reports within the System as well as export data for agency analytics, ad hoc reports, data sharing, and public records requests. Hexagon Response: HxGN OnCall Analytics The HxGN OnCaii Analytics product suite provides tools for data visualization, business intelligence, and analytics for HxGN OnCaii Dispatch, and HxGN OnCaii Records. The suite is built upon a single data warehouse that provides a unified view of the data, organized in a manner that enables self -served analytics to both OnCall Dispatch and Records users. The product suite delivers: • Analysis -ready data models to extract, transform, and organize raw data from complex, underlying source databases into accessible, user-friendly data models for advanced reporting analytics • Pre -built interactive reports (dashboards) covering common operational and business functions • Templates for creating ad hoc analytics and reports Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 2 it, A HEXAGON • Advanced /� geospatial and playback visualization controls � to explore data in new ways HxGN OnCall Analytics I Dispatch Data Models lodels and Reports OnCall Analytics I Dispatch Data Models and Reports provides complete reporting and analysis capabilities. Best for complex analytics and larger data sets, it includes the OnCall Analytics Data Warehouse with 20 subject -area semantic models and 22 standard reporting templates as shown below. • Power BI reports. Built with Microsoft Power BI Desktop, these reports consist primarily of dynamic visualizations that interact with one other. These visualizations allow users to easily explore complex data and their relationships. In Power BI, a report can have one or more report pages and all the pages together are collectively referred to as the report. Delivered Power BI Reports. • Agency Response • Live —Dispatch Operator Activity • AVL Playback • Live Logged On Units • Broadcast • Live - Turn Out Times • Call Statistics • Message • /Calltaker and Dispatcher Workload • Point In Time • Cross Unit Dispatch • • Events by Type by Location • • Events by Type Heat Map • • Facility Recommendations • Unit Coverage Heat Map • Full Complement • • Live — Dispatch Performance Indicator • Exclusive to Dispatch Data Models and Reports are three operational semantic models, used for reporting on live data. They connect directly to a read-only replica of the live OnCall Dispatch database to allow secure, up-to-the-minute reporting. OnCall Analytics I Dispatch Data Models and Reports also includes OnCall Analytics I Power Visuals, a Microsoft Power BI add -on that provides enhanced geospatial analysis and playback controls. Features include. • Plot location -based information • Pin mapping • (Hot spot mapping • Geofencing (geospatial filtering) • Playback data over time, including multi -unit playback of AVL data • Dynamic, cross -filtering interaction with other Power BI visuals • WMS (Web Map Service) support Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 3 A HEXAGON HxGN OnCall Analytics I Records Data Models lodels and Reports OnCall Analytics I Records Data Models and Reports provides complete reporting and analysis capabilities. Best for complex analytics and larger data sets, it includes the OnCall Analytics Data Warehouse with 22 subject -area semantic models and 28 standard reporting templates as shown below. • 28 preconfigured Power BI reports that consist primarily of dynamic visualizations that interact These one other. I hese visualizations allow users to easily explore complex data and their relationships. In Power BI, a report can have one or more report pages and all the pages together are collectively referred to as the report. Delivered Power BI Reports. • Accident Details • Incident Monthly • Accident Monthly •Inci dpe nt Snapshot • Accident Snapshot •Jail pBooking Details • Arrest Details• Jail Booking Snapshot • Arrest Monthly •Jail Incident Details • • /A�rre st Snapshot • /Call for Service Monthly • • • /Citation Details • /citation Monthly • • vita tion Snapshot• • DUI Officer Performance • Misc Service Detail • DUI Snapshot • Offense Monthly • Evidence Snapshot • Use of Force Details • Use of Force Snapshot Also, included is OnCall Analytics I Power Visuals which is an add -on for Microsoft Power BI that provides enhanced geospatial analysis and playback controls (including multiunit AVL playback) for multiple industries, including public safety and utilities and infrastructure, without the need for a complex and costly GIS system. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 4 A HEXAGON D. Quality Assurance & Testing Pi.v The vendor shall develop a Quality Assurance Plan that describes how the desired levels of quality and software testing will be achieved throughout implementation. The Plan should identify resources from both the vendor and Consortium who will be involved in the processes of quality planning, quality assurance, and quality control regarding data, configuration, and software testing. The Proposer shall document any and all deficiencies identified during testing and the manner in which they will be resolved and retested. The system will not be accepted until all deficiencies have been resolved and final acceptance testing has been approved by Consortium. Hexagon Response: Hexag o/n� supports the proposed software through product lifecycle in many ways including Application Quality Control and Assurance Testing during software planning and development. Application Quality Control and Assurance Testing All of Hexagon software releases pass a stringent quality assurance testing process before being released for customer use. Hexagon is committed to delivering high -quality products that meet our customers' needs. As a result, Hexagon maintains a rigorous Quality Control System that includes established policies and procedures documented in a "living" Quality Assurance Reference guide. The Quality Assurance Reference establishes a tool to define test procedures and processes from the development of a product through validation and final release of each software version. The testing methodology is outlined in Section 2.19 "System Testing and Acceptance" in this proposal. Hexagon clarifies that once the Blocker Defects are resolved, the system would be ready for training and cutover. With regard to software certification, Hexagon products undergo the following testing during the certification process: • Functional verification testing, which tests specific functions within the product • Functional validation testing, which encompasses workflow validation within a product • Product interopera bility testing • Integration testing During quality testing, if bugs are uncovered, Change Request (CRs) and/or CR Defects (CR-Ds) are logged in Hexagon's CRM system, where they are individually tracked, fixed (as appropriate), and the fix verified. The Hexagon Quality Assurance Group maintains a series of functional tests used to validate the product. In addition, a series of specific workflow tests ensure that the core products integrate into a whole, seamless system. If bugs are uncovered during the certification of a system, Change Requests —Defects (CR-Ds) are logged in Hexagon's CRM system, tracked, fixed (as appropriate), and the fix is verified. With regard to implementation of a customer system, Hexagon tracks customer -specific configuration information, contacts, and software specifications by enhancement request or product defect report. Both Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 5 / HEXAGON enhancement requests and product defect reports can be tracked from initial filing through resolution and reports can be generated to provide the customer with a status regarding a particular request. Following implementation of a system, product enhancements are driven both by technological advances within the industry and by the customer base. Certification Process Hexagon designates software releases as either a Features Release or a Fixes Release. The differences between the two release types are described below. • Features Release AFeatures release is a software release that includes major modifications. Any of the following may be a part of a Feature Release: New functionality added to product Existing functionality enhanced or modified for reasons other than bug fixes Software redesign that does not add new or change existing functionality During a Features release, bugs identified in earlier software releases are addressed. Features releases occur approximately every 6 months. • Quality Update A Quality Update addresses "bugs." It is not designed to add new or modify (other than to fix known bugs) existing functionality. In order to lower the risk to the software, only those bugs sppeecifically identified by the Change Control Board (CCB) are addressed in a fixes release. The CCB consists of representatives from Quality Assurance, Development, Documentation, Support, and Services. E. Organizational Change Management NOTE — the answers to this section have been provided by third party TDC; Hexagon has proposed to implement change management in coordination with TDC, so the answers below reflect the third party's implementation approach. A full TDC SOW has been provided in Appendix A of this proposal. Vendors shall provide a description of their change control methodology during implementation and post -implementation. The change management plan should address: 1. Overall description of the change management strategy during implementation and post - implementation. TDCResponse. The TDC/Hexagon team proposes to engage in a three (3) phase approach to change management. Change management is essential to the successful implementation of any enterprise technology solution. In a public safety environment, where the effectiveness of tools and processes impact first responders Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 6 iff A HEXAGON and their ability to protect and serve the community, change management is imperative. The proposed phases and scope of change management are as follows. • Discovery / Planning • Continuous improvement/ Reinforcement/Monitoring The Discovery / Planning phase includes definition of the core aspects of the project as related to change and culminates in a definition of the activities and tools which will be used to manage change and ensure adoption of the systems and processes associated with the project. The Discovery / Planning process is intended to identify the stakeholders and the roles and responsibilities associated with the change management process. It also defines how change associated with the project will impact the collective organization and how change management issues will be identified. Managing change includes the execution of the steps and actions set forth in the change management plan. Managing change includes activities and steps designed to mitigate resistance, promote readiness, and promote adoption and beneficial use of the CAD and RMS systems. The Continuous improvement/ Reinforcement/ Monitoring phase includes activities intended to encourage and sustain continued beneficial use of the system and promote adoption. An after -project review will consist of a comprehensive objective evaluation of the process to provide the County with an informed analysis of the lessons learned through the life cycle of the implementation. 2. Process for identifying change management issues throughout the engagement. TDCResponse. Risks and issues captured during, and after, the Discovery process will be documented, tracked, and prioritized in a risk management database. All risks and issues will be managed to closure and include one or more mitigation activities that will be mutually agreed to with impacted stakeholders. 3. Anticipated roles and responsibilities of the Consortium team, the software firm, and the implementation firm. Hexagon and TDC Response: Hexagon has provided a description of its project team structure, roles and responsibilities in Section 2.20, Subsection C of this proposal response. In that same section, Hexagon provided a description of anticipated Consortium team roles related to the project. The Discovery / Planning process is intended to identify the stakeholders and the roles and responsibilities associated with the change management process. The Consortium's key stakeholders will include executives and/or project decision makers, users of the system and others who influence or are otherwise impacted by the project. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 7 4 A HEXAGON The change management plan begins with the definition of the key elements of change that will exist across each of the stakeholder communities in each of the key functional project areas (Process, Systems, Administration / Maintenance / Support). The Consortium team is responsible for presenting the As -Is in each of these functional project areas. The Hexagon team is responsible for the To -Be. The Hexagon /TDC Change Management and Implementation Team is responsible for the gap associated between the As -Is and the To -Be, as well as execution of the strategy for mitigating the various components of change resultant of the gap. 4. Strategy for communicating business process changes. TDCResponse: The Change Management Plan addresses all aspects of communication including types of communication, recipient, and frequency. Acommunications plan will be developed as a part of the change management plan. The communications plan will illustrate communications types, recipients, and frequency for the effective dissemination of informed data and project information which promotes the effectiveness of the project implementation. Sponsor engagement will be managed as a function of a series of activities designed to promote effective project governance, and to disseminate and actively communicate project goals, objectives, and status across all levels of project stakeholders. The Change Management Plan will be accompanied by the tools and templates that will be used to document, manage, and measure the effectiveness of the execution of the change management plan. Change management tools shall include systems used to promote real time access to project information, tools such as quick reference guides, and communications and marketing materials that inform users and stakeholders of upcoming project activities, events, milestones, and achievements. Recognizing project, user and stakeholder successes are a key element of project engagement and is a key instrument for the adoption of the change management strategies and activities associated with the project. Project successes will be an integral part of the communications strategy and will be included as a part of the marketing campaign literature and project status documentation. 5. Strategy for business process re -engineering. TDCResponse: The change management plan begins with the definition of the key elements of change that will exist across each of the stakeholder communities in each of the key functional project areas (Process, Systems, Administration / Maintenance / Support). The information gathered as a function of the Discovery Process will be used to develop a comprehensive and actionable change management plan. The change management plan will detail all change management activities, and a schedule associated with the execution of such activities. The Change Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 8 � A HEXAGON Management Plan provides an actionable work plan that address the key aspects of change in each stakeholder environment. Common and visual templates will be used to capture business processes and highlight key elements of change in the To -Be processes. 6. Tools for facilitating the development of business process maps based upon best practices. TDCResponse: The TDC team will identify the key elements of change as related to functional processes of the dispatch operation and the CAD and RMS system. Processes affected will be documented and categorized with the corresponding impact associated with new CAD and RMS implementation. The proposal assumes that the AsIsprocesses associated with each jurisdiction are documented and available. TDC personnel can provide services associated with the documentation of As -Is processes, but those costs are not included in the pricing within this proposal. 7. Strategy for mitigating change management issues. TDCResponse. Risks and Issues captured during and after the Discovery process will be documented, tracked, and prioritized in a risk management database. All risks and issues will be managed to closure and include one or more mitigation activities that will be mutually agreed to with impacted stakeholders. Readiness Assessments will be conducted at multiple stages of the execution of the change management plan to measure and assess progress toward achieving the stated goals and objectives of the project. Resistance can occur within a project at all levels of an organization. Resistance management techniques will be employed by both county leadership as well as the change management team to mitigate resistance and identify any potential for persistent resistance. Usage data, user forums, and other means will be used to assess sustained progress quantitatively and qualitatively, against the key change areas addressed in the change management plan. Common tools and metrics, agreed upon with project and program stakeholders, will be used to periodically measure progress toward increased beneficial use and to identify actions required to mitigate issues presented from such periodic assessments. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 9 � A HEXAGON 8. Communication p/an for milestones, schedule adherence, issues, etc. TDCResponse: Stakeholder confirmation includes the definition of both executive level stakeholders who set forth and provide the governance associated with the project, as well as the user community and others who influence and are otherwise impacted by the project and the change associated with the project. Goals and objectives of the project are identified and documented for all stakeholders as a step to define the key elements of change, and to identify potential areas of resistance.Sponsor engagement will be managed as a function of a series of activities designed to promote effective project governance, and to disseminate and actively communicate project goals, objectives, and status across all levels of project stakeholders. 9. Optimum team design and governance design for a successful change management program. TDCResponse: All Key Personnel changes will be subject to the approval of the Pinellas County Project Lead. The Hexagon /TDC communication plan and strategy, as well as the project execution strategy provides for distributed management of the intellectual capital associated with the project. This affords an understanding of the project across the project management and project leadership team such that no single change of key personnel effects a risk to the project. The key to a successful project and effective change management is the training and coaching of management and supervisory personnel to enable leaders to support and engage their teams and personnel in the various aspects of change. Training and coaching sessions will be conducted with management and supervisory personnel in the various elements of change, and mitigation of various forms of resistance Change management activities will be integral to training and change management personnel will work with training personnel in the development of training materials, quick reference guides, online training, and additional support references. 10. Strategy and process regarding any change of a Key Personnel after contract approval. The Consortium will have the right to request replacement of any team members. At the time of award, Hexagon will select the appropriate Project Team based on availability, experience, and nature of the requirements. Once in place, Hexagon agrees that key personnel will generally remain assigned to the Project unless unavailable due to death, illness, disability, military service, or termination of the employment relationship. During implementation, Hexagon's project management team is responsible for maintaining project communication with the Consortium Project Manager in the performance of the project. The Consortium Project Manager provides a single point of contact for working with Hexagon and Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 10 HEXAGON maintains sufficient authority within the project to make day-to-day decisions concerning the personnel and material resources. 11. All associated estimated costs for any change in proposed methodologies. Hexagon Response: Hexagon expects the Consortium will participate in a period of negotiating terms and conditions of the project, includingproposed methodologies. Hexagon will agree to abide by the terms negotiated at that Consortium Should the Consortium require a change in the methodology after a contract has been executed, Hexagon would facilitate a change order process to determine any potential change in cost. Hexagon cannot provide an estimate for costs associated with a change in proposal methodology at this stage in the RFP selection process. H. Budget and Staffing Plan Based on vendor experience with similar organizations, explain the extent to which the Consortium should include a contingency factor for additional work effort in its project budget and staffing plan. Hexagon Response: Hexagon clarifies that due to the/�nature of the RFP process (not having had the opportunity to discuss this proposal directly with the Consortium) and its known and unknown variables, Hexagon is not able to make a firm recommendation related to contingency/budget/staffing strategy./Should Hexagon move forward in the RFP process, we are prepared to discuss these items with the Consortium as needed. I. Interfaces The vendor shall provide a list of 3rd party vendors used by the Consortium that already interface with their system. Hexagon Response: Hexagon understands this requirement as instruction to provide a list of which third party vendors we already interface with from the Consortium's provided interfaces list. Those third parties are listed below. This list does not represent every third party vendor Hexagon's applications have ever interfaced with. • Tyler Odyssey • Coplogic • NCIC/FCIC • Motorola VESTA • ANI/ALI and NG911 with various third party telephony providers • VIPAR Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 11 � A HEXAGON • Uata works �V�ugshots • Lin/ • Federal and other state NIBRS • DAVID/FDLE (in progress) • Everbrid ge • RapidSOS J. Hardware, Equipment, and Technical Architecture The vendor shall provide requirements regarding sizing and performance of all hardware needed to implement the complete solution. The vendor shall be responsible for the satisfactory performance of the software included in the proposal. The vendor shall provide an architecture proposal document that describes the completed System topology and various systems interactions (preferably a Visio diagram). The Consortium prefers to avoid pursuing unique data definitions and proprietary systems wherever possible. The Consortium would like the System to have interoperability and ability with equipment available from other vendors, thus ensuring the proposals provide a maximum choice of equipment. Refer/Respond to Attachment A - System Requirements Survey. Hexagon has included a system configuration diagram in Appendix C of this proposal. The first page of this diagram includes specs for recommended hardware to support the proposed cloud solution. K. Pre- and Post -Implementation Support Plan The vendor must provide a Pre- and Post -implementation Plan that describes the approach to software support during the implementation and after go -live. Vendors shall describe what level of support is available under their proposed fee structure. If varying levels of support are available, this section of the vendor's response should clarify these potential services and highlight the level of support that has been proposed. The p/an shall address: I. Pre-imp/ementation support (e.g., number of months of on -site support to include the Proposer's Business Analysts and trainers). Once the contract is awarded, the Consortium will be assigned a Hexagon Project Core Team who will be engaged throughout the implementation, with some work done on site and some work done remotely. 2. Transition plan from project to ongoing operational support. Hexagon Response: After cuttove/r,, the implementation team works to transition each PSAP to Hexagon's customer support center. The Consortium will also be assigned an account manager who will be available for assistance making requests. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 12 A HEXAGON 3. Organizational change management. Hexagon Response: Hexagon has proposed organizational change management services be provided in coordination with third party TDC. A full change management SOW has been included in Appendix A of this proposal. Hexagon has also provided details in response to item E "Organizational Change Management' above. 4. Post -implementation support (e.g., number of months of on -site support after go -live). Hexagon resources will provide Post-Cutover support to Customer. The "Post-Cutover Support Period" is the ten (10) Business Days beginning the Monday following each Cutover. For OnCall Dispatch, this support period is conducted on site the first week and remotely the second week. For OnCall Records, this support period is conducted remotely for both weeks. It is designed to provide the Customer with dedicated, quickly accessible support for questions and Errors encountered following the Cutover to production use of the new System. Hexagon resources will be assigned Blocker Errors that are filed by the Customer against the new System. 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 Errors will not be supported during this time frame. 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. Additionally, Hexagon has optioned 12 months of on site Resident System Administrator (RSA) services to begin at the first PSAP cutover. The RSA services can be renewed at the Consortium's discretion for additional years of on site post-cutover support. 5. Telephone support (e.g., include toll -free support hotline, hours of operation, availability of hotline twenty-four (24) hours per day and seven (7) days per week). The Hexagon Customer Support Center is provides as toll -free, "Always -available" support mechanism that is a central point -of -contact for all problems. Our Helpdesk is structured as a Tiered system. Tiered support: Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 13 A HEXAGON Level 1 — Triage: Live helpdesk 24/7 — no recordings or callback numbers Level 2 — Americas Support: Out -of -the -box functionality support/software errors • Level 3 — Global Product Center Support: Core code support including Defects or Enhancements 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 6. Special plans defining "levels" of customer support (e.g., gold, silver, etc.). Define what level of support is being proposed. Hexagon Response: 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 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 • Problem resolution based on priority level Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 14 A HEXAGON 7. Response time for, and definition of various types (levels ofseverity) of problems reported to the support network (e.g., critical issue response time). Hexagon Response: When reporting an issue to Hexagon Customer Support, the customer initially determines the priority level of the Error and, following investigation, theme Center 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 Maintenance: PRIORITY Level One Level Two Level Three Level Four PROBLEM DESCRIPTION RESPONSE TIME • Loss of data • Data corruption • Productive use prohibited • No workaround available • Aborts • Primary purpose compromised • Productive use significantly impacted • Workaround generally not available • Productive, but incomplete operation • Workarounds generally available • Productive, mainly cosmetic in nature • Workarounds or configurable M-F, 7:OOAM-7:OOPM Central Time — Immediate* o• r within 30 minutes of notification M-F, 7:OOAM-7:OOPM Central Time — Immediate* o• r within one hour of notification during normal business hours M-F, 7:OOAM-7:OOPM Central Time — Immediate* o• r within eight hours of notification during normal business hours M-F, 7:OOAM-7:OOPM Central Time — Immediate* o• r within eight hours of notification during normal business hours options generally available * Immediate - Without need to call back in most cases Priority Level One Errors that have no discernible workaround are escalated, when appropriate, to Hexagon Customer Support Management who participate in the decision -making and resolution process. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 15 A HEXAGON 8. The delivery method of future upgrades and product enhancements, including historical frequency of upgrades by module. Hexagon Response: Hexagon software feature updates for OnCall have been historically released on a bi-/annual basis. Upgrades of Hexagon software and documentation are provided to customers via its Cloud subscription. As part of the proposed Cloud Services Support, the Consortium is entitled to receive all updates and C upgrades to the purchased loud Application(s) and Local Software that Hexagon makes available. Cloud ConsultingCloud Services may be necessary/�to upgrade or update interfaces on the local interface server (i.e. NCIC), which are not part of loud Services Support. From time to time, Hexagon may notify the Consortium 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 Cl oud or upgrade to the Development Environment for Consortium testing and review, which the Consortium shall complete within the time prescribed in the notification of the availability of the update or upgrade. In the event no material adverse effect is reported by Customer during that testing period, then on a subsequently specified date by Hexagon, Hexagon will, at its discretion, deploy the update or Cl oud to Consortium Environment for production. All Hexagon software releases must pass a stringent quality assurance testing process before being released for customer use. 9. Product road maps detailing anticipated changes to the system over the next 3-5 years. Hexagon Response: 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. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 16 � A HEXAGON 10. Availability of user groups and their geographic areas. Hexagon Response: The Hexagon international Users Conference is held yearly, usually in June. This is a large event and encompasses all Hexagon brands. New Products are launched. There is a full show floor called "The Zone" where customers may meet with product experts for demonstrations, with the ability for "hands-on" with all products. • Training sessions are held, free of charge (pre -registration is required). Customers may obtain valuable information from a free training session. These are usually held on the day prior to the are created and available by product grouping for customers to attend sessions, meet with other customers and industry leaders, as well as our Account Managers, Pre -Sales Teams to gain valuable information. • There is a full user group meeting which Just users (no Hexagon employees) attend and discuss issues, enhancements, etc. There are also regional User Conferences held. Depending on the area, some meet quarterly, some meet yearly, and some meet semi-annually. Hexagon experts are invited into these meetings to demonstrate new products, upgrades, etc. Hexagon Product Managers will sometimes discuss road map features and field questions. These conferences are organized and held at customer sites / local areas within their regions. No Hexagon employees are involved in the private sessions. Hexagon schedules "boot camps" which are chargeable events, but provide full training on such topics as CADSystem Administrator, 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. 11. Problem reporting and resolution procedures, including a timeline for resolution. Hexagon Response: The Hexagon Customer Support Center is an integral part of Hexagon's Maintenance Program and is provided at no additional cost with the cost of a cloud subscription. 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 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 Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 17 � A HEXAGON Problem resolution based on priority level 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 Error to Hexagon Customer Support, the customer initially determines the priority level of the problem and, following investigation, 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 Maintenance: PRIORITY PROBLEM DESCRIPTION Level One Level Two Level Three Level Four • Loss of data • Data corruption • Productive use prohibited • No workaround available • Aborts RESPONSE TIME M-F, 7:OOAM-7:OOPM Central Time — Immediate* or within 30 minutes of notification • Primary purpose compromised • Productive use significantly impacted • Workaround generally not available • Productive, but incomplete operation • Workarounds generally available • Productive, mainly cosmetic in nature • Workarounds or configurable options generally available Immediate -Without need to call back in most cases Priority Level One Errors that have M-F, 7:OOAM-7:OOPM Central Time — Immediate* o• r within one hour of notification during normal business hours M-F, 7:OOAM-7:OOPM Central Time — Immediate* o• r within eight hours of notification during normal business hours M-F, 7:OOAM-7:OOPM Central Time — Immediate* o• r within eight hours of notification during normal business hours no discernible workaround are escalated, when appropriate, to Hexagon Customer Support Management who participate in the decision -making and resolution process. Hexagon uses a Customer Relationship Management (CRM) system for tracking technical support incidents reported by customers. First line support requests are logged into Hexagon's CRM System, Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 18 / HEXAGON 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 CRM System. The system is also used to track escalations and reports are run on a regularly scheduled basis to identify escalation problems. Support staff also use the CRM 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 teleconference to view customer workflows. 12. Bug fixes and patches release frequency. Hexagon Response: Hexagon designates software releases as either a Features Release or a Fixes Release. The differences between the two release types are described below. • Features Release AFeatures release is a software release that includes major modifications. Any of the following may be a part of a Feature Release: New functionality added to product Existing functionality enhanced or modified for reasons other than bug fixes Software redesign that does not add new or change existing functionality During a Features release, bugs identified in earlier software releases are addressed. Features releases occur approximately every 6 months. • Quality Update A Quality Update addresses "bugs." It is not designed to add new or modify (other than to fix known bugs) existing functionality. In order to lowertherisk to the software, only those bugs specifically identified by the Change Control Board (CCB) are addressed in a fixes release. The CCU consists of representatives from Quality Assurance, Development, Documentation, Support, and Services. 13. Additional consultants or personnel available for the proposed support level. Hexagon Response: The Consortium will be assigned a Hexagon account manager who will be a resource should the Consortium have questions or requests after the new system has been implemented. Hexagon has proposed an optional Resident System Administrator (RSA) to provide post-cutover support. The Consortium may choose to purchase the RSA and renew the RSA for additional terms, if desired. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 19 A HEXAGON 14. Other support (e.g., on -site, remote dial -in, website access to patches, fixes, and knowledge base). Hexagon Response: Hexagon has proposed an optional Resident System Administrator (RSA) to be an on site resource for the Consortium. The Consortium may choose the renew the term of the RSA to provide additional post - implementation on -site support. As the OnCall suite is browser -based and will be managed by Hexagon, the Consortium will not be expected to download and install patches or fixes to the OnCall applications. Rather, the Consortium users will simply need to log out/log in to the applications and updates will be automatically applied. The Consortium will have access to an online knowledge base that is searchable by topic and by application. In addition to the Customer Support Center, the Consortium's Hexagon account manager will be available to address questions the Consortium may have about the system. 15. /f there is to be a separate maintenance contract, the vendor should attach an example of such a contract, if applicable. Hexagon Response: This is not applicable. Hexagon is proposing a cloud SaaS solution for the Consortium that will have recurring subscription fees, but not a separate maintenance contract. Maintenance support for Custom Interfaces and Third Party products is included in the Recurring Cloud Subscription Fee. The Cloud and Maintenance Support provisions are provided in the Master Terms, a link to which has been included in Appendix E of this Proposal. L. Training Pi. It is the Consortium's intention that the selected vendor will coordinate the in person training of a// participating agency personnel in the use of their application and that satisfactory implementation of an approved training plan will be a key component of this project's deliverables. The vendor must provide a detailed plan for training. This training plan must include the fo/lowing: 1. The role and responsibility of the software and/or implementation vendor in the design and implementation of the training plan (e.g., development of customized training materials, delivering training to Consortium end -users) 2. A detailed organizational change management plan to help members in the Consortium organizations adapt to the new System. 3. The role and responsib/lity of Consortium staff in the design and implementation of the training plan. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 20 A HEXAGON 4. Overview of proposed training plan/strategy, including options for on -site or off -site training services for the core project team, end -users, and technology personnel. 5. The proposed training schedule for Consortium personnel of various user and interaction levels to include shiftwork. 6. Descriptions of classes/courses proposed in the training plan - the vendor should specify the unit of measure for its training, e.g., units, classes, days, etc., and define the number of hours associated with these units of measure. The vendor must be very clear about exactly what training courses are included in the cost of the proposal. 7. The knowledge transfer strategy proposed by the software and/or implementation vendor to prepare Consortium staff to maintain the system after it is p/aced into production. 8. A detailed description of system documentation and resources that will be included as part of the implementation by the vendor including, but not limited to, detailed system user manuals, "Quick Reference" guides, Online support, Help -Desk support, Entity Relationship Diagrams, user group community resources, and others as available. 9. The ongoing training support post -implementation provided, should the software be upgraded and continue to change (online documentation, manuals available, etc.). Hexagon Response: Hexagon is no stranger to deploying large, multi -agency public safety systems, similar to the Consortium. Hexagon has provided references to that point in Section S below. Hexagon will use our tested and proven approach to training that allowed us to successfully train current customer NYPD, which included approximately 1500 communications personnel and approximately 4000 uniformed members of service. Every Hexagon project for a Public Safety system includes the implementation workshops and training classes necessary to ensure that personnel operating and maintaining the Hexagon software have a full T understanding and working knowledge of the system. I o accomplish this goal, both workshops conducted in a consulting environment and formal training courses are provided to appropriate agency personnel. Implementation Workshops For new system implementations, Hexagon personnel begin the education and configuration process with agency personnel by conducting implementation workshops that involve installing the core system and building the necessary site specific data for the system to function properly, 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 as well as data management and configuration tools, and will learn the steps necessary to organize and gather the data needed. Customer personnel who attend these workshops should include the System Administrator, the Core Trainers, and other stakeholders as needed (Support Personnel, Command Staff, Trainers, Power Users). Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 21 A HEXAGON Application Training Application training includes courses that teach users in the proper use of the particular application, as well as administrators and other supporting personnel in the administration, configuration, and maintenance of the system. The Train -the -Trainer approach is the most logical training solution for most large public safety projects. This method seeks to train the agency trainers and power users who learn all functions of each Public Safety application, as well as techniques for the best way to teach user -level employees. Due to the vast functionality of the system, there may be some application commands or functions that 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 what commands and/or functions within the system will be used as part of their operation. This Training Consulting will also provide the opportunity to support the customer team responsible for the design and development of the training curriculum, and make recommendations for customizations necessary to create a successful training program for users. Hexagon acknowledges the Consortium's request for onsite training and has included that in this proposal. Hexagon also acknowledges the Consortium's request to train all end -users. While Hexagon does on occasion propose end -user training, it is our belief that Train -the -Trainer is a best practice and provides the following benefits. • Stability — Train -the -Trainer creates an internal team of experts who can be consulted for training new staff/officers after the Hexagon -led training has already taken place. This equips the Customer to be self-sufficient and to require less frequent supplemental training from Hexagon after the system has been implemented. • — More time, resources and cost are required to train all users on a new system, especially with larger agencies. If all users are trained and turnover happens, then the Customer would experience a loss on its training investment when individuals are no longer with the agency. • Red.oes length of project — Training all users directly requires time, particularly for large, multi - agency Customers with several locations varying numbers of personnel working various shifts. It is Hexagon's experience that a Train -the -Trainer approach equips the Customer's trainers with the skills and support they need to lead their own end -user training while Hexagon's implementation team continues to carry out the project. Hexagon has made web -based training available through purchase of our new e-Learning product, Dynamo. A 24-month Dynamo subscription (beginning when the first training licenses are provided) has been included in this proposal. Hexagon has included licenses that can be allocated for use towards OnCall Dispatch, OnCall Records and OnCall Analytics training. Upon selection, Hexagon and the Consortium can discuss how many of the proposed licenses should be designated for each product. System Administration Training offers System Administrator level courses that provide the necessary training to persons who will be responsible for system configuration, support, and maintenance. There are also courses designed to teach the use of available configuration tools and techniques, as well as a site -specific administration and maintenance session designed around the customer's specific configuration. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 22 A HEXAGON Change Management 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. Hexagon acknowledges the Consortium's request for organizational change management to facilitate a successful implementation of the new public safety system. Hexagon has proposed change management services be provided in coordination with third party TDC. Related details are included in responses to the organizational change management Section E above. Classroom and Facility Logistics • For training classes, industry best practices dictate that the class size should not exceed 12 persons for trainer and user classes, and 6 for technical classes (system administrator and database level). • 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. • Class days are typically based upon 8-hour sessions per working day. • 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 Resources and Materials The Dynamo subscription is renewable at the Consortium's discretion and would be a valuable post - implementation training resource. Each student will receive a soft copy of all training materials and documentation for purchased classes in a pdf format. Additionally, Hexagon provides customers with access to an online support knowledge base with keyword search capability. Users can easily search the knowledge base to facilitate problem resolution. The Consortium will also be able to make toll -free phone calls to the Customer Support Center for help with any functionality questions or problems that may arise. Adata dictionary is included with the OnCall Records installation documentation with each release in pdf format. Hexagon also provides an ERD and schema documentation, however, our documentation does not include full English -language descriptions of every field. Additionally, we have a "data assist" feature in the OnCaii Records product that enables users to see the name of the database table/field that supplies the data for any particular field in the user interface. The Hexagon International Users Conference is held yearly, usually in June. This is a large event and encompasses all Hexagon brands. New Products are launched. There is a full show floor called "The Zone" where customers may meet with product experts for demonstrations, with the ability for "hands-on" with all products. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 23 /HEXAGON • Training sessions are held, free of charge (pre -registration is required). Customers may obtain valuable information from a free training session. These are usually held on the day prior to the Main Conference Kick-off. • are created and available by product grouping for customers to attend sessions, meet with other customers and industry leaders, as well as our Account Managers, Pre -Sales Teams to gain valuable information. • There is a full user group meeting which Just users (no Hexagon employees) attend and discuss issues, enhancements, etc. There are also regional User Conferences held. Depending on the area, some meet quarterly, some meet yearly, and some meet semi-annually. Hexagon experts are invited into these meetings to demonstrate new products, upgrades, etc. Hexagon Product Managers will sometimes discuss road map features and field questions. These conferences are organized and held at customer sites / local areas within their regions. No Hexagon employees are involved in the private sessions. Hexagon schedules "boot camps" which are chargeable events, but provide full training on such topics as CADSystem Administrator, 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. Proposed Training Courses Hexagon has proposed several training courses necessary for the customer to understand the CAD, RMS and Mobile systems. Hexagon provides training courses as well as workshops which are included with Hexagon's base pricing for the benefit of the customer. The training classes typically run 2-4 days depending on the course and are not intended to be configuration sessions. The workshops typically run 4-6 hours and have 2-4 hours of implementation work followed by the loading of data or configuration. The length of standard coursework varies but assumes an 8 hour day. • OnCall Dispatch Fundamentals (Core Team) • OnCall Dispatch System Administrator Training • OnCall Dispatch Train -the -Trainer • O nCall Mobile Unit Trei n-th e-Treiner • OnCall Dispatch Mobile Responder Train -the -Trainer • OnCall Analytics I Dispatch User Training • OnCall Analytics I Dispatch System Administrator Training • OnCall Analytics I Records User Training • OnCall Analytics I Records System Administrator Training • OnCall Records Train -the -Trainer Training & • Federal State NIBRS Training Hexagon has included course descriptions for the proposed courses below. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 24 A HEXAGON HXGN 0ri C 11 Dispatch COURSE OVERVIEW Fundam en ta I s for care eam ®t„: HxGN OnCall Dispatch Funda menials for Core Tee m is a four -day course to familiarize the agency's Core Team with the features and functions 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. Students completing the course should have a good working knowledge of using HXGN OnCaii Dispatch Advantage and Mobile Unit. 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 PREREQUISITES • Customer Environment fully 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 remotely by Hexagon Personnel Target Audience Customer Project Core Team and Other Stakeholders Duration per Course Four (4) days Student Capacity Twelve (12) students Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 25 A HEXAGON HxGN Or,Cali Dispatch I Advar tags Sy stern Administrator Trainit,g (Qt,,: 1) 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 OnCall database and use available tools to administer and configure the system. MAJORTOPICS • Understanding the Environment • Map Legend Management • UI Editor • Layout Manager/n • Notification Configuration • Custom Fields • Parameter Management • Deployment Configuration • Response Plans Configuration • Role Codes Management • Agency Management • Geographic • Resources • 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 remotely by Hexagon Personnel Target Audience Personnel responsible for administering and supporting the system Duration Four (4) days Student Capacity Six (6) students Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 26 A HEXAGON H]GN OnCall Dispatch I Advantages Train -the -Trainer (Qty: 1) HxGN OnCaii 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, mobile units, and fire station printers is also presented, if the interfaces are available. Students completing the course should have a good working knowledge of using HXGN OnCaii 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 OnCaii 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) students Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 27 A HEXAGON HXGN Or,Cali Dispatch I Mobile Unit Train -the -Trainer (Qty: 1) 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 OnCaii Dispatch I Mobile Unit software. Trainers will learn all of the essential functions of HxGN OnCaii 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 I Mobile Unit (if applicable) • Using training guidelines and techniques for HXGN OnCall Dispatch I Mobile Unit PREREQUISITES • 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 CADevents Duration One (1) day Student Capacity Twelve (12) students Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 28 A HEXAGON Mobile Responder rain -the- reinter •ty. 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 • 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 on site 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) Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 29 A HEXAGON HXGN OnCall Analytics I Dispatch User Training (Qt,,: 1) 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 lD�ispatch. 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 • Introduction • Overview and Navigation Delivered Reports and Data Models • Overview of delivered reports • Overview of analytical data models • Overview of live data modelsis Creating and Modifying Reports: • Add Visualizations • Filtering Visualizations is Formatting Visualizations • Pages — Size and Alignment • Interacting and Sharing Power Visuals ating pin, cluster and heatmaps Creating • Playback data over time PREREQUISITES • Familiarity with Windows -based applications • Familiarity with agency workflows COURSE DETAILS Corse Duration Two (2) days Course Type Conducted on site by Hexagon Personnel Student Capacity Ten (10) Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 30 A HEXAGON HXGN OnCaii Anaiytics I Dispatch System Administrator Training (Qty: 1) 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 OnCaii Analytics - Dispatch Solution. TARGET 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 Capacity Four (4) Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 31 A HEXAGON HXGN OnCaii Analytics I Records User Training (Qty: 1) COURSE OVERVIEW HxGN OnCall Analytics I Records 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. l� This course is designed to familiarize the end user with HXGN OnCall Analytics I lR�ecords. 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 • Introduction • Overview and Navigation Delivered Reports and Data Models • Overview of delivered reports • Overview of analytical data models • Overview of live data modelsis Creating and Modifying Reports: • Add Visualizations • Filtering Visualizations is Formatting Visualizations • Pages — Size and Alignment • Interacting and Sharing Power Visuals ating pin, cluster and heatmaps Creating • 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) Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 32 A HEXAGON HXGN OnCaii Anaiytics I Records System Administrator Training (Qty: 1) COURSE OVERVIEW This System Administrator Training course is designed for System Administrators, toprovide instructions on the o setup, site -specific configurations, and administrative tasks needed to maintain the I IxGN OnCall Analytics Records Solution. TARGET 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 RMS configuration COURSE DETAILS Course Duration One (1) Day Type I ype Conducted on site by Hexagon Personnel Student Capacity Four (4) Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 33 � A HEXAGON H.GN OnCaii Rewords Train -the -Trainer Training (Qty: 3) This course provides training for the agency -designated trainers. All modules will be reviewed and related to each department in the agency such as Records, Patrol, Investigations, Personnel, Administration, Evidence, and other departments. The users review the modules, searching capabilities, reporting, and other features in the OnCall Records. MAJOR TOPICS • Navigating in OnCall Records • Understanding the OnCall Records tabs: Hone, Reports, Search, Master Indices, Investigations, Court, Jail Management, Traffic, Evidence Management, Department, and Other Info • Understanding the Master Indices (Master Name, Master Vehicle, Master Location) • Reviewing the OnCall Records Modules • Understanding the Master Indices (Master Name, Master Vehicle, Master Location) • Reviewing OnCall Records modules • Using the Record Properties menu • Using the Records Linked menu • Linking data • Configuring alerts • Exporting search results • Setting alerts • Understanding workflow • Combining Master Index records • Using canned and Report Server reports PREREQUISITES • Introduction to Windows course or equivalent knowledge and familiarity with the Windows user interface • Understanding of basic Public Safety terminology • Knowledge of agency business processes • Agency modules to be used have been identified • OnCall Records configuration complete • OnCall Records Customer Functional Testing complete TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience Agency trainers or end users Duration 4 Days Student Capacity 12, with a maximum of one student per workstation Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 34 A HEXAGON Federal and State NIBRS Training •ty. MAJOR TOPICS • NIBRS Introductions & Historical Background • Statute Table & Code table setup and importance • Group A & B Definitions • Group A & B Data Elements • Validation process • Error Messages • Data Entry— Group A Incidents (Crimes against persons) • Data Entry — Group A Incidents continued (Crimes against property) • Data Entry — Group A Incidents continued (Crimes against society) • Data Entry — Group A Arrest • Data Entry — Group B Arrest • NIBRS Reporting Client Fields & Components • Submitting and Marking the Records • Generating a NIBRS Submission Report • Understanding the Flatfile layout • Time Windows • Sending files to the State TRAINING DETAILS Method. Conducted remotely by Hexagon Personnel Prerequisites. Customer has completed their pick lists and statute tables configuration Facility Requirements: • Training room with up to 10 student workstations • Trainer workstation • Projector connected to trainer workstation Desired Facility Abilities. Internet access available (WiFi preferred, wired acceptable) Course/Session Materials: • NIBRS User Manual • FBI NIBRS Technical Specification v3.1 Required Attendees: • Hexagon NIBRS trainer • Customer NIBRS team members • Customer IT/System administrators Duration: 3 days Student Capacity. 10 students Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 35 ig A HEXAGON Hexagon's Proposed Training Plan for the Consortium Below is a high-level, consolidated overview of the training plan and timeline for the Consortium. Hexagon would like the opportunity to discuss this plan directly with the Consortium as several factors (such as project timeline, budget and number of available agency trainers) will affect whether or not this is the best approach. In our experience implementing training plans for other large, complex agencies and consortiums, Hexagon has learned that dialog is needed to provide a plan that looks good on paper and will be successful in practice. We will be a knowledgeable resource and partner for the Consortium when it is time to finalize a training plan. Training Strategy Hexagon has proposed a best practice Train -the -Trainer approach for the Consortium. These Hexagon - led courses will be provided on site and will be performed during the project prior to when the first PSAP cutover begins. It is Hexagon's intention to provide this training to the Consortium's designated agency trainers. Course descriptions and class sizes are included above. Hexagon requests that the Consortium review this proposed plan and advise if additional instances of the above courses are needed in order to train the number of agency trainers the Consortium has. These train -the -trainer courses will provide the Consortium's trainers with the knowledge to create an end -user training plan for their respective agencies. Once Hexagon's training has been performed, it is our recommendation that the Consortium trainers then perform end -user training over the next 30 days for their respective agencies prior to each PSAP cutover. To facilitate the Consortium -led end -user training, Hexagon has also proposed a subscription to our Dynamo eLearning platform. Hexagon recommends the Consortium incorporate the Dynamo classes as part of its end -user training to reduce the burden on the agency trainers and to provide a better overall learning experience both during and after the Consortium completes its initial end -user training classes. Training Timeline Hexagon has proposed a tentative project schedule in response to Section 2.20—Objectives. As shown in that schedule, it is Hexagon's recommendation that train -the -trainer training is completed before Consortium -led training and PSAP cutovers. Hexagon recommends the Consortium create an end -user training plan with each of the trainers who participated in our training. These trainers and the Consortium should be responsible for agreeing to train end -users in the desired timeline prior to the first PSAP cutover. Hexagon clarifies a readiness review will be performed before a system can complete cutover. End users will need to be trained for each PSAP prior to that PSAP cutover. For example, the end users of PSAP #1 will need to be trained prior to PSAP #1 cutover. The end users of PSAP #5 will need to be trained prior to PSAP #5 cutover. The timeline for the end -user training to occur within that framework for all agencies and shifts is at the Consortium's discretion. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 36 A HEXAGON M. Third -Party Products The vendor shall explicitly state the name of any third -party products that are part of the proposed solution for Consortium. For each third party product, there shall be a statement about whether the vendor contract will encompass the third party product and/or whether the Consortium will have to contract on its own for the product. The successful vendor shall be responsible for the implementation, integration, and satisfactory performance of any third party software included in the vendor's proposal. The proposal must describe any products, features, or other value-added components recommended for use with the proposed system that has not been specifically requested in this R.F.P. The vendor shall also provide proof that it has access to the third -party software source code (owned or in escrow) and that the vendor has the ability to provide long- term support for the third -party software components of its system. Consideration of these product features or other value-added components will be given where they may be of value to the Consortium. Vendors must include all costs of any third party products, inc/uding the software license cost, maintenance, implementation, integration, training cost, estimated hardware costs, and any other related costs (operating system, database, layered products, etc.), including third party software in the total cost of this proposal. Vendors must also include how many times they have integrated with the respective third party products. The vendor must still meet all necessary Project Plan schedules, requirements and abide by all of the Consortium's R.F.P. requirements, regardless of whether they utilize a third party product. Hexagon has proposed the third parties below as part of the solution for the Consortium. Each of these third party products and services meets specific requirements of the RFP; there is no add -on functionality encompassed with these third parties. Each of the third party partners below was made aware of the source code requirement referenced in the RFPtext above. Hexagon does not currently have a source code escrow agreement with any of the below third parties and because the solution is a SaaS solution, escrow is atypical and has not been included. Hexagon has included third party pricing in Section 6 — Proposal Pricing as requested above. Hexagon acknowledges the Consortium's requirement for vendors to meet agreed upon project timelines for any third party services/products proposed. White BCDX Hexagon's proposal incorporates White Box data conversion services and no additional contract between the Consortium and White Box is needed to secure those services. A full White Box SOW is included in Appendix A of this proposal. Hexagon has had a relationship with White Box for many years and the third party's approach to data conversion phas been vetted and approved by the Hexagon services team. Hexagon is currently working with White Box to provide data conversion for Lee County, FL. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 37 A HEXAGON Com mSys Hexagon's proposal incorporates CommSys ASAP consulting services and Con nectCIC product, no additional contract between the Consortium and CommSys is needed. Hexagon has partnered with CommSys to provide queries to NCIC. CommSys has over 20 years' experience in providing solutions and services for public safety software vendors in service and technology supply for state, regional and national CJIS interfaces. CommSys's ConnectClC solution boosts agency productivity and efficiency while improving the solution provider's ability to deliver integrated CJIS access, and more importantly, provide value to the end user. This is a packaged, yet customizable, solution saving solution providers significant costs and time in internal development. ConnectClC Basic Inquiry includes: wanted persons (State/NCIC), stolen vehicle, boat, gun and article (State/NCIC), DMV information (State/Nlets), vehicle registration, driver's license, and driver's history. Below are three examples/�of projects Hexagon and CommSys have worked together on that are similar in functionality to the Consortium. Project 1 — Newport News Police ASAP a. Agency: Newport News Police Department, VA b. Project Date: 2016 d. Responsibilities of each party: Develop implementation plan/for ASAP, based on agency requirements. Provide professional services to support the implementation. Coordinate with the agency's CAD provider the installation of the CAD providers interface application solution in both a Test environment and a Production environment as applicable. Work with agency officials to ensure connectivity to the Nlets network via the state CJIS Message Switch or other transport method if available. Coordinate with alarm companies that are operating in production with the ASAP project and with agency officials through cutover to production. Project 2 — Memphis PD Consulting for Alarm Protocol a. Agency: City of Memphis Police Department, TN b. Project Date: 2018 d. Responsibilities of each party: Develop implementation plan/for ASAP, based on agency requirements. Provide professional services to support the implementation. Coordinate with the agenCy'S CAD provider the installation of the CAD provider's interface application solution in both a Test environment and a Production environment as Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 38 ig A HEXAGON applicable. Coordinate with alarm companies that are operating in production with the ASAP project and with agency officials through cutover to production activities. Project 3 — Phoenix PD a. Agency. Phoenix PD, AZ b. Project Date: 2013 c. Applications Installed: CLIPS and ConnectCIC d. Responsibilities of each party: CommSys used their CLIPS software with approximately 1,800 licenses, plus implemented their ConnectCIC software and facilitated all of Phoenix transactions from Hexagon's inPursuit RMS to the State of Arizona. Telecom munications Development Corporation (TDC) Hexagon's proposal incorporates TDC change management services and no additional contract between the Consortium and TDC is needed. A full TDC SOW is included in Appendix A of this proposal. TDChas over eighteen (18) years of experience leading and/or supporting the implementation of public safety systems in major metropolitan and complex campus environments. TDC has lead or supported CAD/RMS public safety technology projects with the following clients /jurisdictions: • • Maryland Aviation Authority • Amtrak • Washington Metropolitan A. • City of Detroit • Fulton County, GA • Georae Washinaton Univer TDChas a decades long relationship with Hexagon (Intergraph). TDC currently provides a variety of services and support to the Hexagon team including project management, GIS/ mapping, and implementation support. In addition, TDC provides support to existing Hexagon customers as a Resident System Administrator providing user support, database maintenance and support, as well as support of upgrades, enhancements, and configuration changes. Tra ncite Hexagon's proposal incorporates Trancite Easy Street Draw product and no additional contract between the Consortium and Trancite is needed. A full Trancite SOW is included in Appendix A of this proposal. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 39 A HEXAGON Clevest Hexagon's proposal incorporates the Clevest Enterprise Mobility Platform - Platinum product to meet Federal NIBRS and FL IBRS reporting and validation requirements. No additional contract between the Consortium and Clevest is needed. Clevest has not completed any projects with Hexagon. Hexagon is currently working with Clevest to provide this functionality for the City of New Orleans, LA. N. Contract Type and Pricing I. The proposed contract is for a fixed price. 2. The Consortium will not consider time and materials pricing. The vendor shall provide firm and fixed pricing based on the functionality described. For each item, indicate if the cost is one-time, annual, or other. 3. The vendor shall provide price information for each separate component of the proposed solution, as well as the costs of any modifications necessary to fully comply with the R.F.P. specifications. 4. In the event the product or service is provided at no additional cost, the item should be noted as "no charge" or wording to that effect. 5. In the event the product or service is not being included in the vendor's proposal, the item should be noted as "not included" 6. Vendors shall provide all pricing alternatives in their cost sheets, including hourly rates for additional support, training, and API development. 7. Vendors shall describe how Change Orders will be priced and managed. 8. Vendors shall provide prices in U.S. dollars. 9. Vendors shall make clear the rationale and basis of calculation for all fees. 10. Vendors shall show separate subtotals for the required elements of the proposed solution and for any layers of optional elements. Hexagon Response: Hexagon acknowledges these requirements and has abided by them in the calculation and presentation of pricing as shown in Section 6 - Proposal Pricing. Scope management is addressed via formal Change Request Orders. Requested tasks that fall outside of the negotiated contract as detailed in the SOW 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 The performed and an estimate of the level of effort and additional costs. I he Project Manager may Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 40 � A HEXAGON approve and authorize the work to be performed subject to mutual execution of a change order by the The and Hexagon. I he SOW and Project Schedule are then adjusted accordingly. 0. Software License Costs Software license costs will include all costs related to licensing the software application and include third party software license fees where applicable. In presenting software license fees, the vendor shall: 1. Explain all factors that could affect licensing fees. 2. Make clear what type of license is offered for each price (named user, concurrent user, installed copies, processor -based, etc.). 3. Indicate which product versions, operating platform(s), are included for each price. 4. Indicate whether a product is for "server" or "client, "as applicable. 5. Make clear the extent of any implementation services that are included in the license fees (installation, configuration, training, etc.). To the extent possible, the vendor shall show any applicable discounts separately from the prices for products and services. The Consortium requests that the vendor provide separate prices for each functional area/module in the proposed solution. In addition, the Consortium expects software maintenance costs will not increase in the first five (5) years upon live operation. Hexagon Response: Hexagon acknowledges these requirements and has abided by them in the calculation and presentation of pricing as shown in Section 6 - Proposal Pricing. P. Implementation Service frosts Implementation service costs include all costs related to implementation, configuration, data conversion, customization, and training. Typically, implementation service costs are provided as "not to exceed" estimates, and the Consortium will be charged for services as incurred. The Consortium will provide payments associated with software license fees and implementation on a milestone basis; for instance, Project Kick -Off and Project P/an Approval, Interface Development Completion, and Acceptance. Please note the following: 1. The Consortium will not consider time and materials pricing. Vendors shall provide firm and fixed pricing based on the functionality described. For each item, indicate if the cost is one-time, annual, or other. 2. The vendor shall provide price information, including details on the number of hours used and miscellaneous costs associated with each separate component of the proposed solution, as well as the costs of any modifications. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 41 A HEXAGON 3. In the event the product or service is provided at no additional cost, the item should be noted as "no charge." 4. In the event the product or service is not being included in the proposal, the item should be noted as "not included." 5. The vendor shall make clear the basis of calculation for all fees. All travel, printing and other expense costs must be included in the vendor's fixed price cost. The Consortium will not make a separate payment for reimbursable expenses. Per Force Majeure, the Consortium shall not be liable for additional travel costs incurred due to any reason outside Consortium's control. Hexagon Response: Hexagon acknowledges that the implementation services costs include all costs related to implementation, configuration, data conversion as described in the proposal response, integration, and training. Hexagon clarifies that the proposed solution is provided on a firm -fixed price basis. Hexagon will provide the Consortium with a payment schedule for implementation services and third -party software, on Cl oud milestone basis upon selection and contract negotiation. Implementation Environment and Managed Services Fees will be due and payable in accordance with the Master Terms erms and the cutover C Cloud Program Fees will be due on an annual basis beginning at loud Cutover. 1. Hexagon acknowledges these requirements and has abided by them in the calculation and presentation of pricing as shown in Section 6 — Proposal Pricing. 2. Hexagon takes exception to this requirement as the proposed solution is provided on a firm -fixed price basis. 3. Hexagon acknowledges these requirements and has abided by them in the calculation and presentation of pricing as shown in Section 6 — Proposal Pricing. 4. Hexagon acknowledges these requirements and has abided by them in the calculation and presentation of pricing as shown in Section 6 — Proposal Pricing. 5. Hexagon clarifies that the proposed solution is provided on a firm -fixed price basis. Q. Annual Maintenance Cost= Annual maintenance costs include the annual maintenance and support fees for the application environment. For example, the annual maintenance fees associated with a particular module will be paid upon the Consortium's acceptance of the project phase associated with that particular module. The Consortium will not pay maintenance fees on functional areas until sign -off has been provided to approve live operation for one (1) year after final System acceptance. The Consortium expects software maintenance costs will not increase in the first five (5) years upon live operation. The Consortium expects to work with the selected vendor to methodically implement the System across all Consortium entities closely. Describe the fee schedule as it relates to multi -agency staggered deployment. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 42 A HEXAGON Hexagon Response: Hexagon acknowledges these requirements and has abided by them in the calculation and presentation of pricing as shown in Section 6 — Proposal Pricing. For clarification, the majority of the solution being provided is SaaS applications, which are supported as part of the SaaS subscription. R. Source Code Selected vendors shall place source code for the software modules licensed by the Consortium in escrow with an independent third -party (with whom a separate escrow agreement will be entered into by the Consortium at no additional cost). The source code shall be kept current with the releases/version of the software in use at the Consortium agencies. The source code shall revert to the Consortium for the Consortium's use if the vendor files for bankruptcy or protection from creditors in a court of law. The Consortium shall then have full rights to use source code for any purposes other than resale. Within thirty (30) calendar days of the vendor going out of business or no longer supporting the software being licensed, the vendor shall provide appropriate source code to the Consortium. The same applies if the vendor is merged or acquired and the software is no longer supported. Once the Consortium obtains the source code, it shall be a perpetual license, and there shall not be any additional fees due, even if additional licenses are deployed. Hexagon Response: Hexagon clarifies that because the offering is a Software as a Service (as opposed to perpetual licenses), source code escrow is not appropriate and has not been proposed or included in the proposal. S. Client References & Ors -Site Visit The vendor must provide at least five (5), but not more than ten (10) references meeting the following criteria: 1. At least three (3) references should be for systems installed within the last three (3) years. Hexagon Response: DuPage County, IL; El Paso County, TX; South Sound Pierce County, WA; and NYPD 2. At least two (2) references should be for systems installed more than three (3) years ago. Hexagon Response: Each of the references below also meets this requirement. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 43 A HEXAGON 3. At /east three (3) references should inc/ude installations of similar configuration proposed for the Consortium. Hexagon Response: Hexagon has included references for clients who have implemented different combinations of CAD, mobile and RMS systems similar to the Consortium. For example, DuPage County, IL and El Paso County, TX have implemented CAD, RMS and mobile. 4. At least three (3) references should reflect similar Consortium population and call for service levels. Hexagon Response: Hexagon has included references below for DuPage County, IL and South Sound Pierce County, WA which are both large multi -agency deployments similar to the Consortium. While NYPD is not multi - agency, it's population served and call for service levels are quite large and indicate Hexagon's ability to provide effective solutions for customers who are similar in size and scope to the Consortium. The references should include, at a minimum, the following information: 1. Facility Name, Address, and Owner of Project; 2. Contact person at a facility that is familiar with the system and its operation, including their title, phone number, and email address; 3. Details of the Project type, size, and operations; 4. Initiation and Completion dates of the Project; 5. Length of contract; 6. Summary of unanticipated delays or obstacles that were encountered. Hexagon Response: Hexagon has provided these details for the references below. DuPage County, IL Address. 21 North County Farm Road, Wheaton, IL 60187 Contact. Linda Zerwin, Executive Director I linda.zerwin�dupageco.org phone - 630-550-7743 Details of the Project type, size, and operations: DuPage County is the largest consolidated 9-1-1 center in the state of Illinois. Du -Comm provides public safety communication services for Police, Fire, and EMS serving 44 agencies within the County with a population of nearly 950,000. DuPage County Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 44 � A HEXAGON utilizes Hexagon's full product suite- CAD, RMS, and Mobile. Project details include implementing CAD/RMS/Mobile, project management, installation, system administrator training, and train the trainer. n itiati On and Completion dates of the Project: Initial contract June 2016, cutover June 2018. Length Of contract: 5 years Summary of unanticipated delays or obstacles that were encountered: Du Page County consolidated its 22 PSAPs into 3 PSAPs during this project which required alignment and reevaluating best business practices. South Sound Pierce County, WA Address: 955 Tacoma Avenue South- Suite 102, Tacoma, WA 98402 Contact: Tim Hannah, Assistant Director of Technical Services phone - 253-798-6213 Details of the Project type, size, and operations: South Sound 9-1-1 in Pierce County, Washington, consists of 19 Police and 19 Fire/EMS agencies between their two centers with a population of nearly 904,000. Project details include implementing CAD and Mobile, project management, installation, system administrator training, and train the trainer. Ivitiation and Completion dates Of the Project: Upgrade contract signed August 2018, completed December 2020. Length of contract: 7 years Summary of unanticipated delays or Obstacles that were encountered. This project was implemented in a multi -phased approach at the customers request because it involved multiple agencies. South Sound formed committees with its decision -makers to ensure a successful transition to a new system. Obstacles included product adoption for communications staff and field units getting used to a new system, introducing 3rd party product integration with technology that was new to South Sound and Hexagon, change management within the customer sites and Hexagon, as well as a creative approach for the customer to train over 2000 users over the course of several months in preparation for go -live. Additionally, there were hardware replacement delays at the agency that resulted in a longer implementation timeline than originally scoped. Fairfax County, VA Address: 4890 Alliance Drive #1109, Fairfax, VA 22030 Contact: Jon Ronan, CAD Administrator I jon.ronan@fairfaxcounty.gov phone - 571-350-1730 Details of the Project type, size, and operations: Fairfax County is a nationally recognized public safety communications center and is one of the ten largest centers in the US. They are also the largest center in Virginia, serving a population of over 1.1 million. Fairfax County is in the process of upgrading its Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 45 A HEXAGON Hexagon CAD to our latest I/CAD product version. Project details include upgrading CAD and Mobile, project management, installation, system administrator training, and train the trainer. Initiation and Completion dates Of the Project: Upgrade contract signed April 2019 and is scheduled to go live October 2021. Length of contract: 14 years Summary of unanticipated delays or obstacles that were encountered: Upgrade to Hexagon CAD V9.4 currently in progress. Fairfax County has requested to delay implementation from August to October 2021 due to their desire to continue testing in their test environment per agency protocol. There were hardware and third party application issues that caused project delays in the testing phase. Ei Paso County, TX Address: 6055 Threadgill Avenue, EI Paso, TX 79924 - 915-832-6810 Details of the Project type, size, and operations: El Paso County, Texas consists of 39 total agencies benefiting from Hexagon technologies. 24 Law Enforcement, 10 Fire and 4 EMS agencies, in addition to El Paso County 9-1-1. El Paso County serves a population of 963,000 residents. Utilizing Hexagon's full product suite- CAD, RMS, and Mobile, project details include implementing CAD/RMS/Mobile, project management, installation, system administrator training, and train the trainer. Initiation and Completion dates Of the Project: CAD upgrade contract signed December 2018, and cutover in November 2019. RMS migration signed June 2015, completed November 2020. Length of contract: 13 years Summary of unanticipated delays or Obstacles that were encountered: Having an assigned Hexagon resource that worked during hours outside of El Paso County s regular workday created a few delays while working through minor issues that arose. NYPD Address: 1 Police Plaza, Rm 708, New York, NY 10038 Contact: Gina King, NYPD 911 Operations Coordinator I Gina.King@NYPD.org I Mobile — 718-696-5300 Details of the Project type, size, and Operations: NYPD uses the Hexagon Computer Aided Dispatch System. The system is configured for 400+ simultaneous call taker and dispatchers seats operating in two PSAP's ( Brooklyn, Bronx ). The centers are fully redundant and can operate independently. NYPD has an on prem installation. It handles 8.5m calls per year and 10.5m CAD incidents. Initiation and Completion dates Of the Project: The project began in 2008 and went live in 2013 with a recent upgrade completed in late 2020. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 46 � A HEXAGON Length of contract. The current contract is through 2024. Summary of unanticipated delays or obstacles that were encountered. The original project schedule was delayed as the customer added additional scope during the implementation phase. Extended integration to a new 9-1-1 telephony system and new additional interfaces to Fire and EMS agencies in the city had to be designed, developed and tested, prolonging the pre-cutover component of the project. In addition, the Consortium requests a listing of all law enforcement clients. /f possible, at /east one (1) of these references should be a vendor -hosted solution. Hexagon is unable to provide a listing of all law enforcement clients. Hexagon further clarifies/that we are unable to provide contact information for all of our clients without their express legal consent. Contact information has been provided for the selected customer references above. Hexagon is currently implementing cloud solutions for multiple customers, but we have not included one as a reference as those solutions are in -process. T. Exceptions and Deviations /f the vendor finds it impossible or impractical to adhere to any portion of these specifications and all attachments, it shall be so stated in its proposal, with all deviations grouped together in a section entitled, "exceptions/deviations from proposal requirements" and submitted with the R.F.P. Response Form. This section will be all-inclusive and will contain a definition statement of each and every objection or deviation with adherence to specific R.F.P. sections. Objections or deviations expressed only in other parts of the proposal, either directly or by implication, will not be accepted as deviations, and the vendor, in submitting a proposal, will accept this stipulation without recourse. Hexagon Response: Hexagon acknowledges this requirement and has included a section entitled Exceptions and Deviations from Proposal Requirements within Section 8 - RFP Response Form. Response to RFP 21-02 for CAD/RMS/Mobile Section 2.21: Scope of Services, pg. 47 A HEXAGON Section 3 - Submittals Vendors shall include specification sheets on all equipment proposed, as well as a solution overview document and System template/document screenshots that clearly define all of the functions of the system as they relate and adhere to the system specifications and infrastructure specifications provided within this RFP. This section shall also include the required RFP Surveys (Attachment A- System Requirements Survey). Submittals shall be in an electronically searchable format. Hexagon Response: Hexagon has included screenshots throughout the proposal response to assist in describing product functionality, features and workflows. In AppendixB, Hexagon has included product descriptions with additional information and screenshots for the OnCall products. In Appendix C, Hexagon has attached a system configuration diagram to provide an overview of the solution. Specifications for recommended client hardware are included on page 1 of the configuration diagram. Cloud Appendix F, Hexagon has included an OnCall Suite Cloud System Specifications document. Hexagon has included responses to Attachment A — System Requirements survey in an electronically searchable format as part of the digital submission. A printed copy has not been provided as the RFP instructs vendors to leave the workbook as an Excel file. Response to RFP 21-02 for CAD/RMS/Mobile Section 3: Submittals, pg. 1 A HEXAGON Section 4 — Contractual Obligations Describe current or anticipated contractual obligations that have been awarded, which may coincide with the terms of this contract. Hexagon Response: Due to the evolving nature of our bids and privacy concerns between us and our customers, as well as competition -sensitive information, Hexagon cannot provide an accurate estimation of current or anticipated Consortium that no current or potential obligations will create a conflict with any timeline agreed upon during contract negotiations and award, and will not negatively impact our implementation or execution. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Section 5 — Litigation, Claims, and Regulatory Actions Vendor must indicate if they have had any Litigation, Claims, or Regulatory Action. Vendor shall provide detailed information relating to any circumstances and status. Any omission within this item may result in disqualification from the bid process. Hexagon Response: Intergraph Corporation vs. Polish Airport Authority Case No. S.A. 116/07 Judgment awarded to Intergraph. Intergraph Corporation entered into a contract with the Polish Airports State Enterprise or Polish Airport Authority (PAA) on June 29, 2005 to provide software and services for the international airport in Warsaw, Poland. On February 12, 2007, the Company gave notice of termination of the contract based on material breach. Per the contract, the Company filed for arbitration with the Court of Arbitration at the Polish Chamber of Commerce in Warsaw. On April 7, 2009, the Arbitration Court ordered the Polish Airport Authority to pay Intergraph and also found that Intergraph was justified in terminating the contract based on non-payment by the PAA and that Intergraph does not have any continuing obligations under the contract. Eddie Singer vs. Intergraph Corporation Case No. 14 856/EBS/VRO Judgment awarded to Singer On March 12, 2007, the Company received written notice that Eddie Singer had filed a request for arbitration with the International Court of Arbitration in Paris, France. This dispute relates to the Company's January 1999 acquisition of the InTools software from Eddie Singer. Singer claims that the Company did not properly calculate the sales for "earnout" payments due to Singer. On October 14, 2009, the Company received the arbitrator's final notice in favor of Singer. Intergraph v. GeoEye Arbitration — Denver, Colorado Settled This matter arose from a 2007 contract between Intergraph and GeoEye for the development of a "GeoBrowser." Ultimately GeoEye was refusing to pay for outstanding accounts receivable, which were Response to RFP 21-02 for CAD/RMS/Mobile Section 5: Litigation, Claims, & Regulatory Actions, pg. 1 � A HEXAGON fully reserved. The parties could not resolve the issue and agreed to mediate on December 16, 2009. GeoEye agreed to pay Intergraph to resolve all claims. Intergraph Corporationl�& Cobalt BSI Holding, LLC vs. Greg Bentley, Keith Bentley, Barry Bentley, Raymond Bentley, Richard Bentley, Bentley Systems, Inc. In the Circuit Court of Madison County, Alabama CV-08-1729-JPS Settled On November 26, 2008, Intergraph and Cobalt BSI Holding, LLC ("Cobalt") filed an action in the Circuit Court of Madison County, Alabama. The action was brought against Bentley Systems Inc. (`BSI"), Greg Bentley, Keith Bentley, Barry Bentley, Raymond Bentley, and Richard Bentley (collectively, the "Bentley Brothers") and alleged that excessive compensation had been paid to the Bentley Brothers. Cobalt BSI Holding, LLC vs. Bentley Systems, Incorporated Case N. 4198 Settled The Company filed suit on November 26, 2008 against Bentley Systems, Inc. ('BSI") pursuant to Section the inspection of their records for the purpose of investigating the possible mismanagement of corporate assets. Bentley Systems, Inc., Greg Bentley, Keith Bentley, Barry Bentley, Raymond Bentley, & Richard Bentley vs. Intergraph Corporation & Cobalt BSI Holding, LLC Case No. 4294 Settled Bentley filed a Declaratory Judgment action in the Chancery Court of Delaware seeking to have the Court determine that Delaware was the proper jurisdiction for any claims which Intergraph or Cobalt had against Bentley or the Bentley Brothers. Estate of Mark Zimmer vs. Intergraph Corporation Civil Action No. 08-04321 (21) (General Civil Division) a Attorney for Plaintiff: Craig M. G Response to RFP 21-02 for CAD/RMS/Mobile Section 5: Litigation, Claims, & Regulatory Actions, pg. 2 A HEXAGON Attorney for Defendant: William M. Douberley Settled. On April 16, 2008, the Company was served with a complaint filed on behalf of the Estate of Mark Zimmer. The complaint sought damages for the wrongful death of Mark Zimmer, allegedly resulting from the delay of an ambulance dispatched by a 9-1-1 system operated by the City of Plantation, Florida. The parties mediated the matter on November 6, 2009, whereby the Plaintiff agreed to dismiss its case against Intergraph for a confidential and nominal settlement amount paid exclusively by Intergraph's general liability insurance carrier. Final Order of Dismissal was signed by Judge Murphy on April 26, 2011. Intergraph v. Bentley Systems Case No. CV-02-2850-KKH Settled On December 12, 2002, Intergraph filed an action against Bentley Systems Inc. relating to an "earn out" from the sale of a product line to Bentley. Ajudgment was entered in Intergraph's favor, and Bentley filed an appeal. The Alabama Supreme Court later reversed and remanded the case for a retrial on the merits. ASpecial Master was appointed in this case. The matter was set for final hearing in October 2008. A judgment was entered in Intergraph's favor on December 1, 2008. The case was appealed December 2, 2008, and we are awaiting a decision from the Alabama Supreme Court. Intergraph v. Matrox Graphics, et al Civil Action No. CV- 01-2186-BEW Settled The Company filed an action on October 31, 2001 to require Matrox to either defend or indemnify the Company against certain patent infringement claims made by Intel against Matrox products sold by Intergraph. The case was placed on an administrative docket for a significant period of time and in 2007, the case was placed back on the active trial docket and scheduled for trial in June 2008. The Company filed a motion for summary judgment, and the court issued a ruling in the Company's favor and set the matter for a determination of damages. Corporation Directorate of State Airports Administration v. Intergraph Corporation Ankara, Turkey 8th Commercial Court of First Instance -2005/541-2008/382 Response to RFP 21-02 for CAD/RMS/Mobile Section 5: Litigation, Claims, & Regulatory Actions, pg. 3 A HEXAGON Attorney for Defendant: Se Pending The civil court appeal process has not been successful and is in final stage for consideration. If unsuccessful, Intergraph is going to file for relief under a recent amendment to the Turkish constitution applicable to due process violations. Officially served upon decision of 15th Chamber of Court of Appeal on October 29, 2016 rejecting the re -consideration request. We file the individual application with the Constitutional Court. Judgment entered officially denying constitutional -based appeal with no further opposition before Turkish courts, researching enforceability of judgment in the US. Intergraph Corporation v. Colossus (InterAct) Before the American Arbitration Association - Case No.: 50 117 T 00253 14 February 19, 2013. InterAct com peled arbitration. InterAct filed a Cou April 19, 2014. Case relates to money due to Intergraph from InterAct. Settled July 11, 2014 County of Erie, New York v. M/A-Com, Inc., E.M. Systems, Inc., Tyco Electronics Corporation; Intergraph Corporation; and Kevin J. Comerford Civil Action Index No. 12009-012326 State of New York Supreme Court, County of Erie Ifill a n , PC Attorney for Defendant: Hagerty & Brady (Edwin P. Hunter) Settled May 23, 2014 This matter arises from a 2006 contract between Intergraph and M/A-Com, Inc. ("M/A Com") whereby M/A-Com subcontracted with Intergraph for Intergraph to provide a Computer Aided Dispatch system. The claims primarily relate to the process by which M/A-Com was awarded the contract. The stipulations of discontinuance are fully executed. They recite that as to Intergraph, the matter is discontinued on the merits, with prejudice and without costs or further recourse". This matter is fully resolved as to Intergraph and Intergraph is out of the case entirely. Intergraph Corporation v. Ashraf Taha, MDC Software Solutions LLC and Khira Abdelmoujib District Court of Harris County, Texas Cause No. 201646281 Closed/Settled on May 22, 2017 Intergraph filed a Petition, Application for Temporary Restraining Order, Temporary Injunction and Permanent Injunction, Request for Disclosure and Jury Demand against Defendants in July of 2016. Response to RFP 21-02 for CAD/RMS/Mobile Section 5: Litigation, Claims, & Regulatory Actions, pg. 4 A HEXAGON Intergraph is seeking relief due to Defendants actively misappropriating confidential, proprietary trade secret information and intellectual property. Reached settlement with Defendants; submitted settlement paperwork to Defendants' counsel in December of 2016. Xueyan Zhou a/k/a Susan Zhou v. Intergraph Corporation Case 5:17cv01033 Settled March 15, 2019 Plaintiff first initiated EEOC action based on race, sex and retaliation; withdrew same; demanded 18 months of severance; filed lawsuit on June 20, 2017. Formal complaint filed in federal court on June 20, 2017; Intergraph Corporation was served on June 26, 2017; preparing Motion/Answer to be filed by July 17, 2017; We have filed our Answer, conducted the required Rule 26 discovery conference and /� exchanged initial disclosures. We will be submitting our Rule 26 report soon, at which time the Court will enter a scheduling order. Zhou s attorney sent a subpoena foremployee records; complied with request / accordingly by submitting benefit and payroll information. The Court entered the jointly proposed scheduling order, with a discovery cut-off at the end of June, 2018. Xuemei Kang a/k/a Celia Kang v. Intergraph Corporation (Hexagon PPM) New York State; Division of Human Rights; Case No. 10191485 US Dept of Justice Charge No. 197-1-40 EEOC Charge No.: 520-2018-01057 All matters closed. The New York complaint was filed on December 8, and response was filed on December 22, 2017 (65 page submission). No reply or request for further information has been received. Filed response to US Department of Justice of Civil Rights Division in Washington DC on January 11, 2018. Interviews took place for HR employees of EcoSys and Hexagon PPM on April 11, 2018; Kang filed an EEOC charge on May 2, 2018 alleging discrimination based on sex, national origin and retaliation, The NY Division of Human Rights ruled in Intergraph's favor on Kang. She has 60 days to file suit in state court, but that deadline will be affected by her EEOC Charge as well. Intergraph Corporation v. Cloud 5 Solutions, LLC and Travis Enders Case No.: 5:18cv00828-HNJ Complaint filed: May 30, 2018 Closed Intergraph filed a complaint against Cloud 5 Solutions LLC and Travis Endersrequesting (a) the Court to Cloud a judgment for damages in excess of $75K, (b) an injunction refraining Cloud 5/Enders from Response to RFP 21-02 for CAD/RMS/Mobile Section 5: Litigation, Claims, & Regulatory Actions, pg. 5 A HEXAGON copying, distributing, viewing, using, publicly displaying, and/or creating derivative works from Intergraph's software applications, (c) an injunction refraining the facilitation of the downloading of any Intergraph software, (d) an injunction refraining the decompiling or disassembling of Intergraph software, (e) an injunction refraining from engagement of unfair competition , and (f) an injunction refraining Defendants from performing professional services related to Intergraph software. Intergraph is currently attempting service of the Defendants. The Consent Judgment was entered on September 25, 2018, the lawsuit was concluded. In addition to the permanent injunction against Cloud 5 and Enders, Cloud 5 was required to pay Intergraph Corp. $20,000.00 by October 11, 2018. Wendy Downing v. Intergraph Corporation (PPM) EEOC Charge No. 420-2018-03498 Plaintiff filed an EEOC charge of discrimination on December 9, 2018 alleging discrimination based on age and disability. Hexagon responded denying all claims with a position statement on March 7, 2019. She got her right to sue in mid -July, 2019. She had 90 days within which to file a lawsuit. Case closed. Government County Metro Government v. Intergraph Corporation Jefferson County Circuit Court, Case No. 19 CI 05726 removed to U.S. District Court for the Western District of Kentucky, 3:19 CV-746-DJH Plaintiff filed a complaint against defendant on September 18, 2019 alleging defendant breached its contract with plaintiff regarding implementation of a records management solution. Defendant removed The matter to federal court. I he matter was settled. Intergraph Corporation v. Rolta In the Circuit Court for Madison County, Alabama Case No. 47-CV-2019-900636 Intergraph (PPM Division) filed a complaint against Rolta India and Rolta International on April 1, 2019, claiming it suffered damages as a direct and proximate result of Rolta India's breach of their Distributor Agreement and a Memorandum of Understanding. Rolta has not responded to the complaint. Intergraph filed a Motion for Summary Judgment and a Motion to Deem the disputed Requests for Admissions The Intergraph won on breach of contract and amounts due claims. I he fraud claim remains to be determined. On 02/09/2021, Rolta International (Rolta ) filed a motion for reconsideration of order dismissing its The Chapter 11 proceedings. I he court scheduled the matter for hearing on 02/23/2021. However, the court issued an order on 02/17/2021 denying Rolta s motion for reconsideration. PPM has not yet received a copy of the order. In any event, this pending litigation in Circuit Court may proceed as against Rolta. Response to RFP 21-02 for CAD/RMS/Mobile Section 5: Litigation, Claims, & Regulatory Actions, pg. 6 A HEXAGON Rolta v. Intergraph Corporation In the Circuit Court for Madison County, Alabama Case No. 47-CV-2019-900943 Plaintiff: Roita India Limited Roita action against GSP for illegal termination of the Limited Distribution Agreement. On August 28, 2019 we filed an answer to Rolta's compliant in the case. On January 8, 2020, outside counsel prepared a motion to dismiss the GSP case since Roita cannot proceed without counsel. Outside counsel submitted RFAs on February 26. Opposing counsel subsequently filed a motion to continue. Zachry Holdings, Inc. v. Intergraph Corporation In the Supreme Court of the State of New York; County of New York Case No. 653703/2020 Plaintiff: Zachry Holdings, Inc. �I Defendant: Intergraph Corporation dba Hexagon PPM Date: August 12, 2020 Zachry Holdings filed suit against Intergraph arising from the dispute over non-payment of the software This was the subject a lawsuit Intergraph filed against Zachry in Alabama. I his lawsuit has been filed in the same court where Intergraph filed their New York action. Zachry is alleging breach of contract and fraud. Closed: The parties entered a settlement agreement on 12/07/2020 whereby, among other things, Zachry will pay PPM $600,000 in two equal installments: one payment of $300,000 within 3 business days of signing (paid and received) and a second payment of $300,000 due on or before 03/31/2021. Intergraph Corporation v. Zachry Holdings, Inc. In the Supreme Court of the State of New York; County of New York Plaintiff: Intergraph Corporation dba Hexagon PPM Date: August 14, 2020 Intergraph Corporation filed suit against Zachry for breach of contract, account stated, unjust enrichment, and quantum meruit. Closed: The parties entered a settlement agreement on 12/07/2020 whereby, among other things, Zachry will pay PPM $600,000 in two equal installments: one payment of $300,000 within 3 business days of signing (paid and received) and a second payment of $300,000 due on or before 03/31/2021. Response to RFP 21-02 for CAD/RMS/Mobile Section 5: Litigation, Claims, & Regulatory Actions, pg. 7 A HEXAGON Intergraph Corporation v. Zeteky, Inc. formerly CloseWatch Technologies, Inc. In the Circuit Court of Madison County, Alabama Case No. CV-2020-900548 Intergraph Corporation dba Hexagon Geospatial provided services for Zeteky / Closewatch, including the design of a new dashboard and platform for Zeteky's anonymous reporting services ("Services"). For the Services, Zeteky agreed to pay the amount of $1,967,000.�1From April 18, 2018 up to January 17, 2019, Zeteky has not complied with the foregoing obligation. Hexagon Geospatial sued Zeteky for breach of contract and unjust enrichment on April 20, 2020. Motion to Dismiss filed by Zeteky and set for hearing on September 11, 2020. This motion was denied. Intergraph Corporation, et al. v. Geomni, Inc., et al. In the Circuit Court of Madison County, Alabama Case No. CV-2021-000021 Leica Geosystems Inc., Leica Geosystems AG and Intergraph Corporation filed a complaint against Geomni Inc., GV Air, Inc., Verisk Analytics, Inc., Vexcel Imaging US, Inc., Vexcel Holdings, Inc. and Vexcel Group, Inc. on April 2, 2021. Defendants owe Leica and Intergraph for past due lease paym in addition to the payments during the remaining term of a lease agreement. Response to RFP 21-02 for CAD/RMS/Mobile Section 5: Litigation, Claims, & Regulatory Actions, pg. 8 Section 6 — Proposal Pricing Below is Hexagon's proposed pricing in response to Pinellas County Sheriff's Office request for implementation and five-year Cloud subscription. Response to RFP 21-02 for CAD/RMS/Mobile Pricing Assumptions: • The Azure environment sized for the Pinellas consortium includes 4 environments and shared components across all of a customer's environments: Shared Environment resources — used throughout the OnCall environment includes: Customer storage — 1 TB hot block blob storage AKS Control Plane — 2 Linux nodes Message Bus — 3 Linux nodes 8 core 2 VPN Gateways HA ESRI deployment Dev/Stage Environment— Dev is used most often at the beginning of the project phase and then use intermittently throughout the lifecycle of the solution. Whereas Staging is only used when there is an upgrade. Dev/Stage includes: 1 TB storage RA-GRS ore 9 Linux nodes mix of 8 core and 4 core Training Environment — sized to support a large concurrent set of users 2 16 core General Purpose sku databases with 1 TB storage RA-GRS 9 Linux nodes mix of8 core and 4 core Production (1) — includes: 2 16 core Business Critical sku databases with 1 TB storage Z-RS 16 Windows nodes mix of 8 core and 4 core 9 Linux nodes mix of8 core and 4 core 10 TB egress data (monthly) 10 TB innra-regional (monthly) Response to RFP 21-02 for CAD/RMS/Mobile Production (2) — includes: 2 16 core Business Critical sku databases with 1 TB storage Z-RS 16 Windows nodes mix of 8 core and 4 core 9 Linux nodes mix of 8 core and 4 core 10 TB egress data (monthly) 10 TB intra-regional (monthly) • Any commercial -off -the -shelf (COTS) product information provided by Hexagon in this document is intended 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. Except as set forth in a • resulting contract, Hexagon does not commit to develop the future features, functions, and products discussed in this material. Pinellas County 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 unless specified in the resulting contract. Fees from the commencement of the Cloud Term up to 24 months thereafter. If for any reason the Customer has not cutover at its first PSAP site by the second anniversary of the commencement of the Cloud Term, then the Customer is required to pay for additional Implementation Cloud Environment and Managed Services Fee beyond the initial 24-month period. The additional Implementation Cloud Environment and Managed Services Fee will be due and payable in accordance with the Master Terms. • Implementation services costs include project implementation, change management, configuration, integration/interfaces, customization, third parties, travel, and training (Train -The - Trainer and HxGN E-Learning/Dynamo named -user licenses at a quantity of 4000). • The Dynamo Curriculum/E-Learning Licenses included in this pricing are for a 24-month duration to begin once the first training licenses are provided as set forth in the statement of work. • Third parties and interfaces included in the one-time project fee include support/maintenance, some start at cutover and others upon shipment. All have been included in the pricing appropriately. • Pinellas County is responsible for the connection between the cloud environment and the on - premise server. • Largo Police Department RMS data conversion, provided by Whitebox, assumes conversion of 35 source data tables. • Largo Police Department CAD historical data conversion, provided in this proposal, includes up to 3 years of historical CAD data. • If Pinellas County requires a change order during this process, please reference "Section 2.21 — Scope of Services" for how Hexagon manages change orders. • The Cloud Program Fees are subject to capacity limitations as provided in the Cloud Service Schedules to be provided with the resulting contract. • Hexagon has included CAD system builds as part of the project, during which certain system configuration will be done. Hexagon assumes the Consortium prefers to have system management for whole system rather than to have each PSAP perform its own system management. Hexagon has optioned two additional system builds in the event the Consortium prefers for each PSAP to have separate management rather than to consolidate. • Hexagon's Enterprise/Site License is licensed by defined agencies, products, and size of the cloud environment. Our Hexagon Enterprise/Site License does not have user counts restrictions for Hexagon's products. The cloud environment is sized based on the number of Response to RFP 21-02 for CAD/RMS/Mobile users described in the RFP. However, as provided in the Cloud Schedules within the resulting Cl oud there are certain parameters on the applications, such as database size, transactions, and processing capabilities. If more cloud capacity is required or consumed, the Consortium would purchase the additional capacities. • The Hexagon Enterprise/Site License is licensed to, and only to, the following agencies. Pinellas County Sheriffs Office Secondary PSAP shores St. Petersburg Police Department Secondary PSAP Clearwater Police Department Secondary PSAP Largo Police Department Secondary PSAP Pinellas /Park Police Department Secondary PSAP Pinellas bounty Regional 9-1-1 Communications Center Primary PSAP* *Hexagon Enterprise/Site License includes the annual usage of OnCall for the R911 Primary PSAP for the Fire/EMS functionality requested in Addendum 1 for this RFP. Additional items related to that addendum will be forthcoming as part of Hexagon's Fire/EMS proposal response. • This offer is valid for 120 days from date of submission. • TT he pricing in the above tables is exclusive of any applicable sales/use tax. Any applicable tax will be added to the pricing above at time of invoicing. • Hexagon welcomes and reserves discussion of proposed milestones/fee schedule as part of the contract negotiations and finalization of the resulting scope of the implementation and deployment phase. Response to RFP 21-02 for CAD/RMS/Mobile Bill of Materials Hexagon Enterpri s e/Site License CADSoftware Version HxGN OnCall Dispatch - Advantage CC - Subscription Client 10.00.2107 HxGN OnCall Dispatch - Advantage CC - Subscription - TRN Client 10.00.2107 HxGN OnCall Dispatch - Resource Management - Subscription Client 10.00.2107 HxGN OnCall Dispatch - Advanced Mapping - Subscription Client 10.00.2107 HxGN OnCall Dispatch - Viewer CC - Subscription Client 10.00.2107 HxGN OnCall Dispatch - Tracker CC - Subscription Client 10.00.2107 HxGN OnCall Dispatch - Customer Rules Engine Editor - SU Server 03.05.2106 HxGN OnCall Dispatch - Customer Rules Engine Client - SU Client 03.05.2106 HxGN OnCall Dispatch - Customer Rules Engine Server - SU Server 03.05.2106 HxGN OnCall Dispatch - RestAPI NL - Subscription Server 10.00.2107 HxGN OnCall Dispatch - Informer - Subscription Server 10.00.2107 HxGN OnCall Dispatch - PTT - Subscription Server 10.00.2107 HxGN OnCall Dispatch - Fire Link Interface - Subscription Server 10.00.2107 HxGN OnCall Dispatch - CAD Link Interface - Subscription Server 10.00.2107 HxGN OnCall Dispatch - Call -Taker Interface - SU Server 10.00.2006 HxGN OnCall Dispatch - ALPR Interface - Subscription Client NA External Alarms On/Call Dispatch Interface - SU Server 10.00.2009 Dispatch Alerts OnCall Interface - SU Server 10.00.2009 CAD to CAD OnCall Dispatch Interface - SU Server 10.00.2009 PLT Radio OnCall Dispatch Interface - SU Server 10.00.2009 RapidSOS OnCall Call -Taker Interface - SU Server 10.00.2012 HxGN OnCall Dispatch - Deccan LiveMUM Interface - SU Server 10.00.2107 HxGN OnCall Integration Engine Server 10.00.2104 Xalt - Integration Runtime Engine NL - Subscription Server 8.1.254.1 Xalt - Integration Runtime Engine NL - Subscription - BCK Server 8.1.254.1 Xalt - Integration Runtime Engine NL - Subscription - TST Server 8.1.254.1 Xalt - Integration Runtime Engine NL - SU - Training License Server 8.1.254.1 HxGN OnCall Dispatch - ProQA Interface - Subscription Client 10.00.2107 HxGN OnCall Dispatch - ProQA Interface - Subscription-BCK Client 10.00.2107 HxGN OnCall Dispatch - ProQA Interface - Subscription - TRN Client 10.00.2107 HxGN OnCall Dispatch - ProQA Interface - Subscription - TST Client 10.00.2107 Mobibe Software HxGN OnCall Dispatch Mobile Unit Subscription Client 10.00.2107 HxGN OnCall Dispatch Mobile Unit Subscription - TRN Client 10.00.2107 HxGN OnCall Dispatch Mobile Responder Ciient CC -SU Client 04.00.2105 RMS Software HxGN OnCall Records - Server License - Subscription Server 3.07.2106 HxGN OnCall Records - Server CC License - SU - Training Server 3.07.2106 HxGN OnCall Records - Concurrent User License - Subscription Client 3.07.2106 HxGN OnCaii Records - Concurrent User License - SU - Training Client 3.07.2106 HxGN OnCall Records - NIBRS - Federal - Subscription Server 2.03.2107 HxGN OnCall Records - NIBRS - FL - SU Server 2.03.2106 Response to RFP 21-02 for CAD/RMS/Mobile Analytics Software Hx GN OnCall Analytics - Viewer - Subscription Client 2.00.2103 HXGN OnCall Analytics - Author - Subscription Client 2.00.2103 HXGN OnCall Analytics - Dispatch Data Models & Reports - Subscription Server 2.00.2103 HXGN OnCall Analytics - Records Data Models & Reports - Subscription Server 2.00.2103 Non-Enterprise/Site License Custom Interfaces CAD interface for Text-to-911 (VESTA NG911) Server CAD Interface for ALPR Client CADInformer Query to LinX Server CADInformer Query to Pinellas County Criminal Justice System (CJS) Server CADInformer Query to Pinellas County Sheriff Office Arrest Booking/Jail (JMS) Server CADInformer Query to Odyssey Server RMSInterface to AADM (in-house citation application) Server RMSInterface to VIPAR Server RMSInterface to GTL - Offender Management System (OMS) Server RMSInterface for NIBRS Server RMS Informer Transactions (NCIC/FCIC, DAVID/FDLE, ELVIS, Pinellas CJS, Pinellas JMS, Odyssey)) Server RMSInterface to Mugshots Server RMSInterface to Coplogic Server Third Party Products Cievest Enterprise Mobility Platform Platinum Server Trancite/Easy Street Draw Client CommSys Connect CIC & ASAP Consulting Server Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Section 7 — Financial Statements Provide audited financial statements for the most recent two (2) year period. /f the vendor is a wholly -owned subsidiary of another company or corporation and does not possess audited financial statements, unaudited financial statements for the subsidiary fora two (2) year period must be submitted as supplemental information to the company's financial statements in order to meet this requirement. These documents should be affixed to the `original" bound proposal only, submitted by the vendor. Hexagon Response: Hexagon has sound financial footing, solid growth, and ongoing � profitability. Hexagon is a privately held T company and does not release its financial audit records. The Consortium will find two years of financial data in the financial reports linked below. These reports include audited financial statements for Hexagon's parent company, Hexagon AB, a publicly traded corporation on the NASDAQ Stockholm exchange. • 2019 Annual Report: https://vp20p0.alertir.com/afw/files/press/hexagon/202004021243-1.pdf • 2020 Annual Report: https://vp200.alertir.co m/afw/files/press/h exa g on/202103311974-1. pat Hexagon acknowledges the requirement to include hardcopies off these reports in the signed original copy of the proposal. Hexagon has included hardcopies in Appendix G of the signed original copy of the proposal. Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Section 8 — RFP Response Form To include all Remarks and Exceptions to Proposal (Section D). Exceptions and Deviations from the Proposal Hexagon Response: Hexagon provides the below exceptions and clarifications related to the following documents: • "RFP 21-02 for Computer Aided Dispatch & Records Management System & Mobile Data Terminal" "RFP 21-02 - Attachment A— System Requirements Survey" 1.08 Contract (PDF pg. 5) Hexagon proposes the resulting Agreement be based upon the terms and conditions set forth at https://www. hexa go n s afetyinfra structure .co m/-/media/Legal/He xa got/SI/Sales/MT/US-MT06-2021. pdf ("Master Terms"), which are incorporated as if fully set forth herein, in lieu of the County's contract or other terms set forth in the RFP. The Master Terms provide a comprehensive set of terms and conditions tailored to the implementation services, SaaS terms, licensing, maintenance services, and software being provided. Without waiver of its statements above, Hexagon has provided certain comments in response to particular provisions set forth in the RFP. 1.16 Option to Renew (PDF pg. 7) Hexagon proposes that at the end of the term, the parties enter into an amendment or other new terms given changing technology, including the provisioning of SaaS platforms. Hexagon takes exception to automatic renewals contemplated beyond the initial 7 year term (it includes the duration of the project and Cl oud years of subscription from first cutover). 1.18 Termination for Default (PDF pg. 7) Hexagon proposes it have the reciprocal right to terminate in the event the County has defaulted upon its obligations. Hexagon also proposes that neither party may terminate without providing the other party written notice and an opportunity to cure of not less than thirty days. 1.20 Performance Guaranty (PDF pg. 7) Hex/argon proposes the requested performance bond be only for the implementation prices and exclude the Cloud subscription commencing upon Cutover. Theperformance bond would be released and / surrendered upon cutover of the first agency within the County. Response to RFP 21-02 for CAD/RMS/Mobile Section 8: RFP Response Form, pg. 1 iff A HEXAGON 1.23 Contractor's Personnel Standards (PDF pg. 8) Hexagon proposes that for those employees that work remotely that they have a fingerprint card completed by their respective local law enforcement organization and provide the completed card to the County for investigation. 1.30 Indemnification, Patents & Copyrights (PDF pg. 11) Hexagon proposes to indemnify the County in accordance with the Master Terms, which generally provides that Hexagon will indemnify the County for third party claims for bodily injury, death, and property damage arising from Hexagon's negligent acts and omissions. 2.5 Performance & Reliability (PDF pg. 20) Hexagon proposes to provide 99.95% uptime availability. 2.9 Software License Agreement (PDF pg. 21) Hexagon has proposed an enterprise license for the Cloud subscription/�applications, which will be subject to certain restrictions and limitations as to be set forth in the Cloud Schedules (which will be part of the resulting agreement), such as database size, processor sizing, data ingress and egress, processing consumption, etc. The site license is limited to use of the agencies expressly identified in the resulting Agreement, which will exclude the State of Florida, and agencies thereof, and the United States, and the agencies thereof. 2.21 (D) Quality Assurance & Testing Plan (PDF pg. 36) Hexagon clarifies its projects contemplate advancing from testing phase once Level 1 and Level 2 Errors are resolved and that Cutover will occur even if there are lesser Errors. Hexagon takes exception to resolving all deficiencies as described based upon the premise above. 2.21 (M) Third -Party Products (PDF pg. 39) Hexagon clarifies that because the offering is a Software as a Service (as opposed to perpetual licenses), source code escrow is not appropriate and has not been proposed or included in the proposal. 2.21 (P) Implementation Service Costs (PDF pg. 40) Hexagon clarifies it does not disaggregate or break out hours as requested when the project is a fixed price project. 2.21 (Q) Annual Maintenance Costs (PDF pg. 41) Hexagon takes exception to this provision as written. Hexagon provides Cloud Support during the Cloud Cl oud (both prior to and after cutover). With the solution being proposed, the Cloud Fees for the Cloud Program (prior to cutover) will become due once Hexagon creates the Cloud Environment and provides the County the License Keys, which will be used during implementation (assuming implementation is less than 24 months). Upon cutover of the first PSAP, the first year of the post cutover Cloud Term would commence and continue/(subjectto payment and renewal) for the ensuing five years. The Cloud Fees include the right to use the Cloud Applications as well as Cloud Support. Those rights Cloud provided at the commencement of the Cloud Term. Response to RFP 21-02 for CAD/RMS/Mobile Section 8: RFP Response Form, pg. 2 A HEXAGON 2.21 (R) Source Code (PDF pg. 41) Hexagon has proposed a SaaS solution and not software licensed on a perpetual basis. With it being provided on a SaaS basis source code escrow is not appropriate. As such Hexagon proposes this provision be omitted from the resulting contract. 2.21 (T) Exceptions and Deviations (PDF pg. 42) Any other deviations or counterproposals set forth in Hexagon's proposal that are set forth in the corresponding section are incorporated into this section as if fully set forth herein. For clarity, Hexagon proposes to provide the software and services described in its proposal notwithstanding anything to the contrary. RFP Section C (PDF pg. 46) I (A) agrees to provide certificates of insurance, however, it takes exception to being required to provide copies of its insurance policies. I (B) Hexagon proposes to provide notice upon termination in lieu of insurance providers providing advance notice of premature termination. Hexagon clarifies that it can only provide the COI with endorsements, which are triggered by a contractual requirement, once the contract between the County and Hexagon is executed. Section 7. Hexagon has provided the annual report ofpHexagon AB, which is a publicly traded company. Intergraph Corporation is a subsidiary of Hexagon AB, and it has been in business since 1969. It contracts with hundreds of customers and owns dozens of subsidiaries itself located throughout the world. The information pertaining to Intergraph Corporation constitutes material nonpublic information as provided under the Securities Act of 1934. Disclosure of the information is likely to be a violation of securities laws since that information is not made publicly available (See SEC Rule 10b-5). If there are specific questions that do not pose a risk to Hexagon violating applicable securities laws, we would endeavor to address those particular questions. Response to RFP 21-02 for CAD/RMS/Mobile Section 8: RFP Response Form, pg. 3 A HEXAGON Hexagon has completed the Section D — RFP Response Form as requested. [Attachment A begins on the following page Response to RFP 21-02 for CAD/RMS/Mobile Section 8: RFP Response Form, pg. 4 / HEXAGON Section 9 — Federal Debarred List Certification Certification Regarding Debarment, Suspension, Proposed Debarment, and Other Responsibility Matters (Section E). Hexagon Response: Hexagon has completed the Section E — Federal Debarred List Certification form. [Attachment B begins on the following page] Response to RFP 21-02 for CAD/RMS/Mobile A HEXAGON Safety, Infrastructure & Geospatial Division (SIG) 305 Intergraph Way 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: Tiffany Taylor; Blair Jacks; Richard Morris; and Amy Kelly. I further authorize the following additional persons to execute non -disclosure agreements, data processing 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; William (Bill) Starnes; Christopher Tompkins; Pat Thompson; Victor Vasile; Daniel Roach; Walter Kelley; and Rachel Fewell. This authorization shall be effective from January 1, 2023 through December 31, 2023, 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. Steven Cost President SIG, Hexagon NTERGRAPH 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 Asset Lifecycle Intelligence ("ALII") Global l& 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 Reti rement Comm itte: 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 Retirement Committe" (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, 2021 (the "Annual Status Report"). 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 Lee Christoff Penny Simpson BE IT FURTHER RESOLVED, that the individuals committee shall be indemnified to the extent serving on the 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 Di rectors/Officers: WHEREAS, Mladen Stoj is has been removed as an officer as of the date of this resolution because the formally known division known as SIG; WHEREAS, Ola Rollen has resigned resolution; WHEREAS, Mattias Stenberg is being as of the date of this resolution, GSPdivision has merged into the as Director as of the date of this elected as Director to be effective 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 President, President of SIG Executive Vice President, President of ALI Executive Vice President, Treasurer, Operating Officer of ALI Chief Financial Officer of SIG Vice President, Secretary, General Counsel Assistant Secretary Assistant Secretary Empowered Export Official Mattias Stenberg M. Scott Moore Richard B. Jacks Anthony P. Zana Richard L. Morris Stephany L. Steinfath Kristen Sims -2- Executive Officer, Chief Annual Ratification. 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 ncorporation, 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 [Signature Page to Unanimous VV ritten Consent.] Executed as of the st day of May, 2022. ,-DocuSigned by: "- F344AE05000044 Steven L. Cost ,-DocuSigned by: 2CF2B894233146E... Mattias Stenberg (CONSTITUTING ALL OF THE BOARD OF DIRECTORS OF THE CORPORATION) -4 Exhibit "A" Pages removed for Confidential Purposes 5 Exhibit "B" Pages removed for Confidential Purposes 6 s .r g DI\ Detail by Entity Name Foreign Profit Corporation INTERGRAPH CORPORATION -CAD SYSTEMS Cross Reference Name INTERGRAPH CORPORATION Filing Information Document Number FEI/EIN Number Date Filed State Statu s Last Event Event Date Filed Event Effective Date Principal Address P05699 63-0573222 04/17/1985 DE ACTIVE CORPORATE MERGER 12/30/1994 NONE 305 INTERGRAPH WAY MADISON, AL 35758-7567 Cha nged: 04/22/2015 Mailing Address 305 INTERGRAPH WAY 1 NORTH - TAX MADISON, AL 35758-7567 Cha nged: 04/22/2015 Registered 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 Title President, CEO, Director COST, STEVEN 305 INTERGRAPH WAY MADISON, AL 35758-7567 Title S ZANA, ANTHONY P 305 INTERGRAPH WAY MADISON, AL 35758-7567 Title As Secretary STEINFATH, STEPHANY 305 INTERGRAPH WAY MADISON, AL 35758-7567 Annual Reports Report Year Filed Date 2020 04/27/2020 2021 03/29/2021 2022 07/14/2022 Document Images 07/14/2022 -- ANNUAL REPORT 03/29/2021 -- ANNUAL REPORT 04/27/2020 -- ANNUAL REPORT 03/28/2019 -- ANNUAL REPORT 04/03/2018 -- ANNUAL REPORT 03/28/2017 -- ANNUAL REPORT 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 format 03/31/2016 -- ANNUAL REPORT 04/22/2015 -- ANNUAL REPORT 03/03/2014 -- ANNUAL REPORT 03/25/2013 -- ANNUAL REPORT 04/20/2012 -- ANNUAL REPORT 04/19/2011 -- ANNUAL REPORT 03/29/2010 -- ANNUAL REPORT 04/15/2009 -- ANNUAL REPORT 04/09/2008 -- ANNUAL REPORT 04/19/2007 -- ANNUAL REPORT 05/01/2006 -- ANNUAL REPORT 05/02/2005 -- ANNUAL REPORT 03/22/2004 -- ANNUAL REPORT 04/07/2003 -- ANNUAL REPORT 04/24/2002 -- ANNUAL REPORT 03/08/2001 -- ANNUAL REPORT 05/02/2000 -- ANNUAL REPORT 04/21/1999 -- ANNUAL REPORT 04/15/1998 -- ANNUAL REPORT 04/30/1997 -- ANNUAL REPORT 05/01/1996 -- ANNUAL REPORT 04/11/1995 -- ANNUAL REPORT 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 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 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 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 format View image in PDF format 1 Previous on List Next on List Return to List Filing History DIVISION OF CORPORATIONS Submit rc h Fictitious Name Detail Fictitious Name HEXAGON SAFETY & INFRASTRUCTURE Filing Information Registration Number G15000073643 Stmt.. F,�ed Date EXpirat,on Current Owners County Total Pages Events Feed Date FEI/EIN Number Mailing Address ACTIVE 07/15/2015 12/31/2025 1 LEON 2 1 63-0573222 305 INTERGRAPH WAY MADISON, AL 35758 Owner Information INTERGRAPH CORPORATION 305 INTERGRAPH WAY MADISON, AL 35758 FEI/EIN Number: 63-0573222 Document Number: P05699 Document Images 07/15/2015 -- Fictitious Name Filing 10/01/2020 -- Fictitious Name Renewal Filing View image in PDF format 1 View image in PDF format Previous on List Next on List Return to List Filing History Fictitious Name Search Submit