66-27013TS Addendum 1.pdf

Rev: 06/2021

This addendum is issued to answer questions received during the open question period.

1. General: Is UNCC evaluating solutions that replace multiple vendors with a single platform that natively delivers AI-powered visual recognition kiosks, POS, mobile ordering, suites, inventory management, omnichannel capabilities, payment agnostic flexibility, and centralized back-of-house operations?

The university is looking to use a single provider for POS, mobile ordering, suites, omnichannel capabilities, payment agnostic flexibility, and centralized back-of-house operations. The operations are currently centralized under Illumia Transact Cloud Point of Sale.

Inventory management is not currently integrated and would be a nice-to-have.

Directly integrated AI-based visual recognition is also a nice-to-have. We currently operate 2-3 other self-checkout systems, which may continue to be used or be replaced by the new solution.

2. Section 5.0-5.1, Phase 1: In lieu of the 26 tablets specified, will UNCC accept a proposal that includes either a 15-inch fixed terminal or a 6.7-inch handheld terminal device? Both solutions are designed to meet the intended operational needs and provide functionality equivalent to a tablet-based workflow.

Yes, fixed tablets can be acceptable, depending on the level of effort required to relocate them. The intended use case for this scenario is movable carts for game day or pop-up locations for campus operations. These should be movable and manageable by the cashier at the location without IT involvement.

The requirement for the handhelds is that they be actually handheld and support integrated credit card operation. The use case for these is to accept orders and payments for runners at the stadium and other athletics venues.

3. Section 5.0-5.1, Phase 1 and Phase 2: For the two kiosk locations, can you clarify whether UNCC is envisioning a traditional kiosk experience with guest-driven item selection and scanning, or an AI visual recognition solution that automates item identification and checkout?

The kiosks are intended for a traditional kiosk experience with guest-driven item selection.

4. Section 5.0-5.1, Phase 2: If Phase 2 is not expected to be installed and activated until 2028, can UNCC please clarify how bidders should address future technology considerations, solution availability, API capabilities, software platforms, and pricing? Because POS solutions, integrations, and platform capabilities may continue to evolve between now and 2028, and pricing quoted today may not remain valid for purchase orders issues two years from now, additional guidance would help provide the most accurate and beneficial proposal for UNCC’s future needs.

Vendors should price phase 2 as accurately as possible and include the stipulation that pricing of phase 2 is subject to change due to changes in market conditions, updates, new or available solutions, etc. Any change in pricing will be addressed with the university before implementation and invoicing and changes in pricing shall be subject to university approval and based on availability of approved funding.

5. Attachment C: May the bidder reference or apply existing pre-negotiated terms, in its proposal rather than accepting the RFP’s standard terms as written? Bidders may include additional T&C’s, EULA’s etc. with their proposal. Such terms added are subject to review and negotiation before being accepted. The University cannot accept additional terms as replacement for the State’s T&C’s. The State’s T&C’s will take precedence over any conflicting terms added.

REQUEST FOR PROPOSALS #66-27013TS

University of North Carolina at Charlotte Purchasing Office

Reese Building, 3rd Floor 9201 University City Boulevard

Charlotte, North Carolina 28223-0001

Addendum Issue Date: September 18, 2026 Due Date: Friday, October 2, 2026 at 2:00 PM ET Purchasing Agent: Trever Swint Stadium and Campus POS System

ADDENDUM # 1

If there are state terms unacceptable to the vendor, it is highly suggested to submit redlines with their proposal for consideration.

6. Section 5.1 General: The scope of work for Phase 1 includes the requirement of 26 tablets and 15 handhelds. How do you differentiate between the two form factors? Is there a certain screen size or specific dimension limits for each?

Tablets are intended to be fully functional registers set up for the day and reasonably easily movable after event completion.

Handhelds must be actually handheld and support integrated credit card operation. The use case for these is to accept orders and payments for runners at the stadium and other athletics venues.

7. Attachment J, Req. ID 49, 50, and 51: What necessitates BlueFin, Freedom Pay, Windcave, and/or Touchnet as payment gateway? Are there specific requirements attached to these providers? Is it for P2PE? System must use FiServ as processor but also lists payment gateways for online payments and in-person payments. If processing directly through FiServ, is one of the payment gateways still needed?

Physical terminals must be P2PE compliant. Mobile ordering/Online payments need to be processed through one of the listed payment gateways.

The attachments list all current payment gateways and settlement providers approved by the university.

Also note the requirement to support multiple merchants of record. Currently, all transactions are processed through FreedomPay with Chartwells and multiple departments managing their own credit card terminals and provisioning. In the past, we have also used Windcave.

[NR] . For additional background, while Fiserv is our acquiring bank, a payment gateway is still needed to direct the payment information from the POS terminal or website to Fiserv for approval and funding.

8. Attachment J, Req. ID 16: Can you provide clarification on how you see the customer facing food wait times being utilized? Is this to present when the order will be ready or provide a next available time for “ASAP” orders?

The intent is to present when the order will be ready. Currently, all orders are submitted as asap orders.

Food wait times should be available on the kiosks, in mobile ordering, and via a webpage or order display boards located across campus. The data must display the total wait times for each location, including all order channels.

9. Attachment J, Req ID 102: How do you envision tracking missing or incorrect items for suite orders? Would this be marking the items as missing or incorrect and then requisitioning replacement items or simply noting they were missed?

The list of items purchased in the package is sufficient for this purpose. Being able to check these items off would be helpful, but not required.

10. Attachment J, Req. ID 104: Are you looking for an approval process to be digitized through the system or simply to present the authorized representative’s name for staff to verify?

We will simply use the authorized representative’s name for staff to verify

11. Attachment J, Req. IS 108: Would you like for game-day additions to be notated differently from the final invoice/order?

yes

12. Section 5.1 General - For the stadium, what are the use cases for the 26 tablets and 15 handhelds? For the tablets, do you want an 8” device and the handheld is a 6”/smaller form factor?

Tablets are intended to be fully functional registers set up for the day and reasonably easily movable after event completion.

Handhelds must be actually handheld and support integrated credit card operation. The use case for these is to accept orders and payments for runners at the stadium and other athletics venues.

Yes, handhelds should be ~6” form factor.

Tablets should be in the 8-12” range.

13. Section 5.1 General - Are the 10 Mobile ordering sites for suites or is this for various concession stands/pickup locations?

Yes, for the stadium, mobile ordering is planned for the suites only. For the rest of campus, most locations will also have mobile ordering.

14. Attachment J-Req ID 21 - Can additional details be provided on the Paciolan integration? Is Paciolan used for loaded tickets (with stored value) at the stadium?

The envisioned use case is generally a ‘food/drink package add-on’ sold through Paciolan, and then being able to redeem that package on game day. Package details will vary, whether a set number of drinks, snacks, etc, but the ticket barcode scanned at the register needs to trigger that validation/confirmation somehow.

15. What does each value “M, S, C” stand for on ATTACHMENT J -Requirements & Vendor Self-Assessment? M –

Mandatory, S – Should Have, C – Could Have

16. Attachment J-Req ID 94 - Can details be provided on how the anticipated guest count will be used? Is this to provide order recommendations or for the Chartwell’s team?

Yes, both the number of attendees needs to be collected to adjust the food quantity, and any food allergies need to be collected for any menu adjustments.

17. Attachment J-Req ID 7 -What OS is on the following hardware: Touch Dynamics and NCR CX7 Hardware? What is the specific model of the Touch Dynamics Kiosk?

Windows-based, Touch Dynamic Edge Ultra

18. Attachement J-Req ID 37: What type of features are UNC looking for in a loyalty program? Is this for the campus and stadium?

The loyalty program is currently used only for campus operations, but it would be nice to have it for stadium concessions as well. Current usage includes punch cards (free X after X purchases), points rewards (for multiple app interactions, purchases, special events, etc), and points redemptions for multiple prizes, discounts, or app credit.

19. Section 5.1 General - For the stadium, are the provided hardware counts everything needed or are there additional terminal/register needs?

Phase 1 lists the requirements for the expansion. Phase 2 includes the current stadium and campus registers for replacement. There will likely be ongoing additions for various new locations, so future and final numbers may increase.

20. Section 5.1- Campus dining- Will all 49 profit centers be required to accept any form of loyalty, gift cards, declining balance, vouchers, etc. If so, how many of these locations.

All campus locations must have the ability to accept campus card and meal plan transactions as well as cash and credit card. Stadium locations do not need to accept meal plan transactions. Handhelds do not need to accept meal plans or campus card transactions.

21. Section 5.1 General - For Campus dining, can you advise how many locations have digital menu boards?

There are 84 wand display boards across the ~25 locations

22. Section 5.1 General - For campus dining, can you advise on how many locations have KDS? Do all 25 mobile ordering locations have existing KDS?

10 Locations

23. Section 5.1 General - For campus dining, can you advise if any other peripherals are needed. Cashdrawers, scanners, etc. Can you also advise on the age of the existing hardware below?

a. 5 M3W2 Partner Tech Tablets

b. 21 Touch Dynamics Edge Ultra Kiosks

c. 5 NCR CX7 Registers

d. 54 NCR XR5 Registers

e. 67 HP Engage One Pro 1 Register

Cash drawers are required; Some locations will require a scanner.

No patron displays or scales are expected, but the system should be capable of using them.

The NCR CX7 and Touch Dynamics Edge Ultra Kiosks were deployed in Fall 2025. All other hardware can be considered end-of-life.

A SIGNED COPY OF THIS ADDENDUM MUST BE INCLUDED WITH YOUR PROPOSAL

COMPANY NAME DATE

PRINTED NAME SIGNATURE