Booking, lab admin & equipment service
From BioImagingUKWiki
| Line 28: | Line 28: | ||
(Philippe Laissue, University of Essex) | (Philippe Laissue, University of Essex) | ||
| - | [http://www.google.com/calendar/ | + | [http://www.google.com/calendar/ google calendar] |
Pros: Free, easy to set up, hosted externally. Ties in with other Google applications (I set up a Google training site with calendar and Google Docs, forms & code tied in, which can all be easily changed/adapted). Charging is not automated, but can be exported to Excel using Gcal2Excel app. | Pros: Free, easy to set up, hosted externally. Ties in with other Google applications (I set up a Google training site with calendar and Google Docs, forms & code tied in, which can all be easily changed/adapted). Charging is not automated, but can be exported to Excel using Gcal2Excel app. | ||
| Line 36: | Line 36: | ||
====Bumblebee==== | ====Bumblebee==== | ||
| - | [http://bumblebeeman.sourceforge.net/ | + | [http://bumblebeeman.sourceforge.net/ bumblebee] |
The right versions of MySQL, Apache httpd, and PHP need to be pre-installed. | The right versions of MySQL, Apache httpd, and PHP need to be pre-installed. | ||
| Line 46: | Line 46: | ||
(Kurt Anderson, Beatson Institute, Glasgow) | (Kurt Anderson, Beatson Institute, Glasgow) | ||
| - | [http://www.scionics.de/ | + | [http://www.scionics.de/ scionics] |
Pros: Categorised users, facility staff can also be booked. Access granted only after training on an instrument has been completed, using Active Directory for log-ins. Cancellations can only be done 24h before (such ‘last minute’ cancellations often get picked up by others in busy facilities). Can be cancelled retroactively only by Administrator. | Pros: Categorised users, facility staff can also be booked. Access granted only after training on an instrument has been completed, using Active Directory for log-ins. Cancellations can only be done 24h before (such ‘last minute’ cancellations often get picked up by others in busy facilities). Can be cancelled retroactively only by Administrator. | ||
| Line 55: | Line 55: | ||
(Alex Ball, Natural History Museum) | (Alex Ball, Natural History Museum) | ||
| - | [http://www.brownbearsw.com/calcium/ | + | [http://www.brownbearsw.com/calcium/ calcium] |
~1.4k for 25 licenses. It allows data protection as the instrument appears as booked, but it does not reveal by whom. | ~1.4k for 25 licenses. It allows data protection as the instrument appears as booked, but it does not reveal by whom. | ||
| Line 62: | Line 62: | ||
(Colin Gray, University of Sheffield) | (Colin Gray, University of Sheffield) | ||
| - | [http://www.stratocore/ppms | + | [http://www.stratocore.com/ppms ppms] |
Pros: Web based hosted externally (no set-up on internal server required). Fully featured with, individual logins, user rights can be assigned after training, pre-session cancellation time can be set (and allow full or partial charging), different charging rates for different systems, times of day and/or user/project. Project function allows multi-role (e.g. technical) staff to book individual sessions under appropriate account. Long sessions (eg time-lapse) can be discounted after a set time. Special microscope conditions can be requested with the booking. Users can log problems which admins validate to allow warnings of limited/no service status. Full usage and downtime stats. Supports active directory/LDAP and can log actual use on instrument. Charging invoice can be produced automatically, very useful when a grant audit is ordered. | Pros: Web based hosted externally (no set-up on internal server required). Fully featured with, individual logins, user rights can be assigned after training, pre-session cancellation time can be set (and allow full or partial charging), different charging rates for different systems, times of day and/or user/project. Project function allows multi-role (e.g. technical) staff to book individual sessions under appropriate account. Long sessions (eg time-lapse) can be discounted after a set time. Special microscope conditions can be requested with the booking. Users can log problems which admins validate to allow warnings of limited/no service status. Full usage and downtime stats. Supports active directory/LDAP and can log actual use on instrument. Charging invoice can be produced automatically, very useful when a grant audit is ordered. | ||
Cons: Commercial. | Cons: Commercial. | ||
Revision as of 10:05, 20 June 2012
Chair: Philippe Laissue (University of Essex)
Contents |
Background
We had a look at different strategies and options for booking instruments and charging users. There are different solutions, from low-key to advanced. The best solution depends on
• number of users and instruments
• IT support for setting up internal server-based solutions and creating workgroups etc.
• financial support for purchasing commercial solutions
• policies of University/Department/Museum (e.g. for data protection)
As facilities vary considerably in their provision of instruments and technical solutions, any solution should be customisable.
Most solutions have the problem that they do not log the actual use on the instrument, but the hours booked on the calendar.
Swipe card/code-protected access does not prevent ‘rogue’ use of instruments. If users really want to break something, they can.
Another problem exists with users who last operated the instrument many months ago. It would be helpful if a booking system could show that a user has not been active for X amount of time and/or flag up the user after X months of delay. This does not seem to exist in any of the listed solutions. An option however is to delete accounts if they are inactive for more than e.g. six months.
If you are interested in any of the solutions listed below, please consult the website or contact the person who talked about it.
Open Source Solutions
Google calendar
(Philippe Laissue, University of Essex)
Pros: Free, easy to set up, hosted externally. Ties in with other Google applications (I set up a Google training site with calendar and Google Docs, forms & code tied in, which can all be easily changed/adapted). Charging is not automated, but can be exported to Excel using Gcal2Excel app.
Cons: Only booking (does not log actual time spent on instrument). Not fool-proof. Users can modify or cancel their own and other people’s reservations retroactively. Details are visible to everyone (compare to Calcium below). Gets very busy with many instruments in facility.
Bumblebee
The right versions of MySQL, Apache httpd, and PHP need to be pre-installed.
Commercial Solutions
Scionics
(Kurt Anderson, Beatson Institute, Glasgow)
Pros: Categorised users, facility staff can also be booked. Access granted only after training on an instrument has been completed, using Active Directory for log-ins. Cancellations can only be done 24h before (such ‘last minute’ cancellations often get picked up by others in busy facilities). Can be cancelled retroactively only by Administrator.
Cons: Commercial. Scionics set it up on Beatson server for ~1.5k. Does not use different rates for different times (e.g. for overnight time lapse vs. daytime use). This might however get implemented upon request. Also takes several weeks to be fully set up (i.e. with all different users/ categories/ instruments etc.).
Calcium
(Alex Ball, Natural History Museum)
~1.4k for 25 licenses. It allows data protection as the instrument appears as booked, but it does not reveal by whom.
PPMS (Platform-Pilot Management Software)
(Colin Gray, University of Sheffield)
Pros: Web based hosted externally (no set-up on internal server required). Fully featured with, individual logins, user rights can be assigned after training, pre-session cancellation time can be set (and allow full or partial charging), different charging rates for different systems, times of day and/or user/project. Project function allows multi-role (e.g. technical) staff to book individual sessions under appropriate account. Long sessions (eg time-lapse) can be discounted after a set time. Special microscope conditions can be requested with the booking. Users can log problems which admins validate to allow warnings of limited/no service status. Full usage and downtime stats. Supports active directory/LDAP and can log actual use on instrument. Charging invoice can be produced automatically, very useful when a grant audit is ordered.
Cons: Commercial.
