Mar 31, 2015

Two industrial titans are duking it out over a technology that could make electric cars mainstream - Quartz

The high-tech patent wars have spread to a new front, engaging two of the world’s largest industrial companies in a multibillion-dollar court battle over lithium-ion batteries. At issue is a battery chemistry that, while little known to the public, many experts believe currently holds the best chance of electric cars penetrating the mass market.

The case pits Germany’s BASF, the world’s largest chemical company, against Belgium’s Umicore, one of the biggest makers of battery materials. Filed by BASF on Feb. 20 in US federal court in Delaware, the lawsuit—which has been reported only by patent blogs—accuses Umicore of selling a key battery component to which BASF holds an exclusive license. It also alleges that Umicore threatened to sue firms if they gave their business to the German company. The suit seeks billions of dollars in alleged damages.

3M’s NMC powder.(3M)
In addition to the pair of European giants, the case tees up a potential collision between two lithium-ion titans with rival patents for the technology at the heart of the dispute—3M Corp., an industrial giant itself, and Argonne National Laboratory, a US government lab that is a co-complainant with BASF.

The case, if it is not settled informally before trial, will require jurors to make sense of nuanced interpretations of the arcane atomic structure of battery electrodes. Specifically, they will hear dueling versions of what goes on at nano-scale when you charge and discharge a battery containing “NMC,” a positive electrode—or cathode, which is the nervous system of a battery—containing nickel, manganese, and cobalt.

To make their case, lawyers for BASF and Argonne are likely to describe a battle under way among major carmakers to launch next-generation electric cars in the 2017-2020 time frame—Tesla, GM, BMW, andpossibly Apple and Virgin among them. They will allege that Umicore has effectively locked BASF out of the contest.

“BASF has lost out on billions of dollars of potential revenue from selling [NMC] materials because of Umicore’s misrepresentations to major purchasers in the [NMC] materials market,” BASF and Argonne claim in the lawsuit. “In addition, BASF has lost the ability to compete as a supplier for electric vehicle platforms expected to launch in 2016 and 2017.”

In recent years, gigantic patent battles have roiled the market for tablets and smartphones, pitting Apple against Samsung, Nokia, Microsoft, and almost anyone else of consequence. Combat also has been rife in the market for gaming devices. The total number of such suits plunged last year, possibly as a result of a US Supreme Court ruling that made it harder to win. But large cases continue to be filed.

With their lawsuit, BASF and Argonne underline the rising economic stakes in batteries. While technological advances in batteries have been slow to come—thus stunting the expected appeal of electric cars—lithium-ion has nonetheless grown into a respectable $18-billion-a-year industry, according to Navigant, a clean energy research firm. This is because of the stunning popularity of smart phones and tablets, plus sales of the electric Tesla S, the GM Volt, and the Nissan Leaf, all of them requiring lithium-ion batteries. Continued double-digit annual growth should push the lithium-ion battery market to about $38 billion by 2020, Navigant says.

The lawsuit names Umicore and one of its customers—Japan’s Makita Corp., a toolmaker. It cites laboratory tests allegedly showing that Makita tools contain NMC invented by Argonne, and says that the Japanese company obtained the cathode material from Umicore. It says that neither Umicore nor Makita have licenses for Argonne’s NMC.

In a statement emailed to Quartz, Umicore disputed BASF’s assertions and said it intends to fight the lawsuit. Makita did not respond to a phone message left at its La Mirada, California, office. 3M declined to comment. BASF lawyer Brian Farnan did not respond to emails. Argonne said it could not comment beyond what it said in the lawsuit.

Argonne was first, but 3M cornered the non US-market

The competing NMC patents go back a decade and a half. The first was filed in June 2000 by Michael Thackeray, a South African-born researcher working at Argonne. Ten months later, 3M filed a competing patent application on behalf of Jeff Dahn, a researcher at Dalhousie University in Halifax, Nova Scotia.

Thackeray’s patent is good only for the US—at the time it was filed, neither he nor Argonne’s lawyers expected the NMC to take on the industry importance that it has, and so they sought to economize by filing for no international patents. But 3M, calculating differently, obtained patents in the US, plus the world’s most important manufacturing markets—China, Japan, and South Korea.

Over the years, 3M has aggressively defended the overseas patents, threatening and filing lawsuits for alleged infringement against Sony,Matsushita, and Sanyo, and winning settlements in each case. The details of the settlements are sealed, but the outcomes appeared to validate 3M’s claims.

3M has apparently not filed similar lawsuits in the US. Now, Argonne, teamed up with BASF, has taken the offensive.

A ruling against BASF and Argonne could have important implications outside the Umicore-Makita issue. For instance, one of the largest customers for NMC is General Motors, which uses it in the Chevy Volt. Argonne has stated publicly that the Volt’s battery contains its version of NMC. But Dahn has said that the Volt battery contains his work, and not Argonne’s. If BASF and Argonne lose their case against Umicore, the legal question could then arise of whose cathode, chemically speaking, is actually in the Volt.

