1
Team confirmation
Tutors confirm team members, roles, and the project topic before Azure work starts.
June 20, 2026 (Sat) · 11:00 · reg. 10:30
TIU A Campus
Completion Ceremony & AI Hackathon
June 20 closes the 2026 spring semester: a morning completion ceremony for graduates and tutors, then the 1st AI Hackathon in the afternoon — team presentations and awards. This page has the day-of schedule, team setup, and FAQ; the preparation paths (build, samples, judging, submission) live on their own pages.
5
hackathon teams
4
students per team
1
Azure app slot per team
5
slides maximum
Plan Your Day
Five pages cover everything you need before, during, and after the event. Open whichever you need now — the event-day schedule below is the only thing exclusive to this page.
Build paths
30 min / 2 hr / 1 day time-bounded paths with checklists.
Sample tracks
Six deep-dive sample projects with architecture, prompts, code.
Tech & cost
Allowed services, exclusions, and rough budget math.
D-Day flow
Student first-30-minute path and tutor hot-paths.
Judging + Submission
Five-dimension rubric and submission templates.
Event Schedule
10:30
Registration & coffee
Sign in and find your seat in the 1st-floor lobby.
11:00
Completion ceremony
Recognition of graduates and certified tutors, certificate presentation, group photos, and the hackathon briefing.
12:00
Lunch
Shared lunch before the afternoon hackathon.
14:00
Hackathon session
Final working session in the team rooms with judges observing.
15:00
Team presentations
5 teams × 14 min — Team 1 (15:00), Team 2 (15:16), Team 3 (15:32), Team 4 (15:48), Team 5 (16:04).
16:20
Judges’ deliberation
Judges score and decide in a separate room.
16:35
Awards ceremony
Winning teams announced and awarded.
17:05
Closing & group photo
Closing remarks and the final group photo (ends ~17:15).
Need the minute-by-minute student / tutor playbook? See D-Day flow. Technology choices and cost limits are in the technology matrix.
Team Assignment and Account Setup
Teams are assigned during the program so students can use Azure safely without sharing accounts. On June 20 they reconvene for the afternoon working session and presentations.
Team roles: PM / domain lead · Prompt / data lead · Foundry / backend lead · Frontend / demo lead. Per-role responsibilities live in the sample deep-dives, and approved services live in the technology matrix.
2
Account check
Each student signs in with the assigned KOICA-TIU Azure account and completes MFA if prompted.
3
Resource scope
Teams use only their assigned team group, Foundry project, resource group, and app slot.
4
Tutor checkpoint
Tutors check one working model call, one visible UI or notebook, and one safe demo path.
Event FAQ
What if Azure sign-in fails?
Tell your tutor immediately. Keep working in mock mode while the operations team checks the account.
Can we create extra Azure resources?
Use only technologies marked "Allowed now" in the technology matrix. Anything marked possible or ops-enabled needs tutor/admin approval first.
Can we use personal data?
No. Use public, synthetic, or tutor-approved sample data only.
Can we use ChatGPT or other tools?
You may use AI tools for coding and writing help, but the submitted prototype must clearly show the team’s own Azure/Foundry implementation.
General preparation, judging rubric, and submission templates are on the dedicated pages — not duplicated here.
Ready for D-day?
Open the path that matches what you need next.