Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: Robertkese
New Today: 21
New Yesterday: 66
Overall: 142240

People Online:
Visitors: 70
Members: 0
Total: 70

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

Note: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


The Itil Community Forum: Forums

ITIL :: View topic - Into which ITIL process does application decommission fit?
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Into which ITIL process does application decommission fit?

 
Post new topic   Reply to topic    ITIL Forum Index -> Miscellaneous
View previous topic :: View next topic  
Author Message
RickBP
Newbie
Newbie


Joined: Aug 01, 2006
Posts: 1

PostPosted: Wed Aug 02, 2006 4:50 am    Post subject: Into which ITIL process does application decommission fit? Reply with quote

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
Back to top
View user's profile
WendyB
Senior Itiler


Joined: Apr 03, 2006
Posts: 78

PostPosted: Sun Aug 06, 2006 4:51 am    Post subject: Reply with quote

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
Back to top
View user's profile
Ed
Senior Itiler


Joined: Feb 28, 2006
Posts: 411
Location: Coventry, England

PostPosted: Mon Aug 07, 2006 11:09 pm    Post subject: Reply with quote

Rick / Wendy

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

Regards

Ed
Back to top
View user's profile
WendyB
Senior Itiler


Joined: Apr 03, 2006
Posts: 78

PostPosted: Tue Aug 08, 2006 1:23 am    Post subject: Reply with quote

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
Back to top
View user's profile
Ed
Senior Itiler


Joined: Feb 28, 2006
Posts: 411
Location: Coventry, England

PostPosted: Tue Aug 08, 2006 5:07 pm    Post subject: Reply with quote

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
Back to top
View user's profile
Guerino1
Senior Itiler


Joined: Jan 01, 2006
Posts: 500
Location: New Jersey

PostPosted: Fri Aug 11, 2006 2:04 pm    Post subject: Reply with quote

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]
Back to top
View user's profile Send e-mail Visit poster's website
MrDon
Newbie
Newbie


Joined: Aug 24, 2006
Posts: 10

PostPosted: Fri Sep 01, 2006 10:14 pm    Post subject: Reply with quote

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.
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3298
Location: London, UK

PostPosted: Sun Sep 17, 2006 6:39 am    Post subject: Reply with quote

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
Back to top
View user's profile
Fabien
Senior Itiler


Joined: Sep 27, 2005
Posts: 207

PostPosted: Sun Sep 17, 2006 6:52 am    Post subject: Reply with quote

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
Back to top
View user's profile Send e-mail Visit poster's website MSN Messenger
Ziad
Senior Itiler


Joined: Sep 27, 2006
Posts: 91

PostPosted: Thu Sep 28, 2006 1:05 am    Post subject: Reply with quote

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!
Back to top
View user's profile Send e-mail
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Miscellaneous All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.