Adding Davide Zerbetto (I will be out of office for the entire week). Alessandro Portosa Technical Consultant [X][1513603850060_logotipo_knowage_150px.png] Knowage Labs Engineering Group Via G. Marconi, 10 - 40131 Bologna - Italy Tel. + 39 051 0435090 Skype alessandro.portosa www.knowage-suite.com<http://www.knowage-suite.com/> - www.eng.it<http://www.eng.it/web/eng_en/home> The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. ________________________________ Da: Juanjo Hierro <juanjose.hierro at fiware.org> Inviato: martedì 3 aprile 2018 14:39:09 A: 'fiware-tech-help at lists.fiware.org'; José Manuel Cantera; Portosa Alessandro Oggetto: Fwd: Fiware & FASHION CLOUD (IMPACT Accelerator) I forward this to the tech-help inbox as to make sure that a ticket is created and assigned to Jose Manuel and Alessandro. Juanjo Hierro Chief Technology Officer juanjose.hierro at fiware.org<mailto:juanjose.hierro at fiware.org> www.linkedin.com/in/jhierro<https://www.linkedin.com/in/jhierro> Twitter: @fiware<https://twitter.com/fiware> @JuanjoHierro<https://twitter.com/JuanjoHierro> [cid:part5.807BCD8C.8B158D0A at fiware.org] -------- Forwarded Message -------- Subject: Fiware & FASHION CLOUD Date: Tue, 3 Apr 2018 10:21:16 +0200 From: Martin Brücher <martin.bruecher at fashion.cloud><mailto:martin.bruecher at fashion.cloud> To: Juanjo Hierro <juanjose.hierro at fiware.org><mailto:juanjose.hierro at fiware.org>, José Manuel Cantera <josemanuel.cantera at fiware.org><mailto:josemanuel.cantera at fiware.org>, Portosa Alessandro <Alessandro.Portosa at eng.it><mailto:Alessandro.Portosa at eng.it>, Davide Zerbetto <davide.zerbetto at eng.it><mailto:davide.zerbetto at eng.it> CC: Florian Klemt <florian.klemt at fashion.cloud><mailto:florian.klemt at fashion.cloud> Good morning everyone, I hope you guys had a great Easter holiday. We would like to ask you for a consolidated feedback on our suggested Fiware implementation. Florian sent an email on March 27th and José confirmed the setup on the same day. Florian also had a call with the Knowage team to get their advice and during the call our setup was confirmed. Now Davide wrote another mail on March 29th saying that he sees some issues with the Knowage implementation. However it doesn't really contain a concrete advice what we can improve. Therefore we'd be very happy if you could confirm the setup as soon as possible or otherwise provide detailed specification what you expect so that we can present a proper solution on Friday. Thanks a lot in advance and have a great week! Best regards Martin _____ On our side looks good. ccing Alessandro. Please send us an invitation for the checkpoint on April 6th. Best On 27 Mar 2018, at 12:37, Florian Klemt <florian.klemt at fashion.cloud<mailto:florian.klemt at fashion.cloud>> wrote: Hello everyone, thanks again for the chance to present our implementation of Fiware in the FASHION CLOUD application. To make sure that we will meet your expectations for the final assessment, we present our proposed implementation: * Our core Business Intelligence and Data Analytics Service will be solely based on Fiware technologies * Our Application will publish relevant events to the Orion Context Broker. Following Events will be implemented for the final assessment: * a new user signed up * a new file was shared on the Platform * a file was downloaded by a user * a file was deleted by the owner * Since our main use case is to enable users to share Fashion related data/files, these are the most relevant events in our system * We will connect Knowage with the Context Broker to be able to visualize data in real time. To do that we will connect Cygnus to Orion in order to persist the data in a MySQL database. This MySQL database will then be the data source for Knowage. This setup was recommended to us in a previous technical call * We will configure Knowage to use the MySQL data source that get automatically updated as soon as new events are broadcast by Orion * We will set up a dashboard to visualize the incoming data * All of this will deployed to production servers and integrated in our production application We will also share a vision of our roadmap for the FASHION CLOUD BI and Analytics Service: After we have successfully set up the Data Dashboard and customized it to our needs, the plan is to extend this system to get real time notifications of certain events or event constellations. To be able to do that we plan to integrate the Complex Event Processing GE (CEP) to allow us to analyze the generated data in real time. The foundation that we lay now will be the basis for the future development of our Analytics Service. We are more than happy to share this development in blog posts or other means to support other teams to buid a similar monitoring setup. Please let us know if this meets your expectations. Thanks you very much and best regards, Martin & Florian -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20180403/d07c5148/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: foundation-logo.png Type: image/png Size: 8201 bytes Desc: foundation-logo.png URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20180403/d07c5148/attachment-0002.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-1513603850.png Type: image/png Size: 3338 bytes Desc: Outlook-1513603850.png URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20180403/d07c5148/attachment-0003.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy