Process Guide

更新时间:2022-11-08 17:41:28 阅读: 评论:0


2022年11月8日发
(作者:男生空间素材)

ConfigurationManagement

ProcessGuide

CONFIGURATIONMANAGEMENTPROCESSGUIDE

TableofContents

1.

2.

3.

PREFACE............................................................................................3

MISSION..............................................................................................5

OBJECTIVES......................................................................................6

3.1INTRODUCTION....................................................................................6

3.2DEFINITIONS.......................................................................................6

3.3OBJECTIVES........................................................................................6

GPRINCIPLES....................................................................9

4.1INTRODUCTION....................................................................................9

4.2PRINCIPLES.........................................................................................9

................................................................................................11

5.1INTRODUCTION..................................................................................11

5.2XXXXXMANAGEDENVIRONMENT.................................................11

5.3HARDWARECONFIGURATIONITEMS.................................................11

5.4SOFTWARECONFIGURATIONITEMS..................................................13

5.5DOCUMENTATIONCONFIGURATIONITEMS.......................................14

SDESCRIPTION..............................................................15

6.1INTRODUCTION..................................................................................15

6.2PROCESSSUMMARY..........................................................................15

6.3CONFIGURATIONMANAGEMENTPROCESSFLOW..............................17

6.4CONFIGURATIONMANAGEMENTSUB-PROCESSES.............................17

6.5SUBPROCESS1:PLANANDMAINTAINCONFIGURATIONSCHEME...17

6.6SUBPROCESS2:MAINTAINCONFIGURATIONDATA..........................21

6.7SUBPROCESS3:AUDITCONFIGURATION..........................................25

6.8SUBPROCESS4:REPORTINGCIINFORMATION..................................27

7.

8.

ROLESANDRESPONSIBILITIES...............................................31

MEASUREMENTS&REPORTING.............................................36

8.1INTRODUCTION..................................................................................36

8.2MEASUREMENTS...............................................................................36

8.3REPORTING.......................................................................................37

9.

10.

MEETINGS........................................................................................42

INTERRELATIONSHIPSWITHOTHERPROCESSES...........44

CONFIGURATIONMANAGEMENTPROCESSGUIDE

10.1INTRODUCTION..............................................................................44

10.2SYSTEMSMANAGEMENTPROCESSES.............................................44

10.3BUSINESSMANAGEMENTPROCESSES............................................46

10.4INTERRELATIONSHIPMATRIX........................................................48

CONFIGURATIONMANAGEMENTPROCESSGUIDE

e

1Section

Successfulmanagementofbusinessprocessisdependentuponclear

ocessguideisproducedto

idebindstheprocess

byitsscopeandcoverage,describesthemajorfunctionswithintheprocess,

andtsforthstandardsforapplyingtheprocess.

Thefollowingprocesshasbeendesignedtoaccommodatethevarious

rvicesofferedbytheXXXXXInformationTechnology(XXXXXI/T)

mpassboththecomponentsthatmaybedeployedin

thenear-termandthestrategiesthatmaybepursuedastheprocessmatures.

Thisprocessshouldbeviewedasa“to-be”modeltowardswhichthe

sakeofclarity,thisguiderefersto

InformationTechnologieswhereapplicable,inordertoapplyprocess

conceptsdirectlytoXXXXXI/T.

Whilethisguidervesasaroadmapforprocessdeployment,itisalsoa

esscomponentsareactivated,acontinuous

improvementeffortshouldbeundertakentocapturelessonslearnedand

eprocessisfullydeployed

acrossXXXXXI/T,thisguideshouldbecomeaclearandconsistent

documentoftheacceptedmanagementapproachinexecutingtheprocess.

gh

thisguideprentsacomprehensiveoverviewofaspecificprocess,

XXXXXI/Tmaydiscoverotherrelatedprocessthatwouldbenefitfrom

anequallyrigorousanddisciplinedapproachindefinitionand

ectionsdescribing“ScopeandCoverage”and

“InterrelationshipswithOtherProcess,”thisguideprovidesinsightsinto

someoftherelatedprocess.

Inrecognitionoftheuniquerequirementsofdifferentrvices,thisprocess

guideisstructuredtomaintainafunctionalperspectiveoftheprocess

ideaimstodescribe“What”functionsneedtobe

accomplishedandnot“How”thofunctionsmaybeachievedviaspecific

Page3

CONFIGURATIONMANAGEMENTPROCESSGUIDE

ppropriate,thisguidemaybesupplementedwithprocedural

amendmentsforaspecifictaskortofrvices.

Page4

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Section

n

2

InDefiningtheMissionoftheConfigurationManagementProcess,itwas

importanttounderstandthebusinesscontextinwhichitisbeingdefine.

Thekeybusinessdriversinclude:

•Integrationofmultiplegamingenvironments

•SupportnewtechnologydeploymentssuchastheJupiterproject(e-

businessrvices)

•ProvideafoundationforimprovingcustomersatisfactionwithIT

rvices

•Improveoperationaleffectiveness&efficiencythroughthe

implementationofstandardizedprocess

Withthisinmind,themissionofthisprocesswasdefinedasfollows:

ConfigurationManagementwillcovertheidentification,recording,

andreportingofallITcomponentswithintheXXXXXenvironment

(includingtheircurrentversions,constituentcomponents,and

relationships).Timelyandaccurateinformationwillbeprovidedto

allprocessrequiringconfigurationinformation.

Page5

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Section

3.

3.1

Objectives

Introduction

3

TheprimaryobjectivesofXXXXXIncorporatedInformationTechnologies

(XXXXXI/T)configurationmanagementprocessistoidentify,document

andcreatearepositoryforallhardwareandsoftwareconfigurationsinthe

I/Tenvironmentandtoprovideconfigurationinformationtothehelp

desk,changemanagement,problemmanagement,andotherprocessto

effectivelymanageI/Tresources.

3.2Definitions

ConfigurationManagement:ConfigurationManagementcanbedefinedas

thelogicalandphysicalconnectivityandrelationshipsofphysicalastsand

theirinternalcharacteristics.

....ITISNOT....

ProcurementManagement:Thepurchaandreceiptofaphysicalast

AstManagement:Thefinancialmanagementofthephysicalast

InventoryManagement:Thelocationofthephysicalast(whatandwhere)

ReleaManagement:Thecontrolledreleaofasoftwareordocumentation

astfromdevelopmentthroughtest,andintoproduction

3.3Objectives

•Withaclearunderstandingoftheterms“configuration,”and

“configurationmanagement,”theobjectivesoftheconfiguration

managementprocesscanbedefined:

Page6

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Theprocessforconfigurationmanagementshouldbeconsistentacrossthe

organization,andshouldincludestandarddocumentationandreporting

methods

ProvideasinglelogicalviewofallITcomponentsandconnectionsneeded

ewshould

include:

,ratherthen

reportingwhatisactuallyoutthere,theCMDBreflectsthe

ences

betweentheauthorizedandactualconfigurationaretreatedas

inationwithdata

fromotherprocess(changemanagement,incident

management,operationsplanning)theactualstatusatany

givenmomentintime(past,prent,future)canbereported,

shownorpredicted,

oAnabilitytoidentify,document,capture,organizeand

maintainreadilyaccessible,accurate,andup-to-date

informationonconfigurationitems,asidentifiedinthe

processscope.

oAnabilitytostorestandardconfigurationscenarios

(templates)tobeudforprocurement&projectacquisitions

Timelyandaccurateconfigurationinformationisprovidedtoallother

processwithinourenvironment

oTheprovisionofprerequisiteinformationtochange

managementforactivitiessuchasdeviceconfiguration,

hardwareadditionsandsoftwaredistribution.

oTheprovisionofconsistentinformationtothehelpdesk,

problemmanagementandincidentmanagementtoeffectively

manageI/TresourcesandimproveI/Tclientrvicedelivery.

oProvideaccurateandtimelyinformationonconfigurationto

supportanyotherServiceManagementprocess(er

Recovery,CapacityPlanning,Procurement,Architectural

Design,etc)

oSupporttheprovisionofbusinessmanagementimpact

informationfordecisionmaking(/problemdevice

historyfortrendanalysisandvendormanagement)

Reduceoverallworkloadbyintegratingandautomatingexisting

configurationtoolsandprocedurestosupportconfigurationmanagement

andotherrelatedprocess

Provideaprocessthatisadaptableenoughtoincorporatebusinessor

technologychangeswithoutsignificantrework

Page7

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Providetheabilitytoverifyconfigurationrecordsagainsttheinfrastructure

andcorrectanyexceptions

Page8

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Section

4.

4.1

GuidingPrinciples

Introduction

4

Whytheyareimportantandhowtheyshouldbeud

4.2Principles

Therewillbeoneconfigurationmanagementprocess(ePha1in-scope

items)

Therewillbeasingleprocessownerwhowilloveretheoverallprocess

andmanageallchangestoitandalllinkageswithotherprocessaffecting

it

Allconfigurationinformationwillbemaintainedincentralizedrepositories.

Thisinformationwillbeavailableondemandtoanyprocessrequiringit,

includinghelpdesk,problemmanagement,andchangemanagement

OnlytheConfigurationManagementProcessCoordinatorordesignated

rviceproviderscanupdateconfigurationinformation

Anyconfigurationmanagementtoolwillfollowexistingconceptual

architectureprinciplessupportingtheESMDomainarchitecture

Allin-scopeinfrastructureelementsrequiredtogothroughChange

managementarecoveredbytheConfigurationManagementprocess

ThedataintheCMDBshouldalwaysaccuratelyreflectthecurrent

(authorized)infrastructurestatus(thisimplieitherautomationortool

customization)

Configurationdatawillonlybecapturedwhenthereisarequirementfroma

rvicedelivery&supportprocessthatcanbesupportedbyautomation

Theprocessshouldfacilitateperiodicreviewandvalidationof

ConfigurationItems,Attributes,andRelationshiprequirements

Theprocessshouldincludeprocedurestovalidateandcorrectconfiguration

data

Page9

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Page10

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Section5

5.

5.1

Scope

Introduction

BecautheconfigurationmanagementprocessdealswithI/Tmanaged

componentswithintheXXXXXenvironment,itisimperativethatXXXXX

I/Tpersonnelunderstandthescopeoftheprocess.

Inthisction,scription

includesareasthatarebothinsideandoutsideoftheprocessscope.

AnimportantrulefordetermineifanItemisinscopeistheGuiding

Principlethatstatesthat:“Configurationdatawillonlybecapturedwhenthereisa

requirementfromarvicedelivery&supportprocessthatcanbesupportedby

automation”.Thismeansthatifthereisnotooltoverifythestatusofa

ConfigurationItem,documenttheterm

auto-discoveryisudtodescribesuchtools.

5.2XXXXXManagedEnvironment

DisplaylogicalarchitectureofITenvironmenthere…

5.3HardwareConfigurationItems

Introduction

BecautheCMDBwillonlycontainConfigurationItemsofwhichthe

statuscanbeverifiedinanautomatedfashion,onecanreadinthenext

tableswhichCIsareinscope.

stoneistoindicateifthereisa

ond

lasttwocolumnsindicateifthestatusofaCIcanbederivedfromanother

administration.

Page11

CONFIGURATIONMANAGEMENTPROCESSGUIDE

ChangeInitiated

Configuration

Item(CI)

ComputerCluster

Server

Desktop

Laptop

FrontEndProcessors

Stand-AlonePC(networkattached)

Firewall

DiskFarm

BackupUnit

LocalPrinter

NetworkPrinterYes

Yes

Yes

Yes

Yes

Yes

TBD

Auto

Discovery

Yes

Yes

Yes

TBD

Scripts

&automation

Relea

Mgmt(DSL)

Doc

Mgmt(DocSL)

ChangeInitiated

Configuration

Item(CI)

PalmPilot

Router

CISCOPIX

Hub

Switch

Modems

LocalDirectors

PatchPanel

Fax

Scanner

"Dumb"terminal

Yes

Yes

TBD

TBD

TBD

Later

Later

Later

Later

TBD

Auto

Discovery

Scripts

&automation

Later

Relea

Mgmt(DSL)

Doc

Mgmt(DocSL)

Page12

CONFIGURATIONMANAGEMENTPROCESSGUIDE

ChangeInitiated

Configuration

Item(CI)

Telephones

CellPhones

SlotMachine

RetailTerminals

SwitchProbes

FRAD

FDDILines

LeadLines

PBX

UPS

VideoConferenceEquipment

Auto

Discovery

Scripts

&automation

Later

Later

Later

Later

Later

Later

Later

Later

Later

Later

Later

Relea

Mgmt(DSL)

Doc

Mgmt(DocSL)

5.4SoftwareConfigurationItems

ChangeInitiated

Configuration

Item(CI)

Auto

Discovery

Scripts

&automation

Relea

Mgmt(DSL)

Doc

Mgmt(DocSL)

Introduction

OperatingSystem

ProgrammingLanguage

SystemTool

BusinessApp-RevenueGenerating

BusinessApp-BusinessEnabling

ApplicationDataba(SAN)

ExternalInterface

ApplicationModule

PalmSoftware

Yes

Yes

Yes

TBD*

TBD*

TBD*

TBD

TBD

TBD

Later

Later

Later

Later

Later

•*includescurrentlocationandversioninformation,butnotversionhistoryormodulehierarchy

Page13

CONFIGURATIONMANAGEMENTPROCESSGUIDE

5.5DocumentationConfigurationItems

ChangeInitiated

Configuration

Item(CI)

Auto

Discovery

Scripts

&automation

Relea

Mgmt(DSL)

Doc

Mgmt(DocSL)

Later

Later

Later

Later

Later

Later

Introduction

ServiceLevelAgreement

SystemOperationsGuide

ApplicationOperationsGuides

DisasterRecoveryPlan

SoftwareLicens

SystemConfigurationDocuments

Page14

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Section

6.

6.1

ProcessDescription

Introduction

6

Thedetailedconfigurationmanagementprocessisdescribedinthisction.

Adetailedexplanationoftheprocessandsub-processiscontainedinthe

followingpagesandismeanttoprovidetheparticipantsinthe

configurationmanagementprocesswithanunderstandingofthegeneral

functionalflow.

6.2ProcessSummary

ProcessStartsWith

•ChangeinSystemsManagementControls

•ReceiptofnoticeofachangeinSystemorServiceDesignInformation

•Initialcaptureofexistinginfrastructure

•RequestforChange(Add,Modify,RemoveaConfigurationItem[CI])

•Requestsforconfigurationinformation

EndsWith

•Auditofconfigurationdatabaagainsttheinstalledinfrastructure

•Creationofalogicalreprentationofthecurrent(andplanned)

infrastructure

•Provisionofconfigurationinformation

ProcessDesignIncludes

Page15

CONFIGURATIONMANAGEMENTPROCESSGUIDE

•ThecompletelifecycleofaCIfromplanningthroughtoretirement

•FlowofDatabetweenthesubprocessoftheConfiguration

ManagementProcess

•FlowofDatabetweentheConfigurationandotherESMProcess

•ActivitiesperSubprocess

•RolesperActivity

ProcessDesignExcludes

•Designactivitiesforinfrastructurecomponents,bothnewor

modificationstothem

