Mainframe and the Internet of Things

March 10, 2015

Are you ready to jump on the IoT train?

A recent report of Goldman Sachs Group states that the Internet of Things (IoT) is the next megatrend. The 1990s’ fixed internet wave connected 1 billion users while the 2000s’ mobile wave connected another 2 billion.

The IoT has the potential to connect 10X as many (28 billion) “things” to the Internet by 2020, ranging from bracelets to cars.
IoT will have far reaching implications that touch every industry, from healthcare to retail to oil and gas exploitation and home building.
Just as the first 2 waves of the internet era led to profound changes in the economy, the IoT will create new winners and losers based on a company’s ability to adapt to a world where things are connected.

Mainframe blocking the road to innovation
The new world requires a new approach to new technology. Transforming Legacy Applications is mandatory in order to:

  • embrace new technologies, protocols and standards. The ‘old’ mainframe technology makes it difficult to connect to new technologies
  • to handle data and analytics. Legacy systems are not able to keep up
  • deal with security challenges. Cures for new threats are developed for new technologies first
  • smoothly connect/integrate all different environments – open systems are much easier connected than mainframe
  • avoid exorbitant operational cost. A drastic increase in workload and MIPS will drastically increase costs
  • keep up with the competition. Time to a solution is a major driver in gaining and keeping a competitive advantage. Legacy can be a major road blocker in the race for market share


Innovation is key if you do not want to miss the IoT train. It is clear that the mainframe does not offer the flexibility and agility required to adopt the new technologies. Although the transformation of your mainframe environment requires an investment the immediate cost savings, due to drastically reduced operational cost, make the ROI rapid and the investment worthwhile.

Don’t move the legacy issue elsewhere but solve it by truly transforming it….