[oasc-iot-lsp-cities] Section 2.1 update + 2.2

[Muijs, Remco]

Ana,

Please find attached the section that Philips is employing in its H2020 proposals stipulating in more detail the contents of the consortium agreement to be drafted when our project is accepted and prior to project initiation. I strongly suggest inclusion of this text, as it will greatly approval procedures.

Remco

From: fiware-oasc-iot-lsp-cities-bounces at lists.fiware.org [mailto:fiware-oasc-iot-lsp-cities-bounces at lists.fiware.org] On Behalf Of Alex Gluhak
Sent: zaterdag 9 april 2016 16:02
To: Ana Garcia <ana.garcia at enoll.org>; Mirko Presser <mirko.presser at alexandra.dk>
Cc: Fiware-oasc-iot-lsp-cities at lists.fiware.org; margarida.campolargo at portodigital.pt
Subject: Re: [oasc-iot-lsp-cities] Section 2.1 update + 2.2

Anna

Here the OrganiCity IPR section – please look for OrganiCity key word and adapt

Alex

.2.2      Management of Intellectual Property
As with any joint endeavour with potential exploitation/commercial impact, managing the IPR around the project will be critical. As such the project handles this by looking at the general areas: access rights, ownership and the instantiation of these aspects through relevant agreements.
            General: For the success of the project it is essential that all project partners agree on explicit rules concerning IP ownership, access rights to any Background and Foreground IP for the execution of the project and the protection of Intellectual Property Rights (IPRs) and confidential information before the project starts and it will ensure these are formalised in relevant agreements.
            Agreements: The purpose of the Consortium Agreement is to establish a legal framework for the project in order to minimise any internal issues within the consortium related to the work, IP-Ownership, Confidential Information, Access Rights to Background and Foreground IP for the duration of the project and any other matters of the consortium interest.
            Access Rights: In order to ensure smooth execution of the project, the project partners agree to grant royalty-free access to Background and Foreground IP for the execution of the project. Therefore, all project partners determine any Background IP they are willing to submit to the project within the Consortium Agreement before the project starts. Any details concerning the access rights to Background and Foreground IP for the duration of the project will be defined in the Consortium Agreement.
            IP Ownership: Foreground IP shall be owned by the project partner carrying out the work leading to such Foreground IP taking into account the co-creators. If any Foreground IP is created jointly by at least two parties and it is not possible to distinguish between the contributions of each of the parties, such work will be jointly owned by the contributing parties. The same shall apply if, in the course of carrying out work on the project, an invention is made having two or more contributing parties contributing to it, and it is not possible to separate the individual contributions. Any such joint inventions, all related patent applications and patents shall be jointly owned by the contributing parties.  Any details concerning the exposure to jointly owned Foreground IP, joint inventions and joint patent applications will be addressed in the Consortium Agreement. See further details in the management section (3.2.1).
            Access to OrganiCity developments will be made publically available using open source licenses wherever this is appropriate.

From: Ana Garcia <ana.garcia at enoll.org<mailto:ana.garcia at enoll.org>>
Date: Saturday, 9 April 2016 14:36
To: Mirko Presser <mirko.presser at alexandra.dk<mailto:mirko.presser at alexandra.dk>>
Cc: Sebastien Ziegler <sziegler at mandint.org<mailto:sziegler at mandint.org>>, Alex Gluhak <alex.gluhak at digicatapult.org.uk<mailto:alex.gluhak at digicatapult.org.uk>>, "Fiware-oasc-iot-lsp-cities at lists.fiware.org<mailto:Fiware-oasc-iot-lsp-cities at lists.fiware.org>" <Fiware-oasc-iot-lsp-cities at lists.fiware.org<mailto:Fiware-oasc-iot-lsp-cities at lists.fiware.org>>, "margarida.campolargo at portodigital.pt<mailto:margarida.campolargo at portodigital.pt>" <margarida.campolargo at portodigital.pt<mailto:margarida.campolargo at portodigital.pt>>
Subject: Re: [oasc-iot-lsp-cities] Section 2.1 update + 2.2

Status on section 2.2:

