Wednesday, June 25, 2014

Aereo ruled illegal by Supreme Court; must pay copyright fees (ZDNet)

Summary: The future of Internet TV was decided by the U.S. Supreme Court. And it didn't go in cordcutters' favor.

By  for Networking |
supreme-court
Supreme Court

By a six-to-three vote, the U.S. Supreme Court reversed the decision of the US Second District Court in ABC vs. Aereo.
The bottom line: The Supreme Court has ruled that Aereo's over-the-air (OTA) TV over the Internet service is illegal.
According to the SCOTUSblog, "This ruling appears sweeping and definitive, determining that Aereo is illegal." At the same time, the Court claimed that "its ruling does not endanger other technologies." How that can be is an open question. Aereo had claimed that a decision against them might endanger other cloud-based media services.
It appears, however, that "the essence of the Aereo ruling is that Aereo is equivalent to a cable company, not merely an equipment provider." That, according to the court's decision, Aereo's "behind-the-scenes technological differences do not distinguish Aereo's system from cable systems, which do perform publicly."
Aereo was a service that lets you watch over-the-air TV over the Internet for $8 per month. It offered you the same network television shows that are available to anyone with an antenna. To do this, Aereo sets up clusters of miniature antennas in your local area.
For example, If you lived in New York, you'd be able to watch WABC, WCBS, and WNBC; when and if Aereo had expanded to in to Washington, you would have been able to watch WJLA, WUSA, and WRC; and so on.
When you signed up for the service, you were assigned two of those antennas. One is for watching live shows and the other is for recording programs. Your chosen local OTA shows are then also kept in cloud-based digital video recorder (DVR).
"This ruling appears sweeping and definitive, determining that Aereo is illegal."
This isn't just cloud DVR, though. Whether you were watching a "live" show or a recorded one, you're creating, the company stated, "three separate unique copies of the show, each in a different bit rate optimized for different streaming conditions. The lowest bit rate file is ideal for streaming over 3G connections. The medium rate file will work well over most Wi-Fi connections. The highest rate file is intended for really fast broadband connections. While watching, you can choose the video quality on your device. If you select 'auto', you will automatically choose the best bitrate for your current network conditions."
At the time of the decision, Aereo was available in eleven Eastern and Midwest cities. The company had had plans to offer its services in 19 more US cities.
ABC and other networks — including CBS, the parent company of ZDNet and sister-site CNET — had argued that Aereo was violating copyright by retransmitting their signals over the Internet. Legally, the question in ABC vs. Aereo is whether Aereo "publicly performs" a copyrighted television program when it retransmits a broadcast of that program to paid subscribers over the Internet.
Aereo's counter-argument was that, in essence, all they're doing is renting you an antenna with a very, very long cable that just happens to go over the Internet. Since Aereo will only let you watch network shows that are available from your local OTA TV stations, their position was that the company was not violating any copyright or retransmission laws. As for offering a DVR service, Aereo argued that the case of 20th Century Fox vs. Cablevisionhad already shown that remote Internet-based DVRs were legal.
In addition, Aereo argued that a strike against them is a blow against all cloud media storage. The Supreme Court disagreed on both counts. 
What happens now? Good question.
Is Aereo out of business now? The company has always insisted that if its loses it has no alternative plan.
On the other hand, in Fortune, Aereo CEO Chet Kanojia "suggested that Aereo could explore several alternate options in the case of a loss, including perhaps even paying some sort of retransmission fees to broadcasters." This appears to be Aereo's only option for the business to survive.
Whether the networks would agree to such a deal is another question. While, the networks have never been averse to making more money, they all disliked both Aereo's model and their persistence in pushing it through the courts. Still, sooner rather than later the networks must come to terms with the cordcutters in a more sensible way than their current mishmash of network specific Web sites and rerun-specific deals with Amazon, Hulu, and Netflix.
Steven J. Vaughan-Nichols, aka sjvn, has been writing about technology and the business of technology since CP/M-80 was the cutting edge PC operating system. SJVN covers networking, Linux, open source, and operating systems.

