Showing posts with label mobile micro-applications. Show all posts
Showing posts with label mobile micro-applications. Show all posts

Thoughts on SAP Mobility - Reporting from Sapphire

I have learned a huge amount at Sapphire 2010.  I have spoken to, and filmed interviews with, just about every mobility vendor at Sapphire.  Here are the first few:
Tuesday night thoughts

I believe the saying, “content is king!” Although I would add that “content and business processes are king!” Applications that add unique functionality and value to the SAP ecosystem will have longevity. Companies that are only providing interesting views of existing SAP data are subject to being quickly replaced by the next teenager with a cooler UI. 

Mobile applications developers must add deep value to be able to gain mindshare and then defend their positions in the longterm.  They need to demonstrate unique innovation, deep expertise, and extend value in manners that are defensible.

The term "mash-up" is used often at Sapphire to refer to aggregating data from multiple sources.  This is a very interesting concept.  Pulling data from many different sources to add unique value on mobile applications that are geospatially aware.  This is interesting.

I have seen some absolutely fantastic mobile applications at Sapphire that help companies make collaborative decisions and harvest enterprise's institutional knowledge. These are mobile knowledge and decision management applications.  This is a very interesting area to me.  It is new value.  Not mobilized versions of existing SAP systems.

I have heard and witnessed a lot of chest thumping at Sapphire.  The bottom line is how many SAP customers does a vendor have in production. 

Mobile micro-applications are being labeled as "instant value" applications at Sapphire.  I like this description.  It is good marketing.

Inspections, assessments, asset management and field services are still very interesting areas as there is yet a lot of new value that can be created and provided on mobile devices.

Sybase is not known for their mobile applications.  They are a great mobile middleware company.  It will be interesting to see if they can compete with the incredibile mobile applications that I have witnessed here at Sapphire from ecosystem partners.

There is a persistent rumor that HP may try to outbid SAP for Sybase.  Crazy times!

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

Sapphire 2010 Here We Come - The Year of Enterprise Mobility

I must admit it is a self-proclaimed year of mobility, but I believe it is appropriate.  I think enterprise mobility will be front and center everywhere you go at Sapphire next week.  There are many new and innovative mobile micro-applications that were launched last week by SAP partners.
SAP appointed me to be an SAP Mentor this year focused on enterprise mobility.  If any of you will be at Sapphire and would like to meet with me please contact me.

***************************************************
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
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: Syclo's Jeff Kleban

I was able to track down Jeff Kleban EVP and co-founder of Syclo for a good talk this morning. He was kind enough to share his perspective on the world of enterprise mobility and the SAP ecosystem.

To start, Jeff carries a BlackBerry 9700 series, and his favorite mobile application on it is Google Maps. He has been with Syclo from the beginning when there were only four people. Today, Syclo has over 135 employees.

Syclo is one of three co-innovation partners of SAP in the world of enterprise mobility. The three are RIM, Sybase, and Syclo. SAP co-innovation partners share sales revenue, development efforts and product roadmaps with SAP. I wonder if the co-innovation partnership increases the prices of their solutions? I also wonder if having SAP define the roadmap will allow the co-innovation partners to innovate fast enough to keep up with the markets fast changing technologies?

Jeff shared that SAP has designated some mobility applications and business processes as strategic. The strategic ones he identified are:

1. CRM sales force automation [Sybase is the co-innovation partner for this category]
2. CRM field services/enterprise asset management [Syclo is the co-innovation partner for this category]

RIM is also a co-innovation partner, but I am not sure what it covers these days. I have always wondered how an ERP vendor could cozy up to a particular mobile device manufacturer? The next greatest mobile device is always just a press release away so how can you predict which vendor to bet on? Also, who wants to bet against Apple?

I asked Jeff who Syclo's biggest competitor is, and he said it varied since there are so many point solutions in the market but if a customer was looking for a MEAP that they tended to look at Syclo and Sybase who are the leaders. Interesting! OK, SAP's two co-innovation partners for mobility are each other's biggest competitors. That ought to make for some interesting business development and partner meetings. I can imagine the demarcation line between Sybase and Syclo's territories are being battled over daily in Waldorf.

Jeff reported that Sybase uses SAP's NetWeaver Mobile as their integration platform. Syclo, on the other hand, has its own integration technologies which pre-dated the co-innovation partnership. They are using these while they collaborate with SAP to leverage additional integration points.

A question that came to mind following my discussions with Jeff was how does SAP determine which vendor to recommend to a customer needing both mobile SFA and mobile FSA? In many cases CRMs encompass both categories. Does SAP really recommend that a customer select two separate mobility vendors to support one SAP CRM? I hope someone from SAP comments on this.

