Applications Due: 05/15/2022 20:30
Event has ended
  • --
  • --
  • --
Rute C. Sofia

Event checklist


About this event

Co-located with CONASENSE 2022, 27th-29th June 2022, Munich, Germany Project registration:


Hackathon Organizers

fortiss GmbH (; Unternehmer TUM/Munich Colab

Technical Committee

EU-IoT Challenge Domains: Rute Sofia (fortiss), Lamprini Kolovou (Martel); John Soldatos (Intracom); Mirko Presser (Aarhus University); Brendan Rowan (Bluspecs)

EFPF Challenge Domains: Mitula Donga (fortiss), Alexandros Nizami (ITI-CERTH), Florian Jasche (Fraunhofer FIT), Ingo Martens (Hanse Aerospace); Carlos Coutinho (Caixa Mágica), Usman Wajid (Information Catalyst)


The EU-IoT Hackathon focuses on “sustainable next generation IoT applications”. We invite you to bring your ideas and to develop solutions that address IoT skills training, IoT sustainable business models, IoT novel technical solutions in the context of 5 tracks: IoT interfaces, far Edge, near Edge, infrastructure, and data spaces.

The aim of the EU-IoT Hackathon is to disseminate new business ideas, experiments and prototypes as first step to best support next generation sustainable IoT solutions.

The teams shall have the opportunity to develop their ideas within an international flagship environment being mentored by several international experts from the Next Generation IoT (NGIoT) community and being in contact with NGIoT community flagship events.

Challenge Domains

IoT Interfaces: Augmented Reality Interfaces based on the Smart Mirror concept ##

Smart mirrors are a common tool in environments such as home automation, or even retail. The starting point for this challenge is the use of a smart mirror as an IoT hub to the real world. The aim is to integrate new features (feedback to the user) that can improve efficiency and provide a better quality of experience for the user in different environments, e.g., at home, at retail stores (example01 , example02) , in the car (example03) , on the go.

far Edge: Sustainable IoT via TinyML

Tiny machine learning (TinyML) relates with the application of ML on constrained devices with low power, to perform data analytics without necessarily being connected to the Cloud. TinyML projects focusing on this challenge are expected to address IoT solutions on the far Edge that could improve detection of collective health abnormal situations, for instance, persons without a mask on a room; abnormal temperature levels in a school; abnormal environmental situations, e.g., a potential fire; analysis of plants health, etc. The application domains are varied: agriculture, industry, buildings, healthcare, etc.

near Edge: sustainable MEC applications

The aim of this track is to think and develop a project focused on how to best develop Edge-based sustainable services that rely on the ETSI MEC framework .

Infrastructure: Simulating Time-sensitive and Deterministic networking IoT applications

The focus of this track is to propose a service that can best demonstrate the support of real-time applications across deterministic heterogeneous environments. Specifically, you will be working with the fortiss ns-3 deterministic wireless/wired framework, and have the possibility to develop a concrete use-case showing its performance via ns-3.

Data Spaces: Sustainable, user-centric smart mobility

The focus of this challenge is to, based on the analysis of mobility data, come up with ideas and apps that may assist a better functioning of a smart region. This may relate, for instance, on the development of a solution that can provide real-time information about points of interest in a city. It may also relate with a platform, such as a dashboard, that, via data fusion and analytics, can benefit a smart city services. Relevant to address are solutions that can improve sustainability and a green lifestyle.

European Factory Platform: IoT services for Manufacturing

• Sub-challenge EFPF1: Semantic matchmaking for the support of environmental monitoring of the shop-floor. You will be using the open-source EFPF TSMatch gateway ( to improve the existing apps, or to improve the interconnection between TSMatch and the EFPF Data spine.

• Sub-challenge EFPF2: Evaluate the EFPF SDK in developing digital smart manufacturing applications. You will be using the EFPF SDK studio to create applications.

• Sub-challenge EFPF3: Evaluate the usability of the Data Spine for the creation of composite applications. You will be testing the EFPF Data Spine ( and its usability, proposing specific improvements.

• Sub-challenge EFPF4: Analyze industrial data coming from EFPF partners and provide insights based on the EFPF analytics tools. You will be working with open-source Machine Learning Libraries and propose applications for the visualization and analysis of industrial data.

Types of Projects

  • Technical projects: where the focus is on the development of a technical solution to address the challenge. The outcome shall be provided in the form of open-source code to be uploaded to the EU-IoT Hackathon git repository.
  • Training skills projects: where the focus is on the development of a training tool to be available online which addresses the specific proposed challenge. Outcome can be: a Web-based training tool; a Tutorial (e.g., PowerPoint, video), etc. *Prototype Business/Design ideas: where the focus is on the development of a business framework for an IoT solution.


  • Team registration AND challenge selection: 15.05.2022 = register here

  • EU-IoT Hackathon preparation event (online): 30.05.2022

  • Hackathon: 27th-29th 2022, co-located with the CONASENSE 2022 workshop in Munich, Germany - hybrid mode also feasible - contact the organizers for details via


  • Monday
  • This agenda is tentative, and subject to change. Please check closer to the date!

    Hackathon opening and tutorial sessions, 14:00-18:00

  • Tuesday
  • This agenda is tentative, and subject to change. Please check closer to the date!

    Hackathon project development and tutorial sessions, 14-18:00



1. Code of Conduct All participants (developers, experts, mentors, etc.) are expected to follow the overall professional and ethical principles, including the principles for shared software o...

1. Code of Conduct

All participants (developers, experts, mentors, etc.) are expected to follow the overall professional and ethical principles, including the principles for shared software of the ACM code of conduct, available here: Additional aspects to observe are: * No harassment, including personal attacks are allowed. * No spam via E-mail or via any of the Hackathon channels will be tolerated. Posts not relating to hackathons or tech will also be considered spam. * No recruiting for the participating organizations is allowed. Recruitment requests can be discussed with the organizing committee. * No illegal/pirated content is allowed. * Violations to the code of conduct imply team disqualification.

2. Evaluation

The projects shall be supported in a continuous manner and evaluated by the Juri in the meetups of the Hackathon as well as during the final event, based on an objective assessment template provided via Google docs by the coordinating team. For each criterium, each member of the Juri will also be requested to provide feedback.

As explained, the Hackathon is not a competition, so the aim of the assessment is inclusive and to provide a measurement of the effort of the teams. All teams will be provided with awards; and the grading serves the purpose of, in addition, providing best awards in the different categories. The teams will be provided with a report of the final evaluation, which includes averaged grades for each criterium.

Each member of the Juri is provided with an individual template for the evaluation and shall provide a grade between 1 (lower value) to 5 (higher value) to each criterium. The final grading is then the average of all Juri members.

2.1 Technical Project Evaluation Criteria

  • Novelty: How novel are the results compared to related work? 20%
  • Reusability: How easy is it for non-team members to replicate results? 30%
  • Usability: How user-friendly is the developed solution? 30%
  • Community Impact: In your opinion, how likely is this solution to be of interest to the community in the future? 20%

2.2 Skills Training Project Evaluation Criteria

  • Novelty: How novel is this tool in comparison to others that are similar? 10%
  • Reusability: How easy is it for non-team members to replicate results? 30%
  • Reach: What is the reach of the tool in terms of community range, e.g. 10 persons, 100 persons? 30%
  • Resources: How many trainers does the tool need? Would the training require specific equipment, software, etc.? 10%
  • Quality: Quality of developed material (slides, documentation, etc.) in terms of language, graphics, etc. 20%

    2.3 Business Skills Training Project Evaluation Criteria

  • Value proposition: Is the description clear? Is the product feasible and targets a real gap? How easily it can be duplicated? Is there a presence of potential substitutes for the product? 20%

  • Market value: Is there a genuine need for the product or service? How well was the target market defined? What is the size and growth of the market? What is the consumers' willingness to pay for the product/service? 20%

  • Creativity: Is the problem addressed in a novel and creative way? 10%

  • Feasibility: Does the idea/proposal aspire towards clear, realistic, and achievable goals, while thinking big? Can it be implemented effectively? 20%

  • Quality/Presentation: Does the proposal engage the audience? Level of graphical quality? Exciting pitch/report? 10%

  • Sustainability: Does the proposal consider key EU sustainable goals, e.g., energy efficiency? Does it explain how it could break even or raise additional funding (economic sustainability)? Does it consider the different dimensions of financial and social sustainability in a conscientious manner? 10%

3. Roles and Responsibilities

3.1 Hackathon Co-Chairs

The Hackathon co-chairs are responsible for the overall organization and operationalization of the Hackathon and its different meetings, as well as for the development and maintenance of the different tools. The Chairs are the main contact point for all operational questions and concerns. The Chairs can be contacted via

3.2 EU-IoT Hackathon Organizing Committee

The EU-IoT Hackathon Organizing Committee is composed of representatives of each member of the EU-IoT consortium, and are responsible for the alignment with the overall goals of EU-IoT; support the Co-chairs in the dissemination and overall organization of the event.

3.3 Mentors

The Hackathon Mentors are elements of the EU-IoT consortium assigned to the different proposed projects. The Mentors have the following responsibilities: * Volunteer to lead 1 or more proposed projects * Serve as the primary technical and guidance contact for the team questions and respective project guidance * Add and manage the project information on the Hackathon Wiki * Assist the support of the project artifacts in the Hackathon GitLab account * Promote the project in the NGIoT community

3.4 Juri

The Juri are elements of the different RIAs, as well as from the EU-IoT Expert Group. The Juris follow the work of the teams via the different meetings; and shall have access to the different reports and presentations.

As the Hackathon is not a competitive event, the aim of the Juri is to assist in establishing an overall objective appreciation of the work of the different teams, assessing the potential to follow-up e.g., in Open Calls of the existing projects, etc. For that purpose, the Juri shall base the evaluation on offline formulars, templates which shall be provided via the Wiki in a transparent way.

3.5 Teams

  • A team can be formed by 1 to 6 persons.
  • Prizes are provided to teams, not individuals.
  • Changes to the registered team need to be discussed with the organizing committee by sending a mail to

3.6 Submitting a Project

When submitting your project, please register it via "applicants". The description should have the following:

  • Challenge domain where your project fits
  • Project type (business, technical, training)
  • team bio and names