July 24, 2015

About My Lab... Part 1 - The Questionnaire


Okay, let's make this one simple...

Click HERE to answer a few brief questions about how your lab approaches instrument support.

All info is confidential  We will publish results in an upcoming post.

Shortest darn blog all year...


April 27, 2015

The Tip of The Day

Part One

tl_files/labsquad/blog_images/beckman tip.jpgBack in May of 2013, we talked about the use of third party tips on liquid handling robots.   Well, we got a lot of emails on that one as it seems a lot of people are looking for alternative tip providers, for a number of reasons...but mostly cost savings. 

We heard a lot of stories regarding OEM's who threatened to void instrument warranties or even refuse to service instruments that use third party tips.   Is that legal?  Probably not but, it certainly is unwise and I would imagine that is not a company policy so much as it is a regional sales rep or service engineer who does not want to lose a lucrative revenue stream.  

Having worked on the supplier side (at Caliper Life Sciences, now part of Perkin Elmer),  I can tell you that most OEM's want end users to buy their tips...and only their tips.   Why is that?  Well, the biggest reason is that they have invested heavily in the creation of precision injection molds and the logistics required to stock and ship tips.  This is not inconsequential and often explains why OEM tips tend to cost more than third party tips.   Even when the mold costs have been amortized, stocking and distributing tips is a costly endeavor, as is ongoing quality monitoring.

So, you might be asking, how could a third party tip cause an instrument to fail?  The only conceivable scenarios I can think of are:

a) head crashes due to physical differences or
b) 0-rings on mandrels that might wear or deform due to physical differences (polymers or dimensions).

Other than that, it's really a red-herring argument.   Our sister division,  AssayGuru has performed performance analysis on a number of third party tips for various manufacturers and compared both pipetting accuracy and mechanical reliability.  These tests were conducted on various brands of liquid handling robots using both third party and OEM tips.   In most cases, there have been no issues and the third party manufacturers we have worked with were eager to find and correct any flaws, prior to launching their tip products.

In my next post, I will detail one such manufacturer who has impressed us so much that we have actually created a new partnership...stay tuned.


April 3, 2013

Have I Got A Tip For You…


“I want to say one word to you. Just one word.  Are you listening ? Plastics.” - The Graduate, 1967

Automated liquid handlers are very quickly (if not already there) becoming commodity products.   While every liquid handling manufacturer claims certain features or twists on how they do things, ultimately they all do pretty much the same thing…suck and spit (keep it clean people, we’re running a blog here…)  One sure sign of ‘commoditization’ is when third parties begin to offer accessories that compliment or compete with a particular product and in the case of liquid handlers,  that most commonly means disposable pipette tips.

Wondering if there any performance or reliability issues associated with the use of third party tips? tips To be sure, original equipment manufacturers (OEM’s) test and warranty their products using tips that they manufacture.   It is reasonable then for them to discourage the use of third-party tips insofar as performance guarantees are concerned.   Additionally, most of the OEM’s have made significant investments in the creation and maintenance of plastic injection molds that they or their supplier uses to stamp out their tips… so there is of course an understandable financial desire for them to want customers to purchase only OEM tips.

Insofar as periodic maintenance is concerned, end users should note that if they are performing routing CV checks (either gravimetrically or via a dye test), the tester needs to consider that differences in accuracy or precision may be affected by badly formed tips but that holds true regardless of who makes the tip.

However, it is not reasonable for an OEM to claim that the use of non-OEM tips “might” void the equipment’s warranty.  That’s a bit of a scare tactic that upon further reflection speaks more directly to lost consumable revenue than the fear of tip induced hardware failure.   I mean, if a tip gets stuck on a mandrel instead of getting shucked, I guess yeah, you could experience a crash that could damage the liquid handler.  Crashes do happen but such occurrences are rare once a tip is in production as most of the third-party providers I have dealt with have very stringent QC programs.    If you want to err on the side of caution, consider using OEM tips for new purchases and evaluate third-party tips once the warranty expires (usually 1yr).

Looking for alternative tip providers;

Corning/Axygen -   Agilent/V11, Beckman Coulter, BioTek, Caliper/PE, Dynamic Devices, Hamilton, Molecular Devices, Tecan, Qiagen

Labcon - Beckman Coulter

Phenix Research – Agilent/V11, Beckman Coulter,  Caliper/PE,  Eppendorf, Molecular Devices, Tecan, Qiagen

Thermo Fisher/Molecular BioProducts – Agilent/V11, Beckman Coulter, BioTek, Caliper/PE,  Molecular Devices, Tecan, Qiagen

March 26, 2013

Nervous…System Support

My last post about standardization and open source scheduling software for integrated systems got me thinking more about the post-sales support sidon knottsde of those systems.

As many of you know, systems can be very expensive so end-users are making critical decisions on behalf of their employers, both on how well their money is being spent and what are reasonable expectations as to when the system will begin to show a return on that investment.    There is always concern about that ramp up time and the problems you may encounter along the way, so the question of warranty becomes very important to the lab manager or principal user of the system.

Most system integrators go through a very similar process regardless of who the end user is.   It generally all starts with a customer needs assessment, whereby a sales mabiocelnager (usually accompanied by an Application Scientist) asks a number of questions prior  to generating a system concept proposal.   While it may seem tedious to the end-user, (I know what I want, why can’t these people just give me their quote?) this is a critical step in ensuring long term success.   I have been involved in a number of situations where a customer had budgeted hundreds of thousands of dollars but could not provide a single manual method they wanted to automate.    Not good.

Weeks (more like months) after  the system is designed/proposed and agreed upon/purchased by the customer, a date is usually scheduled for a FAT (factory acceptance test) whereby the customer visits the integrator and goes through a “buy-off” checklist prior to shipment.  This buy-off is best done with beckman systemthe actual customer methods (minus real chemistry) to ensure that the system performs as agreed upon prior to shipment.   Remember, shipment means breaking down the system and packaging so that it can be “re-integrated” yet again upon arrival at the customer site whereupon it goes through the SAT (site acceptance test) which is basically the  same buy-off as the SAT, albeit with actual chemistry.   Once completed, you get a handshake (maybe a hug if it goes really well) and “TA-DA !”you own the system.

Most integrated systems come with a one year warranty.  This can mean different things to different integrators but in my experience, entails parts and labor only (travel is nostaublit included).  It also does not include operator induced failures like crashing a robot into an instrument.  In general, most systems include a fair number of third party instruments that the integrator does not manufacture and they don’t make a lot of money providing them.   These instruments come with their own warranties (usually 1 yr) and the integrator almost always passes these on to the end-user, acting as the first point of contact if a failure occurs.   Since the instruments can often reside at the integration firm for several weeks prior to FAT,  it is important for end-users to understand their warranty…’what is covered?’, for how long?’ and ‘when does the clock start ticking (upon shipment, acceptance)?’.

As mentioned in prior posts, an extended warranty for an integrated system can often cost 10-15% of the purchase price of the system.   Some integrators offer an incentive (discount) if you purchase such an extension with they system, or prior to expiration of the standard one year warranty.   Should you choose that option?

In short, the answer is no and I will tell you why.   Let’s assume we are talking about a $350K ELISA system that includes a robot mover, bar code reader, liquid handler, plate washer, ambient storage hotels and plate reader.    Those majorbeckman systemcomponents probably account for less than 50% of the price of that system.   The remainder is comprised of  things that don’t wear or break (system tables, enclosures, scheduling software, PC and …labor).   That last one is a biggie.    Integration is hard work and proper design, build, programming and testing prior to  SAT can include hundreds of person-hours.  That is commonly referred to as NRE or non-recurring engineering.   A warranty for such a system could cost upwards of $50K, or more (not including travel) but you really should only care about the instruments…not the other stuff.

So, if you are faced with a decision regarding extending the warranty of your integratedautomateitsystem…push back.  It’s pretty easy to determine the list price for each instrument in a system and request a contract that is based on just those costs.   You could also go directly to each manufacturer and request contract pricing on their product only.   If that is too time consuming or a management hassle you don’t need, you may want to reach out to one of the major MVS (multi-vendor services) providers (ThermoPEJohnson ControlsAgilentGE) or smaller ISO (independent services organizations) like The LabSquad.

Don’t be nervous about system support…be informed.

March 22, 2013

SiLA Love Songs

Time to talogo_silake a break from talking about instrument support and wax philosophically about a bigger support challenge – integrated systems.    A colleague asked me my opinion of the SiLA, a consortium that is creating standards for lab automation instrument interfaces.

As I understand it, the folks behind SiLA have a business model that will define these interface standards and then presumably charge instrument manufactures for the privilege of claiming “SiLA Compliant,” or some such declaration.    I have to admit that my knowledge of this model is sketchy at best, and the SiLA website does not really lend much insight.

This seems a bit like putting the cart before the horse to me.  That is to say, the instrument interfaces are fairly useless without a higher level scheduling software that manages assay workflow, instrument status and data.

