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 6: EDRM - defining the statement of requirements

Stage 6: Defining the statement of requirements

Reason for stage

This stage is designed to help the project team to plan and produce the statement of requirements for the preferred EDRM solution. This will form part of the Invitation To Tender document that you will need to send out to shortlisted suppliers. The procedures will vary depending on the procurement approach adopted as outlined in stage two, step two of the toolkit. For this stage and stage seven it is assumed that the procurement will be via the OJEC restricted procurement fixed price procedure.

Definition of stage

Stage six takes you through the process of compiling a Statement of Requirements for an EDRM solution. It is based on a model six-part document and steps one to six indicate what you should cover in each section of the document.

  • Step one - the Invitation To Tender section.

  • Step two - the background to the requirements section

  • Step three - the functional requirements section.

  • Step four - the technical requirements section.

  • Step five - the service requirements section.

  • Step six - the price schedule section.

Compilation of Stages 1-5 to create Statement of requirements

Objectives of stage

After reading this stage the EDRM project team should be clear on all the areas that need to be covered in a detailed statement of requirements and of all the work that they need to have completed by then in order to clearly define those requirements.

This stage takes you through the process of defining your detailed requirements for the solution. Following a standard template this stage shows you how to define your high level requirements for a new system, your business objectives and then the detailed functional and technical requirements for a system and the services you require to be covered by the contract. The details of the requirement are impacted by the choice of procurement approach and this is outlined in this stage.


Bookmark and Share
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 ;)