I don't think you can compare HP's $99 TouchPads with RIM's $199  PlayBooks. The former was a fire sale by a company exiting the  (non-Windows) tablet business. RIM, on the other hand, is showing its  firm resolve to stay in the tablet game.

I once proposed that a formula for determining user satisfaction for a tablet would look something like this:

(Hardware Sexiness + User Interface + Apps) / (Upfront Price + Long-term Cost (i.e. subscriptions)) = Overall Satisfaction

The PlayBook is a nice, fast piece of hardware with a slick UI.  But its $499 price was too high. And the app selection for the PlayBook's QNX OS remains slim: about 1,600, as of late November 2011.  (According to a PlayBook user Peter Hansen, PlayBook users who search App World from within their device will actually discover more than 4,200 apps.)

One of those had to change for RIM to change the equation. Obviously, cutting the price was faster.

RIM is definitely losing money with each PlayBook. Amazon probably loses about $3 for every $199 Kindle Fire it sells.  The PlayBook is identical to the Kindle Fire, except that it has more  storage, a camera and nicer casing. And many PlayBooks were manufactured  and shipped to stores even before the Fire was announced.

So let's be  conservative and assume that RIM loses about $50 per PlayBook sold.  If RIM sells a million PlayBooks this Christmas, that's a $50 million  loss. That's not that much. It's less than one-eighth of RIM's net  income for one quarter. RIM would still have $830 million in cash.

The upside is that developers suddenly have a reason to build for QNX  again. Some already did. Read this blog in BerryReview by one  developer, who claims he's already earned about $100 an hour for a PlayBook app after just four days of availability.  That's far more than he's earned on apps he's built for iOS and Android.  And that creates the positive feedback loop that will generate  customer buzz, boost brand value, and eventually allow RIM to raise the  price on future generations of PlayBooks.

That's the epitome of the well-known strategy of giving away razors in order to sell the blades. Or, to modernize it, selling the printer at a low price in order to profit on the toner or ink.

The tablet market, like all mobile markets, is still up for grabs.  Hardware lifecycles are short - 1-2 years. That's why we've been able to  see some mobile vendors rise incredibly fast, and others plummet like a  rock.

I think RIM's other coming moves - like the Mobile Fusion tools for IT, and Android app compatibility - will only build on the momentum it's building today.

-----------

The ironic thing about the PlayBook is that RIM must now hope that  the Bring Your Own Device trend, which has hurt it in smartphones, will  help bring many PlayBooks into enterprises.

But that's the way it goes. In the new era, most organizations will  have to deploy its own tablets as well as accommodate ones brought in by  employees, according to the Universal Declaration of Workers' Mobile Rights in the newly-published book, Mobility Manifesto: Transforming the Enterprise.

You can download the Manifesto at www.MobilityManifesto.com. And take a 5-minute quiz to find out where your organization ranks on  Mobility - a Laggard, Rookie, Dreamer or Leader. We'll compare those  results graphically against your peers worldwide (see below).

...is probably not what you think it is. And it's not something within the control of developers (though IT managers sure as heck do).

In order to tantalize/frustrate you a little longer, let's first take detour along memory lane to 2003, and the Rise of the MachinesWeb 2.0.

As they became inundated with Web traffic, Web 2.0 startups looked for cheaper, less brute-force solutions than their dot-com predecessors would, such as buying Sun servers or renting T3 lines.

Enter "load balancing," which describes the strategy of spreading out your Web or internal network traffic for better performance. This could be done in one of two ways: plopping in a switch-type product into your existing network, or re-architecting your network from several powerful central servers into a large, distributed 'server farm' made up of hundreds or even thousands of PCs.

Load balancing is no longer a hot topic, as the solution has pretty much trickled down from the Web to mainstream enterprises.

But mobility re-creates the need for enterprises to re-balance their workloads.

Why? When PCs were the primary device and 3G still just a dream, real-time access to data was neither important nor expected. Reports were e-mailed to you at regularly scheduled intervals - nobody went into Crystal Reports and pulled data themselves. Any ad hoc reports would be sent as a request to your friendly business analyst, who would then come back with something for you after several days or a week.

Today, we have powerful smartphones and tablets, 3G and 4G networks and easy-to-use mobile apps that connect directly back to the server. Everything on the front-end is enabled for real-time.

How about the back end? Not so much. Delays still abound. Suddenly, your application and data layers look out of balance again. There's your Achilles Heel.