Tuesday, June 24, 2014

Wearable computing: Trends

The explosion of interest in wearable computing is one of tech's fastest rising trends. While big moves from Google, Apple, and Samsung will likely attract a lot of attention, we're going to examine the broader potential that wearables hold for driving innovation in business.
1.- Wearables: An emerging trend with staying power
Summary: Wearable tech, from Google Glass to Fitbit, Jawbone and other devices, is garnering plenty of attention. Here’s what lies ahead for the industry. More:


2.- Research: 92 percent are interested in wearables
Summary: The future of wearables in the enterprise was the subject of the latest Tech Pro Research survey. Find out who is using these devices, and how. More:


3.- Executive's guide to wearable computing in business (free ebook)
Summary: Wearable tech may have begun as a consumer novelty, but now we're beginning to see devices that offer solid business value. This ZDNet/TechRepublic guide looks at how wearable computing is being implemented now — and what you can expect in the near future. More:

4.-Wearables in business: Five companies getting real work done

Summary: Wearables are still trying to win over consumers, but they have made strides in the enterprise. Here are five companies using wearables to add value to their business. More:

http://www.zdnet.com/wearables-in-business-five-companies-getting-real-work-done-7000030082/

5.- The History of Wearable Technology: A timeline

Summary: Humans have always adorned their bodies with gadgetry — be it for show, for utility, or both. Our timeline documents examples such as body armour, spectacles, wearable calculating aids, hearing aids, diving gear, spacesuits, exoskeletons and experiments in human-machine 'cyborgs'. More:

http://www.zdnet.com/the-history-of-wearable-technology-a-timeline-7000030090/

6.- Wearables: The ones we use versus the ones we really want

Summary: There's a gap between the wearable tech that gets the most hype and the ones that actually get used, and the ones that are used versus the ones people really want. More:

Thursday, June 19, 2014

GM Recalls: How General Motors Silenced a Whistle-Blower (BusinessWeek)

In 2006 the wreck of a 2005 Cobalt killed two and injured one
In 2006 the wreck of a 2005 Cobalt killed two and injured one
It was close to 3 a.m. on June 6 when Courtland Kelley burst into his bedroom, startling his wife awake. General Motors (GM), Kelley’s employer for more than 30 years, had just released the results of an investigation into how a flawed ignition switch in the Chevrolet Cobalt could easily slip into the “off” position—cutting power, stalling the engine, and disabling airbags just when they’re needed most. The part has been linked to at least 13 deaths and 54 crashes. GM Chief Executive Officer Mary Barra, summoned before Congress in April to answer for the crisis, repeatedly declined to answer lawmakers’ questions before she had the company’s inquest in hand. Now it was out, and Kelley had stayed up to read all 325 pages on a laptop on the back porch of his rural home about 90 miles northwest of Detroit.

The “Valukas Report,” named for former U.S. Attorney Anton Valukas, who assembled it at GM’s request from interviews with 230 witnesses and 41 million documents, blamed a culture of complacency for the more than decade-long delay before the company recalled millions of faulty vehicles. It described employees passing the buck and committees falling back on the “GM nod”—when everyone in a meeting agrees that something should happen, and no one actually does it. On page 93, a GM safety inspector named Steven Oakley is quoted telling investigators that he was too afraid to insist on safety concerns with the Cobalt after seeing his predecessor “pushed out of the job for doing just that.” Reading the passage, Kelley felt like he’d been punched in the gut. The predecessor Oakley was talking about was Kelley.

Kelley had sued GM in 2003, alleging that the company had dragged its feet addressing dangers in its cars and trucks. Even though he lost, Kelley thought that by blowing the whistle he’d done the right thing and paved the way for other GMers to speak up. Now he saw that he’d had the opposite impact: His loss, and the way his career had stalled afterward, taught others at the company to stay quiet. “He stood in the doorway of our bedroom with a stunned look on his face,” Beth Kelley, his wife of 23 years, says. “Maybe we’re just extremely naive, but we really thought that since this all happened, that something good would come out of it.” Kelley declined to comment for this article, but his allegations are laid out in court records and depositions. A number of friends and family did speak for the record.

