11 - Laserfiche WebLink

— Increase the communication and project status among Operations Services Divisions — Provide an inventory system for vehicles, equipment, materials and supplies to support work orders — Make reporting easier—for both mandated reporting requirements and internal performance measuring — Improve work order routing Subtask 6.2: Test Plan Testing is a vital step in the implementation of the CMMS. Each element of the integrated solution must be tested to anticipate the proper operation of the system. Testing the various elements is balanced with the availability of resources, such as data, the test environment, and the right personnel to test with a well- documented Test Plan. The use of business process workflows will allow testers to verify the application configuration to support the To-Be business processes. Testing serves not only as a QA/QC measure of the system to check that elements have been captured and documented appropriately but also serves as an essential training tool for knowledge transfer and helps users become accustomed to the system. GHD will develop a Testing Plan which documents the following: — Goals for the testing program — Testing methodology including the test environment,involved participants,testing process,and schedule requirements — Change control documentation process — Acceptance procedures — Test scripts for work/service requests,work orders, inspection types,and integration components — Final acceptance sign-off document Subtask 6.3: System Testing GHD will work with the Testing Team staff to perform system acceptance testing within MaintStar to confirm consistency with defined workflows. Major system functions and primary workflows will be tested.Approved test scripts will serve as a checklist for System Testing. System testing serves a pivotal role in the implementation process as prior to this stage,the bulk of the implementation CMMS knowledge was led by GHD. By the time of System Testing, there is a defined knowledge transfer point where the City will be taking more ownership of the system with the support of GHD. System Testing should involve the core project team or power users. To effectively test the system, City testing staff must be properly trained. GHD will be onsite for three (3) days during Task 6 to provide initial onsite training and onsite test support. Day 1 will be Test Team training in preparation for testing. Days 2 and 3 will be onsite test support for testers who will work through test scripts,complete the test script forms, and submit them to a test administrator for review.The administrator will document system deficiencies into an Issues Log on SharePoint. Once testing is complete, the Issues Log will be the source of information for configuration deficiencies to be addressed by GHD and MaintStar. As some of the items listed as deficiencies may be product bugs or deficiencies,GHD will work with the City and MaintStar to agree on the items listed in the Issues Log that are to be corrected. Task 6: City Roles and Responsibilities — The City will identify the Test Team — Test Team will be available during onsite testing of new workflows Task 6: Deliverables — Initial one(1)day onsite Tester training — Final Testing Plan — Test Scripts for the six(6)OSD division's new work request and work order templates — Two(2)days of onsite testing support — Draft and final MaintStar configuration The Power of Commitment 11227916 I Proposal for Workflow Development&Integration into MaintStar CMMS Scope Update and Fee 10