Mobile Systems Costs and Benefits
Jim Hargis har*GIS LLC, Field Information Systems™ 8093 S Oneida Ct. Centennial, CO 80112-3133 303-220-0253 E-Mail: jim@har-gis.com Abstract Barriers to implementing a mobile system include technology risks, lack of resources, and for many companies, Money. While most analysts agree that mobile/wireless 'strategic benefits' are compelling, there are few who can realistically estimate total costs and paybacks in the mobile environment. It turns out that mobile projects typically have much faster payback than projects like GIS. This is due to several features unique to mobile systems. This paper will present a simple to use cost/benefit methodology for analyzing the environment. The paper includes sample tables listing the complete range of project cost items and benefit items. Introduction The approach to this paper is to provide a realistic list of tangible project costs and benefits associated with a mobile system. Mobile Systems are unique from other projects in that the majority of the benefits depend on field productivity improvements rather than office. These systems include both field applications, and the office systems and data required to them. Traditional cost/benefit analysis often fails to recognize the unique differences of the mobile environment. Projects should support business needs, be accepted by user, and provide measurable benefits both to the user and the company. Studies of several mobile projects identify many that have paybacks of less than one year, even a few months. How realistic are these? Corporate Objectives A Mobile System project should support multiple company objectives, such as:
The project must provide certain applications to realize benefits. The following are important for many field applications.
Cost/Benefit Approach The cost/benefit analysis seeks to determine all the incremental costs associated with implementing a field automaton project. The analysis must also identify the resulting operational savings. The following four steps can be used to perform a cost/benefit analysis.
Project Implementation Costs Project costs -- hardware, software, data, personnel, support -- vary greatly on the scope of the project, number users, applications. For instance, using a handheld computer instead of a laptop PC can cut hardware costs by factors of 2 to 3, providing the efficient software application exists. Usually, the data already exists, and the problem is to provide it to the field in a productive manner. Mobile Systems Cost/Benefit
Baseline Costs The company incurs Baseline costs under existing conditions (pre-project). These costs occur if nothing is done. That is, the company spends some amount of money now that will be impacted by the project. Baseline costs identify the current required operating costs. These should include any anticipated growth or inflation. Although there can be many different activities, we focus on the field activities that most companies have information about. Mobile Systems Cost/Benefit
Savings and Benefits Savings are based on the field applications to be implemented. Tangible (measurable) benefits include reduced labor, increased productivity, and reduced vehicle costs per job. Obviously, other possible benefits could include avoided costs (not having to buy something), increased productivity, better customer service response, ability to support to crews operating in unfamiliar territory, and ability to perform office jobs more effectively in-field. Mobile Systems Cost/Benefit
Payback Analysis Tangible benefits are the difference between the operating costs “before automation” and “after automation”. Here we recommend allocating the costs and benefits annually and by mileage. The Annual costs reflect labor and materials savings. The Mileage costs reflect mobile equipment efficiencies. That is, reduced vehicle maintenance and more effective equipment utilization. Payback time is the number of months of savings needed to recover the investment. This also indicates a measure of risk, since longer implementations are more likely Mobile Systems Cost/Benefit
Conclusion With the above approach, the user can undertake a cost/benefit to any desired level of detail. However, we usually find that
| ||||||||||||||||||
|
|