Software intro­duc­tion

The intro­duc­tion of new software is a challenge for many compa­nies. The aim is to actively shape an econo­mi­c­ally viable compro­mise between organi­sa­tional requi­re­ments and technical possi­bi­li­ties, to involve future users in a meaningful way and to prepare them for system deploy­ment. This does not only apply to the intro­duc­tion of trans­port manage­ment systems, but is especi­ally true here, since estab­lished planning processes often have to be renewed. This means that a critical part of the company is subject to a signi­fi­cant change.

We meet this requi­re­ment by provi­ding experi­enced trans­port experts in a software project who know the trans­port planning processes to be renewed very well. The software intro­duc­tion is often preceded by a consul­ting project aimed at optimi­zing trans­port logistics.

The follo­wing topics are not to be unders­tood as ranking, all topics are important.

Project manage­ment

Project manage­ment appro­priate to the project is a prere­qui­site for a successful software intro­duc­tion. When it comes to project manage­ment, we are concerned with planning and calcu­la­ting the necessary activi­ties and control­ling and monito­ring their imple­men­ta­tion.

Contract

The services to be provided for both sides are clearly described and clear to all project parti­ci­pants. The customer knows what to expect and we know what to do.

Coope­ra­tion with the customer

On our site as well as on the customer’s site, one respon­sible person is appointed. These two ensure that the necessary activi­ties are carried out on both sides in a timely and appro­priate manner.

Launch strategy

A complete change-over in one step (Big Bang) is often necessary, but also has disad­van­tages. Experi­ence has shown that a step-by-step intro­duc­tion is manage­able, reduces the stress factor for those respon­sible for the project and allows faster benefits in relation to the time axis.

Risk manage­ment

Drawing up a specific risk check­list at the start of the project and regularly reviewing it over the course of the project allows the planning of preven­tive and contin­gency 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 imple­men­ting the software. Their task is to ensure that the technical requi­re­ments are met and to pave the way for accep­tance of the new solution.

Data migra­tion

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 provi­sion (data export) and proces­sing (data import). As a rule, data conver­sion at the logical level is necessary, often less is more!

Indivi­dual adaptations

X4fleet is a standard product, but standard back and forth — there comes a day when even the most powerful parame­te­ri­za­tion capabi­lity comes to an end and indivi­dual software adaptation becomes necessary. Examples of this are inter­faces to other systems, indivi­dual document layouts, in-house evalua­tions and lists, special pricing proce­dures, and so on. We conti­nuously ensure a trans­pa­rent view and commu­ni­cate when the standard is left or threa­tens to leave.

Open Points List

During the course of a software intro­duc­tion, numerous details arise that require further proces­sing, e. g. software errors that result in correc­tions, new requi­re­ments to be evaluated, ideas for impro­ve­ment that can be integrated into future software releases, etc. With this list, we conti­nuously ensure a common view of the status of the imple­men­ta­tion.

Documen­ta­tion

In the course of the intro­duc­tion of software, a series of indivi­dual rules and appoint­ments are created. We endea­vour to record these in writing and make them avail­able to us and the customer. An important element in the documen­ta­tion is the JIRA, where all tasks and incidents are described and their resolu­tion is documented. The JIRA also serves as a FAQ for the support in asses­sing events.