In my experience many customers view IP as a service business. Now, to be sure, they want to purchase a design that works, covers all their key functions and minimizes the design footprint (small gate size)- but they also want to make sure that any questions they have get answered right away and that the IP supplier 'stands behind' their design. With all the possible issues with tool flows, verification, software drivers, etc there is always going to be a 'misunderstanding' with some aspect of the design.
A service business seems more like a Partnership to me than a Property transaction...
Mike raises a good point for needing a vocabulary to discuss IP Quality. The GSA IP team, chaired by Warren, has investigated several aspects of IP quality, including TSMC9000, and STMicro's Make versus Buy process. We've just chartered a project for Make versus Buy Best Practices, of which the IP quality is a component, and welcome others to join the effort. Interested parties can contact email@example.com
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.