Browse
Search
2024-566-E-Emergency Svc-Hexagon Safety, Infrastructure, & Geospatial-CAD Replacement
OrangeCountyNC
>
Board of County Commissioners
>
Contracts and Agreements
>
General Contracts and Agreements
>
2020's
>
2024
>
2024-566-E-Emergency Svc-Hexagon Safety, Infrastructure, & Geospatial-CAD Replacement
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/19/2024 9:22:46 AM
Creation date
11/19/2024 9:21:34 AM
Metadata
Fields
Template:
Contract
Date
9/13/2024
Contract Starting Date
9/13/2024
Contract Ending Date
9/26/2024
Contract Document Type
Contract
Amount
$2,729,399.34
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
246
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Orange County, NC <br /> <br />On-Premise OnCall Dispatch Implementation <br />Statement of Work 17 <br />5. Custom Interface Requirements Gathering <br />Task Description <br />During this Task, Hexagon and Customer will meet via conference call to validate the assumptions and <br />design of each Custom Interface identified in this SOW and Attachment H (Interface Descriptions). This <br />Custom Interfaces Requirements Gathering workshop is intended to contain a series of discussions to <br />validate the requirements and assumptions underlying the Custom Interfaces. These sessions should <br />include third-party vendors where appropriate. During the sessions, the specific workflow and data <br />requirements for each of the interfaces listed below will be discussed in detail. <br />The information obtained in combination with the information in Attachment H will be used to develop an <br />Interface Control Document for each Custom Interface. If the assumptions reflected in Attachment H <br />materially change, a Change Order may be appropriate. The ICDs will become the foundation for the <br />Custom Interface development by Hexagon. Once an ICD is mutually approved, it should only be <br />modified through a Change Order. The Customer shall not make any changes to and shall take <br />appropriate actions to prevent its third-party vendor from making substantive changes to the third-party <br />software that is the subject of a Custom Interface once that Custom Interface’s respective ICD has been <br />finalized. <br />The following are regarded as “Custom Interfaces” as the term is defined in Attachment I of this SOW: <br /> Text to 911 <br /> Query to OneSolution CAD <br /> Query to OneSolution RMS <br />For descriptions and assumptions regarding each Custom Interface listed above, please see Attachment <br />H: Interface Descriptions. <br />As it pertains to the development of the ICD, the parties shall follow the following process. After the <br />Customer provides the necessary information regarding the Custom Interface, Hexagon will prepare a <br />draft ICD for each Custom Interface. Hexagon will then provide the initial draft ICD to the Customer for its <br />review. The Customer shall review the draft ICD and provide any feedback or comments within ten (10) <br />Business Days. As appropriate, Hexagon will incorporate the feedback into the ICD or advise the <br />Customer why certain requests could not be included (e.g. the request conflicted with Attachment H) and <br />finalize the ICD. Hexagon will provide the finalized ICD to the Customer for its written acknowledgement. <br />The Customer will provide a response within three (3) Business Days from Hexagon providing the <br />finalized ICD. <br />Task Deliverables <br /> Workshop meeting minutes, to include notes on the specific workflow and data requirements for <br />each custom interface proposed <br /> ICD documents <br />Task Prerequisites <br /> Project Kickoff Meeting Task is complete. <br />Task Assumptions <br /> The Customer will coordinate interactions with the third-party vendors, including obtaining and <br />providing any API or specification documentation required to develop the proposed interfaces. <br />Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E
The URL can be used to link to this page
Your browser does not support the video tag.