DOCSLIB.ORG

Modeling Guidelines

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Modeling Guidelines Master Data Services Training Guide Modeling Guidelines Portions developed by Profisee Group, Inc. © 2010 Microsoft MDM: A Multifaceted Discipline Master Data Management is a multi-faceted discipline that covers a wide range of subject areas from data quality to data governance. The focus of this section – and for the entire class – is an overview of some of the components and approaches to building a comprehensive and effective master data model in Microsoft SQL Server Master Data Services. 7 :: 2 Master Data Services Training Guide Objectives This section will begin with an overview of the key components of a master data model: Entities Hierarchies: explicit, derived and derived with explicit cap Attributes: domain-based, free-form and file Collections Member types: leaf and consolidated. Following the dive into model components, this section presents suggested guidelines and considerations when creating and deploying master data models: The relationship between entities and attributes When and how to use certain types of hierarchies How to make the most effective use of business rules The benefits of versioning and version frequencies. This section is a useful reference when undertaking a new project or model implementation. Master Data Services Training Guide 7 :: 3 Model Components: Entity A Master Data Services database may contain one or more master data models. A model typically represents a common subject area such as customers, products, financial accounts and locations. An entity is the foundation of a Master Data Services model. It represents a list of items – often referred to as members or elements – that share common characteristics. As examples, an entity City contains a list of cities; an entity Color contains a list of colors. One or more entities reside in model. An attribute, or property, further defines or modifies an entity. For example population is an attribute that further describes a city. An attribute is classified as domain-based, free-form, or file. Free-form attributes are further classified as text, number, date/time, or link. Every entity has, at a minimum, two system attributes: Code and Name. Code is required, must be unique throughout the entity, and often represents the natural key for a source system. Name is optional, but recommended. It further describes the data element and typically appears on reports. 7 :: 4 Master Data Services Training Guide Model Components: Domain-based Attribute One of the three attribute types that you may create is “domain-based” attributes. A domain- based attribute is an attribute that uses an entity as its data source. For those familiar with relational database theory, an entity is equivalent to a table, an attribute is equivalent to a column in the table. A domain-based attribute is a column that essentially acts as a foreign key. As will be discussed later in this section, domain-based attributes form the basis for derived hierarchies. To further describe domain-based attributes, consider an example of three entities, or tables: 1. States 2. Cities 3. Regions The State entity contains three domain-based attributes: 1. Capital 2. Most Populous 3. Region The list of capitals and most populous cities is derived from „City‟; the list of regions is from the Region entity. Master Data Services Training Guide 7 :: 5 Extending the example a step further, each city is assigned a state or province attribute. The list of available states is derived from the state entity. A more advanced use of domain-based attributes is to create an attribute that refers to the same entity to which the attribute is associated. In this example, Sister City refers to the same list of cities. The term recursive hierarchy is often used to describe this scenario. 7 :: 6 Master Data Services Training Guide Model Components: Free-form Attribute The second type of attribute is free-form. As the name implies, free-form attributes are not restricted to a domain-list. Data entry is restricted to the data type defined when the attribute is created. A free-form attribute is assigned one of the following four data types: 1. Text 2. Numeric 3. Date 4. Link, or URL When assigning or updating attributes, Master Data Services ensures that the data corresponds to the attribute data type. A free-form attribute is equivalent to a standard column in SQL Server. The third attribute type is file. Once defined, it enables users to upload files to Master Data Services. The next section will cover this in more detail. Master Data Services Training Guide 7 :: 7 Model Components: Explicit Hierarchies Hierarchies are typically a key component of a model; they form the basis for data analysis and reporting. Browse through a company‟s annual report; survey an internal managerial report. In both of these scenarios, hierarchies are prevalent and a critical means to display financial data – Income Statements, Balance Sheets, sales by territory, etc. One of the key benefits of Master Data Services is the ability to use existing master data elements to create a myriad of different types of hierarchies – each designed to support a specific need. Through business rules and other forms of automation, many of the hierarchies are subjected to rigorous business requirements. Master Data Services distinguishes between explicit and derived hierarchies. Each explicit hierarchy is associated with a single entity. The addition of the first explicit hierarchy to an entity introduces consolidated member types. Leaf member types are directly associated with entities. Consolidated members are associated with explicit hierarchies. Consolidated members possess a distinct set of attributes (that are shared across hierarchies). An entity contains zero or more user-defined explicit hierarchies. Explicit hierarchies introduce two system attributes, Code and Name, for consolidated members. Code must be unique throughout the hierarchies and entity. 7 :: 8 Master Data Services Training Guide Hierarchy Definition: Explicit vs. Derived The most important difference to understand between explicit and derived hierarchies is that derived hierarchies are formed via attribute relationships and employ multiple entities. Explicit hierarchies have ragged level depths and reside within a single entity. For those familiar with Microsoft SQL Server Analysis Services (or other multidimensional analysis solutions), explicit hierarchies resemble parent-child hierarchies; derived hierarchies equate to attribute-based or level-based hierarchies. Master Data Services Training Guide 7 :: 9 When modeling hierarchies for your master data models, it is critical to invest the time to understand the business and system requirements, so that you select the most efficient hierarchy type. This table depicts further differences between the hierarchy types. 7 :: 10 Master Data Services Training Guide Hierarchy Definition: Derived Hierarchy with an Explicit Cap A derived hierarchy with an explicit cap blends a derived and explicit hierarchy. It is formed by linking related attributes and then connecting an explicit hierarchy at the top. The diagram below illustrates the benefits of using Master Data Services to manage hierarchies. Customers are maintained in a customer entity and each is assigned to a customer group (attribute). The Customers-by-Location derived hierarchy enables you to analyze and report by geography. The derived hierarchy with an explicit cap on the left makes use of the same entity and attributes and then inserts an existing explicit hierarchy. Changes to the underlying data are automatically reflected in both hierarchies. Master Data Services Training Guide 7 :: 11 Model Components – Recap The next three illustrations put together the individual components of a master data model – helping to paint a cohesive picture of how they relate to the other components that make up a model. 7 :: 12 Master Data Services Training Guide Master Data Services Training Guide 7 :: 13 Model Development: Preliminary Considerations Having covered the basic components of a model, the remainder of this section will present some general modeling guidelines for consideration during the design and implementation of a Master Data Services model. The following presents a set of proven steps to build and deploy a high-quality master data model using Master Data Services. This approach leverages the power of Master Data Services to avoid some of the more mundane technical data modeling techniques. It encourages model builders to build and populate the model while it is still being designed. Because it is easy to alter and update a model, real data can and should be analyzed and loaded to help validate assumptions. This approach produces documentation of the model and yields a working pilot, prototype or proof of concept. No model exists in isolation. Before building a model it pays to enumerate and agree on the stakeholders and boundaries of the model. An organization may have 20 or more systems that could potentially subscribe to a model. Furthermore, the model could have hundreds of attributes. While it is technically possible to implement a model that feeds this many systems with this many attributes, it is a good idea to limit the scope and set boundaries for the initial model. Master Data Services simplifies the process of adding new attributes and subscriptions, so starting small does not hinder future scalability. 7 :: 14 Master Data Services Training Guide Model Development: Major Steps The below list and diagram illustrate the key steps a Master Data Services modeler should consider during the design phase: 1. Identify entities 2. Define attributes a. Free-form b. Domain-based 3. Identify hierarchies 4. Implement relationships a. Explicit hierarchy b. Derived (domain-based) hierarchy 5. Group attributes The process is typically quite iterative as the model evolves over time. Each step is covered in specific detail in the ensuing sections. Master Data Services Training Guide 7 :: 15 Identify Entities and Attributes This is a listing of the major, important entities within a model; for example, department, division and center – not gender and postal code.
Load more