•Responsibilityforauthorizationofchanges

•Planninghowandinwhatwayconfigurationdetailsshouldbe

reprented

ProcessControls

•ServiceManagementControls

•ServiceLevelAgreements

•AuthorizedChanges

•InfrastructureDesign

ProcessInputs

•ConfigurationDetailstakenfromRequestForChanges[RFC]

•VerificationDatatakenfromautomatedsystems(autodiscover)

•VerificationDatatakenfromPhysicalchecks

•VerificationDatatakenfromHelpdeskcalls

ProcessOutputs

•ConfigurationInformation

•Signalleddifferencesbetweentheauthorizedandactualconfiguration

Page16

CONFIGURATIONMANAGEMENTPROCESSGUIDE

6.3ConfigurationManagementProcess

Flow

PlaceITILConfigurationFlowHere…

urationManagementSub-ProcessFlow

6.4ConfigurationManagementSub-

process

Theconfigurationmanagementprocessitlfcanbebrokendowninto

veralsub-process:

•Sub1:PlanandMaintainConfigurationScheme

•Sub2:MaintainConfigurationData

•Sub3:AuditConfiguration

•Sub4:ReportingConfigurationInformation

6.5SubProcess1:PlanandMaintain

ConfigurationScheme

ServiceLevel

Agreement

Service

Management

Controls

Systemand

ServiceDesign

Information

Triggers

RequestFor

Changes

SUB1:PlanandMaintainConfiguratScheme

CMDBSchemaUpdates

CurrentCMDBSchema

CMDB

Purpo

ThepurpoofthisSubProcessistomakesurethattheschemaofthe

ConfigurationManagementDataba[CMDB]isabletoregisterallattributes

andrelationshipsaConfigurationItem[CI]canhave,andallpoliciesinvolved

oreitneedstohaveknowledgeaboutCIsandhastobekept

informedaboutchangesthatinfluencesCIs.

Activities

Page17

CONFIGURATIONMANAGEMENTPROCESSGUIDE

A1.1RunanAwarenessProgram

Ifchangemanagementwillnotbeapartoftheprojectoffice,wemightneedan

awarenessactivitytopromotetheCMDB

A1.2Gather&Reviewupcomingchanges.

hangescanhave

veralsources.-EWTA-ChangeManagement–ojectthat

willberunmustbeexaminedforimpactontheCMDB.

A1.3AssstheimpactofachangeontheSchemaoftheCMDB.

Eachidentifiedchangecanpotentiallyrequireachangeforthepoliciesorthe

tancewhennewinfrastructureitemsare

introduced,newCItypesornew/differentlinksbetweenCIs.

A1.4Design/RealizethechangesneededontheSchema.

n

alsoincludeconversions.

A1.5CreateandMaintainstandardconfigurations("Same-as").

Someconfiguration(parts)pleisthedesktop.

Therewillbeastandardconfiguration,

activitydefinesthostandardsandmaintainsthemastechnologyand

requirementsdevelop.

A1.6InvestigatetherelationshipstypesbetweennewCItypes.

TherewillberelationsbetweenCIsthatcannot(easily)beautomatically

tancewhichdistributeddatabaisbeingudbyan

application,,itis

veryimportanttoregistertherelationshipsforinstancetodoimpactanalysis.

Thisactivityanalysinfrastructuredesigns,applicationarchitecturesandwork

procedurestodiscoveralltherelationshipsaCIhavewithotherCIs.

A1.7IdentifytheownersofCItypes.

neristheSubjectMatter

wnerfunctionsasacontactforinformation

abouttheattributes,tivityidentifies

andregistersforeachCItypeanowner.

A1.8IdentifyconfigurationDocumentationforCItypes.

umentationshouldinclude

thebehaviourofaCI,informationaboutthenatureandvaluesofattributes,

andallrelationshipstheCIhas.

A1.9Measureandreporttheperformanceofthissubprocess.

purpoistohaveanobjectivewaytomeasuretheeffectivenessof

improvementstothisprocess.

Page18

CONFIGURATIONMANAGEMENTPROCESSGUIDE

KeyPerformanceIndicators

K1.1Numberofchangestotheschema

K1.2Datesoflatestchanges.

K1.3NumberofCItypeswithoutaidentifiedowner

K1.4NumberofCItypeswithoutconfigurationdocumentation

K1.5Numberandverityofincidentsrelatedtomissingattributesor

registrationofrelationships

Controls

C1.1ServiceManagementControls

TheServiceManagementControlsdeterminehowconfigurationmanagementis

tancetheguidingprinciple“InphaoneonlyItemsthatcanbe

discovered(verified)automaticallyareputasaCIintheCMDB”determinesthe

scopeonCItypelevel.

C1.2ServiceLevelAgreements

TheServiceLevelAgreementsdeterminewhat,froma(IT)businessperspective

hastoberegistered.

Triggers

T1.1NewRequestForChange[RFC];EachChangehastobeevaluated.

T1.2Changesintheinfrastructuredesignthatdoesnotfollowthechange

managementprocess.

T1.3ChangedServiceLevelAgreement

T1.4ChangedServiceManagementControls

Input

I1.1CurrentCMDBSchema.

I1.2RequestForChange

ARequestForChangefromtheChangeManagementProcess

I1.3SystemandServiceDesignInformation.

AdescriptionoftheInfrastructuredesignandchangestotheInfrastructurethat

donotfollowtheChangeManagementProcess.

Output

O1.1CMDBSchema(updates)

Skills(Roles)

Page19

CONFIGURATIONMANAGEMENTPROCESSGUIDE

S1.1ProcessOwner(Management/Architect)

S1.2DatabaSpecialist/Analyst

S1.3InfrastructureSpecialist(Hardware,Software,Applications,Network)

S1.4ConfigurationManager

ToolRequirements

R1.1Automatedaccesstothechangemanagement/projectinformation

R1.2AccesstotheCMDBschema

R1.3DBanalysis/modelingfunctions

R1.4DBdesignfunctions

R1.5DBdevelop,testfunctions(develop/test/acceptation/productionlife

cycle)

R1.6DBConversionfunctions

R1.7AflexibleDataba(flexibleforschemachanges,relationalversus

Hierarchical)

R1.8ThebehaviourCMDBapplicationmustbecontrollablefromthe

‘outside’(tabledriven,norecompilingafterschemachanges)

R1.9Possibilitytoregisterstandardconfigurations(currentdoneinEWTA)

R1.10AccesstoInfrastructurecharacteristics(networktopology,application

documentation)

R1.11Logging,tracking,reportingfunctions(#changestoschema,dateslatest

changes)

Page20

CONFIGURATIONMANAGEMENTPROCESSGUIDE

6.6Subprocess2:MaintainConfiguration

Data

Infrastructure

Design

Service

Management

Controls

Pre-Authorized

Changes

Triggers

Differences

between

CMDBand

Realworld

Sub2:Maintain

ConfigurationData

Detailsof

Authorized

Changes

Updated

CMBD

Data

SignaltoIncidentManagementif

differenceisnotbadonan

authorizedchange

Purpo

ThisSubProcessdealswithregisteringinformationabouttheCIsthatare

managedbytheServiceManagementSystem.

Activities

A2.1Identifyauthorizedchangestotheinfrastructure(realworld)

Changestotheinfrastructure(realworld)willbedonebadonaRFC(Request

ForChange)thathasgonethroughtheChangeManagementProcess,andare

tivityidentifiesthechangesandpreparesthemto

beappliedtotheadministeredconfigurationintheCMDB.

A2.2Identifylistofpre-authorizedtypesofchanges.

Therearechangestotheinfrastructure(realworld)thatdonotgothroughthe

ChangeManagementprocess,

taistoo

ansthatif