General Motors referred questions to LG Chem, which makes the Volt cathode. LG’s NMC is produced under a license with Argonne.

We will hear rare electrochemical nitty-gritty

The dual challenges of lithium-ion batteries are to obtain more energy at a lower cost. The current standard—a 35-year-old battery formulation in which the cathode is made of lithium cobalt oxide—packs a lot of dense energy, but is expensive and also more volatile than almost any commercial rival.

Though it has its own challenges, the NMC may have the best chance to beat lithium cobalt oxide, while performing well on the other metrics of energy and cost, many experts say. Among the reasons are that the cathode contains less cobalt, which is expensive, and also is less volatile, and thus safer for use in electric cars.

Over the years, Thackeray and Dahn have bickered over the precise atomic structure of the NMC—is it a saucy amalgam of metals, or a “solid solution”(Dahn’s position), or is it a more structured composite with a discernible chemical architecture (Thackeray’s)?

Until now, their dispute had seemed largely academic, obscure, and possibly immaterial. But now, who a jury determines is right may end up as the pivotal factor in the BASF/Umicore case. (Quartz reached out to Dahn and Thackeray; both declined to comment on the suit.)

 Thackeray and Dahn bickered over the precise atomic structure of NMC 

In his ground-breaking patent, Thackeray had the central thesis that if you built up the amount of lithium in the NMC—if you added about 10% more to the cathode—you achieved a big increase in capacity. To understand what he meant, and what’s at the heart of the legal dispute, it’s useful to look both at how lithium-ion batteries work, and specifically at how Thackeray’s cathode manages this jump.

All lithium-ion batteries have three basic parts—two electrodes and, between them, a facilitator called electrolyte. When you plug in your smartphone, lithium stored in the cathode begins to shuttle to the other electrode, called the anode. Then, when you unplug your fully charged phone and start to use it, the lithium begins to shuttle back from the anode to the cathode.

 Thackeray claimed he could put more lithium into motion. 

One of battery science’s objectives is to get as much of the lithium as possible to shuttle, because that creates more energy. But no matter what, you cannot put all of it in motion, because, emptied out of so much material, the cathode will collapse in on itself. A rule of thumb with the standard lithium cobalt oxide cathode is that you can put about half of the lithium into the shuttling motion.

Thackeray’s formulation claimed to beat that rule of thumb. It starts with two compounds—the NMC itself, plus a chemistry called Li2MnO3. Visually, both the NMC and Li2MnO3 resemble stripped-down houses. The floors and ceilings are made of oxygen atoms, and the walls are nickel, cobalt, and manganese. Scientists call this framework a lattice. Because the lattices of the NMC and the Li2MnO3 are similar, you can easily integrate the two at the nanoscale.

From Thackeray’s 2000 patent.
And that’s what Thackeray did–he shifted the Li2MnO3 into the NMC—at which point two things happened: The manganese and lithium propped up the NMC like pillars, adding to its sturdiness, and the extra lithium increased its capacity.

The former phenomenon (the sturdiness) was responsible for the latter—the capacity. This was because, with the double lattice at work, you could now shuttle 60% or 70% of the lithium without the cathode collapsing.

And here also is where the distinction comes between the rival cathodes. Thackeray called his invention a “layered-layered” or “composite” cathode. The atoms of the various metals were clearly concentrated in clumps throughout the electrode, he said.

But Dahn called his version a “solid solution.” The same metals were present of course, but they were more or less evenly arrayed, he said.

What’s the real difference? We’ll hear in court.

The Aussie dollar got crushed overnight | Business Insider

The Aussie dollar has fallen a full cent from where it was this time Monday morning and, at 0.7637, is now down 3 cents from the highs of last week when the US dollar was under pressure.
That’s a huge move in the world of forex traders where exchange rates usually move in tenths of a percentage point not the 1.46% the Aussie has lost in the past 24 hours.
What’s driving the Aussie dollar lower are three things at the moment.
  1. Iron ore is lower again with June 62% Fe Cfr China Futures hitting a new low for this selloff last night at $51.46. Annette Beacher from TD Securities wrote yesterday afternoon that the last time iron ore was this low the Aussie was at 64 cents. Traders are taking notice.
  2. The US dollar is on the ascendancy again as strength in the Euro, Yen and others is being reversed once more.
  3. There was talk in forex markets yesterday that the RBA will be forced to cut at next week’s Board meeting
The multi-year low for the Aussie recently was 0.7557. Traders might just be eyeing a pre-Easter test of support.

Compliance issues lead cloud security concerns | Dylan Bushell-Embling

