Dear Monica, This is not the best way to prepare the agenda of such an important (despite ad-hoc) review, definitely. I know you agree with me. Even now, some GE owners still do not know whether their product will be under the eyes of the reviewers. I've started to work with Francisco to prepare a couple of slides focused on the business framework and, in particular, on the joint task force we have already started jointly with the TMForum to integrate their APIs in the BF Ref. Arch. I think that this is a great milestone in terms of standardization, visibility and impact. Bearing in mind that they do not have a reference implementation of their own APIs (just a sandbox to try and test them), it could be also a great opportunity to provide such an open implementation through the FIWARE BF. This will not be a two-day work, but a great effort. It is nevertheless work in progress and in September we plan to have a f2f meeting after the first 3-4 conf calls. Apart from this, we will also say a few words about the adoption in the A16 (the information available is very sparse, but it put it clear that the BF is in use, we are in contact with some startups that are using the BF in their products and I think that it is worth to mention it). Best regards, Javier 2015-07-27 12:59 GMT+02:00 Monica Franceschini <monica.franceschini at eng.it>: > Dear all, > please read the mail sent by Juanjo: since Arian's request i still very > undefined, he asks for a presentation for the whole Business Framework . > Reading the emails below, you can find the best way to proceed. > Thank you, > Monica > > > > -------- Messaggio Inoltrato -------- Oggetto: [Fiware-chapter-leaders] > Fwd: Re: Review of the FI-CORE contract Data: Mon, 27 Jul 2015 08:24:00 > +0200 Mittente: Juanjo Hierro <juanjose.hierro at telefonica.com> > <juanjose.hierro at telefonica.com> A: > fiware-chapter-architects at lists.fi-ware.org > <fiware-chapter-architects at lists.fi-ware.org> > <fiware-chapter-architects at lists.fi-ware.org>, > fiware-chapter-leaders at lists.fi-ware.org > <fiware-chapter-leaders at lists.fi-ware.org> > <fiware-chapter-leaders at lists.fi-ware.org>, > fiware-wg-leaders at lists.fi-ware.org <fiware-wg-leaders at lists.fi-ware.org> > <fiware-wg-leaders at lists.fi-ware.org> > > Hi, > > Please find enclosed the email I sent to Arian with the proposed agenda > for the review. > > It is still unclear what concrete GEs, other than the new ones, are more > in their target for stopping the funding. Knowing it would allow us to > focus what GEs we can cover in the specific slot of 2 hours we are > proposing. However, with his response to my email on July 24th, Arian is > basically saying "everything is subject to stop getting funded". Let's > see how he reacts to my last email on the agenda where I'm insisting in > getting a more concrete list before sending the materials. > > If he insist in his message, we shall then only forward the > presentations about new GEs and focus the 2 hours slot in the agenda we > have proposed on new GEs (I would include Kiara here). Still > presentations regarding the Cloud, Advanced UI and Security chapters should > be prepared as backup as I suggested. This would help to be prepared in > the event a discussion takes place. Based on the email sent by Arian, we > should prepare also slides regarding the IoT chapter, elaborating on the > new Reference Architecture recently discussed (AP initially on Carlos but > since he is on holidays I would suggest that Thierry takes the action) and > the Apps chapter (AP on Javier) probably making some reference to work > under way with TMForum regarding the Business Framework. > > Best regards, > > -- Juanjo > > ______________________________________________________ > > Coordinator and Chief Architect, FIWARE platform > CTO Industrial IoT, Telefónica > > email: juanjose.hierro at telefonica.com > > twitter: @JuanjoHierro > > You can follow FIWARE at: > website: http://www.fiware.org > twitter: @FIWARE > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > > -------- Forwarded Message -------- Subject: Re: Review of the FI-CORE > contract Date: Mon, 27 Jul 2015 08:08:05 +0200 From: Juanjo Hierro > <juanjose.hierro at telefonica.com> <juanjose.hierro at telefonica.com> To: > Arian.ZWEGERS at ec.europa.eu, miguel.carrillopacheco at telefonica.com CC: > Jesus.Villasante at ec.europa.eu, Peter.Fatelnig at ec.europa.eu, > CNECT-ICT-632893 at ec.europa.eu, Juanjo Hierro > <juanjose.hierro at telefonica.com> <juanjose.hierro at telefonica.com> > > Dear Arian, > > Please find enclosed a proposed agenda for the review. > > The general questions about clear definition of what a FIWARE GE is can > be covered in the first slot about "Overall status. Evolution of the FIWARE > concept" if it is ok with you. > > Still we would like to have a explicit list of FIWARE GEs (not only > limited to new GEs) about which you believe it is likely that their funding > be stopped. I guess this doesn't affect all the GEs. We propose to have > a specific slot to discuss about them, strictly limited to two hours in the > overall agenda. > > We would appreciate your feedback. > > Best regards, > > -- Juanjo Hierro > > ______________________________________________________ > > Coordinator and Chief Architect, FIWARE platform > CTO Industrial IoT, Telefónica > > email: juanjose.hierro at telefonica.com > > twitter: @JuanjoHierro > > You can follow FIWARE at: > website: http://www.fiware.org > twitter: @FIWARE > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > On 26/07/15 14:16, Arian.ZWEGERS at ec.europa.eu wrote: > > Dear Juanjo, > > > > Below is a list of GEs that may be discussed. We explicitly do NOT expect > a presentation that covers all GEs in the list; we don't see the value in > that. We expect that the consortium will give a clear definition of what a > FIWARE Enabler is. What distinguishes a FIWARE Enabler from what anyone can > get open source? Then, how do the items on the list below fit in the > definition? > > A second step would be to look at the GEs that are considered valuable by > the A16 subgrantees. That step is outside the scope of this review meeting. > > > > Best regards, > > Arian. > > > > Cloud Chapter > > Self-Service Interfaces Cloud - Portal > > IaaS Resource Management > > Object Storage > > Software Deployment and Configuration - Sagitta > > PaaS Manager - Pegasus > > Monitoring > > Policy Manager - Bosun > > Data Chapter > > BigData Analysis - Cosmos > > Apps Chapter > > Repository - Repository RI > > Marketplace - WMarket > > Store - WStore > > Revenue Settlement and Sharing System - RSS RI > > Application Mashup - Wirecloud > > Data Viz - SpagoBI > > IoT Chapter > > Configuration Manager - IoT Discovery > > Configuration Management - Orion Context Broker > > IoT Broker > > Backend Device Management - IDAS > > Gateway Data Handling - EspR4FastData > > Protocol Adapter - MR CoAP > > Security Chapter > > Security Monitoring > > PEP Proxy - Wilma > > Authorization PDP - AuthZForce > > Content Based Security - CBS > > I2ND Chapter > > Network Information and Control - OFNIC > > Advanced Web-based User Interface > > 2D-UI > > 3D-UI-XML3D > > Synchronization > > Cloud Rendering > > 3DUI - WebTundra > > GIS Data Provider - Geoserver/3D > > POI Data Provider > > 2D/3D Capture > > Augmented Reality > > Real Virtual Interaction > > Virtual Characters > > Interface Designer > > > > *From:* Juanjo Hierro [mailto:juanjose.hierro at telefonica.com > <juanjose.hierro at telefonica.com>] > *Sent:* Friday, July 24, 2015 1:33 PM > *To:* ZWEGERS Arian (CNECT); miguel.carrillopacheco at telefonica.com > *Cc:* VILLASANTE Jesus (CNECT); FATELNIG Peter (CNECT); CNECT-ICT-632893 > *Subject:* Re: Review of the FI-CORE contract > > > > Dear Arian, > > In your email, you make a explicit reference to FIWARE GEs that will be > analyzed during the FI-Core review in order to determine whether it is > appropriate to stop the funding assigned to them for their > evolution/maintenance/support. However you also mentioned that some other > FIWARE GEs may get analyzed based on elements like the followings: > > · FIWARE GEs that are separate, i.e. standing on their own, > without links to selected Enablers, and that are not integratable > > · FIWARE GEs that have “low FIWAREness†, based on agreed > definition of FIWAREness, e.g. NGSI-compliance > > · FIWARE GEs that are considered less potentially valuable, > resulting from the A16 input analysis > > Could you provide a list of FIWARE GEs (existing or old) about which we > should prepare a presentation at the FI-Core review? > > Thanks in advance, > > -- Juanjo > > ______________________________________________________ > > > > Coordinator and Chief Architect, FIWARE platform > > CTO Industrial IoT, Telefónica > > > > email: juanjose.hierro at telefonica.com > > twitter: @JuanjoHierro > > > > You can follow FIWARE at: > > website: http://www.fiware.org > > twitter: @FIWARE > > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > On 22/07/15 19:02, Juanjo Hierro wrote: > > Dear Arian, > > Given the fact that the issue about stopping funding of the activities > linked to several new/existing FIWARE GEs has been put on the table, the > affected partners have requested to be present at the review. > > Based on current expressions of interests, an attendance of 20 people is > foreseen. We kindly ask you to book a room suitable for this attendance. > > On Friday morning we will sent to you the final list of attendees with > the corresponding national ids for security reasons. > > Best regards, > > -- Juanjo > > ______________________________________________________ > > > > Coordinator and Chief Architect, FIWARE platform > > CTO Industrial IoT, Telefónica > > > > email: juanjose.hierro at telefonica.com > > twitter: @JuanjoHierro > > > > You can follow FIWARE at: > > website: http://www.fiware.org > > twitter: @FIWARE > > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > On 16/07/15 09:47, Arian.ZWEGERS at ec.europa.eu wrote: > > Dear Juanjo, Miguel, > > > > As mentioned below, a review of the FI-Core activities is necessary to > refocus the project on today’s priorities of the programme and to allow > the project to stay relevant, efficient and effective. > > > > Therefore, the following elements should be covered in this review meeting: > > 1. Problem Statement: what are the shortcomings the A16 > subgrantees and other customers have identified with respect to: > > o Competitive advantage of the FIWARE enablers as compared to other > existing solutions > > o Quality of enablers (specifications, software, documentation, …) > > o Support for the enablers > > o FIWARE Lab (design, capacity, usability, and customer support) > > o Sustainability (strategy) > > 2. Analysis: for each of the points above, why is it > (perceived as) a problem? What are the causes? > > 3. Way forward: general directions and principles > > 4. Proposed changes to the existing workplan > > > > > > Based on internal discussions and discussions with experts, we believe > that the following points should be reviewed: > > 1. Way forward: general directions and principles > > a. Focus on a small number of enablers > > · Based on (the maturity of) FIWAREness: what does it mean to be a > FIWARE enabler? What sets a FIWARE enabler apart from other solutions? Why > should a certain component be called a "FIWARE enabler"? > > · Based on potential value for customers, i.e. subgrantees and other > third parties, during the lifetime of the FI-PPP > > b. Increased usage of professional expertise, either from the > consortium's companies (but outside their research departments) or outside > the consortium > > c. Ongoing activities would strongly benefit from a change of > way-of-working > > 2. Proposed changes: > > a. Usefulness of existing activities > > · Stop GEs that have “low FIWAREness†, based on agreed definition > of FIWAREness, e.g. NGSI-compliance. > > · Stop development of GEs that are considered less potentially > valuable, resulting from the A16 input analysis > > · Stop development on new GEs: > > · Cross-region enablement > > · Event Driven Orchestration > > · I2ND > > · Open Data Support -/- Open Data Portal > > · Data Visualisation and Analysis > > · Stop enablers that are separate, i.e. standing on their own, without > links to selected Enablers, and that are not integratable. > > · Stop the demos in WP1.1 > > · Stop sponsoring 2 out of 6 Campus Party events > > b. Competitive advantage of the FIWARE enablers as compared to other > existing solutions > > · Strengthen FIWAREness > > · Improve interoperability of Enablers with each other > > c. Quality of enablers > > · Implement a stress test focused on reliability and scalability > > · Extend friendly testing to all supported enablers > > · Implement a wide-ranging bounty program to improve quality > > · Implement a high-quality technical support to developers and > accelerators based on a service-level agreement > > d. Support for the enablers > > · Improve support (e.g. helpdesk) related to enablers > > · Improve documentation > > · Give “how-to†examples, improve usability of enablers > > · Improve training materials and tutorials, e.g. by involving two > Mexican partners > > e. FIWARE Lab > > · Provide a reliable plan to ensure that no bottlenecks in networking > and computing performance will occur > > · Provide attractive trial user places and allow a much wider > participation of users outside Phase 3 > > · Consider stopping the federation of nodes > > · Improve availability and usability of the Lab > > · Improve support related to the Lab based on a service-level agreement > > · Provide appropriate access to open data sources linked into FIWARE > Lab (e.g. in collaboration with the Connecting Europe Facility) > > f. Sustainability (strategy) > > · Appoint an (external) community manager (team) to drive the building > of the open source community > > · Set up a foundation before end 2015 and implement the transition of > FIWARE in a foundation led initiative > > · Enlarge the industrial commitment with companies interested to > become long-term partners in the FIWARE foundation and support the open > source community > > · Get pre-commercial providers as new partners (part of the open > call(s)) > > · Implement a FIWARE application store > > · Implement an outreach program for H2020 projects considering/using > FIWARE, including support and training > > · Improve dramatically social media outreach, move from communications > to marketing, improve showcasing of success stories > > g. Other > > · Present a clear plan for the use of the resources dedicated to the > open call (10% of the overall budget) > > Best regards, > > Arian > > > > _____________________________________________ > *From:* QUENTAL MENDES Lisete (CNECT) *On Behalf Of *VILLASANTE Jesus > (CNECT) > *Sent:* Monday, June 15, 2015 2:44 PM > *To:* 'juanjose.hierro at telefonica.com' > *Cc:* FATELNIG Peter (CNECT); ZWEGERS Arian (CNECT) > *Subject:* Review of the FI-CORE contract > *Importance:* High > > > > > > Dear Juanjo, > > Further to our conversation during the FIWARE Accelerator meeting in Paris > on 12 June, I summarise below the main guidance for the upcoming review of > the FI-CORE contract. > > To review the activities of FI-CORE is critically necessary in order to > refocus the project on todays priorities of the FIWARE programme and to > allow the project to stay relevant, efficient and effective. The outcome of > this may lead to an amendment of the contract with a revised technical > annex. > > Considering the clear forward-looking objective of this ad-hoc review, it > will deviate to some extent from the regular review process and focus less > on progress achieved, checking deliverables and matching resources to plans > (this will be done in the next annual review). Rather the specific topics > for the review will concentrate on key project activities crucial for the > success of the project and the FI-PPP Phase 3. The agenda of the ad-hoc > review meeting and the conversation with the experts, the Commission > services and the project team, will address: > > · *Quality of the existing set of enablers*. How best to reach a > production level quality on all enablers on offer. Consider a > 'service-level agreement'-like support for developers for a high level > technical support to developers and accelerators. > > · *The capacity of the FIWARE Lab* to satisfy the needs of the > startups and SMEs in phase 3 and its evolution to pre-commercial services. > Provide a reliable plan to ensure that the recent bottlenecks in networking > and computing performance will not occur again. This may require a higher > allocation of resources to this task. Provide appropriate access to open > data sources linked into FIWARE Lab and the open access to this > experimental sand-box environment by anybody (trial and community users). > Present a clear plan for the use of the resources dedicated to the open > call (10% of the overall budget). Notably in the context of increased > communications and the support for pre-commercial FIWARE Labs. > > · *Sustainability*: Launching and supporting the open source > community with sufficient support and resources to make it successful. The > setup of a foundation before year end and the transition of FIWARE in a > foundation led initiative. Enlarge the industrial commitment with companies > interested to become long-term partners in the FIWARE foundation and > support the open source community. > > · *A communication strategy* which focusses on communicating a > product-like image of FIWARE, supports the open source community and > launches a social media campaign to reach out world-wide. > > The documentation necessary for this ad-hoc review should be short but > convincing in order to provide a conclusive view of the changes required at > this stage and to ensure that FI-CORE fulfils the strategic tasks necessary > for the PPP phase 3. Please deliver input documents around those topics at > least 10 days before the review takes place. > > I expect that FI-CORE as project will adhere to the new work plan as of 1 > July 2015. Therefore, please initiate the necessary instructions to the > consortium partners to halt work in areas likely to be restructured. > > Finally, please make sure that this note reaches every beneficiary of the > FI-CORE contract. > > Kind regards, > > Jesus Villasante > > > > *Jesus VILLASANTE* > > *Head of Unit* > > << OLE Object: Picture (Device Independent Bitmap) >> > *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 y sus adjuntos se dirigen exclusivamente a su destinatario, > puede contener información privilegiada o confidencial y es para uso > exclusivo de la persona o entidad de destino. Si no es usted. el > destinatario indicado, queda notificado de que la lectura, utilización, > divulgación y/o copia sin autorización puede estar prohibida en virtud de > la legislación vigente. Si ha recibido este mensaje por error, le rogamos > que nos lo comunique inmediatamente por esta misma vÃa y proceda a su > destrucción. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual or > entity named above. If the reader of this message is not the intended > recipient, you are hereby notified that any dissemination, distribution or > copying of this communication is strictly prohibited. If you have received > this transmission in error, do not read it. Please immediately reply to the > sender that you have received this communication in error and then delete > it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinatário, pode conter informação privilegiada ou confidencial e é > para uso exclusivo da pessoa ou entidade de destino. Se não é vossa > senhoria o destinatário indicado, fica notificado de que a leitura, > utilização, divulgação e/ou cópia sem autorização pode estar > proibida em virtude da legislação vigente. Se recebeu esta mensagem por > erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destruição > > > > > > ------------------------------ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, > puede contener información privilegiada o confidencial y es para uso > exclusivo de la persona o entidad de destino. Si no es usted. el > destinatario indicado, queda notificado de que la lectura, utilización, > divulgación y/o copia sin autorización puede estar prohibida en virtud de > la legislación vigente. Si ha recibido este mensaje por error, le rogamos > que nos lo comunique inmediatamente por esta misma vÃa y proceda a su > destrucción. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual or > entity named above. If the reader of this message is not the intended > recipient, you are hereby notified that any dissemination, distribution or > copying of this communication is strictly prohibited. If you have received > this transmission in error, do not read it. Please immediately reply to the > sender that you have received this communication in error and then delete > it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinatário, pode conter informação privilegiada ou confidencial e é > para uso exclusivo da pessoa ou entidade de destino. Se não é vossa > senhoria o destinatário indicado, fica notificado de que a leitura, > utilização, divulgação e/ou cópia sem autorização pode estar > proibida em virtude da legislação vigente. Se recebeu esta mensagem por > erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destruição > > > > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-apps > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-apps/attachments/20150727/7408fc21/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy