40 Reasons to Convert from Paper Processes to Mobile Applications on Smart Phones and Handheld Computers

This article describes the value that mobile software applications on handheld computers, Smart Phones and PDAs can provide businesses:

1. Eliminate time spent in the re-typing data collected in the field.
2. Reduce time spent on the phone dispatching service tickets, rather dispatch direct from your office computer to the mobile handheld computer in the field.
3. Send driving directions in the mobile work order to save driving time and fuel costs.
4. Save driving time by wirelessly synchronizing work orders with the office.
5. Reduce fuel costs by minimizing the need to drive back and forth to the office to deliver paper work.
6. Provide better customer service by accessing their account information via wireless connectivity on your handheld computer.
7. Improve the efficiency of field data collection by using barcode scanners or RFID readers for rapid asset tracking.
8. Improve the quality of work by providing real-time management visibility to work being done in the field.
9. Create and schedule service tickets direct from the field. Reduces the need for an administrative intermediary.
10. Immediate invoicing for faster collections and better cash management by synchronizing with the office accounting system or by using a mobile printer and credit card swipe machine on the handheld computer.
11. Proof of work – GPS audit trail of work with date and time stamp documents location and time of work. Reduces invoicing disputes.
12. Reduce introductions of human errors with automated business processes and systems integration. Move electronic data from the field to your database applications without human intervention.
13. Ensure complete data is sent from the field – incomplete data wastes time tracking down later.
14. Avoid handwriting and translation errors by pre-populating electronic form information.
15. Validate answers on mobile handheld PDA forms – to ensure data accuracy.
16. Take digital images to document work and avoid invoicing disputes.
17. Push data to the handheld and avoid time communicating information on the phone and writing on note pads.
18. GPS tracking for reduced travel time and lower fuel consumption.
19. Compute and analyze data on the handheld in the field – programmed analytics can help field users make quicker and better decisions.
20. Automated business processes - your mobile application can be configured to perform all kinds of automated business functions, queries, computations, analytics and many more time consuming features automatically based on data input or buttons pushed.
21. Enforce business processes for efficiency and best practices - mobile software solutions can be configured to ensure the field user follows the appropriate business processes.
22. Avoid lost data —capture data immediately and sync to headquarters.
23. Avoid undocumented inventory usage and unbilled time due to forgetfulness. Enforce real time data entry at point of work.
24. Require clock in and clock out at jobsites to document the accuracy of work/time estimates.
25. Train new service technicians and inspectors with audio memos or video clips.
26. Capture digital signature for proof-of-delivery and proof of work on handheld computers.
27. Query for available mobile inventory in nearby work vans to save travel time, inventory and fuel cost.
28. Use product and services information on handheld computers to up-sell.
29. Query latest shipping status and/or inventory levels via handheld computer while onsite with customer.
30. Automatically capture date and time stamps on your mobile handheld computer to document work and inspections times to limit liability and invoice disputes.
31. Use mobile technologies as a competitive advantage and show instant visibility to work, shipping status, schedules, inventory and account status.
32. Demonstrate to potential customers the competitive advantages of including GPS, time and date stamps, digital images, audio memos and more to document work and synchronize with the office using your handheld computer.
33. Download product warranty information to the handheld computer for review and presentation at the point of work.
34. Using rugged handhelds are often easier to carry around at job sites and are more durable than using laptops—lower ownership costs.
35. Mobile handheld computers with barcode scanners capture data quicker than typing on a laptop.
36. Combine your phone, GPS device, laptop, digital camera, paper forms and barcode scanner all on one mobile handheld device to save money, weight and support costs.
37. Combine job estimates, inspections, work orders, mobile inventory, time sheets all on one mobile application and one synchronization platform to mobilize and automate the entire business.
38. Scale your business by lowering administrative costs and the administrative work required to run the business.
39. Improve profits by analyzing real-time data collection on handhelds to understand the amount of time each task takes—so better scheduling and estimates can be implemented.
40. Push data to the handheld and avoid time communicating information on the phone.

