STATIC DATA AND MORE


Maintaining data, more specifically static data, often contributes substantially to more than one cost center of a firm, of which at least one is in the IT division.

  • Numerous and various interfacing mechanisms and mapping requirements usually are a heavy burden on IT
  • Other areas suffer under poor or even lacking maintenance practices

Clearly, data management is required to point out owners and responsible entities for data along with new or modified business processes to ensure governance around data matters. Otherwise, the strategic objective of running systems that use the data is met only in part.

We can not only point out and set the stage, but actually resolve functional and IT aspects of issues around data.

  • Often counterpart data in a firm is not consolidated
  • Multiple and duplicate identifiers per counterpart are common
  • Data ownership is not explicitly clear
  • Processes for data maintenance are not defined or enforced

Given that the data is used widely across business areas and various applications there is little justification for lack of incentive to overcome these critical shortcomings. Reasons for this are diverse, some given below.

  • Unawareness of the criticality of consolidated data in processing
  • Abundance of human capital giving the false impression of effective processing
  • Widespread opinion of failure in tackling the consolidation
  • Each set of users manages their issues in silos

DATA OWNERSHIP IS UNCLEAR


PROCESSES FOR DATA MAINTENANCE ARE NOT DEFINED OR ENFORCED


OFTEN DATA IS NOT CONSOLIDATED