Open new doors

lowlyoutstandingMobile - Wireless

Nov 24, 2013 (5 years and 2 months ago)


Viewpoint paper
Open new
Transform to a mobile computing environment
Table of contents
1 Review the trends
1 Gain enterprise mobility
2 Step 1—Review, establish, and refine policies
3 Step 2—Define the collaboration infrastructure
4 Step 3—Establish the architecture
5 Gain connectivity
Viewpoint paper | Open new doors
Viewpoint paper | Open new doors
The consumerization of IT is growing; customers and
employees expect universal access and consumer-oriented
technology and solutions on the device of their choice.
Review the trends
The ubiquitous nature of mobile computing and the blending of personal and professional lives
provide unique opportunities for today’s businesses and their IT organizations. They can grow
market share, build customer intimacy, and increase profit margins by delivering secure, seamless,
context-aware experiences in a connected world. This new emerging environment provides
endless possibilities—but it also brings with it some unique challenges around security, privacy,
speed-to-market, and increased costs that come with supporting more device choice.
Traditionally, IT organizations have focused on driving efficiencies through standardization,
control, and the eventual commoditization of IT services. In this emerging workplace, they will
have to deliver their application and services in an environment where the boundaries between
personal and professional life are blurred, and the enterprise may not control the technology
stack used by their users. This new mobile computing environment has to address device and
network security, and privacy issues associated with having personal and company-owned data
on the same device. This is true whether the device is owned by the individual or enterprise.
IT organizations will also have to deal with changes to their financial model as this environment
forces them to rethink their user computing models—what devices, how many, and who pays
for them—and the associated support models, such as help desk or break-fix.
In short, the consumerization of IT will require businesses to plan for, develop, and
operationalize a comprehensive approach to enable enterprise mobility.
Gain enterprise mobility
Enterprise mobility is ideal for organizations across all industries that wish to reach their
constituents across multiple networks and devices by delivering applications, content, and
services in a scalable, secure, and reliable way.
Mobile computing can grow market share, build
customer intimacy, and increase profit margins
by delivering secure, seamless, context-aware
experiences; it also brings unique challenges
around security, privacy, speed-to-market, and
increased costs.
IT must deliver applications and services in an
environment where the boundaries between
personal and professional life are blurred, and the
enterprise may not control the technology stack
used by their users.
To build, develop, deploy, manage, and govern mobile applications, we recommend a
three primary step process. The first step looks at foundational enterprise-wide policies
around security, privacy, and user computing. The second step assesses the collaboration
infrastructure that needs to be established to support mobility. And the final step evaluates the
end-to-end architectural decisions, application, and infrastructure models that are required to
enable enterprise mobility.
Step 1—Review, establish, and refine policies
Information security and privacy policies in today’s organizations were written for a highly
controlled and monitored computing model where individuals relied on companies to provide
computing capabilities and network access. In that world, policies were simple in managing
what could be done on an enterprise-owned asset such as a PC or BlackBerry, and how to
handle consumer data. Policies also drove a user computing model that used encryption with
very strong password protection and, in many cases, two-factor mechanisms to control how
employees accessed the company’s applications and data. This highly standardized user
computing model made support processes simpler and testing and deployment of applications
to these devices easier.
Viewpoint paper | Open new doors
Figure 1. Steps to enterprise mobility
Email SMS Blog NetworkingCollaboration
Servers Storage Network Software InfoInfrastructure
Thin client Container Native
Mobile app
Mobile enterprise architecture platform
Mobile UE/AD/testing
App store
Step 3
Establish the architecture
to support enterprise-class
mobile applications
Step 2
Define the collaboration
infrastructure for the
End user
Step 1
Review, establish, and
refine foundational policies
In the new mobile world, every one of these policies is more complex. The safeguards that
worked well in a tightly controlled environment are now inadequate to address the risk posed
by the use of personally owned mobile devices and anytime, anywhere, network access. This is
why it is extremely important that organizations address these policies first before embarking
on the journey of enabling enterprise mobility. Some key questions to ask are:
• Who owns the device—company or individual?
• How does the enterprise address the risks of having company-owned data on a personally
owned device? Conversely, how does the enterprise protect the privacy of the employee’s data
on a personally owned or company-owned device?
• What kind of security—like passwords or encryption—can an enterprise enforce on a
personally owned device?
• How does the enterprise monitor and mitigate the risk of the employee losing the device?
• Who pays for the device and access—for example, will the employee buy it or will the
company provide a stipend and how often?
• How will the company support the device when it fails or when the user has a device that the
company does not have the skills to support?
• What are the impacts to the operational expenses of organizations as they move to this new
user computing model—one that provides more choice and contains a mix of company- and
employee-owned devices?
Step 2—Define the collaboration infrastructure
The second step involves establishing a solid infrastructure that supports enterprise-class
mobile applications. This includes the:
• Deployment model for mobile applications
• Network and security architecture
• Collaboration infrastructure for the enterprise
Deployment model for mobile applications
Decisions around security and privacy policies end up driving the deployment model for mobile
applications within the enterprise. Basically, there are three types of deployment models for
native mobile applications (apps):
1. Applications are deployed to the native environment of the device. It has access to all device
resources and is constrained by the capabilities of the device.
2. Applications are deployed into an encrypted container on the device. It has access to selected
capabilities and resources from within the container on the device.
3. Applications are deployed to the device using a thin client. It has no access to the computing
resources on the device. These applications leverage the capabilities of the server on which
they run and render the user interface to the mobile device.
Selecting the deployment model for mobile applications is one of the most critical decisions of
enabling enterprise mobility.
Viewpoint paper | Open new doors
A mobile computing environment must address
device and network security, and privacy issues
associated with having personal and company-
owned data on the same device—whether the
device is owned by an individual or the enterprise.
Network and security architecture
The network architecture in most organizations, including firewall rules and network security,
was defined to support web-based applications. Building web-based applications enabled
organizations to establish zones of defense—in other words, these architectures were defined
on perimeter-based defense structures that were “hard on the outside and crunchy in the
middle.” This network architecture is no longer adequate to deal with employee-owned mobile
devices that can potentially access an organization’s core network behind the corporate firewall.
Changes to the network architecture should be driven by the following questions:
• How would a user access company-owned applications and data from home or a public access
point to the Internet using a personal or company-owned mobile device?
• How would a user access company-owned applications and data from within the walls of the
enterprise (intranet) with a personally owned mobile device?
• How does the enterprise manage and control access to internal and external application stores?
Collaboration infrastructure for the enterprise
This model is the third critical component in defining the collaboration infrastructure of the
enterprise. It focuses on workplace capabilities such as email, instant messaging, micro-
blogging, and social networking, and is heavily influenced by enterprise security requirements.
It also presents some unique challenges around document retention, as enterprises need to
maintain their ability to track use of corporate assets while respecting individuals’ privacy.
Step 3—Establish the architecture
Organizational decisions around the three foundational policies established in Step 2 help the
enterprise develop and implement the other four key components of enabling enterprise mobility:
• Mobile application architecture
• Visualization and information architecture
• Integration architecture
• Testing and quality assurance for mobile applications
Mobile application architecture
One of the major shifts driven by mobile applications has been the demise of monolithic
solutions built around a particular business process that are loaded with features and functions
for a wide range of users. An example is a full-function banking website aimed at the online
user. These monolithic sites are being replaced by multiple smaller apps that are designed
around the user. These new apps are built from a customer-in perspective as opposed to the
company-out model that drove previous application design.
Visualization and information architecture
The rich user interfaces supported by today’s mobile devices are causing a seismic shift in
the area of human-computer interaction. This next-generation user interaction model moves
from the keyboard and mouse interface that has been a standard for the past two decades to
one that processes inputs from multiple devices such as multi-touch screens, accelerometers,
microphones, cameras, GPS chips, and gyroscopes.
This model represents a major evolution of the event-driven application model that was the
foundation of client/server and web-based applications. It’s a shift from applications that were
designed to sense and respond to individual events to one that has to handle more complex
events that enable enhanced reality experiences. For example, a user who is new to a certain
part of the city can point his or her smartphone to the street on which she is standing. The
banking app on her phone will map the nearest locations of ATMs and bank branches and
visually highlight them on the screen image of the street.
Apps in the mobile environment also need to adopt new models for visualizing data. This takes
advantage of the unique hardware and display capabilities of these new mobile devices to
provide context-aware experiences. Features range from the “pinch” to zoom-in and out of
an image to visual representation of complex data used in business intelligence and analytics
applications to enhanced reality applications highlighted earlier.
Viewpoint paper | Open new doors
Integration architecture
It’s also important to remember that enabling enterprise applications is about more than the
application architecture. It requires the rethinking of the integration architecture used by the
organization. Some key elements of the new integration model are:
• Traditional enterprise application integration approaches that relied on complex transactions
move to one that relies on micro-transactions built on lightweight services such as
representational state transfer. This supports smaller apps running on more powerful mobile
devices with new interaction models described earlier.
• A design that can handle thousands of low latency micro-transactions as opposed to hundreds
of long-running state-full transactions.
• The ability to interface with and process inputs from pervasive technologies such as RFID
chips, numerical controls, specialized and multi-purpose sensors, and point-of-sale devices.
• The ability to support complex event processing and real-time business event co-relation
from information sources within and outside the enterprise using a lightweight state-less
interaction model.
• A scalable infrastructure that can provide high-service levels on a 24x7 basis across the globe.
Testing and quality assurance for mobile applications
Businesses that are focused on enabling mobility within the enterprise need an application
deployment model that focuses on deploying apps to personal and company-owned devices
through an enterprise app store. This store has to:
• Support applications that are developed for and deployed to a fragmented mobile
marketplace, and should at least include the five major operating systems—iOS, Android,
Windows Mobile, BlackBerry, and WebOS
• Test applications for compatibility across multiple operating systems and devices
• Deploy applications developed by the internal IT organization, employees, or software
providers such as SAP and Microsoft to all registered devices
• Support “over-the-air” updates for apps to these devices
• Handle remote-wipes and de-registration of devices when they are lost or compromised
Gain connectivity
Today’s world is enabled by near-universal connectivity options and an ever-increasing choice
of mobile devices that enable organizations to deliver their services (any content) at any time
through any network. This ubiquitous connectivity is radically changing how organizations
interact with their producers, partners, employees, and customers. Take full advantage of the
benefits of a mobile enterprise and build the necessary foundational enterprise-wide policies,
assess the collaboration infrastructure needed, and evaluate the architectural decisions,
applications, and infrastructure models required for success.
Viewpoint paper | Open new doors
Rate this document
Share with colleagues
Sign up for updates
Viewpoint paper | Open new doors
© Copyright 2011-2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only
warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein
should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft is a U.S. registered trademark of Microsoft Corporation.
4AA3-5495ENW, July 2013, Rev. 3