FM_UB_ATT_11_Interface_List.xlsx
XLSX spreadsheet 15 KB Posted
- Solicitation number
- RFP 26-106
- Issued by
- Lee County, Fort Lauderdale City, Florida
About this file
This is an Interface List attachment for the City of Fort Myers, Florida's implementation of a new Oracle Utilities Billing System. The document outlines the technical integration requirements between the proposed ERP system and existing third-party systems that support the City's water, wastewater, and solid waste utility operations. The interface list identifies five systems requiring integration: Paymentus (online payment application), ITRON AMI software (automated meter infrastructure), WaterSmart (customer portal), InfoSend (billing service), and two systems under evaluation—a Point of Sale application and a backflow testing results system. For each interface, the vendor proposer must specify whether the existing system will be retained with a permanent interface built into the project, replaced with the new ERP functionality, or replaced with a new third-party system.
The document establishes standardized response categories for vendors to document integration specifications across four key dimensions: direction of data flow (inbound only, outbound only, or bi-directional), duration (temporary during implementation or permanent for the system's lifetime), frequency (real-time, hourly, daily, weekly, or monthly), and any applicable comments. The City notes its openness to alternatives, including retaining WaterSmart or adopting Oracle's native customer portal, and indicates that the current Tyler Cashiering system should be replaced with an integrated Point of Sale solution. All new third-party systems proposed as part of the vendor's solution must be added to this interface list to ensure comprehensive integration planning and technical feasibility assessment during the implementation process.
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_9_Conversions_v1.xlsx | XLSX spreadsheet | |
| FM_UB_ATT_6_Project_Expectations.pdf | ||
| FM_UB_ATT_10_Cost.xlsx | XLSX spreadsheet | |
| FM_UB_ATT_12_Reports_v2.xlsx | XLSX spreadsheet | |
| FM_UB_ATT_7_Functional_Requirements_v2.xlsx | XLSX spreadsheet | |
| FM_UB_ATT_8_Project_Staffing.xlsx | XLSX spreadsheet | |
| FM_UB_ATT_1_Signature_Page.pdf | ||
| FM_UB_ATT_3_Prof_Svcs_Background.pdf | ||
| INSURANCE_REQUIREMENTS_CHART.pdf | ||
| FM_UB_ATT_5_Technology_Deployment.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
Sheet1
| Utility Billing - City of Fort Myers, FL | ||||||
| Attachment 9 (Interface List) | ||||||
| Column E: Available Responses | ||||||
| Replace w/ERP | System is replaced with functionality native to the new the ERP | |||||
| Replace w/New TPS | System is replaced with a new Third Party System (TPS) that has been proposed as part of the new solution | |||||
| Keep | Keep the current system and build a permanent interface as part of the project | |||||
| Column F: Available Responses | ||||||
| Inbound Only | Data will be pulled from the TPS into the ERP System | |||||
| Outbound Only | Data will be pushed from the ERP System into the TPS | |||||
| Bi-Directional | Data will be pushed from the ERP System into the TPS and pulled from the TPS into the ERP System | |||||
| Column G: Available Responses | ||||||
| Temporary | Interface will be needed for limited amount of time during the project be will not be necessary after the project is completed | |||||
| Permanent | Interface will be needed for the life-time of the ERP System | |||||
| Column H: Available Responses | ||||||
| Real-Time | Data is transferred, at a minimum, every 15mins. | |||||
| Hourly | Data is transferred, at a minimum, every 60mins. | |||||
| Daily | Data is transferred, at a minimum, every 24 hours | |||||
| Weekly | Data is transferred, at a minimum, every 7 days | |||||
| Monthly | Data is transferred, at a minimum, every 30/31 days | |||||
| Column J: Available Responses | ||||||
| Yes | ||||||
| No | ||||||
| NOTE: All new Third Party Systems (TPS) that are part of the proposal should be added to this list. | ||||||
| THIS SECTION IS TO BE COMPLETED BY THE VENDOR/PROPOSER | ||||||
| System Name | Description / Use Case | City's Plan | Vendor Recommendation | Direction | Frequency | Comments |
| Paymentus | Online payment application | Keep | ||||
| ITRON | AMI software/NAA | Keep | ||||
| WaterSmart * | Customer portal | Keep | ||||
| InfoSend | Billing service | Keep | ||||
| TBD ** | Point of Sale application | Replace w/New TPS | ||||
| TBD *** | Backflow testing results | Replace w/New TPS |
| * The City is open to keeping WaterSmart or to utiliizing an Oracle customer portal |
| ** The City currently uses Tyler Cashiering but would like to replace it with a POS system that integrates with Oracle |
| *** The City is working to onboard a new vendor for backflow testing. The results of this testing wll need to be added to the Utility Inventory |
File details come from the government source that posted it. Updated .