Telecom Line Audit and Optimization Assessment

Post Information
Posted At:
Mon, Jun 29, 2026 1:09 PM
Sealed Bid Process:
Yes (Bids Sealed / Pricing Sealed)
Private Bid:
No

1. Introduction
   1.1. Summary

This Request for Information (RFI) is issued as a means of discovery and information gathering for an opportunity to explore offerings in the marketplace that could potentially assist the City of Phoenix (City) Information Technology Services in reducing costs and optimizing expenses through the review of the City's legacy telecommunications services.

The RFI is for planning purposes only and should not be construed as a solicitation nor should it be construed as an obligation on the part of the City to make any purchases.

This RFI should not be construed as a means to pre-qualify vendors.

This is not a formal solicitation, but a request for interested parties to provide information as specified herein.

Participation in this RFI is voluntary.

No purchases will be made as a result of this request. Any price information provided shall be used for general comparison purposes only. Do not include applicable state and local taxes.

OBTAINING A COPY OF THE RFI AND ADDENDA

Interested parties may download the complete RFI and addenda from https://procurement.opengov.com/portal/phoenix. Internet access is available at all public libraries.

1.2. Background

The City of Phoenix Information Technology Services has over 460 facilities over 520 square miles. The city has an inventory of almost 2000 legacy services that require review and disposition.

1.3. Contact Information
Rosanne Emerick
Procurement Officer
251 W. Washington Street
8th Floor
Phoenix, AZ 85003
Email: rosanne.emerick@phoenix.gov
Phone: (602) 262-1659

Department:
Finance Central Procurement

1.4. Timeline

All times are Local Arizona Time

City reserves the right to change dates and/or locations as necessary. All times are local Phoenix time.

RFI Posted::
June 29, 2026
RFI Inquires Due Date::
July 17, 2026, 2:00pm
RFI Submittal Due Date::
August 7, 2026, 2:00pm
RFI Electronic Submittal: Procurement@phoenix.gov
2. Scope of Work
2.1. General Overview

The City of Phoenix (City) desires to understand the costs associated with legacy telecom line audits and if vendors offer this service on a contingency basis or performance-based pricing. In other words, the vendor's compensation is contingent upon the savings achieved from the audit.

2.2. Scope of Information Requested

Audit information requested shall cover all legacy telecom lines, including but not limited to POTS, ISDN, analog private line, and T1 lines, throughout the city. Information provided by the vendor shall document how the current state of these lines could be provided, identifying any discrepancies, and providing recommendations for disposition.

Audit process expectations the City may seek include:

Review the City’s internal and carrier telecommunications inventories
Document current state
Create inventory database
Categorization of services
Identify discrepancies
Analyze services
Interview departments to determine need
Conduct site visits to assess the utilization of services.
Provide recommendations for optimization
Identify unused or redundant lines
Suggest other cost-cutting methods.
2.3. Technical Requirements

The Contractor shall:

Describe the methodology used to conduct telecom line audits, including any specific methodologies or frameworks used.
Explain the tools and technologies used during the audit process.
Describe the data security measures taken to ensure data security and confidentiality.
2.4. Contractor Profile

The Contractor shall provide:

The Company Profile - a brief description of your company, including its history, size, and areas of expertise.
Experience and Qualifications - experience with similar projects, including any relevant case studies or references.
2.5. Contractor Questions

(Also included as PDF in Section 5. Vendor Questionnaire)

The Contractor may provide answers to questions which may include, but are not limited to:

Inventory Accuracy
Describe your methodology for establishing an accurate and complete inventory of all telecom lines, circuits, and services across multiple carriers and locations.
Billing Reconciliation
Explain how your team identifies unused, obsolete, duplicate, or incorrectly billed telecom lines.
Describe your approach to reconciling telecom billing records, circuit IDs, service addresses, and carrier terminology to create a clean, unified dataset.
Explain your process for identifying billing errors, contract misalignments, zero‑use lines, and other cost‑recovery opportunities.
Describe your experience working with multiple telecom carriers and managing fragmented telecom account structures.
Legacy Line Rationalization
Outline your process for validating the operational status of lines and determining which can be safely disconnected without impacting business operations.
Partnership
Explain what level of access, data, or coordination you require from the client to complete a telecom audit effectively.
Describe the tools, systems, or analytics platforms you use to support telecom audits and ongoing optimization.
Describe your ability to provide a repeatable or ongoing process for telecom cost management beyond the initial audit.                           
Shared-Savings Verification
Outline how you determine and quantify savings associated with disconnects, optimizations, and corrections.
Explain how you validate and confirm that disconnect‑related savings appear accurately on subsequent billing statements.
Explain how your organization manages and reports on a shared‑savings model, including transparency, auditability, and calculation methods.
Industry Experience
Provide an overview of your team’s expertise in identifying and rationalizing legacy services such as POTS, PRI, copper lines, or outdated technologies.
Describe your recommended project timeline, milestones, and deliverables for a full telecom line audit.
2.6. Cost and Pricing

