Integrating Legacy Tech on the Internet of Enterprise
As enterprises careen toward updating legacy tech, see what to keep in mind when integrating it with the newest, latest, greatest systems.
Join the DZone community and get the full member experience.Join For Free
every enterprise is a brownfield scenario. many legacy devices, especially those used in commercial and industrial applications, tend to have long life-spans. existing devices/tech haystacks, in an enterprise, make up 85 percent of all devices (ims research), all of which mostly run isolated applications. when new data networking capabilities come along — we don’t uproot our existing infrastructure and start all over again — we layer them on top of our existing networks, continuing to improve and enhance them as we go. this drives business transformation to optimize the efficiency of old and new devices, prevent failures, and create new services.
transforming siloed it/ot to unified digital enterprise
here’s where ‘internet of enterprise’ provides the answer. but unfortunately, most iot applications ship ‘one-size-fits-all’ solutions that lead to dead-end dashboards. they answer a predetermined set of questions, where going beyond what we’ve been given turns out to be a can of worms. let’s say we have an iot enablement application that assures to manage diesel generator(s). the application reads historical performance data of generated power, battery voltage, run hours, fuel level etc. but what if you’re to manage multiple diesel generators distributed demographically — like telecom base stations, cell towers, remote atm sites — all of where dg plays a critical role of primary and backup power source.
these assets are quite prone to instances of fuel leakage, maybe a cracked coolant pipe, or possibilities of even fuel theft. you’re to identify conditions that led to downtime, probably predict how often the failures are likely, drill down on parts/systems that fail most often, the manufacturer of these parts, the supplier that caused most issues, and all of this across varied periods of time. at this point, you will certainly require a platform that transforms traditional scada to iot-enabled connected infrastructure.
keeping these exact pain points in mind, we’ve engineered ‘edgex’, a multi-vendor, multi-technology software agent. edgex is more than just a conventional agent, in which it enables real-time acquisition and blending of data within verticals and across a wide range of industries – thus, laying the groundwork to unified connected business.
true connected infrastructure
likewise, enterprise iot will allow building management systems (bms) to evolve from just operating as unconnected systems. instead, these systems will operate as part of a broader and smarter network. buildings are incorporating lighting and power monitoring systems, water harvesting and hvac equipment on the internet. these connected systems collect and analyze data enabling optimization of various operations of a building. today’s bmss are mostly proprietary solutions that can only be upgraded by the system manufacturer — a time-consuming and expensive pursuit. the transformation requires not only a technological shift, but a movement towards open business models that allows third-party providers to develop and integrate bms with an iot aep platform.
and with the case of platforms, there is no shortage there. clearly, the number of platforms appears to be growing by the day and the competitive pressure in iot software market is a lot heavier now than ever.luckily, the internet isn’t just one network — a heterogeneous mix of old protocols (likes of ethernet, wireless, radio, gsm, satellite, bluetooth) and new ones (likes of sensor networks, zigbee, sigfox, lorawan, nfc, and a whole lot more). this means devices must communicate with each other, device data needs to be collected and sent to server infrastructure for analysis, integration and sharing. all of this requires ‘data’ to be moved from point a to b.
sounds simple? no.
iot orchestration (legacy+iot tech stack) requires clear-defined agent libraries to be set up for every individual device vendor and type. this is a lot of work from the standpoint of your it staff or network engineer. something as basic as a door sensor that sends digital signals has to be integrated into the platform as one use case and data from your staff’s ticketing app needs to be integrated for another use case. this very often needs a standardized communication interface to the platform. here’s wherewebnms does the heavy lifting for high-volume, high-drill down usage across multiple enterprise verticals. what sounds simple is however not easily achievable and usually requires expertise and an enterprise-scale software framework. sure you could use multiple pi projects and diy apps but be prepared for massive efforts and laborious swivel-chair integrations. as far as enterprise iot solutions are concerned – a platform that scales, unifies, and provides flexibility to integrate with existing it/ot through open apis, is pretty crucial.
with edgex, powered by webnms symphony iot platform, you can establish a stable communication, acquire, analyze and gain insights from data across multi-vendor, multi-protocol and multi-vertical environment.
Opinions expressed by DZone contributors are their own.