Laserfiche WebLink
6 A i F k _ I - <br />RIVERSIDE PUBLIC UTILITIES <br />WI& Board Memorandum <br />P U B L I C U T I L I T I F 5 <br />BOARD OF PUBLIC UTILITIES DATE: DECEMBER 4, 2015 <br />ITEM NO: 5 <br />File ID — 15 -3851 — D <br />SUBJECT: ENQUESTA CUSTOMER INFORMATION SYSTEM UPDATE <br />ISSUE: <br />Provide an update and oral presentation to the Board of Public Utilities on the status of the enQuesta <br />Customer Information System implementation. <br />RECOMMENDATION: <br />That the Board of Public Utilities receive and file an update on the enQuesta Customer Information <br />System. <br />BACKGROUND: <br />On February 17, 2015, Riverside Public Utilities (RPU) replaced the Banner Customer Information <br />System (CIS) with enQuesta CIS. EnQuesta is a complex system that provides billing capabilities and <br />information for Electric, Water, Refuse and Sewer services. The system provides customer and billing <br />information necessary to support over 400,000 annual customer service contacts and generates over <br />$400 million in billings annually. <br />The project is currently in the "monitor & control" phase in which RPU is working closely with the <br />Innovation and Technology (IT) Department and the software vendor, Systems & Software, Inc., to <br />monitor the performance of the enQuesta CIS and make corrections as needed. As issues and defects <br />are identified, the incident is assigned an issue type (see table below). The incidents are tracked in a <br />database, corrective actions are completed by the vendor, testing is completed by RPU & IT and <br />solutions are deployed into the live system. <br />Issue Type <br />Definition <br />Critical <br />Immediate and significant impact to <br />billing groups of customers <br />High <br />Immediate and significant impact to <br />billing for individual customers <br />Medium <br />Inefficiencies or extra work for staff <br />Low <br />Nice to have <br />Currently, there are 162 critical and high issues, and 71 medium and low issues pending final resolution. <br />The incident count fluctuates as items are resolved and new issues are discovered. <br />Identification and resolution of software concerns is a component of the system stabilization process for <br />complex software applications. This process often takes a minimum of a year from implementation. <br />