Mobile Software Application ROIs for Mobile Service Businesses

The ROI (return on investment), in this context, is the term used to describe the value of a mobile software solution relative to the expense of designing, developing and deploying it. If a mobile solution cost $145,000, how do you justify the investment? Management needs to see that their investment will provide a quick and positive return. The following list contains some of the most common justifications for mobilizing business processes:

1. Eliminate time spent in the office re-typing data collected in the field: Enable field service technicians to synchronize information directly with the office database.
2. Eliminate time spent on the phone dispatching service tickets or work orders. Both the time of the dispatcher and the time of the service technician: Dispatch electronic service tickets direct from your work order management system in the office with the mobile device of your service technician.
3. Save time finding each work location: Send driving directions, or links, in the electronic work order that work with the GPS and mapping software in the mobile device.
4. Avoid the high fuel costs incurred delivering paperwork to the office and picking it up: Synchronize the data direct from the field to the central database application.
5. Avoid the time cost transporting paperwork from the field to the office: Synchronize the data collected from the field with the push of a button.
6. Save time and provide better customer service by providing real-time access to enterprise parts, orders, and inventory data while in the field: Enable mobile access to customer history, product documentation, warranty information, inventory information, time sheets, work schedules and much more.
7. Save time with field data collection by using barcode scanners and barcode labels, or RFID readers and RFID tags on assets: A quick scan with a handheld computer can automatically display all stored information related to the asset for quick review, edits and additions.
8. Save time and reduce admin costs by creating and scheduling new service tickets direct from the field:
9. Provide immediate invoicing for faster collections and better cash management: Allow field tech to print the invoice on a mobile printer at the job site.
10. Save time and postage costs: Print the invoice and leave it with the customer at the job site, rather than wait and bill later from the office.
11. Document proof of work completed to reduce invoice disputes: Leave a GPS audit trail of where work was performed and include a time and date stamp. Digital photo evidence of before and after work is also useful.
12. Reduce the introduction of errors: Paper based systems are inherently slow and error prone due to human interaction, copying and re-typing. The more human hands that touch a paper form and add or edit data, the more chances that errors can be introduced to the data which will cause invoice disputes, inaccurate records and confusion.
13. Reduce administrative costs by ensuring complete data is sent from the field, as incomplete or inaccurate field data can take hours of work to track down and correct: Send data from the field and ensure it is complete with data integrity features on the mobile handheld computers and rugged PDAs.
14. Reduce administrative costs by avoiding errors and misinterpretations due to poor or misread handwriting: Create electronic forms with pre-made options, check boxes and lists, and by using onscreen digital keyboards.
15. Reduce administrative costs by ensuring the accuracy of data: Validate answers in the mobile software application on the handheld PDA.
16. Reduce time on the phone and dangerous note taking while driving: Push documents directly from the office to the handheld.
17. Save time and fuel by providing electronic dispatch and least cost routing: Use vehicle and/or handheld GPS tracking to view your workforce locations. Handheld computers with GPS functionality can integrate with GIS and display the location of the field worker to help managers better organize service responses.
18. Save time by developing computation and analysis features on the rugged handheld in the field: Programmed analytics can help field users make quicker and more accurate decisions and job estimates.
19. Save time in the field by automating business processes in the mobile software: Mobile application can be configured to perform all kinds of automated business functions, queries, computations and analytics.
20. Enforce quality work habits: Automate “best practices” into your mobile software application and provide visibility to managers.
21. Automate quality and best practices - Activate the appropriate business process based upon the data entered: A specific answer can trigger the required business process.
22. Reduce inventory loss - Avoid undocumented inventory usage and unbilled time: Enforce real time data entry before clock out or work order completion.
23. Improve job estimates: Require clock in and clock out on work to document and analyze the accuracy of work estimates.
24. Improve technician training: Train new service technicians and inspectors with audio memos or video clips in the handheld computer application.
25. Reduce disputes by documenting deliveries and work with digital signatures, date and time stamps and barcode scanners on the handheld computer.
26. Save travel time and fuel cost: Query available inventory in nearby company vehicles.
27. Increase profit per customer: Use information on handheld computers to up-sell more products and services while onsite with the customer.
28. Provider quicker and more accurate estimates: Query latest shipping status, schedules or inventory levels via handheld computers while onsite with customer.
29. Increase warranty revenues: Include updated customer information on the handheld computer so the service technician can sell warranty and maintenance plans, new products and upgrades.

These are just some of the common areas where enterprise mobile applications have been found to provide significant value. The issues and costs of designing, developing and deploying the mobile software applications and handheld computers are discussed more in this article.

If you would like to discuss this subject in more detail please email me.
***********************************************
http://mobileenterprisestrategies.blogspot.com/
***********************************************

Hosted or Non-hosted Mobile Software Applications for Handheld PDAs and Smart Phones

Many companies have asked whether a hosted or non-hosted enterprise mobile software application would be best for them. The answer may be best determined by the following questions:

1. Is the enterprise software application in the office that you want to communicate with, via mobile handhelds, an off-the-shelf application like SAP, SAGE, MS Dynamics or Quickbooks?
2. Is the mobile software application simply a mobile front end (GUI) to the back-office application? Does it do basically the same thing you would do on the office application, but in a mobile environment?

If the answer is NO to any of the above, then you are into a custom development environment that is difficult to support in a hosted model. Companies that host applications need volume and reusability. Custom projects may be uploaded to a hosted data center, but there is no business case for the software vendor/developer to pursue this as a business model. However, if the mobile software application is custom, but the database application that it synchronizes with is sold as an off-the-shelf application, then there may be a business case.

Here is a real life scenario. SAP ERP does not handle work orders or service tickets well if they are not associated with a pre-approved purchase order. This is a problem in the oil fields as contractors and service technicians are often called to perform unanticipated work to fix or repair items. Since SAP does not like to receive unexpected invoices, Field Service software vendors have responded to this need by developing applications that convert these unexpected invoices into acceptable SAP formats that are integrated with SAP using standard integrations. These same vendors have created mobile work order applications that synchronize with their work order management systems. They have a standardized model that can be sold in a hosted environment.

Since the work order management application was an off-the-shelf software package, with a standardized integration to SAP, it could be offered in a hosted environment with a good business model.

If the work order management system was custom, and the back-office application or ERP was custom, then the mobile software application would need to be custom and there is no efficiencies in this scenario for a hosted solution.

***********************************************
http://mobileenterprisestrategies.blogspot.com/
***********************************************

Mobile Workflows in the Field, SAP and Other ERPs

The way business processes are designed, implemented and standardized within a company can often mean the difference between success and failure. If often takes years of trial and error, and sometimes flashes of brilliance to come up with just the right business process that will mean success and competitive advantages.

Once the perfect business process is proven it needs to be implemented and automated. Why automated? Because humans are forgetful and have even been known to be from time to time lazy. They want to cut corners and avoid that which is tiresome. Automation enforces and manages the perfect business process.

For years software vendors and ERP developers like SAP have developed applications that help design workflows and workflow engines to run them. These provide the technology infrastructure within the enterprise to automate these business processes and to ensure they are followed, however, once an employee exits the building and drives away in a company van to perform a task remotely, the automated business process breaks down. Suddenly, the business processes that you have spent years perfecting are useless. The employee has broken the "connection" and walked out the door to freedom.

Even today, most mobile field service workers leave the building with a clipboard and a stack of paper service tickets or work orders. How they perform their work, in what order and the processes they utilize in the field are now unsupervised and up for interpretation. The field service technicians often don't much care for the business processes designed by the teams of MBAs in suits at the office. They have their own preferences and opinions about how things should be done, and in remote jobsites who is going to argue?

Many large companies have up to 40% of their employees working remotely and/or in the field on jobsites. How can the SAP or other ERP Business Process Expert design and implement business processes that can be utilized and enforced in mobile and remote locations? This is a challenge worth resolving.

Think about it, a company pays tens of millions of dollars implementing SAP internally and designing business processes and workflows to operate their enterprise. Yet for many services based businesses the money is earned outside the office at remote locations. The location where the customer interaction takes place and where the money is made is often devoid of best in class business process automation.

Mobile applications that need to synchronize with ERPs, should implement mobile workflow support. This requires a client server architecture whereby the mobile client software understands that a workflow or event manager is associated with a particular process and the server also understands that it is both producing and consuming data with the mobile device that is part of an event or workflow. Let me provide a scenario.

A service technician has a ruggded PDA or other mobile device on his belt. He receives an alert that he needs to be dispatched to a jobsite. This initiates a business process with a workflow associated with it. A series of tasks that make up the dispatch and completion of a service ticket are now initiated. The tasks may include:

1. Dispatch receives a service call


2. This initiates a series of tasks including estimating the availability and analyzing the location of all service technicians in the area.


3. Once the nearest available service technician is identified a service dispatch can be sent


4. Service technician confirms availability and accepts the job


5. Least cost and fastest routing information is sent


6. Service technician arrives at the jobsite and pushes a button on his mobile device annoucing his arrival.


7. Arrival message synchronizes with the server workflow or event manager notifying dispatch of his location on site.


8. The workflow may include an inspection, detailed findings, proposed solution, repair and collection of the fee


9. Any parts needed will be automatically deducted from the service vehicle's inventory


10. The workflow can also include sales and marketing activities such as promoting an Annual Service plan or equipment upgrade to the customer


11. The repair is complete, dispatch is notified


12. The service technician is available for another job
    

In this scenario, the mobile client application using a workflow engine that interacts with the server side application steps the service technician through the various tasks included in the business process. These steps can be directions in the form of alerts, messages, next steps, data fields that require input, and feedback from the dispatch office. Each step of the workflow required input from the service technician to confirm that the step had been completed and this information was in turn synchronized with the server side workflow engine. This enables the best practices supported by the company to be practiced and supervised in the field.

SAP has a solution called Event Manager. It is designed to manage activities happening across a geographically dispersed supply chain. It requires data input via B2B and EDI data communications. Similarly, mobile applications can feed data into a centralized workflow or event management solution that helps support and ensure best practices across remote jobsites.

A workflow engine and a mobile client version of a mobile workflow engine is required by companies that want to standardize business processes in the field where interactions with customers take place and where revenue is earned.

If you would like to discuss this concept in more detail please email me.

***********************************************
http://mobileenterprisestrategies.blogspot.com/ /
***********************************************