A couple slightly different models...
At the last employer, RIM was the last step in the decom process. We had
responsibility to check / validate legal holds, then ensure that the IT
team had a plan for the data. It was part of a ServiceNow process and they
needed to indicate if the data was being transferred in whole to a new
system, was being purged in accord with the retention schedule, or was
being archived in accord with the retention schedule. The net was that the
system couldn't be shut down until they passed this checkpoint.
Current employer is also involved in the decom process. In this case, RIM
owns the data archiving solution, so again, pretty much the last stop in
the process. This ensures that data is retained (and disposed of) in accord
with the retention schedule. This can be a challenge because owning the
archiving solution means operating an IT service, with the costs for
storage, hardware, and software. RIM also needs to be in close connection
with IT to ensure that storage needs (and general capacity needs) can be
met. It's easy to become the bottleneck if a large number of applications
are due for decom during a particular year -- and then RIM becomes a focal
point for causing IT to miss cost savings targets.
There should be overarching decommissioning process steps documented by IT,
particularly including instructions on what needs to be archived in order
to be able to utilize the archived data. I've seen situations where the
data gets archived, but there's no way to actually read the data because it
is dependent on an application or database. In certain instances, licensing
of an application or database may prevent the archiving of the application
or database, so determining how the data can be accessed if needed is a
critical step.
Patrick Cunningham, CISM, FAI
List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]
|
