Orange County NC Website
Browse       Search
Orange County, NC <br /> <br />On-Premise OnCall Dispatch Implementation <br />Statement of Work 60 <br />30. Customer Functional Testing <br />Task Description <br />The Customer, with support from Hexagon, will test OnCall Dispatch’s conformance with the Benchmark <br />Criteria. The Customer will conduct Functional Testing over the course of ten (10) Business Days <br />(“Dispatch Testing Period”). During the Dispatch Testing Period, the Customer shall execute the CAD <br />Test Plan and corresponding Test Cases. Except as expressly provided, no other testing or evaluation <br />pertaining to OnCall Dispatch is contemplated in this Project. Customer will document and track the <br />results of each Test Case as either pass or fail and may request Hexagon consultation as necessary <br />during its testing Activity up to twenty-four (24) Business Hours. <br />Within five (5) Business Days of the end of the CAD Testing Period (“CAD Reporting Period”), the <br />Customer shall file any Blocker Defects and Permissive Defects encountered during Functional Testing – <br />Dispatch through Hexagon’s Customer Resource Management (CRM) system. For any Blocker Defect <br />identified, the Customer shall provide, at minimum, the following information: a description of the Defect <br />and the steps used to reproduce it, the functionality tested when the Blocker Defect was encountered, the <br />manner in which the functionality was tested, and the outcome when the functionality was tested. If the <br />Blocker Defects are not filed within the CAD Reporting Period, it is presumed Functional Testing was <br />completed without any Blocker Defect, and this Task is complete. Only Blocker Defects reported by the <br />conclusion of the Reporting Period will be resolved as part of this Task. The existence of Permissive <br />Defect(s) shall not preclude or be a condition of completion of any subsequent Tasks or implementation <br />of a new Release. <br />To the extent requested, Customer agrees to promptly respond to requests for additional information <br />regarding the Blocker Defect requested by Hexagon. Upon diagnosing the Blocker Defect and validating <br />the Defect encountered meets the attributes of a Blocker Defect, Hexagon resources shall proceed to <br />resolve the Blocker Defect accordingly. If the investigation determines the reported Blocker Defect did not <br />meet the attributes of a Blocker Defect then the reported Defect will be reclassified in accordance with the <br />levels provided in the Master Terms Glossary. Alternatively, if the investigation shows the reported <br />Blocker Defect was caused by Customer hardware, Network Infrastructure, or Third-Party Software not <br />provided by Hexagon, or non-conformance with Attachments E and F, then Hexagon will provide such <br />information to the Customer for the Customer to resolve and the Blocker Defect will be closed and <br />regarded as complete. <br />As part of its resolution efforts, Hexagon may at its discretion provide a procedural or programmatic work <br />around, a configuration change, or provide an Update. Once the Blocker Defect(s) is addressed, Hexagon <br />will report to Customer the Blocker Defect has been addressed and the Customer will have five (5) <br />Business Days to execute its Test Plan (“CAD Resolution Testing Period”). <br />After the Functional Testing, the System is intended to be in a near complete state such that all <br />configurations and workflows have been built and tested in accordance with this Task. After this Testing <br />Task is complete the Parties may mutually agree the System should be altered, modified, or otherwise <br />changed. Hexagon shall condition its acceptance of additional modifications outside of addressing <br />Blocker Defects on the execution of a change order to address additional Services, Project Schedule <br />impacts, and fees. To the extent the parties mutually agree to such request and such request is made <br />and agreed upon before the 8th day of the End User Training Period (as defined below), then such change <br />can be addressed. The Customer acknowledges changes requested after this Task may affect the Project <br />Schedule. <br />Task Deliverables <br /> OnCall Dispatch Functional Testing <br />Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9EDocusign Envelope ID: 295A5D15-51E9-4D4A-ABF7-42411BB309FA