* Monthly reporting
-monthly log/diary of GridTalk activities
-granularity up to DD
-should have enough information to produce monthly timesheet, monthly internal report to IT mgmt, quarterly EC periodic report
-indicate task number, % of effort (or num of days, or num of hours)
-indicate personal holidays during the month
-indicate official trips, and link to trip report
-For reference: 
Apr reports http://indico.cern.ch/conferenceDisplay.py?confId=31651
May reports http://indico.cern.ch/conferenceDisplay.py?confId=33557
June reports should appear here http://indico.cern.ch/conferenceDisplay.py?confId=35250

* CERN Deliverables
-Workflow: DD->FH,FE->SP->PMB
-Suggest to SP: D3.1 internal deadline for PMB approval 6th of every month; to reach EC 10th of every month
-We need to check with SP, EC if this is acceptble
-For exceptional cases CERN cannot meet the deadline, DD to inform FE,FH asap to work out solution
-DFS or EDMS for storage

* CERN contribution to quarterly EC reports
- Input taken from Monthly reporting
- Either DD or FE, depends on level of detail required by SP

* Trip
- See procedure http://indico.cern.ch/getFile.py/access?resId=0&materialId=0&confId=35669

* Monthly timesheets
-FE will complete DD's monthly timesheet from now on, input taken from Monthly indico reporting
-DD to send to FE the May timesheet

* iSGTW monthly reports
- DD will check with BJ if monthly D3.1 is sufficient, as presently it is largely similar