Design Strategies for Mobile Applications

One Client Many Apps

I had the opportunity to be briefed on Webalo's mobility solution a couple of weeks ago.  It is much different than most enterprise mobility solutions.  Using their web-based Agenda environment it takes only a few hours to develop a mobile application, and you need download only one mobile client to support and mobilize hundreds of different business processes.

It is an interesting concept.  You can access the Agenda environment in the cloud, configure your integration with backend databases, layout your mobile application screens, download the mobile client to your device, and then login and upload any and all mobile applications you have configured.  Each additional business process that you want to mobilize is simply a configuration exercise, that gets uploaded to the same mobile client on the next login.  You can open your mobile client and see a menu with all of your unique mobile applications, all in the same mobile client. 

You give up some native graphical user interface flexibility when you use the same mobile client for all applications, but what you gain is:

• Lower development costs
• Less development time
• Less deployment effort
• Less support issues
• Lower TCO (total cost of ownership)

In talking to the CEO/Founder of Webalo, Peter Price, he said in many enterprise mobility projects the 80/20 rule comes into play.  You can deploy 80% of the functionality you need for 20% of the cost.  You need to ask yourself if gaining an additional 20% of features is really worth 80% more.

It is an interesting approach to enterprise mobility.  It is very utilitarian.  Mobilize as many business processes as you want for one low price.   I like the idea that one mobile client, can be configured to run hundreds of different workflow kinds of applications, rather than buy separate mobile applications for every different business process.

Webalo's product approach and strategy invites a debate on the value of spending a lot of time on the user interface.  Some vendors spend most of their time talking about their beautiful user experience.  Others take the approach that a simple menu driven approach that quickly and cost effectivly provides mobile capabilities is worth a lot more and commands a better ROI.

What do you think?

***************************************************
Kevin Benedict, Independent Mobile and M2M Industry Analyst, SAP Mentor Volunteer
Follow me on Twitter @krbenedict
Join the SAP Enterprise Mobility Group on Linkedin
Read The Mobility News Weekly
Read The Mobile Retailing News Weekly
Read The Field Mobility News Weekly
Read The Mobile Money News Weekly
Read The M2M News Monthly
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

The Downside of Mobile Applications

I had the fortunate opportunity to meet a classmate for coffee this week. I had not seen him for over a decade. He serves as a traffic cop and uses a TDS Recon mobile handheld computer in the course of his work writing tickets.

During our conversation we discussed the rugged laptop he had mounted in his unmarked police cruiser. He said it had many of their police forms and documents on it, but that the mobile software was not able to keep up with the required edits and changes needed on the forms. As a result, they had stopped using it for much of their documentation.

This discussion highlighted the need for a mobile workflow application that is a separate layer from the data layer. The field data collection requirements should be very simple to edit and not impact the field user. If the mobile application requires a complete update to edit data fields, then it risks early obsolescence or as in my earlier example it will simply not be used.


- Kevin Benedict,
Mobile Strategies Consultant, SAP EDI Expert and Technology Writer

Wirelessly Controlling Equipment with Mobile Software Applications

In a recent article I wrote about mobile software applications that could physically move objects. Here is another example for you to ponder from Telemetrics. This is how they describe themselves, "We deliver cost-effective wireless communication and control solutions for a wide range of distribution automation and power reliability applications." One of their products is called Monitor and Control Reclosures. It uses small monitors with wireless communications equipment to remotely report on equipment status. The most intriguing part though is mentioned below in feature #2, Here is what it does:

1. Monitor recloser status points, such as a trip and lockout event, and automatically notify dispatch personnel. Notifications are sent upon alarms or events via pager, email or voice and can be sent to multiple individuals.
2. Assist repair crews with the ability to provide open and close commands by supervisory (wireless) remote control of the recloser.
3. Offers real time status of all the inputs/outputs of the recloser:- open/close state of recloser contacts- high and low voltage readings (AC powered models)- time of the events- presence of AC voltage (outage monitoring)- recloser malfunction indication- local/remote or hot line tag switch status- total count of recloser operations

