Business Analysis

To successfully deliver a Microlise Transport Management Solution to our customers, it is absolutely imperative that we have a clear understanding of how the operation works, what its business goals and objective for the project are and what the system needs to do to deliver benefit to our customer’s business.

In order to capture all of this information in as timely, efficient and accurate manner as is possible, Microlise – as their Fleet & Distribution platform has evolved, have developed a Solution Business Model process to accomplish this.

Using the Solution Business Model process and documentation templates, Microlise have transformed what was an often laborious “ground up” process into a slick, “gap analysis” based approach.

The Solution business model document templates, which are updated in line with each product release – takes the customer, supported by a Microlise Business Analyst through a standard set of steps – which capture the following information:

Customer Business Overview

- What the customer does, where, for whom and how it is organised, paying particular attention to its transport and logistics function.

Project Goals

- What is the system seeking to accomplish / improve within the operation

Functional requirements

- Solution and whether this is configuration based or will involve customisation

This latter set of steps represents the lion’s share of the document and the process – each requirement is defined in terms of a system or operational function, this will be validated, added to and the Business Analysis will determine whether this can be met simply through system configuration of if custom development is required.
For a “standard” tracking, telematics and Transport Management Centre implementation, this whole process can be wrapped up in half a day. The levels of consequent accuracy and reduced ambiguity is markedly improved. This document, once signed off then becomes the standard reference through the whole implementation, configuration & customisation and training process.
Crucially, the SBM has a section which very clearly sates any assumptions, risks or unknowns which are referred to and addressed throughout the specification process it’s subsequent sign off and any downstream implementation.
 

The completion of the Solution Business Model template is usually embedded in a larger requirements capture process which will include customer workshops to review and sign off the requirements, as well as a formal estimation process within MIcrolise around any custom changes.

This method and its role in the broader implementation process, is summarised further in the Implementation section.

contact us button