llmda newsletter ad (2)

Can you really address the Automotive market with AP designed for smartphone?

Can you really address the Automotive market with AP designed for smartphone?
by Eric Esteve on 03-16-2016 at 7:00 am

If you remember, when TI decided to exit the booming wireless segment in 2012, the company decided to re-focus their application processor product line (OMAP) initially developed for smartphone “to a broader market including industrial clients like carmakers”. Being a TI employee in the 90’s in south of France, where TI has started the very successful wireless venture, I was feeling sad as it was the end of an amazing story. But I understood the business reasons and thought that it was a wise decision.

But the investment made by TI to develop OMAP had been huge, developing OMAP5 could be counted in thousands man.year, and the idea to target industrial market seems to be attractive. I was sharing this view, but I realize that I was naïve when thinking you can pick-up an existing SoC initially developed for wireless and decide to target automotive applications. These three words tell you why this was a naïve view: Reliability, Availability, Serviceability or RAS. The car pictured below is 58 years old. Do you really think that we will be able to use the first iPhone in 2065, even assuming that the proper network will be available?

One of Netspeed’ customers is a diversified company developing complex chips addressing server, automotive, and industrial market segments. Supporting automotive applications requires three criteria, safety, security, and reliability to outperform almost any other application. Safety because an automobile is a life-critical system, security because you don’t want to allow any malware to penetrate this system, and finally reliability as we all expect our car to be failure-free for years if not decades.

But SoC targeting certain automotive applications can be as complexes as application processors, integrating multiple CPU/GPU/DSP cores, which creates the need to design cache-coherent solutions. The company’s previous SoC was coherent, but the coherency solution was severely lacking flexibility and offered only limited configurability. The company’s new SoC architecture was targeting an increase in coherent bandwidth as well as the maximum possible flexibility, including a highly configurable coherency solution with design choices in multiple dimensions. To reach the lowest possible latency, the coherency architecture needed to scale with the number of coherency modules.

On top of these design challenges, which can be shared by SoC targeting other markets, comes the requirement to meet the ISO 26262 standard, specifically defined for the automotive market. To meet this high-reliability standard, architects wanted to provide a rich set of enterprise-class RAS (Reliability, Availability, Serviceability) features. Reliability can be linked with the Mean Time Between Failure (MTBF) and high reliability means the longest possible time before the system produces wrong outputs. Availability is the amount of time a device is actually operating as the percentage of total time it should be operating. Serviceability defines the simplicity and speed with which a system
can be repaired.

Since the company needed a coherency solution that was both highly configurable and fully scalable, NetSpeed was an obvious candidate since its Gemini NoC IP is the only product on the market that addresses both of these requirements. In fact, Gemini can satisfy requirements for both coherent and non-coherent designs and can also handle designs with a mix of coherent and non-coherent traffic. The company needed superior performance on coherent fabric to create differentiation from the competition. NetSpeed’s solution enabled it to meet its aggressive target of 100% increase in coherency bandwidth. Compared with the previous generation, the new SoC with NetSpeed’s superior coherency directory solution delivered ultra-low latency for the system, offering 25% improvement.

When deadlocks occur in a smartphone AP, it’s painful, but not tragic as you can simply reset the system by using On/Off button. Avoiding deadlocks can be life-critical for an automotive SoC! Using patented algorithms and formal methods to design NoCs that are correct-by-construction, NocStudio generated an architecture that was deadlock-free at the application level.

If you consider the long list of challenges directly linked with this SoC target application, automotive, you better understand why picking-up a smartphone AP and re-target this SoC to support the automotive market is attractive… but naïve. The SoC architect would have to rethink the architecture in respect with RAS requirements and flexible cache-coherency support, avoiding unacceptable deadlocks. Netspeed’ NocStudio would be the right cache-coherent NoC generator to help building such an automotive SoC.

This blog has been inspired by NetSpeed “Automotive SoC” Success Stories. You can read more about this story and Mobile AP, Networking, Digital Home SoC or Data Center Storage stories here

From Eric Esteve from IPNEST


Attending DAC in Austin for Free

Attending DAC in Austin for Free
by Daniel Payne on 03-15-2016 at 4:00 pm

I love getting a good deal, and free is always compelling, so how about attending DAC in Austin for free this year? Sound too good to be true? Thanks to the generosity of three EDA companies – ATop Tech, ClioSoft and OneSpin, now you can can attend parts of DAC for free by registering here. This is now the 8th year that the I LOVE DAC offer has been going on, and the only thing that changes each year is which EDA companies decide to band together and make it happen.