Kelley had been the head of a nationwide GM inspection program and then the quality manager for the Cobalt’s predecessor, the Cavalier. He found flaws and reported them, over and over, and repeatedly found his colleagues’ and supervisors’ responses wanting. He thought they were more concerned with maintaining their bureaucracies and avoiding expensive recalls than with stopping the sale of dangerous cars. Eventually, Kelley threatened to take his concerns to the National Highway Traffic Safety Administration. Frustrated with the limited scope of a recall of sport-utility vehicles in 2002, he sued GM under a Michigan whistle-blower law. GM denied wrongdoing, and the case was dismissed on procedural grounds. Kelley’s career went into hibernation; he was sent to work in another part of the company, and GM kept producing its cars.
Selling for around $16,000, Cobalts were popular with teenagers. The first death linked to its switch came in July 2005, when a Maryland 16-year-old, Amber Marie Rose, crashed her red ’05 into a tree. The airbag did not deploy. Although reports streamed into GM about moving stalls and disabled airbags for years, the company waited until Feb. 13, 2014, to issue a recall.
Now GM professes contrition, promises change, and has ousted 15 individuals for misconduct or incompetence. Announcing the Valukas findings to an audience of employees on June 5, Barra called the report “extremely thorough, brutally tough, and deeply troubling.” It describes a corporate bureaucracy fatally indifferent to mounting evidence its cars were killing people. “Group after group and committee after committee within GM that reviewed the issue failed to take action or acted too slowly,” Valukas writes. “Although everyone had responsibility to fix the problem, nobody took responsibility.”
Photographs by National Highway Traffic Safety Administration/ The New York Times/Redux; St Croix Sheriff/Reuters


As bad as that sounds, Kelley’s story shows that the situation was worse—that GM’s problems went beyond diffuse inaction. Management wasn’t just distracted or confused; speaking up was actively discouraged, and workers saw that pointing out safety flaws could derail their careers. When a GM employee did blow the whistle, the nation’s largest automaker shut him down. 
 
Kelley is mild-mannered and 52, with a full head of white hair that makes him look older. His friends, who know him as Court, joke that they should make bracelets reading “WWCD?”—or “What would Court do?”—à la the popular Christian accessory. “He’s just one of those people that you can trust what he says,” his wife says. “I don’t have any doubt in his decisions.”

