News

See Also

Deploying Mobility Solutions

Overview

As the mobile computing industry evolves it becomes more complex in terms of functionality offered and as a result, mobility customers are looking to do more than simply purchase software.

Key to the successful deployment of a mobile solution is the automation of current business processes in a way that optimises field operations and provides users with the data they require to complete their job in a useable format and in the right context.

These requirements have seen the emergence of Whitesmiths Mobility Development Process, which covers the gaps that existing ERP/CRM/SFA and Supply Chain offerings fail to address. These specific business process constraints reduce the benefit of mobilising field operations for a lot of organisations and it is through the use of Whitesmiths Mobility Development Process that these gaps can be closed.

The Whitesmiths Mobility team know that in the end it is all about understanding customers business processes, their challenges and difficulties experienced with their current processes. It is about defining ways of using mobile computing to relieve existing process difficulties, bottlenecks, etc and enhance the current business process and it is about delivering a solution not only on time and within budget but more importantly – it is also about delivering the proposed benefits.

Whitesmiths Mobility Development Process is a phased approach that is designed to deliver mobility applications that assist and enhance the entire customer experience.

Inception

This phase of a Mobility project is designed to ensure that sufficient information is available for all parties (the customer and Whitesmiths) to be confident that a mobility solution will meet the needs of the customer.

The basic objectives of this phase are to:

The Inception Phase is designed to identify the customer’s field force business model and introduce the customer to the Whitesmiths Mobility process.

This phase typically takes 2-4 weeks to complete, with all parties actively involved in the process. A joint study is often conducted during this phase and involves the project team and sponsors working through to determine the business needs and value drivers related to the mobility project. This effort identifies the high-level design aspects of the mobility solution that will deliver rapid time-to-value.

Elaboration

The Elaboration Phase, the second of the four phases, and baselines the requirements, resulting in a clear Solution Design and document agreed functionality in a Functional Specification.

A Requirements Workshop is conducted early in this phase, which further assists the customer to identify key business processes for mobilisation. Participants will define the business processes that will be supported by the mobility solution as well as the information/data required to support the application. Additionally, participants will also identify specific success criteria including metrics and methods of measurement.

The duration of this phase is dependant upon both the number of requirements and complexity of the solution required, as well as the availability of customer resources for workshops, etc.

Construction

The Construction phase commences once the functionality has been agreed by all parties and is typically the most time-consuming phase of the project.

The focus of this phase is on developing a cost-effective and high-quality application that is operationally ready for deployment to the user community. This phase includes development, system testing and user acceptance testing, including any iteration required to achieve acceptance of the application.

Transition

The final phase commences following acceptance of the developed application by the customer via the UAT process. This phase involves the deployment of the solution, tuning the applications performance parameters and any minor bug fixing. Throughout the Transition phase, users are trained, system administration functions are handed over and if required, a pilot is conducted.

It is during this phase, that final stakeholder acceptance as well as all deployment baselines are complete and consistent with the initially agreed project scope.

The duration of this phase can vary, depending upon availability of production systems and length of any pilot. However, typically this phase can be completed within 1-2 weeks.

End of content
Return to top © 2005 Whitesmiths Ltd. Site Map