FlaskTrack vs. LabWare LIMS

Sample testing is great, communications (emails) out is so-so, depending on your need, you have to develop something. But that is not hard to do.

Incentivized

• One of the strengths of this program, as previously stated, is to track your sample through the entire testing process, from log-in to results reporting.
• It is also handy to generate reports of sample results using the LabWare LIMS program.
• LabWare LIMS provides a great way to preserve testing results electronically for future needs.

Incentivized

• The management of Event Triggers can stand to use some improvement. Especially when it comes to using the "DEFAULT" template event versus the specific template event.
• Licenses are considered "concurrent". But LabWare does not have a feature that tells me (at any level) what my peak license usage is. For example ... if I own 100 licenses, LabWare will tell me at any given time how many licenses I am using. But it won't tell me at the end of the day, week, or month, what my peak usage was. So if I own 100 licenses, and I look at my usage right now, it might say I am using 50 licenses out of 100. Does this mean I have 50 too many licenses? Probably not. I just need a way of telling what my peak usage is so that if I want to roll LabWare out to another site, do I need to buy more licenses? Or will my 100 cover for it?
• Importing data into static data tables is not well done in LabWare ... or even available. I can do it outside of LabWare with database management tools such as TOAD. But it is up to me to make sure all the tables and columns are populated correctly. It would be nice to have a feature within LabWare to do import data (from Excel spreadsheet for example) directly into some of the main tables.

Incentivized

I have not used other LIMS systems.

Incentivized

• Very positive. It allows the production units to increase volumes (and thus sampling) with minor impact on the lab.

Incentivized