# data[].attributes.body
test

# data[].attributes.body
Hello Jan

# data[].attributes.body
Data Architecture

# data[].attributes.body
Data Quality

# data[].attributes.body
Metadata

# data[].attributes.body
Data Warehousing & Business Intelligence

# data[].attributes.body
Reference & Master Data

# data[].attributes.body
Document & Content Management

# data[].attributes.body
Data Integration & Interoperability

# data[].attributes.body
Data Security

# data[].attributes.body
Data Storage & Operations

# data[].attributes.body
Data Modelling & Design

# data[].attributes.body
Document Management

# data[].attributes.body
Griffith's big tickets items in this space this year:

Progressing Data Warehouse Upgrade

Finalise Content Manager Upgrade to V10, taking it to the cloud, connecting it to M365

Commencing pilot, ahead of University wide rollout of protective controls associated with sensitivity labels in M365

Commencing review of lifecycle management in business applications (preparing for ongoing assurance reporting)

Finalising advanced retention in M365 (we implemented adaptive scopes, now need to now lift default retention policies and let adaptive scopes take over which will result in nearly 40% of our tenant sites being disposed of)

Currently in procurement for project for PII Discovery and Privacy Uplift Project

# data[].attributes.body
MDM

# data[].attributes.body
How to best introduce data governance across the business given some systems are owned/hosted by work units and not central ITS unit. #avoidculturewars

# data[].attributes.body
Culture change with understanding data governance, and seeing it as a problem solver, not a problem maker.

# data[].attributes.body
wave my magic wand and have data "cleaned" and verified, know where it resides, have complete visibility of all data across the enterprise (no silos or shadow repositories), appropriately allocate data owners and stewards, have it appropriately structured and classified, have a mature data governance framework and lifecycle defined with all the appropriate protection controls working as intended.

# data[].attributes.body
Optimisation and uplift of communication platforms.

# data[].attributes.body
Enterprise Data Governance - Establishing end to end lineage across all information assets and linking to business glossary is one of the prime objectives of this initiative.

# data[].attributes.body
Enterprise Data Governance Platform

# data[].attributes.body
Institutional culture change around information governance and management.

# data[].attributes.body
Replacing Identity Management System to integrate with a System of Reference (that has issues) rather than Systems of Record

# data[].attributes.body
Core HCM replacement (PSHR -> Workday)

# data[].attributes.body
Hub & spoke data analytics team

# data[].attributes.body
People data challenges

# data[].attributes.body
HR Systems "refresh"

# data[].attributes.body
Would love a current corporate knowledge base. Currently too many data silos, too little time, and I desire to not replicate past work efforts

# data[].attributes.body
Better manage the information lifecycle across our business systems, particularly retention and disposal.

# data[].attributes.body
Identity Management

# data[].attributes.body
The ability to grant 'business' owners the understanding of the data critical for their domain and how it flows.

# data[].attributes.body
Enterprise Service Management

# data[].attributes.body
Compelling influence to ignite a passion for data governance and data literacy throughout the institutional community.

# data[].attributes.body
Manage data quality at source.

# data[].attributes.body
Eradication of data quality issues when I am at work.

# data[].attributes.body
I could see all our our data sources!

# data[].attributes.body
ERP Relacement

# data[].attributes.body
Optimize current data platform and build a new one