ISA RAIT Student Section

ISA-RAIT Presents

Artemis Hackathon — National Level Hackathon

The masterpiece is not the first stroke of the brush, but the final victory over a canvas of mistakes.

26–27 September 2026Ramrao Adik Institute of Technology, Nerul

Prologue

In Greek legends, Artemis is worshipped as the goddess of hunt and wilderness. She represents unwavering determination and will to navigate through the challenges unknown to the rest. More than having the greatest resources, a successful hunt demands skilful observation, tricky strategies and adaptability to your environment, overall aiding you to make the right decisions when faced with uncertainty.

ARTEMIS draws inspiration from this unique spirit of the goddess, challenging innovators to step into the unknown and find solutions to real world problems, while within the constraints of limited time and resources. In those 24 hours, we expect ideas to move beyond presentations and imagination to the actual difficulties of confronting the design, failure, testing, and iteration of your solution, before finally becoming something that helps our society.

Every team at ARTEMIS must analyse its challenge, make important engineering decisions, and transform limited resources into a meaningful innovation of their own. ARTEMIS is all about the pursuit of a solution, where your solutions will ultimately be judged by its ability to work in the real world beyond the canvas. Let the challenge begin!

— The Organising Committee

The Trials

Choose your trial

Four trials: three set, and one of your own making.

Asclepius · Healing

Medication Safety and Assistance System

Background

Medication management is a significant challenge for individuals who are required to consume multiple medicines at different times. This is particularly relevant for elderly individuals, patients undergoing long-term treatment, and individuals managing complex medication schedules.

Common medication-related issues include missed doses, incorrect medication intake, repeated consumption of the same dose, and the inability to effectively monitor whether prescribed medication has been taken.

Challenge

Participants are required to design and develop a low-cost automated system that assists users in managing their medication schedule while reducing the possibility of common medication-related errors.

The proposed solution should address one or more challenges associated with medication management, such as timely medication access, medication identification, missed doses, repeated doses, user assistance, monitoring, or communication.

The system must demonstrate a meaningful level of automation and should go beyond a basic reminder or notification mechanism.

Scope for Innovation

Participants are encouraged to explore innovative approaches in areas including automated assistance, intelligent decision-making, verification mechanisms, accessibility, user interaction, monitoring, and communication.

Teams are free to determine the technical approach, system architecture, and implementation methodology based on their proposed solution.

Poseidon · Water

Water Loss and Leakage Prevention System

Background

Water loss caused by leakage, overflow, abnormal consumption, and delayed human intervention remains a significant challenge in residential, commercial, and small-scale infrastructure environments.

In many situations, water loss continues for extended periods before the issue is identified. Conventional systems may provide basic monitoring or alerts but often depend on human intervention before corrective action can be taken.

Challenge

Participants are required to design and develop a low-cost automated system capable of identifying potential abnormal water usage or water loss and initiating an appropriate response to reduce unnecessary wastage.

The proposed solution should demonstrate the ability to distinguish meaningful or potentially abnormal conditions from normal operation based on the team's chosen approach.

The system should focus not only on identifying a potential problem but also on providing an appropriate automated response.

Scope for Innovation

Participants may explore innovative approaches involving intelligent decision-making, adaptive behaviour, predictive analysis, automated intervention, efficient resource management, reduction of false alarms, and improved reliability.

Teams are free to define the specific application scenario and technical methodology for their proposed solution.

Zeus · Lightning

Electrical Hazard Prevention System

Background

Electrical hazards may arise due to abnormal operating conditions, excessive loading, overheating, equipment malfunction, or other developing faults. If such conditions remain undetected, they may lead to equipment damage, electrical accidents, or potentially dangerous situations.

In many cases, conventional protection mechanisms respond only after predefined operating limits have been exceeded and may not provide meaningful information regarding developing or unusual conditions.

Challenge

Participants are required to design and develop a low-cost intelligent system capable of identifying potentially hazardous electrical operating conditions and initiating an appropriate preventive response.

The proposed solution should demonstrate a complete automation cycle involving the identification of a potentially unsafe condition, assessment of the situation, and implementation of an appropriate response.

The solution must go beyond basic parameter monitoring or simple threshold-based indication.

Scope for Innovation

Participants are encouraged to explore innovative approaches involving early risk identification, abnormal behaviour detection, intelligent decision-making, predictive analysis, adaptive responses, automated preventive action, and improved safety mechanisms.

Teams are free to determine the specific hazard scenario, technical methodology, and implementation approach based on their proposed solution.

Hephaestus · Forge

Open Innovation

Background

Not every problem worth solving falls within a domain defined in advance. Teams often arrive having already observed a problem for themselves, in their surroundings, their institution, their field of study, or their daily life, and with a clear idea of what a working solution to it would look like.

This statement exists for those teams. It prescribes no domain and no application area. What it does prescribe is the form the solution must take, because the purpose of this hackathon is the design and development of working systems rather than of applications alone.

Challenge

Participants are required to identify a real and clearly defined problem of their own choosing, and to design and develop a low-cost working system that addresses it. The problem, its context, and the reason it merits a solution must be presented as part of the submission.

The proposed solution must be realised either as a hardware system or as a combination of hardware and software. A purely software solution, such as an application, a website, a dashboard, a model, or any other entirely computational tool, does not qualify under this statement regardless of its merit.

The system must demonstrate a meaningful level of automation and must be presented in working form. A concept, a simulation, or a design proposal alone will not be considered a complete submission.

Scope for Innovation

