Some companies will write, generially, by their company names. Others will tell the names of the people who write the articles. I use my name for these posts, not merely the generic “GeoMetrick Entperprises” and I have some reasons for that.
Compliance is so important that even those people such as myself who are not compliance people must to do what we can to help customers work toward this goal. Today, I will give you three documentation tips from the implementation side of the project.
In my last post, I mentioned LabWare’s name and I noticed some things about the types of posts people were reading that leads me to make some statements about the current state of that product.
For some reason, there are people and companies in this world who think that my company, GeoMetrick Enterprises, has some kind of relationship with the company LabWare. This is not true. I work with the LabWare software not the LabWare company.
In all these posts about the end of my job, some of you might be surprised that I’m only now writing about the LIMS. Me, too. U of M runs the LVS Biobanking solution which I knew before I had an inkling I would work there so I guarantee I’m not passing along any secrets, here. It was easy enough to see from reading people’s LinkedIn profiles so they’re not keeping it a secret.
Many projects have a problem getting reports produced. In one sense, it seems expensive to hire a LIMS, ELN or LES expert who knows the data but who comes with a rather high rate. On the other hand, getting a cheap resource who knows the reporting tool isn’t an easy solution because it’s so incredibly difficult to teach them these massive databases and how they work. Today, I will tell you the solution to this problem.
Paul Drake was Perry Mason’s investigator. Last year, I had an opportunity to do what I suppose might be considered database investigatory work.
In a January post, I wrote that it was Time to Say Goodbye. Recently, some of you have noticed I’ve started blogging, more, working on my web-site, and have been doing business development. As such, some of you have been asking if I’m coming back. That remains to be seen but let me go into more detail.
GeoMetrick Enterprises Entirely Responsible for Accenture’s Purchase of LabAnswer and Other Tall Tales
We have recently read about Accenture acquiring the major LIMS and Laboratory Informatics consulting firm, LabAnswer (Accenture to Acquire LabAnswer) but did you know that GeoMetrick Enterprises is entirely responsible for this? Let me tell you why…
Just the other day, I had an interesting discussion with someone who is using remote resources on their project. We had a bit of a laugh over those people who constantly worry that remote resources might not be doing what they’re supposed to and, instead, goofing-off or, as we say in our industry jargon, “eating bon-bons.” Most projects are pretty savvy about this but what if your project is new to do this? How would you know, short of putting cameras on them?