I'm looking for a best practices approach (or checklist) to taking a software out of service from reviewing vendor contracts, archiving data and removing software. The task list would encompass more than you'd likely need to do for any one software retirement. Thanks Saving Changes...
Sort By:
Elyse NielsenSenior Project Manager| Ascension Health Information ServicesHaines City, Fl, United States
Hi Shari,
I'll start off with a couple of items to check out for decommissioning a system. I'm assuming there is not going to be a replacement. These are not in any particular order, just a place to start.
~ Review workflow impacts and assure there is stop doing, start doing, and continue doing guide for those to follow when the software has been decommissioned.
~ Ascertain the value of the data, and how long it legally needs to be stored. Also is the quality of the data high enough so it can be combined or migrated to another data store.
~ Review the integration of the applcation, and determine if there are any significant dependencies or gaps which need to be handled.
~ Review the reporting of the application, and determine if there are dependencies or downstream impacts which need to be dealt with another way.
~ Phase the removal by removing computer access to the application, then the actual equipment storage.
Renee GalligherIT Project Manager 3, PMP, ICP| Idaho State Board of EducationMeridian, Id, United States
Thank you for the information. I too have been tasked with this and I had a general idea of processes to follow, as a starter, but I wanted to research what others have done. Thank you for the feedback Elyse. Saving Changes...
