From thorsten.sandfuchs at sap.com Thu May 2 14:31:55 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 2 May 2013 12:31:55 +0000 Subject: [Fiware-apps] Review of cloud chapter can start Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646106E64D@DEWDFEMB11A.global.corp.sap> Dear colleagues, as mentioned in our last call, you and we have been assigned to review the cloud chapter (details attached) - the deliverable is now ready and you can start your review: https://forge.fi-ware.eu/docman/view.php/27/2162/M24_WP4_OpenSpec_D412_v2_generated.doc Assignments: Cloud Chapter Thorsten (SAP) IaaS Data Center Resource Management (DCRM) Marco (TI) IaaS Service Management (SM) Pablo (TID) Object Storage Javier (UPM) Cloud Proxy Youssouf (Thales) PaaS Management Joaquin (ATOS) Software Management And Configuration (SDC) Rafa (UPM) Monitoring Torsten (SAP) Edgelets Management Andreas (SAP) Job Scheduler Koen/Sophie (iMinds) Cockpit: https://docs.google.com/spreadsheet/ccc?key=0AmxBgS-lWT4vdHYxYTVOZ3FrNEprZXRBZk80TGRLMGc#gid=0 * 29/April/2013 - this day EOB I will expect the doc version of your chapter uploaded and ready on the open Specs cockpit * 30/April/2013 - start of the peer review * 08/May/2013 - end of the peer review. At the end of this day, the cockpit has links to all the reviews stored on the private project(a word doc tracking the changes). * 10/May/2013 - end of incorporation of comments. This is done directly on thew wiki. At the end of this day, the Open specs cockpit has the new versions of the docs, with all changes incorporated. This docs must be re-generated from the wiki by the WPL Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Miguel Carrillo Subject: [Fiware] Guidelines for Open Specs Date: Fri, 19 Apr 2013 12:51:19 +0000 Size: 19534 URL: From markus.heller at sap.com Fri May 3 09:31:32 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 3 May 2013 07:31:32 +0000 Subject: [Fiware-apps] FI-WARE: WP3 Call In-Reply-To: <393554EDCF801348BC53C7813C6CB73B0694C9@DEWDFEMB14A.global.corp.sap> References: <393554EDCF801348BC53C7813C6CB73B0694C9@DEWDFEMB14A.global.corp.sap> Message-ID: <393554EDCF801348BC53C7813C6CB73B07B438@DEWDFEMB14A.global.corp.sap> Dear all, I would like to kindly remind you of our WP3 call today 13-14 (my time). Hear you soon Markus -----Original Appointment----- From: Heller, Markus Sent: Mittwoch, 24. April 2013 15:24 To: Heller, Markus; 'fiware-apps at lists.fi-ware.eu'; 'Tim.Jonischkat at paluno.uni-due.de'; 'matteo.melideo at eng.it'; 'miguel.huerta at atos.net'; 'mathieu.hutschemaekers at ericsson.com'; PABLO AROZARENA LLOPIS; Fasse, Axel; Froese, Andreas Cc: Klein, Andreas; Leidig, Torsten Subject: FI-WARE: WP3 Call When: Freitag, 3. Mai 2013 13:00-14:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: SAP Connect from Markus Dear WP3 colleagues, On Thursday 02.05 we from SAP cannot participate due to an internal event, so I move the meeting to Friday same time as exception, sorry for the move. Please try to participate, since this is the only possibility to meet sometime on Friday in the week. If too many of you cannot participate, we need t move into week of 6.5 (very late). Best wishes Markus Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call, please use the dial-in info below. Please notify me if you experience dial-in problems with my call or if you miss a dial-in numbers for your country and I will see what I can do to add one. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Blackberry Austria, Vienna : +431253021750 tel:+431253021750,,4211563470# Belgium, Brussels : +3224040657 tel:+3224040657,,4211563470# Czech Republic, Prague : +420228882890 tel:+420228882890,,4211563470# Finland, Helsinki : +358923101631 tel:+358923101631,,4211563470# France, Paris : +33170701777 tel:+33170701777,,4211563470# Germany, Frankfurt : +4969222210764 tel:+4969222210764,,4211563470# Germany, Munich : +4989710424682 tel:+4989710424682,,4211563470# Ireland, Dublin : +35312476192 tel:+35312476192,,4211563470# Israel, Tel Aviv : +97237630750 tel:+97237630750,,4211563470# Italy, Milan : +390236009839 tel:+390236009839,,4211563470# Italy, Rome : +390645236623 tel:+390645236623,,4211563470# Luxembourg, Luxembourg : +35224871454 tel:+35224871454,,4211563470# Netherlands, Amsterdam : +31207168291 tel:+31207168291,,4211563470# Norway, Oslo : +4721502761 tel:+4721502761,,4211563470# Portugal, Lisbon : +351217810275 tel:+351217810275,,4211563470# Singapore, Singapore : +6566549828 tel:+6566549828,,4211563470# Spain, Barcelona : +34938000782 tel:+34938000782,,4211563470# Spain, Madrid : +34917699443 tel:+34917699443,,4211563470# Sweden, Stockholm : +46850336514 tel:+46850336514,,4211563470# Switzerland, Geneva : +41225927995 tel:+41225927995,,4211563470# Switzerland, Zurich : +41434569248 tel:+41434569248,,4211563470# UK, Belfast : +442895950013 tel:+442895950013,,4211563470# UK, Edinburgh : +441314601125 tel:+441314601125,,4211563470# UK, London : +442033645639 tel:+442033645639,,4211563470# USA, New York : 1-646-434-0499 tel:1-646-434-0499,,4211563470# USA, Denver : 1-720-897-6637 tel:1-720-897-6637,,4211563470# USA, Philadelphia : 1-484-427-2544 tel:1-484-427-2544,,4211563470# If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Fri May 3 11:08:46 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 3 May 2013 09:08:46 +0000 Subject: [Fiware-apps] FW: [Fiware-wpa] Focus of State of the Art deliverable In-Reply-To: <51837BB9.8030504@tid.es> References: <51837BB9.8030504@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610708E3@DEWDFEMB11A.global.corp.sap> Dear colleagues, Please adhere to the comments of Miguel - compiling the state of the art deliverable. We have more details in our weekly call, today. Best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Freitag, 3. Mai 2013 10:56 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] Focus of State of the Art deliverable Dear all, after a few interactions withe the WPs, I would like to remark something that we partially mentioned in the confcall on monday but among so much info messages sometimes get lost. * Some WPL ask about the desired length. The answer is that there is not a standard number of pages. We do not expect a chunky doc of 100 pages per WP, we want significant and solid messages. I do not mind if we get 20 pages per chapter as long as they are well written and give the right information. * The focus is twofold: * What there is out there (current situation) * What it is going to be there (trends, foreseable future) * We must say what innovations we offer in each chapter y how it compares with other research projects or products on the market. Research projects do not necessarily mean FP7 or PPP related, not even subsidised. Please avoid a document where 80% of the text is a long list of project subsidised by the EC or national authorities. Subsidised research can be mentioned (must, if it is relevant) but let us avoid a narrow view. Hope this clarifies a bit. Please let your partners know in each chapter. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From andreas.klein at sap.com Fri May 3 14:37:33 2013 From: andreas.klein at sap.com (Klein, Andreas) Date: Fri, 3 May 2013 12:37:33 +0000 Subject: [Fiware-apps] WP3 Meeting Minutes 2013-05-03 Message-ID: <556F697ADC3400408FBBCF7C6040979D0705E2EB@DEWDFEMB14B.global.corp.sap> Dear WP3 partners, please find the minutes of today's WP3 call in the docman: https://forge.fi-ware.eu/docman/view.php/12/2181/2013_05_03_FI-WARE_WP3_MinutesV2.doc Best regards Andreas Andreas Klein SAP AG SAP Research Center Karlsruhe Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe T +49-6227-7-52554 -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Tue May 7 08:57:09 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 7 May 2013 06:57:09 +0000 Subject: [Fiware-apps] FI-WARE: WP3 Call Message-ID: <393554EDCF801348BC53C7813C6CB73B07D2D8@DEWDFEMB14A.global.corp.sap> Hi, Due to a bank holiday here in Germany (Ascension Day) I move our meeting to Friday this week. Best wishes Markus ---- Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call, please use the dial-in info below. Please notify me if you experience dial-in problems with my call or if you miss a dial-in numbers for your country and I will see what I can do to add one. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Blackberry Austria, Vienna : +431253021750 tel:+431253021750,,4211563470# Belgium, Brussels : +3224040657 tel:+3224040657,,4211563470# Czech Republic, Prague : +420228882890 tel:+420228882890,,4211563470# Finland, Helsinki : +358923101631 tel:+358923101631,,4211563470# France, Paris : +33170701777 tel:+33170701777,,4211563470# Germany, Frankfurt : +4969222210764 tel:+4969222210764,,4211563470# Germany, Munich : +4989710424682 tel:+4989710424682,,4211563470# Ireland, Dublin : +35312476192 tel:+35312476192,,4211563470# Israel, Tel Aviv : +97237630750 tel:+97237630750,,4211563470# Italy, Milan : +390236009839 tel:+390236009839,,4211563470# Italy, Rome : +390645236623 tel:+390645236623,,4211563470# Luxembourg, Luxembourg : +35224871454 tel:+35224871454,,4211563470# Netherlands, Amsterdam : +31207168291 tel:+31207168291,,4211563470# Norway, Oslo : +4721502761 tel:+4721502761,,4211563470# Portugal, Lisbon : +351217810275 tel:+351217810275,,4211563470# Singapore, Singapore : +6566549828 tel:+6566549828,,4211563470# Spain, Barcelona : +34938000782 tel:+34938000782,,4211563470# Spain, Madrid : +34917699443 tel:+34917699443,,4211563470# Sweden, Stockholm : +46850336514 tel:+46850336514,,4211563470# Switzerland, Geneva : +41225927995 tel:+41225927995,,4211563470# Switzerland, Zurich : +41434569248 tel:+41434569248,,4211563470# UK, Belfast : +442895950013 tel:+442895950013,,4211563470# UK, Edinburgh : +441314601125 tel:+441314601125,,4211563470# UK, London : +442033645639 tel:+442033645639,,4211563470# USA, New York : 1-646-434-0499 tel:1-646-434-0499,,4211563470# USA, Denver : 1-720-897-6637 tel:1-720-897-6637,,4211563470# USA, Philadelphia : 1-484-427-2544 tel:1-484-427-2544,,4211563470# If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 7077 bytes Desc: not available URL: From markus.heller at sap.com Tue May 7 09:10:35 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 7 May 2013 07:10:35 +0000 Subject: [Fiware-apps] FI-WARE: WP3 Call Message-ID: <393554EDCF801348BC53C7813C6CB73B07D37A@DEWDFEMB14A.global.corp.sap> Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call, please use the dial-in info below. Please notify me if you experience dial-in problems with my call or if you miss a dial-in numbers for your country and I will see what I can do to add one. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Blackberry Austria, Vienna : +431253021750 tel:+431253021750,,4211563470# Belgium, Brussels : +3224040657 tel:+3224040657,,4211563470# Czech Republic, Prague : +420228882890 tel:+420228882890,,4211563470# Finland, Helsinki : +358923101631 tel:+358923101631,,4211563470# France, Paris : +33170701777 tel:+33170701777,,4211563470# Germany, Frankfurt : +4969222210764 tel:+4969222210764,,4211563470# Germany, Munich : +4989710424682 tel:+4989710424682,,4211563470# Ireland, Dublin : +35312476192 tel:+35312476192,,4211563470# Israel, Tel Aviv : +97237630750 tel:+97237630750,,4211563470# Italy, Milan : +390236009839 tel:+390236009839,,4211563470# Italy, Rome : +390645236623 tel:+390645236623,,4211563470# Luxembourg, Luxembourg : +35224871454 tel:+35224871454,,4211563470# Netherlands, Amsterdam : +31207168291 tel:+31207168291,,4211563470# Norway, Oslo : +4721502761 tel:+4721502761,,4211563470# Portugal, Lisbon : +351217810275 tel:+351217810275,,4211563470# Singapore, Singapore : +6566549828 tel:+6566549828,,4211563470# Spain, Barcelona : +34938000782 tel:+34938000782,,4211563470# Spain, Madrid : +34917699443 tel:+34917699443,,4211563470# Sweden, Stockholm : +46850336514 tel:+46850336514,,4211563470# Switzerland, Geneva : +41225927995 tel:+41225927995,,4211563470# Switzerland, Zurich : +41434569248 tel:+41434569248,,4211563470# UK, Belfast : +442895950013 tel:+442895950013,,4211563470# UK, Edinburgh : +441314601125 tel:+441314601125,,4211563470# UK, London : +442033645639 tel:+442033645639,,4211563470# USA, New York : 1-646-434-0499 tel:1-646-434-0499,,4211563470# USA, Denver : 1-720-897-6637 tel:1-720-897-6637,,4211563470# USA, Philadelphia : 1-484-427-2544 tel:1-484-427-2544,,4211563470# If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 8171 bytes Desc: not available URL: From markus.heller at sap.com Tue May 7 09:10:35 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 7 May 2013 07:10:35 +0000 Subject: [Fiware-apps] FI-WARE: WP3 Call Message-ID: <393554EDCF801348BC53C7813C6CB73B07D37F@DEWDFEMB14A.global.corp.sap> Hi, Due to a bank holiday here in Germany (Ascension Day) I move our meeting to Friday this week. Best wishes Markus ---- Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call, please use the dial-in info below. Please notify me if you experience dial-in problems with my call or if you miss a dial-in numbers for your country and I will see what I can do to add one. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Blackberry Austria, Vienna : +431253021750 tel:+431253021750,,4211563470# Belgium, Brussels : +3224040657 tel:+3224040657,,4211563470# Czech Republic, Prague : +420228882890 tel:+420228882890,,4211563470# Finland, Helsinki : +358923101631 tel:+358923101631,,4211563470# France, Paris : +33170701777 tel:+33170701777,,4211563470# Germany, Frankfurt : +4969222210764 tel:+4969222210764,,4211563470# Germany, Munich : +4989710424682 tel:+4989710424682,,4211563470# Ireland, Dublin : +35312476192 tel:+35312476192,,4211563470# Israel, Tel Aviv : +97237630750 tel:+97237630750,,4211563470# Italy, Milan : +390236009839 tel:+390236009839,,4211563470# Italy, Rome : +390645236623 tel:+390645236623,,4211563470# Luxembourg, Luxembourg : +35224871454 tel:+35224871454,,4211563470# Netherlands, Amsterdam : +31207168291 tel:+31207168291,,4211563470# Norway, Oslo : +4721502761 tel:+4721502761,,4211563470# Portugal, Lisbon : +351217810275 tel:+351217810275,,4211563470# Singapore, Singapore : +6566549828 tel:+6566549828,,4211563470# Spain, Barcelona : +34938000782 tel:+34938000782,,4211563470# Spain, Madrid : +34917699443 tel:+34917699443,,4211563470# Sweden, Stockholm : +46850336514 tel:+46850336514,,4211563470# Switzerland, Geneva : +41225927995 tel:+41225927995,,4211563470# Switzerland, Zurich : +41434569248 tel:+41434569248,,4211563470# UK, Belfast : +442895950013 tel:+442895950013,,4211563470# UK, Edinburgh : +441314601125 tel:+441314601125,,4211563470# UK, London : +442033645639 tel:+442033645639,,4211563470# USA, New York : 1-646-434-0499 tel:1-646-434-0499,,4211563470# USA, Denver : 1-720-897-6637 tel:1-720-897-6637,,4211563470# USA, Philadelphia : 1-484-427-2544 tel:1-484-427-2544,,4211563470# If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 6805 bytes Desc: not available URL: From markus.heller at sap.com Tue May 7 10:20:02 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 7 May 2013 08:20:02 +0000 Subject: [Fiware-apps] FI-WARE: WP3 Call Message-ID: <393554EDCF801348BC53C7813C6CB73B07D587@DEWDFEMB14A.global.corp.sap> Hi, I am out of office on Thursday in Brussels. Therefore I move to Friday as exception. Best wishes Markus -- Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call, please use the dial-in info below. Please notify me if you experience dial-in problems with my call or if you miss a dial-in numbers for your country and I will see what I can do to add one. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Blackberry Austria, Vienna : +431253021750 tel:+431253021750,,4211563470# Belgium, Brussels : +3224040657 tel:+3224040657,,4211563470# Czech Republic, Prague : +420228882890 tel:+420228882890,,4211563470# Finland, Helsinki : +358923101631 tel:+358923101631,,4211563470# France, Paris : +33170701777 tel:+33170701777,,4211563470# Germany, Frankfurt : +4969222210764 tel:+4969222210764,,4211563470# Germany, Munich : +4989710424682 tel:+4989710424682,,4211563470# Ireland, Dublin : +35312476192 tel:+35312476192,,4211563470# Israel, Tel Aviv : +97237630750 tel:+97237630750,,4211563470# Italy, Milan : +390236009839 tel:+390236009839,,4211563470# Italy, Rome : +390645236623 tel:+390645236623,,4211563470# Luxembourg, Luxembourg : +35224871454 tel:+35224871454,,4211563470# Netherlands, Amsterdam : +31207168291 tel:+31207168291,,4211563470# Norway, Oslo : +4721502761 tel:+4721502761,,4211563470# Portugal, Lisbon : +351217810275 tel:+351217810275,,4211563470# Singapore, Singapore : +6566549828 tel:+6566549828,,4211563470# Spain, Barcelona : +34938000782 tel:+34938000782,,4211563470# Spain, Madrid : +34917699443 tel:+34917699443,,4211563470# Sweden, Stockholm : +46850336514 tel:+46850336514,,4211563470# Switzerland, Geneva : +41225927995 tel:+41225927995,,4211563470# Switzerland, Zurich : +41434569248 tel:+41434569248,,4211563470# UK, Belfast : +442895950013 tel:+442895950013,,4211563470# UK, Edinburgh : +441314601125 tel:+441314601125,,4211563470# UK, London : +442033645639 tel:+442033645639,,4211563470# USA, New York : 1-646-434-0499 tel:1-646-434-0499,,4211563470# USA, Denver : 1-720-897-6637 tel:1-720-897-6637,,4211563470# USA, Philadelphia : 1-484-427-2544 tel:1-484-427-2544,,4211563470# If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 6561 bytes Desc: not available URL: From thorsten.sandfuchs at sap.com Tue May 7 16:07:35 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 7 May 2013 14:07:35 +0000 Subject: [Fiware-apps] WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461076885@DEWDFEMB11A.global.corp.sap> Dear colleagues from WP3, Although trying to clarify this on the last wp3-meeting there seems to be a misunderstanding. WP11 needs input from your GE perspective on this and so far there was no submission from WP3 in a whole. We need to fix this and I count on your input. Please indicate to me until when you can finish this task and/or how you would propose to solve this and the related commutation to the WPL Juan. To make it more explicit was is needed I attached the document & outlined the tasks below. - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - 4.4.2. "generic enabler of the business Framework" => TID, UPM, iMinds E-IIS need to check and update their respective paragraphs and send corrective text or "OK" - 4.4.3. "Composition" => ATOS, DT, EAB, UPM needs updates reflecting the four major composition paradigmn, an updated graphic and related text (copy&paste can be used potentially from the architecture description) - 4.4.4. "Generic Enablers for Mediation" => THALES, TI need to check and update the complete chapter and send corrective text or "OK" - 4.4.6 "Business Canvas" -> @all contribute GE your specific input and perspective here - 4.4.7 and subchapters: Juan was only able to provide a blueprint for each sub chapter. You have to fill in for your GE: Benefits, Functions, Business and Stakeholders relationships, Value of FI functionalities o 4.4.7.2 "revenue sharing" ? TID o 4.4.7.4 Supporting service composition and crowd-sourcing ? UPM, ATOS, THALES, TI Thanks for all of your support, /Thorsten From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 25. April 2013 10:00 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] FW: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear colleagues, As probably not everybody is part of the WP11 exploitation list, I will distribute this information within this list as well. Action 3 applies to all industry partners: TID, SAP, THALES, TI, DT, EAB, ATOS, E-IIS, iMinds ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May Best, /Thorsten From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Mittwoch, 24. April 2013 19:40 To: fiware-exploitation at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D11.2.2+Exploitation_Plan,_including_IPR_Managementv_M24v2404_FOR_WP3_PARTNER.doc Type: application/msword Size: 4814336 bytes Desc: D11.2.2+Exploitation_Plan,_including_IPR_Managementv_M24v2404_FOR_WP3_PARTNER.doc URL: From thorsten.sandfuchs at sap.com Wed May 8 08:07:46 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 8 May 2013 06:07:46 +0000 Subject: [Fiware-apps] FW: [Fiware-wpa] Kindly REMINDER ON URGENT Action Points on Chapter teams and FI-WARE GEi owners In-Reply-To: <5189DD40.5020105@tid.es> References: <5188A68D.3060302@tid.es> <5189DD40.5020105@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646107C406@DEWDFEMB11A.global.corp.sap> Dear colleagues, As we discussed in the last wp3-concall our current way of thinking is: 1. Planned usage matrix - Split the "business framework" part into the partner contributions (we can have a "part of the business framework" in brackets or something) - please veto until EOB today, if you think this is not appropriate, otherwise we will implement the changes - We should state the more accurate testbed deployment dates for the phase 2 projects - it would be good if we state a date in the past, if the component is already deployed and "usable" within the Testbed - only then the UC2 won't be scared away from a date which is in the future and only then they will try to use our software - please set this on your own for your component. 2. Concerning webinars (the red action item down below) - I would suggest: - Only one webinar for the composition components - briefly touching on similarities and differences (ATOS, DT, UPM) - Only one webinar for the business framework and related stuff (TID, UPM, iMinds - potentially SAP) o Depending on the participants - One separate webinar for Mediator (TI/THALES) - One webinar on WP3 in a whole, where we present basically the ecosystem approach and the high level flow behind it - it will be easy to reuse the slides of the Madrid-FI-PPP-architecture-board session for this ? Do you agree to this approach? ? Can you please name at least 2 days where you as a partner listed above hosts and gives such a webinar? (JH: May 20th until June 14th. Try to make them in two alternative weeks) On a last resort, we will e.g. take our weekly WP3 slot for the webinars and assign people. (subsequently we would have to find another slot for the partner call). Thanks for your support on this, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 8. Mai 2013 07:06 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-wpa] Kindly REMINDER ON URGENT Action Points on Chapter teams and FI-WARE GEi owners Hi all, This is just a reminder about the request to provide your input to the spreadsheet on dates for the 1st series of webinars on FI-WARE GEis in the 2nd Release. Find below the original mail where the request was issued, which included the instructions to follow. You can take a look to what the owners of the WireCloud and the PROTON CEP GEis did as a reference. Thanks for those who already provided your input. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 07/05/13 09:00, Juanjo Hierro wrote: Dear all, Last Friday, May 3rd, we celebrated the first FI-PPP AB virtual meeting involving the new projects in phase 2 of the FI-PPP. You can take a look at the minutes available at: https://docs.google.com/document/d/1_DXfn7qSY4UEidfBv3E9MhplU1wcVOzkEpWhQ_0QK-M/edit?usp=sharing There are two URGENT Action Points that we have to finalize along this week so I ask for the cooperation of the several FI-WARE chapter teams and GEi owners: * Updating spreadsheet about "FI-WARE Testbed/GEis planned usage" available at https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E&usp=sharing * All chapter teams have to review the sheets linked "FI-WARE GEi (2nd Release) planned usage in Phase 1/2" if they haven't done so yet and send me their comments so that I can implement the proposed changes: * @I2ND was going to provide the name of FI-WARE GE and GEis (two first columns) for rows that have to be inserted for the new FI-WARE GEis in 2nd Release * @Apps was going to provide final feedback on whether it would make sense to split the package linked to Business Framework or not * Remember that this is to collect info about planned usage by UC projects, that's why it makes sense to have some rows in the sheets linked to packages of GEis / functionalities (e.g., Cloud) than as individual GEis * Please, don't edit yourself, forward feedback to me through your chapter leader * VERY IMPORTANT for FI-WARE GEi owners: Proposal on first series of webinars regarding FI-WARE GEis already available for UC projects in the Testbed (or to be available by end of May): * Deadline: Thursday May 9 EOB. * You should edit the following spreadsheet in Google docs yourself: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdF9aeWphSkFkWjJRQ3pPVW1PVURLX3c&usp=sharing * You just have to provide two alternative dates during the period from May 20th until June 14th. Try to make them in two alternative weeks. * Note that these webinars are not mandatory for all FI-WARE GEis but strongly recommended for GEis/functionality that can be already demonstrated in the Testbed while in the webinars or at least presented as mockup (e.g., this might be useful for some new Cloud functions) * You can select your favorite bridge tools. How do you declare the tools you plan to use so that people will connect ? Defining a hashtag * This will be used as an Id for the bridge/webex details to be provided in sheet "Logistics details" * It will be referred from the cell associated to the row linked to your GEi and the column "Logistic details" of sheet "FI-WARE GEi (2nd Release) - series of webinars" * We advise you also to use this hashtag in posts to the @FIware twitter account during the webinar. It may be helpful to collect questions on-line so people do not necessarily interrupt you (you can watch the twitter account and then decide when to answer those questions) * UC projects will declare their interest to attend the different webinars along the week of May 17th Please pay attention to this two urgent actions. We believe that their implementation can be rather useful for a successful project review mid June. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From matteo.melideo at eng.it Tue May 7 09:33:12 2013 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 07 May 2013 09:33:12 +0200 Subject: [Fiware-apps] FI-WARE: WP3 Call In-Reply-To: <393554EDCF801348BC53C7813C6CB73B07D2D8@DEWDFEMB14A.global.corp.sap> References: <393554EDCF801348BC53C7813C6CB73B07D2D8@DEWDFEMB14A.global.corp.sap> Message-ID: <5188AE38.90907@eng.it> Dear All, I am no longer involved in FI-WARE project since months now. Please remove me from the mailing list. Thank you in advance and best regards Matteo Melideo Il 07/05/2013 08:57, Heller, Markus ha scritto: > > Event Invitation > > Title: > > > > FI-WARE: WP3 Call > > Location: > > > > SAP Connect from Markus > > When: > > > > 10/05/2013 13:00 ? 14:00 > > Organiser: > > > > Heller, Markus > > Description: > > > > Hi, Due to a bank holiday here in Germany (Ascension Day) I move our > meeting to Friday this week. Best wishes Markus ---- Dear FI-WARE WP3 > colleagues, I invite you to our WP3 Call, please use the dial-in info > below. Please notify me if you experience dial-in problems with my > call or if you miss a dial-in numbers for your country and I will see > what I can do to add one. Best wishes Markus Please join me in a > Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ > Audio Conference Details: Audio Conference Participant Code: 124 225 > 3329 Conference Phone Numbers: Location Phone Blackberry Austria, > Vienna : +431253021750 > tel:+431253021750,,4211563470# Belgium, > Brussels : +3224040657 > tel:+3224040657,,4211563470# Czech > Republic, Prague : +420228882890 > tel:+420228882890,,4211563470# Finland, > Helsinki : +358923101631 > tel:+358923101631,,4211563470# France, > Paris : +33170701777 > tel:+33170701777,,4211563470# Germany, > Frankfurt : +4969222210764 > tel:+4969222210764,,4211563470# > Germany, Munich : +4989710424682 > tel:+4989710424682,,4211563470# > Ireland, Dublin : +35312476192 > tel:+35312476192,,4211563470# Israel, > Tel Aviv : +97237630750 > tel:+97237630750,,4211563470# Italy, > Milan : +390236009839 > tel:+390236009839,,4211563470# Italy, > Rome : +390645236623 > tel:+390645236623,,4211563470# > Luxembourg, Luxembourg : +35224871454 > tel:+35224871454,,4211563470# > Netherlands, Amsterdam : +31207168291 > tel:+31207168291,,4211563470# Norway, > Oslo : +4721502761 > tel:+4721502761,,4211563470# Portugal, > Lisbon : +351217810275 > tel:+351217810275,,4211563470# > Singapore, Singapore : +6566549828 > tel:+6566549828,,4211563470# Spain, > Barcelona : +34938000782 > tel:+34938000782,,4211563470# Spain, > Madrid : +34917699443 > tel:+34917699443,,4211563470# Sweden, > Stockholm : +46850336514 > tel:+46850336514,,4211563470# > Switzerland, Geneva : +41225927995 > tel:+41225927995,,4211563470# > Switzerland, Zurich : +41434569248 > tel:+41434569248,,4211563470# UK, > Belfast : +442895950013 > tel:+442895950013,,4211563470# UK, > Edinburgh : +441314601125 > tel:+441314601125,,4211563470# UK, > London : +442033645639 > tel:+442033645639,,4211563470# USA, New > York : 1-646-434-0499 > tel:1-646-434-0499,,4211563470# USA, > Denver : 1-720-897-6637 > tel:1-720-897-6637,,4211563470# USA, > Philadelphia : 1-484-427-2544 > tel:1-484-427-2544,,4211563470# If you > have never attended a Connect Pro meeting before: Test your > connection: > https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get > a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, > the Adobe logo, Acrobat and Acrobat Connect are either trademarks or > registered trademarks of Adobe Systems Incorporated in the United > States and/or other countries. > > Comment: > > > > Attendees: > > > > > 'fiware-apps at lists.fi-ware.eu' > > 'Tim.Jonischkat at paluno.uni-due.de' > > 'matteo.melideo at eng.it' > > 'miguel.huerta at atos.net' > > 'mathieu.hutschemaekers at ericsson.com' > > > PABLO AROZARENA LLOPIS > > Fasse, Axel > > Froese, Andreas > > Klein, Andreas > > Leidig, Torsten > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas.klein at sap.com Fri May 10 14:55:06 2013 From: andreas.klein at sap.com (Klein, Andreas) Date: Fri, 10 May 2013 12:55:06 +0000 Subject: [Fiware-apps] WP3 Meeting Minutes 2013-05-10 Message-ID: <556F697ADC3400408FBBCF7C6040979D0705F056@DEWDFEMB14B.global.corp.sap> Dear WP3 partners, please find the minutes of today's WP3 call in the docman: https://forge.fi-ware.eu/docman/view.php/12/2243/2013_05_10_FI-WARE_WP3_Minutes.doc Best regards Andreas Andreas Klein SAP AG SAP Research Center Karlsruhe Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe T +49-6227-7-52554 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Fri May 10 15:04:05 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 10 May 2013 13:04:05 +0000 Subject: [Fiware-apps] SUBMISSION - WP3 - RE: FI-WARE: Periodic Report - M13 - M24 Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646108146D@DEWDFEMB11A.global.corp.sap> Dear javier, Find the periodic report out of the WP3 for consolidation with other chapters, attached. Sorry for the late submission Please send the integrated version back to us in order to have an internal review prior to submission and in order to allow us to integrate the final evaluations. The submitted document does not contain some rationals given by the partners, as the numbers were not final so far. We are still missing (although pushing hard) the input from some partners, this will be integrated in the final version, together with the subsuming evaluations. Best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of JAVIER DE PEDRO SANCHEZ Sent: Montag, 15. April 2013 23:07 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: subsidies at tid.es Subject: [Fiware-wpa] FI-WARE: Periodic Report - M13 - M24 Importance: High Dear all As you know we have to deliver the Periodic Report which has to give an overview of the second year of the project (months from M13 (May12) to M24 (Apr13)). I will kindly ask you in another particularized e-mail to update as WPL the information about your WP. The schedule is the following: 1. First request of information to WPL with estimated effort per partner: April 15th, 2013 2. Period to request each WPL to each involved partner its contribution to WP: April 16th, 2013 - Apr 19th, 2013 3. Integration of received information from by each WPL: April 22nd, 2013 - May 5th, 2013 4. WPL send first version of his updated report to Coordinator (subsidies at tid.es): May 6th, 2013 5. Coordinator asks to each partner to update its current effort: April 30th, 2013 6. Each partner sends its current effort according FORM-C 2: May 1st, 2013 - May 10th, 2013 7. Coordinator sends updated data of effort to each WPL: May 15th, 2013 8. Updating of the second version of each report by each WPL: May 16th, 2013 - May 17th, 2013 9. WPL sends final version of his updated report to Coordinator (subsidies at tid.es): May 17th, 2013 10. Integrating and revision by Coordinator: May 20th, 2013 - May 24th, 2013 11. Coordinator sends the Periodic Report to Project Officer: May 28th, 2013 12. Review: June 10th, 2013 At last but not least, please, I kindly ask you to follow the template in order to have a homogeneous report as a team. In the last review report they said: [cid:image001.jpg at 01CE4D8E.DA044210] Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 39114 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP3_M13-M24_with_preparation_WP3_FOR_INTEGRATION_WITH_OTHER_CHAPTERS.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 273852 bytes Desc: WP3_M13-M24_with_preparation_WP3_FOR_INTEGRATION_WITH_OTHER_CHAPTERS.docx URL: From jsoriano at fi.upm.es Mon May 13 09:48:05 2013 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Mon, 13 May 2013 09:48:05 +0200 Subject: [Fiware-apps] Fwd: [Fiware] URGENT action on FI-WARE GEi owners regarding webinars In-Reply-To: <5190963F.9060409@tid.es> References: <5190963F.9060409@tid.es> Message-ID: Dear Markus, dear all, Who is responsible for allocating the date/s for the "Business framework" webinar/s that will merge Store, RSS, etc.? With regard to the Store GE, we prefer to have the webinar as late as possible. This will allow us to have ready as much information as possible (user guide, developer guide, etc.). Please bear in mind that the first release of the Store will be in June. BR, Javier ---------- Forwarded message ---------- From: Juanjo Hierro Date: 2013/5/13 Subject: [Fiware] URGENT action on FI-WARE GEi owners regarding webinars To: "fiware-wpl at lists.fi-ware.eu" , " fiware-wpa at lists.fi-ware.eu" , " fiware at lists.fi-ware.eu" Dear all, Still there are some FI-WARE GEis about which no date or timeslot has been proposed for running a webinars that UC projects in phase 2 will attend. Please note that execution of these webinars may be a relevant achievement to be reported in our 2nd year review. There may be some FI-WARE GEis for which a webinar is not feasible before actual delivery of release 2, but this is not arguable for all cases where a proposed date×lot is missing. In particular, I miss webinars on Cloud functions, at least for "Allocation of single VMs (image instances)", "Management of Blueprints" and "Allocation of Object Storage". Most probably these three may be merged in a single webinar. Please fill this before EOB today, because I will forward the available spreadsheet to the UC projects tomorrow. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/**FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/**groups/FIWARE-4239932 ______________________________**__ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/**disclaimer.aspx ______________________________**_________________ Fiware mailing list Fiware at lists.fi-ware.eu https://lists.fi-ware.eu/**listinfo/fiware -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From pabloa at tid.es Mon May 13 10:11:21 2013 From: pabloa at tid.es (PABLO AROZARENA LLOPIS) Date: Mon, 13 May 2013 08:11:21 +0000 Subject: [Fiware-apps] Fwd: [Fiware] URGENT action on FI-WARE GEi owners regarding webinars In-Reply-To: References: <5190963F.9060409@tid.es> Message-ID: <6ACFAF93FBAA354785593AEA98EFA6DE32FEA71A@EX10-MB2-MAD.hi.inet> Dear Javier, Koen and all, In fact, I had an action point to trigger the discussion about the business framework webinar. A main question is whether we go for separate webinars for each GE or just a combined one, including the Store, BM&BE and the RSS GEs. Personally I would go for a combined business framework webinar. I have also checked with Juanjo and he advises to organize just one session for the business framework webinar before the review, so we may choose a date in early June if that's ok for everyone. Koen, Javier, what do you think about this? Best regards, Pablo -- Pablo Arozarena Product Development and Innovation Telef?nica Digital Distrito Telef?nica, Edificio Oeste 1 - Planta 5 Ronda de la Comunicaci?n, s/n, 28050 Madrid, Spain Tlf: +34 91 4832866 De: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] En nombre de Javier Soriano (FI-UPM) Enviado el: lunes, 13 de mayo de 2013 9:48 Para: fiware-apps at lists.fi-ware.eu Asunto: [Fiware-apps] Fwd: [Fiware] URGENT action on FI-WARE GEi owners regarding webinars Dear Markus, dear all, Who is responsible for allocating the date/s for the "Business framework" webinar/s that will merge Store, RSS, etc.? With regard to the Store GE, we prefer to have the webinar as late as possible. This will allow us to have ready as much information as possible (user guide, developer guide, etc.). Please bear in mind that the first release of the Store will be in June. BR, Javier ---------- Forwarded message ---------- From: Juanjo Hierro > Date: 2013/5/13 Subject: [Fiware] URGENT action on FI-WARE GEi owners regarding webinars To: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, "fiware at lists.fi-ware.eu" > Dear all, Still there are some FI-WARE GEis about which no date or timeslot has been proposed for running a webinars that UC projects in phase 2 will attend. Please note that execution of these webinars may be a relevant achievement to be reported in our 2nd year review. There may be some FI-WARE GEis for which a webinar is not feasible before actual delivery of release 2, but this is not arguable for all cases where a proposed date×lot is missing. In particular, I miss webinars on Cloud functions, at least for "Allocation of single VMs (image instances)", "Management of Blueprints" and "Allocation of Object Storage". Most probably these three may be merged in a single webinar. Please fill this before EOB today, because I will forward the available spreadsheet to the UC projects tomorrow. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware -- [http://conwet.fi.upm.es/images/pieemailupm.png] ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Mon May 13 10:21:26 2013 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Mon, 13 May 2013 10:21:26 +0200 Subject: [Fiware-apps] Fwd: [Fiware] URGENT action on FI-WARE GEi owners regarding webinars In-Reply-To: <6ACFAF93FBAA354785593AEA98EFA6DE32FEA71A@EX10-MB2-MAD.hi.inet> References: <5190963F.9060409@tid.es> <6ACFAF93FBAA354785593AEA98EFA6DE32FEA71A@EX10-MB2-MAD.hi.inet> Message-ID: +1 Pablo. Javier 2013/5/13 PABLO AROZARENA LLOPIS > Dear Javier, Koen and all, > > > > In fact, I had an action point to trigger the discussion about the > business framework webinar. A main question is whether we go for separate > webinars for each GE or just a combined one, including the Store, BM&BE and > the RSS GEs. Personally I would go for a combined business framework > webinar. > > > > I have also checked with Juanjo and he advises to organize just one > session for the business framework webinar before the review, so we may > choose a date in early June if that?s ok for everyone. > > > > Koen, Javier, what do you think about this? > > > > Best regards, > > > > Pablo > > > > -- > *Pablo Arozarena > Product Dev**elopment and Innovation > Telef?nica Digital > *Distrito Telef?nica, Edificio Oeste 1 - Planta 5 > Ronda de la Comunicaci?n, s/n, 28050 Madrid, Spain > Tlf: +34 91 4832866** > > > > *De:* fiware-apps-bounces at lists.fi-ware.eu [mailto: > fiware-apps-bounces at lists.fi-ware.eu] *En nombre de *Javier Soriano > (FI-UPM) > *Enviado el:* lunes, 13 de mayo de 2013 9:48 > *Para:* fiware-apps at lists.fi-ware.eu > *Asunto:* [Fiware-apps] Fwd: [Fiware] URGENT action on FI-WARE GEi owners > regarding webinars > > > > Dear Markus, dear all, > > > > Who is responsible for allocating the date/s for the "Business framework" > webinar/s that will merge Store, RSS, etc.? > > > > With regard to the Store GE, we prefer to have the webinar as late as > possible. This will allow us to have ready as much information as possible > (user guide, developer guide, etc.). Please bear in mind that the first > release of the Store will be in June. > > > > BR, > > Javier > > ---------- Forwarded message ---------- > From: *Juanjo Hierro* > Date: 2013/5/13 > Subject: [Fiware] URGENT action on FI-WARE GEi owners regarding webinars > To: "fiware-wpl at lists.fi-ware.eu" , " > fiware-wpa at lists.fi-ware.eu" , " > fiware at lists.fi-ware.eu" > > > Dear all, > > Still there are some FI-WARE GEis about which no date or timeslot has > been proposed for running a webinars that UC projects in phase 2 will > attend. > > Please note that execution of these webinars may be a relevant > achievement to be reported in our 2nd year review. > > There may be some FI-WARE GEis for which a webinar is not feasible > before actual delivery of release 2, but this is not arguable for all > cases where a proposed date×lot is missing. In particular, I miss > webinars on Cloud functions, at least for "Allocation of single VMs > (image instances)", "Management of Blueprints" and "Allocation of Object > Storage". Most probably these three may be merged in a single webinar. > > Please fill this before EOB today, because I will forward the > available spreadsheet to the UC projects tomorrow. > > Cheers, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Coordinator > and Chief Architect > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware mailing list > Fiware at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware > > > > > > -- > > ------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From marco.ughetti at telecomitalia.it Mon May 13 17:23:48 2013 From: marco.ughetti at telecomitalia.it (Ughetti Marco) Date: Mon, 13 May 2013 17:23:48 +0200 Subject: [Fiware-apps] R: WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66461076885@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66461076885@DEWDFEMB11A.global.corp.sap> Message-ID: <51508CA9C4AE774DAC3FC6B8F0E5A5384728B9E85F@GRFMBX707BA020.griffon.local> Hi all, We have checked the content of the "Generic Enablers for Mediation" chapter and added a contribution to the chapter 4.4.7.4 As a matter of fact the latter relies on the contribution on composition and mashup GEs that should be placed in the same chapter before the mediation part. At least this is my understanding even if in the wiki page the order is the opposite Regards Marco ____________________ Telecom Italia Marco Ughetti Tilab & Global Consulting Services Platforms & Technology Evolution Services Platforms Innovation via G. Reiss Romoli, 274 - 10148 Torino +39 011228 5654 +39 331 6001596 Da: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] Per conto di Sandfuchs, Thorsten Inviato: marted? 7 maggio 2013 16:08 A: fiware-apps at lists.fi-ware.eu Oggetto: Re: [Fiware-apps] WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions Dear colleagues from WP3, Although trying to clarify this on the last wp3-meeting there seems to be a misunderstanding. WP11 needs input from your GE perspective on this and so far there was no submission from WP3 in a whole. We need to fix this and I count on your input. Please indicate to me until when you can finish this task and/or how you would propose to solve this and the related commutation to the WPL Juan. To make it more explicit was is needed I attached the document & outlined the tasks below. - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - 4.4.2. "generic enabler of the business Framework" => TID, UPM, iMinds E-IIS need to check and update their respective paragraphs and send corrective text or "OK" - 4.4.3. "Composition" => ATOS, DT, EAB, UPM needs updates reflecting the four major composition paradigmn, an updated graphic and related text (copy&paste can be used potentially from the architecture description) - 4.4.4. "Generic Enablers for Mediation" => THALES, TI need to check and update the complete chapter and send corrective text or "OK" - 4.4.6 "Business Canvas" -> @all contribute GE your specific input and perspective here - 4.4.7 and subchapters: Juan was only able to provide a blueprint for each sub chapter. You have to fill in for your GE: Benefits, Functions, Business and Stakeholders relationships, Value of FI functionalities o 4.4.7.2 "revenue sharing" ? TID o 4.4.7.4 Supporting service composition and crowd-sourcing ? UPM, ATOS, THALES, TI Thanks for all of your support, /Thorsten From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 25. April 2013 10:00 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] FW: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear colleagues, As probably not everybody is part of the WP11 exploitation list, I will distribute this information within this list as well. Action 3 applies to all industry partners: TID, SAP, THALES, TI, DT, EAB, ATOS, E-IIS, iMinds ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May Best, /Thorsten From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Mittwoch, 24. April 2013 19:40 To: fiware-exploitation at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan [cid:image001.png at 01CE4FFD.B0A2C2E0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE4FFD.B0A2C2E0] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan [cid:image001.png at 01CE4FFD.B0A2C2E0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE4FFD.B0A2C2E0] ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D11.2.2+Exploitation_Plan,_including_IPR_Managementv_M24v2404_FOR_WP3_PARTNER_TI_review.doc Type: application/msword Size: 4872704 bytes Desc: D11.2.2+Exploitation_Plan,_including_IPR_Managementv_M24v2404_FOR_WP3_PARTNER_TI_review.doc URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From thorsten.sandfuchs at sap.com Mon May 13 18:00:03 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 13 May 2013 16:00:03 +0000 Subject: [Fiware-apps] WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions In-Reply-To: <51508CA9C4AE774DAC3FC6B8F0E5A5384728B9E85F@GRFMBX707BA020.griffon.local> References: <2981E9D6242FCF47ADC9B5DBA5DFD66461076885@DEWDFEMB11A.global.corp.sap> <51508CA9C4AE774DAC3FC6B8F0E5A5384728B9E85F@GRFMBX707BA020.griffon.local> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461083980@DEWDFEMB11A.global.corp.sap> Hi Marco, Thanks for your contribution - I would even just add a complete subchapter about "Mediation" in the chapter 4.4.7 - e.g. "4.4.7.5 Supporting Interoperability with Mediation" - although it is formally part of the composition task, I think the mediator should be positioned like this, right? I can't find any changes to the chapter "4.4.4 Generic Enablers for Mediation". Therefore I would assume that you reviewed it and found it "OK" and all the relevant mediation cases: Data, Protocol and Process still would apply in the our/your current way of thinking. In the end this can be as well a chance to drop paragraphs which might disturb or blur our messaging. E.g. if you would focus on "Data mediation" - just to pick any of the Mediation paradigms, then you could now just make this more clearer in the document - it might be because of good reasons and in order to focus on one "relevant" Mediation part only. This would finally help the reviewers and in the end the general public understand better what we _actually_ provide - and this is - at least in my point of view - the exercise that we are currently going through with redefinition of this product vision as part of the exploitation deliverable: Focusing on the things that really did matter or will matter within the rest of the project. Thanks for your support! Best, /Thorsten From: Ughetti Marco [mailto:marco.ughetti at telecomitalia.it] Sent: Montag, 13. Mai 2013 17:24 To: Sandfuchs, Thorsten; fiware-apps at lists.fi-ware.eu Cc: Cappadona Davide (Guest) Subject: R: [Fiware-apps] WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions Hi all, We have checked the content of the "Generic Enablers for Mediation" chapter and added a contribution to the chapter 4.4.7.4 As a matter of fact the latter relies on the contribution on composition and mashup GEs that should be placed in the same chapter before the mediation part. At least this is my understanding even if in the wiki page the order is the opposite Regards Marco ____________________ Telecom Italia Marco Ughetti Tilab & Global Consulting Services Platforms & Technology Evolution Services Platforms Innovation via G. Reiss Romoli, 274 - 10148 Torino +39 011228 5654 +39 331 6001596 Da: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] Per conto di Sandfuchs, Thorsten Inviato: marted? 7 maggio 2013 16:08 A: fiware-apps at lists.fi-ware.eu Oggetto: Re: [Fiware-apps] WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions Dear colleagues from WP3, Although trying to clarify this on the last wp3-meeting there seems to be a misunderstanding. WP11 needs input from your GE perspective on this and so far there was no submission from WP3 in a whole. We need to fix this and I count on your input. Please indicate to me until when you can finish this task and/or how you would propose to solve this and the related commutation to the WPL Juan. To make it more explicit was is needed I attached the document & outlined the tasks below. - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - 4.4.2. "generic enabler of the business Framework" => TID, UPM, iMinds E-IIS need to check and update their respective paragraphs and send corrective text or "OK" - 4.4.3. "Composition" => ATOS, DT, EAB, UPM needs updates reflecting the four major composition paradigmn, an updated graphic and related text (copy&paste can be used potentially from the architecture description) - 4.4.4. "Generic Enablers for Mediation" => THALES, TI need to check and update the complete chapter and send corrective text or "OK" - 4.4.6 "Business Canvas" -> @all contribute GE your specific input and perspective here - 4.4.7 and subchapters: Juan was only able to provide a blueprint for each sub chapter. You have to fill in for your GE: Benefits, Functions, Business and Stakeholders relationships, Value of FI functionalities o 4.4.7.2 "revenue sharing" ? TID o 4.4.7.4 Supporting service composition and crowd-sourcing ? UPM, ATOS, THALES, TI Thanks for all of your support, /Thorsten From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 25. April 2013 10:00 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] FW: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear colleagues, As probably not everybody is part of the WP11 exploitation list, I will distribute this information within this list as well. Action 3 applies to all industry partners: TID, SAP, THALES, TI, DT, EAB, ATOS, E-IIS, iMinds ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May Best, /Thorsten From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Mittwoch, 24. April 2013 19:40 To: fiware-exploitation at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 677 bytes Desc: image003.gif URL: From marco.ughetti at telecomitalia.it Tue May 14 10:51:59 2013 From: marco.ughetti at telecomitalia.it (Ughetti Marco) Date: Tue, 14 May 2013 10:51:59 +0200 Subject: [Fiware-apps] R: WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66461083980@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66461076885@DEWDFEMB11A.global.corp.sap> <51508CA9C4AE774DAC3FC6B8F0E5A5384728B9E85F@GRFMBX707BA020.griffon.local> <2981E9D6242FCF47ADC9B5DBA5DFD66461083980@DEWDFEMB11A.global.corp.sap> Message-ID: <51508CA9C4AE774DAC3FC6B8F0E5A5384728B9E9C5@GRFMBX707BA020.griffon.local> Hi Thorsten, the chapter 4.4.4. is OK for us even if our Mediator implementation is more focused on Data and protocol mediation than process mediation. My understanding is that this chapter should list all mediator capabilities not only the ones implemented by TI so we have to check with THALES but probably we can drop the paragraph on process mediation for instance because it is not our focus and probably neither their focus. In my understanding they added features related to dynamic mediation tasks and semantics Only to check if I well understood. Are you going to move the paragraph 4.4.4. to 4.4.7.5 ? I have no issue about that Marco ____________________ Telecom Italia Marco Ughetti Tilab & Global Consulting Services Platforms & Technology Evolution Services Platforms Innovation via G. Reiss Romoli, 274 - 10148 Torino +39 011228 5654 +39 331 6001596 Da: Sandfuchs, Thorsten [mailto:thorsten.sandfuchs at sap.com] Inviato: luned? 13 maggio 2013 18:00 A: Ughetti Marco; fiware-apps at lists.fi-ware.eu Cc: Cappadona Davide (Guest) Oggetto: RE: [Fiware-apps] WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions Hi Marco, Thanks for your contribution - I would even just add a complete subchapter about "Mediation" in the chapter 4.4.7 - e.g. "4.4.7.5 Supporting Interoperability with Mediation" - although it is formally part of the composition task, I think the mediator should be positioned like this, right? I can't find any changes to the chapter "4.4.4 Generic Enablers for Mediation". Therefore I would assume that you reviewed it and found it "OK" and all the relevant mediation cases: Data, Protocol and Process still would apply in the our/your current way of thinking. In the end this can be as well a chance to drop paragraphs which might disturb or blur our messaging. E.g. if you would focus on "Data mediation" - just to pick any of the Mediation paradigms, then you could now just make this more clearer in the document - it might be because of good reasons and in order to focus on one "relevant" Mediation part only. This would finally help the reviewers and in the end the general public understand better what we _actually_ provide - and this is - at least in my point of view - the exercise that we are currently going through with redefinition of this product vision as part of the exploitation deliverable: Focusing on the things that really did matter or will matter within the rest of the project. Thanks for your support! Best, /Thorsten From: Ughetti Marco [mailto:marco.ughetti at telecomitalia.it] Sent: Montag, 13. Mai 2013 17:24 To: Sandfuchs, Thorsten; fiware-apps at lists.fi-ware.eu Cc: Cappadona Davide (Guest) Subject: R: [Fiware-apps] WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions Hi all, We have checked the content of the "Generic Enablers for Mediation" chapter and added a contribution to the chapter 4.4.7.4 As a matter of fact the latter relies on the contribution on composition and mashup GEs that should be placed in the same chapter before the mediation part. At least this is my understanding even if in the wiki page the order is the opposite Regards Marco ____________________ Telecom Italia Marco Ughetti Tilab & Global Consulting Services Platforms & Technology Evolution Services Platforms Innovation via G. Reiss Romoli, 274 - 10148 Torino +39 011228 5654 +39 331 6001596 Da: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] Per conto di Sandfuchs, Thorsten Inviato: marted? 7 maggio 2013 16:08 A: fiware-apps at lists.fi-ware.eu Oggetto: Re: [Fiware-apps] WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions Dear colleagues from WP3, Although trying to clarify this on the last wp3-meeting there seems to be a misunderstanding. WP11 needs input from your GE perspective on this and so far there was no submission from WP3 in a whole. We need to fix this and I count on your input. Please indicate to me until when you can finish this task and/or how you would propose to solve this and the related commutation to the WPL Juan. To make it more explicit was is needed I attached the document & outlined the tasks below. - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - 4.4.2. "generic enabler of the business Framework" => TID, UPM, iMinds E-IIS need to check and update their respective paragraphs and send corrective text or "OK" - 4.4.3. "Composition" => ATOS, DT, EAB, UPM needs updates reflecting the four major composition paradigmn, an updated graphic and related text (copy&paste can be used potentially from the architecture description) - 4.4.4. "Generic Enablers for Mediation" => THALES, TI need to check and update the complete chapter and send corrective text or "OK" - 4.4.6 "Business Canvas" -> @all contribute GE your specific input and perspective here - 4.4.7 and subchapters: Juan was only able to provide a blueprint for each sub chapter. You have to fill in for your GE: Benefits, Functions, Business and Stakeholders relationships, Value of FI functionalities o 4.4.7.2 "revenue sharing" ? TID o 4.4.7.4 Supporting service composition and crowd-sourcing ? UPM, ATOS, THALES, TI Thanks for all of your support, /Thorsten From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 25. April 2013 10:00 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] FW: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear colleagues, As probably not everybody is part of the WP11 exploitation list, I will distribute this information within this list as well. Action 3 applies to all industry partners: TID, SAP, THALES, TI, DT, EAB, ATOS, E-IIS, iMinds ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May Best, /Thorsten From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Mittwoch, 24. April 2013 19:40 To: fiware-exploitation at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan [cid:image001.png at 01CE5090.4093BDE0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE5090.4093BDE0] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan [cid:image001.png at 01CE5090.4093BDE0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE5090.4093BDE0] ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image003.gif at 01CE5090.4093BDE0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 677 bytes Desc: image003.gif URL: From thorsten.sandfuchs at sap.com Tue May 14 14:26:25 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 14 May 2013 12:26:25 +0000 Subject: [Fiware-apps] please integrated the Open Spec review for your GE in the wiki Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610845B3@DEWDFEMB11A.global.corp.sap> Dear colleagues, Please integrate the open spec reviews of your GE directly in the wiki and let us know once you are done - please do this ASAP as we want to submit the open spec deliverable D.3.1.2 as soon as possible (e.g. Thursday this week together with all the other software related deliverables). We will then generate the WP3 open specification for final submission Repository https://forge.fi-ware.eu/docman/view.php/27/2205/D312_WP3_v2_generated_rev_Repository.docx Marketplace https://forge.fi-ware.eu/docman/view.php/27/2252/D312_WP3_v2_generated_MarketPlace.docx Registry https://forge.fi-ware.eu/docman/view.php/27/2254/D312_WP3_v2_generated_Registry.docx Application Mashup - Wirecloud https://forge.fi-ware.eu/docman/view.php/27/2242/D312_WP3_v2_generated_AppMashup.docx Service Mashup - Mashup Factory https://forge.fi-ware.eu/docman/view.php/27/2280/D312_WP3_v2_generated-1_cmntVJ.docx Light Semantic Composition https://forge.fi-ware.eu/docman/view.php/27/2199/D312_WP3_v2_generated_AppsLWSemanticEnabledComposition.docx Mediator https://forge.fi-ware.eu/docman/view.php/27/2200/D312_WP3_v2_generated_review.docx Revenue Sharing https://forge.fi-ware.eu/docman/view.php/27/2275/LM+-+1+-+D312_WP3_v2_generated.docx Store https://forge.fi-ware.eu/docman/view.php/27/2272/D312_WP3_v2_generated_Store.docx Reference was: https://docs.google.com/spreadsheet/ccc?key=0AmxBgS-lWT4vdHYxYTVOZ3FrNEprZXRBZk80TGRLMGc#gid=0 Best regards, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Tue May 14 18:31:40 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 14 May 2013 16:31:40 +0000 Subject: [Fiware-apps] WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66461076885@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66461076885@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461084F7C@DEWDFEMB11A.global.corp.sap> Dear colleagues, I integrated my current draft and the contribution by Marco for your further consideration. I left it on "track changes" so that you can find the changes performed more easier. INPUT missing (details in the document): - Service composition - Revenue shareing - Business framework Overall the business canvas is as well not updated in this version so far. Thanks for any contribution. /Thorsten From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Dienstag, 7. Mai 2013 16:08 To: fiware-apps at lists.fi-ware.eu Subject: Re: [Fiware-apps] WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions Dear colleagues from WP3, Although trying to clarify this on the last wp3-meeting there seems to be a misunderstanding. WP11 needs input from your GE perspective on this and so far there was no submission from WP3 in a whole. We need to fix this and I count on your input. Please indicate to me until when you can finish this task and/or how you would propose to solve this and the related commutation to the WPL Juan. To make it more explicit was is needed I attached the document & outlined the tasks below. - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - 4.4.2. "generic enabler of the business Framework" => TID, UPM, iMinds E-IIS need to check and update their respective paragraphs and send corrective text or "OK" - 4.4.3. "Composition" => ATOS, DT, EAB, UPM needs updates reflecting the four major composition paradigmn, an updated graphic and related text (copy&paste can be used potentially from the architecture description) - 4.4.4. "Generic Enablers for Mediation" => THALES, TI need to check and update the complete chapter and send corrective text or "OK" - 4.4.6 "Business Canvas" -> @all contribute GE your specific input and perspective here - 4.4.7 and subchapters: Juan was only able to provide a blueprint for each sub chapter. You have to fill in for your GE: Benefits, Functions, Business and Stakeholders relationships, Value of FI functionalities o 4.4.7.2 "revenue sharing" ? TID o 4.4.7.4 Supporting service composition and crowd-sourcing ? UPM, ATOS, THALES, TI Thanks for all of your support, /Thorsten From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 25. April 2013 10:00 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] FW: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear colleagues, As probably not everybody is part of the WP11 exploitation list, I will distribute this information within this list as well. Action 3 applies to all industry partners: TID, SAP, THALES, TI, DT, EAB, ATOS, E-IIS, iMinds ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May Best, /Thorsten From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Mittwoch, 24. April 2013 19:40 To: fiware-exploitation at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D11.2.2+Exploitation_Plan,_including_IPR_Managementv_M24v2404_FOR_WP3_PARTNER_v2.doc Type: application/msword Size: 4892672 bytes Desc: D11.2.2+Exploitation_Plan,_including_IPR_Managementv_M24v2404_FOR_WP3_PARTNER_v2.doc URL: From thorsten.sandfuchs at sap.com Wed May 15 08:10:25 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 15 May 2013 06:10:25 +0000 Subject: [Fiware-apps] software related deliverables ready for submission? In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66461084CDB@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66461084CDB@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461086816@DEWDFEMB11A.global.corp.sap> Dear colleagues, I know there are a lot of parallel tracks, so we should try to close the things that we actually can as soon as possible. Our current assumption is that the EC will not accept deliverables that are delivered past the 17th of May (Friday this week) - therefore we should really focus on finalizing everything as good and as complete as we can until then. We will send out the current status and open points one by one for the pending deliverables to make this a bit transparent. The first one is the easiest one: software related deliverables - as we already invested into this to prepare this thoroughly Please have again a final look if we complied it correctly (by directly following the front page links). We introduced relevant "executive summaries" There are still some open points (that we currently see) from THALES (software delivery itself), ATOS, TI and SAP (user and programmer guide) - if you have additional open points, let us know! Please veto ASAP, but until Thursday noon the latest, if you think we should not submit this. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Deliverables_cockpit#WP3 [cid:image001.png at 01CE50C7.B689C800] -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 22669 bytes Desc: image001.png URL: From thorsten.sandfuchs at sap.com Wed May 15 09:26:01 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 15 May 2013 07:26:01 +0000 Subject: [Fiware-apps] periodic report - current status Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461086A22@DEWDFEMB11A.global.corp.sap> Dear colleagues, as said: we will send out the current status and open points one by one for the pending deliverables to make this a bit transparent. The second one is another "easier" one: periodic report - as we as well invested into this to prepare this thoroughly. Find below the reference to our submission. I got more input from E-IIS on their part which will be part of the final version - did all of you take a second look on our submission or want to change something? Status: submitted to TID for integration with the other chapters Next steps: TID resending it to us, we will distribute and make a second round asking for partner contributions and your deltas. SAP will introduce final statements touching on the overall resource consumption (section at the bottom). Then: submission Given the time frame of Javier, there seems to be another schedule & the delivery is not planned for Friday, this week. Best, /Thorsten From: Sandfuchs, Thorsten Sent: Freitag, 10. Mai 2013 15:04 To: 'JAVIER DE PEDRO SANCHEZ'; 'subsidies at tid.es' Cc: fiware-apps at lists.fi-ware.eu; 'Heller, Markus' Subject: SUBMISSION - WP3 - RE: FI-WARE: Periodic Report - M13 - M24 Dear javier, Find the periodic report out of the WP3 for consolidation with other chapters, attached. Sorry for the late submission Please send the integrated version back to us in order to have an internal review prior to submission and in order to allow us to integrate the final evaluations. The submitted document does not contain some rationals given by the partners, as the numbers were not final so far. We are still missing (although pushing hard) the input from some partners, this will be integrated in the final version, together with the subsuming evaluations. Best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of JAVIER DE PEDRO SANCHEZ Sent: Montag, 15. April 2013 23:07 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: subsidies at tid.es Subject: [Fiware-wpa] FI-WARE: Periodic Report - M13 - M24 Importance: High Dear all As you know we have to deliver the Periodic Report which has to give an overview of the second year of the project (months from M13 (May12) to M24 (Apr13)). I will kindly ask you in another particularized e-mail to update as WPL the information about your WP. The schedule is the following: 1. First request of information to WPL with estimated effort per partner: April 15th, 2013 2. Period to request each WPL to each involved partner its contribution to WP: April 16th, 2013 - Apr 19th, 2013 3. Integration of received information from by each WPL: April 22nd, 2013 - May 5th, 2013 4. WPL send first version of his updated report to Coordinator (subsidies at tid.es): May 6th, 2013 5. Coordinator asks to each partner to update its current effort: April 30th, 2013 6. Each partner sends its current effort according FORM-C 2: May 1st, 2013 - May 10th, 2013 7. Coordinator sends updated data of effort to each WPL: May 15th, 2013 8. Updating of the second version of each report by each WPL: May 16th, 2013 - May 17th, 2013 9. WPL sends final version of his updated report to Coordinator (subsidies at tid.es): May 17th, 2013 10. Integrating and revision by Coordinator: May 20th, 2013 - May 24th, 2013 11. Coordinator sends the Periodic Report to Project Officer: May 28th, 2013 12. Review: June 10th, 2013 At last but not least, please, I kindly ask you to follow the template in order to have a homogeneous report as a team. In the last review report they said: [cid:image001.jpg at 01CE4D8E.DA044210] Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 39114 bytes Desc: image001.jpg URL: From thorsten.sandfuchs at sap.com Wed May 15 10:07:59 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 15 May 2013 08:07:59 +0000 Subject: [Fiware-apps] WP11 contributions - current status Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461086BD3@DEWDFEMB11A.global.corp.sap> Dear colleagues, as said: we will send out the current status and open points one by one for the pending deliverables to make this a bit transparent. The third one is a bit more complex: contributions towards exploitation, market analysis and IPR management 1. Market analysis - we reviewed it internally at SAP and provided feedback for juan (basically the current report focuses very much on "apps" in particular "mobile apps", "mobile app stores" and the ecosystem design around this. In our opinion this merely can be a rough guidance and not the market that "we" as WP3/FI-WARE are competing with. No: we are not building another mobile platform - which could be implied, reading the text. Let's see on how Juan reacts on this. Our comments: https://sapmats-de.sap-ag.de/download/download.cgi?id=C7MVG0VUQCFXC2J3G8YHECXPTF1U3949STYLV8DA10FZ4SJ1C3 Password: Juan2013 2. Exploitation plan of industry partners - this one was distributed directly. DT should have submitted something, iMinds should have synched with Juan directly on the content, SAP did update it's planning. Other industry partners: not tracked/no information. 3. Exploitation plan of FI-WARE (WP3 part) - Identify the main Generic Enablers+ FI-WARE Instances with most market potential a. 4.4 Product vision refinement: was send around yesterday contributed by TI - pending input from composition, revenue shareing and business framework partners b. 4.4.5 Business canvas: SAP prepared a draft which was so far not send around c. 4.4.6 Business Analysis: SAP and TI prepared input - pending input like in a) ? Goal should be to rather simplify and concentrate on the relevant parts, in order to let the reviewers know: we are focused on the relevant exploitation work and refrain from overcommitting. Find below the references. Status: pending integration of part 3 by many partners Next steps: submission to Juan, sections in 4.4.5 and 4.4.6 without contributions will be dropped I was talking to Juan: he is not planning to deliver this Friday, but needs our input by then, the latest during the weekend for integration in the final submission. [cid:image004.jpg at 01CE5154.132EF3F0] Best, /Thorsten From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 25. April 2013 10:00 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] FW: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear colleagues, As probably not everybody is part of the WP11 exploitation list, I will distribute this information within this list as well. Action 3 applies to all industry partners: TID, SAP, THALES, TI, DT, EAB, ATOS, E-IIS, iMinds ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May Best, /Thorsten From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: Mittwoch, 24. April 2013 19:40 To: fiware-exploitation at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 endeavours 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 informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico 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 ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 677 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 21117 bytes Desc: image004.jpg URL: From thorsten.sandfuchs at sap.com Wed May 15 10:27:29 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 15 May 2013 08:27:29 +0000 Subject: [Fiware-apps] WP12 collaboration & communication - current status Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461086CA6@DEWDFEMB11A.global.corp.sap> Dear colleagues, as said: we will send out the current status and open points one by one for the pending deliverables to make this a bit transparent. The forth one is another "easier" one: collaboration & communication - as we think this is ready for submission and TID is currently compiling this. Find below the reference to our submission. Status: TID is compiling the to be delivered document Next steps: TID submitting it (I don't think that we will - unless we push for it - see this deliverable for a final internal review) In general I would still encourage contributions, if you think you forgot something - but then: please let Carlos know directly. The section which I found in a quick review a bit "weak" is the section on our technical meetings within FI-PPP http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Collaboration_activities#Technical_Meetings_and_Actions_with_Specific_FI-PPP_projects It seem to not reflect the engagement that we actually had during the past year (especially as we in WP3 e.g. had that many PoC demonstrators) - I therefore added a text and asked carlos on how to proceed. In general: if you think you can provide more "engaged" and detailed information on how your interaction with the use cases were - this is the right place. Best, /Thorsten [cid:image001.jpg at 01CE5156.CCB2F2C0] From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Heller, Markus Sent: Mittwoch, 24. April 2013 18:36 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] WP3: Reminder Input Dissemination / Collaboration Activities Dear WP3 colleagues, I would like to remind you to send your input Dissemination / Collaboration Activities to TID/Carlos directly (if not done so). (I would appreciate if you could signal briefly to me if you did that, if possible, but not urgently needed for this...) Second, the entries are to be put (also) in the WIKI in these places (but clearly mail to Carlos is needed also, as far as I know): http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Dissemination_activities http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Collaboration_activities http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Communication,_Collaboration_and_Dissemination Best wishes Markus --- a) Citation from Meeting Minutes WPL/WPA Meeting : "AP-T1) WPl to collect their chapter contributions in terms of papers, technical conferences and workshops realized since the last review (Nov 2012). Format is: Conference name, Date/Place, Contribution Title, Contributors, Status, Observations (comments on relevance, benefits for FI-WARE/FI-PPP). Later on we need to update this in the Wiki but I need your e-mails anyway. Deadline is April 25th." b) Citation from Carlos' mail from 22.4.2013: "Let me remind as well that we are expecting a description of your dissemination actions in the last period before April 25th, as described in the Wpl conf.call minutes. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 20377 bytes Desc: image001.jpg URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From thorsten.sandfuchs at sap.com Wed May 15 11:03:47 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 15 May 2013 09:03:47 +0000 Subject: [Fiware-apps] WP11 business canvas first shot Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461086DEB@DEWDFEMB11A.global.corp.sap> Dear colleagues, The business canvas in WP11 follows the methodology outlined here: http://www.businessmodelgeneration.com/book http://www.businessmodelgeneration.com/downloads/businessmodelgeneration_preview.pdf It should provide a holistic overview on complete ?package? that our work package is bringing forward. We started gathering input ? given the main dimensions ? and implying what we already know of your components. Please contribute. We will see on how to layout this finally in the ?table? format ? but the original methodology does imply sticky-notes ? so there should be enough space (per definition) to encorporate this in the final document ? if not we will have to layout a one pager. Anyway let?s first focus on the content: the current business canvas as provided in the document is rubbish ? it was only an initial copy&paste ? so we have to completely redo it with the focus on our complete ?offering?. We for sure missed something, so please: feel free to add you thoughts ? Best, /Thorsten Key Partners - Application service providers and value added service providers - Integrators - Marketplace & store providers - Software & services companies Key Activities - Enable others to explore new business models and business opportunities within an open service ecosystem (the future internet) - Build ?Community of practice? around internet of services and service descriptions (USDL) - Enable 3rd parties to bootstrap ecosystem around services - 3rd parties should adopt and customize contribute to business relevant technologies. - Provide enabling technology as open source and commercially exploitable - Enable new revenue streams and business model interactions in complex environments Key Resources - Design of an open service ecosystem platform for a high degree of automation (provided blueprint with OpenSpecs & Architecture and universal service description paradigm) - Business framework (marketplace, store, revenue, business elements and models) - Composition (application-mashup, ligthsemantic-mashup, service composition and service mashup) - Mediation (gateway) Cost Structure - Core enabling technology are free to use and some provided with BSD-like licenses (which enables commercial exploitation) - Further cost depends on the party adopting the core technology and operating it within its legal boundaries Value Proposition - Universal service description paradigm lowers cost of onboarding, interaction and execution of the complete value chain - Core technologies freely available (easy onboarding, low entry barrier) - Open service ecosystem architecture, open APIs, generalized components freely available - Lower cost in matchmaking and collaboration activities between the ecosystem participants - Increased reach and provisioning of services across business domains - Increased transparency and more - Enablement of semi-automated service trading environment/ecosystem lowers TCD and TCO for involved parties - Enablement of new cross domain business models increases revenue - New opportunities for co-value creation with joint developments and customer-tailored service delivery - Enablement of a ?game of many? where everybody gets his fair share - Core value is provided within the ecosystem & the related business transactions - Customer Relationships - Existing partner ecosystem of the industry partners - Connection towards academia in relation to service description paradigm - FI-PPP use case projects and affiliates - 3rd parties (outside FI-PPP) Channels - ?Web? channel: Enablement of self-serviced on-boarding via publicly available material (wiki, website, forge ?) - Direct channel: o interactions between FI-WARE partners, FI-PPP consortium (see collaboration wiki) o Interaction with 3rd parties o Contributions towards open innovation lab planned and in line with open source strategy - Research channel: related research projects and programs (see collaboration wiki) Customer Segments - General paradigm acts cross business segments ? some initial customer segments which currently engaged more deeply are o Transport & logistics o Smart cities o Application mashup providers Revenue Streams - Allows various business models as enabling technology depending on the business strategy oft he adopting companies -- Thorsten Sandfuchs SAP AG Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Wed May 15 11:42:32 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 15 May 2013 09:42:32 +0000 Subject: [Fiware-apps] WP3 Open Spec submission - current status Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461086F23@DEWDFEMB11A.global.corp.sap> Dear colleagues, as said: we will send out the current status and open points one by one for the pending deliverables to make this a bit transparent. The 5th one is another "easier" one: open spec - it is already know quite well within this week. Current status: waiting for patners to signal their readiness and integration of the reviewers comment Next steps: compilation of the deliverable and upload it for the cockpit - then signal TID that we would be ready for delivery. THIS one we should as well target to deliver this week. Any concerns, or vetos, just let me know. Best, /Thorsten [cid:image001.png at 01CE515E.3EBC0C10] From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Dienstag, 14. Mai 2013 14:26 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] please integrated the Open Spec review for your GE in the wiki Dear colleagues, Please integrate the open spec reviews of your GE directly in the wiki and let us know once you are done - please do this ASAP as we want to submit the open spec deliverable D.3.1.2 as soon as possible (e.g. Thursday this week together with all the other software related deliverables). We will then generate the WP3 open specification for final submission Repository https://forge.fi-ware.eu/docman/view.php/27/2205/D312_WP3_v2_generated_rev_Repository.docx Marketplace https://forge.fi-ware.eu/docman/view.php/27/2252/D312_WP3_v2_generated_MarketPlace.docx Registry https://forge.fi-ware.eu/docman/view.php/27/2254/D312_WP3_v2_generated_Registry.docx Application Mashup - Wirecloud https://forge.fi-ware.eu/docman/view.php/27/2242/D312_WP3_v2_generated_AppMashup.docx Service Mashup - Mashup Factory https://forge.fi-ware.eu/docman/view.php/27/2280/D312_WP3_v2_generated-1_cmntVJ.docx Light Semantic Composition https://forge.fi-ware.eu/docman/view.php/27/2199/D312_WP3_v2_generated_AppsLWSemanticEnabledComposition.docx Mediator https://forge.fi-ware.eu/docman/view.php/27/2200/D312_WP3_v2_generated_review.docx Revenue Sharing https://forge.fi-ware.eu/docman/view.php/27/2275/LM+-+1+-+D312_WP3_v2_generated.docx Store https://forge.fi-ware.eu/docman/view.php/27/2272/D312_WP3_v2_generated_Store.docx Reference was: https://docs.google.com/spreadsheet/ccc?key=0AmxBgS-lWT4vdHYxYTVOZ3FrNEprZXRBZk80TGRLMGc#gid=0 Best regards, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10753 bytes Desc: image001.png URL: From thorsten.sandfuchs at sap.com Wed May 15 15:21:02 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 15 May 2013 13:21:02 +0000 Subject: [Fiware-apps] WP2 contributions - current status Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461087622@DEWDFEMB11A.global.corp.sap> Dear colleagues, as said: we will send out the current status and open points one by one for the pending deliverables to make this a bit transparent. The 6th one is a bit more complex: contributions towards WP2 (global technical activities) 1. Architecture Document - this is blocked by TID for internal review and pending final submission (prior to this TID promised to send it back one time to us) 2. 3rd party innovation enablement - the work and coordination of this has not been started from within the WPL/WPA board 3. State of the art analysis (as markus is today out of office, I might not have the real "current" status) a. Missing contribution from: SAP, UPM, ATOS b. Contributing partners: TI, TID c. Next steps: consolidation and submission to TID, then review, then refinement, then final submission 4. D.2.4.2 Technical Roadmap - (not listed down below, but resubmission planned for the next review) a. Pending contribution from: iMinds, TID b. Everybody else did contribute and we think their status is up-to-date c. Next steps: waiting for your signals when you plan to finish this, then letting TID know 5. "white paper"/Livedemostrator/"product vision update" - (not listed below) a. Reference: checkpoint list of 4th review (checkpoint 1) b. Currently the content is still under negotiation in WPL/WPA meeting - there is a high likelihood that we target reuse of the WP11 product vision updates (chapter 4.4) for this, but no final decision. c. There is some traction from within the liveDemostrator wiki pages - but I personally wouldn't know if this will be consolidated and ready for the review d. Next steps: hopefully the next Monday session will shed a light on this. [cid:image001.jpg at 01CE517F.CEA158A0] [cid:image002.jpg at 01CE517F.CEA158A0] Best, /Thorsten -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 26980 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 35407 bytes Desc: image002.jpg URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From thorsten.sandfuchs at sap.com Thu May 16 15:09:46 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 16 May 2013 13:09:46 +0000 Subject: [Fiware-apps] software related deliverables ready for submission? In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66461086816@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66461084CDB@DEWDFEMB11A.global.corp.sap> <2981E9D6242FCF47ADC9B5DBA5DFD66461086816@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461089565@DEWDFEMB11A.global.corp.sap> Dear colleagues, We generated now the pre-final set of documents - although we didn't receive an official "GO" from TID - but I think we can't wait for that for our final internal review. Please find our M24 deliverable for WP3 in the following link https://sapmats-de.sap-ag.de/download/download.cgi?id=FAI0BWG41AA4CQCBALNNJ6I21RWAL1UDB6ZFHGSRVLL6KB7O08 pass: Fiware2013 You will download a rar-file with all of the docs on this link. The rar file does as well integrate the open specifications. Please veto again until tomorrow, Friday, 17. Mai 2013 10:00 a.m. if you think we did something wrong or you need more time to edit last changes. Everything what is edited after Friday, 17. Mai 2013, 10:00 a.m. will most probably not go for to the final submission. Markus will have as well a final review and might approach you with questions or change request. In the end we will then send this to TID for final submission ASAP. So there might be still road blockers ahead, but so far It seems that we can manage to submit this to the EC by the end of this week. Thanks for all of your support in the matter & best regards, /Thorsten From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Mittwoch, 15. Mai 2013 08:10 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] software related deliverables ready for submission? Dear colleagues, I know there are a lot of parallel tracks, so we should try to close the things that we actually can as soon as possible. Our current assumption is that the EC will not accept deliverables that are delivered past the 17th of May (Friday this week) - therefore we should really focus on finalizing everything as good and as complete as we can until then. We will send out the current status and open points one by one for the pending deliverables to make this a bit transparent. The first one is the easiest one: software related deliverables - as we already invested into this to prepare this thoroughly Please have again a final look if we complied it correctly (by directly following the front page links). We introduced relevant "executive summaries" There are still some open points (that we currently see) from THALES (software delivery itself), ATOS, TI and SAP (user and programmer guide) - if you have additional open points, let us know! Please veto ASAP, but until Thursday noon the latest, if you think we should not submit this. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Deliverables_cockpit#WP3 [cid:image001.png at 01CE5245.C5EBA960] -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 22669 bytes Desc: image001.png URL: From thorsten.sandfuchs at sap.com Thu May 16 15:18:31 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 16 May 2013 13:18:31 +0000 Subject: [Fiware-apps] WP3 Open Spec submission - current status In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66461086F23@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66461086F23@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610895D7@DEWDFEMB11A.global.corp.sap> Dear colleagues, Like in my mail before, we compiled the _current snapshot_ of open specs as well in the last rar-file. following link https://sapmats-de.sap-ag.de/download/download.cgi?id=FAI0BWG41AA4CQCBALNNJ6I21RWAL1UDB6ZFHGSRVLL6KB7O08 pass: Fiware2013 With the delivery this is a bit different here - so far I didn't see much "reviewer" comments being addressed within the wiki. So we will take this and the decision on whether we will submit this within this week to our WP3 call on Friday at 13:00-14:00 Please familiarize yourself with this and try to assess if you think you have blocking reviews which require more time to integrate or if the reviews, provided by other chapters would not be blocking the final submission. Please as well try to incorporate as much feedback as possible directly to the wiki - only then the internal reviews make sense and finally the overall quality does improve. Personally I think there might a chance that we submit firstly in time (by the end of this week) and resubmit shortly prior to the review, if we would have major changes coming out of the reviews - or e.g. if BEMES would have been able to finalize its contributions by then. Thanks in advance for your consideration & providing feedback to this plan & best regards, /Thorsten From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Mittwoch, 15. Mai 2013 11:43 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] WP3 Open Spec submission - current status Dear colleagues, as said: we will send out the current status and open points one by one for the pending deliverables to make this a bit transparent. The 5th one is another "easier" one: open spec - it is already know quite well within this week. Current status: waiting for patners to signal their readiness and integration of the reviewers comment Next steps: compilation of the deliverable and upload it for the cockpit - then signal TID that we would be ready for delivery. THIS one we should as well target to deliver this week. Any concerns, or vetos, just let me know. Best, /Thorsten [cid:image001.png at 01CE5248.8C7CDFC0] From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Dienstag, 14. Mai 2013 14:26 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] please integrated the Open Spec review for your GE in the wiki Dear colleagues, Please integrate the open spec reviews of your GE directly in the wiki and let us know once you are done - please do this ASAP as we want to submit the open spec deliverable D.3.1.2 as soon as possible (e.g. Thursday this week together with all the other software related deliverables). We will then generate the WP3 open specification for final submission Repository https://forge.fi-ware.eu/docman/view.php/27/2205/D312_WP3_v2_generated_rev_Repository.docx Marketplace https://forge.fi-ware.eu/docman/view.php/27/2252/D312_WP3_v2_generated_MarketPlace.docx Registry https://forge.fi-ware.eu/docman/view.php/27/2254/D312_WP3_v2_generated_Registry.docx Application Mashup - Wirecloud https://forge.fi-ware.eu/docman/view.php/27/2242/D312_WP3_v2_generated_AppMashup.docx Service Mashup - Mashup Factory https://forge.fi-ware.eu/docman/view.php/27/2280/D312_WP3_v2_generated-1_cmntVJ.docx Light Semantic Composition https://forge.fi-ware.eu/docman/view.php/27/2199/D312_WP3_v2_generated_AppsLWSemanticEnabledComposition.docx Mediator https://forge.fi-ware.eu/docman/view.php/27/2200/D312_WP3_v2_generated_review.docx Revenue Sharing https://forge.fi-ware.eu/docman/view.php/27/2275/LM+-+1+-+D312_WP3_v2_generated.docx Store https://forge.fi-ware.eu/docman/view.php/27/2272/D312_WP3_v2_generated_Store.docx Reference was: https://docs.google.com/spreadsheet/ccc?key=0AmxBgS-lWT4vdHYxYTVOZ3FrNEprZXRBZk80TGRLMGc#gid=0 Best regards, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10753 bytes Desc: image001.png URL: From thorsten.sandfuchs at sap.com Fri May 17 10:20:05 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 17 May 2013 08:20:05 +0000 Subject: [Fiware-apps] FI-WARE: WP3 Call In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6646101F278@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD6646101F278@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646108AADF@DEWDFEMB11A.global.corp.sap> Please be reminded on the weekly WP3 call, which takes place today (off the usual schedule). The call takes place from 13:00 until 14:00 CET with the dialins provided below by Markus. Looking forward to see/hear you all there. Thanks, /Thorsten -----Original Appointment----- From: Heller, Markus [mailto:markus.heller at sap.com] Sent: Donnerstag, 25. April 2013 23:18 To: Heller, Markus; 'fiware-apps at lists.fi-ware.eu'; 'Tim.Jonischkat at paluno.uni-due.de'; PABLO AROZARENA LLOPIS; Froese, Andreas Cc: Klein, Andreas; Leidig, Torsten Subject: [Fiware-apps] FI-WARE: WP3 Call Where: SAP Connect from Markus Hi, I am out of office on Thursday in Brussels. Therefore I move to Friday as exception. Best wishes Markus -- Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call, please use the dial-in info below. Please notify me if you experience dial-in problems with my call or if you miss a dial-in numbers for your country and I will see what I can do to add one. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Blackberry Austria, Vienna : +431253021750 tel:+431253021750,,4211563470# Belgium, Brussels : +3224040657 tel:+3224040657,,4211563470# Czech Republic, Prague : +420228882890 tel:+420228882890,,4211563470# Finland, Helsinki : +358923101631 tel:+358923101631,,4211563470# France, Paris : +33170701777 tel:+33170701777,,4211563470# Germany, Frankfurt : +4969222210764 tel:+4969222210764,,4211563470# Germany, Munich : +4989710424682 tel:+4989710424682,,4211563470# Ireland, Dublin : +35312476192 tel:+35312476192,,4211563470# Israel, Tel Aviv : +97237630750 tel:+97237630750,,4211563470# Italy, Milan : +390236009839 tel:+390236009839,,4211563470# Italy, Rome : +390645236623 tel:+390645236623,,4211563470# Luxembourg, Luxembourg : +35224871454 tel:+35224871454,,4211563470# Netherlands, Amsterdam : +31207168291 tel:+31207168291,,4211563470# Norway, Oslo : +4721502761 tel:+4721502761,,4211563470# Portugal, Lisbon : +351217810275 tel:+351217810275,,4211563470# Singapore, Singapore : +6566549828 tel:+6566549828,,4211563470# Spain, Barcelona : +34938000782 tel:+34938000782,,4211563470# Spain, Madrid : +34917699443 tel:+34917699443,,4211563470# Sweden, Stockholm : +46850336514 tel:+46850336514,,4211563470# Switzerland, Geneva : +41225927995 tel:+41225927995,,4211563470# Switzerland, Zurich : +41434569248 tel:+41434569248,,4211563470# UK, Belfast : +442895950013 tel:+442895950013,,4211563470# UK, Edinburgh : +441314601125 tel:+441314601125,,4211563470# UK, London : +442033645639 tel:+442033645639,,4211563470# USA, New York : 1-646-434-0499 tel:1-646-434-0499,,4211563470# USA, Denver : 1-720-897-6637 tel:1-720-897-6637,,4211563470# USA, Philadelphia : 1-484-427-2544 tel:1-484-427-2544,,4211563470# If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Sun May 19 14:52:56 2013 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Sun, 19 May 2013 14:52:56 +0200 Subject: [Fiware-apps] WP11 Deliverables Submission D.11.2.2 - Product vision by domain contributions In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66461076885@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66461076885@DEWDFEMB11A.global.corp.sap> Message-ID: Dear all, Please find attached the final version that has been sent to Juan Bare?o (Atos, WP11 leader) with the last contributions from UPM. All the changes are under "track changes". The main changes are: - The store is better considered now in 4.4.2. - I've done my best to improve section 4.4.3 "Composition". Now, there is a bullet list explaining each of the 4 GEs being provided for composition and mash-up, preceding the sections with the detailed description of the approaches to composition and mash-up being considered by these GEs. This allows the reader to focus on FIWARE vision and let us to shorten each of these sections. Moreover, I've reorganized these sections and added a new one for the lightweight semantic composition for the sake of completeness (interestingly, this section was missing and no other refers to semantic composition). The new organization follows that of the GEs in the bullet list for the sake of clarity, and each section is now explicitly linked to the related GE(s). For the time being I decided not to shorten them because the process needs your supervision and agreement. Nevertheless, now it is easier to shorten them if required. @ Joaquin ATOS, please review the new content regarding the lightweight semantic composition. Nevertheless, I'm quite sure it is valid. @ EAB, DT, ATOS, please review your GE description in the bullet list. Again, I'm quite sure it is valid. - I've added some content to section 4.4.6 (now 4.4.5, check). - I've added some content to section 4.4.7 (now 4.4.6, check), and specifically to 4.4.7.4. Hope you all feel comfortable with my changes. Best regards, Javier 2013/5/7 Sandfuchs, Thorsten > Dear colleagues from WP3,**** > > ** ** > > Although trying to clarify this on the last wp3-meeting there seems to be > a misunderstanding. WP11 needs input from your GE perspective on this and > so far there was no submission from WP3 in a whole.**** > > We need to fix this and I count on your input. Please indicate to me until > when you can finish this task and/or how you would propose to solve this > and the related commutation to the WPL Juan.**** > > ** ** > > To make it more explicit was is needed I attached the document & outlined > the tasks below.**** > > ** ** > > **- ***D11.2.2 > Exploitation_Plan,_including_IPR_Managementv_M24v2404***** > > **o **The document describe the following**** > > **? **FI-WARE Product Vision by domain: Identify the main Generic > Enablers+ FI-WARE Instances with most market potential**** > > **? **FI WARE Market Positioning: GE Development Prioritization Matrix*** > * > > **? **FI WARE IPR Management**** > > **? **FI WARE Ecosystem Strategy and Business Model**** > > **? **Individual Exploitation Plans**** > > **o ***ACTION 2:* *Please review it Product Vision by domain (Cloud, > Data, Iot?.) and complete *the identified missing inputs (Use Case > Scenarios and Business Canvas) and provide feedback ? *Each WPL its > domain and the rest helping, before 3rd of May***** > > ** ** > > **- **4.4.2. ?generic enabler of the business Framework? => TID, > UPM, iMinds E-IIS need to *check* and *update* their respective * > paragraphs* and send corrective text or *?OK?***** > > **- **4.4.3. ?Composition? => ATOS, DT, EAB, UPM needs *updates*reflecting the four major composition paradigmn, an updated > *graphic* and related *text* (copy&paste can be used potentially from the > architecture description)**** > > **- **4.4.4. ?Generic Enablers for Mediation? => THALES, TI need > to * check* and *update* the complete chapter and send corrective text > or * ?OK?***** > > **- **4.4.6 ?Business Canvas? -> @all *contribute GE your > specific input and perspective here * > > **- **4.4.7 and subchapters: Juan was only able to provide a > blueprint for each sub chapter. You have to fill in for your GE: Benefits, > Functions, Business and Stakeholders relationships, Value of FI > functionalities**** > > **o **4.4.7.2 ?revenue sharing?**** > > **? **TID**** > > **o **4.4.7.4 Supporting service composition and crowd-sourcing**** > > **? **UPM, ATOS, THALES, TI**** > > ** ** > > Thanks for all of your support,**** > > ** ** > > /Thorsten* > *** > > ** ** > > *From:* fiware-apps-bounces at lists.fi-ware.eu [mailto: > fiware-apps-bounces at lists.fi-ware.eu] *On Behalf Of *Sandfuchs, Thorsten > *Sent:* Donnerstag, 25. April 2013 10:00 > *To:* fiware-apps at lists.fi-ware.eu > *Subject:* [Fiware-apps] FW: [Fiware-exploitation] FW: WP11 Deliverables > Submission Roadmap for M24**** > > ** ** > > Dear colleagues,**** > > As probably not everybody is part of the WP11 exploitation list, I will > distribute this information within this list as well.**** > > ** ** > > Action 3 applies to all industry partners: TID, SAP, THALES, TI, DT, EAB, > ATOS, E-IIS, iMinds**** > > ** ** > > ACTION1: Please review Business Opportunities by domain (Cloud, Data, > Iot?.) and complete the identified missing inputs and provide feedback ? > Each WPL its domain and the rest helping, before 3rd of May**** > > ** ** > > ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot?.) > and complete the identified missing inputs (Use Case Scenarios and Business > Canvas) and provide feedback ? Each WPL its domain and the rest helping, > before 3rd of May**** > > ** ** > > ACTION 3: To Update of the individual exploitation plans, last version > from M18, into the document or into the wiki > https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual-Each FI WARE Partner before 3rd of May > **** > > ** ** > > Best,**** > > /Thorsten* > *** > > ** ** > > *From:* fiware-exploitation-bounces at lists.fi-ware.eu [ > mailto:fiware-exploitation-bounces at lists.fi-ware.eu] > *On Behalf Of *Juan Bare?o Guerenabarrena > *Sent:* Mittwoch, 24. April 2013 19:40 > *To:* fiware-exploitation at lists.fi-ware.eu > *Cc:* fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu > *Subject:* [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap > for M24**** > > ** ** > > Dear Colleagues**** > > ** ** > > Please find here enclosed in the following link > https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the > folder * ?Work Versions?, ?WP11 Final Deliverables M24?* the following > first draft deliverables, pending to complete and fine-tuning:**** > > ** ** > > **- ***D11.1.2-Market and Competition Analysis _M24v2404***** > > **o **The document describe the following:**** > > **? **Rise on 3rd party platforms and Economy of Internet Apps**** > > **? **Business Opportunities by Tech (Cloud, Big Data, IoT, > USDL?and GE combinations)**** > > **? **Business Opportunities by Sector/Industry (Smart Cities, > Smart Industry (Grid, logistics, health?.) and Smart Home)**** > > **? **The new basis of competition and the superiority of ecosystem > economics**** > > **? **The superiority of ecosystem economics**** > > **? **Ecosystems as a new distribution channel **** > > **? **Ecosystem engineering **** > > **? **What is the correct service ecosystem approach with > startups and first ?external? users of an ICT platform?**** > > **? **The biggest challenges for app businesses (and what to do about > them)**** > > **? **The success factors for app store-like platform businesses from > the perspective of third-party developers**** > > **? **European Context and trends (barriers, policy?)**** > > **o ***ACTION1: **Please review Business Opportunities by domain > (Cloud, Data, Iot*?.) *and complete* the identified missing inputs and > provide feedback ? *Each WPL its domain and the rest helping, before 3rdof May > ***** > > ** ** > > **- ***D11.2.2 > Exploitation_Plan,_including_IPR_Managementv_M24v2404***** > > **o **The document describe the following**** > > **? **FI-WARE Product Vision by domain: Identify the main Generic > Enablers+ FI-WARE Instances with most market potential**** > > **? **FI WARE Market Positioning: GE Development Prioritization Matrix*** > * > > **? **FI WARE IPR Management**** > > **? **FI WARE Ecosystem Strategy and Business Model**** > > **? **Individual Exploitation Plans**** > > **o ***ACTION 2:* *Please review it Product Vision by domain (Cloud, > Data, Iot?.) and complete *the identified missing inputs (Use Case > Scenarios and Business Canvas) and provide feedback ? *Each WPL its > domain and the rest helping, before 3rd of May***** > > **o ***ACTION 3: **To Update of the individual exploitation plans, > last version from M18, into the document or into the wiki * > https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- > *Each FI WARE Partner before 3rd of May***** > > * * > > *?Given that there is apparently no intention of joint exploitation > between the industrial partners of FI-WARE, The industrial partners are > especially urged to improve their own exploitation planningdocumentation, taking into account the analysis and conclusions reached at > the general level* > > **? ***Accordingly, Annex I must be fully updated to reflect the > more tangible business view of the industrial partner and a lot more > substantive in describing the planned integration of the FI-WARE outcomes > into the mainstream business of the industrial partners. * > > **? ***Especially at the industrial partner level, leading to concrete > plans for fit-for-deployment FI-WARE instances and other productization > opportunities*** > > **? ***Engagement FI WARE outcomes with your corporate strategy* > > **o ***In which ecosystems are you going to focus or prioritize.**Specifically, ecosystem formation needs to be prioritized strategically. In > this respect, we continue to encourage the industrial partners to more > actively and extensively engage senior business management to be involved > in the exploitation and impact creation activity of the project?* > > ** ** > > Thanks for your collaboration**** > > ** ** > > Juan**** > > ** ** > > [image: Description: cid:image001.png at 01CC3A4E.0D917B80]**** > > *Juan Bare?o* > > Group Innovation, Business Development & Strategy**** > > Research & Innovation**** > > +34 912148859**** > > Calle Albarrac?n 25, 28037 Madrid**** > > juan.bareno at atos.net**** > > www.atos.net**** > > * *[image: Description: Atos_Olympic_Games_Logo[1]]** > > ** ** > > *From:* fiware-exploitation-bounces at lists.fi-ware.eu [ > mailto:fiware-exploitation-bounces at lists.fi-ware.eu] > *On Behalf Of *Juan Bare?o Guerenabarrena > *Sent:* mi?rcoles, 17 de abril de 2013 19:08 > *To:* fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu > *Cc:* fiware-pcc at lists.fi-ware.eu > *Subject:* [Fiware-exploitation] WP11 Deliverables Submission Roadmap for > M24**** > > ** ** > > Dear Colleagues **** > > ** ** > > Following with *the submission of Exploitation Deliverables on M24*, I > enclosed you the following roadmap and the inputs needed to include in each > deliverable *according to the last comments and recommendations from the > last review on M18.* > > * * > > Please feel *free to suggest some indications or solutions to address the > issues identified in each deliverable*, based on the recommendations > provided by the reviewers. For this work, we are going to leverage on the > *following draft documents*:**** > > ** ** > > **- ***11.1.2- Market Analysis***** > > **o **Rise on 3rd party platforms and Economy of Internet Apps**** > > **? **Business Opportunities by Tech (Cloud, Big Data, IoT, USDL?and GE > combinations)**** > > **? **Business Opportunities by Sector/Industry (Smart Cities, Smart > Industry (Grid, logistics, health?.) and Smart Home)**** > > **o **The new basis of competition and the superiority of ecosystem > economics**** > > **? **The superiority of ecosystem economics**** > > **? **Ecosystems as a new distribution channel **** > > **? **Ecosystem engineering **** > > **? **What is the correct service ecosystem approach with startups and > first ?external? users of an ICT platform?**** > > **o **The biggest challenges for app businesses (and what to do about > them)**** > > **o **The success factors for app store-like platform businesses from > the perspective of third-party developers**** > > **o **European Context and trends (barriers, policy?)**** > > **- ***First Draft of the Whitepaper about Product Vision *for > identify main use case scenarios and demonstrate the main advantages > offered by FI WARE in each domain and identify the main and more potential > instances or combinations of GE (PaaS+Big Data, IoT+Big Data?..)- *Any > advance on this whitepaper?***** > > **? **What GEs can be used in combinations with what other GEs? **** > > **? **Do certain GEs force you to use other GEs? **** > > **? **How about interoperability? **** > > **? **Where is the integration burden, with FI-WARE or the users?**** > > **- ***Exploitation and business modeling position paper > prepared together with CONCORD* and that will be finished on April this > month**** > > **- ***Assessment of market traction of the relevant GEs in > those specific domains of the emerging FI-PPP Phase 1- *Feedback from UC > questionnaire sent by FI WARE**** > > **- ***Exploring Policy and Regulatory Challenges paper prepared > together with CONCORD- *Finished** > > **- ***Open Innovation Lab* > > **o **Terms and Conditions- *Status?* > > **o **Establish the strategy and implementation plan to evolve the > FI-WARE Testbed into the ?backbone? of the Open Innovation Lab- *Any > advance on this side?* > > **- ***Third party developers? feedback to the available GEs* > > **- ***Third party Enablement deliverable new version- Is there > a new version available?* > > **- ***European Patent System- *The policy context for IPR, > including the latest development on the matter**** > > ** ** > > *Resubmission Roadmap:* All Deliverables sent *on the 15th May***** > > ** ** > > **- ***Monday 22nd April*- I will send *you an initial and > significant completed draft *of the following three deliverables* trying > to address the following recommendations provided by reviewers on M18:* > > ** ** > > **o ***D11.1.2 Market and Competition Analysis (M24)* > > **? **The consortium is urged to *keep the parallel segment of Smart > Business* in dual focus with Smart Cities**** > > **? **Specifically, *ecosystem formation* needs to be prioritized > strategically**** > > **? **The challenge for future versions is to apply the new > insights to broaden and deepen the analysis of FI-WARE?s own business > ecosystem, and relate the present high level view of this ecosystem to the > more specific analysis within the GE chapters**** > > **? **Additionally, it would be useful to provide *assessment of market > traction of the relevant GEs in those specific domains of the FI-PPP Use > Case projects***** > > **? **From the conclusion of this document, it is clear that *third > party innovation enablement will be critical, and it is also intimately > linked to building a critical mass for FI-WARE results*.**** > > **? **This theme should be further developed from a market and > competitive perspective, in close synergy with and inputting directly to > the forthcoming deliverables D2.5.2 and D2.5.3 regarding *third party > uptake***** > > ** ** > > **o ***D11.2.2 Exploitation Plan, including IPR Management (M24)* > > **? **Providing *usage scenarios, potential usage patterns* (including > the ?typical? combined use of GEs), an overview of the status of available > GEs including level of Use Case interest, a clear schedule of future GE > Releases**** > > **? **Give due and *sufficient business consideration to the > competitiveness of the GEs* with respect to their market benchmarking, > innovation potential and attractiveness) for both business and development > communities.**** > > **? **Focus *on applying ?promising? technologies such as USDL and high > impact areas such as IoT*.**** > > **? **Provide additional analysis and target promising business > ecosystems for GE uptake, beyond Smart Cities. **** > > **? ***Provide clear evidence of business planning* in the targeted > areas through (combined) implementation of GEs. **** > > **? **As a specific suggestion, the market potential of the > individual GEs or groupings of GEs could be even more sharply indicated, > and possibly even contrasted and prioritized**** > > **? ***OIL description* > > **? **A significant number of critical issues have to be > addressed that will ultimately respond to the third party question ?*Why > and how FI-WARE is going to help me to innovate?? * > > **o **From a practical standpoint more detail is required relating to *access, > licensing and utilization rights*.**** > > **o **Also not yet appropriately addressed is the topic of *packaging > in terms of what the application developer can access to build FI solutions > *, such as a starter-kit.**** > > **? **The concrete *offering and strategy towards attracting relevant > communities remains unclear*. **** > > **? **Fostering developer communities fall within the scope of > Open Call 3 (launched in December 2012). This however does not mean that > present partners can derogate all responsibilities of involving potential > users and stakeholders to the future Open Call 3 partners**** > > **? ***IPR Management*: Regarding a possible integration strategy, the > Month 15 Whitepaper about common usage scenarios (and potential usage > patterns) for the GEs is long overdue. The issue was also raised by some of > the new Phase 2 projects: **** > > **? **What GEs can be used in combinations with what other GEs? ** > ** > > **? **Do certain GEs force you to use other GEs? **** > > **? **How about interoperability? **** > > **? **Where is the integration burden, with FI-WARE or the users?* > *** > > **? ***Establish the strategy and implementation plan to evolve the > FI-WARE Testbed into the ?backbone? of the Open Innovation Lab*, in > collaboration and synergy with the upcoming FIPPP Phase 2 Capability > Building project.**** > > ** ** > > **o ***D11.3.2 Market and Policy Regulation Awareness Report (M24)* > > **? **Further development of the issues and themes in Section 4.2 from > 11.3.1.b is expected, among others, for the next version. ** > > **? **The policy context for IPR, including the *latest development on > the European Patent System*, would deserve greater attention in the next > version** > > **? **It is also encouraging to see more consideration *of the platform > issues from a regulatory perspective, which should be deepened in the next > version*** > > * * > > **o ***11.4.3 Standardization (M27)* > > **? **Please provide feedback to the NEC requirements as *an oral update > has to be provided in the next review meeting (M24)***** > > * * > > * * > > **- ***Wednesday 30th April*- **** > > ** ** > > **o ***To Review or complete *the identified missing inputs and provide > feedback about the three before mentioned *deliverables 11.1.2, 11.2.2 > and 11.3.2***** > > **o ***To Update of the individual exploitation plans into the wiki**:* > **** > > **? **Given that there is apparently no intention of joint exploitation > between the industrial partners of FI-WARE, *The industrial partners are > especially urged to improve their own exploitation planning*documentation, taking into account the analysis and conclusions reached at > the general level**** > > **? **Accordingly, *Annex I must be fully updated to reflect the > more tangible business view of the industrial partner *and a lot more > substantive in describing the planned integration* of *the FI-WARE > outcomes into the mainstream business of the industrial partners.* ***** > > **? **Especially at the industrial partner level, leading to *concrete > plans for fit-for-deployment FI-WARE instances* and other productization > opportunities**** > > **? **Engagement FI WARE outcomes with your corporate strategy**** > > **? **Also welcomed is the emphasis given on ?open model?, ?open > solution?, ?open services?, ?open innovation?, ?open ecosystem? etc. *How > to start an ecosystem or leverage existing ones remains to be answered > though*. Equally, what *does ?openness? mean beyond marketing, and > concretely how it is to be applied in corporate strategy* such as on the > FI-WARE instances, need to be clarified.**** > > **? **One good example in this respect is the very specific > description provided in the Orange presentation in Seville, which clearly > explains *how usage of several sets of FI-WARE results is linked to its > corporate strategy* in engaging with the evolution of the services market. > **** > > **? ***In which ecosystems are you going to focus or prioritize.*Specifically, ecosystem formation needs to be prioritized strategically. In > this respect, we continue to encourage the industrial partners to more > actively and extensively engage senior business management to be involved > in the exploitation and impact creation activity of the project.**** > > ** ** > > **- ***Friday 10th May*- I will consolidate all the outputs and > feedback received**** > > ** ** > > **- ***Monday 13th and Tuesday 14th* - Final review and > validation will take place**** > > ** ** > > **- ***Wednesday 15th May* ? We will send the final deliverables* > *** > > ** ** > > ** ** > > Thanks for your collaboration **** > > ** ** > > Juan**** > > ** ** > > ** ** > > [image: Description: cid:image001.png at 01CC3A4E.0D917B80]**** > > *Juan Bare?o* > > Group Innovation, Business Development & Strategy**** > > Research & Innovation**** > > +34 912148859**** > > Calle Albarrac?n 25, 28037 Madrid**** > > juan.bareno at atos.net**** > > www.atos.net**** > > * *[image: Description: Atos_Olympic_Games_Logo[1]]** > > ** ** > > **** > > ------------------------------------------------------------------ > 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 endeavours 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 informacion > confidencial > destinada solamente a la(s) persona(s) mencionadas anteriormente > pueden estar protegidos por secreto profesional. > Si usted recibe este correo electronico 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 ningun > compromiso para el grupo Atos, salvo ratificacion escrita por ambas > partes. > Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor > no puede garantizar nada al respecto y no sera responsable de cualesquiera > danos que puedan resultar de una transmision de virus. > ------------------------------------------------------------------**** > > **** > > ------------------------------------------------------------------ > 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 endeavours 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 informacion > confidencial > destinada solamente a la(s) persona(s) mencionadas anteriormente > pueden estar protegidos por secreto profesional. > Si usted recibe este correo electronico 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 ningun > compromiso para el grupo Atos, salvo ratificacion escrita por ambas > partes. > Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor > no puede garantizar nada al respecto y no sera responsable de cualesquiera > danos que puedan resultar de una transmision de virus. > ------------------------------------------------------------------**** > > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-apps > > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D11.2.2+Exploitation_Plan,_including_IPR_Managementv_M24v2404_FOR_SUBMISSION_UPM_INPUT_v3.doc Type: application/msword Size: 4625408 bytes Desc: not available URL: From thorsten.sandfuchs at sap.com Wed May 22 16:57:54 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 22 May 2013 14:57:54 +0000 Subject: [Fiware-apps] FI-WARE webinar for FI-PPP projects phase 2 - Apps and Services overview Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646108FD1D@DEWDFEMB11A.global.corp.sap> Dear interested parties, Please join us in our schedule webinar on Apps and services for FI-PPP phase 2 projects - on the 23.05.2013 / 15:00 CET outlining the core capabilities of the FI-WARE "apps and services" chapter and giving the relevant pointers for further collaborations. Please as well feel yourself encouraged to add to the discussion and proactively ask questions in relation to the presentation prior, after or during the meeting. Thanks for your interest and looking forward to the session with you. Best regards /Thorsten Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ <- follow this link to join the meeting If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Country Number Germany, Frankfurt tel:+4969222210764 Europe Austria, Vienna tel:+431253021750 France, Paris tel:+33170701777 Italy, Milan tel:+390236009839 Spain, Madrid tel:+34917699443 Switzerland, Zurich tel:+41434569248 UK, London tel:+442033645639 Oversea Australia, Sydney tel:+61290090688 India, Bangalore tel:+918061275055 USA, New York tel:+16464340499 -- Thorsten Sandfuchs SAP AG SAP Research Center Karlsruhe Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4232 bytes Desc: not available URL: From markus.heller at sap.com Thu May 23 13:29:57 2013 From: markus.heller at sap.com (Heller, Markus) Date: Thu, 23 May 2013 11:29:57 +0000 Subject: [Fiware-apps] FI-WARE WP3: Doodle Poll to find a time slot for WP3 Weekly Call Series Message-ID: <393554EDCF801348BC53C7813C6CB73B088C2B@DEWDFEMB14A.global.corp.sap> Dear All I would like to have a Doodle voting to find a time slot for our FI-WARE WP3 Weekly Call Series. Can you please vote until Friday 24.05.13 12.00 (tomorrow)? I can then evaluate and set up a new slot if we find one this round. (To start, I have limited the set to slots between 13 and 18 and from Wednesday to Friday. This is based on evaluating the last poll from Axel where many/most of you were available. If needed, we can of course open the range, if we do not find a slot here.) Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Thu May 23 13:35:13 2013 From: markus.heller at sap.com (Heller, Markus) Date: Thu, 23 May 2013 11:35:13 +0000 Subject: [Fiware-apps] FI-WARE: WP3 Call In-Reply-To: <393554EDCF801348BC53C7813C6CB73B0694C9@DEWDFEMB14A.global.corp.sap> References: <393554EDCF801348BC53C7813C6CB73B0694C9@DEWDFEMB14A.global.corp.sap> Message-ID: <393554EDCF801348BC53C7813C6CB73B088C3E@DEWDFEMB14A.global.corp.sap> Dear all, FYI I will move the meeting series for our WP3 Weekly series from Thursday to Friday 13-14 temporarily: Let us use the Friday-Slot until we finished voting about a new time slot. Reminder: Please attend tomorrow 13-14, if your time permits. We can discuss the doodle poll results that has just finished before there and agree on a time slot if there is a clear favorite. Best wishes & see you tomorrow Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Thu May 23 13:35:32 2013 From: markus.heller at sap.com (Heller, Markus) Date: Thu, 23 May 2013 11:35:32 +0000 Subject: [Fiware-apps] FI-WARE: WP3 Call Message-ID: <393554EDCF801348BC53C7813C6CB73B088C4D@DEWDFEMB14A.global.corp.sap> Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call on Fridays, please use the dial-in info below. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Austria, Vienna : +431253021750 Belgium, Brussels : +3224040657 Czech Republic, Prague : +420228882890 Finland, Helsinki : +358923101631 France, Paris : +33170701777 Germany, Frankfurt : +4969222210764 Germany, Munich : +4989710424682 Ireland, Dublin : +35312476192 Israel, Tel Aviv : +97237630750 Italy, Milan : +390236009839 Italy, Rome : +390645236623 Luxembourg, Luxembourg : +35224871454 Netherlands, Amsterdam : +31207168291 Norway, Oslo : +4721502761 Portugal, Lisbon : +351217810275 Singapore, Singapore : +6566549828 Spain, Barcelona : +34938000782 Spain, Madrid : +34917699443 Sweden, Stockholm : +46850336514 Switzerland, Geneva : +41225927995 Switzerland, Zurich : +41434569248 UK, Belfast : +442895950013 UK, Edinburgh : +441314601125 UK, London : +442033645639 USA, New York : 1-646-434-0499 USA, Denver : 1-720-897-6637 USA, Philadelphia : 1-484-427-2544 If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3968 bytes Desc: not available URL: From markus.heller at sap.com Thu May 23 13:40:23 2013 From: markus.heller at sap.com (Heller, Markus) Date: Thu, 23 May 2013 11:40:23 +0000 Subject: [Fiware-apps] FI-WARE WP3: Doodle Poll to find a time slot for WP3 Weekly Call Series In-Reply-To: <393554EDCF801348BC53C7813C6CB73B088C2B@DEWDFEMB14A.global.corp.sap> References: <393554EDCF801348BC53C7813C6CB73B088C2B@DEWDFEMB14A.global.corp.sap> Message-ID: <393554EDCF801348BC53C7813C6CB73B088CAC@DEWDFEMB14A.global.corp.sap> Dear All I would like to have a Doodle voting to find a time slot for our FI-WARE WP3 Weekly Call Series. DOODLE URL: http://www.doodle.com/7v4ct7iwwuit6yer Can you please vote until Friday 24.05.13 12.00 (tomorrow)? I can then evaluate and set up a new slot if we find one this round. (To start, I have limited the set to slots between 13 and 18 and from Wednesday to Friday. This is based on evaluating the last poll from Axel where many/most of you were available. If needed, we can of course open the range, if we do not find a slot here.) Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Fri May 24 09:30:36 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 24 May 2013 07:30:36 +0000 Subject: [Fiware-apps] WP3 Architecture Deliverable M24: Review from Security Chapter for our contributions Message-ID: <393554EDCF801348BC53C7813C6CB73B089401@DEWDFEMB14A.global.corp.sap> Hi WP3 members, Yesterday we have successfully submitted the WP3 part Architecture Deliverable to TID. Thank you so far for your contributions here. You can find the submitted version linked into the Architecture Deliverable Cockpit URL: https://forge.fi-ware.eu/docman/view.php/7/2405/D.2.3.2+FI-WARE+Architecture+%E2%80%93+WP3+Contributions.docx Two TODO's remain: 1) Update of WIKI: The WIKI is currently not up to date w.r.t this WP3 architecture deliverable, we need to fix this prior to the Review in Brussels. Please update the WIKI for your part which is located in "your" usual sub WIKI pages starting at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture. Deadline is Friday 07.06. 2) Check/Process review results (if applicable): The review from Security Chapter WPL is attached. I addressed as many comments as I could in order to complete the submission and I submitted our deliverable contribution. Please go through the review comments and decide if/how you want to address the comments that relate to your input. We can decide if we want to prepare a version to be resubmitted (at a later time) based on this. Please contact me or WP3 mailing list all for further discussions, if you like. Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Fri May 24 10:05:44 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 24 May 2013 08:05:44 +0000 Subject: [Fiware-apps] WP3 Architecture Deliverable M24: Review from Juanjo for our contributions Message-ID: <393554EDCF801348BC53C7813C6CB73B0894E7@DEWDFEMB14A.global.corp.sap> Hi WP3 members, Ok, I now distribute the review from Juanjo (not Security Chapter WPL, they had kindly reviewed our SOTA....). Please note: The submitted version already contains changes that I made according to the reviewer's comments (among them typos etc). I suggest for you to focus on the comments that directly relate your contributions (like ideas to add more related work in some locations). Best wishes Markus From: markus.heller at sap.com Sent: Freitag, 24. Mai 2013 09:31 To: 'fiware-apps at lists.fi-ware.eu' Subject: WP3 Architecture Deliverable M24: Review from Security Chapter for our contributions Hi WP3 members, Yesterday we have successfully submitted the WP3 part Architecture Deliverable to TID. Thank you so far for your contributions here. You can find the submitted version linked into the Architecture Deliverable Cockpit URL: https://forge.fi-ware.eu/docman/view.php/7/2405/D.2.3.2+FI-WARE+Architecture+%E2%80%93+WP3+Contributions.docx Two TODO's remain: 1) Update of WIKI: The WIKI is currently not up to date w.r.t this WP3 architecture deliverable, we need to fix this prior to the Review in Brussels. Please update the WIKI for your part which is located in "your" usual sub WIKI pages starting at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture. Deadline is Friday 07.06. 2) Check/Process review results (if applicable): The review from Security Chapter WPL is attached. I addressed as many comments as I could in order to complete the submission and I submitted our deliverable contribution. Please go through the review comments and decide if/how you want to address the comments that relate to your input. We can decide if we want to prepare a version to be resubmitted (at a later time) based on this. Please contact me or WP3 mailing list all for further discussions, if you like. Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D232_WP3_v6_generated commented jhierro v3.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 7825673 bytes Desc: D232_WP3_v6_generated commented jhierro v3.docx URL: From markus.heller at sap.com Fri May 24 10:54:15 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 24 May 2013 08:54:15 +0000 Subject: [Fiware-apps] Fwd: FP7-ICT-285248 FI-WARE - Official Invitation to M24 Review Meeting Message-ID: <393554EDCF801348BC53C7813C6CB73B08962B@DEWDFEMB14A.global.corp.sap> Dear WP3 members, As a reminder, I would like to forward the invitation to the FI-WARE Brussels Review. Please remind the prep meeting that is immediately before the EC review. The planning is: a) Review preparation meeting: 10.06 and 11.06 in Brussels (location details to follow) b) EC Review meeting: 12.06 and 13.06 in Brussels (see below mail) Best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 6. Mai 2013 16:48 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Fwd: FP7-ICT-285248 FI-WARE - Official Invitation to M24 Review Meeting FYI, -- Juanjo -------- Original Message -------- Subject: FP7-ICT-285248 FI-WARE - Official Invitation to M24 Review Meeting Date: Mon, 6 May 2013 13:47:14 +0000 From: To: CC: , , , , , , Dear Mr. Hierro, In accordance with Article II.23 of the contract, and as agreed with you recently, I hereby inform you of the Commission's intention to hold a review meeting of the project FP7-ICT-285248 FI-WARE in Brussels, Belgium on 12th & 13th June 2013. The meeting will take place in the premises of the European Commission in avenue de Beaulieu, 1160 Brussels Meeting rooms: 12th & 13th June 2013, avenue de Beaulieu BU25 0/S9 As agreed with you, the Commission will be assisted by the following independent experts: - Dr Renaud Di Francesco - Dr. Dominic Greenwood - Ms Man-Sze Li - Mr. Michele Marzola - Ms Irena Pavlova The objectives of the review are, in particular, to establish: ? the degree of fulfillment of the project work plan for the relevant period and of the related deliverables; ? the continued relevance of the objectives and breakthrough potential with respect to the scientific and industrial state of the art; ? the resources planned and utilized in relation to the achieved progress, in a manner consistent with the principles of economy, efficiency and effectiveness; ? the management procedures and methods of the project; ? the beneficiaries' contributions and integration within the project; ? the expected potential impact in scientific, technologic, economic, competitive and social terms (where relevant), and the plans for the use and dissemination of results. If you have not sent the deliverables for this review period (months 19 to 24) to the European Commission yet, please do so as soon as possible and put the experts (see cc) in copy. Please send us the draft agenda of this meeting before Friday 24th May 2013. Please send me the names of the people attending the review before Friday 7th June 2013. Should you have any questions before the meeting, please do not hesitate to contact me. Thank you for your co-operation. Best Regards, Vanessa Vanhumbeeck European Commission DG CONNECT Unit E3 - Net Innovation Tel.: +32 2 296 49 39 Email: vanessa.vanhumbeeck at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From markus.heller at sap.com Fri May 24 11:40:40 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 24 May 2013 09:40:40 +0000 Subject: [Fiware-apps] WP3 Architecture Deliverable M24: Review from Juanjo for our contributions Message-ID: <393554EDCF801348BC53C7813C6CB73B08972A@DEWDFEMB14A.global.corp.sap> Hi WP3, I better clarify: The task 2 to check the review of our WP3 Architecture Deliverable is not meant for the current submission of Arch deliverable (WP3 has delivered its input and the overall Architecture Deliverable will be submitted today) --> no action on short term required. Best wishes Markus From: markus.heller at sap.com Sent: Freitag, 24. Mai 2013 10:05 To: 'fiware-apps at lists.fi-ware.eu' Subject: RE: WP3 Architecture Deliverable M24: Review from Juanjo for our contributions Hi WP3 members, Ok, I now distribute the review from Juanjo (not Security Chapter WPL, they had kindly reviewed our SOTA....). Please note: The submitted version already contains changes that I made according to the reviewer's comments (among them typos etc). I suggest for you to focus on the comments that directly relate your contributions (like ideas to add more related work in some locations). Best wishes Markus From: markus.heller at sap.com Sent: Freitag, 24. Mai 2013 09:31 To: 'fiware-apps at lists.fi-ware.eu' Subject: WP3 Architecture Deliverable M24: Review from Security Chapter for our contributions Hi WP3 members, Yesterday we have successfully submitted the WP3 part Architecture Deliverable to TID. Thank you so far for your contributions here. You can find the submitted version linked into the Architecture Deliverable Cockpit URL: https://forge.fi-ware.eu/docman/view.php/7/2405/D.2.3.2+FI-WARE+Architecture+%E2%80%93+WP3+Contributions.docx Two TODO's remain: 1) Update of WIKI: The WIKI is currently not up to date w.r.t this WP3 architecture deliverable, we need to fix this prior to the Review in Brussels. Please update the WIKI for your part which is located in "your" usual sub WIKI pages starting at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture. Deadline is Friday 07.06. 2) Check/Process review results (if applicable): The review from Security Chapter WPL is attached. I addressed as many comments as I could in order to complete the submission and I submitted our deliverable contribution. Please go through the review comments and decide if/how you want to address the comments that relate to your input. We can decide if we want to prepare a version to be resubmitted (at a later time) based on this. Please contact me or WP3 mailing list all for further discussions, if you like. Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Fri May 24 14:15:03 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 24 May 2013 12:15:03 +0000 Subject: [Fiware-apps] FI-WARE WP3: Doodle Poll to find a time slot for WP3 Weekly Call Series --> Result Message-ID: <393554EDCF801348BC53C7813C6CB73B089931@DEWDFEMB14A.global.corp.sap> Dear all, The result of the doodle is as follows (screenshot): Each Thursday 15:00-16:00 (all partners have signaled green or yellow, all others have at least one red light). So I propose Thursday each week 15-16 as new WP3 Weekly Call Series slot. I will setup this new slot starting Thursday 6.June then. For next week, we stick to Friday 31.05. at 13-14 (Thursday is a public holiday at least in Germany). Best wishes Markus _____________________________________________ From: markus.heller at sap.com Sent: Donnerstag, 23. Mai 2013 13:30 To: 'fiware-apps at lists.fi-ware.eu' Subject: FI-WARE WP3: Doodle Poll to find a time slot for WP3 Weekly Call Series Dear All I would like to have a Doodle voting to find a time slot for our FI-WARE WP3 Weekly Call Series. Can you please vote until Friday 24.05.13 12.00 (tomorrow)? I can then evaluate and set up a new slot if we find one this round. (To start, I have limited the set to slots between 13 and 18 and from Wednesday to Friday. This is based on evaluating the last poll from Axel where many/most of you were available. If needed, we can of course open the range, if we do not find a slot here.) Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture (Device Independent Bitmap) 1.jpg Type: image/jpeg Size: 631 bytes Desc: Picture (Device Independent Bitmap) 1.jpg URL: From markus.heller at sap.com Fri May 24 14:29:02 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 24 May 2013 12:29:02 +0000 Subject: [Fiware-apps] Canceled: FI-WARE: WP3 Call Message-ID: <393554EDCF801348BC53C7813C6CB73B0899B0@DEWDFEMB14A.global.corp.sap> Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call on Fridays, please use the dial-in info below. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Austria, Vienna : +431253021750 Belgium, Brussels : +3224040657 Czech Republic, Prague : +420228882890 Finland, Helsinki : +358923101631 France, Paris : +33170701777 Germany, Frankfurt : +4969222210764 Germany, Munich : +4989710424682 Ireland, Dublin : +35312476192 Israel, Tel Aviv : +97237630750 Italy, Milan : +390236009839 Italy, Rome : +390645236623 Luxembourg, Luxembourg : +35224871454 Netherlands, Amsterdam : +31207168291 Norway, Oslo : +4721502761 Portugal, Lisbon : +351217810275 Singapore, Singapore : +6566549828 Spain, Barcelona : +34938000782 Spain, Madrid : +34917699443 Sweden, Stockholm : +46850336514 Switzerland, Geneva : +41225927995 Switzerland, Zurich : +41434569248 UK, Belfast : +442895950013 UK, Edinburgh : +441314601125 UK, London : +442033645639 USA, New York : 1-646-434-0499 USA, Denver : 1-720-897-6637 USA, Philadelphia : 1-484-427-2544 If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3993 bytes Desc: not available URL: From markus.heller at sap.com Fri May 24 14:30:32 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 24 May 2013 12:30:32 +0000 Subject: [Fiware-apps] FI-WARE: WP3 Call Message-ID: <393554EDCF801348BC53C7813C6CB73B0899E5@DEWDFEMB14A.global.corp.sap> Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call on Thursdays 15-16, please use the dial-in info below. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Austria, Vienna : +431253021750 Belgium, Brussels : +3224040657 Czech Republic, Prague : +420228882890 Finland, Helsinki : +358923101631 France, Paris : +33170701777 Germany, Frankfurt : +4969222210764 Germany, Munich : +4989710424682 Ireland, Dublin : +35312476192 Israel, Tel Aviv : +97237630750 Italy, Milan : +390236009839 Italy, Rome : +390645236623 Luxembourg, Luxembourg : +35224871454 Netherlands, Amsterdam : +31207168291 Norway, Oslo : +4721502761 Portugal, Lisbon : +351217810275 Singapore, Singapore : +6566549828 Spain, Barcelona : +34938000782 Spain, Madrid : +34917699443 Sweden, Stockholm : +46850336514 Switzerland, Geneva : +41225927995 Switzerland, Zurich : +41434569248 UK, Belfast : +442895950013 UK, Edinburgh : +441314601125 UK, London : +442033645639 USA, New York : 1-646-434-0499 USA, Denver : 1-720-897-6637 USA, Philadelphia : 1-484-427-2544 If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4101 bytes Desc: not available URL: From markus.heller at sap.com Fri May 24 14:31:00 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 24 May 2013 12:31:00 +0000 Subject: [Fiware-apps] FI-WARE: WP3 Call Message-ID: <393554EDCF801348BC53C7813C6CB73B089A06@DEWDFEMB14A.global.corp.sap> Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call on Thursdays 15-16, please use the dial-in info below. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Austria, Vienna : +431253021750 Belgium, Brussels : +3224040657 Czech Republic, Prague : +420228882890 Finland, Helsinki : +358923101631 France, Paris : +33170701777 Germany, Frankfurt : +4969222210764 Germany, Munich : +4989710424682 Ireland, Dublin : +35312476192 Israel, Tel Aviv : +97237630750 Italy, Milan : +390236009839 Italy, Rome : +390645236623 Luxembourg, Luxembourg : +35224871454 Netherlands, Amsterdam : +31207168291 Norway, Oslo : +4721502761 Portugal, Lisbon : +351217810275 Singapore, Singapore : +6566549828 Spain, Barcelona : +34938000782 Spain, Madrid : +34917699443 Sweden, Stockholm : +46850336514 Switzerland, Geneva : +41225927995 Switzerland, Zurich : +41434569248 UK, Belfast : +442895950013 UK, Edinburgh : +441314601125 UK, London : +442033645639 USA, New York : 1-646-434-0499 USA, Denver : 1-720-897-6637 USA, Philadelphia : 1-484-427-2544 If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4101 bytes Desc: not available URL: From markus.heller at sap.com Fri May 24 14:31:41 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 24 May 2013 12:31:41 +0000 Subject: [Fiware-apps] Canceled: FI-WARE: WP3 Call Message-ID: <393554EDCF801348BC53C7813C6CB73B089A1B@DEWDFEMB14A.global.corp.sap> This call cancelled, we are on FI-WARE review. ---- Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call on Thursdays 15-16, please use the dial-in info below. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Austria, Vienna : +431253021750 Belgium, Brussels : +3224040657 Czech Republic, Prague : +420228882890 Finland, Helsinki : +358923101631 France, Paris : +33170701777 Germany, Frankfurt : +4969222210764 Germany, Munich : +4989710424682 Ireland, Dublin : +35312476192 Israel, Tel Aviv : +97237630750 Italy, Milan : +390236009839 Italy, Rome : +390645236623 Luxembourg, Luxembourg : +35224871454 Netherlands, Amsterdam : +31207168291 Norway, Oslo : +4721502761 Portugal, Lisbon : +351217810275 Singapore, Singapore : +6566549828 Spain, Barcelona : +34938000782 Spain, Madrid : +34917699443 Sweden, Stockholm : +46850336514 Switzerland, Geneva : +41225927995 Switzerland, Zurich : +41434569248 UK, Belfast : +442895950013 UK, Edinburgh : +441314601125 UK, London : +442033645639 USA, New York : 1-646-434-0499 USA, Denver : 1-720-897-6637 USA, Philadelphia : 1-484-427-2544 If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4063 bytes Desc: not available URL: From markus.heller at sap.com Fri May 24 14:28:15 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 24 May 2013 12:28:15 +0000 Subject: [Fiware-apps] FI-WARE: WP3 Call (Exception here on Friday) Message-ID: <393554EDCF801348BC53C7813C6CB73B089986@DEWDFEMB14A.global.corp.sap> Dear FI-WARE WP3 colleagues, I invite you to our WP3 Call this Friday, please use the dial-in info below. Best wishes Markus Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Location Phone Austria, Vienna : +431253021750 Belgium, Brussels : +3224040657 Czech Republic, Prague : +420228882890 Finland, Helsinki : +358923101631 France, Paris : +33170701777 Germany, Frankfurt : +4969222210764 Germany, Munich : +4989710424682 Ireland, Dublin : +35312476192 Israel, Tel Aviv : +97237630750 Italy, Milan : +390236009839 Italy, Rome : +390645236623 Luxembourg, Luxembourg : +35224871454 Netherlands, Amsterdam : +31207168291 Norway, Oslo : +4721502761 Portugal, Lisbon : +351217810275 Singapore, Singapore : +6566549828 Spain, Barcelona : +34938000782 Spain, Madrid : +34917699443 Sweden, Stockholm : +46850336514 Switzerland, Geneva : +41225927995 Switzerland, Zurich : +41434569248 UK, Belfast : +442895950013 UK, Edinburgh : +441314601125 UK, London : +442033645639 USA, New York : 1-646-434-0499 USA, Denver : 1-720-897-6637 USA, Philadelphia : 1-484-427-2544 If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/go/connectpro_overview Adobe, the Adobe logo, Acrobat and Acrobat Connect are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3696 bytes Desc: not available URL: From markus.heller at sap.com Fri May 24 19:18:45 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 24 May 2013 17:18:45 +0000 Subject: [Fiware-apps] FW: [Fiware-wpl] IMPORTANT REMINDER: Future Internet Public Private Partnership In-Reply-To: <519C9F8B.5080604@tid.es> References: <04BE08B5CBC6F54AB4B342A70C56474F0230AB6F@S-DC-ESTE04-B.net1.cec.eu.int> <519C9F8B.5080604@tid.es> Message-ID: <393554EDCF801348BC53C7813C6CB73B08A012@DEWDFEMB14A.global.corp.sap> Dear WP3 members, I forward a mail from coordinator to WPL/WPAs with three tasks on "Achievements of FI-WARE" that our WP3 needs do perform like all other WPs. Please first read Juanjo's mail for the context. The FORM that we need to fill is at: https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit . The following tasks refer to PART A in this Google Doc document, ignore Part B. @All: Please contribute to both tasks below. WP3-Internal Deadline for both tasks: Tuesday next week 28.05 EOB. Task 1) Fill a box per GE (RELEASE 1) in the PART A of the Google Doc document - Please provide entries associated to your FI-WARE GEis of Release 1 in the Apps Chapter at: https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit - For each GE you have to copy and fill out this box template. The questions in the box (left side) refer to the FI-WARE catalog mainly... [cid:image003.jpg at 01CE58B3.81BFBD20] Task 2) Prepare CATALOG (catalog.fi-ware.eu) w.r.t PART A - Please update/add consistent/up-to-date information for all your catalog data to the different sections in the catalog and review contents of entries in the catalog with the aim to ensure that they can be used for answer to Part A. Best wishes Markus P.S: Please read this Information from EC how to fill out these forms: [cid:image004.png at 01CE58B2.C5A215C0] From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 22. Mai 2013 12:36 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] IMPORTANT REMINDER: Future Internet Public Private Partnership Hi all, TID didn't want to push that much this AP before because we thought that was better to stay focused on the deliverables that were due end of April as to make sure they get delivered in reasonable time. But now it seems like we are starting to be in a good shape, so that I believe it is now time to push and remind you the AP. I have already got an extension of the deadline in the case of FI-WARE until end of this month due to the fact that we in FI-WARE have many things on the table. That should allow us to deliver a resoable reesponse. Instructions to follow were gathered already in the pre-minutes of the WPLs/WPAs but I'm copy them here for your convenience: The EC has formally asked us to fill a form summarizing achievements of FI-WARE. See mail forwarded on 06/05/13, subject: "Future Internet Public Private Partnership". A shared version of the form for FI-WARE is available at: https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit Juanjo: our take regarding Part A would be to make references to contents of entries in the FI-WARE Catalogue, which indeed should contain complete info answering questions about: ? Description of the Generic Enabler ? What does this Generic Enabler offer in terms of functionality ? What potential use could it have in the development of services and applications Actually, the standard sections on the catalogue titled "What you get" and "Open Specification Reference" should answer the two first questions, while the standard section titled "Why to get it" should answer the third one. We should be able to answer the question on "What is the market position in relation to competitive products? What is the competitive advantage?" based on the contents of the State of the Art deliverable that it is supposed to be under way. AP on all WPLs/WPAs to provide entries associated to FI-WARE GEis of Release 1 in their chapter. Use the google docs provided above for that purpose. AP on all WPLs/WPAs to review contents of the State of the Art deliverable so that it provides clear answers to the questions formulated on benchmarking, not only regarding FI-WARE GEis in Relase 1 but FI-WARE GEis in Release 2 (this will pave the way for an update of the form once Release 2 is delivered) Juanjo: ATOS may try to provide the initial draft to Part C.2) AP on all WPLs/WPAs to provide input to the different sections and review contents of entries in the catalogue to ensure that they can be used for answer to Part A. Deadline: Monday 20, 11:00am. Telefonica will be drafting an answer for the rest of the form. Please keep an eye on what is being drafted in the shared google doc and provide inputs/comments. We shall prepare an update of the form once Release 2 is delivered and entries linked to new FI-WARE GEis are registered in the FI-WARE Catalogue. Try to get this APs done by mid next week. I will be off-line for a while due because travelling to Berlin but supposed to be connected from 17:30 on or so. I will be able to answer any questions you may have by them. Regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Future Internet Public Private Partnership Date: Mon, 6 May 2013 16:18:46 +0000 From: To: , , , , , , , , , , , , , , , , , , CC: , , , , , Dear Project Coordinators, Please find attached a note and the corresponding forms regarding the achievements of the FI-PPP. Regards, Jesus Jesus VILLASANTE Head of Unit [cid:part2.06010704.07010404 at tid.es] European Commission DG Communication Networks, Content and Technology E3: Net Innovation BU25 3/81 B-1049 Brussels/Belgium +32 2 29-63521 Jesus.Villasante at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00001.jpg Type: image/jpeg Size: 1585 bytes Desc: ATT00001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 126480 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 13501 bytes Desc: image003.jpg URL: From markus.heller at sap.com Sat May 25 18:16:45 2013 From: markus.heller at sap.com (Heller, Markus) Date: Sat, 25 May 2013 16:16:45 +0000 Subject: [Fiware-apps] FW: [Fiware-wpl] Regeneration of the Technical roadmap In-Reply-To: <519F8D5F.60400@tid.es> References: <519F8D5F.60400@tid.es> Message-ID: <393554EDCF801348BC53C7813C6CB73B08BB5C@DEWDFEMB14A.global.corp.sap> FYI -----Original Message----- From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Freitag, 24. Mai 2013 17:55 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpl] Regeneration of the Technical roadmap Dear all, This is to announce that I will regenerate the Technical Roadmap based on the info present on the wiki - it will be an extra issue to reflect the current status and I will deliver it to the EC as such. I will regenerate it on Tuesday at 4pm. Best regards, Miguel From thorsten.sandfuchs at sap.com Mon May 27 16:00:35 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 27 May 2013 14:00:35 +0000 Subject: [Fiware-apps] Periodic Report M13-M24 - next steps - DEADLINE: wednesday this week! Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610984E7@DEWDFEMB11A.global.corp.sap> Dear colleagues, We can proceed with the work on the periodic report. The original time plan of TID envisioned a DELIVERY of the final report by the end of this week (Friday, 31.05.2013) and there are your inputs pending. I took everything that needs to be done in one email - please excuse that this is a bit long. :) ? Please provide and prepare the rational paragraph in relation to your partner contribution and according to the latest numbers if possible for Wednesday (29.05.2013) ? Please provide the relevant paragraph to Markus and me in response to this email (we will integrate it in the final report) We are still waiting for the integrated version of the overall report from TID - in the meantime we can work on the effort numbers which TID provided to us in advance. These effort numbers are currently visible to us and we take this as working fundament: (red is a deviation of > 10%; green is a deviate < 10% Remark: TID provided us with the relevant numbers (see down below) and I created this working table) M1-M12 M1-M12 M1-M12 M13-M24 M13-M24 M13-M24 M1-M24 M1-M24 M1-M24 planned worked deviation planned worked deviation planned worked deviation TID 15 14,2 95% 24,00 25,42 106% 39,00 39,62 101,59% SAP 33,75 49,04 145% 54,00 45,61 84% 87,75 94,65 107,86% THALES 2,5 2,45 98% 4,00 3,84 96% 6,50 6,29 96,77% TI 5 5,2 104% 8,00 7,13 89% 13,00 12,33 94,85% DT 7,5 9,23 123% 12,00 10,10 84% 19,50 19,33 99,13% EAB 14,55 20,58 141% 17,45 11,40 65% 32,00 31,98 99,94% ATOS 7,5 8,7 116% 12,00 15,94 133% 19,50 24,64 126,36% E-IIS 2,5 4,87 195% 4,00 3,50 88% 6,50 8,37 128,77% UPM 12 4,3 36% 19,20 30,55 159% 31,20 34,85 111,70% UDE 1,5 3,94 263% 2,40 2,02 84% 3,90 5,96 152,82% iMinds 0 0 14,89 11,46 77% 14,89 11,46 76,96% Given these efforts we can work on finalizing the relevant sections (which were foreseen in the initial report already provided). Section 1. "Partners whose effort is significantly lower compared with the planning are the following" Section 2. "Partners whose effort is significantly higher compared with the planning are the following" Section 3. "In summary, the status of this WP3 regarding consumption of resources is ...." (An evaluation is required) => draft of SAP see below, please approve Section 4. "In general, the consumption of resources in this WP3 " (An evaluation is required) => draft of SAP see below, please approve Task 1. We expect final and updated input from the following partners (as the numbers that we can see are either 10% above or 10% below schedule for the M13-M24 reporting period). Although we are in general reporting on the M13-M24 report it is still encourage to comment on the overall efforts if significant over/underspending happened or was resolved. Please write as well by "when" your company plans to resolve this. If you updated your numbers within the last days, please provide the final rationale to us and elaborate if we should integrate it as over- or underspending!) Section 1. "Partners whose effort is significantly lower compared with the planning are the following" ? SAP - no text initially submitted ? TI - no text initially submitted ? DT - no text initially submitted ? EAB - no text initially submitted ? E-IIS - please touch as well why your overall effort is 128,77% over planned spending, giving an outlook if this will be resolved and until when ? Initial text already provided, see below - please recheck if this still does match your intension & our comments below ? iMinds - please touch as well why your overall effort is 76,96% under planned spending, giving an outlook if this will be resolved and until when ? Initial text already provided, see below - please recheck if this still does match your intension & our comments below ? UDE - please touch as well why your overall effort is 152,82% over planned spending, giving an outlook if this will be resolved and until when Section 2. Partners whose effort is significantly higher compared with the planning are the following ? ATOS - please touch as well why your overall effort is 126,26% over planned spending, giving an outlook if this will be resolved and until when ? Initial text already provided, see below - please recheck if this still does match your intension & our comments below ? UPM - please touch as well why your overall effort is 111,70% over planned spending, giving an outlook if this will be resolved and until when ? Initial text already provided, see below - please recheck if this still does match your intension & our comments below Current input provided by E-IIs, iMinds, ATOS, UPM and relevant comments: Section 1. "Partners whose effort is significantly lower compared with the planning are the following" ? "E-IIS the reason is the increase of engagement in the period to attempt to introduce the existence and universal quantifiers in the initial model that revealed a number of drawback and implications not manageable with the effort allocated." o Comment WPL: Rational seems to be misplaced as the numbers are actually lower for the current period but only higher for the overall reporting period. Please make this explicit ? "EAB's figures (PM consumption) are significantly lower than the estimations. This is due to a resource shift from EAB to UPM, which is explained in the UPM section. EAB was not able to contribute to this periodic report. The statements of EAB given in this periodic report reflect the status as of the M13-M18 periodic report" o Comment WPL: Please contribute to the periodic report and then update the statement Section 2. Partners whose effort is significantly higher compared with the planning are the following ? UPM's figures (PM consumption) exceed the estimations due to the following reasons: ? After EAB left T3.3 at the end of the 1st periodic report, UPM, SAP and Telef?nica I+D agreed that UPM will take over the development of the Store GE and the leadership of T3.1. This agreement has been included in the 4th amendment and its approval is pending at the moment of writing this report, and thus it is not reflected in the planning. In the context of this agreement, UPM has performed the above mentioned tasks during the M13-M24 period. ? This effect is also considered in the current DoW amendment 4 according to which UPM efforts are fully along the plan. ? Comment WPL: UPM, please comment on the general overspending of 111,70% ? ATOS: As we have mentioned, a key team member working on Fiware and specifically in WP3 left the company at the beginning of September 2012 and in order to replace him a new person begun in the project during November 2012. This change affected directly ATOS' performance in this workpackage and its related tasks. Because of this, ATOS reduced effort working for a couple of months (during September and October 2012). However, a new member, without previous knowledge about the project and ist nature and specifications, was incorporated at the end of 2012. Therefore, it required an extra-effort to finish the remaining task and to perform the knowledge transfer to the new member. Specifically, two people instead of one were involved in the project in order to perform the required tasks and at the same time provide the specific training to the new team member. The increase in efforts reported specifically in November, January and March is a consequence of this situation. ? Comment WPL: ATOS: This might be seen as a week excuse by the reviewers, if possible please improve the rational given, especially as you seem to overbook 126% overall. Task 2. @ALL PARTNERS: For section 3 and 4 we prepared the following summary statements for the complete work package - please veto if you are not aligned with the statements: Section 1. Section 2. Section 3. "In summary, the status of this WP3 regarding consumption of resources is ...." ? ... in general in line with the plan, given the cruise speed approach. The overspending introduced in the first project year has significantly decreased overall. Many partners booked effectively less effort than planned. Although there were decommitments by some partners, other partners stepped up and took over their work efforts and contributions. The DoW amendment v4 reflects the current effort and partner contributions quite well. Detailed deviation for the reporting period M13-M24 are outlined on a partner level down below. Section 4. "In general, the consumption of resources in this WP3..." ? ... in general in line with the plan, with roughly 3% underspending in average and over all the partners. As outlined above by the contributing partners, most of the deviation YoY (M1-M24) are foreseen to be resolved within the next reporting period, although currently there is a YoY non-significant overspending of slightly below 10% over all the partners. The current planning for the remaining project indicates that the needed overall efforts will match the projected ones, i.e. the benefit of increased efforts in the early project phase pays of. APPENDIX: Reference from TID: [cid:image003.png at 01CE5AE6.466FC0F0] [cid:image004.png at 01CE5AE6.466FC0F0] [cid:image005.png at 01CE5AE6.466FC0F0] From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Mittwoch, 15. Mai 2013 09:26 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] periodic report - current status Dear colleagues, as said: we will send out the current status and open points one by one for the pending deliverables to make this a bit transparent. The second one is another "easier" one: periodic report - as we as well invested into this to prepare this thoroughly. Find below the reference to our submission. I got more input from E-IIS on their part which will be part of the final version - did all of you take a second look on our submission or want to change something? Status: submitted to TID for integration with the other chapters Next steps: TID resending it to us, we will distribute and make a second round asking for partner contributions and your deltas. SAP will introduce final statements touching on the overall resource consumption (section at the bottom). Then: submission Given the time frame of Javier, there seems to be another schedule & the delivery is not planned for Friday, this week. Best, /Thorsten From: Sandfuchs, Thorsten Sent: Freitag, 10. Mai 2013 15:04 To: 'JAVIER DE PEDRO SANCHEZ'; 'subsidies at tid.es' Cc: fiware-apps at lists.fi-ware.eu; 'Heller, Markus' Subject: SUBMISSION - WP3 - RE: FI-WARE: Periodic Report - M13 - M24 Dear javier, Find the periodic report out of the WP3 for consolidation with other chapters, attached. Sorry for the late submission Please send the integrated version back to us in order to have an internal review prior to submission and in order to allow us to integrate the final evaluations. The submitted document does not contain some rationals given by the partners, as the numbers were not final so far. We are still missing (although pushing hard) the input from some partners, this will be integrated in the final version, together with the subsuming evaluations. Best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of JAVIER DE PEDRO SANCHEZ Sent: Montag, 15. April 2013 23:07 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: subsidies at tid.es Subject: [Fiware-wpa] FI-WARE: Periodic Report - M13 - M24 Importance: High Dear all As you know we have to deliver the Periodic Report which has to give an overview of the second year of the project (months from M13 (May12) to M24 (Apr13)). I will kindly ask you in another particularized e-mail to update as WPL the information about your WP. The schedule is the following: 1. First request of information to WPL with estimated effort per partner: April 15th, 2013 2. Period to request each WPL to each involved partner its contribution to WP: April 16th, 2013 - Apr 19th, 2013 3. Integration of received information from by each WPL: April 22nd, 2013 - May 5th, 2013 4. WPL send first version of his updated report to Coordinator (subsidies at tid.es): May 6th, 2013 5. Coordinator asks to each partner to update its current effort: April 30th, 2013 6. Each partner sends its current effort according FORM-C 2: May 1st, 2013 - May 10th, 2013 7. Coordinator sends updated data of effort to each WPL: May 15th, 2013 8. Updating of the second version of each report by each WPL: May 16th, 2013 - May 17th, 2013 9. WPL sends final version of his updated report to Coordinator (subsidies at tid.es): May 17th, 2013 10. Integrating and revision by Coordinator: May 20th, 2013 - May 24th, 2013 11. Coordinator sends the Periodic Report to Project Officer: May 28th, 2013 12. Review: June 10th, 2013 At last but not least, please, I kindly ask you to follow the template in order to have a homogeneous report as a team. In the last review report they said: [cid:image001.jpg at 01CE5AE1.4FE3E580] Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 39114 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 39519 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 37597 bytes Desc: image005.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.jpg Type: image/jpeg Size: 40387 bytes Desc: image007.jpg URL: From thorsten.sandfuchs at sap.com Tue May 28 09:47:26 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 28 May 2013 07:47:26 +0000 Subject: [Fiware-apps] Pre-final text of Periodic Report M13-M24 for review and your contributions - DEADLINE: wednesday Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646109911A@DEWDFEMB11A.global.corp.sap> Dear colleagues, Please find attached the WP3 input for the periodic report in the integrated version - where I integrated as well the latest submissions that you provided to us. TID has a very tight schedule on this (delivery planned this week), so please work on this with highest possible priority. Yesterday I already send the task to work on the rationales and paragraphs given in the overall-effort section of WP3 to all of you - now we have the pre-final text as well for your final checks. I integrated both work items and reflected the email from yesterday in the comments of the attached document. You can either send the paragraph as intended yesterday via email or work on it within the document. Please use TRACK CHANGES at all times! Again I would like to emphasize that this exercise is of importance as the reviewers will take the content of this report as basis for budget and effort related questions that might arise from the previous reporting period and the given one. Please: 1. Contribute and react upon the comments provided in the effort-related sections and that do apply to you 2. Review if the input you gave us from your partner perspective is reflected in the final document as you wish it to be reflected. 3. Review if you are in line with the effort statements that SAP is giving in a whole and for the complete work package 4. Make sure that the numbers that you consider final are reflected in this report, if not please let JAVIER DE PEDRO SANCHEZ (jdps at tid.es) know 5. Task 3.3. and Task 3.1 we see no strong order of partner contributions and no overall statements, subsuming these contributions (each TASK LEAD) will be in charge of setting this up, if you think this is appropriate (e.g. strong contributions of strong partners go upfront or major achievements are briefly summarized after the first paragraph. 6. My personal feeling is that our part is good and well written overall. I don't think that we need to adopt many things that are given by other chapters - if you find things in other chapters that we didn't report, but actually did work on please let us know. ? Please send the text back to us WITH TRACK CHANGES ON. Deadline: ASAP, if possible provide you in by Wednesday EOB as in Germany there is a public holiday on Thursday. If you have any comments, problems, questions or concerns, please contact us! My telephone is +496227752562 Thanks for your constant support, /Thorsten PS: it might be advised to deactivate the "Format-Markup-change" to have a better overview of what did change from a pure content perspective. [cid:image001.png at 01CE5B88.5B075490] From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Dienstag, 28. Mai 2013 09:10 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Fwd: [Fiware-wpl] FI-WARE: : First version of Periodic Report M13-M24 FYI -------- Mensaje original -------- Asunto: [Fiware-wpl] FI-WARE: : First version of Periodic Report M13-M24 Fecha: Tue, 28 May 2013 00:11:56 +0000 De: JAVIER DE PEDRO SANCHEZ Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Dear all, First, thank you very much for your contribution. Please find attached the first version of the integrated Periodic Report of M24. I kindly ask you to review it. If you have something in yellow in your WP, please update it. If you see something to be updated of another WP, please contact with the WPL directly. We?ll only accept changes from WPL of each own WP. Please, send your updates before next Thursday 30th of May, EOB. (It is very important to use the activated track change control) Next Friday, it will be update with your last versions and it will be reviewed by the Coordinator in order to deliver the final version next week. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 21146 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.1.2.4-FI-WARE_Periodic_Peport-M13-M24-v2_WP3_FOR_CHECK_AND_REFINEMENT_by_PARTNERS.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 821988 bytes Desc: D.1.2.4-FI-WARE_Periodic_Peport-M13-M24-v2_WP3_FOR_CHECK_AND_REFINEMENT_by_PARTNERS.docx URL: From thorsten.sandfuchs at sap.com Tue May 28 14:55:52 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 28 May 2013 12:55:52 +0000 Subject: [Fiware-apps] FW: [Fiware-wpa] Platform for FI-WARE Webinars In-Reply-To: <51A49A51.2010703@eng.it> References: <51A49A51.2010703@eng.it> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461099BC0@DEWDFEMB11A.global.corp.sap> FYI - if you would like to host a webinar with existing technologie, provided by UPM. -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Davide Dalle Carbonare Sent: Dienstag, 28. Mai 2013 13:52 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: abel at dit.upm.es; Juan Quemada Vives Subject: [Fiware-wpa] Platform for FI-WARE Webinars Dear parters, in order to provide FI-WARE webinars I notify you about the possibility of using the MeshMe.tv platform made available by UPM. To understand how this platform works and how to use it, It's possible to attend to a dedicated presentation on these dates: 1) Wednesday 5th of June from 14h to 15h 2) Thursday 6th of June from 14h to 15h To facilitate the organization of these sessions, please, confirm your attendance by sending a message to both: - Juan Quemada Vives - Abel Carril To enter the webinar session click on: http://www.mashme.tv/M/2qvRiO?mode=1 Requirements for accessing the platform: A browser which supports HTML5 must be used. This includes the last versions of Chrome, Firefox, Opera, Internet Explorer 9 or 10, etc. @WPLs, please, circulate this message in your WP mailing lists in order to involve all the potential users. Thank you and Kind Regards, Davide _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa From markus.heller at sap.com Tue May 28 22:00:11 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 28 May 2013 20:00:11 +0000 Subject: [Fiware-apps] FW: [Fiware-wpa] Fwd: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture Message-ID: <393554EDCF801348BC53C7813C6CB73B091314@DEWDFEMB14A.global.corp.sap> Dear WP3 members, I share with you an E-Mail from Juanjo on the production process / Organization of the FI-WARE Architecture deliverable (I removed the attached document). Best wishes Markus From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 27. Mai 2013 07:45 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Fwd: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture Hi, Please find attached the final official submission of the FI-WARE Architecture deliverable. While carrying out a very final cross-chapter revision, I have identified the need to achieve a better consistency between names of sections in the different chapters and even within chapters: * There were some cases where the section titled "Basic Concepts" within the Architecture Description of a given GE was titled as "Main Concepts". I have changed this wherever I found it * There were some cases where the "Main Interactions" section within the Architecture Description of a given GE was titled as "Main Operations". I have changed this wherever I found it. There were GEs in the Security chapter for which the sections related to Copyright and Legal Notices were missing. This also happens regarding Basic Design Principles. Please add these sections asap. Despite I asked for the names of the companies to be added manually, I got no response. It would be nice that you perform a general review of the structure in your chapters and double-check alignment with the standard structure template we defined. I fixed a lot of the issues but this would be only reflected in the final deliverable so I have produced and already sent to you a version with comments that highlighted the changes you should introduce in the public wiki ASAP (note that this document is marked as private). For your convenience, here it goes the structure of sections that should have been adopted: 1. General Architecture Description of a Chapter: * Introduction * Architecture Overview * * Architecture Description of GEs * Interface to other chapters * References 2. Architecture Description of a given GE: * Copyright * Legal Notice * Overview (Target usage should be inside) * Basic Concepts * Architecture (recommended but optional, sometimes you have put this before "Basic concepts" but it would be nice to keep consistency and place it after) * Main Interactions * Basic Design Principles * Detailed Open Specifications (which should contain the links to the rest of Open Specifications) * References There were also A LOT of inconsistencies regarding level of headings. As an example, there were many chapters where there wasn't a second level heading. This was revealed thanks to the automated generation process and should be fixed in the wiki asap to avoid wrong generation next times. I carried out a final spelling checking to all chapters finding also many typos. I have to confess that I got astonished when I saw still those kind of issues in a so late stage of the peer-review ... Didn't nobody notice that? Despite we incurred in a delay, I have now found that it was worth carrying out this final review. Without giving names, when I have asked "how can we still find this issues?" in the draft I had just reviewed, I got the response "honestly, I believe some people hasn't read the contents in that detail". We honestly have to reconsider how we are carrying out our peer-review processes. I have also carried out several changes to improve overall readability. The detailed Open Specifications where not included in all cases, even within the same chapter, so I have had to put a note to the EC and reviewers explaining that we had decided to keep the inclusion by those GEs that decided to include it, because we will adopt that convention finally. Therefore, please do so. In addition, I also found that the copyright notice in many of the cases was only for 2012. This maybe interpreted by the reviewers as "no single line has been touched by the owners this year" when clearly this doesn't apply. Please fix those Copyright Notices where you have to write 2012-2013 (in the case of new GEs, 2013) Last but not least, there are a number of things that I have detected about which we have to reach a final agreement and adopt a convention across all chapters: * Titles, numbering and format (i.e., centered or not) of figures. I believe that we proposed a convention, and asked to avoid using of figure numbers, but apparently hasn't been followed consistently * Architecture section within a GE Architecture Description * Style for references We should address all of them once we finish with the most urgent things we currently have on our plate, but have them ready at the time we will start disseminating this among the wider community of developers. Please share with members of your respective chapters. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture Date: Mon, 27 May 2013 07:32:02 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom at ec.europa.eu, dgr at whitestein.com, msli at icfocus.co.uk, renaud.difrancesco at eu.sony.com, irena.pavlova at isoft-technology.com CC: INFSO-ICT-285248 at ec.europa.eu, Vanessa.VANHUMBEECK at ec.europa.eu, mcp at tid.es, "jhierro >> \"Juan J. Hierro\"" Dear all, This is the official submission of deliverable D.2.3.2 FI-WARE Architecture. To ease review of its contents, separate files have been produced for the different chapters that made up the whole document. All of these files can be extracted from the .zip file you can download from the following URL: https://forge.fi-ware.eu/docman/view.php/7/2468/D.2.3.2+FI-WARE+Architecture+Official+deliverable.zip Note that the FI-WARE Architecture specification is public and its contents become part of the several FI-WARE GE Open Specifications, therefore you can download this file without logging in your FusionForge account. We haven't delivered it earlier to make sure that it was aligned with the contents of FI-WARE GE Open Specifications that will be delivered along this week (some of them have already been delivered to you). The FI-WARE Architecture has beed produced conducting several peer-reviews and a final whole revision by myself, as chief architect, to ensure overall consistency. You will see that the description of the architecture of some GEs ended with a sections that provides the links to the Detailed Specifications. This doesn't happen in all the cases and will be fixed in subsequent releases of the deliverable. However, we thought it was not critical to add them here because you are going to receive them separately. Note that specifications are still provided together with an interim Legal Notice. This is because the Legal Notice accompanying specifications is still going through a final review by legal representatives of the different partners. This process is about to finish, so we don't expect major issues regarding usage by UC projects within the FI-PPP or impact in the launch of the FI-WARE Open Innovation Lab. Furthermore, differences between the final and interim Legal Notices is rather minor. As you know, the FI-WARE GE Open Specifications are constantly updated on the FI-WARE public wiki. You can refer to contents of the public wiki for the most up-to-date contents of public documentation associated to the FI-WARE project. Don't hesitate to contact us in case you have any question. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From thorsten.sandfuchs at sap.com Wed May 29 07:32:03 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 29 May 2013 05:32:03 +0000 Subject: [Fiware-apps] Pre-final text of Periodic Report M13-M24 for review and your contributions - DEADLINE: wednesday In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6646109911A@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD6646109911A@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646109AA3C@DEWDFEMB11A.global.corp.sap> Dear colleagues, Here is the current set of responses I received so far - deadline is today. Find attached again the email send with the effort overview. Please indicate if you have any problems with the deadlines, then I would need to escalate this to TID. Best, /Thorsten confirmed working on it received OK for partner contribution contributed paragraph for effort deviation contribution considered final, no action required TID MISSING MISSING not needed SAP OK OK OK OK THALES OK OK not needed OK TI MISSING MISSING MISSING DT OK OK OK OK EAB MISSING MISSING still initial version ATOS MISSING MISSING MISSING E-IIS OK MISSING still initial version UPM MISSING MISSING still initial version UDE OK MISSING MISSING iMinds MISSING MISSING still initial version From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Dienstag, 28. Mai 2013 09:47 To: jsoriano at fi.upm.es; Andrea Manieri (manieri at eng.it); camille.reynders at iminds.be; Koen Casier (koen.casier at intec.ugent.be) (koen.casier at intec.ugent.be); Horst.Stein at telekom.de; calin.curescu at ericsson.com; pierre.chatel at thalesgroup.com; MHOMA Youssouf (youssouf.mhoma at thalesgroup.com); Joaquin Iranzo Yuste (joaquin.iranzo at atosresearch.eu); marco.ughetti at telecomitalia.it; fiware-apps at lists.fi-ware.eu; Sammodi, Osama (osama.sammodi at paluno.uni-due.de); Froese, Andreas (andreas.froese at paluno.uni-due.de) Subject: [Fiware-apps] Pre-final text of Periodic Report M13-M24 for review and your contributions - DEADLINE: wednesday Importance: High Dear colleagues, Please find attached the WP3 input for the periodic report in the integrated version - where I integrated as well the latest submissions that you provided to us. TID has a very tight schedule on this (delivery planned this week), so please work on this with highest possible priority. Yesterday I already send the task to work on the rationales and paragraphs given in the overall-effort section of WP3 to all of you - now we have the pre-final text as well for your final checks. I integrated both work items and reflected the email from yesterday in the comments of the attached document. You can either send the paragraph as intended yesterday via email or work on it within the document. Please use TRACK CHANGES at all times! Again I would like to emphasize that this exercise is of importance as the reviewers will take the content of this report as basis for budget and effort related questions that might arise from the previous reporting period and the given one. Please: 1. Contribute and react upon the comments provided in the effort-related sections and that do apply to you 2. Review if the input you gave us from your partner perspective is reflected in the final document as you wish it to be reflected. 3. Review if you are in line with the effort statements that SAP is giving in a whole and for the complete work package 4. Make sure that the numbers that you consider final are reflected in this report, if not please let JAVIER DE PEDRO SANCHEZ (jdps at tid.es) know 5. Task 3.3. and Task 3.1 we see no strong order of partner contributions and no overall statements, subsuming these contributions (each TASK LEAD) will be in charge of setting this up, if you think this is appropriate (e.g. strong contributions of strong partners go upfront or major achievements are briefly summarized after the first paragraph. 6. My personal feeling is that our part is good and well written overall. I don't think that we need to adopt many things that are given by other chapters - if you find things in other chapters that we didn't report, but actually did work on please let us know. ? Please send the text back to us WITH TRACK CHANGES ON. Deadline: ASAP, if possible provide you in by Wednesday EOB as in Germany there is a public holiday on Thursday. If you have any comments, problems, questions or concerns, please contact us! My telephone is +496227752562 Thanks for your constant support, /Thorsten PS: it might be advised to deactivate the "Format-Markup-change" to have a better overview of what did change from a pure content perspective. [cid:image001.png at 01CE5C3E.9C276BC0] From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Dienstag, 28. Mai 2013 09:10 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Fwd: [Fiware-wpl] FI-WARE: : First version of Periodic Report M13-M24 FYI -------- Mensaje original -------- Asunto: [Fiware-wpl] FI-WARE: : First version of Periodic Report M13-M24 Fecha: Tue, 28 May 2013 00:11:56 +0000 De: JAVIER DE PEDRO SANCHEZ Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Dear all, First, thank you very much for your contribution. Please find attached the first version of the integrated Periodic Report of M24. I kindly ask you to review it. If you have something in yellow in your WP, please update it. If you see something to be updated of another WP, please contact with the WPL directly. We?ll only accept changes from WPL of each own WP. Please, send your updates before next Thursday 30th of May, EOB. (It is very important to use the activated track change control) Next Friday, it will be update with your last versions and it will be reviewed by the Coordinator in order to deliver the final version next week. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 21146 bytes Desc: image001.png URL: -------------- next part -------------- An embedded message was scrubbed... From: "Sandfuchs, Thorsten" Subject: [Fiware-apps] Periodic Report M13-M24 - next steps - DEADLINE: wednesday this week! Date: Mon, 27 May 2013 14:00:35 +0000 Size: 334296 URL: From thorsten.sandfuchs at sap.com Wed May 29 10:11:50 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 29 May 2013 08:11:50 +0000 Subject: [Fiware-apps] M24-review slides preparation and input Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646109AF3B@DEWDFEMB11A.global.corp.sap> Dear colleagues, find down below the link to our current rough agenda as described in the previous calls - seeking for your input and comments. We introduced blank sheets with rough content guidance for the major topics as foreseen. This is still not written in stone and currently we should focus on first finding the right set of "basis data" - later we can make it presentable. Some slides have indications what patners we think should contribute - please act accordingly or raise this to us, if you feel uncomfortable. https://forge.fi-ware.eu/docman/view.php/12/2506/2013-06-WP3_business_framework_for-4th-review+-+For+Partner+Input.pptx Please upload contributions on this directory in our docman and mark it afterwards as "private" https://forge.fi-ware.eu/docman/new.php?group_id=12&selected_doc_group=439 Thanks for any comments/contributions/etc /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Wed May 29 11:28:19 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 29 May 2013 09:28:19 +0000 Subject: [Fiware-apps] FI-WARE Catalogue access and entries Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646109B255@DEWDFEMB11A.global.corp.sap> Dear colleagues providing GEs in V2.X, soon there will be new guidance and related actions to update entries in the catalogue http://catalogue.fi-ware.eu/enablers?chapter_tid=1 .... but we can as well start with the obvious things independent to central guidance of TID - in the end this will as well help us to prepare the review! Please for the new GEs and as well for the ones that provided anything in v2.2: - Make you again familiar with the catalogue system and how to edit stuff there - Apply and register for an account on the system in order to allow changes (if you didn't do this before) - Especially talk to your company internal decision makers to prepare the relevant statements on the "Terms and Condictions" tab - related dimensions are o Experiments within FI-PPP o Open innovation lab o External availability ? Example at http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud/terms-and-conditions - Integrate the link to software binary for v2 which is presented in http://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/D.3.2.2_FI-WARE_SW_Release_report in your existing entries My analysis shows the following needed changes (which might still - TI/THALES Mediator_TI http://catalogue.fi-ware.eu/enablers/mediator-mediatorti o Unclear if THALES contribution should be represented here or with a separate entry - needs to be clarified ASAP and acted upon o Terms and conditions does not follow the proposed structure (see above) - DT http://catalogue.fi-ware.eu/enablers/service-mashup-mashup-factory o Terms and conditions does not follow the proposed structure (see above) - EAB http://catalogue.fi-ware.eu/enablers/service-composition-ericsson-composition-engine-ece o First rough analysis: OK - UPM: Wirecloud o First rough analysis: OK - ATOS: LightSemantic Composition o First rough analysis: OK NEW GEs UPM, iMinds, TID, SAP: please prepare the needed information - if not in the system, please use the fiware-apps wiki or a word template to compile the needed text and follow the Currently there is still an internal approval process in place which prevents edits from being displayed - so my assumptions might be as well based on the wrong data - sorry for that. And again: there might be more central guidance coming up from TID on this topics within the next days, but the topics mentioned above almost certainly will apply in any case. Thanks for your support and best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Wed May 29 12:08:48 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 29 May 2013 10:08:48 +0000 Subject: [Fiware-apps] FI-ware overview session webinar for UC2 projects - REPLAY Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646109B3CF@DEWDFEMB11A.global.corp.sap> Dear WP3 colleagues Please join us in our schedule webinar on Apps and services for FI-PPP phase 2 projects REPLAY - on the 4.06.2013 / 14:00 CET outlining the core capabilities of the FI-WARE "apps and services" chapter and giving the relevant pointers for further collaborations. Please as well feel yourself encouraged to add to the discussion and proactively ask questions in relation to the presentation prior, after or during the meeting. Thanks for your interest and looking forward to the session with you. Best regards /Thorsten Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ <- follow this link to join the meeting If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Country Number Germany, Frankfurt tel:+4969222210764 Europe Austria, Vienna tel:+431253021750 France, Paris tel:+33170701777 Italy, Milan tel:+390236009839 Spain, Madrid tel:+34917699443 Switzerland, Zurich tel:+41434569248 UK, London tel:+442033645639 Oversea Australia, Sydney tel:+61290090688 India, Bangalore tel:+918061275055 USA, New York tel:+16464340499 -- Thorsten Sandfuchs SAP AG SAP Research Center Karlsruhe Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4193 bytes Desc: not available URL: From thorsten.sandfuchs at sap.com Wed May 29 17:19:44 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 29 May 2013 15:19:44 +0000 Subject: [Fiware-apps] Pre-final text of Periodic Report M13-M24 for review and your contributions - DEADLINE: wednesday In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6646109AA3C@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD6646109911A@DEWDFEMB11A.global.corp.sap> <2981E9D6242FCF47ADC9B5DBA5DFD6646109AA3C@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646109BC73@DEWDFEMB11A.global.corp.sap> Dear colleagues, The current status (towards EOB) is the listed below. As TI won't be able to deliver prior to Friday we renegotiated the deadline overall and will accept _small_ changes until Friday morning. In general: if I don't hear anything until Thursday evening from the partners listed below as "MISSING", I will consider their current input as final and respectively submit without further consideration. Questions related to this posted by the reviewers will be distributed directly to you. Best, /Thorsten confirmed working on it received OK for partner contribution contributed paragraph for effort deviation contribution considered final, no action required TID OK OK not needed OK SAP OK OK OK OK THALES OK OK not needed OK TI OK MISSING STALLING (Fr) DT OK OK OK OK EAB MISSING MISSING still initial version ATOS OK OK MISSING E-IIS OK OK OK OK UPM MISSING MISSING still initial version UDE OK MISSING MISSING iMinds OK MISSING OK From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Mittwoch, 29. Mai 2013 07:32 To: jsoriano at fi.upm.es; Andrea Manieri (manieri at eng.it); camille.reynders at iminds.be; Koen Casier (koen.casier at intec.ugent.be) (koen.casier at intec.ugent.be); Horst.Stein at telekom.de; calin.curescu at ericsson.com; pierre.chatel at thalesgroup.com; MHOMA Youssouf (youssouf.mhoma at thalesgroup.com); Joaquin Iranzo Yuste (joaquin.iranzo at atosresearch.eu); marco.ughetti at telecomitalia.it; fiware-apps at lists.fi-ware.eu; Sammodi, Osama (osama.sammodi at paluno.uni-due.de); Froese, Andreas (andreas.froese at paluno.uni-due.de) Subject: Re: [Fiware-apps] Pre-final text of Periodic Report M13-M24 for review and your contributions - DEADLINE: wednesday Dear colleagues, Here is the current set of responses I received so far - deadline is today. Find attached again the email send with the effort overview. Please indicate if you have any problems with the deadlines, then I would need to escalate this to TID. Best, /Thorsten confirmed working on it received OK for partner contribution contributed paragraph for effort deviation contribution considered final, no action required TID MISSING MISSING not needed SAP OK OK OK OK THALES OK OK not needed OK TI MISSING MISSING MISSING DT OK OK OK OK EAB MISSING MISSING still initial version ATOS MISSING MISSING MISSING E-IIS OK MISSING still initial version UPM MISSING MISSING still initial version UDE OK MISSING MISSING iMinds MISSING MISSING still initial version From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Dienstag, 28. Mai 2013 09:47 To: jsoriano at fi.upm.es; Andrea Manieri (manieri at eng.it); camille.reynders at iminds.be; Koen Casier (koen.casier at intec.ugent.be) (koen.casier at intec.ugent.be); Horst.Stein at telekom.de; calin.curescu at ericsson.com; pierre.chatel at thalesgroup.com; MHOMA Youssouf (youssouf.mhoma at thalesgroup.com); Joaquin Iranzo Yuste (joaquin.iranzo at atosresearch.eu); marco.ughetti at telecomitalia.it; fiware-apps at lists.fi-ware.eu; Sammodi, Osama (osama.sammodi at paluno.uni-due.de); Froese, Andreas (andreas.froese at paluno.uni-due.de) Subject: [Fiware-apps] Pre-final text of Periodic Report M13-M24 for review and your contributions - DEADLINE: wednesday Importance: High Dear colleagues, Please find attached the WP3 input for the periodic report in the integrated version - where I integrated as well the latest submissions that you provided to us. TID has a very tight schedule on this (delivery planned this week), so please work on this with highest possible priority. Yesterday I already send the task to work on the rationales and paragraphs given in the overall-effort section of WP3 to all of you - now we have the pre-final text as well for your final checks. I integrated both work items and reflected the email from yesterday in the comments of the attached document. You can either send the paragraph as intended yesterday via email or work on it within the document. Please use TRACK CHANGES at all times! Again I would like to emphasize that this exercise is of importance as the reviewers will take the content of this report as basis for budget and effort related questions that might arise from the previous reporting period and the given one. Please: 1. Contribute and react upon the comments provided in the effort-related sections and that do apply to you 2. Review if the input you gave us from your partner perspective is reflected in the final document as you wish it to be reflected. 3. Review if you are in line with the effort statements that SAP is giving in a whole and for the complete work package 4. Make sure that the numbers that you consider final are reflected in this report, if not please let JAVIER DE PEDRO SANCHEZ (jdps at tid.es) know 5. Task 3.3. and Task 3.1 we see no strong order of partner contributions and no overall statements, subsuming these contributions (each TASK LEAD) will be in charge of setting this up, if you think this is appropriate (e.g. strong contributions of strong partners go upfront or major achievements are briefly summarized after the first paragraph. 6. My personal feeling is that our part is good and well written overall. I don't think that we need to adopt many things that are given by other chapters - if you find things in other chapters that we didn't report, but actually did work on please let us know. ? Please send the text back to us WITH TRACK CHANGES ON. Deadline: ASAP, if possible provide you in by Wednesday EOB as in Germany there is a public holiday on Thursday. If you have any comments, problems, questions or concerns, please contact us! My telephone is +496227752562 Thanks for your constant support, /Thorsten PS: it might be advised to deactivate the "Format-Markup-change" to have a better overview of what did change from a pure content perspective. [cid:image001.png at 01CE5C90.85A21100] From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Dienstag, 28. Mai 2013 09:10 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Fwd: [Fiware-wpl] FI-WARE: : First version of Periodic Report M13-M24 FYI -------- Mensaje original -------- Asunto: [Fiware-wpl] FI-WARE: : First version of Periodic Report M13-M24 Fecha: Tue, 28 May 2013 00:11:56 +0000 De: JAVIER DE PEDRO SANCHEZ Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Dear all, First, thank you very much for your contribution. Please find attached the first version of the integrated Periodic Report of M24. I kindly ask you to review it. If you have something in yellow in your WP, please update it. If you see something to be updated of another WP, please contact with the WPL directly. We?ll only accept changes from WPL of each own WP. Please, send your updates before next Thursday 30th of May, EOB. (It is very important to use the activated track change control) Next Friday, it will be update with your last versions and it will be reviewed by the Coordinator in order to deliver the final version next week. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 21146 bytes Desc: image001.png URL: From thorsten.sandfuchs at sap.com Fri May 31 11:54:41 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 31 May 2013 09:54:41 +0000 Subject: [Fiware-apps] M24-review slides preparation and input In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6646109AF3B@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD6646109AF3B@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646109DA18@DEWDFEMB11A.global.corp.sap> Dear colleagues, Please submit your slides previous to our weekly concall on 13:00 CEST in order for us to screen them internally. Thanks From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Mittwoch, 29. Mai 2013 10:12 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] M24-review slides preparation and input Dear colleagues, find down below the link to our current rough agenda as described in the previous calls - seeking for your input and comments. We introduced blank sheets with rough content guidance for the major topics as foreseen. This is still not written in stone and currently we should focus on first finding the right set of "basis data" - later we can make it presentable. Some slides have indications what patners we think should contribute - please act accordingly or raise this to us, if you feel uncomfortable. https://forge.fi-ware.eu/docman/view.php/12/2506/2013-06-WP3_business_framework_for-4th-review+-+For+Partner+Input.pptx Please upload contributions on this directory in our docman and mark it afterwards as "private" https://forge.fi-ware.eu/docman/new.php?group_id=12&selected_doc_group=439 Thanks for any comments/contributions/etc /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Fri May 31 14:28:20 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 31 May 2013 12:28:20 +0000 Subject: [Fiware-apps] live demonstrator session for WP3 partners Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646109DD52@DEWDFEMB11A.global.corp.sap> As discussed and announced during out weekly WP3 call, UPM will be able to comment on the current plan and present the status of the LiveDemonstrator within this slot. It would be good if you make yourself available. Please join me in a Connect Pro Meeting at: https://sap.emea.pgiconnect.com/fiware_heller/ <- follow this link to join the meeting If you have never attended a Connect Pro meeting before: Test your connection: https://sap.emea.pgiconnect.com/common/help/en/support/meeting_test.htm Audio Conference Details: Audio Conference Participant Code: 124 225 3329 Conference Phone Numbers: Country Number Germany, Frankfurt tel:+4969222210764 Europe Austria, Vienna tel:+431253021750 France, Paris tel:+33170701777 Italy, Milan tel:+390236009839 Spain, Madrid tel:+34917699443 Switzerland, Zurich tel:+41434569248 UK, London tel:+442033645639 Oversea Australia, Sydney tel:+61290090688 India, Bangalore tel:+918061275055 USA, New York tel:+16464340499 -- Thorsten Sandfuchs SAP AG SAP Research Center Karlsruhe Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3789 bytes Desc: not available URL: From markus.heller at sap.com Fri May 31 15:18:49 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 31 May 2013 13:18:49 +0000 Subject: [Fiware-apps] FW: [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B8905173D@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B8905173D@EX10-MB2-MAD.hi.inet> Message-ID: <393554EDCF801348BC53C7813C6CB73B15BBCC60@DEWDFEMB14A.global.corp.sap> Hi WP3, Please act accordingly with the deadlines mentioned. Best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Donnerstag, 30. Mai 2013 17:50 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers Dear Partners, Let me remind you that we are finishing sprint S2.3.2-M25 and about to start S2.3.3-M26. Please, be aware S2.3.3 is the last sprint of the second major release. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Please, update your backlog accordingly: * Close the backlog items finished during M25 (if not already done) * Update items under execution not finished to belong to S2.3.3 * Proceed to identify the backlog items for next sprint Let me inform you that the trackers have implemented the new features: * Bug is available as entry type - theme isn't available anymore * You can update sprints and releases by selecting them on a select box. The old release and sprint fields will exist until we transfer data to the new fields. * You have available all states for the backlog items, let me remind: o Open -> defined o Scheduled -> mean those selected for the current sprint and release o Under execution -> developing them o Impeded -> items cannot be progressed because something else prevents you doing it o Under verification -> validating them o Closed -> finished successfully * All chapters have available the GE Implementation field. If you had any doubt, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From markus.heller at sap.com Fri May 31 17:55:32 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 31 May 2013 15:55:32 +0000 Subject: [Fiware-apps] WP3 Review Slide Deck Prep: Please contribute asap Message-ID: <393554EDCF801348BC53C7813C6CB73B15BBCE5D@DEWDFEMB14A.global.corp.sap> Hi, as discussed today in the WP3 telco please find here the PPT: https://forge.fi-ware.eu/docman/view.php/12/2533/2013-06-WP3_business_framework_for-4th-review+-+For+Partner+Input_v2.pptx Your input is missing. Please provide your input here on the relevant slides ASAP (best Tuesday EOB). Please contact us immediately if you have problems with filling in your input since we cannot waste time next week Best wishes Markus From markus.heller at sap.com Fri May 31 18:13:29 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 31 May 2013 16:13:29 +0000 Subject: [Fiware-apps] WP3 Review Slide Deck Prep: Please contribute asap In-Reply-To: <393554EDCF801348BC53C7813C6CB73B15BBCE5D@DEWDFEMB14A.global.corp.sap> References: <393554EDCF801348BC53C7813C6CB73B15BBCE5D@DEWDFEMB14A.global.corp.sap> Message-ID: <393554EDCF801348BC53C7813C6CB73B15BBCE93@DEWDFEMB14A.global.corp.sap> Hi WP3, as discussed today in the WP3 telco please find here the PPT: https://forge.fi-ware.eu/docman/view.php/12/2533/2013-06-WP3_business_framework_for-4th-review+-+For+Partner+Input_v2.pptx Your input is missing. Please provide your input here on the relevant slides ASAP (best Tuesday EOB). Please contact us immediately if you have problems with filling in your input since we cannot waste time next week Best wishes Markus