Master data management solutions have mostly evolved from the need of large organizations to better manage either their customer data or product data, both of which tend to be in a poor state in most of the companies. However master data goes beyond product and customer, including detailed information such as location, organization, financial information etc. One specific area that has emerged recently is companies specializing in dealing with supplier data in particular. Now of course many generic Master Data Management technologies are perfectly capable of handling supplier data; they may treat a supplier as a "party" and can treat it in a similar way to customer. However, there are aspects of supplier data that mean that some more specific attention is required.

We are in the early stages of designing a Data Governance Organization in my company. I am interested in any best practices, guidance or suggestions from this community. While we want to build the governance needed to maintain a high data quality standard, we do not want to be a hindrance to getting things done!

I have been doing some research on standard naming conventions for business rules and I have hit nothing but roadblocks. When managing business rules in a tool, are there any guidelines out there on how best to name a business rule? Whereas requirements can be named using a [verb-phrase]+[noun-object] format, this does not always apply to business rules since not all rules describe active behavior.

Have you come across, or do you use, any standards when giving a name or title to a business rule?