Just yesterday, I ended up in a conversation about product safety. Today, I’m writing about how LIMS product safety tracking is part of that puzzle.
I recently wrote about the LabWare and the SampleManager systems but the last “big” system I started to learn was the Labvantage (LVS) system. Here are some thoughts to pass along to those of you thinking that that might be your next big adventure.
A recent post discussed modules within the LabWare LIMS and about not getting too crazy with downloading and installing things. Today’s post gives one example of how you can kill your system performance with one simple combination. This is an issue for just about any software, really, but here’s a specific example using the LabWare system.
This is a continuation of the last blog post discussing these search phrases that brought readers to this blog: “sap-lims interface” and “sap-lims interface challenges.”
As I like to do upon occasion, today my post is based off of not just one but two (Yes, count them! TWO!!) search phrases that brought one or more readers to this blog. Today’s phrases are “sap-lims interface” and “sap-lims interface challenges.” In this case, though, I’ve already split this into two posts, so this post will give some background and the next post will list some of the most common issues to deal with.
In this day and age, you would think that every system would have been interfaced with every other type of system. That’s probably true. But it’s NOT true that every individual system has been interfaced with every other individual system and that’s where most of the challenges are.
In my last post, I suggested to customers interested in running mobile apps for their LIMS, ELN or LES that they consider writing their own or having someone write one for them. I suggested writing them specifically for the devices that they will use. But some clever folks are still thinking they’re going to write one generic app that works for everything. They think if they do this that, if they switch devices, they can just swap the new devices in. Here are two more considerations.
These days, a criterion of looking for a new LIMS, ELN or LES is more and more commonly that it have mobile capabilities or some other mobile factor. More customers are looking for this. Yet, how critical is this on your requirements list?
Over time, many systems, despite strong procedures and practices, end up with portions that are convoluted or messy, in one way or another. I see plenty of opportunities where customers could get in and rewrite some code to make it cleaner and easier-to-manage. I’ve written about this, before. And, as before, I think we all acknolwedge that this is a tricky business because, first off, everyone is already too busy to do this and, secondly, it could introduce other problems. But we’re seeing a growing trend in this that I specifically want to talk about: Version 7 LabWare LIMS upgrades.
Most of us consultants probably can tell at least one story where database backup (or lack thereof) plays an important part in a sad story of an implementation that’s gone off-track.