Mobile Expert Interview: Christy Wyatt CEO/President Good Technology

It has been a business day #1 here at the Mobile World Congress 2014 in Barcelona!  My feet are killing me!  I started MWC 2014 interviewing the CEO and President of Good Technology, Christy Wyatt.  In this interview Christy shares her insights and opinions are where the market for mobile device management and mobile security is heading, plus information on their new cloud based products and planned acquisitions. Enjoy!

Video Link:  http://youtu.be/UkzT6GpB_fQ

*************************************************************

Kevin Benedict

Senior Analyst, Digital Transformation Cognizant

View my profile on LinkedIn

Learn about mobile strategies at MobileEnterpriseStrategies.com

Follow me on Twitter @krbenedict

Browse the Mobile Solution Directory

Join the Linkedin Group Strategic Enterprise Mobility

***Full Disclosure: These are my personal opinions. No company is silly enough to claim them. I am a mobility and digital transformation analyst, consultant and writer. I work with and have worked with many of the companies mentioned in my articles.

Enterprise Mobility and the Gift of Time

McCall, Idaho - Winter Wonderland

I was standing next to a grizzled old man (definition: anyone older than me that can grow a beard), at the coffee shop today.  He said he had been standing in lines all day.  I said, "Makes you appreciate smartphones, doesn't it?"  He agreed and added they save me so much time!

That comment is a perfect example of "blogger's inspiration!"  I said, "What do you mean by - "It saves you so much time?"  He said his work is closely tied to the weather.  He runs snow removal services in beautiful McCall, Idaho.  As a result, he must carefully monitor the weather including wind direction, precipitation forecasts and the beginnings and endings of storms.  He can now do all of this precisely from his smartphone.  He said he is absolutely more productive.

He went on to say, "I want to start working at the tail-end of a storm to maximize my productivity and customer services."  If he starts work too early his work will be covered by snow and he will have too remove it again, adding expense and delaying his work for other customers.  If he starts too late, he will have dissatisfied customers."  He uses his smartphone constantly in the winter to maximize his productivity.

Enterprise mobility solutions can provide all kinds of "gifts of time" to employers and employees.   From simple collaboration with colleagues, prospects and customers using your smartphone for voice, SMS, Skype or Google+ instead of traveling to a face-to-face, navigating quickly and accurately to a destination or to collect data in the field that is integrated with back-office systems.  There are all kinds of ways time can be saved by utilizing mobile technologies.

In recent decades productivity gains in manufacturing have been driven through better processes and process automations, automated data collections, advances in SCM (supply chain management), logistics and ERPs.  Today, there are even more productivity gains to be had in each of these areas by using mobile technologies to improve real-time visibility into events, processes, statuses, locations, resources and snow fall!

Have you reviewed my new Mobile Solution Directory at http://mobilesolutiondirectory.blogspot.com/?

*************************************************************

Kevin Benedict, Head Analyst for Social, Mobile, Analytics and Cloud (SMAC) Cognizant

View Linkedin Profile

Learn about mobile strategies at MobileEnterpriseStrategies.com

Follow me on Twitter @krbenedict

Join the Linkedin Group Strategic Enterprise Mobility

***Full Disclosure: These are my personal opinions. No company is silly enough to claim them. I am a mobility and SMAC analyst, consultant and writer. I work with and have worked with many of the companies mentioned in my articles.

Finally the Tide of Rugged Android Devices Begins

In my opinion, Microsoft blew it when they left the rugged mobile device manufacturers hanging for years with no meaningful upgrades or upgrade path to the Windows Mobile 6.5x operating system.  They sentenced the ruggedized device industry to compete against the iPhone, iPad and Android consumer devices.  This meant service organizations worldwide started considering the merits of switching to consumer devices, with new operating systems that had many more features rather than upgrading to new ruggedized mobile devices.

Otterbox and other rugged case manufacturers were definitely the winners of this Microsoft orchestrated industry trend.  They produced many great ruggedized cases that added device protection and gave buyers confidence that using consumer devices in rugged environments was worth the risk.

Today, however, the tide of rugged Android devices is starting to enter the market as demonstrated by this marketing piece from Honeywell that I received in the mail today announcing the new rugged Dolphin 7800 EDA running on Android.  Here is how they describe it, "Honeywell’s new Dolphin® 7800 Android™ rugged EDA pairs the intuitive Google® Android™ operating system with remote device management capabilities and invaluable security features, making the device enterprise ready."

For a time the Android operating system was difficult to secure, since every device and device manufacturer seemed to have their own version of it, but the MDM (mobile device management) or MAM (mobile application management) vendors have seemed to resolve much of that challenge now as this piece from the MDM/MAM vendor Soti suggests, "SOTI, a leader in cross-platform mobile device management, is announcing that its unique MDM solution provides advanced and consistent management for all Android devices, regardless of the device manufacturer."

I have spoken with and interviewed many rugged handheld manufacturers over the past few months and most if not all have rugged Android devices in development.  I believe that going forward service organizations will soon be able to get the latest Android operating system features in the rugged device of their choosing.

*************************************************************

Kevin Benedict, Mobile Industry Analyst, Mobile Strategy Consultant and SAP Mentor Alumnus

Visit MobileEnterpriseStrategies.com

Follow me on Twitter @krbenedict

Join the SAP Enterprise Mobility and Sybase Unwired Platform Groups

Read The Mobility News Weekly

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.

Mobile Expert Video Series: IDC Research's Nicholas McQuire

In this segment of the Mobile Expert Video Series, I got the opportunity to interview IDC Research's Nicholas McQuire in Rotterdam at the Enterprise Mobility Exchange.  He is one of my favorite speakers and interviewees.  In this video we dig deep into how multinational corporations support a BYOD (bring your own device) strategy.

D0 you know I have recorded hundreds of mobile expert interviews and they are available in my archives?

*************************************************************

Kevin Benedict, Mobile Industry Analyst, Mobile Strategy Consultant and SAP Mentor Alumnus

Visit MobileEnterpriseStrategies.com

Follow me on Twitter @krbenedict

Join the SAP Enterprise Mobility and Sybase Unwired Platform Groups

Read The Mobility News Weekly

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.

Mobile Expert Podcast Series: PSION's Mike Petersen, Part 1

I had the pleasure of interviewing PSION's Mike Petersen this week about rugged and industrial grade mobile devices, total cost of ownership and device strategies.  This is Part 1, you can listen to Part 2 of this interview here.  This article is a good one for those debating the merits of using consumer grade smartphones or rugged handhelds for specific jobs and tasks.

When you are done listening to this podcast, I hope you will take a few minutes to complete the enterprise mobility survey.  All participants will receive the survey results in a report for free.

*************************************************************

Kevin Benedict, Independent Mobile and M2M Industry Analyst, SAP Mentor Volunteer

Visit MobileEnterpriseStrategies.com

Follow me on Twitter @krbenedict

Join the SAP Enterprise Mobility Group

Read The Mobility 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.

SAP PCN Webcast on Mobile Device Management

I wanted to share information about an upcoming SAP PCN webcast on mobile device management that I will be participating in at 2 PM ET on March 2, 2011. Here is an excerpt from the SAP PCN's official invitation.

LEARN HOW YOU CAN BETTER MANAGE ENTERPRISE MOBILITY

Learn Directly from SAP and Industry Experts About Key Device Management Aspects of Enterprise Mobility

Webinar Highlights

• The case for mobile device management
• What the Afaria mobile device management solution brings to the table
• Strategies for managing your enterprise usage of mobile devices such as iOS, Android, and Blackberry
• Deploying and integrating with Afaria

Panelists

Kevin Benedict
Kevin Benedict is an SAP mentor volunteer, blogger, mobile and M2M industry analyst, and SAP Topic Leader for enterprise mobility.  He is a popular enterprise-mobility consultant, writer, and speaker on subjects related to mobile enterprise. Kevin is an entrepreneur and consultant on enterprise mobility. 

James Naftel
James Naftel is an Afaria product manager at Sybase, an SAP company. In this position, James drives product strategy for Afaria, the market-leading mobile-device- management solution from Sybase. His areas of focus include mobile-device software and asset management, identity and access management, and threat management.

Sam Lakkundi
Sam Lakkundi is an enterprise-mobility architect and a “SWAT” team member at Sybase, an SAP company. He has 15 years' experience working directly with customers that employ a wide range of technologies including client server, database, application server, and mobile engineering.

Registration link:
http://bit.ly/hhMiUq



***************************************************
Kevin Benedict, Independent Mobile and M2M Industry Analyst, SAP Mentor Volunteer
Phone +1 208-991-4410
Follow me on Twitter @krbenedict
Join the SAP Enterprise Mobility group on Linkedin:
http://www.linkedin.com/groups?about=&gid=2823585&trk=anet_ug_grppro

Full Disclosure: I am an independent mobility consultant, mobility analyst, writer and Web 2.0 marketing professional. I work with and have worked with many of the companies mentioned in my articles.

Mobile Expert Interview Series: Pyxis Mobile's EVP Christopher Willis

Pyxis Mobile is one of those companies that accomplishes great things, but moves under the radar.  Gartner recently highlighted Pyxis Mobile in their Magic Quadrant report so moving under the radar may be over.  Pyxis Mobile has over 500,000 mobile clients in the field.  Most of their traditional customers are in the financial services industry, but they have been rapidly expanding into higher education, manufacturing and pharmaceuticals. I had the opportunity recently to interview Chris Willis, Pyxis Mobile's EVP of Marketing and Strategy.

Chris joined Pyxis in 1998.  In 2001 the company became 100% focused on enterprise mobility. 

Chris what mobile device do you carry?
I carry two mobile devices, the iPhone for personal use, and the BlackBerry Bold for professional use.  I have always used BlackBerrys professionally and am just used to it.  I know how to get what I need from it.  I use the iPhone as a large iPod.

What is your favorite mobile application?
A CRM application built by Pyxis Mobile.  It is connected to our expense management system and enables me to complete my expense reports while on the road.  On the personal side I love MLB at Bat.  When you see MLB at Bat on an iPad it is amazing.  It is better than the programs you get at the game.

What industries do you see adopting mobility?
Financial services is big for us.  Seventy percent of our business is still in financial services.  We have developed complete trading systems on mobile devices for some customers.  Higher education is big for us.  We have developed all kinds of mobile applications for universities that show class schedules, grades, etc.  Emerging markets for us are in manufacturing and pharmaceuticals.

What business processes do you see companies mobilizing first?
Sales and field services to start, however, nowadays we are seeing a lot of B2C (business to consumer) application demand.  Companies want to give mobile applications to their customers for product sales, branding, marketing and customer support.

What are some of the most surprising trends that you saw in mobility over the past 12 months?
B2C is the biggest trend - "There's an App for that!"  Companies wanting to provide their customers with mobile applications.

What do you see happening in the near future, say 2010-2011?
Mobility vendors delivering on their promises and filling the missing "app gaps."  Companies are now educated on mobility.  They are now looking for complete solutions and mobility platforms to execute a full enterprise mobility strategy.

Tell me about some of the most interesting mobile applications you have seen in the market.
We have developed a mobile laundry application.  It is a M2M (machine-to-machine) application.  Laundry machines text students in the dorms when there is a machine available and when it is finished.  Another application I love is from Concur Mobile.  It helps you book travel, manage travel expenses, call taxis and have it all paid for by the credit card they have on file.  No cash needed.  You can also use it to photograph receipts and turn them in as well.  Nice!

What are some of the most unusual mobile applications you have seen?
There is an application that consists of a website and a mobile application. The website shows a 2D barcode on the screen, and your iPhone captures the barcode and activates various games that use the accelerometer on the iPhone to control various objects in races.  Very interesting!

When is a consumer oriented mobile device sufficient, and when do you need a ruggedized industrial grade device?
Consumer devices (smartphones) are capturing market share from industrial grade mobile handhelds.  There is less interest in expensive rugged devices, because the service technician is carrying a smartphone anyway.  If you buy expensive rugged devices, they will now have two devices to break.  Many companies are simply buying rugged cases for smartphones.

What is the most complex mobile application that you have seen?
We developed entire mobile trading systems for use by companies in the financial services industry.  Very complex!  We developed a very sophisticated mobile application for Thomas Reuters that pulled data from dozens of different sources.

What are some of the biggest challenges you see in the mobile industry today?
Rapid changes to mobile operating systems and new mobile devices.  Today Samsung announced a new mobile OS.  Today enterprises use the same mobile OS as consumer devices so we need to stay on top of all of them.

What do you see from ERP vendors in mobility?
All ERPs have to mobilize their solutions.  Pyxis Mobile is supporting all the majors, and we believe this is a competitive advantage.

What is still missing from MEAPs (mobile enterprise application platforms)?
I think MEAP vendors are simply taking different approaches.  Some try to be ERP agnostic.  Others focused on specific markets.  I think the differences will be how effective you are with partners.  Are you systems integrator friendly?  Pyxis Mobile provides tools for SIs to develop and support new mobile applications.  This is important!

How important is mobile device management to your customers?
It isn't.  Our customers don't ask for it.  Smartphones and online app stores seem to have resolved many of the earlier issues.  Perhaps in the future our customers will ask for it.

How is Pyxis Mobile positioned?
We are the one mobility platform that enables all of a company's mobility needs including B2B and B2C.  We cover mobile enterprise and consumer applications.

What are your thoughts on when thick/rich mobile clients are needed and when micro-apps or browser apps are needed?
We like rich native apps that optimize what you can do on each OS and mobile device.

Do your customers want to develop their own mobile applications using your Application Studio, or do they want you to develop it?
About 80% of our customers want us, or one of our systems integrator partners to develop the mobile application for them.  They are not experienced, but we are.

Thanks for your time Chris!!!

To read more interviews in the Mobile Expert Interview series, visit:
- http://mobileenterprisestrategies.blogspot.com/p/mobile-expert-interview-series.html

