Continuing from my last post on MDS which has link
- MSBI # 32 – MDS #2 –Understanding Environment Master Data Services(MDS)
- MSBI # 31 – MDS #1 – Lets have an introduction to Master Data Services(MDS)
Some of folks here ask me before I dig into actual topic of MDS they all wanted to know project phase approach for MDS i.e how MDS is going to use as project development approach
When I am searching for same topics I just came across various pdf and whitepaper so just try to gather all of them at one article so that my reader can have all look one glance itself
So here in this article I am going to cover following all project phase approach for MDS
- Bringing Master Data Management to the Stakeholders
- Master Data Management from a Business Perspective
- Master Data Management from a Technical Perspective
- Implementing a Phased Approach to Master Data Management
- What new in MDS in SQL server Denali
Following points are covered in this post
Now lets go ahead cover each points
Bringing Master Data Management to the Stakeholders
- MDS is single valid integrated place for all type of data.
- A master data management project brings together users of disparate roles including business users, technologists, sales people, and foremen.
- Provider constant and static framework for organization and make it consistence and stable growth in all IT essential structure
- Data governance sets the rules for data management in an organization. Examples of data governance rules are required fields, standard values, encryption or security requirements, data retention policies, and so on.
As master data is integrated across the organization, a number of governance issues must be addressed:
- How will the organization manage changes to the master data?
- What rights does each group have over attributes of the models they maintain and consume?
- How will dependencies be monitored and managed?
- When data inconsistencies arise, how will these be addressed?
Master Data Management from a Business Perspective
As organization grows in every way and all its size only one thing important thing in all way out of it is Having build successful master data on top of it .
But following are many challenges for MDS of different size organizations
Why we required master Data
In may application we do develop MDS but that is only related to that application only such as ERP,BI
But Due to MDS we can have one project build and can be used in all projects ‘
A true master data management solution must be process-agnostic and customizable to the needs of the organization. With time and consideration, business stakeholders can determine how a master data management solution will help their business and determine which domains should be integrated first.
Master Data Management from a Technical Perspective
MDS can be implemented in following four ways
- Master Data registry implementations
- Data aggregation implementations
- System-of-record-only implementations
- Complete enterprise master data management implementations
Following is various system where we are actually using MDS in different forms
Master Data registry implementations
Following implementation overview for registry
Data aggregation implementations
Following implementation overview for Data aggregation
Following implementation overview for System-of-record
Complete enterprise master data management implementations
Following implementation overview for Complete enterprise master data management
Implementing a Phased Approach to Master Data Management
As MDS consider all the entities and its respective attribute and behaviors too we cant have completion of MDS in one go
We have divide each MDS project in to chuck of phases and started implementing it !!
Following are some well know approaches:
Single Dimension Build Out
This approach is applicable when the master data management problem has these characteristics:
- Single dimension is affected
- Low resistance to a new system of entry for this dimension
- Minimal additional stakeholders required for complete implementation
- Central data management (at least for the dimension in question)
- In this approach we may divide project into two parts
- Phased Approach – Before
- Phased Approach – After
Following is example overview of Phased Approach – Before
Following is example overview of Phased Approach – After
Regional Build Out
These projects can be identified by regional autonomy. By implementing master data management in a phased approach, organizations can also lessen the costs of travel and time zone differences. It is likely that subtle differences will exist between regions.
Following is example overview of Regional Build Out
Denali enhancement in MDS
- Help ease data management with MDS designed to deliver credible, consistent data
- Manage data that is worthwhile for the consumer
- Leverage self-service data management with the MDS add-in for Excel
- Help reduce time-to-solution
- Enable rapid insights and trusted analytics
- Help ease data management
- Now form next post will dig more into MDS core !!
Hope this helps !!
Thanks for reading my blog !!
For more interesting links and daily update please subscribe our link resource website
Todays link are follows: