How often have you wished that you could tweak the vendor-supplied software that came with your commercial-off-the-shelf laboratory automation system, in order to better suit your specific needs?  Just like the way you "tweak" the hamburger your order at your favorite restaurant.   It's a given that commercial software isn't going to be a glove-fit for everyone.  If your need for customization is acute, you may be able to pay the vendor or a 3^rd party integrator to write custom software for you, but you're unlikely to be given (or sold) the vendor's source code to tinker with yourself.  This isn't a knock on the vendors, either.  They can't be expected to be eager to release source code, or support code customized by someone other than their programmers.  Nor can they afford to develop (or you afford to buy) software that covers all wants and needs.

When programmers felt hemmed in by commercial operating systems back in 1983, the open-source software movement was born.  Open source software is developed by a community of developers and users, with source code open to all and royalty-free licensing.  The "community" develops, modifies and evolves open-source software over time. The GNU project is the best known of these early efforts, focused on creating a non-Unix, but Unix-like OS (GNU stands for Gnu's Not Unix).  Through some twists and turns, this movement eventually led in the 1990's the creation of the Linux open-source operating system (or GNU/Linux if you're into the debate of who should get credit).  From humble beginnings, Linux can now functions as the OS of choice for large server farms sold by the likes of HP, Dell, IBM and Sun, as well as for the TiVo device sitting under the LabMan's television.  If the LabMan wanted to install Linux on his PC, it'd be free, and it'd be open for me to modify in any way I desired - perhaps to make it cat-friendly?  I'd then be free to contribute that modification back to the community, where it'd no doubt be wildly popular! 

So, what if that same open-source movement caught on in the laboratory automation field?  Would it open the door to cheap, easy to create, custom-fit software for your special lab automation needs?  Neil Benn thinks so.

Neil has founded the Open Lab Automation Project, via his company Ziath.  Neil thinks that today's commercial laboratory automation has finally become electromechanically reliable and mature, so it's time to focus on software.  Through this project, he plans to develop open-source instrumental communication code, instrument drivers, schedulers and GUI interfaces.  The eventual goal is to provide a toolbox of code that the lab automation community can mix, match and modify to fit their specific needs.  He envisions the project to be "agile", meaning avoiding large pieces of code, large standards and lengthy documentation. 

His biggest technical challenge to date has been the lack of implemented equipment control or interface standards across the various technology providers.  They all do it differently.  Neil hopes to use his project to implement some of the elements of existing and proposed laboratory automation standards, such as LECIS, acting essentially as reference implementation for these standards. 

You can keep track of Neil via his blog, LabAuto Lounge, and find his latest contact information there.  If you have time, resources, expertise or equipment to donate to the project, get in touch.  Best wishes for success.    

Until Next time,

Domo Arigato, Mr. Roboto!