Data Warehouse Architect and Lead Data Modeler

• Responsible for building and leading the Lidl/Kaufland architecture team (about 15 architects and data modelers).
• Defining architecture standards and modeling guidelines.
• Designing a conceptual enterprise data model and a business glossary.
• Designing a semantic layer for the Lidl Enterprise Data Warehouse:
• Leading a team of 8 analysts and developers.
• Project planning and setup.
• Designing a dimensional data model for enterprise reporting.
• Responsible for analysis, data mapping, and development.
• Lead data modeler for building a logistics DWH.
• Architect for migrating the data warehouse from Teradata to Snowflake:
• Defining the target architecture with a data lake in Microsoft Azure and a data warehouse in Snowflake.
• Architecting an integrated data quality concept using Ab Initio Metadata Hub and Snowflake.
• Lead architect for designing a new enterprise data warehouse model:
• Leading about 15 architects and analysts.
• Writing specifications and guidelines for a team of about 30 developers.
• Requirements analysis.
• Modeling an integration layer and a presentation layer.
• Responsible for business analysis and source data mapping.
• Advising on designing an automated fraud detection system.
• Advising on implementing a data mesh concept.

Tools used: Teradata 16.20, Snowflake, Microsoft Azure, PowerDesigner, Ab Initio.

• Responsible for designing an application layer for freight price analysis:
• Solution architecture.
• Data modeling.
• Data mapping.
• Defining modeling guidelines and architecture standards.
• Responsible for designing Maersk Line’s new enterprise DWH:
• Relational and dimensional modeling.
• Leading a team of about 10 data modelers.

Tools used: Teradata 15.10, Erwin.

• Logical and physical data modeling based on Teradata FSDM.
• Responsible for data mapping.
• End-user training.

Tools used: FSDM 13, Teradata 15.10, Erwin.

• Acting as the customer’s liaison to the implementation partner.
• Responsible for creating a dimensional model based on IBM TDW.
• Overseeing data mappings.

Tools used: Netezza, IDA, IBM TDW, DataStage.

• Responsible for extending Vodafone Germany’s data warehouse model to a standard solution across all Vodafone organizations in Europe.
• Design authority for the core data warehouse model.
• Defining collaboration and governance processes.
• Advisory architect for Vodafone Greece’s enterprise data warehouse.
• Advisory architect for Vodafone Turkey’s enterprise data warehouse.

Tools used: Teradata 13.0, CLDM R.13, IBM TDW, PowerDesigner.

• Pre-sales support for Teradata Austria.
• Solution architecture.
• Writing specifications and guidelines for a team of about 50 analysts and developers.
• Responsible for creating a conceptual data model using business data elements methodology.
• Lead data modeler responsible for the enterprise data warehouse model:
• Leading a team of 8 data modelers and business analysts.
• Logical and physical data modeling.
• Responsible for data mapping and implementation guidelines.
• Training and coaching RBI staff.

Tools used: Teradata 13.10, FSLDM R.11, Unix, ERWin, PowerDesigner.

• Member of the architecture team:
• Adapting Teradata FSLDM.
• Physical data modeling.
• Responsible for data mapping and implementation (leading a team of about 15 analysts and developers).
• End-user training and workshops.
• Technical lead for a reporting subproject:
• Technical project lead for a team of 4 consultants.
• Project planning.
• Requirements analysis and reverse-engineering existing processes.
• Architecture and design.
• Architect for migrating the data warehouse to a new core banking system:
• Technical project lead for a team of about 15 analysts and designers.
• Logical and physical data modeling.
• Responsible for data mapping.
• Advisory architect for UniCredit Italy’s data warehouse:
• Responsible for logical and physical data modeling.
• Responsible for data mapping.
• Architect for Bank Austria CEE’s data warehouse (rollout in about 10 countries):
• Logical and physical data modeling.
• Responsible for data mapping (about 10 analysts and developers).
• Responsible for designing a MicroStrategy application layer.
• Lead architect for extending the data warehouse to a group-wide solution for UniCredit:
• Design authority for DWH architecture, data model, and mapping.
• Writing specifications and guidelines for a team of about 120 analysts and developers across multiple countries.
• Co-developing a semi-automated data mapping process, “Business Data Elements” (included in Teradata’s standard DWH methodology).

Tools used: Teradata V2R6.2, Teradata 12, FSLDM R.8/R.9/R.10, Unix, ERWin, DataStage 8.0.

• Database administration for the largest Teradata installation in Europe (168 nodes).
• Performance monitoring and tuning.
• End-user and production support.
• Designing and implementing a performance and workload management solution.

Tools used: Teradata V2R5.1, NCR MP-RAS, ERWin, C.

• Technical project management for a team of 6 consultants.
• Developing technical concepts and guidelines for two external development partners (~50 consultants and programmers):
• Solution design.
• Hardware sizing.
• ETL concept.
• Backup concept.
• Operations concept.
• Database setup and administration.
• Physical data modeling.
• Quality assurance of implementation.
• Training and end-user workshops.

Tools used: Teradata V2R5, CLDM, NCR MP-RAS, ERWin.

• Advising on selecting various implementation bids for a DWH project.

• Requirements analysis.
• Design and data modeling.
• Developing the rating engine and billing database.
• Designing and implementing billing functionality:
• Hot billing.
• Simultaneous calculation of customer charges, interconnection charges, and service fees.
• Flexible bill cycles.
• Custom pricing per customer.
• Integrated data warehouse functionality.
• Integrated customer service portal via web applications.
• Quality assurance.
• Consulting.

Tools used: Linux, C++, shell scripts, Perl, Erwin, Windows 2000, MySQL, MS SQL Server 2000.

• Integrating the telephony business into the data warehouse.
• Data modeling.
• Developing and implementing a load and transformation program.
• Transformations and hierarchy logic.
• Developing a frontend configuration tool.
• Consulting.

Tools used: Teradata V2R3, NCR MP-RAS, C++, shell scripts, ERWin.

• Project planning.
• Requirements analysis.
• Data modeling.
• Load and transformation scripts.
• Programming for CDR tickets.
• Database administration.
• Reports and analysis.
• Churn analysis.

Tools used: Teradata V2R3, NCR MP-RAS, C++, shell scripts, ERWin.

• Responsible for call data in the data warehouse:
• Data modeling.
• Implementing a load and transformation program.
• Regular data loads.
• Performance optimization.
• Reports and user support.
• Integrating retail data from branch transactions:
• Data modeling.
• Load and transformation scripts.

Tools used: Teradata V2R2, CLDM, NCR MP-RAS, C, shell scripts, OS/390, TSO, JCL, MS Access, ERWin, Business Objects.

• Developing a data compression algorithm:
• Analyzing measurement data samples.
• Comparing and selecting modeling and compression methods.
• Building a prototype encoder.

Tools used: MS-DOS, Pascal.