With I LOVE DAC you get to attend the following on Monday – Wednesday, June 6-8, 2016:

  • Keynotes (NXP Semiconductors, NVIDIA Corporation, Univ. of Texas at Austin)
  • DAC Pavilion (SKYTalks, Fireside CEO Chats, three Teardowns, Austin Angle talks, daily panels )
  • Exhibits with 180 booths
  • IoT Exhibit
  • NXP Cup US Finals
  • Networking receptions (Sunday night, Monday – Wednesday Post Session receptions, Monday-Tuesday networking receptions, Wednesday Work-in-progress poster sessions)
  • Designer/IP Track Poster Sessions
  • Silicon Technology Art Show on Monday
  • Food Court

In the EDA and IP world the DAC event is a big deal because of the technical, academic, business and marketing networking that goes on. Attendees at DAC come from over 1,000 organizations, and you’ll find system designers, architects, logic designers, circuit designers, CAD managers, verification engineers, managers, executives, researchers, academics, and consultants that blog like me.

When you get this deal then make sure to stop by and thank Eric Thune at ATop Tech in booth #1648, Ranjit Adhikary of ClioSoft in booth #519, and Dave Kelf at OneSpin in booth #1249.

This offer is limited in time, so register by May 18th, 2016 to get into DAC for free.

I’ll be at DAC in Austin again this year, visiting with EDA vendors to learn what’s new with their SPICE circuit simulators and IC implementation tools, attending presentations at breakfast-lunch-dinner, live tweeting, live blogging, and in general not getting enough sleep from Sunday through Wednesday. I’d love to meet you during the many networking receptions and hear your views on the state of our semiconductor and EDA industry, off the record of course, unless I’m typing on my iPad – then it’s getting blogged.

DAC Exhibitors
[TABLE] style=”width: 600px”
|-
| Aegis
| Agnisys
| Aldec
| Allegro DVT
|-
| ALLEGRO DVT
| AMIQ EDA
| AMS
| Analog Bits Inc.
|-
| ANSYS
| Arcadia Innovation
| ARM
| ATop Tech
|-
| Ausdia
| Avery Design Systems
| Blackcomb DA
| Blue Pearl Software
|-
| Breker Verification Systems
| Brite Semiconductor
| Cadence Design
| Calypto Design
|-
| CAST
| CEA Tech
| Chip Design
| ChipEstimate.com
|-
| ChipStart LLC
| ClioSoft, Inc.
| CMP
| Cadasip
|-
| Concept Engineering
| Conventor
| CST
| Dassault Systemes
|-
| Defacto Technologies
| Design and Reuse
| DINI Group
| Dorado DA
|-
| Doulos
| EDACafe.com
| EDXACT SA
| EMC
|-
| EnSilica
| Entasys
| Europractice / IMEC
| Excellicon
|-
| Faraday Technology
| Fish Tail DA
| Flex Logic
| Fractal Technologies
|-
| Fraunhofer IIS/EAS
| Gold Standard Simulations
| Helic
| IBM
|-
| IC Manage
| ICScape
| Imperas Software
| Integrand Software
|-
| Intel
| Intento Design
| IROC Technologies
| Jedat
|-
| Keysight Technologies
| Laflin/Instigate
| Library Technologies
| Lorentz Solution
|-
| Magillem Design Services
| Magwel NV
| Menta
| Mentor Graphics
|-
| Methodics
| Micro Magic
| Mixel
| Mobile Semiconductor
|-
| Mobivell
| MOSIS
| MunEDA
| Nangate
|-
| NEWRACOM
| Omni Design Technologies
| OneSpin Solutions
| OpenText
|-
| Oski Technology
| PLDA
| ProPlus Design
| Pulsic
|-
| Real Intent
| Rocketick
| Runtime DA
| S2C Inc
|-
| S2 Group
| Sage DA
| Samsung Electronics
| Sankalp USA
|-
| Semiconductor Mfg Int
| Semiconductor Research Corp
| Semifore
| Shaghai Huali Micro
|-
| Si2
| Siemens PLM Software
| Sigasi
| Silicon Creations
|-
| Silicon Frontline
| Silvaco
| SmartDV Technologies
| SoCScape
|-
| Solido DA
| Sonnet Software
| Springer
| StarNet Communications
|-
| SureCore
| Synopsys
| Tanner EDA
| Teklatech
|-
| Teraproc
| TOOL Corp
| TowerJazz
| True Circuits
|-
| TRUECHIP
| TSMC
| Verific DA
| Verification Academy
|-
| Verification Technology
| Verifyter
| Veritools
| Vtool
|-
| WinterLogic
| XYALIS
| Zentera Systems
| Zipalog
|-

About DAC
The Design Automation Conference (DAC) is recognized as the premier event for the design of electronic circuits and systems and for electronic design automation (EDA). Members of a diverse worldwide community from more than 1,000 organizations attend each year, represented by system designers and architects, logic and circuit designers, validation engineers, CAD managers, senior managers and executives, and researchers and academicians from leading universities. Close to 60 technical sessions selected by a committee of electronic design experts offer information on recent developments and trends, management practices and new products, methodologies and technologies. A highlight of DAC is its exhibition and suite area with approximately 200 of the leading and emerging EDA, silicon, intellectual property (IP) and design services providers. The conference is sponsored by the Association for Computing Machinery (ACM), the Electronic Design Automation Consortium (EDA Consortium), and the Institute of Electrical and Electronics Engineers (IEEE), and is supported by ACM’s Special Interest Group on Design.


Software-Driven Verification and Portable Stimulus

Software-Driven Verification and Portable Stimulus
by Bernard Murphy on 03-15-2016 at 12:00 pm

I was at every single lunch at DVCon, not because the food was that great (it wasn’t bad) but because the topics were all interesting. The Wednesday lunch, hosted by Cadence, was a panel on software-driven verification and portable stimulus, moderated by Frank Schirrmeister (a different role for Frank – he’s usually a panel member and doing most of the talking ;)). What follows is a condensation of many comments from the panelists, the audience and Frank (I also had a chance to talk with him after the panel).

Why do we need these approaches?
Because software and hardware have become completely intertwined in electronic products. You can’t separate verification between these domains any longer, which means that software is the right way and in some cases the only way to drive realistic use-cases. But we also need to be able to drive subset use-cases down to lower levels of design. And we need to be able to randomize to get a reasonable sense of system-level coverage, which is why the portable stimulus (PS) standard is important.

As hardware becomes more complex, you accept out of necessity that not all bugs are created equal – you want to find the most harmful by exercising the hardware in the way it will be used. Consider some obvious cases where you have to model the software to verify the hardware: you increasingly need firmware just to get out of reset, power management is largely driven by software and cache coherency correctness can only be determined when linked to realistic software use-cases. Proving the hardware will play nice with the software requires software models and scenarios which can be used in these lower-level hardware tests.

To approach this systematically, we need to define system level coverage. Unsurprisingly, this starts from software-driven verification. Begin with basic firmware coverage: function and line-coverage. In graph-based/declarative approaches, coverage of the graph is another metric (a more complete version of branch coverage). Then there should be metrics associated with external factors, such as high interrupt rates. And you want to be able to randomize over these factors, something PS aims to enable through vendor tools.

It’s also worth considering the role played by big data analytics. We’re already at a point where system-level behavior may be sufficiently complex that escapes are possible even in software driven approaches. Data mining and analytics may provide a way to detect rare or unexpected behaviors that would otherwise be missed.

Are we ready?
Frank and others believe this direction is going to force verification engineers out of their comfort zones (hardware towards software and vice-versa). How do we organize and educate for that shift? At one level executives and business priorities can force a shift – adapt or die – but we can do things to ease this transition.

Frank feels we’re making great strides on the technology side. We’re finding commonalities between engines and disciplines, we have cockpits to debug hardware and software together and we have unified interfaces to different verification platforms. We also have verification IP portable between emulation and simulation and we can collect coverage from all sources through verification management so we can see and drive progress on overall coverage goals. Adoption is, at least for now, gated more by organizational limitations.

There are some promising signs. A power engineer understands how sequences affect the task, as does a cache-coherency engineer, so they’re motivated to communicate in structured ways with the software team and then to find ways to automate that communication. But there are still challenges. One idea that ought to be reasonable is to get the virtual platform model ready very early (to drive subsequent verification). But Frank has seen cases where even when that was done, the software team couldn’t take advantage of it because they were tied up in finishing the last project – an organization problem.

However you parse this, it is clear that product designers and tool vendors are jointly searching for the way through to the promised land of system verification. These are interesting times.

You can learn more about the Cadence system-level verification solutions HERE.

More articles by Bernard…


TSMC and ARM Serving up 7nm!

TSMC and ARM Serving up 7nm!
by Daniel Nenni on 03-15-2016 at 10:00 am

One thing I learned while writing the books about TSMC and ARM is that collaboration has always been at the core of both companies. They started with collaboration on day one and it is now a natural part of their business models. And the word collaboration in the fabless semiconductor ecosystem gets redefined at every process node, absolutely.

