Tag Archives: Ecosystem

Cost of IoT Implementation

17 Mar

The Internet of Things (IoT) is undoubtedly a very hot topic across many companies today. Firms around the world are planning for how they can profit from increased data connectivity to the products they sell and the services they provide. The prevalence of strategic planning around IoT points to both a recognition of how connected devices can change business models and how new business models can quickly create disruption in industries that were static not long ago.

One such model shift is that from selling products to selling a solution to a problem as a service. A pump manufacture can shift from selling pumps to selling “pumping services” where installation, maintenance, and even operations are handled for an ongoing fee. This model would have been very costly before it was possible to know the fine details of usage and status on a real time basis, through connected sensors.

We have witnessed firms, large and small, setting out on a quest to “add IoT” to existing products or innovate with new products for several years. Cost is perhaps at the forefront of the thinking, as investments like this are often accountable to some P&L owner for specific financial outcomes.

It is difficult to accurately capture the costs of such an effort, because of iterative and transformative nature of the solutions. Therefore, I advocate that leaders facing IoT strategic questions think in terms of three phases:

  1. Prototyping
  2. Learning
  3. Scaling

Costs of Developing an IoT Prototype

I am a firm believer that IoT products and strategies begin with ideation through prototype development. Teams new to the realities of connected development have a tremendous amount of learning to do, and this can be accelerated through prototyping.

Man showing solar panels technology to student girl.jpeg
There is a vast ecosystem of hardware and software platforms that make developing even complex prototypes fast and easy. The only caveat is that the “look and feel” and costs associated with the prototype need to be disregarded.

5 Keys T0 IOT Product Development

Interfacing off-the-shelf computers (like a Raspberry Pi) to an existing industrial product to pull simple metrics and push them onto a cloud platform, can be a great first step. AWS IoT is a great place for teams to start experimenting with data flows. At $5 per million transactions, it is not likely to break the bank.

1. Don’t optimize for cost in your prototype, build as fast as you can.

Cost is a very important driver in almost all IoT projects. Often the business case for an IoT product hinges on the total system cost as it relates to incremental revenue or cost savings generated by the system. However, optimizing hardware and connectivity for cost is a difficult and time consuming effort on its own. Often teams are forced by management to come to the table during even ideation with solutions where the costs are highly constrained.

A better approach is to build “minimum viable” prototypes to help flesh out the business case, and spend time thereafter building a roadmap to cost reduction. There is a tremendous amount of learning that will happen once real IoT products get in front of customers and the sales team. This feedback will be invaluable in shaping the release product. Anything you do to delay or complicate getting to this feedback cycle will slow getting the product to market.

2. There is no IoT Platform that will completely work for your application.

IoT Platforms generally solve a piece of the problem, like ingesting data, transforming it, storing it, etc. If your product is so common or generic that there is an off the shelf application stack ready to go, it might not be a big success anyways. Back to #1, create some basic and simple applications to start, and build from there. There are likely dozens of factors that you didn’t consider like: provisioning, blacklisting, alerting, dashboards, etc. that will come out as your develop your prototype.

Someone is going to have to write “real software” to add the application logic you’re looking for, time spent looking for the perfect platform might be wasted. The development team you select will probably have strong preferences of their own. That said, there are some good design criteria to consider around scalability and extensibility.

3. Putting electronics in boxes is harder and more expensive than you think.

Industrial design, designing for manufacturability, and design for testing are whole disciplines unto themselves. For enterprise and consumer physical products, the enclosure matters to the perception of the product inside. If you leave the industrial design until the end of a project, it will show. While we don’t recommend waiting until you have an injection molded beauty ready to get going in the prototype stage, don’t delay getting that part of your team squared away.

Also, certification like UL and FCC can create heartache late in the game, if you’re not careful. Be sure to work with a team that understands the rules, so that compliance testing is just a check in the box, and not a costly surprise at the 11th hour.

4. No, you can’t use WiFi.

Many customers start out assuming that they can use the WiFi network inside the enterprise or industrial setting to backhaul their IoT data. Think again. Most IT teams have a zero tolerance policy of IoT devices connecting to their infrastructure for security reasons. As if that’s not bad enough, just getting the device provisioned on the network is a real challenge.

Instead, look at low cost cellular, like LTE-M1 or LPWA technologies like Symphony Link, which can connect to battery powered devices at very low costs.

5. Don’t assume your in-house engineering team knows best.

This can be a tough one for some teams, but we have found that even large, public company OEMs do not have an experienced, cross functional team covering every discipline of the IoT ready to put on new product or solution innovation. Be wary that your team always knows the best way to solve technical problems. The one thing you do know best is your business and how you go to market. These matter much more in IoT than many teams realize.

