In the near future, you may hear about the appointment of a Chief Internet of Things (IoT) Officer. Before you roll your eyes and chortle at the thought of another chief-of-something, consider the problem.
First, companies are beginning to make and implement smart, connected, data-producing products. That can be anything—automobiles, assembly line robots, washing machines and even coffee makers. This data can be used in predictive analytics to avoid product failures, as well as to schedule maintenance around when a product actually needs it. These products, mechanical and electronic, will likely get ongoing software updates.
Second, connected products are now part of a broader system. Or as Michael Porter, a Harvard economist, pointed out at this week's ThingWorx conference, you aren't just selling a tractor, you are selling a tractor that is becoming part of a smart farm, a system. Things have to be able to work together.
(Score: 2, Insightful) by Anonymous Coward on Saturday May 09 2015, @11:19PM
Seriously, this is a fucking dumb submission.
The Chief Technology Officer (CTO) already cares about this shit. She's been considering IoT and dealing with it for years, for crying out loud. There's no CIoTO because the goddamn CTO already does his job!
(Score: 3, Funny) by pe1rxq on Saturday May 09 2015, @11:33PM
I beg to differ. There are limits to the amount of incompetence a single CTO can spread around. The limit is pretty high but at some point the amount of technology within a company gets high enough that some gets past unnoticed and actually works. Having an IoT (I like how it sounds like 'idiot') will ensure nothing usefull gets done with it. No matter how stupid most of the 'internet of things' buzz is anyway.