To watch videos of mobile expert interviews, visit:
- http://mobileenterprisestrategies.blogspot.com/p/mobile-expert-video-series.html

For a weekly recap of mobility news, analysis and market numbers read:
- http://mobileenterprisestrategies.blogspot.com/p/kevins-mobility-news-weekly.html

***************************************************
Kevin Benedict, SAP Mentor, SAP Top Contributor, Mobile and M2M Industry Analyst
CEO/Principal Consultant, Netcentric Strategies LLC
http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
http://twitter.com/krbenedict
***Full Disclosure: I am an independent mobility consultant and Web 2.0 marketing expert. I work with and have worked with many of the companies mentioned in my articles.
***************************************************

MEAPs, Thick Clients and Mobile Chain of Custody Applications

For people with HIV/AIDS in developing countries like Ethiopia, Cote D’Ivoire, Kenya, and Ghana, receiving AIDS mediation in a cost effective, secure and reliable manner is critical to saving the lives of millions.  In addition to the health crisis, the geographical challenges of trying to care for patients that live in remote villages where access to medical facilities is minimal is a huge obstacle.

The challenge undertaken by global health organizations and companies funded by PEPFAR was to create a drug delivery system that would accomplish the following:

1. Expedite the delivery process.
2. Ensure the secure transfer of drugs.
3. Provide visibility and transparency to participating agencies.
4. Ensure accurate deliveries.
5. Automate ARV drug processes that provide a rapid, regular, reliable supply of medications to patients.
6. Provide a transactional record of the ARV drugs and test kits at every key point in the distribution chain.

The bottom line goal was to provide a truly mobile chain of custody system that could extend across a challenging geographical landscape with minimal technology infrastructure. How was this goal accomplished?  The answer - by implementing a MEAP solution that enabled delivery drivers to utilize a mobile application designed to work in a disconnected or connected model.  The application leveraged the power and flexibility of an enterprise quality mobile database in a thick mobile client that enabled the delivery drivers to maintain inventory counts, accept proof of delivery, and store key data on a consumer grade PDA until they could be connected with the internet at a later time.

Prior to implementing mobile solutions, agencies were only able to track drugs to a warehouse located in the larger cities in many countries.  Now delivery drivers are supplied with a mobile application that can track the delivery and re-ordering of ARV drugs from the warehouse, to regional distribution centers, to area regional centers and finally to the patient.  Every time the ARV medications change hands, a digital record is made of the transaction.  The information collected is synchronized back up the chain where program managers can actively manage the continual flow of mediations.

Since implementation this mobile solution has helped over 50,000 AIDS patients receive treatments in the Ivory Coast alone.  This, coupled with the fact that the mobile solutions decreased the delivery cycle from three months to as little as three weeks, has caught the attention of many other countries and relief organizations around the world.   These thick client mobile applications that operate in a connected and disconnected mode are critical to these kinds of environments.  Many organizations are looking at using MEAPs and thick client applications to offer better and more timely treatment to those afflicted with AIDS.

In the SAP ecosystem Sky Technologies, Sybase, and Syclo are the SAP mobility partners that seem to focus on supporting custom mobile applications with MEAPs that operate in both connected and disconnected modes using a thick client architectures.  By thick client I mean a mobile application that can operate with or without connectivity and that includes a mobile database for storing data on the device while waiting for synchronization.

In my opinion a good MEAP should have an SDK so that the IT department can utilize it to update and edit mobile applications and develop new ones.  Without a good SDK that the IT department can learn, the enterprise is hostage to the vendor.  The world of mobility is moving far too fast, and the IT department needs to be able to update and upgrade mobile applications on their schedule not the vendors.

Mobile micro-applications and mobile browser based applications are valuable and provide significant ROIs in many situations, but they cannot support the rugged environments described in this case study and would not have saved thousands of lives like the thick client mobile solution that was used.

***************************************************
Kevin Benedict
SAP Mentor, Mobile Industry Analyst, Founder/CEO Netcentric Strategies LLC
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy Consultant and Web 2.0 Marketing Services
www.linkedin.com/in/kevinbenedict
twitter: http://twitter.com/krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/
***Full Disclosure: I am an independent mobility consultant and Web 2.0 marketing expert. I work with and have worked with many of the companies mentioned in my articles. ***************************************************

Mobile Expert Interview Series: PriceWaterhouseCoopers' Ahmed El Adl, PhD

I had the privilege of interviewing PriceWaterhouseCoopers' Director of Enterprise Mobility Solutions, Dr. Ahmed El Adl a few days ago. He works out of PWC's Boston office and focuses on developing and expanding PWC's mobility practice. He is a big fan of this blog which instantly increased his credibility with me.

Ahmed worked for SAP in Waldorf from 1998-2002 and focused on SAP's CRM solutions. In fact he was involved in one of the very first mobility projects for SAP CRM. At that time SAP's architecture was simply not suited for mobility and it did not go well.

Ahmed said that a lesson learned from that first mobile SAP CRM experience was not to let sales and marketing completely drive design and engineering. The engineers developed everything that the marketing teams asked for, but the result was a mobile application that was far too big and heavy to work for customers.

Ahmed is a fan of SAP's current mobile strategy of working with many mobility partners. He believes SAP should slow down and focus on defining the mobile connectivity layer and open up their system for more nimble and innovative mobility partners to provide mobile applications. Mobility is evolving very fast and it is hard for a giant like SAP to effectively keep up. By opening up to mobility partners, SAP customers can get what they want now without waiting for SAP.Ahmed is the kind of consultant I would want to hire. He has experienced the good and bad of early mobility adoption and brings great wisdom to the table now.

Although Ahmed agrees with SAP's current strategy and likes what he sees from many of SAP's mobility partners, it doesn't mean he is satisfied. He believes Sybase, an SAP mobility partner, is good but complex, heavy and has too many different components and technology layers. He listed the numbers of technology layers that are involved in a Sybase/SAP integration and it was daunting.

He shared his thoughts on Sky Technologies, another SAP mobility partner. He thought their approach was interesting, but he was concerned that their "mobile SAP innerware" strategy would introduce challenges. He wondered how IT departments would accept a third party mobility solution being so closely embedded with SAP code? Would the benefits out weigh the risks for IT departments? Would they accept it, or avoid it?

He said he likes much of what he sees from SAP's mobility partners, however he is still cautious. In fact, he has recommended to some clients that they should go through a complete RFI process to determine for themselves which vendor has the best fit for them.

Ahmed believes that ultimately SAP customers will want a strong MEAP (mobile enterprise application platform) that they can standardize on, but for today mobile micro-apps can provide real value quickly. I was particularly interested in this statement as it aligns with many of the comments that other industry experts shared on the SAP Enterprise Mobility group on Linkedin.

Ahmed identified several areas of mobility that he finds particularly interesting:

1. Telemedicine
2. Medical diagnostics that feed data to iPhone applications (e.g. EKGs, x-rays)
3. The Apple iTune model for app stores that allows small companies to compete against the big software companies.
4. He loves the idea of unlimited innovation, on a level playing field, and that one person software companies can help large enterprises increase productivity.

I asked Ahmed what mobile device or smartphone does he carry. He said all of them. He carries a PWC issued Blackberry in his pocket, but he literally travels with a suitcase full of different mobile devices that he can show off and demonstrate to clients. What a nightmare for the TSA agents! Don't get in line behind him.

I want to again thank Dr. Ahmed El Adl for his time and willingness to share his insights.

This article was the third in the series called Mobile Expert Interviews. See related articles:

• Mobile Expert Interview Series: Nokia's John Choate
• Mobile Expert Interview Series - Jane and Keelin Glendon of HotButtons

***************************************************
Kevin Benedict
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy Consultant, Mobile Industry Analyst and Web 2.0 Marketing Expert
http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
twitter: http://twitter.com/krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/

***Full Disclosure: I am an independent mobility consultant and Web 2.0 marketing expert. I work with and have worked with many of the companies mentioned in my articles.
**************************************************

Sybase, iPad and an Analysis - I am Not Usually Snarky

I am mostly nice on this blog, but come on Sybase!!! What were you thinking with this report, "...Sybase has announced the results of a survey on mobile device usage, commissioned by Sybase and conducted by Zogby International. The survey, which was compiled from an online survey of 2443 adults with a mobile phone, 770 of which own smart phones, uncovered that the #1 reason U.S. consumers would use a device such as the Apple iPad is for "working on the go."

Sybase, the next time you want to commission such an in-depth report please call me. I will conduct it for at least 10% less than Zogby International and come up with the same findings.

More, "...the study demonstrates that consumers want more access to information and work applications on their mobile devices." OK, with that level of analysis, perhaps I would need to add another 5% to my proposal.

I looked up the definition of the word snarky. Sybase's report makes me feel that way. If you want to hear the word snarky, click here.

Remember to join the SAP Enterprise Mobility group on Linkedin if you are interested in real expert advice.

***************************************************
Kevin Benedict
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy Consultant, Mobile Industry Analyst and Web 2.0 Marketing Expert
http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
twitter: http://twitter.com/krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/

***Full Disclosure: I am an independent mobility consultant and Web 2.0 marketing expert. I work with and have worked with many of the companies mentioned in my articles.

**************************************************

Advice for Mobile Start-ups: Working with SAP, Part 5

Part 4 of this series may have demoralized some mobile start-ups hoping to work closely with SAP, but Part 5 in this series provides solutions to many of the challenges identified in Part 4. Let's now take a closer look at some of the comments I made in Part 4.

The SAP customer is simplifying their IT infrastructure to reduce complexity and no non-SAP technology will be added unless it is approved by 17 business and IT committees. Who has the time to fight this battle?

• Embed your solution in SAP so it becomes a part of SAP and avoids these issues (Sky Technologies, a Certified SAP Partner embeds their mobile solutions in SAP)
  
• Simply provide a mobile application or iPhone view of SAP's current applications (Mobile micro-apps)
  

The IT Managers only want to learn mobile technology that will add to their resume and help them get their next assignment. The cool mobile technology that they just witnessed does not have its own category on the IT recruiters' websites. They want NAME power on their resume.

• Show IT managers how to extend their current SAP infrastructure and code to mobile applications. This will accomplish their purposes.
  
• Show IT managers that your solution is from a Certified SAP Partner
  

The SAP system integrator does not support the mobile technology, so recommends some other mobile solution that they support and have trained experts on.

• Go directly to the end user with your message and evangelize and educate them. Build support internally for the "best" mobile technology. Close the deal first, then motivate the system integrator to be trained on your mobile technology and play a role in the implementation.
  

The SAP sales team does not get quota credit on it, but they do on another mobile solution. If the sales person does not make their numbers they are fired, so they do not care which mobile technology is better if it does not help keep their job.

• Find a way for your mobile technology to sell more SAP licenses and products. Perhaps the mobile workforce that is not currently using SAP licenses will need them if they are connected via mobile devices. This would encourage the SAP sales force to work with you to sell more SAP licenses. Think in terms of the SAP AE's interests as well as the customers.
  

SAP's Industry Principals and Solutions Managers also must be very selective as to the mobile technology they recommend. They would not want to recommend a product that was not on the SAP price list or Certified Partner list, unless there was no other viable choice or this product helped sell other SAP licenses that benefited the SAP sales team.

• SAP has only identified a few mobile categories for partnerships; field service automation, route/delivery and mobile CRM. I can tell you from personal experience that hundreds of mobile applications are needed in most large enterprises. Mobile applications that deal with security, asset management, inspections, compliance, job estimating, fleet management, engineering, construction, logistics, etc. There are massive opportunities to mobilize these business processes.
  
• Show the SAP user and the SAP sales team how you can help them.
  

SAP customers are often on 5 year plans. These plans include upgrades, roll-outs, add-ons, customization, old product sun setting, mergers and acquisitions, etc. What does this mean to the mobile entrepreneur? It means your product needs a 5 year road map that aligns with SAP and the SAP customer's. If it does not, you are unlikely to survive the first round.

• Be the thought leader and explain where mobility is going to be in 5 years. Tell them why your solution is better aligned with the direction of mobility than any.
  

The biggest project and highest priority in the company is around route delivery improvement, and your project is mobile SAP CRM. The route delivery mobility vendor agrees to extend their mobile solution into mobile CRM and since it is a higher priority, you lose.

• Understand the decision making process, organizational chart and budget limits within IT and the department you are targeting. Can you keep the project cost below the threshold that requires additional management approvals? Can you break down your project so that yearly costs keep it below the approval thresholds so you can simply focus on this one department until it is firmly established?
  

The CIO will never get invited to speak in front of thousands at Sapphire if they choose your solution. Your user conferences could be held at Denny's.

• Become a Certified SAP partner and attend Sapphire yourself. Be a mobile solution provider in a different category than other larger mobility vendors. Be the mobile application provider for; food processors, engineers, bridge inspections, healthcare, quality assurance, sustainability, etc., and then expand your mobile offerings. That is exactly what all the other mobile partners of SAP are doing.
  

If you would like to discuss these strategies and/or my consulting practice please contact me.

Related Articles:

• Advice for Mobile Start-ups: Working with SAP, Part 1
  
• Advice for Mobile Start-Ups: Working with SAP, Part 2
  
• Advice for Mobile Start-Ups: Working with SAP, Part 3
  
• Advice for Mobile Start-Ups: Working with SAP, Part 4
  
• Advice for Mobile Start-Ups: Find Your Market Aggregation Points
  
• Advice to Mobile Start-Ups: You are a Publishing Company Like it or Not!
  
• Advice to Mobile Start-ups: Focus on Mobile Content, Mobile Business Processes, Integration and Workflow
  

____________________________

Author Kevin Benedict
Mobility Consultant, Wireless Industry Analyst and Web 2.0 Marketing Expert

http://www.netcentric-strategies.com/

***Full Disclosure: I am an independent mobility consultant and Web 2.0 marketing expert and as such I work with, and have worked with, many of the companies mentioned in my articles.

Mobile Enterprise Application Platforms, SAP and Marketing

Yesterday I was reading Gartner's Magic Quadrant for Mobile Enterprise Application Platforms. It was interesting to me that one of the points Gartner considers before including a MEAP vendor in their report is marketing. They consider the following:

1. Success at marketing (I am guessing it is measured by sales?)
2. Market awareness (name recognition within a target market)
3. Marketing strategy (if Gartner is convinced you have a good strategy)
4. Your ability to recruit a good partner ecosystem and support it through marketing

Think about it. You invest millions of dollars and tens of thousands of man/woman hours into your products, middleware, synchronization technologies, SAP integration methodologies, databases, device management dashboards, rapid application development environments and multi-channel support for dozens of mobile devices, but that is not enough. Gartner is going to evaluate your marketing before including you in their report.

Gartner understands what many smart engineers have not yet learned. A better mouse trap does not sell itself or pay the expenses - sales do. Unless a comprehensive marketing plan is designed, developed and successfully implemented you will not gain sufficient mind share and market share quick enough to remain viable in this fast changing market.

It almost seems like SAP is holding a marketing Olympics for their mobility partners. They have chosen to partner with a handful of companies like Sky Technologies, Syclo, Sybase, RIM and ClickSoftware. Many of these companies have overlapping mobility solutions, but SAP seems to want to invite their partners to compete on the marketing field and see which one comes out on top.

I enjoy a good game of strategy. Although, I can feel the pain that passionate software engineers must feel. They have dedicated their life to developing a progammer's MEAP masterpiece, but the winner is determined by the folks in the marketing department with the expense accounts and travel budgets.


***************************************************
Author Kevin Benedict
Mobility Consultant, Wireless Industry Analyst and Web 2.0 Marketing Expert

http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
twitter: http://twitter.com/krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/

***Full Disclosure: I am a mobility consultant and Web 2.0 marketing expert and as such I work with, and have worked with, some of the companies mentioned in my articles.
**************************************************

$21 Million Raised by Pressing the Keys on a Mobile Device

The Red Cross was "texted" $21 million dollars in donations for Haiti disaster relief efforts according to this article. This is an incredible development, and it happened on mobile devices.

The Haiti relief campaign has been promoted by both traditional media sources and online social media. However, it really took off in the first couple of days through its promotion on Facebook and Twitter. The report said these donations were texted, so these donations were submitted on mobile devices.

It works like this:

1. You get notified of the campaign through a mobile Facebook or twitter application
2. You send a text to a given number and a $10 dollar charge (donation) appears on your mobile phone bill.
3. You pay your mobile phone bill and the money is transferred from your carrier to the Red Cross

I am amazed at this example of the power represented by mobile communications, social media and mobile devices. I am also intrigued by the e-commerce processes represented by using the mobile phone billing system to collect these donations.

By simply pushing a few buttons on a handheld mobile device you can (collectively) be saving lives on the other side of the planet.

Let's all take a moment to be amazed together, and celebrate the good in these times of pain.

***********************************************
Author Kevin Benedict
Independent Mobility Consultant, Wireless Industry Analyst and Marketing Consultant
www.linkedin.com/in/kevinbenedict
twitter: @krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/
***********************************************

Peer-to-Peer Mobile Computing and Field Services Automation, Part 1

There are a lot of times when the supervisor or owner/operator of a SMB (small to medium sized business) is not at his or her desk staring at the computer screen. They are often in the field working with customers and their service teams. The problem with this is that it prevents visibility to other projects that may benefit from the supervisor's real time advice and oversight. Let's now talk about some possible solutions to this issue.

In many field service automation or work order management software applications, the design and architecture of the software is in a client server model. Information and electronic service tickets are wirelessly dispatched to mobile handheld computers and Smart phones, and the service technician completes the electronic service ticket and the information is synchronized back to the server in the office. The problem with this design again is that the supervisor who is most interested in viewing this real-time work order information is not in the office looking at the application on the server.

One possible solution would be to create a special managers view or summary of all operational data. A summary of all inbound and outbound work orders, business process or rule exceptions, identify issues or customer relationship problems and then synchronize this subset of information out to the supervisor's mobile handheld computer or Smart phone. This would provide a management summary in a dashboard view of all operations.

A second option would be to provide a complete duplication of all information to the supervisor. You would duplicate and synchronize all inbound and outbound work orders to the supervisor's mobile device. There would be no summary, rather all information would be synchronized out from the server to the supervisor's mobile handheld.

A third option would be to have the mobile device of all the service technicians synchronize in a peer-to-peer model directly with the supervisor's mobile device and the office server. This would require the supervisor's mobile handheld computer or netbook to have full server synchronization capabilities that would enable all of his or her mobile service technicians to constantly synchronize with it. This would be data intensive and may cause synchronization performance issues, but would enable the supervisor to see all operations in real-time.

A fourth option is to have a real-time online connection between the supervisor's mobile device and the office server. This would only work when there was wireless connectivity available, but could provide efficient and real-time visibility into all the operations of the company.

In Part 2 of Peer-to-Peer Mobile Computing and Field Services Automation, we will discuss some ideas for using location based services (LBS) and P2P computing with Field Service Technicians.

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

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

Mobile Applications that Move Things

There is a new category of mobile software applications for Smart Phones and handheld computers that physically move things. I love it!!! Zip Car, a rental car service, allows you to use your iPhone to both find and unlock the rental car. Zip Car's business model is they park their rental cars around a metropolitan area and people can register and pay for the rental online, then they are provided with a list of locations where these cars are parked near them. Once there, they can enter their rental code into their iPhone and the Zip Car is unlocked for them.

In this USA Today article, a California company has now created an application called Viper SmartStart that can replace your car keys. Your iPhone will now be able to lock, unlock and start your car. Again, your Smart Phone is controlling mechanical movements. Next I can see throwing away my garage door opener, TV Remote and using my iPhone to start up and warm my car during the dark of winter.

I have read in other articles about home security systems and security related video cameras all being managed and activated by Smart Phones. There has been the concept of convergent devices for some time, but this generally referred to converging different pieces of equipment such as bar code scanners, GPS, digital cameras etc, together in one mobile device. This new Convergence 2.0 includes taking control of and managing the mechanical movement of things.

***********************************************
Author Kevin Benedict
Independent Mobile Strategy and Marketing Consultant
www.linkedin.com/in/kevinbenedict
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/
***********************************************

54 Questions to Help You Select the Right Mobile Handheld Computer

Mobile computing requires mobile computers. Which brands and models you select can be a hard decision. The following list of questions are designed to help you think through some of the big issues that will enable you to narrow down the selection list.

The first big question you should answer is what is the primary purpose of the handheld or mobile device. Is it barcode scanning, GPS, RFID, surveying, map reading, voice calls, email, digital signatures or field data collection?

The second big question is what is the environment that the device will be used in. Is it used in the office, clinic, warehouse, cold storage or out in the rain on a construction site.

There are a large number of very good handheld computers, PDAs, Tablet PCs, laptops and Smart Phones to select from, however, the key to getting the right mobile device is to research the business purposes and the environment in which the solution will be used before making a selection. The following questions should help you narrow down your list of mobile handheld computers:

1. What environment will you be working in - is it hot, cold, wet or dusty?
2. How rugged do you need your device? There is a ruggedness scale.
3. Are there explosive vapors or explosive powders?
4. Is it a clean office environment, or a muddy and rugged outdoors environment?
5. Is the user in and out of vehicles all day?
6. Is your software application focused exclusively on bar code scanning, RFID reading, GPS, or do you need a multi-purpose data collection device?
7. Will the hardware configuration ever need to be changed? Some handhelds can be configured at will; others are locked and can only be used with the original configuration.
8. Will the device be used as a primary phone, or is it focused on data collection?
9. What hardware requirements does your mobile application require?
10. Will the battery last long enough to complete your daily work between charges? Do you need back-up batteries? Can you use batteries purchased at the local market, or are they vendor specific?
11. What is your budget? What does the value of using a handheld computer justify spending?
12. Do you have enough budget to purchase or develop the mobile software and hardware you need? Does your budget only allow for low cost consumer devices?
13. How many replacements(of a consumer device) does it take to equal the cost of a ruggedized handheld?
14. How do you replace broken devices? Can you get a replacement service in 24 hours, or must you wait a week?
15. What kind of support contracts and warranties are available?
16. How long will your new handheld computer be supported, serviced and manufactured by the vendor? Is it near end of life and being discounted for a reason?
17. Can you upgrade the operating system when Microsoft releases a new version of their mobile operating system?
18. Can you use standard laptop data cards in the handheld, or do you need to pay for high priced vendor specific cards?
19. Can you view the screen effectively in the sunlight?
20. Can you add more memory if your requirements increase?
21. A few industrial handheld computers have flashlights built into the device to provide better light for taking digital photos. Is this useful?
22. Do you require GPS? If so, how accurate?
23. Will your users be wearing gloves? If so, small keyboard buttons won't work. How big of keys do you need?
24. Do you need a water proof, or just water resistant case for your handheld?
25. Does the bar code scanner work effectively in real-world environment? Some scanners cannot scan effectively through glass or plastic.
26. Is the size and weight of the handheld appropriate for the user and environment?
27. Can your handheld computer support all the add-ons you require at the same time? Some devices can only support a specific number of add-on components so you are forced to choose. Some cannot support both a GPS and a data card at the same time. Some devices cannot support both a bar code scanner and a GPS add-on. This is an important consideration.
28. Do you need only a touch screen and navigation pad, a number pad or a full QWERTY keyboard? This is very important for user acceptance.
29. Is the handheld device also going to be used as a phone? Is a 2 pound industrial grade handheld really a usable phone?
30. Does your low cost consumer grade PDA need a rugged case like the ones Otterbox sells?
    If you only have a budget for a low cost device, does it support the battery life and add-on components you require?
31. How will the device be transported around a job site? Will it strap to a belt, swing from a shoulder strap, sit in a holster or be mounted to the dashboard of your truck? Does your device support your chosen method?
32. Where is the closest inventory of extra handheld computers? Where is the closest repair depot?
33. Will your vendor loan you a device on trial?
34. Can you rent the handheld if you only need it for a short-term project?
35. Does your vendor take trade-ins on your old handheld computers?
36. Can you get the same exact handheld, under a different brand name for less?
37. How will your handheld computer send data back to the office? Cradle sync, WiFi, bluetooth, wireless data card, GPRS/GSM, CDMA?
38. What size screen do you need? Some devices like the Jett-Eye have a "landscape view" others a "portrait view" many have different sized screens. What do you require?
39. Do you need an integrated digital camera? Do you need a low or high resolution camera and does your device support it?
40. Does a refurbished device from Ryzex make better sense that a new device?
41. Where is your vendor's office? Are they in the neighborhood or on the other side of the planet? Does their location offer you the support and attention you deserve?
42. Does your handheld computer run on the same operating system that your mobile software solutions requires? I have had customers order Windows CE devices for their Windows Mobile application. It did not work.
43. Is your device likely to be stolen? If so, you may want to use cheap devices that can be easily secured and replaced. We have implemented projects in Africa where this was an issue for the buyer.
44. Does your handheld computer come with a pistol grip or other straps that help you avoid dropping it?
45. Can you comfortably hold the device in your handheld and complete your work? Some devices have scanners on the side, on the end or underneath.
46. Can you effectively view the data you need? Some jobs simply require a full keyboard and a full screen for viewing large CAD files or Maps. Does your screen size match your requirements?
47. Where will you store the device when you use the washroom? One of my customers used Tablet PCs and they kept breaking when they slipped off of the sinks in the bathrooms.
48. Does the mobile device you select support the RFID reader you need for distance and accuracy?
49. Does the battery in the mobile handheld last long enough after you have added on all the additional hardware accessories? Each added radio uses more energy.
50. If you have dozens of handheld computers, how will you charge them all at the same time? Do you have a docking station that allows for all of your devices to both charge and synchronize at the same time?
51. Do you need wireless data plans, or does batch synchronziation after each shift work?
52. What wireless carrier and data plan provides the best service and cost for you? Does that wireless carrier support your mobile device?
53. Does the wireless carrier have sufficient coverage for your workers?
54. What is your budget for each handheld computer? This may limit your selection and make the choice simpler.

I don't sell or represent any mobile hardware. I have just managed many mobile application development projects around the world so have learned some lessons. If you would like to discuss this topic in more detail please contact me.

***********************************************
http://mobileenterprisestrategies.blogspot.com/
***********************************************

Mobile Applications and 69 Enterprise Support Questions

Often the focus of a mobile software project is on gathering the functional requirements, designing, developing and deploying the mobile solution, but little or no advanced planning is given to the question of how to support it once it is deployed. The following list contains many of the questions your IT helpdesk and support department will want and need to know:

