INTRODUCTION :
This Tutorial is on Master Data Management for Local Government.
It presents the Steps involved as Best Practice.
Topics covered in this Tutorial include Data Sources and Targets, mapping between them, Data Quality, Data Governance and Reference Data
I hope you find this Tutorial interesting and helpful.
Please
email us and let me know, and you can also
email us for a detailed Mapping Specifications document.
These are the Steps in the Tutorial :-
- Agree the Scope of the Project
- Identify the Data Sources
- Determine the Target
- Specificy the Mapping between Sources and Target.
- Review Guidelines for managing Reference Data
- Address the Issue of Data Quality
- Ensure comliance with Data Governance
- Check that the MDM Data Model can provide data for Perforcement Reports as specified by the Users.
My starting-point is the Data Model for
Customers and Payments in e-Government.
|
This is the MDM Local Government Generic Enterprise Data Model which is the Target
This shows how data from a number of sources is integrated into one Generic Master Data Management Model.
|
1) ENTITY MAPPING SPECIFICATIONS :
Source Area |
Source Entity |
Target Entity |
Ref Data |
Council_Tax |
Council_Tax |
MDM_Customers |
  |
|
|
|
|
Electoral_Register |
Electoral_Register |
MDM_Customers |
  |
|
|
|
|
Housing_Benefits |
Housing_Benefits |
MDM_Customers |
  |
|
|
|
|
Parking_Tickets |
Parking_Tickets |
MDM_Customers |
  |
Parking_Tickets |
Parking_Payments |
N/A |
  |
Parking_Tickets |
Ref_Payment_Methods |
Ref_Data |
Yes |
|
|
|
|
Social_Services |
Social_Services |
MDM_Customers |
  |
|
|
|
|
|
2) REFERENCE DATA :
Each Data Source will have its own sets of Reference Data.
These have to be mapped to a common set of Data, which in turn is subject to corporate Data Governance.
|
|
|
3) MDM CUSTOMERS AND SERVICES :
Source Area |
Source Entity |
Target Entity |
Ref Data |
Council_Tax |
Council_Tax |
MDM_Customers |
  |
|
|
|
|
Electoral_Register |
Electoral_Register |
MDM_Customers |
  |
|
|
|
|
Housing_Benefits |
Housing_Benefits |
MDM_Customers |
  |
|
|
|
|
Parking_Tickets |
Parking_Tickets |
MDM_Customers |
  |
Parking_Tickets |
Parking_Payments |
N/A |
  |
Parking_Tickets |
Ref_Payment_Methods |
Ref_Data |
Yes |
|
|
|
|
Social_Services |
Social_Services |
MDM_Customers |
  |
|
|
|
|
|
4) COUNCIL TAX :
This shows the fields in the Tables that are candidates for mapping to the MDM Tables.
Council Tax Table |
Reference Data |
Comment |
ct_resident_id |
  |
  |
ct_resident_details |
  |
  |
|
|
|
5) ELECTORAL REGISTER :
This shows the fields in the Tables that are candidates for mapping to the MDM Tables.
Electoral Register Table |
Reference Data |
Comment |
er_voter_id |
  |
  |
er_voter_details |
  |
  |
|
6) HOUSING BENEFITS :
This shows the fields in the Tables that are candidates for mapping to the MDM Tables.
Housing Benefits |
Reference Data |
Comment |
hb_recipient_id |
  |
  |
hb_recipient_details |
  |
  |
|
|
|
7) PARKING TICKETS :
This shows the fields in the Tables that are candidates for mapping to the MDM Tables.
Parking Tickets Table |
Reference Data |
Comment |
pt_offender_id |
  |
  |
pt_offender_details |
  |
  |
Parking Tickets are not Master Data and are not included in this mapping activity.
However, the Payment Methods are Master Data and they are included in the Reference Data category.
|
8) SOCIAL SERVICES :
This shows the fields in the Tables that are candidates for mapping to the MDM Tables.
Social Services |
Reference Data |
Comment |
ss_client_id |
  |
  |
ss_client_details |
  |
  |
|
|
9) DRAFT FIELD LEVEL MAPPING SPECIFICATIONS TO THE MDM DATA MODEL :
These Specifications have been partially completed to provide guidelines.
Source Area |
Source Entity |
Source Field |
Field Validation |
Field Transformation |
Target Entity |
Target Field |
Council Tax |
Council Tax |
ct_resident_id |
Mandatory |
Created in CMI |
MDM_Customer_Index |
AutoIncrement |
Council Tax |
Council_TaX |
ct_resident_details |
  |
To be determined |
MDM_Customers |
To be determined |
  |
  |
  |
  |
  |
  |
  |
Electoral_Register |
Electoral_Register |
er_voter_id |
Mandatory |
Created in CMI |
MDM_Customer_Index |
AutoIncrement |
Electoral_Register |
Electoral_Register |
er_voter_details |
  |
To be determined |
MDM_Customers |
To be determined |
  |
  |
  |
  |
  |
  |
  |
Housing_Benefits |
Housing_Benefits |
hb_recipient_id |
Mandatory |
Created in CMI |
MDM_Customer_Index |
AutoIncrement |
Housing_Benefits |
Housing_Benefits |
hb_recipient_details |
  |
To be determined |
MDM_Customers |
To be determined |
  |
  |
  |
  |
  |
  |
  |
Parking_Tickets |
Parking_Tickets |
pt_offender_id |
Mandatory |
Created in CMI |
MDM_Customer_Index |
AutoIncrement |
Parking_Tickets |
Parking_Tickets |
pt_offender_details |
  |
To be determined |
MDM_Customers |
To be determined |
Parking_Payments |
Parking_Payments |
pt_payment_id |
  |
  |
N/A |
  |
  |
  |
  |
  |
  |
  |
  |
Social_Services |
Social_Services |
ss_client_id |
Mandatory |
Created in CMI |
MDM_Customer_Index |
AutoIncrement |
Social_Services |
Social_Services |
ss_client_details |
  |
To be determined |
MDM_Customers |
To be determined |
  |
  |
  |
  |
  |
  |
  |
REFERENCE DATA ... |
Source Area |
Source Field |
Target Field |
Council_Tax |
  |
  |
  |
  |
  |
Electoral_Register |
  |
  |
  |
  |
  |
Housing_Benefits |
  |
  |
  |
  |
  |
Parking_Tickets |
  |
  |
Parking_Payments |
  |
N/A |
  |
  |
  |
Social_Services |
  |
  |
|
PLEASE EMAIL ME
- During this short Tutorial,we have covered the following Topics :-
- An Approach to MDM
- Creating a Data Dictionary
- Mapping from Sources to the Target MDM Data Model.
- Reference Data
- I hope you have found this Tutorial interesting and useful.
- I would be pleased to have
your comments with your questions or suggestions.
Good luck with your first MDM Project !
Barry Williams
Principal Consultant
Database Answers Ltd.
London, England
|