My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CENTAMAN, INC.
Clerk
>
Contracts / Agreements
>
C
>
CENTAMAN, INC.
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/3/2024 9:46:19 AM
Creation date
11/7/2022 3:37:37 PM
Metadata
Fields
Template:
Contracts
Company Name
CENTAMAN, INC.
Contract #
A-2022-216
Agency
Parks, Recreation, & Community Services
Council Approval Date
11/1/2022
Expiration Date
10/31/2030
Notes
For Insurance Exp. Date see Notice of Compliance
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
78
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
The Zoo would also like to have the option for on -site kiosk for self -purchase. <br />The ticketing system capabilities should include, but not be limited to, all of the following. <br />1. Allow the setup of daily, timed ticketing events (e.g., Saturday, August 1, 10-11 am). <br />2. Allow the ability to limit the total number of tickets that can be sold for any one-time slot (e.g., 150 guests <br />total for the Saturday, August 1, 10-1 l :00 am timeslot). <br />3. Allow set up of single date events, as well as multiple date events, and event series. <br />4. Ability to identify blackout dates. <br />5. Limit the number of tickets any guest can buy for one day. <br />6. Allow for different ticket categories such as general admission, children, children age two and under, <br />seniors, members, etc., and establish separate pricing for each. <br />7. Ability to define eligibility requirements for any category of ticket buyer. <br />8. Ability to set future release dates for tickets as well as end dates/times for the ticket purchase. <br />9. Allow for promotional or coupon codes. <br />10. Allows customers to make purchases without creating an account. <br />11. Ability to track the zip code of the ticket purchaser. <br />12. Ability to restrict users from multiple registrations for multiple dates of the same event or within the same <br />series. For example, if someone purchases a Resident Day ticket on August 2, they cannot buy another <br />Resident day ticket for another August date. <br />13. Allow ticketing confirmation via email and/or texts. <br />14. Ability to send email and text reminders prior to their ticket date. <br />15. Support the use of bar coding or QR coding on mobile devices to allow customers to scan their tickets on - <br />site. <br />16. Ability to support waitlist features for any given date and timeslot. <br />17. Ability to easily convert waitlist registrants into ticketholders. <br />18. Support text notifications on waitlists. <br />19. Compatibility across common mobile devices. <br />20. Allow flexibility in customizing tickets, including logos, ticket date and times, fine print, and other <br />information. <br />21. Ability to create and print customer tickets of customizable size that could be printed on hard card stock if <br />desired vs. standard 8 %z by 11" paper size. <br />22. Ability to provide an itinerary or detailed receipt via email or hard copy. <br />23. Ability to integrate with the Alvarado EDS Waist High Series turnstile system <br />(https://www.alvaradomfg.com/t)roductsn so that when a customer scans their ticket the turnstile opens and <br />allows them access. <br />24. Allow items to be added on to the ticket purchase such as stroller/wheelchair/scooter rentals or ride tickets. <br />recognizing that revenue would need to be split between the two entities (i.e., City of Santa Ana and <br />FOSAZ). <br />City of Santa Ana RFP 22-008 <br />Page 13 <br />
The URL can be used to link to this page
Your browser does not support the video tag.