[labnetwork] Booking Management System

[mike at badgerlms.com]

Hi Owain,

 

You should consider Badger LMS as an option. Certainly, drop me an email if
you'd like a demo. Badger began life as Coral at Stanford in 2000 and that
codebase led to the creation of Badger as a commercial application about 7
years ago. Unlike Coral, Badger has been under constant development with new
features added regularly. As importantly we've upgraded the application
internals all along the way which is critical to the long-term reliability
of any application. Over the years Badger has evolved into a significantly
different app with greater flexibility, dramatically more efficient
workflows, browser / mobile microservices that can accommodate most users,
real-time status dashboards and a lot more. Badger can be quickly configured
and installed turnkey in the AWS Cloud. You can easily schedule equipment
and base reservations on a wide range of parameters, including: horizon,
time of day, combined devices, a penalty on future reservations for late
cancelations and more. Likewise, you can charge in a variety of ways
including: use time, reservation time, unused reservation time, cancelled
reservation penalties and so on. You can also capture information and charge
for services and supplies, training and staff time. Attachments give you the
ability to include Excel data, jpg's or anything else with reservations,
equipment problems and historical transactions. Our reports and utilities
give you the ability to do fine grained analysis, graphing and dump into
native Excel format for further review. You can expire user qualifications
based on last use or initial qualification, easily manage project and
accounts changes in past and much more. At the same time Badger's
reliability is simply amazing.

 

Badger isn't free, but you probably don't want it to be. We have zero VC
funding or debt. Unlike a lot of apps, we run Badger the old-fashioned way -
we try hard to deliver a product that people will want to use and charge a
price that will sustain our business and our families. We've managed to
start and stay profitable solely based on product revenue and believe this
is your best guarantee that we will be here for the foreseeable future. 

 

Best of luck in your search.

 

Regards, Mike

mike at badgerlms.com

 

 

 

On 12/18/2018 05:31 AM, Clark O.D. wrote:

Dear all, at the UoS Nanofab we currently use a system called Phoenix to
manage our users, tool bookings, and report generation. Unfortunately due to
an acquisition of the vendor there is a possibility that support for the
software will be dropped soon, leaving us with the issue of whether to adopt
development or replace the system. I know some other UK facilities are in a
similar situation. Before Pheonix we had an in house solution but this was
found to be inadequate in several ways (mostly tied to monitoring and
funding). 

 

I would be very interested to know if you use any other management software
that could be recommended. At a minimum it must handle user details/training
per tool, zoning, tool maintenance settings, user notifications, calendar
bookings, budget code tracking, and report generation E.g. tool
uptime/utilisation or a breakdown of tool spend per budget code etc. 

 

Best regards, Owain

 

Facility Manager

Southampton Nanofabrication Centre
University of Southampton
Highfield
Southampton 
Hampshire SO17 1BJ

 

+44 (0) 2380 597389

 



 

 

_______________________________________________
labnetwork mailing list
labnetwork at mtl.mit.edu <mailto:labnetwork at mtl.mit.edu> 
https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork
<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmtl.mit.
edu%2Fmailman%2Flistinfo.cgi%2Flabnetwork&data=01%7C01%7Codc1n08%40soton.ac.
uk%7C16d42a41e5f24341af3808d665c36046%7C4a5378f929f44d3ebe89669d03ada9d8%7C1
&sdata=USxJXNBpNLWGtj%2BokM0t2P1mmotxLKcKqwlTIQD%2BsYg%3D&reserved=0> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mtl.mit.edu/pipermail/labnetwork/attachments/20181219/18c26b2f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11532 bytes
Desc: not available
URL: <https://mtl.mit.edu/pipermail/labnetwork/attachments/20181219/18c26b2f/attachment.png>