The Reasons for Moving to a Database !!

Considering a move from Excel to a database makes sense

Our Excel files are so complex that it would make a lot of sense to move towards a database.

The initial question is why there are so many individual Excel files at all.

or maybe other solutions are unsuitable

Maybe there is no common database at all yet. Maybe a current PLM solution is not sufficient to solve all individual concerns, which make it necessary to work around with Excel downloads. So-called “low-code” solutions restrict users more than they help, because they are often not flexible enough to fully and comprehensively map the user’s issues

The Operational Issues

agile methods on the business side contradicts the traditional way of working in IT development
difficult to get all business areas around the table to define one common solution
today's databases can usually only be created by external IT experts
users have to stick with labour-intensive workarounds until a business case is approved
it is not sufficient to merely store different files in a common location where they are still separated

Tankers and Speedboats

We believe: It will always be necessary to have “tankers” and “speed-boats” for different purposes.

The objective

A solution would be desirable that can be expanded in stages, preferably by the users themselves without the continuous involvement of external IT specialists.

Instead of working directly with the tables

tables must be stored in a common data pool where individual rows can be linked to rows in other tables
put the tables in the background and define specific views, displayed differently for task dependent activities
initial departments agree and start with their process and expand the model when additional areas or needs arise
apply a dynamic workflow to enable a "handshake" between business processes
identify changes and ensure data quality when integrating different source files