Into which ITIL process does application decommission fit?

[RickBP]

Need to file a "application decommission" template by it's appropriate ITIL process (for use by others) and was looking for some guidance. My guess would be "Change Management" but wondered if it has been identified as a part of some other process.

Rick

[WendyB]

Rick,

We're adding it into Change Management. But might also come in via Release and then go to Change for the RFC.

Just a thought.

~W

[Ed]

Rick / Wendy

I would have thought that this was more a place for Configuration Management. It is certainly not Change.

Regards

Ed

[WendyB]

Ed,

My thinking is that since it is a change to the environment, even though it's a decomission, it would have to be validated and approved by Change. And from Change the approval to change the appropriate CIs to indicate that it was decomissioned.

Just my two cents,

~W

[Ed]

Hi Wendy

I agree, it would have to be validated and approved by Change as does any amendment to the Environment.

I felt that as we were talking about decomissioning, and the final steps will be to change the CI to make it 'dead', then the template would sit with Config.

The Change process is all about Management of changes, rather than 'owning' and this reinforces my thinking here.

thoughts!

Regards

Ed

[Guerino1]

Hello All,

OK, I'll throw in my two cents...

How about you put the templates under "Project Management", where they belong? After all, an application decommission is large enough to be its own project, these days. It's one of multiple IT Operations type projects.

For example, if you have an application that exists in your Development, Systems Integration Testing, User Acceptance Testing, and Production environments, you will have to decommission that application and any related infrastructure that gets shut down, including dependencies, in all environments, starting in Dev and moving all the way to Prod. You will need to coordinate work from multiple teams/organizations who control multiple domains within any given environment and you will want to perform the decommission over a sequenced time to ensure that as you shut things down in one environment nothing breaks before you allow things to shut down in the next.

In most companies we deal with, an Application Decommission effort is a form of project that typically generates multiple Change Requests to perform the work to shut down all related components. Some enterprises might also generate a Decom Release in order to have a unique Release to associate the Change Requests to but this is rare.

I hope this helps.

Regards,
_________________
[Edited by Admin to remove link]

[MrDon]

I would say a change as you are changing the environment by removing the application from the userbase.
Once the OCR is raised, it would have to be approved by the necessary parties - once approved, job done.

[UKVIKING]

A decommsion is the same as a addition to the IT environment that is managed.

A Change Request would be needed to be raised

If there is Change Management
If the CM process includes the IT environment being affected
If the device is being monitored/used etc by any person.
If there is a CMDB/Asset Register etc
If there is or is not a Addition/Deletion process.

John Hardesty

[Fabien]

Defintely a Change. Once it went through that process, I like to see the execution by a PMO which would normally holds much of the release management process anyway. If the application is large enough that you think about "decommissioning" it, then it should be done the proper way, through a project.
_________________
BR,
Fabien Papleux

Accenture
Technology Consulting | Service Excellence
Red Badge Certified

Twitter @itilgeek

[Ziad]

Release operates under Change, I cannot think of any situation where Release is independent from change.

Since Release is responsible for the rollout and the backout of applications, Release will be responsible of decomissionning the application (under Change, an RFC is required for any release activity in the live environment).

So I will say you template should be part of the Release Management process.

Cheers,
Z!