Showing posts with label mobile software. Show all posts
Showing posts with label mobile software. Show all posts

Innovation and Mobile Applications in Lisbon

I had the honor of speaking in Lisbon, Portugal last week on mobile strategies, Code Halos and digital transformation.  When possible I try study up on the location I am traveling as I recognize it as a special treat that should not be overlooked.  In this short video I share some of my observations about technology innovation, mobile solutions and Portuguese history.  Enjoy!

Video Link: http://youtu.be/_G8pQ06lI6g?list=UUGizQCw2Zbs3eTLwp7icoqw




************************************************************************
Kevin Benedict
Writer, Speaker, Senior Analyst
Digital Transformation, EBA, Center for the Future of Work Cognizant
View my profile on LinkedIn
Learn about mobile strategies at MobileEnterpriseStrategies.com
Follow me on Twitter @krbenedict
Subscribe to Kevin'sYouTube Channel
Join the Linkedin Group Strategic Enterprise Mobility
Join the Google+ Community Mobile Enterprise Strategies
Recommended Strategy Book Code Halos
Recommended iPad App Code Halos for iPads

***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.

Mobile App Design Is Irrelevant - Latest Research

Your mobile app design is irrelevant if your back-end systems can't support the real-time requirements of the user. 

A recent report* by CIO Strategic Marketing Services states that most customer and employee mobility applications are integrated with back-end systems.  Although that is not necessarily a surprise, it is useful to see the average number of apps that are connected to different back-end systems.  Here are the numbers from the survey.

Question: How many of your company's mobile apps for both customers and employees integrate with the following back-end systems? (average number of apps)
  • 4.8 apps per survey participant connect to a CRM systems (including sales, customer service and marketing)
  • 4.8 apps per survey participant connect to an Ecommerce system
  • 4.6 apps per survey participant connect to an ERP (including project management system)
  • 4.4 apps per survey participant connect to a supply chain, logistics or operations system
  • 4.0 apps per survey participant connect to a document management system
  • 3.7 apps per survey participant connect to an accounting and/or financial system
  • 3.6 apps per survey participant connect to an HR (human resource) system
In my recent survey, Real-Time Mobile Infrastructure, eighty participants identified that back-end systems were causing real headaches for mobile app developers.  Here are a few of the questions and their results from the survey:

