Departmental Services

Validation code - SET UP INSTRUCTIONS
Produce a number of codes, each with a certain time value, and expiration. Example - buy 10 codes designated for 2 hours of time each, upon use equals 20 hours of metered parking time. Administrative person can buy codes and distribute to staff as needed. User parks at meter and enters zone, code and license plate number. User can choose amount of time up to the max value of time purchased for each code. User is notified via app when time is about to run out and can continue to add time (up to total time purchased or limit designated for the code). *Note - there is a “buy-in” to start up a “vendor account.” The T-Card holder opens an account and purchases a base funding prior to codes being generated. This diminishing balance must be refunded as necessary.
Pros
Works at any meter (UI, Champaign, Urbana)

• Administrative person can purchase and distribute codes
• User does not have to manage/purchase codes, single use code provided
• Reporting available on where codes used
• Codes/parking time available until used - example: if all parking time used, can buy more time to continue to use codes; if all codes used, can re-fund the balance to provide funds for outstanding, unexpired codes.

Cons

• User must keep track of codes for use
• App (smartphone) preferred for validation code usage
• Can use codes remotely via app on a PC if necessary
• Does not support voice call

Wallet - SET UP INSTRUCTIONS
User funds time on a ‘wallet’ using their or administrative person’s tcard. To use meters in each entity, a separate wallet is required for each of the three entities (UI, Champaign, Urbana). User can monitor ‘declining balance’ for each entity and add more value when needed. When parking, user enters zone, which will bring up the appropriate wallet and time to start. User is notified via app when time is about to run out and can continue to add time up to value in applicable wallet.
Pros

• User does not have to keep track of codes, only time left in ‘wallet’.
• User can see time left in ‘wallet’ at any time.
• Most similar option to outgoing meter keys.
• Reporting available on where time used.

Cons

• Wallet value is available only to user on the individual account linked to the purchased time (unlike meter key that is easily transferable).
• App (smartphone) preferred for use (some testing in progress for voice call usage).
• If not T-Card holder, Wallet must be funded by 3rd party(the T-Card holder) at both party’s convenience
• Must purchase time at each parking entity, not transferable
   

Credit card
User enters/stores personal credit card for use when parking. Credit card is charged each time used. When parking, user enters zone and authorizes credit card usage. Reporting available for user to submit for reimbursement monthly. This option will not be authorized for a Tcard to be stored/used due to: 1) tcard cannot be stored; and 2) tcard reconciliation on multiple small dollar purchases causes too much administrative work and expense to the University.
Pros

• User can use the same method to pay for parking for personal or business use without keeping these two separate, but can then get reimbursed for all business use using reporting available.
• Time is purchased/used on demand, rather than dealing with validation codes or storing funds/paying for parking in advance of use. User does not have concern of when/if value is used up.
   

Cons

• User tracking and administrative work for reimbursement of business parking.