I asked, "Outside of the categories of mobile CRM SFA (sales force automation) and CRM FSA (field service automation), who should an SAP customer use for custom mobile applications?" "Syclo of course!" Jeff answered but then added, "There is still a lot of room for innovation and other SAP EcoHub partners in this mobility space." So outside of SFA and FSA the market is wide open for the rest of SAP's mobility partners. The challenge, of course, is getting mindshare. If Sybase and Syclo are being promoted in certain specific categories, then how does the best of breed from the rest of SAP's mobility partners capture a category and gain recognition and exposure?

I asked Jeff about Syclo's target markets and he answered, "Complex and strategic mobile applications for SAP users." He then explained that they like the big mobility projects with hundreds and thousands of users but will also entertain smaller mobility projects if there is a future potential for more mobile enterprise applications with the customer. "We like projects with hard ROIs (returns on investment)," he explained.

Jeff said that the enterprise mobile software market is still very fragmented, and no one really has a sizable market share. SAP reports around 90,000 customers, and Syclo has around 750 mobility customers but not all are SAP shops. The bottom line is there are a lot of opportunities available for mobility vendors in the SAP ecosystem.

Jeff added that in the mobile operating system market, there is increased fragmentation rather than decreased. It seems there is a lot of new innovation happening in the world of mobile operating systems.

I asked Jeff what he expects to see happen in the next few years in enterprise mobility. He said, "TCO (total cost of ownership) will drop dramatically as mobile application development tools become easier and MEAPs (mobile enterprise application platforms) more mature. He already believes Syclo has a low TCO but believes there is much more that can be done. He then added that it will be very interesting to watch how companies manage important data on their employees' smartphones. He said perhaps companies will have "sandbox" locations on their employees' personal smartphones. These sandbox locations would be reserved for confidential company data and controlled and managed by the company. Interesting indeed!

I asked Jeff about the term MEAP. He said, "It is Gartner's term, and they defined the meaning." He then pointed out that Syclo is in the Leaders section of the Gartner Magic Quadrant for MEAPs. He believes a MEAP should be able to support many different kinds of mobile enterprise applications, include an SDK and be able to integrate with many different back-end ERPs, business applications and databases.

I asked Jeff for his opinion on mobile micro-applications. He said, "There is a lot of room for innovation! They have their role. Especially with consumers and reaching out to mobile employees." He added, "Companies are seeking mobile applications for a variety of reasons including branding and establishing a closer relationship with their customer base." Again, there is much room for innovation here!

Where does Jeff see the hottest markets for Syclo?

• Field services
• Utilities
• Oil and gas companies
• Oil and gas supply chains
• Life science companies that have FDA compliance requirements
• Government

Jeff said government has a couple of things going for it now:

1. Government economic stimulus money
2. Government's support for, and desire to use, technology to make things more efficient.

What business processes are they targeting?

• Work order/service tickets
• Plant maintenance
• Enterprise asset management
• Social workers/Case managers (and similar roles in other areas)
• Police incident reporting
• Replacing any paper-based processes used in the field

I asked what were some of the most interesting developments in mobility in the past 24 months for him. He said, "Apple iPhones, Apple iTunes and the explosion of smartphones used by consumers." He added that these developments have totally changed the game and has had a major impact on the enterprise. "IT cannot ignore the pressures to mobilize now," he said. In addition, he pointed out that it is surprising there has not seen more consolidation. Rather, there are even more new players and mobile operating systems entering the market today."

I asked Jeff what he thought about SAP's mobile strategy. He said, "SAP must own the roadmap for the most critical mobile applications and business processes." He likes their strategy.

What differentiates Syclo from other SAP mobility partners? Jeff answered:

• Lower TCO (total cost of ownership)
• Pre-packaged mobile applications are relatively inexpensive
• Co-innovation with SAP
• Syclo shares revenue with SAP
• SAP sales teams are incented to promote Syclo
• Syclo has an model-driven development approach which enables mobile applications to be developed without programming.
• IBM resells Syclo solutions
• Syclo integrates with Oracle
• Accenture and CSC are systems integrator partners (there must be a lot of money on the table for these SI companies to be involved).

What are some of the most interesting mobile applications that Syclo has developed? "We partnered with Motorola and IBM to help the Red Cross manage their supplies and logistics after hurricane Katrina," Jeff answered. "Twenty of our staff worked together to develop the mobile application in 14 days."

Thank you Jeff for sharing your insights as a Mobile Expert!

For more articles in this series please see:

