This morning I visited with a significantly larger enterprise client that has divisions that provide services in  mining, oil and gas exploration, environmental impact studies, building engineering, water conservation and more. In our conversation he commented, “My biggest challenge is that we have come to realize we all have all these disparate mobile solutions that service individual business silos, but can not interact with each other. Each division is running their own mobile strategy. Some have mobile apps, some are still on spread sheets, others have no mobile solution but considering and I just learned we currently have two MEAP solutions running. And we haven’t even discussed the mobile device issues. While we are all benefiting individually, it’s a mobility mess.”

In my experience companies who have rolled out mobile solutions have deployed them in an opportunistic fashion. Typically a field manager has caught the mobile vision early. Through his ingenuity, tenacity and budget maneuvering has implemented a mobile solution specific to his group. The positive impact of his mobile solution inevitably catches the eye and envy of other departments who eagerly clamor to adopt mobile solutions.

While this approach provides a strong, quantifiable internal use case for mobile solutions it often leads to a reevaluation of the first mobile solution. Especially, if the first mobile implementation only addressed a specific business need, was limited in scope, didn’t plan for the broader needs of the company and was not scalable.

Developing a strategic plan is critical for the on-going adoption of enterprise mobile solution. The key is understanding “why you are going mobile“. Evaluate what you trying to accomplish from an enterprise level all the way down to the individual level. Then develop a strategy that addresses this across the enterprise. Companies need to focus on the following key areas

1. Identify key business processes that will benefit from mobilization.
2. Determine how individual mobile projects integrate with a central mobile management, backend databases and security infrastructure?
3. Establish security policies for data accessibility, network accessibility, application distribution, device management, BYOD policies, etc.
4. Identify supported mobile devices; SmartPhone, TabletsPCs, Rugged devices
5. What supporting hardware is needed? Mobile Printing, GPS, RFID, etc.
6. Determine if mobile apps will be available on different mobile form factors; SmartPhone, TabletPCs, Rugged devices, etc.
7. Identify mobile user roles. User will roles determine data accessibility, security rules, appropriate device options.
8. Determine if mobile roles are transactional, informational or collaborative
9. Identify if mobile business processes and user roles are B2B, Internally driven or B2c
10. How many mobile users are targeted?
11. How will deployment and support of mobile users scale over-time?
12. What mobile architecture do you need to have in place?
13. How will mobile apps be developed, deployed and managed? Who will oversee this?
14. What types of apps will be supported? Custom-built, off-the shelf, modified mobile app templates, HTML5 mobile apps
15. Determine how success will be measured

Yes enterprise mobility brings new challenges and opportunities. Investing the time to conduct a full enterprise mobility assessment and developing the appropriate strategic mobility plan is critical for long-term sustainability and scalability of mobile solutions in the enterprise.

Like my client said, “We’ve been dabbling in mobility long enough. It’s time to get serious and unify our mobile strategy and get out of this mobility mess.”

Jody Sedrick

This week I had a great meeting with a new customer that is looking to build a really cool enterprise mobile application for the lighting industry. Meeting with them was refreshing as they obviously had invested serious time thinking through the mobile application, end-user requirements, backend integration and reporting requirements. This is unusual in that most of the customers come to us with an idea for a mobile app but haven’t really throught through the business application.

My experience with them motivated me to share some enterprise mobility guidelines we walk through with our customers.

First Question: What is your goal in “Going Mobile”? Or better yet, WHY do you want to go mobile?

Obvious as this questions seems, it is the foundation of your success. But many companies are on their 2nd, 3rd even 4th mobile implementation because they didn’t understand the “why” of going mobile. If a customer understands the “why” of going mobile their success rate  increases exponentially.  Some example goals and the “whys” brought to us to date:

• Improve responsiveness to customers.
  This is really a goal. It’s a result of good systems. Why do you want to improve responsiveness to customers? Have you struggled in this area? Have you identified the bottlenecks? What does it mean if you are successful?
• Providing mobile access to existing applications in the field to improve field worker productivity
  When I hear this I ask, “why is it important for field workers to have this data?” Does it enable the customer to make a decision now? Does it enable the field worker to guide decisions of the customer? Does it enable the service tech to offer the service now?