Recommended publications
  • 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]
  • 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]
  • What to Look for When Selecting a Master Data Management Solution What to Look for When Selecting a Master Data Management Solution
    What to Look for When Selecting a Master Data Management Solution What to Look for When Selecting a Master Data Management Solution Table of Contents Business Drivers of MDM .......................................................................................................... 3 Next-Generation MDM .............................................................................................................. 5 Keys to a Successful MDM Deployment .............................................................................. 6 Choosing the Right Solution for MDM ................................................................................ 7 Talend’s MDM Solution .............................................................................................................. 7 Conclusion ..................................................................................................................................... 8 Master data management (MDM) exists to enable the business success of an orga- nization. With the right MDM solution, organizations can successfully manage and leverage their most valuable shared information assets. Because of the strategic importance of MDM, organizations can’t afford to make any mistakes when choosing their MDM solution. This article will discuss what to look for in an MDM solution and why the right choice will help to drive strategic business initiatives, from cloud computing to big data to next-generation business agility. 2 It is critical for CIOs and business decision-makers to understand the value
    [Show full text]
  • Centralized Or Federated Data Management Models, IT Professionals' Preferences
    Paper ID #8737 CENTRALIZED OR FEDERATED DATA MANAGEMENT MODELS, IT PROFESSIONALS’ PREFERENCES Dr. Gholam Ali Shaykhian, NASA Ali Shaykhian has received a Master of Science (M.S.) degree in Computer Systems from University of Central Florida and a second M.S. degree in Operations Research from the same university and has earned a Ph.D. in Operations Research from Florida Institute of Technology. His research interests include knowledge management, data mining, object-oriented methodologies, design patterns, software safety, genetic and optimization algorithms and data mining. Dr. Shaykhian is a professional member of the American Society for Engineering Education (ASEE). Dr. Mohd A. Khairi, Najran University B.Sc of computer science from Khartoum university. Earned my masters from ottawa university in system science. My doctoral degree in information system from University of Phoenix( my dissertation was in Master Data Management). I worked in IT industry over 20 years, 10 of them with Microsoft in different groups and for the last 4 years was with business intelligence group. My focus was in Master Data Management. For the last 2 years I teach at universify of Najran in the college of Computer Science and Information System . My research interest in Master Data Management. c American Society for Engineering Education, 2014 CENTRALIZED OR FEDERATED DATA MANAGEMENT MODELS, IT PROFESSIONALS’ PREFERENCES Gholam Ali Shaykhian, Ph.D. Mohd Abdelgadir Khairi, Ph.D. Abstract The purpose of this paper is to evaluate IT professionals’ preferences and experiences with the suitable data management models (Centralized Data Model or Federated Data Model) selection. The goal is to determine the best architectural model for managing enterprise data; and help organizations to select an architectural model.
    [Show full text]
  • IBM Infosphere Master Data Management
    Data and AI Solution Brief IBM InfoSphere Master Data Management Maintain a trusted, accurate view of Highlights critical business data in a hybrid environment • Support comprehensive, cost-effective information Organizations today have more data about products, governance services, customers and transactions than ever before. • Monitor master data quality Hidden in this data are vital insights that can drive business using dashboards and results. But without comprehensive, well-governed data proactive alerts sources, decision-makers cannot be sure that the information • Simplify the management they are using is the latest, most accurate version. As data and enforcement of master volumes continue to grow, the problem is compounded over data policies time. Businesses need to find new ways to manage and • Integrate master data govern the increasing variety and volume of data and deliver management into existing it to end users as quickly as possible and in a trusted manner, business processes regardless of the computing modality. • Quickly scale to meet changing business needs IBM InfoSphere Master Data Management (InfoSphere MDM) provides a single, trusted view of critical business data to • Optimize resources using users and applications, helping to reduce costs, minimize risk flexible deployment options and improve decision-making speed and precision. InfoSphere MDM achieves the single view through highly accurate and comprehensive matching that helps overcome differences and errors that often occur in the data sources. The MDM server manages your master data entities centrally, reducing reliance on incomplete or duplicate data while consolidating information from across the enterprise. Data and AI Solution Brief With InfoSphere MDM, you can enforce information governance at an organizational level, enabling business and IT teams to collaborate on such topics as data quality and policy management.
    [Show full text]
  • Practical Fundamentals for Master Data Management How to Build an Effective Master Data Capability As the Cornerstone of an Enterprise Data Management Program
    Practical Fundamentals for Master Data Management How to build an effective master data capability as the cornerstone of an enterprise data management program WHITE PAPER SAS White Paper Table of Contents Introduction . 1 Considering Master Data Management (MDM) Benefits . 2 They Sound Good, But… . 2 Master Data and Real Business Value . 3 Assessing Organizational Readiness for Enterprise Initiatives . 4 Horizontal Coordination . 4 Coordinating Systemic Change . 5 Consistency in Meaning . .. 5 Standardized Business Rules . 5 Practical Master Data Management . 6 Technical Data Improvement . 6 Reconsidering MDM . 7 Purpose-Driven MDM . 7 Start with the Fundamentals . 8 Standardize Semantics . 8 Consolidate Enterprise Metadata . 8 Improve Data Quality . 9 Balance Business and Technical Benefits . 9 Establishing the Fundamentals . 10 Ready? . 10 Set … . 10 Go! . 11 About the Author . 11 Practical Fundamentals for Master Data Management Introduction Enterprisewide programs are often designed to improve business processes and business decisions through enhanced information sharing – based on a more reliable foundation of data . For this purpose, these initiatives promise significant organizational benefits along a number of dimensions of value, but, as with any business project, they can also carry significant risks and complexity . Since the early tangible value Organizations that have successfully deployed programs that span the enterprise are of an MDM strategy comes prime candidates for a successful enterprise master data management (MDM) initiative; from standardized semantics, those lacking this experience are at greater risk for MDM failure . However, since the consolidated metadata, and early tangible value of an MDM strategy comes from standardized semantics, consolidated metadata, and most critically, data quality improvement, focusing on most critically, data quality these fundamental aspects of MDM reduces the risks while providing practical utility to improvement, focusing on the data user community .
    [Show full text]
  • Essential Elements of a Master Data Management Architecture
    The Fourth MIT Information Quality Industry Symposium, July 14-16, 2010 Essential Elements of a Master Data Management Architecture ABSTRACT Building master data management (MDM) into an IT infrastructure is not as simple as buying a product and plugging it in. Rather, selecting the right MDM architecture is a function of business and technological considerations. Business considerations include management style, organizational structure, and governance. Technical considerations include vendor affinity policy, middleware architecture, and modeling capabilities. In this presentation, Burton Group Principal Analyst, Joe Bugajski, will examine the MDM architecture selection decision, and four of the most common MDM architectural styles: local MDM, hub MDM, federated database MDM, and hybrid MDM. He also will review the characteristics of an MDM system. BIOGRAPHY Joseph M. Bugajski Burton Group Joe Bugajski is principal analyst for Gartner’s Burton Group Research. He covers IT governance, enterprise architecture, and data standards, data access, master data management, information quality, and data integration. Prior to Burton Group, Joe was founder and managing partner of Venture KPI Research Partners who deliver due diligence for venture capitalists. Before this, Joe was chief data officer for Visa International bearing global responsibility for information interoperability. He was Visa’s resident entrepreneur and chief enterprise architect of back office, risk control, and business intelligence infrastructure systems. Prior to Visa, Joe was CEO of Triada, a global business intelligence software maker. Before Triada, Joe was an executive at Ford Motor Company, responsible for engineering information systems and prototype vehicle manufacturing in which function he architected the legendary Taurus/Sable engineering program. Joe is also a data analytics researcher with four patents and twenty-six peer-reviewed publications.
    [Show full text]
  • Learning Data Modelling by Example Chapter 9) Master Data Management
    Learning Data Modelling by Example Chapter 9) Master Data Management 9. Master Data Management (MDM)...............................................................................................2 9.0 Welcome .............................................................................................................................................2 9.1 Introduction ........................................................................................................................................2 9.2 MDM for CRM.....................................................................................................................................3 9.3 MDM for Law Enforcement ................................................................................................................9 9.4 MDM for Local Government.............................................................................................................16 9.5 What have we learned ? ...................................................................................................................21 Page 1 Learning Data Modelling by Example Chapter 9) Master Data Management 9. Master Data Management (MDM) 9.0 Welcome You are invited to follow developments on our Web Site :- http://www.databaseanswers.org/index.htm You can also join our Database Answers Community http://databaseanswers.ning.com/ Barry Williams Principal Consultant Database Answers Ltd. [email protected] 9.1 Introduction This Chapter will discuss MDM for CRM, Law Enforcement and Local Government.
    [Show full text]
  • Master Data Management (MDM) Improves Information Quality to Deliver Value
    MIT Information Quality Industry Symposium, July 15-17, 2009 Master Data Management (MDM) Improves Information Quality to Deliver Value ABSTRACT Master Data Management (MDM) reasserts IT’s role in responsibly managing business-critical information—master data—to reasonable quality and reliability standards. Master data includes information about products, customers, suppliers, locations, codes, and other critical business data. For most commercial businesses, governmental, and non-governmental organizations, master data is in a deplorable state. This is true although MDM is not new—it was, is, and will be IT’s job to remediate and control. Poor-quality master data is an unfunded enterprise liability. Bad data reduces the effectiveness of product promotions; it causes unnecessary confusion throughout the organization; it misleads corporate officers, regulators and shareholders; and it dramatically increases the IT cost burden with ceaseless and fruitless spending for incomplete error remediation projects. This presentation describes—with examples—why senior IT management should launch an MDM process, what governance they should institute for master data, and how they can build cost-effective MDM solutions for the enterprises they serve. BIOGRAPHY Joe Bugajski Senior Analyst Burton Group Joe Bugajski is a senior analyst for Burton Group. He covers IT governance, architecture, and data – governance, management, standards, access, quality, and integration. Prior to Burton Group, Joe was chief data officer at Visa responsible worldwide for information interoperability. He also served as Visa’s chief enterprise architect and resident entrepreneur covering risk systems and business intelligence. Prior to Visa, Joe was CEO of Triada, a business intelligence software provider. Before Triada, Joe managed engineering information systems for Ford Motor Company.
    [Show full text]
  • Optimize Master Data Management Through Federated Data Governance
    SAP Thought Leadership Paper | PUBLIC Data Management in the Cloud Optimize Master Data Management Through Federated Data Governance An Adaptive Model for Trusted, Process-Relevant Data to Drive Greater Insights, Efficiencies, and ROI 1 / 17 © 2021 SAP SE or an SAP affiliate company. All rights reserved. All rights company. affiliate SE or an SAP SAP © 2021 Table of Contents 3 The Master Data Imperative 5 The Importance of Master Data Integration 8 A New Paradigm: Federated Data Governance 11 The Case for Cloud-Centered Federation 12 Master Data Governance in the Cloud 15 Becoming an Intelligent Enterprise 17 First Steps to Federated Data Governance 2 / 17 © 2021 SAP SE or an SAP affiliate company. All rights reserved. Optimize Master Data Management Through Federated Data Governance The Master Data Imperative Organizations have seldom faced greater chal- analysis and insights to respond quickly and lenges. Financial markets and corporate finance accurately to a rearranged business landscape. remain volatile. Customer behaviors are evolving as more people shop electronically. Employee But effective master data management (MDM) behaviors are adapting as more staff work has long been an escalating imperative. You need remotely. And operations are adjusting as supply the right data in the hands of the right people chains recoil from sudden shocks. to optimize operations, understand and serve customers, and speed innovations to market It has never been more important for your enter- (see Figure 1). And in a digital economy, you need prise and your lines of business (LoBs) to have those insights fast. access to trusted, high-quality data. They require Figure 1: Business-Critical Initiatives Supported by MDM E nsure r ies.
    [Show full text]
  • IBM Industry Models and IBM Master Data Management Positioning And
    IBM Analytics White paper IBM Industry Models and IBM Master Data Management Positioning and Deployment Patterns 2 IBM Industry Models and IBM Master Data Management Introduction Although the value of implementing Master Data Management (MDM) • The Joint Value Proposition summarizes the scenarios in which solutions is widely acknowledged, it is challenging for organizations IBM Industry Models and MDM accelerate projects and bring to realize the promised value. While there are many reasons for this, value. ranging from organizational alignment to siloed system architecture, • Positioning of IBM MDM and IBM Industry Models explains, by certain patterns have been proven to dramatically increase the success using the IBM reference architecture, where each product brings rates of successful projects. value, and how they work together. • IBM Industry Models and MDM deployment options describes The first of these patterns, which is not unique to MDM projects, is the different reasons for which IBM Industry Models are that the most successful projects are tightly aligned with a clear, concise implemented, and how IBM Industry Models are used together business value. Beyond this, MDM projects create challenges to an with IBM MDM in implementing a solution. organization along several lines. • A comparison of IBM Industry Models and MDM discusses the similarities and differences in structure and content of IBM • MDM is a business application that acts like infrastructure. Industry Models and IBM MDM. Organizations need to learn what this means to them and how they are going to adapt to it. This document is intended for any staff involved in planning for or • Although MDM projects might not start with data governance, implementing a joint IBM Industry Models and MDM initiative within they quickly encounter it.
    [Show full text]