Skip to main content
Version: 2.0.0

Governance (formerly Data Governance)

Menu access

The module is located under Operations > Governance (formerly Data Governance), with the My Actions, 360° View and Quality entries. Rule configuration (configurator, simulation, governance rules, configuration) is grouped under Design > Traceability (formerly Etiquettes Manager). When you hover over a renamed entry, a "Formerly: …" tooltip shows its previous label.

Screenshots being refreshed

Most screenshots on this page reflect the 2.0.0 interface. Some screenshots (Executions with the link to governance actions, label sheet in the Data Shop, label details and lineage tree in the 360° View) still show the previous interface and will be refreshed shortly.

Introduction: Data governance framework and process​

Data governance framework: layered model​

Data governance brings together all the processes, roles, policies and tools needed to guarantee the quality, security, compliance and value of the company's data.

Layered model of Data Governance: Data Governance, Federated Data Governance, Operational Data Governance

Toward operational data governance with Orkestra​

ORKESTRA provides a set of features covering all the key points of Governance. In this guide, we will focus on explaining:

  • The configuration of Governance rules
  • The application of governance rules

Orkestra's operational response to the layered Data Governance model, showing for each operational building block the associated Orkestra feature (Datafabrik, Contextualized label, Traffic lights, Governance & Datashop, Logs & Supervision, Traceability)

General presentation of governance rules​

  • A pack of governance rules is available as part of the Orkestra offering.
  • These predefined governance rules bring together several rule values. Rule values can be linked to one another.
  • Governance rules are associated with a tagged object when it is created, so they can be applied to the resulting label.

General presentation of the available governance rules (« Approbation » (Approval), « Certification » (Certification), « Confidentialité » (Confidentiality), « Diffusion (Périmètre) » (Distribution (Scope)), « Diffusion (Etat) » (Distribution (Status)), « Archivage » (Archiving), « Suppression » (Deletion)) and their possible values, grouped into Validation, Sharing and Purging

Overview of the Governance process in Orkestra​

  1. Defining users (see the dedicated guide)
    1. Role on governance rules
  2. Defining a tagged object (see the dedicated guide)
    1. Selecting Governance rules
  3. Defining a UTD (see the dedicated guide)
    1. Associating a module with governance rules
  4. Tagged production in Orchestration (formerly Data Fabrik) (see the dedicated guide)
    1. Managing entitlements
  5. Applying Governance rules
    1. Applying a governance rule
    2. Enabling data distribution
    3. Production / governance / distribution / Data Shop workflow
    4. Viewing label contexts
    5. Accessing data quality

9 steps specific to managing governance rules​

Preparation steps:

  • Step 1: user roles
    • Prerequisite for managing entitlements
  • Step 2: choice of governance rules
    • Among the list of available rules, select for each tagged object those that apply
  • Step 3: associating governance rules with a module
    • Indicate, per module, whether production is subject to governance rules
  • Step 4: managing entitlements
    • Identify the users authorized to manage the governance rules of productions

Production steps:

  • Step 5: governance follow-up
    • Update rule values per label to keep your datasets current
  • Step 6: data distribution
    • Manage access to produced datasets
  • Step 7: overall workflow
    • Facilitation within Orkestra to logically chain steps 5 and 6

Consultation steps:

  • Step 8: viewing label contexts
    • Access to the information describing each dataset
  • Step 9: accessing data quality
    • Access to the detailed qualifications of the produced datasets

ORKESTRA PREREQUISITES: Preparing to manage governance rules​

Step 1: User roles​

  • Defining the users who can manage the governance rules of productions
    • Users with the « Super-Admin » role: these users can modify all governance rules of all productions.
  • Users with the « Créateur » (Creator) and/or « Administrateur » (Administrator) role
    • These users will be eligible to be assigned to modify the governance rules of a future production (see step 4 below).

Settings Menu

  • Settings > Access & Permissions (formerly Administration) > Users / Authorizations

Settings menu > Access & Permissions expanded, with the Users, User templates, Authorizations and Login statistics entries

« Ajouter un rôle » (Add a role) window for a user, with the Data Governance application and the list of roles (Viewer, Creator, Data Driven, Super-Admin)

Step 2: Choice of governance rules​

The selection is made in two stages:

  • First stage: the list of rules available in Orkestra
    • This list cannot be modified; it may evolve with future Orkestra versions.
    • Each predefined rule has specific characteristics (see the following sections).
  • Second stage: choosing the rules applicable per label template
    • For each tagged object, it is possible to indicate, among the available rules, which ones will apply, so that every label generated from it will have the applicable rules associated with it (see the procedure below).

1) List of available rules: viewing general information​

Design Menu (formerly Management)

  • Design > Traceability (formerly Etiquettes Manager) > Governance Rules (formerly Rules Customization) / governance rules

  • A pack of data governance rules is available in Orkestra.

  • These rules cannot be modified.

  • This rule pack is automatically attached to all tagged objects (see the guide on defining a tagged object).

  • For each rule, the following information is available:

    • A unique code
    • An expressive label
    • A detailed explanatory description
    • A time dimension:
      • None: the rule has no notion of time.
      • Duration: it is possible to define a duration in days for the rule's validity (example: a label template will be approved for a duration of 30 days).
      • Period: it is possible to define a period in days for the rule's validity (example: a label template will be distributable for a period of 60 days).
      • Deadline: it is possible to define a number of days that will determine the date on which the rule takes effect (example: a label template will be archived after 90 days).

Design > Traceability > Governance Rules screen, Governance rules tab, listing the available rules with their code, label, description and time limit

1) List of available rules: viewing the possible values per rule​

Design Menu

  • Design > Traceability > Governance Rules / rule values

The following properties are associated with these rules:

  • Display order: the list of values for the rule concerned is displayed in the order specified when entering a value (see the chapter "Entering a governance rule value").
  • Time limit start? (Y/N): indicates whether the rule value is associated with a date from which the deadline is calculated.
  • Action: for now, defined only virtually (no action is actually triggered by Orkestra).
  • Value after deadline: when displaying the governance rules available for a label, this is the value shown by default once a deadline has been reached (see the chapter "Entering a governance rule value").
  • Default value: when displaying the governance rules available for a label, this is the value shown by default for a rule (see the chapter "Entering a governance rule value").

Rule Values tab showing, for each rule and value, the display order, time limit start, action, value after deadline and default value

1) List of available rules: viewing linked rules​

Design Menu

  • Design > Traceability > Governance Rules / linked rule values

Relationships between rules can be defined. Here, between the rules « Approbation » (Approval) (value: « Rejeté » (Rejected), « Périmé » (Expired)), « Certification » (Certification) (values: « Non certifié » (Not certified), « Certification périmée » (Certification expired)) and « Etat diffusion » (Distribution status) (« Non diffusable » (Not distributable)).

Example: when the « Approbation » (Approval) rule takes the value « Rejeté » (Rejected), the « Certification » (Certification) rule takes the value « Non diffusable » (Not distributable).

Linked Rule Values tab showing the relationships between rules, for example "Rejeté" (Rejected) linked to "Non diffusable" (Not distributable) and "Non certifiée" (Not certified)

2) Configurator: choosing the applicable rules per tagged object​

Design Menu

  • Design > Traceability > Configurator / Tagged objects

  • The configurator is used to make one or more predefined rules applicable to a tagged object.

  • The rules made applicable in this way will be available for every future label generated.

  • Adding or removing applicable governance rules has no impact on labels already generated.

Configurator screen > Tagged objects, with the choice of tagged object and the table of applicable rules (rule code, value, applicable, deadline or duration)

2) Configurator: applying or not applying a rule and adding time information​

Design Menu

  • Design > Traceability > Configurator / Tagged objects

To apply a rule:

  1. Double-click on the rule.
  2. Click « Rendre applicable » (Make applicable) and, if needed, enter time units for the deadline.
  3. Save.

"Edit Rule" window with the "Rendre applicable" (Make applicable) option and entry of a deadline or duration in days

Step 3: Associating governance rules with a module​

  • For each module, it must be indicated whether it is subject to governance rules.
    • This setting is used during production to determine whether or not to display the area for designating the users who will have rights to modify the governance rules.
    • This is configured at the module definition level, via a « Soumis aux règles de gouvernance » (Subject to governance rules) checkbox. It is visible in the table and editable at the bottom of the edit pop-up.
    • When a UTD version is duplicated, the value of this field is automatically copied over for each module.

Design Menu

  • Design > Flow > Processing (formerly UTD Manager > Declaration) / governance rules

Module table of a UTD version in Design > Flow > Processing, with the "Gouvernance" (Governance) column (shown via the column selector)

Module edit window with the "Soumis aux règles de gouvernance" (Subject to governance rules) checkbox

Step 4: Managing entitlements​

  • During a production, it is necessary to indicate who will be able to modify the governance rules.
    • A multi-user selection field in the UTD production creation screen is used to designate the people responsible for the associated data governance.
    • This field is displayed only if the selected module is subject to governance (see step 3).
    • Only users with a « Créateur » (Creator) or « Administrateur » (Administrator) role in the Data Governance application can be selected (see step 1).
    • This field can be searched by last name and first name.
    • If an equivalent production (same UTD + module) has already been carried out, the previously designated owners are proposed by default.
    • The field remains editable before validation and is not required; in that case, only Super-Admin profiles on the "Data gouvernance" (Data Governance) application will be able to update the governance rules.

"Nouvelle production" (New production) window for a module subject to governance, with the "Responsable(s) de la data gouvernance" (Data governance owner(s)) field

PRODUCTION: Applying a governance rule to a label​

