Error rendering macro 'rw-search'

null

Downloads

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel2

What the Lifecycle Vector Is

...

2. Disposition, what to do with it. Within each direction, iDNA adds what the application needs:

LabelMeaningWhat to do
Keep/ModernizeKept, and in considerable use: at least medium usage in the last 90 days.Make it ready for the target platform. These applications come first in modernization.
Keep/QualifyKept, but used little in the last 90 days.Look at the application before investing in it: is it worth modernizing, or on its way to sunset?
Sunset/ArchiveReady to retire, but some replica still holds documents within your retention period.
Archive
Consider putting the application
, then remove it
on a read-only archive server.
Sunset/DeleteReady to retire, and no replica holds documents within your retention period.
Remove the application; no archive is needed
Application can be deleted if reducing the number of databases is relevant.
Sunset/QualifyWould be retired, but something prevents a safe decision, for example no retention configured, or replicas that disagree.Resolve the named issue first. Until then, iDNA recommends neither archiving nor deleting.

Both Keep dispositions continue to modernization: every kept application gets a modernization vector (see Modernization Vector: The Route to Ready). Sunset applications get none, because an application you retire needs no fixing.

...

  • Sunset/Delete and Sunset/Archive: before you retire an application, check who used it last, so nobody loses something they still need: [App Lifecycle] → [Top User Lookup] and [Department/Location Activity Lookup]. Archive where the vector says so, then remove the application in your Domino environment; iDNA identifies the candidates, the retirement itself happens outside iDNA.
  • Sunset/Qualify: resolve the issue the label names, for example configure retention for the application or bring its replicas back in sync. The next nightly run re-evaluates it.
  • Keep/Qualify: decide per application whether it is worth keeping. Low but steady use by a key department can justify it; a slow decline points towards sunset.
  • Keep/Modernize and Keep/Qualify: continue with Modernization Vector: The Route to Ready to see how each kept application gets ready for the target platform.

...