As I write this I am in the lobby of the Hilton at the San Jose Convention Center waiting for the 22[SUP]nd[/SUP] annual TSMC Technical Symposium to start. This event is unique as it is invitation only for TSMC collaboraters (customers and partners). The Toms (Tom Simon and Tom Dillinger) and I will be covering it live for SemiWiki so stay tuned.

One of the more interesting press releases to come out before the event is the one highlighting the TSMC and ARM collaboration on 7nm. Interesting because it focuses on the server market (high-performance compute) which should be a very big swing for the fabless semiconductor ecosystem.

The first book we published was a brief history of the fabless semiconductor ecosystem. I really have to thank Intel for the motivation on that book. Remember when Mark Bohr of Intel said, “The fabless model is collapsing”? This was back in 2012 and referenced TSMC 20nm. Today TSMC will talk about 16FFC, 10nm, and 7nm, all of which will signal for the first time a process lead change from IDM to foundry. So not only was the fabless business model NOT collapsing, it is now challenging the feasibility of the IDM model.

The second book we published is a detailed history of ARM followed by brief histories of Apple, Samsung, and Qualcom. This is an SoC focused book documenting the billions of ARM enabled devices. In the epilogue we talk about how ARM gets to the trillions of devices and that of course brings us to IoT, which is what our third book is about.

Will there be a fourth SemiWiki book? Well, we are looking for topics right now with the leading candidate being the server market and this is why:

“Existing ARM-based platforms have been shown to deliver an increase of up to 10x in compute density for specific data center workloads,” said Pete Hutton, executive vice president and president of product groups, ARM. “Future ARM technology designed specifically for data centers and network infrastructure and optimized for TSMC 7nm FinFET will enable our mutual customers to scale the industry’s lowest-power architecture across all performance points.”

“TSMC continuously invests in advanced process technology to support our customer’s success,” said Dr. Cliff Hou, vice president, R&D, TSMC. “With our 7nm FinFET, we have expanded our Process and Ecosystem solutions from mobile to high performance compute. Customers designing their next generation high-performance computing SoCs will benefit from TSMC’s industry-leading 7nm FinFET, which will deliver more performance improvement at the same power or lower power at the same performance as compared to our 10nm FinFET process node. Jointly optimized ARM and TSMC solutions will enable our customers to deliver disruptive, first-to-market products.”

Now that the foundries have the process lead and 64-bit ARM technology has a significant price/power/performance advantage over other architectures, I see the sever market as being the next big Fabless v. IDM battlefield. Remember, at the 2015 ARM TechCon it was stated that ARM is predicting a 25% server market share by 2020. SemiWiki is totally on board with this strategy and, if successful, it will certainly make a good book.


SPIE – Interview with Greg Mcintyre of IMEC

SPIE – Interview with Greg Mcintyre of IMEC
by Scotten Jones on 03-15-2016 at 7:00 am

One of the things I really like about major technical conferences is the opportunity to meet with people for networking and interviews. On Wednesday at the Advanced Lithography Conference I had the opportunity to interview Greg Mcinttyre, the director of advanced patterning at IMEC.

IMEC researchers are the first author on 32 to 33 papers at this years SPIE Advanced Lithography Conference with the papers split evenly between EUV, SAQP and DSA.

DSA (directed self-assembly) – IMEC presented 14 papers on DSA. DSA has the highest potential for near term insertion with memory the most interested in DSA implementation. A DSA line/space approach is defectivity limited. A templated via approach can be done with grapho-epitaxy. EUV templates for a templated via can change a double litho-etch (LE) to a single LE. Electrical testing of templated via taken through to electrical test looks as expected with performance tracking hole size. The biggest challenge is defectivity. Memory is expected to use this approach first because it is more defect tolerant. DSA needs to fit into an environment designed for multi-patterning. They are looking at different materials to make DSA fit into today’s design environment. The first DSA symposium in Belgium this year. Survey says 2 to 5 years before DSA insertion. Current XSADP going to XSAQP could be replaced with DSA. Some DRAMs have been made with DSA.

EUV – they have a program looking at alternate materials. They have an ASML NXE3300, materials, masks, and pellicles and they are looking at integration. The alternate materials program has multiple partners including inprea, and JSR, and they are looking at metallic concepts, adding metallic sensitizer to chemically amplified photoresist. They are looking at dry develop rinses or adding material that stays in during dry to prevent collapse until you etch it away. They want to understand the latest chemically amplified photoresist capability. As you lower a dose you get more shott noise so they are looking at smoothing in etch tools from TEL and Lam. DSA offers contact hole smoothing on a track.

