Software introduction
The introduction of new software is a challenge for many companies. The aim is to actively shape an economically viable compromise between organisational requirements and technical possibilities, to involve future users in a meaningful way and to prepare them for system deployment. This does not only apply to the introduction of transport management systems, but is especially true here, since established planning processes often have to be renewed. This means that a critical part of the company is subject to a significant change.
We meet this requirement by providing experienced transport experts in a software project who know the transport planning processes to be renewed very well. The software introduction is often preceded by a consulting project aimed at optimizing transport logistics.
The following topics are not to be understood as ranking, all topics are important.
Project management
Project management appropriate to the project is a prerequisite for a successful software introduction. When it comes to project management, we are concerned with planning and calculating the necessary activities and controlling and monitoring their implementation.
Contract
The services to be provided for both sides are clearly described and clear to all project participants. The customer knows what to expect and we know what to do.
Cooperation with the customer
On our site as well as on the customer’s site, one responsible person is appointed. These two ensure that the necessary activities are carried out on both sides in a timely and appropriate manner.
Launch strategy
A complete change-over in one step (Big Bang) is often necessary, but also has disadvantages. Experience has shown that a step-by-step introduction is manageable, reduces the stress factor for those responsible for the project and allows faster benefits in relation to the time axis.
Risk management
Drawing up a specific risk checklist at the start of the project and regularly reviewing it over the course of the project allows the planning of preventive and contingency plans (“act instead of react”).
Key User principle
Users who play a key role in the use of the software should play a key role in defining, deploying and implementing the software. Their task is to ensure that the technical requirements are met and to pave the way for acceptance of the new solution.
Data migration
The transfer of data from legacy systems to the new software is usually a complex task. In the rarest cases it is reduced to a simple provision (data export) and processing (data import). As a rule, data conversion at the logical level is necessary, often less is more!
Individual adaptations
X4fleet is a standard product, but standard back and forth — there comes a day when even the most powerful parameterization capability comes to an end and individual software adaptation becomes necessary. Examples of this are interfaces to other systems, individual document layouts, in-house evaluations and lists, special pricing procedures, and so on. We continuously ensure a transparent view and communicate when the standard is left or threatens to leave.
Open Points List
During the course of a software introduction, numerous details arise that require further processing, e. g. software errors that result in corrections, new requirements to be evaluated, ideas for improvement that can be integrated into future software releases, etc. With this list, we continuously ensure a common view of the status of the implementation.
Documentation
In the course of the introduction of software, a series of individual rules and appointments are created. We endeavour to record these in writing and make them available to us and the customer. An important element in the documentation is the JIRA, where all tasks and incidents are described and their resolution is documented. The JIRA also serves as a FAQ for the support in assessing events.