Alphabet Shakes Up Its Robotics Division
nytimes.com
nytimes.com
Karl Benz invented the 'first automobile' in 1885 [0]. 29 years later, in 1914, Ford built the first mass-production factory for his autos. It initially produced 4 cars/hour, an annual rate of about 15,000. In 1915, there were 8,000 cars in all of the US. [1]
I cannot find data, but let's guess that it's 10 more years before 1% of households in the US have cars. That would have meant about 500,000 cars.
1885 - 1925 is 40 years between invention of the first gas powered auto and 1% market penetration (bearing my assumption). Where was the robotics industry in 1976, 40 years ago?
Moreover, the automobile solved one problem: Moving a human from point A to point B on a paved road. Many efforts are approaching robots as consumer products by trying to solve many very hard problems all at the same time. Perhaps robotic vacuums are the (only?) successful commercial robot because they solve a similarly discrete problem.
It is understandable that we have not yet seen the type of commercial breakthroughs that we so highly anticipate. Give it another 20 years...
[0] https://en.wikipedia.org/wiki/Car#History
[1] http://www.thejournal-news.net/opinion/commentary/here-s-loo...
https://hbr.org/2013/11/the-pace-of-technology-adoption-is-s...
is an interesting graph. Historically a lot of consumer tech took a long time to be adopted.
Universal robots, ones that can do basically any task that any human can do are not even on the drawing board right now, so we're limited to these application specific models but where they are engaged they are incredibly effective and have all but replaced the humans that did those jobs previously.
The reason often quoted is that this is because robots can work 24x7, won't unionize and so on, but the little fact that people usually miss is that repeat accuracy is a very important factor in reducing part and product failure so betting on robots means that you get a much more reliable and consistent product out the door saving you a fortune in re-work and warranty claims.
That is a very good point, the other factor is that robots can collect massive amounts of data faster and more accurately than their human counter parts.
"1974: The world's first microcomputer controlled electric industrial robot, IRB 6 from ASEA, was delivered to a small mechanical engineering company in southern Sweden"
Here's a cute video showing this robot, still in use 40 years later:
Mowing lawns is the other obvious task that falls into this category and, indeed, robotic lawnmowers do seem to be coming onto the market.
Ford produced 500,000 Model T's from 1908-1914, and 500,000 in 1916 alone. While they didn't all sell in the US, with 1.3 million T's produced, it's safe to say they sold half a million cars in the US by 1916.
That bumps your 40 year estimate down to 30.
(And yes I realize these tasks involve surprisingly hard AI problems, but why isn't Google already running pilots where they give people special washing machines, laundry machines, robot-friendly book shelves, etc etc that help mitigate the hard AI aspects of the problem?)
It's interesting when I meet people I can smell who has left their clothes in the washer too long.
But as someone else said, that's probably the step associated with doing laundry that's the least effort. Putting clothes away is the biggest effort and good luck designing a robot to handle that.
The kind of butler robot we can make today [3] would seem extremely expensive for the functionality it could offer, making it hard get the sales needed to recoup your up front engineering costs - let alone to achieve the economies of scale needed to bring down the price on those sensors.
[1] http://www.robotshop.com/en/hokuyo-urg-04lx-ug01-scanning-la... [2] http://www.newark.com/xsens/mti-20-2a5g4/mems-module-3d-moti... [3] https://www.youtube.com/watch?v=tODGHw8uNnY
It's a lot cheaper than it used to be. When we did our DARPA Grand Challenge vehicle ten years ago, we had about 3 degrees of heading noise, which kept the system which integrated LIDAR data into a terrain map from reliably mapping. The system had a MEMS gyro with too high a drift rate, and a magnetometer compass for long-term correction. But there were enough magnetic fields from the onboard equipment to mess up the magnetic compass. The software could detect trouble, and would stop, tilt the laser head to scan the terrain ahead and get a clean image, then advance. So the vehicle kept stopping to rescan.
We looked into better heading gyros, but they cost about $20K at the time.
Applications for IMUs include dead reckoning (working out your position based on rotation and acceleration measurements), orientation sensing (figuring out which way is down is much easier than dead reckoning, because you can just sense gravity), and compensating sensor readings for robot motion.
Some cheap sensors aren't very precise; you won't notice if your phone thinks it's rotating two degrees a minute around the vertical axis, but a robot will if it moves for five minutes then it's ten degrees off course. I haven't looked at the market for a long time - I suspect the cheaper IMUs are better nowerdays. Eight years ago they didn't offer very good precision and the open source software could be very fiddly to get working, if you could get it working at all.
The OXTS RT3000 has impressive specs - 1cm accuracy in world coordinates. That's better than you need for most robotics applications that aren't running blind. The Trimble AP10 [2] has the same functionality at much lower cost, but is not as accurate.
A lot of progress in robotics comes from component improvement like this. There was a time when just getting a wireless data link to your robot was a big deal.
[1] http://www.analog.com/en/products/mems/mems-gyroscopes/adxrs... [2] http://www.trimble.com/gnss-inertial/AP10.aspx?dtID
I basically have zero confidence that we'll see something like what you are describing in next 2 decades atleast.
Consumer robotics doesn't have much of an entry barrier but as other have pointed out the components you need mean that prices are going to be in the $X0,000 range. That's too much for consumers but I think we're going to be seeing robots in warehouses soon.
If I were a car manufacturer and nobody wanted to buy my cars because they were seen as dangerous, I might try to make my cars safer to increase my sales, even if the law didn't require it.
Because the line of how much is too much is indistinct, someone is going to guess wrong before too long. This is even before you mix in perverse organizational incentives involving short-term view or individual profit vs long-term company health.
I also think that not enough thought has been put into the question of: if we do manage to replace unskilled workers with robots, what do we do with all the people who are only capable of unskilled work? Not everyone has what it takes to become a coder.
Seriously? I can rent a human for $7.50 an hour. In other countries they're even cheaper. If you want to sell me a robot to clean my house, that's your competition.
Yes, in the very long run, assuming relatively unchanging tasks and capacity demand.
But most jobs aren't like that - industrial robotics are dominated by robots that are purpose-designed with a singular task in mind, with a narrow envelope for deviations. A human can be re-trained to do something completely different than before, whereas a robot would likely have to receive completely new hardware. A welding robot cannot become a precision fan-balancing robot, but a human can be retrained from one task to another.
It's cheaper to train a large group of humans to do something different than it is to upgrade the hardware & software on the same number of robots.
This means that some jobs (see: automotive manufacturing) lend themselves easily to robotics - the throughput is steady, the capacity requirements are stable (i.e., you don't suddenly need 5x more cars in July than in March), and even between different models the general process is the same.
Other jobs (see: warehousing, shipping) do not lend themselves to robotics easily - the job changes regularly as processes evolve, the capacity requirements are chaotic (i.e., you need to scale to 10x your normal throughput during Xmas), and there is significant variation in process requirements (e.g., Japanese retail warehouses that run vertically instead of horizontally).
Robots are also still astonishingly expensive and largely made-to-order with long lead times. This means that it takes many years to break even on a robot (whereas you can fire the human when you don't need them), and you can scale easily with humans (it's much quicker to find a human than it is to order and receive a robot).
"Why are they against militarizing robots? It pays the bills. They could start with consumers or business but it's harder to build a market. This makes it harder to fund further development. Once the technology is developed by anyone for non-military use, transitioning to the military is easy. There's not some magic that prevents consumer developed technology from reaching the battlefield."
I highly doubt Google is interested in that revenue stream. Google doesn't just want to pay the bills -- and it doesn't need to. It wants to develop entirely new businesses that complement its existing ones, e.g. Nest.
Also, it's bad for the brand. There are probably not many companies that sell both weapons and consumer goods...
I get that their duty is to their shareholders, but you have to draw a line at some point. I wouldn't want to work on tools of violence.
Rethink Robotics for example had a great start, but soon ran into cultural issues and weaker than expected sales. iRobot has been unable to escape the vacuum cleaner market. KUKA and the other really big industrial robot manufactures have started doing new things with sensor-enabled manipulators, but the customers haven't exactly flocked.
What is it about robotics that seems to run these companies off the rails? I worry about Fetch robotics hitting a similar barrier, despite having a pretty clear business case.
In the consumer space.
iRobot has a healthy relationship with the Defense Department.
To even get off the ground, you need strong people in each of the three pillars. Additionally, you need a leader who is sufficiently knowledgeable across all three pillars. Purely from an HR/talent acquisition perspective, this is difficult logistically and financially. Uber raided NREC to accomplish this, essentially creating a second headquarters, and paid quite a bit to get the talent.
Then, you need a prototyping facility for both the ME/EEs.
To start from scratch, a very hefty investment has to be made before product development has even begun. Then you're bleeding money through the product development phase (hopefully with some pre-sales, but odds are pretty low of this). After product development, you hit manufacturing, which is extremely difficult. Bolt.io has some good reading on this.
To get to a product driving around, you've spent millions over the course of a year or two. To amortize that cost in a reasonable fashion, you've got to produce thousands of units. Fanuc took over manufacturing early on and was able to accomplish this, but for a lot of companies, the sales volume just isn't going to be there.
The DoD, with SBIRs and other long term contracts, helps fund a lot of the product development, often provides you with a paying customer, etc. The risk and amount of monetary bleeding drops significantly as soon as you partner with the DoD.
[1] Shameless plug http://www.righthandrobotics.com/
I don't see the problem with it. It's not like YCombinator or other VCs are going to pay for years and years of research.
The DoD can afford to throw money at robotics projects and fund the grunt work of getting the technology developed. Spending a billion dollars researching and developing a walking robot or whatever is a great use of money if it means keeping a bunch of humans out of dangerous situations.
For everybody else it's a cool idea, but not useful enough that they'd pay for it. Better to let DoD pay for it, and wait until that technology makes it into other products.
(I liked the idea, but after calculating how big our property was, only the most expensive commercial lawnmower robot reached parity with our John Deere Z-track riding lawn mower's capabilities, and the payback period was implausibly long, so I'm stuck doing the mowing myself. For now.)
But I can see the attraction if someone had a smallish lawn--especially if they didn't already have a lawn mower. It would be just one more task they wouldn't have to think about.
The two you mentioned (smaller lawns and higher labor costs) are the biggest drivers though.
I lead a team working on these for a major outdoor power equipment company, so I'm more than happy to chat.
Alphabet is so secretive that no one can tell from the outside if they're doing something great or getting nowhere. Boston Dynamics stopped updating their web site after the Google acquisition. Schaft has no visible web presence at all. Raibert, Boston Dynamics' CEO, is 67, time to retire. Who replaces him?
Good thing it was only Google that had to abide by the "don't be evil" mantra (more or less). Alphabet apparently could care less about it.