For pellicles they have an initial solution for 40 to 80 watts full field with 85% single pass transmission. Silicon based pellicles are likely limited to 80 to 100 watts. They are investigating alternate films with carbon nanotube meshes that provide strong mechanical strength and transmission but lack chemical stability in hydrogen. Graphene and silicon nitride films with DSA for holes to improve transmission and mechanical stress in the film are also being looked at. Carbon based films are very promising.

EUV versus 193i integration. EUV imaging is clearly superior and pattern fidelity is there. Throughput, roughness and critical dimension (CDU) are key issues. One EUV layer can replace 3 argon fluoride immersion (ArFi) layers for 32nm IMEC N7.

Metal contamination of scanner, etch and track so far looks OK.

Nigh-NA system, anamorphic was a big breakthrough!

EUV insertion around 2018, if N7 is late 2017 (authors note, this is TSMC’s target) then N5 plus N7 cost reduction. The biggest push is from logic. 2D metal is worth a node but then at the next node you are back to 1D. 1D offers better electrical performance and simpler design rules. EUV most likely to be used for single exposure BEOL and as a cut mask for SAQP in the FEOL to replace multiple cut masks.

SAQP (self aligned quadruple patterning) – well controlled 22nm pitch fins with sub nanometer pitch waling. 22nm pitch is ~N5. The big SAQP is process control with CD and roughness varying with height. You need to control every process step, core 1, spacer 1, etc. They are working with ASML and Lam tuning the scanner and the etcher. Just the scanner or etch optimization gets 0.8nm CDU three sigma but co-optimization gets 0.6nm CDU three sigma.

Multi-beam eBeam – they are not focused on eBeam. He thinks multi-beam wafers is a big challenge but multi-beam for masks seems more likley.

Device Technology – Aaron Theon is presenting on the future of new devices. Horizontal nanowires look promising to replace FinFETs. Vertical nanowires versus horizontal nanowires depends on the design with vertical offering better gate length control.


Speaking about the Internet of Trust on April 21

Speaking about the Internet of Trust on April 21
by Don Dingee on 03-14-2016 at 4:00 pm

Five minutes to ruin a reputation built over 20 years, as Warren Buffett put it, holds true in personal relationships. On the Internet of Things, reputations can disappear in five seconds. How do we move from merely intelligent Things to a level where devices have to be Trusted? Continue reading “Speaking about the Internet of Trust on April 21”


Mentor Extends Verification Offering!

Mentor Extends Verification Offering!
by Daniel Nenni on 03-14-2016 at 12:00 pm

With verification consuming more and more of the design cycle and the increasingly complex industry standard interfaces that are now common place, Verification IP (VIP) is again a trending topic. Back in my IP days the age old question was: Is it better to use VIP from the IP vendor? Because you know it will work, right? Or is it better to use independent VIP that is used by multiple IP vendors because you REALLY know it will work?


I had this discussion again at DVCon amongst the masses and the consensus was that independent VIP is preferred, to which I wholeheartedly agree with but quite often VIP is bundled in with the IP if the vendor has both. In fact, that type of bundling seriously thinned the independent VIP herd which was quite apparent at the exhibit hall this year. The other crushing competitive force is the integration of VIP into the mainstream verification cycle including emulation.

For further clarification I met with Mark Olen and Jason Polychronopoulos from Mentor’s Verification Division. Mark and Jason are both very interesting men and very approachable so if you have any questions for them put it in the comment section and I will make sure you get a response.

Mark and Jason were at DVCon to push the availability of the:

First entirely native UVM SystemVerilog memory verification IP library for all commonly used memory devices, configurations, and interfaces. Mentor is adding over 1600 memory models to theMentor[SUP]®[/SUP] Verification IP(Mentor VIP) library that already supports over 60 commonly used peripheral interfaces and bus architectures. As a result, Mentor becomes the first company to supply ASIC and FPGA SoC designers with a complete UVM SystemVerilog verification IP library that covers the breadth of their peripheral interface, bus protocol and memory device needs. Providing the complete library in one consistent industry-standard format reduces the time it takes for engineers to set up verification runs, so they can focus on verifying unique, high-value parts of their designs.

“The vast majority of ASIC and FPGA project teams have moved to standard UVM SystemVerilog verification methodology, and until now have been unable to find a universal VIP library that supports bus protocols, peripheral interfaces, and memory devices, all in native UVM,” says Mark Olen, Mentor Graphics product marketing manager, Design Verification Technology Division. “Judging from initial adoptions of our new memory VIP library, it’s easy to see why verification IP is one of the fastest growing sub-segments in the functional verification market, now exceeding $110 million in annual spending, according to the Electronic Design Automation Consortium.”

