amenity
commented
5 years ago Teri, John, Joseph, Jacob, Ryan, Peggy, Amenity
Passport is current pay-to-park provider, but contract is up in December. We will need to go back out for an RFP; there are several providers that can provide services. We want them all to do at zero cost to City.
Online payment options
City payment --- Chase Connexion
- Fees: 2.5%+ $.30
- Estimate 3 months for implementation
- Probably would always have to have Controller's office as part of solution
- Not WCAG compliant
- Contract up at the end of this calendar year...
Stripe
- Ready to go out of the box with Knack; extremely low level of effort
- Fees: 2.9% + $.30 charge
- American Express, Visa, Discover
- Cannot accept e-checks ... (probably not a bad thing after discussion with Controller's office; lots of headaches with them)
- Don't have additional contract reqs over the current Knack agreement
- Will have to go through the CISO for security approval
ParkATX (RFP in the fall, so might be another mobile platform payment processer solution)
- AMANDA wasn't able to tie in ...but that's not saying much
- Fees: Uses "wallet" where customers pay in $10 increments, so fees are fewer and less visible (Is this part of their permit solution or just their parking meter solution?)
- Most applications we would choose would be able to integrate with their payments
- Won't have this in place until at least September — but that's okay; we have back office solutions and it's worth the wait
Knack vs. vendor solution
Permitting is always idiosyncratic, ootb solution is never perfect
- How much would we have to pay vendor to customize?
- Knack protects us from being constrained by vendor capabilities for the lifetime of the product - value in "I don't have to wait two years for third party to build in new functionality"
- This first app in Knack will take a little time; but the second app would go faster; Teri: Knack is a different kind of product --- easy to learn, can always hire or contract out work
New mobility platform
Features & requirements
- "Mobile pay" - Pay by phone/app (JC: would this be necessary for chauffer? Joseph: Could be)
- Mapping - shows where permits are active, allows users to verify address
- Translation (Spanish)
- Data portability
- Extensibility - Needs to be able to tie into platforms for data analysis, other solutions
- Enforcement (could have) - citation revenue, location of citations, license plate reader
- Current Tylertech contract is held by APD; we have to use what they use bc they do citations as well
- ATD's Brazos units aren't capable of checking for ParkATX; if we switched to Android they could...but they're tied to Tylertech
RFP
- Split RFP into sections to encourage integration: Give everyone a list of all the applications we need solutions for, let companies bid on as many as would they want --- possibly all of them...We could accept multiple vendors.
- Note: We really don't know what the requirements are for these other solutions, haven't done user research —but we can see how mature their solutions are.
- Could make it a requirement to add in to Knack so we always have a back up solution
- How long will RFP take? One month to write, one month out, one month for evaluation, + time for contracting and council approval...
Future ATD permitting and online payment needs
ParkATX brand will eventually cover:
- Rides for hire
- Chauffer permitting
- Valet
- Pedicab
- Trade permitting
- Validation of parking
- Possibly ROW for valets in the future; (right now handled by AMANDA)
Objective Discuss Transportation’s direction for ParkATX as well as online payments for RPP?
Participants Teri, John, Joseph, Jacob, Ryan, Peggy, Amenity