DOCSLIB.ORG

Creating the Golden Record

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Creating the Golden Record CreatingCreating thethe GoldenGolden RecordRecord BetterBetter DataData throughthrough ChemistryChemistry Donald J. Soulsby metaWright.com AgendaAgenda • The Golden Record • Master Data • Discovery • Integration • Quality • Master Data Strategy DAMADAMA –– LinkedInLinkedIn GroupGroup C. Lwanga Yonke - Information Quality Practitioner ......SpewakSpewak advocatedadvocated usingusing datadata dependencydependency toto determinedetermine thethe idealideal sequencesequence inin whichwhich applicationsapplications shouldshould bebe developeddeveloped andand implemented:implemented: “Develop“Develop thethe applicationsapplications thatthat createcreate datadata beforebefore thosethose thatthat needneed toto useuse thatthat data”data” (p.10).(p.10). ArchitectureArchitecture AdvocatesAdvocates WilliamWilliam SmithSmith – Entity Lifecycle CliveClive FinkelsteinFinkelstein - Information Engineering – CRUD RonRon RossRoss -- ResourceResource LifeLife CycleCycle AnalysisAnalysis CRUDCRUD inin aa PerfectPerfect WorldWorld CanonicalCanonical SynthesisSynthesis Broadly speaking, materials scientists investigate two types of phenomena. Both are based on the microstructures of materials: … ii. How do these microstructures influence the properties of the material (such as strength, electrical conductivity, or high frequency electromagnetic absorption)? http://www.its.caltech.edu/~matsci/WhatIs2.html Business VS Development Life Cycles Zachman Framework for Enterprise Architecture WHERE WHAT WHEN HOW WHO WHY CONTEXTUAL List of List of List of List of List of Scope List of things Processes Locations Organization Events Business Units Goals/Stat. CONCEPTUAL Business Business Process Logistics Work Flow Master Business Business Model Entity Model Model Network Model Schedule Plan Application System Human LOGICAL Logical Data Process Network Interface Processing Business System Model Model Model Model Paradigm Structure Rule Model Application Network PHYSICAL Physical Structure Technology Presentation Control Rule Design Technology Model Data Model Chart Model Architecture Structure OUT-OF- Data Network Interface Timing Rule CONTEXT Definition Program Components Components Definition Specification Components PRODUCT DATABASE APPLICATION NETWORK ORGANIZATION SCHEDULE STRATEGY Functioning System TibetanTibetan ProverbProverb “ If upstream is dirty, downstream will be muddy” DataData WarehousingWarehousing -- ETLETL TransmutationTransmutation TheThe SecretSecret BernardBernard Trevisan,Trevisan, aa 15th15th centurycentury alchemist,alchemist, sspent much of his life and a sizable fortune in search of the secret of turning base metals into gold, realized while dying was… ““ToTo makemake gold,gold, oneone mustmust startstart withwith gold.”gold.” DAMADAMA GuideGuide toto thethe DataData ManagementManagement BodyBody ofof KnowledgeKnowledge Reference and Master Data Management: Managing golden versions and replicas DataData ManagementManagement BodyBody ofof KnowledgeKnowledge © 2008 DAMA International DAMADAMA DictionaryDictionary ReferenceReference DataData Any data used to categorize other data, or for relating data to information beyond the boundaries of the enterprise. See master data. MasterMaster DataData Synonymous with reference data. The data that provides the context for transaction data. It includes the details (definitions and identifiers) of internal and external objects involved in business transactions. Includes data about customers, products, employees, vendors, and controlled domains (code values). DAMADAMA DictionaryDictionary MasterMaster DataData ManagementManagement (MDM)(MDM) Processes that ensure that reference data is kept up to date and coordinated across an enterprise. The organization, management and distribution of corporately adjudicated data with widespread use in the organization. ReferenceReference && MasterMaster DataData ManagementManagement Ensuring consistency with a “golden version” of data values. One of nine data management functions identified in the DAMA-DMBOK Functional Framework. TopTop 1313 MDMMDM buzzwordsbuzzwords 1.1. MetadataMetadata (Don’t(Don’t saysay metadata)metadata) 2. Product information management (PIM) 3. Enterprise master patient index (EMPI) 4. Data governance 5. Customer data integration (CDI) 6. MDM hub 7. MDM architecture 8. "Collaborative" vs. "analytical" MDM 9. MDM return on investment (ROI) 10. MDM stakeholders 11. Enterprise hierarchy management 12. MDM metrics 13. Data competency center 02 Jul 2009 | Justin Aucoin, Assistant Site Editor, searchdatamanagement.com TheThe QuestQuest Bloor Research: the discovery of relationships between data elements, regardless of where the data is stored Discovery dDIQ MDM Quality Integration DAMA: The degree to which data DAMA: The planned and is accurate, complete, timely, controlled transformation and consistent with all requirements flow of data across databases, and business rules, and relevant for operational and/or analytical for a given use. use. AtomicAtomic DataData ofof thethe EnterpriseEnterprise Provide and maintain a consistent view of an enterprise's core business information assets Mendeleev ALCHEMY VS. CHEMISTRY WhatWhat isis MasterMaster Data?Data? Point In Time Currency Customer $ Product Country Transaction A Transaction is relationship of Master Data + Reference Files + time stamp + volumes + secondary descriptors MasterMaster DataData -- ClassificationClassification Customer Code Master AR Customer Data ID Cross ISO 3166 Reference INVENTORY Country Universal Data Code Enterprise Community Reference Status Data Code Local Operational Analytical Unified Master Data Types Operational Master Data Definition, creation, and synchronization of Master Data required for transactional systems and delivered via service-oriented architecture (SOA). Analytical Master Data Definition, creation, and integration, including multiple historical versions, of Master Data required for Enterprise Reporting or Data Warehousing applications. Unified Master Data Master Data that is defined and crated to apply to both Operational and Analytical applications. Implementation of the “single view of the truth”. It requires achieving agreement on a complex topic among a group of people MasterMaster DataData IntegrationIntegration Universal Master Data that is created and maintained by an external organization. For reference data it is often developed by a standards organization such as the ISO. Master Data Models are often available to members of an industry trade or professional association Enterprise Master Data that represents the common business information assets that need to be agreed on and shared throughout the enterprise Community Master Data that is shared between two or more applications. Typically data is replicated from the application that contains the system of record for the Master Data, by federation (key linkage) or propagation (materialized views). Local Master or Reference Data that is created and maintained for a single operational application. Much of the Reference Data will remain local, such as Status Codes, for the transactions within the application. MasterMaster DataData -- ContentContent Master Data Transactional Analytical Unified Definition Operational Technical Business Product Place Process Period Person Atomic Primitives PIM PRODUCT PROCESS PURPOSE PERIOD PEOPLEPARTY PLACE CDI MasterMaster DataData ClassificationClassification Artifact Person Product Place Period Process (Who) (What) (Where) (When) (How) Internal Product Time Business Geography Organization Hierarchy Slice Activity Customer Service Geo-Political Seasonality Go To Market MDMMDM –– IntegrationIntegration TechniquesTechniques DataData PropagationPropagation (Today)(Today) Copies Master Data from one location to another (materialized view). DataData ConsolidationConsolidation Captures data from multiple data sources and integrates into a single Master Data hub. DataData FederationFederation Provides a single virtual Master Data view of one or more data sources. No data is stored in the Master Data hub. VS ArchitectureArchitecture choiceschoices Independent Data Mart Bus Data Mart Architecture R e f F i l e Federated Data Stores Hub & Spoke Centralized Architecture Data Warehouse (Corporate Information Factory) (Enterprise Data Warehouse) Metadata + Repository Are master data files metadata? Need for central repository Inside Metadata Outside Metadata Repository Repository Metadata Repository Metadata Repository Master Data Master Data Meta Data MasterMaster DataData ArchitectureArchitecture –– RepositoryRepository • Comprehensive, single source for Master Data • Centrally managed, highly effective data governance • Fixed data model – typically Customer & Product • Extensive and sophisticated data integration process • All applications need to change to conform to Hubs • Expensive to modify to new business requirements • Hard to adapt to rapid changes S Legacy Data E Source Product R Application V I Customer C New Data HUB E Application Source S MasterMaster DataData ArchitectureArchitecture –– RegistryRegistry • Linkages to other data stores with transform logic • Low Cost, small footprint, only unique key kept in DB • Minimal disruption of current applications • Limited Data Governance, no merged Master Data • No resolution of semantic disintegrity • No History, System of Record linked to Data Source • Query performance - data availability from multiple sources Application Data Source MDM New Application XREF Application Data Source MasterMaster DataData ArchitectureArchitecture
Load more

Recommended publications
  • Data Warehouse Fundamentals for Storage Professionals – What You Need to Know EMC Proven Professional Knowledge Sharing 2011
    Data Warehouse Fundamentals for Storage Professionals – What You Need To Know EMC Proven Professional Knowledge Sharing 2011 Bruce Yellin Advisory Technology Consultant EMC Corporation [email protected] Table of Contents Introduction ................................................................................................................................ 3 Data Warehouse Background .................................................................................................... 4 What Is a Data Warehouse? ................................................................................................... 4 Data Mart Defined .................................................................................................................. 8 Schemas and Data Models ..................................................................................................... 9 Data Warehouse Design – Top Down or Bottom Up? ............................................................10 Extract, Transformation and Loading (ETL) ...........................................................................11 Why You Build a Data Warehouse: Business Intelligence .....................................................13 Technology to the Rescue?.......................................................................................................19 RASP - Reliability, Availability, Scalability and Performance ..................................................20 Data Warehouse Backups .....................................................................................................26
    [Show full text]
  • Design and Integration of Data Marts and Various Techniques Used for Integrating Data Marts
    Rashmi Chhabra et al, International Journal of Computer Science and Mobile Computing, Vol.3 Issue.4, April- 2014, pg. 74-79 Available Online at www.ijcsmc.com International Journal of Computer Science and Mobile Computing A Monthly Journal of Computer Science and Information Technology ISSN 2320–088X IJCSMC, Vol. 3, Issue. 4, April 2014, pg.74 – 79 RESEARCH ARTICLE Data Mart Designing and Integration Approaches 1 2 Rashmi Chhabra , Payal Pahwa 1Research Scholar, CSE Department, NIMS University, Jaipur (Rajasthan), India 2Bhagwan Parshuram Institute of Technology, I.P.University, Delhi, India 1 [email protected], 2 [email protected] ________________________________________________________________________________________________ Abstract— Today companies need strategic information to counter fiercer competition, extend market share and improve profitability. So they need information system that is subject oriented, integrated, non volatile and time variant. Data warehouse is the viable solution. It is integrated repository of data gathered from many sources and used by the entire enterprise. In order to standardize data analysis and enable simplified usage patterns, data warehouses are normally organized as problem driven, small units called data marts. Each data mart is dedicated to the study of a specific problem. The data marts are merged to create data warehouse. This paper discusses about design and integration of data marts and various techniques used for integrating data marts. Keywords - Data Warehouse; Data Mart; Star schema; Multidimensional Model; Data Integration __________________________________________________________________________________________________________ I. INTRODUCTION A data warehouse is a subject-oriented, integrated, time variant, non-volatile collection of data in support of management’s decision-making process [1]. Most of the organizations these days rely heavily on the information stored in their data warehouse.
    [Show full text]
  • Data Mart Setup Guide V3.2.0.2
    Agile Product Lifecycle Management Data Mart Setup Guide v3.2.0.2 Part Number: E26533_03 May 2012 Data Mart Setup Guide Oracle Copyright Copyright © 1995, 2012, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Data Warehousing on AWS
    Data Warehousing on AWS March 2016 Amazon Web Services – Data Warehousing on AWS March 2016 © 2016, Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. Page 2 of 26 Amazon Web Services – Data Warehousing on AWS March 2016 Contents Abstract 4 Introduction 4 Modern Analytics and Data Warehousing Architecture 6 Analytics Architecture 6 Data Warehouse Technology Options 12 Row-Oriented Databases 12 Column-Oriented Databases 13 Massively Parallel Processing Architectures 15 Amazon Redshift Deep Dive 15 Performance 15 Durability and Availability 16 Scalability and Elasticity 16 Interfaces 17 Security 17 Cost Model 18 Ideal Usage Patterns 18 Anti-Patterns 19 Migrating to Amazon Redshift 20 One-Step Migration 20 Two-Step Migration 20 Tools for Database Migration 21 Designing Data Warehousing Workflows 21 Conclusion 24 Further Reading 25 Page 3 of 26 Amazon Web Services – Data Warehousing on AWS March 2016 Abstract Data engineers, data analysts, and developers in enterprises across the globe are looking to migrate data warehousing to the cloud to increase performance and lower costs.
    [Show full text]
  • Master Data Management Whitepaper.Indd
    Creating a Master Data Environment An Incremental Roadmap for Public Sector Organizations Master Data Management (MDM) is the processes and technologies used to create and maintain consistent and accurate representations of master data. Movements toward modularity, service orientation, and SaaS make Master Data Management a critical issue. Master Data Management leverages both tools and processes that enable the linkage of critical data through a unifi ed platform that provides a common point of reference. When properly done, MDM streamlines data management and sharing across the enterprise among different areas to provide more effective service delivery. CMA possesses more than 15 years of experience in Master Data Management and more than 20 in data management and integration. CMA has also focused our efforts on public sector since our inception, more than 30 years ago. This document describes the fundamental keys to success for developing and maintaining a long term master data program within a public service organization. www.cma.com 2 Understanding Master Data transactional data. As it becomes more volatile, it typically is considered more transactional. Simple Master Data Behavior entities are rarely a challenge to manage and are rarely Master data can be described by the way that it interacts considered master-data elements. The less complex an with other data. For example, in transaction systems, element, the less likely the need to manage change for master data is almost always involved with transactional that element. The more valuable the data element is to data. This relationship between master data and the organization, the more likely it will be considered a transactional data may be fundamentally viewed as a master data element.
    [Show full text]
  • Value and Implications of Master Data Management (MDM) and Metadata Management
    Value and Implications of Master Data Management (MDM) and Metadata Management Prepared for: Dimitris A Geragas GARTNER CONSULTING Project Number: 330022715 CONFIDENTIAL AND PROPRIETARY This presentation, including any supporting materials, is owned by Gartner, Inc. and/or its affiliates and is for the sole use of the intended Gartner audience or other intended recipients. This presentation may contain information that is confidential, proprietary or otherwise legally protected, and it may not be further copied, distributed or publicly displayed without the express written permission of Gartner, Inc. or its affiliates. © 2015 Gartner, Inc. and/or its affiliates. All rights reserved. Enterprise Information Management Background CONFIDENTIAL AND PROPRIETARY 330022715 | © 2015 Gartner, Inc. and/or its affiliates. All rights reserved. 1 Enterprise Information Management is Never Information Enterprise Information Management (EIM) is about . Providing business value . Managing information (EIM) to provide business value . Setting up a business and IT program to manage information EIM is an integrative discipline for structuring, describing and governing information assets across organizational and technological boundaries. CONFIDENTIAL AND PROPRIETARY 330022715 | © 2015 Gartner, Inc. and/or its affiliates. All rights reserved. 2 Enterprise Information Management and the Information-Related Disciplines Enterprise Information Management (EIM) is about how information gets from a multitude of sources to a multitude of consumers in a relevant,
    [Show full text]
  • Managing Data in Motion This Page Intentionally Left Blank Managing Data in Motion Data Integration Best Practice Techniques and Technologies
    Managing Data in Motion This page intentionally left blank Managing Data in Motion Data Integration Best Practice Techniques and Technologies April Reeve AMSTERDAM • BOSTON • HEIDELBERG • LONDON NEW YORK • OXFORD • PARIS • SAN DIEGO SAN FRANCISCO • SINGAPORE • SYDNEY • TOKYO Morgan Kaufmann is an imprint of Elsevier Acquiring Editor: Andrea Dierna Development Editor: Heather Scherer Project Manager: Mohanambal Natarajan Designer: Russell Purdy Morgan Kaufmann is an imprint of Elsevier 225 Wyman Street, Waltham, MA 02451, USA Copyright r 2013 Elsevier Inc. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or any information storage and retrieval system, without permission in writing from the publisher. Details on how to seek permission, further information about the Publisher’s permissions policies and our arrangements with organizations such as the Copyright Clearance Center and the Copyright Licensing Agency, can be found at our website: www.elsevier.com/permissions. This book and the individual contributions contained in it are protected under copyright by the Publisher (other than as may be noted herein). Notices Knowledge and best practice in this field are constantly changing. As new research and experience broaden our understanding, changes in research methods or professional practices, may become necessary. Practitioners and researchers must always rely on their own experience and knowledge in evaluating and using any information or methods described herein. In using such information or methods they should be mindful of their own safety and the safety of others, including parties for whom they have a professional responsibility.
    [Show full text]
  • Oracle Warehouse Builder Concepts Guide
    Oracle® Warehouse Builder Concepts 11g Release 2 (11.2) E10581-02 August 2010 Oracle Warehouse Builder Concepts, 11g Release 2 (11.2) E10581-02 Copyright © 2000, 2010, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Data Warehouse Applications in Modern Day Business
    California State University, San Bernardino CSUSB ScholarWorks Theses Digitization Project John M. Pfau Library 2002 Data warehouse applications in modern day business Carla Mounir Issa Follow this and additional works at: https://scholarworks.lib.csusb.edu/etd-project Part of the Business Intelligence Commons, and the Databases and Information Systems Commons Recommended Citation Issa, Carla Mounir, "Data warehouse applications in modern day business" (2002). Theses Digitization Project. 2148. https://scholarworks.lib.csusb.edu/etd-project/2148 This Project is brought to you for free and open access by the John M. Pfau Library at CSUSB ScholarWorks. It has been accepted for inclusion in Theses Digitization Project by an authorized administrator of CSUSB ScholarWorks. For more information, please contact [email protected]. DATA WAREHOUSE APPLICATIONS IN MODERN DAY BUSINESS A Project Presented to the Faculty of California State University, San Bernardino In Partial Fulfillment of the Requirements for the Degree Master of Business Administration by Carla Mounir Issa June 2002 DATA WAREHOUSE APPLICATIONS IN MODERN DAY BUSINESS A Project Presented to the Faculty of California State University, San Bernardino by Carla Mounir Issa June 2002 Approved by: Date Dr. Walter T. Stewart ABSTRACT Data warehousing is not a new concept in the business world. However, the constant changing application of data warehousing is what is being innovated constantly. It is these applications that are enabling managers to make better decisions through strategic planning, and allowing organizations to achieve a competitive advantage. The technology of implementing the data warehouse will help with the decision making process, analysis design, and will be more cost effective in the future.
    [Show full text]
  • Master Data Management Services (MDMS) System
    ADAMS ML19121A465 U.S. Nuclear Regulatory Commission Privacy Impact Assessment Designed to collect the information necessary to make relevant determinations regarding the applicability of the Privacy Act, the Paperwork Reduction Act information collection requirements, and records management requirements. Master Data Management Services (MDMS) System Date: April 16, 2019 A. GENERAL SYSTEM INFORMATION 1. Provide a detailed description of the system: The Nuclear Regulatory Commission (NRC) has established the Master Data Management Services (MDMS) system to address both short and long-term enterprise data management needs. The MDMS is a major agencywide initiative to support the processes and decisions of NRC through: • Improving data quality • Improving re-use and exchange of information • Reducing or eliminating the storage of duplicate information • Providing an enterprise-wide foundation for information sharing • Establishing a data governance structure The MDMS provides an overall vision for, and leadership focused on, an enterprise solution that establishes authoritative data owners, delivers quality data in an efficient manner to the systems that require it, and effectively meets business needs. The MDMS is also focused on data architecture and includes projects that will identify and define data elements across the agency. The MDMS system is a web-based application accessible to representatives from every NRC office—that provides standardized and validated dockets and data records that support dockets, including licenses, contact and billing information, to all downstream NRC systems that require that data. The NRC collects digital identification data for individuals to support the agency core business operations, issue credentials, and administer access to agency‘s physical and logical resources. To support this need, the MDMS system also serves as a centralized repository for the accessibility of organization and personnel data.
    [Show full text]
  • Data Warehousing
    DMIF, University of Udine Data Warehousing Andrea Brunello [email protected] April, 2020 (slightly modified by Dario Della Monica) Outline 1 Introduction 2 Data Warehouse Fundamental Concepts 3 Data Warehouse General Architecture 4 Data Warehouse Development Approaches 5 The Multidimensional Model 6 Operations over Multidimensional Data 2/80 Andrea Brunello Data Warehousing Introduction Nowadays, most of large and medium size organizations are using information systems to implement their business processes. As time goes by, these organizations produce a lot of data related to their business, but often these data are not integrated, been stored within one or more platforms. Thus, they are hardly used for decision-making processes, though they could be a valuable aiding resource. A central repository is needed; nevertheless, traditional databases are not designed to review, manage and store historical/strategic information, but deal with ever changing operational data, to support “daily transactions”. 3/80 Andrea Brunello Data Warehousing What is Data Warehousing? Data warehousing is a technique for collecting and managing data from different sources to provide meaningful business insights. It is a blend of components and processes which allows the strategic use of data: • Electronic storage of a large amount of information which is designed for query and analysis instead of transaction processing • Process of transforming data into information and making it available to users in a timely manner to make a difference 4/80 Andrea Brunello Data Warehousing Why Data Warehousing? A 3NF-designed database for an inventory system has many tables related to each other through foreign keys. A report on monthly sales information may include many joined conditions.
    [Show full text]
  • Lecture @Dhbw: Data Warehouse Review Questions Andreas Buckenhofer, Daimler Tss About Me
    A company of Daimler AG LECTURE @DHBW: DATA WAREHOUSE REVIEW QUESTIONS ANDREAS BUCKENHOFER, DAIMLER TSS ABOUT ME Andreas Buckenhofer https://de.linkedin.com/in/buckenhofer Senior DB Professional [email protected] https://twitter.com/ABuckenhofer https://www.doag.org/de/themen/datenbank/in-memory/ Since 2009 at Daimler TSS Department: Big Data http://wwwlehre.dhbw-stuttgart.de/~buckenhofer/ Business Unit: Analytics https://www.xing.com/profile/Andreas_Buckenhofer2 NOT JUST AVERAGE: OUTSTANDING. As a 100% Daimler subsidiary, we give 100 percent, always and never less. We love IT and pull out all the stops to aid Daimler's development with our expertise on its journey into the future. Our objective: We make Daimler the most innovative and digital mobility company. Daimler TSS INTERNAL IT PARTNER FOR DAIMLER + Holistic solutions according to the Daimler guidelines + IT strategy + Security + Architecture + Developing and securing know-how + TSS is a partner who can be trusted with sensitive data As subsidiary: maximum added value for Daimler + Market closeness + Independence + Flexibility (short decision making process, ability to react quickly) Daimler TSS 4 LOCATIONS Daimler TSS Germany 7 locations 1000 employees* Ulm (Headquarters) Daimler TSS China Stuttgart Hub Beijing Berlin 10 employees Karlsruhe Daimler TSS Malaysia Hub Kuala Lumpur Daimler TSS India * as of August 2017 42 employees Hub Bangalore 22 employees Daimler TSS Data Warehouse / DHBW 5 WHICH CHALLENGES COULD NOT BE SOLVED BY OLTP? WHY IS A DWH NECESSARY? • Distributed
    [Show full text]