Attachment C

CUSP SUB-PROJECTS

· Project Charter & Executive Sponsorship – First step in the enterprise CUSP project that was taken by the executives who had a vision for an integrated system. Project charter concluded with the City Council’s approval to develop an RFP for an integrated Customer Service, Billing, and Contract Enforcement. The Sponsorship task will continue for the length of the project.

· Business Question Assessment – The project manager assessed the need for this solution at a very high level.

· Discovery – Project manager and key business experts examine background, current systems and draw up a roadmap for the project.

· Request for Information (RFI) – An RFI was issued in order to educate staff on solutions in the market and to gather data from the industry on published prices and possible solutions.

· Business Process Improvement Project (PIP) – UBS and IWM business processes are shaped by antiquated solutions and systems that are available to business units. In order not to model the new system after the existing processes and procedures, a PIP was initiated for all business units in the CUSP scope. During this process cost savings were also documented that will play a big role in the Return On Investment (ROI) analysis later in the project.

· _{Stabilize Current System (IRIS/Socrates, etc) – In order to avoid duplicating improvements and efficient use of resources, improvements to the current system are now part of the CUSP project.}

· Current IT Infrastructure & Integration Requirements Study – This task is required for the development of a successful RFP.

· RFP Process – This process starts with documenting requirements and high level features gathered through the previous sub-projects and ends with the start of the Implementation phase.

· ROI Analysis – Analysis of cost savings compared to solutions proposed by the top few proposers is one of the selection criteria. This analysis will also serve as a measure for success of the system every year.

· Detail Technical and Functional Requirements & Specification (Solution Specific) – This sub-project is completed with the selected vendor and is designed to create a detail technical and functional map of the system.

· Implementation – Accomplished with conjunction with the contractor. The City’s project manager will be managing the overall project. Contractor’s project manager will report to the City’s project manager.

· Functional & Technical QA – Test plans will be developed by City staff or third party consultants and applied to the system before final acceptance.

· Deployment – Preparations and carrying out of the switch over to CUSP.

· Project Termination – Resource re-allocation.

· Maintenance – Our method requires that a team consisting of IT, business stakeholders and budget analysts be formed and exist for the life cycle of the system and have periodic business process reviews and feature and upgrade checks and do not allow home grown databases to develop because of lack of functionality that can easily be obtained through regular feature upgrades or new system reports.

· Risk Management (Continuous Throughout the Project) – This task started with a Risk Assessment Matrix and will continue to the end of the Termination sub-project.