A | B | C | D | E | |
---|---|---|---|---|---|
1 | Attachment 1 - Functional Requirements | ||||
2 | City of Portland, Oregon | ||||
4 | |||||
6 | This attachment describes the City's function and feature requirements of the System. Included with this document is the score provided by Cayenta Canada, Inc. in response to the City's request for proposal in February 2003. | ||||
7 | |||||
9 | Points | Weight | Description | ||
11 | 5 | Current Base | The function is provided in the base product. No modification is required. | ||
13 | 4 | Planned Base | The function will be provided in a future release. No modification is required. | ||
14 | |||||
15 | 3 | Roll Into Base | The function will be developed and placed into the base at no cost | ||
17 | 2 | Partial Base | The function will be developed at some cost to the customer, however, all or a portion may be rolled into base. | ||
18 | |||||
19 | 1 | Other Base | The function can be obtained from another customers enhancements or a joint effort with another customer. | ||
20 | |||||
21 | 1 | Enhancement | This requires a specific enhancement to be developed for the customer which may or may not be rolled into base. | ||
22 | |||||
23 | |||||
24 |
A | B | C | D | |
---|---|---|---|---|
1 | FINANCIAL MANAGEMENT | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 1 | The CIS meets Governmental GAAP (Generally Accepted Accounting Practices) and GASB (Governmental Accounting Standards Board) requirements. | 5 | |
4 | 2 | Payments can be transferred between receivable types within the same account and between different accounts | 5 | |
5 | 3 | Uses double entry accounting to post detailed financial transactions to individual customer accounts and simultaneously post to one or more separate self-balancing general ledger (GL) control accounts within the CIS solution for multiple funds (currently Water and Sewer). User-defined GL control accounts may consist of (a) balance sheet accounts such as cash, accounts receivable, allowance for doubtful accounts, deferred revenue, and due tu/due from other funds, and (b) related income statement accounts such as revenue, discounts and allowances, and bad debts. | ||
6 | 4 | Cash, journal entries, and any other monetary transaction are posted before accounts are aged | 5 | |
7 | 5 | Balancing can be completed at user defined time intervals: daily, weekly, monthly or on demand | 4 | |
8 | A mechanism is provided to (respond to each): | |||
9 | 6 | Balance the details to the account totals | 5 | |
10 | 7 | Flag out of balance accounts | 4 | |
11 | 8 | Prevent posting of financial transactions to out of balance accounts | 5 | |
12 | 9 | Automatically suspends posting of any out-of-balance transactions during batch processing while allowing batch processing of in-balance transactions to continue | 5 | |
13 | 10 | Provide on-line entry for correction | 5 | |
14 | 11 | Automatically produces a report of transactions that do not balance | 5 | |
15 | 12 | System will assure that when billing adjustments are made, all appropriate GL transactions will be applied | 5 | |
16 | 13 | Provides adequate control, balancing and reconciliation between the billing cycle revenues and the general ledger revenue cycles. | 5 | |
17 | 14 | Ability to transfer delinquent balances by fund between a customer's accounts. | 5 | |
18 | 15 | Late payment penalty applied based on a flat dollar amount for all types of accounts. | 5 | |
19 | 16 | Debit returned checks back to the customer’s account reversing the amounts by fund originally applied and create appropriate returned check charge. | 5 | |
20 | 17 | Provide a report that tracks the total number of accounts on payment extensions, including the total deferred revenue. | 5 | |
21 | 18 | System will apply a returned check fee by fund upon entry of the reversal of the payment. | 5 | |
22 | 19 | Report of payments collected by receivable type for a specified period of time. | 5 | |
23 | 20 | Daily account balance report by receivable type. | 5 | |
24 | 21 | Report of accounts with balances past-due (aging of AR balances) for a predetermined number of days. The report would indicate accounts which are ready to be written-off. | 5 | |
25 | 22 | Provide for the transfer of records from the accounts receivable when collection activity has been completed. Appropriate G/L interface transactions will occur. | 5 | |
26 | 23 | System provides a means for automatically archiving and purging bad debt history information. | 5 | |
27 | 24 | Report of the amount owed by customers by fund who have filed for bankruptcy. | 4 | |
28 | 25 | Process payments from non-cash transaction such as crisis voucher, interfund transfer from another city agency | 2 | Cayenta confirms in base package. |
29 | 26 | Identification and reporting of payments by user-defined criteria | 4 | |
30 | 27 | Identification and reporting of payments by batch. | 5 | |
31 | 28 | Provides on-line corrections of misapplied and rejected payments | 5 | |
32 | 29 | Identify, accept, reconcile and allow transfer of unidentified payments | 5 | |
33 | 30 | Payments are allocated by fund to the customer account(s) in a user defined hierarchy (full, partial, overpayments), which is parameter driven and easy to modify. All payments/accounts are allocated identically by fund. | 5 | |
34 | User defined rules to automatically apply the distribution of partial payments or overpayments by fund. The distribution may include: | |||
35 | 31 | Service Type | 5 | |
36 | 32 | Fund (water, sewer) | 5 | |
37 | 33 | Percentage of Accounts Receivable | 5 | |
38 | 34 | Fees and Charges | 5 | |
39 | 35 | Line Item | 5 | |
40 | 36 | Age of past due receivables | 5 | |
41 | 37 | System will handle overpayments in a defined manner such as hold till next billing, prorate by fund according to the last billed transaction, prorate by fund using a fixed (user-defined) percentage. | 5 | |
42 | 38 | Provides on-line transfer of payments by account. The transfer process should reverse the exact transaction used to apply the payment. | 5 | |
43 | 39 | Cash must be balanced daily. System will balance for both total dollars received and the number of items by fund and by payment method and payment source. | 5 | |
44 | 40 | A consolidated cash report is provided for interface with G/L. Interface between the modules is electronic or manually entered from the consolidated report. | 5 | |
45 | 41 | Entry of updates/corrections for bank reconciliation information. Upon recognition of an error, a Utility representative can manually make a correction to a single payment or batch. A detailed audit trail of these transactions is provided. | 2 | Cayenta confirms in base package. |
46 | 42 | Transfer payments from one account or fund to another with the ability to review audit trail. | 5 | |
47 | 43 | Report accounts receivable transactions by type by customer. Report can be segmented by customer class, or by receivable and fund such as Water & Sewer | 5 | |
48 | 44 | Report aging of accounts receivable for all accounts by receivable type by customer and fund. Aging segments are flexible and may be 30, 60, 90, 120 days, etc. | 5 | |
49 | 45 | Report the aging of Receivables for accounts by customer segment (customer class, billing frequency, by rate, etc.) | 5 | |
50 | 46 | Report of the total Receivables by customer segment (Class, SIC, etc.). | 5 |
51 | 47 | On-line view and report of the aging of Receivables for accounts by dollar amount. | 5 | |
---|---|---|---|---|
52 | 48 | When refunds are made, the system records the information needed to make the appropriate journal entry(s) to the general ledger | 5 | |
53 | 49 | Automatically and immediately identify a credit balance on a finaled account | 5 | |
54 | 50 | Ability to reverse any refund or transfer. System will allow manual intervention to prevent an accounts payable transaction. | 5 | |
55 | 51 | System allows check generation or provides an interface to another system for check generation, such as an accounts payable system. | 5 | |
56 | 52 | System will provide a report of all requested refunds on a daily basis, so that a check can be cut offline | 5 | |
57 | 53 | System will provide the appropriate accounting interface to accurately debit/credit various accounts as refunds are processed, i.e.. issued, reissued, voided, etc. | 5 | |
58 | 54 | System allows refunds that have been issued and not presented for payment within a user defined number of days of issue to be placed in an unclaimed moneys account by fund. Unclaimed moneys are held by fund for specified period and then forwarded to the proper agency. | 5 | |
59 | 55 | Provides an automatic interface to the General Ledger/Financial Management System or reporting that allows manual update to the general ledger based on user-defined needs. The timing on this interface is user defined (daily, weekly, monthly, etc.) | 5 | |
60 | 56 | A daily accounts receivable reconciliation by fund, by service, by cycle day, by rate, etc. | 4 | |
61 | 57 | A daily transfer of revenues by fund as needed. | 5 | |
62 | 58 | Internal financial controls and balancing is provided. | 2 | Cayenta confirms in base package. |
63 | 59 | Prepare user-defined financial reports | 5 | |
64 | 60 | Provides for an automatic interface to G/L accounts payable or reports with information needed to allow manual entry to the G/L for processing credit refunds. | 5 | |
65 | 61 | Provides the ability to download a revenue file for analysis that includes both monthly and cumulative information of the following: Account number, meter number, usage total billed amount, etc. | 5 | |
66 | 62 | Automated annual calculation for unbilled revenue for billing periods defined by the user | 5 | |
67 | 63 | Individual rate schedules must contain a 17-digit code related to the City's accounting requirements | 5 | |
68 | 64 | Daily balancing to include cash, returned items, accounts receivable, deposits, billing, adjustments, payments, refunds and discounts. | 5 | |
69 | 65 | Capability for diagnostic reporting if out of balance | 5 | |
70 | 66 | Provides the ability to make necessary adjustments and close month end or accounting periods, as well as provide a secure auditable financial record. | 5 | |
71 | 67 | Capability for diagnostic reporting if out of balance when closing revenue months. | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | CUSTOMER ACCOUNT MANAGEMENT | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 68 | The CIS maintains separate data on customer accounts, properties and meters | 5 | |
4 | 69 | The property address links the customer account to a property profile | 5 | |
5 | The following fields have been identified to have search capability to get to a customer account record: | |||
6 | ||||
7 | 70 | Customer Name (Allow partial name search) | 5 | |
8 | 71 | Property Address | 5 | |
9 | 72 | Customer Account Number | 5 | |
10 | 73 | Meter Number | 5 | |
11 | 74 | Telephone Number | 5 | |
12 | 75 | Social Security Number (optional field) | 5 | |
13 | 76 | Federal Business Identification Number | 5 | |
14 | 77 | Drivers License Number | 5 | |
15 | 78 | Service Order Number | 5 | |
16 | 79 | Doing Business As (D.B.A.) name | 5 | |
17 | 80 | By Old Account Number from previous System(s) | 5 | |
18 | 81 | Joint Customer Name | 5 | |
19 | 82 | The CIS maintains on-line notification and statusing of the customers account and any special condition items associated with the account as defined by user. | 5 | |
20 | System will provide the following statuses of customer accounts: | |||
21 | 83 | Active: Customer Account Actively Billing for Service | 5 | |
22 | 84 | Inactive: Customer Account having never billed for service or activated | 5 | |
23 | 85 | Final Billed: Customer Account that has calculated a final billing and is now closed | 5 | |
24 | 86 | Pending: Customer Account waiting to start actively billing for service | 5 | |
25 | 87 | Write-off: Customer Account that has had a balance written off for bad debt, bankruptcy, etc. | 5 | |
26 | 88 | System will provide the ability to create user-defined account statuses. | 5 | |
27 | 89 | A single customer can be established with several accounts billing for several properties. | 5 | |
28 | 90 | All available services can be reviewed at the property on-line. | 5 | |
29 | 91 | The CIS allows the user to establish a customer on a Low Income Discount Program. | 5 | Modification: M1 |
30 | The CIS allows on-line access to account information from a consolidated view to a detailed view. Account views are provided as follows: | |||
31 | 92 | Consolidated view of a customer with multiple accounts. All accounts are billed separately. | 5 | |
32 | 93 | A service view (water, measured sewer volume, etc.) | 5 | |
33 | 94 | A meter or equipment view. | 5 | |
34 | 95 | On-line access to a similar view of the bill as it was produced and distributed to the customer. Bill information for the past 36 months should be available on-line. | 5 | |
35 | 96 | On-line access to the exact image of the bill for the past 36 months of customer consumption history, read dates, reading, and bill amounts displaying the most recent information first. | 5 | |
36 | 97 | On-line access for a minimum of three years of customer consumption history, read dates, reading, and bill amounts displaying the most recent information first. | 5 | |
37 | 98 | On-line view of account consumption/usage history by meter or by service. | 5 | |
38 | 99 | On-line access to total combined consumption across multiple meters and multiple registers. | 5 | |
39 | 100 | On-line view of account payment history. | 5 | |
40 | 101 | On-line view of how the payment was applied to charges and funds. | 5 | |
41 | 102 | On-line view of payment transactions for up to the minute postings. Batch processing is not required to view the payments made. | 5 | |
42 | 103 | On-line view of account billing history. | 5 | |
43 | 104 | On-line access for a minimum of three years of customer account transactions (including adjustments, payments) . | 5 | |
44 | 105 | On-line view providing an "Account at a glance". Information would include: A/R, deposit info, adjustments, payments, credit history, etc. | 5 | |
45 | 106 | On-line access to historical service orders for an account. | 5 | |
46 | 107 | On-line access to pending service orders for an account. | 5 | |
47 | 108 | On-line access to charges and fees pending and not yet billed (ie: collection charges, miscellaneous adjustments and calculated unbilled charges | 5 | |
48 | 109 | On-line view of all previous and present customer accounts at a property | 5 | |
49 | 110 | Consumption should be viewed by account. | 5 | |
50 | 111 | The CIS allows the user to assign a new customer account number or if the customer had previous service with the Bureau for the same property address, the CIS allows the user to reactivate their existing customer account number. | 5 |
51 | Customer Account profiles are automatically cross-referenced to check for the following duplicates (allow for override if duplicate found): | |||
---|---|---|---|---|
52 | 112 | Social Security Number | 5 | |
53 | 113 | Name | 5 | |
54 | 114 | Driver's License | 5 | |
55 | 115 | FBI | 5 | |
56 | 116 | An account will allow for joint customers | 5 | |
57 | 117 | Establish customer mailing address, including foreign address, specific to each account. | 5 | |
58 | 118 | If no mailing address, system uses the property address as the default to send billings. Allow for user-defined exceptions | 5 | |
59 | 119 | Allow accounts to have non-standard mailing address (ie, City Bills) | 5 | |
60 | 120 | The CIS allows on-line entry of a new forwarding address to an account & reflects this change on the account. Customers can indicate the date when the address will become valid, which in turn terminates the system's use of any previous mailing address as of that same date. | 5 | |
61 | 121 | Identify a customer as deceased and assign an executor to the account. | 5 | |
62 | 122 | At the time a customer account is accessed the system will highlight user-defined special conditions. | 5 | |
63 | 123 | The system will readily distinguish between active customers receiving services and customers pending activation (Pending Status) | 5 | |
64 | 124 | When a customer is established in the system they are immediately linked to a single customer account number. | 5 | |
65 | 125 | The customer can establish various addresses including; property addresses, mailing addresses, temporary addresses, etc. | 5 | |
66 | Information specific to the customer is maintained or is associated with a customer on one property address and account. This information is exclusive to this account. The information may include: | |||
67 | 126 | Billing History | 5 | |
68 | 127 | Payment History | 5 | |
69 | 128 | Consumption History | 5 | |
70 | 129 | Social Security Number | 5 | |
71 | 130 | Historical Rate Assignments | 5 | |
72 | 131 | Driver’s License | 5 | |
73 | 132 | Special Conditions | 5 | |
74 | 133 | Joint Customer Name | 5 | |
75 | 134 | Mailing Address, Including Foreign | 5 | |
76 | 135 | Debt Recovery History | 5 | |
77 | 136 | Doing Business As Name (D.B.A.) | 5 | |
78 | 137 | Phone Number(s) (Cell phone, Unlisted phone, fax, etc.) | 5 | |
79 | 138 | System supports the establishment and maintenance of user-defined special conditions. | 5 | |
80 | 139 | Users can define a start, end and review date for a special condition. | 5 | |
81 | 140 | System automatically generates a report defining special conditions that are pending removal. This report is generated "x" number of days prior to the removal or re-certification date. (User defined "x" number of days.) | 4 | |
82 | 141 | Special conditions should have a free form comment field. | 5 | |
83 | 142 | Special conditions should be modifiable and deletable | 5 | |
84 | 143 | Special conditions should be date and user stamped when created, modified or deleted. | 5 | |
85 | 144 | When moving customer in and out of a property, the CIS may generate a service order to shut off water service at the property if a new account is not established at the property within a user defined time period | 5 | |
86 | 145 | Display the status of the water meter at the property address and allow a user to create a service order if water meter is currently shut off. | 5 | |
87 | 146 | Automatically create the final bill for the customer getting closed at the property. | 5 | |
88 | 147 | Final bills are calculated based on end of service date according to the last on cycle read date or a new meter read (which is used to prorate for a Final Bill Read). | 5 | |
89 | System allows the following actions for changing property responsibility. System can use a current, retro or future date as user defines: | |||
90 | 148 | Move Out, Issue Final Bill | 5 | |
91 | 149 | Move In, Activate New Customer Account | 5 | |
92 | 150 | Move Out (Final Bill) / Move In (Activate CustomerAccount) | 5 | |
93 | 151 | The initiation of move in service orders will force out the previous customer and generate their final bill. | 5 | |
94 | 152 | A move in / move out service order made in error can easily be reversed on-line and all action originally generated by that service order is automatically reversed. | 5 | |
95 | 153 | Anytime a move in/move out is scheduled within "x" period of time to coincide with the meter reading window, the on cycle read will be used to complete the service order. | 5 | Modification: M5 |
96 | 154 | Upon account activation, billing is calculated from service and meter installation and/or connect date. | 5 | |
97 | 155 | When a customer enters into an agreement for service the system generates a non-intelligent account number and contain no more than 9 digits (customer ID - property ID) . | 5 | |
98 | 156 | System transfers bill options, rate assignment, bill frequency and other information as defined by the user to the new customer account automatically via the Move In or Move Out Service Order. | 2 | |
99 | 157 | Ability to open and/or close specific services without opening and/or closing others. | 5 | |
100 | 158 | Indicate on the new account that the customer has filed for bankruptcy on an old account at the same property. | 5 |
101 | 159 | The system provides for the recording of the customer notes, including date and time of contact and the CSR initials | 5 | |
---|---|---|---|---|
102 | 160 | Provide for an unlimited amount of notes/remarks | 5 | |
103 | 161 | Provide for free form notes/remarks of reasonable size | 5 | |
104 | 162 | Provide for categorization of notes/remarks. | 2 | Cayenta confirms in base package. |
105 | 163 | Provide options for sorting and displaying notes/remarks. | 5 | |
106 | 164 | Provide for the identification of critical notes/remarks. | 5 | |
107 | 165 | Provide pre-defined notes/remarks or comments. | 5 | |
108 | 166 | The CIS must provide a field on the property record that holds the owner of the propertie's account number and full name. This field is populated with the owner's information regardless if the owner is the party responsible for billing. This field must be user modifiable, deletable and insert capable. | 5 | |
109 | 167 | The CIS must provide a tool that verifies the validity of a mailing address, e.g. Postalsoft. | 5 | |
110 | 168 | A move in / move out service order that has not completed, can easily be modified on-line, therefor modifying all action originally generated by that service order. | 5 | |
111 | 169 | Move In and Move Out processes should be automated via Service Orders that obtain field reads and/or shut off and turn on meters. | 5 | |
112 | 170 | The CIS must support the possibility of "continous billing" at a property; which means specifically that a property must always have an active account to bill regardless if the property is vacant or demolished. | 5 | |
113 | 171 | The CIS must support the possibility that one customer account is only associated with a single property record, and never continued to a secondary property record. | 2 | |
114 | 172 | The CIS must easily allow for "correction" to a customer account's final bill date, as well as a new customer account's start date. "Correction" could mean either a change in the start or end date, or it could mean a total error and the customer never should have been started or ended. | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | PROPERTY MANAGEMENT | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | The property profile includes or is linked to the following data items (respond for each): | |||
4 | 173 | Meter History for that property | 5 | |
5 | 174 | Special condition at site, such as hazardous meter box, hospital, nursing home | 5 | |
6 | 175 | Meter location at site | 5 | |
7 | 176 | Impervious Area | 5 | |
8 | 177 | The CIS must provide a field on the property record that holds the owner of the propertie's account number and full name. This field is populated with the owner's information regardless if the owner is the party responsible for billing. This field must be user modifiable, deletable and insert capable. | 5 | |
9 | 178 | The meter remove service order will automatically update meter and meter component attribute values | 5 | |
10 | 179 | System allows for a meter to be removed without replacement and continue to bill on-cycle | 5 | |
11 | 180 | View consumption by property address or location | 5 | |
12 | 181 | The system must contain a field that captures the size of property (impervious area). This field must be modifiable by user and will be used to calculate stormwater charges. | 5 | |
13 | 182 | Provide a report that identifies usage on vacant properties. | 5 | |
14 | 183 | The meter install service order will automatically update meter and meter component attribute values (install read, install date, etc.) | 5 | |
15 | 184 | The meter exchange service order will automatically update meter and meter component attribute values (ie, exchange read, exchange date, etc.) | 5 | |
16 | A search capability provides keyword and partial search on all components of the property address. A property address can be identified by: | |||
17 | 185 | Property Number | 5 | |
18 | 186 | Intersecting Roads | 2 | Cayenta confirms in base package. |
19 | 187 | Meter Number | 5 | |
20 | 188 | Legal Parcel Number | 5 | |
21 | 189 | Service Address components | 5 | |
22 | The property address is standardized into components. Components include: | |||
23 | 190 | House Number (Allows for leading zero) | 5 | |
24 | 191 | Fraction/Extension | 5 | |
25 | 192 | Prefix | 5 | |
26 | 193 | Street Name | 5 | |
27 | 194 | Street Type | 5 | |
28 | 195 | Direction | 5 | |
29 | 196 | Space Number (apt, suite, bldg) | 5 | |
30 | 197 | Ability to have a companion address (multi-unit with separate street addresses) | 5 | |
31 | 198 | City | 5 | |
32 | 199 | State | 5 | |
33 | 200 | Intersecting Roads | 2 | Cayenta confirms in base package. |
34 | 201 | Route and Box | 5 | |
35 | 202 | Provide the ability to classify the property level by SIC code (e.g., car wash, restaurant, manufacturing, etc.) | 5 | |
36 | 203 | Maintain multiple contact information (third party) related to the property address. Owner account and name needs to be held at property for on-line reference. | 5 | |
37 | 204 | Capability to maintain user-defined property information. | 5 | |
38 | 205 | Maintain legal parcel information | 5 | |
39 | 206 | The system must contain a field that captures the number of dwelling units. This field must be modifiable by user and will be used to calculate multi-family class average | 5 | |
40 | 207 | On-line historical review of meters/equipment located at a property for a specific period of time. The historical timeframe is a table parameter which is modifiable. | 5 | |
41 | 208 | On-line view of all previous and present customer accounts at a property | 5 | |
42 | 209 | The CIS allows for the creation of a new property | 5 | |
43 | 210 | CIS allows charges (ie services) to be started and stopped for a single account on different dates. The system does not require the same start or stop date for all services | 5 | |
44 | 211 | Upon activation, billing is calculated from service and meter installation and/or connect date | 5 | |
45 | 212 | CIS automatically assigns a property ID number for new property addresses | 5 | |
46 | 213 | Validation of street names within city exists for establishment of the customer property. New addresses can be overridden when a non-existent street name is found. | 5 | |
47 | 214 | Allow entry of new service address information on a partial basis, the system understands the address is pending activation following successful completion of construction activities (e.g. when a subdivision is created). | 5 | |
48 | 215 | Customer accounts are assigned a date-driven primary billing cycle, all accounts within a cycle will bill on a scheduled day of the month. | 5 | |
49 | 216 | The cycle billing schedule is easily changed with the ability to combine multiple cycles, segregate cycles, accelerate or delay the billing of a cycle. | 5 | |
50 | 217 | Accommodate billing of accounts on a bi-monthly, monthly and quarterly basis. | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | METER MANAGEMENT | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | The system will accommodate the following meter types: | |||
4 | 218 | Water Meters | 5 | |
5 | 219 | Irrigation Meter | 5 | |
6 | 220 | Sewer Meters | 5 | |
7 | 221 | Paddle Wheel Meters | 5 | |
8 | 222 | Fireline Meters | 5 | |
9 | 223 | Sub Meters (Add/Subtract Meters) | 5 | |
10 | 224 | Identify all meters set at the property. Meters can be identified for each service | 5 | |
11 | An on-line search capability is supported, including: | |||
12 | 225 | Property Number | 5 | |
13 | 226 | Utility Assigned Meter Number | 5 | |
14 | 227 | Customer Name or Number | 5 | |
15 | 228 | Account Number | 5 | |
16 | 229 | Service Order Number | 5 | |
17 | The on-line review and update of all meter attributes and engineering information. Attributes may include: | |||
18 | 230 | Property Address and Location | 5 | |
19 | 231 | Meter Number | 5 | |
20 | 232 | Meter Type | 5 | |
21 | 233 | Meter Size | 5 | |
22 | 234 | Meter Manufacturer | 5 | |
23 | 235 | Test Dates | 5 | |
24 | 236 | Test Results | 5 | |
25 | 237 | Tested By | 5 | |
26 | 238 | Last Test Date | 5 | |
27 | 239 | Purchase Date | 5 | |
28 | 240 | Installation/Turn-on Date | 5 | |
29 | 241 | Remove Date | 5 | |
30 | 242 | Number of Registers | 5 | |
31 | 243 | Number of Dials | 5 | |
32 | 244 | On-line historical review of meters/equipment located at a property for a specific period of time. The historical timeframe is a table parameter which is modifiable. | 5 | |
33 | 245 | Provide viewing of meter set components by: Components Age, Components Manufacturer, Model Number, Received Date. | 5 | |
34 | Provide for statusing of the meters, including: | |||
35 | 246 | Inventoried (warehouse) | 5 | |
36 | 247 | Active | 5 | |
37 | 248 | Inactive | 5 | |
38 | 249 | Retired / Junked | 5 | |
39 | Reading Types should include the following, along with other user-defined types: | |||
40 | ||||
41 | 250 | Prorated | 5 | |
42 | 251 | Estimated | 5 | |
43 | 252 | On-Cycle | 5 | |
44 | 253 | Move Out | 5 | |
45 | 254 | Move In | 5 | |
46 | 255 | Information | 5 | |
47 | 256 | Shut Off | 5 | |
48 | 257 | Reconnect | 5 | |
49 | System updates and maintains the following information for each meter route: | |||
50 | 258 | User-defined route identifier | 5 |
51 | 259 | System generated next read date | 5 | |
---|---|---|---|---|
52 | Readings will be validated prior to billing, an example of the type of validations performed are: | |||
53 | 260 | Number of Dials On A Read | 5 | |
54 | 261 | Dial Turnover | 5 | |
55 | 262 | Read Units (gallons, ccf's) | 5 | |
56 | The system will provide the following reasonableness checks (high and low, zero consumption for "x" months) against recorded usage: | |||
57 | 263 | Current Consumption to Year Ago's Consumption and allow percentage of variance that is user defined | 5 | |
58 | 264 | Current Consumption to the Special Parameters Established by Users | 5 | |
59 | System maintains meter test history that contains the following items: | |||
60 | 265 | Date submitted for test | 5 | |
61 | 266 | Initials of person performing test | 5 | |
62 | 267 | Test results | 5 | |
63 | 268 | Date test completed | 5 | |
64 | 269 | Reason for test | 5 | |
65 | 270 | Test procedure performed | 5 | |
66 | 271 | Comments | 5 | |
67 | 272 | Meter problem description | 5 | |
68 | 273 | Person requesting test | 5 | |
69 | 274 | Must support recording of multiple test results for a given test scenario. | 5 | |
70 | 275 | Provide a credit or a charge to the customers account based upon the results of the customer requested meter test. Not automated. | 5 | |
71 | System provides for the following reading related information: | |||
72 | 276 | The CIS creates download (host) file for meter reading to interface with Schlumberger handheld software | 5 | |
73 | 277 | The CIS accepts upload read file from Schlumberger and creates service orders from meter reading codes | 5 | |
74 | 278 | Automatic resequencing feature for renumbering sequences based on modified sequence numbers in the upload file | 5 | |
75 | 279 | Accommodate a charge based on input from another service (measured sewer is based off of water readings) | 5 | |
76 | 280 | Measure volume based upon a measured flow. For example, meter readings | 5 | |
77 | 281 | Allow changes to the route, and/or sequence number without changing the account number. | 5 | |
78 | 282 | Automatic renumbering feature for re-arranging meters on a route to allow for addition of properties | 5 | |
79 | 283 | Automatic resequencing feature for renumbering sequences within a route to allow for the addition of meters | 5 | |
80 | 284 | Directly input a corrected reading and retain the corrected reading and the original reading. | 5 | |
81 | 285 | Use the actual read date to bill | 5 | |
82 | 286 | Support a minimum of 10 digits for storage and display of the read | 5 | |
83 | 287 | Does not allow duplicate meter numbers | 5 | |
84 | 288 | Allows Utility to assign meter numbers | 5 | |
85 | 289 | Allow sequencing new meters into meter reading routes | 5 | |
86 | 290 | The CIS calculates field high/low parameters and downloads the parameters to the meter reading device. | 5 | |
87 | 291 | Controls are provided for identifying data lost during the meter reading upload or download | 5 | |
88 | 292 | Download of meters based upon cycle billing and associated reading schedules | 5 | |
89 | 293 | View consumption by property address or location | 5 | |
90 | 294 | View consumption by account | 5 | |
91 | 295 | Provide for routes, sequence numbers | 5 | |
92 | 296 | Accommodate multiple routes per property address | 5 | |
93 | 297 | Allow for the establishment of a new route | 5 | |
94 | 298 | Allow for the deletion of a route. | 5 | |
95 | 299 | System will track the history of installations for a meter. | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | BILLING MANAGEMENT | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 300 | Any type of charge, refund or fee can be adjusted on-line within defined dollar limits for user classes. | 5 | |
4 | 301 | CIS recognizes active customer account and has the capability to bill, regardless of the water meter status | 5 | |
5 | 302 | Supports an unlimited number of user defined adjustment types, e.g. refunds, final bill, leaks, etc. | 5 | |
6 | 303 | The ability is provided to cancel and/or rebill selected charges on-line while maintaining the original billing history | 5 | |
7 | 304 | The CIS maintains read date, due date and bill date information on current and past bills | 5 | |
8 | 305 | The CIS does not force the customer account bill date to be determined by the scheduled meter reading date | 5 | |
9 | 306 | CIS allows charges, ie services, to be started/stopped for a single account on different dates. It does not require the same start/end date for all services | 5 | |
10 | 307 | On-line access for a minimum of three years of customer consumption history, read dates, reading, and bill amounts displaying the most recent information first. | 5 | |
11 | 308 | On-line view of account consumption/usage history by meter or by service. | 5 | |
12 | 309 | On-line access to total combined consumption across multiple registers | 5 | |
13 | 310 | On-line view of how the payment was applied to charges and funds. | 5 | |
14 | 311 | On-line view of account billing history. | 5 | |
15 | 312 | On-line access for a minimum of three years of customer account transactions (including adjustments, payments) . | 5 | |
16 | 313 | On-line access to charges and fees pending and not yet billed (ie, collection charges, miscellaneous adjustments and calculated unbilled charges). | 5 | |
17 | 314 | Multiple rate changes will be tracked and accommodated when rebilling a service. | 5 | |
18 | 315 | On-line adjustment of all charges, fees, surcharges, and refunds on a customer account for current and 36 previous months. For example: consumption charges, customer charges, miscellaneous fees. | 5 | |
19 | 316 | Provide the ability to adjust consumption, rebill the account, and have appropriate readings and revenue adjusted accordingly | 5 | |
20 | 317 | On-line review of adjustment history. The number of years of on-line adjustment history will be for a minimum of three years. | 5 | |
21 | 318 | Apply adjustments to accounts which have been written-off. | 5 | |
22 | 319 | Provide the ability to reverse transactions where a customer has been moved in/moved out of an address in error. Charges have been applied to the bill in error. Mechanism will be provided to easily rectify. | 5 | |
23 | 320 | A billing cycle will not be delayed if all reads are not received for the cycle. | 5 | |
24 | Accommodate billing for customers of various classes. For example: | |||
25 | 321 | Residential Single-family dwelling (owned or rented) | 5 | |
26 | 322 | Residential Multi-family dwelling (individually metered/non-metered buildings) | 5 | |
27 | 323 | Commercial Customers | 5 | |
28 | 324 | Residential Single Family Sewer Only | 5 | |
29 | 325 | Residential Multi Family Sewer Only | 5 | |
30 | 326 | Commercial Sewer Only | 5 | |
31 | 327 | Stormwater Only | 5 | |
32 | 328 | Wholesale Customers | 5 | |
33 | 329 | Pipeline Customers | 5 | |
34 | 330 | Flexibility to add additonal revenue classes(City specific) | 5 | |
35 | 331 | Easily modify a single account’s billing cycle | 5 | |
36 | Accounts meeting the following conditions will be allowed to bill at any time based on a User Action: | |||
37 | 332 | Rebill an Adjusted Bill | 5 | |
38 | 333 | Final Bill | 5 | |
39 | 334 | Billing Due to Late and Early Readings | 5 | |
40 | 335 | Cancel / Rebills for consumption corrections | 5 | |
41 | 336 | Validate consumption based upon user-defined estimating guidelines and algorithms. | 5 | |
42 | 337 | Provide report of customers with greater than "x" number of estimated bills over "x" period of time. (User Defined) | 5 | |
43 | 338 | Calculate consumption based upon set usage averages, based on customer class | 4 | |
44 | 339 | Utilization of rate schedules to calculate charges | 5 | |
45 | 340 | Accommodate billing of accounts on a bi-monthly, monthly and quarterly basis. | 5 | |
46 | 341 | Prorate average consumption on a customer’s account based upon the number of days in the billing period. | 5 | |
47 | 342 | Bill for measured water volume based upon previous and current meter readings. Charges for measured water volume are based on a metered rate multiplied by consumption. | 5 | |
48 | 343 | Bill customers based upon a daily rate for water service charge | 5 | |
49 | 344 | Bill Measured Sewer Volume for commercial customers based on a metered rate multiplied by the current water consumption | 5 | |
50 | 345 | Bill customers based on a daily rate for sewer service charge | 5 |
51 | Billing of Measured Sewer Volume on a multi-family account is one of the following: | |||
---|---|---|---|---|
52 | 346 | Class x Rate x # Dwelling Units | 4 | |
53 | 347 | Volume x Rate | 5 | |
54 | 348 | Winter Average x Rate | 5 | |
55 | 349 | For unmeasured sewer volume accounts, default sewer to a class average | 4 | |
56 | 350 | Accommodates Storm Water Charges based upon size of property (impervious area). This field must be modifiable by user. | 5 | |
57 | Continue to bill on cycle customers who participate in: | |||
58 | 351 | Payment Plans | 5 | |
59 | 352 | Low Income Discount Plans | 5 | Modification: M1 |
60 | Provide the ability to bill various fees and charges by posting Misc. Adjustments by dollar amount. For Example: | |||
61 | 353 | Late payment charges for past due amounts | 5 | |
62 | 354 | Refund of deposit and credit balances on accounts | 5 | |
63 | 355 | Returned check fees | 5 | |
64 | 356 | Initiation/Collection/Reconnect fees | 5 | |
65 | 357 | Service labor amounts for work performed by a service crew | 5 | |
66 | 358 | Meter tampering penalties | 5 | |
67 | 359 | Others, as defined by user | 5 | |
68 | 360 | Accommodate back billing for "x" number of months with an appropriate start and end date. | 2 | Modification: M2 for multi-period billing requirement. |
69 | Accommodate an on-line cancel/rebill (adjustment) process which will allow canceling, adjusting, and rebilling the accounts for "x" previous billing periods for changes in any billing component including rates and usage. Examples include: | |||
70 | 361 | Misread Meter | 5 | |
71 | 362 | Over/Under Estimated Read | 5 | |
72 | 363 | Meter/Equipment/Service Change | 5 | |
73 | 364 | Customer Bankruptcy | 5 | |
74 | 365 | Leakage | 5 | |
75 | 366 | High Bill Investigation | 5 | |
76 | 367 | Major Disaster | 5 | |
77 | 368 | False Registration | 5 | |
78 | 369 | Miscellaneous | 5 | |
79 | 370 | Cancel/Rebill process may be applied to an entire bill, line item, or to a specific service. | 5 | |
80 | 371 | System provides the ability to cancel only those services selected by the user and then rebill the selected service(s) only. The rebill includes all other unchanged items that were on the original bill and in the same format as the original bill. The cancel/rebill only affects the services selected on the account selected | 5 | |
81 | 372 | System reverses original bill entries when cancel is performed | 5 | |
82 | 373 | Maintain past and present usage billed to each rate schedule for a customer account to support the need for reconstructing or rebilling the customer for previous periods. | 5 | |
83 | 374 | Produce and print a corrected bill which reflects adjustments made to previous period consumption for "x" previous periods. | 5 | |
84 | 375 | Provide a corrected current bill which reflects adjustment made to a previous period’s bill. | 5 | |
85 | 376 | Accommodate non-meter related consumption adjustments such as a leak adjustment. | 5 | |
86 | 377 | Usage for multiple metered and non-metered services will display an unlimited number of meters on a single bill. | 5 | |
87 | 378 | Accommodates billing for all services on a single bill. | 5 | |
88 | 379 | Accommodate billing for add and subtract meters | 5 | |
89 | 380 | System will select the appropriate due date without manual intervention. | 5 | |
90 | 381 | Assignment of special handling codes to the bill for purposes of sorting, bill printing, reviewing, routing, and mailing. | 5 | |
91 | 382 | Billing cross-checks are available to ensure that all reads were input, all charges calculated correctly, and all bills printed for the scheduled cycles and off-cycle accounts. A report is produced for exceptions | 4 | |
92 | 383 | Validation of the bill consumption and dollar amount against a user defined range; provide on-line review of the unbilled charges which fail this test with autumatic hold on bill print until review is completed. These charges will remain unbilled until user releases them for print, or adjust and recalculate | 4 | |
93 | 384 | Ability to transfer delinquent balances by fund between a customer's accounts. | 5 | |
94 | 385 | Allow adjustments by fund on transferred balances. | 5 | |
95 | 386 | Debit returned checks back to the customer’s account reversing the amounts by fund originally applied and create appropriate returned check charge. | 4 | |
96 | 387 | Provide for automatic write-off of accounts by fund based upon user defined parameter. Allow for override of this automated process. | 5 | |
97 | 388 | Provide for manual write-off by fund. User has the option to select specific charges. | 2 | Cayenta confirms in base package. |
98 | 389 | Identify and maintain bankruptcy information on the customer account. Upon notification that a customer has filed for bankruptcy have the option to leave active or close the account as of the date of filing. | 5 | |
99 | 390 | Provide for the identification of usage on a vacant account | 5 | |
100 | 391 | Review of payment transaction history for 36 months. | 5 |
101 | 392 | Provides on-line corrections of misapplied and rejected payments | 5 | |
---|---|---|---|---|
102 | 393 | Identify, accept, reconcile and allow transfer of unidentified payments | 5 | |
103 | 394 | Provides on-line transfer of payments by account. The transfer process should reverse the exact fund allocation used to apply the payment and retain transfer date, payment received date | 5 | |
104 | 395 | Ability to reverse any refund or transfer. | 5 | |
105 | 396 | Refund an overpayment on an active account, (the customer made a duplicate payment or mortgage payment, etc.). | 5 | |
106 | 397 | Provide the ability to pay credit balance refunds to the customer. System will provide a report of all customers maintaining a credit balance, by fund. | 2 | Cayenta confirms in base package to alert the user when a customer has a credit balance. |
107 | 398 | Track and provide adequate control over refund checks. Maintain checks and balances when printing refund checks. Provide the ability to control the user authorized to initiate refund checks based on user-defined security parameters | 5 | |
108 | 399 | Allow check generation or provide an interface to another system for check generation, such as an accounts payable system. | 5 | |
109 | 400 | Allow authorized users the ability to void a previously generated refund | 4 | |
110 | 401 | Provide a report of all requested refunds on a daily basis | 5 | |
111 | 402 | Provide the appropriate accounting interface to accurately debit/credit various accounts as refunds are processed, i.e.. issued, reissued, voided, etc. | 5 | |
112 | 403 | Calculate consumption for multiple meter exchanges on an account during a single billing period. Accommodate an install reading and an out reading. | 5 | |
113 | 404 | The dial change service order will automatically change the number of dials on a meter and all relevent meter values | 5 | |
114 | 405 | The meter remove service order will automatically update meter and meter component attribute values | 5 | |
115 | 406 | System allows for a meter to be removed without replacement and continue to bill on-cycle | 5 | |
116 | 407 | The meter reset service order will automatically update the readings on the meter and all relevent meter values | 5 | |
117 | 408 | Provide a credit or a charge to the customers account based upon the results of the customer requested meter test. | 5 | |
118 | 409 | Ability to track the customers historical rate assignments | 5 | |
119 | 410 | Allow multiple rate changes within a billing period with proration reflected on the customer’s bill, if applicable | 5 | |
120 | 411 | Accommodate a rate based on input from another service (e.g sewer based on water service) | 5 | |
121 | 412 | Water Volume algorithms are: Consumption x Rate | 5 | |
122 | 413 | Stormwater rates are: Impervious Area x Days x Rate | 5 | |
123 | 414 | Water Service Charge rate algorithms are: Days x Rate (billed read to read) | 5 | |
124 | 415 | Sewer Service Charge algorithm is: Days x Rate (billed read to read) | 5 | |
125 | 416 | Service Charge on Unmeasured is based on bill to bill date: Days x Rate | 5 | |
126 | Measured Sewer Volume rates may contain the following billing algorithms: | |||
127 | 417 | Monthly Residential: | ||
128 | 418 | Spring, Summer + Fall = avg. winter usage x rate | 5 | |
129 | 419 | Winter = usage x rate | 5 | |
130 | 420 | Default average = class avg x # dwelling units x rate | 4 | |
131 | 421 | Bi-Monthly Residential: Class Avg x rate | 4 | |
132 | 422 | Quarterly Residential: | ||
133 | 423 | Spring, Summer + Fall = avg. winter usage x rate | 5 | |
134 | 424 | Winter = Usage x Rate | 5 | |
135 | 425 | Default average = class avg x rate | 4 | |
136 | 426 | Quarterly Commercial: Usage x Rate | 5 | |
137 | 427 | Monthly Commercial: Usage x Rate | 5 | |
138 | 428 | The system must contain a field that captures the number of dwelling units. This field must be modifiable by user and will be used to calculate multi-family class average | 5 | |
139 | 429 | Allow for manually entered reads. These reads can be for information or for billing | 5 | |
140 | 430 | Directly input a corrected reading and retain both the corrected reading and the original reading. | 5 | |
141 | 431 | Use the actual read date to bill | 5 | |
142 | 432 | Support a minimum of 10 digits for storage and display of the read | 5 | |
143 | Readings will be validated prior to billing. Examples of the type of validations to be performed are: | |||
144 | 433 | Number of Dials on a Read | 5 | |
145 | 434 | Dial Turnover | 5 | |
146 | 435 | Read Units (gallons, CCFs) | 5 | |
147 | The system will provide the following checks (high and low, zero consumption for "x" months) against recorded usage: | |||
148 | 436 | Current Consumption to Last Year's Consumption and allow percentage of variance that is user-defined | 5 | |
149 | 437 | Current Consumption to the Special Parameters Established by Users | 5 | |
150 | 438 | System must prorate over rate change | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | CASHIERING | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 439 | The Cashiering System will interface with the CIS in a way that is transparent to the user | 5 | |
4 | Generation of a receipt automatically after a manual payment is posted. The receipt must include the following: | |||
5 | 440 | Account number | 5 | |
6 | 441 | Customer Name | 5 | |
7 | 442 | Property Address | 4 | |
8 | 443 | Account balance prior to payment | 4 | |
9 | 444 | Payment Amount | 5 | |
10 | 445 | Account balance after payment | 4 | |
11 | 446 | Date and time of payment | 5 | |
12 | 447 | Method of Payment | 5 | |
13 | 448 | Cashier and Workstation ID | 5 | |
14 | 449 | The Cashiering System must provide a separate record/tape of all transactions done each day, per cashier and cashier station. | 5 | |
15 | 450 | A CSR must be able to manually post multiple payments at one time. | 5 | |
16 | 451 | The Cashiering System must provide end of day balance info to include total number of checks received, total cash, total stubs, total transactions and total dollar amount received. | 5 | |
17 | 452 | The Cashiering System operates within a Windows, GUI environment | 5 | |
18 | 453 | The Cashiering System automatically prints the MICR and other required data for bank processing on the check | 2 | Cayenta confirms in base package to print Date, Time, Check Amount, Account Number, Transaction Number, Cashier Number, Location, Source and Station. Portland accepts does not print MICR on check. |
19 | 454 | Separate drawers and reports are maintained for each cashier | 5 | |
20 | 455 | No double entry is required between the CIS and the Cashiering system | 5 | |
21 | 456 | All manual payments are posted to accounts immediately upon receipt and viewable online | 5 | |
22 | 457 | Cashiering system can be utilized at multiple user desktops | 5 | |
23 | 458 | Processing of cash in both on-line and in batch modes. | 5 | |
24 | 459 | Indicate the method of payment on accounts (cash,check). | 5 | |
25 | 460 | Audit trail showing the source of payments, walk-in, mail, etc.. | 5 | |
26 | 461 | Process payments from Pay Stations | 5 | |
27 | 462 | Provides on-line corrections of misapplied and rejected payments | 5 | |
28 | 463 | Identify, accept, reconcile and allow transfer of unidentified payments | 5 | |
29 | 464 | Cash drawer processing and cash reconciliation is provided for each cashier. System will allow a cashier to balance their own drawer at any time during the day. | 5 | |
30 | 465 | A consolidated cash report is provided to interface with G/L. Interface between the modules is electronic or manually entered from the consolidated report. | 5 | |
31 | 466 | Entry of updates/corrections for bank reconciliation information. Upon recognition of an error, a Utility representative can manually make a correction to a single payment or batch. A detailed audit trail of these transactions is provided. | 5 | |
32 | 467 | Apply a single payment over multiple accounts. Customer paying with a single payment, the System must accommodate distributing the payment across multiple accounts by fund. If manual payment, then issue receipt. | 5 | |
33 | 468 | Post payments to accounts which have been written off | 5 | |
34 | 469 | Payments and adjustments can be posted to accounts which are in bad debt | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | PAYMENT EXTENSIONS | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 470 | CIS allows payment extensions for each delinquent customer account based on user defined rules | 5 | |
4 | 471 | CIS calculates the prorations for a payment extension with multi-payments | 5 | |
5 | 472 | The CIS allows for the reversal of a penalty amount which was incorrectly applied to an account | 5 | |
6 | 473 | Bill customers on cycle who participate in payment extensions. | 5 | |
7 | 474 | System allows accounts to be set up on a payment extension for a specified length of time to stop Debt Recovery. Debt Recovery is only stopped for charges associated with the extension. | 5 | |
8 | 475 | Debt Recovery will resume if a customer defaults on a payment extension | 5 | |
9 | 476 | Provide a report that tracks the total number of accounts on payment extensions, including the total deferred revenue | 2 | |
10 | 477 | Track the number of payment extensions not met. For each extension that is made provide the ability to track default. | 2 | |
11 | 478 | Establish and maintain customer payment extensions based upon an installment extension. Total balance owing can be divided into multiple user-defined installments. | 5 | |
12 | 479 | Establish payment extensions on the final bill of an inactive account. | 5 | |
13 | 480 | Track payment extensions on both active, inactive and final billed accounts and begin regular collection efforts upon default of payment extension | 5 | |
14 | 481 | Payment extension dates can be user defined. | 5 | |
15 | 482 | On-line view or report of payment extensions made with a customer for an account. Report can be segmented by class, status of extensions, or amount. | 2 | Cayenta confirms in base package. |
16 | 483 | Payment extension can be made on miscellaneous adjustments, on cycle bills, rebills, or final bills. | 5 | |
17 | 484 | Payments posted on accounts with payment extensions will allocate the same way as accounts that are not on a payment extension. | 5 | |
18 | 485 | There is not a limit to the number of times an account can be set up on a payment extension. | 5 | |
19 | 486 | A Customer Service Rep can terminate a payment extension at any time. | 5 | |
20 | 487 | An account with a credit in one fund and a debit in another fund must not affect the payment extension. | 2 | Cayenta confirms in base package. |
21 | Budget Billing: A monthly payment is determined by the accounts usage history over the previous 12 months. At completion of the budget billing (12 months) the account is reconciled. | |||
22 | ||||
23 | 488 | A CSR can override the monthly payment calculated by the system | 5 | |
24 | 489 | If the customer does not have 12 months of billing history a CSR will determine a monthly payment. | 5 | |
25 | 490 | System generated payment coupons are required for each payment installment. | 5 | Modification: M3 |
26 | 491 | On cycle bills are generated for customers on budget billing. | 5 | |
27 | 492 | Budget billing may be set up on quarterly or bi-monthly accounts. | 5 | Modification: M3 |
28 | 493 | Budget billing may be set up on any type of account. (residential or commercial) | 5 | |
29 | 494 | Budget billing may be set up on a pending or active account. | 5 | |
30 | 495 | Miscellaneous adjustments can be completed while a customer is on budget billing. | 5 | |
31 | 496 | A move in, move-in/move out, or move out can be completed on an account with budget billing. | 5 | |
32 | 497 | Debt recovery will stop while a customer is on budget billing. | 5 | |
33 | 498 | The system will track accounts that are on budget billing and in default. | 5 | |
34 | 499 | Debt recovery will start on an account with budget billing that is in default. | 5 | |
35 | 500 | Payments on budget billing will allocate the same way as accounts that are not on budget billing. | 5 | |
36 | 501 | CSR must be able to terminate budget billing at any time. | 5 | |
37 | 502 | An account with a credit in one fund and a debit in another fund must not affect budget billing. | 5 | |
38 | 503 | On-line view or report of budget billing made with a customer for an account. Report can be segmented by class, status, or amount. | 2 | Cayenta confirms in base package. |
39 | 504 | There is not a limit to the number of times an account can be set up on budget billing. | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | DEBT RECOVERY | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 505 | Collection service orders are distributed based on user defined workflow criteria. | 5 | |
4 | 506 | The CIS allows for transfers of balance to bad debt or bankruptcy write-off | 5 | |
5 | 507 | Payments and adjustments can be posted to accounts which are in bad debt | 5 | |
6 | 508 | The CIS creates an electronic file based on user defined delinquency rules of delinquent accounts to be forwarded to a collection agency | 5 | |
7 | 509 | A sequence of delinquent notices can be identified. The system will support any number of notices with variable contents and format. | 5 | |
8 | 510 | The CIS allows flexibility in defining the date the collection process begins, such as increasing the grace period for a group of accounts or an individual account | 5 | |
9 | 511 | The CIS supports "ready" collection, e.g., account status is reviewed daily to determine delinquency status. If delinquent, CIS automatically begins the collection process | 5 | |
10 | 512 | On-line view of an account's credit history | 5 | |
11 | 513 | System allows accounts to be set up on a payment extension for a specified length of time to stop debt recovery | 5 | |
12 | 514 | System will select the appropriate due date without manual intervention. | 5 | |
13 | 515 | Ability to transfer delinquent balances by fund between a customer's accounts. | 2 | Cayenta confirms in base package. |
14 | 516 | Shutoff processing will include automatic generation of shutoff service orders. | 5 | |
15 | 517 | Ability to select the number of collection service orders to be worked each day | 5 | |
16 | 518 | Shutoff orders will automatically be cancelled if payment is received | 5 | |
17 | Allow for preventing shutoff of service due to delinquency for various reasons including: | |||
18 | 519 | Bankruptcy Proceedings - Pre-petition account | 4 | |
19 | 520 | Fire-line Service (automatic) | 5 | |
20 | 521 | Life Support (automatic) | 5 | |
21 | 522 | High Bill Investigation/Bill Disputes | 5 | |
22 | 523 | Re-Read Order Pending | 4 | |
23 | 524 | Payment Extensions | 5 | |
24 | 525 | Other User Defined Circumstances | 5 | |
25 | 526 | Allows for circumvention of the move in/move out disconnect and non-pay disconnect orders | 5 | |
26 | 527 | Preparation of debt recovery action is based primarily on a total delinquent unpaid dollar amount and aging threshold based on user-defined parameters | 5 | |
27 | 528 | Notices will be mailed directly to customers except for those identified as special handling, including deliver notice to property address | 5 | |
28 | Debt Recovery notices must include the following: | |||
29 | 529 | The mailing address and the property address. | 5 | |
30 | 530 | Account number | 5 | |
31 | 531 | Specify if to be delivered in person to the customers service address. | 5 | |
32 | 532 | Customer Name | 5 | |
33 | 533 | Total past due amount and total account balance | 5 | |
34 | 534 | Date Due | 5 | |
35 | 535 | Collection fee | 5 | |
36 | 536 | On-line identification or reporting of accounts that have been turned off for non-pay | 5 | |
37 | 537 | Allow for a late payment penalty on all types of accounts. | 5 | |
38 | 538 | Upon receipt of a partial late payment, system will automatically indicate the payment amount on the delinquency notice and reduce the balance due. | 5 | |
39 | 539 | Customers with returned checks will automatically be placed into the debt recovery process if the balance is past due. | 5 | |
40 | 540 | Provide identification of previous debt recovery actions taken on the account | 5 | |
41 | 541 | CIS will support user-defined debt recovery action on delinquent final billed accounts | 5 | |
42 | 542 | Provide for automatic write-off of accounts by fund based upon user defined parameter. Allow for override of this automated process. | 5 | |
43 | 543 | Provide for manual write-off by fund capability. User has the option to select specific charges | 2 | Cayenta confirms in base package. |
44 | 544 | Provide a mechanism for easily tracking and identifying final billed accounts with outstanding balances due. | 5 | |
45 | 545 | Report of customers who have made payments and are currently being collected through an outside agency. | 5 | |
46 | 546 | Report of accounts with balances past-due (aging of AR balances) for a predetermined number of days. The report would indicate accounts which are ready to be written-off. | 5 | |
47 | 547 | Automatically generate user-defined collection notices on final billed accounts with user-defined minimum balances after "x" number of days. | 5 | |
48 | 548 | Provide for the write off of balances from AR when debt recovery action/collection agency has been completed. Appropriate G/L interface transactions will occur. | 2 | Cayenta confirms in base package. |
49 | 549 | System provides a means for automatically archiving and purging bad debt history information. | 5 | |
50 | 550 | Identify and maintain bankruptcy information on the customer account. Upon notification that a customer has filed for bankruptcy have the option to leave active or close the account as of the date of filing. | 5 |
51 | 551 | The delinquency process for a bankruptcy customer is stopped for the amount due at the time of filing to prevent the service from being disconnected for non-payment or going to a collection agency for the closed account. | 5 | |
---|---|---|---|---|
52 | 552 | Report of the amount owed and bankruptcy status by customers by fund who have filed for bankruptcy. | 4 | |
53 | An on-line order initiation process for collection related orders. Include the following: | |||
54 | ||||
55 | 553 | Notification (door hanger) prior to non-pay disconnect | 5 | |
56 | 554 | Non-Pay Shut Off | 5 | |
57 | 555 | Other Collections as defined by user | 5 | |
58 | 556 | Non-Pay Re-connection | 5 | |
59 | 557 | Verify the customer's collection class before allowing non-pay disconnect | 2 | Cayenta confirms in base package. |
60 | 558 | Automated report based on user-defined aging of final billed account for assignment to collection agency | 2 | |
61 | 559 | Provide a report of accounts assigned to collection agencies, with additional user-defined criteria | 5 | |
62 | 560 | Once an account has been turned over to an agency, the Utility can manually override an individual account or a mass of accounts. | 5 | |
63 | The CIS manages collection agency activity (respond for each): | |||
64 | 561 | Assign account to a collection agency automatically | 5 | |
65 | 562 | Send/Receive account, payments, updates electronically | 5 | |
66 | 563 | Reverse assignment to collection agency | 5 | |
67 | 564 | Debt recovery can be started from a miscellaneous adjustment, on-cycle bill, rebill or final bill. | 5 | |
68 | 565 | The CIS applies late fees to customer accounts according to delinquency status. Late fees can be overridden by the CSR on an individual account or for a group of accounts | 5 | |
69 | 566 | A CSR can manually replan a completed debt recovery action. | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | SERVICE ORDERS | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 567 | Service orders are created and routed appropriately via user defined criteria | 5 | |
4 | 568 | CIS provides a selection window of types of user defined service orders, e.g. verify read, why high, check for leak, etc. | 5 | |
5 | 569 | CIS has the ability to print service orders at remote locations | 5 | |
6 | 570 | Service orders are sorted by user defined criteria, e.g. location | 5 | |
7 | Service order history is displayed on-line and available in report fomat via the follwing parameters (respond for each): | |||
8 | 571 | Service Order Number | 2 | Cayenta confirms in base package. |
9 | 572 | Property | 2 | |
10 | 573 | Customer | 2 | |
11 | 574 | Create/Due/Complete dates | 2 | |
12 | 575 | Type of service order | 2 | |
13 | 576 | Crew assigned | 2 | |
14 | 577 | CIS service order functionality supports flexibility in scheduling final meter reads, service shut offs, etc. | 5 | |
15 | 578 | Service Orders provide "site" data for the field technician such as meter location, type of meter at site, hazards at site. | 5 | |
16 | 579 | The fields that print on the service order will be user defined. | 5 | |
17 | All service orders created for an address should be displayed as follows: | |||
18 | 580 | Date of Creation | 4 | |
19 | 581 | Status of all service orders | 4 | |
20 | 582 | Total number of pending service orders (by type) | 4 | |
21 | 583 | Type of service order | 4 | |
22 | 584 | Date Completed | 4 | |
23 | 585 | On-line access to historical service orders for an account. | 5 | |
24 | 586 | On-line access to pending service orders for an account. | 5 | |
25 | 587 | Meter shutoff processing will include automatic generation of shutoff service orders. | 5 | |
26 | 588 | Ability to select the number of debt recovery service orders to be worked each day | 5 | |
27 | 589 | Allows for user circumvention of the move out/move in and non-pay disconnect orders. | 5 | |
28 | 590 | Shutoff orders will automatically be cancelled if payment is received | 5 | |
29 | CIS automatically performs the service order's specific tasks at completion. For example: | |||
30 | ||||
31 | 591 | The meter install service order will automatically update meter and meter component attribute values (install read, install date, etc.) | 5 | |
32 | 592 | The meter exchange service order will automatically update meter and meter component attribute values (ie, exchange read, exchange date, etc.) | 5 | |
33 | 593 | The dial change service order will automatically change the number of dials on a meter and all relevent meter values | 5 | |
34 | 594 | The meter remove service order will automatically update meter and meter component attribute values | 5 | |
35 | 595 | System allows for a meter to be removed without replacement and continues to bill the account on-cycle. | 5 | |
36 | 596 | Generate a maintenance service order based on last meter test date, scheduled maintenance date, or meter install date. | 5 | |
37 | 597 | Enable meter tests to be initiated by a customer request. Users can generate a service order. | 5 | |
38 | The CIS must allow for the following Service Orders and field action when a user initiates a change in billing responsibility at a property. (This includes any of the following scenarios: a Move In only, Move In/Move Out (force out), or Move Out only.) | |||
39 | ||||
40 | 598 | Move Out - Shutoff (Read and Disconnect required) | 5 | |
41 | 599 | Move-In/Move-Out (Read Only Required) | 5 | |
42 | 600 | Install (Set) Meter and Turn-on | 5 | |
43 | 601 | Remove Meter | 5 | |
44 | 602 | Site inspection order | 5 | |
45 | 603 | Read and Leave On (special reads) | 5 | |
46 | 604 | Upload data from Schlumberger meter read device and generate a service order. | 5 | |
47 | An on-line initiation process for service order investigations. Include the following: | |||
48 | ||||
49 | 605 | Reread Meter | 5 | |
50 | 606 | Illegal Usage Investigation | 5 |
51 | 607 | Other Investigation | 5 | |
---|---|---|---|---|
52 | 608 | High/low Bill Investigation | 5 | |
53 | An on-line service order initiation process to set, remove or exchange a meter. Include the following: | |||
54 | 609 | Install Meter | 5 | |
55 | 610 | Exchange Meter | 5 | |
56 | 611 | Exchange Meter for Meter of Different Size | 5 | |
57 | 612 | Dial Exchange | 5 | |
58 | 613 | Remove Meter & Other Meter Orders as defined by user | 5 | |
59 | An on-line order initiation process for collection related orders. Include the following: | |||
60 | ||||
61 | 614 | Non-Pay Shutoff | 5 | |
62 | 615 | Other Collections as defined by user | 5 | |
63 | 616 | Non-Pay Re-connection | 5 | |
64 | 617 | Accommodate work initiated and/or completed in the field | 5 | |
65 | 618 | Accommodate the initiation and completion of emergency work with minimal information, or allow for information to be entered into the system after the fact. | 5 | |
66 | 619 | Minimal screens are required to initiate the service order. | 5 | |
67 | 620 | CIS verifies the customers collection class before allowing non-pay disconnect. | 5 | |
68 | 621 | The initiation of move in service orders will force out the previous customer and generate their final bill. | 5 | |
69 | 622 | A move in / move out service order made in error can easily be reversed on-line and all action originally generated by that service order is automatically reversed. | 5 | |
70 | 623 | Unique identification of the service order by a system generated service order number. | 5 | |
71 | The CIS allows on-line inquiry and browsing of service orders. Access will include: | |||
72 | ||||
73 | 624 | Customer Account Number | 5 | |
74 | 625 | Street Address | 5 | |
75 | 626 | Property Number | 5 | |
76 | 627 | Service Order Number | 5 | |
77 | The CIS provides order statusing. Status types can include: | |||
78 | 628 | Preliminary (Data entry, not scheduled) | 5 | |
79 | 629 | Working (Created, issued to the field) | 5 | |
80 | 630 | Completed (Field Work done, service order closed | 5 | |
81 | 631 | Cancelled (Service order no longer needed - action cancelled) | 5 | |
82 | 632 | Open (Created, but not issued to the field) | 5 | |
83 | 633 | CIS allows for on-line access, viewing and modification of preliminary, open or working service orders | 5 | |
84 | 634 | Anytime a move in/move out is scheduled within "x" period of time to coincide with the meter reading window, the on cycle read will be used to complete the service order. | 5 | |
85 | 635 | On-line ability to cancel preliminary, open and working service orders. The system will retain the canceled order with the reason it was canceled, who canceled it and the date it was canceled | 5 | |
86 | 636 | Cancellation of service order will automatically cancel all related actions and activity | 5 | |
87 | 637 | Collection service orders will be automatically cancelled if payments and/or payment extensions are made. | 5 | |
88 | 638 | Provide flexibility in defining the information to be printed on the order. | 5 | |
89 | 639 | Customization of the service order format is user defined. | 5 | |
90 | 640 | Provide the ability to work/complete service orders regardless of where the customer/property is in the billing cycle. | 5 | |
91 | 641 | Provide the ability to create and complete service orders in one step. | 5 | |
92 | 642 | Allow for input of the actual date the service order is worked/completed including weekend and holidays. | 5 | |
93 | 643 | Service Order information is captured at the time the order is completed and retained with the property, the customer, and/or the account. | 5 | |
94 | 644 | Completion of the order will change the status of the service order and identify it as a completed historical order (on-line) | 5 | |
95 | 645 | A move in / move out service order that has not completed, can easily be modified on-line, therefor modifying all action originally generated by that service order. | 5 | |
96 | 646 | Move In and Move Out processes should be automated via Service Orders that obtain field reads and/or shut off and turn on meters. | 5 | |
97 | 647 | More than one Move In or Move Out service order can be in an open and/or working condition at the same time. | 5 | |
98 | 648 | Move In Service Orders must be created in sequential order according to the start date/force out date of each customer. The CIS must only allow these Service Orders to be completed in order of creation. | 2 | Modification: M6 |
A | B | C | D | |
---|---|---|---|---|
1 | RATES | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 649 | CIS allows changes to rate components or calculation without modification to system programs | 5 | |
4 | 650 | CIS contains a flexible rate structure that supports an unlimited number of rates based on factors such as flat fees, multiple component formulas, one time services, and other factors determined by the user | 5 | |
5 | 651 | CIS allows billing of new rates to be tested without affecting current or historical accounts | 5 | |
6 | 652 | Multiple rate changes will be tracked and accommodated when rebilling a service. | 5 | |
7 | 653 | Utilization of rate schedules to calculate charges | 5 | |
8 | 654 | On-line creation of new rate structures. Programming is not required. | 5 | |
9 | 655 | On-line identification and copying of current/historical rate structures to new rate structures. | 5 | |
10 | 656 | Ability to modify a rate and track changes for purposes of historical modeling and billing. | 5 | |
11 | 657 | Ability to track the customers historical rate assignments. | 5 | |
12 | 658 | On-line entry and maintenance of table driven rates and fees. | 5 | |
13 | 659 | Allow multiple rate changes within a billing period with proration reflected on the customer’s bill, if applicable | 5 | |
14 | 660 | Accommodate a rate based on input from another service (e.g sewer based on water service) | 5 | |
15 | 661 | Compare minimum usage to actual usage, if actual is more than minimum system will bill actual usage) | 5 | |
16 | 662 | Water Volume algorithms are: Consumption x Rate | 5 | |
17 | 663 | Stormwater rates are: Impervious Area x Days x Rate | 5 | |
18 | 664 | Water Service Charge rate algorithms are: Days x Rate (billed read to read) | 5 | |
19 | 665 | Sewer Service Charge algorithm is: Days x Rate (billed read to read) | 5 | |
20 | 666 | Service Charge on Unmeasured is based on bill to bill date: Days x Rate | 5 | |
21 | Measured Sewer Volume rates may contain the following billing algorithms: | |||
22 | Monthly Residential: | |||
23 | 667 | Spring, Summer + Fall = avg. winter usage x rate | 5 | |
24 | 668 | Winter = usage x rate | 5 | |
25 | 669 | Default average = class avg x # dwelling units x rate | 4 | |
26 | 670 | Bi-Monthly Residential: Class. Avg x rate | 4 | |
27 | Quarterly Residential: | |||
28 | 671 | Spring, Summer + Fall = avg. winter usage x rate | 5 | |
29 | 672 | Winter = Usage x Rate | 5 | |
30 | 673 | Default average = class avg x rate | 4 | |
31 | 674 | Quarterly Commercial: Usage x Rate | 5 | |
32 | 675 | Monthly Commercial: Usage x Rate | 5 | |
33 | 676 | Quarterly / Monthly Commercial: Negative (sub meter) usage x Rate | 5 | |
34 | 677 | Individual rate schedules must contain a 17-digit code related to the City's accounting requirements | 5 | |
35 | 678 | Provide for the creation of user-defined miscellaneous charges. | 5 | |
36 | 679 | Accommodate pending rate changes without affecting the customer account | 5 | |
37 | System disinguishes rate versions in the following statuses: | |||
38 | 680 | Released (In Use) | 4 | |
39 | 681 | Pending | 4 | |
40 | 682 | Historical | 4 | |
41 | 683 | In Error | 4 | |
42 | 684 | In Test | 4 | |
43 | 685 | Ability to view timeframe when rate was active, including start and end dates for the rate version | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | BATCH PAYMENT PROCESSING | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 686 | Must be able to post batch (bulk mail) payments received via UNISYS Remittance Processor file | 5 | |
4 | 687 | Must identify payments as being posted via remittance processor | 5 | |
5 | 688 | Batch payments must be check digited and displayed on the billing stub (1 at the end of the account number and 1 at the end of the combined account number and amount.) Both check digits must pass successfully in the remittance processor in order to be included in the batch file for posting. | 2 | Portland will configure UNISYS to meet this requirement. |
6 | 689 | When payment batch file is completed and formatted in the UNISYS, the file is FTP'd across the Intranet to the host | 5 | |
7 | 690 | Batch payments are verified as posted or placed in suspension. | 5 | |
8 | 691 | Payments accounts can be viewed on-line immediately after batch processing is completed | 5 | |
9 | 692 | Consolidated cash report is provided for interface with General Ledger. The interface between the modules is electronic or manually entered from the report. | 5 | |
10 | 693 | Must accommodate distributing a single payment across multiple accounts by fund. | 5 | |
11 | 694 | Must be able to search the suspense (unidentified payment) account for a payment amount and transfer payment to customer's account | 5 | |
12 | 695 | Must provide for audit trail showing the source of payments. | 5 | |
13 | 696 | Must be able to process payments received from other sources like pay stations | 5 | |
14 | 697 | Must be able to post payments to accounts which have been written off | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | BILL PRINT & PROCESSING | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 698 | Displays consumption detail per meter on one bill for customers who have multiple meters at their location | 5 | |
4 | Line Items are printed on the customer bill such as: | |||
5 | 699 | Previous balance | 5 | |
6 | 700 | Payment date(s) | 5 | |
7 | 701 | Payment(s) - Individually Listed | 5 | |
8 | 702 | Adjustments | 5 | |
9 | 702 | Refunds | 5 | |
10 | 703 | Due Date | 5 | |
11 | 704 | Account number | 5 | |
12 | 705 | Meter number | 5 | |
13 | 706 | Meter reading | 5 | |
14 | 707 | Actual meter read date | 5 | |
15 | 708 | Rate Applied | 5 | |
16 | 709 | Usage per meter | 5 | |
17 | 710 | Past Due amount | 5 | |
18 | 711 | Collection charges | 5 | |
19 | 712 | Service period | 5 | |
20 | 713 | Postal standard bar code | 5 | |
21 | 714 | CIS can print a corrected bill after adjustments have been made to it, online or batch, e.g. payment, new due date | 5 | |
22 | 715 | On-line access to the exact image of the bill for the past 36 months. | 5 | |
23 | 716 | Provide a corrected current bill which reflects adjustment made to a previous period’s bill. | 5 | |
24 | 717 | Flexibility in combining line item charges or separating item charges for bill printing. | 5 | |
25 | 718 | Flag charges to not appear on the bill. Adjustments or charges made in error that the Utility does not want the customer to view. | 2 | Cayenta confirms in base package. |
26 | 719 | Bill is printed with a user defined identifier of the type of bill, e.g., corrected final bill, regular on-cycle, delinquent and estimated | 5 | |
27 | 720 | Display the date and meter readings at the beginning and at the end of the period for which the bill is rendered. | 5 | |
28 | 721 | Display the beginning and ending dates for the service. Non-metered services that are not consumption based. | 5 | |
29 | 722 | Display the number and kind of units metered (e.g., gallons, cubic feet, MCF's) | 5 | |
30 | 723 | Display the total amount due in an easy definable place on the bill. | 5 | |
31 | 724 | Display the total amount due plus amount of penalty if not paid by due date. The penalty amount can be viewed as a separate line item. | 5 | |
32 | 725 | System will select the appropriate due date without manual intervention. | 5 | |
33 | 726 | Ability to add headers and footers | 5 | |
34 | 727 | Provides for two check digits to be included on the bill | 5 | |
35 | 728 | Allow global custom messages. All bills produced will have a single message | 5 | |
36 | 729 | Indicate the Low Income Discount as a separate line item | 5 | |
37 | 730 | Assignment of special handling codes to the bill for purposes of sorting, bill printing, reviewing, routing, and mailing. | 5 | |
38 | 731 | Provide bar coding of postal information | 5 | |
39 | 732 | Provide CASS certification of the mailing address for postal discount. | 5 | |
40 | 733 | System will provide multiple capabilities for sorting bills. (e.g. Zip code, cycle, customer number) | 5 | |
41 | 734 | System provides sorted output in accordance with U.S. Postal Service standards. For example: sort bills based on zip plus four plus two. | 5 | |
42 | 735 | Input a range of bills to be produced. For example, the entire bill run does not need to be printed all at one time. | 5 | |
43 | 736 | Produce a single bill for all charges. | 5 | |
44 | 737 | System will display the number of bills to be printed at the beginning of the print program | 2 | Cayenta confirms in base package via Dashboard. |
45 | 738 | System will display the number of bills remaining to be printed. | 2 | |
46 | 739 | System will display the number of total bills printed at the end of the print job | 2 | |
47 | 740 | System allows restarting of a bill run from any point within the bill run. | 5 | |
48 | 741 | System allows a bill run to be paused and restarted. | 2 | |
49 | 742 | Accommodate different formats for different types of bills. | 5 | |
50 | 743 | Re-print a duplicate copy of the current bill in an on-line or batch mode | 5 |
51 | 744 | Re-print a duplicate copy of the bill for any previous billing period. | 5 | |
---|---|---|---|---|
52 | 745 | Billing cross-checks are available to ensure that all reads were input, all charges calculated correctly, and all bills printed for the scheduled cycles and off-cycle accounts. A report is produced for exceptions | 4 | |
53 | 746 | Validation of the bill consumption and dollar amount against a user defined range; provide on-line review of the unbilled charges which fail this test with autumatic hold on bill print until review is completed. These charges will remain unbilled until user releases them for print, or adjust and recalculate | 4 | |
54 | 747 | System provides a data stream in the form of a flat file to any bill print program for the purposes of printing a bill. The file should include data which is defined by the user. | 5 | |
55 | 748 | Bill print format should be user defined. | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | REPORTS | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 749 | Support user requests to identify and list accounts by account classification or category, for example by: S.I.C. code, Postal Code Area, Critical Care Customers, Government, Wholesale, etc. | 4 | |
4 | 750 | Billing cross-checks are available to ensure that all reads were input, all charges calculated correctly, and all bills printed for the scheduled cycles and off-cycle accounts. A report is produced for exceptions | 5 | |
5 | 751 | The system produces a preliminary billing register listing accounts that failed validation of the bill consumption or dollar amounts against a user defined range. This includes to be billed amounts including line item detail and the total amount of unbilled charges | 4 | |
6 | 752 | Produce a report for revenue by rate, customer classification and service type by fund | 4 | |
7 | 753 | Produce a report showing number of bills generated from meters read. | 4 | |
8 | 754 | Produce a report showing the number of estimated accounts and the bill amount. | 4 | |
9 | 755 | Provide a report of Customer Accounts without Readings Over "x" Days | 4 | |
10 | 756 | Provide a report of Customer Closed Accounts with Credit Balances | 4 | |
11 | Various post-billing reports including: | |||
12 | 757 | Cash Receipts Journal | 5 | |
13 | 758 | Statistical Reports to include consumption by rate class. | 4 | |
14 | 759 | Bill Register to verify any differences between pre and post billing. | 5 | |
15 | 760 | Customer Accounts not Billed Over "x" Days | 4 | |
16 | 761 | Inactive meters registering consumption. | 4 | |
17 | 762 | Revenue reporting: per cycle, month ended report, per service, etc. by fund | 4 | |
18 | 763 | Identification and user-defined reporting of non-pay disconnect customers for subsequent follow-up. | 4 | |
19 | 764 | On-line identification or reporting of accounts that have been turned off for non-pay. | 4 | |
20 | 765 | Report based on user-defined aging of final billed account for assignment to collection agency | 5 | |
21 | 766 | Provide a report of accounts assigned to collection agencies, with additional user-defined criteria | 5 | |
22 | 767 | Provide a report that shows accounts which have received payment after they were assigned to a collection agency | 5 | |
23 | 768 | View employee payment and debt recovery status. (user defined) | 4 | |
24 | 769 | Provide a report that tracks the total number of accounts on payment extensions including the total deferred revenue by fund | 4 | |
25 | 770 | Produce a report that tracks the number of returned checks | 5 | |
26 | 771 | Track the number of payment extensions not met. For each extension that is made provide the ability to track default. | 5 | |
27 | 772 | On-line view or report of payment extensions made with a customer for an account. Report can be segmented by class, status of arrangement, or amount. | 4 | |
28 | 773 | Report of customers who have made payments and are currently being collected through an outside agency. | 5 | |
29 | 774 | Report of payments collected by receivable type for a specified period of time | 5 | |
30 | 775 | Report of accounts with balances past-due by fund (aging of AR balances) for a predetermined number of days. The report would indicate accounts which are ready to be written-off. | 5 | |
31 | 776 | Report of the amount owed by customers by fund who have filed bankruptcy | 4 | |
32 | 777 | Identification and reporting of payments by user-defined criteria | 4 | |
33 | 778 | Identification and reporting of payments by batch. | 5 | |
34 | 779 | Report of the accounts receivable transactions by type by customer. Report can be segmented by customer class, or by receivable and fund such as Water and Sewer | 4 | |
35 | 780 | On-line view and report of the aging of accounts receivable for all accounts by receivable type by customer and fund. Aging segments are flexible and may be 30, 60, 90, 120 days. | 5 | |
36 | 781 | On-line view and report of the aging of Receivables by fund for accounts by customer segment (customer class, billing frequency, etc.). | 4 | |
37 | 782 | On-line view and report of the total Receivables by customer segment (Class, SIC, etc.). | 4 | |
38 | 783 | On-line view and report of the aging of Receivables for accounts by dollar amount. | 4 | |
39 | 784 | System will provide a report of all customers maintaining a credit balance, by fund. | 4 | |
40 | 785 | Validate the amount of the refund given to each customer against a predetermined parameter. System will check for any "large" refund payments and provide a report. | 4 | |
41 | 786 | Will provide a report of all requested refunds | 5 | |
42 | 787 | Provide for general rate reporting for example allow reporting of consumption used and dollars received | 4 | |
43 | 788 | Provide a report of all new services which do not have a route assigned. | 4 | |
44 | 789 | Reports contain multiple select and sort parameters to support various standard utility reporting requirements. | 4 | |
45 | 790 | Standard and utility specific reports can be scheduled to print daily and nightly using standard system functionality. | 5 | |
46 | 791 | System reports can be generated and viewed on-screen before printing. | 5 | |
47 | 792 | System provides integration to a data warehouse | 2 | |
48 | 793 | Provide the ability to create and define an unlimited number of user defined reports utilizing query, third party report writing tools (e.g. Crystal Reports). | 5 | |
49 | 794 | System flexibility should allow selection of information for reports by customer class, billing frequency, type of charge, fund (water, sewer), and other customer variables. | 5 | |
50 | 795 | Detail and summary for financial transactions related to all customer billing by fund, by day or other selected time frame. | 4 |
51 | 796 | Detail and summary for financial transactions related to all customer payments (cash, money order, check, etc.) by fund, by day or other selected time frame. | 5 | |
---|---|---|---|---|
52 | 797 | Detail and summary for financial transactions related to all customer payments by fund, by payment type (walk-in, mail, pay station, EFT, non-cash/voucher, etc.). | 5 | |
53 | 798 | Detail and summary for financial transactions related to all customer payments by fund, by batch. | 5 | |
54 | 799 | Detail and summary for financial transactions related to all adjustments (including discounts) by fund on customer accounts by day or other selected time frame. | 4 | |
55 | 800 | Detail and summary for financial transactions related to all refunds on customer accounts by fund, by day or other selected time frame. | 4 | |
56 | 801 | Report of returned checks. Report would include: Customer name, mailing address, service address, amount, date of original payment, date check was returned, charge applied for returned check, and other user-defined information | 4 | |
57 | 802 | Detail and summary listing of accounts that did not bill during their normal billing cycle. | 4 | |
58 | 803 | List of the accounts receivable balance for the water fund, for the sewer fund, and in total for each account, regardless of whether account is active or inactive. | 4 | |
59 | 804 | List of the "age" of the balance on all accounts (an accounts receivable aging) by fund and in total. | 4 | |
60 | 805 | Detail and summary of current and past-due charges on individual accounts by fund and in total. | 3 | |
61 | 806 | Detail and summary for write-offs due to non-collectibility on customer accounts by fund and in total. | 5 | |
62 | 807 | Listing of accounts by customer class-commercial, multi-family, residential -- type-water/sewer, water only, sewer only, government, other -- billing frequency-monthly, bi-monthly, quarterly, annual, other -- and status-active, inactive, other. | 4 | |
63 | 808 | Listing of accounts that have each individual rate attached to them - water volume, sewer volume, water service charge, BOD, etc. | 4 | |
64 | 809 | Listing of accounts that have filed by bankruptcy. Include the amount of the account balance by fund at the time of the filing. | 4 | |
65 | 810 | Audit trail for individual accounts on an as needed basis. Report can be selected by date for individual account(s), employee ID, and other user-defined criteria. Trail will include all transactions related to the account that had the potential to impact the customer's bill or debt recovery activity. Information in the audit trail includes: user ID, date/time of transaction, type of transaction, result of transaction (adjustment of $XXX.xx made, meter read changed, etc.). | 2 | |
66 | 811 | Any of the financial reports named here should be available for accounts by debt recovery status, especially those who are active in a debt recovery collection cycle (reminder notice, urgent notice, etc.) | 2 | |
67 | 812 | Printed duplicate of any bill sent to customers. | 5 | |
68 | 813 | Billing error/edit report | 5 | |
69 | 814 | Report of customers on a payment plan including the "age" of their debt, the payments they have made, and the timeliness of those payments. | 2 | |
70 | 815 | Consumption of water billed by period (week, month, 4-week periods, other). | 2 | |
71 | 816 | Report automatically printed when the billing system is out of balance including details related to the out-of-balance condition. | 4 | |
72 | 817 | List of customers who are receiving a low income discount or who have received a crisis voucher or other type of non-cash payment. | 2 | |
73 | 818 | Daily list of accounts which received a refund with refund amount by fund and in total. | 4 | |
74 | 819 | Daily list of returned checks by total for the account and by fund. | 4 | |
75 | 820 | Detailed and summary report of accounts assigned to a collection agency. Report should include customer name, date of assignment, account balance at assignment, current account balance, payments during the current month, payments to date through the collection agency. | 4 | |
76 | 821 | Provide report of water customers not billing sewer and/or not billing stormwate and sewer customers not billing stormwater | 4 |
A | B | C | D | |
---|---|---|---|---|
1 | ADMINISTRATION | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 822 | Validate the amount of the refund given to each customer against a predetermined parameter. System will check for any "large" refund payments and provide a report. | 2 | |
4 | 823 | System provides user and user classified specified parameters for posting adjustments. | 5 | |
5 | 824 | Payments are allocated by fund to the customer account(s) in a user defined hierarchy, which is parameter driven and easy to modify. All payments/accounts are allocated identically by fund | 5 | |
6 | 825 | Track and provide adequate control over refund checks. System maintains checks and balances when printing refund checks. Provides the ability to control the user authorized to initiate refund checks based on user-defined security parameters | 2 | |
7 | 826 | System has an easy to use and easy to maintain billing and debt recovery calendar allowing adjustment for holidays, weekends | 5 | |
8 | 827 | Allow users to maintain key system parameters on-line without the need for IS intervention to change the values. This includes items such as: rate tables, edit parameters, security access, etc. An audit log (containing at least user ID, date/time of the change, items changed) is maintained. | 5 | |
9 | 828 | System security is capable of preventing unauthorized users from logging into the database. | 5 | |
10 | 829 | System constrains authorized users to the data they are approved to access. | 5 | |
11 | 830 | Specify user access and security by screen and type of action such as update versus inquiry. | 5 | |
12 | 831 | Provide for security down to the data field | 5 | |
13 | 832 | The ability to track the use of the system by authorized users. | 5 | |
14 | 833 | The ability to report attempts by unauthorized users to use the system. | 5 | |
15 | 834 | The ability to suspend after "x" attempts to access the system with an incorrect password. | 5 | |
16 | 835 | Provides adequate levels of management review and approval throughout the system | 5 | |
17 | 836 | The product provides security at the system, business function, and screen level. Restriction is by user, or defined user group | 5 | |
18 | System should provide process for the user to define, create and/or maintain: | |||
19 | ||||
20 | 837 | Financial transaction types | 5 | |
21 | 838 | Service Orders | 5 | |
22 | 839 | Miscellaneous Adjustments | 5 | |
23 | 840 | Debt Recovery process | 5 | |
24 | 841 | Payment allocation | 5 | |
25 | 842 | Other, as defined by system | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | INTERFACES | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 843 | Be able to download and upload all necessary meter reading information received from Schlumberger handheld meter reading software | 5 | |
4 | 844 | Be able to selectively download and upload meter reading information to the Schlumberger handheld software based upon type e.g. water meter or sewer meter and other Schlumberger software required or user defined parameters | 5 | |
5 | 845 | Include the download and upload of meter information for inactive (vacant) accounts | 5 | |
6 | 846 | Provide for the download and upload of sewer meter information and readings | 5 | |
7 | 847 | Be able to upload and update information from the Schlumberger software, including meter location, meter reads, resequencing, meter reader comments and trouble codes | 5 | |
8 | 848 | Provide controls to safeguard the upload and processing of the same readings more than once (duplicate reads). | 5 | |
9 | 849 | Retain all upload reads received regardless of their validity (no user override capability) | 5 | |
10 | 850 | Ability to automatically generate service orders based on trouble codes/information from the meter reader | 5 | |
11 | 851 | Must be able to pass and receive information electronically to and from external general ledger system | 5 | |
12 | 852 | Must be able to receive and upload payments transmitted from UNISYS remittance processor | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | SYSTEM MECHANICS | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 853 | System provides windows-like point and click navigation. | 5 | |
4 | 854 | Provide for user configurable screens / windows | 5 | |
5 | 855 | Provide for standardized screens / windows | 5 | |
6 | 856 | Provide for direct screen/window access from anywhere within the system (drop down, fastpath) | 5 | |
7 | 857 | Ability to have multiple customer sessions without multiple log ons. Application must support multiple user sessions. | 5 | |
8 | 858 | System provides navigation using hot keys instead of the mouse. | 5 | |
9 | 859 | Provide the capability to perform a new search from any window or screen | 5 | |
10 | 860 | Maintains key header information from one screen to the next. Customer name, service address, start date, etc. | 5 | |
11 | 861 | Valid values should be available in a drop down box or popup window. | 5 | |
12 | 862 | Values can be input directly without the use of a drop down box. Can type first few letters and value will display or placed in the drop down list. | 5 | |
13 | 863 | The system uses a "rule-based" architecture allowing a secured user to set up and maintain the software without requiring programmer intervention. | 5 | |
14 | 864 | Allows for the monitoring of system uptime, response time, and batch window in order to keep within acceptable levels. | 5 | |
15 | 865 | Provides for a 4 digit year throughout the system to allow for the year 2000+. | 5 | |
16 | 866 | Support real time on-line update as the primary processing mode. | 5 | |
17 | 867 | Provide ability to selectively archive system data based on user-defined number of years or other user-defined criteria. The archived data can be accessed via another medium such as tape or CD-ROM. Provide secondary process to purge archived data. Please note: Oregon State Law requires a minimum of 3-year retention of these records. | 5 | |
18 | 868 | Accommodates Zip + Four | 5 | |
19 | 869 | Allow users to maintain key system parameters on-line without the need for IS intervention to change the values. This includes items such as: rate tables, edit parameters, security access, etc. An audit log (containing at least user ID, date/time of the change, items changed) is maintained. | 5 | |
20 | 870 | On-line submission of batch jobs to be run in a real time or a batch mode. Ability to utilize a scheduler for automated submission. | 5 | |
21 | 871 | System provides detailed error messages that are user friendly and descriptive | 5 | |
22 | 872 | System must enforce data integrity constraints that prevent the introduction of corrupt data into the system (ie, enter future read dates, etc.) | 5 | |
23 | 873 | Provide transaction logging or journalizing at the data base level in support of a full and quick system recovery | 5 | |
24 | 874 | Ability to recover the system from the transaction log | 5 | |
25 | 875 | The product is operated within a proven, robust, well supported environment | 5 | |
26 | 876 | The product currently utilizes a client/server or web-based environment offering cohesive GUI desktop | 5 | |
27 | 877 | The client interface will link to desktop productivity tools e.g. word processing, spreadsheet and data base. | 5 | |
28 | 878 | The product provides for tools to easily export data to a data warehouse. | 5 | |
29 | 879 | The product provides flexible features, allowing the authorized administrative user to easily configure the base application. | 5 | |
30 | 880 | The application must support TCP/IP. | 5 | |
31 | 881 | The application must provide for data security. | 5 | |
32 | 882 | System will promote a central repository for purposes of data security, control, backup and recovery. The solution will be inherently resistant/immune to software viruses, and will not be vulnerable to denial-of-service (DoS) attacks. | 5 | |
33 | 883 | A modern, highly performant relational data base management system is required. With Oracle preferred. | 5 | |
34 | 884 | The product design and modularity allow it to be ported to smaller and/or larger platforms without the need for excessive redesign work. | 5 | |
35 | 885 |
The solution is scalable. The solution is distributed and fault
tolerant with redundant/failover components to achieve maximum
system availability. |
5 | |
36 | 886 | The solution will position the Utility to easily take advantage of evolving technologies such as imaging, work group computing, video conferencing, etc. | 5 | |
37 | 887 | The product and its life cycle tools provide for a simplified and timely testing and modification environment. | 5 | |
38 | 888 | The Utility is looking for the vendor to support the product and grow the product to maturing platforms. | 5 | |
39 | 889 | The product was developed on the platform proposed by the Vendor and optimizes the proposed platform’s data base(s) and operating system. | 5 | |
40 | 890 | The product database allows access by an SQL-based language. | 5 | |
41 | 891 | The product has been designed around a core package which provides standard functionality and data structure for the primary utility services. The core package provides user defined exits, user defined fields, user defined screens, user defined reports, | 5 | |
42 | 892 | The primary focus of the product is on-line real time entry and update of information. | 5 | |
43 | 893 | On-line response time for inquiry and basic updates is within an acceptable range averaging no more than sub second during peak usage. (5,000 db transactions/second) | 5 | |
44 | 894 | Any nightly batch window executes within an acceptable maximum period of 8 hours. | 5 | |
45 | 895 | The product will be available and support a minimum of 12 hour by 6 day a week business operations. | 5 | |
46 | 896 | The product source code is available for placing into escrow | 5 | |
47 | 897 | The product offers on-line inquiry during the batch processing window. | 5 | |
48 | 898 | The product offers on-line update during the batch processing window. | 5 | |
49 | 899 | The product provides full restart and recovery features for all batch transactions | 5 | |
50 | 900 | The solution provides full recovery features for all on-line transactions. | 5 |
51 | 901 | System backup can be accomplished within a maximum of 8 hours. | 5 | |
---|---|---|---|---|
52 | 902 | The solution provides a comprehensive computing site disaster recovery or approach. | 5 | |
53 | 903 | A product data model is available and has been provided for review of all data entities and relationships. | 5 | |
54 | 904 | The solution provides an integrated batch scheduler. | 5 | |
55 | 905 | Full system restore can be accomplished within 24 hours | 5 | |
56 | 906 | Provide automatic logging of system changes by user for on-line review. | 5 | |
57 | 907 | Each record contains a date/time stamp reflecting last add/change. | 5 | |
58 | 908 | The Utility has permission to freely copy all system and technical documentation, once the contract with the vendor has been signed, for internal use. | 5 | |
59 | 909 | The solution provides a full test set and the ability to conduct distinct testing outside of production environments. | 5 | |
60 | 910 | The solution will work within the Utility's existing network environment, taking full advantage of existing topologies (i.e. optimizes the bandwidth). | 5 | |
61 | 911 | The solution and required hardware will be sized to accommodate the utility's customer base and number of users, plus expected room for growth. | 5 | |
62 | The product provides a full suite of utility jobs required to execute various systems maintenance functions including: | |||
63 | 912 | Version control of source code | 5 | |
64 | 913 | Disk management, Data Mirrors/RAID | 5 | |
65 | 914 | Tape management | 5 | |
66 | 915 | Multiple on-line sessions | 5 | |
67 | 916 | Storage archival and retrieval | 5 | |
68 | 917 | Job scheduling utility | 5 | |
69 | 918 | Performance monitoring (application and system) | 5 | |
70 | 919 | Ability to monitor executing jobs | 5 | |
71 | 920 | Debugging tools | 5 | |
72 | 921 | Transaction monitors | 2 | |
73 | 922 | Programming tools | 5 |
A | B | C | D | |
---|---|---|---|---|
1 | AUDITING | |||
2 | # | Function / Feature | Cayenta's Self Score | Additional Comments / Notes. |
3 | 923 | An audit trail should be provided for all financial transactions and any other transaction or data modification that will impact the customer's bill or debt recovery status. | 5 | |
4 | 924 | Audit trails will be retained for the minimum 3-year records retention period | 5 | |
5 | 925 | Automatically creates a complete detailed audit trail including information such as date, time, and User ID, transaction type and amount, transactions attempted, transactions completed. | 5 | |
6 | 926 | Authorized User can review audit trails on-line or in a report | 5 |