Skip to main content

Managing Data

Data is a critical asset of every business. It needs to be managed properly in order to deliver services effectively. If we do not manage our data, we will be maintaining and collecting data that is not needed. Data quality, integrity and security of information may be compromised. We are painfully aware of identity theft and the risk of unprotected data to our business. To effectively manage our information we must be able to answer the following questions:
  • What data do we currently have, how is it classified, what if any are the security constraints?
  • What data needs to be collected or created to support our business?
  • What are our current and future needs for data storage and maintenance?
  • Who will access the data, how will they access it?
  • What are our disposal considerations, how long does the data need to be kept?
 In the ITIL Service Lifecycle, during requirements gathering, answering these questions is essential for the implementation of new or changed services. I have seen many new services fail because the management of data has not been addressed during Service Design. Best practice advice is to have a Data Management process that establishes policy and standards, provides expertise and makes it easier to handle the data aspects of new service. After all, our goal is to reduce risk to our business and to add value to the services we deliver to our customers.

Comments

Gregor Petri said…
Dear professor,

Having received my IT education in the 80ties I completely agree with the importance of understanding and managing data as a prerequisite for success, also in IT service management. However, I do believe this understanding can best be reached by having a model, in case of service management a model that models the service and the data belonging to it. When moving more and more data into the cloud a model to keep track of what is important will become more critical.

rgds
twitter.com/LeanITManager

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th