DO – Data Owner (Biz)

Mission

• Ensuring the dataset is used in a secured and compliant manner to address business requirements across the dataset lifecycle

---

Responsibilities

• Dataset attributes (business data) in the Data Governance tool (Collibra)

  • ADO name conventions are followed

  • Self-descriptive definition of the dataset content and purpose is in place

  • Information of the dataset (metadata) is accurately recorded and maintained up-to-date.

  • Business rules are documented and accurately recorded

  • IPA is collected and attached to use cases requesting access to PII for datasets classified “orange” and “red”

  • Record of use cases is documented and maintained up-to-date (date the access was granted, requester, use case description)

  • Dataset Linage related to traceability of its business usage (technical linage is responsibility of the data steward)

    • When the dataset is built with the combination of pre-existing datasets, inform those dataset owners of any change in the dataset configuration and usage

    • When the dataset is souring another dataset, inform the dataset owner of any change in the dataset configuration and usage

  • Data Steward is assigned and up-to-date

• Dataset access requests

  • Collect the input from the supporting stakeholders CISO (BISO/TISO), LEG and R&D to ensure the use case is compliant with all the applicable rules to the risk levels defined for the dataset. When PII in the dataset, ensure data privacy constrains are checked and validated with LEG

  • Assess the use case against the ADO guidelines to ensures policies, standards and rules are enforced

  • Approve/reject the request in a timely manner (SLA)

• Dataset lifecycle

  • Address use case data quality requirements and engage with the data steward to implement those technically

  • Any change in the dataset configuration (e.g., new data instances or new data points) is assessed against the risk levels and other applicable data rules.

  • Ensure retention and disposal policies for data are applied

  • Collaborate in the resolution of any data privacy issue affecting the dataset

• Relationship with the BDO

  • Escalate to the Business Data Officer (BDO) any issue or impediment (lack of support, conflict with other responsibilities, …)

  • Communicate any change in other no-DO related responsibilities, affecting the DO duties

  • Inform Business Data Officer (BDO) in advance of any leave period (e.g. holidays, maternity) to ensure a backup is in place

  • Contribute to the monitoring and reporting activities for the data domain

• Training and education

  • Complete the training required to perform the role functions

  • When leaving the role, ensure a new entry is identified, proper handover is done, and the data governance tools are updated in accordance