Metadata and IT service management Presentation Transcript
Metadata and IT service management Charlie Betz Accenture
What we will cover
A brief history & analysis of this word “metadata”
Comparison and contrast of metadata repository, CMDB, and other sources of structured IT information.
CMDB data architecture
Technical and organizational issues
Integrated, ERP-like solutions for IT
What is “metadata”?
A view from the data analysis community:
“ Metadata describes critical elements of data scattered across the organization.” (Jahn)
The data dictionary
The data dictionary in context What databases is this data structure in? What servers are they on? What programs depend on this data? What data feeds contain this data structure? Over what middleware are they flowing, and where are they going?
Scope, scope, scope
All of the following are metadata according to current metadata experts
Software portfolio (application inventory)
IT assets (hardware inventory)
File, database, object, class, and component definitions
Business process documentation
Organizational structure as it relates to IS system control (e.g., data stewardship, business process ownership)
Batch job operations
Data quality statistics
Software configuration management
Configuration management according to ITIL
The Configuration Management system
identifies relationships between an item that is to be changed and any other components of the infrastructure,
thus allowing the owners of these components to be involved in the impact assessment process.
Whenever a Change is made to the infrastructure,
associated Configuration Management records should be updated in the CMDB.
Where possible, this is best accomplished by use of integrated tools that update records automatically as Changes are made.
Scope of CMDB
From ITIL Service Support volume:
Customer and supplier databases [why stop there?]
Operational environments and applications supporting regulated business systems
Desktop builds and software licences
Items that could affect regulatory compliance for the organisation
EDI and database feeds, e.g. payroll feeds
External interfaces to trading partners, suppliers, Customers and business partners
Interfaces to branches with Customer systems
Other possible CMDB data sources
From ITIL Service Support volume:
Requirements analysis and design tools, systems architecture and CASE tools
Database management audit tools
Distribution and installation tools
Build and release tools
Installation and de-installation tools
Listing and configuration baseline tools
Audit tools (also called 'discovery' or 'inventory' tools)
Detection and recovery tools
From the ITIL data management volume (back-catalog)
“ A corporate repository is a store house for all the data definitions of the complete corporate data model for access by all its authorized users…. UNIX, DEC VAX, PC and other environments use the concept of a Configuration Management Database …”
Metadata repository vs. CMDB Unstable state. There is strong pressure to converge! Config, change, incident, problem, release, etc. This is the BIG difference!
Configuration management that’s not about metadata
Desktops have rarely if ever been of interest to metadata administrators
Metadata is typically not integrated with management frameworks
Perhaps this should change!
Metadata has been historically weak in process
Assumes that someone else has been keeping it up to date
Can my metadata repository also be a CMDB?
Most ITIL suites integrate at least change, config, and incident.
More convenient, but also greater vendor lock-in.
Stand-alone CMDBs can exist
One can decouple the CI inventory from process applications through unique IDs (e.g. URLs/URIs)
Your repository starts to turn into an OLTP tool; be ready
Repository as CMDB - 2 Are you ready for complex data? Simple data Complex data
Challenges of complex data
Deep inheritance from highly abstract supertypes
Recursion (trees and networks)
All of the above result in object/relational mapping layers in advanced repository products
The CMDB requirements
“ Configuration structures should describe the relationship and position of CIs in each structure… CIs should be selected by applying a decomposition process to the top-level item using guidance criteria for the selection of CIs. A CI can exist as part of any number of different CIs or CI sets at the same time… The CI level chosen depends on the business and service requirements.
“ Although a 'child' CI should be 'owned' by one 'parent' CI, it can be 'used by' any number of other CIs…
“ Components should be classified into CI types…Typical CI types are: software products, business systems, system software.…
The relationships between CIs should be stored so as to provide dependency information. For example, … a CI is a part of another CI[,] … a CI is connected to another CI [,] … a CI uses another CI…”
Configuration item definition
Per ITIL: The CM team is to "set up CI types, attributes, types of relationships, high-level CIs."
Defining types and valid dependencies is metamodeling
Difficult, abstract task for CMDB admins
Risks re-inventing metamodel wheel when standards exist
Naïve CMDB metamodel
Far too close to the data modeler’s inside joke
Doesn’t scale! SQL databases can’t optimize…
Seek out your company’s data architecture group! (You’ll probably need the most senior person to assist in assessing/setting up your CMDB.)
Problems of unconstrained any to any
Columns can contain databases, tables can contain servers, and so on.
Logical consequence: “black belt” team emerges
Can’t outsource data entry
HP just introduced constraint architecture
Challenge your vendors!
If I define an service CI, and a server CI, can I prevent my CMDB admins from putting the service inside the server?
If I define a hard drive CI, and an application CI, can I prevent my CMDB admins from making the application directly dependent on the hard drive?
The technical data management term is “constraints.” Does your tool support them?
Trying to make sense of the enterprise IT world
Project Portfolio Management
Application Portfolio Management
IT Portfolio Management
IT Service Management
ITIL, COBIT, CMM, TOGAF, IEEE/ISO/ANSI, …
Business Service Management
Application/Technology Relationship Mapping
Application Profiling/Reverse Engineering
Data & Metadata Management
The IT value chain
The IT tools vendor cyclone Most are silos Tremendous data redundancy Limited interoperability and/or standards Great risk of lock-in!
The internal IT tools mess
The tools mess 2
Most shops do not build these interfaces, resulting in disparate internal IT data and IT service inefficiency
They are VERY TOUGH tools-level programming
WE NEED STANDARDS!
The standards convergence Metadata Process
Look for opportunities for data re-use in IT
Don’t underestimate the difficulty of defining the CI metamodel
Or building interfaces between internal IT tools
Challenge your vendors for understandable, standard data models more detailed than “any to any.”