My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
01-11-2023 Council Packet
>
City Council Packets
>
2020-2029
>
2023
>
01-11-2023 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/24/2023 10:34:07 PM
Creation date
4/24/2023 9:08:25 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
78
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
CONFIDENTIAL <br />SOW – City of Little Canada – AP Automation <br />Page 5 <br />Departmental Approval <br />Sub -process added to get necessary approval to pay invoices before they’re approved for posting <br />Can require initial coding and attachment of receipts or confirmation of receipt of goods at <br />departmental level <br />A detailed process outline has been attached to this SOW that specifies which components of the <br />templated framework are included in scope. <br />Change Management Process <br />It may become necessary to amend this SOW for reasons including, but not limited to, the following: <br />Changes to the project schedule, scope or budget <br />Changes in priorities (external or internal to the project) that impact the project <br />Environmental or architectural impediments not previously identified <br />Lack of access to personnel, facilities, or systems necessary to complete project as scoped <br />In the event that it is necessary to change this SOW, the following process will be followed: <br />A Project Scope Change Request (PSCR) will be used to communicate change. The PSCR must describe the <br />change, the reasons for the change, and the effect the change will have on the project, which may include <br />scheduling changes, pricing, etc. A PSCR will be initiated by OPG-3 but must be executed by both parties <br />to make it effective and binding on the parties. <br />Parking Projects <br />Once a project is started, if work is halted for two consecutive weeks (“Dead Weeks”) due to <br />circumstances beyond our control (like users are unavailable for testing), the project may be parked so <br />resources can be allocated to other projects. Once the impediment is removed, the project will be re- <br />activated as soon as resources are available. If a project is parked for an extended period, there may be <br />additional cost associated with the time required to get resources back up to speed.
The URL can be used to link to this page
Your browser does not support the video tag.