Paintless Dent Repair & Mobile Automotive Services Software, Handhelds, PDAs and Mobile Software

In a blog article I wrote earlier, I discussed a mobile work order software application for use on PDAs, handhelds and Smartphones under development that is designed to run on ruggedized handheld computers and to be used by automotive service technicians. They bar code scan the VIN of a car and then create a work order. Once the work order is approved they complete the work, invoice the customer and synchronize the data with the office. In the image above you see the desktop application used in the office. This application allows work orders to be created and dispatched to the automotive service technicians in the field. Reports can be generated and the work orders can be loaded into QuickBooks for invoicing.

If you operate an automotive inspection service, paintless dent repair, detailing or other automobile services business then you may find this very interesting. If you would like more information please contact MobileDataforce by email or visit our website.

Paintless Dent Removal and Mobile Software Solution for PDAs and Handhelds

MobileDataforce is in the process of developing a very interesting mobile software application for handhelds and PDAs called FieldSync Automotive (TM). This software application runs on a rugged handheld computer and synchronizes with a desktop application that manages work orders, schedules, reports, invoices and integrates with Quickbooks. Other accounting systems can be supported but require additional customization.

MobileDataforce is developing a powerful collection of applications for companies that provide mobile automotive services. Services such as paintless dent repair (PDR), detailing, mobile windshield repair, automotive inspections, etc. If you would like more information please email us or visit our website.

The mobile handheld software application (pictured above) enables the user to scan (using a barcode scanner) the VIN number on the automobile and then assign a work order to that unique vehicle.

Business Process Optimization for Mobile Handheld PDAs

How do you improve upon a paper forms-based business process? The plumber, electrician and appliance repair person have been using a clipboard with paper work orders and service tickets forms forever. How do you improve upon this tried and true process? Let me provide some ideas for your consideration:

1. The office can wirelessly dispatch new work orders directly to a handheld device
2. Small service companies, with an owner/operator, can take calls from customers while on the road and enter new work orders on their mobile PDA phones. These work orders can be synchronized with the office and dispatched immediately to other service technicians
3. Wireless work orders can be integrated straight into office database applications and accounting systems so there is no additional paperwork to be entered
4. The wireless work orders can contain all the information on the customer, warranties, equipment type and model, history of the account, driving directions, etc. No need to call the service technician on the phone and dictate all the information.
5. Re-prioritize work orders automatically from the office to the mobile handheld device
6. Print invoices directly from the handheld using a mobile printer and give to the customer
7. Get a digital signature from the customer on the electronic work order
8. Take digital pictures of the work both before and after and integrate with the wireless work order
9. Get an automatic date and time stamp on the work order when it is opened at the customer's site
10. Track the time it took to complete the work - record for job scheduling and cost analysis
11. Wirelessly synchronize completed work orders directly to the office accounting system for instant invoicing.
12. Send parts orders directly to the office via the mobile handheld for quick processing
13. Parts and inventory can be queried from the field. Do we have the needed part in stock either in the office or another van? If it is available in another van, where is the van? Can you drive over and retrieve it?
14. If you implement a GPS system on your handheld computers, the office can see the location of all service technicians and optimize job dispatch
15. The service technician can schedule future service visits on his mobile handheld computer and synchronize back to the office
16. The service technician can estimate a new job on the handheld computer and sync this information back to the office for reference and database integration
17. The service technician can record parts, equipment and services sales on his handheld for immediate syncing with the office
18. The service technician can view past work orders on his handheld device for improved customer service

I heard a story about why Sears Service Technicians implemented a wireless work order system in their service vans. They wanted to be able to increase the sales of warranties, parts and other appliances while at the customer site. The results are said to be impressive. There is no better time to sell additional services, parts, warranties and other products than when you are with a happy customer in their home. The wireless mobile computer enabled them to fill out product and service orders at the point of work, reference online product catalogs, check shipping status and a variety of other customer friendly activities.

