Laserfiche WebLink
<br />EXHIBIT "A" <br /> <br />SCOPE OF SERVICES <br /> <br />Scope of Work for Stage 9 <br />Stage 9 represents a major enhancement to WAP. It consists generally of some relatively minor <br />maintenance improvements, plus support for multi-family residential (MFR) customers, <br />commercial (Comm) customers, and an analysis tool for drought scenarios. <br />Currently WAP supports only residential customers with bimonthly billing. Providing support for <br />MFR and Comm customers, and monthly billed residential customers, is fairly involved because <br />the data model must be changed to reflect the complex relationships among customers, sites, <br />accounts, and meters and calculations for water allocations must be extended to support <br />monthly as well as bimonthly billing. The new drought scenario tool represents significant new <br />functionality. <br />The work for Stage 9 is divided into categories of maintenance, general data model and <br />processing changes, data loading, drought scenarios, system test, documentation, and <br />miscellaneous. <br /> <br />MAINTENANCE <br /> <br />Task Description. Perform maintenance as described below. <br />. Record the identity of any user who enters or updates data in WAP. <br /> <br />. Make the query and reporting facilities and allocation calculator available in wapadmin2. <br /> <br />. Automate processing of account updates and exporting of the allocation master. <br />(See <br /> <br />. GENERAL DATA MODEL AND PROCESSING CHANGES for a discussion on why the <br />account master no longer needs to be imported.) <br /> <br />. Provide notification to WAP system administrator of new accounts. This will be done by <br />Redwood City IT. <br /> <br />. Support other ad hoc minor maintenance requests that may arise during the project. <br /> <br />Deliverables. Design, implementation, unit test. <br />Work Estimate. Not to exceed 90 hours. <br /> <br />GENERAL DATA MODEL AND PROCESSING CHANGES <br /> <br />Task Description. In order to implement support for MFR and Comm customers, the current <br />system must undergo significant changes to the data model and underlying software. Under the <br />current implementation for residential customers only, no distinction is made between customer <br />and account, or between account and meter. However, with MFR and Comm customers, we <br />have a much richer and more complex data model. We need to support the notion of a <br />Customer who is responsible for one or more sites, each of which may have one or more billing <br />accounts, each associated with exactly one meter. Water allocation targets apply to the <br />collection of all meters at a site. Water-saving programs such as toilet rebates will be applied at <br />the level of a customer's site. The formula for calculating water allocation will be a function of <br />the customer's class (residential, MFR, or Comm). <br />Note that the notion of site is not rigorously defined. Intuitively, a site groups meters for a <br />customer at a more-or-Iess contiguous set of locations. For Residential customers, a site is the <br /> <br />Agreement over $1 OK <br />City Attorney Approved Version 111803 <br /> <br />10 <br />