SOP: Change Control

If a substantial change is requested to a project scope after the quote or SOW has been signed, please follow the process outlined below. However, please note that AuraConnect involves a three month ramp period, unless specified otherwise in SOW. 

Initiation 

All change requests must be presented to and discussed by the parties’ project managers in the first instance. The party making a change request must provide the other party with the following items in writing: 

• A description of the proposed change accompanied by the specific reason(s) for the change. 

• A list of the documents and other components that will need to be kept updated if the change is implemented. 

• An indication of the level of evaluation that is required to assess the full impact of the change. 

• An estimate of the impact of the change. 

Evaluation 

The parties will then evaluate the change request to consider its feasibility and other relevant issues including cost, risk, performance, contracts, documentation and general impact on the Project. Upon completion of the evaluation, the change request will be presented for review/approval. 

Review and Approval 

Each change request will be reviewed by the parties to assess its merits and potential impact on the Project. If the parties approve the change request, it will be documented in this form and will be effective as of the date it is signed by both parties. The parties will ensure that decisions relating to change requests will be recorded in a change control log. 

Closure 

Following the parties’ written approval of the change request and any relevant impact on pricing, Aura will implement the agreed-upon changes. Aura may, but will not be obliged to, consider implementing change requests that fall outside the general scope of this SOW. Such changes will be subject to Aura’s then current prices.