Addendum_1.pdf

City of Minneapolis – Procurement Office 505 Fourth Ave S, Room 310

Minneapolis, MN 55415

TEL 6 1 2 . 6 7 3 . 2 5 0 0

Addendum #1 Issued Date: July 16, 2026 Event #: 0000004102 RFP Title: Electric Vehicle Mobility Network

Change(s) to RFP

Change in Response Due Date Change in Terms and Conditions Change to Scope of Services

Responses to Questions Received Other

Please Note the Following Addition(s)/Change(s)/Clarification(s):

Change in Response Due Date:

Original Date/Time: 2:00 pm on July 29, 2026 Revised Date/Time: 12:00 pm on August 10, 2026

Please Note: In order for Procurement staff to assist you in case there is an issue with the submission of your proposal, please attempt to log in to the eSupplier portal at least two hours in advance of the 12:00 pm deadline on August 10, 2026.

If you need assistance with your eSupplier login or registration, please contact eprocurement@minneapolismn.gov

Question and Responses:

1. Question: Was the Pre-Proposal Conference recorded and if so, will it be distributed?

• Answer: Yes. The recording is linked here.

2. Question: Can it be confirmed that the ZEF-made hardware can run software platforms other than ZEFNET? What is the contingency plan if ZEFNET ceases to function?

• Answer: Confirmed, we intend to have the awarded vendor utilize their systems for the charging network, incumbent or otherwise.

mailto:eprocurement@minneapolismn.gov https://minneapolismngov-my.sharepoint.com/:v:/g/personal/max_gonzalez_minneapolismn_gov/IQCeikS6m08pR4rE1coyBvdeAe1Smra8Oc4R8l5caQ7cA_w?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZy1MaW5rIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXcifX0%3D&e=ojQiIR

3. Question: In Attachment B, can you provide additional detail on the chargers in both Minneapolis and St. Paul, such as manufacturer, common model name, kW rating, mounting hardware?

• Answer: Please see page 24 of the RFP for additional information.

4. Question: For future DCFC installations, what will the physical conditions be? For example, how much of a footprint will be available? Would you be open to distributed systems or is there a preference for an all-in-one architecture?

• Answer: We have considered (and shall continue to consider) both options for installations, as each curbside location we evaluate as a potential EV Spot Network site has differing physical conditions and special allowances.

5. Question: In Attachment C, Section 1.A, should the questions about receipt options and transaction process be moved to the software section since no hardware on the market provides a paper receipt and transactions are processed by the software?

• Answer: Answers regarding the receipt options will be accepted in either Section

1. A or Section 2.

6. Question: In Attachment C, Section 1.B., is BABA compliance required for the Level 2 units?

• Answer: There is a desire for BABA compliant equipment should future federal funding or projects be awarded or pursued by either City.

7. Question: In Attachment D, can you provide more specifications on the New Equipment items? For example, what amperage for the Level 2 stations? Are they pedestal-mounted or wall-mounted? What is the desired cable length? For the DC units, what is the desired kW rating, should it be an all-in-one unit or distributed, and is futureproofing a priority (the ability to add more power or ports later)?

• Answer: Our network utilizes pedestal-mounted charging stations as we operate in the public right of way in a curbside environment. Our current Level 2 charger inventory operates at 48 amps, on 60 amp circuits. Current cable lengths for level 2 chargers average around 20’ with 10’ tensioners. We desire a minimum kW rating of 150kWh for DCFC chargers, with an openness to consider all-in-one as well as distributed depending on location. It is important to note that we do not require all potential products to be quoted during the solicitation, e.g. if a distributed solution is the best fit for a future installation, we would be open to receiving quotes from a selected vendor regarding what solutions they have that meet specific site needs.

8. Question: Would tax returns be a sufficient substitute for audited financials?

• Answer: CPA-reviewed financial statements can be accepted if no audits were performed.

9. Question: Section 2.C mentions a strong willingness to integrate with the MPLS Parking Application (Flowbird/Arrive). Can the City provide the existing API documentation, technical schemas, and specific sandbox endpoints for the Flowbird platform so we can accurately scope the development costs for Attachment?

• Answer: We are not requiring an integration cost estimate as part of this RFP. Our app platform is currently undergoing a back-end transition so current API documentation would not reflect future integration requirements. Once the back-end migration is complete (likely after vendor selection resulting from this RFP) we can provide documentation and work with the vendor selected through this RFP to scope integration. The technical requirement reflects a willingness to assist in facilitating such an integration with a 3rd party.

10. Question: Are all 149 existing chargers currently confirmed to be unlocked and running open standard OCPP (1.6J or higher).

• Answer: The chargers are running a slightly modified protocol, per the incumbent, but can be rapidly transitioned to OCPP 1.6J if a new vendor is selected. The incumbent is fully willing to cooperate with transition if necessitated by the outcome of this RFP.

