The long-term nature of industrial IoT connectivity is forcing carriers to consider the lifetime value of customers and adapt their pricing accordingly.
Enterprises are using ‘network unaffiliated virtual operators’ (NUVOs) to disintermediate MNOs and cut costs, and new SIM technology is helping NUVOs to optimize coverage for their customers.
As cloud and IoT become the dominant models for ICT, it is increasingly obvious that the networks are only a means to customers’ ends. Big beasts though they are, telcos are merely part of an ecosystem that supports customers. As such, the lifetime value of a customer who stays inside a telco’s ecosystem is higher than the one who churns after his two-year smartphone contract ends. Smart telcos are changing their business models to reflect this. Continue reading “The Embedded SIM: How It Is Making the Customer King”→
IoT is a strong focus for all ITSPs, but there are multiple organizational strategies used to accommodate the growth opportunity without diluting the ‘cash cow’ of traditional enterprise mobility.
Mobile app development is evolving to better meet the needs of customers with faster development tools, use of open source resources, and new development and delivery options.
Current Analysis provides biannual update reports on the mobility services of key IT service providers such as Accenture, IBM, T-Systems, BT Global Services, HPE and CSC. Our most recent updates show some key trends.
• Application platform vendors are working to build IoT initiatives based on integration infrastructure, app development tools, and business intelligence.
• UX has become mobile app development’s critical component for ensuring success around B2E and B2C apps.
Keenly aware that Mobile World Congress (MWC) is heavy with telco vendors, application platforms providers at last week’s event aggressively marketed their IoT and mobile initiatives to try to convince customers that their core integration technology provides the best foundational platform for expanding app development to connect to IoT devices. They are pressed to provide clarity around their IoT strategy, however, as the industry struggles to differentiate between various solution provider and service provider platforms.
• In IoT, connected car and other transportation verticals are seeing use cases from infotainment to automotive health and performance monitoring to fleet management. Asset tracking, retail apps, and utility management are also providing enterprise benefits.
• A number of promising new vertical solutions, technology enhancements and security services to deal with malware, data leakage, and security breach concerns are expected in 2016.
•SD-WAN products are well suited to address the complexity and scale of IoTAs diversity in IoT grows.
• SD-WAN vendors will be challenged to address the specific needs of new and increasingly specialized IoT products.
Commercial IoT networking in the short term is more about connecting and protecting IoT devices and gateways that are already deployed, or will be soon, rather than having to support a raft of new, IP addressable devices. The IoT name has been equally applied to what otherwise are called sensor networks, command networks, industrial Ethernet, and other network-attached devices. SCADA devices certainly fall into this realm. The difference being that these devices are being connected—on purpose or inadvertently—to public networks and exposing them to the potential for additional attacks. Continue reading “SD-WAN and IoT: A Long Road Ahead”→
Operators, OEMs, and service/application platform vendors keep hinting about converged services and platforms to manage both traditional enterprise mobility and IoT functions
Has the ecosystem made much progress in these efforts; does it need to make more?
Service delivery and management platforms for EMM and M2M/IoT have some similarities; EMM manages mobile devices used by people, by managing, securing and containerizing devices and the applications residing on them or accessed by them. IoT platforms for connected devices/machines are a bit different and tend to be divided into service delivery management, and application enablement, with device management sometimes added in and other times missing in action. The vendors that talk the most about bringing these two separate worlds together have been the mobile app platform vendors – if SAP, Oracle, IBM, HP, and Microsoft can help businesses develop mobile apps for smartphones and tablets, developing an app that collects and integrates data with back-end databases from wirelessly connected machines, vehicles, or sensors is a natural next step. EMM vendors such as Vmware/AirWatch. MobileIron, Blackberry, and Good include IoT routinely in their discussions of the future of the “digital workspace” but it’s not clear that many customers are using their platforms to managed connected IoT devices. Jasper and VMware have achieved some level of service delivery and EMM platform integration, adding the key element of device management element to Jasper’s IoT solution. Continue reading “EMM/IoT Management Convergence: Are We Making Progress?”→
With over 19 Internet of Things (IoT) radio protocols in use today, the need for consolidation is clear.
Short of consolidation, integration of IoT devices will occur at the application layer with robust APIs.
Many of the ‘things’ in the IoT like lights, sensors, switches, HVAC controls, and other actuators will be connected via wireless gateways because rewiring a building is expensive. I counted over 19 wireless protocols between standards-based protocols, proprietary protocols, and protocols that have a basis in both standards and proprietary protocols. Continue reading “Over 19 IoT Radio Protocols Drive the Need for Integration APIs”→
• Mobile application platform providers target Internet of Things with middleware gateways, advanced APIs
• Red Hat leverages JBoss integration, messaging; while Kony taps MBaaS MobileFabric
Mobile app platform providers are quietly assembling IoT strategies and solutions, based on their flagship middleware technology, in hopes of providing an important middle tiered component between devices and data centers. Here’s a quick peek into the early IoT efforts of Red Hat and Kony.
Red Hat refers to that middle tiered component as the control tier or the gateway. These gateways handle the data pre-processing necessary to stream aggregated data sets; and real-time analytics for rapid insight into the data in order to trigger business rules which control the actions at the device. Included in Red Hat’s set of middleware IoT building blocks is its Data Grid in-memory computing technology, its FUSE integration technology, and its A-MQ messaging to support data transport. And though it’s not required, of course Red Hat claims the most optimal experience is achieved when combined with the Red Hat Enterprise Linux (RHEL) operating system. Red Hat’s belief is that gateways provide the mechanism which allow the IoT to scale, solving latency problems between the device and the data center.
Red Hat does not offer a formalized IoT solution, rather it has assembled a set of building blocks based primarily on JBoss technology for enterprise customers building IoT solutions. The company has created a new subscription pricing tier to accompany these efforts, based on one to multiple workloads leveraging its gateways and RHEL. The pilot program is expected to be formalized within a year and I expect Red Hat will partner where necessary to fill technology gaps for issues such as systems level security.
Leading mobile app platform pure play Kony will leverage advanced API technology within its mobile app platform to connect to the slew of wearables hitting the market (think Apple Watch combined with Apple HealthKit). Like Red Hat, Kony sees its role as providing value around improving data streaming between the device and data center (i.e., at the event collection/orchestration level). Specifically, it is evolving its MBaaS technology, MobileFabric, to provide integration and messaging services to enable connection to the sensors used in wearable technology. (Please see Kony Addresses Agility, DevOps Concerns via API Management, Analytics, July 23, 2015).