Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Configuration Management


Published on

HDI Capital Area November 16th Meeting

Published in: Technology
  • Be the first to comment

Configuration Management

  1. 1. CFM PURPOSEProtect the integrity of service assets and CisPlace IT assets and Cis under CfM controlsEstablish a CMS to ensure integrityProvide accurate information to support other processes through the Service LifecycleContent and CONTEXTC dUtlization drives value
  2. 2. CFM SCOPEFull lifecycle management of IT and service assetsMaintenance and status of asset inventoryComponents are identified baselined and maintained identified, baselined,Supports/is supported by Change controlsService iS i view – modeling whole services end-to-end and using that information f d li h l i d d d i h i f i for impact assessment
  3. 3. CFM – VALUE TO THE BUSINESSOptimizing service value from our assets and Cis Better change planning and forecasting Better impact assessments and risk management Better resolution of incidents and problems Better measurement of service warranty Better adherence to legal/regulatory obligations Better controls and utilization of services and assets Better traceability of requirements for new and changed services Better awareness of service provisioning costs
  4. 4. BASIC CONCEPTS: CONTROLCfM – Control my baseline (where am I?)ChM – Control my future state planning (Where am I planning to go?)RDM – Controlling my execution in moving new services and changes into future state (How do I get from current state to proposed future state?)These three processes are fundamental to successful service transition and must work together to maintain meaningful controls.
  6. 6. Service Service Customer level package portfolio Banking Contract core service Serviced byE-banking Supported by Hosted Application Uses Technical supportt Application A li ti hosting h ti infrastructure service service service User Business Data Web Network NetworkAvailability Messaging Authentication experience logic services services topology service
  7. 7. CIS (CONFIGURATION ITEMS)An asset, service component, or other item under CFM Controls Service Lifecycle Cis (Business Case, SDPs, Release Plans) Service Cis (systems, applications, information, data, infrastructure, facilities, people) Organization Cis (policies, legal/regulatory frameworks) Internal Cis (project mgmt software, SDLC software, etc.) External Cis (external customer requirements external services, etc.) requirements, services etc ) The big idea behind CFM Plans is fundamentally about “How Wide, How Deep” to go in establishing SACM controls
  8. 8. CMS OVERVIEWCMSs and multiple CMDBsSecure libraries and secure storesDefinitive Media Library (DML)Definitive SparesConfiguration BaselinesSnapshotsS h
  9. 9. Change and Release Asset Management Configuration Life Technical Configuration Quality Management Service Desk View User View View Cycle View View View assetsPresentation Project configurations Schedules/plans Change Financial Asset Asset Service Applications Asset and User configuration, Layer Service Strategy, Portal Request Status Change Status Reports Asset Application Configuration Changes, Releases, Advisory Board agenda and Statements and Bills Design, Transition, Environment Management Asset and License Management Operations configuration Test Environment Policies, Processes, Configuration item and Asset performance baselines and Infrastructure Procedures, forms, related incidents, templates, checklists problems, Search, Browse, Store, Retrieve, Update, Publish, Subscribe, CollaborateKnowledge MonitoringProcessing Performance Management Forecasting, Scorecards, Dashboards Query and Analysis Reporting Modelling Layer Planning, Budgeting Alerting Business/Customer/Supplier/User – Service – Application – Infrastructure mapping Information Integration Layer Service Portfolio Service Service Catalogue Model Integrated CMDB Service Release Service Change Common Process, Schema Meta Data Data Data synchronization Extract, Transform, Data and Information Mapping Management reconciliation Load Mining Data Integration Project Definitive Media Physical CMDBs Documentation Library Platform Software Discovery, Enterprise Applications Filestore Configuration Tools Configuration asset Access Management Data and Definitive CMDB1 Eg. Storage Management Management Human ResourcesInformation Document Library Database and audit Supply Chain Sources Structured Middleware Network tools Management and Tools Definitive Multimedia Mainframe Customer Relationship Library 1 CMDB2 Distributed Desktop Management Project Software Definitive Multimedia Library 2 CMDB3
  10. 10. DML and CMDBDML Physical CIs Information about the CIs Electronic CMDB CIs Release Record Build new Release Test new Release Implement new Release Distribute new Release to live locations
  11. 11. Planning, management resources, time Management support Working relationships Resources, facilities, CMS and tools Training and GuidancePolicy, Standards, Control Management Configuration Strategy, and Planning Management Plan, Service Portfolio, ContractCustomer Portfolio,Contract Portfolio, Portfolio CI Identification,, Contract Requirements, naming, labelling, Configuration data and requirements Design, Identification documentation Maintenance, Release, Baseline and Release Deployment, Id Operations plans Updated RFC, p , Configuration RFC/ updated CI Control change to CI Status record/Report Status Configuration Change and Accounting and information and Configuration C fi ti Reporting Performance Records and Documentation Verification Action items Physical CIs, and Audit Confidence in Test results service and Audit/discovery f infrastructure Feedback tools
  12. 12. CONFIGURATION PLANNINGPlenty of perfectly good templatesNeed a process first, then serves as a practical planLiving documentFocus on USE, not content
  13. 13. CFM IDENTIFICATIONConfiguration Structure and CI SelectionNaming ConventionsLabelingCI attributesCFM DocumentationRelationship mappingR l i hi iCI Types (service, HW, SW, documentation, staff)Media librariesConfiguration BaselinesRelease Units and Numbering schema
  14. 14. CONFIGURATION CONTROLEstablishing integrated controls with CHM and RDM to ensure License controls Change management process Version controls of assets, Cis, builds, and releases Access controls Build specifications Promotion and migration of data Configuration baselines Deployment controls (and touchpoints) Installation DML integrity
  15. 15. CFM STATUS ACCOUNTINGInsert example of asset/CI lifecyclesDefine state changes (how does CI move from one status to another) as part of your CFM Plan
  16. 16. REPORTINGMaintaining and archiving recordsManaging status of current configurationsMaking status information visible and availableRecording changes in CI statusEnsuring changes to baselines are properly documented and “re-baselined” or reconciled after changes are implemented
  17. 17. TYPICAL REPORTSCI information in a particular baselineCI lists and baseline configurationsCurrent revision status and historyStatus reports on deviationsStatus of delivered/maintained productsRevisionR i i statusReports on unauthorized usage/changes to HW/SWUnauthorized CIs detectedVariations between CMS and physical audit activities
  18. 18. VERIFICATION AND AUDITConformity between CMS and actualsVerify physical existence of CisConfirm RDM information and baselines before executing Deployment of a releasePlanned vs ad hocUse ChM and Incident Mgmt to address any unregistered or unauthorized CisAutomation hA i here d i drives b better performance across the service lif f h i lifecycle l
  19. 19. TRIGGERS, INPUTS/OUTPUTS, AND INTERFACESSupporting processes Change Management Financial Management Service Continuity Incident Management Problem Management Availability ManagementIn truth is the fundamental basis for all process activities since provides accurate information to underpin all services and service changes
  20. 20. INFORMATION MANAGEMENTCMS archiving/backup a fundamental part of your CFM PlanCMS contains information on backups of CisHow much archiving? Cost/benefit analysis analysis…
  21. 21. KPIS AND METRICS% improvement in maintenance schedulingAlignment between provided maintenance and business support (availability/windows)Assets identified as causes of service failuresImproved diagnosis/MTRS for incidentsImpacts of incidents/errors by particular CI type (for availability improvements)% reuse of unused/underused assetsAlignment of insurance premiums with business needRatio of used licenses vs paid licensesCost/user for licensesAccuracy in budgets/charging for services%reduction in business impact based on incorrect CI dataImproved audit compliance
  22. 22. CHALLENGES, CSFS, AND RISKS ChallengesMaintaining check-in/Check-out of DMLFundingData over useLack of management commitment (why do we need this?) CSFsValid justifications for what data is maintained jTop-down approach – “enough” dataHow accurate??Using technology to automate CMS practices RisksFocusing on technologies instead of services and outcomesMovement of hardware assets by unauthorized staff
  23. 23. INITIAL PLANNINGDesignate Configuration ManagerDefine MissionDetermine project scopeDefine overall project interfaces to other ST processesSurvey current capabilities and resourcesDevelop i i i lD l initial tooling plan li l
  24. 24. DEVELOP PROJECT PLANLaunch/approve and charter formal projectDefine Project TeamPlan Project Phases Feasibility Initiation Specification Process design Product selection Implementation Review ClosurePrepare operational mgmtConduct Feasability Study (Project Scope and constraints)
  25. 25. REQUIREMENTSIdentify and interview stakeholdersCapture (MOSCOW) and prioritize requirementsValidate and verify requirementsEstablish requirements management strategyDefine purpose, scope, and objectivesDefine li iD fi policies, procedures dDefine roles and responsibilitiesDefine metrics and reportingDefine Overall Plan
  26. 26. RELATIONSHIPSPlan relationships Among infrastructure components Among functional teams Among processesAlign to business services and outcomes
  27. 27. PLAN DEPENDENT ACTIVITIESPlan support toolsPlan support processesCommunicate benefits (mgmt)Plan staff training (diff for diff roles)
  28. 28. DEFINE ROLES AND RESPONSIBILITIESCfM Role specificationsAssignmentsRole/billet decisionsProject rolesCRC team? Integrated processes, tools, and teams?ROM of width of scope f id h fScope across operations and pipelineUsable existing tools?
  29. 29. BASELINE CURRENT PRACTICESCI OwnersPeople, process, technologyChMRDMSVTAsset mgmtARoles/resources
  30. 30. PROCESS IMPLEMENTATION PLANAnalyze existing practices (what do I already have?)Analyze ST capabilities (who do I have?)Define existing data and plan to move it into new CMSRefine and re-validate requirementsCreate vendor selection criteriaEvaluate and select toolingAcquire and install tooling q gDesign process interfaces in detailPlan structure and attributes of CisAlign Business ProcessesEstablish DMLTrain on roles/responsibilitiesManage Organizational Change needs
  31. 31. PLANNING PHASED IMPLEMENTATIONCoordination with other process/tool implementation activitiesPlanning CMS population and federationPlanning to take CfM control of CisFreezeManaging Cis during the FreezePlanning switchoverPl i i h
  32. 32. PHASING CFM INTraining (user and admin)Plans, Procedures, and Work InstructionsDefine and mature the CfM planLaunch update rolesPlan CI registration processesPlanPl ELSMature monitoring and metrics