Hey there, human — the robots need you! Vote for IEEE’s Robots Guide in the Webby Awards.

Close bar

iRobot and Willow Garage Debate Closed vs. Open Source Robotics at Cocktail Party

What's the best approach to building commercially successful robotics companies: To develop specific, proprietary products or to create and share free, open-source technologies?

4 min read

In this guest post, Frank Tobe, a robotics analyst and publisher of The Robot Report, describes a recent debate between two prominent robotics executives and their opposing views on how to nurture profitable robotics businesses.

What's the best approach to building commercially successful robotics companies: To develop specific, proprietary products that satisfy the needs of large markets, or to develop and share free, open-source technologies and wait for the commercial applications to emerge?

These two points of view were presented by executives from iRobot and Willow Garage in a spirited cocktail party debate the other evening in Lyon, France, at InnoRobo 2012, a trade show for service robotics. Here's how it happened, who they were, and what they said.

Colin Angle, co-founder and CEO of iRobot, was one of the InnoRobo keynote speakers, and after his presentation (about the need for robotic solutions in healthcare), I met him for an interview. I asked him, among other things, what he thought about Willow Garage's Robot Operating System (ROS) open source software strategy. Angle said he thought it was dangerous to the industry and was fearful that it was also detrimental to the monetizing of the service robotics sector in particular.

Later that day I was talking with another presenter, Robert Bauer, the executive director for commercialization at Willow Garage. In his talk, Bauer made the point that, when it comes to robotics, hardware was farther along than software and therefore application software was where the robotics industry needed help. When I told Bauer what Angle had said, Bauer became feisty and said he'd love to debate Angle as to which approach contributed more to product development and commercialization.

iRobot Colin Angle, Willow Garage Bob BauerLeft: Colin Angle, co-founder and CEO of iRobot, in Bedford, Mass. Right: Robert Bauer, executive director for commercialization at Willow Garage in Menlo Park, Calif.

I thought a debate would be great. I just didn't know it would happen just a few hours later, at a cocktail party that same evening. I was casually talking with Bauer when Angle came by to say hello. I introduced them to each other -- and the fun began.

Angle suggested that Willow Garage's approach of freely providing such a key component as the robotic operating system -- and the extensive libraries that go with ROS, not to mention its source code -- was tantamount to letting the biggest consumer electronics giants gobble up any mass market applications and re-market them globally at low cost because they already have (or could easily reverse-engineer) the hardware, could produce it cheaply, the operating system was free courtesy of ROS, and the only real cost was the acquisition of the application.

Angle thought that the approach was dangerous and led to losing a potentially U.S./European market to offshore commodity conglomerates. (The dangers of losing trade secrets to foreign conglomerates was the subject of a recent Bloomberg Businessweek issue.) He added, "Robotics innovation represents a tremendous opportunity for economic growth akin to automobiles, aerospace, and information technology. If we are to freely share our 'intellectual capital' on the open market we risk losing the economic engine that will advance our economies and send growth and jobs overseas."

It was Bauer's turn now, and he argued that Willow Garage's objectives were to stimulate the industry by enabling participants to not have to reinvent the many cross-science elements of robotics ventures; to reuse software under the premise that by so doing it saves developer time and allows researchers to focus on research. By giving them free access to the tools, libraries, and simulation capabilities of ROS, Willow Garage hopes to advance the state-of-the-art in autonomous robotics technologies -- and the commercial applications will follow.

Bauer also said that, once a successful application was developed, then the new endeavor would likely lock down the operating system and application software in order to protect their invention.

Angle responded by suggesting that ROS itself could be locked down, protected, and commercialized -- and that it should be done right away. What the robotics industry needs, he said, is successful robotics companies -- profitable companies selling in-demand products and rewarding employees and investors. (This week, Amazon acquired Kiva Systems, a provider of warehouse robotic system, for $775 million.) That could happen if ROS "privatized;" What's more, he added, unless ROS is protected and made stable and secure, it could never be used for sensitive (defense, space, security) solutions, and until it became rugged, secure, and stable, it could never be used in factories that cannot afford down time from their robots or software.

He said it would make him happy if all the people that displayed their robots at InnoRobo were successful and wealthy, but that the opposite was more likely because the right big-market robotic applications hadn't happened just yet.

The discussion went on and ended with Bauer inviting Angle to continue the discussion onsite at Willow Garage and Angle agreeing to do it.

I hope I have presented the two positions fairly because I think that both sides have merit. Using the analogy that developing apps for smartphones and tablets is similar to developing applications for service robots in the open source community of shared libraries, imagine how much talent is being squandered in the whimsy of making a "fun app"? Do we have to sift through the chaos and diversity of thousands of apps to find the few -- if any -- that are suitable for real business tasks? Or would we be better served to rethink how we satisfy real needs by building specific products to satisfy those needs?

What do you think?

The Conversation (0)