The Campuscard System Dr. Tamas Molnar Humboldt- Universität zu Berlin Berlin, Germany 1
An alliance of universities 2
Overview • Mifare DESfire EV1 cards • Electronic Student IDs • 25 mm TRW strip Phase 1a • 2015 Photo and barcode for library use • Integrated electronic IDs for university libraries Phase 1b 2016 • Electronic employee IDs • Electronic visitor IDs Phase 2 2017 • Integrated electronic ticket for public transport Phase 3 2018 3
Problem – The card issuing process • Requires a high number of employees Personally • Multiple different processes • Requires much office space • Expensive • Outsourcing is problematic because of privacy laws Dispatch • In-house production requires machinery • Multiple different processes 4
Our innovation – The print terminal Automated card issuing Integrated photo station Integrated card printing 5
The process Card - received Card - validated QR-code – received Through the terminal Through TRW kiosk (electronic or postal (20 terminals in delivery) (30 kiosks in Berlin) Berlin) 6
The user interface 7
Some impressions 8
The system components Mifare DESfire EV1 4K 70pF cards • Blank with the university layout and deployed cafeteria application Card print terminals • Self service terminals with integrated photo station and card printer TRW-kiosks • Self service kiosks with integrated TRW-printer Card management Software and WebGUI • Universal solution for different data sources 9
The Campuscard alliance 10
Structure of the Campuscard alliance • Design of the cards • Design of the terminals, kiosks and WebGUIs Individual • Support for specific university services solutions Common • Identical technological groundwork components and • Identical system infrastructure • Identical card structure compatibility • Procurement • Application compatibility Joint coordination • Campuscard Service Centre • Steering Committee 11
The card management Data Source – Student Administration System Card Management Card Management System System Card Validation Card Printing (Kiosk) (Terminal) 12
What is inside? HIS- SOS Tomcat based Data SAP- transformation PostGreSQL CM Data Source Talend Open Studio KMS 2 13
The KMS 2 KMS Database WebGUI for Admins KMS 2 Core KMS WebGUI WebGUI for Students (in Development) KMS Auth with Sibboleth 14
Interfaces KMS 2 <?xml version="1.0" encoding="UTF- • RESTful 8"?> • XML or JSON <CardInfo> <sys>sys</sys> <externid>8555236</externid> <photoflag>true</photoflag> <cardid>0F000F000F000F</cardid> Machines <csid>0123456789012345678901234</ (Terminals csid> and Kiosks) </CardInfo> • RESTful • XML or JSON 15
KMS Database 16
Database structure PersonInfo CardInfo TicketInfo Feature(N) UniLog 17
The future Integration of CampusCard – the electronic Integration of electronic CampusCard – library ID with CampusCard – the electronic multifunctional Visitor Card compatibility alumnicard ticket employee Card across the alliance 18
Thank you 19
Recommend
More recommend