We went through the slides, which they were nice enough to give me so you can find them HERE. The key takeaway from our discussion is two-fold for me: First and foremost Mentor is the leader in verification and VIP is now an integral part of that. Second, Mentor does not compete with their IP partners so not only do they have an early and intimate relationship with ARM, Northwest Logic, PLDA, etc…, Mentor also offers truly independent IP verification.

Again, post questions in the comment section and I will make sure they are answered, absolutely.


Mobile Will Disrupt These Industries Next

Mobile Will Disrupt These Industries Next
by Matt Crampton on 03-14-2016 at 7:00 am

Technologists from across the globe recently gathered in Barcelona for the Mobile World Congress, the annual conversation on connectivity and celebration of new gadgets. While the conference traditionally focuses on phones, the discussions about mobile—in Barcelona and beyond—have grown increasingly wide-ranging as mobile technologies continue to seep into more areas of daily life. As one journalist covering the conference eloquently noted, “The Internet is becoming an invisible fabric—like air—that enables all the services we’ve come to depend on.” In this schema, mobile devices and their apps are the stitches weaving together these services that help us work, play and live.

Indeed, the rise of mobile technologies has spurred the transformation of industries once considered sleepy into areas where some of the hottest new startups are operating. Uber and Lyft drivers have largely displaced cabbies; Airbnb has won over travelers who had previously booked hotel rooms; Postmates couriers have sped past the bike messengers of yesteryear with their promise of any local product delivered to your door in under one hour.

Looking at the common denominators of these startups gives us some clues about where the next mobility-enabled disruption might occur. First, these companies all offer services characterized by high time-sensitivity. After all, it’s far more likely that someone waiting for a ride they’ve requested will return to a service that supplies a driver in four to five minutes as opposed to ten. By bypassing the dispatching step of traditional cab companies with location-based data capabilities, Uber et al. have cornered that competitive edge.

Second, these companies invest in technology but stay capital light by relying on assets that are already owned by the independent providers they partner with: Cars, bikes, houses and apartments. This low barrier to entry for service providers—no pricey taxi medallion to buy or hotel to maintain— results in the greater supply that drives down costs for consumers and thereby renders these services more desirable.
Finally, these companies are able to use technology to turn what I’ll call “serendipity” into operating efficiencies. Theoretically at least, Lyft drivers or Postmates couriers accept jobs close to where they already are when the job comes up. Jobs are done more quickly, which means that workers make more money in less time and customers are more satisfied.

While a variety of industries have one or more of these features of providing time-sensitive services, possessing the option to rely on shared assets, and capitalizing on serendipity, I believe three more traditional areas especially ripe for mobile-enabled disruption are healthcare, staffing and banking. Watch these spaces if you’re looking for the next company to have its “Uber moment.”

Healthcare

Pioneers in telemedicine are improving access to care for patients who live in underserved areas or who can’t otherwise travel to their doctor’s offices. Startups like American Well and Doctor on Demand offer live video doctor visits via mobile app for a relatively small patient fee, and they’re starting to gain momentum in part by making inroads to employer-sponsored plans. These services might be especially valuable in the arena of mental health, where on-demand offerings are growing and a shortage of face-to-face appointment availability means that patients are often unable to get the timely help they need to avoid crisis.

Staffing

Many of today’s contingent workers find project-based “gigs” and other short-term work using mobile workforce platforms like Upwork, Fiverr and the company I co-founded, Gigwalk. The rise of such platforms has changed the game not just for independent workers, but also for HR departments and staffing agencies, which must now bolster their technological capabilities to stay competitive. The employers of today want to work with staffing partners who can anticipate and meet constantly and rapidly shifting staffing needs. The day when the average staffing agency employee wakes up and glances at an app on her phone to get that day’s work location and assignment is closer than we think.

Banking

Brick-and-mortar and online-only banks alike have been quick to offer mobile apps that let their customers check balances, transfer funds and deposit checks from their phones, but there’s still room for innovation in the key area of cash transfer. While mobile apps like Venmo and Circle let users send or receive cash instantly via text at no charge, we still haven’t seen this capability offered at large scale and integrated with other banking services. The area is ripe for players who can wrap these services together at a low price point.

Just like EBay changed the garage sale to a large-scale virtual goldmine in the ’90s as it used the Internet to match far-flung buyers and sellers, mobile is causing another wave of disruption that will reward a new crop of innovative players. Wherever they emerge from, they promise to further ease the “life on-the-go” that is our 21st century reality.


The Emerging Battle for Your Car’s Data

The Emerging Battle for Your Car’s Data
by Roger C. Lanctot on 03-13-2016 at 8:00 pm

