Mobile enterprise application strategies need to consider that differences in business processes may be needed to achieve the highest degree of integration, security and transactional integrity. Part of that strategy may involve cloud-based servers and even software as a service (SAAS)-style deployment and consumption of business applications.
Regardless of approach, provisioning of users is a key consideration in any mobile strategy. Is the chosen approach to provisioning sustainable? Do new users require human intervention? How are users validated? What rights do they inherit? Only by a process of detailed business analysis can an organization establish the right procedural and strategic approach.
Many procedures and data structures may simply be "artifacts" left behind by manual processes or past approaches to automation. If that's the case, then the organization needs to ask if this step in the process is really necessary. What business need, accounting requirement or regulatory provision makes this data or process necessary? How can the new possibilities brought about by mobile computing enhance the customer or user experience? What is possible now that was impossible before?
By their very nature, mobile business applications may be enhanced by relevant geospatial data. At the IT level, device location and usage can be tracked and recorded for asset management purposes on a continuous and transparent basis. In ordinary business transactions, the location of a data entry terminal is typically fixed. In mobile applications, the location of the device may be changing all the time, and its current location and proximity to other mobile devices or known fixed locations may be a relevant aspect of a business process.
In a business application involving asset management, for example, the GPS location of the device at the time of data entry may be highly relevant. Midday routing and dispatching adjustments can be enhanced when the location of other mobile devices are known. Existing business applications may have been designed without the proper data structure to track geospatial metadata. Integration requirements should be addressed at a strategic level so that they can also be resolved on a practical level.