The Contractor shall provide:

Pricing Structure - Outline your pricing model.
Describe areas for cost savings, bundles, or any pricing programs offered.
3. Submittal Requirements

An electronic PDF copy of the material shall be submitted following the outline provided herein. The Contractor Questions (PDF located in Section 5. Vendor Questionnaire) shall be answered in no more than one-hundred (100) pages, double sided plus a one-page cover letter. Pages that have photos, charts and graphs will count towards the maximum number of pages. Sales material can be submitted and shall not count towards the one-hundred (100) page count.

The submittal shall include:

A one-page cover letter prepared on the company’s letterhead and signed by an authorized employee of the company Provide primary contact information and contact person’s telephone number, e-mail address, and company webpage. A brief summary shall be included in the cover letter that provides information on the company’s background and expertise as relates to this RFI. (This sheet will not be included in the page count.)
Each response should clearly mark which contractor question from Section 5. Vendor Questionnaire, 2. Contractor Questions are addressed with the solution being proposed. Solutions can be proposed for one or more problem statements. Vendors do not have to propose solutions to all problem statements.
4. Instructions to Vendor
4.1. PREPARATION OF RESPONSE

It is the responsibility of all vendors to examine the entire RFI and seek clarification of any requirement that may not be clear and to check all responses for accuracy before submitting a response.

The City does not reimburse the cost of developing, presenting or providing any response to this RFI. Responses submitted for consideration should be prepared simply and economically, providing adequate information in a straightforward and concise manner. The vendor is responsible for all costs incurred in responding to this RFI. All materials and documents submitted in response to this RFI become the property of the City and will not be returned.
4.2. SUBMISSION OF INFORMATION

Responses must be in possession of the Department on or prior to the exact time and date indicated in the Schedule of Events. Late submittals may not be considered. The prevailing clock will be the City Department’s clock.

Offers should be submitted electronically via the City’s e-Procurement Portal by clicking on “Draft Response” via https://procurement.opengov.com/portal/phoenix/projects/268525. Offerors that are unable to submit electronically should contact the Procurement Officer to discuss the logistics of hard copy submittals. Offerors must be registered with OpenGov by signing up via https://procurement.opengov.com/signup. Vendor training guides can be found at: https://opengov.my.site.com/support/s/article/ca6d1285-1e48-4a21-bb0d-715edb7794ed

It is the responsibility of the Offeror to ensure that the Offer is timely and to confirm that there are no technical reasons that any Offer submitted electronically may be delayed. The date and time on the upload as received/stamped by the City’s e-Procurement Portal will provide proof of submission and verification whether the Response was received on or prior to the exact time and date indicated in the Schedule of Events.

Please DO NOT submit links to Google Docs, Dropbox Paper, or similar services. Your offer may be deemed non-responsive if your offer is supplied utilizing these services.

4.3. WITHDRAWAL OF SUBMITTAL

At any time prior to the solicitation due date and time, an Offeror (or designated representative) may withdraw the Offer by clicking “Unsubmit Response” on the Offer submission via the City’s e-Procurement Portal.

4.4. INQUIRIES

All questions that arise relating to this solicitation should be directed via City’s OpenGov e-Procurement Portal and must be received by the due date indicated in the Schedule of Events. The City will not consider questions received after the deadline. All questions concerning or issues related to this solicitation must be presented in writing.

The Procurement Officer will answer written inquiries in an addendum and publish any addenda on the City’s OpenGov e-Procurement Portal.

4.5. PUBLIC RECORD

All submittals in response to this RFI shall become the property of the City and become a matter of public record available for review pursuant to Arizona State law.

If a vendor believes that a specific section of its response is confidential, the vendor shall isolate the pages marked confidential in a specific and clearly labeled section of its response. The vendor shall include a written statement as to the basis for considering the marked pages confidential including the specific harm or prejudice if disclosed and the Procurement Officer will review and make a determination.

4.6. DEMONSTRATIONS
Vendors may be invited to construct a hands-on demonstration or presentation of their solution at the City of Phoenix.
The City does not reimburse the cost of developing, presenting, or demonstrating a solution, and the vendor is responsible for all costs incurred.
5. Vendor Questionnaire

1. One-Page Cover Letter - Contractor Summary*

Upload per submittal requirements.

Response required
2. Contractor Responses to Question Statements

Please download the list document below, complete responses, and upload.

  Contractor_Questions.pdf
*Response required
6. Attachments
No attachments were included

Attached documents:
• Telecom_Line_Audit_and_Optimization_Assessment.pdf