Skip to content

good practice and innovation

about us infoKits Tools & Techniques Publications Events

You are here: Home » infoKits » Electronic Documents and Records Management » Stage 1: Positioning EDRM » Step-2

EDRM System Implementation Toolkit

- How to Use this Toolkit

Stage 1: Positioning

- Historical Background

- Paper Records

- Word Processing

- Records Management Software

- Office Software

- Document Image Processing

- Electronic Document Management

- Content Management

- Web Content Management

- Electronic Records Management

- Electronic Document & Records Management

- Content Management Suites

- Which Functions

- Electronic Capture

- Analogue/Paper Capture

- Document Image Capture

- Document Image & Unstructured Full Text Capture

- Document Image Capture & Structured Form Processing

- Document Image & Semi-structured Data Capture

- Electronic Document & Content Management

- Elecronic Records Management

- Collaboration/Business Process

- Collaboration

- Workflow/Business Process

- Checklist of Functions

- EDRMs & Relational Databases

- Systems & IT Infrastructure

- Business Process

- Collaboration/Knowledge

- Deliverables for stage

- Resources for stage

- Tools for stage

- FAQs for stage

- Hints & Tips for stage

Stage 2: Project management

Stage 3: Information gathering and analysis

Stage 4: Feasibility study and options review

Stage 5: Making the business case

Stage 6: Defining the statement of requirements

Stage 7: Procuring the solution

Stage 8: Managing the implementation

Stage 9: Measuring the results

Stage 10: Project closure and solution support

Step Two - where does EDRM fit?

Step two is designed to show where an EDRM system or an ECM suite fits within your wider IT infrastructure. For simplicity we shall use the term EDRM to mean all the varieties of document/content and records management system described above.

As this toolkit is aimed at both non-technical records managers and IT professionals this step will inevitably represent a compromise that may seem very basic to some and too technical to others.

The IT world is a fast changing one and statements that everyone would have agreed with five years ago would now be ridiculed and easily contradicted. Nevertheless we will try and make some definite statements to try and position EDRM as it is mid 2004.

If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)