Kelley is third-generation GM. His father and grandfather worked for the company. A prized possession is a ring his grand­father was given commemorating his participation in the famed Sit-Down Strike of 1936-37. In his driveway is a black Pontiac Fiero sports car that Kelley and his teenage son, Ryan, fixed up.
In 1983, Kelley started at GM as a technician fresh out of community college. By 1988 he was working on what would become the company’s Global Delivery Survey, an audit of GM cars at rail yards across the country—a spot check of vehicles on the last leg of their journey to dealerships. Originally meant to find minor noises and rattles, the program had begun to turn up more serious safety concerns. The creator of the effort, Bill McAleer, considered Kelley his protégé and someone who shared his alarm at the problems they found over the next decade—such as tie rods in danger of falling off.
“Bill and I looked at each other in amazement,” Kelley later recalled in a deposition, “that that kind of thing was happening, where the bolts on the front suspension fell out as we drove over the track. I thought that GM alarm bells would go off.”
They didn’t. McAleer, who thought no one at GM was taking his criticisms seriously, was taken off the audit; he sued the company seeking whistle-blower protection. GM denied the allegations, and a judge dismissed the case. With McAleer gone, Kelley grew even more concerned about the problems he was seeing, he said in a June 2000 deposition from McAleer’s lawsuit. He indicated that the audit was picking up an average of two to three “significant safety defects” each month. In May of that year, Kelley told lawyers, the audit found three problems, including a vehicle in Flint, Mich., with its antilock brakes improperly attached and a vehicle in Lansing with a fuel leak. McAleer’s lawsuit claimed that as much as 1 percent of all vehicles manufactured by GM during the 1999 model year could be defective, or more than 30,000 North American cars and trucks.
Kelley said he approached his direct supervisor, George Kingston, who in 2000 was director of quality for North American operations, about his growing concerns. “I would go to George and tell him this, but it didn’t seem to surprise him or provoke him to take new action,” Kelley said in his deposition. “He seemed to take it more seriously when I told him that I could no longer sit by and I may have to personally go to the federal government.” The response? “He cringed,” Kelley said, “and said that he would prefer that I don’t do that.” Kelley gave Kingston 60 days to act but in the end didn’t alert regulators. Kingston did not respond to a request for comment.
In September 2000, Kelley would later allege in court filings, Kingston instructed Kelley not to give McAleer, still a GM employee at the time, any data on serious defects that the audit program turned up. “Kingston indicated that he just returned from a meeting in which depositions taken in the McAleer litigation and questions being posed to GM by the media about litigation had been discussed,” Kelley’s lawsuit said. Kingston told Kelley “that high-­level GM staff and the company’s general counsel were involved in the teleconference and that these individuals were irate.” Kingston allegedly told Kelley that he was concerned that “higher-ranking executives might want to make things difficult” for Kelley—perhaps banishing him to the “second shift at Hamtramck,” a plant on the outskirts of Detroit.
While his troubles at work intensified, Kelley’s home life blossomed. He and his wife were raising two children, and they purchased a white two-story home on a tree-lined street in sleepy Owosso, Mich. Kelley remained loyal to his employer. As he saw it, he was agitating not to harm the company or enrich himself but to save it—and because it was the right thing to do. Neighbor Fred Van Alstine, a doctor whose father worked in a GM factory, remembers talking with Kelley around this time and inadvertently slighting the automaker. He recalls Kelley taking offense and saying, “I’m proud to be at GM.”
 
One day in November 2001, Kelley came across a problem that would forever change him. Making inspections at a rail yard in Tampa, he found a Chevrolet TrailBlazer SUV leaking fuel. Kelley discovered that the fuel line had disconnected at the filter. “They told me as they were driving it off the train, the vehicle quit,” Kelley recalled in a September 2003 deposition. “Fuel began spraying.” The next day, he began getting similar reports from around the country. He began pushing not only his supervisor but product investigators and GM’s legal department to act.

Kelley thought it was just a matter of time before someone was injured or killed. “I became aware of police reports, police stating that they thought the person would have been severely injured had a spark occurred and ignited the fuel,” Kelley said in a deposition. “I became aware of fire departments being involved because of the severity of the fuel leaks.” Despite his concerns, he said, colleagues resisted contacting the government. During a Nov. 27, 2001, conference call with GM engineers, Kelley wrote in his notes, “No NHTSA contact yet.”
“At this point, I knew it was big enough that—where we could not, in my opinion, not report it,” Kelley said in a deposition. “I heard them have many discussions about not wanting to notify the government, not putting voice mails out to dealers, because the government could get them.”
By December, Kelley thought he knew what was causing the problem: The TrailBlazer’s fuel-line quick-connect fasteners weren’t the proper size. He had photos of nine vehicles with leaking fuel. That month, he clashed with a product investigator named C.J. Martin who had turned up fewer “serious quality incidents” in her own probe, according to Kelley’s deposition testimony.
Kelley pushed Martin on the issue, he testified. “She became concerned that I was overly aggressive on how to fix the problem,” Kelley said. “Her response to me was, ‘Well, what do you want us to do, recall all the cars?’ ‘If that’s what needs to be done,’ I said, ‘yes, that’s what we should do.’ She said that would be way too expensive.”
Martin, who retired from GM in early 2002, says she vaguely remembers Kelley but disputes his claim that she resisted a recall. “I didn’t have that power nor that ability,” she says. She also disputes the notion that safety recalls were influenced by costs. “We were never allowed to show cost of an item in regard to making a decision for a safety recall—ever,” she says. That a recall was conducted in April after being flagged in November suggests to Martin that GM acted quickly, she says. “That’s extremely fast. If there was something that told us that there was anything related to safety, I can tell you that team in that period of time was extremely aggressive,” she says.
Photographs by James Fassinger/Corbis; J. Scott Applewhite/AP Photo
As 2002 began, Kelley’s crusade “gained significant momentum as a result of a vehicle line executive having experienced a ruptured fuel line on his own company vehicle while driving on the interstate,” according to his lawsuit. On April 30, 2002, GM sent the NHTSA a letter saying it was recalling 60,044 Chevrolet TrailBlazers, GMC Envoys, and Oldsmobile Bravadas, according to government records. Kelley felt vindicated—a moment of satisfaction that would prove fleeting.

