Well this is not an IT project since IT do not manage records. To support an
ERMS acquisition there are no 'extra' skills required of an IT person: the
IT person needs to be capable of doing what all IT people should always be
able to do, namely
1) *identify, (and help the records manager document) all current ESI in the
organization*: where it is, how it is stored throughout its lifecycle
including migration routines, and what the ESI is (not its intellectual
content since that is the business owner's responsibility, but where the
data comes from eg. what application). This is called 'data mapping' and is
a requirement of new (and old) Federal Rules of Civil Procedure (ediscovery
rules). If the IT department is mismanaged and doesn't identify IT support
roles, then you'll never be able to scope the project (eg. what should be
captured into the ERMS to begin with).
2) *implement a piece of software like an ERMS:* assess hardware needs,
test the software, install it company-wide, troubleshoot, log issues,
problems, changes etc. The IT person would need to have, and
follow directions from, the ERMS project team who determines the policies
(or 'business rules') that in turn drive ERMS programming/defaults/custom
coding.
The records manager needs to steer this ship, not IT. A starting point to
explain to IT what is needed of IT could be the UK government's
functional requirements for an ERMS (although that document is not an 'IT'
document).
Maureen Cusack
San Francisco
On Mon, Jun 1, 2009 at 10:04 AM, Vandenberg, Erin <[log in to unmask]>wrote:
> I have several years of experience dealing with paper and microfilm
> records management, but I admit I am lacking in experience dealing with
> managing electronic records. I've tossed out the idea of an ERMS to
> several university administrators and some seem receptive to the idea.
> The head of our IT department has asked me to provide him a list of
> skills I would like to see in whichever IT staff person or persons he
> assigns to this project. And this is where I'm stumped. I'm not even
> really sure *I* have the requisite skills to develop such a project so
> I'm unsure how to go about making a list of skills or experience for the
> IT department.
>
> So, listserv, I turn to you:
>
> What would be your dream skill set for any IT staff assigned to help you
> research and possibly implement an ERMS? Or is the answer "it depends"?
> Should I just say we need to hire a consultant and be done with it? Or
> did I just offend everyone and open a huge can of worms?
>
> Erin Vandenberg
> Director of Records Management
> Office of the Secretary
> DePaul University
> 55 E Jackson, Suite 850
> Chicago, IL 60604
> 312-362-7941
> [log in to unmask]
> http://rm.depaul.edu
>
> 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]
>
--
Maureen,
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]
|
