https://twitter.com/ChadKJackson/status/1009101128930418688
I think this is one of the most frequent mistakes that companies make when thinking about IoT efforts. Many get so wrapped up in the technology, and the hyperbole that anyone without an IoT initiative will go out of business, that they rush ahead without thinking how will this make the company save money or make more money. This really is true of any technology-led engineering initiative. But I do see lots of companies struggling with this in particular with IoT. It is so wide open in how it can be applied. So my takeaway is to first identify your biggest problems; period. Then brainstorm on if an initiative like IoT… or something else… can address it.
https://twitter.com/ChadKJackson/status/1009093944205021190
This is a fair point. It can help to abstract the technologies away. What is key, however, is to identify which capabilities enable which activities that support the business change. So if you need real-time visualization of how a product is performing in the field, you better figure out what technology or set of technologies is going to make that possible.
https://twitter.com/ChadKJackson/status/1009093393086107648
I wholeheartedly agree with this approach. In fact, I think this applies to modern PLM as well. Start small. Get a win. Document it. Showcase it. Then other organizations in the company will start to get involved and even request involvement.
So that’s it. Those are the takeaways. And I think the closer you look at something like this, you find that an IoT effort is no different than any other technology-led engineering initiative.
Get Research-Backed Guidance
Join InsightEX for independent insight on engineering transformation. No vendor bias, just what works.
Join InsightEX →