Tuesday, November 2, 2010

Becoming the Microsoft of the Robot World

Robots have become increasingly important in the manufacturing world. Companies such as General Motors rely on them to create the most modern and reliable products in the fastest and most efficient manner. Many people fear that they will replace human workers in the manufacturing industry and eliminate jobs, although companies have proved that this is not the case. In fact, the use of robots has actually opened up new jobs, and the need for human workers to work alongside robots still exists. A new GM plant contains over 1,100 robots, but GM is still looking to hire back some of its laid-off employees to keep up with the growing demand of new cars.

Since robots are in such high demand and have been proven to open up new jobs, (people are needed to design, build, program, and service robots) an even bigger opportunity for programmers has arisen. Approximately 8.6 robots exist today, and most of them have been designed from scratch, as stated by the article, “Becoming the Microsoft of the Robot World.” The article goes on to say that creators of these robots have basically reinvented the wheel each time a new robot is created. The hardware and code, which drives the robots’ actions, is designed anew with each new robot.

This provides an opportunity to make an enormous profit for whatever company can become the “Microsoft of the robotic world.” Companies are competing to see who can have the dominant operating system for robots. It will be a standard system that can be used and adapted for any robotic needs. The lack of a standard is inhibiting progress with robots and it is lowering revenues for companies that produce them, since each one is so expensive to make.

Right now, there are several companies, such as Microsoft and Evolution Robotics, who have released operating software for robots. Another company is trying to create an open-source robot operating system. For it to be open-source, it was have to be “non-dedicated as to use, nondiscriminatory as to software, and modular in design.” This system, which is being created by a former Google employee, is meant to be able to be used by the entire robotics industry. However, it cannot be used to household robots. It is meant to be used by researchers who need robots with massive processing power. For tinier robots, this open-source does not necessarily make sense.

Other researchers have also considered creating open-source hardware. People with access to laser cutters would be able to download the designs and create the hardware for robots themselves.

As profitable as the open-source software systems would be for whichever company can design it, there are downsides. For example, these systems would be more vulnerable to hackers. They would have to rely on more safety controls than software alone. It also would not make sense for smaller robots with less computing capacity. Its benefits would be limited to larger, more complicated robotic systems.

http://www.businessweek.com/technology/content/nov2010/tc2010111_884564_page_2.htm

http://www.businessweek.com/technology/content/may2010/tc20100526_198981.htm?chan=technology_special+report+--+ceo+guide+to+robots+in+the+workplace_special+report%3A+ceo+guide+to+robots+in+the+workplace

Eileen Browne

No comments: