Dear colleagues,
We can proceed with the work on the periodic report. The original time plan of TID envisioned a DELIVERY of the final report by the end of this week (Friday, 31.05.2013) and there are your inputs pending.
I took everything that needs to be done in one email - please excuse that this is a bit long. :)
ð Please provide and prepare the rational paragraph in relation to your partner contribution and according to the latest numbers if possible for Wednesday (29.05.2013)
ð Please provide the relevant paragraph to Markus and me in response to this email (we will integrate it in the final report)
We are still waiting for the integrated version of the overall report from TID - in the meantime we can work on the effort numbers which TID provided to us in advance.
These effort numbers are currently visible to us and we take this as working fundament:
(red is a deviation of > 10%; green is a deviate < 10% Remark: TID provided us with the relevant numbers (see down below) and I created this working table)
M1-M12
M1-M12
M1-M12
M13-M24
M13-M24
M13-M24
M1-M24
M1-M24
M1-M24
planned
worked
deviation
planned
worked
deviation
planned
worked
deviation
TID
15
14,2
95%
24,00
25,42
106%
39,00
39,62
101,59%
SAP
33,75
49,04
145%
54,00
45,61
84%
87,75
94,65
107,86%
THALES
2,5
2,45
98%
4,00
3,84
96%
6,50
6,29
96,77%
TI
5
5,2
104%
8,00
7,13
89%
13,00
12,33
94,85%
DT
7,5
9,23
123%
12,00
10,10
84%
19,50
19,33
99,13%
EAB
14,55
20,58
141%
17,45
11,40
65%
32,00
31,98
99,94%
ATOS
7,5
8,7
116%
12,00
15,94
133%
19,50
24,64
126,36%
E-IIS
2,5
4,87
195%
4,00
3,50
88%
6,50
8,37
128,77%
UPM
12
4,3
36%
19,20
30,55
159%
31,20
34,85
111,70%
UDE
1,5
3,94
263%
2,40
2,02
84%
3,90
5,96
152,82%
iMinds
0
0
14,89
11,46
77%
14,89
11,46
76,96%
Given these efforts we can work on finalizing the relevant sections (which were foreseen in the initial report already provided).
Section 1. "Partners whose effort is significantly lower compared with the planning are the following"
Section 2. "Partners whose effort is significantly higher compared with the planning are the following"
Section 3. "In summary, the status of this WP3 regarding consumption of resources is ...."
(An evaluation is required) => draft of SAP see below, please approve
Section 4. "In general, the consumption of resources in this WP3 "
(An evaluation is required) => draft of SAP see below, please approve
Task 1. We expect final and updated input from the following partners (as the numbers that we can see are either 10% above or 10% below schedule for the M13-M24 reporting period). Although we are in general reporting on the M13-M24 report it is still encourage to comment on the overall efforts if significant over/underspending happened or was resolved. Please write as well by "when" your company plans to resolve this. If you updated your numbers within the last days, please provide the final rationale to us and elaborate if we should integrate it as over- or underspending!)
Section 1. "Partners whose effort is significantly lower compared with the planning are the following"
§ SAP - no text initially submitted
§ TI - no text initially submitted
§ DT - no text initially submitted
§ EAB - no text initially submitted
§ E-IIS - please touch as well why your overall effort is 128,77% over planned spending, giving an outlook if this will be resolved and until when
· Initial text already provided, see below - please recheck if this still does match your intension & our comments below
§ iMinds - please touch as well why your overall effort is 76,96% under planned spending, giving an outlook if this will be resolved and until when
· Initial text already provided, see below - please recheck if this still does match your intension & our comments below
§ UDE - please touch as well why your overall effort is 152,82% over planned spending, giving an outlook if this will be resolved and until when
Section 2. Partners whose effort is significantly higher compared with the planning are the following
§ ATOS - please touch as well why your overall effort is 126,26% over planned spending, giving an outlook if this will be resolved and until when
· Initial text already provided, see below - please recheck if this still does match your intension & our comments below
§ UPM - please touch as well why your overall effort is 111,70% over planned spending, giving an outlook if this will be resolved and until when
· Initial text already provided, see below - please recheck if this still does match your intension & our comments below
Current input provided by E-IIs, iMinds, ATOS, UPM and relevant comments:
Section 1. "Partners whose effort is significantly lower compared with the planning are the following"
· "E-IIS the reason is the increase of engagement in the period to attempt to introduce the existence and universal quantifiers in the initial model that revealed a number of drawback and implications not manageable with the effort allocated."
o Comment WPL: Rational seems to be misplaced as the numbers are actually lower for the current period but only higher for the overall reporting period. Please make this explicit
· "EAB's figures (PM consumption) are significantly lower than the estimations. This is due to a resource shift from EAB to UPM, which is explained in the UPM section. EAB was not able to contribute to this periodic report. The statements of EAB given in this periodic report reflect the status as of the M13-M18 periodic report"
o Comment WPL: Please contribute to the periodic report and then update the statement
Section 2. Partners whose effort is significantly higher compared with the planning are the following
§ UPM's figures (PM consumption) exceed the estimations due to the following reasons:
· After EAB left T3.3 at the end of the 1st periodic report, UPM, SAP and Telefónica I+D agreed that UPM will take over the development of the Store GE and the leadership of T3.1. This agreement has been included in the 4th amendment and its approval is pending at the moment of writing this report, and thus it is not reflected in the planning. In the context of this agreement, UPM has performed the above mentioned tasks during the M13-M24 period.
· This effect is also considered in the current DoW amendment 4 according to which UPM efforts are fully along the plan.
· Comment WPL: UPM, please comment on the general overspending of 111,70%
§ ATOS: As we have mentioned, a key team member working on Fiware and specifically in WP3 left the company at the beginning of September 2012 and in order to replace him a new person begun in the project during November 2012. This change affected directly ATOS' performance in this workpackage and its related tasks. Because of this, ATOS reduced effort working for a couple of months (during September and October 2012). However, a new member, without previous knowledge about the project and ist nature and specifications, was incorporated at the end of 2012. Therefore, it required an extra-effort to finish the remaining task and to perform the knowledge transfer to the new member. Specifically, two people instead of one were involved in the project in order to perform the required tasks and at the same time provide the specific training to the new team member. The increase in efforts reported specifically in November, January and March is a consequence of this situation.
· Comment WPL: ATOS: This might be seen as a week excuse by the reviewers, if possible please improve the rational given, especially as you seem to overbook 126% overall.
Task 2. @ALL PARTNERS: For section 3 and 4 we prepared the following summary statements for the complete work package - please veto if you are not aligned with the statements:
Section 1.
Section 2.
Section 3. "In summary, the status of this WP3 regarding consumption of resources is ...."
§ ... in general in line with the plan, given the cruise speed approach. The overspending introduced in the first project year has significantly decreased overall. Many partners booked effectively less effort than planned. Although there were decommitments by some partners, other partners stepped up and took over their work efforts and contributions. The DoW amendment v4 reflects the current effort and partner contributions quite well. Detailed deviation for the reporting period M13-M24 are outlined on a partner level down below.
Section 4. "In general, the consumption of resources in this WP3..."
§ ... in general in line with the plan, with roughly 3% underspending in average and over all the partners. As outlined above by the contributing partners, most of the deviation YoY (M1-M24) are foreseen to be resolved within the next reporting period, although currently there is a YoY non-significant overspending of slightly below 10% over all the partners. The current planning for the remaining project indicates that the needed overall efforts will match the projected ones, i.e. the benefit of increased efforts in the early project phase pays of.
APPENDIX: Reference from TID:
[cid:image003.png at 01CE5AE6.466FC0F0]
[cid:image004.png at 01CE5AE6.466FC0F0]
[cid:image005.png at 01CE5AE6.466FC0F0]
From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten
Sent: Mittwoch, 15. Mai 2013 09:26
To: fiware-apps at lists.fi-ware.eu
Subject: [Fiware-apps] periodic report - current status
Dear colleagues,
as said: we will send out the current status and open points one by one for the pending deliverables to make this a bit transparent.
The second one is another "easier" one: periodic report - as we as well invested into this to prepare this thoroughly.
Find below the reference to our submission. I got more input from E-IIS on their part which will be part of the final version - did all of you take a second look on our submission or want to change something?
Status: submitted to TID for integration with the other chapters
Next steps: TID resending it to us, we will distribute and make a second round asking for partner contributions and your deltas. SAP will introduce final statements touching on the overall resource consumption (section at the bottom). Then: submission
Given the time frame of Javier, there seems to be another schedule & the delivery is not planned for Friday, this week.
Best,
/Thorsten
From: Sandfuchs, Thorsten
Sent: Freitag, 10. Mai 2013 15:04
To: 'JAVIER DE PEDRO SANCHEZ'; 'subsidies at tid.es'
Cc: fiware-apps at lists.fi-ware.eu<mailto:fiware-apps at lists.fi-ware.eu>; 'Heller, Markus'
Subject: SUBMISSION - WP3 - RE: FI-WARE: Periodic Report - M13 - M24
Dear javier,
Find the periodic report out of the WP3 for consolidation with other chapters, attached. Sorry for the late submission
Please send the integrated version back to us in order to have an internal review prior to submission and in order to allow us to integrate the final evaluations. The submitted document does not contain some rationals given by the partners, as the numbers were not final so far.
We are still missing (although pushing hard) the input from some partners, this will be integrated in the final version, together with the subsuming evaluations.
Best,
/Thorsten
From: fiware-wpa-bounces at lists.fi-ware.eu<mailto:fiware-wpa-bounces at lists.fi-ware.eu> [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of JAVIER DE PEDRO SANCHEZ
Sent: Montag, 15. April 2013 23:07
To: fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>
Cc: subsidies at tid.es<mailto:subsidies at tid.es>
Subject: [Fiware-wpa] FI-WARE: Periodic Report - M13 - M24
Importance: High
Dear all
As you know we have to deliver the Periodic Report which has to give an overview of the second year of the project (months from M13 (May12) to M24 (Apr13)).
I will kindly ask you in another particularized e-mail to update as WPL the information about your WP.
The schedule is the following:
1. First request of information to WPL with estimated effort per partner: April 15th, 2013
2. Period to request each WPL to each involved partner its contribution to WP: April 16th, 2013 - Apr 19th, 2013
3. Integration of received information from by each WPL: April 22nd, 2013 - May 5th, 2013
4. WPL send first version of his updated report to Coordinator (subsidies at tid.es<mailto:subsidies at tid.es>): May 6th, 2013
5. Coordinator asks to each partner to update its current effort: April 30th, 2013
6. Each partner sends its current effort according FORM-C 2: May 1st, 2013 - May 10th, 2013
7. Coordinator sends updated data of effort to each WPL: May 15th, 2013
8. Updating of the second version of each report by each WPL: May 16th, 2013 - May 17th, 2013
9. WPL sends final version of his updated report to Coordinator (subsidies at tid.es<mailto:subsidies at tid.es>): May 17th, 2013
10. Integrating and revision by Coordinator: May 20th, 2013 - May 24th, 2013
11. Coordinator sends the Periodic Report to Project Officer: May 28th, 2013
12. Review: June 10th, 2013
At last but not least, please, I kindly ask you to follow the template in order to have a homogeneous report as a team. In the last review report they said:
[cid:image001.jpg at 01CE5AE1.4FE3E580]
Thank you in advance.
BR
Javier.
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20130527/a537cc49/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 39114 bytes
Desc: image001.jpg
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20130527/a537cc49/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 39519 bytes
Desc: image003.jpg
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20130527/a537cc49/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 37597 bytes
Desc: image005.jpg
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20130527/a537cc49/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 40387 bytes
Desc: image007.jpg
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20130527/a537cc49/attachment-0003.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy