Software Services Standards & Definitions

1. Change Request Procedure

The process below will be followed if a change to this SOW is required:

A Change Order (“CO”) will be the vehicle for communicating change. The CO must describe the change, the rationale for the change, and the impact the change will have on the project.

The designated Project Manager of the requesting Party (ACCESS or CLIENT) will review the proposed change and determine whether to submit the request to the other Party.

A written CO must be signed by both Parties to authorize implementation of the changes.

Several assumptions have been made regarding the nature of the services and Deliverables, which are incorporated into the pricing line items and unit multipliers described in the Price Schedule. Throughout the operational process descriptions within this SOW, additional assumptions (or clarifications of those already established) may be listed within the applicable operational process sections.

Changes to these assumptions could affect unit prices and could have an impact on the throughput rates or units encountered (and therefore, the actual extended costs invoiced) for each task performed as part of the services. In all cases, invoicing for all tasks performed will be based on actual units encountered during the conversion. Significant variances to these assumptions will be addressed as and when encountered, via a CO. This CO may result in revisions to project schedule, scope, budget, processes, assumptions, Deliverables, and/or unit pricing.

Analysis and approval of proposed process and method modifications under this Change Request Procedure, together with any resulting implementation of modifications so proposed and approved, will be performed by experienced and authorized team members from both ACCESS and CLIENT to the mutual agreement of both Parties in writing.