Laserfiche WebLink
'SMARTWORKS <br />• STATUS —current status of the risk (typical values are "open" or "closed") <br />The following Risk Matrix will be used to establish the severity of risk: <br />m <br />m <br />cc <br />a <br />6 <br />4 <br />6 <br />JM <br />2 <br />3 <br />Medium <br />High <br />(2) <br />(3) <br />IMPACT <br />Throughout the duration of the project, as risks are identified they will be added to the Risk Log and will <br />be reviewed at weekly Status Meetings with the team to determine the possibility of occurrence and the <br />best plan for mitigation. <br />If identified risk(s) and/or mitigation strategies are deemed to have an effect on project timeline, <br />budget, or scope, a Change Request may be created, as per section 4.3, to address those concerns. <br />Based on SmartWorks' experience, the following have been identified as dependencies that could have <br />negative effect on project timeline, cost and/or scope and could become potential risks: <br />• VPN ports not opened for SmartWorks personnel and for communication between integration <br />points <br />• AMI not ready on time, or not sending the data <br />• Data source not ready for DataSync <br />• Resources not available to provide required information <br />Early engagement and commitments on timelines by all parties can significantly reduce risks linked to the <br />above dependencies. <br />4.5. Acceptance Management Approach <br />In collaboration with Customer, SmartWorks will develop and maintain a central listing of all Deliverables <br />and Work Products to be completed throughout the project "Deliverable Acceptance Criteria <br />Document'. The Deliverable Acceptance Criteria Document will also set forth the acceptance criteria for <br />each deliverable ("Deliverable Acceptance Criteria"). <br />A baseline version of the Deliverable Acceptance Criteria document will be created through a combined <br />effort between SmartWorks and Customer during the Initiation and Build phase. The Deliverable <br />Acceptance Criteria Document will be reviewed with Customer regularly and updated to record the <br />approval of the Deliverables as they are accepted. The approvals of the Deliverables in the Acceptance <br />Criteria document will constitute final system acceptance. <br />A core component of the Deliverable Acceptance Criteria Document will be the execution of the test plan <br />and test cases. The Testing Plan, also created in the Initiation and Build phase, and the Test Case Scenarios, <br />City of Santa Ana—SmartWorks Statement of Work <br />2 5 H -73 Page 66 <br />