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.
It’s not uncommon within specific software communities for there to be what we call “vertical” resources. I’m one, myself – a person trained to be able to handle the entire project, from project management, to business analysis to development work. There are specific reasons these resources exist and, as my customers tend to like, some benefits, as well.
LIMS selection for an industry is difficult even if there are many such systems within an industry, and that’s true of ELNs and LESs, as well. By the way, if the title of this seems awkward, it is, but I stopped wordsmithing it and just left it alone.
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.
When we talk about programming the LabWare LIMS, we have to be careful what we mean. The LabWare LIMS Smalltalk is NOT what we’re going to be using. Instead, think LabWare LIMS Basic.
Today’s blog post was inspired by a search phrase that brought readers to this blog, which is “labware user manual save off line”. Today, we will discuss storing the LabWare LIMS User Manual, locally.
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.