Attachment 6 - Interfaces.xlsx
XLSX spreadsheet 32 KB Posted
- Solicitation number
- 147077
- Issued by
- Los Angeles County, California
About this file
This file is an Interfaces workbook attachment for the City of Burbank's Enterprise Resource Planning (ERP) Software and Services RFP, providing detailed instructions and response templates for vendors to document proposed interface solutions between the new ERP system and existing applications. The workbook requires vendors to complete a comprehensive analysis across 21 existing systems currently used by the City, including Oracle EPM (budgeting and planning), Oracle WAM (work order and asset management), Oracle CCS (utility billing), ePLAS by EdgeSoft (permitting), FASTER (fleet management), E.J. Ward (fuel management), Telestaff/Intime (time entry), NeoGov (recruitment), Target Solutions (learning management), ESRI (GIS), and multiple third-party payroll and benefits systems such as CalPERS, Bank of America, Vertex, and IRS solutions. For each application, vendors must propose interface plans, data flow directions, frequency of data transfers, technical methods, and support strategies using standardized response keys provided in the workbook.
The workbook standardizes vendor responses through defined categories including interface plan types (Keep, Replace, Temporary, Go-Away, Not Accommodated), data flow directions (Inbound, Outbound, Bi-directional), transfer methods (API, File, N/A), vendor experience indicators, solution types (Configurable or Customized), and support providers (Software Developer, Third Party, or Not Supported). Key interface challenges identified by the City include manual workarounds in current Oracle EBS integrations, miscellaneous batch receipts affecting forensics and analysis for utility billing and permitting, the need to integrate the newly selected EAM system for asset management, and the requirement to seamlessly connect FASTER fleet management with capital asset tracking. Vendors must also address integration with multiple external payroll processors and benefits providers with no current ERP connectivity, alongside optional enhancements such as full LMS integration and GIS-based asset visualization capabilities for fleet and utility operations.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP IT-2026-01 ERP Software and Services.pdf | ||
| Attachment 5 - Acceptance Requirements.xlsx | XLSX spreadsheet | |
| Attachment 18 - Price Proposal.xlsx | XLSX spreadsheet | |
| Attachment 11 - Staffing Level of Effort.xlsx | XLSX spreadsheet |
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
Instructions
| Burbank, CA |
| Interfaces |
| Please use the descriptions below to complete columns L - S on the subsequent tab. | |
| Indicates input cell for Offeror to supply information |
| Column | Header | Description |
| A | Application | Current City application |
| B | Application Description | Description of application |
| C | Interface Description | Description of the interface needs with the application and future ERP |
| D | FdL Comment | City's comment on the interface |
| E | Offeror Interface Plan | Offeror's proposed interface plan |
| F | Direction_R | Offeror's proposed data flow direction |
| G | Frequency_R | Offeror's proposed frequency of interface |
| H | Method_R | Offeror's proposed method for interface |
| I | Experience | Indicate if Offeror has experience developing interfaces with the third-party solution or provider |
| J | Type of Solution | Offeror should indicate if the solution is configurable or will require customed development |
| K | Type of Support | Offeror should indicate the type of support for the interface |
| L | Comments | Offeror should include any comments or assumptions relevant to the answers above |
| Response Key - Column E (Offeror Interface Plan) | |
| Available Response | Description |
| Keep | A permanent interface with the ERP solution |
| Replace | System/Module will be replaced as part of the ERP process as will the interface |
| Temporary | The interface that is only required during implementation |
| Go-Away | The interface that is no longer required as a result of the new ERP solution |
| Not Accommodated | Offeror will not accommodate this interface |
| Response Key - Column F (Direction_R) | |
| Available Response | Description |
| Inbound | Offeror proposes an inbound data transfer to the ERP |
| Outbound | Offeror proposes an outbound data transfer from the ERP |
| Bi-directional | Offeror proposes a bi-directional data transfer to and from the ERP |
| Response Key - Column H (Method_R) | |
| Available Response | Description |
| API | Offeror proposes an API to transfer data |
| File | Offeror proposes use of a file to transfer data |
| N/A | Type of connection is not applicable or unknown |
tc={667B44BF-1024-4CEC-ABCA-AF933EFA4959}: [Threaded comment]
Your version of Excel allows you to read this threaded comment; however, any edits to it will get removed if the file is opened in a newer version of Excel. Learn more: https://go.microsoft.com/fwlink/?linkid=870924
Comment:
Are these helpful/desired by Burbank
| Response Key - Column I (Experience) | |
| Available Response | Description |
| Yes | Offeror has experience developing interface with third-party solution or provider |
| No | Offeror DOES NOT have experience developing interface with third-party solution or provider |
| Response Key - Column J (Type of Solution) | |
| Available Response | Description |
| Configurable | Existing interface that will need to be configured |
| Customized | Interface will require custom development specific for the City |
| Response Key - Column K (Type of Support) | |
| Available Response | Description |
| S | Interface will be supported by software developer |
| TPS | Interface will be supported by a third party |
| NS | Interface will not be supported |
| Response Key - Column L (Comments) | |
| Available Response | Description |
| Text | Include any comments or assumptions relevant to the answers above |
Are these helpful/desired by Burbank
Interfaces
| Interface Requirements | |||||||||||
| Respondent Proposed Future State | |||||||||||
| Application | Application Description | Interface Description | FdL Comments | Respondent Interface Plan | Direction_R | Frequency_R | Method_R | Experience | Type of Solution | Type of Support | Comments |
| Oracle EPM | Budgeting and Planning | Although the City is not necessarily looking for a replacement for Oracle EPM, if the proposed solution offers similar capabilities to the Planning and Reporting functions in Oracle EPM, the City would like to learn more about that solution. Alternatively, if Oracle EPM is retained alongside the proposed system, EPM will need to undergo a complete transformation to reflect the new interfaces from the future ERP, GL Structure, Dimensions, Reporting and forms. | Current: Interface with Oracle EBS with multiple manual workarounds for aspects of processing daily and longitudnal transactions. | ||||||||
| Oracle WAM | Work order, projet, and asset management | Utilized by Burbnk Water and Power (BWP) to manage utility-specific workorders and assets. | Current: The system is outdated and is currently under review for replacement under a separate RFP. The offeror will need to configure the ERP-specific integrations with the newly select EAM system which will be handling Utility Assets. All BWP inventory as well as other capital assets will be maintained in the newly selected ERP system. | ||||||||
| Oracle CCS | Utility Billing | Current interfaces exchange BWP customer AR data and customer refunds from AP back to CCS | Data often carries as a miscellaneous batch reciepts which makes forensics and analysis dificult. | ||||||||
| ePLAS by EdgeSoft | Permitting | Handles all permitting needs except for Film Permits. This system is currently being considered for replacement under a separate RFP. The current interface creates miscellaneous receipts for permit fees which makes customer tracking and refunds difficult. | The current interface creates miscellaneous receipts for permit fees which makes customer tracking and refunds difficult. And miscellaneous batch reciepts makes forensics and analysis dificult. | ||||||||
| FASTER | Fleet Management | All Fleet Managment work order and asset tracking. No current interface with ERP | Keeping FASTER and need ERP integration to enable seamless tracking of capital assets | ||||||||
| E.J. Ward | Fuel Management | Syncs fuel transactions in the ERP to deduct Fuel inventory from City owned fuel tanks and creates the necessary financial transactions as a result | Need interface with ERP and system to track and audit inputs when field equipment fails | ||||||||
| Telestaff/Intime | Police and Fire time entry | Does not currently interface leading to manual work for payroll and other timekeeping processes. | Needs to interface | ||||||||
| NeoGov | Candidate reruitment | Handles all recruiting activities and process through new employee onboarding and no current integration to ERP. | No current integrations with ERP and integration solution needed. | ||||||||
| Target Solutions LMS | Learning Managment System | Limited interface with ERP. | An LMS solution or a pre-integrated solution built into HCM with ability to add specific city content to replace Target Solutions with a fully integrated LMS system | ||||||||
| ESRI | GIS and BWP Asset tracking | Utilized for GIS. Currently not integrated with the ERP | City desired to use location and visual/picture data to utilize GIS data for multiple fleet and asset applications inside the future ERP | ||||||||
| CalPERS | Medical Benefits | No current ERP interface | ERP integration deisired for open enrollement of benefits, changes, and payroll | ||||||||
| BERMT | Burbank Employees Retiree Medical Trust | No current ERP interface | ERP integration deisired, but basic reporting and systems checks needed at a minimum. | ||||||||
| VEBA | Voluntary Employees Beneficiary Association | No current ERP interface | ERP integration deisired, but basic reporting and systems checks needed at a minimum. | ||||||||
| IRS | No current ERP interface | ERP integration deisired, but basic reporting and systems checks needed at a minimum. | |||||||||
| Vertex | Tax calculation | No current ERP interface | ERP integration deisired, but basic reporting and systems checks needed at a minimum. | ||||||||
| EDD (California Employee Development Department) | Unemployment payment and tracking system | No current ERP interface | ERP integration deisired, but basic reporting and systems checks needed at a minimum. | ||||||||
| Great Western | 457 Plans | No current ERP interface | ERP integration deisired, but basic reporting and systems checks needed at a minimum. | ||||||||
| Mission Square | 457 Plans | No current ERP interface | ERP integration deisired, but basic reporting and systems checks needed at a minimum. | ||||||||
| PERS | Retierment | No current ERP interface | ERP integration deisired, but basic reporting and systems checks needed at a minimum. | ||||||||
| Bank of America | Payroll Processing | No current ERP interface | ERP integration deisired, but basic reporting and systems checks needed at a minimum. | ||||||||
| Evident ID | Vendor insurance verification and status | No current ERP interface | ERP integration deisired, but basic reporting and systems checks needed at a minimum. | ||||||||
| TINCheck | IRS Tin Verification Tool | No current ERP interface | ERP integration deisired, but basic reporting and systems checks needed at a minimum. | ||||||||
| US Bank | P-Card provider | Expense transaction detail (vendor, amount, date), but posted to accounting as a single batch payment | Data often carries as a miscellaneous batch reciepts which makes forensics and analysis dificult. |
&F &A &P
File details come from the government source that posted it. Updated .