managing electronic records in governmental bodies - National ...
managing electronic records in governmental bodies - National ...
managing electronic records in governmental bodies - National ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
34<br />
ANNEXURE A: Required <strong>records</strong> management functionality conta<strong>in</strong>ed <strong>in</strong><br />
Integrated Document Management Systems<br />
This Annexure conta<strong>in</strong>s only the <strong>records</strong> management functionality required of an<br />
Integrated Document Management System. Governmental <strong>bodies</strong> should take note<br />
that the technical requirements as well as the <strong>in</strong>tegration with messag<strong>in</strong>g and<br />
calender<strong>in</strong>g applications, imag<strong>in</strong>g and scann<strong>in</strong>g applications, document management<br />
applications, workflow applications, search and retrieval applications and<br />
security applications are critical to the success of the system.<br />
Governmental <strong>bodies</strong> that wish to <strong>in</strong>vite tenders for Integrated Document<br />
Management Systems can use the follow<strong>in</strong>g specification to ensure that the required<br />
<strong>records</strong> management functionality is addressed <strong>in</strong> the tender documentation: Model<br />
Requirements for the Management of <strong>electronic</strong> <strong>records</strong>. Moreq specification that is<br />
available on the website: http://cornwell.co.uk/moreq. This specification covers to<br />
both the US DoD 5015.2 standard and the UK PRO requirements discussed on page<br />
2, and was used jo<strong>in</strong>tly with these standards to compile the requirements set out <strong>in</strong><br />
this Annexure.<br />
The <strong>National</strong> Archives and Records Service requires that Integrated Document<br />
Management Systems should conta<strong>in</strong> the follow<strong>in</strong>g m<strong>in</strong>imum required <strong>records</strong><br />
management functionality:<br />
Storage of <strong>electronic</strong> <strong>records</strong><br />
In the paper-based environment <strong>records</strong> are stored <strong>in</strong> a dedicated, secure<br />
environment. The same should apply to <strong>electronic</strong> <strong>records</strong>. It is not very practical to<br />
store <strong>records</strong> on a LAN file server. Access to the documents on the file server is<br />
dependent on the security features of the host LAN. The protection it gives to the<br />
documents is only as good as the users' application of the security system.<br />
Furthermore, if the <strong>electronic</strong> <strong>records</strong> are stored on the LAN file server, they will<br />
have to compete for space with the system files etc. Electronic documents should at<br />
the very least have the same level of secure fil<strong>in</strong>g space as the paper-based<br />
<strong>records</strong>. A sound reliable repository requires a dedicated, stable, long-term storage<br />
space.<br />
Where should one then store <strong>electronic</strong> <strong>records</strong> The <strong>records</strong> can either be stored <strong>in</strong><br />
network-attached storage devices such as CD/DVD-ROM towers/ jukeboxes, etc. or<br />
<strong>in</strong> separate storage area networks. Whichever method is chosen, the follow<strong>in</strong>g<br />
should be kept <strong>in</strong> m<strong>in</strong>d when construct<strong>in</strong>g a storage system:<br />
- Prevent data loss;<br />
- Offer adequate capacity that can easily be <strong>in</strong>creased as storage needs<br />
grow;<br />
- Provide fast access to data without <strong>in</strong>terruptions;<br />
- Be prepared for equipment failures;<br />
- Use cost-effective technologies.<br />
Manag<strong>in</strong>g <strong>electronic</strong> <strong>records</strong>_Policy Guidel<strong>in</strong>es.doc<br />
First Edition<br />
Version 1.1<br />
April 2003