Select Page

Software introduction

The intro­duc­tion of new soft­ware is a chall­enge for many com­pa­nies. The aim is to actively shape an eco­no­mic­al­ly via­ble com­pro­mi­se bet­ween orga­ni­sa­tio­nal requi­re­ments and tech­ni­cal pos­si­bi­li­ties, to invol­ve future users in a meaning­ful way and to prepa­re them for system deployment. This does not only app­ly to the intro­duc­tion of trans­port manage­ment systems, but is espe­ci­al­ly true here, sin­ce estab­lished plan­ning pro­ces­ses often have to be rene­wed. This means that a cri­ti­cal part of the com­pa­ny is sub­ject to a signi­fi­cant change.

We meet this requi­re­ment by pro­vi­ding expe­ri­en­ced trans­port experts in a soft­ware pro­ject who know the trans­port plan­ning pro­ces­ses to be rene­wed very well. The soft­ware intro­duc­tion is often pre­ce­ded by a con­sul­ting pro­ject aimed at opti­mi­zing trans­port logistics.

The following topics are not to be understood as ranking, all topics are important.

Project management

Pro­ject manage­ment appro­pria­te to the pro­ject is a pre­re­qui­si­te for a suc­cessful soft­ware intro­duc­tion. When it comes to pro­ject manage­ment, we are con­cer­ned with plan­ning and cal­cu­la­ting the neces­sa­ry acti­vi­ties and con­trol­ling and moni­to­ring their implementation.


The ser­vices to be pro­vi­ded for both sides are cle­ar­ly descri­bed and clear to all pro­ject par­ti­ci­pan­ts. The cus­to­mer 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 respon­si­ble per­son is appoin­ted. The­se two ensu­re that the neces­sa­ry acti­vi­ties are car­ri­ed out on both sides in a time­ly and appro­pria­te manner.

Launch strategy

A com­ple­te chan­ge-over in one step (Big Bang) is often neces­sa­ry, but also has dis­ad­van­ta­ges. Expe­ri­ence has shown that a step-by-step intro­duc­tion is mana­geable, redu­ces the stress fac­tor for tho­se respon­si­ble for the pro­ject and allo­ws faster bene­fits in rela­ti­on to the time axis.

Risk management

Dra­wing up a spe­ci­fic risk check­list at the start of the pro­ject and regu­lar­ly revie­w­ing it over the cour­se of the pro­ject allo­ws the plan­ning of pre­ven­ti­ve and con­tin­gen­cy plans (“act instead of react”).

Key User principle

Users who play a key role in the use of the soft­ware should play a key role in defi­ning, deploying and imple­men­ting the soft­ware. Their task is to ensu­re that the tech­ni­cal requi­re­ments are met and to pave the way for accep­tance of the new solution.

Data migration

The trans­fer of data from lega­cy systems to the new soft­ware is usual­ly a com­plex task. In the rarest cases it is redu­ced to a simp­le pro­vi­si­on (data export) and pro­ces­sing (data import). As a rule, data con­ver­si­on at the logi­cal level is neces­sa­ry, often less is more!

Individual adaptations

X4fleet is a stan­dard pro­duct, but stan­dard back and forth — the­re comes a day when even the most powerful para­me­ter­izati­on capa­bi­li­ty comes to an end and indi­vi­du­al soft­ware adap­t­ati­on beco­mes neces­sa­ry. Examp­les of this are inter­faces to other systems, indi­vi­du­al docu­ment lay­outs, in-hou­se eva­lua­tions and lists, spe­cial pri­cing pro­ce­du­res, and so on. We con­ti­nuous­ly ensu­re a trans­pa­rent view and com­mu­ni­ca­te when the stan­dard is left or threa­tens to leave.

Open Points List

During the cour­se of a soft­ware intro­duc­tion, num­e­rous details ari­se that requi­re fur­ther pro­ces­sing, e. g. soft­ware errors that result in cor­rec­tions, new requi­re­ments to be eva­lua­ted, ide­as for impro­ve­ment that can be inte­gra­ted into future soft­ware releases, etc. With this list, we con­ti­nuous­ly ensu­re a com­mon view of the sta­tus of the implementation.


In the cour­se of the intro­duc­tion of soft­ware, a series of indi­vi­du­al rules and appoint­ments are crea­ted. We endea­vour to record the­se in wri­ting and make them available to us and the cus­to­mer. An important ele­ment in the docu­men­ta­ti­on is the JIRA, whe­re all tasks and inci­dents are descri­bed and their reso­lu­ti­on is docu­men­ted. The JIRA also ser­ves as a FAQ for the sup­port in asses­sing events.