Like his predecessor McAleer, Kelley was taken off the quality audit in 2002. He was transferred to a role as brand quality manager for the Chevrolet Cavalier and Pontiac Sunfire, compact cars that preceded the Cobalt. He was given an employee named Steven Oakley, who’d worked for GM since 1990, to handle the Sunfire. They were the middlemen between dealers, who wanted to talk about problems with cars, and engineers, who would work with factories to address those issues—and it was in this role that Kelley began hearing that the TrailBlazer recall had not gone far enough. Dealers complained that SUVs not covered by the recall were still leaking fuel. Kelley contacted one of GM’s field product investigators, employees who look into possible recall issues, and weeks later contacted him again. He got a listless response. “ ’I've done all I can,’ ” Kelley testified that the investigator told him. “ ’I wanted more vehicles recalled. They shot me down.’ ”
Kelley decided to escalate his campaign. In a June 17, 2002, memo addressed to his boss’s boss, Keith McKenzie, director of car brand quality, Kelley was direct. “It is my belief that General Motors is violating the law by not properly dealing with safety issues that are persistent and ongoing,” Kelley wrote. “I have spent several years trying to work through the system at General Motors to address these concerns with a goal of protecting our customers and stockholders.” McKenzie could not be reached for comment.
McKenzie stonewalled, according to Kelley. Instead of dealing with the complaint, he said, McKenzie warned him about another GM employee who had raised safety-related complaints and how it had derailed his career, the court filings show. Kelley agreed to tone down his memo, resubmitting a version that said GM was “not properly dealing with certain safety issues.” He again gave the company 60 days to address them or he’d go to “the proper law enforcement agencies.”
GM, in a court filing, said McKenzie reacted immediately to the memo, alerting his supervisor, who was “relieved but also extremely upset at [Kelley's] method of communication.” Sixty-three days later, GM expanded the TrailBlazer recall by 76,000 vehicles. Four days after that, Kelley said he was called into a meeting with McKenzie and Ron Porter, a GM lawyer, “in response to his letter of June 21.” Kelley was told he shouldn’t concern himself with defects on models other than the Cavalier. McKenzie told him vehicles had already been recalled and that more would be included in “direct response” to his concerns.
It was a mixed victory: Kelley got unsafe trucks off the road, but he was transferred that fall to another role, described in his testimony as “special assignment.” It was a GM version of purgatory. He had no job responsibilities, he claimed. In his new role, Kelley testified, he was instructed not to get involved with fuel-line connectors and instead was told to “come up with charts, predict warranty for the vehicle, but not find every problem that GM might have.”
 At home in Owosso, Kelley wrestled with taking his concerns public. After putting their kids to bed, Kelley and his wife would sit at their kitchen table and talk late into the night. Beth Kelley says she didn’t know then that GM retirees were telling her husband he might as well leave the company—that nobody goes against GM and survives. “He would say, ‘What do you think I should do?’ and, ‘Do you want to do this?’ ” she says now. “If he felt strongly enough that people could potentially die from the safety issue, then I didn’t have any doubt in my mind that we needed to do it.” On Jan. 9, 2003, he filed suit against GM.

Kelley’s allegations—which predated the ignition switch problems—made a small splash; Beth remembers the news crawling across CNN’s ticker. What little momentum there was faded as the challenges of fighting the nation’s largest automaker became apparent. GM argued for a judge to dismiss the case because Kelley did not have standing as a whistle-blower—the law required such a person to prove he had suffered for his actions, and Kelley still had a job with the company and was getting the same pay and benefits.
During a deposition, GM’s outside lawyer, Peter Kellett, pressed Kelley to admit that raising concerns about trucks wasn’t part of his job description, as an inspector of cars.
“My job assignment as a GM employee is to make sure that our customers are safe in any way I can. That’s my understanding,” Kelley said.
GM: “But was it your specific understanding that you were charged with responsibility for monitoring information relating to vehicles other than the [small cars]?”
Kelley: “I felt morally responsible—”
GM: “That’s not what I asked you.”
Kelley: “—to fix a problem that I found in a vehicle.”
GM: “Was it part of your job description?”
Kelley: “No.”
Kelley’s lawsuit didn’t get far. Court records show that his attorney didn’t appear at a hearing in April 2004, and the case was closed without a response from his lawyer. A later motion to reconsider was denied. Kelley’s lawyer, Rose Goff, became sick around this time, eventually dying of cancer. The Kelleys, who had spent more than $20,000 on legal fees, received a payment covering most of the cost from their lawyer’s insurance company because of the handling of the case, Beth says.
Courtland Kelley
Courtesy Beth Kelley Courtland Kelley
Courtland Kelley sank into depression. His dark brown hair turned snow-white in the span of a year. Van Alstine, the neighbor, who is also Kelley’s doctor, looked at his friend one day with astonishment. “I clearly saw him age drastically,” Van Alstine says. “You just knew he was under a tremendous amount of stress. … It shook him to the core.” Kelley couldn’t sleep at night, waking in cold sweats and experiencing chest pains and panic attacks, friends and records say.
His wife encouraged him to leave GM. He stayed for his family, she says. “He would always say, ‘You know, if I stay this amount of time, I’ll get my retirement,’” she says.
“Where else in that job market over the last 10 or 15 years is a person going to go?” says Van Alstine.
At GM, Kelley has been floating from position to position, says McAleer, who was laid off from GM in 2004 and keeps in close contact. “He still has a job—he doesn’t have a career,” he says. “He has no possibility of a promotion.”
As Kelley’s lawsuit petered out in 2004, GM was replacing the Cavalier with the Cobalt. Models produced from 2005 to 2007 contained the ignition switch that could easily slip out of the “on” position at the touch of a driver’s knee or simply from bumps in the road. Airbags failed to deploy in dozens of accidents. Amy Breen, 42, an Ohio preschool teacher, was killed in a 2007 crash, even though she was wearing her seat belt. Marie Sachse, 81, died when her Saturn Ion, which used the Cobalt’s ignition switch, left the road and struck a tree in Missouri in 2009. In June 2013, Dany Dubuc-Marquis, 23, of Quebec, lost control of his Cobalt and was pronounced dead at the scene. At GM, the mounting evidence caused little alarm. “Throughout the entire 11-year odyssey, there was no demonstrated sense of urgency, right to the very end,” Valukas, the former U.S. attorney, wrote in his report.
It is impossible to know what might have happened differently if Kelley had remained an inspector of GM’s small cars as it moved from Cavalier to Cobalt. He was replaced by his employee, Oakley, who in March 2005 reviewed a memo from a GM engineer on the Cobalt ignition. Interviewed three times by Valukas’s team, Oakley told investigators that he felt pressure to describe something as a convenience issue rather than a safety problem, and cited Kelley’s ordeal. GM declined to make Oakley available for comment.
Yet in one indirect way, Oakley tried to rouse concern. In a draft of a service bulletin to dealers, he included the term “stall,” a “hot” word known to attract attention. Had it actually gone out to car sellers, federal regulators would have most likely seen it. But as they had with Kelley three years before, GM’s product investigators tamped down the response, striking the language. It was one of the many occasions in which GM engineers failed to link the ignition switch position and disabled airbags, Valukas concluded. “From beginning to end, the story of the Cobalt is one of numerous failures leading to tragic results for many,” he wrote.
With the report out, CEO Barra was set to return to the House for more questions on June 18. While she has described the Valukas inquiry as thorough, she has also attempted to limit its implications. “In this case with these vehicles, we didn’t do our job,” Barra said in the June 5 employee town hall. “What the Valukas investigation uncovered—in this situation—is a pattern of incompetence and neglect.” Lawmakers may want to ask her whether the account of Courtland Kelley suggests the company’s problems go deeper.
On June 16, GM recalled an additional 3.16 million U.S. vehicles, across seven models, bringing the total recalled this year in North America to 20 million. “This latest recall raises even more questions about just how pervasive safety problems are at GM,” said Fred Upton (R-Mich.), chairman of the House Energy and Commerce Committee, in a statement. “This is not just a Cobalt problem.”
In response to questions from Bloomberg Businessweek, GM issued a statement on June 17: “We are going to reexamine Mr. Kelley’s employment claims as well as the safety concerns that he has, and that’s part of our redoubled effort to ensure customer safety.”
A week after her appalled husband woke her up in the middle of the night, Beth Kelley is sitting in her tidy kitchen, as her son, who’s changed his mind about becoming an engineer after watching his father’s tribulations, hovers nearby. Is she surprised that more whistle-blowers didn’t emerge at GM?
She laughs. “I’m surprised there aren’t more people who stand up for what they believe,” she says. “But am I surprised that they wouldn’t go against General Motors? I suppose not.”
Nick Summers covers Wall Street and finance for Bloomberg Businessweek. Twitter:@nicksummers.
Higgins is a reporter for Bloomberg News in Detroit

Wednesday, June 18, 2014

Inside the Secretive R&D Lab Behind the Amazon Phone (BusinessWeek)


Disclosure: Brad Stone is author of The Everything Store: Jeff Bezos and the Age of Amazon. The book is published by Little, Brown & Co., a division of the Hachette Book Group (MMB:FP), which is currently involved in a contract dispute with Amazon that is affecting the availability of The Everything Store and other Hachette books on the Amazon website.
On Wednesday, Amazon (AMZN) will release a smartphone. It’s a huge bet for the online retailer and, in the moment, a nice vindication for the product managers and hardware hackers at Lab126, Amazon’s secretive Silicon Valley hardware division.
More than 1,600 people claim Lab126 as their employer on the professional networking site LinkedIn (LNKD). Just a few months ago, Amazon investors might reasonably have demanded to know what those expensive engineers and product managers—and many others working on device hardware and software from Amazon’s offices in Seattle and in Cambridge, Mass.—were actually doing.
But this is turning out to be a big year for Lab126. Amazon released its Fire TV set-top box in April, to good reviews and endless promotion on the Amazon home page. Around the same time the company started quietly distributing the wand-likeAmazon Dash, which lets users of its AmazonFresh grocery service scan barcodes of everyday items and add them to their online shopping lists. Tomorrow’s announcement—and refreshes to the e-reader and tablets that are no doubt coming later this year—will make this the most productive year for Lab126 since Chief Executive Officer Jeff Bezos established the group to pursue a digital reading device back in 2004.
Many Amazon watchers struggle to explain just why the online retailer and cloud services provider is in the risky business of making hardware in the first place. That’s the wrong question to ask. Lab126 is in the business of asking: Why the heck not? Fueled by his pride in Amazon’s inventiveness and his stubborn refusal to cede even an inch of the tech landscape to other companies, Bezos provides much of the motivation at Lab126, pushing it to develop mainstream hardware devices, as well as a variety of so-called “science projects,” many of which have yet to see the light of day.
One group at Lab126, for example, is working on a device that projects a computer image onto any surface. A second is developing a wireless speaker that responds to voice commands. Apparently there are many more. Lab 126 insiders whisper about a credit-card reading device similar to Square, which could help propel Amazon’s fledgling payments business, plus a remarkably thin upcoming version of the Kindle Paperwhite, code-named Ice Wine.
The smartphone project has been one of the longest in development at Lab126. Interviews with multiple Lab126 employees over the course of many months—all conducted with promises of anonymity because Amazon fiercely guards such information—suggest that the phone project was started as far back as 2009. One of the inspirations was this famous video by hacker Johnny Chung Lee, now an employee of Google (GOOG), who demonstrated that by reversing the position of sensors on the Nintendo (7974:JP) Wii, you could create a display that tracked people’s heads and presented images that moved along with their vantage points. It effectively created a 3D display without the need for special glasses.
The Amazon smartphone took off from there. It was at one point code-named Tyto, after a genus of owl. The project was accompanied inside Lab126 by a lower-cost smartphone design without the 3D effect, code-named Otus, for another owl genus. That Amazon would name its smartphone projects after birds of prey may not come as a surprise to anyone who’s paid attention to the company over the years.
The development of Tyto, however, was bedeviled by technical and organizational challenges, including getting the right cameras to produce a stable 3D effect and controlling the cost of the handset—as well as figuring out just why smartphone owners would need such a feature in the first place. (It won’t be clear until the phone actually goes on sale whether Amazon has actually figured that one out.) Lab126 employees say the phone group was reorganized several times. Leadership changed, and turnover was high. Bezos himself spent part of last summer with Lab126, which may have sped things along and instigated the current flood of hardware roll-outs.

Monday, June 16, 2014

Too Big? (BusinessWeek)

Airbus: Come for an A380 Test Ride, and Please Buy One

Airbus A380-800
Airbus A380-800
The world’s largest passenger airplane, the Airbus A380, has seen meager sales—including zero orders by U.S. airlines in the seven years the plane has been flying. To drum up potential customers and interest from investors, Airbus (EAD:FP) and Amedeo, a Dublin-based aircraft leasing company, are co-hosting an event today in New York and flying the massive, twin-deck jet over Manhattan, with Wall Street analysts on board. The goal is to bring the biggest plane into service in the biggest aviation market in the world.
The plane, which can carry more than 500 passengers, faces a virtually insurmountable hurdle in cracking the U.S. market: its size. “Go try to fill it every day—that’s the problem,” says Robert Mann, an aviation analyst and former network planner for American Airlines (AAL). U.S. airlines have shunned the biggest planes as they tie seat capacity closely to demand, to maximize profit. That’s why Boeing’s (BA) 747 isn’t “flying the Atlantic any more and not flying domestically any more,” Mann says.
Eleven airlines have taken 132 of the planes. Airbus has 324 orders for the A380, most of those committed to Emirates, the largest operator of the model. But many potential customers have concluded that the A380 is too large to work in their networks. Airbus is facing open production slots on the A380 program next year, meaning it will be building planes for which there are currently no buyers.
Amedeo, the only lessor of the model, has 20 A380s on order. It will begin receiving them in 2016. Amedeo’s chief executive, Mark Lapidus, has long argued that airlines have never properly configured the A380 and fly it with too few seats. Emirates and Singapore Airlines, the largest operators, put 10 seats abreast; Lapidus says 11 is more appropriate for the plane, which could accommodate 40 to 50 more seats than most carriers fly it with now. At full capacity, with one cabin layout, an A380 can hold more than 800 people. “It’s a cash-printing machine for an airline that is using it correctly,” Lapidus told Bloomberg TV last year.
U.S. airlines generally prefer to have more flights with smaller planes rather than one or two with large-capacity aircraft. Moreover, Mann says, most airport congestion problems are resolved with innovations in air traffic control and aircraft fleet adjustments, which lessen the need for large-capacity flights. Says Mann: “I don’t know why you’d bring an A380 here. No one’s going to buy it.”
Bachman is an associate editor for Businessweek.com.