YZone wrote: ↑Thu Feb 11, 2021 7:50 am
We are looking for a management platform with the following capabilities:
- User access to the equipment through a NFC badge reader
- In some way the user access to the ongoing measuring program is blocked by the platform software until the user has been logged in, which means he/she has made a reservation in Booked for that period of time
- The power of the equipment can never be switched off even if no one has been logged in
- The measuring program continues even after the user has been logged out
The aim of all this is to avoid anonymous use of the equipment (a reservation in Booked is mandatory and checked by the platform prior to the logon) and the access control motivates the user to take care of the equipment.
We implemented at least parts of your requirement (perhaps generic enough to fit anyway) with a client recently, and the IoT controller plugins were put on our site.
https://apps-n-add-ons.com/product.php? ... trolPreRes (uses Check In/Out to control the IoT device - i.e., a 'push' message when triggered by the User)
https://apps-n-add-ons.com/product.php? ... StopAction (uses Start/End times to control the IoT device - i.e., a 'pull' system activated by a CRON request {must run every minute, like Booked Reminders})
For the 'User access to the equipment through a NFC badge reader', that would require some specifications for the particular hardware (likely some sort of API is available) and a bit of design to implement, though nothing 'hard' most likely.
The rest of your requirement sounds like our StartStopAction plugin above is a lot like what you are asking for. Both the plugins work the same for Booked Scheduler to IoT part - they send CMD messages to the devices which then control what is allowed at the equipment - it may be a power on/off or could be restricting access - depending on the CMD and unit software/hardware (so you have total control over what happens at the equipment side using the same interface to Booked). The difference is that one is a 'push' (when the User does CheckIn/Out) and the other is a 'pull' (triggered by a CRON job), which is more like 'blocked by the platform software until logged in - and has an active Booked reservation'.
If you would like to see more on how this works I can set up a demo or we can discuss directly about your specifications and building a custom package that suits your needs specifically.