Step 5: Governance follow-up​

  • The objective is to update the governance rule(s) associated with a completed production (see step 2).
  • The production must be associated with a module subject to governance rules (see step 3).
  • The user must be entitled to the "Data gouvernance" (Data Governance) application (see steps 1 and 4).
  • There are two ways to find the governance rules to update:
    • Option 1: Selecting a label from a request number.
    • Option 2: Selecting a label via multi-criteria search.

Finding the label to apply a rule to — Option 1​

Selecting a label from a request number:

  1. Select the request number.
  2. Double-click on the row of the rule whose value you want to enter.

Actions tab of the My Actions screen listing the rules to update per label, with their request number

Entering a rule value: example of the « Certification » (Certification) rule​

  1. Enter the value.
  2. Value entered.

Operations Menu (formerly General)

  • Operations > Governance (formerly Data Governance) > My Actions (formerly Governance actions)

Operations > Governance menu expanded (My Actions, 360° View, Quality) and the My Actions screen

"Edit Rule" window showing the current value and the list of possible values (example of the Approval rule)

Finding the label to apply a rule to — Option 2​

Selecting a label via multi-criteria search:

B) Filtered search

  • Example: by UTD module.
  • Then choose from the list of matching labels.

Management tab filtered by UTD module, listing the matching labels

C) Filtered search

  • Example: by label.

Management tab filtered by a search on a label, showing the label being searched for

Entering a rule value: example of the « Approbation » (Approval) rule​

  1. Double-click on the row of the rule whose value you want to enter.
  2. Enter the value.

"Edit Rule" window opened from the label's rules, with the selected value

PRODUCTION: Enabling data distribution​

Step 6: Data distribution​

  • By default, produced datasets are not visible in the Data Shop.
  • For each label, the access mode must be specified:
    • Either named: by selecting the desired user(s).
    • Or public.
  • Once these entitlements are set, the datasets become accessible via the Data Shop.

Operations Menu

  • Operations > Governance > My Actions / Management

1. Named access​

"Quick entitlement management" window for named access, with a user selected and the Authorize option

2. Public access​

"Quick entitlement management" window for public access

PRODUCTION: Production / governance / distribution / Data Shop workflow​

Step 7: Workflow​

Concept​

To simplify the overall governance process, user "shortcuts" have been added. These shortcuts take the form of hyperlinks that make it easy to move from:

  • A production
  • To its results
  • And therefore to the screen for applying its rules
  • Then to distribution management
  • And finally to the Data Shop.

Here we will look at how the steps described previously are simplified from a business-user perspective.

1. From production to applying a rule​

From Operations > Orchestration > Executions (formerly UTD Production), clicking on a production request number takes you directly from a production to the requested governance actions (Operations > Governance > My Actions).

Note

The link is available only if governance actions are required (see further below: "Workflow 4. Case of a label with no governance actions to process before distribution").

Operations > Orchestration > Executions screen, with a production request number selected

2. From applying a rule to distribution​

From the list of actions, clicking on a production request number takes you, within Operations > Governance > My Actions, from the Actions tab to the Management tab. This screen is used to configure the distribution of a label.

Governance Actions tab, with the production request number shown as a link

3. From distribution to Data Shop access​

Once distribution has been configured, clicking on the label provides direct access to the Data Shop to view the label and download its content.

Management tab, with the label and the request number shown as links

Label information sheet in the Data Shop

4. Case of a label with no governance actions to process before distribution​

If no governance rule is required on a production (no hyperlink present), it is still necessary to go and configure the distribution of the generated labels.

  • Go to the Operations > Governance > My Actions menu.
  • Click on the MANAGEMENT tab.
  • Configure the distribution of a label.

Operations > Orchestration > Executions screen, with a production request showing the "Aucune règles de gouvernance" (No governance rules) tooltip

CONSULTATION: Access to context data​

Step 8: Access to context data​

Operations Menu

  • Operations > Governance > 360° View (formerly Governance context)

Viewing general information​

  • Searching for the label using the filters.
  • Access to the label and its descriptive information: label name, date, scope, etc.

360° View screen, with the search filters and the list of labels

Viewing descriptive information​

  • Click on the dropdown menu shown as a black triangle.
  • Access to descriptive information: UTD, requester, referent, etc.

Governance Context screen, with the dropdown menu expanded showing the request number, the UTD and the module description

Viewing the lineage tree​

Access to the label lineage tree, covering:

  • Production: from which other label(s) is the label being viewed produced?
  • Consumption: by which other label(s) is the label being viewed consumed?

Icon for accessing the lineage tree of a label in the Governance Context screen

Lineage tree of a label with the Production and Consumption tabs

CONSULTATION: Access to data quality​

Step 9: Access to production quality​

Objective: faster, more detailed analysis of the most frequently encountered quality issues.

  • Access to information about requests (Number, UTD, Module, Production Info) and their Qualifications.
  • Detailed access to all the rules processed per production, regardless of their number.

Operations Menu

  • Operations > Governance > Quality (formerly Production quality)

Quality screen, listing requests with their UTD, module, qualification rule, qualification, nature and status