Showing posts with label b2e. Show all posts
Showing posts with label b2e. Show all posts

Monday, March 18, 2013

Enterprise Glass

Google Glass is looking like a great leap forward in ubiquitous computing. My previous article covering computing uses and form factors will probably still hold true until a step change with input devices occurs. Most of the excitement around Glass is in the consumer space with amazing looking first person videos of sky diving and the like. What I wanted to write about was the potential for glass in the enterprise.

Augmented Reality
According to Wikipedia: "Augmented reality (AR) is a live, direct or indirect, view of a physical, real-world environment whose elements are augmented by computer-generated sensory input such as sound, video, graphics or GPS data."

AR is already making big inroads in the Business to Consumer (B2C) space especially for marketing/advertising scenarios. Not long back I was in Thailand and noticed a lot of people running around a Uniqlo store looking for butterflies. AR also has some potential in the Business to Enterprise (B2E) space using a mobile device to 'look' at equipment or similar. What really makes Glass a practical alternative is the hands free operation with the screen always where you need it. Makes me think of 'The Terminator' and obviously the military use similar technology in helmets for aircraft and such. In many enterprise environments safety glasses are already standard equipment so why not leverage them with powerful targeted information?

Glass in the Enterprise
Ok Sergei, Steve, Babak, and team here are some ideas that I can quickly come up with for Google Glass in the Enterprise, send me a set and I will happily come up with some more:

StyleExampleDescription
B2ETrainingNew staff are inducted to the office, OH&S policies, firescapes, bathrooms, etc using an interactive augmented reality application.
B2EHRCombined with facial recognition provide the ultimate 'whisper in the ear' to identify staff and associated metadata.
B2EMeetingsUse with IM /meeting sharing apps for a unique perspective on remote meetings. Connect to whiteboards and other equipment.
B2ELogisticsCombine with OCR/Scanning/RFID to aid with stock takes, bin counting, receipting, proof of delivery.
B2EAssetsIdentify assets, schematics, parts. Request/Enable remote assistance when repairing.
B2ERetailStaff can be instant experts on their own products. With overlayed pricing and detailed product information + onselling recommendations.
B2BRealestateInspect realestate with guided room checklists, record results. Provide virtual property tours.
B2BConferenceRecognition for attendees, AR product information, competition entry, location awareness, photography.
B2BEventsProvide targeted buyers (e.g. fashion) with glass and let them sit back and watch the show with AR provided product information.

As you can see there are a variety of opportunities to leverage and launch investments in Social, Mobile, Analytics, and Cloud (SMAC). I'd love to hear your suggestions for more ideas for Glass in the Enterprise.

Google does it again
This is the second time in my life I can recall where I had an idea that Google launched as a new offering in an amazing way. The first was around 10 years ago I was making cartoons on my animated flash website MonkeyStyle and used a collection of satellite data to allow my character to zoom into his target. Not quite Google Maps but hey it was similar in concept! In the last couple of years I drafted a science fiction novel about Augmented Reality Contacts - now they are real!

Tuesday, March 12, 2013

The Rules of Enterprise Mobility

During many mobile meetings, presentations, and discussions I've come across a collection of "Rules For Enterprise Mobility". These rules cover topics like selecting mobility tools, types of users and applications, mobility needs and a lot more. Let's start with three rules of three:

Rule of Three
Gartner coined the phrase "the rule of three" to help convey when it best makes sense to use a MEAP (Mobile Enterprise Application Platform). The idea is that you should consider a MEAP if you have any of the following needs:
  • 3 x mobile applications
  • 3 x device types
  • 3 x back end systems
Of course a platform helps with these by providing security, integration, and write-once deploy-many tools that you may have to develop yourself if you go it alone. So that's a rule number 1.

Three Mobile Groups
Coincidentally there are three user groups that we typically identify as the target of mobile applications:
  • B2E (Business to Employee/Enterprise)
  • B2B (Business to Business)
  • B2C (Business to Consumer)
Business to Employee/Enterprise applications are those which are used by employees of ones own company. Business to Business are used by partners or subcontractors and Business to Consumer are used by the general masses. Ok this is not really a rule per say but it's still mobility and involves the number 3.

Three Application Types
Thirdly there are 3 commonly recognised mobile application types:
  • Web
  • Native
  • Hybrid
Each of these application types have their place and various pros and cons (for example portability, performance, learning curve, cost) which I've discussed in my previous blogs. I don't know if that's now 9 or 27 rules or if it makes sense to try to or correlate them further. It would be great if there was one rule to bind them all but Tolkien didn't write enterprise mobility.

Four C's 
In the blog by Christopher Koch the concept of the four C's is discussed to explain the scope of a mobility platform:
  • Create
  • Consume
  • Connect
  • Control
