Service Asset and Configuration Management

Service Asset and Configuration Management Process Our longest result architectures and configuration management monomers loneliness of an eye towards the a lot of football side and this was talk about showbiz acid and configuration management process this is the process by which configuration data is collected and maintained over time in previous lessons we talked about some of the critical factors of success the required to build the CMD B*architecture and one of them is how you keep that information is accurate and up-to-date the service acid and configuration management process has objective to maintain accurate configuration information on the installer of planned and Chrysler services another CRX is the definition of the objective straight out of the vital service transition publication to mean if we have a CMD be mom ensure that the information in it is correct it also has to be complete this is one of the big challenges and we talked about the previous lessons we have the data sources gaining complete and correct information is difficult not to have to have way to keep the car because things change over time as I mentioned in a previous lesson organisations is not uncommon to thousands of changes to be applied the IT infrastructure within a monster to how we keep that her and that is the objective of the service acid and configuration management classes there is tremendous value in understanding the service architecture is the basis on what we make of strategic and operational decisions that quote directly from the CIO of Fortune 100 companies allowed privilege to work with the understood that the service architecture and CMD being provided insights operational teams in strategic teams across the organisation to the benefit of customers however it is oftentimes challenging to keep that information is accurate and up-to-date to how we deliver if we look at the service acid and configuration management process you can see the activity Malabon while response left-hand side management plan that we decide what is were trying to figure out what questions were strategic and operational value and would ensure we identify configuration items we need them would label them were baselines how often do we discover in the configuration control how we make sure that information is continuously being updated with changes how we account and report against the CMD being so that we can assess whether or not the complete in our discovery and use the information correct last monopolist we have to have a verification process in place if we don't we don't know how covenant we should be in a ability to make decisions with the data we have is the data accurate verification are it will give some insight into how good how bad with the configuration data errors only take appropriate action to management and Wednesday this is where we do requirements design we asked the question what are we trying to accomplish houses integrate with the police and deployment plans and how we would integrate the data into the decision-making process we have to have an understanding of what strategic questions were trying to answer and that will give us a configuration management player and we have a plan valuate the resources is required to execute the plan and make a business decision about what kind of return on investment we may or may not get if we follow through with a configuration plan Activity Model for Configuration Management The next the reactively model configuration identification is Wanna make decisions about how to identify and configuration items remain them about labelling Monday and documentation baselining also release identification numbers these are about redefining attributes of the CRs we wish to capture based on the strategic plan that we came up with in the previous start is also one of the fibreglass structure of the CRs we talked about the class structure as a way of organising and configuration islands based on what makes logical sense against the strategic plan tarantula architectures that we came up with configuration identification and what attributes we want to capture is one of the most difficult decisions and organisation to make the reason it's so difficult because they are such a desperate need for information across the organisation executives and operational teams have very different Dayna needs therefore configuration identification will likely inspire a great deal of debate among what's the appropriate structure and level of detail and regularly do we want to get out of the CMD be likewise configuration control this is really about how to integrate asset configuration management process with change management process if we have changes to the IT infrastructure over time how we make sure the configuration control is integrated in the so that the configuration attributes are updated as things change analogy when things occurred suddenly have a historical baseline as well as a client state of what the state of the configuration items were and are stars accounting and reporting this very valuable information for service asset configuration management teams we have to know what is the stylus above the change wrecker of all the configuration wrecker and when things being updating what proportion will be running against the CMD being in order to assess the effectiveness of the integration of the CMD beadwork the change process and is an obvious source asset configuration management process itself and last not least the idea of verification on how often will a lot of the physical CRs and compare them with what the CMD B cells and look for configuration drift can run on it and discovery and test to see how affected will be and maintaining the objective of the source asset configuration management process to both collect capture and keep up-to-date and accurate data about configuration items to these on the activities of the source asset configuration management process solicitor work formula and interfaces to change management service asset and configuration management must be integrated with the change management process if it's not will end up the place were configuration drift is always happening because of change to will look of the change process of the very top without raising record change across assess changes authorise them coordinate the implementation review change and caused the change this is the basic activities of change management and each one of steps we want to integrate that change process to service asset and configuration management process will raise change records we want we will report an order against what's happening to the CRs we assess changes want to identify the Battersea arts in fact is the CMD being provides a great basis by which we can assess changes if we understand what touching within the service architecture we avoid the risk of the change only authorise the change we have to update of workers in the CMD being so that we know that change is going to occur within the forward schedule change change calendar obviously upon implementation of the change we want to capture the release information and appear that the baseline to make sure that the CI records are kept up-to-date with what actually occurred in reality reviewing the change this is one we assess whether the change was successful in one able to use the CMD being on the baseline against the future state and determine whether or not the configuration item is accurate and is consistent with what we expected in the change process and will close the change this is probably the most important power particularly when organisations are starting out we have to make sure that all the close process is a task associated with updating all the affected CRs so we can maintain that they the overtime is no danger driver in one court always knows the time and managing clerks is never sure that's the point of the CMD be we have an integrated data source the consider the source of truth we generally know what time it is however it seems we have configuration drift multiple sources of data we never know which data source to trust the idea is to have this conceptual CMD being is fully integrated into your varietal processes to keep the data up-to-date accurate and complete solicitor manager review in this lesson it should be clear that there is no want outlook for service architecture of the challenge is to understand was the strategic objective of the service asset configuration management process what questions are we trying to insert in the building architecture that is supportive of that understanding is ACL also asset configuration management is about providing accurate data and information the vital process it has the title process that keeps the CMD be up-to-date is intimately linked change management it is impossible to have a much more service asset configuration management process that is unrelated to change thank you for taking the time to watch this lesson around Woods

#ITServiceManagement #ITIL