Dear all, The first SynchroniCity Grant Preparation call wil be: Tuesday, August 9, 11:30 CEST (Brussels time). The preliminary agenda is: 1. Overall status on the process, evaluation, issues (Martin, AU) 2. Input from WP leads 3. Discussion 4. Next meeting 5. AOB Please note that there are admin tasks already pending: PIC codes to be checked, LEARs to be appointed, red crosses to be chased in the system. You will be notified, through this channel, soon, and before the call. You'll find the online call login details below. Best, Martin === 1. Please join my meeting. https://global.gotomeeting.com/join/413566277 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Denmark: +45 69 91 84 58 Australia: +61 2 8355 1034 Austria: +43 7 2088 0716 Belgium: +32 (0) 28 93 7002 Canada: +1 (647) 497-9372 Finland: +358 (0) 923 17 0556 France: +33 (0) 170 950 590 Germany: +49 (0) 692 5736 7206 Ireland: +353 (0) 19 030 053 Italy: +39 0 699 26 68 65 Netherlands: +31 (0) 208 080 759 New Zealand: +64 9 974 9579 Norway: +47 21 04 30 59 Spain: +34 931 76 1534 Sweden: +46 (0) 852 500 691 Switzerland: +41 (0) 435 0026 89 United Kingdom: +44 (0) 20 3713 5011 United States: +1 (571) 317-3116 Access Code: 413-566-277 Audio PIN: Shown after joining the meeting Meeting ID: 413-566-277 === > On 29. jul. 2016, at 19.38, Martin Brynskov <brynskov at cavi.au.dk> wrote: > > Dear all, > > As promised, here's a short practical follow-up to yesterday's email, kicking off the grant preparation phase of SynchroniCity. > > First, please indicate your availability for the first call in the period August 9 to 11 here: > https://doodle.com/poll/vepqb35ep5h8ahn7 > > Deadline: Tuesday August 2 EOB (End of Business, i.e. usually 6 pm). > > Since we are so many, we need a good and clear naming practice in such instances, so register with your name + partner name. You may use the full or short partner name. > > Second, please fill in the following spreadsheet: Mailing Lists and Committees > https://docs.google.com/spreadsheets/d/16KakXlmSKWmHCMqsfBbyAefsx1FH0aoLuBfodLjciDk/edit#gid=0 > > The FIRST TAB concerns contact information for all related persons. Also indicate which email lists each of them should receive. This is especially relevant for legal and admin people in this grant preparation phase. > > In the SECOND TAB, you should indicate the name(s) of your representative(s) in the Project Steering Committee (PSC) and Technical Steering Committee (TSC, i.e. Work Package Leads). Some roles are yet to be filled, when we start properly. > > Thirdly, concerning suggested improvements and edits to the Description of Action, please compile a document with your suggested improvements, dividing them into "Substantial" (e.g. timing, task descriptions and budget/effort tweaking) and "Clerical" (anything not impacting the actual work; do not include simple proof-reading). > > Please note that there is no negotiation phase, and the budget and effort allocation stand as submitted. So any suggested budget must happen within a partner, or with prior agreement within a Reference Zone. > > The first draft version of this document, one per partner, containing all "Substantial" issues to be raised, should be ready by the first call for you to present and subsequently submit in an updated version to the coordinator. Stick with a simple bullet list format, and keep it short and crisp (no more than 1 page). The call should be used to vet redundant issues. > > I attach the proposal Technical Annex Section 1-3 for your convenience. All the documents are online in the repository: > https://drive.google.com/drive/folders/0Byvp-hC42m3gbjVIb1hfODItQm8 > > Lastly, regarding communications, I would like to keep external communication to a minimum before we have signed the Grant Agreement. Please check with me if in doubt. This, however, does not mean that you cannot inform internally in your organization, and feel free to vet the apetite of audiences in presentations you make. > > To that effect, I attach a simple slide overview (4 slides, in PDF), which you may use in presentations. The most important thing to keep in mind is that the project is UNDER GRANT PREPARATION; it has not yet been awarded. So don't jinx it. The Commission doesn't take misinformation lightly. There will be plenty of opportunity to brag and shout later. We will create a structured communication strategy as part of the first phase. That will include creating a proper visual identity, webspace, social media channels etc. It'll all come. We've just begun. > > If you have any questions regarding the process, feel free to get back to us. I'll announce the call early next week. > > Have a great weekend! > > Best, > Martin > >> On 29. jul. 2016, at 02.20, Martin Brynskov <brynskov at cavi.au.dk> wrote: >> >> Dear all, >> >> Today, Thursday, we received the formal message from the European Commission that our SynchroniCity IoT LSP project proposal has been successfully evaluated and invited to start "grant preparation". In short: We won. Congratulations, all. The efforts paid off. >> >> Now the real work begins. :) >> >> This message is to briefly inform you of the evaluation results and the next steps. >> >> There are some crucial actions which need to be taken in the coming days and weeks, so please read both the email and the attached documents thoroughly. Failure to meet the deadlines may lead to rejection of a partner or the entire proposal. So don't take it lightly. SynchroniCity is a complex beast; the wheels must turn smoothly. >> >> An invitation to start grant preparation is not a final acceptance. That happens when the grant is signed, and that has to happen within 3 months from today. The attached "Invitation letter" from the Head of the IoT unit, Mechthild Rohen, describes the steps. >> >> Before the grant can be signed, there are two formal milestones: >> 1. Submission of grant data & annexes: 6 weeks after receiving the letter. This gives us the opportunity to improve the Description of Action (DoA, our proposal and work plan), within the limits of the original proposal and the call text, and the obligation to fix gaps. I'll return to that. >> >> 2. Signature of the declaration of honour (DoH): 9 weeks after receiving the letter. This is the electronic signature by each partner that they are intending to move forward with the project as planned. >> >> As you are most likely aware, the Grant Agreement is between the Commission and the Coordinator (Aarhus University). So in addition, all partners must agree upon and sign a Consortium Agreement. The timing is such that the Consortium Agreement must usually be signed before the Grant Agreement, to ensure a firm legal foundation for the project. >> >> This all means that we must work quickly to move through the steps in a timely manner. >> >> SynchroniCity is part of the IoT Large Scale Pilots (LSPs), which consists of 5 LSPs. Furthermore, to coordinate across and support all 5 LSPs, there are 2 Coordination and Support Actions (CSAs), one technical and one focusing on co-creation. This means that some timing is foreseen to be synchronized :) with the entire IoT LSP project portfolio, including the kickoff month. >> >> We need more details and guidance from the Commission on this, but as for now, starting the project before January 2017 does not seem likely, given the complexity and syncing with the other projects. But we'll have to wait and see. >> >> As far as I have heard, the other LSPs and CSAs have SynchroniCity consortium partners and/or affiliates quite well represented. This should bode well for collaboration and synergies. >> >> As for the concrete project content, we got some brief feedback from the evaluation. I attach the Evaluation Summary Report (ESR). We got an overall score of 13,5 (5 for excellence, 4.5 for impact and 4 for implementation, with 5 being max), so quite OK -- and in any case the highest among the competition. >> >> The main concern raised in the ESR is the duration. The evaluators are skeptical that 27 months is enough, especially to allow for co-creation. We will have to discuss this as one of the main points when we propose improvements to the DoA. The rest is relatively minor stuff, mainly asking for greater detail in task descriptions and exploitation plans. >> >> So far, so good. >> >> In order to move the process forward, you will receive tomorrow, Friday, a follow-up email. It will ask you to provide updated information on your team and communication preferences, including your availability for a preparatory call in the date range August 9-11 (Tuesday-Thursday). There will be separate mailing lists for project content, admin and legal stuff. >> >> July is vacation time in Northern Europe, and August is marking the main vacation time in Southern countries and elsewhere, so I understand that some teams aren't fully operational. However, it is crucially important that you join the conversation in the coming weeks, since we will have a process where we will take non-trivial decisions, e.g. regarding project duration. >> >> We will make sure the process is run as well-prepared, documented and smoothly as possible, but it will be impossible to accomodate last minute requests. >> >> Also, we do have experience from similar processes, including the legal side of things, and this experience tells us that many issues will be resolved swiftly and constructively, while we still need to allow time to sort out whatever outstanding issues. I therefore encourage you to activate your admin and legal teams immediately so that we can start working right away and be upfront about any preferences. I'm confident that we will find the right balances. >> >> Your first task is to go through the proposal again, and note suggestions for improvements. We will set up a structured process to collect and assess them. There are some clerical erros that our internal checks have already found, but we have all become wiser since we put in the proposal in April, so let's see what comes up. >> >> That is all for now. >> >> I'm sorry for the late notice -- I spent the day, virtually, alas, in Brazil where our Portuguese colleagues in the SynchroniCity consortium are hosting the Beyond 2020 Conference. And while a colleague was there physically representing OASC, I did have the opportunity to say a few words to the audience, including breaking the good news the SynchroniCity is coming. >> >> It felt really good. I'm looking so much forward to working with you on this. Thanks for all your efforts, and faith, in our fruitful collaboration. >> >> Best, >> Martin >> >> -- >> Martin Brynskov, Ph.D. >> Associate professor, interaction technologies >> Aarhus University >> >> Chair, Open & Agile Smart Cities // oascities.org >> Research director, AU Smart Cities // smartcities.au.dk >> Director, Digital Design Lab // ddlab.dk >> Participatory IT Centre // Digital Urban Living // CAVI >> Tel. (+45) 3068 0424 >> More info: http://au.dk/en/brynskov@cavi >> <Invitation Letter including the information out of ranking-2.pdf><732240-SynchroniCity-Evaluation Summary Report.pdf>_______________________________________________ >> Fiware-oasc-iot-lsp-cities mailing list >> Fiware-oasc-iot-lsp-cities at lists.fiware.org >> https://lists.fiware.org/listinfo/fiware-oasc-iot-lsp-cities > > -- > Martin Brynskov, Ph.D. > Associate professor, interaction technologies > Aarhus University > > Chair, Open & Agile Smart Cities // oascities.org > Research director, AU Smart Cities // smartcities.au.dk > Director, Digital Design Lab // ddlab.dk > Participatory IT Centre // Digital Urban Living // CAVI > Tel. (+45) 3068 0424 > More info: http://au.dk/en/brynskov@cavi > <SynchroniCity-overview.pdf><SynchroniCity-Section-1-3-FINAL.pdf> -- Martin Brynskov, Ph.D. Associate professor, interaction technologies Aarhus University Chair, Open & Agile Smart Cities // oascities.org Research director, AU Smart Cities // smartcities.au.dk Director, Digital Design Lab // ddlab.dk Participatory IT Centre // Digital Urban Living // CAVI Tel. (+45) 3068 0424 More info: http://au.dk/en/brynskov@cavi
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy