Catching the mobility wave
Keith Sherringham, Information Age
10/04/2008 15:25:32
The Internet wave that swept through business will be seen as a ripple in a pond compared to the changes which will result from the adoption of mobile business.
Although some businesses are starting to offer mobile services and others are preparing for mobility, many are still formulating the strategies and coming to grips with the necessary processes and infrastructure changes to support mobile business. Irrespective of business or industry sector, some common challenges are seen.
Driven by business for business
The integration of mobile business into business, including the delivery of services to mobile devices, is a business operation and not an information communication technology (ICT) activity. Unlike the initial adoption of the Internet and Web sites that were often driven by ICT, the strategic businesses are driving the adoption of mobility by the business for the business. The fact that changes in ICT are required is a consequence of the process and not the driver of the process.
Like the adoption of the Internet into business, the extent of services that need to be mobile enabled is approximately the same as those that were in need of Web enabling. Similar to the adoption of the Internet, the integration of mobile business will be a phased implementation according to pragmatic business need, the ability of the business to manage the change and the time it takes to optimise ICT necessary to support mobility.
Mobile business, as with the use of the Internet within business, can be used to provide services on behalf of the business to external parties as well as optimising operations within a business. Although different strategies and priorities are needed to meet the varying mobile business needs, there are some core elements that are required for effective and efficient service delivery on mobile devices.
Mobile business strategy
Like the initiation of any other services and business changes, an effective strategy with a clear business case and well-defined expectations and outcomes is required. For external customers a phased approach of alerts and messaging may be provided first.
Then additional services for simple transaction processing and validation support can be made available next. A focus on the provision of business critical information may also be a priority.
As the capability of the business to provide and support mobile business grows, more complex processes can be supplied. For internal needs, access to contact details on any device anywhere anytime may be the initial requirement followed by the capabilities of ordering, purchasing and invoicing. Messaging alerts and information access may come next, with support for advanced transaction processing subsequently.
Irrespective of the business, best results are likely to be seen from mobile business through the adoption of a pragmatic business approach with a proven business case to lower costs or grow revenue. This way, business can avoid the excesses and mistakes seen in the dotcom era.
Screen size
A key feature of the mobile device is the screen size. Although the screen of a mobile device is often less palatial than that of the desktop, this is actually an advantage to business and screen size should not be seen as a barrier to the provision of mobile business services.
The small screen of the mobile device makes it difficult for people to manage information on the device; that is, the information needs to be sorted and organised before it can be delivered to the mobile device. The large screens of the desktop perpetuate the need for people to have advanced skills in information management (versions, locations, formats and applications) to complete their job when there is no need for it to be this way.
The small screen of the mobile device also drives a greater adoption of standardised process. By presenting the right information at the right stage in the process to achieve an outcome, users on mobile devices are delivering results and not spending their time searching and trying to define and remember processes, as occurs at the desktop. Again, the large screens of the desktop often perpetuate inefficiency.
For a user to work effectively on a mobile device, the rendering of data needs to be in the context and tightly integrated with workflow.
The small screen of the mobile device will also drive more effective design in applications and user interfaces. Ultimately one common interface shall exist on both the mobile device and the desktop with all of the advantages this brings the user.
Realising the changes necessary for mobile business may take some time and some innovative thinking, but overall it is likely to drive significant business improvement as well as creating mobile business opportunities.
Process changes
Aligned with the screen size of the mobile device are the changes to processes necessary to support mobile business. The changes brought by mobile business occur not only in how the business operates and in the processes to support mobile business but also in the detail of the business processes and transaction processing itself.
When mobile is enabling a process, inefficiencies within current business processes may be highlighted and need to be changed as well as altering the process to span mobile devices.
When changing processes to operate on mobile devices, the following issues needed to be addressed:
» How will this process continue if connection to the network is lost?
» How will this process work if there is no access to the network?
» How will this process continue when connection to the network is resumed?
Proven business experience shows that these issues need to be addressed from a business, a process and a technological perspective if mobile business is to be effective. These issues will impact upon the solutions implemented, the offering, the cost and time to market.
Authentication
Although authentication (user access) may appear as a slightly more technical issue, the definition of mobile business services to be provided will significantly affect the authentication solution used, with a subsequent impact upon cost and time to deploy.
For transactions and payments a higher level of authentication and security is often required. Effective authentication may include:
» Enter user name and password for a service; for example, banking.
» You are then called on the listed mobile device to advise that access is required.
» You are then prompted to key in a PIN in real time that is validated before approval is provided.
Not only does this approach mitigate risk (need user name and password, the listed mobile device and a PIN) but it provides a level of security not achieved through SMS. SMS is suitable for alerts and messaging but is not preferred for transaction authentication.
Authentication at the transaction level, the application level, the device level and the network level may well be required. Resolution of authentication is key to solution design with an impact upon cost, offering and time to market.
Mobile device management
Management of the mobile device has several business impacts that need to be addressed for the effective provision of mobile business services. When providing services to external customers, a business has little control over the mobile devices used and supporting multiple devices, multiple systems and multiple applications is just the cost of doing business.
For services within an organisation, all of the advantages from mobile device standardisation can be realised. A standardisation of the mobile device lowers the cost of deployment, maintenance, support and administration of the device, the services provided, the applications used and the support provided. Any effective mobile business strategy would include a standardisation of the mobile device and, where required, a standardisation of the desktop environment with all of the resulting impacts upon ICT.
Realising mobile business shall see the deployment of effective solutions (technology and processes) for:
» Asset management: the mobile device is an asset of an organisation and like any other asset, its existence, occurrence and value need to be tracked and managed.
» Device tracking: mobile devices are by nature prone to being lost and/or taken out of an organisation. Some form of device tracking solution is required.
» Device administration: solutions are needed for the administration of the mobile device including its initial and ongoing configuration, operating system and application deployments, and upgrades and updates.
» Standalone operation: issues around a mobile device working as a standalone as well as getting its updates when connected to the network need to be addressed.
» Data synchronisation: solutions for the synchronisation of data between the mobile device and the original data source are required. This is to include versioning, shared access and concurrent usage.
Data management
Although the significance of screen size on a mobile device in impacting data management requirements has already being noted through the need to get data organised with workflow before rendering to a mobile device, there are other aspects of data management that directly affect any mobile business implementation.
Current mobile devices are not suitable for long-term data storage. Although the capacity to store data is likely to increase, any good mobile business strategy and implementation should assume that extended data storage on the mobile device shall not occur. Some short-term storage is obviously needed but a "no data storage on mobile device" strategy is the preferred approach.
The business importance of "no data storage on mobile device" is further seen when all of the issues of trapping and the isolation of data on the desktop and the resulting business issues are considered.
Effective and efficient mobile business requires that data are single sourced from virtual consolidated repositories. The use of "virtual consolidated data repositories" complements the "no data storage on mobile device" solution. These two fundamental principles are essential to any mobile business strategy with subsequent impacts upon processes, services, deployment times and costs.
The demands of mobile business will further drive the ever increasing demand for disk space storage. The use of virtual consolidated repositories for single sourcing data and the need to record many of the transactions and messages being sent to and from any device anywhere anytime are key elements of the demand.
Other significant demand will come from data streaming, video-conferencing and messaging, images and file sharing - all driven by the needs of mobile business.
The synchronisation of data between mobile devices and repositories poses several issues and resolution of synchronisation is key to services that require a "write element". Since data synchronisation is less of an issue for broadcast and query services, many mobile business strategies and implementations would probably see these types of services provided first.
All of these data management issues impact upon the decisions for mobile business on what services to provide, at what cost, and in what time frame.
Messaging environment
As increasing demands are made of mobile business, the need for a consolidated messaging environment that guarantees service delivery comes to the fore. The model for this environment is the FedEx model. FedEx guarantees the delivery of parcels and mail (messages) as follows:
» There is a quality of hand-off to FedEx and without this quality of hand-off, the parcel is not taken, that is, responsibility is at source and exception processing returns the package to source.
» FedEx has a scalable, reliable, industrial strength solution for the transfer of packets between defined points.
» There is a quality of hand-off from FedEx back to the customer for acceptance of the package.
» FedEx separates the acceptance, moving, storage and hand-off of the package. FedEx then has systems for error handling, reporting and archive of information.
» The environment and operations are standardised.
Whilst the parallel between the FedEx model and what is required of a messaging environment is self-evident, it is the impact of the absence of a consolidated messaging environment that affects mobile business in terms of cost, time to market and services that can be provided.
Applications
Although many core business applications have now been successfully Web enabled, mobile business will bring some additional challenges. The importance of the mobile device screen size in changing the user interface has already been noted and the demands of the user interface will be one of the key issues in determining how quickly services can be brought to market at what cost.
In addition, many applications have been written from a features perspective assuming the much larger screen size of the desktop. Conversely, the user of the mobile device does not have the time or the screen size to use features and the focus is on processes to achieve an outcome.
For effective and efficient mobile business, applications will need to move from being feature-rich to process-driven. Again, this change impacts upon what mobile business services can be offered at what cost in what time frame?
Security
The security issues around mobile business and mobile devices just add to the already complex security needs seen within business. Suffice to say, mobile business services can only be provided once they are secure. This affects cost, service offering and time to market.
Audit and compliance
The audit and compliance needs for business vary but in some instances, it will be necessary to record and keep a copy of the messages and authentications used for mobile business for a period of time. In addition to the design considerations and disk space demands, mobile business can raise various privacy issues. All of these issues affect what mobile business services are offered, at what cost, in what time frame?
Enterprise architecture
From all of the elements (screen size, process, authentication, device management, data management, messaging, applications, security, and audit and compliance) can come an assessment of the ability of an enterprise, its architecture and its ICT infrastructure to deliver mobile business. This assessment will in turn impact upon the business decisions of what mobile business can be deployed, when, at what cost and in what time frame?
If the infrastructure and solutions provided by ICT is highly standardised and is currently an effective assembly line for knowledge workers, then your business has a competitive advantage and can readily adopt mobile business. The inability of ICT to deliver the knowledge worker assembly line may be a significant barrier to what mobile business can be readily realised.
Business integration
Just as it is with Web enablement and the deployment of any new ICT solution, it is all about the business integration and business change. Mobile business will be no different. Common elements include:
» Optimisation of process: resolution of the new processes and how business will operate.
» Business logic: resolution of the business logic required to ensure the functioning of mobile business.
» Data management: addressing the data management issues necessary.
» Training: training of all relevant parties.
» Support: the support infrastructure provided to staff and customers to support mobile business.
» Performance: realising the promised cost savings or revenue opportunities.
» Communication: communication to all relevant parties on what is happening, how it is happening, the benefits and how to do things.
Moving forward
Like the Web enabling of business, mobile enablement will provide business with many challenges and significant rewards. Just as the Internet is now integral to business, so will it be with mobile business. The main driver in the adoption of mobile business is likely to be the benefits derived from routine transaction processing accompanied by the need to support an ever-increasingly mobile workforce collaborating in virtual teams.
The adoption of mobile business is likely to occur incrementally with set outcomes being delivered and realised, which will then drive a greater adoption of mobile business and the provision of more services in a self-sustaining process.
Once a strategy and vision for an organisation has been set, key projects are likely to be initiated that shall drive out the issues associated with mobile business and lay down key infrastructure that other projects can leverage.
Any mobile business strategy needs to tightly integrate data with workflow and use the "no data storage on mobile device" and "virtual consolidated data repositories" approach. For best results, mobile business shall be driven by the business for the business and in the process, realise much needed change in the way ICT is implemented, managed and adopted by the business.
[ Printer Friendly Version ]
[ Other stories about FedEx, ProVision, Provision ]
|