11. Question: If any firmware upgrades, controller swaps, or physical modem modifications are required to point them to a new platform, will the City treat those tasks as separate, billable civil change orders?

• Answer: We would prefer they be unified into a single change order, but the work would be billable.

12. Question: For new deployments is the selected vendor responsible for permitting, running new underground electrical conduits, and coordinating transformer drops with local electric utilities (e.g., Xcel Energy)? Or will the Cities bring the electrical service loop directly to the concrete pad foundation before the turnkey installation begins?

• Answer: The selected vendor is responsible.

13. Question: Is there any interest in curbside charging?

• Answer: Yes. Our existing network that our teams are procuring for are currently curbside only, but the City has a variety of off-street installations.

14. Question: Can you release the full list of attendees from the pre-bid meeting?

• Answer: Attendance was not officially taken, nor were names and organizations required to be provided to join the meeting.

15. Question: Confirming the awarded bidder will be responsible for on-demand installation services of future charging equipment?

• Answer: Confirmed.

16. Question: Does the City expect the successful bidder to remit taxes on behalf of the City

• Answer: At present the City of Minneapolis remits taxes, however the preference would be to move to a merchant provider model that will remit taxes on our behalf.

17. Question: Can the bidder be successful without these integrations (Flowbird and Curbside applications) today but provide proven property management system and parking system integrations with a plan to integrate into these applications if successful?

• Answer: Yes, we do not require a standing integration, but we would prefer an integration.

18. Question: When were the initial chargers installed?

• Answer: Initial chargers were installed in 2022-Present.

19. Question: What generation are the Enphase units?

• Answer: The vast majority of our Enphase chargers were manufactured in 2022.

20. Question: Are all charging hardware listed intended for public and private fleet use? Or are some of the chargers only for city fleets?

• Answer: The listed hardware is intended for public charging use, and for the Public carsharing network(EVIE) vehicles managed by Saint Paul and Minneapolis.

21. Question: What is ZEF's role moving forward? Are they willing to unlock their firmware on the chargers to allow the successful bidder to integrate?

• Answer: The selected vendor shall be responsible for managing all elements of the EV Spot Network described in the RFP. If the incumbent is not selected, their role will be to fulfill all remaining work orders and tasks under the current contract and facilitate a smooth transition to the selected vendor. For the charger transition question, please see the response to question 11.

22. Question: Do all stations need credit card readers?

• Answer: No, our carshare-specific chargers are currently activated via RFID tag and do not accept credit card payments.

23. Question: How many new L2 ports and DCFC ports are planned as part of Minneapolis and St. Paul 2026 planned installations?

• Answer: All of the new installations in 2026 are level 2.

24. Question: What is the status of construction/pre-construction for the planned 2026 installations?

• Answer: The planned 2026 installations are currently being installed and willbe completed through the current vendor prior to new vendor selection.

25. Question: How are we supposed to determine the project values of the 14 planned installations without knowing the charger quantities, kW demand, and scope at each location?

• Answer: Please see response to question 24.

26. Question: To help us better understand the scope of this opportunity, could you share some context around the decision to issue this RFP? Specifically, we'd like to understand whether this is primarily a contract renewal process or whether you are actively evaluating new vendors and solutions.

• Answer: We are actively evaluating all proposals received through this RFP with a desire to receive a variety of qualified responses to select the best possible fit for the current and future needs of the EV Spot Network. Procurement rules dictate a need to abide by existing contract limits, and the ever-evolving EV charging landscape necessitates a thorough evaluation of new solutions.

27. Question: We want to ensure our proposal accurately reflects the full scope of services expected. Please confirm whether the selected vendor will be responsible for maintenance and software services across your entire existing deployment, in addition to any new installations.

• Answer: Confirmed.

28. Question: Please confirm whether Buy America Build America (BABA) requirements will apply to all new deployments under this contract. If so, kindly provide the specific federal grant program or grant language that governs this requirement so we can ensure full compliance.

• Answer: Please refer to the response to question 6.

29. Question: As part of your broader infrastructure planning, do you have any interest in replacing or upgrading any portion of your existing charging equipment through this solicitation?

• There is a possibility to upgrade or replace, however the main area of opportunity is new locations, or maintenance related replacements.

30. Question: We would appreciate any insight into challenges or pain points you have experienced with your current deployment. Understanding these issues will help us tailor our proposal to best address your needs.

• Answer: Mitigating cut cables, spare part availability and timing for 3rd party DCFC chargers represent examples of challenges faced by the EV Spot Network to date.

31. Question: We would like to request a 2-week extension to the due date of July 29. This will help bidders with time to prepare a comprehensive proposal.

• Answer: The City will extend the due date from July 29 to Aug 10, 2026, 12:00 pm.

City of Minneapolis – Procurement Office