Data Mastering Model policy governing usage Deliverable Template
From MIKE2.0 Methodology
||This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.
|This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
|Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.
The Master Data Management Architecture is determined by mapping a candidate system of record to each KDE using a Data Mastering Model. The Data Master Model defines:
- Primary Masters (System of Record) Primary Master is a system having ownership of a business event and is seen as the authority on this data. There may not always be a primary master for a business event and there can never be more than one primary master.
- Secondary Masters: The Secondary Master has the ability to update relevant elements, but only on reconciliation from the primary master and other secondary masters.
- View Only: A View Only system cannot update, and is only a receiver of data changes.
This task can be done in an iterative fashion, with obvious candidates being defined first. The Data Governance Council reviews this model and can be used to resolve disputes when multiple candidates exist.