dear clara, Regarding the contract signature, are you going to send a CA model before > project starting? > i'm working on that > Can you please also to send the final document of the project description? > I cannot find it in the ECAS system > indeed the new system, which name by the way is sygma and not any longer ecas, is a bit tortuose but the information are there. i'm writing this short guide so that everybody can find by himself/herself the docs (in addition they are a bit big for sharing via email). step 1: acces the system via http://ec.europa.eu/research/participants/portal/desktop/en/home.html step 2: login with your acces id (normally your email) and pwd step 3: select "my project(s)" step 4: select fi-next. at this stage the system normally opens a new instance of your browser step 5: select "latest legal docs" in the left blu colum. at this stage the system normally opens a new instance of your browser step 6: select "documents" in the lower bar of the title bar. this is a dark grey bar and "documents" is written in white, below the one with big icons which you see all greyed as they are not available for editing at this stage (not even for me). step 7: here you are! you have a list of all the available docs. Regarding the KOM, could you detail the agenda for three slots you > propose? Depend on the topic I need to allocate right person of the team. > here i'm reporting what i wrote which now i detail more although i thougth self-explanatory enough 1. formal opening and discussion on the role and main goals of the various wps here i'd like to create and reach a common understanding on what the project is about and how to get its planned achievements. so here we have to discuss the various wps (10 min presentation by the wp leaders) and discussing eventual open points. at the moment i see at least two main ones: 1.1 clear undestanding on fiware lab and in particular to t4.3 and the deliverable we did add on fiware la sustainability 1.2 in the proposal support to the fiware catalogue and fiware academy have been forgotten. we have to agree how to tackle these to critically important fiware tools, as there are important questions to solve, such as: 1.2.0 do we need and want them? 1.2.1 who will host them? 1.2.2 who will manage their operations? 1.2.3 who will manage their evolution if any? 1.2.4 who will guarantee the quality of their content? 1.2.5 .... of course each answer to the above (migth)requires redefinition in the doa (e.g. who, what, how, budget allocated) 2. debriefing of the first day having started with the above i'd liek here people reporting on their attendance to the sessions of 13 dec. as i said the doa cearly stated who HAS to attend where, so i do expect people attending to the various sessions as they are already project activities! this is importnat as we have to have the pulse of the community in order to take actions and perform work 3. detailed plan for the first six months. this is i gues clear, isn't it? however, as i said in my previous emails, i'm far then happy to receive your comments and suggestions about the agenda. till today no news about ec signature. however, i think the probability the ec not signs within november low (anyhow greater then 0 ...). ciao, stefano > > Thanks > > > > Clara Pezuela > > Head of IT Market > > Research and Innovation Group > > ARI website <https://atos.net/en/insights-and-innovation/innovation-labs> > > Atos Spain SA > > Clara.pezuela at atos.net > > +34 675 62 9974 > > > > [image: Atos_Olympic_Games_Logo_signature] > > > > > > *From:* fiware-sustainability-proposal-bounces at lists.fiware.org [mailto: > fiware-sustainability-proposal-bounces at lists.fiware.org] *On Behalf Of *stefano > de panfilis > *Sent:* Monday, November 21, 2016 1:59 PM > *To:* Murphy Seán (murp); Fiware-sustainability-proposal at lists.fiware.org; > Piero Corte; Paolo Fabriani; Laura Pucci; Carmen Mac Williams; Muryshkin, > Peter > *Cc:* Wandekoken Grazioli Bruno Gaetano (gaea) > *Subject:* Re: [Fiware-sustainability-proposal] clarification regarding > KOM > > > > dear all, > > > > i take the opportunity of this email from sean to tell you all, that due > to organisational issues the kow will be set in two two tranches as foolows: > > > > 1: 08:30-10:00 14 dec (before the formal opening of the conference) > > 2: 17:30-18:30 14 dec (in parallel with ihubs session) > > 3: 09:30-12:00 15 dec. > > > > in addition all have to attend to the various fiware community sessions on > 13 dec according to their role in fi-next and interests > > indeed, as i said in other emails, our role is to is to smoothly manage > the fiware community and having it growing in a sustainable way more and > more. so in fact our work is to be embeded in the community. > > > > so our kow per session will be: > > 1. formal opening and discussion on the role and main goals of the various > wps > > 2. debriefing of the first day > > 3. detailed plan for the first six months. > > > > happy to receive your comments and suggestions. > > > > of course all the above will be cancelled if the ec will not sign the > contract within 30 novemebre 2016. for you to know engineering has already > signed the contract as coordinator. > > > > ciao, > > stefano > > > > 2016-11-21 9:53 GMT+01:00 Murphy Seán (murp) <murp at zhaw.ch>: > > Hi Stefano, > > Regarding KOM: as I understand we are currently agreed on a slot > on Dec 13 from 1400. The slot on Dec 15 morn is still tentative > afaik - when will a decision be made regarding this? > > It would be good to know before booking flights etc. > > BR, > Seán. > _______________________________________________ > Fiware-sustainability-proposal mailing list > Fiware-sustainability-proposal at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-sustainability-proposal > > > > > > -- > > Stefano De Panfilis > Chief Innovation Officer > Engineering Ingegneria Informatica S.p.A. > via Riccardo Morandi 32 > 00148 Roma > Italy > > tel (direct): +39-06-8759-4253 > tel (secr.): +39-068307-4513 > fax: +39-068307-4200 > cell: +39-335-7542-567 > > skype: depa01 > > twitter: @depa01 > > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. > As its integrity cannot be secured on the Internet, the Atos group > liability cannot be triggered for the message content. Although the sender > endeavors to maintain a computer virus-free network, the sender does not > warrant that this transmission is virus-free and will not be liable for any > damages resulting from any virus transmitted. > > Este mensaje y los ficheros adjuntos pueden contener información > confidencial destinada solamente a la(s) persona(s) mencionadas > anteriormente y pueden estar protegidos por secreto profesional. > Si usted recibe este correo electrónico por error, gracias por informar > inmediatamente al remitente y destruir el mensaje. > Al no estar asegurada la integridad de este mensaje sobre la red, Atos no > se hace responsable por su contenido. Su contenido no constituye ningún > compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. > Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor > no puede garantizar nada al respecto y no será responsable de cualesquiera > daños que puedan resultar de una transmisión de virus. > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-06-8759-4253 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 skype: depa01 twitter: @depa01 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-sustainability-proposal/attachments/20161123/3a1ba77e/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 11614 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-sustainability-proposal/attachments/20161123/3a1ba77e/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy