Automating a Data Warehouse with Wherescape for a Railway C…

INTRODUCTION A large mobility and transport group with a core business of railways, which managed the rail traffic in Germany, wanted to integrate Wherescape instances into their data warehouse development process. CASE DESCRIPTION The client already had its own data warehouse development process and wanted to extend it with Wherescape. Therefore, the large mobility and transport group bought Wherescape licenses to in- tegrate instances of Wherescape 3D and Red into the existing development process. For the imple- mentation, freelancers were hired but several issues regarding the setup occurred due to a lack of expertise in the company. This was due to the fact that no one was willing and able to deal with these kinds of issues. The customer approached Scalefree with the intention of having a clear setup of the Wherescape instance which would work properly. In this case, the project required the secure implementation of the automation solution during the implementation of the data warehouse project process. On top of that, a certain level of knowledge about Wherescape needed to be handed over at a specific point in order to maintain the project. In this project, the focus was the correct setup of the automation solution and the preparation, as well as the connection, of the data which is relevant to the data warehouse. The Wherescape in- stances were prepared in a ten-day project and implemented in further work sprints in the overall project. Another service offered was the plan from the Scalefree to provide an expert based on the weekly request of the customer. With these services and the proper setup of the Wherescape solution, the client was able to use an automation solution that worked as expected. Further, this solution could also be used as a solid base on which more complex models can be built on. The correct working instance lowers the costs because it reduces the time spent on error remedies, which was often the case when Wherescape was installed incorrectly.

2/3