thevalidationprocessindicatesthattheadministeredconfiguration(CMDB)is

notthesameasthediscoveredinfrastructure(realworld)thenewvalueis

pliesthatinthe

examplegiven,thetoken-ringportnumberofalaptopintheCMDBreprents

the‘lastknown’value,

ins

A2.3Validatechanges(namingconvention,completeness).

Authorizedchangesarevalidatedontheircompletenessandcomplianceofthe

tivityalsovalidatesthe

completenessofalldocumentationrequirementsandmakessurethatthe

tivitymakextensiveuofStandard

Configurations.

A2.4UpdatetheapprovedchangesintotheCMDB.

Thisactivityupdatestheactualdatabaentriesbadontheauthorized

theCMDBis

Page21

CONFIGURATIONMANAGEMENTPROCESSGUIDE

updatedassoonasachangeisauthorized(theCMDBthenreflectsthe

authorizedconfiguration).Theothertechniqueistodeferapplyingthechange

combiningtheChangerecords,ConfigurationrecordsoftheCMDBthis

specialformsofRFCsarethe“initialpopulationoftheCMDB”andthe

“synchronizationpopulationoftheCMDB”ctionscanbe

consideredasasortofpreauthorizedchangebecaualldataisaccepted

withoutcheckingeachupdateagainstachangeintheRFC.

A2.5CreaterelationshipsbetweenCIs.

Sincetheauto-discovertoolscannotdiscoverallrelationshipsbetweenCIs,

tivity

usthechangeadministration,orchecksagainststandardconfigurationsto

determinetherelationshipsaCIhaswithotherCIs.

A2.6Createsoft-label.

pointitisnotclearhowthe

interfacebetweenAstManagementandConfigurationManagementwillbe

ytheast-labelwouldbeudaspartofthe

t-labelisnotonlyuniqueforaCIbutalsouniquefordifferent

versions/ythevariousconfigurationsofaCI

throughitslifecyclecanbetraced.

A2.7SignaltoIncidentManagement.

Thisactivitytakesthedifferenceslist[outputfromsubprocess3:Audit

Configuration]andverifiesifeachdifferenceisbadonanauthorizedchange

ferencebetweentherealworldandthe

CMDBisnotbadonanauthorizedchange,asignalisflaggedforIncident

Management.

A2.8Measureandreporttheperformanceofthissubprocess.

purpoistohaveanobjectivewaytomeasuretheeffectivenessof

improvementstothisprocess.

KeyPerformanceIndicators

K2.1NumberofmodificationstotheCMDB

K2.2Numberofincidentssignalled.

-Indicativeofunauthorizedconfigurationchanges

-Indicativeofunsuccessfulchanges

-Indicativeofplanningproblemsforchanges

K2.3Numberofincidentsrelatedtoincorrectconfigurationinformation

Inputs

Page22

CONFIGURATIONMANAGEMENTPROCESSGUIDE

I2.1DifferencesbetweenCMDBandInfrastructure.

ThislistiscreatedbySubprocess3:AuditConfigurationthroughcomparing

CIsintheCMDBandCIsintherealworld.

I2.2DetailsofAuthorizedchanges.

Theareplannedchangestotheconfigurationagainstthedifferencesare

checked.

Controls

C2.1ServiceManagementControls

TheServiceManagementControlsdeterminetheprerequisitesforchangesto

bepre-authorized.

C2.2TheInfrastructureDesign

ThedesigndetermineswhichrelationsbetweenCIxist

C2.3Preauthorizedchanges.

SomeCItypeshavevolatileattributes/relationships,changesareautomatically

tancethetypeofthemouattachedtoaDesktop.

Triggers

T2.1RFC[RequestForChange];Theconfigurationchangesresultingfrom

anauthorizedchangehavetoberegisteredintotheCDMBifsuccessfully

implemented.

T2.2Aftereachauditoftheconfigurationthedifferencesareevaluatedandcan

resultinupdatesoftheCMDB.

Output

O2.1UpdatesontheCMDBdata

O2.2SignalstoIncidentmanagement

Skills(Roles)

S2.1ConfigurationManager

ToolRequirements

R2.1AutomatedAccesstoChangetickets

R2.2Changes(fields)inrecognisableandstandardformat

R2.3AutomaticupdateCMDBifchangeandverificationareinsynch

R2.4Registrationofchangetypes(attribute-orrelation-level)thatarepre-

authorized

Page23

CONFIGURATIONMANAGEMENTPROCESSGUIDE

R2.5AutomaticupdateCMDBifdifferencesarematchingapre-authorized

change

R2.6ValidationofChangesonfieldlevel(namingconvention,validvalue

range),(mantic,andsyntaxvalidation)(mandatoryfieldntered)

[responsibilityofChangeManagement]

R2.7Databageneratesaquencenumber

R2.8Asttagregisteredasanattribute

R2.9Abilitytogenerate,fillappropriatefields)androuteanincidentticket

R2.10Logging,tracking,reportingfunctions(#updatesinCMDB,#incidents

signalled)

Page24

CONFIGURATIONMANAGEMENTPROCESSGUIDE

6.7SubProcess3:AuditConfiguration

Service

Management

Controls

CMDBdata

Triggers

Verificationdataof

theconfiguration

gatheredduringa

HelpdeskCall

Differences

between

CMDBand

Realworld

RealWorld

Configuration

Information

gatheredby

aFysicalCheck

Sub3:Audit

Configuration

RealWorld

Configuration

Snapshot

Information

gathered

byAuto

Discover

Purpo

ThisSubProcess:-Gathersinformationabouttherealworld,-Verifiesand

formatsthedata,comparesittotheregisteredinformationintheCMDB,and

gso,itenablesanauditoftherealworld

configuration.

Activities

A3.1Runtheauto-discover.

ThisactivityrunsAuto-discoverto‘sniff’the'realworld'configuration,

comparesthistotheconfigurationaccordinglytotheCMDBandcreatesalist

ofthedifferences.

A3.2VerifyCMDBonaHelpdeskcall.

OnaHelpdeskcall,ahelpdeskoperatorverifiesthe'realworld'configuration

againsttheCMDBbyquestioningthecustomerandcreatesalistofdifferences.

A3.3VerifyCMDBbyPhysicalcheckingthe'realworld'configuration.

Thisactivityconsistsofdoingaphysicalcheckofthe‘realworld’,comparing

thistotheconfigurationaccordinglytotheCMDBandcreatingalistofthe

differences.

A3.4MeasureandreporttheperformanceofthisSubprocess.

purpoittohaveanobjectivewaytomeasuretheeffectivenessof

improvementstothisprocess.

KeyPerformanceIndicators

K3.1NumberofCIsfoundbydiscoveryactivities

K3.2NumberofattributesfoundforeachCIbydiscoveryactivities

K3.3NumberofrelationshipsbetweenCIsfoundbydiscoveryactivities

K3.4Numberofdifferencesreported.

Page25

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Inputs

I3.1ConfigurationInformationfromHelpdeskoperatoracquiredfromcaller

I3.2Auto-discovertooloutput

I3.3Physicalcheckresults

I3.4CMDBdata

Output

O3.1Listofdetecteddifferences

Controls

C3.1ServiceManagementControls

TheServiceManagementControlsdetermine:

-Thescopeandtimingoftheauto-discoverinformation:Forinstanceoncea

day,1/7ofthetotalconfiguration,ordayonethervers,daytwothe

desktops,daythreethenetwork,etc.)

-tanceonlythe

relevantconfigurationafterachange.

-Thescopeandtimingofthephysicalcheck.

-ThescopeandtimingofauditafteranimplementedRFC.

-ThescopeofthequestioningonaHelpdeskcall.

Triggers

T3.1Availableinformationfroman(automated)auto-discoveraction

