The Magic Quadrant for Handheld Computers

I was in Paris, France last week at Symbol's EMEA Partner Conference. While there I heard more evidence of a trend I have been watching for a while. The 2 largest ruggedized handheld computer manufacturers - Symbol and Intermec have both recently come out with small, ruggedized, full functional handheld computers. These handheld computers combine the ruggedness of larger handhelds, and include barcode scanners, GPS, phones, WiFi, bluetooth and more. Symbol says that their MC70, pictured above in PointSync Developer, has become one of their top sellers. It is especially appealing to the "field service" market. That is also the market MobileDataforce focuses on.

I have also recently seen a lot of very interesting looking small ruggedized handheld computers coming out of Korea and China. These are sub $1,000 USD devices that can reasonably be used as handheld computers, phones and barcode scanners. They are a little bulky for the suit coat, but work nicely attached to the belt.

MobileDataforce is a big fan of these smaller handheld computers. They carry a lot of power and allow us to provide software solutions to our customers for reduced overall project costs due to less expensive ruggedized hardware.

If you can get full functional, ruggedized handheld computer/phones for under $1,000 USD - there is very little business justification for buying consumer grade PDAs. Most consumer grade PDAs with business capabilities are priced at $500-$800, yet are not ruggedized.

Let's go back to the title of this blog - Where is the magic quadrant for handheld computers? It is handheld computers that are truly convergent. Convergent, meaning they combine the ruggedness and size that is easy to carry, plus they have the phone, Windows Mobile 5.0, GPS, barcode scanners, plus the industrial grade batteries to support a full day's work.

I love it!

More on Buy vs Building Mobile Solutions, Part 3

There are always reasons and/or business justifications for wanting to mobilize a business process. Something has motivated the individual or company to march down the path of mobilization. So when considering whether to buy or build a mobile solution these additional factors should be considered:

• Tolerance for risk
• Opportunity Costs
• Expected ROI
• Competitive Advantages

Let's briefly discuss each of these considerations.

Tolerance for risk - are you willing to risk attempting to develop an enterprise mobile solution for the first time (If your team is an experienced mobile development team, then you can ignore this point)? It can be done, but the first time requires a lot of thought, design meetings, trial and error, debugging and above all else - time. What if the design can not scale? What if the synchronization engine that your developer made is too slow? What if after 8 months the system is still only half complete and full of bugs?

Opportunity Costs - this is one of the most common issues that IT managers discuss with me. Most often IT departments are already over worked and behind schedules. The last thing they need is a another new project added to their list and schedule. IT managers are already annoyed at their current workload, and now the business unit is asking them to develop a completely new and unproven mobile solution? The IT manager is not happy. All they can think of is the headaches this will cause.

The questions the IT managers ask the business unit managers are:

1. What project should I delay in order to insert this new project into the schedule?
2. Who is going to support it?
3. Can I hire more developers to develop and support a mobile solution?

These questions then force the business unit manager to go back to senior management and ask them to re-prioritize other IT projects in favor of the mobile solution. So now all the business unit managers get involved and defend their particular interests.

The opportunity costs can be considerable if you want to code/program the complete mobile application yourself internally.

Expected ROI - if the business unit requesting the mobile solution expects to save $53,000/month by mobilizing their work order management system, then every month that passes without the mobile solution being deployed wastes $53,000. So if coding your own solution from scratch takes 3 months longer than using a RADs-ME tool like MobileDataforce's PointSync, you must consider the $159,000 you just wasted.

Competitive Advantages - we have developed many mobile solutions for companies that are considered competitive advantages. Solutions that provide new and unique revenue opportunities for our customer. We have seen this in the automotive industry, the beef industry, the concert and event promotion industry and many more.

If the business justification of the mobile solution is motivated by a competitive advantage, then the length of time it takes to code a mobile solution from scratch must be considered. What if the mobile solution takes 5 months to code from scratch, but only 5 weeks with a RADs-ME tool like PointSync? The associated competitive advantages and disadvantages must be considered in the equation.

More on Buy vs Building Mobile Solutions, Part 2

This seems to be the topic of the week this week - so let me add more thoughts to this topic.

If your organization has .NET programmers that are available now and they have a lot of time on their hands, then yes it is possible to develop your own enterprise mobile application. Here are a couple of questions before you start:

• Have your programmers completed successful mobile applications before? If this is their first time there is a steep learning curve that must be considered.
• Is the same programmer going to code the mobile application, code the security, code the synchronization logic, code the database integration and code the business logic? If there are multiple developers/programmers involved - ask question #1 about each of them.
• Are these programmers going to also write your user guide and document the solution?
• How long will your programmers stay with your organization? What if the programmer leaves? Who will support it and maintain it?

There are many parts to an enterprise mobile solution. It is rare for even an experienced .NET programmer to have experience in all of the components. Here are some good questions to ask a programmer before you start coding your mobile application:

• How do you plan to sync the data?
• What sync engine will you use and why?
• How will you connect to the enterprise database remotely from the field?
• How do you handle security?
• How will you integrate the data into existing database systems?
• How will you glue all these components together in your application so it all works?
• How will you support multiple mobile devices- Windows Mobile, WinCE, Tablet PC, Windows PC?

These are all questions that need to be answered before a programmer begins. Here is the problem - often a programmer views their component (the mobile application on the handheld PDA) as 90% of the project. Will that simply is not the case. The majority of the time and effort is in connecting all the different components together, integrating and testing.

I have often heard a comment from a programmer that the mobile application is done, although it takes another 8 weeks before it could be deployed. The mobile application is often the smallest part of the project. Many programmers can code a simple PDA application. However an enterprise mobile application needs much more than a simple, stand alone PDA application. It needs full synchronization, remote connectivity, device management, integration, security and more.

- the reason companies love MobileDataforce's PointSync Suite is that all of these components and features are already developed and available for you to configure. You are not required to figure out all of these issues and code them. PointSync is a RADs-ME tool - A rapid application development solution for mobile environments. It is designed for organizations without the desire or time to program all of these components.

So in summary - anyone with the time, interest, intellect and money to code a complete enterprise mobile solution can. PointSync is for those that need the mobile application without the time and money needed to code it from scratch.

More on Buy vs. Build

Even More on Buy vs. Build

You've got to be kidding - yet more on Buy vs. Build...

....more

Buy vs. Building an Enterprise Mobile Solution? Part 1

This is a good and fair question. Let's start our discussion with a scenario - You want to monitor assets for your government agency. That means you want to track all the street signs, sewer pipes, manhole covers, guard rails etc, that your organization owns using a mobile software application on a handheld computer. You also want to mobilize your inspection processes involving these assets. In addition, you would like to integrate a "work order" management system to dispatch repair technicians when work is needed. You would like all of these processes to be mobilized on a handheld computer that synchronizes with your central databases.

The problem - Often the above processes involve more than one desktop application and multiple backend databases. How would you mobilize all of these? You can't buy 1 mobile software package that will integrate with all of these desktop applications and databases. Why, some of your applications are home grown, undocumented and specific to your working environment. No one else knows your unique inventory of applications. Typically you will have 3 choices:

1. Buy pre-built mobile clients for each of your off-the-shelf desktop applications. So if you have 8 desktop applications that you use, you will need 8 different mobile software packages in order to mobilize these processes. This is very expensive, forces you to learn 8 different mobile applications, punch 8 different holes in your firewall, learn 8 different synchronization technologies, and 8 different configuration environments. In addition, this does not help you to mobilize your home grown custom applications. Another challenge, most of your 8 desktop applications will not have mobile client applications available.
2. Develop mobile software applications from scratch using .NET or other programming environments. This can be done, but you need a person with mobile programming experinece to develop a new and different mobile client application for each desktop application and database. There is little ability to reuse code so each of these mobilization projects will take considerable planning and lengthy development time.
3. Use a mobile software platform that is a rapid application development environment for mobile solutions. This allows you to quickly configure mobile client applications that can synchronize with multiple backend databases. You can standardize on one method of synchronization, learn one development environment, one integration methodology and have one company that can train and support you. You don't need to be a programmer, and you can edit and update your own mobile applications as often as you want. You maintain control of your own applications and you can easily support any of your custom home grown database applications. You can mobilize all 8 of your desktop applications using one mobile software platform. You don't have to pay someone else to develop mobile applications, your own IT team can support any of your mobile client application needs.

OK...so I am bias, but there is a lot of value to owning your own mobile RADs-ME tool (rapid application development environment for mobile solutions). You buy your RADs-ME tool once, and then you can develop an unlimited number of mobile applications. You control the cost, you control the updates, you customize to your requirements and you are not dependent on some outside software company's schedule and cost structure. Once you have been trained, you can develop mobile client applications internally for any desktop database application.

PMM Selects MobileDataforce Software for Handheld PDAs

Last week MobileDataforce was selected to provide mobile asset management/field inspection software for a large project in South Africa. It will be used by the South African government to assess property taxes.

Properties will be inspected, data will be collected on a mobile handheld device and the data will be synchronized to an enterprise database. The software application that will be used is MobileDataforce's PointSync. It will be integrated with GPS and mapping software so the exact location of all property assessments can be identified and documented.

Manitoba Hydro Selects MobileDataforce Software

We do a lot of business in the electrical utility industry. This previous blog article identified many of the mobile utility projects we have delivered. This week we gained a new customer in Canada called Manitoba Hydro. They selected MobileDataforce as their mobile software platform for field inspections. They listed over 17 inspections that they want to mobilize (convert from paper to mobile handheld data collection).

The solution will involve using rugged PDAs in the field, MobileDataforce software for the mobile inspection application and synchronization to an enterprise database.

