[labnetwork] Booking Management System

[David S Barth]

Hi Owain,

A few people have already mentioned NEMO. Here at Princeton, we switched to NEMO about four months ago, and it has been a big success both with staff and labmembers. We've also been able to modify and customize it to meet our needs. Our fork of the NIST's code with those modifications is available here: https://github.com/dsbarth/NEMO

I'm happy to discuss more about the experience of setting up and transitioning to NEMO if you'd like.

Best,
David Barth
dbarth at princeton.edu<mailto:dbarth at princeton.edu>
PRISM Cleanroom
Princeton University


From: labnetwork-bounces at mtl.mit.edu <labnetwork-bounces at mtl.mit.edu> On Behalf Of Clark O.D.
Sent: Tuesday, December 18, 2018 7:31 AM
To: labnetwork at mtl.mit.edu
Subject: [labnetwork] Booking Management System

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

[Untitled]

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