I would avoid OASIS as it is an standardization body. I like also SCALE, and maybe CityScale Best regards Clara Pezuela Head of IT Market Research and Innovation Group ARI booklet Atos Spain SA Clara.pezuela at atos.net +34 675 62 9974 -----Original Message----- 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 David Gómez Fernández Sent: Thursday, March 17, 2016 12:46 PM To: Martin Brynskov; Fiware-oasc-iot-lsp-cities at lists.fiware.org Subject: Re: [oasc-iot-lsp-cities] Looking to London Thanks a lot Martin for your time (seems you find inspiration at nighttime :-P ). With regards to the name of the project, I like the most the "SCALE" option (with "OASIS" standing out in the silver medal position) but, after quickly googling it, I have detected some potential overlappings, i.e. [1], [2] and [3], that might jeopardize the name in case we decide to give green light to "SCALE". As a hybrid solution (sharing the roots with "OASIS"), I would propose to leverage our OASC position and, with a straightforward tweak, move from "SCALE" to "OASCALE", resulting in an "unwrapped" name as follows: Open and Agile Smart Cities Alliance for Large Scale Experimentation. All in all, the benefit would be twofold: 1- We can avoid the aforementioned overlappings and 2- The other half of the work (i.e. the design of a logo) would not start from scratch, since we could, to the extent possible (e.g. ethical/legal constraints), reuse OASC's fonts to design our own alternative. [1] Project Scale is an INTERPOL project to support member countries in identifying, deterring and disrupting transnational fisheries crime (http://www.interpol.int/Crime-areas/Environmental-crime/Projects/Project-Scale). [2] SCALES stands for Securing the Conservation of biodiversity across Administrative Levels and spatial, temporal, and Ecological Scales. The SCALES project will seek ways to build the issue of scale into policy and decision making and biodiversity management (http://www.scales-project.net/). [3] Whereas the two previous ones are completely orthogonal to the extent of our proposal, this one corresponds to an FP7 project (http://www.cloudscale-project.eu/). As you can see, it carries a prefix beside "Scale", so I propose to follow the same approach and have something that really make us "unique". Just thinking loud, just to put yet another candidate on the table... Best, David On 17/03/2016 10:32, De Lama Sanchez, Nuria wrote: > Thanks Martin for the clear and complete message. Points taken. > > WRT the proposed names for the proposal my vote go for SCALE and OASIS (still not sure which one I prefer). > > Nuria de Lama > > Research & Innovation > ICT Program Manager > Vice-Secretary General Big Data Value Association > > M +34 680645692 > T +34 91214 9321 > F +34 91754 3252 > nuria.delama at atos.net > Albarracín 25 > 28037 Madrid > Spain > www.atosresearch.eu > es.atos.net > > Feel free to download our booklet at > http://atos.net/en-us/home/we-are/insights-innovation/research-and-inn > ovation.html > > > -----Original Message----- > 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 Martin Brynskov > Sent: Thursday, March 17, 2016 3:56 AM > To: Fiware-oasc-iot-lsp-cities at lists.fiware.org > Subject: [oasc-iot-lsp-cities] Looking to London > > Dear all, > > Following today's (Wednesday's) meeting, allow me to summarize a few main points leading to 48 productive hours in London next week, and to a fine finish. > > There are action points for every partner, basically in two categories: > - deliver basic info (partner descriptions, reference zone basics > etc.) ASAP, > - participate actively in welding the bits and pieces into a marvellous proposal, first of all by writing the sections with your name on (found in the London agenda and proposal timeline). Mikko and Mirko will bug you immediately if you don't. > > The points I cover in this message are the following: > 1. Process (teams and meetings) > 2. London meeting (agenda, objectives) 3. Reference zones (description > and theme development) 4. Partners (local and horizontal) 5. Project > name and acronym > > Be sure to read this email, especially if you weren't in the last two calls (with cities last Thursday and the weekly meeting today). > > You will find the agenda and minutes from the meeting below[1], and I'll refer to specific online documents with direct links as well. This message is also inserted at the end of the minutes for reference. > > Here we go. > > 1. PROCESS > > We now have established productive working teams around three logics: (a) local reference zones, (b) work packages and (c) proposal sections. In addition to this, the coordination team keeps things, well, coordinated, and gives direction. Up until now, the giving direction and vision part has been very organic and tacit (at least to some). This will change somewhat as the input and development matures over the next week. > > Each reference zone acts as a local group of stakeholders responsible for producing and coordinating input for the proposal, and engaging in the development of shared goals and activities. The zones are: > > ANT (Antwerp+iMinds), Belgium > CAR (Carouge+Mandat International), Switzerland EIN > (Eindhoven+Philips, Atos), Netherlands HEL (Forum Virium Helsinki, > Aalto Uni), Finland MAN (Manchester+Future Cities Catapult, Digital > Catapult), UK MIL (Milan+Engineering), Italy POR (Porto), Portugal SAN > (Santander+Uni. Cantabria, Telefónica), Spain > > This is the most dynamic part, and also the most vulnerable part of the proposal development. We rely on each of the partner/city groups to keep coordination tight. The vision is to shape a global urban IoT market based on European city needs, by showing what works on a large scale when we really push the envelope from a mature baseline. Envisioning this as a concerted, locally rooted effort is a very interactive exercise which cannot be easily delegated. The coming seven days will rely on these groups working as an agile collective on both local and project level. I'll return to the content and process more specifically below. Main action point here is to HAVE ALL CITIES DIRECTLY LINKED INTO THE LONDON MEETING (both during the 48 hours and preparation before). Without direct participation and access to information, it will be very difficult to co-create the common themes and development plan. > > The proposal sections are also integrated in the London meeting agenda, including responsible leads. In the proposal timeplan[2] you'll find each section, with responsible leads and dates for final versions. ALL PARTNERS HAVE SECTION RESPONSIBILITIES. By the end of this week, ALL PARTNER DESCRIPTIONS and ALL REFERENCE ZONE INPUT should be provided. > > The work packages are available online[3] in iteratively more consolidated versions. We didn't spend lots of time in the weekly meeting discussing them, and there are still connections which can be shifted, but the teams are active, so dive in if you want to check specifics. We kick off the London meeting with a session on the WP tasks and relations. And end by suggesting effort distribution across partners. > > We've had weekly meetings Wednesdays at 10-11 CET, which cover core issues. In addition, we had the first all-zones city meeting Thursday last week. In addition, smaller working groups have met in parallel offline. The London meeting will condensate all of these tracks. After London we shall keep the weekly Wednesday meeting, still only for the most pressing issues and (prepared) decisions. Actual development happens in the teams. Furthermore, I propose a city-focused meeting on Thursday March 31, 10-12 CET. Eventually, we have a final approval meeting of the entire proposal on Friday, April 8, 10-12 CET. All of this is noted in the proposal timeplan[2], and calendar invites will go out. > > We won't call more all-hands physical meetings, but we may meet in core groups if needed. I happen to be in Eindhoven on Tuesday, March 29, and some will likely meet in the OASC/iMinds premises in Brussels in the latter days also, to finetune the engagement part (WP1/5/6). > > 2. LONDON MEETING > As you are hopefully all aware, the London meeting is Monday to Wednesday next week (March 21-23). The agenda is online[4]. > Register ASAP in the sheet provided by Nadia[5]. Venue details are in the enclosing folder[6]. Monday/Tuesday are at the Future Cities Catapult/Nadia, Wednesday at the Digital Catapult/Alex (one underground stop apart). > > The meeting has two overall objectives: to ensure that the overall vision and themes are co-created in a way which both hits the call objectives and ignites the resources of the reference zone stakeholders; and to ensure that the proposal is created with all sections and elements fleshed out and linked coherently with only specific chunks to be formulated in the following days. > > In order for this to work, we have created an agenda which contains a few plenary sessions -- focusing on overview and alignment -- and many parallel, interactive and iterative sessions on specific sections. It will be very difficult to contribute to the proposal if a partner is not present. We have the possibility of remote participation, but it will not be nearly as effective, and especially the local reference zone collaboration will be challenged when the iterations are quick and concrete if one party is no engaged. Ultimately, the coordination is responsible for quality asessment and contingency planning for the proposal development, and this element is foreseen as absolutely essential. We shall therefore put emphasis on the commitments that can be made on-site and in active dialog with the collective as a whole. > > The weekly Wednesday morning meeting will naturally be replaced by the London agenda that week. > > 3. REFERENCE ZONES > There is some work left to elicit, share and fuse the city/reference zone status and ambitions. To be structural, we need both the "State of the Art" (status) and "Beyond State of the Art" (ambition) both on an individual reference zone level and project level, and we need it from some key perspectives, such as technical assets (e.g. Technology Readiness Levels), usage (e.g. engagement/transactions), market, legal/governance situation and impact (e.g. policy change, cost reduction, improved governance). This, in turn, needs to be translated into local and project-wide objectives with KPIs and a work plan. Overall, we're aiming for 2-4 themes which will be translated into local implementations of new/improved services, using shared enablers. > > Currently, this is captured in several places: > In the Reference Zone Matrix[7] you find two sheets: an overview of the zones and a functional matrix structured by application domains and themes. ALL LOCAL REFERENCE ZONE TEAMS SHOULD FILL THIS FUNCTIONAL MATRIX OUT and use it actively to explore and suggest themes to move beyond the state of the art. > > For each reference zone there's a proper description in the appropriate Reference Zones folder. This should provide a more elaborate and rich description of each reference zone, including: > (a) a map (the reference zone is a specific geographic area, by the > call definition), > (b) a concise list of assets (in the minutes [1] you find an example), > (c) any legal/governance extra freedom related to the reference zone > (directly asked for in the call), > (d) a local stakeholder/partner list (also related to budget and partner formalities). > > The provisioning and co-creation is facilitated in London by Remco (as with the previous cities meeting), supported by Mikko and Mirko, who oversee the matrix and reference zone documentation. In the proposal, we have limited space in Sections 1-3 for description of reference zones. This will therefore go into relevant sections with concise information, and fuller descriptions will go in Section 4 Partner descriptions, with sub-section 4.2 having a proper description of each reference zone. > > 4. PARTNERS > In connection to the reference zone descriptions, we discussed the local partnership models, both for financing and for formal participation. To quote the minutes[1]: "When discussing the financing and partnership/budget model for reference zones, the following was concluded: Reference zones should, in addition to the information above, indicate a preferred financing/partnership model, either with 1-3 specific local organisations directly as partners in the project, or an alternative model where the reference zone development budget is held with a core partner, preferably the municilality, and a specific sub-contracting specification, including named partners, is supplied." > > This has two implications: First, no later than in London on Monday, EACH REFERENCE ZONE MUST PROPOSE A LOCAL MODEL, INCLUDING NAMED PARTNERS. After London we will only have time to include those who have been brought in in this structured fashion. Second, we leave it to the reference zones to propose a way to allocate funds locally which is optimal for them. There are pros and cons of having more full partners vs. sub-contracting, and sometimes non-goverment organizations have more flexibility, wheras public commitment to distributing funds seems more credible. In addition, there are the open calls. They are used to engage *additional* actors, both within the existing reference zones and in new sites. > > After the meeting Wednesday there was a short follow-up discussion about additional horizontal partners. The concrete case was dissemination/integration partners and a communications partner. In general, the baseline now is not to include more partners, unless we really need them. We probably need a dedicated communications partner. We probably don't need more dissemination/integration partners. Decisions will be taken in London. > > One way of linking key actors on the global IoT scene to the consortium would be through the Advisory Board. This will also be discussed in London. Feel free to propose candidates. > > 5. Name > Although we have six suggestions for a project name in the dedicated doc[8], no decision or consensus has been reached. The list is currently: > SCALE Smart Cities Alliance for Large-scale Experimentation > OASIS OASC IoT Smart Cities > OILaSP OASC IoT LArge-Scale Pilot > CCL Connected Cities for Large Scale IoT Pilots > CCN European IoT Network for Connecting Cities > BYOC Bring Your Own City > > Another a approach would be anagrams, which produce zesty hits like: > Camp Mesh > Scam hemp > A Spec--hmm... > > :o) > > Anyway, feel free to vote or suggest in the doc. > > With this I will end, reminding us that there is 26 days left until closure of the call, on April 12, 17:00 CET. You will all be invited, by PIC/main contact email to the Participant Portal so that you can gaze at the clock. > > We can do it, and it will be great, but there are som "implementation details" which require a truly concerted effort. I look forward to doing that in London. > > Cheers, > Martin > > [1] Minutes: > https://docs.google.com/document/d/1IqC-2toFn5J213fvzo8ZGi2YWmzm3EmmZa > cNPdjJ8SU/ [2] Timeplan: > https://docs.google.com/spreadsheets/d/1qZWJ4evEfAnijKZx5bN7yW5KrEmwrX > ANCWwd6YMA1kI/ [3] WPs: > https://drive.google.com/drive/folders/0B4jiMzhNIS92NVVqSThHVXJwM2s > [4] London agenda: > https://docs.google.com/document/d/1KlWxwSHGOUx1FlLxw1-ItKu83t93Of-v8l > _X8nvNdGU/ [5] London sign-up: > https://docs.google.com/spreadsheets/d/1fmr8uUltAmeJHheK0IGrPFXLe8YhAg > 3eq5t6F2_ZYXs/ [6] Venue details: > https://drive.google.com/drive/folders/0B6nLNqwgl-RsZElodmw2c1lqTDA > [7] Reference Zone matrix: > https://docs.google.com/spreadsheets/d/1XzT5JxLzCNXgzcFFpggb2QioL2hHFB > uHlRMt1XNi400/ [8] Name list: > https://docs.google.com/spreadsheets/d/17ubU00Oy6wQZ4UKetZWfC3_ycwUO8B > 6u96gHvxHbX3U/ > > -- > 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 > > _______________________________________________ > 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 > 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. > _______________________________________________ > 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 _______________________________________________ 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 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.
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy