FM_UB_ATT_7_Functional_Requirements_v2.xlsx
XLSX spreadsheet 43 KB Posted
- Solicitation number
- RFP 26-106
- Issued by
- Lee County, Fort Lauderdale City, Florida
About this file
This is a functional requirements document for a Utility Billing System (UBS) for the City of Fort Myers, Florida, detailing 379 comprehensive requirements across multiple operational domains. The document serves as Attachment 7 to a Request for Proposals for professional implementation services and establishes the technical and functional specifications that the selected vendor's Oracle Utilities Billing system must satisfy. The requirements span account management, customer files, meter information and readings, billing processes, collections, payments, deposits, backflow prevention, service requests, work orders, waste collection, reporting, security, and system integration capabilities. The document does not specify response dates, due dates, site visits, bidder's meetings, or award dates; these details are contained in the primary RFP documents. The requirements apply to the City's water, wastewater, and solid waste utility operations and establish the baseline functionality expected of the implemented system.
The functional requirements document does not address pricing terms, set-asides, incumbent information, or funding details. Instead, it provides a detailed specification framework with response options including "Y" (Requirement Met and Proposed as standard features), "Y-ND" (Requirement Met but requiring custom development or non-standard features), "N" (Requirement Not Met), and support designations of "S" (Software Developer supported), "TPS" (Third Party supported), or "NS" (Not Supported). Proposers are required to complete responses in designated columns and provide comments explaining exceptions, assumptions, and any limitations. The document emphasizes integration capabilities with existing systems through APIs and direct connectors, mobile technology support, role-based security, audit trail functionality, and multi-format reporting and dashboarding capabilities as critical system features for the City's utility operations.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Professional_Implementation_Services_for_Oracle_Utilities_Billing_(Addendum_#4_Revision).pdf | ||
| Professional_Implementation_Services_for_Oracle_Utilities_Billing_(Addendum_#1_Revision).pdf | ||
| Fort_Myers_UB_RFP_09_18_26.pdf | ||
| FM_UB_ATT_10_Cost.xlsx | XLSX spreadsheet | |
| FM_UB_ATT_6_Project_Expectations.pdf | ||
| FM_UB_ATT_9_Conversions_v1.xlsx | XLSX spreadsheet | |
| FM_UB_ATT_11_Interface_List.xlsx | XLSX spreadsheet | |
| FM_UB_ATT_12_Reports_v2.xlsx | XLSX spreadsheet | |
| FM_UB_ATT_8_Project_Staffing.xlsx | XLSX spreadsheet | |
| FM_UB_ATT_5_Technology_Deployment.pdf | ||
| FM_UB_ATT_1_Signature_Page.pdf | ||
| FM_UB_ATT_3_Prof_Svcs_Background.pdf | ||
| INSURANCE_REQUIREMENTS_CHART.pdf | ||
| FM_UB_ATT_2_Proposer_Statement.pdf | ||
| FM_UB_ATT_4_Prof_Svcs_Reference_v1.pdf |
Show all 15
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Requirements UTILITY BILLING - City of Fort Myers, FL
| Attachment 7: Functional Requirements | ||||||
| Column E: Available Responses | ||||||
| Y | Requirement Met and Proposed (Standard features in the generally available product) | |||||
| Y-ND | Requirement Met and Proposed (Features that are not offered as a generally available product or require custom development) | |||||
| N | Requirement Not Met with Proposal | |||||
| I | Need More Information/Discussion | |||||
| Column F: Available Responses | ||||||
| S | Requirement and Feature Supported by Software Developer | |||||
| TPS | Requirement and Feature Supported by Third Party | |||||
| NS | Requirement and Feature Not Supported | |||||
| NOTE: | All exceptions and assumptions should be listed in the comments field | |||||
| Req. # | Function | Process | Requirement | Implementation Response | Support Response | Comments |
| 1 | UB | Account Information | System tracks account for each service at each location. There could be multiple services at the same location e.g. solid waste and water or multiples of the same service type at a location or the location may only have a single service (sewer only or water only) | |||
| 2 | UB | Account Information | Accounts support multiple service types: | |||
| 3 | UB | Account Information | Water (with multiple meters - irrigation, potable, sewer, backflow, Remote Shutoff valves (RSV), deductible meters) - different water types have different rates | |||
| 4 | UB | Account Information | Sewer | |||
| 5 | UB | Account Information | Waste Collection (dumpster, rolloff, recycle) | |||
| 6 | UB | Account Information | System has the ability to allow users (with proper security) to create new charge types | |||
| 7 | UB | Account Information | Accounts linked to customer | |||
| 8 | UB | Account Information | System creates parent/child relationship with accounts/customers (landlord/tenant) |
Note: When tenant leaves needs the account to revert back to owner.
| 9 | UB | Account Information | Scan and attach multiple forms of ID |
| 10 | UB | Account Information | System supports automation of online application process, including workflows for review, verification and approval and payment processing for deposit |
| 11 | UB | Account Information | System has the ability to inquire and report on prior accounts with outstanding balance |
| 12 | UB | Account Information | System allows users to query for people that move apartments and leave balances on previous addressess |
| 13 | UB | Account Information | Generate multiple types of bills for a single account |
| 14 | UB | Account Information | System allows a single customer to have multiple accounts and receive a single bill for all their accounts |
| 15 | UB | Account Information | System will support an account that has various combinations of utility services |
| 16 | UB | Account Information | System will check for duplicate accounts before creating new one by: |
| 17 | UB | Account Information | Duplicate service names |
| 18 | UB | Account Information | Owner's account |
| 19 | UB | Account Information | Meter number |
| 20 | UB | Account Information | Meters at address |
| 21 | UB | Account Information | System tracks backflow prevention requirements |
| 22 | UB | Account Information | System tracks backflow devices |
| 23 | UB | Account Information | System sends letters (automated and manual) concerning testing requirements based on prior test dates |
| 24 | UB | Account Information | System accommodates issue tracking |
| 25 | UB | Account Information | System allows users to generate communication to customers via email, text, and phone based on City defined criteria (EX: Campaigns for delinquent shutoffs, high consumption, ad hoc) |
| 26 | UB | Account Information | System flags high-risk accounts (medical facilities, etc.) |
| 27 | UB | Customer File | Customer File contains (at minimum) the following fields: |
| 28 | UB | Customer File | Name |
| 29 | UB | Customer File | Multiple addresses (Including forwarding address and billing address) |
| 30 | UB | Customer File | Property tax id |
| 31 | UB | Customer File | Multiple email addresses |
| 32 | UB | Customer File | Multiple phone numbers |
| 33 | UB | Customer File | Authorized party |
| 34 | UB | Customer File | Valid official ID (EX: Official government ID, drivers license number and state or passport with country, etc.) |
| 35 | UB | Customer File | Billing preference (electronic or hard copy) |
| 36 | UB | Customer File | Owner, tenant, association, contractor, landlord, land trust, property management (or other as defined) |
| 37 | UB | Customer File | Number of people in household |
| 38 | UB | Customer File | System accepts foreign addresses |
| 39 | UB | Customer File | System identifies and tracks residential and commercial accounts (via Business Tax Receipt information and/or Zoning) |
| 40 | UB | Customer File | System can link commercial and residential accounts |
| 41 | UB | Customer File | System tracks customer owning multiple properties |
| 42 | UB | Customer File | System supports transfer of service by customer number where one account is closed and another opened without loss of data on customer history |
| 43 | UB | Customer File | System allows users to view and limit timeframe for transfer of account between addresses. |
| 44 | UB | Customer File | System maintains alternate address for customers |
| 45 | UB | Customer File | System identifies time period to send bill to alternate address |
| 46 | UB | Customer File | System allows user to search for account by (but not limited to) the following: |
| 47 | UB | Customer File | Name |
| 48 | UB | Customer File | Address |
| 49 | UB | Customer File | Phone number |
| 50 | UB | Customer File | |
| 51 | UB | Customer File | Meter number |
| 52 | UB | Customer File | Account and/or Customer Number |
| 53 | UB | Customer File | Radio number |
| 54 | UB | Customer File | Service order number |
| 55 | UB | Customer File | System provides flags or notes on customer records for delinquent payments |
| 56 | UB | Customer File | System validates address accuracy (i.e. USPS) |
| 57 | UB | Customer File | System will support master meters (e.g., one master meter for entire subdivision or building with one invoice/bill) |
| 58 | UB | Customer File | System will support reading multiple meters and combining into one master bill (i.e., City reads multiple meters and creates one single bill) |
| 59 | UB | Customer File | System allows the sale of bulk water that is not tied to a meter |
| 60 | UB | Customer File | System adds a new service type or charge to large segments of customers (mass additions based on criteria) |
| 61 | UB | Meter Information | System tracks meters by ID, including meter ID and radio |
| 62 | UB | Meter Information | System tracks meters by size |
| 63 | UB | Meter Information | System tracks meters by location |
| 64 | UB | Meter Information | System tracks meter by customer type (commercial, residential, etc.) |
| 65 | UB | Meter Information | System tracks utilities consumption (e.g. spikes in usage, leaks, etc.) |
| 66 | UB | Meter Information | System tracks meter inventory and inventory of AMI components |
| 67 | UB | Meter Information | System tracks status of meters and AMI components in inventory (i.e. new, in service, in testing, out of service, ready for use, etc.) |
| 68 | UB | Meter Information | System tracks meter consumption history |
| 69 | UB | Meter Information | System tracks meter change-out history |
| 70 | UB | Meter Information | System tracks meter lifecycle and usage history |
| 71 | UB | Meter Information | System flags meters based on user defined criteria (i.e. over 12 years old) |
| 72 | UB | Meter Information | System flags meters over a certain consumption |
| 73 | UB | Meter Information | System flags meters with consumption under a certain level |
| 74 | UB | Meter Information | System supports the use of bar codes for meter inventory and work order processing |
| 75 | UB | Meter Information | System has the ability to review accounts with an edit report and generate readings out of parameters for reread |
| 76 | UB | Meter Information | System has the ability to make adjustments based on rereads |
| 77 | UB | Meter Information | System has the ability to support change out of meters and update billing based on new meter for all charges |
| 78 | UB | Meter Information | Can drilldown to meter location on customer record |
| 79 | UB | Meter Information | Provide comments for meter reader |
| 80 | UB | Meter Information | System identifies meters with Remote Shutoff Valves (RSVs) |
| 81 | UB | Meter Information | System receives alarm codes from Itron and flags for investigation |
| 82 | UB | Meter Information | System allows adding new assets into inventory through a batch job (e.g., 100's to 1000's at a time) |
| 83 | UB | Meter Readings | System can support handheld devices that allow users to upload meter reads in the field to a mobile device, then download reads when Wi-Fi is available |
| 84 | UB | Meter Readings | System can export meter reading information by Cycle and Route |
| 85 | UB | Meter Readings | System can import reads by Cycle and Route |
| 86 | UB | Meter Readings | System can report on readings and consumption based on cycle, meter type or consumption |
| 87 | UB | Meter Readings | System tracks meter reading history by location |
| 88 | UB | Meter Readings | System tracks meter reading history by customer |
| 89 | UB | Meter Readings | System can identify reads for inactive meters for unauthorized usage |
| 90 | UB | Meter Readings | System can generate a work order automatically for zero reads for a user-defined time frame |
| 91 | UB | Meter Readings | System will allow users with security permissions to update or edit data within the system if there are errors. |
| 92 | UB | Meter Readings | System accommodates different units of measurements for meter reads (Please list all the types of measurement supported in the comments section.) |
| 93 | UB | Meter Readings | System allows users to load meter reads in bulk |
| 94 | UB | Meter Readings | System accommodates bulk removal of duplicate reads that have been bulk-loaded |
| 95 | UB | Meter Readings | System processes meter reads obtained in the field and received in Excel spreadsheet from different municipalities |
| 96 | UB | Meter Readings | System tracks number of units per meter (used for rate calculation) per location, per customer |
| 97 | UB | Meter Readings | System tracks service line material type by location |
| 98 | UB | Meter Readings | System can service type by meter |
| 99 | UB | Account Close | System can generate final bill, collection letters (as required based on City defined criteria) |
| 100 | UB | Account Close | System can generate emails/texts or calls to customer based on delinquency (based on City defined criteria e.g. closed accounts) prior to the accounts going to Collections |
| 101 | UB | Account Close | Generate email notification to collection agency on a monthly basis |
| 102 | UB | Account Close | Calculates final bills during any cycle, based on the internal system issuance of a turn-off service order, or closing/transfer of a customer account |
| 103 | UB | Account Close | Permit off-cycle billing for accounts that have been disconnected in order to get final bills to customers as soon as possible |
| 104 | UB | Account Close | System integrates with AP and refunds remaining credit balances through AP (based on City defined criteria) |
| 105 | UB | Account Close | System provides amount to refund if necessary |
| 106 | UB | Account Close | System requires forwarding address for account close (and reuse service address if required) |
| 107 | UB | Account Close | System generates mail to multiple addresses |
| 108 | UB | Service Requests | System provides mobile/remote access for meter readers and meter maintenance technicians (i.e., iPad or other mobile device through mobile app or responsive design) |
| 109 | UB | Service Requests | Mobile application displays service requests and routes on a map. |
| 110 | UB | General Billing | System has capability to process monthly cycle, manual and final billings. |
| 111 | UB | General Billing | System calculates billing and fees for different services including (but not limited to): |
| 112 | UB | General Billing | Multi-family |
| 113 | UB | General Billing | Irrigation |
| 114 | UB | General Billing | Residential potable |
| 115 | UB | General Billing | Commercial |
| 116 | UB | General Billing | Trash/Rolloff |
| 117 | UB | General Billing | Outside water |
| 118 | UB | General Billing | Sewer |
| 119 | UB | General Billing | System can calculate billing for multiple services |
| 120 | UB | General Billing | System can calculate billing charges based on complex rate structure |
| 121 | UB | General Billing | System can calculate billing based on the billing period/prorate for short or long bills |
| 122 | UB | General Billing | System has the ability to calculate special charges |
| 123 | UB | General Billing | System has the ability to calculate taxes |
| 124 | UB | General Billing | System maintains multiple rate tables that can determine charges by type of service |
| 125 | UB | General Billing | System maintains multiple rate tables that can determine charges by type of service type of customer (residential / commercial) |
| 126 | UB | General Billing | System maintains multiple rate tables that can determine charges by consumption |
| 127 | UB | General Billing | System maintains multiple rate tables based on residential and commercial accounts |
| 128 | UB | General Billing | System maintains multiple rate tables that can set flat fee charges |
| 129 | UB | General Billing | Rate tables can be set to tiered rate tables with consumption charged at marginal rate for each unit of consumption |
| 130 | UB | General Billing | System utilizes tiered billing structures to recognize inclining/declining block rates, thresholds of consumption, and rate differentials by customer type |
| 131 | UB | General Billing | Rate tables can be set to flat fee (service charge) |
| 132 | UB | General Billing | Rate tables can be updated based on effective date per service |
| 133 | UB | General Billing | Rate tables can be automatically updated based on specified percentage per service |
| 134 | UB | General Billing | System allows special fees (i.e. Excessive hazardous material discharge) to be added to the account when service is rendered, as opposed to when the service request has been closed |
| 135 | UB | General Billing | System calculates rates based on tonnage |
| 136 | UB | General Billing | System can establish a minimum invoice amount |
| 137 | UB | General Billing | System generates bills on multiple billing cycles |
| 138 | UB | General Billing | System has built in controls related to completion of all required cycle actions within a defined sequence |
For example; meter reading, then billing, then ACH, then collection notifications, etc.
| 139 | UB | General Billing | System has option to determine who receives bills (tenant, landlord, or both, etc.) |
| 140 | UB | General Billing | System has option to determine who receives bills by service type |
| 141 | UB | General Billing | System generates bill/notice/communication to multiple recipients (tenant gets bill, landlord gets notice, etc.) |
| 142 | UB | General Billing | Third party can receive bill instead of account owner |
| 143 | UB | General Billing | System supports electronic billing (paperless) |
| 144 | UB | General Billing | System can Email copy of bill to customer |
| 145 | UB | General Billing | System supports online billing |
| 146 | UB | General Billing | Customer can access bill from online portal |
| 147 | UB | General Billing | System can calculate estimated readings based on billing period |
| 148 | UB | General Billing | System supports estimated billing (monthly billing with bi-monthly meter read) |
| 149 | UB | General Billing | System prints bill with reading and consumption amount |
| 150 | UB | General Billing | System prints bill with graphical display of usage |
| 151 | UB | General Billing | Systems prints bill with number of days, usage and average (1 unit equals X gallons) |
| 152 | UB | General Billing | Provides pre-printed bills with a back page message |
| 153 | UB | General Billing | System prints bill with notes / Special Instructions to Customer |
| 154 | UB | General Billing | System provides capability to print bill from City printer (individual bills on demand) |
| 155 | UB | General Billing | System has the ability to make manual adjustments to bill and adjust reports and graphics based on the adjustments to the bill |
| 156 | UB | General Billing | System adds administrative fees for adjustments based on user-defined criteria |
| 157 | UB | General Billing | System has the ability to bill minimum billing without reading |
| 158 | UB | General Billing | System has the ability to flag account billing that have charges or consumption out of specific parameters |
| 159 | UB | General Billing | System has the ability to generate multiple billing reports including: |
| 160 | UB | General Billing | Customers billed |
| 161 | UB | General Billing | Unread accounts |
| 162 | UB | General Billing | Unpaid accounts |
| 163 | UB | General Billing | Type of billing |
| 164 | UB | General Billing | Read and Unread |
| 165 | UB | General Billing | Unbilled listings |
| 166 | UB | General Billing | Leftover reads |
| 167 | UB | General Billing | Service on/service off |
| 168 | UB | General Billing | Next-time billing |
| 169 | UB | General Billing | Backflow |
| 170 | UB | General Billing | Cut cable/endpoint tamper |
| 171 | UB | General Billing | Missed/skipped |
| 172 | UB | General Billing | Leak |
| 173 | UB | General Billing | Closed; Doubtful; Write-off; Bankruptcy accounts with zero consumption |
| 174 | UB | General Billing | Doubtful accounts with zero consumption |
| 175 | UB | General Billing | Active accounts with greater than a City defined number of gallons in a defined timeframe e.g. >500,000 gallons |
| 176 | UB | General Billing | Active accounts with zero consumption |
| 177 | UB | General Billing | Active residential accounts with less than a City defined number of gallons in a defined timeframe e.g. <500 gallons |
| 178 | UB | General Billing | Active residential accounts with greater than a City defined number of gallons in a defined timeframe e.g. >19,131 gallons |
| 179 | UB | General Billing | Active commercial accounts with greater than a City defined number of gallons in a defined timeframe e.g. >34,500 gallons |
| 180 | UB | General Billing | Meters over a certain size with zero consumption e.g. > 1.5" meters with zero consumptions (used it make sure the meter has been tested to prevent future back billing) |
| 181 | UB | General Billing | Reporting on the test circle codes; meter size, endpoint prior to exporting the billing cycle to prevent errors in importing the readings if a change out has occurred |
| 182 | UB | General Billing | Hydrant Meter reporting - to provide reads and pictures of the registers |
| 183 | UB | General Billing | System provides dashboard (or interface to ERP's dashboard) to monitor Past Due accounts and other relevant billing data |
| 184 | UB | Deposits | System refunds deposit after one year of on-time payments, or other City defined criteria |
| 185 | UB | Deposits | System will manage deposit requirements based on City defined criteria (e.g. penalties on account) |
| 186 | UB | Deposits | System will accept surety bonds or letters of credit in lieu of deposit |
| 187 | UB | Deposits | System will report/flag when a surety bond or letter of credit has expired |
| 188 | UB | Collections | System provides mail merge templates that use system information to generate customer letters |
| 189 | UB | Collections | System can provide a file for a third party bill printer |
| 190 | UB | Collections | System automatically applies late penalties to any overdue payments |
| 191 | UB | Collections | System will add Non-Sufficient Finds (NSF) fees to account balance based on City defined criteria. |
| 192 | UB | Collections | System generates reminder notices for late payments via text/email/phone/mail |
| 193 | UB | Collections | System provides statement with all outstanding payments and late charges (paper and/or electronic) |
| 194 | UB | Collections | System provides dunning capabilities (30/60/90 statements) |
| 195 | UB | Collections | System generates statement with outstanding charges, penalties/interest |
| 196 | UB | Collections | System generates statements with consumption history |
| 197 | UB | Collections | System provides account write-off capability |
| 198 | UB | Collections | System termination letters identify which service or services and minimum amount to pay to avoid disconnect. |
| 199 | UB | Collections | System automatically generates reconnect fee for payment to be reconnected |
| 200 | UB | Collections | System has the ability to configure arrangements (payment plans) based on specific amounts or specific amounts plus current bill |
| 201 | UB | Collections | System has the capability to flag City and Bank holidays as blackout dates for payment plans and service terminations. |
| 202 | UB | Collections | System can age balances on accounts |
| 203 | UB | Collections | System can report on aged balances by service, account type and age |
| 204 | UB | Collections | System can automatically establish a disconnect process for payment plan customers. |
| 205 | UB | Collections | System allows users with appropriate security to waive deposits or penalties |
| 206 | UB | Collections | System flags accounts that are ineligible for shut-off based on City defined criteria |
| 207 | UB | Collections | System flags RSV-enabled accounts |
| 208 | UB | Collections | System automatically flags lockout status |
| 209 | UB | Payments | System will create file to pull payments from a customer's financial institution |
| 210 | UB | Payments | System will show payments in real time as pending prior to review and update |
| 211 | UB | Payments | System has the ability to accept multiple payment types (cash, check, credit card, e-check, IVR, wire payments, etc.) |
| 212 | UB | Payments | System has the ability to accept payment through multiple mediums (in-person, IVR, online, bank files, etc.) |
| 213 | UB | Payments | System has point of sale capability. If not, please advise a third party you would partner with. |
| 214 | UB | Payments | System will process payments (and update customer accounts) that are made through Lock Box Services (i.e. retail locations such as Walmart, CVS or Family Dollar) |
| 215 | UB | Payments | System's payment portal has the ability to accept payments if the user creates an account or if the user would like to pay as a guest |
| 216 | UB | Payments | System generates reports for cashier balancing |
| 217 | UB | Payments | System generates various reports based on payments by amount and payment method |
| 218 | UB | Payments | System will accept assistance agency pledges and show as pending on account |
| 219 | UB | Payments | System will accept assistance agency payments based on the pledge and will automatically clear pledge |
| 220 | UB | Payments | System will show assistance agency pledge deducted from the balance on billing and collection notices |
| 221 | UB | Payments | System will import payments via text file |
| 222 | UB | Payments | System will stop collections process with a full payment or % of balance. |
| 223 | UB | Payments | System will automatically generate a turn-on service request based on customer payment. (EX: If a customer pays a delinquent balance in full or a customer paid their initial deposit, etc.) |
| 224 | UB | Payments | System will to easily track payments and adjustments |
| 225 | UB | Location Information | System accommodates two separate files for each account, one for the location and the other for the customer. |
| 226 | UB | Location Information | System tracks history of all accounts at location (unique identifier for each location) |
| 227 | UB | Location Information | System will have multiple locations for each master location (parent/child) (example: landlord owns apartments in multiple locations and pays one service for all locations) |
| 228 | UB | Location Information | Users can explore the history of a location separate and apart from the history of a given customer. (For example: the location may have the history of three different customers that live there over the course of ten years) |
| 229 | UB | Location Information | System tracks activity against each location separate and apart from activity against each customer file. |
| 230 | UB | Location Information | System will pull directly from (or synchronize with) the GIS address and parcel files. |
| 231 | UB | Location Information | System can view GIS address/parcel information from within the application screens |
| 232 | UB | Location Information | System can display activity from service requests and work orders at a specified location |
| 233 | UB | Location Information | System can read/display ESRI REST end point services or consume feature data sets from ARCGIS Online |
| 234 | UB | Self Service | System allows users to access online payment portal to view current and past bills |
| 235 | UB | Self Service | System can be setup to allow customer to request and/or schedule services (e.g., turn on/turn off, move in/ move out, meter testing, etc.) |
| 236 | UB | Self Service | System generates application fees |
| 237 | UB | Self Service | System allows users access to online payment portal to review consumption information |
| 238 | UB | Self Service | System allows users access to online payment portal to view payment history |
| 239 | UB | Self Service | System allows users access to online payment portal to make payment |
| 240 | UB | Self Service | System allows customer to make payment through credit/debit card |
| 241 | UB | Self Service | System allows customer to make payment through direct withdrawal from checking account or other account (credit/debit/Apple Pay, etc.) |
| 242 | UB | Self Service | Customer can set up automatic payments on website through bank draft and/or credit card |
| 243 | UB | Self Service | Customer can set up automatic notifications for consumption over user defined amount |
| 244 | UB | Self Service | Customer can update forwarding address, email address, phone number, etc. within the self service portal |
| 245 | UB | Self Service | Audit trail created when personal information is updated. Audit trail should be able to be searched, viewed, reported on. |
| 246 | UB | Self Service | System has the ability to block a particular payment type for a particular customer/account |
| 247 | UB | Self Service | System can notify customer if payment method is blocked/unaccepted |
| 248 | UB | Self Service | System can support phone based payment e.g. IVR/auto attendant |
| 249 | UB | Self Service | System can support pre-notifications prior to scheduled payment being taken |
| 250 | UB | Backflow Prevention | System can track backflow prevention devices based on location, customer and service type (This includes existing devices and the ability to enter/upload data on newly installed devices.) |
| 251 | UB | Backflow Prevention | System can track last date backflow prevention device was tested, the next date that testing is required and the results of testing (both current and historic) |
| 252 | UB | Backflow Prevention | System can generate report (for third party) of upcoming testing requirements for backflow prevention devices. Report to include: address, meter number, end point number, location/description of meter location, meter size, customer account number, etc. |
| 253 | UB | Backflow Prevention | Testing of backflow prevention devices can be completed in the field using mobile devices and uploaded to the system. |
| 254 | UB | Backflow Prevention | Data (and pictures/videos) from testing in the field can be uploaded to the system by third party, based on City defined security controls. Please list any limitations in the comments. |
| 255 | UB | Backflow Prevention | System can generate communication with customers via text/email/mail/phone based on testing requirements and/or testing results (This can include requirements for testing, options for testing, testing results and remediation, etc.) |
| 256 | UB | Backflow Prevention | System can create Cross Connection Control Annual report for FDEP. |
| 257 | UB | Backflow Prevention | System can automatically add a defined fee to customers that selects to have the City arrange for backflow prevention device testing on their behalf. |
| 258 | UB | Technical | System has the ability for the system to interface with other systems using API or direct connector to activate or trigger certain events within the system and in connected systems. Please list any limitations in the comments. |
| 259 | UB | Technical | System has complete technical documentation on connectivity and data mapping that can be provided to the client |
| 260 | UB | Technical | System uses effective dating |
| 261 | UB | General | System will mask any discrete data element based on user preferences. (e.g., Government ID number). Visibility to masked data should be controlled based on security permissions. |
| 262 | UB | General | System will search any field within the system. (Please identify any limitations in the comments) |
| 263 | UB | General | System can accommodate multi-level electronic workflow approvals. Please list any limitations or third-party systems in the comments. |
| 264 | UB | General | System allows users to conduct transactions offline and syncs later when Wi-Fi is available. Please list any limitations in the comments. |
| 265 | UB | General | System supports mobile technology (e.g., mobile phone, iPad, mobile devices). Please list any limitations in the comments. |
| 266 | UB | General | System is browser agnostic (e.g., Chrome, Firefox, Edge, Safari). Please list any limitations in the comments. |
| 267 | UB | General | System will allow attachments (e.g., Word, PDF, Excel, jpeg, HEIC and video) to transactions in the system. Please list any limitations in the comments. |
| 268 | UB | Security | System has the ability to set security for access, viewing and add, edit, delete capabilities |
| 269 | UB | Security | System has the ability to base security access or restrictions based on user and/or group |
| 270 | UB | Security | System has the ability to schedule jobs to run and update during non business hours without a user monitoring or starting job |
| 271 | UB | Security | System will automatically track changes to accounts by user account for audit purposes |
| 272 | UB | Security | System will automatically track changes to individual transactions by user account for audit purposes |
| 273 | UB | Security | System uses role-based security where security roles are tied to users |
| 274 | UB | Security | System supports geo fence capabilities, geo block or geo track login information |
| 275 | UB | Security | System uses role-based security where security roles are tied to positions |
| 276 | UB | Security | Security settings can be set to allow user to add data |
| 277 | UB | Security | Security settings can be set to allow user to delete data |
| 278 | UB | Security | Security settings can be set to allow user to change data |
| 279 | UB | Security | Security settings can be set to allow user to view data (Read-only access). Please list any limitations in the comments. |
| 280 | UB | Security | Audit log tracks user permission changes, user log on, and user log off. |
| 281 | UB | Security | System is PCI/DSS compliant |
| 282 | UB | Security | System supports Single Sign-On through MS Entra ID |
| 283 | UB | Reporting | System allows creation, scheduling, distribution and control of automated report generation. |
| 284 | UB | Reporting | System has an out-of-the-box reporting/dashboarding system |
| 285 | UB | Reporting | System has the ability to integrate with a mainstream reporting/dashboarding services product (e.g., SQL Server Reporting Services, Crystal Reports, PowerBI, Tableau). Please note any limitations in the comments |
| 286 | UB | Reporting | System allows adding/creating custom and complex reports (For example Crystal Reports, SSRS, or Power BI, other Data analytics tools). Please list any limitations and third-party in the comments. |
| 287 | UB | Reporting | System allows ad-hoc query on any field in system. Please list any limitations in the comments. |
| 288 | UB | Reporting | Queries can be saved, reused and shared. Please list any limitations in the comments. |
| 289 | UB | Reporting | System provides dash boarding tools to present data. Please list any limitations in the comments. |
| 290 | UB | Reporting | Reports can be scheduled and distributed (via email or dashboard). Please list any limitations and third-party in the comments. |
| 291 | UB | Reporting | System has drill-down capabilities to access source data in the system. Please list any limitations in the comments. |
| 292 | UB | Reporting | System allows for user-defined dashboards with flexibility to add/subtract data/charts. Please list any limitations and third-party in the comments. |
| 293 | UB | Reporting | Ad-hoc reporting is available throughout the system |
| 294 | UB | Reporting | System automatically generates monthly revenue report each month with total revenue, revenue by account type, and revenue by service type |
| 295 | UB | Reporting | System allows reports to be exported in multiple formats (e.g. Excel, pdf, Word, etc.). Please list any limitations in the comments. |
| 296 | UB | Reporting | System allows dashboards to be shared with other users. Please list any limitations in the comments. |
| 297 | UB | Reporting | System reports on consumption by account type |
| 298 | UB | Reporting | System can generate a report to identify services/accounts that have been disconnected for a specified reason (e.g. non-payment) |
| 299 | UB | Reporting | System can support geo based report (e.g. polygon shape file, etc) by City defined criteria |
| 300 | UB | Key Performance Indicators | The system can track Key Performance Indicators (KPIs) in a variety of City-defined categories. Please list any limitations in the comments. |
| 301 | UB | Key Performance Indicators | The system can report KPIs in a dashboard. Please list any limitations and third-party in the comments. |
| 302 | UB | Embedded Help Features | System includes training references, (i.e., how-to guide, video). Please list any limitations in the comments. |
| 303 | SW | Waste Collection | System has the ability to track / bill Waste Container and Waste collection services |
| 304 | SW | Waste Collection | System has the ability to maintain Account Number for each container for the following: |
| 305 | SW | Waste Collection | Containers Billed |
| 306 | SW | Waste Collection | Containers Issued |
| 307 | SW | Waste Collection | Annual Billing Level |
| 308 | SW | Waste Collection | Serial Number |
| 309 | SW | Waste Collection | Issue Date |
| 310 | SW | Waste Collection | Pickup Date |
| 311 | SW | Waste Collection | Pickup Day |
| 312 | SW | Waste Collection | Frequency |
| 313 | SW | Waste Collection | Route/Day of Service |
| 314 | SW | Waste Collection | Systems will track multiple Waste and Recycling containers for each account / location by container number. Please list any limitations in the comments. |
| 315 | SW | Waste Collection | Systems will track multiple Waste and Recycling containers for each account / location by container barcode and/or RFID. Please list any limitations in the comments. |
| 316 | SW | Waste Collection | System allows for the creation of waste container-related service requests and work orders (e.g., bulk pickup, container repair, additional container order, etc.) |
| 317 | SW | Waste Collection | System allows adding new containers into inventory through a batch job (e.g., 100's to 1000's at a time) |
| 318 | SW | Waste Collection | System generates route sheets, including special routes |
| 319 | SW | Waste Collection | System enables routes to be displayed on a mobile device. Please list any limitation in the comments. |
| 320 | SW | Waste Collection | System enables all routes/remaining stops to be displayed |
| 321 | SW | Waste Collection | System allows routes/stops to be reassigned as required. Please list any limitations in the comments |
| 322 | SW | Waste Collection | Additional stops (special pick-ups) can be added to existing routes. This could be while route is in progress. |
| 323 | SW | Waste Collection | System can be integrated to GPS application on trucks to track vehicle locations |
Note: Current application used to review trucks and retrieve video footage is 3rd Eye
| 324 | SW | Waste Collection | System can track status of each stop (e.g. Has stop been serviced or is it still outstanding?) |
| 325 | SW | Waste Collection | New account can be added dynamically to route, based on City defined approval process |
| 326 | SW | Waste Collection | System allows field technicians to attach photos |
| 327 | SW | Waste Collection | System can attach photos to specific location or route |
| 328 | SW | Waste Collection | System allows field technicians to measure the bulk pile (roadside) |
| 329 | SW | Waste Collection | System allows field technicians to complete charge ticket in the field |
| 330 | SW | Waste Collection | System verifies address for field technicians (e.g. Can define location address based on photo location/GPS coordinates) |
| 331 | SW | Waste Collection | System has the ability to shift routes for holiday weeks (e.g. override system to move routes by one day for holiday week only) |
| 332 | SW | Waste Collection | System will capture weight/load ticket information by service order or route |
| 333 | SW | Waste Collection | System will reconcile weight/load ticket information with third party invoice by service order or route or class of material |
| 334 | SW | Waste Collection | System will report on tonnage, class of material, by truck number, by date, by weight ticket number, by account type |
| 335 | SW | Waste Collection | System will scan weight tickets into system using OCR, etc. Please list any limitations in the comments |
| 336 | SW | Waste Collection | System allows uploading data from third party waste disposal sites/vendors. Please list any limitations in the comments |
| 337 | SW | Waste Collection | System will complete review/reconciliation with approval step following upload of third party file |
| 338 | SW/UB | Service Requests | System can check/warn and notify for duplicate service requests based on caller, location, or account before creating new one. |
Please specify any limitations in the comments.
| 339 | SW/UB | Service Requests | System provides cutoff listing |
| 340 | SW/UB | Service Requests | Need to be able to inquire and report on various conditions (e.g. high usage, zero reads) |
| 341 | SW/UB | Service Requests | System has the ability to establish billing rates per service (EX: Some service orders have fees tied to them) |
| 342 | SW/UB | Service Requests | System has the ability to add a fee based on specific circumstances (e.g. blocked container, locked gate, contamination, etc.) |
| 343 | SW/UB | Service Requests | Can disconnect from one utility and not the other or any combination of utilities |
| 344 | SW/UB | Service Requests | System has the ability to generate door hangers |
| 345 | SW/UB | Service Requests | System has the ability to distribute notifications of disconnect via email/text/phone/mail |
| 346 | SW/UB | Service Requests | System can automate service orders to service technicians |
| 347 | SW/UB | Service Requests | System can differentiate between turn-on/turn-off and move-in/move-out |
| 348 | SW/UB | Service Requests | System tracks service request types (e.g. calls for new service, meter/service problem investigation) |
| 349 | SW/UB | Service Requests | System creates work orders from service request (work order type to be determined by the results of the service request) |
| 350 | SW/UB | Service Requests | System links work orders and/or creates additional work orders based on needs that are identified during the work (e.g. work could not be completed in field) |
| 351 | SW/UB | Service Requests | Notes can be added to a service request and work order and can be coded to the customer or the location |
| 352 | SW/UB | Service Requests | System allows users to add Notes/Logs relevant to account, location, customer, or equipment accessible by meter reader/technician in field on mobile device |
| 353 | SW/UB | Service Requests | System requires approval step before service request is completed |
| 354 | SW/UB | Service Requests | System supports internal notification (e.g. via email) for City defined criteria including service request type, priority, severity, etc |
| 355 | SW/UB | Work Orders | Notes/Logs relevant to account, location, customer, or equipment accessible by meter reader/technician in field on mobile device. |
| 356 | SW/UB | Work Orders | System allows mobile work orders (through Toughbooks, tablets, smartphones) |
| 357 | SW/UB | Work Orders | Mobile application displays work orders and routes on a map. |
| 358 | SW/UB | Work Orders | System can check for duplicate work orders based on asset id, location, or account before creating new one. Please specify any limitations in the notes. |
| 359 | SW/UB | Work Orders | System can track priority for each work order. |
| 360 | SW/UB | Work Orders | System can track date of request for each work order. |
| 361 | SW/UB | Work Orders | System can track problem type from drop-down menu for each work order |
| 362 | SW/UB | Work Orders | System can track location for each work order |
| 363 | SW/UB | Work Orders | System can track meter/radio for each work order |
| 364 | SW/UB | Work Orders | System should allow for work order requests to be system-generated |
| 365 | SW/UB | Work Orders | System flags work orders for unpaid deposits, and notifies a defined set of users |
| 366 | SW/UB | Work Orders | System can interface with the meter software to automatically create service requests or work orders based on high consumption data or other alerts from said system. |
| 367 | SW/UB | Work Orders | System to notify requestor (including external customers) when work has been completed through automated notification (email, text, etc.) |
| 368 | SW/UB | Work Orders | Notify work requester of status changes, including date/time work requested |
| 369 | SW/UB | Work Orders | System routes updated meter read information to Billing when work order has been closed |
| 370 | SW/UB | Work Order Assignments/Scheduling | System allows internal users to schedule work orders based on current schedule and available technicians |
| 371 | SW/UB | Work Order Assignments/Scheduling | System assigns work orders based on current schedule and available technicians |
| 372 | SW/UB | Work Order Assignments/Scheduling | System routes work orders to technicians based on work order priority and geographic information (intelligent routing) |
| 373 | SW/UB | Equipment | System tracks equipment by type/account number |
| 374 | SW/UB | Equipment | System tracks equipment by ID/inventory number |
| 375 | SW/UB | Equipment | System can read/store equipment ID by scanning barcode or QR code |
| 376 | SW/UB | Equipment | System tracks equipment category/department by size |
| 377 | SW/UB | Equipment | System tracks equipment access and requirements |
| 378 | SW/UB | Equipment | System tracks equipment by location |
| 379 | SW/UB | Equipment | System tracks equipment by container |
File details come from the government source that posted it. Updated .