TRITECH SOFTWARE SYSTEMS -2015 - Laserfiche WebLink

Home Browse Search

9.4 Travel costs incurred by TriTech in connection with services rendered under this Agreement shall be paid by Client, payable upon receipt of TriTech's invoice for such costs. Travel costs submitted for reimbursement will be reasonable, actual costs in accordance with TriTech's travel policy, a copy of which has been provided to the Client. 10.0 ACCEPTANCE 10.1 General. Testing of the System and Subsystems shall occur throughout the Project life cycle as further defined in the Statement of Work (SOW). Client shall not suspend testing when problems are experienced and restart Acceptance testing when the problems are corrected unless the problems prevent continuing with Acceptance testing. If Acceptance testing must be suspended pending corrective action, Client shall promptly advise TriTech by the fastest available means. 10.2 Once the Pre -Go Live tests are complete in accordance with the process set forth and defined in the SOW, the Parties will mutually agree that the Subsystems are ready for Go Live. Such agreement will be documented in the Go Live authorization letter. 10.3 Final Subsystem Acceptance — Inform CAD, Inform RMS, Inform FBR, and Inform Mobile Subsystems. Each group of related Subsystems (Inform CAD, Inform Mobile and related interfaces are grouped together, and Inform RMS, Inform FBR and related interfaces are grouped together) shall be assessed separately during the Reliability Acceptance Test period. In the event that these two groups of Subsystems do not Go Live concurrently, they shall go through the Reliability Acceptance Test at different times, in accordance with the criteria set forth by this Agreement. Upon Go Live of each Subsystem or group of related Subsystems, the Client shall utilize the Subsystem(s) for a thirty (30) day Reliability Acceptance Test period to verify system reliability in a live environment. If no Critical Priority or Urgent Priority Software Errors (as those terms are defined in the Agreement) are reported during such thirty (30) day period, the Subsystem(s) shall be deemed to have passed the Reliability Acceptance Test. In the event that a Critical Priority or Urgent 'Priority Software Error occurs during the Reliability Acceptance Test period, TriTech shall commence actions in accordance with the Software Support Agreement to correct the reported error. 10.3.1 In the event that a Critical Priority Software Error occurs between day one (1) and day thirty (30) of the Reliability Acceptance Test Period, the Reliability Acceptance Test Period will be stopped and restarted at day one (1) once the Software Error has been resolved in accordance with the Software Support Agreement. 10.3.2 In the event that an Urgent Priority Software Error occurs between day one (1) and day fifteen (15), the Reliability Acceptance Test Period will be stopped and restarted from day one (1) once the Software Error has been resolved in accordance with the Software Support Agreement. If the Software Error occurs between day sixteen (16) and day thirty (30), the Reliability Acceptance Test Period will be stopped and restarted from day sixteen (16) once the resolution has been provided in accordance with the Software Support Agreement. Santa Ana System Purchase and Support Agreement Copyright © 2015 TriTech Software Systems Unpublished: Rights reserved under the copyright laws of the United States Page 13 of 104