Note feature number 2 - it provides the ability to remotely open and close the reclosure (see definition of reclosure). Mobile devices are being used to remotely monitor equipment, physically control and move them, in addition to things like visually watch, locate and track equipment assets.

We live in very interesting times. The challenge this year for mobile technology companies is to start aggregating these various mobile applications and technologies together and marrying them with mobile workflows, business process engines and business analytics.

If you would like to discuss these technologies in more detail please contact me.

Here are some related articles about mobile workflow, business processes, location based services and mobile business analytics and intelligence:

• Mobile Software and Mobile Business Intelligence
• Mobile Application Integration Platform
• Mobile Workflows and ERPs
• Mobile Workflows in the Field
• Mobile Applications that Move Things
• Mobile Applications, Location Based Services and Distribution

***********************************************
Author Kevin Benedict
Independent Mobile Strategy and Marketing Consultant
www.linkedin.com/in/kevinbenedict
http://mobileenterprisestrategies.blogspot.com/
***********************************************

Mobile Application Integration Platform - For Data Collection and Cloud Computing Services

An increasingly large amount of data is being consumed by mobile handheld computers and Smart phones. This data can come from a wide variety of sources and be in many different formats including GPS, LBS (location based services), SMS, voice, Email, Video, digital photos, barcode scanning, RFID, voice memos, documents and Bluetooth data connectivity to a large variety of data collection tools and equipment. The data can come from many different ERPs, database applications and SaaS (software as a service) offerings in a cloud computing environment.

The demand for mobile applications and mobile devices to be able to consume all of these various data sources and formats creates a need for an mobile data aggregation platform for mobile data feeds. This data often needs to be integrated into a mobile application somehow so the data can be used by the mobile worker. Some of this data can be aggregated on the database server side and downloaded or streamed to the mobile device, but data collection equipment and some applications are connected directly to the mobile device. For example, a voice memo application, GPS reader and a barcode scanner may be directly connected to the mobile device. The results of the barcode scan and the GPS data may be synchronized with the ERP to identify an asset that is located at a particular location. A data collection form that helps document the condition of the asset needs to be integrated with a digital photo, GPS data, voice memo, barcode scan and the asset data downloaded from the ERP. All of this data once aggregated, can be updated and synchronized back with the ERP.

There are some data sources such as weather conditions, shipment tracking and currency exchange rates that may be available as web services. This data also may be required on the mobile device, and even incorporated into the mobile asset management application. How do you bring all of this data together from the server and from the data collected on the mobile device so it can be used by the mobile worker in the field? That is the challenge. It can always be done in a custom manner, but how can this be solved in a reusable manner?

Mobile applications need:

• GUIs or mobile application forms that have an integrated data validation and business rules engine
• GUIs or mobile application forms that include a mobile workflow engine associated with the screens
• Mobile database and synchronization technology
• Mobile data aggregation platform (this article)
• Mobile business process platform and ERP integration so the mobile worker can be part of the enterprise business processes in the ERP even outside the four walls of the enterprise

There needs to be a design and development strategy and a solution that can aggregate all of the various web services with the feeds from data collection equipment on the server side and on the mobile device side. This will become increasingly important as additional LBS (location based services) and consumable web services become available.

A mobile application on a Smart Phone or ruggedized handheld has access to a great deal of data. The value of the data comes from aggregating it in a standard way that can be used to make good business decisions. Today this takes a great deal of custom software development for each application. It is time for some good mobile software developers to solve these problems.

If you would like to discuss this topic in more detail please contact or hire me :-)

***********************************************
Author Kevin Benedict
Mobile Computing, EDI and B2B Evangelist and Consultant
www.linkedin.com/in/kevinbenedict
http://b2b-bpo.blogspot.com/
http://mobileenterprisestrategies.blogspot.com/
***********************************************

