Service Asset and Configuration Management – Example

Types of Changes Colonial mutual pictures and configuration management morning loneliness vital extra Moroccan football site in this lesson will be worthwhile to take a few minutes and water's assets and configuration management exam hopefully this example will add colour from the previous lessons and give you insight into some about the continuing by having a was CMD B*architecture of the previous lesson configuration management depends on mature change my these two processes from the idle framework must work together in mutual together in order to improve the quality of the data unseemly being as well as provide insights into the architectures what is the advisers unseemly bewitches and configuration management system to changes occur to the IT infrastructure and from what to write to the change management was being links about the service asset configuration management processes so there is the morning your experience configuration to always minimise so what refuting the example of a typical type of change within the IT infrastructure with the component of technical architecture what operating system the calming and happens Bolshevist operations response transition depending on your organisation was important to keep the infrastructure company to homeless process in place to update the technical architecture when I otherwise we might when you close to an application for major functional anatomy this is primarily with the business pages to do any new functionality because business process change the business environment has changed and need to drive outcast or improve performance from the functional requirements could about and eventually deployed to the production environment this process occurs to recycle was also intimately tied to change management the cycle is about gathering the functional requirements and taking them through what's called the so the model which is linked to acquitted testing and Marianne is deployed to production change management problems the process by which it moves to steps likewise the configuration management system captures the data with new baseline as these releases moved to the recycle another interchangeably transition your initial response was: is what we would call: the organisation produces commercial off-the-shelf software and loan applications eventually removed to source: from the portfolio when this occurs the configuration management system should be updated to illustrate that the new service is available likewise all the underpinning technology components including vendor processes and people supported; within service architecture of change of the hard disk space to storage area network this is probably standard change because the existing procedure about when to do it and defined trigger oftentimes event monitoring system will notice the threshold is breached and it's time to get your standard maintenance windows and procedures in place and which delivers however change) should also be created along with the update to the configuration management system to the data is available that this occur and last but not least for example prospective research bypassing this is one often comes up in classes because people wonder is that an Internet standard change will request the courses yet it depends on how the organisation views research bypassing is that really important with one mitigate so much of that they won another standard procedure to go through and capture the day was generally are not considered configuration items in most organisations the are for they are within the CMD B however the transaction that occurred to reset my password is part of the configuration management and knowledge management system capture of the event occurred because it consumes resources however in general password are not come under change control within the configuration management system and this is just a choice there is no best practice around however most organisations do not can manage specific individual password within the configuration management system Interfaces to Change Management Let's start with specific examples change lets assume that we have crossed change that has been created of giving you extra that is probably email servers I've outlined service architecture world of email service at the very top of email is connected to some applications and systems infrastructure which V-max au revoir to thwart this request will change through the change process and see how Leinster this shows us and configuration management processes. Change management process is to raise and change request is usually done within the 97 tour and a change request is created from the valuation is that knowing the record would be available within the configuration management system which will for and against the side. Of the change process is to assess the change this is typically were change advisory board care is convened with the changes only to determine whether or not to approve or authorise the change typically account things such as risk and change the timing of change how effects of the changes the many occurring within the IT infrastructure et cetera so this assessment of the change occurs it oftentimes very useful to look at what is called the business impact analysis the business impact analysis is when we're stars a piece of infrastructure and what little cash to along with what services they may in fact this is how risk assessments typically now wonders this information come from will also come from disaster configuration management system and one of the primary benefits of having a robust CMD be ensure architecture in place the can assess the risk of change so we don't ultimately have any unintended consequences do not feel change so as you can see the change management process not only works to update the configuration management system but also consumes the Gaidar that with in the configuration management system to make better decisions and every about previous lessons that really the whole point capturing all Baldersdale and aggregating and information and knowledge is to make better decisions one of the key decisions that often made with need a change management process is whether or not to approve a change and when it should be scheduled to minimise risk to the business the third step of the change management process is to make that decision we authorise or reject the change based on the risk assessment and the outside business benefit the marketing by successfully implementing regardless of the decision that decision should be captured within the CMS the next step is to want make the change implementation this will coordinated teams that are actually going to implement the change this might be this package was set of change CRS in the configuration management process Wanna make sure we capture the baseline in the future state were the configuration items should look like we implement the change we one of the change to determine whether successful this is Windows running on the configuration items that was supposed to change and make sure that they did in the correct configuration and last but not least because the change of the change recognises that changes complete and one validate the records have an updated appropriately liquidated is available within the CMD be Configuration Drift The water example of a changed hopeful you can see how change management and service asset configuration management are intimately related the depend on each other change management depends on the data within the service asset configuration management system to make better decisions about when authorised project changes in the missionary schedule likewise the service asset configuration management process depends heavily on the change process to keep the CMD be and service architecture information up-to-date to consider armaments were change control was not mature if you work for an organisation with change control is not fully mature and scope is to now what is the likely result was you can imagine we have things that we think we know list of the service asset configuration management system and service architectures with change control is to Melbourne scope was not fully mature and fully integrated in the service asset configuration management system what happens over time over time we experience was called configuration drift any information within the CMD B becomes out of date movie actually now is a much for the picture of what we think we and the end result is that we may not make the best decisions recorded with the information that we have access to configuration drift is a condition in which over time the data within the CMD be becomes out of date was they'll which measures as the verification audit process this is akin to taking a physical inventories compared to a virtual inventorying in inhibitory management system developed in the house were in the retail establishment alma mater so people go out and out accountant actually on the shelves within the actual counts what the computer system projects they should have the difference is called shrinkage in the configuration management space the same principle for every now and then we need to go out and verify that the configurations in the actual real systems are was recorded in the configuration management system where those differences were deviations, configuration drift configuration drift is an indicator of how mature processes are very immature process change also possess and configuration management will result in significant configuration drift the verification audit is both necessary and valuable another expat to the Danish problem that we can last was one portholes old-timers members to courts is never sure the CMD BSO's architectures that kept up-to-date service asset configuration management process alters make sure that we have one clerk once was of truth in one place we can go to interrogate our systems to understand what was architectures look like also we can make better decisions tonsorial this lesson we talked about the service asset configuration management processes are intimately linked to change management we also covered how service asset configuration management process creates data and information which is the basis for decision making those decisions are oftentimes would give us the ability to improve services for customers and disappointed competitive manage without about configuration drift is an indicator of the change control is not sure what scope is tuna web service asset configuration management is not whingeing tightly enough and lastly we talked about the risks that configuration drift creates a greater awareness will remain a poor decision was should remember thank you for business last NLP one something look forward to seeing you in future lessons

#ITServiceManagement #ITIL