My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
25B - AGMT - PD SOFTWARE SYS
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2015
>
11/17/2015
>
25B - AGMT - PD SOFTWARE SYS
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/12/2015 2:33:31 PM
Creation date
11/12/2015 1:58:24 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Clerk of the Council
Item #
25B
Date
11/17/2015
Destruction Year
2020
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.
/
204
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
1311.A Reliability Acceptance Testing, Subsystem and System Acceptance <br />Final Subsystem Acceptance — Inform CAD, Inform RMS, Inform FBR, and Inform Mobile Subsyste s, <br />Each group of related Subsystems (Inform CAD, Inform Mobile and related interfaces are grouped together, <br />and Inform RMS, Inform FBR and related interfaces are grouped together) shall be assessed separately <br />during the Reliability Acceptance Test period. In the event that these two groups of Subsystems do not Go <br />Live concurrently, they shall go through the Reliability Acceptance Test at different times, in accordance <br />with the criteria set forth by this Agreement. Upon Go Live of each Subsystem or group of related <br />Subsystems, the Client shall utilize the Subsystem(s) for a thirty (30) day Reliability Acceptance Test period <br />to verify system reliability in a live environment. If no Critical Priority or Urgent Priority Software Errors (as <br />those terms are defined in the Agreement) are reported during such thirty (30) day period, the Subsystem(s) <br />shall be deemed to have passed the Reliability Acceptance Test. In the event that a. Critical Priority or Urgent <br />Priority Software Error occurs during the Reliability Acceptance Test period, TriTech shall commence <br />actions in accordance with the Software Support Agreement to correct the reported error. <br />o In the event that a Critical Priority Software Error occurs between day one (1) and day thirty (30) of <br />the Reliability Acceptance Test Period, the Reliability Acceptance Test Period will be stopped and <br />restarted at day one (1) once the Software Error has been resolved in accordance with the Software <br />Support Agreement. <br />In the event that an Urgent Priority Software Error occurs between day one (1) and day fifteen (15), <br />the Reliability Acceptance Test Period will be stopped and restarted from day one (1) once the <br />Software Error has been resolved in accordance with the Software Support Agreement. If the <br />Software Error occurs between clay sixteen (16) and day thirty (30), the Reliability Acceptance Test <br />Period will be stopped and restarted from day sixteen (16) once the resolution has been provided in <br />accordance with the Software Support Agreement. <br />6 If the Subsystems do not pass after three (3) restarts or resumption due to an unresolved. Critical or <br />Urgent Priority software error, the City and TriTech will develop a joint resolution plan. <br />Final System Acceptance. If all Subsystems Go Live together, Final System Acceptance shall occur at the <br />conclusion of the thirty (30) day Reliability Acceptance Test Period defined above. Should the Subsystems <br />be implemented in a two - phased approach with Inform CAD, Inform Mobile and related Interfaces in Phase <br />1; and Inform RMS, Infonn FBR and related Interfaces in Phase II, Final System Acceptance will be <br />achieved at the conclusion of the thirty (30) day Subsystem Reliability Acceptance test period for Phase 11 <br />(Inform RIvIS, Inform FBR, and related Interfaces) if there are no unresolved Critical Priority or Urgent <br />Priority software errors, including transfer of data between Inform CAD and Inform Mobile, and Inform <br />RMS and Inform FBR as defined in the Software Support. Agreement. In the event of Critical or Urgent <br />Priority software error, the steps in sections 103.1 through 10.3.2 will be followed. <br />8"7 <br />25B -122 <br />
The URL can be used to link to this page
Your browser does not support the video tag.