Dear all, As promised, please find herewith a Word template you can use for describing your Ref. Zone. In the finer details, feel free to add subheadings as necessary, of course. Please do append the name of your reference zone in the filename when editing. Would you, within each zone, please agree on a person who could deliver such a textual/visual description a) by email to me or b) by uploading it to the respective workspace folder<https://drive.google.com/open?id=0Byvp-hC42m3gV0Etb2hXTFV2d1E> by Wed 10-Feb, 10 am CET, even as a draft? The close-to-final version would be due one week from there. This is quite important to get fleshed out now, and mutually visible to all, before we get into further and more detailed budgeting discussions. Further, the text from these will ultimately be copied directly into the proposal master document, so please pay attention to and use the styles as defined in this template. A copy of the template is also in the workspace. kind regards, Mikko On 11 Feb 2016, at 21:53, Riepula Mikko <Mikko.Riepula at aalto.fi<mailto:Mikko.Riepula at aalto.fi>> wrote: Dear all, We have created a Google folder<https://drive.google.com/open?id=0Byvp-hC42m3gbjVIb1hfODItQm8> for the purpose of sharing and collaboratively editing documents for the preparation of our project proposal. Please request access from a Google account you use, if it doesn’t work directly for you. The idea is that it will be kept in confidence by and between the consortium members. Once you have access, you may further grant access to relevant colleague but please, do it only to accounts that can be clearly identified as such (no anonymous access). 1) Please take a look at the sheet named Reference Zone Info (…)<https://docs.google.com/spreadsheets/d/1XzT5JxLzCNXgzcFFpggb2QioL2hHFBuHlRMt1XNi400/edit#gid=0>. It looks quite a bit the same as the previous similar sheet, but is another, more elaborate and hopefully more purposeful at this stage. The focus is at (should be at, or should at least move towards) the application and service level, but for that, a good idea of the existing and planned IoT infrastrucutre is of course still relevant. (I carried over the earlier text for your conveience, splicing some, adding further comments to resolve to some.) The idea is that there you will all see each others’ inputs, can compare and try to align the level of abstraction in the respective descriptions, which are of course bound to be short there. 2) Tomorrow you will receive a “traditional” Word document template where you can the spell out more in detail (text, graphics etc.) your existing reference zone infrastructure, applications as well as your future aspirations — so the two are complementary, dealing with the same topic, in different formats/level of detail. It’s important to try to respect the formatting there in order to integrate them all into one master document in the end. More on that tomorrow. Kind regards, Mikko Mikko Riepula, MSc (Tech), Dr (Econ. & Bus. Admin) Project Manager, Post-doctoral Researcher Aalto University Runeberginkatu 22-24 00100 Helsinki (PO Box 21220, 00076 Aalto) Finland tel: +358 50 3837378 (mobile) -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-oasc-iot-lsp-cities/attachments/20160212/2b6ea4fd/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Reference Zone Description Template v1.2.1.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1517986 bytes Desc: Reference Zone Description Template v1.2.1.docx URL: <https://lists.fiware.org/private/fiware-oasc-iot-lsp-cities/attachments/20160212/2b6ea4fd/attachment.docx>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy