|Figure1 - MADP|
It seems to me one solution would be to start developing "mobile workflows" junior technicians could access and use. These "mobile workflows" could be developed by experienced experts for the use of more junior service technicians. These "mobile workflows" could be integrated into mobile applications by way of dispatched service tickets/work orders.
|Figure 2 - Mobile Workflow |
The MADP (mobile application development platform) would have a "mobile workflow" configurator in the RAD (rapid application development) component (see figure 1). You would be able to associate specific tasks in your mobile workflow (see figure 2) with fields in your mobile client application.
What is the value? The junior technician receives his/her next assigned work order and it comes attached with a configured mobile workflow. They review it to understand exactly what needs to be done. Let me provide an example. A service technician receives a work order to maintain an escalator in a busy store during the Christmas shopping season. The mobile workflow identifies the necessary tasks associated with this job.
- Schedule the escalator maintenance with the store.
- Make sure the store security is notified and aware of the time and date of the work.
- Make sure you have job site access instructions.
- Make sure you know where you should park your vehicle.
- Set-up the mandated type of safety barrier.
- Set-up the mandated type of warning signs.
- Turn-off the escalator and lock it.
- Bring the right tools - identify the right tools.
- Bring the right specialized equipment.
- Bring the right equipment manuals.
- Photograph the job site and safety measures.
These steps are made up from the accumulated knowledge of your most experienced company experts. These mobile workflows can be integrated into a mobile workflow layer in your mobile application client. Again, each step in the mobile workflow could be associated with a field in the mobile client application.
We all know these kinds of workflows exist in our ERPs. I have found myself filling in numerous web based forms lately and can see there are obvious workflows built into the process. So I asked myself, "Why haven't we done the same thing for mobile applications?"
When I was the CEO of a mobile application company, we showed our clients how we could customize workflows in a mobile application. In field A, if your answer is "YES", it jumps to form 17, if your answer is "NO", then it jumps to form 4. This was a workflow configured into a mobile application. I suggest a step beyond that. I propose the "mobile workflow" be assigned to the work order/job, rather than the mobile application. I propose that if a service technician receives six different work orders per day, each unique work order includes a unique mobile workflow specific to the particular tasks required.
I wrote an article earlier this year, and then discussed it with Israel Beniaminy (see this mobile expert video) on the topic of "mobility will ultimately go away." What did we mean? We suggested that mobility will soon become a commodity. It will no longer be something novel. All applications will be mobile. So how would a mobile software vendor differentiate themselves? I propose by developing additional layers of functionality in the mobile applications, including mobile workflows.
What do you think? Is this a good idea?
Kevin Benedict, Mobile Industry Analyst and Mobile Strategy Consultant
Follow me on Twitter @krbenedict
Join the Strategic Enterprise Mobility Linkedin Group
Full Disclosure: I am a mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.