As Yogi Berra said, “It’s deja vu, all over again. So, yes, you did see this same post just in recent weeks. However, I realize the first one just sounded too dry and robotic plus I did get some good feedback to that effect.
LIMS configuration versus customization remains an issue after many years of products and implementations. Here, we discuss the confusion behind these terms, as well as examining the decision-making process that goes on during implementations regarding these.
Today’s topic is actually not a written blog post but a podcast. This podcast’s topic is “Seven Initial Questions For Combining R&D and QC LIMS.”
Maybe. R&D and QC LIMS can be combined under some circumstances. However, there are a number of factors to consider.
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 used to occasionally get involved with being a reference for articles that I did not write, myself. In past years, I’d gotten more involved with writing articles for periodicals, myself, as well as this blog. I thought it would be interesting to get involved with other areas where I have relevant expertise. After all, many of these do relate to issues in our own industry.
This is the first post of the new GeoMetrick Enterprises “Out on a LIMS®” blog. If you’re seeing this post, you’re subscribed. You will probably see yet another post but, if you do, you do not need to do anything more to remain a subscriber to this blog. Unfortunately, sending two blog posts out, this…
Crafters seem to have “stashes” – a pile of material collected that they intend to use “some day” but that continues to grow to the point where they have too much money and space invested in materials that they haven’t used. Occasionally, crafters come up with “stashbusting” projects that “bust” the “stash.” If you think of your project that way, where you have too many things on the list of tasks (i.e., where you’ve run into “critical path” issues and/or resource blockages), it’s a little bit like that – it’s a pile of something that needs to be conquered.
In my last post, I talked about how companies sometimes keep non-performing people on their projects. They also keep non-performing vendors and under-performing vendors.
When I first started my business, I knew there were quite a number of projects that had resources who couldn’t finish their work. I don’t mean that they couldn’t finish in a reasonable time, but that they literally couldn’t finish anything, at all. I knew this partly from working with these projects but also from running into customers who told me about their projects at user group meetings or on the phone. I thought this was the best source of revenue I could find. I was wrong on that account.