Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Chris Murphy

Chris Murphy

Editor, InformationWeek

Ford And Toyota Team Up To Speed Development

In a bold collaboration, the carmakers will compete on what customers see but cooperate on back-end data and telematics standards.

Ford and Toyota are fierce rivals, but they're in such a hurry to improve their in-car applications that they've decided to collaborate on standards for back-end technology that their car and truck customers never see.

With telematics, the carmakers know that apps and the digital interface will be an increasingly important reason why people buy one vehicle over another. So Ford and Toyota will cooperate on data standards, such as those for transferring data securely to and from a vehicle, providing Wi-Fi inside the vehicle, improving Bluetooth for connecting mobile devices, and managing information on the back-end.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

The pact "doesn't touch what the customer sees," says Jim Buczkowski, Ford's director of global electrical and electronics systems engineering. "We'll continue to compete vigorously on that experience in the vehicle." That customer-facing digital experience is part of "what makes a Ford a Ford," he says.

Two messages should be blaring like an annoying car alarm right now for anyone involved in IT in any industry.

One, technology teams must find ways to move a faster to keep up with customer and employee expectations for what technology can do. The likes of Apple, Google, and Netflix are setting those expectations, and IT teams must keep pace.

Two, technology teams must be brainstorming ways to make IT a part of their products --whether that product's a pickup truck, a hotel stay, a watt of energy, or a trash service.

These are themes we've been addressing throughout this year, warning IT teams they'll drift into irrelevance if they don't move faster and insert themselves into the discussion about how technology fits into new products and the product development cycle. (Want to meet other top IT leaders working out how to deliver IT faster? Join our InformationWeek conference Sept. 11 to 13.)

For anyone tempted to take the "not in my industry" rationale for ignoring these trends, consider the magnitude of what Ford and Toyota are doing. The carmakers couldn't be more intense rivals, and they're coming out of a precipitous drop in car sales. Each has staked out the “digital experience” as central to their products and been aggressively creating partnerships to improve those in-vehicle experiences. (Ford and Toyota are also working together on the next-generation of hybrid vehicle technology for light trucks and SUVs.)

Toyota crafted a partnership earlier this year to work with Microsoft to develop in-vehicle apps. Ford also works closely with Microsoft on its Sync in-vehicle entertainment system, and it has experimented with such out-there ideas as having cars collect health data, like seats that monitor changes in weight.

"It's not in the history of the automotive industry to have this kind of collaboration, but you see this kind of collaboration in the consumer electronics business," Buczkowski says. Consumer electronics companies work on standards for everything from 3-D to Blu-Ray.

For Ford, the bottom line is speed to market and lower costs. If it can develop the back-end standards and innovation needed to enable in-car apps--the things that customers don't see--more quickly and at a lower cost, then its people can focus more creative energy on dreaming up things that make car buyers think "I need that."

"Speed is very, very important--bringing new experiences to the market faster," Buczkowski says.

Still hearing that car alarm blaring? IT teams need to move faster, and they need to focus on innovating for the end customer, not just making back-end processes more efficient. There's no ignoring these trends.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.