Project directive template
< The draft notice below is part of the project directive template, and is meant to stay in the actual document head for as long as the project directive exists in draft form, to be removed only when the document is approved by the steering group. >
This is a draft document
It is still incomplete, and very probably still contains numerous factual errors and inconsistencies. In order to avoid confusion, do not disseminate this document either in full nor in part, and do not act upon information contained herein without first checking with the document owner.
< This document is based on a template from Tieto PPS. Text in angular brackets are instructions to the author >
< To create a project directive draft wiki page, create a new page as "<Project name> project directive" on the internal wiki, remove it from the "Template" category and add it to your project category. Keep the above draft notice until the plan is approved by the project steering group, at which point it should be moved to the external wiki. >
< The span below helps if you want to make a .doc or .pdf out of it at some point later. >
NeIC <Area>
<Project name>
Project directive
< The purpose of the project directive is to form the basis for a decision on starting the project (DP1, see annex 1) and to define the boundaries for the preparation phase. >
< .doc page break here >
Background
< Briefly describe the project background, possibly also its history. Also specify if it is an individual project, part of a NeIC strategic area or related to other projects. Describe cooperation with the national e-infrastructure providers. If applicable, also describe interactions with other stakeholders of NeIC; research communities, researchers, etc. >
Project idea
< Describe the project idea in exactly one sentence. Use the phrase ”The project contributes to (measurable strategic goal) by (concrete summary of implementation).”. The project idea should describe the connection between the expected benefit and the project objective by summarizing the purpose of the project and the manner in which the project contributes to it. >
< Example: “This project will contribute to raising impact of Nordic BMS research by 10% by implementing a platform for handling sensitive data”. >
Expected benefit
< Formulate the expected benefit to the national e-infrastructure provider organizations and other stakeholders of NeIC. Describe the Nordic dimension of the project and the added value that NeIC can provide through a successful project. Describe also how the benefit will be measured, if applicable. >
Basis
< List the fundamental documents that form the starting point for the project. For example, a feasibility study. >
Contact persons
< List all persons having knowledge or information and that could/should participate in the preparation phase. Specify whether the person was already contacted, is interested in the project or would be willing to provide more details, or can be considered as official National contact point. Especially, note contacts in the national e-infrastructures. Attach a list of potential stakeholders. >
| Name | Role | |
|---|---|---|
Timeframe and estimates for the preparations
< Enter the dates and estimates for the work up to DP2/DP3 (cf. annex 1). >
| Commitment up to | Date | Estimated effort | Estimated expenditures |
|---|---|---|---|
| DP2 | |||
| DP3 |
Project goals
Result goals
< State the wishes/requirements for the project result where these have been identified. >
Time goals
< Specify the wishes/requirements regarding the point in time for the project deliveries (DP6), for the handover of a delivery (DP7), and for the approval of the final report (DP8), if they have been identified (cf. annex 1). >
Cost goals
< State the wishes/requirements for the total project cost if known. >
Project objective priority
< Define the wishes/requirements regarding the project objective priorities. These should be expressed as decimal numbers whose total sum equals one (=1.0). >
| Result | Time | Cost |
|---|---|---|
| 0. | 0. | 0. |
Financing
< Describe how the project will be financed. The project needs co-financing from at the very least two but preferably four or five Nordic countries in order to be eligible to receive co-financing from NeIC. >
Other
< If the steering group members have been appointed, please list them here. Provide any other possible information that can be of benefit to the work involved in the project. Especially, include any known risks and opportunities. >
< .doc page break here >
Annex 1 – Terminology
1. Decision points
During the life span of the project from startup to termination, a number of formal decisions must be made by the steering group. These fall into eight different types; which are numbered in the chronological order in which they are typically made.
DP1 – Decision point type 1; steering group decision to start the project, based on the project directive.
DP2 – Decision point type 2; steering group decision to continue, change or interrupt the project based on findings during the preparation phase. A project may have multiple DP2.
DP3 – Decision point type 3; steering group decision to approve the project plan developed during the preparation phase. Typically this is tied to a DP4 decision to start the execution phase.
DP4 – Decision point type 4; steering group decision to start the execution phase.
DP5 – Decision point type 5; steering group decision to continue, change or interrupt the project based on findings during the execution phase. A project may have multiple DP5.
DP6 – Decision point type 6; steering group decision to approve the result of a delivery, for example to end users. A project may have multiple DP6.
DP7 – Decision point type 7; steering group decision to transfer the responsibility for a delivery, typically to operations in a receiving organization.
DP8 – Decision point type 8; steering group decision to approve the final report and terminate the project.