HomeMy WebLinkAboutExhibitOIij of 41tTiami
ANNIE PEREZ, CPPO Arthur Noriega V
SUPPLEMENTAL AGREEMENT
BETWEEN
CITY OF MIAMI
AND
INTERGRAPH CORPORATION D/B/A HEXAGON SAFETY, INFRASTRUCTURE &
GEOSPATIAL DIVISION
This Supplemental Agreement is entered into this
day of , 2022,
by and between the City of Miami ("City"), a municipal corporation of the State of Florida, whose
address is 444 S.W. 2"d Avenue, Miami, Florida 33130, and Intergraph Corporation -CAD Systems
d/b/a Hexagon Safety, Infrastructure & Geospatial Division, a Delaware foreign profit corporation,
qualified to do business in the State of Florida, whose principal address is 305 Intergraph Way,
Madison, Alabama 35758("Hexagon").
RECITALS:
WHEREAS, pursuant to Section 18-111 of the City of Miami Code of Ordinances ("City
Code"), in lieu of the City's usual competitive bidding procedures, the City may access a contract
secured by or on behalf of any federal, state, county, or municipal government provided the
contract was entered into through a competitive process; and
WHEREAS, Pinellas County Sheriff's Office awarded a contract titled "Primary Contracting
Document" to Hexagon pursuant to Request for Proposals ("RFP") No. 21-02 for Computer Aided
Dispatch & Mobile Date Terminal, which was executed on July 22, 2022 (the "Contract"); and
WHEREAS, Hexagon has agreed to extend its services to the City subject to the same
terms and conditions in the Contract, except to the extent those terms are amended herein, and
WHEREAS, the City and Hexagon wish to proceed with the procurement of a computer
aided dispatch system subject to the terms and conditions in the Contract, except as modified
herein.
NOWTHEREFORE, for good and valuable consideration, the sufficiency of which is
hereby acknowledged by the parties, Hexagon and the City agree as follows.
1
TERMS:
1. RECITALS, INCORPORATIONS, AND PRIORITY OF PRECEDENCE:
These recitals are true and correct and are hereby incorporated into and made a part of
this Agreement. The following documents are hereby incorporated into and made a part of this
Agreement as though fully set forth herein.
A. This (Supplemental Agreement
B. The Contract, which consists of the following.
a. Primary Contracting Document
b. ApplicablegSchedules
c. Master Terms and Conditions
d. Sample Project Deliverable Sign -Off Form
e. Cloud Program Conditions
f. Standard Training Program Terms
Common Terms Glossary
g•
h. Data Processing Addendum
i. Hexagon Cloud Services — Acceptable Use Policy
i• Florida CJIS Security Policy
k. Criminal Justice Agency and Contractor CJIS Network Agreement
I. Orders
HxGN OnCall Dispatch Cloud Hosted Implementation, August 15,
2022, Attachment A
ii. Statement of Work for HxGN Connect Cloud Consulting Services,
August 15, 2022, Attachment B
The order of precedence whenever there is any conflicting or inconsistent language
between documents is as follows in descending order of priority. (1) this Supplemental
Agreement, inclusive of any amendments which may be authorized by the City and executed by
the parties, if any, and (2) The Contract and its exhibits in the order indicated above.
2. TERM:
This Supplemental Agreement shall become effective on the date indicated on the first
page, and shall continue through the term of the Contract, ending on July 22, 2027, unless
terminated sooner or renewed in accordance with the Contract.
Page 2 of 14
3. CONFLICT OF INTEREST:
Pursuant to City of Miami Code Section 2-611, as amended ("City Code"), regarding
conflicts of interest, Contractor hereby certifies to the City that no individual member of Contractor,
no employee, and no subcontractors under this Agreement or any immediate family member of
any of the same is also a member of any board, commission, or agency of the City. Contractor
hereby represents and warrants to the City that throughout the term of this Agreement, Contractor,
its employees, and its subcontractors will abide by this prohibition of the City Code.
4. NO THIRD -PARTY BENEFICIARIES
No persons other than Contractor and the City (and their successors and assigns) shall
have any rights whatsoever under this Agreement.
5. SURVIVAL
All obligations (including but not limited to indemnity and obligations to defend and hold
harmless) and rights of any party arising during or attributable to the period prior to expiration or
earlier termination of this Agreement shall survive such expiration or earlier termination provided
that those rights are intended to survive. For purposes of clarity, those rights that are limited in by
time, including, but not limited to, Subscription Licenses, the Cloud Program, Support Contract(s),
and Training Program Statements, provide only rights for the term specified in the Order
Documents. Section 23.2 of the Master Terms remains applicable in addition to the provision set
forth in this paragraph.
6. COUNTERPARTS; ELECTRONIC SIGNATURES
This Agreement may be executed in counterparts, each of which shall be an original as
against either Party whose signature appears thereon, but all of which taken together shall
constitute but one and the same instrument. An executed facsimile or electronic scanned copy of
this Agreement shall have the same force and effect as an original. The parties shall be entitled
to sign and transmit an electronic signature on this Agreement (whether by facsimile, PDF, or
other email transmission), which signature shall be binding on the party whose name is contained
therein. Any party providing an electronic signature agrees to promptly execute and deliver to the
other parties an original signed Agreement upon request.
7. GENERAL MODIFICATIONS
Page 3 of 14
Any references to "Sheriff" shall be construed to mean "City Manager."
8. MODIFICATIONS TO PRIMARY CONTRACTING DOCUMENT
8.1 Section 3 is hereby deleted in its entirety and replaced as follows:
"All notices or other communications required under this Contract shall be in writing and
shall be given by hand -delivery or by registered or certified U.S. Mail, return receipt
requested, addressed to the other party at the address indicated herein or to such other
address as a party may designate by notice given as herein provided. Notice shall be
deemed given on the day on which personally delivered, or, if by mail, on the fifth day after
being posted or the date of actual receipt, whichever is earlier.
TO HEXAGON: TO THE CITY:
Victor S. Vasile Arthur Noriega V
SIG Legal Department City Manager
305 Intergraph Way 444 SW 2— Avenue, 10« Floor
Madison, AL 35758 USA Miami, FL 33128-1910
Annie Perez, CPPO
444 SW 2— Avenue, 6`" Floor
Miami, FL 33130-1910
City Attorney
444 SW 2— Avenue, 9`^ Floor"
8.2 Sections 4 and 5 are hereby deleted in their entirety in favor of the details included in the
pertinent Orders provided that by executing this supplement the Parties simultaneously
accept, without need to execute any other Order Documents, the Orders reflected in two
(2)
separate statements of work: (i) the implementation for implementation of OnCall
Dispatch and (ii) the implementation of I IxGN Connect.
9. MODIFICATIONS TO MASTER TERMS AND CONDITIONS
9.1 Section 3.2, Order of Precedence, is hereby deleted in its entirety.
Page 4 of 14
9.2
9.3
9.4
9.5
Section 4.2, Payment, is hereby deleted in its entirety and replaced as follows.
"Customer shall make payment within forty-five (45) days of the date it receives a
proper invoice from Hexagon in accordance with the Florida Prompt Payment Act,
Fla. Stat. §218.70 et seq."
Section 5.3.3, Termination for Cause, is hereby deleted and replaced with the following.
"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 conforming
Work performed as well as Product(s) provided on aall impacted Orders up to the
termination date, less amounts previously paid by Customer under the affected
Orders."
Section 5.3.4, Termination for Cause, is hereby deleted and replaced with the following.
"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 forty-five (45) 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 on 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."
Section 8, Limitation of Liability, is hereby deleted and replaced with the following.
"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, OR LOSS OF DATA.
Page 5 of 14
9.6
Section 9.3, Indemnification Provisions, is hereby deleted and replaced with the following.
"Contractor shall indemnify, hold and save harmless, and defend (at its own cost
and expense), the City, its officers, agents, directors, and/or employees
(collectively "Indemnitees"), from all third party: liabilities, damages, losses,
judgements, and costs, including, but not limited to, reasonable attorneys fees,
for bodily injury, death, or property damage to the extent caused by the negligence,
recklessness, negligent act or omission, or intentional wrongful misconduct of
Contractor and persons employed or utilized by Contractor in the performance of
this Agreement. Contractor shall further, hold the City, its officials and employees,
indemnify, save and hold harmless for, and defend (at its own cost), the City its
officials and/or employees against any civil actions, statutory or similar claims,
injuries or damages made against the City arising or resulting from the Services,
or from any alleged failure to comply with applicable federal, state and local laws,
rules, regulations, codes, and ordinances (collectively "regulations"), as they may
be amended from time to time.. In the event that any action or proceeding is
brought against the City by reason of any such claim or demand, the Contractor
shall, upon written notice from the City, resist and defend such action or
proceeding by counsel satisfactory to the City. The Contractor expressly
understands and agrees that any insurance protection required by this Agreement
or otherwise provided by the Contractor shall in no way limit the responsibility to
indemnify, keep and save harmless and defend the City or its officers, employees,
agents, and instrumentalities as herein provided.
The indemnification provided above shall obligate the Contractor to defend, at its
own expense, to and through trial, administrative, regulatory, appellate,
supplemental and bankruptcy proceedings, or to provide for such defense, at the
City's option, any and all claims of liability and all suits and actions of every name
and description which may be brought against the City, whether performed by the
Contractor, or persons employed or utilized by Contractor.
These duties will survive the cancellation or expiration of the Agreement. This
Section will be interpreted under the laws of the State of Florida. Contractor shall
Page 6 of 14
9.7
9.8
9.9
9.10
require all sub -Contractor agreements to include a provision that each sub -
Contractor will indemnify the City in substantially (the same language as this
Section. Contractor agrees and recognizes that the City shall not be held liable or
responsible for any claims which may result from any actions or omissions of the
Contractor in which the City participated either through review or concurrence of
the /Contractor's actions. In reviewing, approving, or rejecting any submissions by
the Contractor or other acts of the Contractor, the City, in no way, assumes or
shares any responsibility or liability of the Contractor or sub -Contractor under this
Contract.
Ten dollars ($10.00) of the payments made by the City constitute separate, distinct,
and independent consideration for the granting of this Indemnification, the receipt
and sufficiency of which is voluntarily and knowingly acknowledged by the
Contractor."
Section 9.4, Indemnification Provisions, is hereby deleted in its entirety.
Section 9.5, Indemnification Provisions, is hereby deleted in its entirety.
Section 9.6, Indemnification Provisions, is hereby deleted in its entirety.
Section 10, Insurance, including all subsections, is hereby deleted, and replaced with the
following.
"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.
A. Commercial General Liability
Limits of Liability
Bodily Injury and Property Damage Liability Each Occurrence
$1,000,000.00
General Aggregate Limit
$2,000,000.00
Prod ucts/Co m pl eted Operations
$1,000,000.00
$1,000,000.00
Page 7 of 14
Endorsements Required
City of Miami included as and Additional Insured
Contingent and Contractual Liability
Premises and Operations Liability
Primary and Non -Contributory Insurance Clause Endorsement
Additional Insured Endorsement naming the City of Miami as an additional insured
must be provided.
B. Business Automobile Liability
Limits of Liability
Bodily Injury and Property Damage Liability
Combined Single Limit
Any Auto Including Hired, Borrowed or Non -Owned Autos
Any One Accident
$1,000,000.00
Endorsements Required
City of Miami included as an Additional Insured
Additional Insured Endorsement naming the City of Miami as an additional insured
must be provided.
Umbrella/Excess Liability (Excess Follow Form)
Limits of Liability
Each Occurrence
$1, 000, 000.00
Aggregate
$2,000,000.00
Additional Insured Endorsement naming the City of Miami as an additional insured
must be provided.
Page 8 of 14
C. Workers' Compensation
Limits of Liability
Statutory - State of Florida
Employer's Liability
Limits of Liability
$ 100,000.00 for bodily injury caused by an accident, each accident.
$ 100,000.00 for bodily injury caused by disease, each employee
$500,000.00 for bodily injury caused by disease, policy limit
Professional/Errors and Omissions
Combined Single Limit
Each Claim
$5,000,000.00
$5,000,000.00
Retro Date Included
Network Security and Privacy Injury (Cyber Liability) If Applicable
Each Claim
$5,000,000.00
Policy Aggregate
$5,000,000.00
Retro Date Included
Consultant agrees to maintain professional liability/Errors & Omission's coverage,
along with Network Security and Privacy Injury (Cyber) coverage, if applicable, for at
least two (2) years after termination of the Agreement period subject to continued
availability of commercially reasonable terms and conditions of such coverage.
Hexagon shall provide the City of Miami with prompt written notice of cancellation or
material change. Companies authorized to do business in the State of Florida, with the
following qualifications, shall issue all insurance policies required above:
The company must be rated no less than "A-" as to management, and no less than
"Class V" as to Financial Strength, by the latest edition of Best's Insurance Guide,
published by A.M. Best Company, Oldwick, New Jersey, or its equivalent. All
Page 9 of 14
certificates of insurance are subject to review and verification by Risk Management
prior to insurance approval.
NOTE: CITY INVITATION FOR BID ("IFB")/REQUEST FOR PROPOSALS ("RFP")
NUMBER AND/OR TITLE MUST APPEAR ON EACH CERTIFICATE.
Compliance with the foregoing requirements shall not relieve the Provider of liability
and obligation under this section or under any other section of this Agreement.
"If insurance certificates are scheduled to expire during the contractual period,
the Provider shall provide renewed certificates as soon as possible but in no event
more than twenty business days following the expiration of the original certificate.
"In the event that expired certificates are not replaced with new or renewed
certificates which cover the contractual period, at its discretion, the City shall.
Suspend the Agreement until such time as the new or renewed certificates are
received by the City in the manner prescribed in the IFB/RFP; or,
Terminate this Agreement for cause(uand seek re -procurement damages from the
Provider in conjunction with the General and Special Terms and Conditions of the
IFB/RFP. The Provider shall be responsible for assuring that the insurance certificates
required in conjunction with this Section remain in force for the duration of the
contractual period, including any and all option terms that may be granted to the
Provider."
9.11 Section 12.2, Mediation, is hereby deleted in its entirety.
9.12 Section 12.3, Prerequisites to Litigation, is hereby deleted in its entirety.
9.13 Section 13, Notices, is hereby deleted in its entirety.
9.14 Section 17, Confidential Information, is hereby deleted and replaced as follows.
"Subject to the requirements of Florida Statutes Chapter 119 and Article I, Section
24 of the Florida Constitution, 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 competent jurisdiction. 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
Page 10 of 14
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.
If Hexagon provides any Confidential Information that qualifies for exemption from
Florida Public Records Law, it must be clearly identified and labeled as
"CONFIDENTIAL INFORMATION - TRADE SECRETS." Hexagon acknowledges
and is aware that the designation of an item as a trade secret may be challenged
in court by any person. If such information is requested pursuant to a public records
request, the City will notify Hexagon and provide a reasonable opportunity to seek
a protective order in court. Any costs associated with obtaining a protective order,
or any costs incurred by the City defending itself in a public records case in
connection with such Confidential Information, shall be borne solely by Hexagon."
9.15 Section 17a, Public Records Law, is hereby deleted and replaced as follows.
"Pursuant to the provisions of Section 119.0701, Florida Statutes, Contractor must
comply with the Florida Public Records Laws, specifically, Contractor must:
1) Keep and maintain public records that ordinarily and necessarily would be required
by the public agency to perform the service.
2) Provide the public with access to public records, on the same terms and conditions
that the public agency would provide the records, and 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.
4) Meet all requirements for retaining public records(�and transfer, at no cost, to the
City all public records in its possession. Contractor, upon termination of the
Agreement, shall destroy any duplicate public records that are exempt or
confidential and exempt from public records disclosure (requirements.
5) All records stored electronically must be provided to the City in a format compatible
with theinformationtechnology systems of the public agency.
6) Should Contractor determine(�to dispute any public access provision required by
Florida Statutes, then Contractor shall do so at its own expense and at no cost to
the City.
IF CONTRACTOR HAS QUESTIONS REGARDING THE APPLICATION OF
CHAPTER 119, FLORIDA STATUTES, IT IS CONTRACTOR'S DUTY TO
PROVIDE PUBLIC RECORDS RELATING TO THIS AGREEMENT, CONTACT
Page 11 of 14
THE DIVISION OF PUBLIC RECORDS AT (305) 416-1800, VIA EMAIL AT
PUBLICRECORDS@MIAMIGOV.COM, OR REGULAR MAIL AT CITY OF
MIAMI OFFICE OF THE CITY ATTORNEY, 444 SW 2ND AVENUE, 9TH FLOOR,
MIAMI, FL 33130. CONTRACTOR MAY ALSO CONTACT THE RECORDS
CUSTODIAN AT THE CITY OF MIAMI DEPARTMENT WHO IS
ADMINISTERING THIS AGREEMENT."
9.16 Section 19, Assignment, is hereby deleted and replaced as follows:
"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."
9.17 Section 23.1, Authority, is hereby deleted and replaced as follows:
"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. 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 issuing a Purchase Order
expressly referencing the Order Documents, Customer represents and certifies to
Hexagon it has the requisite legal authority to enter into and be bound by the Order
contemplated in the Order Documents.
9.18 Section 23.6, Governing Law, is hereby deleted and replaced as follows:
"This Agreement will be construed and interpreted in all respects in accordance
with the laws of the State of Florida without regard to its conflicts of law's
provisions. Venue for any dispute arising under this Agreement shall be exclusively
in the federal and state courts located in Miami -Dade County, Florida. Each Party
submits to the jurisdiction of such courts and expressly waives any objection as to
personal jurisdiction or forum non -convenes. Each party shall be responsible for
its own attorneys' fees."
Page 12 of 14
9.19 Section 23.9, Limitation on Claims, is hereby deleted in its entirety.
9.20 Section 23.14 is hereby deleted in its entirety.
9.21 Section 23.15 is hereby added as follows.
"Funding for this Agreement is contingent upon the availability of funds and
continued authorization for program activities and the Agreement is subject to
amendment or termination due to lack of funds, reduction of funds, failure to
allocate or appropriate funds, and/or changes in applicable laws, city programs or
policies, or regulations, upon thirty (30) days written notice. To the extent the
Agreement is terminated pursuant to this provision, the parties shall wind down
and address all claims in the manner provided under Section 5.2 (Termination for
Convenience)."
9.22 Section 24 is hereby deleted and replaced as follows.
"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 Docu ment, the supersedes any and all prior
discussions and/or representations, whether written or oral, and no reference to
prior dealings may be used to in any way modify the expressed understandings of
the Master Agreement. The Master Agreement may not be amended or modified
unless so done in a writing signed by authorized representatives of both Parties.
Page 13 of 14
IN WITNESS WHEREOF, the parties have executed this Addendum to the Agreement.
"Hexagon"
ATTEST: INTERGRAPH CORPORATION,
a Delaware Corporation
By 9 4-9.-A. PCP
C
Print Name Ki2+.1-1
Title:\" • t CaSf .
,(Gn oripta4
ft: I Y
krItE T! � ') r
By i t .
(
Print Name: -f C2Yjy— laL 1l
i
Title: HI 'C-LL Y E ,11 '(X?'1 f
(Authorized Corporate Officer)
"City"
CITY OF MIAMI,
a Florida municipal corporation
By: By:
Todd B. Hannon, City Clerk Arthur Noriega V, City Manager
APPROVED AS TO LEGAL FORM APPROVED AS TO INSURANCE
AND CORRECTNESS: REQUIREMENTS:
Victoria Mendez Ann -Marie Sharpe
City Attorney Risk Management Director
Page 14 of 14
A HEXAGON
Attachment A
Statement of Work
for
HGN Connect
Cloud Consulting Services
PRESENTED BY:
Trent Low
Regional Sales Manager
Hexagon Safety, Infrastructure, & Geospatial
305 Intergraph Way
Madison, AL 35758 USA
772-559-6489
trent.lowe@hexagon.com
Ai.igi.ist 15, 2022
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
2
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
TABLE OF CONTENTS
Purpose 4
Statement of Work Outline 4
Order and Defined Terms 4
Project Outline 5
H.GN Connect Program Functionality and Support 5
Customer Project Team Structure 6
Project Assumptions and Responsibilities 7
Training and Development 10
Project Initiation 11
Project Tasks 12
IOC Phase 12
Project Kickoff Meeting 12
HxGN Connect Cloud Environment Creation 14
HxGN Connect Administrator Training 15
to Customer - IOC Completionl6
FOC Phase 18
Configuration of HxGN Connect Program 18
UserAcceptence Testing 19
Address Blocker Errors from UAT 21
User Training 23
System Availability 24
Attachment A — Pricing Summary 25
Attachment B — Payment Milestones 26
Attachment C — Initial Project Schedule 27
Attachment D — Training Courses Curriculum 28
Attachment E — Local Application System Requirements 29
Attachment F — Functional Specification Matrix 30
Attachment G — Interface Addendum 31
Attachment H — Glossary of Terms 32
Attachment I — Reserved 34
Attachment J — Onboarding Worksheet 35
3
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Purpose
The SOW describes the Cloud Consulting Services for the Cloud Program. It documents Project
implementation requirements, Cloud Application and Local Software functionality, the Activities and Tasks
comprising the Project, the timeframe for completion of Activities and Tasks, the responsibilities for each
Party, and the Task Acceptance Criteria.
Statement of Work Outline
The Services reflected in this SOW, exclusive of the Services described in Attachments G (Interface
Addendum) and I (Additional Services), are included in the Quote' line item, "HxGN Connect Program
Implementation Services." Services for Interfaces and Additional Services are reflected in Attachments G
and I, if any, and separately identified in the Quote.
The SOW includes and incorporates the following Attachments.
• Attachment A— Pricing Summary (Quote)
w Attachment B — Payment Milestones
Attachment C — Initial Project Schedule
Attachment D —Training Courses Curriculum
Attachment E — Local Application System Requirements
Attachment F — Functional Specifications Matrix
Attachment G — Interface Addendum
Attachment H — Glossary of Terms
Attachment I — Reserved
• Attachment J — Onboarding Information Worksheet
Each task identified in the SOW includes the following as necessary. Task Description, description of
Activities, Task Deliverables, Task Prerequisites and Assumptions, Hexagon/Customer Team
Participation and Responsibilities, and Task Acceptance Criteria. The Tasks described in this SOW may
not be listed chronologically, and the actual Project implementation Tasks and timelines will follow the
Project Schedule, unless otherwise noted.
Order and Defined Terms
This SOW, together with the attached Quote, is an Order made pursuant to the Master Terms identified in
the Quote. Execution of the Quote accompanying this SOW reflects the Customer's acceptance of the
Order. This SOW describes the Cloud Consulting Services and other Software (if purchased) provided by
Hexagon in connection with the initial implementation of HxGN Connect. Hexagon will provide the Cloud
Consulting Services to facilitate implementation of HxGN Connect as expressly set forth in this SOW (the
"Project"). Unless otherwise defined in this SOW, capitalized terms shall have the same meaning as set
forth in the Common Terms Glossary and Attachment H (Glossary) attached hereto.
For purposes of this Statement of Work, the Quote refers to Attachment A.
4
HEXAGON
Project Outline
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
The Project consists of two (2) phases: Initial Operating Capability ("IOC") and Final Operating Capability
("FOC"). During IOC, Hexagon will Onboard the tenant(s) accounts associated with this Project and
provide access to the HxGN Connect application. As part of FOC, Hexagon shall provide services to
support Customer Activities as expressly described in this SOW.
All Tasks reflected in this SOW are regarded as complete and accepted upon completion of Task: System
Availability.
HxGN Connect Program Functionality and Support
As part of the Cloud Program(,, Hexagon shall provide Credentials/License Keys to the Cloud Application
components identified in the Quote. The Cloud Program shall have the capabilities and functionality set
forth in the Specifications, which reflects all of the functionality Hexagon is obligated to provide in the
HxGN Connect Program. From time to time, Hexagon may update HxGN Connect, including during the
Project, which may modify the Specifications. Such updates as documented by Hexagon will reflect the
then -current Specifications for purposes of this SOW. User Acceptance Testing shall only test that the
functionality set forth in corresponding to Cloud Programs purchased (see Attachment A), and data is
flowing into the HxGN Connect application as expected. Errors identified during testing are addressed in
accordance with the terms related to Cloud Services Support. Only Blocker Errors are required to be
resolvedpriorto completion of the System Availability Task. This scope does not include any Product
Change Requests.
As part of the Cloud Program, the Customer may have access to various HxGN Connect Tenant accounts
and environments: Production, Dev, and Training. This Project contemplates most Activities for
configuring the HxGN Connect application occurring in the Production Environment. Any interface
development (if any) will be performed and tested in the Dev environment.
Upon i completion of the System Availability Task (which constitutes Cloud Cutover in this Statement of
Work), the Cloud Program Start Date shall have occurred. Consequently, Cloud Services Support will
also begin at that time. The Customer is responsible for performing its Cloud Services Support obligations
as reflected in the Master Terms for the duration of the Cloud Term, as may be extended.
5
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Customer Project Team Structure
The Customer is responsible for providing qualified resources to staff the Core Team (described below) to
facilitate a successful implementation of HXGN Connect. The Core Team roles and responsibilities are
described in the following sections.
Core Team Roles and Responsibilities
The Core Team (as described below) shall consist of designated organization (Customer) personnel with
the various skill sets and knowledge and backgrounds required to implement HXGN Connect. The
following list identifies the required Core Team and its respective roles and corresponding responsibilities.
• PrOjeot Manager — responsible for the day-to-day coordination of Project Activities on behalf of
• Sy.tern Adn,inistraicr Personnel — responsible for all system administration and configuration
responsibilities related to the HXGN Connect Program. Note, it is recommended that each
separate organization have its own System Administrator.
• Sub;eci Mailer Experts (SME.) — responsible for representing end -users' needs and providing
specific IT/networking expertise. SMEs should have a deep understanding of their organization's
business processes. Note, it is recommended that each separate organization have SME(s) on
the Core Team.
6
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Project Assumptions and Responsibilities
The following reflects the assumptions and responsibilities regarding the Project. Changes in any of the
assumptions will affect the scope, Project Schedule, and/or cost of the Project.
Agreement and Schedule Assumptions
• This Cloud Consulting Services Order and the Cloud Program Order have been executed by the
Customer, accepted by Hexagon, and the Customer has provided a notice to proceed, Purchase
Orders (PO) for both Orders, or written confirmation. Only the execution of the Orders or other
acceptance documented in the Primary Contracting Document is necessary to bind the Customer.
• Prior to Project Kickoff, Customer shall have secured any necessary permissions or agreements
with Tenants who are to exchange data with Customer and be bound to the responsibilities and
obligations of this Order and the Agreement. This includes any required agreements
between among participating organizations.
• The Customer shall perform its assigned Activities set forth in this SOW in the timefra me identified
within the Initial Project Schedule (Attachment C) and Project Schedule developed as part of
Task: "Project Kickoff Meeting," as modified from time to time. If the Customer requests Hexagon
extend the Initial Project Schedule or any subsequent Project Schedule, it acknowledges
additional Consulting Services may be necessary for which a Change Order will be required.
it is assumed there is only one "Project Kickoff Meeting," unless otherwise negotiated.
• Hexagon will have timely access to Customer Project staff in accordance with the Project
Schedule and Tasks. Customer shall make additional personnel available on a priority basis, as
needed, to provide subject matter expertise to complete this Project.
• Customer shall have at least one (1): Project Manager, System Administrator, technical
resource(s), and SME available to perform and/or support all Customer responsibilities and timely
respond to Hexagon requests.
• The Customer shall provide Hexagon with or access to all data, documents, plans, reports, and
diagrams, related to this Project and Hexagon responsibilities for this Project.
• Unless otherwise noted in this SOW, all Documentation, if any, provided by Hexagon under this SOW will be COTS Documentation and the Documentation will not be customized by Hexagon. All
Documentation delivered will be in Hexagon -approved electronic format.
• Customer, and any Tenants, shall conform to the requirements of the Master Terms, including, but
not limited to, those provisions related to the Cloud Program, at all times.
• Unless otherwise stated in the Task, all Tasks will be conducted remotely.
• If the Customer desires additional Services from Hexagon, the Parties can either enter into a
separate Order for those Services or enter into a Change Order to explicitly modify this Order.
Except for those Services expressly identified as being performed by Hexagon herein, it is not
obligated to provide any other or additional Services under this Order.
• Notwithstanding anything to the contrary within the Master Terms, they Customer shall
substantively respond to the delivery of a sign -off form within five (5) Business Days as part of the
Task Acceptance Process.
• Historical data conversion or importation is not included in this Project.
• Hexagon shall provide its Project Services only during normal Business Hours.
• For meetings or workshops involving both the Customer and Hexagon there will be at least a
fifteen (15) minute break every two (2)(�hours with a one (1) hour lunch break for meetings
scheduled to last an entire day (eight (8) hours).
7
„ A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Hardware and Software Assumptions
• Local Software, if any, will be electronically delivered to the Local Environment.
• To the extent Local Software is delivered as part of this SOW, the Customer shall provide access
to its Local Environment to Hexagon for the duration of the Project.
• No Local Software will be delivered during the IOC Phase.
• The Customer shall purchase, install, and test all physical hardware comprising the Local
Environment.
• . he Customer will ensure its hardware, operating system software, and other third -party
products/environments conform with Attachment E — Local Application System Requirements.
• Customer shall purchase all applicable operating systems and software in the Local Environment,
including, but not limited to, client workstations, and ensure such operating systems and software
meet the minimum requirements as defined in Attachment E Local Application System
Requirements.
• Customer shall be responsible for the wired and wireless connectivity between servers/clients and
clients/clients and with the Cloud Applications.
• o the extent the Customer desires to use the Cloud Program or other deliverables provided
herein in a manner or in combination with software or hardware that is not certified or
recommended by Hexagon, then the Customer shall be solely responsible for such use. Hexagon
shall not be responsible for the correction of any Errors, reduced performance, compromised
functionality, or other unintended
consequences arising from such use. The
he Customer also shall
not withhold acceptance of any Task or the Cloud Program due to such use.
System Access Assumptions
• The Cloud Program shall store data (in either transit or at rest) in the Cloud Environment.
Customer is solely responsible for (i) assuring it is permitted by appropriate government
organizations to transmit the intended information and store data (in either transit or at rest) in the
Cloud Environment and (ii) otherwise complying with and ensuring this Project and the Cloud
Program to be provided does not violate applicable government regulations.
• Customer shall purchase, install, configure, and administer its Network Infrastructure, including,
but not limited to, its WAN/LAN and wireless infrastructure.
Customer consents to Hexagon's inspection and use of Customer's data and systems, including,
but not limited to, log files and databases, for the limited purpose of providing the Cloud Services
and Cloud Consulting Services.
• If necessary, Hexagon shall access the Cloud Program, including Local Software, and Customer
Data via a Security Access Tool.
• The Customer is responsible for ensuring its data communications infrastructure and devices
comply with applicable government requirements.
Third -Party As sumptions
• Customer shall schedule and coordinate third -party technical resources with the skills necessary
to perform and/or support all Customer Responsibilities, respond to Hexagon requests, and
support the testing of Interfaces, as required.
• Customer shall maintain, in good working order, all third -party systems which will integrate with
Hexagon software or on which the Hexagon software depends as part of this Project except for T
the Third -Party Software included as part of the Cloud Program and provided thereunder.
• Customer shall be responsible for the operation and timely availability of external systems or third -
party software necessary for the execution of the Project, if any.
8
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
If a delay in the Project is caused by a third -party vendor or Tenants, Hexagon services not covered
in this SOW may be required at additional costs.
9
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Training and Development
Hexagon shall provide the Customer access to user and system administration documentation for HxGN
Connect and related product component documentation.
At the Project Kickoff Meeting, Hexagon will also provide the Customer e-learning credentials (the "Base
eLearning Credentials") for the e-learning courses purchased in the Quote accompanying this SOW
("Base eLearning Courses").
The e-learning classes reflect Hexagon's latest learning and training tool, which can and should be used
throughout the Project. The product Documentation and Base eLearning Credentials may be used at all
times during the Project; however, the Customer's access to the Base e-learning Credentials shall end
one p(1) year after formation of this Order, unless otherwise renewed. The Training Program Statement for
the Base eLearning Credentials provided in this Project, is described in Attachment D, which may be
supplemented with other Training Program Statements for additional eLearning classes purchased and
not identified in this SOW.
The Customer should take advantage of these tools during all Phases of the Project. The comprehensive
use of these learning tools will facilitate a better transition to HxGN Connect and can lead to more
constructive exchanges with Hexagon resources during workshops and consulting sessions. As denoted
at certain Tasks, certain prerequisites for Tasks will include Customer personnel having read the relevant
sections of the Documentation and/or watched the relevant eLearning course.
10
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Project Initiation
Prior to the Project Kickoff Meeting and after placement of the Order, the following initial Activities must
be performed before any Tasks can occur.
•
Identify the Project Start Date, which should be within two (2) business days prior to the
Project Kickoff Meeting;
Schedule the Project Kickoff Meeting;
Provide an agenda describing the goals of the Project Kickoff Meeting; and
Discuss factors that could affect the Project (e.g., scheduling conflicts, communication factors,
change management and other risk factors).
• Hexagon's Project Manager shall update the Initial Project Schedule to reflect local holidays;
Hexagon resource availability; and any additional Services, Software, or other items included
within the Order, identify the Project State Date, and provide the Updated Initial Project Schedule
to the Customer Project Manager prior to the Project Kickoff Meeting.
• Hexagon shall provide the Customer an electronic copy of the User and System Administrator
Documentation for HxGN Connect prior to the Project Kickoff Meeting.
• Hexagon shall provide the Customer the Base e-learning Credentials and any other e-learning
credentials listed in the Quote.
11
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Project Tasks
IOC Phase
1. Project Kickoff Meeting
Task Description
The objective of this Task is to confirm the updated Initial Project Project Schedule (Attachment C) provided on
the Project Start and provide an overview of the Project. A meeting for Project Kickoff will be held via
virtual meeting after the Project Start date. There will be only one Project Kickoff meeting, regardless of
how many Tenants are included in the Project. The Kickoff Meeting may be held in conjunction with the
Kickoff Meeting for the OnCall Dispatch Order or independently.
The Project Kickoff Meeting shall last no more than one (1) hour.
During this Task, the Parties, including representatives from the Tenants, shall confirm the updated Initial
Project Schedule as updated by the Hexagon Project Manager. The resulting updated Initial Project
Schedule shall be substantially similar in duration as provided within Attachment C unless accepted by
Hexagon. Prior to the Project Kickoff Meeting Task, the Customer Project Manager shall have reviewed
the updated Initial Project Schedule and be in a position to succinctly identify any needed changes
understanding material extensions of the Initial Project Schedule may require additional Hexagon
Services to be added via a Change Order. Once the list of changes has been made to the updated Initial
Project Schedule by the Hexagon Project Manager, the Hexagon Project Manager will thereafter provide
the Project Schedule to the Customer Project Manager. From time to time, the Parties' Project Managers
may modify the Project Schedule upon mutual written consent or upon transmission of an updated Project
Schedule to the Customer Project Manager as part of a status report and the Customer Project Manager
offers no objection to the updated Project Schedule within five (5) Business Days thereafter.
As part of the Project Kickoff Meeting, the Hexagon Project Manager shall provide to Customer. (i) acces
credentials to Hexagon online training materials and (ii) any applicable Interface Worksheets (as
described in the Interface Addendum). At the Project Kickoff Meeting, the Customer shall provide: (i)
contact information for all members of its Core Team and Executive/Departmental Sponsor, (ii) proposed
alterations to the updated Initial Project Schedule, (iii) contact information for any third party vendors
which HxGN Connect will integrate as contemplated in the Interface Addendum, (iv) review and complete
the onboarding information worksheet (Attachment J), and (v) identify to Hexagon any perceived
concerns or risks with the Project.
Ta sK Deliverables
• Project Schedule
• Access credentials to Hexagon online training materials
• Onboarding information worksheet (Attachment J)
TasK Prerequisites
• The following Activities must be completed prior to beginning this Task:
the full amount reflected in both Quotes (or the Customer has indicated in writing it does
not need to issue Purchase Orders to facilitate transactions of this type).
Hexagon Project Manager has verbally communicated with the Customer to (i) identify
the Project Start date and (ii) coordinate a date for the Project Kickoff Meeting.
12
„ A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Customer has assigned a Customer Project Manager.
• Customer's Core Team has reviewed this SOW.
• Customer is in compliance with Attachment E — Local Application System
Requirements.
Task Assumptions
• The Core Team, representatives from the Tenants, and the Hexagon Project Manager shy
the Project Kickoff Meeting.
• The Project Kickoff Meeting will last no more than one (1) hour unless otherwise extended
because other SOWS are to be discussed (as described above).
Hexagon Team Participation and Responsibilities
• The Hexagon Project Manager shall attend the Project Kickoff Meeting
• Hexagon shall.
' Provide an overview of this Project and address nontechnical questions,
Conduct an overview of the Project including a review of the SOW to verify all aspects
of the Project approach,
Establish status reporting requirements (but no more frequentlythanonce per month),
Provide the Customer the Base e-Learning Credentials for the Base e'learning Course
• Gather information from the customer to complete the onboarding information
worksheet, and
Prepare the updated Initial Project Schedule the parties will review during the Project
Kickoff Meeting. Customer Team Participation and I'') responsibilities
• The Core Team shall attend the Project Kickoff Meeting.
• The Customer shall
Provide Hexagon: contact information for all members of its Core Team and
Executive/Departmental Sponsor, (ii) proposed alterations to the updated Initial Project
Schedule, and (iii) contact information for any third -party vendors which the HxGN
Connect Program will integrate.
• Provide information to complete the onboarding information worksheet, and
• Identify any perceived risks or concerns.
Task Acceptance Criteria
This Task is complete at the conclusion of the Project Kickoff Meeting and delivery of the Project
Schedule to Customer.
13
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
2. HXGN Connect Cloud Environment Creation
The objective of this Task is to create and "spin -up" the Customer's Development Environment for the
HxGN Connect Program.
The Development Environment will be used by Customer during the Project and serve as the basis for the
Development Cloud Environment upon Cloud Cutover. Hexagon will inform the Customer once the
applicable Development Environment for Customer has been created.
Task Prerequisites • Project Kickoff Meeting Task ask is complete.
Task Assumptions
• None
Hexagon Team Participation and Responsibilities
Hexagon shall:
• Create the Cloud Environment (only Development Environment at this Task) with the HXGN
Customer Team Participation and Responsibilities
Task Acceptance Criter
This Task shall be complete upon creation of the Customer's Development Environment for the HxGN
Connect Cloud Program.
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
3. HxGN Connect Administrator Training
Task Description
The objective of this Task is to have the Core Team prepare for the subsequent Tasks. HXGN Connect
Administrator training consists of e-learning training curricula (subject to being purchased) intended for
the persons responsible for administering and configurating the HxGN Connect system (see Attachment
D). Customer will complete its review of the Administrator and User training and other training
Documentation ("IOC Training Materials") within 30 Business Days from the end of the Project Kickoff
Meeting ("IOC Training Period").
Example topics in this Base e-learning Curricula include:
40 Creating and managing user accounts
• Access management — creating and managing access tokens for API interfaces
• Defining HxGN Connect screen layouts
• Configuring map display data
Task Prerequisites and Assumptions
• Hexagon has provided access to Hexagon Base eLearning Credentials to Customer.
Hexagon Team Participation a nd Responsibilities
• Only the IOC Training Materials are included — no Hexagon live training is provided as part of IOC.
Customer Team Participation and Responsibilities
• Customer Project Manager has distributed access credentials to Hexagon online training materials
and training Documentation to Core Team.
• The Core Team shall view and read IOC Training Materials.
• Customer Project Manager will manage the Customer's training compliance and report to
Hexagon Project Manager once the Customer Core Team has completed the requirements of this
Ta sk.
Ta sk Acceptance Criteria
IOC Training Materials or (ii) the IOC Training
15
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
4. IOC Completion
This Task serves as a milestone and culmination of the previous Tasks. It is at this point in the Project
that: Hexagon has created all relevant license keys and set up the Tenant account(s). The Customer
should have completed the e-learning training curricula and should be familiar with the next steps in
getting the Tenant login account(s) established. Hexagon will host a virtual meeting with the Customer
project manager and designated system administrator(s) to (i) deliver the customer credentials/license
keys applicable to the Cloud Program, and (ii) walk the system administrator(s) through the steps to logon
and setup the initial Tenant account(s) and guide the system administrator(s) in setting up the initial
default user interface forms. Note, if additional virtual meetings are desired for each organization, they
can be quoted.
If access to HxGN Connect Dev and/or Training environments were purchased, the relevant license keys
and Tenant account(s) will be established in those environments as well.
The Credentials Delivery Meeting is complete once those two objectives are achieved. Completion of this
Task also serves to mark the completion of IOC Phase.
Task Deliverables
included within the Quote.
• Customer can login to the Cloud Program using Credentials/License Keys and navigate to the
initial user interface screens.
Task Prerequisites
• Tasks. Project kickoff meeting and HxGN Connect Administrator Training curricula is complete.
Task Assumptions
• Customer has necessary hardware, equipment, and Network Infrastructure ready and available to
access the Cloud Program.
• The Credentials Delivery Meeting is of a limited duration and only intended to cover the two topics
specified above. 1�
Hexagon Team Participation and Responsibilities
• Hexagon shall.
• Host the Credentials Delivery Meeting;
p can log into the Cloud Program to confirm connectivity,
Address Customer reported issues with accessing HxGN Connect.
Customer Team Participation and Responsibilities
• Customer Project Manager and System Administrator(s) will attend the Credentials Delivery
Meeting. Note, if the Customer desires a separate meeting for each Tenant, additional meetings
can be quoted.
• Customer shall access the HxGN Connect Program
during the Credentials Delivery Meeting.
• Report to Hexagon verbally during the Credentials Delivery Meeting whether the Customer can
access the Cloud Program or identify issues encountered in accessing the HxGN Connect
Progra m.
16
� A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
If Customer encounters issues in accessing HxGN Connect, it will work collaboratively with
Hexagon to troubleshoot and address the issue until resolution.
Ta s k Acce pta nce Criteria
This Task is complete when Hexagon has delivered the Cloud Program Credentials/License Keys to
Customer and confirmed the Customer is able to access HxGN Connect.
17
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
FOC Phase
5. Configuration of HXGN Connect Program
Task Description
HxGN Connect is a highly configurable software suite that is intended to be configured by the Customer
and reconfigured by the Customer as needs change. This Task is intended to provide the Customer time
within the scope of the FOC and Hexagon consulting services, to facilitate Customer's initial configuration
of the HXGN Connect Program. This Task is intended only for the Customer. Other Tenants desiring
configuration services may separately order or request a Change Order for such Services, which are not
included in this scope. This Task assumes the Customer wants assistance in setting up an initial
configuration in HXGN Connect. If the Customer does not want assistance with initial system
configuration, then this Task shall be regarded as complete.
Hexagon will remotely host up to two (2), two (2) hour configuration sessions to assist the Customer in
configuring HxGN Connect. The first configuration session will occur no earlier than four (4) days after this
Task commences. The remaining configuration sessions should be complete prior to user acceptance
testing. The Customer shall complete all configurations within 30 days from the final configuration session
(the "Configuration Period") Additional configuration sessions can be quoted as requested.
The configuration sessions should be attended by System Administrator(s) and Subject Matter Experts
(SMEs) who fully understand their organization's business processes.
Task Deliverables
• HxGN Connect configuration session(s).
Task Prerequisites
• The following items must be complete prior to beginning this task.
Task: System Administration Training is complete.
Task. SME5 have completed the User Training.
Task Assumptions
• Customer SMEs have significant knowledge of and/or access to Customer Business Processes.
• Customer has available at least one (1) SME for the HxGN Connect configuration sessions
Hexagon Team Participation and Responsibilities
• A Hexagon technical resource will conduct up to two (2) Configuration Session(s).
Customer Team Participation and Responsibilities
• Customer shall make its desired configurations to the HXGN Connect Program within the
Configuration Period
• The Core Team, as applicable, shall attend and participate in the configuration session(s).
Task Acceptance Criteria
This Task is complete upon the earlier of. Customer advising Hexagon it has completed making its
configuration changes or the Configuration Period has lapsed.
18
4 A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
6. User Acceptance Testing
The objective of this Task is to test the HxGN Connect Program and its interfaces and identify any
Blocker Errors.
Following completion of the Configuration of the HxGN Connect Program Task and specified Interface
Addendum Tasks, the Customer will test the HxGN Connect Program interfaces to identify Blocker Errors.
The UAT will consist of Customer evaluating whether the HxGN Connect Program is able to materially
achieve the intended outcome set forth in the Specifications with ordinary use. No other testing or
evaluation is contemplated in the FOC Phase of this Project. The Customer shall complete UAT within
five (5) Business Days from the latter of: the date the Task Configuration of Cloud HxGN Connect
Program is complete or specified Interface Addendum Tasks are complete ("UAT Commencement").
Within one (1) Business Day of the completion of UAT, Customer shall provide the Hexagon Project
Manager a written report of any Blocker Errors encountered during UAT ("Blocker Error Report"), if any.
For any Blocker Error identified in the Blocker Error Report, the Customer shall provide, at minimum, the
following information: a description of the Error and the steps used to reproduce it, the functionality tested
when the Blocker Error was encountered, the manner in which the functionality was tested, and the
outcome when the functionality was tested. If the Blocker Error Report is not provided to Hexagon within
the time allotted, it is presumed UAT was completed without any Blocker Errors, 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 Master Terms.
The existence or Permissive Errors shall not preclude or be a condition of completion of any subsequent
Tasks.
Task Prerequisites
The following items must be completed prior to beginning this Task.
Task: "Configuration of HxGN Connect Program" has been completed.
All Interfaces are developed and installed.
Task Assumptions
• UAT will consist of only testing the HxGN Connect Program against the Specifications identified in
the HxGN Connect Program Order.
• Only qualified Customer personnel will conduct UAT. Qualified Customer personnel are
considered resources who have completed the online training sessions required up to this point in
the Project and reviewed the identified portions of the System Administration documentation in
this SOW in the preceding Tasks.
Hexagon Team Participation and Responsibilities
• None
Customer Team Participation and Responsibilities
• Customer shall:
Complete UAT for the HxGN Connect Program in the manner described above within
five (5) Days, and
Provide the Blocker Error Report within one (1) Business Day following completion of
UATwith, at minimum, the details described above.
19
„ A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Ta s k Accepta nce Criteria
This Task is complete upon the earlier completion of UAT and tendering the Blocker Error Report to
Hexagon or six (6) Business Days from UAT Commencement.
20
A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
7. Address Blocker Errors from UAT
Task Description
Duringpthis Task, Hexagon will investigate, troubleshoot, and resolve valid Blocker Errors documented in Bl
ocker locker ErrorpReport. Notwithstanding the Task Acceptance Criteria below, which assumes the B existence of locker Errors, this Task is complete if the Customer does not timely return the Blocker
Report or if the Customer reports the absence of any Blocker Errors. Permissive Test Case Failures are
addressed in accordance with the Cloud Support Services provisions of the Master Terms.
After receiving the Blocker Error Report, Hexagon will investigate each Blocker Errors identified in the B Blocker Error Report to diagnose the source and cause of the locker Error. To the extent requested,
Customer agrees to promptly respond to requests for additional information regarding each Blocker Error
requested by Hexagon. Upon diagnosing the Blocker Error and validating the Error encountered meets
the attributes of a Blocker Error, Hexagon resources shall proceed to resolve the Blocker Error and
update the HXGN Connect Program 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. Alternatively, if the investigation shows the
reported Blocker Error was caused by Customer and/or third -party hardware, Network Infrastructure, or
software not provided by Hexagon, or non-conformance with Attachment E, then Hexagon will provide
such information to the Customer for the Customer to resolve and the Blocker Error will be closed and
regarded as complete.
As part of its resolution efforts, Hexagon may at its discretion provide a procedural or programmatic work
around, a configuration change, or provide an Update to the HXGN Connect Program. Once the Blocker
Error(s) is addressed, Hexagon will report to Customer the Blocker Error has been addressed and the
Customer will have two (2) Business Days to test only the resolution to confirm the resolution efforts
addressed the Blocker Error ("Resolution Testing Period")
Upon addressing all Blocker Errors, the HxGN Connect Program is a "Production Ready System." A
Production Ready System signifies completion of all configuration and testing Tasks.
Task Deliverables
• Response to Blocker Errors
Task Prerequisites
• The following items must be completed prior to beginning this Task.
/�
User Acceptance Testing Task
Task Assumptions
•
None I�
Hexagon Team Participation and Responsibilities
• Hexagon technical resource shall investigate and reported on the
Blocker Error Report.
• Hexagon will advise Customer once the valid Blocker Errors have been resolved in a manner
described above.
Customer Team Participation and Responsibilities
• A Customer technical member of the Core Team will promptly respond to requests for additional
information from Hexagon related to a reported Blocker Error
• The Customer will test Blocker Error resolution efforts within the Resolution Testing Period.
21
„ A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Ta s k Accepta nce Criteria
This Task will be completepwhen Hexagon has addressedr�valid Ulocker Errors and the Customer has
U either confirmed the locker Errors are resolved or the Resolution Testing Period has lapsed.
22
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
8. User Training
Task Description
The objective of this Task is to facilitate the transfer of knowledge and information necessary for the
Users to use the HxGN Connect Program for its intended purposes.
Appreciating User training is a critical element of the Project, Hexagon has provided specific online
training materials the Core Team should make available to Users. The Customer's Users should view the
online training materials to facilitate their respective use of the HxGN Connect Program depending upon
each resource's intended role and discipline. The specific User materials are identified below depending
on the HxGN Connect Program components purchased. Customer may have its Users view the online
training materials as many times as desired during the Project. The Customer may start User training at
any point in the Project. It is recommended that Customer develop its own training program, including, but
not limited to: creating a training plan suitable for its needs and leveraging the Hexagon online training
materials and Documentation to ensure its Users have acquired the necessary knowledge and are in a
position to use the HxGN Connect Program. The Customer is solely responsible for training its Users. The
Customer shall complete its User Training (see Attachment D) no later than forty (40) Business Days after
IOC Completion ("User Training Period").
Task Prerequisites and As s urn ptions
• The following items must be complete prior to beginning this task.
Project Kickoff Meeting Task
Hexagon Team Participation and Responsibilities
• None
Customer Team Participation and Res p on s ibilities
• Customer shall disseminate User training materials to its Users.
• Customer shall/�complete User training within the User Training Period.
Task Acceptance Criteria
This Task is complete upon the earlier of: (i) the Customer Project Manager reporting the Customer's
Users have completed User Training or (ii) the User Training Period has lapsed.
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
9. System Availability
Task Description
This Task reflects the final Task within the Project.2 Customizing the HxGN Connect user interface, data
sharing options, and workflows can be performed directly in the HxGN Connect production environment.
Interfaces to external systems or data sources that will provide data to the HxGN Connect system should
first be implemented and tested in the HxGN Connect Dev environment (if purchased) to ensure their
proper operation before implementing in the HxGN Connect production environment.
The purpose of this Task is to replicate those interfaces in the HxGN Connect production environment (or
just redirect the interfaces to the production environment) in preparation for production use of HxGN
Connect. If any user interface configurations were created in the Dev environment, it is the Customer's
responsibility to replicate or perform those in the HxGN Connect production environment prior to
completing System Availability. A cursory test will be performed as part of this process to ensure the
Interfaces are functioning in the production environment.
Upon completion of this Task the production HxGN Connect system is ready for use. The Customer may
use the Cloud Program in production at its convenience.
Task Deliverables
•Replication of production ready interfaces in the HxGN Connect production environment.
• Cursory test of interfaces in Cloud production environment.
Task Prerequisites
Task Assumptions
• This is the final Task of the Project, and the Customer may use in production at its convenience.
Hexagon Team Participation and Responsibilities
• Hexagon resources will replicate the interfaces in the HxGN Connect production environment.
• Hexagon resources will conduct')a cursory test of the interfaces in the production environment.
Customer Team Participation and Responsibilities
•
TaskAcceptance
Acceptance Criteria
This Task is considered complete when Hexagon has replicated the Interfaces in the Cloud Production
Environment.
2 For purposes of clarity, the completion of this Task constitutes "Cloud Cutover" notwithstanding any
alternate connotation or meaning to the contrary within the Common Terms Glossary.
24
HEXAGON
Miami City Fire Rescue
Attachment A— Pricing Summary
DESCRIPTION PRICE
Total One -Time Implementation Costs $48,037
Dynamo/E-Learning (12 months) $15,000
Recurring Fee for each Year through Year Z
(Annually beginning at System Availability)
Year 1 Recurring Fee
$27,862
Year 2 Recurring Fee
$30,648
Year 3 Recurring Fee
$33,713
Year 4 Recurring Fee
$37,085
Year 5 Recurring Fee
$40,794
Year 6 Recurring Fee
$44,873
Total One Time Implementation Costs a nd_2even-Year Recurring
$278,012
Fees
BILL OF MATERIALS
5
HxGN Connect Live Share
1
HxGN Connect Interface - Incident API
1
HxGN Connect Interface - Unit API
1
HxGN Connect Tenant Access
1
HXGN Connect Interface - OnCall Dispatch - Cloud
1
Xalt - Integration Runtime for HxGN Connect Interfaces - SU
1
HxGN Connect Xalt Gateway - Subscription
4
Dynamo Curriculum HxGN Connect Ad min - cloud
6
Dynamo Curriculum HxGN Connect User - cloud
Pricing Assumptions:
The Dynamo Curriculum/E-Learning Licenses (quantity of 10) included in this pricing are for a 12-
month duration to begin once the first training licenses are provided as set forth in the statement of
work.
30, 2022March 10, 2023.
25
„ A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Attachment B — Payment Milestones
The payment milestones percentages below are only for the Cloud Consulting Services described in this
SOW.
PAYMENT MILESTONE
PAYMENT (%)
Upon Completion of Task. IOC Credentials Meeting
50%
Upon Completion of Task: System Availability
50%
For purposes of clarity, the subscription fee amount for the first year of the Cloud Program is $27,862,
and the amount for the second year of the Cloud Program is $30,648 and is due in accordance with the
Master Terms.
26
A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Attachment C — Initial Project Schedule
[will be provided to Customer at a later date]
27
4 A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Attachment D — Training Courses Curriculum
The following is a list of HxGN Connect E-Learning courses offered by Hexagon:
• Dynamo Curriculum: HxGN Connect — Admin (HXTC0007)
• Dynamo Curriculum: HxGN Connect— User (HXTC0008)
28
„ A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Attachment E — Local Application System Requirements
Recommended Specifications:
Memory: 32 GB
300 GB of space
Network: Single 1 Gb required
Windows Server 64-bit 2019 Standard or DataCenter
29
„ A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Attachment F — Functional Specifications Matrix
This matrix is intended to provide a list of all functionality HxGN Connect can perform. Please note
functionality /is only avail/able for purchased Cloud Programs that match the application listed in the bill of
materials in Attachment A.
Attachment F -
HxGN Connect Live `.
30
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Attachment G — Interface Addendum
[no custom interfaces included at this time]
31
A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Attachment H — Glossary of Terms
Capitalized terms within the SOW are defined as follows:
"Blocker Error" means a Level One Error.
"Cloud Consulting Services Order" means this Order for Cloud Consulting Services related to the
Cloud Applications identified in the HXGN Connect Program Order
"C
loud oud Program Order77 means that certain Order, which identifies the Cloud Applications and Cloud
Term, executed simultaneously with this Order. For purposes of clarity, the Cloud Program Order is
separate and distinct from the Cloud Consulting Services Order.
"Common Terms Glossary" means that certain collection of defined terms set forth at the link.
http s.//www. h e x a g o n s a fety i nfra structure . c o m/-/media /Legal/Hexagon/S I/TPS/CTG 06-2021. p d f "Core
Team" means those certain Customer resources as described in Section 6.
COTSInterfaces" means those prebuilt, product delivered Interfaces specifically identified in the Order
Document and the Interface Addendum (if any).
"Customer" means the organization that purchases and has a contract with Hexagon for the x
GN
Connect Program. A Customer may have one Tenant (i.e., one organization) or multiple Tenants. For
example, a Customer could be a police department, and it could have Tenants for each major department
within the police department. In this case it is an INTRA Agency scenario, but with multiple Tenants.
There could also be a Customer that is comprised of more than one organization.
"Customer Responsibilities" means (1) those specific tasks and obligations identified in the SOW as
being the responsibility of the Customer and (2) those obligations, not stated in the SOW, but which
would otherwise be reasonably considered as being Customer obligations and responsibilities.
"Custom Interfaces1f means those Interface(s) developed as part of the Project and specifically
identified in the Order Document and Interface Addendum (if any).
"Day"
means a calendar day.
11Documentation11 means any COTS materials describing the system or use of the system. These
materials may be delivered only in electronic format, such as online help, e-learning courses, and/or other
documentation files delivered with software. Custom versions of documentation will need to be quoted.
"FOC" means Final Operational Capability.
"GIS" means geographic information system
"Hexagon Project Manager" means the person authorized by Hexagon to coordinate and manage the
providing of Hexagon Services and Deliverables for the Project on behalf of Hexagon, in addition to being
responsible for other duties specified in the Agreement and SOW.
"Initial Project Schedule" means the initial iteration of the Project Schedule, which is contained in
Attachment C of the SOW.
"Interface Control Document" or "lCD" means a document reflecting the design and requirements of a
Custom Interface based upon the requirements set forth in the Interface Addendum.
32
4 A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
"IOC" means Initial Operating Capability.
"Network Infrastructure" means the provision of adequate network and Internet connectivity to provide
sufficient operational bandwidth for the operation of the Cloud Program in a manner consistent with the
Product System Specifications together with all industry -standard network security, monitoring, and
protection.
"Pern,i..ive Errors" means a substantially failed Test Case that would correspond to a Level Two, Level
Three, or Level Four Error (as defined in the Common Terms Glossary) if the Error occurred in a live
environment.
"P
roduction action ea y ystem1f means the earlier of. the point at which the Customer Is either satisfied
with the testing results for the Cloud Program or the resolution of all Blocker Errors reporting during UAT.
"Project Assumptions" means assumptions regarding the Project, which are listed In the SOW.
Changes in any of the assumptions will affect the scope, schedule, and/or cost of the Project.
"Project Start" means the date following mutual acceptance of the Cloud Consulting Services Order on
which Hexagon communicates to the Customer the Project shall commence.
"Project Team" means the applicable Core Team and other resources assigned to provide information or
services in connection with the Project, or applicable part thereof.
"Specifications" means those certain capabilities and functionalities as explicitly expressed In Attachment
F. To the extent there is any ambiguity as to the interpretation or meaning of a Specification, the actual
functionality exhibited in the COTS Software shall control.
"Standard Interfaces7f means those Interfaces specifically identified in the Interface Addendum If any).
"Subject Matter Expert" or "SME" means a person(s) who has particular knowledge about a specific
topic(s).
"System Administrator(s)" means a person or persons having the appropriate education, training,
and/or experience in information technology to provide first tier support of the System.
"Task Prerequisites" means those events, Deliverables, or accomplishments that are required to occur
prior to the commencement of the applicable Task, except as may otherwise be agreed by Hexagon.
"Tenant" means an organization or collection of organizations that is authorized to use HxGN Connect
and is subject to the applicable provisions of the Master Terms. The Tenant need not be synonymous
with the Customer,
"Updated Initial Project Schedule" means the Initial Project Schedule updated by the Parties' Project
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Attachment I — Reserved
34
A HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Attachment J — Onboarding Worksheet
The information provided on this worksheet is required to establish a Customer Tenant account in HxGN
Connect. Once the Tenant account is created, the person(s) designated as the system administrator can
modify this information as needed in HxGN Connect.
Tenant Name.
HxGN Connect application.
Example. Phoenix Public Works Dept
Azure location. for Azure commercial use or Azure Government (U.S. only)
Location.
City
State
Country
Primary Administrator email address.
The email address of the person designated as the
primary system administrator for the HxGN Connect
Tenant account.
Industries — Identify the industry most closely associated with your organization
Government
Private and Non -Profits
Mayor's office _ Hospital
Traffic dept Public Works
Public Safety
EMS/Ambulance
Fire Dept
Highway Patrol
Police Agency
Sheriff
Transit Company
Utility Company
35
HEXAGON
Miami City Fire Rescue
HxGN Connect Cloud Consulting Services
Attachment K — Cloud Service Schedule
PDF
PDF
PDF
PDF
HCN1300-CSS-HxGN HCN1308-CSS-HxGN HCN1307-CSS-HxGN HCN1303-CSS-HxGN
36
HEXAGON
City of Miami Department of Fire Rescue
Statement of Work
for
HxGN OriiCaii Dispatch
Cloud Hosted Implementation
PRESENTED BY:
Trent Lowe
Regional Sales Manager
Hexagon Safety, Infrastructure, & Geospatial division
305 Intergraph Way
Madison, AL 35758 USA
772-559-6489
trent.loweghexagon.com
Ai.igi.ist 15, 2022
HEXAGON
TABLE OF CONTENTS
Introduction 5
Purpose 5
Project Outline 6
Cloud Program Functionality & Support
Project Governance 6
Customer Core Teams) 7
Core Team Roles and Responsibilities 7
Dispatch Core Team 7
Mobile Core Team 8
umptions 8
Project Tasks 12
Project Initiation 12
Initial Operating Capability (IOC) Phase 13
1. Project Kickoff Meeting 13
2. COTS Interface Questionnaire Completion 16
3. OnCall Dispatch & Mobile Unit Launch 18
4. OnCall Dispatch GIS Requirements Review 20
5. OnCall Cloud Environment Creation 21
6. IOC Completion 22
Final Operating Capability (FOC) Phase 24
7. OnCall Dispatch System Build 1 24
8. OnCall Dispatch Deployment & Response Planning Workshop 26
9. OnCall Dispatch System Build 2 28
10. Connectivity to Cloud Program 30
11. Active Directory Integration 31
12. Custom Interface Requirements Gathering 32
13. Custom Interface Development 34
14. On Premise Local Software Server Installation and Configuration35
15. OnCall Analytics Cloud Environment Creation 37
16. OnCall Dispatch GIS Consulting 38
2
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
17. OnCall Dispatch Fundamentals for bore Team 40
18. COTS Interface Product Installation and Configuration 42
19. OnCall Dispatch Configuration Consulting 1 44
20. OnCall Dispatch Configuration Consulting 2 47
21. OnCall Dispatch Configuration Consulting 3 50
22. OnCall Dispatch I Customer Rules Engine Configuration Workshop
52
23. OnCall Dispatch I Mobile Unit Configuration Consulting Session 1 54
24. OnCall Dispatch I Mobile Unit Configuration Consulting Session 2 56
25. OnCall Dispatch I Mobile Responder Configuration 58
26. Custom Interface Product Installation and Configuration 59
27. Standard Interface Product Installation and Configuration 60
28. Test Plan and Test Cases Development 61
29. Customer Functional Testing 62
30. Hexagon -Led Training 64
31. Replicate Cloud Environments 66
32. Cloud Cutover Plan 67
33. Cloud Program Readiness Review 68
34. Cloud Cutover to Production Use 70
35. Post-Cutover Support 72
Terms and Conditions 74
Approval Signatures 75
Attachment A — Pricing Summary 76
Attachment B — Payment Schedule 79
Attachment C — Initial Project Schedule 80
Attachment D — Training Curriculum 82
HXGN OnCall Dispatch I Advantage System Administrator Training
(Qty: 1) 82
HXGN Or,Call Dispatch I Advantage Train -the -Trainer (Qty: 2) 83
HXGN Or,Call Dispatch I Mobile Unit Train -the -Trainer (Qty: 2) 84
Mobile Responder Train -the -Trainer (Qty: 2) 85
HXGN Or,Call Analytics I Dispatch User Training (Qty: 1) 86
3
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
HXGN Or,Call Analytics I Dispatch System Administrator Training
(Qty: 1) 87
Attachment E — OnCall Cloud Specifications 88
Attachment F — System Configuration Diagram 89
Attachment G — CAD/Mobile Functional Specifications Matrix 90
Attachment H — Interface Descriptions 91
COTS Interfaces 91
ANI/ALI Interface 91
HxGN OnCaii Dispatch 1 CAD Link 92
HxGN OnCali Dispatch Fire Station Alerting to WestNet First -In 93
HxGN OnCaii Dispatch Deccan LiveMUM 93
HxGN OnCaii Dispatch 1 ProQA Interface 94
HxGN OnCaii Dispatch Tracker 95
Standard Interfaces 97
PLT Radio OnCall Dispatch Interface to Harris Radio 97
Dispatch Alerts OnCall Interface to Everbridge 98
Custom Interfaces 99
Telestaff 99
WebEOC 99
Attachment J — Glossary of Terms 100
Attachment K — Azure Maps Overview 103
Mapping Technology within the HxGN OnCall System 103
Azure Maps 104
Render Service 105
Route Service 105
GeoCoding Service 106
High Availability 106
Attachment L — Cloud Service Schedules 107
Attachment M — Regional Provisions 110
Attachment M-1 —CJIS Security Addendum 111
Attachment N — Deccan Li„.MUM SOW 113
4
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Introduction
This Statement of Work, including the attachments hereto, provided by Intergraph Corporation by and
through its Hexagon Safety, Infrastructure & Geospatial division ("Hexagon") to the City of Miami on
behalf of its Fire Rescue Department ("Customer") describes the Cloud Consulting Services provided by
Hexagon in connection with the initial implementation of the Dispatch Cloud Program. Hexagon will
provide the Cloud Consulting Services to facilitate implementation of the Dispatch Cloud Program as
expressly set forth in this SOW (the "Project") in exchange for payment of the amount set forth in the
Quote (which is included as Attachment A). Except as otherwise provided herein, capitalized terms shall
have the meaning set forth in the Agreement and Attachment J (Glossary of Terms) hereto.
The Software provided by Hexagon will be the HxGN OnCaii Dispatch Advantage Subsystem, inch
the OnCall Mobile Unit and OnCall Mobile Responder Cloud Applications ("HxGN OnCall Dispatch
System" or "OnCall Dispatch" or "Dispatch Cloud Program").
Purpose
The SOW describes the Cloud Consulting Services for the Dispatch Cloud Program. It documents.
Project implementation requirements, Cloud Application and Local Software functionality, the Activities
and Tasks comprising the Project, the timefra me for completion of Activities and Tasks, the
responsibilities for each Party, and the Task Acceptance Criteria.
The SOW includes and incorporates the following Attachments.
• Attachment A — Pricing Summary
• Attachment B — Payment Schedule
Attachment C — Initial Project Schedule
Attachment D — Training Curriculum
• Attachment E — OnCall Cloud Specifications
• Attachment F — System Configuration Diagram
• Attachment G — CAD/Mobile Functional Specifications Matrix
• Attachment H — Interface Descriptions
-) Attachment I — CJIS Security Addendum
Attachment J — Glossary of Terms
Attachment K — Azure Maps Overview
Attachment L — Cloud Service Schedules
Attachment M — Regional Provisions
Attachment M-1 — CJIS Security Addendum
Attachment L — Deccan LiveMUM SOW
The remainder of this section details Project assumptions that impact the Project cost, schedule and
scope, Project team composition, and Project management responsibilities.
Each Task identified in this SOW includes the following, as necessary. Task Description, Task
Deliverables, Task Prerequisites, Task Assumptions, Hexagon/Customer Team Participation and
5
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Responsibilities, and Task Acceptance Criteria. The Tasks defined in the SOW may not be listed
chronologically, and the actual Project implementation Tasks and timelines will follow the Project
Schedule, unless otherwise noted.
Project Outline
The Project consists of two (2) phases: Initial Operating Capability ("IOC") and Final Operating Capability
("FOC"). During IOC, Hexagon will create the Dispatch cloud environment. For the Project to be
successful, it is imperative the Customer timely perform its Activities. Upon IOC completion, the Dispatch
Cloud Program is in a state that it can be used to perform its primary function. dispatch emergency
resources in accordance with the Specifications. IOC Completion also marks the Cloud Program Start
Date for the Dispatch Cloud Program.
Following the completion of IOC, the system build workshops, additional configuration, interface
development and implementation, functional testing of the Cloud Applications in accordance with the
Benchmark Criteria ("Functional Testing"), training, and deployment Activities can occur. As part of FOC,
Hexagon shall provide services to support Customer Activities as expressly described in this SOW,
develop and implement identified Interfaces, perform Hexagon -led training, provide a draft Cutover plan,
and provide support to the Customer during Cloud Cutover.
Cloud Program Functionality & Support
As part of the Cloud Program(,, Hexagon shall provide Credentials/License Keys to the COTS Cloud
Applications identified in the Quote. The Dispatch Cloud Program shall have the capabilities and
functionality set forth in the Specifications, which reflects all of the functionality Hexagon is obligated to
provide in the Dispatch Cloud Program. Functional Testing shall only test for conformance to the
Specifications. Errors identified during testing are addressed in accordance with the terms related to
Cloud Services Support. Only Blocker Errors are required to be resolved prior to Cloud Cutover. This
scope does not include any Product Change Requests.
As part of the Dispatch Cloud Program, the Customer will have access to various Cloud Environments:
Production, Development, and Staging. This Project contemplates most Activities occurring in the
Development Environment. After the Dispatch Cloud Program has completed Functional Testing and
prior to Cloud Cutover, Hexagon will replicate the Development Environment to the Production
Environment and Staging Environment.
Upon issuance of the Credentials/License Keys for the Dispatch Cloud Program, the Cloud Program Start
Date shall have occurred. Consequently, Cloud Services Support will also begin at that time. The
Customer is responsible for performing its Cloud Services Support obligations as reflected in the Master
Terms for the duration of FOC and the remainder of the Cloud Term, as may be extended.
Project Governance
Hexagon will assign a Project Manager at the beginning of the Project to act as the primary point of
contact at Hexagon for the Customer and provide general oversight and guidance for the Hexagon
Project team throughout Project.
To ensure successful delivery of the Project in accordance with the schedule, regular communications
and an escalation path are necessary. Typically, all formal communications will occur between the
Hexagon Project Manager and the Customer Project Manager. Generally, each Party's Project Manager
will have, at minimum, a biweekly status conference with one another. On a monthly basis, Hexagon will
6
� A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
provide a status report reflecting completed Activities, upcoming Activities, at -risk Activities, other
pertinent matters affecting the Project, and, as necessary, an updated Project Schedule. The Customer
may propose revisions to the status report and its attachments, but it must do so within five (5) Business
Days, otherwise it is final and accepted by the parties.
Finally, on a quarterly basis, or more frequently if deemed necessary by the Parties, the Department
Sponsor for Customer, a Hexagon Director or Vice President responsible for operations, and the
Customer's Project Managers shall hold a remote executive review meeting to discuss the status of the
Project and particular challenges impacting the Project. The two senior officials for both parties shall also
serve as the escalation point for disputes arising between the Project Managers.
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 may
occur. The Hexagon Project Manager and Customer Project Manager will address and take actions to
mitigate such delays, to the extent reasonably possible.
The Hexagon Project Manager will manage the Project Schedule and provide copies of it to the Customer
as updated. From time to time and outside of the status report process described above, the Project
Managers may find an adjustment to the Project Schedule is necessary. If the adjustment is mutually
agreeable, the Hexagon Project Manager shall update the Project Schedule and it will become the then
current Project Schedule, superseding all prior Project Schedules. The Parties acknowledge that
potentially material adjustments to the Project Schedule may need to be addressed through a Change
Order due to its impact on other aspects of the Order. Unless otherwise noted between the Project
Managers, all Tasks reflected in this SOW are regarded as having completed the Task Acceptance
Process upon Cutover or commencement of a Task for which the earlier Task was a prerequisite as noted
within the SOW and/or Project Schedule.
Any provisions particular to Customer's country are specified in Attachment M — Regional Specifications,
which shall supersede any conflicting provisions provided in this SOW.
Customer Core Teams)
The Customer shall provide qualified resources to staff the Core Team (described below) to facilitate a
successful implementation of OnCall. The Core Team consists of an overall Customer project manager
who is responsible for the day-to-day coordination of Customer's Project Activities and personnel divided
amongst smaller discipline -oriented groups with particular roles and responsibilities appropriate to the
discipline. Those subdivided groups are denoted with suggested team member resources below.
Core 1 eam Roles and Responsibilities
Dispatch Core Team
Below is the defined group of Customer members responsible for decision making for the remainder of
the Public Safety Access Point ("PSAP") user group(s) regarding configuration and use of the OnCall
Dispatch solution. The "Dispatch Core Team" should consist of, at a minimum, the following resources
with the corresponding qualifications.
• 9-1-1 Cali -Taxer — This person intimately understands the process by which emergency calls for
service are answered, triaged, created in the current CAD, and sent for dispatch.
• Radio Dispatcher — This person intimately understands the structure of the PSAP, the agencies
for which it dispatches, and the methods in which dispatching occurs.
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• System Administrator (Operational) — This person is responsible for the operational
administration of the OnCall Dispatch system. Managing things like user accounts, permissions,
parameter settings, user interface layouts, units, event types, etc.
• Decision Maker (Operational) — This person has authority, either by role or designation, to make
decisions on behalf of the agency or agencies OnCall Dispatch is serving pertaining to the
configuration of OnCall.
The ideal size of the Dispatch CoreTeam is six (6) members. Under no circumstances shall the Dispatch
Core Team be larger than twelve (12) members.
Mobile Core Team
Below is the defined group of Customer members responsible for decision making for the remainder of
the field operations user group(s) regarding configuration and use of the OnCall Dispatch mobile solutions
(OnCall Mobile) including OnCall Dispatch Mobile Unit, and OnCall Dispatch Mobile Responder. The
"Mobile Core Team” should consist of, at a minimum, the following resources with the corresponding
qualifications.
• Patrol / Firefighter — This person is an active member of the patrol / operational division of the
agency. They are tasked with responding to calls for service, field -initiated activities like traffic
stops or inspections, and other duties in patrol / operations. This person should not be technology
averse. They should embrace the use of technology and seek to find ways to leverage it to their
benefit in their daily duties.
• Patrol Supervisor / Fire Supervisor — This person is an active member of the patrol /
operational division of the agency and responsible for the day-to-day supervision of a group of
patrol members or of a specific station/apparatus crew. This person is typically a rank of Sergeant
or above in law enforcement and lieutenant or above in Fire/EMS, although actual rank structure
in agencies may vary.
1 Investigations / Dete.tive / Fire Marshal — This person is an active member of the
investigations division or fire marshal's office and has primary responsibility for long-term case
work or other fire -related investigations.
• Command Staff — This person is an active member of the command staff at the agency. This
person is typically a rank of Captain or higher in law enforcement or battalion chief or higher in fire
departments, although actual rank structure in agencies may vary.
• Decision Maker — This person has authority, either by role or designation, to make decisions on
behalf of the agency or agencies OnCall Dispatch Mobile Unit or Mobile is serving pertaining to
the configuration of OnCall Dispatch mobile products.
The ideal size of the Mobile Core Team is six (6) members. Under no circumstances shall the Mobile
Core Team be larger than twelve (12) members.
It is possible to have a Mobile Core Team duplicated for different responder roles.
Project As s u m ption s
The following list of assumptions and Customer responsibilities reflect Hexagon's understanding of the
Project. Changes in any of the assumptions and Customer responsibilities will affect the scope, Project
Schedule, and/or cost of the Project.
8
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Agreement and Schedule Assumptions
• This Cloud Consulting Services Order and the Cloud Program Order have been executed by the
Customer, accepted by Hexagon, and the Customer has provided a notice to proceed, Purchase
Orders (PO) for both Orders, or written confirmation only the execution of the Orders is necessary
to bind the Customer.
• Hexagon and the Customer will review the SOW and determine a mutually agreeable date for the
Services to be performed.
• The Customer shall perform its assigned responsibilities as identified within the Initial Project
Schedule (Attachment C) and Project Schedule developed as part of Task 1 in the time allotted. If
the Customer does not reasonably comply with the Project Schedule, Hexagon is permitted with
written notice to suspend its performance on this Project and redeploy its resources on other
active projects until the parties determine a mutually agreed upon date to restart the Project. At
that time, a new Project Schedule will be provided.
• Hexagon will have timely access to the Core Team and other Customer Project staff in
accordance with the Project Schedule. Customer shall make additional personnel available on a
priority basis, as needed, to provide subject matter expertise to complete this Project
• Customer shall assign personnel to the Core Team and ensure they are actively engaged in the
Project.
• Any work and effort ascribed to Hexagon in a given Task is confined to that specific Task and
may not be used for or applied to any other Task.
• Customer shall provide Hexagon Project Manager with contact information for a Customer
resource to resolve any issues that should arise from Hexagon's access of Customer's System
during working and nonworking hours.
• Any Service Request that is set to "Waiting on Customer” (WOC) will be automatically closed
after ten (10) Business Days if the Customer does not update the SR.
• The Customer shall provide Hexagon with access to all data, documents, plans, reports,
diagrams, and analyses reasonably related to the Project or otherwise necessary to facilitate
Hexagon's performance of its Activities.
• Unless expressly stated in this SOW, all Documentation, if any, provided by Hexagon under this
SOWwill be COTS Documentation, and the Documentation will not be customized. All
Documentation delivered will be in Hexagon -approved format. Changes to Hexagon -format to
accommodate specific Customer requests may be done at Hexagon's discretion and at an
additional cost.
• Unless Hexagon and Customer mutually agree otherwise, all Documentation provided by
Hexagon will only be provided in electronic format.
• Unless otherwise stated in the Task, all Tasks will be conducted remotely.
• All Hexagon personnel performing remote tasks which require unescorted access will be
identified and properly vetted prior to commencement of those remote Activities.
• As reflected herein, Hexagon may have proposed certain Activities or Tasks be performed on
site. Hexagon and/or Customer may alternatively choose or circumstances
necessitate to have
these Activities and Tasks performed remotely. Payments due under the Quote and as specified
herein shall remain the same.
• To the extent the Customer requires Hexagon personnel undergo COVID testing prior to
performing work at Customer's facilities, the Customer would be responsible for any such costs,
which are not included in the scope and price of this Order.
9
4 A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• If the title of a Task includes the name of a Subsystem (e.g., OnCall Dispatch), that Task shall be
construed as pertaining only to that Subsystem unless expressly stated otherwise.
Hardware and Software Assumptions
• All Software will be electronically delivered.
• Local Software, if any, will be electronically delivered to the Local Environment.
• The Customer shall provide access to its Local Environment to Hexagon for the duration of the
Project.
• No Local Software will be delivered during the IOC Phase.
• The Customer shall purchase, install, and test all physical client hardware comprising the Local
Environment.
• The Customer will ensure its hardware, operating system software, and other third -party
products/environments conform with Attachment E. OnCall Dispatch Specifications and
Attachment F. System Configuration Diagram. Deviations from Attachments E and F will not be
considered due to the critical nature of the software supported by these systems.
• Hexagon and the Customer will test the final system hardware configuration to ensure
conformance with Attachment F. System Configuration Diagram and Attachment E. OnCall
Dispatch Specifications.
• Customer shall purchase all applicable operating systems and software in the Local Environment,
including, but not limited to, client workstations, and ensure such operating systems and software
meet the minimum requirements as defined in Attachment E Cloud Application System
Requirements.
• Customer shall purchase, install, configure, and administer its Network Infrastructure, including,
but not limited to, its WAN/LAN and wireless infrastructure. Customer's wireless infrastructure
shall be the same for all agencies and meet minimum bandwidth requirements as stated in
Attachments E and E.
• Customer shall be responsible for the wired and wireless connectivity between servers/clients and
clients/clients and with the Cloud Applications.
• Customer shall be responsible for, and purchase and maintain if necessary, any hardware and/or
third -party software necessary for implementing interfaces.
• Except as specified in this SOW, including Attachment A. Pricing Summary, Hexagon is not
required to provide any additional Software customizations, custom forms, forms modifications,
third -party software, custom interfaces, or custom reports.
• To the extent the Customer desires to use the Dispatch Cloud Program or other deliverables
provided herein in a manner or in combination with software or hardware that is not certified or
recommended by Hexagon, then the Customer shall be solely responsible for such use. Hexagon
shall not be responsible for the correction of any Errors, reduced performance, compromised
functionality, or other unintended consequences arising from such use. The Customer also shall
not withhold acceptance of any Task or the Cloud Program due to such use.
• Customer has reviewed the SOW and acknowledges and agrees Software Requirements: (i)
represents all the functionality required of the System, and (ii) is the only functionality that is
required to be delivered under this SOW.
10
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
System Access/CJ IS Assumptions
• The Cloud Program shall store data (in either transit or at rest) in the Cloud Environment, which is
within Microsoft Azure Government Cloud. Customer is solely responsible for (i) assuring it is
permitted by appropriate State agencies to transmit CJI and store data (in either transit or at rest)
in the Cloud Environment and (ii) otherwise complying with and ensuring this Project and the
Cloud Program to be provided does not violate applicable State CJIS policies.
• Depending upon the Customer's jurisdiction, additional security guidelines and assumptions are
provided in Attachment M.
Customer consents to Hexagon's inspection and use of Customer's data and systems, including,
but not limited to, log files and databases, for the limited purpose of providing the Cloud Services
and Cloud Consulting Services.
• In addition to tools provided by Microsoft Azure, SecureLink is the remote access solution used by
Hexagon. If Customer desires for Hexagon to utilize an alternate method and/or process for
remotely working on the Cloud Program, such alternate method and/or process shall be mutually
agreed upon prior to this SOW being executed. Such alternate method and/or process may impact
the original level of effort and Project Schedule quoted for this upgrade, which in turn may require
a Change Order to modify.
• Customer shall provide unrestricted system and VPN access via SecureLink to Hexagon
developers and implementers who will need to have access to multiple infrastructure platforms at
the same time. The Customer shall provide Hexagon personnel individualized system access
credentials and allow Hexagon authorized resources VPN access twenty-four (24) hours a day,
seven (7) days a week for the duration of the Project.
• Customer shall provide external VPN access while on -site to access various Hexagon resource
libraries.
• After completion of this Project, Hexagon will VPN using SecureLink into the live System only at
Customer's request and will follow Customer's required VPN access procedures.
Third -Party Assumptions
• Customer shall schedule and coordinate third -party technical resources with the skills necessary
to perform and/or support all Customer Responsibilities, respond to Hexagon requests, and
support the testing of interfaces, as required. Customer shall schedule and coordinate third -party
technical resources in such a way as to ensure that a negative impact to the overall Project
Schedule does not occur.
• Customer shall maintain, in good working order, all third -party systems which will integrate with
Hexagon software or on which the Hexagon software depends as part of this Project except for
the Third -Party Software included as part of the Cloud Program and provided thereunder.
• Customer shall be responsible for the operation and timely availability of external systems or third -
party software necessary for the execution of the Project.
• If a delay in the Project is caused by a third -party vendor, Hexagon services not covered in this
SOWmay be required at additional costs.
• Customer may use any supported third -party mapping provider for GIS information within the
Dispatch Cloud Program during this Project (see Attachment K). It is the Customer's responsibility
to provide this. Alternatively, the Customer can use the default map, which is Azure Maps.
11
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Project Tasks
Project Initiation
Prior to the Kickoff Meeting and after execution of this SOW or Order, the Hexagon Project Manager will
contact the Customer Project Manager to identify the Project Start date and coordinate scheduling the
Kickoff Meeting. For the Project to be successful, the following initial Activities must be performed before
any Tasks occur.
•
Schedule the kickoff meeting,
Identify the Project Start date,
Create a detailed agenda describing the goals of the kickoff meeting,
Discuss any mitigating factors that could affect the Project (e.g., scheduling conflicts,
communication factors, and other risk factors),
Schedule a conference call before the kickoff to go over the kickoff agenda,
available
for kickoff, and
Hexagon's Project Manager will prepare kickoff materials.
Hexagon's Project Manager shall have updated the Initial Project Schedule and provide the draft
Updated Initial Project Schedule and sent a copy to the Customer Project Manager for review
prior to the Kickoff meeting.
12
HEXAGON
Miami City Fire Rescoe
Hosted OnCall Dispatch Implementation
Initial Operating Capability (IOC) Phase
1. Project Kickoff Meeting
Task Description
The objective of this Task is to discuss and address questions regarding Project Assumptions, discuss
the updated Initial Project Schedule and agree to it at the meeting or shortly thereafter, and all
requirements are understood prior to beginning any significant work. A meeting for Project Kickoff will be
held after the SOW has been fully executed. The Project Kickoff meeting will be scheduled by each
party's Project Manager as part of Project Initiation Activities.
Prior to the Kickoff Meeting and after written acceptance of the Agreement, the Hexagon Project Manager
will contact the Customer Project Manager to identify the Project Start date and coordinate scheduling the
Kickoff Meeting. The Project Kickoff Meeting shall last no more than one (1) Business Day.
During this Task, the Parties shall confirm the updated Initial Project Schedule as updated by the
Hexagon Project Manager. The resulting updated Initial Project Schedule shall be substantially similar in
durations as that provided within Attachment C. Prior to the Project Kickoff Meeting Task, the Customer
Project Manager shall have reviewed the updated Initial Project Schedule and be in a position to
succinctly identify any needed changes understanding material extensions of the Initial Project Schedule
may require additional Hexagon Services to be added via a Change Order. Once the list of changes has
been made to the updated Initial Project Schedule by the Hexagon Project Manager, the Hexagon Project
Manager will thereafter provide the Project Schedule to the Customer Project Manager. From time to
time, the Parties' Project Managers may modify the Project Schedule upon mutual written consent or
upon transmission of an updated Project Schedule to the Customer Project Manager as part of a status
report and the Customer Project Manager offers no objection to the updated Project Schedule within five
(5) Business Days thereafter.
At the Project Kickoff Meeting, the Customer shall provide: (i) contact information for all members of its
Core Team and Executive/Departmental Sponsor, (ii) proposed alterations to the updated Initial Project
Schedule, (iii) contact information for any third -party vendors which OnCall will integrate as contemplated
in Attachment H, and (iv) identify to Hexagon any perceived concerns or risks with the Project. During the
Project Kickoff Meeting, Hexagon shall provide template COTS Interface Questionnaires for Customer
completion prior to required Tasks.
Task Deliverables
• Kickoff meeting agenda
• Project Schedule
• Kickoff meeting (minutes, to include identified risks and action items
• COTS Interface Questionnaire
Task Prerequisites
• Hexagon Project Manager has verbally communicated with the Customer to (i) identify the Project
Start date and (ii) coordinate a date for the Project Kickoff Meeting.
• Customer has a
• The Core Team
13
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• Customer is in compliance with Attachment K - GIS Requirements.
Task Assumptions
• The Hexagon Project Manager will conduct the kickoff.
• This task will be conducted on site.
may participate remotely.
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Review the Project organization, roles, and responsibilities with the Customer;
• Conduct an overview of the Project including a review of the SOW to verify all aspects of the
Project approach;
• Review the draft Updated Initial Project Schedule and adjust the Updated Initial Project Schedule
as needed and mutually agree upon it with Customer;
• Work with Customer to identify and document any potential Project risks;
• Provide meeting minutes that document risks and action items that affect the Project Schedule,
resources, and/or the SOW;
• Inform the Customer of VPN requirements for Project implementation and continued System
maintenance;
• Review of delivery methodology;
• Establish status reporting requirements; and
• Provide overview of Standard Interfaces being delivered as part of the Project as identified in
Attachment H.
Customer Team Participation and Responsibilities
Customer shall.
• Review the SOW;
• Ensure its Core Teams attend the applicable portions of the Kickoff Meeting;
• Provide SMEs and any other resources as recommended by the Customer and Hexagon Project
Managers;
• Provide Hexagon with VPN access and individualized user accounts to Customer's System as
appropriate for this Project and continued software maintenance;
Have previously reviewed the Updated Initial Project Schedule and work with Hexagon to finalize
the Updated Initial Project Schedule;
• Provide location and logistical support for Kickoff Meeting; and
• Designate and prepare workspace for Hexagon personnel.
14
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Ta s k Flcce pta nce Criteria
This Task is complete at the conclusion of the Project Kickoff Meeting and delivery of the Project Kickoff
meeting minutes to Customer.
15
d A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
2. COTS Interface Questionnaire Completion
Task Description
Hexagon will provide an interface questionnaire ("COTS Interface Questionnaire") to the Customer to
complete. The Customer shall complete the COTS Interface Questionnaire within five (5) Business Days
of receipt ('COTS Interface Review Period") whereupon Hexagon will be able to install the COTS
Interface and configure it based upon the information provided in the COTS Interface Questionnaire
subject to the functionality and features within the COTS version of the Interface.
The following Interfaces are regarded as the COTS Interfaces (collectively, "COTS Interfaces"):
• ANI/ALI Interface (included with HxGN OnCaii Dispatch I Advantage)
• HxGN OnCall Dispatch CAD Link to ESO SafetyPAD and ESO FRMS
• HxGN OnCaii Dispatch Fire Station Alerting to WestN et First -In
• HxGN OnCall Dispatch I Deccan LiveMUM
• HxGN OnCaii Dispatch I ProQA Interface
• HxGN OnCaii Dispatch I Tracker
• OnCaii Dispatch I Mobile Responder
For more information on, parameters of, and assumptions underlying the COTS Interfaces, see
Attachment H, Interface Descriptions.
Task Deliverables
• Completed COTS Interface Questionnaires
Task Prerequisites
COTSInterface Questionnaires to Customer.
Task Assumptions
• The Customer will direct its third -party vendors to provide any API or specification documentation
required to configure the COTS Interfaces.
• If required, all NDAs between Hexagon and third parties will be executed and current. The
Customer will exercise all reasonable efforts to facilitate its third -party vendors reasonable
cooperation with this requirement.
• The Customer will exercise all reasonable efforts to facilitate cooperation and information from its
third -party vendors and/or state agency as reasonably necessary for the configuration, testing,
and Cutover of the COTS Interfaces.
• Unless otherwise provided in the Specifications, only COTS versions of the COTS Interfaces will
be provided and configured.
• The Customer shall be responsible for underlying requirements pertaining to its third -party
systems as described in Attachment H.
16
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• The ANI/ALI interface component of the OnCall Dispatch System will provide the interface to an
ANI/ALI controller. It will accept ANI/ALI packets containing ASCII data via an Ethernet Network
(TCP/IP) or a Serial COM Port connection. If the Customer's ANI/ALI feed is via Serial COM Port
the Customer will need to obtain an IP to Serial device.
Hexagon Team Participation and Responsibilities
Hexagon shall.• (�
Review completed COTS Interface Questionnaires.
Customer Team Participation and Responsibilities
Customer shall.
• Promptly review, complete, and submit COTS Interface Questionnaires and provide comments,
questions, Criteria
approval within the COTS Interface Review Period.
Task Flcce pta nce Criteria (�
This Task is complete upon Hexagon providing the COTS Interface Questionnaires and reviewing
Customer's responses it provided within the COTS Interface Review Period.
17
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
3. OnCall Dispatch & Mobile lobile Unit Launch
Task Description
OnCall Dispatch & Mobile Unit Launch ("Launch Workshop") is a workshop style session lasting up to
three (3) Business Days that is intended to educate Dispatch and Mobile Core Team members on the
features and functionality of OnCall Dispatch and OnCall Dispatch Mobile Unit to support the collection
and importation of data and information that CAD requires to execute its primary functions ("CAD Static
Data"). During the Launch Workshop, Hexagon will provide limited instruction on the use of OnCall
Dispatch and OnCall Dispatch Mobile Unit illustrating how the CAD Static Data elements identified below
are utilized in the Subsystem. The Launch Workshop is limited in scope to facilitate upcoming System
Build Tasks, it is not intended or designed to provide a comprehensive overview or instruction of the
Subsystem. Such instruction and training will be provided at later stages of the Project. During the Launch
Workshop, Hexagon shall provide to Customer OnCall Dispatch Static Data Collection Spreadsheet(s) to
facilitate Customer's collection and eventual importation of CAD Static Data in subsequent Tasks.
Task Deliverables:
• OnCall Dispatch Static Data collection spreadsheets
Task Prerequisites
• Project Kickoff Meeting Task is complete.
• Customer Dispatch Core Team is identified.
• Customer Mobile Core Team is identified.
Task Assumptions &
• Launch Workshop is conducted using a Hexagon -provided default OnCall Dispatch Mobile Unit
environment.
• Hexagon responsibilities will be executed on site at a Facility.
• If the Customer's policies preclude connecting Hexagon -owned equipment to their network, a
computer workstation for use by Hexagon for presenting content shall be made available.
• Each Customer attendee will have access to their own Project Workstation.
• The Launch Workshop shall last no more than three (3) Business Days.
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Provide limited, focused instruction on the use of OnCall Dispatch, OnCall Mobile Unit, and
OnCall Dispatch Administrator, on functional areas that utilize or display the following CAD Static
Data elements.
Units
Event Types
Personnel/User Accounts
Beats/Station Areas
Dispatch Groups
Number Formats (event, case, etc.)
18
4 A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Rotational Services (towing, ambulance, lock
smith, etc.)
Vehicles
Provide the Customer with Microsoft Excel based data collection spreadsheets ("OnCall Dispatch
Static Data Collection Spreadsheets") to be used in assembling the CAD Static Data elements.
Custorner Participation and Responsibilities
Customer shall.
• Provide a facility according to the requirements provided in Task Assumptions,
• Ensure appropriate members of the Dispatch Core Team and Mobile Core Team attend the
workshop for the entire Launch Workshop,
• Ensure each attendee has a Project Workstation, and
• Participate in discussions and engage with the Hexagon team member.
Task Accepta nce Criteria
This Task is complete upon conclusion of the Launch Workshop and the delivery of the OnCall Dispatch
Static Data Collection Spreadsheets.
19
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
4. OnCall Dispatch GIS Requirements Review
Task Description
This Task introduces the Customer GIS members to the address locator services, routing services, map
display services, and deployment polygonsrequiredto be provided by the Customer for use by OnCall
Dispatch. Over the course of up to one (1) Business Day, Hexagon will present on the following topics
during the "OnCall Dispatch GIS Requirements Review:"
• Optional GIS data elements that can be used by OnCall Dispatch
This session will use Hexagon -provided GIS data for the purposes of discussion. Hexagon will use its
equipment to conduct any demonstrations that may occur. Customer attendance should be limited tom GIS
professionals with responsibility for the creation and maintenance of Customer GIS data. Up to six (6)
Customer personnel may attend. Map content will be provided to the OnCall Dispatch system through
map layers and web services to be provided by the Customer.
Task Deliverables
• OnCa11 Dispatch GIS Requirements Review
Task Prerequisites
Task Assumptions
• Appropriate facilities have been identified to support the number of attendees (if co -located),
including an LCD projector and a projection screen.
Hexagon Team Participation and Responsibilities
Hexagon shall:
• Conduct the OnCall Dispatch GIS Requirements Review.
Customer Team Participation and Responsibilities
Customer shall:
• Ensure its GIS/Map Administrator is involved throughout this Task,
• Supply facilities, including an LCD projector and a projection screen;
• Designate and assign no more than four (4) Customer mapping/GIS personnel to attend the
entire workshop. Two (2) additional people may attend as observers/auditors, and
• Ensure that all appropriate Customer GIS professionals are sufficiently trained and experienced in
GISfu n d a menials.
Task Acceptance Criteria
The Task is complete after the OnCall Dispatch GIS Requirements Review is conducted.
20
HEXAGON
5. OnCall Cloud Environment Creation
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
The objective of this Task is to create and "spin -up" the Customer's Development Environment for the
Dispatch Cloud Program.
The Development Environment will be used by Customer during the Project and serve as the basis for the
Development Cloud Environment upon Cloud Cutover. Hexagon will inform the Customer once the
applicable Development Environment for Customer has been created.
Task Prerequisites
Task Assumptions
• None
Hexagon Team Participation and Responsibilities
Hexagon shall. • Create the Cloud Environment (only Development Environment at this I T
ask) with the Dispatch
Customer Team Participation and Responsibilities
•
Accepta
Ta sk Acceptance Criteria
This Task shall be complete upon creation of the Customer's Development Environment for the Dispatch
Cloud Program.
� A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
6. IOC Completion
Task Description
This Task serves as a milestone and culmination of the previous Tasks. It is at this point in the Project
that Hexagon has created the Cloud Environment. With the completion of the foregoing Tasks and as
part of this Task, Hexagon will host a meeting with the Customer Project Manager to: (i) deliver to
Customer the Credentials//License Keys applicable to the Dispatch Cloud Program and identified in the
Quote to the Cloud Program Order and (ii) ensure the Customer Project Manager is able to access the
Cloud Program with the Cloud Credentials/License Keys ("Credentials Delivery Meeting"). The
Credentials Delivery Meeting is complete once those two objectives are achieved. Completion of this
Task also serves to mark the completion of IOC Phase.
Task Deliverables
ded within the Quote
Task Prerequisites
• /� OnCall Cloud Environment Creation task is complete.
Task Assumptions
• Customer has necessary hardware, equipment, and Network Infrastructure ready and available to
access the Cloud Program
in The Credentials Delivery Meeting is of a limited duration and only intended to cover the two topics
specified above. I�
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Host the Credentials Delivery Meeting;
• Ensure the Customer can log into the Dispatch Cloud Program to confirm connectivity, and
• Address Customer reported issues with accessing the Dispatch Cloud Program.
Customer Team Participation and Responsibilities
Customer shall.
• Attend the Credentials Delivery Meeting;
• Access the Dispatch Lloud I rogram via the Lrede ntials�License I\eys provided during the
• Report to Hexagon verbally during the Credentials Delivery Meeting whether the Customer can
access the Dispatch Cloud Program or identify issues encountered in accessing the Dispatch
Cloud Program, and
22
4 A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
If Customer encounters issues in accessing the Dispatch Cloud Program, it will work
collaboratively with Hexagon to troubleshoot and address the issue until resolution.
/�
Ta s k /Ace pta nce Criteria
This Task is complete when Hexagon has delivered the Dispatch Cloud Program Credentials/License
Keys to Customer and confirmed the Customer is able to access the Dispatch Cloud Program.
23
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Final Operating Capabillity (FOC) Phase
7. OnCall Dispatch System Build 1
Task Description
OnCall Dispatch System Build 1 workshop ("System Build 1") builds upon the OnCall Dispatch and Mobile
Unit Launch to begin the process of populating OnCall with required static data elements. System Build 1
is the first of two (2) static data workshops and primes OnCall Dispatch with base data to support the
buildout of remaining static data elements addressed in OnCall Dispatch System Build 2.
At the commencement of System Build 1, the Customer shall have obtained information and documents
(e.g., records, operating procedures, resources, etc.) to support the eventual entry or import of the Build 1
Data Elements. For any Build 1 Data Elements not entered or imported during System Build 1, the
Customer will enter those after System Build 1 within ten (10) Business Days and prior to OnCall Dispatch
System Build 2.
During System Build 1, the focus will be on the entry and import of Build 1 Data Elements (es defined
below). System Build 1 will last no longer than three (3) Business Days. As part System Build 1, the
Customer will experience the manual entry of static data elements to provide an understanding of the
process and data relationships. Some manual entry of all static data elements is required as part of the
workshop. Bulk import of remaining data can occur after sufficient understanding of the data elements
and relationships is obtained.
Following System Build 1, OnCall Dispatch will have foundational data elements to support future build T
activities. In addition, Dispatch and Mobile Core Team members will be exposed to OnCall Dispatch
Administrator and gain understanding of its use and function.
Task Deliverables
• OnCall Dispatch System Build 1 workshop
Task Prerequisites
• OnCall Dispatch & Mobile Unit Launch Task is complete.
• Inc. Phase is complete.
• OnCal(l` Dispatch GIST Consulting I ask is complete.
• Initial VIS services published and configured for use by OnCall Dispatch:
Map display
• (Routing
Geocoding
Task Assumptions
• Hexagon responsibilities will be executed on site at a Facility.
• System Build 1 is conducted using the Customer's OnCall Dispatch environment.
• System Build 1 will last no more than three (3) Business Days.
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Hexagon Team Participation and Re s pons i bilities
Hexagon shall:
• Host System Build 1 during which, limited, focused instruction on the use of OnCall Dispatch,
OnCall Mobile Unit, and OnCall Dispatch Administrator, on functional areas that utilize or display
the following static data elements ("Build 1 Data Elements"):
• Unit Types (Patrol, Engine, etc.)
• Units
• Event Types
•
• Out -of -Service Types
Personnei/User Accounts
Beats/Station Areas
Dispatch Groups
etc.)
Number Formats (event, case, etc.)
I Known Caller Types Vehicles
• Provide the Customer with Microsoft Excel based data collection spreadsheets to be used in
assembling the Build 1 Data Elements for importation into the Dispatch Subsystem.
Customer Partici pati on and Res pen s i bilities
Customer shall:
• Ensure appropriate Dispatch and Mobile Core Team
during the System Build 1 for the entire duration,
members attend and actively participate
•
• to each attendee,
• Provide all necessary information and documents to facilitate importation of Build 1 Data
Elements at the outset of System Build 1, and
• Participate in discussions and engage with the Hexagon team member.
Task Acce pta nce Criteria
This Task is complete upon conclusion of System Build 1.
25
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
8. OnCall Dispatch Deployment & Response Planning Workshop
Task Description
This workshop, "Deployment and Response Planning Workshop," builds upon System Build 1 to begin
the process of creating the deployment and response planning components of OnCall Dispatch. The
Deployment and Response Planning Workshop is intended to facilitate importation with deployment data
necessary to successfully execute the OnCall Dispatch System Build 2 and the subsequent OnCall
Dispatch configuration workshops.
As part of the Deployment and Response Planning Workshop, Customer will be taught about the OnCall
Dispatch unit recommendation model, how to build response plans, and briefed on the parameters which
control how OnCall Dispatch processes response plans. The Deployment and Response Planning
Workshop shall last no longer than three (3) Business Days. At the outset of Deployment and Response
Planning Workshop, the Customer must have obtained and have necessary information and documents
to facilitate eventual creation of the Deployment Plans, and Response Plans (as defined below). The
Deployment and Response Planning Workshop is intended to provide the Customer experience on how
to build Deployment Plans and Response Plans, it is not expected or intended that all such Deployment
Plans and Response Plans will be completed during the Deployment and Response Planning Workshop.
The Customer will be expected to complete the build of any necessary Deployment Plans and Response
Plans within ten (10) Business Days prior to the commencement of System Build 2.
Task Deliverables
• OnCall Dispatch Deployment & Response Planning Workshop
Task Prerequisites
• OnCall Dispatch System Build 1 Task is complete.
• Necessary Build 1 Data Elements have been imported into the Dispatch Subsystem to facilitate
/�
the build of Deployment Plans and Response Plans.
Task Assumptions
• Hexagon responsibilities will be executed on site at a Facility.
Workshop is conducted using the Customer's OnCall environment.
• Deployment and Response Planning Workshop shall last no longer than (3) Business Days.
Hexagon Tean, Participation and Responsibilities
Hexagon shall:
• Provide formal instruction on the OnCall Dispatch deployment model ("Deployment Plans"):
• Deployment plans
Emergency Service Zones p
Beats Backup Beats
Dispatch Groups
• Provide formal instruction on the OnCall Dispatch response planning model ("Response Plans"):
„ A HEXAGON
Miami City Fire Rescue
Hosted 0nCall Dispatch Implementation
Recommend unit service.
Number of recommend unit services needed
Recommend search area
Recommend method (beats, street network, closest)
Recommend unit parameters
Response plans.
Requirements
Conditions
Nested plans
• Support Customer buildout of deployment and response plans.
Customer Participation and Responsibilities
Customer shall.
•
for each attendee,
• Ensure appropriate Dispatch and Mobile Core Team members attend and actively participate
during the Deployment and Response Workshop over the entire duration,
• Bring maps, documents, or other materials that detail the agency deployment model(s) and
pDe ploy ment Plans,
• Bring materials that document or detail the agency unit recommendation model(s) and Response
Plans; a n d
• Build deployment and response plans with Hexagon guidance during the Deployment and
Response Planning Workshop and independently following Deployment and Response Planning
Workshop.
Ta s k Acce pta nce Criteria
This Task is complete at the conclusion of the Deployment and Response Planning Workshop.
27
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
9. OnCall Dispatch System Build 2
Task Description
This OnCall Dispatch System Build 2 Workshop ("System Build 2") finalizes Hexagon -led system build
activities and completes the enablement of the Dispatch and Mobile Core Teams to continue build related
activities for the remainder ofthe project. The same Dispatch and Mobile Core Team members who
1 participated in System Build and the Deployment and Response Planning Workshop shall attend
System Build 2 to ensure continuity of decisions and facilitating continuing to build upon previous
workshops.
During System Build 2, deployment polygons will be loaded into the Subsystem. Additionally, System
Build 2 focuses on reviewing data entered into the Subsystem for level of completion and analyzing
whether data was entered imported correctly. System Build 2 shall last no longer than three (3) Business
Days. While certain updates or modifications to the static data may occur during the Configuration
Phase, the Customer shall upload all of its static data within ten (10) Business Days following System
Build 2.
Task Deliverables
• OnCall Dispatch System Build 2 Workshop
Task Prerequisites I�
• OnCall Dispatch Deployment & Response Planning Worksho
Task Assumptions
• Hexagon responsibilities will be executed on site at a Facility.
• Workshop is conducted using the Customer's OnCall environment.
• System Build 2 will last no more than three (3) Business Days.
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Load deployment polygons into the OnCall Dispatch database,
• Provide support to Customer teams while continuing the system build efforts;
• Review with the Customer teams the data entered to date for accuracy and level of completion,
and
• Provide feedback on the build progress and areas that need focus or attention.
Customer Participation and Responsibilities
Customer shall.
• Provide a Project Workstation for each attendee, 1�
• Ensure past participants in System Build 1 and Deployment and Response Workshop attend
System Build 2 for the entire duration,
28
4 A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• Provide at the outset of System Build 2 all necessary information and documents to. make
deployment polygons and facilitate review of Build 1 Data Elements, Response Planning
Parameters, and Deployment Parameters;
• Participate in discussions and engage with the Hexagon team member;
• Complete any outstanding entry or import of static data within ten (10) Business Days following
/�
the end of System Build 2.
Task Acce pta nce Criteria
This Task is complete upon conclusion of System Build 2.
29
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
10. Connectivity to Cloud Progra m
Task Description
This task is a shared responsibility between the Customer and Hexagon. The Customer is responsible for
the connectivity between the Customer on -premise infrastructure and the Hexagon Azure VPN gateway.
The Customer is also responsible for setting up additional site to site tunnels where multiple agencies are
involved or other alternatives that will facilitate these types of connections. Hexagon will provide the VPN
gateway and will collaborate with the Customer to define acceptable private IPs. The Customer is
responsible for ensuring the Customer VPN hardware conforms to the Azure hardware requirements for
connecting to their cloud platform.
Task Deliverables
• The ability for the Customer to connect to Azure is confirmed by accessing the Hexagon OnCall
application hosted on Azure.
Task Prerequisites
• IOC Phase is complete.
Task Assumptions
• The shared key for the VPN tunnel encryption has been shared between the Customer and
Hexagon. I�
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Set up the initial meeting between the Customer IT teams and Hexagon technicians;
• Provide network diagrams relevant to supporting communications between the Customer site
and the Hexagon VPN gateway; and
• Collaborate with the Customer IT representatives on design connectivity details such as VPN
configurations and IP ranges.
Customer Team Participation and Responsibilities
• Ensure appropriate Core Team members attend and actively participate in VPN connectivity
/�
meeting. /�
Ta s k Acce pta nce Criteria
This Task is complete upon the Customer confirmation of the ability to access the OnCall applications
over the configured VPN tunnel.
30
1:10
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
11.Active Directory Integration
Task Description
The Hexagon application leverages Azure Active Directory (AAD) for authentication. Leveraging the AAD
is a shared responsibility between the Customer and Hexagon. There are multiple configurations that the
Customer can leverage to connect their existing Active Directory to AAD or to use the AAD tenant directly.
Supported configurations include.
• AD sync with a password
• AD sync with a HASH
• Direct connectivity to the AAD tenant without AD sync
Task Deliverables
• AAD tenant will be created for Customer use.
Task Prerequisites
• IOC Phase is complete.
• Global Admin for AAD is identified.
Task Assumptions
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Create tenant in AAD; and
• Create AAD Admin account. l�
Customer Team Participation and Res pon sibilitie
Determine AD configuration best suited to Customer's internal requirements; and
• Confirm authentication is working.
Ta s k /Ace pta nce Criteria
This Task is complete Customer being able to authenticate using AAD when accessing the Hexagon
OnCall application hosted in Azure.
31
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
12.Custom Interface Requirements Gathering
Task Description
During this Task, Hexagon and Customer will meet via conference call to validate the assumptions and
design of each CAD Gusto m Interface identified in this SOW and Attachment H (Interface Descriptions).
This Custom Interfaces Requirements Gathering workshop is intended to contain a series of discussions
to validate the requirements and assumptions underlying the Custom Interfaces. These sessions should
include third -party vendors where appropriate. During the sessions, the specific workflow and data
requirements for each of the interfaces listed below will be discussed in detail.
The information obtained in combination with the information in Attachment H will be used to develop an
Interface Control Document for each Custom Interface. If the assumptions reflected in Attachment H
materially change, a Change Order may be appropriate. The ICDs will become the foundation for the
Custom Interface development by Hexagon. Once an ICD is mutually approved, it should only be
modified through a Change Order. The Customer shall not make any changes to and shall take
appropriate actions to prevent its third -party vendor from making substantive changes to the third -party
software that is the subject of a Custom Interface once that Custom Interface's respective ICD has been
finalized.
The following are regarded as "Custom Interfaces" as the term is defined in Attachment J of this SOW:
Tele staff
• WebEOC
For descriptions and assumptions regarding each Custom Interface listed above, please see Attachment
H: Interface Descriptions.
As it pertains to the development of the ICD, the parties shall follow the following process. After the
Customer provides the necessary information regarding the Custom Interface, Hexagon will prepare a
draft ICD for each Custom Interface. Hexagon will then provide the initial draft ICD to the Customer for-Iits
review. The Customer shall review the draft ICD and provide any feedback or comments within ten (10)
Business Days. As appropriate, Hexagon will incorporate the feedback into the ICD or advise the
Customer why certain requests could not be included (e.g. the request conflicted with Attachment H) and
finalize the ICD. Hexagon will provide the finalized ICD to the Customer for its written acknowledgement.
The Customer will provide a response within three (3) Business Days from Hexagon providing the
finalized ICD.
Task Deliverables
• Workshop meeting minutes, to include notes on the specific workflow and data requirements for
each custom interface proposed
• ICD documents
Task Prerequisites
Task Ass urn ptions
• The Customer will coordinate interactions with the third -party vendors, including obtaining and
providing any API or specification documentation required to develop the proposed interfaces.
32
� A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• If required, all NDAs between Hexagon and third parties will be executed and current. Customer
is responsible for facilitating its third -party vendors reasonable cooperation with this requirement.
• The Customer is responsible for obtaining cooperation and information from its third -party
vendors and/or state agency as reasonably necessary for the development, testing, and cutover
of the interfaces.
Hexagon Team Participation and Ices ponsi bi l hies
Hexagon shall.
• Lead the interface requirements gathering process and track outstanding items requiring
resolution;
• Confer with Customer and third -party points of contact to gather information required to develop
ICDs;
• Validate the third -party points of contact are appropriate sources of information necessary to
develop ICD;
• Mutually agree with the third -party vendors on the operational and technical interface
requirements;
• Gather all available interface data detailed schema, protocols, and specifications, as needed
• Prepare draft ICDs and submit to Customer for feedback;
• Incorporate Customer feedback into draft ICDs;
• Finalize ICDs for Customer review and approval; and
• Manage the approved ICDs consistent with the change control process.
Customer Team Participation and Responsibilities
Customer shall.
• Identify and set up appropriate facilities;
• Provide points of contacts who are knowledgeable of the workflow and data requirements for
Customer hardware and software components with which the Custom Interfaces will interact;
• Provide or have available all necessary information during the workshop to facilitate the creation
of the ICD;
• Promptlyreviewall draft ICD submissions and provide comments, questions, or approval within
ten (10) Business Days of receipt; and
• Agree to and sign the ICDs before any development work can begin. Failure to approve in a
timely manner/�may impact Project Schedule and incur additional cost.
Ta s k /'lcce pta nce Criteria
This Task is complete upon completion of all ICDs and execution of the ICDs by both Hexagon and the
Customer.
33
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
13.Custom Interface Development
Task Description
During this Task, Hexagon will develop the (' Custom Interfaces based upon the ICDs that were created
from the Custom Interface Requirements Gathering Task.
Task Deliverables
• Custom Interface documentation
Task Prerequisites
• /� Custom Interface ICDs have been executed by each Party.
Task Assumptions
• Any changes to a third -party interface developed by Hexagon that will alter the agreed -upon ICD
will have to be reflected in a mutually executed document, which may include a Change Order.
• Development of the Custom Interface shall not commence until the signed approved ICD is
returned to Hexagon. Failure to approve in a timely manner may impact project schedule and
incur additional cost.
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Develop the Custom Interfaces based upon the ICD.
Customer Team Participation and Responsibilities
Customer shall:
• Ensure SMEs are available as needed, and
• /� Obtain third( --party cooperation as reasonably requested by Hexagon.
Ta s k Accepta rice Criteria
This Task is complete when all Custom Interfaces are developed.
34
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
14.On Premise Local Software Server Installation and Configuration
Task Description
This Task is for creation and configuration of the On Premise Local Software Server VMs. It includes the
creation of the VMs, setting server names and IPs, joining them to the domain and adding the Hexagon
CAD/RMS Admin groups to the local admins groups of the servers to provide the implementers the
required access for the rest of the Project.
Task Delivers bles
• Server configuration documentation, which consists of a spreadsheet with server names, IPs and
passwords utilized Updated Visio document showing servers, applications installed, names, and
IPs
Task Prerequisites
• Customer must have available virtual environment resources for staging of project VMs
• VPN credentials and client (if needed) must be provided
Not required if Customer is
• Complete the Server name, IP Address and Service account template provided by Hexagon.
Task Assumptions
• All work being performed by Hexagon that requires physical access to the equipment will be
performed on site, and those tasks that do not require physical access may be performed
remotely at Hexagon's discretion.
• New virtual servers will be created/provided for the sole purpose of the Project defined by this
SOWand will not serve other roles.
• Access to the vCenter server via Power CLI is required by the Hexagon staff to script the creation
of the VMs. 1�
Hexagon Team Participation and Responsibilities
Hexagon shall:
• Import VM Templates to vCenter, create the VMs, assign them the required CPU, memory, and
disk space to comply with the OnCall Dispatch Specifications document,
• Assign the IP Addresses to the VMs,
a Join the VMs to the domain,
• Apply current Windows updates if Internet connectivity or access to another repository for
updates is available,
• Create and deliver the Server Configuration Documentation; and
• Provide spreadsheet with server names, IPs, and passwords utilized.
Customer Team Participation and Ices pon s ibilities
Customer shall.
35
� A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• Provide domain level credentials for the vCenter server and Join servers to the domain,
• Provide assistance with resolving issues related to network connectivity and/or remote access,
and
• Answer other configuration questions as needed.
Task Acceptance Criteria
This Task is complete when the Server Configuration Documentation has been delivered to Customer.
36
� A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
15.OnCaii Analytics Cloud Environment Creation
Task Description.
The objective of this Task is to create and "spin -up" the Customer's Development Environment for the
Analytics Cloud Program.
The Development Environment will be used by Customer during the Project and serve as the basis for the
Development Cloud Environment upon Cloud Cutover. Hexagon will inform the Customer once the
applicable Development Environment for Customer has been created.
Task Prerequisites
Task Assumptions
• None
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Create the Cloud Environment (only Development Environment at this Task) with the Analytics
Cloud Program identified in the1')Cloud Program Order, which will be used for subsequent Tasks.
Customer Team Participation and Responsibilities
• /� None.
Task Acceptance Criteria
This Task shall be complete upon creation of the Customer's Development Environment for the Analytics
Cloud Program.
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
16. OnCall Dispatch GIS Consulting
Task Description
Acentral feature of OnCall Dispatch is interoperation and use of a map source in OnCall Dispatch. The
Customer may use whichever map provider they choose, subject to Attachment K. The objective of this
Task is to collaborate with the Customer's GIS Administrator regarding use of the Customer -provided
map within OnCall Dispatch and management of the source map.
Over the course of up to three (3) consecutive weeks ("GIS Consulting Period") a Hexagon technical
resource will host meetings with the Customer GIS Administrator and any other interested Customer
SMEs, which in the aggregate shall last no more than twenty-four (24) Business Hours ("GIS Meeting
Time"). The OnCall Dispatch GIS Consulting is intended to be a collaborative session and for Hexagon
and the Customer GIS Administrator to discuss use of the map within OnCall Dispatch and management
of the map in the context of OnCall Dispatch. As time permits, the parties can discuss other GIS related
topics.
To facilitate a productive session, the Customer GIS Administrator, at a minimum, should have
participated in the OnCall Dispatch GIS Requirements Review. The Customer shall also have complied
with the mapping requirements prior to this Task.
As a result of the sessions, the Customer's GIS Administrator will have been provided additional insight
and information on how to manage and use the map in connection with OnCall Dispatch. For purposes of
clarity, these sessions are not intended to result in configuration or modification of Customer's source
map. The Customer may configure the map at its discretion up to the commencement of Functional
Testing. At the commencement of Functional Testing, the Customer shall refrain from making any
modification or configurations to the map until after System Cutover.
Task Prerequisites
• OnCall Dispatch GIS Requirements Review Task is complete.
Task Assumptions
• The Customer GIS Administrator has sufficient authority to make decisions about the use,
configuration, and integration of the source map.
• Hexagon will not provide training or services specific to Esri software.
Hexagon Team Participation and Re s pon s i bi Iities
Hexagon shall.
• Conduct the GIS Consulting through a Hexagon technical resource.
Customer Team Participation and Res pon s ib ilities
Customer shall.
• Manage and make any desired configurations to the Customer -provided map, and
• Ensure appropriate GIS resources attend GIS consulting ses
on(s).
38
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Ta s K Accepta nce Criteria
GIS Meeting Time or (ii) end of the GIS
39
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
17.OnCaii Dispatch Fundamentals for Core Team
Task Description
The OnCall Dispatch Fundamentals for Core Team course is presented directly to Dispatch and Mobile
Core Team personnel to provide complete instruction on they use of the OnCall Dispatch and Mobile Unit
applications. The course shall last no longer than three (3) Business Days. This course is intended to
instruct the Dispatch and Mobile Core Teams with the features of OnCall Dispatch and Mobile Unit,
including event processing and dispatching, map utilization, and inquiries. The following major topics will
be reviewed, as applicable.
HxGN OnCall Dispatch I Advantage functions.
•
• Map View Control
HxGN OnCall Dispatch I Mobile Unit functions.
• Accessing the system
• Event Updates
• Inquiries • Unit Status
• Messaging • Messaging
•
•
Task Deliverables
• OnCall Dispatch Fundamentals for Core Team course
Task Prerequisites
• Completion by Customer attendees of an introductory Microsoft Windows course or equivalent
knowledge and familiarity with the Microsoft Windows user interface.
Task Assumptions
• Hexagon responsibilities will be executed on site at a Facility.
• The course shall last no longer than three (3) Business Days.
Hexagon Team Participation and Responsibilities
Hexagon shall.
course.
Customer Team Participation and Responsibilities
Customer shall.
• Provide a Project Workstation for each attendee
40
41 HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• Ensure appropriate personnel who have attended an introductory MS Windows course, or have
comparable education, training, or experience, participate fully and collaboratively in the session,
• Designate the Dispatch and Mobile Core Team members for attendance and ensure those same
participants participate in subsequent Dispatch and Mobile configuration and testing Tasks,
▪ Provide sufficient copies of the training materials supplied by Hexagon to support all students in
the Core Team Training;
• Ensure that all training workstations and servers are operational prior to the agreed start of
training classes, and
• Provide internal training to users that are unable to attend the Hexagon -provided training.
Ta s k Acts pta nce Criteria
This Task is complete upon delivery of the OnCall Dispatch Fundamentals for Core Team course.
41
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
18.COTS Interface Product Installation and Configuration
Task Description
During this Task, Hexagon will install and unit test the COTS Interfaces in the Customer's Production
Environment. Hexagon will be able to install the COTS Interface and configure it based upon the
information provided in the COTS Interface Questionnaire subject to the functionality and features
existing within the COTS version of the COTS Interface.1 To facilitate Hexagon's implementation and
configuration of the COTS Interfaces, the Customer shall make available or provide access to all third
party software components which are intended to integrate with the Dispatch Subsystem through the
COTS Interface(s).
Although the Customer is expected to participate in Hexagon's internal testing of the COTS Interfaces,
the Customer will formally test interface functionality during Functional Testing Task.
Task Deliverables
• Installation and configuration of the COTS Interfaces
For more information on the COTS Interfaces, see Attachment H, Interface Descriptions.
Task Prerequisites
• Operation or availability of all(external systems or Third -Party Software.
• Completed COTS Interface Questionnaires provided to Hexagon during the COTS Interface
Review Period.
Hexagon Team Participation and Responsibilities
Hexagon shall.
Install COTS Interfaces in the Customer's Production Environment; and
Unit test interfaces in accordance with the COTS Interface Questionnaires.
Customer Team Participation and Responsibilities
Customer shall.
• Ensure SMEs are available to support Hexagon Activities as needed;
• Verify that physical connectivity and communication has been achieved from Customer's
Communication/Interface server to remote system servers and all other third -party systems (such
as Customer message switch(es), Stete/NCIC, RMS systems etc.);
• Provide availability and confirm operation of external systems or third -party software;
• Provide the following information to Hexagon:
IP address for remote databases/systems
1 Mobile Responder configuration is not included within the scope of this Task. Within this Task, COTS
Interface does not include Mobile Responder. Configuration of Mobile Responder is separately addressed
in subsequent Tasks.
42
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Socket value for remote databases systems
Enter operator IDs (ORIs), terminal mnemonics, etc., as needed by remote
databases/systems
• Ensure the system and network administrators are available to work closely with the Hexagon
team for the duration of the Task, and
• Ensure third -party cooperation with Hexagon's reasonable requests.
Ta s k Acce pta nce Criteria
This Task is complete when each COTS Interface is installed and configured in accordance with the
COTSInterface Questionnaire, and subject to the functionality and features within the COTS version of
the COTS Interface.
43
d A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
19.OnCaii Dispatch Configuration Consulting 1
Task Description
With the configuration capabilities included in OnCall Dispatch, the Customer is able to tailor the
Subsystem based on certain needs and intended outcomes. This Task begins the process of configuring
OnCall Dispatch to better align with Customer's workflows, intended graphical layout, and desired
processes. The objective of this Task is to begin to familiarize the Customer with the configurability of the
OnCall Dispatch Software to facilitate configuration for its call -taking and dispatching operations as well
as its administrative and supervisory operations.
During this Task, Hexagon will conduct the "Configuration 1 Workshop," which will last no longer than
three (3) Business Days. Hexagon will provide independent configuration services for up to three
Business Days following the Configuration 1 Workshop ("Configuration 1 Period"). During the
Configuration 1 Workshop, Hexagon and Customer will work collaboratively with one another to configure
the Basic Settings, Viewing Settings, Call Taking Process Settings, Event Creation Settings, and UI
Layouts (as defined below). The Configuration 1 Workshop format includes up to four (4) hours of joint
work between Hexagon and Customer with the remaining hours of the Business Day allocated for
independent work. During the joint session and by the end of each daily joint session, the Customer
Dispatch Core Team will record the list of requested configurations from each day, placing them in order
of priority to be completed, which Hexagon will work on during its independent configuration time.
Up to the end of the Configuration 1 Period, Hexagon will configure the pConfiguration 1 Settings (as
defined below) based upon direction from Customer and subject to the Benchmark Criteria. After the
Configuration 1 Period has expired, the Customer will be responsible for making any configuration
changes to the Configuration 1 Settings that were not otherwise completed during the Configuration 1
Period or that Customer seeks to further configure. Scope of the configuration is limited to the capabilities
described in the Benchmark Criteria. Not all requested product configuration may be possible.
Task Delivera bias
• OnCall Dispatch Configuration 1 Workshop
Task Prerequisite
Customer's OnCall Dispatch Subsystem is available for use.
initial GIS services published and configured for use by OnCall Dispatch.
Map display
Routing
Geocoding
• OnCall Dispatch Fundamentals for Core Team Task is complete.
Task Assumptions
• Hexagon responsibilities will be executed on site at a Facility.
• The Configuration 1 Workshop will last no longer than three (3) Business Days.
• The Configuration 1 Workshop will be interactive with up to twelve (12) Customer attendees for
up to four (4) Business Hours per day with any remaining time allocated for independent Hexagon
configuration work.
44
4 A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• Customer Dispatch Core Teams will record the list of requested configurations from each day,
placing them in order of priority to be completed.
• During the Hexagon independent work time, Customer can have up to two (2) designated Team Core I eam members shadow Hexagon.
® Requested configurations not completed each day will be rolled to the next day and worked in
priority order until the end of the Configuration 1 Period.
Requested• configurations to the Configuration 1 Settings not completed by the end of the
Configuration 1 Period can be completed by the Customer, if so desired, which must be done
prior to Configuration 2 Workshop.
Hexagon Team Participation and Responsibilities
Hexagon shall:
Provide consulting and configuration services to review (collectively, "Configuration 1 Settings"):
Customer's preferences for basic settings, including but not limited to (collectively,
"Basic Settings"):
Colors for unit statuses
Colors for event priorities
Icons for event types on the map and event cards boards
Icons for unit types
Customer's needs for viewing event and unit related data in real-time lists (status
monitors) (collectively, "Viewing Settings"):
Visible columns
Customer's emergency and non -emergency call -taking processes, including but not
limited to (collectively, "Call Taking Process Settings"):
Location validation
Event -type selection
Jurisdiction determination
Customer's event creation processes, including but not limited to (collectively, "Event
Creation Settings"):
Nearby or possible duplicate detection
User Interface Layouts ("UI Layouts")
Customer Participation and Responsibilities
Customer shall.
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• Provide a Project Workstation for each attendee,
• Ensure the attendance and active participation of the Dispatch Core Team members and other
SMEs for the duration of the Configuration 1 Workshop,
• Participate in discussions and engage with the Hexagon team member;
• Track and prioritize requests for configuration of the Configurati onl Settings on a daily basis
during the Configuration 1 Workshop; and
• Complete any changes to Configuration 1 Settings prior to the commencement of Configuration 2
/�
Workshop. /�
Task Acceptance Criteria
This Task is complete upon. (i) the conclusion of the Configuration 1 Workshop and (ii) upon the earlier
of, expiration of the Configuration 1 Period or configuration of the Configuration 1 Settings.
46
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch implementation
20.OnCali Dispatch Configuration Consulting 2
Task Description
The objective of this Task is to continue to familiarize the Customer with the configurability of the OnCall
Dispatch Software to facilitate configuration for its call -taking and dispatching operations as well as its
administrative and supervisory operations.
During this Task, Hexagon will conduct the "Configuration 2 Workshop," which will last no longer than
three (3) Business Days. Hexagon will provide independent configuration services for up to three (3)
Business Days following the Configuration 2 Workshop ("Configuration 2 Period"). During the
Configuration 2 Workshop, Hexagon and Customer will work collaboratively with one another to configure
the Configuration 2 Settings (as defined below). The Configuration 2 Workshop format includes up to four
(4) hours of joint work between Hexagon and Customer with the remaining hours of the Business Day
allocated for independent work. During the joint session and by the end of each daily joint session, the
Dispatch Core Team will record the list of requested configurations from each day, placing them in order
of priority to be completed, which Hexagon will work on during its independent configuration time.
Up to the end of the Configuration 2 Period, Hexagon will configure the Configuration 2 Settings based
upon direction from Customer and as contemplated within the Benchmark Criteria. After the
Configuration 2 Period has expired, the Customer will be responsible for making any configuration
changes to the Configuration 2 Settings that were not otherwise completed during the Configuration 2
Period or that Customer seeks to further configure. Customer shall complete any changes to the
Configuration 2 Settings prior to the start of OnCall Dispatch Configuration Consulting 3. Scope of the
configuration is limited to the capabilities described in the Benchmark Criteria. Not all requested product
configuration may be possible.
Task Deliverables
• OnCall Dispatch Configuration 2 Workshop
Task Prerequisites
• Configuration 1 Workshop and Configuration 1 Period are complete, and Customer has
completed any and all additional configurations to the Configuration 1 Settings.
• Connection established to Customer's state crime system.
Task Assumptions
• Hexagon responsibilities will be executed on site at a Facility.
• Configuration 2 Workshop will last no more than three (3) Business Days.
• The Configuration 2 Workshop will be interactive with Customer attendees for up to four (4)
Business Hours per day with any remaining time of the Business Day allocated for independent
Hexagon configuration work.
• Customer Dispatch Core Team will record the list of requested configurations from each day,
placing them in order of priority to be completed.
• During the Hexagon independent work time, the Customer can have up to two (2) designated
Dispatch Core Team members shadow Hexagon.
• Requested configurations not completed each day will be rolled to the next day and worked in
priority order until the end of the Configuration 2 Period.
47
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• Requested configurations to the Configuration 1 Settings not completed by the end of the
Configuration 2 Period can be completed by the Customer, if so desired, which must be done
prior to Configuration 3 Workshop.
Hexagon Team Participation and Responsibilities
Hexagon shall:
• Provide consulting and configuration services to review the settings below (collectively,
"Configuration 2 Settings"):
▪ Customer's event triage and dispatching processes
• Customer's event management processes, including but not limited to:
Unit recommendation & assignment
Unit on event management
Unit location changes
Staging areas
Case numbers
Remote inquiries
Queued events Rotational services (e.g., Tow
ow trucks, lock smiths,
• Call back process
• Known callers
•
Fsell Events (a.k.a
• Associated Events
• Cnnied F.,enis
Customer Participation and Responsibilities
Customer shall:
•
etc.)
• Provide a Project Workstation for each attendee,
• Ensure the attendance and active participation of the Dispatch Core Team
eam members and other
SMEs for the duration of the Configuration 2 Workshop;
• Participate in discussions and engage with the Hexagon team member; T
• Track and prioritize requests for configuration of the Configuration 2 Settings on a daily basis
during the Configuration 2 Workshop; and
• Complete any configurations changes to the Configuration 2 Settings prior to the commencement
of Configuration 3 Workshop.
48
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Ta s k Flcce pta nce Criteria
This Task is complete upon. (i) the conclusion of the Consulting 2 Workshop and (ii) upon the earlier of,
expiration of the Configuration 2 Period or configuration of the Configuration 2 Settings.
49
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch implementation
21 .OnCali Dispatch Configuration Consulting 3
Task Description
The objective of this Task is to complete the configuration of the OnCall Dispatch Software for its call'
taking and dispatching operations as well as its administrative and supervisory operations.
During this Task, Hexagon will conduct the "Configuration 3 Workshop," which will last no longer than
three (3) Business Days. Hexagon will provide independent configuration services for up to three
Business Days following the Configuration 3 Workshop ("Configuration 3 Period"). During the
Configuration 3 Workshop, Hexagon and Customer will work collaboratively with one another to configure
the Configuration 3 Settings. The Configuration 3 Workshop format includes up to four (4) Business
Hours of joint work between Hexagon and Customer with the remaining hours of the Business Day
allocated for independent work. During the joint session and by the end of each daily joint session, the
Dispatch Core Team will record the list of requested configurations from each day, placing them in order
of priority to be completed, which Hexagon will work on during its independent configuration time.
Up to the end of the Configuration 3 Period, Hexagon will configure the Configuration 3 Settings based
upon direction from Customer and as contemplated within the Benchmark Criteria. After the
Configuration 3 Period has expired, the Customer will be responsible for making any configuration
changes to the Configuration 3 Settings that were not otherwise completed during the Configuration 3
Period or that Customer seeks to further configure. Customer shall finish any changes to the
Configuration 3 Settings within ten (10) Business Days following the Configuration 3 Period. Scope of the
configuration is limited to the capabilities described in the Benchmark Criteria. Not all requested product
configuration may be possible.
Task Deliverables
• OnCall Dispatch Configuration 3 Workshop
Task Prerequisites
• Configuration 2 Workshop and Configuration 2 Period have been completed, and Customer has
/�
completed any additional configurations to the Configuration 2 Settings.
Task Assumptions
• Hexagon responsibilities will be executed on site at a Facility.
• The Configuration 3 Workshop will last no more than three (3) Business Days.
• The Configuration 3 Workshop will be interactive with Customer attendees for up to four (4) hours
per day with any remaining time of the Business Day allocated for independent Hexagon
configuration work.
• Dispatch Core Team will record the list of requested configurations from each day, placing them
in order of priority to be completed.
• During the Hexagon independent work time, the Customer can have up to two (2) designated
Dispatch Core Team members shadow Hexagon. Requested configurations not completed each
day will be rolled to the next day and worked in priority order until the end of the Configuration 3
Period.
• Requested configurations not completed upon consumption of all allocated labor hours can be
completed by the Customer, if so desired, which must be done prior to the commencement of
Customer Functional Testing.
50
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Hexagon Team Participation and Res pen s i bilities
Hexagon shall:
• Provide consulting and configuration services ("Configuration 3 Settings”) to review:
Biased based profiling data collection
Notifications
• ures (SOPS)
Event Tags
Logging on
Logging off
Logon Group (Lineup)
CADSearches
Event search
Unit history search
Broadcasts (a.k.a. BOLO.)
Customer Participation and Responsibilities
•
•
• Ensure the attendance and active participation of the Dispatch Core Team members and other
SME5 for the duration of the Configuration 3 Workshop,
• Participate in discussions and engage with the Hexagon team member;
• Track and prioritize requests for configuration of the Configuration 3 Settings on a daily basis
during the Configuration 3 Workshop; and
• Complete any configurations changes prior to the commencement of Customer Functional
Te sting.
Task Flcce pta nce Criteria
This Task is complete upon: (i) the conclusion of the Consulting 3 Workshop and (ii) upon the earlier of,
expiration of the Configuration 3 Period or configuration of the Configuration 3 Settings.
51
4 A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch implementation
22.OnCall Dispatch I Customer Rules Engine Configuration Workshop
Task Description
The objective of this Task is to familiarize the Customer with configura bility of the OnCall Dispatch
Customer Rules Engine (CRE), an add -on component to the HXGN OnCall Dispatch product suite. CRE
allows customized business rules to be created using a drag -and -drop editor. The customized business
rules can be used to implement workflows that are specific to a particular customer and therefore not
available out -of -the -box in the core HXGN OnCall Dispatch product suite.
The Customer is responsible for configuring CRE. Hexagon will provide specific consulting sessions as
part of the Project, but the Customer Core Team's understanding of configuration will correspondingly
allow the Customer to use CRE to create custom workflows. Hexagon will also provide an example of
how to implement a CRE-based configuration in the Customer's Environment.
Hexagon will conduct a workshop ("CRE Workshop") to familiarize the Customer with CRE, provide an
example of a CRE configuration, and, if time permits, begin working pon implementing CRE-based
configurations. The CRE Workshop shall last no more than four (4) Business Days. Any CRE-based
configuration not completed at the end of the CRE Worksh-Iop shall be the responsibility of Customer. The
Customer shall complete configuration of CRE within ten (10) Business Days after the CRE Workshop
(the "CRE Configuration Period"). If the Customer has questions as it configures CRE, it may contact
Hexagon to address the question.
Task Deliverables
• CRE Workshop
Task Prerequisites
Task Assumptions
9 Hexagon responsibilities will be executed on site at a Facility.
Attendance by the Customer's personnel will be limited to no more than twelve (12) people and
must consist of field users and stakeholders capable of making finalized decisions about
configurations within OnCall Dispatch.
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Conduct the CRE Workshop; and
Customer Team Participation and Responsibilities
Customer shall.
for each attendee
configures CRE.
• Ensure appropriate personnel attend, and fully participate in all the CRE Workshop
52
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• Provide department -specific CAD configuration and workflow data as needed, and
• Configure CRE within the CRE Configuration Period.
Ta s k Acce pta nce Criteria
This Task is considered complete when Hexagon has conducted the CRE Workshop.
53
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
23.OnCaii Dispatch I Mobile Unit Configuration Consulting Session 1
Task Description Hexagon will conduct one (1) consulting session with the Customer lasting no more than three (3)
Business Days as part of the Project ("Fire Mobile Configuration Session 1"). During the Fire Mobile
Configuration Session 1, Hexagon will provide information regarding configuration options for Mobile Unit
1 workflows as they pertain to the mobile environment. The Fire Mobile Configuration Session will
address.
• Sign on/Sign off
• Brief Uve rvi ew
• Screen Layout
•
• Alerts
• Toolbars
• Map
• Messaging
• Unit Bogard
•
Event Board r�
• The included Dispatch Report
• Network requirements and ports to ensure the Mobile Unit client can communicate appropriately
The Customer will need to make available one dispatcher familiar with OnCall Dispatch to perform
dispatching and other related tasks as necessary during the Fire Mobile Consulting Session 1.
Following the Fire Mobile Configuration Session 1, the Customer will configure Mobile Unit during the
next ten (10) Business Days ("Fire Mobile Configuration Period 1"). After the first five (5) Business Days
of this period, Hexagon will review the Customer's configuration and provide feedback in ae consultation
session lasting no longer than one (1) Business Day ("Fire Mobile Configuration Consultation 1"). The
Customer will then have the remaining five (5) Business Days to continue or revise configuration ("Fire
Mobile Configuration Follow -Up Period 1"). At the conclusion of the Fire Mobile Configuration Follow -Up
Period 1, Hexagon will perform a final review with the Customer and provide feedback in a consultation
lasting no more than one (1) Business Day ("Fire Mobile Configuration Follow -Up Consultation 1").
The Customer is responsible for configuring the Mobile Unit subsystem. Upon completion of this Task, the
Customer will have one (1) mobile configuration of Mobile Unit for testing.
Task Deliverables • Fire Mobile Configuration Session -1 1
54
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Task Prerequisites
• OeCall Dispatch Configuration Consulting 3 Task is complete.
Task Assumptions
• Hexagon responsibilities will be executed on site at a Facility,
• Attendance by the Customer's personnel will be limited to no more than twelve (12) people and
must consist of field users and stakeholders capable of making final decisions about product
behavior and functionality.
Hexagon Team Participation and Responsibilities
Hexagon shall.
Customer Team Participation and Responsibilities
Customer shall.
•
•
for each attendee
• Provide mobile SME to support Hexagon as needed,
• Provide a Dispatcher SME to give feedback on how Mobile Unit will affect dispatchers and to
assist with various dispatching Activities; • Participate fully and collaboratively in the Fire Mobile Configuration Session 1
1 with the
understanding that Mobile Unit client configuration decisions must be documented and agreed
upon at the conclusion of these sessions;
• Begin the Fire Mobile Unit Configuration Document.
Task Acceptance Criteria
Configuration Session 1, Fire Mobile
55
4 A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch implementation
24.OnCaii Dispatch I Mobile Unit Configuration Consulting Session 2
Task Description Hexagon will conduct one (1) consulting session with the Customer lasting no more than three (3)
Business Days as part of the Project ("Fire Mobile Configuration Session 2"). During the Fire Mobile
Configuration Session 2, Hexagon will provide additional information regarding configuration options for
Mobile Unit workflows as they pertain to the mobile environment based on the results of Fire Mobile I
Configuration Follow -Up Consultation I. The Fire Mobile Configuration Session 2 will include.
• Continuation of configuration consulting identified from -I
Up Consultation 1
Fire Mobile Configuration Session 2 will continue configuration consulting on the following areas:
• Sign on/Sign off
•
Brief Overview of Appl
•
Screen Layoout
•
Navigation Buttons
•
Alerts
• Toolbars
• Event Search
• Menus and Submenus
• Map
• Messpaging
•
Unit Bogard
• Event Board•
r�
The included Dispatch Report
The Customer will need to make available one dispatcher familiar with OnCall Dispatch to perform
dispatching and other related tasks as necessary during the Fire Mobile Consulting Session 2.
Following the Fire Mobile Configuration Session 2, the Customer will configure Mobile Unit during the
next ten (10) Business Days ("Fire Mobile Configuration Period 2"). After the first five (5) Business Days
of this period, Hexagon will review the Customer's configuration and provide feedback in a consultation
session lasting no longer than one (1) Business Day ("Fire Mobile Configuration Consultation 2"). The
Customer will then have the remaining five (5) Business Days to continue or revise configuration ("Fire
Mobile Configuration Follow -Up Period 2"). At the conclusion of the Fire Mobile Configuration Follow -Up
Period 2, Hexagon will perform a final review with the Customer and provide feedback in a consultation
lasting no more than one (1) Business Day ("Fire Mobile Configuration Follow -Up Consultation 2").
The Customer is responsible for configuring the Mobile Unit subsystem. Upon completion of this Task, the
Customer will have one (1) mobile configuration of Mobile Unit for testing.
56
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Task Deliverab le
• Fire Mobile Configuration Consultation 2
• Fire Mobile Configuration Follow -Up Consultation 2
Task Prerequisites
Task Assu rn ptions
• Hexagon responsibilities will be executed on site at a Facility,
• Attendance by the Customer's personnel will be limited to no more than twelve (12) people and
must consist of field users and stakeholders capable of making final decisions about product
behavior and functionality. 1�
Hexagon Team Participation and Responsibilities
Hexagon shall.
Consultation 2, and Fire Mobile Configuration Follow -Up Consultation 2.
Customer Team Participation and Responsibilities
Customer shall.
•
• for each attendee
•
• Provide a Dispatcher SME to give feedback on how Mobile Unit will affect dispatchers and to
assist with various dispatching Activities;
• Participate fully and collaboratively in the Fire Mobile Configuration Session 2 with the
understanding that Mobile Unit client configuration decisions must be documented and agreed
upon at the conclusion of these sessions,
• Begin the Fire Mobile Unit Configuration Document.
Task Acceptance Criteria
The Task is complete when Hexagon has conducted the Fire Mobile Configuration Session 2, Fire Mobile
Configuration Consultation 2, and Fire Mobile Configuration Follow -Up Consultation 2.
57
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
25. OnCall Dispatch I Mobile Responder Configuration
Task Description
During the COTS Interface Questionnaire Task, the Customer will have selected configuration options for
OnCall Dispatch I Mobile Responder. During this Task, Hexagon will configure Mobile Responder based
on the requested configuration changes according to the COTS Interface Questionnaire up to eight (8)
Business Hours ("Fire Mobile Responder Configuration Period").
Task Deliverables
• One (1) Fire Mobile Responder Configuration
Task Prerequisites (�
• COTS Interface Questionnaire Completion Task is complete.
Task Assumptions
• N/A
Hexagon Team Participation and Responsibilities
Hexagon shall.
Customer Team Participation and Responsibilities
Customer shall.
SMEto Hexagon as needed, and
• Provide a Dispatcher SME to give feedback on how OnCall Dispatch Mobile Responder will affect
dispatchers and assist with various dispatching tasks.
Task Acceptance Criteria
The Task is complete when Hexagon has completed the Fire Mobile Responder Configuration Services.
58
4 A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
26.Custom Interface Product Installation and Configuration
Task Description
During this Task, Hexagon will install, configure, and test the Custom Interfaces. Although the Customer
is expected to participate in Hexagon's internal testing of the Custom Interfaces, the Customer will
formally test the Custom Interfaces' functionality during Functional Testing.
Task Deliverables
• Documentation of Custom interfaces installation testing
Task Prerequisites
• Operation or availability of the external system or Third -Party Software.
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Test Custom Interfaces in accordance with the approved ICDs.
Customer Team Participation and Responsibilities
Customer shall.
• Ensure SME5 are available to support Hexagon Activities as needed,
• Verify that physical connectivity has been achieved from Customer's communication server to
OnCall Dispatch;
• Provide availability and confirm operation of external systems or third -party software,
• Provide the following information to Hexagon:
IPaddress for remote databases
Socket value forremotesystems
Operator IDs (ORls), terminal mnemonics, etc., as needed by remote systems
• Ensure the system and network administrators are available to work closely with
team for the duration of the Task, and
Ensure third -party cooperation with Hexagon's reasonable requests.
Task Ai0ptance Criteria
This Task is complete when each Custom Interface is installed and configured in accordance with the
applicable ICD.
59
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
27.Standard Interface Product Installation and Configuration
Task Description
During this Task, Hexagon will install and configure the Standard Interfaces. The Customer will formally
test the interface functionality and reliability during Functional Testing.
The following are regarded as "Standard Interfaces" as the term is defined in Attachment H of this SOW:
• PLT Radio OnCall Dispatch Interface to Harris Radio
• Dispatch Alerts OnCall Interface to Everbridge
Task Deliverables
• Documentation of Standard Interfaces installation
Task Prerequisites
• Operation or availability of the external system or Third -Party Software
Hexagon Team Participation and Responsibilities
Hexagon shall:
Customer Team Participation and Responsibilities
• Ensure SMEs are available to support Hexagon Activities as needed;
• Verify that physical connectivity has been achieved from Customer's communication server to
OnCall Dispatch;
• Provide availability and confirm operation of external systems or third -party software,
• Provide the following information to Hexagon:
IP address for remote databases
Socket value for remote systems
Operator IDs (ORIs), terminal mnemonics, etc., as needed by remote systems
• Ensure the system and network administrators are available to work closely with the Hexagon
team for the duration of the Task; and
• Ensure third -party cooperation with Hexagon's reasonable requests.
Ta s k Acce pta nce Criteria
This Task is complete when each Standard Interface is installed and configured.
60
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
28.Test Plan and Test Cases Development
Task Description
During this Task, the Customer will create a test plan ("CAD Test Plan") with Test Cases for OnCall
Dispatch. The CAD Test Plan and Test Cases are essential for the Customer to be able to validate and
prove the functionality of the Dispatch Subsystem. Every Benchmark Criteria corresponding to OnCall
Dispatch should have at least one Test Case, some Benchmark Criteria may have multiple associated
Test Cases. The Customer will identify the Benchmark Criteria that correspond to the applicable Test
Cases. A clear pass/fail criterion must be defined for each Test Case. The Test Plan and Test Cases will
be agency -specific, and work -process driven with clearly documented Pass/Fail criteria. Only the
elements of the Test Plan and Test Cases conforming with the Benchmark Criteria shall be used in
evaluating and testing the Subsystem. The Test Plan is the set of Test Cases that will serve as the basis
of testing the fully configured Subsystem, including interfaces.
The Customer will not need a fully configured Subsystem to create the Test Plan and Test Cases. The
Test Case creation should be accomplished using a workflow -based Test Case.
Task Deliverables
Customer's CAD Test Plan and Test Cases
Task Prerequisite=
• OnCaii Dispatch Fundamentals for Core Team Task is complete.
Task Assumptions
• N/A
Hexagon Team Participation and Responsibilities
Hexagon shall:
during the Test Plan and Test Cases creation Task to validate the
he Benchmark Criteria (applicable to Dispatch).
Customer Team Participation and Responsibilities
Customer shall:
• Provide CAD Test Plan and Test Cases to Hexagon.
Ta s k Acce pta nce Criteria
CADTest Plan and Test Cases and Hexagon
has validated the same in accordance with the Benchmark Criteria.
61
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
29. Customer Functional Testing
Task Description
The Customer, with support from Hexagon, will test OnCall Dispatch's conformance with the Benchmark
Criteria. The Customer will conduct Functional Testing over the course of ten (10) Business Days
("Dispatch Testing Period"). During the Dispatch Testing Period, the Customer shall execute the CAD
Test Plan and corresponding Test Cases. Except as expressly provided, no other testing or evaluation
pertaining to OnCall Dispatch is contemplated in this Project. Customer will document and track the
results of each Test Case as either pass or fail and may request Hexagon consultation as necessary
during its testing Activity up to twenty-four (24) Business Hours.
Within five (5) Business Days of the end of the CAD Testing Period ("CAD Reporting Period"), the
Customer shall file any Blocker Errors and Permissive Errors encountered during Functional Testing —
Dispatch through Hexagon's Customer Resource Management (CRM) system. For any Blocker Error
identified, the Customer shall provide, at minimum, the following information: a description of the Error
and the steps used to reproduce it, the functionality tested when the Blocker Error was encountered, the
manner in which the functionality was tested, and the outcome when the functionality was tested. If the
Blocker Errors are not filed within the CAD Reporting Period, it is presumed Functional Testing was
completed without any Blocker Error, and this Task is complete. Only Blocker Errors reported by the
conclusion of the Reporting Period will be resolved as part of this Task. The existence of Permissive
Error(s) shall not preclude or be a condition of completion of any subsequent Tasks or implementation of
a new Release.
To the extent requested, Customer agrees to promptly respond to requests for additional information
regarding the Blocker Error requested by Hexagon. Upon diagnosing the Blocker Error and validating the
Error encountered meets the attributes of a Blocker Error, Hexagon resources shall proceed to resolve
the Blocker Error accordingly. If the investigation determines the reported Blocker Error did not meet the
attributes of a Blocker Error then the reported Error will be reclassified in accordance with the levels
provided in the Master Terms Glossary. Alternatively, if the investigation shows the reported Blocker Error
was caused by Customer hardware, Network Infrastructure, or Third -Party Software not provided by
Hexagon, or non-conformance with Attachments E-1 and F, then Hexagon will provide such information
to the Customer for the Customer to resolve and the Blocker Error will be closed and regarded as
complete.
As part of its resolution efforts, Hexagon may at its discretion provide a procedural or programmatic work
around, a configuration change, or provide an Update. Once the Blocker Error(s) is addressed, Hexagon
will report to Customer the Blocker Error has been addressed and the Customer will have five (5)
Business Days to execute its Test Plan ("CAD Resolution Testing Period").
After the Functional Testing, Hexagon will enforce a Code Freeze. No configurations or modifications will
be allowed to the Subsystem by Hexagon or Customer, except those required to resolve any Blocker
Error. Upon addressing Blocker Errors, the Subsystem 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 Subsystem -wide Code Freeze. Any System/Subsystem modifications will be handled via
Change Order.
Task Deliverables
• System Code Freeze
62
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Task Prerequisites
• Customer and Hexagon mutually confirm that OnCall Dispatch and Mobile Unit are ready for
testing.
• Test Plan and Test Cases Development Task is complete.
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Verify all applicable software, systems and ancillary systems, including the redundancy of
Production system (if applicable), are ready for Functional Testing,
• Provide support during Functional Testing,
• Review Errors filed by the Customer, and
• Resolve Blocker Errors filed by the Customer.
Customer Team Participation and Responsibilities
Customer shall.
• Verify all applicable software, systems and ancillary systems, including the redundancy of
Production system (if applicable), are ready for Functional Testing,
• Execute the CAD Test Plan, and•
Track and document results from executed Test Cases and file any Ulocker Errors in the CRM
system by the/+end of the CAD Reporting Period.
Ta s k Flcce pta nce Criteria p
This Task is complete upon expiration of the CAD Testing Period and resolution of all Ulocker Errors
reported by the end of the CAD Reporting Period.
63
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch implementation
30. Hexagon -Led Training
Task Description
During the Training phase, Hexagon resources will conduct Administrative and Train -the -Trainer sessions
for Customer -designated personnel.
The following formal training classes are included in the Project ("Hexagon Training Classes"):
HxGN OnCall Dispatch System Administrator Training — Qty: 1
HxGN OnCall Dispatch Train -the -Trainer — Qty: 2
HxGN OnCall Dispatch I Mobile Unit Train -the -Trainer — Qty: 2
HxGN OnCall Dispatch I Mobile Responder Train -the -Trainer — Qty: 2
HxGN OnCall Analytics I Dispatch User Training — Qty: 1
HxGN OnCall Analytics I Dispatch System Administrator Training — Qty: 1
It is recommended that Customer develop its own training program, including, but not limited to: creating
a training plan suitable for its needs, identifying a training cadre for each Subsystem, and leveraging the
Hexagon training materials and Documentation to ensure its Users have acquired the necessary
knowledge and are in a position to use OnCall Dispatch upon Cutover. The Customer is solely
responsible for training its Users. The Customer shall complete its User Training no later than thirty (30)
calendar days after Hexagon has completed the Hexagon Training Classes ("End User Training Period").
Task Deliverables
• Training course agendas
• Applicable COTS Documentation, in electronic format, for the Hexagon Training Classes
Task Prerequisites
• Customer has identified and secured an appropriate training room and set up with the
workstations, at least one (1) LCD projector, display screen or other appropriate surface to
display a projected image, and white -board space or other ability to take notes and record
questions.
• The Customer has installed and configured at least one (1) workstation per student attending the
session.
Task Assumptions
• The Customer will complete end user training within the End User Training Period.
• Both end -user training and train -the trainer training will be provided as specifically identified
herein. Training will take place during normal Business Hours, which is typically from 8:00 am
5:00 pm.
• Training documentation provided by Hexagon with this SOW will be standard COTS
Documentation and help files and will not be customized to the Customer's site -specific
configuration. All Documentation will be provided in electronic format. Should printed copies be
required, the Customer is responsible for providing them.
64
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Hexagon Team Participation and Responsibilities
Hexagon shall.
Customer Team Participation and Responsibilities
Customer shall.
• Provide appropriate facilities and install configure workstations as indicated in the Task
Assumptions,
• Provide a Project Workstation for each attendee of the Hexagon Training Classes;
• Ensure appropriate personnel participate in the Hexagon Training Courses; and
• Complete end user training within the End User Training Period.
Task Acceptance Criteria
This Task is complete once Hexagon has delivered the Hexagon Training Classes to the Customer.
65
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
31. Replicate Cloud Environments
Task Description
Up to this point, the Project has focused on creating the Cloud Development Environment and configuring
and testing the Dispatch Cloud Program in the Development Environment, which was the only Cloud
Environment
� available. Following achievement of a Production Ready System, Hexagon will replicate the
Production Ready System in the newly created Staging Environment and Production Environment. This
Task is intended to be completed within five (5) Business Days prior to scheduled Cloud Cutover.
Task Deliverables
Task Prerequisites
Task Assumptions
• This Task is intended to be completed within five (5) Business Days prior to scheduled Cloud
Cutover.
• Notwithstanding anything to the contrary in the Master Terms and in addition to the rights provided
with a Cloud Staging Environment, the Customer shall also have the right to have its Users use
the Cloud Staging Environment for training purposes in like manner as if the Cloud Staging
Environment was also a Cloud Training Environment.
Hexagon Team. Participation and Responsibilities
Hexagon
� shall, r�
• Replicate the Production Ready System in a S
Customer Team Participation and Responsibilities
• None
Task Acceptance Criteria
This Task is complete when Hexagon has replicated the Production Ready System into the Staging
Environment and Production Environment.
66
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
32. Cloud Cutover Plan
Task Description
Hexagon and the Customer will Jointly develop a Cloud Cutover Plan. The Cloud Cutover Plan will detail
the steps necessary to cutover the Dispatch Cloud Program. The Cloud Cutover Plan will assign tasks
and responsibilities to both Hexagon and Customer personnel in the month prior to Cloud Cutover. The
Cloud Cutover Plan covers topics including Customer staffing, movement of equipment into final
locations, final database cleanout of test events, procedures to report issues, and planned sequence of
events for the Cutover day.
Hexagon will provide the initial draft of the Cloud Cutover Plan to the Customer for review. The Customer
will review the draft and provide feedback to Hexagon within ten (10) Business Days, which will
incorporate appropriate feedback into a final Cloud Cutover Plan.
TasK Deliverables
• Cloud Cutover Plan 1�
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Create a draft Cloud Cutover Plan (i.e., prepare a checklist of responsibilities and tasks to be
completed during the Cutover Task prior to Cutover),
•
•
Customer Team Participation and Res pon sibili[ies
Customer shall.
• Review and comment on the draft Cloud Cutover Plan within ten (10) Business Days of receipt,
Ta s K Acce pta nce Criteria
This Task is complete when the Customer has reviewed and approved the final Cloud Cutover Plan.
67
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
33. Cloud Program Readiness Review
Task Description
During this Task Hexagon technical resources, the Hexagon Project Manager, and the Customer team
will meet and determine if the Dispatch Cloud Program is ready for Cloud Cutover.
In addition, the Cloud Readiness Review verifies that the following has occurred.
• A document titled, "Cloud Cutover Plan" has been developed and approved by both Hexagon and
the Customer;
• Establishment and approval of a schedule for Cloud Cutover Activities, and
• Identification and scheduling of Hexagon and Customer resources required for Cloud Cutover
Activities.
Task Deliverables
Cloud Readiness Review meeting minutes
Discussion notes on the results from Hexagon's final review of the Cloud Program
Task Prerequisites
Task Assumptions
• The Customer certifies it has
� trained all personnel who will be utilizing the Cloud Program.
Hexagon Team Participation and Responsibilities
Hexagon shall.
• Conduct a conference call to discuss if the system is ready to perform Cloud Cutover,
• Provide Cloud Cutover notification to appropriate internal and external interface stakeholders
supplying systems integral to Cutover operations;
• Review and provide timely feedback approval of Cloud Cutover Plan, and
• Work with Customer to determine suitable Cutover schedule.
Customer Team Participation and Responsibilities
Customer shall.
• Participate in the conference call;
• Notify internal and external interface stakeholders about pending Cloud Cutover,
• Review and provide timely feedback approval of Cloud Cutover Plan; and
• Work with Hexagon to determine suitable Cutover schedule.
68
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Ta s k Acce pta nce Criteria
This Task is complete when tine Cloud Readiness Review has been conducted.
69
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
34.Cloud Cutover to Production Use
Task Description
Cloud Cutover reflects the culmination of all the Tasks in this SOW. It reflects the pointatwhich the
Customer first uses the Cloud Program in a live environment for its intended purpose. Before Cloud
Cutover, the Customer shall have completed the preceding Tasks. Although the Customer may use the
Cloud Program at any time after IOC, Cloud Cutover reflects the point at which the Cloud Program has
been configured, had Interfaces installed, completed Functional Testing, and the Customer has trained all
of its end users.
The Parties shall execute the Cloud Cutover Plan, as practical, as part of Cloud Cutover. Beginning on
Monday of the week of Cloud Cutover, Hexagon resources and the Project Manager will support the
Customer's Activities leading to Cloud Cutover, during Cloud Cutover, and post -Cloud Cutover. Except for
the day of Cloud Cutover where the resource may be on site at alternate hours, the Hexagon
resource will be available Monday to Friday of the week of Cloud Cutover. Upon Cloud Cutover, the
Customer's System Administrator will assume primary responsibility of the management and
administration of the System, and the Hexagon resources will provide support as needed by the
Customer System Administrator. At times where the Hexagon resources are not otherwise available after
the Project is complete, the Customer shall contact Hexagon's HelpDesk in accordance with the
Maintenance Terms within the Agreement.
Task Deliverables
Task Prerequisites
• All prior Tasks are complete.
• The End User Training Period is complete.
Task Assumptions
• The Parties have agreed Cloud Cutover can proceed.
• Cutover will take place on the day and time specified in
• Hexagon will provide resources on site.
• First year maintenance of Hexagon Local Software will begin upon Cloud Cutover/Cutover.
Hexagon Team Participation and Res pops ibilities
Hexagon shall.
• Hexagon shall provide technical resource(s) to support Cutover during the week of Cloud
Cutover. 1'')
Customer Team Participation and Responsibilities
Customer shall.
• Ensure availability of trained Users;
• Ensure availability of Core Team during Cloud Cutover Activities,
70
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• Assume System Administration and management for the System upon Cutover;
•
availability of all third -party vendors impacted by the Cloud Cutover,
• availability of all IT disciplines necessary to immediately address issues as necessary,
and
• Ensure availability of member(s) of the training cadre during all shifts.
Ta sk Acceptance Criteria
71
1:10
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
35. Post-Cutover Support
Task Description
During this Task, Hexagon resources will provide Post-Cutover support to Customer. The "Post-Cutover
Support Period" is the ten (10) Business Days beginning the Monday following Cutover. It is designed to
provide the
-I Customer with dedicated, quickly accessible support for questions and Defects encountered
in the ten (10) Business Days following the Cutover to Production use of the new System.
During this Task, Hexagon resources will be assigned Defects that are filed by the Customer against the
new System. Hexagon resources will work to identify and address the Defects reported, understanding
the Defects will be triaged based upon their severity during the Post Cutover Support Period. Defects
remaining after the Post Cutover Support Period will be addressed by the Help Desk. Defects reported
outside of Business Hours will be addressed in accordance with the maintenance provisions of the
Agreement.
The Post-Cutover Support Period is not a configuration period. Requests for new configurations that are
not related to addressing a Defect will not be supported during this time frame. This is done to ensure the
stability of the System delivered and that focus remains on Defects and to minimize the introduction of
new opportunities for errors or problems.
Task Deliverables
• Task Completion Form confirming that Post-Cutover Support has been provided in accordance
with SOW Post-Cutover Support task description
Task Prerequisites
Task Assumptions
• Week 1 will be conducted on site, and Week 2 conducted remotely.
•
hours emergency support procedures, defined in the Cutover Plan, remain the same for the
duration of this Task.
• Defects will be reported via Hexagon's designated CRM tool.
• The Customer System Administrator remains the primary point of contact and initial
troubleshooting point of contact for all issues during this Task.
• The Customer System Administrator maintains responsibility for core system administration tasks.
Hexagon Team Participation and Responsibilities
Hexagon shall:
• Provide ten (10) Business Days of Post-Cutover support in
Customer Team Participation and Responsibilities
Customer shall.
72
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Ensure Defects are recorded in Hexagon's CRM tool in a timely manner and in accordance to the
mutually agreed upon Project Schedule.
'ask Aace pta rt..Criteria
This Task is complete when the Post-Cutover Support Period has expired.
73
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Terms and Conditions
This SOW is governed 7 by that certain agreement by and between Hexagon and Pinellas County Sheriffs
Office dated July 22, 2022 as modified by that certain Addendum by and between Customer and
Hexagon (collectively, the "Agreement").
74
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Approval Signatures
Signature by all parties listed below constitutes acceptance of and notice to proceed with this Cloud
Consulting Services Order, and the Cloud Program Sales Order (reflected in the Quote (Attachment A)).
This SOW may be executed in one or more counterparts, each of which shall be deemed to be original,
and all of which together shall constitute one and the same agreement. A signature delivered by facsimile
shall be deemed to be an original signature and shall be effective upon receipt thereof by the other party.
This document is approved by:
AUTHORIZED HEXAGON SIGNATURE
Name:
Richard Morns, VP of Global Contracts
Signature:
Date:
AUTHORIZED CUSTOMER SIGNATURE
Name:
Signature:
Date:
75
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch implementation
Attachment A— Pricing Summary
DESCRIPTION PRICE
Dynamo/E-Learning (12 months)
Total One -Time Implementation Costs
Recurring Fee for each Year through Year 47:
(Annually beginning at Cutover/Upon Go -Live)
Year 1 Recurring Fee
Year 2 Recurring Fee
Year 3 Recurring Fee
Year 4 Recurring Fee
Year 5 Recurring Fee
$1,360,813
$155,392
$15,000
$1,531,205
$671,279
$816,587
$898,246
$988,070
$1,086,877
Year 6 Recurring Fee
$1,195,565
Total One Time Implementation Costs a nd ].even -Year Recurring Fees
Pricing Assumptions:
$7,187,829
• This pricing assumes a database size of no greater than 500 GB ,on initial installation to allow
adequate space for database growth once the application is in use.
• This pricing assumes production, development, and staging environments. Users can train on the
staging environment unless an upgrade is being performed in that particular environment.
• 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. Miami City, FL should not factor any future features, functions, or
77
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Services Fee beyond the initial I8-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 management, installation, training/travel,
customizations, and third parties.
• The Dynamo Curriculum/E-Learning Licenses (quantity of 10) included in this pricing are for a 12
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 Implementation Services Costs include
support/maintenance, some start at cutover and others upon shipment. All have been included in the
pricing appropriately.
• The Customer is responsible for the connection between the cloud environment and the on -premise
server.
• The Cloud Program Fees are subject to capacity limitations as provided in the Cloud Service
Schedules to be provided with the resulting contract.
• This offer, including pricing, is valid until December 30, 2022.
BILL OF MATERIALS
CAD Software
- 8
H.GN OnCaii Dispatch - Advantage - Cloud
8
H.GN OrCaii Dispatch - Resource Management - Cloud
8
H.GN OnCaii Dispatch - Advanced Mapping - Cloud
8
H.GN OnCall Dispatch - Scheduling & Facilities Mg mt - Cloud
2
H.GN OnCall Dispatch - Essentials - Cloud
50
H.GN OnCaii Dispatch - Viewer - Cloud
8
H.GN OnCall Dispatch - Customer Rules Engine - Advantage-CLD
2
H.GN OnCall Dispatch - Customer Rules Engine -Essentials CLD
1
H.GN OnCaii Dispatch - Customer Rules Engine - Editor - CLD
1
H.GN OnCaii Dispatch - Customer Rules Engine - Server - CLD
150
H.GN OnCall Dispatch - Tracker - Cloud
1
H.GN OnCall Dispatch - RestAPI - Cloud
1
H.GN OnCaii Dispatch - Fire Station Alerting - Cloud
1
H.GN OnCaii Dispatch - Deccan LiveMUM Interface - Cloud
1
H.GN OnCaii Dispatch - CAD Link Interface - Cloud
1
Dispatch Alerts OnCall Interface - Cloud
1
H.GN OnCall Integration Engine
1
PLT Radio OnCall Dispatch Interface - Cloud
1
Xalt - Integration Runtime Engine NL - Subscription - BCK
1
)(alt. - Integration Runtime Engine NL - Subscription
1
Xait - Integration Runtime Engine NL - Subscription - TST
8
H.GN OnCaii Dispatch - ProQA Interface - Subscription-BCK
8
H.GN OnCaii Dispatch - ProQA Interface - Subscription
77
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
BILL OF MATERIALS
4
HxGN OnCali Dispatch - ProQA Interface - Subscription - TRN
8
HXGN OaCali Dispatch - ProQA Interface - Subscription - TST
[ Mobile Software
15 HxGN OnCali Dispatch - Mobile Unit - Cloud
85 I HXGN OnCeii Dispatch - Mobile Responder Client - Cloud
Analyiics Software
50
HXGN OnCall Analytics - Viewer - Cloud
5
HXGN OnCall Analytics - Author - Cloud
1
HXGN OnCall Analytics - Dispatch Data Models & Reports - CLD
78
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment B — Payment Schedule
On or after the completion of the Tasks identified below, Hexagon shall invoice the Customer the
corresponding amounts set forth below for Services and Local Software, which Customer shall pay in
accordance with the Agreement:
TASK
AMOUNT
Upon Completion of Task 1: Project Kickoff Meeting
$231,931
Upon Completion of Task 16: OnCall Dispatch GIS Consulting
$231,931
Upon Completion of Task 17: OnCall Dispatch Fundamentals for Core
Tea m
$231,931
Upon Completion of Task 21: OnCall Dispatch Configuration Consulting
3
$231,931
Upon Completion of Task 24: OnCaii Dispatch I Mobile Unit
Configuration Consulting Session 2 - Fire
$231,931
Upon Completion of Task 30: Hexagon -Led Training
$231,931
Upon Completion ofTask 34: Cloud Cutoverto Production Use
$154,619
Total
$1,546,205
For purposes of clarity, the subscription fee amount for the first year of the Cloud Program is $671,279,
and the amount for the second year of the Cloud Program is $816,587 and is due in accordance with the
Master Terms.
79
HEXAGON
Hosted OnCall Dispatch Implementation
Attachment C - Initial Project Schedule
TASK NAME
BUSINESS
DURATION DAYS SINCE
START
Miami City Fire Rescue, FL OnCall Dispatch (Hosted) Project
313 days
0 days
y
Initial Operation Capability (IOC) Phase
20.5 days
20 days
Project Kickoff Meeting
12.55 days
20 days
COTS Interface Questionnaire Completion
10 days
30.5 days
Customer completes COTS Interface Questionnaires
5 days
35.5 days
On/Call Dispatch & Mobile Unit Launch
4.25 days
33 days
On/Call GIS Requirements Review
1.13 days
32 days
/Dispatch
OnCaii Cloud Environment Creation
1 dayda
31 days
IOC Phase Completion
0.88 days
32 days
Final Operation Capability (FOC) Phase
339 days
0 days
OnCall Dispatch System Build 1
16.25 days
48.26 days
OnCall Dispatch System Build 1
3 days
51.51 days
Customer Builds Out Remaining Data
10 days
54.51 days
OnCall Dispatch Deployment and Response Planning
Workshop
14.25 days
69.51 days
OnCall Dispatch Deployment and Response Planning
Workshop
3 days
70.76 days
Customer Builds Out Remaining Data
10 days
73.76 days
OnCall Dispatch System Build 2
14.25 days
88.76 days
OnCall Dispatch System Build 2
3 days
90.01 days
Customer Builds Out Remaining Data
10 days
93.01 days
Connectivity to Cloud Program
2.25 days
32.88 days
Active Directory Integration
0.5 days
36 days
Custom Interface Requirements Gathering
41.25 days
0 days
Interface to Telestaff
15.13 days
0 days
ICD Development
1.5 days
0 days
ICD Delivered to Customer
0.13 days
1.5 days
Customer Reviews ICD
10 days
1.63 days
ICD Updated based off Customer Review
0.5 days
11.63 days
Customer Approves ICD
3 days
12.13 days
Interface to WebEOC
14.13 days
1.63 days
ICD Development
0.75 days
1.63 days
ICD Delivered to Customer
0.13 days
2.38 days
Customer Reviews ICD
10 days
2.51 days
ICD Updated based off Customer Review
0.25 days
12.51 days
Customer Approves ICD
3 days
12.76 days
Custom Interface Development
3.13 days
15.13 days
On Premise Local Software Server Installation and
Configuration
2 days
32.88 days
OnCall Analytics Cloud Environment Creation
2.5 days
31 days
OnCall Dispatch GIS Consulting
15.13 days
33.13 days
OnCall Dispatch Fundamentals for Core Team
4.5 days
103.01 days
COTS Interface Product Installation and Configuration
9 days
40.5 days
OnCall Dispatch Configuration Consulting Session 1
14.25 days
112.51 days
OnCall Dispatch Configuration Consulting Session 2
14.25 days
131.76 days
OnCall Dispatch Configuration Consulting Session 3
14.25 days
151.01 days
Statement of Work
80
HEXAGON
Hosted OnCall Dispatch Implementation
OnOall Dispatch Customer Rules Engine Configure Lion
Workshop
17 days
170.26 days
CRE Configuration Workshop
4 days
173.26 days
Customer Configures CRE
days
177.26 days
Consulting
OnCall Dispatch I Mobile Unit Configuration Consulting
Session 1
14.25 days
170.26 days
OnCall Dispatch Fire Mobile Unit Configuration 1
3 days
171.51 days
Customer Configures OnCall Dispatch Mobile Unit
10 days
174.51 days
OnCall Dispatch I Mobile Unit Configuration Consulting
Session 2
14.25 days
189.51 days
OnCall Dispatch Fire Mobile Unit Configuration 2
3 days
190.76 days
Customer Configures OnCall Dispatch Mobile Unit
10 days
193.76 days
OnCall Dispatch Mobile Responder Configuration
2 days
40.5 days
Custom Interface Product Installation and Configuration/�
2.63 days
16.63 days
Standard Interface Product Installation and Configuration
6.13 days
17.63 days
Test Plan and Test Cases Development
0 days
133.01 days
Customer Functional Testing
30 days
203.76 days
Customer Functional Testing
10 days
203.76 days
Customer Provides Blocker Error Report
5 days
218.76 days
Customer Executes Test Plan Post-Blocker Error
Resolution
5 days
228.76 days
Hex a on -Led Training
38.5 days
234.26 days
OnCall Dispatch System Administrator Training//
5.5 days
234.26 days
C OnCall Dispatch I Train the Trainer lass #1
6 days
239.76 days
Mobile Unit Train -the -Trainer Class #1
4 days
245.76 days
Mobile Responder Train -the -Trainer Class #1
3 days
249.76 days
OnCall Dispatch I Train the Trainer Class #2
6 days
252.76 days
Mobile Unit Train -the -Trainer Class #2
4 days
258.76 days
Mobile Responder Train -the -Trainer Class #2
3 days
262.76 days
OnCall Analytics I Dispatch Training
7 days
265.76 days
Customer -Led End User Training (30 calendar days)
21 days
272.76 days
Replicate Cloud Environments
12 days
234.26 days
Cloud Cutover Plan
12.63 days
293.76 days
Cloud Program Readiness Review
0.5 days
306.39 days
Cloud Cutover to Production Use
6 days
306.89 days
Post Cutover Support Week 1
5 days
312.89 days
Post Cutover Support Week 2
5 days
317.89 days
Statement of Work
81
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment D — Training Curriculum
HxGN OnCall Dispatoh I Advantage System Administrator Training (Qty: 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 Dispatch Cloud Program and use available tools to administer and configure the
system.
MAJOR TOPICS
• Understanding the Environment
• Map Legend Management
• UI Editor
• Localized Strings
• Layout Manager
• Notification Configuration
• Custom Fields
• Parameter Management
• Deployment Configuration
• IResponse Plans Configuration
• Role Management
• Type 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 on site by Hexagon Personnel
Audience Audience
Personnel responsible for administering and supporting the system
Duration
Four/�(4) days
Student Capacity
Six (6)
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
HxGN OnCall Dispatch I Advantage Train -the -Trainer (Qty: 2)
HxGN OnCall Dispatch I Advantage Train -the -Trainer is a four -day comprehensive course to familiarize
communications personnel with the use of OnCall. Students will learn all of the essential functions of
OnCall including navigating the application, entering and updating events, performing inquiries,
handling units including updates and status changes, and communicating with other users. Students
completing the course should have a good working knowledge of using HxGN OnCall Dispatch I
Advantage.
MAJOR TOPICS
• Events — Creation, Updates, and Status Changes
• Mapping — Commands, Controls, and Views
Units — Status Changes and Properties Updates
6 Inquiries — Events, Units, and Employees
• Messaging — Send, Receive, and Attachments
• Using training guidelines and techniques for HxGN OnCall Dispatch I Advantage
PREREQUISITES
• Customer Cloud Environment fully staged and available
• HxGN OnCall Dispatch I Advantage fully licensed, staged, and available
• Credentials available
• Hexagon user account provisioned with local administrator rights on all appropriate workstations
TRAINING DETAILS
Method
Conducted on site by Hexagon Personnel
Target Audience
Personnel responsible for training call -taking and dispatching staff
Duration
Four (4)
Student Capacity
-days
Twelve ( 2)
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
HxGN OnCali Dispatch I Mobile Unit Train -the -Trainer (Qty: 2)
COURSE OVERVIEW
HxGN OnCaii Dispatch I Mobile Unit Train -the -Trainer is a two-day comprehensive course to familiarize
trainers with the operation and use of the HxGN OnCall Dispatch I Mobile Unit software. Trainers will
learn all of the essential functions of HxGN OnCall Dispatch I Mobile Unit including navigating the
application, creating, receiving and updating events, utilizing the map, performing inquiries, handling
units including updates and status changes, and communicating with other users. Trainers completing
the course should have a good working knowledge of HxGN OnCall Dispatch I Mobile Unit.
MAJOR TOPICS
• Create, receive and update active events
• Update active unit status and properties
• Submitting inquires for events and units
• Submitting and receiving messages
• 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
Two (2) days
Student Capacity
Twelve (12)
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCa11 Dispatch Implementation
Mobile Responder Train -the -Trainer (Qty: 2)
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
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)
85
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
HXGN OnCall Analytics I Dispatch User Training (Qty: 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 Dispatch. It will
provide instruction on accessing, viewing, and creating reports from the OnCall Analytics Report
portal.
It will also provide an overview of the delivered reports and data models. The delivered report
provides out -of -the box access to key performance metrics while the data models provide an easy
and powerful way for users to ask their own questions of the data and create new reports.
TARGET AUDIENCE
Personnel responsible for reporting and analysis (Report Builders, Report Consumers, and System
Admins)
MAJOR TOPICS
OnCaii 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 models
Creating and Modifying Reports:
• Add Visualizations
• Filtering Visualizations
• Formatting Visualizations
Pages — Size and Alignment
• Interacting and Sharing
Power Visuals
• Creating pin, cluster and heatmaps
• Playback data over time
PREREQUISITES
• Familiarity with Windows -based applications
• Familiarity with agency workflows
COURSE DETAILS
Course Duration
Two (2) days
Course Type
Conducted on site by Hexagon Personnel
Student Capacity
Ten (10)
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
HXGN OnCall Analytics 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 OnCall 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)
87
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment E — OnCall Cloud Specifications
88
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment F — System Configuration Diagram
PDF
89
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment G — CAD/Mobile Functional Specifications
Matrix
PDF
CAD -Moe e F o
90
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment H — Interface Descriptions
COTSIrite rfacas
ANI/ALI Interface
Description.
The ANI/ALI interface works with the Cell-te ker component of OnCal
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.
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 also be 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).
Assumptions.
• Hexagon assumes that the Customer's 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 traditional ANI/ALI Controller, this interface will have to be rescoped as a custom
interface. The Customer must provide complete specifications of the device or service providing
the data.
• 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.
91
� A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
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 OnCaii Dispatch CAD Link
• to ESO SafetyPAD
• to ESO FRMS
Description:
OnCall Dispatch I CAD Link interface will facilitate the automatic periodic transfer of event and unit
information from OnCall Dispatch to external systems such as Police Records Management, Electronic The Care, and Fire Records Management systems using XML files ASCII delimited files. I he third -
party vendor (or the Customer) is then responsible for importing the information into the designated
database.
The CAD Link interface includes support for configurable event profiles, these are sets of event criteria for
matching data field values within the OnCall events to be exported and a configurable target directory for
exported output files. The profiles act as event filters, determining which OnCall events are to be exported
to which file system directories (inboxes).
Assumptions:
• Hexagon assumes this is for the transfer of CAD event and unit data only to the specified
systems.
• Additional services are required from the third -party vendor to consume and distribute the incident
information provided via CAD Link.
• The Customer will be responsible for any data mapping
• The Customer will provide a technical resource as well as any necessary subject matter experts
• The Customer will provide a test system for installation and testing
• Hexagon will configure CAD Link to output to a single location where the Customer is responsible
for consuming the data
• The Customer is responsible for ensuring that any third -party vendor technical resources are
available to support the testing of this interface.
• Hexagon assumes that the third -party vendor will be utilizing XML protocols for this interface.
• This is a one-way interface. CAD Link exports OnCall Dispatch incident -related data, but it does
not import data. Any import is the responsibility of Customer or of the third -party vendor.
Constraints:
• OnCall Dispatch events must be closed before they are candidates for export by CAD Link.
92
� A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• CAD Link does not provide features for obtaining next available case numbers, location
verification, or any other OnCall Dispatch -related functionality or interface, it only provides export
of specified event data for closed OnCall Dispatch events.
HxGN OnCall Dispatch I Fire Station Alerting to WestNet First -In
Description:
OnCall Dispatch I Fire Station Alerting (FSA) is a software interface between OnCall Dispatch and fire
station alerting vendors. It provides a method for OnCall Dispatch to send audible alerts to fire stations.
The interface provides support for remote fire station turnout when units from a station are dispatched. It
interfaces to third -party alerting controllers, such as Zetron IP FSA, and performs such operations as
ringing alarms and enabling public address systems. Fire station operators can also change the unit
status of vehicles from the station, such as en -route and available -in -station, if the alerting controller
supports this feature. The actions taken in the fire station (ringing alarms, enabling PAs) are
implementation -dependent upon the station and the alerting controller. The functionality of this product is
limited to sending alerts upon the dispatch of a unit from a station, disabling alerts on a unit status
change, and setting unit status.
Assumptions:
• Hexagon assumes the Customer uses one of the existing Fire Station Alerting systems currently
supported:
WestNet CADI API version 1.0.6
CADVoice Locution: CADVoice version 5.10
Zetron IP FSA version 2.6.0
• One implementation of FSA interface is required for each distinct Turnout Controller. Hexagon
has assumed that all stations will use the same controller. If not, additional licenses and services
may be required at additional cost.
• FSA requires Xalt Integration as a prerequisite.
Constraints:
• Hexagon cannot be held accountable for incompatibilities in its interface that are due to changes
in input/output formats or data requirements of the vendor's product
• The Customer is responsible for providing complete and accurate documentation on the devices
with which FSA will be implemented
• The Customer is responsible for providing any specific SDK necessary to implement the interface
HXGN OnCall Dispatch I Deccan LiveMUM
Description:
OnCall Dispatch I Deccan LiveMUM Interface provides a two-way interface between OnCall and the
Deccan LiveMUM software for move -up algorithms to monitor and adjust resource coverage for Fire and
Ambulance agencies.
Deccan International's Move -Up Module (LiveMUM) interprets CAD unit and event data and presents it in
an easy to understand, color -coded map format for evaluating unit coverage. LiveMUM reveals holes in
93
41 HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
service area coverage and offers recommendations for reallocation of first responder units. LiveMUM
monitors OnCall Dispatch unit and event information and applies move -up algorithms to determine unit
move -up recommendations in real time. The OnCall Dispatch I Deccan LiveMUM Interface supports a
two-way interface between OnCall Dispatch and LiveMUM by which dispatchers are notified of move -up
needs in OnCall Dispatch. The dispatcher can then analyze, change move -up recommendations through
LiveMUM and execute the move -up in OnCall Dispatch. This relieves the strain placed on the dispatchers
to make complex analysis in maintaining the status of coverage in the service areas.
Benefits.
• Get a continuous updated display indicating the status of live engine, ladder, and ALS coverage
by accurately analyzing CAD data in real-time.
• Get color -coded maps that allow dispatchers to instantly view weaknesses and strengths in
coverage.
• Test and evaluate the effectiveness of pre -planned reallocations taking into account the various
specific agency criteria set by the agency.
• Achieve consistency in quality of reallocation across all dispatchers by removing need of personal
objectivity.
• Obtain a log of dispatcher decisions for review.
Assumptions.
• Hexagon only interfaces with LiveMUM for the relocation of units. Hexagon does not interface
with Deccan's ADAM or BARB products.
• This interface will send the standard XML protocol that Hexagon has defined for unit status
information to the Deccan -written server over the TCP/IP connection. Each unit status change will
result in a transmission from Deccan Interface to the Deccan -written server. This interface price
does not include the cost associated by Deccan to write their server piece.
• It is the responsibility of the external system vendor, or Customer, to develop any programs
necessary to interface with Deccan Interface using the provided XML documents.
HxGN OnCall aspatch ProQA Interface
Description.
The OnCall Dispatch I ProQA Interface for Paramount application is a protocol -based product that
provides a standard certified set of determination questions and answers that Police, Fire and EMS can
use to identify the necessary resources required when responding to an event. OnCall Dispatch I ProQA
Interface for Paramount is an add -in to the OnCall Dispatch I Call -Taker application (included with OnCall
Dispatch Advantage).
Key Features:
• Multidiscipline launching
• Pre -alerts
• Transfer of location information to OnCall Dispatch I Call -Taker
• Configured to spill key questions into the Event information remarks field.
94
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Assumptions:
• The OnCall Dispatch system supports ProQA version 13.0.
HxGN OnCall Dispatch I Tracker
Description:
HxGN OnCall Dispatch I Tracker accepts incoming Global Positioning Satellite (GPS) data directly from a
GPSdevice, location servers or mobile data devices. HxGN OnCall Dispatch I Tracker functions as an
extension to the dispatch environment, periodically updating vehicle and personnel locations in OnCall
maps and monitors.
Supported GPS Devices:
• Radios transmitting GPS data in the following message formats
Trimble TAIP messages, UDP connection
NMEAmessages, UDP connection
OpenSky messages, UDP connection
Harris GPS Radio Types M-803, M5300, M7200, M7300, P5400, P5500, P7200 transmit
OpenSky GLR1/GLP1 messages over UDP
OMA/MLP (web service)
Non -Supported GPS Devices
• Smartphones riot running Mobile Responder or Mobile Unit
• Motorola radios using the P25 message
• Harris radios that do not support OpenSky messages
M7100, P7100, XG-100M, XG-75, XG-100P
Certain GPS devices also accept commands from external systems to control the frequency of location
reports. HxGN OnCall Dispatch (Tracker can be configured to send the appropriate commands to these
devices, setting the frequency of location reports based upon unit type, unit status, and the type of event
the unit is currently assigned to.
When OnCall Dispatch I Tracker is used with our mobile solution on MDC5, Mobile Unit uses the in -
vehicle map and high-speed access to the GPS receiver to match the vehicles route to the map to
determine the address of the vehicle. This approach is necessary because mapping information is seldom
as accurate as the GPS device. The map is often several hundred feet off from the true location. This
approach is more accurate than the more common method of using a server to attempt to place a point
on the map based on a single position report. The computed location is used to pre -populate forms
requiring a location such as on -view incidents and unit emergency. The officer can override the location if
required as a final check before submitting the command.
The selected GPS receivers may support commands to change their delta time and/or delta distance
reporting rates dynamically. AVL information may be used in the CAD system in the Recommend Unit
processing.
95
� 41 HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Depending on the existing AVL solution, the OnCall Dispatch I Tracker interface supports three different
modes of operation. passive, poll, and poll list.
• Passive mode interfaces to a radio system, data terminal system, or location server and directly
receives location reports from radio, MDT, or GPS devices. In the passive mode, OnCall Dispatch
ITracker exerts no control over the behavior of the location reporting devices and only receives
these location reports, processes their contents, and forwards them to OnCall Dispatch when
needed.
This mode is useful when the devices are not capable of responding/honoring the poll rate
commands that are issued to them from OnCall Dispatch I Tracker. This mode is also used when
the GPS devices in service are capable of regulating their own polling.
• In poll list mode, OnCall Dispatch I Tracker may interface with a location server or controller, that
is, a software/hardware solution that performs the actual polling of vehicles and devices. The
location server/controller may also perform other functions, such as differential correction. This
could be some software application running on a different server (Windows, Linux, and so forth)
or some other type of hardware controller (a "black box") that communicates with the devices
OnCall Dispatch I Tracker needs to set the poll rates for. In this mode, OnCall Dispatch I Tracker
does not communicate directly with these devices but instead goes through an intermediate
"solution" that communicates with the devices. Essentially, this is an indirect mode of
communication where OnCall Dispatch I Tracker must go through third -party "solution" to
communicate with the devices.
OnCall Dispatch I Tracker builds a list of devices internally that it packages up and sends to the
location server or controller ("solution") when it sets poll rates in the "poll list" mode. All devices
are then divided among poll groups which are configured in the AVL Poll Group dialog. OnCall
Dispatch I Tracker assigns each unit to one of these poll groups based on specified parameters
of the unit. As in the poll mode, these may include a unit's type (agency/dispatch group), unit
status, event type and/or last reported velocity.
Each poll group has an associated polling interval. For example, a poll group may be defined to
be all vehicles whose status is 'ON SCENE' and whose last reported velocity is less than 10 miles
per hour, the polling interval for this group could be set to 600 seconds (10 minutes). When
OnCall Dispatch I Tracker determines that the last location report for a vehicle in this polling
group is more than 10 minutes old, it will generate a new poll request to the controller. The poll
group with the largest polling interval defines the maximum polling cycle for the fleet.
The poll list mode is used to minimize the contention for radio frequency bandwidth. The location
server/controller sends out the location queries to each device in the polling list along with a time'
slot during which it expects to receive the corresponding location report. In this manner, the
controller seeks to guarantee that no two vehicles will attempt to transmit a location report
simultaneously.
• Poll mode requires the devices to be programmable by an external source. This programmability
allows the reporting behavior of the device to be by varying parameters, such as delta distance
and/or delta time that are transmitted directly to each device. In poll mode, all devices are divided
among a certain number of poll groups. OnCall Dispatch I Tracker assigns each unit or device to
one of these poll groups based on certain parameters of the unit.
OnCall Dispatch I Tracker actively changes these parameters by assigning new values based on
a unit's type (agency/dispatch group), status (Available, On -Scene, and so forth) and an event
type. For systems that include velocity in the location report, the last reported velocity may also
be used to determine the location reporting behavior.
Assumptions.
• Licensing is by device
96
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
• OnCall Dispatch I Tracker is a zero -cost product when bidding Hexagon mobile clients (Mobile
Unit and Mobile Responder)
Pricing is only required when connecting to non -Hexagon devices such as radios and third
party mobile clients
• OnCall Dispatch I Tracker must be installed and licensed to track any device even if there is no
• The OnCall Dispatch I Tracker interface establishes communications between a third -party AVL
controller/message switch and the OnCall Dispatch System.
• Hexagon assumes that communication with the AVL controller/message switch will be achieved
via TCP/IP or serial line (RS-232) communication protocol.
• The OnCall Dispatch I Tracker interface supports NMEA, OpenSky, UlueTree, Sierra Wireless
RNAP, and TAIP protocols and devices that support these protocols should be compatible with
OnCall Dispatch I Tracker. If the Customer is currently running AVL hardware that OnCall
Dispatch I Tracker does not support, additional services must be purchased to develop a custom
AVLinterface.
• Hexagon recommends that the Customer purchase a device such as the Sierra Wireless, Trimble
TrimFleet, or Airlink modems that supports one of the above protocols.
• Hexagon assumes that the Customer uses one of the supported GPS Receiver/Systems. If the
Customer requires Hexagon to interface to a GPS Receiver/System that is not supported,
additional development services will need to be quoted.
Constraints.
• The Customer is responsible for providing Hexagon with a complete and accurate description of
the interface to the AVL controller/message switch.
• If the Customer has AVL hardware that OnCall Dispatch I Tracker currently does not support,
Hexagon reserves the right to bid additional services to develop a custom AVL interface.
• Hexagon cannot be held accountable for incompatibilities that occur in this interface as the result
of changes to input/output formats or data requirements associated with the third -party vendor's
product.
Standard Interfaces
PLT Radio OnCall Dispatch Interface to Harris Radio
Description.
The PLT Radio OnCall Dispatch Interface is an interface between Hexagon OnCall Tracker and a P25
Radio System to support receiving GPS data from the radio systems and report them to OnCall Dispatch
as Tracker messages. This functionality is specific to the Person Level Tracking (PLT) Features in
OnCall Dispatch.
The vendors supported are:
• Motorola ASTRO P25
• Harris StatusAware P25
97
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Assumptions:
• Additional third party licensing may be necessary, the Customer should consult with their radio
provider for additional information.
• Requires a separate license of HXGN OnCall Dispatch I Tracker.
• Any expense incurred by L3Harris for obtaining API, SDK, lab access, testing support, etc. should
be the responsibility of the Customer.
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.
Dispatch Alerts OnCall Interface to Everbridge
Description:
The Dispatch Alerts OnCall Interface provides a method for sending alerts, notifications and messages to
third -party providers used in turn to notify a defined group of people. Notifications can include unit
dispatch notification, command staff notifications, on demand personal notifications, etc.
Assumptions:
• The Interface is compatible with the Everbridge REST API Specification document dated January
18, 2017
Constraints:
• The Customer is responsible for providing complete and accurate description of the API needed to
interface, and for any software/hardware/data required to implement communications with the
external systems.
98
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Custom Interfaces
Telestaff
Description:
Hexagon will create an interface that monitors a folder for Telestaff updates. Updates will be processed
and submitted to RestAPI for updating. The interface and RestAPI will support updating the following
information in Personnel records:
• Name
• Personnel Number
• Badge Number
r• V�ehicle
•
Radio
•
Department
• Position
• Title
• Skills
Assumptions
• Components of this interface will be installed in the Customer's data center (the Local Software
Server).
Constraints.
• The Customer is responsible for providing complete and accurate description of the API needed to
interface, and for any software/hardware/data required to implement communications with the
external systems.
Web EOC
Description:
Hexagon will develop an interface that provides real-time event data transfer from OnCall Dispatch to
WebEOC for the purposes of supporting Incident Management workflows.
Constraints:
• The Customer is responsible for providing complete and accurate description of the API needed to
interface, and for any software/hardware/data required to implement communications with the
external systems.
99
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment J — Glossary of Terms
Capitalized terms that are not defined below or within the body of the SOW, shall have the same meaning T
as set forth in the Master Ter Glossary.
"Acceptance" T Task mean acceptance of a Task in accordance with I ask Acceptance Process.
"Analytics Cloud Program" means a certain Cloud Program that pertains only to OnCall Analytics.
"BenchmarkCriteria" means the objective criteria which identifies an intended outcome as reflected in,
as applicable, an ICD, a Design Document, Specifications, or Software Requirements (whichever
document having last addressed the functionality in question being dispositive)
"Blocker Error" means a Level One Error.
"I.rJIS" means the Criminal Justice Information Services Security Policy version number 5.0 formally
published by the Federal Uureau of Investigation, Criminal Justice Information Services Division.
"Cloud Consulting Services Order" means this Order for Cloud Consulting Services related to the
Cloud Applications identified in the Cloud Program Order
"Cloud oud Program Order71 means that certain Order, which identifies the Cloud Applications and Cloud
Term, executed simultaneously with this Order. For purposes of clarity, the Cloud Program Order is
separate and distinct from the Cloud Consulting Services Order.
"COTSInterfaces" means those Interfaces specifically identified in in the COTS Interface Questionnaire
Completion task
"Customer Responsibilities" means (1) those specific tasks and obligations identified in the SOW as
being the responsibility of the Customer and (2) those obligations, not stated in the SOW, but which
would otherwise be reasonably considered as being Customer obligations and responsibilities.
"Custom Interfaces1f means those Interface(s) specifically identified in the Custom Interface
Requirements Gathering task
"Customization" means a modification of the source code of Software.
Cutover Plan" means a document reflecting the Activities and actions necessary to complete Cloud
Cutover
"Day" ay means a calendar day.
"Design Document" means a document articulating the design and intended output of a Customization.
"Dispatch Cloud Program" means a certain Cloud Program, or as applicable, collection Cloud
Applications, that pertains only to OnCall Dispatch, including but not limited to, OnCall Dispatcher, OnCall
Calltaker, OnCall Viewer, OnCall Mobile Unit, and OnCall Mobile Responder
"D
ocumentation" means, whether in printed or electronic format, all documents digital or hardcopy)
delivered by Hexagon as part of the Project. Unless otherwise specified, it shall mean COTS
Documentation.
100
Aff A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
"Facility" means a Customer provided facility/building/room that. (i) Can accommodate up to twelve (12)
Customer participants, (ii) Has a projector and screen for displaying the content being presented, (iii) has
Project Workstations for each participant; and a Customer workstation available for Hexagon's use while
in the Facility.
"FIPS" means Federal information processing standards, which describe document processing,
encryption, and other information technology standards for government contractors.
"Fire/EMS" means the agency(ies) of Customer that are primarily oriented towards firefighting and
emergency medical response.
"GIS" means geographic information system
"Initial Project Schedule" means the initial iteration of the Project Schedule, which is contained in
Attachment A of the SOW.
"Interface Control Document" or "lCD" means a document reflecting the design and requirements of a
Custom Interface or certain(`Informer Interfaces based upon the requirements set forth in the Custom
Interface Requirements Gathering task.
"Help Desk Portal" the electronic portal through which Customer may access the Help Desk to among
other actions, log Services Requests, review the Knowledge Base
"Hexagon Project Manager" means the person authorized by Hexagon to coordinate and manage the
providing of Hexagon Services and Deliverables for the Project on behalf of Hexagon, in addition to being
responsible for other duties specified in the Agreement and SOW.
"Law" means the agency(ies) of Customer that are primarily oriented towards statutory and regulatory
code enforcement and service.
"Master Terms Glossary" means that certain Common Terms Glossary contained in the Agreement.
"NCIC" means the National Crime Information Center.
"Network nfrastructuref1 means the provision of adequate network and rote rn et connectivity to provide
sufficient operational bandwidth for the operation of the Cloud Program in a manner consistent with the
Product System Specifications together with all industry -standard network security, monitoring, and
protection.
means a substantially failed Test Case that would correspond to a Level Two, Level
Three, or Level Four Error (as defined in the HelpDesk website) if the Error occurred in a live
environment.
"P
roduction action ea y ystem1f means the earlier of. the point at which the Customer is either satisfied
with the testing results for the Cloud Program or the resolution of all Blocker Errors reporting during
Functional Testing.
"Project
Assumptions"means assumptions regarding the Project, which are listed in the
Changes in any of the assumptions will affect the scope, schedule, and/or cost of the Project.
"Project Start" means the date following mutual acceptance of the Cloud Consulting Services Order on
which Hexagon communicates to the Customer the Project shall commence.
101
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
"Project Team" means the applicable Core Team and other resources assigned to provide information or
services in connection with the Project, or applicable part thereof.
"Project Workstation17 means a computer workstation expressly excludes tablets or other smart
devices) that has. (i) Google Chrome installed and ready for use, (II) Internet access, (iii) at least one (1)
external monitor with a resolution no smaller than 1920x1080 (understanding two (2) external monitors
are recommended), (iv) the ability to connect to the web conference audio, and (v) a headset.
"PSAP" means a public service answering point.
"Records Cloud Program" means a certain Cloud Program, or as applicable, collection Cloud
Applications, that pertains only to OnCall Records.
"Server Setup Worksheet" means a document reflecting, among other details, the identification of
servers, IP addresses, and node names for the System.
"Site Configuration Document" means a document reflecting the configurations made to the System.
"S
oftware wareRequirements" means the functionality and capabilities affirmatively included in the OnCall
Software as expressly specified in OnCall Functional Matrix.
"S
pecifications" means those certain capabilities and fu nctionalities as explicitly expressed in the User
Guide for OnCall Dispatch. To the extent there is any ambiguity as to the interpretation or meaning of a
Specification, the actual functionality exhibited in the COTS Software shall control.
"SR" or "Service Request" a request logged into Hexagon's Help Desk Portal identifying a request for
Hexagon to address a Error, question, provide an Update, or provide an enhancement request, among
other requests.
"Subject Matter Expert" or "SME" means a person(s) who has particular knowledge about a specific
topic(s).
"System Administrator(s)" means a person or persons having the appropriate education, training,
and/or experience in information technology to provide first tier support of the System.
"Task Prerequisites" means those events, Deliverables, or accomplishments that are required to occur
prior to the commencement of the applicable Task, except as may otherwise be agreed by Hexagon.
"Test Case77 means a set of conditions and parameters agreed to by the Parties which the Parties shall
use to test whether the intended functionality identified in the Benchmark Criteria is reflected in the
Sy ste m.
"T
est Case Failure" means a situation in which an executed Test Case has substantially failed in
meeting the passage criteria set forth in the applicable portion of the Benchmark Criteria.
"Updated Initial Project Schedule" means the Initial Project Schedule updated by the Parties' Project
"VPN" means virtual private network.
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment K —Azure Maps Overview
Hexagon's OnCall Dispatch System has been specifically designed to take advantage of server -based
mapping services that may be a part of portal architectures that expand the development and deployment
of Web mapping content. Having access to multiple basemaps and translucent raster overlays will allow
users to call up the most appropriate map features for any number of dispatching scenarios. These
services being available to users, yet managed in a highly available environment, is a significant
strengthening of dispatching capabilities and begins to take advantage of current GIS technologies, as
well as emphasizing the Web -centric nature of the technologies.
Mapping Technology within the HxGN OnCall System
GIS provider for HxGN Dispatch Cloud application. Azure Maps web map
services containing data for consumption by public safety and many other disciplines.
Web Map Service ' The map contains the area of responsibility for the dispatch system and is accessed
by HxGN OnCall Dispatch through Web map services. Many/�maps may be accessible and configured as
basemaps and/or translucent overlays to the basemaps. Azure Maps will be responsible for providing
Web mapping services and is the default GIS provider for the Hexagon OnCall Cloud Program. Resiliency
or the length of time the HxGN OnCall Dispatch system will wait to complete a request before returning an
error is governed by the resiliency RequestTimeOut parameter and by default is set to 15 seconds.
Note: The resiliency RequestTimeOut parameter is a high-level setting that applies to all URL requests
and is not specific to Just the Web map services being accessed.
Web Geocoding Service A Web geocoding service resolves address strings and street names to
longitude latitude coordinates (geocoding) and returns an address string for a point selected from the map
or precision coordinate key -in (reverse-geocoding). Azure Maps will be responsible for providing Web
geocoding services. Resiliency or the length of time the HxGN OnCall Dispatch system will wait to
complete a request to the geocoding service or aggregated geocoding services before returning an error
is governedat a high level by the resiliency RequestTimeOut parameter and ata low level by the
geocoding AggregatorTimeout parameter. The default value of the geocoding AggregatorTimeout
parameter is 5000 milliseconds (5 seconds) and applies to all the configured geocoders.
Web Routing Service A Web routing service is used to determine the best route between two or more
points on the map based on time and distance. The routing service can also return driving directions for
the calculated route. Azure Maps services have the capability to react to real-time traffic conditions,
thereby increasing the accuracy/�of route results and providing more efficient workflows which strive to
mimic real world conditions. Azure Maps will be responsible for providing Web routing services.
Resiliency or the length of time the HxGN OnCall Dispatch system will wait to complete a request before
returning an error is governed by the resiliency RequestTimeOut parameter and by default is set to 15
seconds. Latency in the Web router service could have an adverse effect on the recommend unit
functionality. The recommend unit architecture has been extended to perform routes for multiple units in
parallel thereby reducing susceptibility to latency issues.
Pol„gons — The HxGN OnCall Dispatch System architecture has been expanded to take advantage of
spatially -enabled database functionality available within Microsoft SQL Server and Oracle. The HxGN
OnCall Dispatch System now supports storing polygons using the Geography data type for SQL Server
and for Oracle, ST_Geometry (a data type that is interoperable with the SDO_Geometry data type).
Deployment areas, special situations, and special addresses are now stored as uniquely attributed
polygons in the database. For example, a four-story building with each floor having a unique response
could be represented by four coincident polygons, each with a keyword and the overriding agency
103
A HEXAGON
Miami City Eire Rescue
Hosted OnCall Dispatch Implementation
response and additional messages. Special addresses have historically been part of the location
verification system and used as rooftop locations. Now, Hexagon leaves address validation to the
Geocoding services, and polygonal special addresses are used to augment the user workflows with
messages or deployment overrides.
Azure Maps
Azure Maps is a collection of geospatial services that use fresh mapping data to provide accurate
geographic context to web and mobile applications. The Cloud Dispatch Program is currently using the
Routing, Map Rendering and GeoCoding services. Additionally, Azure Maps provides the features below.
• REST APIs for rendering maps in multiple styles and in satellite imagery.
• Searches for addresses, places, and points of interest around the world.
• Routing point-to-point, multipoint, multipoint optimization, isochrone, commercial vehicle, traffic
influenced, and matrix routing, viewing traffic flow and incidents.
• Mobility services for requesting public transit and alternative modes of transportation (like bike
share, scooter share, and car share), and planning routes in real time.
• Establishing user location through geolocation, and converting location to time zones.
• Services for geofencing and map data storage, with location information hosted in Azure.
• Location intelligence through geospatial analytics.
Azure Map Services leveraged by HxGN Dispatch Cloud Application currently leverages the following
Azure services.
104
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Render Service
The service uses either high -quality raster graphic images, available in 19 zoom levels, or fully
customizable vector format map images.
Route Service
The Route service contains robust geometry calculations for real -world infrastructure and directions for
multiple transportation modes. The service allows for developers to calculate directions across several
105
4 41 HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
travel modes such as car, truck, bicycle, or walking. The service can also consider inputs such as traffic
conditions, weight restrictions, or hazardous material transport.
slid
S
0 Bellevue
Seattle
trY
Redmond
Sans
47)
5ammamish
•
m�, Microsoft
GeoCoding Service
When you search for a location with Azure Maps, the search service takes your search terms and returns
the latitude and longitude coordinates, a process called geocoding.
• Address points - Addresses data can be resolved to a latitude longitude coordinate within the
address parcel (property boundary). Sometimes referred to as Rooftop accurate. This is the
highest level of accuracy available for addresses.
• House numbers -Addresses are interpolated to a latitude longitude coordinate on the street.
• Street level - Addresses are resolved to the latitude longitude coordinate of the street that
City
the address. The house number may not be processed.
• level - City place names are supported.
High Availability
High availability can be defined as a system that remains continually operational. These systems
eliminate the threat of a single point of failure. Azure Map Service is a Platform as a Service (PaaS)
offering from Microsoft Azure. The Azure platform is responsible for availability via the use of Regions,
Availability Zones and performance thresholds. Because it is offered as a PaaS, Microsoft publishes the
Service Level Agreements (SLA) associated
https://a zure.micros oft.com/en-u sisu pport/legal/sla/a z ure-m a p sw10/
106
A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment L — Cloud Service Schedules
CLOUD PLATFORM PROVIDER:
REDUNDANCY:
Azure/SQL Active Geo-replication
SERVICE LEVEL:
99.5% Availability
SERVICE CREDIT:
10% of the monthly fee for this Cloud Application
CLOUD SERVICES SUPPORT AVAILABILITY HOURS:
For Level One Error (P1) telephone support is available 24.7.365; for all other errors telephone support is
available between 07:00 — 19:00 CT US.
PRODUCTS: The products listed below are subject to this Schedule.
PART NUMBER
HCL1103
HCL1105
PART DESCRIPTION
Dispatch Alerts OnCall Interface - Cloud
PLT Radio OnCaii Dispatch Interface - Cloud
HCL1122
HCL1132
HCL1133
HCL1134
HCL1155
HCL1166
HCL1186
H.GN OnCall Dispatch -Advantage -Cloud
H.GN OnCeii Dispatch - Resource Management 'Cloud
H.GN OnCall Dispatch - Advanced Mapping - Cloud
H.GN OnCaii Dispatch - Scheduling & Facilities Mgmt - Cloud
H.GN OnCall Dispatch - Essentials - Cloud
H.GN OnCall Dispatch - Viewer - Cloud
H.GN On Call Dispatch - Tracker - Cloud
HCL1195
HCL1197
HCL1202
H.GN OnCall Dispatch - RestAPI - Cloud
H.GN OnCall Dispatch - Fire Station Alerting - Cloud
H.GN OnCall Dispatch - Mobile Unit - Cloud
107
41 HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
PART NUMBER
PART DESCRIPTION
HCL1203
HCL1206
HCL1230
HCL1231
H.GN OnCall Dispatch - Deccan LiveMUM Interface 'Cloud
H.GN OnCall Dispatch - CAD Link Interface - Cloud
H.GN OnCall Dispatch I Customer Rules Engine Editor
H.GN OnCall Dispatch I Customer Rules Engine Client
HCL1232
H.GN OnCall Dispatch I Customer Rules Engine Server
HCL2310
H.GN OnCall Analytic. - Viewer - Cloud
HCL2311
HCL2312
HCL3209
HCL3213
H.GN OnCall Analytic. - Author - Cloud
H.GN OnCall Analytic. - Dispatch Data Models & Reports - CLD
H.GN OnCall Dis
H.GN OnCall Integration Engine
Assumptions.
The Azure environment includes three (3) environments and shared components across all of the
Customer's environments. The following reflects the Cloud Application capacity that has been
purchased. Use beyond any single Cloud Application capacity limitation identified below are governed by
Shared Environment resources — used throughout the OnCall environment includes:
Customer storage — 1 TB hot block blob storage
AKS Control Plane — 6 Linux nodes
Message Bus — 3 Linux nodes 2 core
1 VPN Gateways
10 Units
Azure Front Door - monthly
.5 TB inbound
30 Routing rules
Azure Mapping Per (per Month)
250KMap tile, Route and Geoiocation transactions ea.
100KSearch transactions
108
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
10KImagery and Static Map transactions
• 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:
2 Standard SKU databases with 100 GB
6 Linux nodes 4 core
Production (1) — includes:
4 2 core Business Critical SKU databases with .5 TB storage Z-RS
6 Linux nodes mix of 4 core and 2 core
150 GB egress data (monthly)
75 GB intra-regional (monthly)
109
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment M — Regional Provisions
The following terms, including any sub -attachments to this Attachment M, modify provisions set forth
above to accommodate regional requirements. To the extent there is any conflict between the terms
specified below and the terms set forth in the remainder of the SOW, the following shall control.
1. A Business Day includes up to eight (8) Business Hours, including breaks, during a twenty-four
(24) hour period.
2. Upon Customer request, Hexagon personnel may undergo a criminal background check
consisting of biographical information necessary to initiate an NCIC query and fingerprinting. To
the extent the Customer requires Hexagon personnel to undergo such criminal background
check, the Customer shall arrange for such criminal background check and fingerprinting and be
responsible for all costs associated with the criminal background check and fingerprinting. Any
remote personnel shall only be required to provide biographical information necessary to initiate a
NCICquery and a fingerprint card completed by any law enforcement agency.
3. The Cloud Program shall(�store data (in either transit or at rest) in the Cloud Environment, which is
within Microsoft Azure Government Cloud. Customer is solely responsible for (i) assuring it is
permitted by appropriate State agencies to transmit CJI and store data (in either transit or at rest)
in the Cloud Environment and (ii) otherwise complying with and ensuring this Project and the
Cloud Program to be provided does not violate applicable State CJIS policies.
4. Per CJIS security policy, customers who wish to access U.S. national databases using mobile
devices must use data encryption that is FIPS 140-2 certified and meets other CJIS
requirements. The Customer is responsible for ensuring that their data communications
infrastructure and devices comply with CJIS and applicable State requirements.
110
„ A HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment M-1 — CJIS Security Addendum
FEDERAL BUREAU OF INVESTIGATION
CRIMINAL JUSTICE INFORMATION SERVICES
SECURITY ADDENDUM
The goal of this document is to augment the CJIS Security Policy to ensure adequate security is provided
for criminal justice systems while (1) under the control or management of a private entity or (2)
connectivity to FBI CJIS Systems has been provided to a private entity (contractor). Adequate security is
defined in Office of Management and Budget Circular A-130 as "security commensurate with the risk and
magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of
information.”
The intent of this Security Addendum is to require that the Contractor maintain a security program
consistent with federal and state laws, regulations, and standards (including the CJIS Security Policy in
effect when the contract is executed), as well as with policies and standards established by the Criminal
Justice Information Services (CJIS) Advisory Policy Board (APB).
This Security Addendum identifies the duties and responsibilities with respect to the installation and
maintenance of adequate internal controls within the contractual relationship so that the security and
integrity of the FBI's information resources are not compromised. The security program shall include
consideration of personnel security, site security, system security, and data security, and technical
security.
The provisions of this Security Addendum apply to all personnel, systems, networks and support facilities
supporting and/or acting on behalf of the government agency.
1.00 Definitions
1.01 Contracting Government Agency (CGA) - the government agency, whether a Criminal Justice
Agency or a Noncriminal Justice Agency, which enters into an agreement with a private contractor subject
to this Security Addendum.
1.02 Contractor - a private business, organization or individual which has entered into an agreement for
the administration of criminal justice with a Criminal Justice Agency or a Noncriminal Justice Agency.
2.00 Re
2.01 The CGA will ensure that each Contractor employee receives a copy of the Security Addendum and
the CJIS Security Policy and executes an acknowledgment of such receipt and the contents of the
Security Addendum. The signed acknowledgments shall remain in the possession of the CGA and
available for audit purposes. The acknowledgement may be signed by hand or via digital signature (see
glossary for definition of digital signature).
3.00 Responsibilities of the Contractor.
3.01 The Contractor will maintain a security program consistent with federal and state laws, regulations,
and standards (including the CJIS Security Policy in effect when the contract is executed and all
111
41 HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
subsequent versions), as well as with policies and standards established by the Criminal Justice
Information Services (CJIS) Advisory Policy Board (APB).
4.00 Security Violations.
4.01 The CGA must report security violations to the CJIS Systems Officer (CSO) and the Director, FBI,
along with indications of actions taken by the CGA and Contractor.
4.02 Security violations can justify termination of the appended agreement.
4.03 Upon notification, the FBI reserves the right to.
a. Investigate or decline to investigate any report of unauthorized use;
b. Suspend or terminate access and services, including telecommunications links. The FBI will provide
the CSO with timely written notice of the suspension. Access and services will be reinstated only after
satisfactory assurances have been provided to the FBI by the CGA and Contractor. Upon termination, the
Contractors records containing CHRI must be deleted or returned to the CGA.
5.00 Audit
5.01 The FBI is authorized to perform a final audit of the Contractor's systems after termination of the
6.00 Scope and Authority
6.01 This Security Addendum does not confer, grant, or authorize any rights, privileges, or obligations on
any persons other than the Contractor, CGA, CJA (where applicable), CSA, and FBI.
6.02 The following documents are incorporated by reference and made part of this agreement. (1) the
Security Addendum; (2) the NCIC 2000 Operating Manual; (3) the CJIS Security Policy; and (4) Title 28,
Code of Federal Regulations, Part 20. The parties are also subject to applicable federal and state laws
and regulations.
6.03 The terms set forth in this document do not constitute the sole understanding by and between the
parties hereto; rather they augment the provisions of the CJIS Security Policy to provide a minimum basis
for the security of the system and contained information and it is understood that there may be terms and
conditions of the appended Agreement which impose more stringent requirements upon the Contractor.
6.04 This Security Addendum may only be modified by the FBI, and may not be modified by the parties to
the appended Agreement without the consent of the FBI.
6.05 All notices and correspondence shall be forwarded by First Class mail to:
Criminal Justice Information Services Division, FBI
1000 Custer Hollow Road
Clarksburg, West Virginia 26306
112
HEXAGON
Miami City Fire Rescue
Hosted OnCall Dispatch Implementation
Attachment N — Deccan LiveMUM SOW
Attachment N
�eccan LIVeMUM SC
113