Continuous Connectivity: An IoT Imperative

By Special Guest
Frank Knox, Co-Founder, Chief Technology Officer, Edge Velocity
January 03, 2018

We all hope that 2018 is the year that IoT truly flourishes, as the capabilities and data gained from connected cities has the potential to help mankind in many ways. From safer cities, to more efficient enterprises the benefits of connected things offer a world of potential – as long as there is connectivity we can count on.

For connected devices to provide any form of meaningful value in 2018, first and foremost they need connectivity – and not just any connectivity. The connectivity needs to be the ‘always on’ type as applications, such as Safe City implementation, will require continuous, uninterrupted connections to effectively capture and communicate data in real-time. Think about it, in an application such as surveillance, the data gained can vary significantly from one to second to the next, with even the slightest amount of “downtime” negatively impacting the potential value that can be provided.

We believe strongly that IoT success in 2018 is possible, and that the type of “continuous connectivity” that is required is now ready for prime time. While this has not always been the case, today’s technologies have evolved into truly intelligent offerings that are smart enough to find alternate communications paths in the event their primary connection fails. By placing intelligent, software-based solutions at the network’s edge, we now have the capability to ensure that the connection to devices, things and sensors scattered across a dense metropolitan environment will never be offline.

From connected light bulbs to autonomous driving, we now have the ability to connect anything, anytime, anywhere with complete confidence. As a result, we expect that in 2018 we will see enterprises, municipalities and organizations more fully invest in their IoT and Safe City initiatives, and that we will finally be able to realize the benefits of a connected culture.




Edited by Ken Briodagh


Original Page