Mobile Expert Interview Series: Leapfactor's Lionel Carrasco
Mobile Expert Interview Series: Sky Technologies' Neil McHugh
Mobile Expert Interview Series: ClickSoftware's Gil Bouhnick
Mobile Expert Interview Series: Vivido Labs' Greg Tomb
Mobile Expert Interview Series: Sky Technologies' Troy O'Connor
Mobile Expert Interview Series: EntryPoint’s Pete Martin
Mobile Expert Interview Series: PriceWaterhouseCoopers' Ahmed El Adl, PhD
Mobile Expert Interview Series: Nokia's John Choate
Mobile Expert Interview Series: HotButtons' Jane and Keelin Glendon
***************************************************
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
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: Troy O'Connor

I had the opportunity to interview Troy O'Connor recently while he was in Australia.  He is the CEO of Sky Technologies, an SAP Partner, and an expert in SAP mobility.  Sky Technologies is a software company, and their mobile solution for SAP is the SkyMobile Framework.

Troy first got into mobility as a systems integrator for SAP.  He cut his teeth on mobile applications for warehouse and inventory management over a decade ago.  SAP developed a lot of barcode data collection applications using rugged handheld computers like the LXE.

I asked Troy about his thoughts on mobile micro-applications and MEAPs (mobile enterprise application platforms).  He said that mobile micro-applications are very useful, especially for simple forms-based mobile applications, but he would advocate that mobile micro-applications should be developed using a MEAP and supported by a MEAP.  That way there is a standard way of developing, integrating and supporting them.  MEAPs should provide a rapid and agile development environment for both thick client applications and mobile micro-applications.

I then asked Troy for his thoughts on the role of thick mobile clients and thin mobile clients.  He responded that thick mobile clients are less important when there is 100% connectivity, but there are many cases where rugged working environments do not have connectivity.  In such places being able to operate in a connected or disconnected mode is important.  He added that he prefers the term "Intelligent Mobile Client" over the term thick client.  Intelligent Mobile clients typically have more computing power, on device databases, document management, and data collection capabilities that thin clients.

"What about MEAPs?" I asked.  He listed the core features he felt a MEAP should have:
  1. SDK to provide tools for rapid and agile mobile application development.
  2. Interface management to protect the integrity of the SAP transaction and ensure it happens and is completed in SAP.
  3. Data modeling, data profiling and data synchronization.
  4. Device management, which is important so errors and support issues can be discovered and resolved quickly.
I followed up by asking, "How do you tell the difference between a good and bad MEAP?"  He answered:
  1. The MEAP must be very flexible, because SAP is very flexible.  The SAP user must be able to rapidly customize their mobile applications to match any customization they do in SAP.
  2. The MEAP must support both pre-developed (canned) mobile applications and custom mobile applications.
  3. 100% of Sky Technologies' customers have requested some level of customization.  That is why the MEAP must support this capability.
  4. SAP is a transactional management system, and because of that any mobile applications integrated with SAP must also be compliant as a transactional management system and provide complete end-to-end visibility to these transactions.
  5. SAP interface management is critical.  SAP must have visibility into mobile transactions and be able to monitor them from inside of SAP.
  6. SAP scales up to tens of thousands of users.  The mobile enterprise application platform must also scale up.
I asked Troy about Sky Technologies' strategy of using an SAP "Innerware" architecture for their MEAP.  He responded that Sky Technologies was given a namespace inside of SAP by SAP to integrate their SkyMobile MEAP.  It was then certified by SAP and enables SAP to have complete transactional visibility to mobile transactions.  The "innerware" strategy also enables them to utilize and maximize SAP's integration technologies including SAP NetWeaver.  Many other mobile software companies choose to duplicate SAP functionality in external third party middleware which adds unnecessary layers of complexity.

I learned a new term from Troy - "short pants."  This term refers to youngsters or pretenders, those that lack a complete understanding of an environment.  He used that term to refer to mobile software companies that do not have deep knowledge and experience working with SAP.  I have now added that term to my vocabulary.

When asked his opinion on SAP's current mobility strategy, Troy answered that he agrees with SAP's partnership strategy for delivering mobile applications.  He said the market and technology is moving too quickly for a large software company to keep up.  They need to support the innovation that can come out of their smaller mobility partners.

In response to the question, "What should SAP do differently?"  He answered, "Clarify the licensing strategy and price for mobile applications."  He shared that some of his SAP customers had run into confusing licensing issues around mobile devices for SAP, and this caused some grief.

The last question I asked was, "What should an SAP customer ask a mobile application vendor before purchasing?"  Troy answered, "Where is the master system?  Is it SAP or a third party database or middleware application?"

