We do almost everything on chartered projects here.  For each project we
write a charter, assign roles, tasks, etc.  For instance, we are working
on a big project to capture drawings at our plants into Documentum.
Some of these will be scanned in from paper, mylar, film etc and some of
them will be brought in electronically from shared network drives.  So
the name of this project became Project management drawing system. 

Now I have several other huge projects that will concentrate on a
particular functional area like environmental.  We will actually be
looking at a total records management overhaul including:  inventory and
retention, mapping requirements document(s), electronic records (where
are they, what format, who sees, what systems feed into others),
establishing a file plan with standard naming conventions, etc. etc.
etc. and eventually ending up probably with both a paper and Documentum
repository.  So we are talking processes all the way.  Now the question
- some of the staff insists that it should be called environmental
electronic records management.  I think that's way too narrow.  You all
know how these kinds of things can get hung up on "what you said it
was".  

BTW, the project charters are a bit loose so some of this is spelled out
but there's not much detail.  

Any thoughts? 



List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance