We are developing an open source federatable management system for FabLabs, Makerspaces and Hackerspaces. FabAccess aims to manage access to machines in order to avoid accidents. FabAccess has three main functionalities: - Machine management - Authorization system - User management
We want to combine Neil Gershenfeld's idea of users learning to operate machines independently with the requirements of open workshops that users do not injure themselves in the process. Thus, users need instruction for dangerous machines, and this principle is then reflected in the authorization system.
The principle of FabAcces is to switch machines on and off via the power connection or via internal firmware. This way, machines are normally de-energized and therefore harmless. Only when users are at the machine who are competent and instructed for safe operation, the machine gets connected to the power supply by FabAccess.
The management of machines that require cleaning after use is supported, either. This ensures the usability of machines for the next user and reduces wear and tear.
We also support the reservation of machines, but we do not want to take over scheduling for the users. Therefore, as a compromise we implement that users can reserve machine only for half an hour (as a modifiable parameter). So they don't have to worry about someone else using the machine while they commute to the FabLab.
The authorization system makes it possible to allow access to machines only for certain users. Thus, it can be used to map instructions for dangerous machines, but more complex mappings are possible due to the high configurability of the RBAC system (role-based access system).
It is also possible to map simple machines that do not require instruction but need to be used in a somehow structured way (workplaces, tools, lockers, ..).
The user administration should make it possible not to lose track of the users in the space. FabAccess is intended to be used as a SmartCard system, so each user receives an NXP Mifare DESFire (FabCard) card to authenticate himself at the machine.
In order to reduce the administrative effort, users can register on their own and can then be activated after the operator has checked their data. The user contract is mapped in the process and may be integrated into other systems.
Speakers: Tasso Mulzer