ESBD_File_353172_RFI_UtilityInvProcessing_Addendum 1 & Questions and Answers.pdf

125 EAST 11TH STREET, AUSTIN, TEXAS 78701-2483 | 512.463.8588 | WWW.TXDOT.GOV

OUR VALUES: People • Accountability • Trust • Honesty OUR MISSION: Connecting You With Texas

An Equal Opportunity Employer

ADDENDUM No. 1

DATE: 3/25/2024

SOLICITATION TITLE: Utility Invoice Processing Service

SOLICITATION NO.: RFI_UtilityInvProcessing

RESPONSE SUBMISSION DUE DATE: 3/27/2024

Change Response Due Date:

From: 03/27/2024

To: 04/03/2024

Purchasing Point-of-Contact: Carolyn Brooks, CTCD, CTCM

TEXAS DEPARTMENT OF TRANSPORTATION

DocuSign Envelope ID: 17709689-19DA-447A-A6BB-5FEC56CA9A82

Rev. 2/2/23

Questions and Answers

TxDOT Solicitation No. RFI – Utility Invoice Priocessing Service

Solicitation Title: Utility Invoice Priocessing Service

Date: 03/25/2024

Question Answer

1. Question: Invoice Data Interaction: Could you please elaborate on how TxDOT envisions interacting with the invoice data? Are there specific functionalities or data analytics features that you wish to prioritize?

TxDOT is interested in what the industry has available with regard to invoice data, the functionalities and data analytics.

2. Question: User Roles and Numbers: Could you provide us with details on the anticipated number and types of users who will be operating the UIPS? Understanding whether they are Analysts, Accounts Payable Clerks, Managers, etc., would help us tailor the user experience and access controls.

Please tell us what the capabilities of your offering with reguard to user roles and numbers

3. Question: Third-Party Tools Integration vs.

Custom Development: In reference to the third-party tools mentioned, does TxDOT prefer utilizing existing tools, or would you be inclined towards a custom-developed solution that caters to your specific needs?

TxDOT would like to know what is available.

Does your offering allow integration and or custom development?

4. Question: Volume and Structure of Invoices:

With the four electric utility providers mentioned, does TxDOT receive a single consolidated invoice from each, summarizing all locations? Or would it be several invoices, one or more for each location? The anticipated volume and format will guide our strategy.

Please provide the capabilities of your offering.

Rev. 2/2/23

Question Con’t Answer Con’t

5. Question: Preference for Electronic Data Interchange (EDI) Integrations: Is TxDOT interested in exploring direct API, WSDL, or EDI integrations as alternatives to traditional invoice processing? We would like to understand if there is a preference for direct data integrations which could streamline operations and reduce the need for manual processing.

TxDOT is interested in all options. The only restriction is all invoices must be paid by TxDOT.

6. Question: Is TxDOT looking for a SaaS solution only, or would other hosting solutions be considered?

TxDOT is looking for information for any and all solutions

7. Question: Does TxDOT have any plans to use RPA, or have RPA already in place?

What is RPA? Please describe this process and use