Laserfiche WebLink
LAWSN <br />12. Lawson Implementation Methodology <br />Planning Phase <br />Design Phase <br />-Project Initiation <br />-Business <br />-As-Is Assessment <br />Transformation <br />.Application <br />and Design <br />Exploration <br />Technical <br />Infrastructure <br />•Detailed Technical Design <br />Planning <br />-Business Detail Design <br />-Project Plan <br />Development <br />•trtegration Plan <br />-Software <br />-Conference Room Pilot <br />Installation <br />.Policyand Procedure Review <br />•Project Team <br />Training <br />Construction <br />Phase <br />A cti v at ion <br />Phase <br />-Develop <br />Acceptance Test -Define Cut -Over Plan <br />Plans -End User Training <br />-Establish -Readiness <br />Production Data Assessment <br />-Cut- Over <br />-Acceptance <br />Testing -Product ion Support <br />Key Assumptions: <br />(6) Project transparency and communication channels will support the success of this Project and Lawson <br />assumes a schedule of management meetings with: <br />• the City Project steering committee every month and upon request within two (2) weeks' notice <br />• The Project's core project team for one (1) hour every week; other times upon request. <br />12.1 Deviations to Lawson Implementation Methodology <br />There are no deviations to the Lawson Implementation Methodology <br />SOW- SantaAna- 12Feb08 vFinal_v2.doc Confidential 43 <br />