Related Articles:

Mobile Expert Interview Series: PriceWaterhouseCoopers' Ahmed El Adl, PhD
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.
**************************************************

Mobile Micro-Applications vs Thick Mobile Clients

As I have shared before, my background was in the MEAP (mobile enterprise application platform) world.  We used different acronyms, some not repeatable in this family friendly blog, but it was the same thing as today's MEAPs.  I have managed development projects where the mobile applications we delivered could be considered a full ERP in many places.  It was painful and expensive, but it worked.  Our customers had hundreds of route sales, service technicians, and delivery folks walking around carrying full functional ERPs on their ruggedized mobile handheld computers.

The application I am referring to above consisted of the following:
  • Mobile sales force automation application
  • Mobile order entry application
  • Mobile invoicing
  • Mobile proof-of-delivery application
  • Mobile work order management application
  • Mobile inventory management system
  • Mobile price and promotion management application
  • Mobile enterprise asset management application
  • Mobile CRM to access customer service and support issues
MEAPs and thick client mobile applications certainly have their place, but there was so much customization that this finished mobile application was probably out-dated by the time we delivered it.  If any part of our mobile application needed changed, the entire mobile application had to be updated and re-tested.  With a mobile application that big and complex, the opportunities for bugs were endless.  We had to charge a fortune to deliver it.

Our customer wanted a thick mobile client application that could work in a connected and disconnected mode so that their employees could work whether there was connectivity with the internet or not.  Three years ago there were not a lot of options.  As a result there were a lot of thick mobile clients delivered.

With this particulary mobile application, the training requirements were huge.  The mobile workforce needed to understand every aspect of their mobile ERP before it could be effectively used.  You can image the level of IT support for the first six months.

It will be interesting to see how thick clients and MEAPs evolve.  There are some very active debates on the SAP Enterprise Mobility group on LinkedIn on this subject.

Where do MEAPs stop and mobile micro-applications start?  If I were to develop that same mobile application today, would I use nine mobile micro-applications rather than try to build all of the features and functionality into one giant mobile application?  Good question! 

SAP's partners are on both sides of this question. SAP partners like Vivido Labs and Leapfactor focus mostly on mobile micro-applications.  Sybase and Syclo focus mostly on thick mobile clients, while Sky Technologies seems to be hedging their bets with both thick mobile clients and mobile micro-apps.

It will be an interesting evolution to watch!

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

Simple Mobile Applications Can Offer Real ROIs

The International Telecommunication Union reported in 2009 that 28% of people in Africa have mobile phones but only 5% have the internet.  The report also said that mobile phone subscriptions in Africa were increasing by 50% per year.  As a result of this rapid growth, mobile application developers have been creating simple mobile applications for African businesses that utilize SMS rather than mobile smart phones with data plans.  There are some lessons to be learned.

In a recent CNN article entitled, "Mobile App Developers Tackle Africa's Biggest Problems," the author writes about developers creating powerful and beneficial mobile applications that work with simple and limited 140 character text message inputs.  One example was a mobile application that enables dairy farmers to request the average price of a unit of milk in certain areas.  The text message queries a database that returns an answer.  This may seem to be a very simplistic application, but it means a huge amount to the dairy farmer.  Without access to information on the local market prices for milk, the dairy farmer can be convinced, out of ignorance, to sell his/her product for less that the market price.  Armed with knowledge, the dairy farmer can negotiate for a fair price.

Another example given was a mobile wireless fish sensor in a lake that alerts local fisherman via text messages of the presence of fish.  For the local fisherman whose income depends on being a successful fisherman, this could be a very useful mobile application.

The lesson I learned from these examples is to not undervalue the usefulness of simple mobile applications.  My background is in the MEAP space where we developed thick client mobile applications that were mini-ERPs on ruggedized Windows Mobile devices.  Our MEAPs and mobile applications required large and expensive development efforts.  They were certainly useful and appreciated by our clients, but it does not always require that level of development to provide real value.

Some segments of the mobile workforce could benefit from simple updates, key data provided at the right time, and the ability to query on key data and incremental efficiency improvements.  Mobile micro-applications definitely have their place.

In the SAP ecosystem you are starting to see an increasing number of mobile micro-applications from SAP partners like Vivido Labs, Leapfactor, Sky Technologies.  These applications are designed to replace specific paper processes and enable the mobile workforce to accomplish more while traveling.  I have been given some previews and I believe that Sapphire 2010 will be remembered as the Year of Mobility in the SAP ecosystem.

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

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

Interviews with Kevin Benedict