Mobile Enterprise Application Integration

The mobile paradigm extends beyond simple perceptions of PDA capability and enterprise utilization. It includes the integration of handheld and wireless technologies with existing corporate information infrastructures. Companies are beginning to see the Pocket PC for what it truly is: a fully enabled computer operating within the mobile context.

Whenever a new computing platform is released, the common reflex in the developer community is to "port" or convert existing software to the new platform. Unfortunately, since mobile devices like the Pocket PC are not used in the same way as other computing platforms are, software that is simply ported is rarely even usable because of basic differences such as screen size and input methods. In addition, in most cases mobile technologies should not replace existing technologies but rather extend them. Existing software systems can be mobilized by developing a new front end or mobile application that can connect to the back-end data store and/or business logic of the existing system through wireless connectivity or wired synchronization.

The following is the process of mobile enterprise application integration with existing enterprise systems.

The Mobile Enterprise Application Integration Process:

1. Existing System Evaluation.

The first thing to recognize when evaluating your existing systems is that not all systems need to be extended to mobile platforms. Heretical as it might be to suggest in this publication, certain users may simply get no advantage out of going mobile. Or perhaps a specific mobile application is not usable or even feasible. You need to look at the business process and usage scenario that is "wrapped around" your systems and determine whether location is even a potential value-added factor. Is the system working with data that is either collected or viewed on paper, and would eliminating the paper process be beneficial? Look for specific needs and inefficiencies. For instance, if the potential user is wearing thick gloves you probably could not successfully implement a system with complex user interface or navigation architecture. Finally, you need to make a bottom-line judgment about whether a potential mobile system would provide an overall positive impact on the business.

2. Common Functionality Identification.

After you have decided that a specific existing system has the need for a mobile counterpart, you need to identify the functionalities and capabilities that should be shared between the two systems. Keep in mind that a vast majority of the feature set is not usually applicable or appropriate for a mobile usage environment. You can start by defining the fundamental capabilities of the two systems. The goals and purpose (and therefore fundamental capabilities) of the mobile system will not necessarily be the same as those of the existing system. Most likely they will be similar but probably not identical. You can then discover the greatest common denominators between the two systems and determine the practicality of specific common functions for mobile uses. Functionality such as complex data input or heavy graphics is probably not appropriate for mobile usage, and an alternative must be discovered if the function is of critical importance. Think "out of the box" as much as possible during this process, and question your premises, because false assumptions in this step will doom a mobile system to failure. For success, just focus on the big picture and be open-minded.

3. Mobile System Innovation.