Mobile Workflows and ERPs

As mobile applications become more complex and sophisticated and used by large enterprises there will be an increasing emphasis and requirement for automated mobile workflows and supported ERP business processes. I wrote about mobile application support for ERPs in this article, but today I want to focus on the automated workflow on the mobile handheld computer, Tablet PC or laptop that is used in the field. ERP business processes and automated workflows have been supported within the four walls of the enterprise for decades, but they often don't extend outside the four walls to the remote jobsite and/or mobile sales and service processes. That is a big problem that needs to be addressed by mobile application vendors.

Let's begin by recognizing that it is often the service technician that is face-to-face with your customers. They are the face and personality of the service company. The actions they take, the words they say, the professionalism they display and the quality of work they perform all impact the customer's perception of your company and their willingness to continue to do business with and refer your business to others. Since the activities that happen in these remote and mobile jobsite environments can have such a big impact on your business, wouldn't it be important that you ensure the best quality work and presentation of your company? This is where automated workflows on your mobile devices comes into effect.

Let me now outline a process that you may want to consider when designing a mobile application for use in the field.

1. Outline the tasks and actions you want each service technician to perform at the customers location. Examples - Greet customer by name, give business card, thank them for their business, ask about animals or children that my be in the work area, interview the customer about the problem, understand the customer's schedule, understand how the customer will pay, is there a warranty or service plan, provide estimate, complete work, get customer's signature, etc.
2. Once all of the "best practices" tasks are identified for a generic service call, complete the same process for the other kinds of service calls you may have. For example: a warranty process has 11 tasks, an annual maintenance call has 16 tasks, an emergency system repair for HVAC equipment has 19 tasks.

Once you have identified and documented these tasks, your mobile application developers can design and develop these workflows to become part of your mobile application. Once in production, these mobile applications can direct and guide each service technician through the specific best practices that the company wants completed in a standardized manner in the field. As a result, quality and professionalism can be standardized into the company's customer interactions.

What does this process look like on a mobile handheld computer?

1. The workflow processes should be a layer in the mobile application that is tied to a specific set of screens that go with the workflow. If the mobile application has multiple workflows, then the first step is for the service technician, or the service ticket itself, to identify which automated workflow is most appropriate for the needed service. This then launches the appropriate process/workflow on the mobile device.
2. If the automated workflow consists of 17 steps/tasks, then this workflow will dictate that mobile form fields including check boxes, radio buttons and data fields are completed in the right order and with valid data entries.
3. If the service technician skips a step an alert sound or pop-up message should guide the service technician to finish the process and continue it in the appropriate manner.
4. Automated scorecards can also be created to monitor the performance of service technicians to the standards and detail any exceptions to the process so they can be analyzed for process improvements over time.
5. Brief customer surveys can also be provided for the mobile handheld computer to tie the customer's opinion of the service provided with the exact service order and service technician. It is great to reward the service technician for work well done.

The mobile workflow process is specific to the role of the user and service performed. A recent report I read said up to 40% of workers are mobile. That represents a lot of remote jobsites and customer interactions. If companies want to ensure a high level of professionalism and quality customer interactions, then means of standardizing those processes need to be employed. As more and more of these mobile workers are equipped with Smart Phones and mobile handheld computers, these processes become easier to deploy.

For a related article read - http://mobileenterprisestrategies.blogspot.com/2009/10/mobile-application-integration-platform.html

If you would like to discuss this topic in more detail please contact me. I am available for SAP and Mobile Solution related consulting and permanent hire opportunities. My Linkedin profile can be found at http://www.linkedin.com/in/kevinbenedict.

***********************************************
Author Kevin Benedict
Mobile Computing, SAP, EDI and B2B Evangelist, Marketing and Business Development Consultant
http://b2b-bpo.blogspot.com/
http://mobileenterprisestrategies.blogspot.com/
***********************************************