• Search

• Categories

  • Company News
  • Industry Observations
  • Information Security
  • ITAM (Asset Management)
  • ITIL and Service Management
  • RFID
  • Software License Compliance

• Recently Written

  • Policies and why they are crucial
  • SAM for security
  • Software is going to solve all of my problems…NOT!
  • Accountability for your assets
  • Software Asset Management (SAM) – why not?
  • BSA says piracy is up yet again
  • Animus’ Phara McLachlan in TechNewsWorld
  • What is a data steward?
  • GRC – convergence killers
  • The value of data

• Blogroll

  • Miro Consulting

• Subscription

  •  Blog Articles
  •  Subscribe by Email
  • 

• Archives

  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • February 2008
  • January 2008
  • December 2007

• Members

  • Log in

When companies are implanting data governance they often identify a data steward (or several, depending on the size of the organization) to synchronize data collection processes, reduce data redundancy, and increase data accessibility, availability, and flexibility in a systematic manner or more simply put, exercise quality control of data.

We highly recommend assigning this responsibility to a properly trained individual, or one individual for each business unit, depending on your specific needs. Please keep in mind that this person will need to be managed as well to be sure the job is being done properly.

The idea of governing data is certainly not a new one. Most businesses have some form of data governance, but most are not doing it well. With advancements in technology comes added complexity to managing data, forcing companies to separate data governance out by division, business function and/or geographic location, causing the process to break down. All levels must be engaged in the process - from corporate to IT - across the enterprise.

There are many advantages to a successful data governance system, including:

Operational Savings and Efficiencies - data governance allows you to proactively monitor data and make changes for future business operations, avoiding one-off projects that typically cost much more.

Compliance - policies and procedures that are strictly monitored and enforced improve compliance.

Customer Service - improved understanding of customer data provides better customer service and also greater visibility for cross- and up-selling.

Mergers and Acquisitions (M&A) Preparation - should your company be faced with a merger or acquisition, you are better equipped to combine data assets, lessening the time to get back to core business functions.

A typical IT Service Management (ITSM) implementation can be anywhere from 30 days to a year, depending on the task at hand. When we begin the process with any client, our first step is determining what we are working with - the existing IT infrastructure, the process and services in place, etc. Once we have defined the current system, identified the issues and established why they were implemented from the start, we move to the next phase — which includes determining what the new system needs to provide that the old one did not. Existing systems often do not grow with the company, creating a scenario where they are no longer of value.  In some cases, existing systems have been neglected due to more pressing matters in the business.

Once current needs are determined, a roadmap is put into place to show how you get from point A to point B, whether it’s purchasing new software and hardware, overhauling the existing systems, updating and optimizing the existing system, or a combination. Typically, there are several first steps that can be taken to show immediate ROI, whether it’s retiring legacy systems or something as simple as telecom expense management to reconcile telecom inventory and bring overspending to a halt.

Once the roadmap has been clearly established, execution begins. The most important aspect of the ITSM implementation comes after the lengthy process of achieving the objective - making sure that after implementation the proper procedures are in place to manage software and hardware assets and keep your IT investment performing optimally.

Next Page →