Warning: Creating default object from empty value in /home/johnnz/public_html/wp-content/themes/simplicity/functions/admin-hooks.php on line 160
Tag Archives: #MDM

Logical Data Model for Customer & Supplier

The logical data model below shows the data structure needed to support Customer, Supplier and Employee.  Pardoxically, none of these appear as an enitity on model! How can that be? There is a very good reason for this, which is that Supplier, Customer and Employee are all deriveable data entities and, as such, ought NEVER […]

2 Comments Continue Reading →

Customer is Not a Master Data Enitity.

Having Customer and Supplier as Master Data Entities is about as sensible as having Creditor and Debtor. Why? Because all of these terms refer to derivable relationships and implementing them as Master Data Entities is both a modelling and business error. If this is true, why are they so often modelled as such? It all […]

1 Comment Continue Reading →

There Are No Such Things as Data Rules!

This may come as a surprise to many involved in Data Quality but, wait for it, there are no such things as data rules! By looking at data you can never deduce or define a rule that dictates that one entity should be related to another or that a value of an attribute of an entity has to be, in a certain format and have limits to its value. So what does dictate data content, structure, format and constraints?
Click on “Read More” and find out why….

12 Comments Continue Reading →

There's No Such Thing as a Customer!

“Customer” is one of the Data Enitities that lies at the heart of most MDM practices in enterprises around the world and it is not in fact a Data Entity at all! This situation has arisen because far too much “data quality” work is done without the use of a properly structured Logical Data Model. This work then serves to perpetuate rather than remove fragmented data structures.

17 Comments Continue Reading →

Unique Keys are the Primary Cause of Duplication in Databases

It is perhaps the greatest paradox of data quality that the PRIMARY cause of duplication of entries in any database is the mistaken use of unique keys as the Unique Identifiers UIDs) of records.
Click on “Read More” to learn how to avoid this error.

8 Comments Continue Reading →

Five Key Steps to Quality Data Modelling

To most business people data modelling is a black art that is practiced by the company IT department. It brings no tangible business benefits and is solely designed to make mere mortals feel confused and inferior.  Sadly, many IT departments actually foster this view and, for those that do, the data modelling that they carry […]

Leave a comment Continue Reading →