Developing A Mobile Bi Strategy Sap Inside Track New York City June 2012


Published on

The session focusses on points to consider when starting off on enabling a Mobile BI capability in an organization. It highlights macro trends in the technology landscape and connects them with internal drivers that impact a Mobile BI delivery in an enterprise

What’s driving Mobility in the Enterprise?
Why a strategy for Mobile BI?
What is Mobile BI?
Current state of Mobile BI
Macro, Data Security, User Experience

Video recording:

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Good afternoon and thank you for the opportunity Its a pleasure to be here to share with you our experiences in enabling Mobile BI capabilities I am smack in the middle of the Melatonin dip hour but hopefully the session will keep you sufficiently engaged
  • In the session today we will cover points to consider when starting off on the Mobile BI journey We will touch on the drivers behind Mobility in the Enterprise, the need for a Mobile BI strategy, what is and isn't Mobile BI, its current state and key considerations while planning a Mobile BI service A quick Show of hands --- How many of you have a centralized team looking at Enterprise Mobility? And how many of you have a centralized / shared service around Business Intelligence? Good. Then the agenda should be broadly in line with what you expect from this session
  • First things first My name is Mayank Misra and I am an employee of Pfizer. What follows is based on my experience with this technology and does not endorse a particular technology and delivery direction in Pfizer
  • The business need for faster, more intuitive and self serve access to business intelligence (BI) continues to grow. With the exponential pace of mobile device adoption, delivering on the promise of pervasive and real time BI is more urgent. Mobile devices becoming primary source for creating and consuming digital content New approaches to store and compute vast amounts of data have removed the cost barriers of delivering on this opportunity. The app stores have commoditized and reduced the cost of Mobile BI application development. As disruptive as it may seem, the fundamentals of enabling an organization with Mobile BI are not all that different from rolling out a new business intelligence solution.
  • Smart phones sales have outpaced personal computers. Tablets are geared to overtake desktop sales in the next couple of years. These trends will make mobile devices the primary source for creating and consuming digital content. The mobile device market is still emerging with new devices coming to market continuously. From a development and IT roadmap perspective, Android and iOS remain the dominant players in the Mobile operating system space. Blackberry still has a large install base in the enterprise space and analysts have really high hopes from Microsoft’s latest release of Windows OS. In short, a clear leader is yet to emerge. In this ever changing ecosystem, Business Intelligence platform vendors are trying to best meet the need for a Mobile BI product. Each vendor will have varying levels of interoperability within and external to their own BI offerings. An organization may have multiple mobile enablement efforts specific to a line of business. It’s important for data management strategists to develop a Mobile BI roadmap that factors in these internal and external drivers.
  • Delivery of analysis and reporting content to smart phones and tablet computers is loosely referred to as Mobile Business Intelligence. From a technology perspective, Mobile BI modules are usually extension of the enterprise reporting platforms that convert the BI content to work with the navigation construct and screen real estate of a Mobile device. It builds on your current investments in data repositories, guided analysis, reports and data visualization. The limited screen size is more suited towards simple visualizations and displaying aggregate values like key performance indicators. Garbage in garbage out, still applies
  • In terms of maturity, Mobile BI today is usually delivery of reports and enabling hierarchy navigation through a Mobile device The real business case is in nuggets of data delivered at the right time and not in chartoons and glorified excel spreadsheets Achieving Simplicity is not ease. Making the navigation intuitive takes technical skills and requires deep domain knowledge.
  • Success of a mobile operating system has hinged on the strength of its developer community. The same holds true for Mobile BI platforms as well. The more the developers, more the number of innovative apps available on that platform. Mobile BI Vendors will need to ensure that their products offer a robust set of application programming interfaces (API) and licensing structures to make it worthwhile of an app developer’s time. Understand the Mobility Strategy of the vendor in detail. BYOD - BI on Bring Your Own Device doesn’t mean any and all variants of devices should be supported. Organizations should standardize on one or two devices and operating systems. For multinational companies, the standardization choice should take into account in-country and geographical preferences for a device/OS combination. Flash - Keep an eye on development standards. A position by a technology vendor with a big clout can move development standards rapidly and radically. Adobe Flash is on its way out with the momentum shifting to HTML5.
  • A Mobile BI data protection strategy should go beyond identity and access management (authentication, authorization, and entitlements). Think about remote swipe of in-app data. This is separate from the remote swipe of the full device which is useful for a lost or stolen device. Ability of remote swipe within an app used to remove the ‘reports’ stored within the Mobile BI application remotely. Usually this is triggered when a BYOD user changes roles or leaves the company. Remote uninstall should be considered for license management for seat based app licensing. Many choices of in-app integrated cloud storage are available. Consider your companies policies around cloud storage of enterprise data. Evaluate if the Mobile BI app of choice enables management of in-app capabilities Factor in the ability of the BI platform API/SDK to enable User/Group Management, Single Sign On, Object Level Security, Row Level Security for the Mobile BI components.
  • Who is your audience? Think about who can benefit. Mobile delivery of business intelligence is not limited to real time data on cost, revenue, margins and distribution channels for sales or finance or the executive tier. The real value of BI is when it’s pervasive in an organization. Mobility makes it possible to push BI to the edge of an organization. Arming the teams that work directly with customers, vendors, partner is where the business case is. As it is with any BI solution, a Mobile BI implementation should be geared towards serving the needs of the targeted community of users. Expectations of an executive tier user will be different from a sales representative or a scientist. User requirements for Mobile BI solutions are usually around: Self server access to information in on-premise or Cloud LoB systems (CRM, ERP etc) Access to reports and metrics optimized for context sensitive mobile navigation Offline report access to stay current with customer information Alerts – Subscribe to alerts and be notified of data changes and refreshed reports Over-the-air installation – Deploy the software at convenience using a wireless connection Ability to collaborate form within the Mobile BI app Should be intuitive with little to no training requirements Content design considerations Mobile BI is primarily graphical in nature. Developers need to be strict followers of rules around visual display of data. The graphing choice should invoke thinking and lead the eye to seek comparisons. The navigation should be intuitive and context driven. Considerations should be made for the screen real estate. Cramming a lot of information in a small space may make it hard to read. Consider a standard template based approach. BI content aimed for Mobile distribution requires a tighter partnership with business. For this, a developer will need to know in advance the various navigation permutations a business user may take.
  • Developing A Mobile Bi Strategy Sap Inside Track New York City June 2012

    1. 1. Developing a Mobile BI Capability Strategy considerations Mayank Misra Director, Architecture & Engineering Global Data Management, Pfizer Inc. @MayankMisra | #SITNYC
    2. 2. Abstract• What’s driving Mobility in the Enterprise?• Why a strategy for Mobile BI?• What is Mobile BI?• Current state of Mobile BI• Considerations – Macro, Data Security, User ExperienceThe session focusses on points to consider when starting off on enabling aMobile BI capability in an organization. It highlights macro trends in thetechnology landscape and connects them with internal drivers that impact aMobile BI delivery in an enterprise
    3. 3. DisclaimerI am an employee of Pfizer. The statements or opinions expressed are my own and do not necessarily represent those of Pfizer.This presentation outlines a general technology direction. Pfizer has no obligation to pursue any approaches outlined in this presentation or to develop or use any functionality mentioned in this presentation. The technology strategy and possible future developments are subject to change and may be changed at any time for any reason without notice.
    4. 4. What’s driving Mobility in general?
    5. 5. Why a strategy for Mobile BI?
    6. 6. Mobile BI: What it is and what it’s not
    7. 7. Mobile BI Current State HIGH Mobile BI – Where it should be… Alerts Insights Mobile BI – Where it usually is…Solution Complexity Technical Skills LOW Business Value HIGH Need for Domain Knowledge
    8. 8. Macro Consideration
    9. 9. Data Security Considerations
    10. 10. User Experience Considerations