In the 1980′s and 90′s, there were many such products from well establishepolarad system integrators such as  RoboCon (acquired by CRS Robotics), CRS Robotics (acquired by Thermo Electron, who merged with Fisher Scientific),  Scitec (acquired by Zymark), Zymark (acquired by Caliper, who merged with Perkin Elmer) and Velocity11 (acquired by Agielnt) — do you sense a theme here?  All this M&A activity happened during the HTS and uHTS craze.  Once that goldrush ran it’s course, it became clear that system integration is difficult in a public company.   It’s hard to take a 16-20 week design/build/install model and cram in into a quarterly revenue model.  Systems needed to become smaller, more standardized and less expensive.

Nevertheless, each integration company created their own assay management and scheduling software and wrote their own libraries of instrument interfaces.  Hundreds of systemsMicrosoft.Net were installed and not a single one required the involvement of SiLA or any other instrument standard.   One common thread that enabled each of these software’s to succeed was the widespread adoption of Microsoft’s COM, OLE and eventually ActiveX  and .NET frameworks.  As long as instrument manufactures included automation “hooks” based on the MS framework, integrators had little trouble creating robust instrument interfaces.   It’s really not that complicated, as you really just need to be able to initialize, start, stop and report error status for most instruments.   Data (from readers primarily) was generally a secondary consideration and not part of the scheduling paradigm.

So flash forward a few years and there are remarkably fewer pure integration companies left.   Caliper/PE and V11/Agilent are still out there, but not perhaps as visible as they once were.   Thermo Fisher now has a more limited presence as well.   To be sure, companies like Beckman, Tecan and Hamilton still build systems but they are primarily liquid handling companies first, integrators second.   Really only HiRes Biosolutions,Process Analysis & Automation Ltd. or PAA and Hudson Robotics still fit the pure integrator definition.

It would seem to me that without an Open Source scheduler software standard, there isn’t much need for an Open Source instrument interface standard.    Each of the companies mentioned above already have significant investments in creating their device libraries.  What is the incentive for them to abandon those interfaces (many of which they charge for) in favor of the SiLA standard?   I’m not saying they wouldn’t but I’d like to hear a good business argument for it, other than fear of someone else doing it.   In fact,  I would imagine that an Open Source scheduler could exist nicely even without SiLA, much as the proprietary schedulers have existed.    As users create interfaces to various instruments, they would put them into the public domain for anyone to use…no SiLA required.

A few years back, a number of folks in the Cambridge, MA community came together and started to discuss an Open Source scheduler.    About two years ago,  Caliper donated it’s CLARA/iLink source code to the University of Wales, in Aberystwyth which can still be found on Source Forge under the name  LABUX.   Last fall, two MIT students created a similar effort called Clarity.   I have not followed either of these endeavors closely, but it seems to me that they could either solidify SiLA or bury it.

My opinion?  When I ran the system business at Caliper, prior to the PE merger, I was not a big fan of Open Source scheduling.   I knew the investment we had made in our own software and although I knew it had it’s limitations, it was enabling technology that created significant revenue.   Still, I saw the LABUX initiative as a way of testing the waters.    If an open source scheduling standard did emerge, better that it be something we were familiar with.     Additionally, if we could build systems and not have to maintain the software staff to maintain the scheduling software, we could in theory be more profitable (that public corporation thing again).   Now, two years removed from that role,  there does not appear to be  solid consensus on Open Source scheduling or interfaces.    I have no stake in the game anymore, so perhaps I can now be a bit more candid and say.  I am a big fan of the pure integration model, so I am rooting for HiRes, PAA and Hudson!   I still don’t get the whole SiLA thing.   Seems a bit… SiLLY to me.

March 18, 2013

Is it a System or is it a Liquid Handler?