Participants are free to work in any domain, including but not limited to healthcare, agriculture, environment, energy, mobility, accessibility, safety, and assistive technology, and are encouraged to explore approaches involving sensing, actuation, embedded intelligence, automated decision-making, verification, and user interaction.

Teams are free to determine the problem, the technical approach, the system architecture, and the implementation methodology. Software may carry any part of the solution, whether control, intelligence, interface, or analysis, provided that it operates together with hardware the team has built.

Rules of the Trial

Before you begin

Ten rules govern every entry, whichever trial you take. Two of them bind before the day itself — read six and eight twice.

  1. Each participating team must consist of a minimum of 2 members and a maximum of 4 members.

  2. The hackathon will be conducted continuously for a duration of 24 hours. All participating teams must complete and submit their work within the specified event timeline.

  3. Participants must strictly follow the instructions, timelines, and guidelines provided by the organizing committee throughout the hackathon.

  4. For Round 1, teams must strictly use the official presentation template provided by the organizing committee and adhere to the prescribed slide limit.

  5. All ideas, presentations, designs, code, and prototypes submitted by participating teams must represent their original work. Any form of plagiarism, copying, or misrepresentation of another individual's or team's work is strictly prohibited.

  6. AI tools may be used only as supporting tools. Participants must be able to understand, explain, and justify their proposed solution, implementation, and technical decisions during evaluation.

  7. Each team must submit its required component list within the deadline specified by the organizing committee. The total cost of the requested sensors and electronic components must strictly remain within the maximum budget of ₹2,000 per team.

  8. Only the approved and provided components may be used for prototype development during the hackathon. The use of unauthorized or externally procured components without prior permission from the organizing committee is prohibited. Permitted 3D-printed mechanical structures may be used as per the event guidelines.

  9. Final evaluation will consider factors including innovation and novelty, prototype functionality, technical implementation, automation capability, practical relevance, cost efficiency, and presentation.

  10. Participants must maintain discipline and professional conduct throughout the event. Any misconduct, unfair practices, deliberate interference with another team, damage to equipment, or violation of the event rules may result in penalties or disqualification. The decision of the organizing committee and judging panel shall be final.

The Odyssey

Order of the two days

Two days and the night between them. Times are provisional and will be fixed nearer the day.

Day I

26 September

  1. 08:00

    The Gathering

    Reporting at the college, for the commencement of the event.

  2. 08:30

    Early Feast

    Morning breakfast, before reading of the omens.

  3. 09:00

    Reading of the Omens

    Orientation of the Hackathon in the auditorium, and distribution of hardware kits for each team.

  4. 11:00

    Event Commences

    Official Hackathon starts.

  5. 13:00

    Mid-day Feast

    Lunch break between 1 and 2 pm.

  6. 18:00

    Proespérisma

    Evening snacks break for 15 minutes.

  7. 21:00

    Late Night Feast

    Dinner between 9 to 11 pm.

  8. 23:00

    Labor Continues

    Keep working on your project.

Day II

27 September

  1. 07:00

    Sunrise Ceremonious Drinks and Meals

    Morning tea break and breakfast between 7 to 9 am.

  2. 09:00

    Work Continues

    PPT preparation period.

  3. 11:00

    The Final Reckoning

    The final evaluation of your hackathon project will happen during this time, between 11 am to 2 pm.

  4. 14:00

    Crowning of the Laurels

    Award ceremony for the winners, final goodbyes and farewell speeches.

  5. 17:00

    The Great Labour ends

    The Hackathon ends officially.

The Boons

Gifts of the gods

Laurels, and rather more practical rewards, for those whose work the judges favour.

I

The Golden Bough

₹ 30,000

By the branch of gold, the gates of the unseen open. You topped it all.

II

The Silver Arrow

₹ 15,000

The arrow that hits the bullseye is the result of a hundred misses you didn't let stop you. Don't seek a paved path.

III

The Bronze Aegis

₹ 5,000

Forged under pressure to protect the future of the craft. You made the podium.

The Oracle Speaks

Voices from past trials

What those who came before had to say once the dust settled.

ISA is a platform where individuals from diverse, multidisciplinary engineering backgrounds come together and work as one team. Our goal is to create the best possible environment for collaboration, innovation, and collective development, where diverse ideas and expertise come together to create meaningful impact.

Arya Bhagwat

Treasurer, ISA-RAIT

Artemis represents our collective effort to bring together ideas, innovation, and engineering to address some of the major challenges faced by society. We hope that through this initiative, we can create meaningful solutions, inspire collaboration, and contribute in our own way towards a shared purpose and a better future.

Yash Patil

President, ISA-RAIT

ISA RAIT is more than a committee it’s a community where students learn, build, compete, and grow together. Beyond achievements, it’s about teamwork, friendships, experiences, and memories. We don’t just build technology we build people, leaders, and a community for the future.

Jyotiraditya Patil

Vice President, ISA-RAIT

Cast Your Lot

Enter the trials

Teams of up to four. Registration closes when the last seat goes.

tally.so/…
Loading form…

Form not loading? Open it in a new tab

Consult the Priestess

Questions answered

No, any discipline, any branch, any college students can participate in this hackathon.

Epilogue

As the sacred fires of Artemis 2026 quiet into embers, the sparks of innovation endure. Over 24 intense hours, brilliant minds channeled divine focus to forge groundbreaking hardware from raw silicon and code.

Though the champions of The Golden Bough, The Silver Arrow, and The Bronze Aegis have claimed their glory, this odyssey is only the beginning. May the vision forged under the night sky guide your path until we gather again.

~ ISA-RAIT Student Chapter