M

Tuesday, November 9th, 2021 3:27 PM

How do you govern End-User Computing at your organization?

At various of our clients we get the question how to document & govern EUC within Collibra. This includes the End-User Computing Application itself (e.g. Excel with macros) but also the outcome (e.g. a generated report, shared with consumers within or even outside your organization).

How do you tackle this at your organization?

640 Messages

 • 

1.6K Points

3 years ago

@martijn.datashift.eu, I’ve moved this to the more active ‘Product Q&A’ discussion category as we have archived the ‘Use Cases’ category as we try to move towards more product/solution-specific discussion categories to, hopefully, increase response times.

1.2K Messages

3 years ago

What are your criteria for what should be governed or not?
Why does it matter and what’s your objective?

Documenting all EUC is an impossible task given the current technologies available (maybe microsoft can build that into Office/Purview at some point). So that comes down to documenting business processes, data and reports manually.
At which point does an excel file become so important for governance that you want to catalog it? Maybe it supports business critical processes, and you need a way to identify and flag those.

A good practice I saw from Adeo at one of the last meetups was to put the Collibra URL into their avro schema definitions => Establishing checkpoints and making sure the files have a collibra ID (maybe a property in the excel file) is a good way to identify those important data managed by users.

3 years ago

Hi Arthur,

Thank you for your feedback. To answer your question:

  1. first step = get a complete and accurate overview of the current data landscape (including EUCs)
  2. second step = define some guidelines to classify which EUC need to be governed (prioritization exercise: e.g. input for important processes/reports)
  3. third step = define a tbd layer of governance for those EUCs

In paralel issues like: very similar processes/EUC tools,… can be identified and solved.

1.2K Messages

Trying to get a "complete and accurate overview of the current data landscape (including EUCs)" might be an impossible task, especially considering the amount of EUC that is typically ongoing in a company.

Probably better that you set yourself some inclusion/exclusion criteria, and identify the checkpoints where you’ll collect information. e.g. if you say that all inputs to the data warehouse/reporting layer should be documented, AND it so happens that there are some excel files ingested, then you can include them in your analysis.

Everything that is simply a user doing some excel analysis to type in numbers manually should not be included and considered out of scope. When exceptions start to arise, you can manually add those.

Loading...