For the past few years, analysts have touted M2M as a rapidly growing market full of promise. Technologies such as web services, XML data schemas and RFID were expected to impact the market's growth, as is remote device server technology, which effectively enables M2M communications and is the foundation for distributed device intelligence. The market for M2M is ripe with possibility due to the convergence of four major trends: the omnipotence of the Internet now connects everyone and everything; users now expect continuous access to information; users now recognise the need for, and value of, real-time information sharing; reduction in both the size and cost of networking hardware.

But even with the huge expectations surrounding it, the M2M market has seen slower-than-expected growth. This is largely due to the fact that companies see the difficulties and risk of designing with disparate technologies that are needed to make M2M a reality. There is also uncertainty about the results and ROI of implementing these solutions.

There is no doubt that the technologies required to make M2M a reality are readily available, from hardware to software and from user interface to server-side applications. What has been missing is a single source to unify implementation. By putting all the pieces together, suppliers will inevitably create more advanced systems that make it easier to share information.

The first step to moving toward total information convergence is the adoption of device-networking technology within the market. While this has been achieved, the next step is for suppliers to provide the other piece of the puzzle. Once this has been achieved, vendors will be more likely to stick with the same supplier, creating long-term partnerships that will drive the creation of complete solutions and grow confidence in M2M. Beyond that, suppliers can work together to create total solutions that will gain wider acceptance of the M2M promise.

M2M-application possibilities

Remote device management via device servers allows users to proactively monitor usage and performance of equipment from anywhere, anytime. The ideal solution is one that is fully-automated, programmable and ubiquitously available to users. It should also be an effective end-to-end system that is capable of managing the complexities and inherent risks of implementing a comprehensive M2M solution based on otherwise incompatible devices.

With autonomous device control, users have the ability to anticipate problems before they occur and even prevent them. When a problem does exist, they can remotely identify and diagnose it before deploying technicians, making repairs more efficient. In some cases, problems or actions that would typically be addressed by a technician or require human intervention could actually be handled automatically by networked equipment in real time.

The ability to utilise existing web tools to automate reporting and centralise device management leads to more efficient processes. Beyond internal operations, the application of remote autonomous device control can result in improved service for customers, thereby enhancing customer relations. Results are generated more quickly due to remote access to controls for problem detection, streamlining of diagnosis and repair, and the ability to partner with others to troubleshoot issues more efficiently. Service management can also be improved through reporting tools, dashboards and metrics. Having access to usage and equipment monitoring data enables preventative maintenance, saving organisations from unnecessary downtime.

Real-world applications

As the promise of M2M states, the better technology gets, the more machines will begin to interact directly with each other and the network, requiring less human intervention. Virtually everything that has anything to do with information management and control is now becoming Internet- or Ethernet-connected, meaning that machines are already working together. Consider the following example, which illustrates the use of device servers for maintaining security in a facility.

Most large facilities have a number of security cameras placed in critical areas throughout their premises, which are generally connected to the network or Internet via device server technology. With the use of these device servers and networking technology, security guards can monitor all cameras remotely. If an incident occurs, the security guards are notified, at which time they have the opportunity to manually locate the specific camera recording the incident and zoom in for more information.

When a programmable device server is connected to the cameras, the security system can incorporate programs that will automatically pan and zoom the camera if a person walks by the camera; subsequently, it will, as defined by the user, not only trigger an alarm but initiate other associated events such as turning on the lights or reporting the identity based on a proximity reader or other identification systems. Users can also program the device server to react to more than one event simultaneously. For instance, if a wire is cut or the door is not shut within the allotted time, the device server can trigger an alarm or notify security (Figure 1).

Figure 1: An example of M2M in a security application.

With convergence comes end-to-end networking and communication. This means that an alarm can trigger other actions unrelated to the door to take place. For example, it can send an email to employees of a high-security facility to lock down their workstations. It can also signal security to look for authorised personnel who chould be walking through the doors at a given time and for those who tend to prop the door open, then send an email to any violator's management to assure the event does not repeat itself.

On example of autonomous network control is EventTrak from Lantronix. This scripting language enables the monitoring of events and allows appropriate actions to be taken when necessary. When an event occurs, automatic pre-determined, user-defined commands are sent to the equipment, causing it to take appropriate actions - all without any user intervention. Notification can be sent via email when an event is detected and handled accordingly. It allows users to specify chain definitions (series of events/actions) that can be not only be saved, stored and transferred from one device server to another but also allow interaction between multiple device servers, providing a great deal of flexibility for large-scale deployment (Figure 2).

Figure 2: An example of large-scale M2M deployment.

Much like the convergence of features and services that catapulted the smart-phone market, M2M total convergence (otherwise referred to as iM2M) will take on considerable importance as those suppliers who support it provide OEMs with full end-to-end solutions that give users the freedom, flexibility and immediate remote access to the intelligence they need. Once that happens, M2M will evolve from a novelty that sets users apart from their competition to a necessity for providing customers with the services they require. iM2M anyone?