Webinar on Enterprise Mobility Strategy

Editor's Notes

• #4: Generic Definition Capturing/Delivering the Enterprise information at the point of activityForrester’s take The ability for an enterprise to connect and control suppliers, partners, employees, assets, products, and customers from any location - from any mobile deviceWhy Enterprise MobilityNecessity: Need for information at the point where it matters, is a necessity in today’s competitive world, for making critical business decisionsImproves Operational Efficiency: Enhances productivity, efficiency and responsiveness of the workforce
• #5: Earlier Mobile apps - youVoice and SMS, Low powered devices, Enterprise use disconnected mode devices (PDA, Laptops), Low penetrationLet’s face it well all know that for a large number of enterprises, email is pretty much the only application in use and that’s about all we can do with our mobile phones in many enterprises.This is Changing Now: There is a realization that entire enterprise infrastructure is important to create more interactive and more powerful mobile apps. We want access to the enterprise data stored in servers behind the firewall to make more of our work mobile.
• #6: So what we want to see happen now is our mobile devices reach into the availability of corporate data:WHY - Let me get your imagination going here ....You want to enable better and faster decision making without waiting - (especially from mobile devices)To quickly illustratewe want to go beyond simply making email or instant messaging better we want direct access to what’s happening in real time - an example of this is access social media engagement dashboards from our mobile phone - especially during critical campaigns.2. We want enabling a mobile worker to work away from office (more completely) without having to come in to finish reports or access the status of the entire workflow process for tasks.3. We see people wanting Dashboards with intelligent reporting and analytic capabilities provide powerful business aides on the move.4.We want to manage the growing cost and use of mobile devices: From device procurement, software overheads, recurring telecom expenditures and so forth.5. We want our mobile devices to provide real-time tracking of user behaviors on the website, provide more responsive customer service, improve brand loyalty, by access enterprise social media streams as mentioned above.
• #7: So how do we actually put a strategy together to take advantage of all the new mobile devices AND the interconnetive with enteprisebackends?
• #8: Th get the gains in operational efficiences we are going for - we need a top level strategy that coverBudgeting and Total Cost of OwnershipPolicies and management controlThe plan that covers how we’re going to implement the new mobile strategy
• #9: What will be our challenges in implementing a strategy?We’ll cover these areas next in the presentation for you.Focus on people ? Think about this for a moment from UI and security perspective: We have different types of users (and user roles) We have the ENABLERS - admins, content publishers, support staff) We have External entities - customers, suppliers - --- how does the application you have in mind reflect the different roles here?How an application looks and works can be driven by various corporate policies and governing principles - these policies determine security, data access, control and remote manaement of the mobile devices, and support and maintainenceThe ability to implement these policies for different users and roles is a directly impacted by the middleware - this is the connection to the enterprise servers so a mobile application can function the way you envision.In this world of multiple mobile vendors - RIM, Apple, Nokia, Google Android - you have to consider what you want to support in your overall platform strategyThen there is distribution of your application - will it be over the air? Will apps be different for different regions of the world?And finally security - will you need to encrypt data on each mobile device, is encryption needed at the transport level and so forth ..
• #10: So let’
• #11: Let’s touch on these three area - infrastructure - data management and integration w existing systems.InfrastructureEnsuring the infrastructure is well suitable In projects Endeavour see they are faced with numerous challenges while integrating with SharePoint services for mobile devices. SharePoint has a lot restrictions for the user permission, So we maintained our own hierarchy and managed the policy according to the project needs.So we’re often dealing with Finding extensions for mobility infrastructure. Each one has to be This impacts existing security Policy and permissions With regards to Data Management – think about Enterprise data management comprising security in three stagesDevice Level – Storing data in secured manner, Enabling standard encryption techniquesOn the Network – how do you provide a secure channel for data transmission over the networkBackend System – what is the procedure for sending data to a backend system via a secure channel for the tablets and mobile phonesIntegration with existing systemsProviding authorized access to the system and the users by enabling directory services already existing in the enterprise - you don’t want to duplicate what’s there just securely link with it.
• #12: This deck discuss about the security component at various levelsData Access Security ( Device + Backend System)Data Storage ( Implementing level of security on the device )Data Transmission ( Security involved over the transmission channel between client and server)Security meansSome of major features that can be adopted for Enterprise level security
• #13: To illustrate how why we need to address these security issues let’s take a specific case study. We’re going to show you an application developed for from Kimberly Clark - large manufacturer of personal care products. They wanted a more mobile based reporting system to share real-time manufacturing analytics results with management. However they were extremely concerned about security.
• #14: In this app it was critical that they have two factor authentication - they did not want any data being left on the device after it’s used. Two factor authentication provides a way to securely delete data remotely. ====================not sure if I’ll go into this level of detail or not here ...Following is a brief on the approach on mobile security and authentication in this project for Kimberly-Clark.The user login process has user authentication that requires the mobile app to send unique Device Id and PIN (One time password) to the server. The server authenticate the details (log them), generate the new GUID1 (unique identifier) and store it in the session. The reply is sent to the client with new GUID. This performs first factor authentication. Additionally for each session a two factor authentication is created, the mobile client makes a request for a PIN (One time password) along with the GUID (sent by the server in the last request). Server authenticates with GUID and requests a session; then performs the second factor authentication using Password and GUID. After this, second key (unique identifier) is created and sent to the client you have the ability to know exactly what happens in this session (by who) and you can securely delete the data exchanged during that session. Therefore no proprietary information once it’s deleted is left and you have an exact record of what happened during the session. For any subsequent requests received, the server will create a new GUID and sent back to client; client will send a request with new GUID and sent by the server for further communication
• #16: To integrate a mobile app into an enterprise IT backend you have to consider the followingHow to handle multiple access to data sources (and their locationsThe business logic the data must engage with across the different server end points - sybase, Oracle, SAP ...The meta data definitions that are in use to exchange data across these different types of servers - for example everyone should know what a PDF is, what an audio file is, what an Excel file is, a Word file, email file, SMS file and so forth. Commonly defined data definitions use meta data to interface with backend connectors.And finally integration with either an existing or custom MEAP - - MEAP is a Mobile enterprise application platform that brings consistency to the way multiple mobile devices and mobile apps interface with enterprise backend systems. It reduces the amount of custom coding needed for each device and each application.-----Provide Data AccessIdentifying data from various sources of the backend system, Extending or creating new set of format for the mobile devices, and data handling based on the various locationWrapper services or web services, it plays major role for enabling enterprise applications on the mobile devices. Providing authorized access and identifying the need for offline storages and synchronizationEnable Service AccessEnabling Business logic specifically meant for mobile devicesEnabling various level of data bindingsEnterprise Meta Datataxonomists, librarians, and administrators to create and manage terms and sets of terms across the enterpriseMEAP ( Mobile Enterprise Application Platform)Developing composite Applications Landscape and devicesMobile Device ManagementPhased approach for Common Services and Mobile ApplicationsWhy MEAP is important ?To develop, manage and deploy the mobile applications for multiple platforms, it is also useful in Mobile Data Management and Data Synchronization for both offline and Online mechanism. Each MEAP consists of standard set layers and development environment to manage the components and support secure channel of data and its resources for variety of mobile platforms.Providing a solution for designing, deployment and managing high level of security for the mobile enterprise applications should have comprehensive strategy that incorporates the secure connectivity, proper authentication, access permissions, data confidentiality and so on. In addition to the facilities, the audit report, logging, mobile device management will be key considerations for enterprise mobility.
• #17: Let’s cover now an application TechEndeavour is developing that exemplifies why backend integration is so important.
• #18: This app is being developed by a medical equipment manufacturer. This is one of the largest mobile application being developed for the iPad for field sales. The challenge is to see how sales guys can get access to the latest product knowledge for thousands of product and this information is accessible while on the road and this information remains secure on the iPad and during transmission as we mentioned before.This sales briefcase is on the ipad and integrates to multiple backend systems for manufacturing, marketing, inventory, sales and accounting - all being done in a secure manner. This iPad is always up to date with the latest product prices and availability giving the sales person the ability Act On the data immediately at the client site to increase sales.
• #20: A question you may have in your mind is - what happens if a sales guy looses his iPad or it’s stollen? Well this is where the Techendeavour strategy covers “mobile device management’. in this case you want to actively monitor and manage the devices in real time. You want the ability t remotely lock or wipe or kill the device.On a more practical day to day level you simply want to remotely update the apps - over the air. OTA.Other aspects of MDM is provide data specific to a person based on their GPS location as well as help you locate the device when it’s misplaced.FInally - there are other issues in your strategy to consider - for example is the device company owned or user owned. You may define different use policies and administration policies based on ownership. This is all part of the interview process you go through when developing a mobile enterprise strategy.
• #21: I realize there is a lot here for you to take in - The slide describes the process of how MEAP works - remember MEAP is a common interface for the enterprise to have a more consitent way of interface with multiple kinds of mobile devices and mobile apps that reach into different servers behind the fire wall.This is Endeavours understand of the various touch points - they will explain this in more detail during a strategy session and of course if you have a specific question about this for you company please bring this up at the end of the webinar. We’ll be happy to spend more time here.------------------------------This slide describes the process of MEAP. How MEAP works.The above mentioned components are interrelated and the physical deployment of the components will be different from that depicted. Some components may be divided into more granular sub-components and some may be combined within a single software block. The components of Custom MEAP are detailed in the following sections.Data Connectivity Layer Data Connectivity Layer will manage and abstract the data connectivity with the backend of K-C IT infrastructure. This layer will have two major components:The Enterprise Data Provider component of the Data Connectivity Layer will provide an interface that will interact with the backend services and data stores to fetch and update data. On the other hand, the Data Provider will expose itself to the other components of the MEAP and service their data needs. The Enterprise Meta Data ServiceThe Data Connectivity Layer will maintain meta-information about the source and format of the data being accessed. The Mobile Application LayerThe Mobile Application Layer will contain the business logic components of MEAP. It will consist of Enterprise Libraries, Mobile Server Components and Applications, Common Services, and a Mobile Rendering EngineCommon services are consumed by server- and client-based mobile applications. Common services also include interfaces using which external components can interface into the Mobile Middleware. These services implement and provide a set of common functionalities. Enterprise Library will contain reusable components that will be available to both mobile web applications and mobile applications developed on one or more platforms (BlackBerry / J2ME / iPhone / Windows Mobile).The Mobile Rendering Engine will be a component that would be used to render specific content for multiple device and delivery methods. In general, it would transform services and data for consumption by mobile devices.Connectivity ServicesProviding different communication means such as Wi-Fi and GPRS /3G data services to connect to corporate network .
• #22: So as you might expect if you’re going to make a significant investment in buying and support mobile devices and their enterprise accessing applications - there are some significant Business Challenges to tackle. We refer to this is MDM.MDM is Mobile device management software for enterprise tracks, monitors and manages devices across Wi-Fi and cellular networks with any mobile OSThe key points to keep in mind are:Software Distribution — The ability to manage and support mobile application including deploy, install, update, delete or block.Policy Management — Development, control and operations of enterprise mobile policy.Inventory Management — Beyond basic inventory management, this includes provisioning and support.Security Management — The enforcement of standard device security, authentication and encryption.Service Management-- here you want to think about telecom expenses and the IT teams to adminster the day to day management of the networking costs, inventory costs and so forth. You want a good handle on these costs to stay within budget constraints.---------------------TEM : Telecom Expense Management helps the IT teams to streamline the administration and day to day management of their telecommunications and networking costs, inventory and estate. The most common telecom activities are deployed by businesses to identify and remove costs from their telecoms budgets.
• #23: This is an example of a PC that provides a more unified view (think Dashboard) on mobile policy management and operation management. This app gives you the ability to monitor use, access and costs along with remote access to the devices when needed. From an enterprise perspective you want something like this to update or delete applications OTA over the air versus leaving this to the users, adjust performance, manage information from crashes. You want consistency in the way these things are handled so communication with mobile devices is done by policy management as we mentioned earlier.==============================Endeavour has been involved in developing an application that provides mobility service monitoring, automated policy management, guaranteed expense reduction software and services and advanced device security and communication encryption systemThis slides provides brief information on the integrated software framework and Dashboard view of the application.This application leverages our multimodule , integrated proprietary software framework to deliver customised solution to Enterprise, government & consumer oriented client and operation world wide.
• #25: Here is something to keep in mind - an enterprise application store has a completely different agenda (in most cases) then the kind of application store you’re familiar with for Apple, Android and RIM devices. There are stricter security standards to follow for one but less obvious are issues like differences in screen parameters and memory sizes and processing power for enterprise apps running on multiple devices. Besides platform diversity you may need to consider variations of the same app for different users - a light version versus a full version and some apps may be only used on the enterprise internal LAN others might be used over the Internet. You may need to consider regional differences in the world that impact how the app is made available in the enterprise app store. It’s just not as simple as you might think at first.Stricter Standards for Public storesHardware diversity, such as differences in screen parameters (size, color depth, orientation, aspect ratio), memory size (heap, persistent), processing power, input mode (keyboard, touch screen, etc.), Software diversity:Platform diversity, such as differences in platform/OS (Symbian, Nokia OS, RIM OS, Apple OS X, PalmOS, Mobile Linux, Android, BREW,etc.), API standards (MIDP 1.0, MIDP 2.0, etc.), optional APIs, proprietary APIs, variations in access to hardware (e.g., fullscreen support, access to local storage),  and differences in multimedia support (e.g., codecs), maximum binary size allowed, etc.Implementation diversity, such as quirks of implementing standards (different interpretations of the standards, bugs, etc.). Incidentally, fragmentation resulting from implementation bugs/quirks is one of the most tiresome type of fragmentations, according to practitioners.Feature variations, such as light version vs full versionUser-preference diversity, in aspects such as in language, style, etc., or accessibility requirementsEnvironmental diversity, such as diversity in the deployment infrastructure (e.g., branding by carrier, compatibility requirements of the carrier backend APIs, gateway characteristics, opened ports, restrictions on access to outside the network etc.), locale, local standards.
• #26: We’ve been touch on various app distribution issues in the previous slides. When you develop your enterprise strategy you need to carefully consider a number of issues that impact How you distribute the app. As the bullet items indicate you need to consider all these things so you know you have your basis covered. You cannot assure success unless all of these are discussed at length. It might not make sense it first for a single app but remember what you want to think about is a strategy that extends out over a couple of years and you can imagine how mobility will increase the next 24 months.(I’ll briefly mention each bullet item again)
• #28: Undoubtedly you know that any mobile strategy must heavily consider the nature of the target audience. What are the different profiles of use? For example if you’re developing an app for the airline industry - the app will work one way for the cabin crew that is pressed for time and needs minimal clicks - versus - the maintenance crew that needs to be extremely thorough with every maintenance single step being carefully documented - hence requiring more detailed data entry. As you also can imagine - consumer apps are more like a ‘one size fits all’ design. But in the enterprise you will need to adjust the UI (sometimes dynamically based on user profiles and use policies) to fit the different needs based on your roll in the company.
• #30: This slide highlights the phases of approach that Endeavour takes to Analyze, Plan and Recommend strategies to various Enterprise. It distinctively talks about how as first step Endeavour tries to understand the Goal of the organization, the people and the different processes followed by the particular organization. Once the organizational environment is understood Endeavour plan out the various factors and based on the understanding and analysis a strategy is mapped out and recommended to the Organization.