Clinical Research Company Selects MobileDataforce

MobileDataforce just won the contract to develop a large clinical research solution for stroke victims. This project involves healthcare providers using handheld PDAs and PDA software from MobileDataforce to monitor treatment programs and the clinical results over a number of years.

MobileDataforce is becoming more and more involved in the healthcare field. We have recently delivered solutions for remotely monitoring young patients, mobile asset management in hospitals, safety inspections of hospitals and now clinical research.

The clinical research project involves using handheld pdas for data collection, software from MobileDataforce, and synchronization with an enterprise database.

Ease of use, flexibility, and quick application development were reasons given for MobileDataforce winning the award.

Going Mobile Global

In the past few hours I have either spoken or emailed with partners or project teams in the following locations:

1. Germany
2. Australia
3. Hong Kong
4. Dublin, Ireland
5. Belfast, Ireland
6. UK
7. The Netherlands
8. Canada
9. USA
10. South Africa

The internet is enabling businesses to expand as never before. The internet provides low cost communication globally. Online marketing allows you to meet companies around the world. Online project management tools enable the management of remote projects. Video conferencing let's you look your team leaders and customers in the eyes across the Atlantic, Pacific or any other ocean or sea. Wire transfers allow us all to get a paycheck. Digital products like software can be distributed across the internet - kind of like a digital fedex service.

Now consider MobileDataforce's mobile software platform - PointSync. A person can be conducting a quality assurance inspection of a food processing plant in Melbourne, Australia and with a click of a button on a mobile handheld computer, the information can be immediately synchronized to a database in New York city for viewing by managers. The internet makes this communication both inexpensive and a reality for most of our deployments these days.

MobileDataforce and Large International Deployments

MobileDataforce has been involved in several good sized international deployments of mobile handheld computer solutions lately. These kind of implementations need careful management and planning. Here are a few points to consider and plan for:

1. First of all the customer must have dedicated staff assigned to the roll-out. It can't be done ad hoc.
2. If at all possible have the deployment teams onsite at the pilot location.
3. Pilot and beta programs need documented issue reporting paths. Everyone involved must know how to report issues, and how they are to get resolved.
4. Don't roll-out to large numbers in the first round. Test...roll-out...test...roll-out...there is a nice pattern here. Minimize the impact of inevitable issues in the early stages.
5. Use PointSync Manager to deploy updates to the field. PointSync can publish updates to the end user transparently. This reduces end user errors and self-inflicted injuries.
6. Often it is helpful to load the mobile application onto each handheld device before the initial roll-out. Minimize the variables that can go wrong in the field. Keep it simple for the new users. We often load our mobile applications to an SD or Mini SD card and then simply insert the card into each new device and load.
7. Keep the user interface on the mobile application as close to the paper process as possible to minimize the training time required. If there is a certain process flow that your field users are familiar and comfortable with, then keep your mobile application as close to it as is reasonable.
8. Mandate the use of a mobile application, don't give the field user the option of paper. Learning takes time and is often annoying - make sure the end user knows there is no going back to paper...so start learning it.

Even a Sales Guy Can Build a Mobile Application

Even a sales guy can create bar code scanning applications for use in route deliveries to grocery stores! I was walking down the hallway in our office on Monday and Mark was proudly showing off an application he had developed for the Symbol MC70 bar code scanner. One of his clients delivers products to grocery stores and wanted a route delivery application using this handheld device. So what did Mark do? He (a sales guy) developed one for them! This just proves that MobileDataforce has nearly accomplished our dream. Ok, ok, ok...he didn't quite get it production ready, but he got the mobile application running.

Our dream has always been to develop a rapid application development environment- PointSync, that could be used by the business folks to develop mobile applications. Every month we are adding new features and functionalities to our mobile applications to make them simplier to use and faster to implement.

Route delivery applications often consist of the following parts:

1. Inventory
2. Delivery
3. Merchandising
4. Planograms
5. Promotion
6. More

Planograms are one of the most interesting components to me. Here is the definition of a planogram:

• The placement of merchandise that is arriving to the store can be planned out on paper by using a Planogram before the products actually arrive to the store. A planogram is a retailer's drawing (blueprint) which visually communicates how merchandise and props physically fit onto a store fixture or window to allow for proper visibility and price point options. The retailer can plan to mix the new products with current items or initiate entirely new displays. If you have more than one store this is an excellent way to communicate to your staff how you would like displays executed.
  

I would like to add some more to the description of planograms - Here at MobileDataforce one of our recent route delivery application projects included a design of the shelf space plus a color code to signal what task needed to be done for that shelf space and product. This was all done on a handheld computer using MobileDataforce's PointSync. Talk about efficiency. The delivery person would walk into a store, enter the store code/street address and a detailed task list would be produced instructing him/her on what needed to be done with each product and shelf space in that particular store location.