Configuration Management Fontys ITIL course Hans Bezemer Fortis

Configuration Management Fontys ITIL course Hans Bezemer Fortis Bank Nederland N. V.

Cube Management Model

Configuration Management (Level 0)

Configuration Management Data. Base

The configuration management process Specify Identify Register Actualize Configuration Management Inform Verify

The configuration management process Specify Identify Register Actualize This is what it is all about!! Configuration Management Inform Verify

The third axis (Infrastructure axis) "Can be inhabited as needed, depending on the problem you want to solve. "

Basic principles of specification l First question: WHAT to store l Don't specify "fuzzy" data: define! l Don't store what you don't use immediately l Don't store what you can't update l Don't store data that changes too often l Specify HOW you want data to be stored l Remember specifications DO change, so plan for future changes

Specification: Levels of Configuration Management

Specification: layout of data CI-TYPE RACK: CI-TYPE SERVER: is part of Brand Model/Type Processor Size Processor speed exists of Serialnumber Memory CI-TYPE LOCATION Street is location of is located at CI-Type definitions Zipcode Residence is location of is located at

Identification CI-TYPE LOKATION: Street Zipcode Residence CI: GL 0001 The object ISE Woerden is related to CI Type location by CI-code GL 0001 ISE Woerden: Street Polanerbaan 1 Zipcode 3447 GN Residence WOERDEN

Identification (continued) RR 0015: MRS 0123: In preparation is part of In use IBM exists of R-7026 -H 50 R-7015 19" Power. Pc 604 e 332 Mhz GL 00001: In use 512 Mb is location of Polanerbaan 1 S 701544 F 4645 is location of 3447 GN is located at Woerden is located at

Is lokatie van Heeft als lokatie RS/6000 Console Heeft als lokatie Is gekoppeld met Is onderdeel van RS/6000 Tapeunit Lokatie Is lokatie van Heeft als lokatie Bestaat uit RS/6000 Diskettestation Is onderdeel van Is gekoppeld met Is lokatie van Bestaat uit Is onderdeel van Heeft als lokatie Is lokatie van Heeft als lokatie RS/6000 Is onderdeel van Bestaat uit RS/6000 Rack Is lokatie van Wordt gevoed door Voedt Is gekoppeld met (extern) Is gekoppeld met Bestaat uit (intern) Is onderdeel van RS/6000 Server Bestaat uit Is onderdeel van Bestaat uit Is gekoppeld met RS/6000 Cdromspeler Bestaat uit RS/6000 Tapelibrary Is onderdeel van Bestaat uit SSA-Kabinet Is gepatched op Patched RS/6000 Netwerkadapter RS/6000 Patch RS/6000 Voeding RS/6000 Heeft als interface Bestaat uit Is onderdeel van Is interface van RS/6000 Netwerkinterface Disk Technical Infrastructure view

Actualization: getting your data in time l Verifying is NOT Actualizing! l The keyword is: IN TIME l Make sure there is some kind of mechanism that allows you to get your data as soon as possible l This means: rechannelling the information flow, new procedures, possibly even a new organization l Every change in the CMDB must be covered by an information transfer procedure

Actualization: the "time lapse" problem Change executed RFC transferred RFC processed CMDB up to date

Verification: how are we doing? l The primary goal of verification is NOT to check the database, but HOW well the process performs l Verification must be measured using unbiased, uninterpreted Performance Indicators l Verification allows to analyse the performance in depth (drill down)

Verification: how to do it? Scanning + + + - Low cost (when automated!) Can be done regularly Can be done globally Not everything can be scanned Inspection + (automated) (manual) High cost Can't be done regularly Can't be done globally Everything can be inspected

Verification: checking qualitity

Verification: checking quantity

Information needs l Ad hoc reports l Regular reports l Queries Means l Secure data access l Easy data access l Reporting tools (spreadsheets, documents) (webbased, spreadsheets) (webbased, R/O clients) (use, don't change) (R/O clients, webbased) (e. g. Access, Crystal Reports) Possibilities l We got the information l We don't, so. . add new information? If so, specify!

Basic organization Configuration Manager Cfg Mgr sector CA CA

Basic procesflow CA CA CM Desk Employee CA Processing Verifying Delivery Design Implementation Intake Quality check Distribution Monitoring Coordination Employee Failures Info requests RFC's Other

Specification: Levels of Configuration Management Configuration Manager Life Cycle Management Configuration Administrator

Advantages of leveled Configuration Management l Can be expanded and extended easily l Knowledge doesn't have to be concentrated: full use of corporate information infrastructure l No single point of failure l Easy monitoring, simple and clear responsibilities l No information overload l Same information channels and procedures for everything and all l Can be automated easily

Basic principles of implementation “Think global, act local” “First make it work, then improve it” “One step at the time” “Enable the workfloor” “Decentralize what can be decentralized; centralize what must be centralized” “Only results count”

Three stages of Configuration Management l Pioneering Ø Diverging procedures, databases, tooling, standards Ø Working 'the old way' along with working 'the new way' Ø Keywords: persuading, trying, making it work, facilitating, promoting l Converging Ø Getting to common procedures, tools and standards Ø The 'old way' is retreating, 'private' databases abandoned Ø Keywords: detecting the change, supervising, accomodating, connecting l Maturing Ø Common procedures, tools and standards are accepted Ø People don't want to work by the 'old way'; this is the only way to do it! Ø Keywords: professionalism, retreating, expanding

The dangers of not doing things right Lots of incoherent data, unable to produce reports Actualize No uptodate information Specify Identify Register Configuration Management Inform How are we doing? Idunno! Verify Why do it anyway?

Pittfalls (1) l l l l Thinking tools "will save the day" Not enough attention for identification Not enough attention for specification Tight and rigid planning Implementing Config Management before implementing Change Management Big Bang implementations Integral implementations

Pittfalls (2) l Not enough attention for verification l Giving in (say "NO!") l Adding shadow repositories l No or insufficient communication l Mixing good and bad information l Repeated inventories l Assuming that information "needs" are true