Thereby, the development team quickly gets in touch with the product owners which allows for an iteration process where requirements and possibilities converge to the final dashboard. Due to short interaction times between the development team and the product owners a “fail hard fast” approach is enforced which allows Dillinger to solve issues quickly. Scalefree coins this also as the “tracer- bullet approach” since the first results are presented to the product owners within sprint one. In order to meet the tough timeline to produce a dashboard within sprint one, there is not much room for failure. Additionally, for the internal team, Data Vault 2.0 as well as WhereScape was completely new. Of course, this is a risk as Scalefree is committed to meeting the deadlines of the sprints. To mitigate this, at least partly, Scalefree commends so-called “project setup” sprints which are denoted with numbers -2, -1, 0. These sprints are standardized and contain a huge list of checkpoints as well as a technical smoke test which should be addressed prior to the first “delivery” sprint. By going through these project setup sprints Scalefree and Dillinger put themselves in an ideal position to hold the tight schedule. FIRST SUBPROJECT: ROLLING MILL - SLAB THROUGHPUT The first project was to provide key performance indicators for the first subsection of the rolling mill and its slab throughput. One of the key learnings for Dillinger was the value of the “right” business keys to be selected for the Data Vault model. In this project, the main business objects are orders, positions, bars, slabs and sheets. All of them are equipped with reference numbers. The design of the source database is mostly hierarchical. This dates back to the time when most programs were written in Fortran. Since then, all development is done in Java but the database layout still reflects the old Fortran design. The database for the mill’s main frame is constantly under heavy load. With its very large tables at high traffic volumes, even minor blockages can have unpleasant impacts on the production environment. But there were more challenges: unfortunately, but typical for legacy databases, the documentation of the key figures was non-existent in a user accessible format. Old visualizations of key figures written in Visual Basic, were the only input available for the requirements analysis but these also needed to be reverse-engineered in a time-consuming manner to extract the relevant information. In this project, Dillinger’s DWH team is responsible for the full delivery of not only the information marts (and upstream layers) but also the dashboards. With this in mind, simply providing a database view would not be sufficient to get the job done. There was no designated team to take care of the visualization of metrics at the end-users side, adding to the challenge. The availability of team resources was an issue, initially. In addition to the limited end-user availability, the data warehouse team was also very limited at the very beginning, with only one internal person working on the project. On top of that, this person had additional responsibilities in maintaining the legacy data warehouse and project management tasks.
Made of Steel - Data Vault 2.0 at Dillinger | Scalefree International GmbH
6/13
Powered by FlippingBook