Of course, switching server applications or middleware to decrease latency can frankly be expensive. But the ROI can be well worth it.

I've often talked up the sheer scale of the mobile device deployments at my parent company, SAP: 11,000 iPads, 5,000 iPhones, experiments with the Samsung Galaxy Tab and Amazon Kindle Fire, etc.  What's equally impressive, however, are what it's done on the back-end.

SAP's salespeople used to rely on Excel to track sales, one of many factors why "we had to wait 2, 3, 4 months to understand what was selling, what  was not selling," said Global Sales President, Rob Enslin in a recent video.

Now, his salespeople as well as SAP executives can get such information instantly on their iPads. This is enabled by the use of SAP's HANA in-memory data appliance in conjunction with SAP BusinessObjects. Together, they accelerate the processing of 3 TB of CRM data so that it can crunched and manipulated by end users.

SAP heads know what I mean by the acronym COPA. It stands for the Profitability Analysis module of its long-standing ERP software.  HANA is also being used to speed up COPA internally at SAP.

During a Tweetchat last week, CIO Oliver Bussmann revealed that HANA sped up processing time so much that a key KPI fell from 28 hours to 4 hours - a seven-fold improvement.

As Bussmann tweeted during his chat: "The combination of real-time data combined with the mobile access is the new killer app."

In other words: if you want to get the most out of your mobile devices and apps, then you need to bolster, if not overhaul, your back-end systems. By doing so, though, you'll regain your prior balance, but at a higher plane.

---------

Time for a quick commercial: Sybase, an SAP Company, has just released a new book, Mobility Manifesto: Transforming the Enterprise, for which I was the editor. 

You can download it at www.MobilityManifesto.com. Expect  a mix of snarky observations about the plight of mobility-starved workers, possibly like yourselves.   Mixed in  also is helpful business strategy and actionable IT tactics. All with a minimum of  shilling for Sybase and SAP products. 

You  could even send a copy of the book or e-book to your boss or CIO. It’s  easier than Occupying his or her office, and may turn  out to be just as effective.

Eric Lai

Is it Time to Occupy CIO?

Posted by Eric Lai Nov 21, 2011

When the IT boss won't invest in tools that empower workers and boost their productivity, is it time to raise your voice? 

When mobile tools are treated as 'executive jewelry' available only to corner office-types, doesn't that inequality create "We are the 99%" discontent among the rest of the employees?

Politics is beyond the realm of UberMobile. This blog isn't meant to support, denigrate or trivialize the Occupy movement.

But there are some parallels between the Occupy movement and what's happening - or not happening, as the case may be - inside companies today.

As always, the future is here, but it's not evenly distributed, as cyberpunk author William Gibson wrote.

Resistance remains stiff in many quarters against new technologies despite being cheaper, more empowering, and likely to produce hard dollar benefits.

I'll bring up mobility because that's what I know. Some CIOs are charging head-first into mobility. Like Onyeka Nchege, CIO of Coca-Cola Bottling Co. Consolidated, who deployed hundreds of iPads to employees and encouraged them to install Angry Birds and other fun apps. His theory was that by letting them see the fun side of the iPad, they would get attached. And that it would result in lower breakage and loss rates than the ruggedized tablets Coca-Cola previously used. Nchege's theory proved correct.

Or take Oliver Bussmann, CIO of my parent company, SAP. He's deployed 11,000 iPads and 5,000 iPhones, runs an analytics data warehouse that crunches terabytes of data to return answers to iPad-using executives in a matter of seconds, and is building his own enterprise-compliant alternative to DropBox and iCloud.

But too many other CIOs remain stuck in a 'command-and-control' mode. Change is bad. Suggestions for new technologies from knowledge workers and field workers who know best what would would empower them get an emphatic "NO!" response if they don't fit neatly into the existing master plan.

Little do they realize that the era of technocrats getting to dictate what software and hardware that employees must use is coming to an end.

The burgeoning 'Bring Your Own Device' is an expression of workers' demands to be freed from the productivity-dulling manacles of the desktop PC. It's also the recognition of IT departments that they need to start getting on the right side of this Transformation.

Are you unsure whether your company is on the right side of the Mobile Transformation? Check out www.MobilityManifesto.com to take a 5-minute quiz to see if your company is a Mobile Laggard, Rookie, Dreamer – or Leader. You can compare your results against other companies, and then comment (see below):

 

 

 