Question 1: Do you (or your clients') have IT systems that are too slow or incapable of supporting real-time mobile app requirements?  83.9% answered YES.

Question 2: Will your (or your clients') IT environment and back-end systems prevent you from delivering an optimized mobile application experience?  43.2% answered YES.

Question 3: Are your (or your clients') mobile strategies and plans inhibited or limited because of the current IT environment, infrastructure and/or design?  77.7% answered YES.

Question 4: Which components of an end-to-end mobile solution cause the most performance problems (involving mobile apps)?  Here are the top three answers in order of how problematic they are:
  1. Back-end systems 
  2. Internet connectivity
  3. APIs and integration design and performance
Question 5: How important will having optimized mobile applications and user experiences be to the future success of your business? 72% answered "very important" to "critical."

What is the bottom line?  Although it is often more fun and interesting to talk about innovative user experiences and app designs, the foundation for supporting real-time mobile applications must be in place first.  Without back-end system and IT infrastructures that can support a "real-time" environment, you are just putting lipstick on a pig, as we say in Boise, Idaho.

These are the kind of challenges and topics I cover during my Analyst Briefings and Mobile and Digital Strategy workshops.  If your company would benefit from a workshop contact me here to discuss.

*Survey of 414 executives at midsize and large enterprise organizations worldwide
************************************************************************
Kevin Benedict
Writer, Speaker, Editor
Senior Analyst, Digital Transformation, EBA, Center for the Future of Work Cognizant
View my profile on LinkedIn
Learn about mobile strategies at MobileEnterpriseStrategies.com
Follow me on Twitter @krbenedict
Join the Linkedin Group Strategic Enterprise Mobility
Join the Google+ Community Mobile Enterprise Strategies
Recommended Strategy Book Code Halos
Recommended iPad App Code Halos for iPads

***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.

Kevin Benedict's Video Comments: Mobile Development Models

In this segment of "Kevin Benedict's Video Comments" I share the six different models for enterprise mobility apps.  If there are more, please share so I can add them to the list.  These six take different levels of development, different designs and support models.




*************************************************************
Kevin Benedict, Independent Mobile Industry Analyst, Consultant and SAP Mentor Alumnus
Follow me on Twitter @krbenedict
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.

Planning Your Next Mobile Development Project: Best Practices, Hidden Risks

I would like to invite you to join T. L. Neff and me as we present a webinar on the subject of Planning Your Next Mobile Development Project on Thursday, October 20th at 1 PM EDT.  Developing mobile apps brings a new set of challenges and processes that IT teams must be prepared to address.  We’ll focus on the key areas across the software development lifecycle where mobile development differs from traditional IT projects. 

• Learn how to balance project planning and software development processes against today’s constantly changing business and technical requirements for mobile solutions.
• Learn about best practices in defining requirements for mobile apps.
• Avoid the hidden risks in building out and managing the infrastructure to test and deploy mobile apps.

Click here to register!


*************************************************************
Kevin Benedict, Independent Mobile and M2M Industry Analyst, SAP Mentor Volunteer
Follow me on Twitter @krbenedict
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.

Building Compliance Features into Your Enterprise Mobility Solution, Part 1

uboatPeriscope
One of the many challenges that companies have is managing a mobile workforce that is often working on remote and distant jobsites.  Many important parts of the business can be impacted by how the mobile workforce does their job while in these environments.  This article will discuss how mobile enterprise applications, with integrated compliance monitoring and prompting, can help companies manage remote and mobile work forces.

Customer Service in Remote Locations

The experience the customer has with your company is directly determined by how they are treated by the company representative they meet.  Often the onsite worker is the only face to face interaction the customer ever has with a person from your company.  The way the customer is treated and the services that are preformed can make all the difference between a good and bad experience and referral business.  How do you ensure that best practices are being followed in remote worksites?

Jobsite Safety

Jobsites can often be dangerous.  There may be safety issues and safety regulations that must be followed.  There are often specific processes that must be followed to reduce risks and to provide the safest working conditions possible for the workers and other people around the jobsite.

Legal Liabilities

There are many risks that must be considered.  If a jobsite is not properly prepared for safety and an accident happens, the company responsible for the work may be liable.  How do you ensure your workforce follows the appropriate processses, does mandated tasks and documents these steps to reduce risks?  Can a mobile device be used?

Best Practices

It is often the case that companies train their employees to do what is considered best practices within their company and industry.  These best practices can be at the core of a company’s competitive advantage.  How does a manager ensure that best practices are being followed on remote jobsites where there is no onsite supervision?  Best practices might be the difference between running an profitable operation and an unprofitable operation.

Read Part 2 of this article.



***************************************************
Kevin Benedict, Independent Mobile and M2M Industry Analyst, SAP Mentor Volunteer
Phone +1 208-991-4410
Follow me on Twitter @krbenedict
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 to Acquire Sybase, Day 3 - Kevin Benedict's Thoughts and Analysis

There have been several additional comments made in the past 24 hours that seem to shed light on the thinking behind SAP's intent to acquire Sybase.  These statements seem to be highlighting three specific themes:
  1. A shift from desktop to mobile devices
  2. A goal to connect with billions of mobile users
  3. Support for all leading mobile devices
In a comment yesterday on the Linkedin group SAP Enterprise Mobility (you should all join), Sam Lakkundi, Sybase's Chief Architect said, "Moving from the Desktop Computer to a Mobile Device is the new path for enterprise computing that I vision."  In an email exchange between myself and Bonnie Rothenstein, Head of SAP's Enterprise Mobility Communications, Bonnie said, “We’re excited about our intent to acquire Sybase, as we believe the acquisition will enable SAP to accelerate our plans to deliver SAP’s industry leading business applications and analytics offerings to billions of mobile users on any device.” 

Add these highlighted statements to SAP's co-CEO Bill McDermott's, "We see a huge emerging market for the real-time, unwired enterprise," and SAP co-CEO Jim Hagemann Snabe's, "We want to make sure that SAP solutions can be accessed from all leading mobile devices."

I see the fog beginning to rise.  The Sybase acquisition can ensure that a standardized way of integrating mobile devices and mobile enterprise applications with SAP systems is defined and available through Sybase's mobile middleware and integration tools.  I spoke to an unnamed source in SAP who confirmed this statement with two taps on the table.  This same source said there will always be choices in how to integrate, but there will be a defined SAP way for mobile software providers to integrate.  SAP must have read my blogs.

I read and interpret that SAP believes mobility, mobile device support, and integration with mobile applications is too important to leave totally up to the discretion of partners.  SAP wants to bring order to the chaos and define a path, methodology, and strategy for their partners.

On the question of where SAP's current mobility partners fit into this new world order, SAP's Rothenstein provided this statement, "SAP’s intent to acquire Sybase will expand opportunities for our joint ecosystems and we believe our software and implementation partners can capture new opportunities by innovating on Sybase’s open and market leading mobile platform."

The SAP statement above seems clear.  Mobile software companies that develop "rich or thick mobile clients" in the SAP ecosystem will want to seriously consider embedding Sybase's mobile middleware, synchronization, integration, and device management technology in their future mobile software upgrades to better align with SAP's future direction.

I have had a chance to talk to a number of SAP's mobility partners in the last few hours who, after they digested the announcement, seem to have embraced it.  To summarize (as I will blog more on this soon), they see incorporating relevant pieces of Sybase mobile middleware into their solutions, but continuing to see themselves as the subject matter experts on complex, tactical, and industry specific mobile applications.

One last thought for today (as my irrigation system needs to be activated before I leave for Sapphire) is that SAP seems to really be emphasizing the "support for all mobile devices" theme.  This is very different than last year when there was a specific emphasis on RIM products.

***************************************************
Kevin Benedict SAP Mentor, SAP Top Contributor,CEO Netcentric Strategies LLC
Mobile Industry Analyst, Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy Consultant and Web 2.0 Marketing Services
http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
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: Leapfactor's Lionel Carrasco

I was in Miami, Florida a few weeks ago and was able to meet up with Lionel Carrasco and do some sailing. Lionel Carrasco is the CEO and founder of Leapfactor, an Enterprise mobility player and partner of SAP. Lionel shared his thoughts and insights while the sun was setting over Miami.

I asked Lionel how he originally got into the mobility industry. He explained that he managed the development, as an SAP systems integrator CTO, of a number of large enterprise mobility projects in the Direct Store Delivery, Logistics Execution, and Sales Force Automation space. These projects were in the USA, Latin America, and Europe. In the course of designing, developing, deploying and supporting these applications, he learned much. He believes this experience will be invaluable to SAP and Leapfactor customers.

I asked Lionel how he would describe Leapfactor. He answered that Leapfactor understands that cloud computing and mobility should come together. This joining together will enable large enterprises to take advantage of mobility in ways similar to consumers. He believes enterprises should mobilize employees, partners, and consumers. He believes enterprises should consider mobilizing their entire ecosystem as there is value to be recognized in all areas of it.

What differentiates Leapfactor from other SAP mobility partners? Lionel answered that Leapfactor is a native cloud based mobile offering that can handle a large scale volume of users, even in on premises implementation models. They do their best to remove the complexity from a mobile enterprise, yet they offer the required enterprise class security and compliance capabilities. He added that Leapfactor does not think from the "inside out." “Looking from the inside out,” according to Lionel, “Makes you think like an ERP running on a desktop computer and simply extending features outside the four walls which limits you.”

"We are thinking of not just one mobile application but hundreds!" Lionel emphasized. "Developers can build them, customers can build them, our partners can build them, and we can build them on behalf of our customers as well."

Lionel emphasized again and again that the economics of mobile applications, the way they are developed, deployed and supported is completely different now than they were even a few months back. I interpreted that to mean not many mobility vendors have recognized or accepted the new paradigms and realities yet. He believes the new business models that Leapfactor is bringing to the SAP marketplace are significant, not only for customers but SAP and the partners ecosystem.

I asked Lionel about his target audiences. His answer was end users, end users, and end users. He believes that end users need to realize value with the very first click of a mobile application, and the enterprise should receive their value second. It is a view that suggests the end users are the secret to an enterprise's success. If the end user likes the mobile application, then the enterprise will realize the value.

Lionel said that Leapfactor is here to create value for the business. The winners will be those enterprises that create apps for the edges of the processes because the core is already taken care of and automated by ERPs. The edges are where the enterprise relates to customers and partners and where the opportunities for mobility lie. He then added that it is also very important to make the IT department the heroes, because they will be able to respond to business demands faster instead of managing the complexity and maintenance budgets.

I asked about Leapfactor's mobile applications. He listed them as follows: 
  • Business Indicators - Mobilized business intelligence for all types of users from the executives down to blue collar workers.
  • Mobile Alerts - When action and acknowledge is required and email is not enough.
  • Mobile Approvals - For any system and process that requires an approval. 
He then shared that one of the most interesting new mobile applications would be released in time for Sapphire. It is a mobile social intelligence application for large enterprises.

I asked Lionel if he viewed Leapfactor as a development platform. He answered that it is a mobile deployment platform that can rapidly scale up and scale down depending on the customer's and software developer's needs. “We added some development accelerators and user interface libraries to increase productivity and reduce complexity for developers, but that does not make us a development platform. We rely on the native development tools of each mobile OS,” he said.

It is a deployment platform that mobile application developers can use to deploy the applications they have developed without the need to build a complete and expensive SaaS infrastructure themselves.

One of the most interesting thoughts that Lionel shared was this, "Applications and lines of code are increasingly disposable. The code is less and less important since mobile applications can be developed quickly and with relatively little investment." Hmmm . . . where is the value then? Lionel believes the value will be in the ability to economically and quickly deploy and support mobile applications – applications that offer immediate value to the end users and that are easily distributed. I think he was only half joking but he said, "Mobile applications can be easily thrown away as newer and better mobile applications are developed." It seems to be the personification of agile.

Lionel sees one of the key roles of Leapfactor is to help other mobile software developers manage deployments, compliance issues, and testing and then supporting their operational environments through the Leapfactor platform.

One of the key values in the Leapfactor platform is its ability to meter and measure the use of mobile applications. This information can be used for any number of emerging business models that may include charging the user based on transaction numbers, volume of data used, etc.

I asked Lionel for his opinion on the role of mobile micro-apps. He said mobile micro-apps are easy to maintain, easy to deploy, and easy to develop. This means developers can rapidly bring value and incremental improvements to users. He added that sharing the consumer approach to mobile applications with large enterprises also offers a lot of value.

Lionel refers to "thick client" mobile applications as "obese" mobile applications. He said it is wrong to include too many features in one code base for mobile devices. Obese applications are nightmares to maintain and take far too long to develop, test and deliver. He added, "Developers need to stop thinking like Windows Desktop application developers and change their paradigms to think like a mobile user."

In my past I have been involved in many "obese" mobile application development projects. I can share that the customer requirements always seemed to change faster than you could design, develop, test, and deploy them.

I asked Lionel for his opinions on MEAPs (mobile enterprise application platforms). He said there is still a need for MEAPs on some projects, but the development is very expensive. He believes MEAPs were mostly designed for older development paradigms, and they need to change to support a more consumer-oriented approach for enterprises of today.

I asked Lionel to look into the future and tell me what he sees. He offered that mobility is already pervasive. He said most less-developed nations have more mobile phones than landlines. He believes that soon all mobile phones will be smartphones.

He also believes that enterprises will begin building management functionality that enables a separation between work and play on the same mobile phone. Perhaps it is a work phone until 5:00 p.m. and then switches to personal settings with personal applications. I find this whole area of thinking very interesting.

What is SAP doing right? Lionel said SAP is focused on mobility in 2010, which is a very good thing. They are demonstrating that they believe it is important, and although they have been slow to embrace mobility and cloud computing, they seem to be picking up speed. They are rallying the SAP troops and the customer base which is all good. Lionel added, “I have had the chance to meet Kevin Nix, who now leads the SAP mobile strategy, and it was refreshing to hear his fresh ideas and real world experiences.”

Lionel believes that SAP's partner strategy for mobile applications is the right strategy. "They realize they cannot do it all and have invited partners to fill the gaps" he added. "Past failures that SAP experienced in mobility were due to SAP following old paradigms."

What can we expect from Leapfactor in 2010? Lionel provided the following list:
  • Leapfactor will show the industry and customers more proof points that Leapfactor's model and technology is the right approach. It will be disruptive to current thinking, but it is the right approach.
  • Leapfactor will deliver more killer apps, but more importantly, customers and partners will do the same.
  • Leapfactor will be adding many customers, small and extra large ones.
  • Leapfactor will publicly release a Developer Kit that has been limited to date to only a few partners.
  • Additional RIM and Android apps will be released this year.
If there is a mobile expert that you think I should interview please contact me!

Read more interviews with mobile experts:
***************************************************
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. ***************************************************

Mobile SAP Apps for Sales Order Capture and Delivery

Banks Holdings Limited (BHL), a SAP customer, is one of Barbados' most successful public companies and the island's largest beverage conglomerate.  BHL has four subsidiaries comprising of two beverage manufacturers, a dairy processing plant and a distribution firm.

BHL has recently mobilized three key SAP business processes:

  1. Pre-Selling - The Pre-Selling scenario enabled the capture and confirmation of new orders by the mobile salesforce as they interacted with the end customers, giving them visibility into their individual orders and pricing structures.  By delivering SAP pricing schemas to the mobile device, BHL's sales representatives now have the ability to highlight to customers any volume scale based price breaks and a potential for cross selling opportunities.
  2. Dispatch - Dispatch is responsible for managing the inventory required to fulfill the orders being delivered on a daily basis.  Leveraging the SAP FIFO and guided picking processes, the mobile dispatch process ensures the correct stock is not only loaded into the correct delivery truck but also in the most efficient order for the actual deliveries being fulfilled.
  3. Delivery - The delivery process is responsible for the Proof of Delivery (POD) process to the end customers. The mobile component not only manages core delivery processes, but also allows for any last minute adjustments to a delivery requested by a customer and the corresponding downstream SAP pricing impacts these changes may have.
BHL wanted a solution that could meet the following requirements:

  • The ability to work both online and offline when mobile staff is beyond mobile device coverage boundaries.
  • Support for multiple device types such as Motorola’s hand-held devices and printers.
  • Integration without the need for complex middleware.
  • Flexibility of the GUI interface.
  • In-depth SAP experience.
  • The ability to extend SAP specific business processes to the point of activity (mobile)
  • The ability to utilize existing SAP ABAP skills kept cost of enhancements low as any future changes and enhancements could be performed in-house.
SAP has a number of mobility partners including Sybase, RIM, Sky Technologies, Sylco and Vivido Labs. In this case BHL selected SAP Certified Partner, Sky Technologies for their mobile SAP CRM.

***************************************************
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.
**************************************************

Mobile Expert Interview Series: EntryPoint’s Pete Martin

Pete Martin, the founder of EntryPoint Consulting worked for SAP for over five years. He managed field operations in his region which included sales and pre-sales. His consulting company, which was founded in 2003, resells SAP solutions to US based middle market companies and business units of the Fortune 1000. They focus on SAP CRM, an area where they have a lot of experience. Today mobility is a big issue for his customers.

Pete was involved in one of the first mobile SAP CRM implementations. It did not go well. Why?

  • SAP did not have a well defined interface for CRM at that time. There was about five different ways to interface with it and this caused confusion with all involved.
  • SAP did not have a strong mobility roadmap or good guidance at the time.
  • It was a case of you don't know what you don't know.
  • Broadband internet was not widely available and connection and synchronization speeds were slow.
  • The customer wanted to download huge price books and massive amounts of customer data which bogged down the system.
  • The client wanted to replicate their ERP on the mobile devices – not good.

After this first painful experience, Pete and his team stepped back and studied the mobility space for about three years. However, in 2009 they lost two SAP CRM sales because they did not have a strong mobile SAP CRM offering. This pain motivated them to jump back into researching good mobile solutions for SAP CRM. Pete says that now 100% of SAP CRM sales prospects are requesting mobile extensions. It is no longer an option. A mobilized version of SAP CRM is a requirement.

They looked at a lot of different MEAPs that worked with SAP. There were several things they wanted from a mobility partner:

  1. EntryPoint sells to medium and large companies. They need a solution that can scale from a few dozen users to a few thousand. They needed a partner that could support both of these markets and be priced to work in both.
  2. They looked for a mobile provider that had already successfully implemented mobile SAP CRM solutions at a large company. They wanted to see a full production environment already in place. The partner they chose already had a successful mobile SAP CRM implementation with one of the largest global CPG companies.
  3. They wanted a mobile provider that was not overly complex. They were looking for a simple and elegant architecture that was easy to implement and support.
  4. They wanted to partner with and learn one mobile solution that could be broadly implemented across many different business processes.
  5. They wanted a mobile provider that "partnered" well. Some mobile providers are large and small partners get overlooked. EntryPoint wanted a mobile partner that wanted them.

The end result was that EntryPoint Consulting selected SAP Partner, Sky Technologies as their mobile SAP CRM partner. They are now confident in telling customers they can have a mobilized CRM in 90 days.

Mobility is a big focus for EntryPoint Consulting in 2010. Why?

  • SAP customers are asking for mobile solutions and mobile extensions to their business processes.
  • Sales prospects are all asking for mobile extensions.
  • When EntryPoint Consulting promotes events around mobilizing SAP CRM they get BIG responses.
  • They lost two SAP CRM sales last year because they did not have a good mobile solution provider and plan in place.
  • SAP field sales is asking EntryPoint about their mobile solutions and plans. Pete wants a good answer.

I asked Pete what he thought about SAP's current mobility strategy and he said, "In markets where products and technologies are changing fast, it is hard for SAP to keep up. They are simply too big to be nimble. It is best for them to partner for mobile solutions today." In a follow up statement he added, "SAP's sales teams are still a bit confused by SAP's mobility strategy." It seems there is more to be done to evangelize SAP's mobility strategy and plans internally.

Pete also shared his thoughts on what SAP sales teams could learn from other CRM vendors. He said other vendors had learned how to sell to mid-level, line of business folks successfully. This according to Pete, is where CRM is sold. SAP sales teams are great at the C level sales process, but have historically been troubled when selling to the line of business. "If the VP of Sales can't connect to the CRM with his/her favorite mobile smartphone, the sale is lost," said Pete.

To read additional articles from the Mobile Expert Interview Series see below:

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

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.utilizer.com/
http://mobileenterprisestrategies.blogspot.com/

***Full Disclosure: I am an indpedent 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: Nokia's John Choate

I had the pleasure of interviewing Nokia's John Choate last week. He is working in the Augmented Reality (AR) space for mobile applications at Nokia's office in San Francisco. Isn't that a cool area to focus on? John's title is PMO 2.0. (Program Management Organization), and he works with the hardware and software sides of the Nokia business to bring them together and to define new technologies and solutions.

A funny side note - Nokia's offices are so high in an office building that their phones have a difficult time getting good reception and Nokia employees only use mobile phones. As a result Nokia employees are running around the office trying to find good reception. I must add that any mobile phone at that altitude, at that location, is likely to have the same challenges. It was just a reminder that there is more work to be done and that disconnected mobile smartphone applications are still needed, even in downtown areas. Can you image a field service technician trying to enter his mobile work order on a smartphone application that is dependent on real-time connectivity in that office?

Let's get back to the interview about Augmented Reality with John. Augmented Reality is described as a live direct or indirect view of a physical real-world environment whose elements are augmented by virtual computer-generated imagery or data. Nokia's Point and Find solution is one of those solutions. With Point and Find the user can point the camera phone at an object and snap a picture. The picture combined with GPS coordinates immediately identifies the object and displays information about it.

Point and Find is not just for buildings and landmarks. The user can snap a picture of a movie poster and information about the movie, nearby theaters and run times is presented. In addition, you can snap a photo of a 2D bar code and product information will appear. Nokia also supports video as well as digital photos with Point and Find.

AR is fascinating to me. Different movie posters can bring up different information. The posters are recognized and different data is found. For example, the same poster in London, because it is associated with a GPS coordinate, would bring up different information than the same poster in New York.

Slight graphical differences in a poster or sign could tell the Point and Find application to display different information. Your real-world reality can now be supplemented by historical facts, nearby businesses, crime statistics, favorite restaurants and anything else you can image. This is crazy powerful stuff to ponder.

I wrote an article last year called Network-Centric Field Force Automation on how the military is using similar technologies in their network-centric warfare strategies and how field services could learn from it.

John and his colleagues at Nokia have many amazing ideas on how this can add value to the hospitality, retail and travel industries to list a few. For example, a sports tourist spends five times more than a general tourist. It is a demographic that businesses would like to target. How can this be done using AR...use your imagination.

A Nordstrom shopper could simply snap a photo of a Nordstrom store and information about their favorite products, their locations and prices could pop up in AR. Perhaps the application could alert the Nordstrom attendants that a premium shopper had just arrived.

John used terms like "buying a world" in our discussions. A business could "buy a world" in the Point and Find solution and decide what to put in this AR world. Do they want to load this world with historical facts, crime statistics, tourist locations, hotels and restaurants? The owner of this "world" could add as many layers of information as they desired. They could identify the underground electrical lines, sewage systems, accident statistics, health inspection reports of nearby restaurants, tour packages or simply point to a Starbucks.

I appreciate John opening this AR "world" to us and introducing us to Nokia's Point and Find.

Related article:

Mobile Expert Interview Series - Jane and Keelin Glendon of HotButtons

If you are involved in or interested in SAP related enterprise mobility, then you are invited to join the Linkedin group SAP Enterprise Mobility.

***************************************************
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:

____________________________

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.


Advice for Mobile Start-Ups: Working with SAP, Part 4

SAP can be like a giant aircraft carrier moving powerfully across the ocean. It is huge and heavy and if you are a swimmer in the ocean trying to make it change directions to suite your purposes, good luck. A more successful approach is to understand the direction the ship is going and jump on board. Sign on, offer them a hand and help them get there. Perhaps as you gain their confidence they will let you into the wheelhouse where you can learn about their intended strategies and influence future directions.

Mobile software companies and their entrepreneurs often feel their mobile technology and strategy is better than all others. They often feel driven by a messianic mission to carry their mobile technology message to the world, and then scream in frustration when others don't seem to "get it." I understand. I have screamed.

Mobility entrepreneurs are often focused on their specific mobile technology. Many have engineering backgrounds and believe they have solved a significant problem. The challenge they often face is not understanding the business of their potential partners, resellers and target customers. Let me provide the following scenario to demonstrate my point:

There is a large conference room with a long table. There are 2 mobility entrepreneurs, 12 IT managers for a large SAP customer, 4 sales and pre-sales folks from SAP, and 3 representatives from a large system integrator with a focused SAP practice in attendance. The mobility entrepreneurs stand up and present the "world's best" enterprise mobility technology to the attendees. When they are done presenting, lots of questions are asked; the entrepreneurs cover them all and leave to catch their flight home expecting a PO on the fax machine when they arrive. The PO never arrives. Why?

Here are some possible reasons:

  1. The SAP customer has a $14 million problem, and the mobile technology presented will solve only $675,000 of that problem. They need a complete solution, not a partial.

  2. The $14 million problem requires a full range of systems integration, business process design and SAP customization to fix. They want to fix this problem with one overall integrated solution, not many small solutions linked together. Complexity can kill.

  3. The SAP customer has three preferred SAP systems integrators – none have a practice around this particular mobile technology.

  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?

  5. 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.

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

  7. 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.

  8. 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. Their priorities would be:

    1. SAP solution

    2. SAP price list solution (could be a partner's solution on the price list)

    3. SAP Certified or Innovation Partner

    4. Only in desperate times would a non-partner be recommended and then only if it helped sell more SAP products

  9. SAP pre-sales teams learn about many different technologies, but if it does not help their Account Executive make his/her quarterly numbers, it is unlikely to be introduced to the customer. However, there is an exception; if the solution, combined with an SAP solution helps close more revenue for the SAP Account Executive, then you have a winner.

  10. 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.

  11. Large software companies like SAP often consider potential partners as possible acquisition targets. Issues like are you private or public, customer base size, intellectual property ownership, market presence, etc, play into these considerations. If two partners have similar technologies, the one that is a better future acquisition target may be chosen for strategic reasons.
  12. The SAP customer may have outsourced their IT to a large service provider with their own recommended mobile solution.
  13. The SAP customer may have a large server deal with IBM, and IBM agrees to throw in a software solution for free if the annual support contracts are renewed...it happened to me :-(
  14. 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.
  15. The CIO will never get invited to speak in front of thousands at Sapphire if they choose your solution.
  16. Your user conferences could be held at Denny's.

In summary, a mobile solution needs to be viewed favorably by the SAP customer, SAP sales team and the SAP system integrator. Not always all of them, but most of them. It needs to align with most of their strategic visions, personal interests and compensation structures. The frustrating part of this list for many mobility entrepreneurs is that none of it has to do with "best" mobile technology. These are primarily business issues that relate to alliances, partnerships, self-interests, marketing, strategic directions and business models.

Since we live in the real world, not all of the players' motivations will be clear or have the same level of priority. Sometimes new technologies appear that do not fit these molds, but once you understand these underlying motivations it becomes more clear.

If you are interested in discussing these issues in more detail and/or learning more about my consulting practice please contact me.

Watch for Part 5 in this series - it gives hope back to the Mobile Start-Ups. You can follow-me on Twitter (see right sidebar) and by RSS.

Related Articles:

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

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.
**************************************************

In Remembrance of the PDA


How long has it been since you stopped using the term PDA? It occurred to me the other day that the PDA has played an important part in my career and I should not let it pass away without a ceremony of some sort.

The PDA has been replaced by iEverything and smartphones. However, it was an important gadget that paved the way for the mobile technology advances of today. It opened our minds to the possibilities of keeping on task, even with poor memories. It helped generations of soccer moms remember where each child was dropped off and when they needed to be recovered. It allowed us men to seem organized despite ourselves.

PDAs started the concepts of software applications, music and photos in our pockets. PDAs kicked-off companies like Palm and motivated people like me to begin blogging.
Let us be silent for 30 seconds in rememberance of the PDA. We can quietly bow our heads and reach down into our pockets and try to remember the last place we used our stylus before it disappeared.

***********************************************
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/
***********************************************

Advice to Mobile Start-ups: Working with SAP, Part 1

I was invited to spend time on SAP's rain soaked campus in Palo Alto, California last week and met with people from several different groups to discuss mobile computing, mobile strategies and how mobile start-ups can best partner with SAP. This article reviews some of those discussions.

One of the first points to understand is that SAP LOVES mobility. In December SAP announced that one of their key focuses for 2010 would be mobility. I wrote about SAP's announcement here in December. What this means is SAP is looking for partnerships with mobile software companies that will extend the reach of their core software to more users. Let's talk about what that means.

SAP is one of the largest software companies in the world and traditionally they have focused on selling to the largest global companies. They have been successful in this strategy, but even with their successes, they still have relatively few users in each of their customers' operations. Some estimates have it at about 445 users per customer on average. That may sound like a lot of users, but many of these companies may have tens of thousands of employees.

SAP's strategy now is to look for solutions and partnerships that will expand the value of their core systems to employees within their customers' operations that are not traditionally SAP users. This is a key point for mobile software companies to understand.

If you imagine the glassy surface of a pond and how it looks when a rock is thrown into it. The rock lands with a splash and a series of circles form. The inner circle is the smallest and represents SAP's current users within an enterprise. Each surrounding circle is bigger and covers a wider area and represents more possible users. These are the circles SAP wants to move into and where they want to add value. If you, as a mobile software company, can help them do that, then they are interested.

Let's explore how to expand the circles. What do we need to know?
  1. Who needs access to SAP system data, but is not sitting in a cubicle with SAP access today?
  2. Who collects SAP system data that is not currently a SAP user? They may be collecting data on paper forms today and re-keying the data into SAP at another time.
  3. Who are the mobile employees at a SAP customer? What are their roles and what data do they need to view and collect while on the road?
  4. What supervisors need access to SAP anywhere and at anytime?
  5. What managers need SAP management reports while on the road?
  6. Is there SAP system data that needs to be shared externally with extended multi-enterprise supply chains via mobile devices? You don't want your supply chain partners to view all of your system data, but are there alerts, updates, reports, etc., that should be shared via mobile devices?
  7. Should the logistics department have mobile "proof-of-delivery" applications in the hands of their truck drivers?
  8. Should plant maintenance managers have mobile inspection applications that feed SAP?
  9. Should service technicians be using mobile service tickets that feed SAP or an SAP partner's work order management system?
  10. One SAP customer has over 600 food processing inspectors worldwide. This inspection data needed to be collected and stored centrally. While this may not be a core SAP application, it shows that SAP customers often have a large number of mobile data collection requirements that can be turned into management reports and provided to traveling managers.

All of these applications are adding new users to the SAP family. If you can add new users to the SAP family, then you will have the ear of the entire SAP sales organization.

Part 2 of this series can be found here, Part 3 here and part 4.

If you would like to discuss this subject in more detail please email me here. If you would like to follow my discussions and be alerted to new Mobile Strategies for Businesses' articles, then you can add me to your RSS reader or twitter account @krbenedict.

***********************************************
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/
***********************************************

Advice to Mobile Start-ups: Focus on Mobile Content, Mobile Business Processes, Integration and Workflow

The mobile and wireless industries have changed dramatically in the past year and this has significantly changed the market for mobile application start-ups. Many of the missing application development tools and features that forced programmers to develop their own proprietary mobile middleware, have been filled by the mobile OS (operating system) developers over the past 12 months. This is both good and bad news for mobile start-ups.

The good news is that mobile application developers can focus more on providing business value, rather than coding clever mobile client and mobile middleware features. This is good for the entrepreneurs that have started with an existing back-office business application in mind and simply wants to support it with a mobile client.

The bad news is that many mobile application companies have already invested heavily into their own mobile client technology, mobile application development tools and mobile middleware platforms. Why is this bad? Because most enterprise buyers won't appreciate the investment.

Enterprise buyers own smartphones. They download mobile applications over the weekend for $1.99. Their expectations have changed. In the past, mobile applications were a novelty surrounded by mystery and complexity. Mystery and complexity made it easy to charge $500 or more per mobile user. Now mobile applications are only a finger stroke and a password a way on their favorite mobile app store.

The mobile application itself is not where the biggest value can be found. The biggest value is in the following:
  • Mobile client integration with enterprise business applications and data
  • Support for enterprise business processes
  • Support for ERP (enterprise resource planning) workflows
  • Support for ERP data requirements
  • Integration with high value data sources (web services)
  • Support for complex and niche business processes
  • Support for high value data collection hardware (survey equipment, RFID, Barcode, GPS etc.)

The value of mobile business applications, no matter what the original investment was, will be attributed to the above capabilities not the mobile client itself. ROIs need to be achieved by supporting core business functions in mobile environments. It is the efficient support for a business process, not the mobile client where the real value can be found.

As a mobile software vendor, having the best of breed enterprise mobile applications will not be good enough. Companies will continually seek to simplify their IT environments and reduce the number of applications they are required to support. They will look to find mobile solutions that are hosted in a SaaS (software as a service) business model in a cloud computing environment, and that are most closely aligned with their primary ERP or key business software solution either through ownership, endorsement or partnership.

Early adopters will experiment with best of breed and leading edge technologies, but the masses want simplicity and security.

Do you agree? I look forward to your thoughts and comments.

***********************************************
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/
***********************************************

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

Analysis - SAP's Emerging Mobility Strategy - Fasten Your Seat Belts!


SAP has announced this week that one of their strategic focuses for the next 5 years is mobile computing and mobile software applications according to SAP chief technology officer Vishal Sikka said. The pervasiveness of mobile computing and social networking also have SAP developing applications and extensions, which will allow wireless users to collaborate and utilize SAP and non-SAP related data for on the fly computing.
I write wireless industry analyst reports and provide consulting on mobile strategies so have been keeping a careful eye on this market. It is moving at warp speed now! After many years of mostly small software companies in the mobile enterprise software applications market, the big kahunas are jumping in with both feet and this will change the industry. Read a few of these article titles:

A quick glance at the above articles shows you that the biggest technology companies in the world are now taking mobility seriously and the M&A activities are heating up. Mobile Epiphany is not a large company, but its parent is well funded and sets a higher standard for other start-ups than was faced in the past.

SAP is planning to compete against Salesforce.com in 2010. Salesforce.com has a popular mobile application and SAP will be required to launch one as well to successfully compete. This is an example of what entrepreneurs should be looking for now. Opportunities to help the ERP vendors meet their 5 year plans with add-on mobile solutions that extend their business processes to the mobile workforce.

My analysis - mobile start-ups cannot simply have a good idea now days. They must do a thorough investigation into the plans of the wireless carriers, mobile device manufacturers, mobile operating system developers and ERP vendors to understand the solution gaps and market place ambitions before launching another mobile application. The enterprise mobile applications market has just been promoted to the big league.

The growth strategies for mobile start-ups these days in the enterprise mobile applications space should involve working closely with the wireless carriers, mobile device manufacturers, ERP vendors and mobile operating system developers. Mobile start-ups are going to need to get in the game quickly or be left behind.

"Sixty to seventy percent of the population have mobile devices" said Don Bulmer SAP VP industry relations, adding that mobile gear is the preferred communications and computing platform. "There are lots of opportunities for SAP," he said.

SAP users want to be able to use social networking sites such as Facebook to collaborate, said SAP executive board member Jim Hagemann Snabe. "Companies want to take advantage of these technologies without disrupting business," he said. Much of SAP's innovation focus will revolve around flexible extensions to core applications and processes, which can be developed and deployed quickly, via an on-demand or on-premise model, said Hegemann Snabe.

Mobile start-ups - Did you catch the model proposed by SAP? They want innovations (think mobile) that are flexible extensions to their core applications and processes that are available to customers in an on-demand model (SaaS).

Social networking is responsible for much of the huge growth in mobile data usage these days. Adding social networking to the enterprise market promises many opportunities for mobile applications companies as SAP has described. If the enterprise adopts mobile solutions with a social networking emphasis, you will quickly see the wireless carriers plunge into this market as well. Keep your eyes open!

I look forward to your thoughts and comments.

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

Mobile Field Services, Cross-Selling and Enterprise 2.0

Selling more service contracts, warranties and appliances were three reasons Sears gave for mobilizing their field service technicians in this recent article. Cross-selling is also a key to successful field services organizations according to Gartner's Magic Quadrant for Field Service Management ( May 2009). Isn't it interesting how important onsite sales are for organizations that provide services?

It seems that in these days of internet e-commerce, people still like to look into the eyes and talk to a real person. If that person just happened to fix your satellite TV hours before your football game, you are very happy with them. You are willing to listen to them as they make recommendations and referrals.

If you are a software developer of mobile applications for Field Services Automation (FSA) you are going to have to take the notion of "sales" seriously in your application. Gartner states that leading FSA companies will need to include CRM components in their field services applications. This may include integrations with mobile sales force automation tools or SaaS providers, product catalogs, inventory levels, shipment tracking, etc.

Location based services may also have a role here as discussed in this article on mobile sales applications and LBS.

Let's continue this thought process and integrate cross-selling, Enterprise 2.0 and mobile applications. In this article on Enterprise 2.0 and Mobile Software Applications, the idea of a Facebook like application for businesses is explored. The ability to have an enterprise collaboration and communication tool that utilizes many of the concepts of social networking. If a key contributor to the success of a field services company is selling products and services while onsite with a customer, then what would happen if the service technician expanded his product line with those of key collaborating business partners?

Let's think through a scenario:
  1. Plumber Edward fixes a leak for Mrs. Jones
  2. Plumber Edward sees the tile floor on the bathroom needs repaired
  3. Plumber Edward is connected to a tile installer via an online Enterprise 2.0 website
  4. Plumber Edward refers the tile installer and uses the Enterprise 2.0 website or the iPhone version of it to notify the tile installer
  5. The tile installer receives the referral via the Enterprise 2.0 service on his Blackberry and wins the business.
  6. The tile installer notices that the floor needs repaired and refers a carpenter via the Enterprise 2.0 website.

You get the picture. A group of linked and collaborating businesses cross-sell each other's products and services via a mobile Enterprise 2.0 service. Each of these collaborating businesses have eyes, ears and faces in the marketplace seeking to find business for the other members. This is business collaboration with big benefits!

I can image a time when there is a monetary value placed on each level of referral. Direct referrals are worth more than a 2nd level referral. Members could participate in different collaboration groups depending on the market dynamics.

Sears said that the onsite service technician, standing face-to-face with the customer, had the best opportunity to sell products and services. They invested in equipping their mobile service technician with more wireless mobile software applications to assist in closing more sales. They reported it was successful.

I would like to hear your thoughts and comments.

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

Interviews with Kevin Benedict