Orange County NC Website
Browse       Search
Orange County, NC <br /> <br />On-Premise OnCall Dispatch Implementation <br />Statement of Work 2 <br />Responsibilities, and Task Acceptance Criteria. The Tasks defined in the SOW may not be listed <br />chronologically, and the actual Project implementation Tasks and timelines will follow the Project <br />Schedule, unless otherwise noted. <br />Software Functionality and Support <br />As part of this Project, Hexagon shall provide licenses to Software identified in Attachment A (“Project <br />Software”). The Project Software is licensed in accordance with the End User License Agreement subject <br />to the GSA Contract. The Project Software shall have the capabilities and functionality set forth in the <br />Specifications corresponding to the Project Software, which reflects all of the functionality Hexagon is <br />obligated to provide. The Project Software shall only be tested to evaluate conformity to the <br />Specifications. The COTS versions of the Project Software will be provided, and, unless otherwise <br />provided in the Specifications, this Order does not include any Product Change Requests or <br />Customizations. <br />OnCall presents an iterative upgrading process that will also be reflected in the Project. Several times per <br />year, Hexagon may publish a new release to OnCall Software Products. Until the end of the Testing <br />Phase, Hexagon may periodically implement newer releases of OnCall within the Customer’s <br />environment, so the Customer may have a more current release of OnCall leading into the Training <br />Phase and Deployment Phase. <br />Upon Cutover, the Warranty Period for the Project Software shall commence as described in Attachment <br />K (Warranty). <br />Project Governance <br />Hexagon will assign a Project Manager at the beginning of the Project to act as the primary point of <br />contact at Hexagon for the Customer and provide general oversight and guidance for the Hexagon <br />Project team throughout Project. <br />To ensure successful delivery of the Project in accordance with the schedule, regular communications <br />and an escalation path are necessary. Typically, all formal communications will occur between the <br />Hexagon Project Manager and the Customer Project Manager. Generally, each Party’s Project Manager <br />will have, at minimum, a bi-weekly status conference with one another. On a monthly basis, Hexagon will <br />provide a status report reflecting completed Activities, upcoming Activities, at-risk Activities, other <br />pertinent matters affecting the Project, and, as necessary, an updated Project Schedule. The Customer <br />may propose revisions to the status report and its attachments, but it must do so within five (5) Business <br />Days, otherwise it is final and accepted by the parties. <br />Finally, on a quarterly basis, or more frequently if deemed necessary by the Parties, the Department <br />Sponsor for Customer, a Hexagon Director or Vice President responsible for operations, and the <br />Customer’s Project Managers shall hold a remote executive review meeting to discuss the status of the <br />Project and particular challenges impacting the Project. The two senior officials for both parties shall also <br />serve as the escalation point for disputes arising between the Project Managers. <br />Projects of this nature involve both Parties performing a variety of Tasks that are dependent upon one <br />another. With that type of relationship and the number of Tasks involved, from time to time delays may <br />occur. The Hexagon Project Manager and Customer Project Manager will address and take actions to <br />mitigate such delays, to the extent reasonably possible. <br />Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E