RECMGMT-L Archives

Records Management

RECMGMT-L@LISTSERV.IGGURU.US

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Vednere, Ganesh" <[log in to unmask]>
Reply To:
Records Management Program <[log in to unmask]>
Date:
Tue, 26 Aug 2008 09:55:34 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (57 lines)
Vincent wrote ".........what tasks need to be done & other procedures undertaken with branches/departments that are taking part in the EDRMS before the start of the Pilot Project ....."

Listed below are key tasks prior to starting a pilot project (Several of these may have already been done by your team but listing here for reference)

- Evaluate and understand organizational landscape - review business, legal, regulatory, operational, financial factors affecting the company

- Understand current state of document and records management(if any) processes and practices

- Understand business "pain -points" related to doc/records mgmt

- Perform cost/benefits analysis of the project 

- Obtain line of business buy-in (assuming of course that sr. mgmt has already committed to the project)

- Develop high level "vision" of the project - what are the goals, objectives, and success criteria (review what "pain points will be addressed by the EDRMS)

- Develop and document key business requirements for the EDRMS project

- Think about taxonomy, file plans, retention etc.

 - Review file formats, media to be managed etc

- Conduct records management awareness session to ensure branches/departments know what is entailed

- Determine team structures (who from business, tech, legal, RM etc ) will participate

- Determine roles and responsibilities 

- Develop records inventory - series/types, retention periods, detailed file plans (the sequence of this may vary from company to company - depending on your organization this may be done as an early step or even later)

- Evaluate pilot candidates based on factors important to the business

- Determine scope of pilot(s) (identify which requirements will be piloted)

- Determine scanning requirements

- Validate technology development requirements (design, architecture, tool sets, standards, testing scripts etc etc)

- Validate infrastructure requirements (servers, software, loadsets, versions, sizing etc)

- Determine pilot project plans, dates, milestones

- Conduct detailed training session for pilot personnel

- Start Implementing....!

Thanks
Ganesh Vednere 

[log in to unmask]


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]

ATOM RSS1 RSS2