# MultiXscale sync meeting 2022-10-28 - next meeting, shortly before submission (2/3 Nov) - to be decided via email - TODO - finalising funding agreement - - spending duplicate overhead JSC - we would like to add additional PMs + (partial) compute time costs for JSC, but unclear if project officer (PO) would accept that - no response from PO (on leave) or their replacement - we should make it clear that we reached out, no feedback was received - go forward with adding PMs for JSC, hope it doesn't backfire? - update Gantt chart => todo for NIC - Alan needs updated Gantt chart ASAP - all necessary info is in "Deliverables" tab in "CoE_budget-New.xlsx" - WP7 - tasks are too much extended in time? - missing deliverable for T7.4 - too many deliverables - 41 deliverables currently, which is excessive - would be nice to cut some deliverables - cut D5.4 (intermediate report for T5.4) - does mean we only have one report for T5.4 (M12-M48), total effort 38PMs - Sauro/Carlo are OK with dropping on of the deliverables they introduced - NIC should check if some deliverables can be deleted - see double deliverable in WP8 - remarks to tackle - baseline for used codes - can be added in Table 3, see new column - still missing for LAMMPS => Matej (NIC) - "open science pratices" => TODO Matej - KPIs + target groups => TODO Alan - management of potential risks is not sufficiently clear => TODO Barbara - exploitation plans - Caspar added some stuff on this in T1.2 - can we claim that EESSI will be made available at JSC/BSC? - required for *all* participants, so needs to be a table? - unclear how this relates to exploitation plan (section 2.2) - => Caspar will turn this into a table and ask all partners to fill in their part - Leonardo can be mentioned as target for battery use case - timing of tasks - updated in WPs where needed - need Gantt to get a clear view on this - pilot cases remark - part from Matej is still missing - involvement of each participant in specific tasks is not sufficiently clear - breakdown of partners per WP tasks has been included - expertise not clear - see new table towards the end (section 3.2) - => requires input from all partners! - details on risks - TODO Alan - deliverable WP1 => resolved - involvement in key apps => see expertise table in section 3.2