Difference between revisions of "PROC03 Financial and effort review"
Line 9: | Line 9: | ||
|- | |- | ||
| '''Link''' | | '''Link''' | ||
| <br> | | [https://wiki.egi.eu/wiki/PROC03_Financial_and_effort_review https://wiki.egi.eu/wiki/PROC03_Financial_and_effort_review]<br> | ||
|- | |- | ||
| '''Owner<br>''' | | '''Owner<br>''' | ||
Line 21: | Line 21: | ||
|- | |- | ||
| '''Related document'''<br> | | '''Related document'''<br> | ||
| <br> | | N/A<br> | ||
|} | |} | ||
Line 28: | Line 28: | ||
= Overview = | = Overview = | ||
The | The procedure has been introduced to better coordinate process of requesting changes in the DoA. <br> | ||
'''For Deliverables and Milestones change requests should be sent no later than six months before submission deadline.''' | |||
= Definitions = | = Definitions = | ||
Line 36: | Line 38: | ||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. | ||
= | = Requirements = | ||
Each request needs to be described as follow: | |||
• Scope: deliverable/effort/other | |||
• Motivation | |||
• For deliverables: | |||
o name of deliverable/milestone | |||
o type of change: name/timeline/scope | |||
• Current status in DoA | |||
• New proposed <br> | |||
= Steps = | = Steps = | ||
Line 55: | Line 68: | ||
! Prerequisites, if any | ! Prerequisites, if any | ||
|- valign="top" | |- valign="top" | ||
| 1<br> | |||
| <br> | |||
| Anyone<br> | |||
| Requester send request to WP leader<br> | |||
| <br> | |||
|- valign="top" | |||
| 2<br> | |||
| <br> | |||
| WP leader<br> | |||
| Creates ticket in AMB queue in EGI RT system with prefix [DoA change request] and is writing proposal to WP1 mailing list<br> | |||
| <br> | |||
|- valign="top" | |||
| 3<br> | |||
| <br> | |||
| AMB <br> | |||
| Discussion during the next AMB meeting<br> | |||
| <br> | |||
|- valign="top" | |||
| 4<br> | |||
| <br> | | <br> | ||
| AMB<br> | |||
| Proposes action plan to Technical Coordinator (TC)<br> | |||
| <br> | |||
|- valign="top" | |||
| 5<br> | |||
| <br> | |||
| Technical Coordinator (TC) | |||
| Proposes for approval/rejection or ask for more explanation<br> | |||
| <br> | |||
|- valign="top" | |||
| 6<br> | |||
| <br> | | <br> | ||
| Administrative & Financial Coordinator (AFC) | |||
| Validate proposal or ask for more information | |||
| <br> | |||
|- valign="top" | |||
| 7<br> | |||
| <br> | | <br> | ||
| TC<br> | |||
| If change does not require a change in the DoA, TC submit the proposal to PMB for approbation<br> | |||
| <br> | |||
|- valign="top" | |||
| 8<br> | |||
| <br> | | <br> | ||
| TC<br> | |||
| If change requires a change in the DoA, AFC submit the proposal to CB for approbation<br> | |||
| <br> | | <br> | ||
|- valign="top" | |||
| 9 | |||
| | |||
| PMB or CB | |||
| Approval or rejection | |||
| | |||
|- valign="top" | |||
| 10<br> | |||
| <br> | |||
| <br> | |||
| Once approved by the appropriate body (PMB or CB)<br> | |||
| <br> | |||
|- valign="top" | |||
| <br> | |||
| 1<br> | |||
| TC<br> | |||
| Mail EC Office for approval <br> | |||
| approved by CB or PMB<br> | |||
|- valign="top" | |||
| <br> | |||
| 2<br> | |||
| Project office (PO) and QM<br> | |||
| Submit a formal amendment request to the EC and the QM update related documentation, PO add information in changelog for the amendment <br> | |||
| approved by CB<br> | |||
|} | |} | ||
Revision as of 10:51, 31 May 2016
Title | Financial and effort review |
Link | https://wiki.egi.eu/wiki/PROC03_Financial_and_effort_review |
Owner |
Quality Manager |
Status | Approved |
Approval date | |
Related document |
N/A |
Overview
The procedure has been introduced to better coordinate process of requesting changes in the DoA.
For Deliverables and Milestones change requests should be sent no later than six months before submission deadline.
Definitions
Please refer to the EGI Glossary for the definitions of the terms used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Requirements
Each request needs to be described as follow:
• Scope: deliverable/effort/other
• Motivation
• For deliverables:
o name of deliverable/milestone
o type of change: name/timeline/scope
• Current status in DoA
• New proposed
Steps
The following table describes
Step# | Responsible | Action | Prerequisites, if any | |
---|---|---|---|---|
1 |
Anyone |
Requester send request to WP leader |
||
2 |
WP leader |
Creates ticket in AMB queue in EGI RT system with prefix [DoA change request] and is writing proposal to WP1 mailing list |
||
3 |
AMB |
Discussion during the next AMB meeting |
||
4 |
AMB |
Proposes action plan to Technical Coordinator (TC) |
||
5 |
Technical Coordinator (TC) | Proposes for approval/rejection or ask for more explanation |
||
6 |
Administrative & Financial Coordinator (AFC) | Validate proposal or ask for more information | ||
7 |
TC |
If change does not require a change in the DoA, TC submit the proposal to PMB for approbation |
||
8 |
TC |
If change requires a change in the DoA, AFC submit the proposal to CB for approbation |
||
9 | PMB or CB | Approval or rejection | ||
10 |
Once approved by the appropriate body (PMB or CB) |
|||
1 |
TC |
Mail EC Office for approval |
approved by CB or PMB | |
2 |
Project office (PO) and QM |
Submit a formal amendment request to the EC and the QM update related documentation, PO add information in changelog for the amendment |
approved by CB |
Revision History
Version | Authors | Date | Comments |
---|---|---|---|