The Future Networked Car gathering put on by the International Telecommunications Union at the Geneva Motor Show last week highlighted the intensifying debate over automotive data privacy. A representative from FIA, the international federation of car clubs, and Stephan Appt, legal director and attorney at Pinsent Masons, highlighted fundamental contradictions facing car makers and consumers.

FIA is in the forefront of a global effort by car clubs to alert consumers to the data collection capabilities of automobiles. FIA has been leading the MyCarMyData campaign to educate consumers regarding the vehicle data collection activities of car makers and the potential consequences.

FIA is concerned that consumers know their rights to privacy but the organization is also advocating for consumer choice. FIA believes consumers should have the right to choose their telematics service providers and vehicle repair options.

The FIA position reflects the organization’s perception that connected cars will increasingly be tied to the car maker’s eco-system of service providers. FIA says its consumer surveys show that:

  • 90% believe the car data is owned by the car owner or user
  • 95% want legislation to protect user data
  • 78% want to choose their service providers
  • 76% believe that consent to access data should be for a limited time or per-ride basis

The irony and the reality is that very little car data is being gathered in real-time today, though some data is being gathered periodically. But the onset of connected and autonomous cars is rapidly altering the industry mindset around vastly increased data collection.

FIA’s focus on consumer choice relates to the roadside assistance and insurance services offered by car clubs, which are increasingly introducing aftermarket telematics systems to connect to their customers and compete with car makers.

Car makers are still remarkably conflicted regarding connecting cars. Some car makers may themselves be interested in privacy protection for their customers and for themselves. It was only two years ago that former VW CEO Martin Winterkorn warned that the car was becoming a Datenkrake (Data Octopus) and that VW was committed to protecting the privacy of its customers.

Winterkorn’s words revealed the profound ambivalence prevailing in the auto industry regarding privacy and data collection, particularly in the wake of two years of record-breaking recall levels. Car makers still aren’t quite sure they want to collect all that vehicle data.

It is clear that vehicle data can not only be used against the driver by law enforcement, marketers or insurance companies, it can also be used against the car companies by regulators or consumers. Additionally, vehicle data has become a battleground as governments such as Russia and China insist that car makers locate their data collection servers within the borders of those countries and as regulators throughout the world specify how long data must be preserved or how quickly it must be destroyed.

The last thing any car maker wants to do today is get into the business of selling its data. Any vehicle or customer data that might escape into the wild, even via a valid commercial agreement, could contain the seeds of a devastating lawsuit or regulatory action.

There are exceptions to this ambivalence. Tesla Motors proudly maintains its lifetime always-on connectivity. By and large car companies are not gathering vast quantities of data. But that is about to change.

Appt of Pinsent Masons doesn’t see how car companies can possibly avoid collecting data on their cars and he pointed out the need for clear customer disclosures and opt-in procedures in advance of vehicle usage data collection. He also noted the requirements associated with event data recorders and the regional limitations placed on dashcam data collection.

For all their ambivalence about collecting data, though, car makers have an obligation and a need to collect data. Vehicle data may turn out to be incriminating, but Appt says car makers are obliged to collect and analyze data since they are answerable for the performance of the vehicle and the safety of the customer.

In the context of security concerns, the need for car companies to collect data has only increased. Car makers are increasingly recognizing they have a need to monitor vehicle systems as much as possible in real-time to ensure the integrity of vehicle performance and to detect and prevent the intrusion of malware.

Appt notes that efforts are underway to rationalize and harmonize privacy laws in Europe and around the world, but these efforts are at the earliest stages. In the meantime, car makers are caught like deer in the headlights. They are answerable for vehicle failures, recalls or security intrusions but they have a limited set of tools to take on these responsibilities and are confronting a fragmented legal framework around privacy and their customers are increasingly wary regarding vehicle connections and data collection.

On a separate panel at the Fully Networked Car event a moderator asked about the right of consumers to opt out of connectivity and the impact that might have on safety systems based on vehicle-to-vehicle communications. The FIA notes that 91% of the respondents to its survey said they wanted the right to turn their car connections off.

Consumers shutting car connections off may create the peace of mind of an escape from the intrusive data gathering eyes of car makers, marketers and insurers, but it does not let the car maker off the hook for liability regarding the safe and secure operation of the vehicle. It also undermines safety systems designed to use connectivity to avoid collisions.

Finally, it isn’t enough to collect the data. If a car company collects vehicle data there is an implied obligation to thoroughly analyze the data. This is yet another reason why car companies remain ambivalent. They will clearly be held liable for collecting data which might contain evidence of vehicle malfunctions. Yes, the days of plausible deniability are officially past.

As car companies collect and analyze data they will be expected to notify vehicle owners and drivers in a timely manner as to imminent vehicle system failures. Ultimately, existing guidelines for postal notifications of potential malfunctions or flaws will no longer be sufficient. Real-time, in-dashboard warnings and alerts will ultimately be implemented by all car makers.

Herr Winterkorn was correct in observing that his industry was confronting a Datenkrake, but his prescription was wrong. The auto industry must embrace connectivity and all of the responsibilities that it entails. Data is neither good nor bad. It is only a resource to be used to better serve and protect the customer.

More articles from Roger…


Apple Protects Its Designs With Custom Silicon And You Can Too

Apple Protects Its Designs With Custom Silicon And You Can Too
by Bob Frostholm on 03-13-2016 at 4:00 pm

In the February 22-28 issue of Bloomberg Businessweek magazine, Johny Srouji, Apple’s senior vice president for hardware technologies, discusses Apple’s winning strategy of owning its own silicon. It began with the acquisition a Silicon Valley chip startup called P.A. Semi in April of 2008 and since then, Apple has never looked back.

The Bloomberg article cites that “When the original iPhone came out in 2007, Steve Jobs was well aware of its flaws. It had no front camera, measly battery life, and a slow 2G connection from AT&T. It was also underpowered. A former Apple engineer who worked on the device said that while the handset was a breakthrough technology, it was limited because it pieced together components from different vendors.”

In an earlier paper, I likened this to the Frankenstein Effect where I wrote:

Mary Shelley’s 1818 novel, Frankenstein, tells the story of a monster created with parts collected from random cadavers. The creature stands eight feet tall due to an inability to integrate all the necessary components into a standard humanoid form factor. Additionally, this haphazard collection of limbs and organs lacks sufficient neural network connections, accounting for its awkward gate and general stiffness of its arms and shoulders as it walks with forearms extended. This is perhaps the first documented evidence of the problems that can occur when designing a system using ‘point-products’, parts selected for their unique special functions without regard for their perfect interoperability. Clearly, Mary Shelley was a visionary.

The BBW article continues, “Steve came to the conclusion that the only way for Apple to really differentiate and deliver something truly unique and truly great, you have to own your own silicon, Srouji says. ‘You have to control and own it.”

Not every company can afford to acquire and successfully maintain a semiconductor development center dedicated to supporting their internal needs. But you can gain many of the same benefits by working with a reputable ASIC (Application Specific Integrated Circuit) semiconductor company to design and produce custom ICs for you.

No one can deny that Apple and a handful of other high tech companies are anomalies. They have the wherewithal and financial resources to do just about anything they want including acquiring at the drop of a hat capabilities they don’t already have. Good for them. Your company may not be so fortunate. That doesn’t mean you have to throw your hands in the air and give up. There are lesser cost alternatives that can generate similar technological, cost and size advantages to ignite your sales.

First and foremost is to eliminate any Frankenstein Effects in your design.

In the world of standard product ICs, there are chips that can do just about any function you can imagine…just like the arms, legs, torso and brain Mary Shelley wrote about. The trick is to get them to connect and interoperate in a smooth and efficient manner. If every chip interfaced smoothly with every other chip in a design, engineering would be so easy that even a finance major could do it. Unfortunately that isn’t the case, so engineers spend a disproportionate amount of their time and effort getting part A to communicate with part B and getting part B to communicate with part C, etc., and thus designs can quickly become awkward and cumbersome as additional components are added to bridge these transitions.

Apple’s solution was nothing short of brilliant timing but not unique. Companies have grown dramatically by gaining needed technology by acquiring other companies for decades; look into Cisco’s history. These big ticket approaches are reserved for companies with deep pockets. A less costly approach is to develop a relationship with an ASIC chip company to roll your critical design elements into a custom system on a chip. You don’t even need to go that far. Often a subset of a system integrated into a single silicon chip can be the needed catalyst to jump start your product’s success.

ASICs are no longer the purview of the high volume users. Many ASIC companies entertain volumes as low as a few tens of thousands of units per year; some even as low as a couple of thousand. And some offer NRE & Tooling rebate programs that over time make the development costs zero, putting total cost of ownership on par with off the shelf components.

Whether through acquisition or partnering with an ASIC company, the benefits are nearly identical: Faster Time to Market, Improved Performance, Lower Total System Cost, Reduced Size, IP Protection, Lower Power Dissipation, and Improved Reliability.

No one ever accused Apple of being stupid. Investigate for yourself and see how you can keep Frankenstein out of your designs.