• Improve operational efficiencies both in the field and back end
  Again this is a goal. What is the cause of operational inefficiencies? Where are the bottlenecks? If I can eliminate those bottlenecks how does this affect serving my customers? How does it improve invoicing cycles? What reports now become available to help managers/sales people more effectively drive business.
• Expedite the invoicing process
  The why on this is clear as every business wants to keep cash flow moving in a positive direction so they can grow their business.
• Proof of service completion and acceptance
  Why? – A business wants to confidently demonstrate  service was completed or accepted.

Once you understand the “whys” of going mobile you can can establish the goals that will help you determine the right mobile strategy.  Most companies today deploy mobile applications in opportunistic business silos. While this approach can serve as a proving ground for mobile solutions it also can create a situation where mobile solutions become limited in scope, disjointed, invite technology disparity and are not scalable.

Businesses need to consider the overall mobility requirements within an organization and develop a long-term strategy that supports these goals then develop rollout strategies and pilots that align with the long-term strategy. Businesses tend to initially evaluate mobile solutions from the perspective of the field worker. But mobility needs assessments need to consider the entire business process and infrastructure considering every component including:

• Customer experience; Do customers interact with the device? A customer might review a service ticket or to provide a digital signature
• Field worker: what is the business process in the field? What data is required to help the technician or customer make a decision? Is mobile printing required? GPS -Do you need to know where your workers are or do they need help finding customer locations
• What kind of PDA device? Smartphone? Rugged PDA? Customer and field worker needs will drive device selection
• Back end integration: what accounting or corporate database systems need to be integrated with?
• Management and Executive Management: Considerations may inclue reporting, management evaluation and / or approval processes
• IT Support – what is required from the IT department? What device and connectivity standards have been set?
• Security policies

I find companies are on track when they’ve carefully considered these areas as well as some conclusions on the following:

• They have identified specific business processes that will significantly benefit mobile technology and why those are important
• Individual or departmental mobile projects are implemented with the overall business goals in mind. “Smaller” mobile projects can integrate with the enterprise mobile management, infrastructure and security policies.
• Common software, cloud based solutions or middleware mobile solutions are implemented across the organization.
• Implementation of device policies whether they be BYOD or corporate sponsored are clear and enforceable
• Projects are managed and supported according to clearly defined policies

I’ll take a look at deciding which mobile applications to deploy in part 2 of this article.

Jody Sedrick

SAP finally got it right with the announcement of acquiring Syclo. I remember shaking my head when SAP acquired Sybase thinking, “I see the infrastructure and synchronization value but Sybase doesn’t provide a MEAP, SDK or even off-the shelf apps.”

In a previous life, I spent 5 years building a MEAP solution that sat on top of Sybase.  I know first hand the power of the infrastructure as well as the weakness and lack of development tools. Sybase always seemed like a three legged stool somehow propped up with only two legs. The one significant benefit I saw at the time was that it provided a truly viable path for SAP’s customers to extend data to mobile users – all be it the 9th attempt as pointed out by Narendra Agrawal in his article “With Syclo Acquisition SAP does it again”

My first question when I heard the news was “Did SAP finally realize they made a mistake the first time around learning that Syclo would’ve be a better bet in the first place? Or, is this a key strategic move to further support and build on SAPs mobile vision?” It’s probably a little of both.

I think this is a big win for SAP since Syclo provides a much better mobile platform as well as industry proven mobile applications.  Companies looking to deploy enterprise mobile solutions quickly will be drawn to a Syclo’s enterprise class app library that already integrate with SAP and a powerful MEAP to extend app capabilities or build entire new libraries.

I think the acquisition further entrenches SAPs commitment to enterprise mobility. I see it as a strategic play to broaden their enterprise mobility reach. Public consensus seems to agree as illustrated by Kevin Benedict in his blog “SAP Acquires Syclo – A second Cup of Coffed and 25 Comments“. A whopping 78% think this is a good move for SAP.

The question remains, will customers view the acquisition in the same light?  I see the potential for many projects being placed on hold as companies wait for the dust to settle from yet another merger. I wonder if SAP will take this as an opportunity to simplify the pricing model as the current SUP pricing model is confusing at best.

Clearly this is another indicator of how quickly the Enterprise Mobility landscape is evolving.  This evolution creates on-going challenges and opportunities for mobile solution integrators and customers who are trying to decide how to develop and deploy mobile projects amidst an ever changing field of mobility players.