Auditing, compliance and data privacy issues are considered to be the top cloud security challenges facing organisations, according to a global survey from CipherCloud.
The results of a survey of Global 2000 organisations from North America, Europe, APAC and Latin America shows that 64% identify audit/compliance/privacy as the top challenge.
Nearly a third named unprotected data in the cloud as their primary concern, while 2% cited malware protection for documents and 2% selected a shortage of secure cloud file-sharing technologies.
“Organisations are harnessing cloud computing to more effectively compete in the global economy with faster time to market and cost efficiencies,” said CipherCloud founder and CEO Pravin Kothari.
“At the same time, the headwinds of privacy legislation in [the four regions] make the case for data-centric protections in the cloud. Our research indicates that compliance factors are galvanising organisations, particularly in healthcare and finance, to fortify their data defences in the cloud.”
The healthcare and finance industries are accordingly leading the way in adopting cloud data protection technologies, with 38% and 25% of organisations respectively in these segments doing so.
Finance and healthcare face strict data privacy requirements, and protected 100% of personally identifiable information as a result.
Globally, organisations’ cloud data protection efforts are more focused on data encryption than tokenisation by a margin of 81% to 19%. But in APAC, the two technologies are being adopted in equal measure.

Wanted: Easy database app dev tools for the Web | InfoWorld

A friend of mine needs a simple database application to support his team. It's fairly straightforward: a handful of tables, forms, and queries. The team is globally distributed, so of course this needs to be a database-backed Web application. He's most comfortable with Python, so he's been coding it up in Django. You probably know somebody who's doing the same thing in Python with a different Web application framework or others using Ruby on Rails, ASP.Net, or a JavaScript-centric framework like Angular.js. There are a million ways to skin the cat.
mobile smartphone hands user
Google's Android for Work promises serious security, but how does it stack up against Apple's iOS and
Programming languages, application frameworks, SQL or NoSQL databases, data-binding mechanisms, templating libraries -- they're all up for grabs. Choice is good. But let's think about how my friend would have solved this problem 25 years ago for a colocated team on a LAN.
There weren't many choices then. There was dBase, there was Access, there was my personal favorite, FoxPro. You didn't have to be a proficient programmer to create a basic database app. A power user could do the job, and many did. Of course the LAN didn't span the globe; it only connected people in the same building. The apps you created ran on the desktop against a shared resource on a file server.
Thinking about my friend's situation led me to a perverse thought: As bandwidth to the cloud increases, could an ancient copy of FoxPro become useful again? Of course that's ridiculous. We want modern Web apps that talk to Web servers, not desktop apps that talk to file servers. But where are the well-known and widely used modern equivalents of dBase, FoxPro, and Access for today's Web? I don't see them.
Back in the day there were three big productivity apps: the spreadsheet, the word processor, and the database. Each of the legs of this three-legged stool was an app that power users could effectively customize. Two made the jump to the cloud. Google and Microsoft both offer cloud-based spreadsheets and word processors. Neither offers a cloud-based database. Why didn't the third leg materialize in the cloud?
Consider the file formats. Canonically they were XLS, DOC, and DBF. In the case of word processors and spreadsheets, we use the cloud as a file server, and we still share XLS and DOC files on the moral equivalent of a multiuser LAN.
But databases evolved differently in the pre-Web era. The client/server architecture appeared. Servers stored data in many proprietary formats; they communicated with clients using a few protocols; a more-or-less standard query and data manipulation language, SQL, helped unify them; an umbrella standard, ODBC(Open Database Connectivity), completed that unification. Given that ODBC was an interface not only to servers but to files -- DBF, XLS, CSV -- you could say that the early 1990s was a golden era of data interoperability.
Then came the Web, with its very different client/server architecture. To this day we have yet to reconcile the two. Tim Berners-Lee envisioned that reconciliation in hisoriginal proposal. "A generic tool could perhaps be made," he wrote, "to allow any database which uses a commercial DBMS to be displayed as a hypertext view."
We now have a standard way to do that. OData, aka Open Data Protocol, enables a common RESTful interface to Web data. It emerged from Pablo Castro's work onProject Astoria and is now an OASIS standard. But if you don't inhabit the Microsoft ecosystem, OData isn't on your radar. It's easy to consume OData from any platform, but producers are still scarce and Microsoft-centric.
In OData Client goes Open Source (2010), Miguel de Icaza wrote:
If Microsoft were to open-source their server-side implementation of oData, we could overnight allow Linux users to expose their data in a format that can be mined. Linux users would only need to run a Mono front-end to the System.Data.Services library to expose the data that currently lives in their servers and is being served by Joomla, Wordpress, Rails, Django front-ends to become available as data services.
That hasn't happened yet. Given that the core .Net runtime and frameworks went to GitHub in November, what seemed like a pipe dream in 2010 now feels inevitable. But maybe that ship has sailed. Maybe it's too late for OData to become the universal ODBC for the Web it was meant to be.
One way or another, though, we need a common way to work with Web data, one that every database can use to easily enable a basic API. On that foundation, we might re-create the kinds of tools that make building simple back-office database apps as easy as it was 25 years ago.