Unpack, packaged applications!
Begin with the metadata concealed within packaged applications – discover what lies beneath the opacity barrier. Industry-standard ERP & CRM packages from global vendors have large, complex, impenetrable data structures; opaque table & field names which can drain your resources & budget due to:
- lack of ‘business-friendly’ metadata, variables, table names or data structures;
- inability to access the data dictionary – unhelpful if you intend to do data cataloguing or inventory;
- metadata ‘hidden’ behind APIs;
- many and complex tables (as many as 90,000) make it difficult to locate target metadata without discovery tools;
- the need to relate, compare & provision data structures to your wider environment e.g. how many fields, in which instances, are called ‘customer’, and how many do you have, want or need?
- the risk of non-compliance arising from failure to locate or curate personally identifiable data (PII) in complex, big data CRM or ERP systems;
- data model gaps & inconsistencies stalling migration, consolidation or integration projects;
- empty cells negatively impacting ETL routines & derailing data migration timelines;
- the inability to subset the metadata in big data volumes or complex databases into more manageable chunks.
The upside of tackling packaged application metadata first, is that it is designed for applications, not people, and therefore likely to be of the machine-readable variety and easily usable once you can actually find out what’s there.