(source: https://www.link-labs.com/blog/5-keys-to-iot-product-development)

Learning – Building the Business Case

Firms cannot develop their IoT strategy a priori, as there is very little conventional wisdom to apply in this nascent space. It is only once real devices are connected to real software platforms that the systemic implications of the program will be fully known. For example:

  • A commodity goods manufacturer builds a system to track the unit level consumption of products, which would allow a direct fulfillment model. How will this impact existing distributor relationships and processes?
  • An industrial instrument company relied on a field service staff of 125 people to visit factories on a routine schedule. Once all instruments were cloud connected, cost savings can only be realized once the staff size is reduced.
  • An industrial convenience company noticed a reduction in replacement sales due to improved maintenance programs enabled by connected machines.

Second and Third order effects of IoT systems are often related to:

  • Reductions in staffing for manual jobs becoming automated.
  • Opportunities to disintermediate actors in complex supply chains.
  • Overall reductions in recurring sales due to better maintenance.

Costs of Scaling IoT

Certainly complex IoT programs that amount to more than simply adding basic connectivity to devices sold, involve headaches ranging from provisioning to installation to maintenance.

Cellular connectivity is an attractive option for many OEMs seeking an “always on” connection option, but the headaches of working with dozens of mobile operators around the world can become an problems. Companies like Jasper or Kore exist to help solve these complex issues.

WiFi has proven to be a poor option for many enterprise connected devices, as the complexity of dealing with provisioning and various IT policies at each customer can add cost and slow down adoption.

Conclusion

Modeling the costs and business case behind an IoT strategy is critical. However, IoT is in a state where incremental goals and knowledge must be prioritized over multi-year project plans.

Source: https://www.link-labs.com/blog/cost-of-iot-implementation

How Do We Buy Smart Phones?

11 Sep

Earlier this year we were fortunate to have entrepreneur, blogger and product strategist Mike Mace drop by and host a brown-bag strategy discussion with some frogs. One of the topics we discussed was whether smart phones have changed the way we think about buying phones.

Most frogs and Mike were in agreement that we bought our first iPhones for its shiny look and joy of the beautiful touchscreen. However, there was good debate as to whether that still holds true — or whether application ecosystems and services lock in second and third generation buyers, making them less likely to switch. Put another way, when you pick Apple/iOS or Google/Android, are you likely to remain a happy prisoner to your ecosystem or are you just as likely to switch when the new shiny device comes along?

To test this, I surveyed my colleagues at frog to assess their feelings about the Nokia Lumia 900 that came out this spring (more on this later) and their stated approach to buying phones. 82 frogs based in our US studios took part in my study. When asked directly about their phone buying philosophies:

  • 55% claimed to be iPhone/iOS all the way
  • 8.5% claimed to be Android enthusiasts
  • 36.5% claimed to have used a variety of smart phones are were agnostic to iOS, RIM and Android

When I cross tabulated buying philosophies with expressed interest in a new phone, iOS loyalists were the happiest of prisoners, in that 81% would not even consider another phone. Android fans were fairly loyal (50% would not consider operating system infidelity), and not surprisingly the agnostics were the most open to a new phone. Added up, roughly 1/3 of frogs were open to considering a new phone and new operating system. 

So what are the characteristics of the agnostics and unhappy prisoners who are open to a new phone/OS? What are the characteristics of buyers likely to fall for the hot new phone?  My hypothesis is that if OS switchers were evenly distributed across all levels of experience with smartphones, the shiny-device theory would hold. If they were clustered around first time buyers only, it would indicate that there is an ecosystem effect.

There was very little correlation between how many generations of smart phone the frog in question was on, and their openness to switching.  Those who had never had a smart phone were more likely to be interested, but the sample size of smart-phone virgins at frog was too small (just 3 out of the 82) to read much into it. As for the others, there was no significant difference between those on their second smart phone compared to those on their third, fourth or fifth. 

What other indicators might help us here?

Of all the things we tested, app use was the best indicator of willingness to switch. I asked each of the 82 frogs who participated in this study to think back through the last 24 hours and tell me how many apps on their phone they had used. I then grouped them into three buckets:

  • A light app user group consisting of those who had used 0-4 apps
  • A medium app user group who had used 5-8 apps
  • A heavy app user group who had used 9-25 apps

Cross tabulating interest in the new phone with app use was instructive.

 

 The light app users were significantly more open to getting the new phone than heavy app users. So it isn’t just how long you have been with one platform or another that matters, but how deeply you are into that application ecosystem. As the land-grab for first time smartphone buyers slows down, this has interesting implications for who to target with new phones. Going after all users seems to be a struggle but there may be a better strategy of targeting light app users. My colleague Hiro Ellis pointed out that if app use is related to operating system, I would just have found an effect. I tested this and found that iOS fans and agnostics were somewhat more likely to be heavy app users, but overall there was very little difference in app use by OS philosophy. 

One implication of this is that a switch to browser based applications will weaken the current lock-in effect. There is more to this story, but Apple and Google are both backing HTML 5 initiatives. They must be confident that we are happy prisoners who will stay with them even when the prison is unlocked and open, as opposed to unhappy prisoners, who bolt at the first opportunity!

Source: http://designmind.frogdesign.com/blog/how-do-we-buy-smart-phones.html – By Timothy Morey – September 10, 2012

%d bloggers like this: