|
This is the 6th article in a series on using Mobile computing. There are many considerations for firms to consider when building mobile and wireless-internet based systems. It is a complicated topic and involves ego’s, hardware, software, networks, processes and most importantly making profit !
Topics to be covered
|
1.
|
Processes and methodologies to follow
|
|
2.
|
Vertical markets where wireless and mobile is driving profit
|
|
3.
|
Hardware, devices and selection criteria firms need to use
|
|
4.
|
Software, applications and selection criteria firms need to use
|
|
5.
|
ROI models
|
|
6.
|
Real World examples and Case Studies of Wireless architectures
|
|
7.
|
The Future of Standards, devices and networks and their impact on business productivity and processes in Canada
|
4. Software, applications and selection criteria firms need to use
The choice of software for mobile and / or wireless computing is dependent on a number of inter-related factors;
11 Key Points in choosing your software;
|
1.
|
Who is the project champion and what is the political risk – reward reality within the firm. Ie. Who will stand up and be counted to ensure the system works.
|
|
2.
|
Political factors regarding technology choice [for instance Microsoft supporters vs. Java supporters, or IBM vs. Oracle etc.].
|
|
3.
|
The key Competitive pressures and problems/bottlenecks we are trying to solve and counter-act.
|
|
4.
|
The type of business process which is being automated or extended from the existing IS systems to the mobile environment.
|
|
5.
|
Your budget and the project leader’s experience with software applications.
|
|
6.
|
The type of software available in your vertical and the maturity of the software.
|
|
7.
|
The hardware device choice and how it will interact with the business process and software.
|
|
8.
|
The type of networks needed to support the system – ie. Internet, 2.5 G Cell network, 802.11 Wi Fi etc. These will impact the data transfer speed and type of data.
|
|
9.
|
End User skills in using software and hardware and the training needed to get them up to speed.
|
|
10.
|
Your in house IS skills and the ability to manage the system in house vs. outsourcing.
|
|
11.
|
Your existing data systems and applications and issues pertaining to security and extension of these systems to a mobile environment.
|
The above is a simple list but it gets complicated fast. People always ask what comes first ? Well the 11 points above all come first. You must address them all.
It is best to take these 11 key points that everyone knows [but usually ignore] and look at them in logical clusters – this will lead you on to the right path and right choice for your software. Typically a rationale roadmap is:
The recycling process might take a few iterations but the clustering ‘checklist’ has to be done properly. If you miss some areas, the project or the software choice might enjoy a rough ride from various sides. This is why many projects are typically managed by an exalted leader, who manages a ‘Steering Committee’ containing a person of every possible political persuasion. Some firms have the visionary and courageous leader who will implement the right solution regardless of political pressures. This personality is rare.
The Business Cluster provides the following;
 Some if not all of the budget- The Business champion, leader, and evangelist
- Requirements for the hardware and software
- End user requirements and preferences on the hardware and software
- Change management to change end user behavior once they start using the software
The Technology cluster must use the business requirements and political factors in building an easy to use and simple to use system. System simplicity is a must, not a nice to have. The software application must be easy to use for the end user and just as importantly -- FAST. It needs to eliminate the 2 or 3 major headaches that the business side currently is experiencing. As well it should not disrupt existing IT operations nor compromise existing IT data models.
The software choice will depend on a simple matrix that encompasses the key factors in looking at which software to buy.
For example if you wanted to implement a Palm based solution for CRM you would quickly find that as you work your way along the rationale for such a system a number of issues crop up, including; device robustness, Java based code [very difficult to find good java programmers], lack of vertical applications, weak legacy system integration, missing functionality, issues with memory and speed. The technology must fit the business process and solve business issues. If the choice of Palm or another device and OS is a political decision don’t expect the business issues to be resolved.
Most projects fail when many of the above issues are not addressed. Top Management ownership and political support are imperative to secure proper financing, problem resolution and to ensure that end users do not destroy the system through a rejection of technology through the perceived ‘big brother’ effect. To deploy a project properly you need to use the above 11 points and matrices and follow a robust methodology – much like what an Object Oriented Analysis and Design methodology offers. Link here for more information on methodologies:
For specific software products and solutions by device choice please email me @ . In General the following are good guidelines:
- Field Systems; PDAs running Pocket PC software from vertically focused firms. Do not extend ERP systems to the Field unless you have a lot of money that you like to waste.
- Internal Mobile systems such as Warehousing: Intermec or Symbol Pocket PC devices running a WMS system tied in seamlessly with your accounting system. There are many good WMS products available in a range from ‘light’ to ‘heavy’ applications.
- Management systems: Pocket PC or RIM running data access software.
In general I would stay away from Palm systems and ‘Smart’ phones – neither of these devices nor their associated systems offer a robust business solution, and their operating systems require non standard coding and integration problems.
Craig Read
Craig is a director of IT at a Toronto based mobile and wireless firm. Craig also founded the Toronto Wireless User Group which now has well over a hundred members www.torwug.org He can be reached at
|
