Definitions of Planned Disposition values?

[MEBoatman]

I've searched but can't seem to find any definitions related to the 4 values for the Planned Disposition field. Can anyone point me in the right direction?

Invest, Sustain, Migrate, Retire

I mean it's not too hard to use reason to figure these out. Just wondering if there is anything documented...

[mcastoe]

There is nothing formal though they are terms that have been in use for many years when describing the dispositions of Applications and in fact Gartner has made considerable reputation with their TIME (Tolerate, Invest, MIgrate, Eliminate) model over the years.  Our APM Dispositions match in concept. Sustain what is working, Invest in what's working exceptionally well, Migrate the necessary that have high costs, poor performance/reliability, bad architecture etc, and finally Retire duplication and unused.

thanks,

mark  

[MEBoatman]

Thanks, Mark!  I'm super delinquent on responding - my apologies.  So it seems like applications might move between the various planned dispositions...  For example, App A might be something we need to invest in to add some capabilities so we mark it Invest right now.  Next year, it might move back to Sustain when that work is done. Is that fair?

What about the difference between Invest and Migrate? I know some in our org have struggled a bit with that...  Let's say an application is mainframe-based so we want to replatform it to bring it to modern standards. That seems to me a clear case for "Migrate" with an approach of "replatform" but others have said that by doing that we are really investing in it so Invest seems more appropriate.  I suspect this is more art than science...?