09.11.2012 Views

Implementing an EDRMS – Lessons from agencies

Implementing an EDRMS – Lessons from agencies

Implementing an EDRMS – Lessons from agencies

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

National Archives of Australia <strong>Implementing</strong> <strong>an</strong> <strong>EDRMS</strong>: Ten <strong>Lessons</strong><br />

LESSON 6 INVEST IN GETTING YOUR AGENCY’S INFORMATION<br />

MANAGEMENT RIGHT<br />

6.1 In successful implementations, the <strong>EDRMS</strong> was viewed as <strong>an</strong> enabler for improved<br />

information m<strong>an</strong>agement, not the solution itself.<br />

6.2 Some <strong>agencies</strong> found that introducing a new file pl<strong>an</strong> or records classification scheme<br />

during <strong>an</strong> <strong>EDRMS</strong> implementation was too much ch<strong>an</strong>ge at once. Others found it was<br />

useful to introduce a titling scheme on their shared drives in adv<strong>an</strong>ce. Staff therefore<br />

became familiar with how to title records before the <strong>EDRMS</strong> was rolled out. This<br />

helped to resolve <strong>an</strong>y issues with the new file pl<strong>an</strong>, <strong>an</strong>d reduced the risks to the<br />

successful adoption of the <strong>EDRMS</strong>.<br />

6.3 Depending on configuration decisions <strong>an</strong>d previous records m<strong>an</strong>agement practices,<br />

end users were sometimes required to assume more responsibility for m<strong>an</strong>aging their<br />

own records (for example, creating <strong>an</strong>d naming electronic files). Some <strong>agencies</strong><br />

acknowledged that they did not invest enough time in developing business rules <strong>an</strong>d<br />

training staff in their basic records m<strong>an</strong>agement responsibilities.<br />

10

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!