T3.2AHelpdeskcall

T3.3Availableinformationofaphysicalcheck

T3.4RequestfromIncidentorProblemManagement

T3.5VerifyCMDBafterimplementingRFC.

Afterthecompletionofachange(successfulorunsuccessful)thistriggerstarts

thecomparingoftherelevant'realworld'configurationtotheCMDBtoanaly

theeffectsofthechangeandcreatesapotentiallistofdifferences.

T3.6PopulateinitialCMDB.

Thistriggerstartsan(onetime)initialpopulationoftheCMDBbadonthe

'realworld'configuration,verifiesalltheCIsonthelistanduitasinputfor

Subprocess2:UpdatingtheCMDB.

T3.7SynchronizeCMDB.

Afteramajorupdate(efininganewCItype,orcomplementingthe

environmentwithalargenumberofCIs)doaSynchronizationPopulation,

verifythelistanduitasinputforSubprocess2.

Page26

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Skills(Roles)

S3.1OperationalServicesSpecialist(SystemsManager/Operator)

S3.2HelpdeskOperator

S3.3ConfigurationManager

ToolRequirements

R3.1AutomateddiscoveryofaCI

R3.2AutomateddiscoveryofthevalueofattributesofaCI

R3.3AutomateddiscoveryofrelationsbetweenCIs

R3.4Schedulableauto-discovery

R3.5Auto-discoveryforalectionofCIs

R3.6Formattingtherawauto-discoverinformationforcomparisonto

CMDB

R3.7AutomatedAccesstoCMDB

R3.8Comparefunction(auto-discoverdataversusCMDB)

R3.9Generatingadifferenceslist

R3.10GenerationachecklistfromtheCMDBudbythePhysicalchecking

activity

R3.11Abilityto(easily)enterthedatagatheredbythePhysicalchecking

R3.12AccesstotheCMDBdatafromtheHelpdeskapplication(preferable

integrated)

R3.13AbilitytoregisterthedifferencesbetweentheinformationtheHelpdesk

receivesversustheinformationfromtheCMDB

R3.14Logging,tracking,reportingfunctions(#CIauto-discovered,

#differences)

6.8Subprocess4:ReportingCI

Information

Page27

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Report

Request

Service

Management

Controls

CMDB

Data

Triggers

Sub4:Reporting

CMDBInformation

CMDB

Information

Purpo

ThisSubProcessgeneratesallthenecessaryconfigurationreports.

Activities

A4.1Design/ImplementReportsofConfigurationData.

Thisactivitydesignsandimplementsreportstoreprentconfigurationdata.

Thedatacanbeprentedintext,eportscanbe

‘cannedreports’(forfrequentu)orareportforaspecificrequest.

A4.2Generate/ScheduleReportsofConfigurationData

n

tivityalsodefines

thetimetableforgeneratingstandardreports,andmaintainsthelistof

subscriptionsonperiodicallystandardreports.

A4.3ProvideConfigurationDataindownloadableform.

tance

toimportinadatabaprogramforanalysis.

A4.4GenerateChangeImpactreports.(BadonaRFC,listtheeffectedCIs)

A4.5GenerateDetailedconfigurationreportsforIncident/Problem

Management

A4.6MeasureandreporttheperformanceofthisSubprocess.

purpoittohaveanobjectivewaytomeasuretheeffectivenessof

improvementstothisprocess.

KeyPerformanceIndicators

K4.1Numberofreportsgenerated

K4.2Numberofsubscriberstoregularreporting

K4.3Number&contentofadhocqueries(canpointtotheneedtodefine

newstandardreports)

Inputs

Page28

CONFIGURATIONMANAGEMENTPROCESSGUIDE

I4.1CMDBdata

Controls

C4.1ServiceManagementControls

•Thedatathatwillbemadeavailableindownloadableform

•Thedatathatwillbereportedtosubscribers

•Thedatathatwillbepublished,andhowactualwillitbe

•Rulesforwhocanbeasubscriber

C4.2ReportRequests

•ReportscanbefortheallCIs,agroupofCisorforasingleCI.

•Areportcanbefixed(canned)orcreatedonthefly(adhoc)

Triggers

T4.1On-demandReports

T4.2PeriodicalReports.

Output

O4.1ConfigurationReports

Thiscanhavemanyformsliketext,lformsofa

configurationreportsareaRFCimpactanalyanddetailedreportsudby

IncidentControl/ProblemManagement.

Skills(Roles)

S4.1DatabaSpecialist/Analyst

S4.2OperationalServicesSpecialist(SystemsManager/Operator)

S4.3ConfigurationManager

ToolRequirements

R4.1AccesstoCMDBdata(read-only?)

R4.2Reportgenerationfunctions

R4.3Generatetext

R4.4Generatetables

R4.5Generategraphics

R4.6Schedulereportgeneration

Page29

CONFIGURATIONMANAGEMENTPROCESSGUIDE

R4.7ParameterizedReportgeneration(levelofdetail,scope)

R4.8On-linequeryfacilitiesonCMDBdata(verallevelsofactuality)

R4.9DownloadofpartsoftheCMDB

R4.10ProvidecopiesofCMDBdata(forinstancegeneratedatnight)

R4.11Registrationoftherequestedreports

R4.12Abilitytosubscribetoperiodicalstandardreports

R4.13Creationofcanned/prefabreports

R4.14Accesstostandardreports(postedonweb,Maillist,paper)

R4.15Logging,tracking,reportingfunctions(numberofreportsgenerated,

numberofsubscribers,numberandcontentofadhocqueries)

Page30

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Section

ndResponsibilities

7

Thisctiondescribesthefunctionsandactivitiestobeperformedbythe

Rolesandresponsibilitiesmustbeagreedto,documented,authorities

understood,keptcurrent,andallfeelempoweredtofulfillresponsibilities

andcrossreportingboundaries.

Therolesandresponsibilitiesinvolvedintheprocessare:

•ConfigurationManagementProcessOwner.[P_owner]

•ConfigurationManagementCoordinator.[P_exec]

AlsocalledtheConfigurationManagerortheProcessExecutor

•Infrastructure(Network,Hardware,Software,Application)Specialist

[Infra]

•DatabaAdministrator[DB]

•Helpdesk/ServiceDesk[HD]

•OperationalServicesSpecialist(systemsmanager/operator)[OPS]

Thepositionsdiscusdrefertoafunctionalityroleanddonotreprenta

onetoonefulltimeequivalent(FTE)cas

veralrolesmaybeassignedtoasinglepersonintheorganizationor

veralpeoplemayplayasinglerole.

Page31

CONFIGURATIONMANAGEMENTPROCESSGUIDE

ConfigurationManagementProcessOwner

TheConfigurationManagementProcessOwneristheXXXXXI/T

designatedmanagementreprentativewithultimateresponsibilityand

ConfigurationManagementProcessOwnermustensurebusinessobjectives

oftheXXXXXI/Torganizationareproperlymanagedandsupportedby

figurationManagementProcessOwnerhasthe

followingresponsibilities:

•Prioritizesprocessinvestment,(responsibleforcostandinvestmentof

theprocess).

•Actsasafinalescalationpointforconfigurationmanagementprocess

issues.

•Defines,prepares,andcommunicatesnewandchangedpolicies.

•Approvesnewprocessdefinitions,requirementsandrequestsfor

improvement.

•AssignstheConfigurationManagementCoordinator.

•Enforcestheprocessthroughouttheorganization.

•Ensuresconsistencywithotherprocess.

•Approvesorrejectsprocessdeviationrequests1.

•Definesprocessmeasurementsandassociatedtargets.

ConfigurationManagementCoordinator

TheConfigurationManagementCoordinatorisresponsiblefortheday-to-

rdinatorensuresadherencetothe

figurationManagement

Coordinatorisresponsibleforthefollowing:

•Providescentraldirectionfortheconfigurationmanagementsystem

including:

Identifyingtherequirements.

Creatingthelogical,operationaldesignincludingtoolanddatabausage.

Testingandimplementingdesign.

Ensuringconsistencyacrosstechnicaldomainsandcompatibilityof

applicationsandsystemsconfigurations.

1AProcessDeviationRequestisamanagementapprovedrequestforacoveredcomponentoftheXXXXXI/T

productionenvironmenttobeexemptfromtheprovisionsoftheconfigurationmanagementprocess.

Page32

CONFIGURATIONMANAGEMENTPROCESSGUIDE

•Manages/controlstheday-to-dayexecutionofconfiguration

informationmanagementactivities.

•Monitorshowwelltheconfigurationmanagementsystemisperforming

andtakescorrectiveactionstoimproveaccordingtotheprocess

effectivenessmeasurements.

•Managesprocesspoliciesandstandards.

•Assspotentialimpactstotheprocess

•Ensuresavailabilityandaccessibilityofaccurateconfiguration

informationandcontinuouslymaintainsandupdatesinformationas

required.

•Ensurestoolsareavailableandproperlymaintained.

•Ensuresthatconfigurationinformationmanagementrolesarecorrectly

assignedandexecuted.

•Provideducationoftheprocessandtools.

•Communicatesprocessstatusandchangestoallprocessparticipants.

•Attendsappropriatechange,astandproblemmanagementmeetings.

•Resolvesissuesrelatedtotheprocesswhenthenormalstructureisnot

adequate.

•Escalatexceptionstouppermanagementtogetherwithsupporting

factsandrecommendedactions.

•Analyzesconfigurationtrendsandreports.

•Surveysclientsatisfactionwiththeprocess.

•Managesretrievalofconfigurationinformationfrominstalled

components.

•Auditsdeviationsbetweenrecordedandactualconfigurations.

•Issuesappropriatenotifications.

•Requestsupdatesofconfigurationinformationandndsto'validate

andmaintainsub-process.'

InfrastructureSpecialist

TheInfrastructureSpecialistprovidesthesubjectmatterexpertiabout

haracteristicsareregisteredasthe

InfrastructureSpecialisthasthefollowingresponsibilities:

•Provideknowledgeaboutwhatinformationforeachtypeof

ConfigurationItemisrelevanttoberegistered.

Page33

CONFIGURATIONMANAGEMENTPROCESSGUIDE

•Provideknowledgeabouttheacceptablerangesforvaluesofattributes

foreachtypeofConfigurationItem.

•Provideknowledgeaboutwhichrelationstoothertypesof

ConfigurationItemsarerelevanttoregister.

•Provideknowledgeaboutstandardconfigurationsandrequired

componentsofstandardconfigurations.

DatabaAdministrator[DB]

TheDatabaAdministrator/DatabaAnalystprovidessupportneeded

aba

Administratorhasthefollowingresponsibilities:

•DesignadatabaschemathatcansupporttheConfiguration

Managementrequirements.

•UpdatetheConfigurationManagementDataba[CMDB]schemais

needed.

•MaintainandoptimizetheCMDB

•SupplySupportforApplicationsthatneedtoaccesstheCMDB

Helpdesk/ServiceDesk[HD]

TheHelpdeskisprocess/organizationwhointeractswithursand

ethefirstlinesupportandnexttousingarealsoasource

Helpdeskhasthefollowingresponsibilities:

•Verifytheregisteredconfigurationofauroneachcalltothe

Helpdesk.

OperationalServicesSpecialist(systemsmanager/operator)[OPS]

TheOperationalServiceSpecialistisresponsibleforthedailyoperationsinthe

XXXXX’ecialistwillexecutemanytasksofthe

rationalServicesSpecialisthasthe

followingresponsibilities:

•ExecuteallscheduledConfigurationManagementReporting.

•Executetheauto-discoverprocess.

•ExecuteSystemsManagementactivitiesontheConfiguration

ManagementApplication,Databaandtoolnvironment.

Page34

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Page35

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Section

8.

8.1

Measurements&Reporting

Introduction

8

Measurementsandreportingareanecessarypartoftheconfiguration

ekeyaspectsinmaintainingacontinuous

agementProcessOwnerwillconduct

ultsof

thelf-asssmentwillbereportedandanalyzedwithmanagement.

Themeasurementsandreportingoftheconfigurationmanagementprocess

shouldaddressthestatusoftheprocessatmeetingornotmeetingits

definedobjectivesstatedinSection3ofthisdocument.

8.2Measurements

NexttotheKeyPerformanceIndicatorsmentionedinction6Process

Description,therearesomegeneralmeasurementsthatcanbeudto

measurethestatusoftheprocessinthefollowingareas.

Effectiveness

Indicatorsmaybedefinedtocontrolthelevelofeffectiveness(isthe

processmeetingornotmeetingit’sobjectives?)oftheconfiguration

managementprocess:

•Numberofconfigurationcorrectionrequestsandthenumberof

configurationrequests.

•Percentageofprocessthatcanobtainconfigurationinformationper

theprocessthatrequireit.

•Percentageofcapturedcomponentconfigurationsperthenumberof

knownI/Tmanagedcomponents.

Page36

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Accuracy

Informationaccuracyindicatorscanbeudasawaytoauditconfiguration

tedindicators:

•Percentageofconfigurationcorrectionrequestsperthenumberof

configurationrequests.

•Percentageofcomponentrecordswithaninaccurateconfiguration

figuration

ProcessCoordinatorregularlylectsalistofI/Tmanagedcomponents

andmanuallyverifiesthecapturedinformationwithactualinformation.

Efficiency

Themeasurementshelpdeterminethelevelofautomationimplemented

onfigurationmanagement

procesvolves,manualprocesswillbecomeautomatedviasystem

iciencyofthetoolsmustbecontinually

measuredtodetermineareasforimprovement.

•PercentageofI/Tmanagedcomponentconfigurationsgatheredvia

automatedmethodsversusI/Tmanagedcomponentconfigurations

gatheredmanually.

8.3Reporting

Reportsareproducedonaperiodicbasistosupporttheongoingoperation

lowingreportsprovidevaluable

informationaboutthestatusoftheprocess:

SubprocessKeyPerformanceIndicators

K1.1Numberofchangestotheschema

K1.2Datesoflatestchanges.

K1.3NumberofCItypeswithoutaidentifiedowner

K1.4NumberofCItypeswithoutconfigurationdocumentation

K1.5Numberandverityofincidentsrelatedtomissingattributesor

registrationofrelationships

K2.1NumberofmodificationstotheCMDB

K2.2Numberofincidentssignalled.

-Indicativeofunauthorizedconfigurationchanges

-Indicativeofunsuccessfulchanges

-Indicativeofplanningproblemsforchanges

K2.3Numberofincidentsrelatedtoincorrectconfigurationinformation

K3.1NumberofCIsfoundbydiscoveryactivities

K3.2NumberofattributesfoundforeachCIbydiscoveryactivities

Page37

CONFIGURATIONMANAGEMENTPROCESSGUIDE

K3.3NumberofrelationshipsbetweenCIsfoundbydiscoveryactivities

K3.4Numberofdifferencesreported.

K4.1Numberofreportsgenerated

K4.2Numberofsubscriberstoregularreporting

K4.3Number&contentofadhocqueries(canpointtotheneedtodefine

newstandardreports)

ConfigurationRequestEffectivenessReport

Thisreportdisplaysthenumberofconfigurationcorrectionrequestsand

lebelowgivesanexample.

ConfigurationRequests

UnavailableConfigurationInformation

InaccurateConfigurationInformation

SatisfiedRequests(ConfigurationRequestsminusUnavailableand

InaccurateConfigurationInformation.

ConfigurationRequestAccuracyReport

124

10

8

106

Thisreportchartsthenumberofconfigurationcorrectionrequestsagainst

ferencebetweenthisnumber

isassumedtobeasatisfiedrequest.

ConfigurationInformationRequests

SatisfiedRequests

7%

6%

Unavailable

ConfigurationData

Inaccurate

ConfigurationData

87%

ConfigurationInformationAvailabilityReport

Thisreportchartsthepercentageprocessthatcanobtainconfiguration

informationversthothatcannot.

Page38

CONFIGURATIONMANAGEMENTPROCESSGUIDE

ConfigurationInformationAvailabilitytoOtherProcess

13%

ESMProcessthat

canreceiveConfig

Info

ESMProcessthat

cannotreceive

ConfigInfo

87%

CapturedConfigurationInformationReport

Thisreportchartspercentageofcapturedcomponentconfigurationsperthe

numberofknownI/Tmanagedcomponents

CapturedConfigurationInformation

forI/TManagedComponents

13%Captured

NotCaptured

87%

ConfigurationDataAccuracyAuditReport

ThisreportdisplaystheaccuracyofthedataforI/Tmanagedcomponents

ormationshouldbecapturedduringauditsofthe

ortcouldlooksomethinglikethebar

chartbelow.

Page39

CONFIGURATIONMANAGEMENTPROCESSGUIDE

ConfigurationAudit

100%

80%

60%

40%

20%

M

a

i

n

f

r

a

m

e

Di

s

t

r

i

b

u

t

e

d

T

e

l

e

c

o

m

N

e

t

w

o

r

k

0%

Correct

IncorrectData

NotCaptured

Configurationdatacaptureautomationreport

Itindicatestheconfigurationdatathatiscapturedautomaticallyversdata

ortindicatesthelevelofautomationinthe

ormationshouldbegatheredby

collectingthenumberofrecordsinthedatabaofeachtypeofcomponent

wheredataiscollectedautomaticallyandcompareittothenumberof

ortcouldlook

somethinglikethebarchartbelow.

ConfigurationDataCollectionAutomation

100%

80%

60%

40%

20%

Di

s

t

r

i

b

u

t

e

d

N

e

t

w

o

r

k

T

e

l

c

o

m

H

o

s

t

0%

AutomatedManual

informationinthelogscouldbeutogeneratethereportsaboveorany

newreports.

ConfigurationHistoryLog

Thisloglistsnewandupdatedconfigurations,storedtoreflectthe

evolutionofhardware,software,

ortmayspecify

whethertheupdatesweretriggeredbydiscoveredconfigurationinformation

orbychangeexecutionresults.

Page40

CONFIGURATIONMANAGEMENTPROCESSGUIDE

ConfigurationErrorLog

Thisloglistrrorswhenattemptingtoenternewandupdated

logsan

eventwheninformationthatshouldbeinthedatabacannotberetrieved.

TheconfigurationErrorLogshouldbereviewedwithin1dayofanerror

andshouldberesolvedwithin5workingdays.

NewConfigurationInformationLog

Thislogliststhenewconfigurationinformationthathasbeenimplemented.

ChangedConfigurationInformationLog

Thislogliststheplannedconfigurationchangesthathavebeen

portalsolists

ngedconfiguration

informationlogshouldbereviewedwithin1dayofanunplannedchange

andshouldberesolvedwithin5workingdays.

Page41

CONFIGURATIONMANAGEMENTPROCESSGUIDE

Section

gs

9

Thisctionoutlinestopicstobecoveredinconfigurationmanagement

es,criteriaand/orguidelinesforthemeetingsareshown

themeetingsthereisarequirementforinputfrom

ConfigurationManagementduringChangeAdvisoryBoardmeetingswhere

RequestForChangesareevaluated.

•ConfigurationManagementMeeting(monthly).

•ConfigurationManagementProcessImprovementMeeting(yearlyoras

needed).

ConfigurationManagementMeeting

Thepurpoofthismeetingistoresolveconfigurationmanagementissues.

ThemeetingsshouldbeattendedbytheConfigurationManagement

ProcessCoordinator,ConfigurationManagementI/TStrategicBusiness

Unitreprentatives,tingshould

beheldmonthlyorasneeded.

Thefollowingisanexampleoftheformat/agendaoftheconfiguration

managementmeeting.

•Reviewconfigurationmanagementreportsandresolveissues

•Identifyandresolvefailuresoftheprocesstomeetitsdesign

•Reviewconfigurationmanagementstrategy.

ConfigurationManagementProcessImprovementMeeting

Thepurpoofthismeetingistoreviewtrendsrelatingtotheconfiguration

managementprocessandtodetermineifimprovementsarenecessary.

Recommendationsforimprovementarereviewedandadeterminationis

ndexpectedresultsare

tion,thismeetingcanbeaforumfortheConfiguration

ManagementI/TStrategicBusinessUnitreprentativestoshareideasfor

improvementswiththeManagementProcessOwnerandencourageopen

etingischairedbytheConfigurationManagement

Page42

CONFIGURATIONMANAGEMENTPROCESSGUIDE

ProcessOwnerandattendedbytheConfigurationManagement

Coordinator,ConfigurationManagementI/TStrategicBusinessUnit

tingshouldbe

heldquarterlyoruponrequest.

Thefollowingisanexampleoftheformat/agendaoftheprocess

improvementmeeting.

•Communicateproblemareas:process,documentation,tools,dataentry

fields,dataintegrity,reporttc.

•Suggestedareasforimprovement.

•Reviewnewreportingrequirements.

•Providefeedbackontheexecutionoftheprocess.

•Documentandcommunicateimprovementplans.

Page43

CONFIGURATIONMANAGEMENTPROCESSGUIDE

elationshipswithOther

Process

10.1Introduction

10Section

Whenoperatingwithintheconfigurationmanagementprocess,itis

imperativethatallparticipantshaveaclearunderstandingofhowthe

processinteractswithotherdisciplineswithintheXXXXXI/T

environment.

10.2SystemsManagementProcess

SystemsManagement(SM)processreprentatofintegrated

cess

arechangemanagement,incidentmanagement,problemmanagement,

rvicelevelmanagement,capacitymanagement,performancemanagement

etheconfigurationmanagementprocess

mayinteractwiththeprocess,itisimportanttounderstandthe

interrelationshipsbetweenthem.

ingon

thefinalorganization,responsibilityforthedisciplinesandfunctionsmay

resideeitherinasingledepartmentwithasingleindividual,acrossmany

departments,ttheorganizationthatis

important,buttheeffectiveexecutionofconfigurationmanagement

responsibilities.

Page44

CONFIGURATIONMANAGEMENTPROCESSGUIDE

ArchitecturalDesign

BackupandRestore,

ContingencyPlanning

Procurement

ManageChanges

DevelopandTrackITPlan

ITPlan&architecture

configurationstandards

BackupandRestore

ReleaManagement

Configuration

Updateor

Inquiry

ManageProblems

ProjectRequest

AdministerTechnical

ConfigurationInformation

Configuration

Information

ManageProblems

IncidentManagement

Audit

Requests

Configuration

Information,

Validation,

Findings

DesktopChanges

ProjectRequests

(includesIMACactivity)

Ast&Inventory

Management

Capacity&Performance

Management

ManageChanges

AnyProcess,

ConfigurationStandards

IncidentManagement

Eachprocessshouldanswerthequestion:“Whatwillbeprovidedto

configurationmanagementprocessandwhatixpectedfromthe

configurationmanagementprocess?”

ThefollowingisadescriptionoftheSMprocessthatinterrelatewiththe

configurationmanagementprocess.

IncidentManagement

Thisprocessinvokesconfigurationmanagementtoretrieveconfiguration

ivesfromconfiguration

managementsignalsaboutdeviationsbetweenauthorizedandactualstatusof

configurations.

ProblemManagement

Thisprocessinvokesconfigurationmanagementwhenhardwareand

softwareinformationisrequestedtoassistwithproblemdeterminationand

resolution.

ChangeManagement

Thisprocessinvokesconfigurationmanagementwhenachangerequestto

implementanewcomponentoraffectinganexistingcomponent

ordisupdatedandtheNeworChanged

ConfigurationInformationLogisupdatedwithanexpectedconfiguration

changeentry.

Page45

CONFIGURATIONMANAGEMENTPROCESSGUIDE

ServiceLevelManagement

Thisprocessinvokesconfigurationmanagementwhenmeasuringthe

performanceoftheconfigurationmanagementprocess.

RecoveryManagement

Thisprocessinvokesconfigurationmanagementwhenhardwareorsoftware

failuresoccurandconfigurationinformationisrequiredtorestore

operation.

PerformanceManagement

Thisprocessinvokesconfigurationmanagementwhenthereisaneedto

tunevariouscomponents

CapacityManagement

Thisprocessinvokesconfigurationmanagementwhenthereisaneedto

upgradecomponentcapacity.

SecurityManagement

Thecuritymanagementprocesnsurestheconfidentialityandintegrity

orinformationtechnologyasts,andmanagestheregistrationor

enrollmentofpeopleandprogramstoaccesscontrolledinformationsystem

ocessinvokesconfigurationmanagementwhensystem

configurationinformationisneededtoregisterclientstoappropriate

rvicesusingrelevantregistrationproducts.

SoftwareDistributionManagement

Thesoftwaredistributionmanagementprocesnablessoftwaretobe

deployedonI/ocesswillrequire

informationfromtheconfigurationmanagementprocesstodetermineif

softwaredistributionsarenecessaryorpossible.

10.3BusinessManagementProcess

WhileSMfocusonmanagementoftheI/Tenvironment,theXXXXXI/T

organizationisalsosubjecttotheguidelinesofmanyotherbusiness

tion,theconceptsandconstructsoftheconfiguration

managementprocesscanbeappliedacrosstheentireXXXXXI/T

environmentbeyondI/Trvices.

ThefollowingisadescriptionoftheSMprocessthatinterrelatewiththe

configurationmanagementprocess.

Page46

CONFIGURATIONMANAGEMENTPROCESSGUIDE

HelpDesk

Thisprocessinvokesconfigurationmanagementwhenhelpdeskpersonnel

requesthardwareandsoftwareinformationtoassistwithproblem

determination.

InformationTechnologyPlanning

InformationTechnologyPlanningencompasstheactivitiespursuedby

XXXXXI/Tmanagementtoidentifyandfulfillthetechnology

requirementsfortheirrviceofferings,andtointegratethorequirements

figurationmanagementprocess

shouldattempttofulfillXXXXXI/Tmanagementrequirements.

BusinessPlanning

BusinessPlanningencompasstheactivitiespursuedbyclient

organizationstoidentifyandfulfillthefunctionalrequirementsfortheir

businessneeds,andtointegratethorequirementsintotheirexisting

geManagement,BusinessPlanningcontributesto

identificationoftheasssmentcriteriaforcategorizingandmitigating

configurationmanagementprocessshouldattempttofulfillXXXXXI/T

managementrequirements.

ServiceDelivery

ServiceDeliveryencompasstheoperationalproceduresandpractices

executedbyXXXXXI/

theprocessdoesnotimpospecificrequirementson“how”arviceisto

beexecuted,itdoesprentguidanceonthemanagementdisciplines

,thisProcessGuidereprentsamodeof

managementandnotaprescriptionforexecution.

ProjectRequests

ServiceRequestencompasstheproceduresandpracticesdeployedby

XXXXXI/erequest

alsoencompassthereportingandauthorizationproceduresdeployedby

theclientpriortocontactingXXXXXI/igurationmanagement,

rvicerequestmaygeneratearequirementthatissubjecttothediscipline

ofthisprocess.

AstManagement

Theastmanagementprocessmaintainsallinformationregarding

technologyasts,includingleadandpurchadasts,licensand

inventory(includinglocation)fromthetimeanastisreceiveduntilits

etmanagementprocessandconfigurationmanagement

processshouldsharedatabassothatthereisonesourcetoretrieve

informationaboutI/Tmanagedcomponents.

Page47

CONFIGURATIONMANAGEMENTPROCESSGUIDE

10.4InterrelationshipMatrix

Theconfigurationmanagementprocesshasdataandfunctional

trixoutlinesthe

inputsandoutputstotheConfigurationManagementprocessinrelationto

otherXXXXXI/Tmanagementprocess.

Process

HelpDesk

InputorcontrolprovidedOutputsreceivedfrom

toConfigurationConfiguration

ManagementManagement

Configurationinformation

request,includingclientor

rvicecriterianeededto

retrievetherequested

information.

Configuration

requirementswhenclient

requestsimplynewor

upgradedconfigurations.

SeverityandPriority

informationofeach

configurationcomponent

badonrvicelevel

objectives.

Configurationinformation

requesttoanalyzeand

resolveproblems.

Configuration

informationaboutthe

componentsudto

deliverrvicestoclients

callingtheHelpDesk.

Notificationto

requirementsubmitter.

Problem

Management

Configuration

informationrequiredto

analyzeandresolve

problems.

RequestforinformationtoPriorityandSeverity

determinethepriorityandInformationforafailing

verityofafailingcomponent.

component.

Configuration

informationtodetermine

thecomponentsthatare

affectedastheresultof

anotherfailing

component.

ExceptionLogofmissing

orincorrectconfiguration

Page48

CONFIGURATIONMANAGEMENTPROCESSGUIDE

informationthatis

createdasaresultofthe

CaptureConfiguration

InformationSub-Process

ErrorLogoferrorsthat

werecreatedwhenthe

ConfigurationDataBa

wasupdatedornew

recordsorfieldswere

created.

ChangeRequestfromthe

Implement(Designand

Plan)SubProcessto

makechanges/additions

totheConfiguration

Information.

Configuration

Managementsupplies

requestedConfiguration

Information

Change

Management

Changerequest,approval,

scheduletotheAnalyze

ConfigurationInformation

sub-processtomake

changes/additionstothe

configurationinformation.

Changenotificationfrom

animplementedchangeto

ensurethatthe

Configurationdatabais

updated.

RequestforInformationtoInformationtoChange

determinetheimpactofaManagementto

ineimpactandrisk

asssments.

Changereviewstatus,

especiallyfeedbackfrom

technicalreview.

Configuration

implementationplanfor

configurationsthatneed

stagedimplementation

(emorethan

onechange).

ChangeexecutionreportsPreparedchangereadyto

areneededtoreflectactualbeimplemented.

configurationsinthe

informationba.

ConfigurationRequirementConfiguration

forbackup,archiveandinformationaboutvital

retrievalconfigurationscomponents.

Backup&

Restore

Management

Page49


本文发布于:2022-11-08 17:41:28,感谢您对本站的认可!

本文链接:http://www.wtabcd.cn/fanwen/fan/82/453916.html

版权声明:本站内容均来自互联网,仅供演示用,请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系,我们将在24小时内删除。

下一篇:PROCESS
标签:process
相关文章
留言与评论(共有 0 条评论)
   
验证码:
推荐文章
排行榜
Copyright ©2019-2022 Comsenz Inc.Powered by © 专利检索| 网站地图