STEMMONS Data Governance

Data Governance

Ensuring a company's information database is full of good, clean data is one of, if not the most, important aspects of a company's operation. Any software or procedure within a company will function at its best when the data feeding it is as organized and clean as possible. Central aids in the management and maintenance of data within an enterprise by periodically ensuring that data quality inspections are carried out on a regular basis. Any problems found through inspection, or independently by an employee noticing a problem, is quickly addressed and corrected in order to resume operations with good data.

User Experience:

  • CAST runs on a periodic basis creating a case for data analysis
  • Case is assigned to data analyst to complete a data governance inspection of a specific section of the company's information database
  • Quest form is used in the inspection, for any data issues that is found in the inspection a case is created
  • Alternatively, if an employee at any point notices an issue with company data, they can create a case for correction
  • Data governance cases are assigned to a Hopper that a data analyst manages
  • Data analysts assign casesfrom Hopper to correct individual in order to correct data issue
  • A link to instructions on how to correct issue is inculded in every case

Functional Setup:

  • CAST must be programmed to create cases ona  periodic basis and assign to data analysts
  • Case types must be created for data governance inspections and corrections along with a Hopper 
  • Data analyst must be associated as hopper manager 
  • Instructions and procedures to correct data must be created and documented in Standards
  • Quest form must be created for the various data QA inspections to be performed

Best Practices:

  • It is the best practice for employees to report any data issue as soon as possible in order for the problem to be corrected. This is very important as there is some data that is only ever seen or utilized by a few people within a company and might never be corrected if not reported.
  • Similarly Data QA inspections should cover all sections of the company in order to identify any and all problems in the company database
  • Data analyst assigned as Hopper manager should be one that is familiar with other's skills in order to more efficiently assign cases

2 thoughts on “Data Governance

  1. Robert Panetta says:

    I’d like to remove steps 2-4 and replace with a business rule to be tested against facts, then cast cases to data stewards accociated with the broken rules.

  2. Scott Heikkila says:

    Bob, great feedback and yes that can be done and is in practice. A “Trigger” can be configured to look for the data related to the “broken rules” and initiate a case when found, essentially automating the analysis part above.

Leave a Reply

Your email address will not be published. Required fields are marked *