Laserfiche WebLink
LAWSN <br />5.8 Final Acceptance and System Acceptance Criteria <br />The City will execute the Go -Live tasks by the estimated production completion date (s), as defined in the <br />Readiness Assessment(s). The "Actual Project Completion Date" will be the actual date the new system is <br />available for production operations as a result of successfully completing the Go -Live tasks. Initial Acceptance <br />shall occur once the City has successfully completed the Go -Live tasks for each project phase. <br />Once the City has completed the first month -end closing process for each phase, the City shall certify its final <br />acceptance of the Lawson system and the final milestone payments based upon them will be made. This <br />period will not exceed 60 calendar days from the Actual Project Completion Date. <br />System Acceptance Criteria <br />The system acceptance criteria should be the sum of all the deliverables throughout the project. The criteria <br />should verify if the deliverables were complete, and whether their results /content are still valid at the time of final <br />acceptance. <br />Following is the system acceptance criteria: <br />Criteria <br />Details <br />System Operation <br />The underlying technical infrastructure for the production environment is in place <br />and operating predictably; the production conversion (load) is complete, and has <br />been validated; the system is available for user transactions. <br />Testing <br />Unit and system testing has been executed per the Test Plan; integration testing <br />with all other systems has been executed per the Test Plan with satisfactory <br />results. <br />Business Requirements <br />Criteria have been addressed using the Functional Requirements matrix <br />documented in Schedule 1 for both Lawson and Systems and Software <br />applications. <br />User Readiness <br />Training is complete per the Training Plan. The Readiness Assessment is <br />complete <br />Procedures/Documentation <br />The documentation of operational procedures is complete, and available to users; <br />the system design documentation is complete and available to users; key <br />functional operational procedures have been executed successfully, key technical <br />operational procedures have been executed successfully (such as backup /restore <br />procedures, and critical patch - application procedures); and, all of the project <br />documents have been consolidated, and reside in a central location for easy <br />reference and audit. <br />Risk Management and <br />All open issues have been resolved, or identified as not required for system <br />Contingency <br />acceptance; a disaster recovery strategy is in place and available; and, backup and <br />recovery procedures are complete per the operational procedures. <br />SOW- SantaAna- 12FebN vFinal_v2.doc Confidential 20 <br />