HomeMy WebLinkAbout26 - Instructions - Bozeman Utility Billing Software Services & Implementatiion RFP (3)Bozeman, MT
Interfaces
Please use the descriptions below to complete columns L - R on the subsequent tab.
If the Respondent recommends additional interfaces, please add them in the table at the bottom of the interfaces tab and include them in the fixed fee price.
Column
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
Response Key - Column L (Respondent Interface Plan)
Available Response
Keep
Temporary
Go-Away
Not Accommodate
Response Key - Column M (Direction_R)
Available Response
Inbound
Outbound
Bi-directional
Response Key - Column O (Method_R)
Available Response
API
File
N/A
Response Key - Column P (Experience)
Available Response
Yes
No
Response Key - Column Q (Type of Solution)
Available Response
Configurable
Customized
Indicates input cell for Respondent to supply information
Header
Application
Application Description
Interface Description
Comments
Direction
Frequency
Method
City Interface Plan
Direction_FS
Frequency_FS
Method_FS
Respondent Interface Plan
Direction_R
Frequency_R
Method_R
Experience
Type of Solution
Comments_R
Description
A permanent interface with the ERP solution
The interface that is only required during implementation
The interface that is no longer required as a result of the new ERP solution
Respondent will not accommodate this interface
Description
Respondent proposes an inbound data transfer to the ERP
Respondent proposes an outbound data transfer from the ERP
Respondent proposes a bi-directional data transfer to and from the ERP
Description
Respondent proposes an API to transfer data
Respondent proposes use of a file to transfer data
Type of connection is not applicable or unknown
Description
Respondent has developed an interface with the third-party solution
Respondent HAS NOT developed an interface with the third-party solution
Description
Existing interface that will need to be configured
Interface will require custom development
Description
Current City application
Description of application
Description of the interface needs with the application and future ERP
City's comment on the interface for additional context
Current data flow direction of interface
Current frequency of interface
Current method for interface
The City's intention for the interface plan
City's envisioned data flow direction of interface
City's envisioned frequency of interface
City's envisioned method for interface
Respondent's proposed interface plan
Respondent's proposed data flow direction
Respondent's proposed frequency of interface
Respondent's proposed method for interface
Indicate if Respondent has experience developing interfaces with the third-party solution or provider
Respondent should indicate if the solution is configurable or will require customed development
Respondent should include any comments or assumptions relevant to the answers above
Interface Requirements
Application
ActiveDirectory
Billing File Export / Provider
Cityworks
Future ERP System
Potential Future Point of Sale System
GIS (ESRI) - VantagePoint
Invoice Cloud
Laserfiche
Naviline
Neptune 360
PowerBI
Rams/Alpine Tech
US Bank
If Respondent recommends additional interfaces not included in this, please add them here and include in Price Proposal
Application Description
Add additional rows as necessary
Application Description
Single Sign On
Export billing statements for printer to print, stuff, and send
Work order management and asset tracking
TBD ERP
TBD POS
Infrastructure asset location tracking; Property file information
Online payments for utilities
Document storage
Current Utility Billing system that also provides ERP functionality
Current Water Meter System
Data reporting / manipulation
Current System used for Solid Waste Route Management and Inventory
Current City bank for deposits and payments
Interface Description Needs
Interface Description Needs
1. Employee ActiveDirectory data
1. Billing statement data
1. Work orders
2. Capital asset information (description, location, value, etc.)
1. Employee data
2. Chart of Accounts / GL Mapping
3. Cash receipts / deposit advice
4. Summary revenue data by account code
5. Accounts receivable summary
6. Refunds & deposits
1. Customer information
2. Account balance information
3. Payment information
1. Parcel data
2. Customer data
3. Asset information
1. Customer information
2. Revenue information (individual accounts and summary data)
TBD
1. Chart of Accounts / GL Mapping
2. Summary revenue data
1. Meter Reads (AMR/AMI/Manual)
2. Meter Status
3. Exception Flags
4. Final / Ad-hoc Read Requests
Access to system data for City to run ad-hoc and custom reports in PowerBI application
1. Customer account data
2. Asset information (tote sizes and serial numbers)
3. Ah-hoc fees
4. Work order / service request creation and close out
1. Payment collection
2. Disbursements (refunds)
3. Bank reconciliation
4. Return / NSF processing
Comments
Comments
The City would like to understand if providers can offer this functionality and / or service
The City uses Cityworks for some work orders so the City will have to decide if all work orders should go through Cityworks or if it should use the UB's work order system, if available
List ERP providers for which Respondent has a pre-existing integration
The City may procure a unified POS system for customers to make payments for multiple City services in one payment. If so, an integration would be required.
GIS is the source of truth for geospatial data
May be temporary integration until UB system goes live.
Possible need to link transactions to documents stored in Laserfiche
Envision needing a temporary integration for revenue data until new Utility Billing and Permitting systems go live
Reads generally done monthly for billing but need to daily access for final reads, etc.
Query-based reporting
Our current work orders are sent to Rams via email and updates the Rams database. Unfortunately, we only get a spreadsheet back in order to close the work orders and add charges/fees.
Payments and refunds, if UB system used as POS
Direction
Direction
None
Outbound
None
None
None
Bi-Directional
Inbound
None
None
Bi-Directional
Outbound
Outbound
None
Frequency
Current State
Frequency
N/A
Monthly
N/A
N/A
N/A
Daily
Auto - On Demand
N/A
N/A
Monthly
Daily
Daily-multiple times/day
N/A
Method
Method
N/A
File
N/A
N/A
N/A
Auto (programmatic) Procedures
Auto Procedures
N/A
N/A
Export/Import right now
Report Export
Spreadsheet
N/A
City Interface Plan
City Interface Plan
Keep
TBD
Keep
New
New
Keep
TBD
Keep
Temporary
Keep
Keep
New
New
Direction_FS
Direction_FS
Bi-directional
Outbound
Bi-directional
Bi-directional
Bi-directional
Bi-directional
Inbound
Bi-directional
Inbound
Bi-directional
Outbound
Bi-directional
Bi-directional
Frequency_FS
BZN Envisioned Future State
Frequency_FS
Real time
Ad-hoc
Hourly
Real time
Real time
Hourly
Hourly
Ad-hoc
Daily
Daily
Ad-hoc
Daily
Hourly
Method_FS
Method_FS
API
File
API
API
API
API
File
API
File
API
API
API
File
Respondent Interface Plan
Respondent Interface Plan
Direction_R
Direction_R
Frequency_R
Respondent Proposed Future State
Frequency_R
Method_R
Method_R
Experience
Experience
Type of Solution
Type of Solution
Comments_R
Comments_R