1. Who does the field worker call if there is a mobile device problem?
2. Who does the field worker call if their mobile application is not synchronizing correctly?
3. Who trains new employees on how to use the mobile device and application?
4. If there is a mobile software problem, who fixes it - IT, consultant, contractor, your systems integrator or VAR? How do you get in contact with them?
5. Who does the field worker call if the mobile application needs edited or upgraded?
6. If the user downloads a new version of the mobile operating system and the mobile application doesn't work, who will fix it?
7. How do you prevent mobile users from downloading new software applications that might break the system?
8. How do you back-up mobile devices so the information is centralized?
9. Who owns and defines the business process you have mobilized? They may need to approve any changes to the business process.
10. Who controls the security of the device?
11. How do you set-up a new user to securely access the enterprise database?
12. What kinds of security rules must the field user follow?
13. Do different users have different security profiles?
14. Is there a standard set of security rules for mobile devices across the enterprise?
15. Who controls access to the enterprise database application (a DBA)?
16. Will the Database Administrator allow you to synchronize data directly to their enterprise database application, or do they want a "staging database" or API layer to review all data before it is loaded to the enteprise database application. They will likely be involved in any future changes to the mobile application.
17. Are synchronizations done in real-time, near-real-time, or batch on a schedule?
18. Does one mobile device have multiple synchronizing applications? Are they on different schedules or do they synchronize at the same time?
19. How many different enterprise database applications are synchronizing with a mobile device? If there is a sync problem, how do you know what database applications may be impacted?
20. If you hire an additional field worker, how do you order an additional mobile device? Whose budget covers this? Who is the vendor? What support plan or insurance plan should be included?
21. Who decides if the new mobile device needs to be ruggedized or a consumer grade? What level of ruggedness is required for the specific user?
22. Do different job functions require different devices, carriers and wireless data service plans?
23. Who decides what brand of mobile devices are going to be the company standard?
24. Where do you purchase your mobile devices if one breaks or you need to add one to your inventory? Do you have a corporate discount or volume discount agreement?
25. How do you manage and control the variable costs of using a data plan from a local wireless carrier? What happens if the costs of the data services gets out of control? Who pays for it?
26. Are the mobile devices or the mobile software solutions under warranty? Where are these contracts stored? Who owns them?
27. Is there a yearly support contract IT needs to know about? How much? Whose budget?
    What is the account number the warranty is under?
28. How do you set-up a new data plan for a new user with your wireless carrier? Who does that in the company? What is the account number so you can add subscribers? Whose budget pays for it?
29. What happens when Microsoft releases a new Windows Mobile operating system and you can only purchase mobile devices with the new OS on them? Who is going to upgrade your mobile software solutions so they work with the new OS?
30. What happens when the field engineer treks across 2 miles of muddy field to work at a construction site, but the battery on his handheld computer dies about 10 minutes after he gets there? What is the backup battery plan?
31. What happens when text messages, photos, videos, music, and games claim all the memory on the rugged PDA and the Construction application becomes either too slow or unreliable because of low memory?
32. How do you know when your mobile workers are synchronizing the latest information? You don't want mobile workers going days without synchronizing their device.
33. When you send an updated software application to your mobile workers, how do you know who is using the new application and who is still on the old?
34. How do you disable synchronization on a lost or stolen mobile device?
35. How do you kill and/or protect your data on the mobile device if it is lost or stolen?
36. How do you keep track of which workers are using which mobile devices? If there is an operating system update, or firmware update, how do you know who needs it?
37. What is the process for bringing mobile handhelds into the IT department for repairs and upgrades? Is there a central location, or should various locations be scheduled on specific dates.
38. If you are taking care of many different mobile field workers and many different mobile devices with a variety of operating systems, wireless carriers and screen sizes, how do you track who gets what?
39. If you have a project manager that requires visibility to more data than other workers, how do you manage different views on the handheld computer?
40. Some mobile projects require different levels of security, for different levels of data visibility. How would you manage and track that?
41. Will your company standardize on 1 mobile operating systems or several (Blackberry, Microsoft Windows Mobile, Palm, Android, iPhone, etc)
42. Some applications require barcode, RFID, GPS, digital camera and other specialized data collection accessories, while others don't. How does the IT Helpdesk track the brand, version and other details of these accessories?
43. If a dump truck backs over your supervisor's $1800 ruggedized computer and crushes it into hundreds of unidentifiable pieces, how do you get a replacement out to the supervisor with the exact application and data that is required as quickly as possible?
44. If a mobile device needs repaired - what is the process for keeping your field workers operating without it? Do you have a stock of spare mobile devices?
45. Does your mobile device reseller have a replacement program?
46. How do you deploy new mobile applications to your 1,300 mobile device users? Must they bring all their devices back to the IT department, or can you publish new applications directly to the handheld computer?
47. How do you support the mobile device, when the user has limited computer knowledge and is sitting on the top of a utility pole? What tools can the IT Helpdesk use to remotely help and diagnose problems?
48. How do you recognize a defective mobile device that is being shared by 12 different mobile workers? Do you have a method of identifying which problems are being reported on a particular device or are you logging support calls only by users?
49. What is your process for dispatching work orders to service technicians when they are disconnected or out of range of cellular and wireless networks? A process needs to be defined.
50. What is your synchronization plan for each mobile worker? Can they sync in the morning and evening at their office desk, or do they need to sync every 5 minutes or in real-time?
51. What is the synchronization plan for a service technician that rarely has wireless network access? Does it justify a satellite up-link? (Sears Service Technicians use both)
52. How do you know when information was successfully synchronized with a mobile device in the field? Can you see and determine the success of the synchronization from the IT Helpdesk?
53. What is an acceptable synchronization time? Is it 20 seconds, 2 minutes, 20 minutes? Does the IT Helpdesk know what times are acceptable so they can consider this when configuring a new user?
54. Does all data need to be synchronized in real-time, or only some. Product catalogs are an example of updates that may only be needed weekly or monthly?
55. How much data can be synchronized in a given period of time on the chosen connectivity option? Is that an acceptable speed for the task at hand?
56. Who determines the hardware requirements that support the mobile application and desired synchronization speeds?
57. When a new mobile software application is developed, who tests its operating speed on different devices, processors, memory levels and connectivity options to determine what is acceptable and what is not?
58. When you are updating or reconfiguring an enterprise database, how do you know what mobile applications and mobile users will be impacted by these changes? How do you manage this update process?
59. How does the IT Helpdesk know which one of the 17 mobile applications on the handheld computer is having a synchronization problem?
60. If you are supporting 174 work crews and their mobile devices around the globe, how do you know where they are located, and who is responsible for them?
61. How does the IT Helpdesk know if a mobile device is using a cradle, modem, bluetooth, wireless, USB, satellite or Cellular connection to synchronize? The IT Helpdesk really wants to know before they begin working on the issue.
62. What wireless carrier, technology and through-put speed is the mobile device using? Is it GPRS, GSM, CDMA, Edge or some other network configuration?
63. Do you need to stagger the synchronization times? One of my clients had a problem with 300 mobile workers downloading large product catalogs all at the same time each month -the first Monday of the month. This caused a bottleneck and slow downloading times.
64. What do you do with old and retired mobile handheld devices? Companies like Ryzex buy back old handheld mobile devices and recycle them.
65. What rugged or semi-rugged cases are required to protect the mobile device?
66. What add on assessories are supported on the mobile device? Ear pieces, GPS, add-on RFID, barcode scanners? Who supports these and where do you order replacements?
67. Does the same mobile software application work on rugged mobile handhelds and on mobile consumer devices?
68. What employees and roles get the different levels of rugged devices?
69. Do you have a corporate account with a mobile device reseller that will repair all of the different mobile devices or do you work with many different vendors with different support and warranty plans.

All of these questions are very important and need to be answered upfront. If you would like to discuss this subject in more detail please email me.