How do you select the right handheld computer or Smart Phone?  This article lists 54 questions that will help you identify the right kind.

If you would like to discuss any of these topics in more detail, or to discuss your mobile project or application requirements please contact us.

Mobile Software Applications - 58 Questions the IT Helpdesk Needs to Know

Often the focus of a mobile software project is on gathering the functional requirements, designing, developing and deploying the mobile solution, but little or no advanced focus is given to the question of how to support it once it is deployed. The following list contains many of the questions your IT helpdesk and support department will want to know:

1. Who does the field worker call if there is a mobile device problem?
2. Who does the field worker call if their mobile application is not synchronizing?
3. Who trains new employees on how to use the mobile application?
4. If there is a mobile software problem, who fixes it - IT, consultant, contractor, or your systems integrator?  How do you get in contact with them?
5. Who does the field worker call if the mobile application needs edited or upgraded?
6. If the user downloads a new version of the mobile operating system and the mobile application doesn't work, who will repair it?  How do you prevent mobile users from downloading new software applications that might break the system?
7. Who defines the business process you are mobilizing? They may need to approve any changes to the business process.
8. Who controls the security of the device? How do you set-up a new user to securely access the enterprise database? What kinds of security rules must the field user follow? Do different users have different security profiles? Is there a standard set of rules for mobile devices across the enterprise?
9. Who controls access to the enterprise database application (a DBA)?
10. Will the Database Administrator allow you to synchronize data directly to their enterprise database application, or do they want a "staging database" or API layer to review all data before it is loaded to the enteprise database application. They will likely be involved in any future changes to the mobile application.
11. How many different enterprise database applications are synchronizing with a mobile device? If there is a sync problem, how do you know what database applications may be impacted?
12. If you hire an additional field worker, how do you order an additional mobile device? Whose budget covers this? Who is the vendor?  What support plan or insurance plan should be included?
13. Who decides if the new mobile device needs to be ruggedized or a consumer grade? What level of ruggedness is required for the specific user?
14. Do different job functions require different devices, carriers and wireless data service plans?
15. Who decides what brand of mobile devices are going to be the company standard?
16. Where do you purchase your mobile devices if one breaks or you need to add one to your inventory? Do you have a corporate discount or volume discount?
17. How do you control the variable costs of using a data plan from a local wireless carrier? What happens if the costs of the data services gets out of control? Who pays for it?
18. Are the mobile devices or the mobile software solutions under warranty?
19. Is there a yearly support contract IT needs to know about? How much? Whose budget?
20. What is the account number the warranty is under?
21. How do you set-up a new data plan with your wireless carrier? Who does that in the company? What is the account number so you can add subscribers? Whose budget pays for it?
22. What happens when Microsoft releases a new Windows Mobile operating system and you can only purchase mobile devices with the new OS on them? Who is going to upgrade your mobile software solutions so they work with the new OS?
23. What happens when the field engineer tromps off across 2 miles of muddy field to work at a construction site, but the battery on his handheld computer is not fully charged and it dies about 10 minutes after he gets there? What is the backup battery plan?
24. What happens when text messages, photos, videos, music, and 97 saved solitaire games claims all the memory on the PDA and the Construction application becomes either too slow or unreliable because of low memory?
25. How do you know when your mobile workers are synchronizing the latest information? You don't want mobile workers going days without synchronizing their device.
26. When you send an updated software application to your mobile workers, how do you know who is using the new application and who is still on the old?
27. How do you disable synchronization on a lost mobile device?
28. How do you kill and/or protect your data on the mobile device if it is lost or stolen?
29. How do you keep track of which workers are using which mobile devices? If there is an operating system update, or firmware update, how do you know who needs it?
30. What is the process for bringing mobile handhelds into the IT department for repairs and upgrades?  Is there a central location, or should various locations be scheduled on specific dates.
31. If you are taking care of many different mobile field workers and many different mobile devices with a variety of operating systems and screen sizes, how do you track who gets what?
32. If you have a project manager that requires visibility to more data than other workers, how do you manage different views on the handheld computer?
33. Some mobile projects require different levels of security, for different levels of data visibility. How would you manage and track that?
34. Some applications require barcode, RFID, GPS, digital camera and other specialized data collection accessories, while others don't. How does the IT Helpdesk track the brand, version and other details of these accessories?
35. If a dump truck backs over your supervisor's $1800 ruggedized computer and crushes it into hundreds of unidentifiable pieces, how do you get a replacement out to the supervisor with the exact application and data that is required?
36. If a mobile device needs repaired - what is the process for keeping your field workers operating without it? Do you have a stock of spare mobile devices?
37. How do you deploy new mobile applications to your 1,300 mobile device users? Must they bring all their devices back to the IT department, or can you publish new applications directly to the handheld computer?
38. How do you support the mobile device, when the user has limited computer knowledge and is sitting on the top of a utility pole? What tools can the IT Helpdesk use to help diagnose problems?
39. How do you recognize a defective mobile device that is being shared by 12 different mobile workers? Do you have a method of identifying which problems are being reported on a particular device or are you logging support calls only by users?
40. What is your process for dispatching work orders to service technicians when they are disconnected or out of range of cellular and wireless networks? A process needs to be defined.
41. What is your synchronization plan for each mobile worker? Can they sync in the morning and evening at their office desk, or do they need to sync every 5 minutes or in real-time?
42. What is the synchronization plan for a service technician that rarely has wireless network access? Does it justify a satellite up-link? (Sears Service Technicians use both)
43. How do you know when information was successfully synchronized with a mobile device in the field? Can you see and determine the success of the synchronization from the IT Helpdesk?
44. What is an acceptable synchronization time? Is it 20 seconds, 2 minutes, 20 minutes? Does the IT Helpdesk know what times are acceptable so they can consider this when configuring a new user?
45. How much data can be synchronized in a given period of time on the chosen connectivity option? Is that an acceptable speed for the task at hand?
46. Who determines the hardware requirements that support the mobile application and desired synchronization speeds?
47. When a new mobile software application is developed, who tests its operating speed on different devices, processors, memory levels and connectivity options to determine what is acceptable and what is not?
48. When you are updating or reconfiguring an enterprise database, how do you know what mobile applications and mobile users will be impacted by these changes? How do you manage this update process?
49. How does the IT Helpdesk know which one of the 17 mobile applications on the handheld computer is having a synchronization problem?
50. If you are supporting 174 work crews and their mobile devices around the globe, how do you know where they are located, and who is responsible for them?
51. How does the IT Helpdesk know if a mobile device is using a cradle, modem, bluetooth, wireless, USB, satellite or Cellular connection to synchronize? The IT Helpdesk really wants to know before they begin working on the issue.
52. What wireless carrier, technology and through-put speed is the mobile device using? Is it GPRS, GSM, CDMA, Edge or some other network configuration?
53. Do you need to stagger the synchronization times?  One of my clients had a problem with 300 mobile workers downloading large product catalogs all at the same time each month.  The first Monday of the month.  This caused a bottleneck and slow downloading time.
54. What do you do with old and retired mobile handheld devices? Companies like Ryzex buy back old handheld mobile devices and recycle them.
55. What rugged or semi-rugged cases are required to protect the mobile device?
56. What add on assessories are supported on the mobile device?  Ear pieces, GPS, add-on RFID, barcode scanners?  Who supports these and where do you order replacements?
57. Does the same mobile application work on rugged mobile handhelds as mobile consumer devices?  What employees get the different levels of rugged devices?
58. Do you have a corporate account with a mobile device reseller that will repair all of the different mobile devices or do you work with many different vendors with different support and warranty plans. 

These questions are very important and need to be answered upfront.  If you would like to discuss this subject in more detail please email.