You can also send your company's results to your boss or CIO! Anonymously, of course...   While you are at MobilityManifesto.com, get a copy of the new book, Mobility Manifesto: Transforming the Enterprise. Published by Sybase, an SAP Company, I was the editor. 

Expect a mix of snarky observations about mobility-starved workers mixed in with business strategy and actionable IT tactics. All with a minimum of shilling for Sybase and SAP products. 

You could even send a copy of the book or e-book to your boss or CIO. It's easier than pitching a  tent in front of his or her office, and may turn out to be just as effective.

Nobody seems to think the Amazon Kindle Fire has a chance of succeeding in business.http://www.informationweek.com/news/security/mobile/231903118

InformationWeek thinks the Kindle's Android OS is both insecure, and un-securable via Mobile Device Management (MDM) software. CIO Insight dismissed the Kindle tablet's reliance on the cloud, while eWeek calls the Amazon brand too fundamentally consumer-y. Meanwhile, CIO magazine said the iPad's just got too commanding of a lead within enterprises.

Whoa. I just had the strongest feeling of deja vu wash over me. It's as if I read and heard these same exact opinions 22 months ago, except it was about the iPad vis-a-vis laptops (I might have even been guilty of writing some of it).

You know what they say: learn from history, or else you'll let it repeat itself.  I know that's not enough convince tech-savvy, logical readers like yourself. So here are five arguments for why the Kindle Fire will surprise enterprise skeptics:

1) Developers are coming! Like moths to a Fire, Android developers are being attracted to the Amazon tablet and making it their highest priority. 49% of North American developers are very interested in building for the Fire, according to an Appcelerator survey, ahead of second-place Samsung Galaxy Tab.

Some developers are no doubt attracted by things such as the Kindle Fire code becoming open-source. But most developers simply go where they think  customers will be. That was the  feedback loop that boosted the iPad. And it should boost the Fire and Android overall.

2) So are consumers. According to a recent survey, 77% of tablets used in the enterprise are purchased and paid for by employees via Bring Your Own Device plans.

Consumers, in other words. Who by and large remain extremely price-sensitive. For the cost of equipping mom and dad with $499 iPads, one could equip the parents, two kids and even the family dog, too, with five $199 Kindle Fires.

This is why there are studies like Retrevo's that show more people planning to to buy a Kindle Fire than an iPad this Christmas. Or why DisplaySearch expects 6 million Fires to be shipped (versus 9-11 million iPads).

Expect millions of workers to start nagging their IT administrators in the New Year about when they can connect their Kindle Fires to the corporate network.

3) And so is IT. In an IBM-sponsored survey of 4,000 IT pros worldwide released last week, 70% said they plan to deploy apps for Android devices, versus 49% for iPhone and iPad, 35% for Windows 7, and 25% for BlackBerry.

On a more anecdotal level, I know two CIOs who have already started testing the Kindle Fire for internal use: SAP's Oliver Bussmann and Sybase's Jim Swartz. I have to believe that plenty of other CIOs are investigating Kindle Fires.

The reason is simple: consumer tablets are so inexpensive that they are the enterprise IT equivalent of a "disposable razor," according to Yankee Group analyst Eugene Signorini. And no mainstream tablet is less expensive than the Fire.

(Interested in seeing some Android enterprise tablet deployments today? Check out my list here)

4) Also, corporate e-mail support is here. Microsoft's Exchange email server dominates businesses, hands-down. And e-mail along with Web browsing remain core business uses for tablets.

Android may not offer native support - it's a Google product, remember? - but there are capable and secure third-party Exchange-friendly apps already available. NitroDesk, for instance, announced earlier this month that its TouchDown e-mail client app for the Kindle Fire was available.

5) The Zen of Minimalism. For IT managers, less can definitely be more when it comes to technology. How do you think on-board graphics became near-ubiquitous in desktop PCs? Because companies wanted anemic graphics so as not to  encourage their employees to while away hours watching Netflix or playing Halo.

So the perverse upside of the Kindle Fire's 8 GB of storage and 512 MB of RAM - half of what the BlackBerry PlayBook has - means less data stored (and potentially lost), and fewer movies and games to be watched and played by procrastinating employees.

Similarly, the Kindle Fire's lack of 3G/4G connectivity means one less headache for IT administrators worried about exorbitant data roaming charges from salesguys streaming movies in their overseas hotel room. The same goes for the inability of Kindle Fire owners to access the Android Market. Fewer apps, sure, but also much less exposure to malware.

Users love cloud storage services like DropBox and iCloud for their power and ease of use. IT managers hate them for the ginormous potential for data leakage and loss they create. But clamping down on them isn't so straightforward.  

In the past, a CIO could simply decree DropBox and iCloud verboten and his or her will would be carried out. IT management software would prevent banned applications from being installed, while network firewalls would block outlawed Web sites or network ports. End of story.

That's not so simple today. Many smartphones and tablets used inside companies remain unsecured by Mobile Device Management (MDM) software.  At the SAPPHIRE conference in Madrid last week, SAP CIO Oliver Bussmann gave a talk to fellow CIOs about how SAP is using its subsidiary Sybase's Afaria MDM software to secure the 11,000 iPads used by its employees.

"I had a CIO ask me afterward, 'Should we also do this [use MDM] with our iPhones?'" he said. "It just shows how there's a lack of information."

Another issue is that many of the Samsung Galaxy smartphones and iPads used inside companies today are owned by the employees themselves, courtesy of shrunken budgets and the desire of workers to Bring Their Own Devices.

That creates a legal grey area in regions like Europe, where strong data privacy laws there allow workers to unilaterally revoke their consent for employers to secure and manage the data residing on their phones and tablets at any time. Allowing BYOD devices can create liability risk for companies.

Moreover, we've moved on from command-and-control IT shops towards the 'consumerization of IT' era. Conditioned to the slick devices and apps they use at home, employees are rebelling against the ugly, kludgy gear and software they are issued at work. It's not just a matter of aesthetics. Consumer devices are more powerful and easier to use than their enterprise counterparts.

In this era, CIOs need to strike a balance between enabler - and dictator. That's what Bussmann is doing. Using Afaria, he plans to shut down access to iCloud to his employees by the end of the month. "The risk is far too high," he said.

But in closing that door, he plans to open another. His team has already created a prototype of a document-sharing service that will be released to employees by the end of year.

Based on the WebDAV standard, Bussmann says the goals are to make it as easy to use as iCloud or DropBox for both mobile devices and laptops (something SharePoint, what many companies use today, is poor at), while also providing the security only an internal, behind-the-firewall network can.

Bussmann talked up the service at SAPPHIRE and says he got a strong reception from other CIOs. So strong, he says, that if things go well, the service might eventually end up being offered to SAP customers.

If you're curious to learn more, you can ask Oliver himself during a one-hour Tweetchat tomorrow Tuesday November 15. Watch the #SAPchat hashtag starting at 11 am EST/8 am PST, and submit any questions using that hashtag.

They say you can't teach old dogs new tricks. So what about Big Dogs?

For the first 35-odd years of its existence, SAP only marketed and sold its own software. We weren't a platform vendor like Microsoft (Windows), Google (Android) or Apple (Mac OS X, iOS). So we didn't need to woo, support or sell other developers' applications.

It was a self-centered strategy that was borne out of a need to serve the many customers clamoring for our applications, as well as fend off our many rivals - IBM, Oracle, Microsoft and others.

You know how the story turned out: SAP grew to become the market leader (by revenue) in ERP, CRM, and business intelligence/analytics software. The Big Dog, in other words.

But as the enterprise market matured, it posed major challenges to SAP. Rather than rolling over and playing dead, we learned some new tricks.

One of those was launching the SAP Ecohub, an online marketplace for partner software and solutions, in 2008.  As independent analyst Dennis Howlett put it at the time: "EcoHub is a step in a fresh direction for SAP which has been perceived  as a company that doesn’t sell products that are ‘not made here.’"

Three years later, SAP offers more than 1,000 partner-built applications via the EcoHub and other channels.

Even bigger than EcoHub was SAP's $5.8 billion purchase of Sybase. Though also falling in the general category of enterprise software, Sybase has always been more of middleware and platform company than applications vendor ala SAP. It's always cultivated developers and partners to build applications that connect to its ASE database or run on top of the Sybase Unwired Platform (SUP).

With these two moves, the next was a no-brainer: releasing our own Enterprise App Store. Called the SAP Store for Mobile Apps, it opened up stealthily on Halloween with more than 50 SAP and SUP-certified apps from partners today, ranging from sales to productivity to human capital management (HCM) running on iOS, BlackBerry and other platforms.

Debuting at the SAPPHIRE NOW + TechEd conference in Madrid this week, the Store is a key part of our strategy to build up an SAP-centric mobile ecosystem. Even as SAP rushes to release more and more apps that connect with our applications, our goal is to have 80% of all mobile apps be built by partners.

So far, we're not doing too bad. For SAPPHIRE NOW, 20 partners submitted 200 apps to be shown on the show floor. 100 were chosen (check them out at the SAP Partner Mobile App Catalog).

Why are developers starting to come to the SAP Store for Mobile Apps and otherwise build for SAP? I asked Usman Sheikh, the vice-president at EcoHub in charge of the new enterprise app store. He answered my questions and, helpfully, shared these slides.

 

As I discussed in my blog, 'How Many Kinds of Enterprise App Stores are There Today?', vendors are starting to deploy their own enterprise app stores, in order to provide a blend of the features in consumer-oriented app stores (easy browsing, instant purchase and download) and the kind of features required by enterprise users: flexible payments (credit card or corporate invoice), company discounts, the ability to check if your device or OS version is compatible with the app, as well as certification (by SAP) that apps will work with back-end systems, confirmed Sheikh.

Other features include pre-sales support for potential customers. These include a 1-800 number and chat and e-mail to reach SAP reps as well as the original partner developer. This supports the higher-touch model preferred by customers forking over not $1.99 per app, but potentially hundreds of dollars or more.

To accommodate line-of-business users who prefer to quickly get the app running in order to kick the tires themselves, SAP is offering its app store as an iOS app. See the screenshot below.

 

Longer-term, the SAP Store for Mobile Apps will be tightly integrated with the Sybase Afaria mobile device management software. Within weeks, users should be able  to launch the SAP Store from within Afaria, said Sheikh. 

Afaria will also eventually be able to communicate with the Store so that only apps consistent with an employee's role in a company  are displayed, as well as help configure and install new apps. That  integration will continue to grow. "Afaria will be the preferred MDM  solution," he said.

The Store not only supports apps built on Sybase's SUP app  development platform, but also apps built using other technologies such  as the cloud-based Business ByDesign or SAP NetWeaver Gateway, Sheikh  said. See the chart below.

And what about the all-important financial terms? Developers will get an 85% share of all app license and subscription revenue garnered through the Store, said Sheikh.

In other words, SAP is taking 15% - just half of Apple's 30% take for its App Store. Developers are not bound by exclusivity agreements, said Sheikh.

Sheikh said SAP will "respect" developers who wish to offer their apps on a freemium basis - i.e. free versions that can be converted later into paid via in-app purchases - but expects to receive their 15% cut of those subsequent in-app purchases.

As mentioned, apps must be certified by SAP before they can be sold on the Mobile Apps Store. That is free for the rest of the year.  How about for 2012? "It will be reasonable and competitive," Sheikh said.

Granted, the Store remains in beta today. Many of the features mentioned above, such as credit card purchasing and the ability to selectively offer apps to users based on their job role, won't be ready til first or second quarter next year.

Even still, can you name another vendor-operated enterprise app store that is more advanced than SAP's? If so, please share with me and other readers. For now, I think SAP Store is further proof that big dogs can learn new tricks.

Don't be dismayed if you're a little fuzzy on what exactly constitutes an 'enterprise app store'. The market appears to be in a Rashomon-like state of disagreement, too.

Despite what the analysts' might write, there are multiple, somewhat-overlapping definitions of the enterprise app store floating around in the minds of techies and business-types.

All of them borrow heavily from the original Apple App Store - that is, a Web site or mobile portal serving up apps to users. But they differ in how they work and who they are intended to serve. And none are likely to disappear soon.

It's not as confusing or infuriating as it sounds. Just as the e-business era gave us two terms for corporate Web sites - employee-facing intranets and customer- and partner-facing extranets - I'd argue that mobile enterprise app stores can be divided into 1) those that face inward towards one's own workers, and 2) those that are public-facing and aim at customers and partners. Let's tackle them in that order.

-------

Internal enterprise app stores are what your IT manager or  CIO probably thinks of, if they've been exposed to the marketing of any of a  dozen-plus mobile device management (MDM) software vendors (including that of my employer, Sybase, with our Afaria software): a personalized portal for employees to download apps or updates on a  self-service basis. 

