{"id":28,"date":"2010-12-23T22:57:36","date_gmt":"2010-12-23T17:27:36","guid":{"rendered":"http:\/\/www.jkspeaks.com\/wordpress\/?p=28"},"modified":"2011-01-30T23:06:09","modified_gmt":"2011-01-30T17:36:09","slug":"data-governance-a-beginners-approach-to-level-2-implementation","status":"publish","type":"post","link":"https:\/\/www.jkspeaks.com\/wordpress\/business-intelligence\/data-governance-a-beginners-approach-to-level-2-implementation\/","title":{"rendered":"Data Governance: A beginners approach to Level-2 implementation"},"content":{"rendered":"<p style=\"text-align: justify;\"><strong>The 3-Level approach<\/strong><br \/>\nThe 3-level approach (Figure 1) works  well when the organization is serious, has the required funding, resources to  execute and a mature Enterprise Information Management (EIM) setup.<\/p>\n<p style=\"text-align: justify;\"><a href=\"https:\/\/www.jkspeaks.com\/wordpress\/wp-content\/uploads\/2011\/01\/3level.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-19\" title=\"3level\" src=\"https:\/\/www.jkspeaks.com\/wordpress\/wp-content\/uploads\/2011\/01\/3level.png\" alt=\"\" width=\"450\" height=\"169\" srcset=\"https:\/\/www.jkspeaks.com\/wordpress\/wp-content\/uploads\/2011\/01\/3level.png 450w, https:\/\/www.jkspeaks.com\/wordpress\/wp-content\/uploads\/2011\/01\/3level-300x112.png 300w\" sizes=\"auto, (max-width: 450px) 100vw, 450px\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">In organizations where the IT team is pressurized to show tangible output for  every penny invested, a 4-level approach as shown in Figure 2 can be adopted.  The question, \u201cIs it possible to divide this further into multiple levels?\u201d  might arise. The thumb rule is more the number of levels, the (substantial)  tangible benefit business can see at every stage will reduce. So a faster  turn-around with visible progress should be the mantra for a successful  implementation.<\/p>\n<p style=\"text-align: justify;\"><a href=\"https:\/\/www.jkspeaks.com\/wordpress\/wp-content\/uploads\/2011\/01\/4levels.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-32\" title=\"4levels\" src=\"https:\/\/www.jkspeaks.com\/wordpress\/wp-content\/uploads\/2011\/01\/4levels.png\" alt=\"\" width=\"518\" height=\"166\" srcset=\"https:\/\/www.jkspeaks.com\/wordpress\/wp-content\/uploads\/2011\/01\/4levels.png 518w, https:\/\/www.jkspeaks.com\/wordpress\/wp-content\/uploads\/2011\/01\/4levels-300x96.png 300w\" sizes=\"auto, (max-width: 518px) 100vw, 518px\" \/><\/a><\/p>\n<p>The four level data governance implementation has been considered for this  article as that\u2019s more common in the industry today.<\/p>\n<p style=\"text-align: justify;\"><strong>What do we need for Level-2?<\/strong><br \/>\nTo setup a \u2018very basic\u2019 DG  practice leveraging the existing setup, a database with a few tables, some  scripts to act as a trigger and an intranet portal should suffice. Note that  this is just a starting point and hence focus would be on data quality and not  data governance to begin with. As funds flow in, one can move from data quality  monitoring to data quality control and from there to data governance.<\/p>\n<p style=\"text-align: justify;\"><strong>Going online<\/strong><br \/>\nThe organizations existing intranet portal  would be leveraged and the objective now is to take processes online one by one  starting with the change management process. As part of Level-1 activities, the  DG team would have already defined the process for change management and this  would be used now. Steps to convert this process into something that can be  monitored are as follows:<\/p>\n<ul>\n<li style=\"text-align: justify;\">Capture key fields to be used in the form. Example, Ticket ID, priority of  change request, source &amp; target systems affected, change description,  etc.<\/li>\n<li style=\"text-align: justify;\">Design the form front end with the fields identified and link this with a  database (MS Access, Oracle, MS SQL) at the backend. Mature organizations can  leverage their SOA setup<\/li>\n<li style=\"text-align: justify;\">Define the process flow. Example, who raises the request, what happens next,  who approves it, exceptions handling, etc. This detail would again come from the  detail captured in the previous phase<\/li>\n<li style=\"text-align: justify;\">Now bring in the governance component to ensure that no change gets moved to  production without going through this process<\/li>\n<\/ul>\n<p><span style=\"color: #0000ee; -webkit-text-decorations-in-effect: underline;\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-33\" title=\"DGimplementation\" src=\"https:\/\/www.jkspeaks.com\/wordpress\/wp-content\/uploads\/2011\/01\/DGimplementation.png\" alt=\"\" width=\"343\" height=\"125\" srcset=\"https:\/\/www.jkspeaks.com\/wordpress\/wp-content\/uploads\/2011\/01\/DGimplementation.png 343w, https:\/\/www.jkspeaks.com\/wordpress\/wp-content\/uploads\/2011\/01\/DGimplementation-300x109.png 300w\" sizes=\"auto, (max-width: 343px) 100vw, 343px\" \/><\/span><\/p>\n<p style=\"text-align: justify;\">More the detail captured in step a, tighter will be the governance in step d.  For example, if there is a field to capture the results of QA, automatically it  will imply that the change that is moving to production has to move through QA  (Dev \u2013 QA \u2013 Production). Assuming process has been defined to ensure QA  compliance for approval of change request. Step c which talks about defining  process flow can be accomplished using database triggers and\/or procedures. If  the organization already has a rule engine in place, it can be leveraged  here.<\/p>\n<p style=\"text-align: justify;\">As part of enhancement, this setup can be improved by addition of small bits  like SLA tracking, report generation capability, etc. Report generation  capability can help governance in a major way by helping the DG team to track  various critical parameters like open requests, SLA breaches, requests moved to  production through exception process, etc. This in turn will help the DG team to  fine tune processes and improve their maturity.<\/p>\n<p style=\"text-align: justify;\">Moving ahead and taking another process online, say BI Tools &amp; Technology  control. The steps shown in figure 3 are applicable here also. The difference  would be in steps c and d, where the process is defined and governed.<\/p>\n<p style=\"text-align: justify;\">Some of the other processes that can be brought under the governance control  without too much of cost and effort are:<\/p>\n<ul>\n<li>Database related activities (E.g. New DB creation, index creation)<\/li>\n<li>Data quality dashboard (E.g. rejected records list pulled from ETL, data  certification status)<\/li>\n<li>Data security (E.g. user access to systems)<\/li>\n<li>Training tracker<\/li>\n<\/ul>\n<p style=\"text-align: justify;\">In addition to this, various database triggers can be set to increase  response levels. Primary advantage of getting to this stage is that the users  would now be conversant with various processes in the organization and adapted  to them. Some amount of governance would also have been established to move to  the next level.<\/p>\n<p style=\"text-align: justify;\"><strong>What next?<\/strong><br \/>\nThe organization can now consider moving to  the next level by creating self-healing mechanisms wherever applicable. More  advanced tools like say Kalido can be considered if required to improve the DG  maturity level.<\/p>\n<blockquote><p>I\u2019m really bored today hence posting this blog without much thought. Will  definitely refine it later. Please do feed me with your comments to improve on  this topic.<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>The 3-Level approach The 3-level approach (Figure 1) works well when the organization is serious, has the required funding, resources to execute and a mature Enterprise Information Management (EIM) setup. In organizations where the IT team is pressurized to show tangible output for every penny invested, a 4-level approach as shown in Figure 2 can [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[3],"tags":[8,9],"class_list":["post-28","post","type-post","status-publish","format-standard","hentry","category-business-intelligence","tag-data-governance","tag-dg"],"_links":{"self":[{"href":"https:\/\/www.jkspeaks.com\/wordpress\/wp-json\/wp\/v2\/posts\/28","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jkspeaks.com\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jkspeaks.com\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jkspeaks.com\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jkspeaks.com\/wordpress\/wp-json\/wp\/v2\/comments?post=28"}],"version-history":[{"count":2,"href":"https:\/\/www.jkspeaks.com\/wordpress\/wp-json\/wp\/v2\/posts\/28\/revisions"}],"predecessor-version":[{"id":35,"href":"https:\/\/www.jkspeaks.com\/wordpress\/wp-json\/wp\/v2\/posts\/28\/revisions\/35"}],"wp:attachment":[{"href":"https:\/\/www.jkspeaks.com\/wordpress\/wp-json\/wp\/v2\/media?parent=28"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jkspeaks.com\/wordpress\/wp-json\/wp\/v2\/categories?post=28"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jkspeaks.com\/wordpress\/wp-json\/wp\/v2\/tags?post=28"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}