Laserfiche WebLink
Issue Group - Project <br />Goal Resolution <br />Response <br />Critical <br />High <br />Medium <br />Low <br />(Priority 1) <br />(Priority 2) <br />(Priority 3) <br />(Priority 4) <br />Scope Change Request <br />< =1 day <br />< =10 days <br />< =30 days <br />< =60 days <br />See below for priority <br />Response <br />definitions. <br />Project Implementation Issues <br />< =1 day <br />< =7 days <br />< =30 days <br />< =45 days <br />See below for priority <br />Response <br />definitions. <br />Decision Making Delays <br />< =1 day <br />< =7 days <br />< =30 days <br />< =45 days <br />See below for priority <br />Response <br />definitions. <br />Personnel Issues <br />< =1 day <br />< =15 days <br />< =30 days <br />< =45 days <br />See below for priority <br />definitions. <br />Conversion Issues <br />< =1 day <br />< =7 days <br />< =30 days <br />< =45 days <br />See below for priority <br />definitions. <br />Critical (Priority 1): <br />Issue is critical to the City and has significant impact on live processing, time sensitive <br />training or critical path tasks. <br />High (Priority 2): <br />Issue is severe, but there is a work around or intermediary action the City can take. <br />Medium (Priority 3): <br />Issue is a non - severe but requires follow up from Tyler. <br />Low (Priority 4): <br />Issue is non - critical for the City and they would like to work with applicable Tyler <br />resource as time permits. <br />B,1,22 Scope Change Process <br />If the City requires the performance of services that are not then being performed, or requires a change to <br />the existing services, the City's Project Manager shall deliver to the Tyler's Project Managers a scope <br />change request specifying the proposed work with sufficient detail to enable Tyler to evaluate it. Tyler, <br />within ten (10) business days, or longer as may be mutually agreed between the parties, following the date <br />of receipt of such change request, shall provide City with a written scope change proposal containing the <br />following: <br />• Detailed description of resources (both Tyler and City) required to perform the change <br />• Specifications <br />• Implementation Plans <br />• Schedule for completion <br />• Acceptance criteria <br />• Impact on current milestones and payment schedule <br />• Impact on project goals and objectives <br />• Price <br />All scope change requests and scope change proposals will be approved first by the City Project Manager <br />and Tyler Project Managers. Scope change requests will also be identified on the issues log and elevated <br />to the City Executive Team for review at the next Executive Team meeting. <br />Within the reasonable timeframe specified in Tyler's scope change proposal, which timeframe shall not <br />be less than ten (10) business days from the City Project Manager's receipt of such scope change proposal <br />(the "Response Period "), the City shall notify Tyler in writing if the City elects to proceed with the <br />change proposal. If, within the Response Period, the City gives notice to Tyler not to proceed, or fails to <br />give any notice to Tyler, then the scope change proposal shall be deemed withdrawn and Tyler shall take <br />no further action with respect to it. Tyler shall promptly commence performing the Services described in <br />CITY OF SAN MARCOS, TX PAGE 18 OF 62 <br />ERP PROJECT- FINAL SOW <br />