Scribd
Upload
5 views2 pages

Hackdata26 Guidelines Final

The document outlines a problem statement for designing a semi-autonomous system that aids human decision-making across various domains while ensuring meaningful human control. It specifies team composition, submission requirements including a presentation and a video, and guidelines for both software and hardware tracks, emphasizing innovation and the necessity of a clear system architecture. The focus is on safety, reliability, and real-world applicability, with an encouragement for cross-disciplinary collaboration.

Uploaded by

ujjawalbansal4816
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views2 pages

Hackdata26 Guidelines Final

The document outlines a problem statement for designing a semi-autonomous system that aids human decision-making across various domains while ensuring meaningful human control. It specifies team composition, submission requirements including a presentation and a video, and guidelines for both software and hardware tracks, emphasizing innovation and the necessity of a clear system architecture. The focus is on safety, reliability, and real-world applicability, with an encouragement for cross-disciplinary collaboration.

Uploaded by

ujjawalbansal4816
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Problem Statement

Design an innovative semi-autonomous system that intelligently assists humans in decision-making or task execution
while retaining meaningful human control.

Your solution may operate in domains such as (but not limited to):

• Healthcare

• Transportation and mobility

• Smart infrastructure and cities

• Industrial automation

• Assistive technologies

• Environmental monitoring

• Defense, disaster response, or public safety

The proposed system should focus on safety, reliability, human-in-the-loop interaction, scalability, and real-world
applicability. Emphasis should be placed on how autonomy is shared between the system and the human operator.

Team Rules
1. Each team must consist of exactly 4 participants.

2. All team members must be officially registered on the HackData platform.

3. Cross-disciplinary teams (software + hardware + domain knowledge) are highly encouraged.

4. A participant may be part of only one team.

Submission Requirements
All teams must submit both the following:

1. Presentation (PDF / PPT)

The presentation should clearly explain:

• Problem Identification – the real-world challenge being addressed

• Proposed Solution – detailed explanation of the semi-autonomous system

• Level of Autonomy – what is automated vs. what requires human intervention

• System Architecture – software and/or hardware architecture diagram


• Feasibility & Scalability – deployment potential and constraints

• Expected Impact – technical, social, or economic impact

2. Video (Maximum 3 minutes)

The video should cover:

• Clear explanation of the idea

• Use case or scenario demonstration

• Key innovations and differentiators

• Implementation approach

Optional but recommended:

• Process flow diagram

• Wireframes / mockups

• Simulation results or early experimental validation

Software Track Guidelines


1. The solution must demonstrate meaningful innovation. Simple wrappers around existing APIs, LLM prompts,
or pre-built tools without added value will score poorly.

Hardware Track Guidelines


1. The solution must include non-trivial hardware components, such as:

o Advanced sensor fusion systems

o Embedded systems with control logic

o Robotics or mechatronic designs

o Custom or significantly modified circuitry

2. Purely basic IoT-based solutions without intelligent control or autonomy will not be considered.

3. Hardware designs must be:

o Original, or

o Demonstrate substantial innovation over existing solutions

No physical prototypes are expected for the online round. The problem statement and requirements for the
offline round may differ and will be communicated to shortlisted teams.

Teams are encouraged to focus on strong conceptual clarity, system design, and justification of technical
choices rather than full-scale implementation.

You might also like