Remember Razzles? – ‘is it a candy or is it gum?,” so the TV commercial went.   (I actually razzlessubmitted a contest entry calling it  ‘Ghandy…a peaceful coexistence of seemly incompatible delights.’  Not bad for 9yrs old and still waiting on a reply.

Servicing liquid handlers can be a lot like Razzles in that you start out thinking you are working on one thing only to show up and find out that you have something else going on.

System Types:

There are essentially three types of plate based automated systems commonly found in life science research labs.

Robot Centric – A robot arm (manipulator) delivers all consumables to/fropaam a variety of plate based instruments and storage devices.   While many such systems include a liquid handler, they along with other instruments are controlled via a separate scheduling software that oversees the assay steps and ensures proper timing.   Common examples are Hi-Res Biosolution ACell , PAA automate.it,  Agilent BioCel and Caliper (PE) Staccato.

Distributed Robots – Similar to above, except that there are multiple robot arms connected via a conveyor belt or other plate transporter.  Each arm is dedicated to a small number of instruments which each carry out the assay in a sequential (first station to last) fashion.  Again, one or more liquid handlers may be present in the system however they contain programs that are initiated 


by a higher level scheduling software.  Such systems were very popular in the pharma industry (Thermo Dim 4, Zymark Allegro) rush to process more compounds per day (HTS and uHTS) looking for new chemical entities, but nowadays you be hard pressed to find many survivors still in operation.

Liquid Handler Centric- In this instance, the liquid handler is the heart of the system, which is to say, the liquid handler software runs the assay (no higher level scheduling software).   A large number of these types of ‘systems’ consist of just the liquid handler, by itself, simply carrying out pipetting operations.   However, as many mainstream liquid handlers now include robotic gripper capabilities, these devices start to be 


stretched into more capable systems that automate more of the assay freeing up lab personnel for more high value operations.   The plate gripper can load/unload consumables for multi-plate runs or can deliver consumables to shaking, heating, cooling or waste locations on the liquid handler deck or may move them off-deck to plate readers, washers, centrifuge, incubators, thermal cyclers, reagent dispensers or storage devices.   Examples can be see from well known vendors such as Beckman CoulterTecanHamilton RoboticsAgilent and Perkin Elmer.

Conclusion – when exploring your options for servicing a liquid handler, be sure to consider any peripheral equipment attached to that device.   If the end-user expects their entire system to PM’d during a routine visit, the service tech may be either the bearer of bad news or a well prepared and valued service provider.

March 6, 2013

Liquid Handling Questionaire (‘questionaire’ is French for…questionaire)

If you or your lab currently use liquid handlers, or are planning to purchase liquid handlers please take a few minutes and fill out this labX survey.

(click on the image below and you will be redirected to LabX)


Looking to buy a liquid handler?   Try www.UsedLiquidHandlers.com

March 4, 2013

IT's an IT Thing

windows xp the task failed successfully dr heckle funny wtf windows errorsWe’ve been hearing a lot of our customers ask about various lab instruments being compatible with Windows 7 lately.   Seems  IT groups everywhere are struggling with the eventual demise of Windows XP.  Already unavailable for new PC’s since 2010, Microsoft has announced that all support for WinXP will cease in April of 2014.

While most instrument OEM’s (original equipment manufacturers) are already making the move to Win7,  a huge number of legacy instruments in labs are running XP.   Manufacturers may not want to provide ‘backward compatibility’  for older equipment for two reasons; First, if it ain’t broke don’t fix it.  Sounds lame, but most instrument software is developed with the OS of the day in mind.   Trying to get the performance and reliability that users expect by supporting a major OS upgrade could lead to tons of surprises…ones that  they won’t be paid to correct.   Also,  more than a few vendors have used this Microsoft phase out as a reason to obsolete older instruments and encourage users to upgrade to new hardware in order to get Win7 compliance.

If budgets don’t permit the purchase of new equipment desperate users should consider exploring the Windows 7 compatibility tool.    One caveat is that you would be well advised to back up your WinXP first, or better still try installing your legacy applications on a new Win7 PC.    It’s a lot easier to mess around with a new PC if you know you can go back to the original PC if all else fails…

The following is gratuitously ‘borrowed’ from http://www.howtogeek.com

Using Program Compatibility Mode in Windows 7

It can be quite annoying when you try to install a driver or other software on Windows 7 just to find out it isn’t compatible with the new OS. Today we look at using the Program Compatibility Assistant, and troubleshooting compatibility issues so programs install successfully.

Program Compatibility Assistant

Program Compatibility is a mode that allows you to run programs that were written for earlier versions of Windows. The Program Compatibility Assistant detects compatibility issues and allows you to reinstall using the recommended settings. For example we got this error trying to install a music interface device driver for home recording.


After we closed out of the error, the Program Compatibility Assistant came up advising that the program didn’t install correctly. To try to install it again select Reinstall using recommended settings.

The Compatibility Assistant went through and fixed the issue and we were able to install the driver. The problem was the driver was designed for Vista and the the assistant automatically select the correct compatibility mode for us to install it.

Sometimes you might get a screen similar to this example where Virtual PC 2007 isn’t compatible with Windows 7 and you can check for solutions online.

After checking for solutions online, we’re shown that there is an update that might solve the issue.

Which points us to the Microsoft site to download Virtual PC 2007 SP1.

Note: Sometimes a program does install correctly and Program Compatibility Assistant thinks it didn’t. There are also times when you cancel an installation half way through and it pops up. If you’re an Admin and tired of seeing it pop up because you know what you’re doing, check out our article on how to disable program compatibility assistant in Windows 7 and Vista.

Program Compatibility Troubleshooter

There might be times when Program Compatibility Assistant can’t find a solution, or a program installs fine, but doesn’t work the way it should. In that case you’ll need to troubleshoot the issue. Right-click on the program icon from the Start Menu or in many programs the shortcut icon and select Troubleshoot compatibility.

Windows will detect any issues with the program and you can try to run it with the recommended settings, or go through the troubleshooting wizard. For this part of our example we’ll select Try recommended settings.

This option allows us to test run the program to see if the new compatibility settings fix the issue. Click on Start the program to begin testing it out. After testing the program and determining if the settings work or not click on Next.

If the program is running correctly you can save the settings and it will continue to run with those settings. If it didn’t work properly, you can try using different settings or report the problem to Microsoft and check for an online solution.

If you selected No, try again using different settings it will bring up the troubleshooter where you can specify the issues you’re having with the program.

Depending what you check in the screen above, you’ll be presented with other options for what is not working correctly. Where in this example it shows different display problems.

New settings are applied to the program and you can try running it again.

If none of the compatibility settings work for the program, you’re prompted to to send a generated problem report to Microsoft.

Manually Select Compatibility

Of course if you don’t want to deal with the Program Compatibility troubleshooter, you can go in and manually select Compatibility Mode. Right-click the program icon and select Properties.

Then click the Compatibility tab then check the box Run this program in compatibility for and select the version of Windows from the dropdown. Now it will always run the program in Compatibility Mode for the version of Windows you selected.


Hopefully running the program in an earlier version of Windows helps solve the problems you’re experiencing. Each program is different so the troubleshooting steps will vary. Most programs written for Vista should work in Windows 7, but not all of them. If you’re having problems with a program not working correctly on Windows 7 and have gone through the Compatibility Mode troubleshooter, your best bet is do search the developers website for a newer version or in their forums.

February 27, 2013

Aye Robot...

scottyThe first lab robot was introduced bzymark logoyZymark Corporation in 1982.   The Zymate robot was used to move labware between various instruments in a ‘pie’ shaped work area, simulating the same procedures followed by theoreticallyhigher priced lab researchers and their assistants.  Fast forward 30yrs and the term lab robot can be further applied to several unique devices;

  • Liquid Handlers – XYZ robots that pipette reagents, some can move plates usinbravog gripper hands.  These devices can pipette in a variety of ways from one single channel, 4-12 channels for row or column work or 96 or 384 channels for whole plate transfers.   Some liquid handlers are used as stand alone devices (islands of automation) and can also be found as the central components on larger automated systems which provide extended walkaway time for users.
  • Plate Movers – Essentially bench top robots that are specifically designed to transport KiNEDxmicroplates.  Unlike more flexible industrial robots, these units are pre-tooled for handling microplates and  come with plate gripper hands and plate storage racks.  Plate Movers generally have a simple software interface for teaching plate locations so users don’t have to deal with the vast command sets that come with more flexible robots.
  • Industrial Robots – While designed for a host of applications from electrical/mechanical manufacturing to painting, weldinstaublig and sorting, a number of industrial strength robots can be found at the heart of fully integrated systems.  Generally chosen for their extended reach, these highly sophisticated devices use a small subset of their potential for moving plate between storage devices and instruments at slower speeds than might be found in other applications.

All of these devices are approaching commodity status is the life science markets (drug discovery, genomics, proteomics…etc) which means that their prices are dropping and their ease-of-use is increasing, resulting in faster adoption and deployment.   And while it may be obvious to most,  several of the main reasons for automating lab applications remain constants over time;

  • Increased Throughput – process more samples without human intervention.  This makes lab workers more productive by freeing up time to work on other critical tasks.
  • Repeatability – many lab techs can pipette just as good as any liquid handler, however pipetting is time consuming and its repetitive nature can make it an error-prone operation.   Liquid handling robots largely eliminate human variability and human error, resulting in more reliable data (that’s the whole point of an assay, n’est pas?)
  • Human Safety – Operator exposure to dangerous pathogens, reagents  or radioactive chemistry can be minimized with automation.   (think the garlic smell of DMSO to skin exposure…maybe not life threatening, but certainly a potential social stigma…)
  • Assay Integrity – While human safety is a major concern for many labs, protecting assay integrity  is equally important.  Environmental enclosures around automation helps minimize assay contamination due to human interaction

For more information’

Liquid Handlers;

Plate Movers;

Industrial Robots;