Self-service is important: you don't want to force a fat new app or update down a skinny 3G pipe, especially if the worker is traveling and could incur expensive data roaming charges.  The stores securely host purchased or internally-developed apps on the corporate  server, or point to external download sites, such as Apple’s App Store or  a developer’s server.

The  white list of apps for each employee is sometimes auto-generated from  the same Active Directory permissions that determine his desktop or laptop PC’s network  access and downloadable applications. But more often, it is created or  heavily tweaked by an IT administrator creating groups and permissions using the MDM application or  service. The app store can also manage blacklists of apps or games, and help you manage complicated app licenses and purchases. 

Despite the initial configuration work, IT administrators will save time from not having to manually track usage via Excel spreadsheets, and gain the control that they desire. 

------

External-facing enterprise app stores come in three flavors. The first is what you would hear about if you quizzed a random smartphone-wielding person: a platform-run store such as Apple's App Store, Google's Android Market, or BlackBerry's App World. It makes sense: there are some 28,000 paid and free apps in the business and productivity sections of Apple's offering.

The advantage of these stores for enterprise developers is obvious: an established program with lots of potential customers. But there are key disadvantages for enterprise developers. The low-touch, high-volume model of these stores means that enterprise developers don't get much control over how their apps are marketed, sold and delivered.

That's key. Some enterprise apps can be marketed in freemium (easy-to-install free demo or limited function versions) models like consumer apps, but most cannot, as they require technical customization to get connected to a company's database or server applications and start running.

------

Third-party app stores are the second category of external enterprise app store. They are easily-browsed indices of apps drawn from multiple sources:

- official app stores such as Android Market or App World;

- developers whose apps were not approved by Apple or RIM (read: adult), and/or run only on jailbroken or unlocked devices;

- apps that were uploaded by the developer or ISV themselves.

Third-party app stores can be quite large and popular. GetJar.com says it lists more than 366,000 mobile apps and games for a mind-boggling 2,500 different devices. It says it has offered 2.2 billion downloads to date. Another, Appia.com, says it has 140,000 paid and free apps drawn from 32,000 developers. Both have business or productivity categories.

For enterprise developers, the advantages are similar to the platform app stores: customers and a defined program. However, the sites tend to offer even fewer commerce and marketing features for developers than platform app stores. That's because, as mentioned above, a large percentage of their apps are hosted elsewhere.

In other words, a third-party app store works less like a storefront and more like a  app store functions less like a storefront and more like a catalog (indeed, much of their revenue comes from Web ads and commissions for referred downloads).

In that way, third-party stores may get trapped into their niche as a simple aggregator of apps, and fail to build the m-commerce features desired by developers (and often by endusers). That could put them at risk of obsolescence, similar to the way dot-com era Internet Malls were quickly leapfrogged by eBay and Amazon.com.

--------

Vendor-operated app stores are also emerging. This is partly because of the availability of technology: many vendors of internal app stores sold to IT managers have also packaged their offering into white-label/OEM solutions for developers to publish externally. Appia and Partnerpedia come to mind.

The bigger driver is that vendors, as mentioned above, aren't overjoyed with how large-scale app stores are connecting them with potential customers.  Rather than breadth, what vendor-run app stores want to offer is depth - depth that should be appreciated by both other developers and enterprise customers:

- online compatibility check to ensure that apps will run with your hardware;

- certification that vendor- or ISV-built apps will run with certain applications;

- support for multiple devices (i.e. RIM, Apple, Android);

- flexible purchasing terms (i.e. individualized customer discounts, or the ability to pay with credit cards or corporate invoicing);

- enabling high-touch interaction, such as connecting customers with support engineers, or system integrators before, during and after deployment;

- internal enterprise app store features such as enabling only employees in a certain position or department to download certain apps;

- deeper integration with internal enterprise app stores.

At the SAPPHIRE Madrid conference later this week, SAP will unveil its own Mobile App Store. Many of the above-mentioned features will be demonstrated there. Others, such as deep integration with the Sybase Unwired Platform and Sybase Afaria (and its internal enterprise app store features), are coming.

Look for the announcement later this week and my coming blog, where I'll interview Usman Sheikh, vice-president of SAP Ecohub, to get a deep dive into the SAP Mobile App Store's features and roadmap. http://i.zdnet.com/blogs/rashomon.png

None of the following problems should be showstoppers for your corporate mobile deployment.

But as described by the CIOs and IT managers sharing their experiences at this week's Enterprise Mobility Exchange conference in Las Vegas, they can certainly cause a sleepless night or two.

All the more reason to go into your mobile deployment forewarned about these potential annoyances - along with some potential solutions.

1) The headache of managing your wireless carriers. With 127,000 employees around the world, one of the biggest jobs for Stephen Jones, global mobility service manager at Proctor & Gamble, is trying to keep track of P&G's 100+ carrier plans worldwide, and the implications thereof.

What implications? Preventing employees from using iPhones in certain countries because of high data rates is one. P&G also has to make sure that employees who live close to foreign borders (Buffalo, NY, for example) aren't inadvertantly charged roaming rates.

"The phones don't know where they are sometimes," he said. Wildly-varying prices between countries also create a grey market of sorts, as some employees try to buy phones in one country to bring back and use in their home country, he said.

Potential solutions: Many mobile device management (MDM) software include telecom expense management (TEM) features that help simplify tracking and enforce your policies.

2) The surprising fragility of ruggedized devices. Ruggedized devices are hugely expensive because of all of their protective design and materials, as well as the military certifications for harsh environments that they possess. To keep TCO reasonable, many IT managers try to extend the life of ruggedized devices to five or even seven years - a surprisingly vain effort in many cases, it turns out.

One major reason is that workers never get emotionally attached to these homely, fun-free devices and thus tend to be careless with them. That indifference slowly turns to hate as the devices age, as resentful employees treat them even more roughly.

Potential solutions: At FedEx Ground, the company uses a lot of "less-technical approaches" to keep its 100,000 mobile devices safe, according to Matthew Berardi, managing director of field technology operations. These include making the devices wearable, i.e. putting them on wrists of warehouse workers to let them sort packages hands-free, and requiring workers to check-in their devices into storage lockers at the end of shifts.

Another potential solution: deploy consumer mobile devices like an Android smartphone or iPad instead, and encourage your workers to become emotionally attached to them by letting them check their e-mail and play Angry Birds on them. They'll treat the devices with as much TLC as if they were their own, according to Onyeka Nchege, CIO of Coca-Cola Bottling Co. Consolidated.

Because they're far cheaper than ruggedized devices, companies can view iPads and Kindle Fires like "disposable razors," says Yankee Group analyst Eugene Signorini. Still, you can augment their longevity with an inexpensive after-market case like an Otterbox that offers near or true military-spec protection.

3) Strict industry or country laws make Bring Your Own Device (BYOD) hard to do. That's what Tony Winston discovered when he recently moved from American Airlines to the bank Capitol One. At American Airlines, Winston helped negotiate "very aggressive discounts for unlimited data plans" for its employees, to encourage them to buy smartphones and use them at work. Capitol One prohibits BYOD devices, he said, though they do allow employees with corporate smartphones to use some personal apps.

At P&G, the company only offers Bring Your Own mobile in Canada for managers, though it is running a 300-employee pilot in the US, Jones said. It hasn't made headway in Europe and Latin America because strict data privacy laws make it more difficult for companies to control corporate data residing on employee-owned phones and tablets.

Potential solution: The right MDM software may be able to help you set management policies that provide adequate protection for your company while respecting individual data privacy laws.

4) Low budgets for mobility. In this economy, it afflicts companies in every industry, though it hits certain industries worse. One manager at a large US utility told me that all IT budgets and IT projects must be approved by government regulators.

Potential solutions: Sure, you could wait for an economic recovery or switch companies and/or industries. The better approach, if possible, is to try and gain the support of your business-side peers for mobility (see 6) below).

5) Untrained or rebellious users. This is not as common of a problem as IT workers, especially those manning the helpdesk, like to imagine. But it's potentially more harmful. At PG&E, a huge percentage of the heavily-unionized workforce is nearing retirement, giving them little incentive to adopt new technology, said Joe Chung, MobileConnect Program Lead at the Northern California utility.

"I was talking to one of the users who is 8 months from retirement. He told me, 'You can't make me use it and you can't fire me,'" he said. Even worse: some PG&E repairmen, leery of being tracked via the GPS in their devices, have tried to put tinfoil over the satellite antennas in their trucks (not realizing that the GPS chip and antenna is built into the device).

Potential solutions: For the untrained but willing, it can simply a matter of training. At Exelon, Johnson discovered that some of the drivers using the laptops had never used a mouse before. Exelon deployed mandatory computer-based training that covered basics like using a mouse for all of its drivers, said Johnson.

For rebellious users, try giving reports or analytic dashboards to senior managers that show what percentage of their workers aren't using the new technology, along with the ROI that is being lost.

6) Getting support from business-side managers. When GE Healthcare tried to deploy mobility five years ago, it failed in part because the managers of the field teams that would use the technology "didn't see the need for change," said Geoff Hunt, lean, productivity and technology programs manager for Americas at GE Healthcare. There are also the narrow, bottom-line focused managers who will view mobile deployments as expensive and non-strategic.

Potential solutions: More than ever, IT leaders need to get out of their shell, suck up their pride and woo their business counterparts to ensure that projects are a success. That means, says Hunt, "socializing your program around, getting them to feel like they have skin in the game, either by investing their budget or people."

That doesn't mean wasting your efforts on the many when you need just one.

"Lots of people may have veto power. You need to find the one person who can say 'Go!'" he said.

...is a complete no-brainer. Yet, so often and easily-ignored by the IT team.

The key is: ensure that mobile deployments, like any IT project, are true partnerships between the business teams that will use the technology, and the IT departments building it.

It's so simple. Yet, it's the natural tendency of IT to go it alone and take the attitude of "Build it and they will come (and like it)."

I'm not blaming IT here and saying it's because they are a bunch of asocial Aspergers-afflicted oddballs, as shows such as The Big Bang Theory or The IT Crowd depict.

I mean, that's probably true some of the time. But I've found in my working life that the tendency towards prideful secretiveness, lazy non-communication and treating other departments as enemies rather than colleagues is pretty dang universal. Doesn't matter what department you're in or whether your department is full of introverts or social butterflies.

Ted Johnson, IT manager for mobility support at Chicago-area energy firm, Exelon, said that talking to his business peers was key to discovering that many of the utility repairmen who were due to get ruggedized laptops had "never used a  mouse before."

Learning about that early on gave Johnson's 18-person  team time to develop computer-based training that addressed that issue.

"If IT leads too much, you WILL miss business requirements," he said during a presentation this morning at the Enterprise Mobility Exchange in Las Vegas. "It was so critical to have business involved."

Starting in 2006, Exelon rolled out 2,300 ruggedized Panasonic laptops to its utility repairmen in an effort to automate work orders and speed up the time to fix electrical outages.

The success of that project, he says, was also due in part to the creation of three levels of committees with the business-side managers. These included a steering committee comprised of direct supervisors and lower-level managers of the repairmen; a governance committee of senior managers; and an executive committee of C-level types.

This proved key when Johnson began measuring the results of the laptop rollout and discovered that some drivers were actively resisting the technology.  Johnson smartly gave the executives a dashboard showing usage of the tool to the executive committee members.

Once they discovered the problem, they "drove it down to their managers to get on their people" to use the laptops, he said.

Similarly, Onyeka Nchege, CIO of Coca-Cola Bottling Co. Consolidated, also created a high-level Enterprise Mobility Advisory Group (EMAG) of executives for his deployment.

That may seem contradictory: Nchege's goal at the time was moving IT at Coca-Cola from its traditional role as "order-takers" to business.

"Our service was absolutely there: tell us what you want, and we could get it done, and get it done for you quick," he said during a presentation on Wednesday at the Exchange.

So wouldn't you want to get less advice and less feedback from the know-nothing business guys? Not says Nchege.

"We proactively sought feedback even while we took ownership," he said. "By getting feedback from our business partner, we got instant credibility. 'Man, you asked me what I thought.' They understood that we're building this for you and building it for us."

Nchege even took the step of accompanying one of the field sales rep managers to a visit with a restaurant owner to better understand their challenges simply trying to get the attention of a busy potential customer.

Nchege had a hunch - maybe arming the field salesguys with then-new iPads could help break the ice with restaurant owners in places like Mobile, Alabama? So he rolled out the Apple tablets to them. His hunch proved correct.

"We had an uptick in sales and on-premises business as a result of putting iPads out there," he said.  Nchege recognizes that the uptick won't last forever. He says getting the iPads out in the hands of salespeople was a quick, momentum-building win.

But Nchege says that simple step helped him immensely bridge the gap between business and IT. There must be similar steps you can also take, no matter how busy you are.

"You may think you're the only one running 100 miles per hour, but guess what? Everyone else is like that," he said.