Recent Entries
Weblog
Some Mobile Solution design tips
November 09, 2004
It strikes me that the "Mobile Solutions" industry is still underestimating the importance, and complexity, of successfully integrating handheld devices with existing "back-end" ERP systems. These systems range from tailored SAP or Siebel deployments, through ERP systems specific to an industry vertical, all the way to home-grown, evolved solutions used by individual companies. The goal of of a Mobile Solution is to put the power of these "back-end" systems in the hands of the mobile workers. But how?
Here are some things to consider when choosing a Mobile Solution...
Integrate, don't Aggregate. Many off-the-shelf Mobile Solutions mandate an architecture that may not suit your business or your IT systems. Why deploy Yet-Another-IT-System that wants to own your customer data / finance data / field service data etc.?
Design for Occasionally Connected clients. GPRS is not always on. Wireless networks are not always available. That's just how it is! Make sure your handheld application knows this and doesn't stop your mobile workers from doing their job when and where they need to. A web client connecting over wireless is usually not suitable.
Emphasise Data Integrity. Remember that your ERP system encapsulates the rules of how your business data behaves and changes over time. Some of this behaviour may be subtle and even undocumented in your organisation. Providing access to the ERP system via mobile devices must not lead to the business logic being bypassed for the expedient of a fast mobile solution.
Protect your Investment. IT Systems change with requirements. Don't choose the mobile solution that's provided as an add-on to your ERP system because (i) it locks you in and limits your choices and (ii) it may have been written by people that don't understand the complexities of mobile solutions.
Post a comment