***********************************************
http://mobileenterprisestrategies.blogspot.com
***********************************************

Mobile Software SDKs and Toolkits for Handheld PDAs and Smart Phones

In the recent article by Peter Wayner of InfoWorld called iPhone development tools that work the way you do, he describes the value of using a mobile application SDK or framework. He lists 4 new toolkits to help mobile application developers develop applications faster for use on handheld PDAs and Smart phones. This is a market in which I am intimately familiar.

The challenge with the market for mobile application frameworks and SDKs is that very few developers want to spend money on an SDK from a small vendor, and even fewer companies want SDKs or are willing to fund long term custom development and support projects internally. Companies want a finished product that works with their ERPs, database and accounting applications. They don't want to invest in a non-standard mobile framework. They want mobile extensions to their enterprise applications. SAP is addressing this with their NetWeaver based mobile infrastructure. This provides SAP users with a standardized method for extending their applications out to mobile devices, but it does not address how to develop the mobile application code. This theoretically creates an opportunity for mobile SDK vendors.

Appforge and Dexterra are two very BIG examples of how challenging it is to be a successful vendor of mobile application frameworks and SDKs. It is yet to be proven that there can be a successful business model as the author of these mobile application frameworks, unless you are a giant like Microsoft or Apple. Dexterra bet the house that Microsoft would acquire them and they lost.

Now, it is true that to make these finished mobile software applications, there is a need for powerful mobile SDKs, but these SDKs are very costly to development and there is yet to be a good and proven business model for small independent vendors of such.

Some vendors of mobile application frameworks want to sell you a toolkit and then charge you a license fee for every mobile device you deploy on. This is not a good model, unless the application is an off-the-shelf mobile application. It makes sense to pay for syncing technology and mobile databases, but a per deployment model for code that you create is hard to swallow.

The biggest challenge vendors of mobile application frameworks and mobile SDKs face is getting the economies of scale that all software companies seek. Who is the real market? Developers? They seek to work in the sexy high profile technologies from the big name companies so they can pad their resumes. They do not want to take a chance on learning an SDK from a very small company that no one knows and they are unlikely able to leverage in the future. They may use an SDK to deliver their cool mobile application, but there is simply not enough of these developers willing to buy your SDK for significant amounts of money to be profitable.

Does the IT department in a company want to buy your SDK, a few but not enough to build a profitable long term software business as an SDK vendor. Again, companies will always seek a finished mobile application that extends their internal IT investment. If SAP has a mobile framework, they want that. If SAP didn't have the mobile extension, then the company would want a finished mobile application that is already integrated with SAP.

In summary, there are many examples of companies developing very cool mobile SDKs and mobile frameworks, but very few with successful business models. Companies want to extend internal applications with mobile extensions developed by the owner of their internal applications. In the event there are no mobile extensions from their key vendor, then they want a finished mobile application that is pre-integrated with their ERP or back-office applications. SDKs are cool, but a successful business model remains elusive.


***********************************************
http://mobileenterprisestrategies.blogspot.com/
***********************************************

Mobile Workflows in the Field, SAP and Other ERPs

The way business processes are designed, implemented and standardized within a company can often mean the difference between success and failure. If often takes years of trial and error, and sometimes flashes of brilliance to come up with just the right business process that will mean success and competitive advantages.

Once the perfect business process is proven it needs to be implemented and automated. Why automated? Because humans are forgetful and have even been known to be from time to time lazy. They want to cut corners and avoid that which is tiresome. Automation enforces and manages the perfect business process.

For years software vendors and ERP developers like SAP have developed applications that help design workflows and workflow engines to run them. These provide the technology infrastructure within the enterprise to automate these business processes and to ensure they are followed, however, once an employee exits the building and drives away in a company van to perform a task remotely, the automated business process breaks down. Suddenly, the business processes that you have spent years perfecting are useless. The employee has broken the "connection" and walked out the door to freedom.

Even today, most mobile field service workers leave the building with a clipboard and a stack of paper service tickets or work orders. How they perform their work, in what order and the processes they utilize in the field are now unsupervised and up for interpretation. The field service technicians often don't much care for the business processes designed by the teams of MBAs in suits at the office. They have their own preferences and opinions about how things should be done, and in remote jobsites who is going to argue?

Many large companies have up to 40% of their employees working remotely and/or in the field on jobsites. How can the SAP or other ERP Business Process Expert design and implement business processes that can be utilized and enforced in mobile and remote locations? This is a challenge worth resolving.

Think about it, a company pays tens of millions of dollars implementing SAP internally and designing business processes and workflows to operate their enterprise. Yet for many services based businesses the money is earned outside the office at remote locations. The location where the customer interaction takes place and where the money is made is often devoid of best in class business process automation.

Mobile applications that need to synchronize with ERPs, should implement mobile workflow support. This requires a client server architecture whereby the mobile client software understands that a workflow or event manager is associated with a particular process and the server also understands that it is both producing and consuming data with the mobile device that is part of an event or workflow. Let me provide a scenario.

A service technician has a ruggded PDA or other mobile device on his belt. He receives an alert that he needs to be dispatched to a jobsite. This initiates a business process with a workflow associated with it. A series of tasks that make up the dispatch and completion of a service ticket are now initiated. The tasks may include:

1. Dispatch receives a service call


2. This initiates a series of tasks including estimating the availability and analyzing the location of all service technicians in the area.


3. Once the nearest available service technician is identified a service dispatch can be sent


4. Service technician confirms availability and accepts the job


5. Least cost and fastest routing information is sent


6. Service technician arrives at the jobsite and pushes a button on his mobile device annoucing his arrival.


7. Arrival message synchronizes with the server workflow or event manager notifying dispatch of his location on site.


8. The workflow may include an inspection, detailed findings, proposed solution, repair and collection of the fee


9. Any parts needed will be automatically deducted from the service vehicle's inventory


10. The workflow can also include sales and marketing activities such as promoting an Annual Service plan or equipment upgrade to the customer


11. The repair is complete, dispatch is notified


12. The service technician is available for another job
    

In this scenario, the mobile client application using a workflow engine that interacts with the server side application steps the service technician through the various tasks included in the business process. These steps can be directions in the form of alerts, messages, next steps, data fields that require input, and feedback from the dispatch office. Each step of the workflow required input from the service technician to confirm that the step had been completed and this information was in turn synchronized with the server side workflow engine. This enables the best practices supported by the company to be practiced and supervised in the field.

SAP has a solution called Event Manager. It is designed to manage activities happening across a geographically dispersed supply chain. It requires data input via B2B and EDI data communications. Similarly, mobile applications can feed data into a centralized workflow or event management solution that helps support and ensure best practices across remote jobsites.

A workflow engine and a mobile client version of a mobile workflow engine is required by companies that want to standardize business processes in the field where interactions with customers take place and where revenue is earned.

If you would like to discuss this concept in more detail please email me.

***********************************************
http://mobileenterprisestrategies.blogspot.com/ /
***********************************************