As Christopher explains a mobility platform for enterprise that covers each of these areas will add value to business and IT. Suggest you have a look at the Gartner quadrants for some good information on the various mobile platforms.

Seven Steps
The 7 Steps for an Enterprise Mobility Strategy are covered nicely in Spider 21's Weblog these are:
  • Mobility Roadmap
  • User Workflow Analysis
  • Mobile Platform Selection
  • Device/OS Selection
  • Back-end integration
  • Mobile app development
  • Change Management.
Well worth a read to understand more about each of these important topics.

More Numbers?
I hope this selection of rules serves as a good reference for Enterprise Mobility and would love to hear some suggestions for more rules to include/update the article. If you are looking for detailed information on topics like Mobile Device Selection, Benefits of Mobility, or Mobile Testing then please follow the links or read through all the articles on this blog.

Tuesday, January 29, 2013

SAPs mobile audience

The Apple of the enterprise? A goal for one billion users (please read that with a Dr Evil voice). Makes a lot of sense for any software licensing organisation. Of course I don't mean to be cynical and firmly believe the mobilisation of enterprise software like SAP has wide ranging benefits. Reading great articles like Joshua Greenbaum's blog you can see that there is confusion in the market wrt how SAP will effectively achieve its goal.  Buying products to expand the portfolio (like the Sybase and Syclo acquisitions) as well as leveraging partner license sales is certainly part of the strategy. For me of interest is where are the users coming from? Take a quick look at each of the mobile user categories i.e. B2E, B2B, and B2C.

B2E
Business to enterprise, typically applications that an organisation's users are doing at a desktop. SAP has quite an extensive user base entering their SAP transactions into the GUI. Certainly there is a good case to mobilise a number of these users. You could read business value of B2E applications for a few ideas. So if existing users move from the desktop GUI to a mobile device do they count towards the one billion goal?

Of course there are opportunities in greenfield and replacement projects. When an organisation is moving from legacy to SAP then most will (or should!) consider mobile as an option for some user groups. However if these users would have previously been desktop users and are now mobile users then there is a degree of 'robbing Peter to pay Paul' happening with the licenses. Regardless the licensing concept is fairly simple, users tend to be named, and hence a fee can be charged per user.

B2B
Business to business, typically these applications are in the domain of 3PLs or marketing, HR and similar industries. Where by definition one company has a mobile application that is used by another company. For example a business may want an application for their customers (not the general public) to order directly or a 3PL may capture information on behalf of another company. Historically the B2B space has been achieved with interfaces, Edi, portals and the like. As with B2E the licensing can revolve around named users but sometimes there can be challenges here with subcontracting scenarios and the like. There are some great use cases for mobile B2B but compared to the final category the potential number of users is limited.


B2C
Business to consumer, the untapped holy grail of enterprise mobile applications.  How can SAP effectively provide valuable mobile applications to consumers? What is the most practical licensing model? The acquisition of the Sybase product suite has immediately brought a lot of consumer banking users under the SAP banner but what about the non-finance sector.

For example a hypothetical business sells, makes to order, and delivers goods to a customer. This business wants to provide a mobile application connected seamlessly to SAP that allows ordering, tracking, and customer self service. Here is an opportunity for SAP to add thousands of potential users to their 1 billion target. However the sticking point is that no one wants to pay for the mobile application. The app store phenomenon has set a low value expectation for mobile applications. How can SAP effectively monetize all these users?

While consumers might believe that B2C mobile applications should be free most businesses understand that they have value. Mobile apps reduce cost by moving some of the effort from employees to the consumer. Apps form part of a marketing, branding, and the advertising strategy. Dammit it's just plain expected these days.

Websites like Google, Facebook, Linkedin, etc. have done a fantastic job of grabbing an audience and these sites continue to evolve their strategies to monetise. One thing they have in common is they don't charge their audience directly to access the service. Often they make money from clever (sometimes unpopular) advertising or market research. Take the online electronic game industry that can now serve advertising between game rounds thus enabling premium games to be played for free. Consider also that in the case of programming languages arguably the most popular are free or in some cases offer premium content for a fee.

To get hold of the largest audience should SAP consider making the SAP Mobile Platform (SMP) for consumer applications free? Or charge for the platform only but not by user volume? Can their creative marketing geniuses come up with a model that would enable wide spread adoption of the platform? I'm sure ideas are being thrown around. What about mobile OS specific container application running html5 with SAP branding that was free to use for consumer applications, but a company could pay to self brand? How about a model where specific services/data sources/tables where able to be mobilised to consumers for little cost?

Over time the technologies and licensing models will continue to evolve and in a lot of ways the explosion of mobile apps is like the Internet bubble. Suddenly there is a way to reach a large potential audience along with the challenge of getting a return on investment.

Edit: For those of you mystified by SAP's licensing Sharon's blog does a great job of providing an overview of how it currently works.



Wednesday, January 23, 2013

Business value of B2E apps

Thanks to the consumerization of information technology and the app store phenomenon Enterprise Mobile Applications are moving away (thankfully) from clunky form driven screens. B2E apps are now expected to provide polished and guided business process with zero learning curve. This of course is a mixed blessing. On one hand there is more up front work in mobile projects to “get it right”. On the other hand when successful there are many benefits to change management, training, process conformity, and increased throughput.
If you already have a case to replace an existing desktop or paper based solution then it will pay to consider “mobile first” where the new solution has mobile components or is entirely mobile based. However if you are proposing to mobilise an existing process then it is important to concentrate on real business value to successfully compete for funds. I like to think of two general benefit categories for Enterprise Mobile Applications. Less Bad and More Good!
Less Bad
·         Eliminating double handling
·         Less paperwork
·         Less travel
·         Inventory holdings can be smaller
·         Mistakes are reduced
·         Less time to up skill new resources

More Good
·         Information is more accurate
·         Information is more timely
·         React more quickly
·         Process more work
·         Plan and schedule more accurately
·         Enable process conformity
·         Spend more time on business activity rather than on IT admin

These general buckets are great for a high level discussion. However when it comes to preparing a business case a more thorough investigation of mobile applications and functionality is required. I’ve compiled a short list by Mobile Application of some typical benefits.
Employee Self Service
Employees are empowered to enter leave/timesheet/expenses directly into their mobile device. The employees can more easily enter the activity when it happens rather than at the end of the week or month.
Benefits:
·         Reduce trips into the office just to do admin
·         Eliminate the need for a VPN token to access  a laptop remotely
·         Information is more accurate – resulting in fewer credit notes
·         Information is timelier – resulting in better planning, reporting, and resulting actions
·         Reduce double handling e.g. taking down timesheets on paper forms and sending them into the office.
·         Photograph/scan receipts directly with the expense claim

CRM / Sales
Employees can access customer and sales activity information at the point of business. Existing data can be updated or new data can be entered at the customer site.
Benefits:
·         Information (customers, activities, sales) is more accurate
·         Reduce double handling e.g. taking down notes and retyping them later
·         Act on customer leads/opportunities/sales in real time
·         Be better prepared for customer facing engagements
·         Spend more time with customers and less time in the office

Service / Plant Maintenance / Asset Maintenance
Employees can receive and view jobs in the field. Jobs can be transacted through to completion and new jobs can be created while on site. Assets can be inspected, updated, and created on the fly.
Benefits:
·         Information (jobs, assets, customers) is more accurate
·         Reduce double handling e.g. taking down notes and retyping them later
·         Easier to plan and schedule workforce
·         React to changes more quickly
·         Less need to travel to the office
·         Take payment directly in the field
·         Print customer receipts in the field
·         Scan and interface directly to data
·         Process conformity

Stock Take
Employees can capture and/or scan counts directly into a mobile device.
Benefits:
·         Reduce time to complete stocktake
·         Reduce paperwork
·         Less count errors
·         Enable more frequent stocktake
·         Enable guided and/or blind stocktakes
·         Enable cycle counting
·         Print new labels
·         Process conformity

Proof of Delivery
Enable employees to receive a schedule of deliveries on a mobile device. While on site enable the update of delivery, inventory, and AR data. Capture customer signatures and take payments at the customer location.
Benefits:
·         Reduction of paperwork
·         Information timeliness
·         Inventory accuracy
·         Improve DIFOT
·         Cash reconciliation simplified
·         AR position accuracy
·         Capture customer signature
·         Reduction of errors and credit notes

Mobile Training & Documentation
Enable employees to receive documentation out in the field to support training and/or OH&S.
Benefits:
·         Push reminders and documents to employees
·         Ensure process conformity
·         Reduce need to travel
·         OH&S

Mobile Inventory/ Warehouse Management
Enable employees to transact receipts, transfers, and other inventory movements with a mobile device and/or scanner.
Benefits:
·         Information is more timely
·         Eliminate errors
·         Eliminate reliance on paperwork
·         Scan documents, inventory, and locations
·         Improve DIFOT

Most organisations have limited funds and plenty of potential candidates for investment. Hopefully the above tips will help when formulating a case for B2E mobile applications. 

Edit 2015 - This topic has proven very popular and been syndicated across many sites. I've included a revised and more detailed version on the entire business case process in my book Enterprise Mobile Tips and Tricks