Kennesaw State University initially issued physical cards to its students and staff. Aside from identification, these cards also permitted access to various facilities and use of meal plans.
Effective Spring 2024, Kennesaw State University began to provision prototype MobileID cards that were to be available via mobile devices. As a student assistant of Talon One, we were responsible for the operation of Card Management as one of its many services. Once fully integrated, this new digital ID system would be added to our other card management duties. When I was informed that I had been provided an invitation to participate in the pilot group to assist with troubleshooting the Mobile Talon Card during it's Beta Testing period, I knew it was an offer I couldn't pass up.
As an approved participant for the Pilot Group, I was assigned to test the user interface of the Mobile Card and report any issues regarding access compatibility. Over the next two weeks for the Testing Period, I would receive various task to test and operate as I provide feedback with my experience.
The first taskset pertained to accessing Administrative offices
The second taskset added functionality to accessing meal plan transactions, printing services, the Rec Center facility, Residential dorms, and lastly event check-ins
The third taskset pertained to adding accessibility to classrooms within the University's Colleges for each major on the Kennesaw Campus
The final taskset pertained to adding accessibility to Athletic facilities, off-campus facilities, and the remaining buildings on the Marietta Campus that weren't previously encoded
Following the conclusion of the beta test, Kennesaw State University officially began the widespread provision of Mobile Talon cards for all current students and staff. Among other Talon One student assistants, we became the primary line in assisting students and faculty that encountered any compatibility issues, to devise and troubleshoot solutions.
While I didn't get to directly contribute to the application development, I primarily oversaw card encoding and make sure the mobile cards were assigned to the devices of participants within the Pilot Group. I gained a lot of firsthand experience and field training for Beta Testing by my participation in the Pilot Group; through this process I got to understand a lot of the intricacies that come with software and hardware requirements to allow for the provision of Mobile Credentials. Aside from testing the mobile card's functionality at various locations, I also did a lot of research into device specifications to make review compatibility. The compatibility required the device to (1) allow for Near Field Communication (NFC) protocols, (2) be fully updated on software OS, and (3) be a device acquired within the United States.
Similar to the physical cards, the mobile cards have security clearance specific to the student it was assigned, students/faculty must recharge their card through a hotspot every 7 days (every 24 hours for those with high security clearance), failure to update the device will render it inactive for access until it is updated. Below are some additional troubleshooting issues we devised solutions to.
"This ID exists on another device. Please remove the ID and try again or contact Card Office for support"
The user agreement allows a mobile credential to be active on only one device at a time. It must be removed from the previous device before it can be added to a new one, as it does not transfer automatically. If the user still has access to their old device, they should remove the card from there. Otherwise, they will need to contact the Card Services office for assistance.
"Image not found"
The student has not yet submitted a photo, which is required to set up their ID. They can either upload a photo through the online submission portal and wait for approval, or visit the office to have their photo taken. Once a photo is assigned to their profile, they will be able to proceed with the Mobile ID setup.
Locked Icon
Any client that sees a lock icon when trying to setup the mobile card is likely not an active student/staff and would not be eligible for the Mobile ID card. Status can be confirmed by referencing the TransAct system to review if they are currently active.
Device is not functioning effectively for Door Access
The issue is likely due to user error or the registration steps not being followed correctly. To complete the mobile card setup, the student must:
1) Download the app and log in
2) Register the card to their device’s digital wallet.
3) Activate the card by updating it to a hotspot connection.
Door Access periods are valid for 7 days. If the mobile key has expired, the user will need to update it to regain access.
Door access is identical for both mobile and physical cards. If a mobile card does not function at a specific door, switching to a physical card will not resolve the issue, as the access permissions are the same.
Other Card Access Services
Services like door and meal plan access are available immediately upon activation. Printing access requires a minimum of 24 hours after setup before becoming available.
Clients who transition from a physical card to a mobile card will retain access to both IDs for a temporary period of 7-14 days. After that, the physical card will be automatically deactivated unless the mobile card has been removed. An email notification is sent to each student or staff member at the time of activation. For security reasons, only one active ID is permitted at a time to prevent unauthorized use.
Incompatible Devices
For devices found to be incompatible—either due to issues with the NFC chip or because they were acquired from a foreign market—we issue the student a physical card and log the device as incompatible. We review the device specifications using the GSM Arena website to verify compatibility.