EUBra-BIGSEA – - Europe-Brazil Collaboration of BIG Data Scientific Research through Cloud-Centric Applications

"Simplicity is key for EUBra-BIGSEA. We are promoting 11 components and it’s clear that we need to have a simple message rather than an explosion of the things we have in 11 components. Communication should concentrate more on how customers could solve their problems with EUBra-BIGSEA. The CloudWATCH2 support has helped us realise that we need to take a change of viewpoint towards simplicity and starting the message from the actual benefits for the users."

Ignacio Blanquer, University of Valencia & EU Coordinator, EUBra-BIGSEA

 
 
About EUBra-BIGSEA

The EUBrazil BigSEA project is a research and innovation project funded under the EU-BRA joint funding of the European Commission and the Brazilian Government. CloudWATCH2 assessed the EUBRA BigSEA project in June 2017.

The BigSEA project set out to integrate no less than 11 components into meaningful sets of services and toolkits for its customers. The most prominent use case is the city of Sao Paulo wanting to improve its traffic management and forecast system to provide local and international tourists with better traffic announcements and recommendations for sightseeing, increasing the overall tourism experience in Sao Paulo and its suburbs.

EUBra-BIGSEA at DI4R (Krakow, September 2016) and Cloudscape Brazil (São Paulo, July 2017)

EUBra-BIGSEA & TRL and MRL

The BigSEA project self-assessed with a score at (MRL 4, TRL 5), which is identical to our assessment. The project is well aware of its challenge of needing to integrate a large number of components on heavily varying levels of maturity: While some components can be safely assumed to have reached TRL 8, or even knocking on the door of TRL 9, many other components sit around TRL 4 or 5 at the time of the MTRL assessment. Even though some components reside on the low complexity end of the spectrum, some components still require significant amounts of effort to elevate them to a level of maturity that would allow integration with other components with reasonable effort.

Despite these challenges the project has interesting outcomes with potential – however the communication and value proposition arguments were hidden gems under an overload of technical and very detailed project and component documentation: The information was there, but needed to be carved out by the readers themselves. This is perhaps an overcompensating response to earlier project reviews and criticisms of a lack of documentation.

Given the relatively advanced maturity of the project with about 6 months until completion (at the time of the assessment) the suggestions for the project emphasised improving the description and scope of the various services and added values the project has on offer, and to reduce the overall technical terminology and focus of its web presence.

 

Back to "Tips for "go to market" strategies"