MobileDataforce develops wireless work order systems. If you would like to discuss your business and your requirements please contact us here or visit our website.

Saving Time Developing Mobile Software for Handheld PDAs

It is important to recognize that mobile software applications for handheld PDAs are not just developed by 1 person in a dark room with a computer. The business unit manager can order a mobile software application to be developed, but someone must design it, develop it, test it and approve it. Do you really want the programmer to complete the entire application on his/her own, or do you want a person who understands the business to be involved? Here are some considerations:

1. Do you want the mobile software application to look exactly like the paper form in use today? If you don't specify differently, the programmer may design it to look like a small piece of paper on a mobile handheld PDA.


2. Do you want the programmer to dictate your business process, or do you want to tell the programmer how the business process should work?


3. Do you want the programmer to tell the field workers how, when and where they should sync the mobile application, or do you want the business users to tell the programmer.


4. Do you want the programmer to select the mobile handheld PDAs, or do you want the business unit to describe their requirements to the programmer?


5. Do you want the programmer to tell the business unit when the mobile software application is complete and final, or do you want to test it and approve it?

Most of these questions have obvious answers. The business unit, the organization that will benefit or suffer from the mobile application, needs to have active input into the design, development, testing, deployment and support of the application. It is not a 1 programmer job.

The problem many development projects suffer from is this active involvement was not anticipated or planned, therefore, it either does not happen or comes as an inconvenient surprise. However, you have now been warned in advance so this will not happen on your project, right?

You Should Not Develop a Mobile Application - Just Because You Can

We often receive calls from software developers asking about our mobile software development environment. The developers often ask the question, "Why should I use your development platform when I can develop my own mobile software application for handheld PDAs?" That is a good and fair question. I will usually follow their questions with my own:

1. How many mobile software applications have you already designed, developed, deployed and supported successfully for handheld PDAs? Is your employer comfortable with having you learn on the job or are they risk adverse? Are they willing to be patient with your learning curve? If it takes you 4 months longer to develop your own, does the business suffer?
2. Have you created a full synchronization engine successfully in the past? This is very complicated and software companies like MobileDataforce have spent years optimizing these. What are the chances you will get it right and optimized on the very first project?
3. Do you have experience developing and configuring a variety of connectivity options such as cradle sync, wireless sync, satellite sync, bluetooth, etc.? Does the business manager know which one is needed in every case? Should you develop one, or develop multiple methods? Are the business requirements likely to change in the next 3 years?
4. Have you developed a full database integration manager for mobile solutions? Do you need an API or will your DBA allow you to directly populate the database? If you can directly populate the database, then the data better be validated in the mobile software application on the handheld pc. Did you set aside time for that?
5. Do you have experience designing scalable and reliable mobile applications? This is simply an experience thing. You don't know what you don't know.
6. Do you have support for a Pocket PC 2003, Win CE, Microsoft Mobile 5 & 6? How are you going to upgrade and support next year's mobile OS from Microsoft? Is this built into your project plan and budget?
7. Have you developed mobile applications that run on a large variety of different mobile handheld devices? This takes a lot of work and thought. Every week new mobile handheld devices are being delivered with new technologies and add-on components. The device selected today, will likely not be available next year at this time. How do you keep current?
8. Do you have experience developing interfaces for third party hardware? Mobile applications often need additional third party technology integration like bar code scanners, RFID, GPS, Digital Cameras, etc.
9. Have you thought through and developed dashboards for managing mobile application security, users, applications publishing, etc?
10. Do you have a development environment set up exclusively for mobile applications development that may include short-cuts, libraries, screen designs and scripts?
11. Do you have experience creating a helpdesk dashboard for sync logs, users, applications, device management, etc.?

Most often the developer was only interested in creating the screens for the mobile application, not a complete mobile application platform and support system. They had not considered the full end-to-end solution requirements when volunteering to develop a mobile handheld application.