- Nuria and Sebastien please lets work in a strong introductory part as discussed I put the key words discussed today (half a page) INPUT IN already, I need to harmonise it
- Exploitation strategy (Nuria, half a page) DONE
- Dissemination plan, actions and measures (Ana, 1 page) In progress
- Impact through standardisation (Sebastien, Juanjo, 1/2 page) DONE
- Knowledge management and IPR (Nadia/Adrienne, 1/2 based on Organicity) Nothing IN so far
- Data management plan (not clear to me who was going to write this but Alex/Remco/Sergio/Juanjo mentioned in the call) (1/2 page) Some text in/DONE
- Communication (Ana, 1 page) DONE

A more consolidated version will be ready tonight and I will inform of status then

Best,

Best,
Ana García
Director

ENoLL ivzw | Pleinlaan 9 | 1050 Brussels | Belgium | www.openlivinglabs.eu<http://www.openlivinglabs.eu/>

T:  | F: +32 2 629 16 13 | M: +32 470 19 3118

@openlivinglabs | @RoblesAG



On 9 April 2016 at 12:53, Mirko Presser <mirko.presser at alexandra.dk<mailto:mirko.presser at alexandra.dk>> wrote:
Dear all,

Here is a section 2.1 update.

LUIS will look at the 2.1.1 points 4-9.

Any VOLUNTEERS to look through 1-3?

I am expecting inputs from MARGARIDA for the KPIs – she will collect this form the cities.

I need the Mexican City description. SERGIO

I need ATOS - NURIA, TELEFONICA - SERGIO, PHILIPS - REMCO, ENGINEERING - STEPHANO to look at 2.1.2.10 and shorten to 1-2 pages. Each company gets 1/3 page max.

MIRKO to write an intro to 2.1.2 based on the moved figure (Arup Table) which sits now in section 1.

We have 9 cities (including the Mexican city) - this means that with 1 page per city we spend 50% on that. Most of the content is boasting how great the cities already are. We don’t need that in this section – that can be in section 4 – what we need is how SynchroiCity will help you propel you even further into becoming an even greater city. So – EACH CITY should revise their inputs to focus on IMPACT and not how great they are. 2/3 pages per city is max.

Any VOLUNTEERS to check barriers and obstacles 2.1.3? - shorten to 1.5 pages

SERGIO – I need that standards table 2.1.4.

I have deleted the section on other societal impact that Pentti made based on PEST – it was too generic.

MARTIN – please give me a first draft for 2.1.5 Quantifiable Impact of the Project form a project perspective – cities will be coming in from MARGARIDA’s work.

Ana – could you give a status on 2.2?

Finally we have a page limit problem. We need to cut this down to 20 pages. Including 2.2! So we are not looking for volume.

Thanks

Mirko

____________________________________________
MIRKO PRESSER
INTERNET OF THINGS EXPERT AND TEAM LEADER
DATA SCIENCE AND ENGINEERING LAB

ALEXANDRA INSTITUTTET A/S
ÅBOGADE 34, 8200 AARHUS N
KONTOR: HOPPER-333

+ 45 30 49 09 76<tel:%2B%2045%2030%2049%2009%2076>
mirko.presser at alexandra.dk<mailto:fornavn.efternavn at alexandra.dk>
alexandra.dk<http://www.alexandra.dk/>
linkedin.com/in/mirkopresser<http://linkedin.com/in/mirkopresser>
twitter.com/mirkopresser<http://twitter.com/mirkopresser>
____________________________________________



_______________________________________________
Fiware-oasc-iot-lsp-cities mailing list
Fiware-oasc-iot-lsp-cities at lists.fiware.org<mailto:Fiware-oasc-iot-lsp-cities at lists.fiware.org>
https://lists.fiware.org/listinfo/fiware-oasc-iot-lsp-cities


________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-oasc-iot-lsp-cities/attachments/20160410/d9855564/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Submission H2020_Management of Intellectual Property.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 17827 bytes
Desc: Submission H2020_Management of Intellectual Property.docx
URL: <https://lists.fiware.org/private/fiware-oasc-iot-lsp-cities/attachments/20160410/d9855564/attachment.docx>