Enabling Enterprise Mobility
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Enabling Enterprise Mobility

  • 1,413 views
Uploaded on

Transform the mobile computing environment

Transform the mobile computing environment

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,413
On Slideshare
1,413
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
58
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Enabling Enterprise MobilityWhite paper transform the mobile computing environment. As we enter the second decade of this millennium, a rapidly changing technology landscape is propelling a hyper-competitive environment and moving us to an inter-connected world.
  • 2. Table of contentsEnabling Enterprise Mobility. ......................................1Step 1—Review, establish, and refinefoundational policies.................................................2Step 2—Define the collaboration infrastructurefor the organization..................................................3Step 3—Establish the architecture to supportenterprise-class mobile applications. ...........................4 .Conclusion..............................................................5About the author......................................................6
  • 3. Technology is pervasive and easily accessible inall aspects of our daily lives. Consumers are morecomfortable with technology, social networking,and cloud-based services in their personal lives,and they expect the same always-on experiencein their professional lives. This trend is commonlyreferred to as the “consumerization of IT,” and itrepresents the growing expectations of customersand employees to use consumer-orientedtechnologies and solutions such as smart phones,video, audio, social networking, micro-blogging,and universal access from their employers andbusiness partners. The ubiquitous nature of mobile computing and the Finally, IT organizations will also have to deal with blending of personal and professional lives provide changes to their financial model as this environment unique opportunities for today’s businesses and their forces them to rethink their end-user computing models IT organizations. They can grow market share, build (what devices, how many, and who pays for them) customer intimacy, and increase profit margins by and the associated support models, such as help desk delivering secure, seamless, context-aware experiences or break-fix. in a connected world. This new emerging environment In short, the consumerization of IT will require businesses provides endless possibilities—but it also brings with to plan for, develop, and operationalize a comprehensive it some unique challenges around security, privacy, approach for enabling Enterprise Mobility. speed-to-market, and the increased costs that come with the task of supporting more choice in devices. Enabling Enterprise Mobility Traditionally, IT organizations have focused on driving HP’s approach to enabling Enterprise Mobility is efficiencies through standardization, control, and ideal for organizations across all industries who wish the eventual commoditization of IT services. In this to reach their constituents across multiple networks emerging workplace, they will have to deliver their and devices by delivering applications, content, and application and services in an environment where the services in a scalable, secure, and reliable way. This boundaries between personal and professional life are approach leverages our global applications services blurred and where they do not control the technology capabilities to provide the architecture, systems stack used by their users. This new mobile computing engineering, development, and support services. environment has to address device and network Combined, they help an organization simplify its security, as well as privacy issues associated with applications, extend them where necessary, and having personal and company-owned data on the build innovative mobile business-to-business (B2B), same device. This is true whether the device is owned business-to-consumer (B2C) and business-to-employee by the individual or the enterprise. (B2E) applications. This approach also leverages HP’s well-defined and mature, service-oriented 1
  • 4. Figure 1Figure text describes illustration contents. Internal IT Visualization Testing and Mobile Mobile applications and QA for Application Integration Information Mobile Architecture Architecture Architecture Applications Applications written by employees Collaboration Services— email, calendar, instant messaging Enterprise Application Store Infrastructure Design and Security Application provided by Mobile Deployment Architecture software vendors Information Enterprise End-User Security Policies Privacy Policies Computing Policyarchitecture-based integration architecture and is done on an enterprise-owned asset (such as a PC orenabled by development and security frameworks BlackBerry) and how to handle consumer data. Theythat helps create componentized building blocks also drove an end-user computing model that usedfrom monolithic legacy applications to develop and encryption with very strong password protection anddeploy mobile applications that are Designed for in many cases, two-factor mechanisms to control howRun™. Our methodology goes beyond cool devices employees get access to the company’s applicationsand flashy user interfaces: It requires a thorough and and data. This highly standardized end-user computingcomprehensive look at how mobile applications are model made support processes simpler and the testingdeveloped, deployed, managed, and governed in and deployment of applications to these devices easier.mid-sized and large enterprises. In the new mobile world, every one of these policies isOur process has three primary steps. The first step more complex. The safeguards that worked well in alooks at foundational enterprise-wide policies around tightly controlled environment are now inadequate tosecurity, privacy, and end-user computing. The second address the risk posed by the use of personally ownedstep assesses the collaboration infrastructure that mobile devices and anytime, anywhere, network access.needs to be established to support mobility. And This is why it is extremely important that organizationsthe final step evaluates the end-to-end architectural address these policies first before embarking on thedecisions, application, and infrastructure models that journey of enabling enterprise mobility. Some of theare required to enable enterprise mobility. key questions that HP will help clients answer are: • Who owns the device—company-owned vs.Step 1—Review, establish, and refine personally owned device?foundational policies • How does the enterprise address the risks of havingInformation security and privacy policies in today’s company-owned data on a personally ownedorganizations were written for a highly controlled and device, and conversely, how does the enterprisemonitored computing model where individuals relied protect the privacy of the employee’s data on aon companies to provide computing capabilities and personally owned or company-owned device?network access. In that world, policies were simple • What kind of security can an enterprise enforce on aand sometimes onerous in managing what could be personally owned device—password, encryption, etc.? 2
  • 5. • How does the enterprise or HP monitor mitigate the Additionally, HP’s mobile development framework risk of the employee losing the device? supports all common ways to create applications• Who pays for the device and the access—will the targeting the mobile devices. These include: employee buy it or will the company provide a • Web sites optimized for the mobile form factors stipend and how often? • Use of cross platform development tools to efficiently• How will the company support the device when the target multiple platforms device fails or when the user has a device that the • Pure native development for cases where there is a company does not have skills to support? single target platform• What are the impacts to the operational expenses • Rich Internet Applications for apps that require rich of organizations as they move to this new end- media support user computing model—one that provides more • Use of a mobile enterprise application platform choice and contains a mix of company-owned and where multiple back-end data sources must be employee-owned devices? accessed in addition to multiple client support • Mobile business intelligence and content portal clientsStep 2—Define the collaborationinfrastructure for the organization In short, HP’s development frameworks and capabilities support creation of a wide variety ofThe second step of HP’s approach to enabling mobile content in an efficient way.Enterprise Mobility involves establishing a solidinfrastructure that supports enterprise-class mobile Network and security architectureapplications. This includes the: The network architecture, including firewall rules and• Deployment model for mobile applications network security, in most organizations was defined to support web-based applications. Building web-based• Network and security architecture applications allowed organizations to establish zones• Collaboration infrastructure for the enterprise. of defense—in other words, these architectures defineDeployment model for mobile applications on perimeter-based defense structures that were “hardDecisions around the security and privacy policies on the outside and crunchy in the middle.” Thiswill end up driving the deployment model for mobile network architecture is no longer adequate to dealapplications within the enterprise. with employee-owned mobile devices that can potentially access an organization’s core network behind theBasically, there are three types of deployment models corporate firewall. Changes to the network architecturefor native mobile apps: should be driven by the following questions:1. Applications are deployed to the native environment • How would a user access company-owned of the device. It has access to all the resources on applications and data from home or from a public the device and is constrained by the capabilities of access point to the Internet using a personally or the device. company-owned mobile device?2. Applications are deployed into an encrypted • How would a user access company-owned container on the device. It has access to selected applications and data from within the walls of capabilities and resources from within the the enterprise (intranet) with a personally owned container on the device. mobile device?3. Applications are deployed to the device using • How does the enterprise manage and control access a thin client. It has no access to the computing to internal and external application stores? resources on the device. These applications leverage the capabilities on the server they run on and render the UI to the mobile device.Selecting the deployment model for mobileapplications is one of the most critical decisions ofenabling enterprise mobility. 3
  • 6. Collaboration infrastructure for the enterprise client/server and web-based applications. It’s a shiftThis model is the third critical component in defining the from applications that were designed to sense andcollaboration infrastructure of the enterprise. It focuses respond to individual events to one that has to handleon workplace capabilities such as email, instant more complex events that enable enhanced realitymessaging, micro-blogging, and social networking experiences. For example, a user who is new to aand is heavily influenced by the enterprise security certain part of the city can point her smart phone torequirements. It also presents some unique challenges the street on which she is standing. The banking apparound document retention, as enterprises need to on her phone will map the nearest locations of ATMmaintain their ability to track use of corporate assets machines and bank branches and visually highlightwhile respecting the privacy of the individuals. them on the screen image of the street. Apps in the mobile environment also need to adapt newStep 3—Establish the architecture models for visualizing data. This takes advantage of theto support enterprise-class mobile unique hardware and display capabilities of these newapplications mobile devices to provide context-aware experiences. Features range from the “pinch” to zoom-in and out ofHP will use the organizational decisions around the an image to visual representation of complex data usedthree foundational policies established in Step 2 to in business intelligence and analytics applications tohelp the enterprise develop and implement the other enhanced reality applications highlighted earlier.four key components of enabling Enterprise Mobility:• Mobile Application Architecture Integration Architecture It is also important to remember that enabling enterprise• Visualization and Information Architecture applications is about more than the application• Integration Architecture architecture. It requires the rethinking of the integration• Testing and Quality Assurance for Mobile architecture used by the organization. Some of the key Applications elements of the new integration model are:Mobile Application Architecture • A move from traditional EAI (Enterprise ApplicationOne of the major shifts driven by mobile applications Integration) approaches that relied on complexhas been the demise of monolithic solutions built transactions to one that relies on micro transactionsaround a particular business process that are loaded built on lightweight services such as Representationalwith features and functions for a wide range of users. State Transfer (REST). This supports smaller appsAn example is a full functioned banking website running on more powerful mobile devices with newaimed at the online user. These monolithic sites are interaction models described earlier.being replaced by multiple smaller applications • A design that can handle thousands of low latency(“apps”) that are designed around the end user. These micro-transactions as opposed to hundreds of long-new apps are built from a customer-in perspective running state-full transactions.as opposed to the company-out model that drove • The ability to interface with and process inputs fromapplication design in the past. pervasive technologies such as RFID chips, numericalVisualization and Information Architecture controls, specialized and multi-purpose sensors, andThe rich user interfaces supported by today’s mobile point of sale devices.devices are causing a seismic shift in the area of • The ability to support Complex Event Processinghuman-computer interaction. This next-generation (CEP) and real-time business event co-relation fromuser interaction model moves from the keyboard and information sources within and outside the enterprisemouse interface that has been a standard for the past using a lightweight state-less interaction model.two decades to one that processes inputs from multiple • A scalable infrastructure that can provide highdevices such as multi-touch screens, accelerometers, service levels on a 24x7 basis across the globe.microphones, cameras, GPS chips, and gyroscopes.This model represents a major evolution of the event-driven application model that was the foundation of 4
  • 7. Testing and Quality Assurance for ConclusionMobile ApplicationsBusinesses that are focused on enabling mobility Today’s “Everybody On” world is enabled by near-within the enterprise need to have an application universal connectivity options and an ever-increasingdeployment model that focuses on deploying apps choice of mobile devices that allow organizations toto personal and company-owned devices through an deliver their services (any content) at any time throughEnterprise App Store. This Enterprise App Store has to: any network. This ubiquitous connectivity is radically changing how organizations interact with their• Be able to support applications that are developed producers, partners, employees, and customers. As for and deployed to a fragmented mobile the only global provider of end-to-end services across marketplace that includes at least five major the mobile ecosystem, HP provides a unique enterprise operating systems–iOS, Android, Windows Mobile, perspective, global reach, and flexible and scalable BlackBerry, and WebOS. engagement models that allow today’s businesses to• Test applications for compatibility across multiple take full advantage of the benefits of a mobile enterprise. operating systems and devices. HP’s comprehensive approach to enabling Enterprise• Deploy applications developed by the internal IT Mobility leverages our extensive experience in organization, employees, or software providers such developing mobile applications, global development as SAP and Microsoft to all registered devices. centers, intellectual capital (frameworks and code• Support “over the air” updates for apps to assets), industry-leading mobile frameworks, and tools these devices. to provide a true enterprise-class mobile solution for our clients in all industries across the globe.• Handle remote-wipes and de-registration of devices when they are lost or compromised. 5
  • 8. About the author Srinivas (Srini) Koushik Srinivas (Srini) Koushik is vice president and worldwide application development executive for Hewlett-Packard. In this role, he ensures that HP is working with clients to provide the best possible balance of cost, speed, quality, and risk for large scale transformational programs, systems integration projects, and innovative technology initiatives. Previously, Koushik was senior vice president and chief information officer at Nationwide Insurance, a Fortune 100 financial services company. During his tenure at Nationwide, he drove the design and implementation of a cutting-edge Business Analytics environment, a first-of-a-kind banking environment based on cloud computing, a large scale transformation of the company’s infrastructure, and one of world’s first CMMi Level 3 Application Development Centers. Koushik was also previously vice president and worldwide architecture practice leader at IBM. He was appointed as an IBM distinguished engineer in 1998 and elected to the IBM Academy of Technology in 1999. Koushik has had a highly decorated career that includes being named an Elite 8 CIO by Insurance & Technology, a Top 25 CTOs by Infoworld in 2004, and one of the Top 10 All Stars in the Financial Services Industry by Techdecisions in 2007. He is also an Open Group Distinguished Certified Architecture Profession Leader. Koushik holds a bachelor’s degree in physics from the University of Madras, a master’s degree in computer science from the University of Bombay, a master’s degree in business administration from The Ohio State University, and has taken several executive education courses from both MIT’s Sloan School of Management and Duke University. Share with colleagues Get connected www.hp.com/go/getconnected Get the insider view on tech trends, alerts, and HP solutions for better business outcomes© Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The onlywarranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing hereinshould be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.4AA3-5495ENW, Created June 2011; Updated September 2011, Rev. 1