Okay, my learners, we're gonna move on to listen. 3.4 service transition process. So are learning objectives for today. In this video, we will cover the purpose and objectives of service, transition, planning and support
service asset and configuration management s A C M processes and break down and then breaking down the S a c m concepts depicting the key systems within the process.
All right, so we go into a transition planning and support
the great stuff, right? So this right here, in a nutshell, it ensures that all parties adopt the common framework of a standard reusable process and supporting systems in order to improve the affecting the effectiveness of integrated planning and coordination activities. So it helps provide that clear
in comprehensive plan that enables a customer and the business change projects
to allying their activities with the service transition plans so identifies and manage. It controls risk to minimize the change of failure and disruption across the transition activities,
and also ensures that the S T issues and risks and deviations are reported to the appropriate stakeholders and decision makers
like, for example, you have suppliers represent the risk and large applications risk of deviation from the service from what we said would be so it in a nutshell as well, it just monitors and improve the performance of the S T life cycle stage as a whole.
So when you start looking at you know what the scopes is, you know is make sure that you maintain those policies, those guidelines, those standards and those those models of service transition activities and processes actually got a guy that each major change or new change or new service changes
that's through the through the whole S T process,
as well as prioritizing conflicting requirements of the STV resources and keeping a review and improving performance of the transition, planning and support activities. So when you start getting to their, you know, you could be able to coordinate with the program management
in the service design or the service development activities as a whole.
so the service asset and configuration management, the S a C M process. So in this case, so the e understand that the relationship between the service assets right. So the information includes details of how the assets have been configured in the relationship between those assets.
So the logical relationship down to the infrastructure level is understood at all components. When we discussing that s a C M process.
So the objectives for is just to identify the sea ice, including the versions, the baselines, the components as well as the attributes and the relationships between those services. So the integrity of the sea ice through the life cycle by working with the change management, everything, everything in relations with each other.
To ensure that Onley authorized components are used, only authorized changes are being made just to ensure that
the services is being established and it's being is maintaining an accurate and a complete CMS. So and as well. You know, you maintain that information on a historical plan in a current state services and with other, um, sea ice in that sense
so that may include the interface between the asset register normally under the control of the financial management.
So those interfaces with the internal and external service providers where there are assets and configuration items that need to be controlled like share assets, for example.
so some of the basic concepts of S E. M s a C m. So you have your configuration items Some of the abbreviations that I have been mentioning, as well as the configuration management system, which is CMS in the definitive media library. Now, those particular ones, um,
we could go in depth with the more of the C I. A writer. That is an important term to understand within
the S C a m. So this right here it includes
is it give you the information about this the c I. So it's it's recorded of the configuration records. So within the C. M s and maintained throughout the life cycle of a service asset and configuration management. So sea ice are under control of this change management.
So they typically include this I T services, hardware service, um, software, buildings, people, even formal documentation such as the process documentations or the service level agreements. So CSR service assets that are important to the delivery of the organization services. So, CSR under example,
the service service life, psycho sea ice, as you can see here.
And those examples, like becomes like business cases or service management plans or service life cycle plans. Then you have your service. Sea ice encompasses, like the service capability assets the management organizations. You know, knowledge and people service packages, service models.
And then you have the organization sea ice. It's more of the documentation that will define the characteristics of the C I A.
And then you have the internal sea ice where it's like, um, more of the comp comprise through the deliver by individual projects, including, like tangible, like data centers or intangible assets, such as software
that's that's included in the delivery have external sea ice, more example of external customer requirements and agreements releases from suppliers and subcontractors.
Then you have your interface sea ice, where it comes into more of a play of a that's required to deliver toe in the end service across the service provider interface, for example, exploration document that specifies how incidents will be transferred between the two provider's service providers. Okay,
and then you go to the give me a little breakdown of the C. M. S. So the CMS is it's maintains s So this is like the helpful during many other processes, so
such as the change management, for example, an organization with the mature CMS will easily be able to predict the impact that a change for half on the other aspects of the of their i t environment.
So by recording the relationship between the sea ice, the S A. C M process provides a model of a service that are delivered so this model can be used so it could be to assess the impact and cause of incidents and problems that could be for a proposed changes. New and change services, technology refreshes or upgrades.
So these are not nature. So the CMS forms
ah, part of the S K M s, which is the service knowledge management system, and that s K M s is a tool used to manage the organization's knowledge. And the S K M s will be discussed later on during the K M process. Okay,
And then we go into the C m d. B, which is the configuration management database. Now, this is more of a single logical storage area to where you have more, more of a multiple locations, so that so is controlled by a service assets and configuration
of what's recorded in the confirmation management system.
and then we go into our configure configuration baseline. So this right here is more of a configuration of the services and the product and the infrastructure that has been formally reviewed and agreed. So service that is basis off of the future activities
as well as it could be changed through a formal, um most likely has changed to a former changed procedures.
When you're going through that baseline,
And then, of course, we have our definitive media library. So are definitive media library. That's more on a circle of is controlled.
It's like a secured storage place for all media s C I. So the demon the D m l it can include both electronic and physical storages and contents include definitive copies of purchase software, copies of software developed on site is media licensed documentations master copies of control documentations.
So it does not include any backup of any kind.
alright, So in summary less than 3.4 the close out. So I provided you keep processes the service asset and configuration management, the transition planning, support key concepts with that faras the configuration items and CMS as well as the defendant Media Library.
So our next come up we will have in the lesson
quiz and then on to the next lesson. All right, See, there