LabWare LIMS

Score8 out of 10

4 Reviews and Ratings

Community insights

TrustRadius Insights for LabWare LIMS are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

LIMS Basic Customization: Several users have praised the valuable feature of LabWare's LIMS Basic code, which allows for customization of the system to meet specific user needs. This flexibility enables users to request LabWare to perform functions that are slightly different from the standard functionality or completely new to the system.

Security Management with Roles: Users appreciate LabWare's ability to effectively manage security within the system through roles. By utilizing roles, administrators can define specific roles for different users, ensuring that only authorized individuals have access to sensitive information and functionalities. This feature significantly contributes to the overall security and integrity of the system.

LabStation Interface Streamlines Workflow: The LabStation interface provided by LabWare has been praised by users for its ability to improve lab workflow and reduce data input errors. Through this interface, users can easily interface with instruments, streamlining the data collection process and minimizing manual data input. This integration leads to increased efficiency and accuracy in laboratory operations.

Reviews

2 Reviews

LabWare LIMS - Streamline your Sample Log-In, Testing, and Results Reporting Process

Rating: 8 out of 10

Incentivized

February 14, 2019

Use Cases and Deployment Scope

Our Analytical Department utilizes the LabWare LIMS program to track samples submitted for Analytical Release and Stability testing. It's very easy for our group and other groups to track the progress of the testing and see exactly where the samples are in the release process. The program itself is somewhat intuitive and user-friendly.

Pros

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.

Cons

LabWare LIMS seems somewhat intuitive, but there is room for improvement in the user controls. It can be difficult or confusing sometimes to find the exact sample that you are looking for.

Likelihood to Recommend

It is well-suited to a busy QC laboratory with a medium sample load. It is a good mechanism for managing sample flow. It may not be as easy to use in a busier laboratory with a very large sample load that may overload the LIMS system.

Verified User

Director in Research & Development (501-1000 employees)

Vetted Review

LabWare LIMS Review

Rating: 10 out of 10

Incentivized

April 13, 2018

Use Cases and Deployment Scope

It is used by most business units and sites within our corporation. We are moving about 5-10 sites to this system per year.

We use it to manage lots, samples, tests, and results, and all the workflow around these when testing samples from our production units. We also use it in to manage projects, samples, tests, and results and all the workflow around these for our Technical Services and R&D departments.

Pros

The LIMS Basic code that supports the standard LabWare functionality. From time to time, and user may request to have LabWare perform some function that is slightly different than standard functionality, or completely new to LabWare. Through LIMS Basic. and other standard functionality (such as Event Triggers and Automation Scripts), you can customize LabWare to do just about anything you want. I always tell the users ... "before you ask, the answer is always 'Yes ... LabWare can do that!'".
The use of roles to significantly helps facilitate the management of security within the system.
Interfacing with instruments through the use of LabStation helps improve lab workflow and reduce data input errors.

Cons

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.

Likelihood to Recommend

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.

Ronald Starcher

Systems Analyst in Information Technology at Solvay (10,001+ employees)

Vetted Review

View profile

Loading Reviews List....

LabWare LIMS Review

Rating: 10 out of 10

Incentivized

April 13, 2018

Use Cases and Deployment Scope

Pros

The LIMS Basic code that supports the standard LabWare functionality. From time to time, and user may request to have LabWare perform some function that is slightly different than standard functionality, or completely new to LabWare. Through LIMS Basic. and other standard functionality (such as Event Triggers and Automation Scripts), you can customize LabWare to do just about anything you want. I always tell the users ... "before you ask, the answer is always 'Yes ... LabWare can do that!'".
The use of roles to significantly helps facilitate the management of security within the system.
Interfacing with instruments through the use of LabStation helps improve lab workflow and reduce data input errors.

Cons

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.

Likelihood to Recommend

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.

Ronald Starcher

Systems Analyst in Information Technology at Solvay (10,001+ employees)

Vetted Review

View profile