ITKIT
Airport and road gates · 16 / 20
iCheck
Self check-in and bag drop at shared stations
From the problem to how we solve it
October 2026
Interactive prototype · synthetic data only
The problem
Queues at one desk. Empty desks next door.
1
Check-in queues build while desks of other airlines stand empty.
2
Bags are treated as accepted before the baggage system confirms them.
3
Each airline brings its own kiosks, so stations cannot be shared.
Long queues · A desk per airline · Idle space · One shared station
ITKIT · iCheck · Prototype screens, synthetic data
The problem
Our answer
iCheck · prototype with synthetic data
One kiosk serves every participating airline: scan a passport, weigh and tag the bag, and leave only when the baggage system has confirmed it. Staff and operations consoles handle what the kiosk cannot.
How it works · 1 of 6
Shared station
One station. Every airline.
iCheck is a shared station. Any participating airline runs on any kiosk.
ITKIT · iCheck · Prototype screens, synthetic data
How it works
How it works · 2 of 6
Check in
Scan passport · booking found · seat 14C
She scans her passport. The chip is checked, her booking is found, and she keeps seat 14C.
ITKIT · iCheck · Prototype screens, synthetic data
How it works
How it works · 3 of 6
Bag and tag
21.4 kg · within 23 kg
The bag is within the allowance. The tag prints with a barcode and an RFID inlay.
ITKIT · iCheck · Prototype screens, synthetic data
How it works
How it works · 4 of 6
The difference
Not accepted yet
Here is the difference. The kiosk waits for the baggage system before it says yes.
ITKIT · iCheck · Prototype screens, synthetic data
How it works
How it works · 5 of 6
Confirmed
Accepted means confirmed
Only the reply turns the screen to “Bag accepted”. Then Yara goes to security.
ITKIT · iCheck · Prototype screens, synthetic data
How it works
How it works · 6 of 6
Operations
8 stations need attention
When something goes wrong, the duty manager sees it first and sends a person.
ITKIT · iCheck · Prototype screens, synthetic data
How it works
What it includes
9 screens and workflows in the prototype
Kiosk welcome
Departing passengers at a shared iCheck station
Booking found and seat
Passengers after the passport scan
Weigh the bag
Passengers dropping a bag
Waiting for the baggage system
Passengers whose bag is on the belt
Bag accepted
Passengers whose bag was confirmed
Bag not accepted
Passengers and the staff member who comes to help
Airport operations console
Terminal duty managers
Accessible mode
Passengers with visual, hearing, reach or cognitive needs, and older passengers
ITKIT · iCheck · Prototype screens, synthetic data
What it includes
Built to standards
International standards it is built to
| Standard | What it covers in iCheck |
|---|---|
| IATA CUSS (RP 1706c), CUSS 2.x | Common-use platform and airline applications |
| IATA CUWS (RP 1741) | Self bag drop data exchange |
| ICAO Doc 9303 (8th ed., 2021), Part 11 | Chip passive authentication |
| IATA Resolution 792 (BCBP, guide 7th ed.) | Boarding pass barcode |
| IATA RP 1745 | Baggage information messages |
| IATA Resolution 753 | Baggage tracking points |
| PCI DSS v4.0.1 and IATA RP 1791d | Card payment at the kiosk |
| EN 301 549 (V3.2.1; V4.1.1 adopted 2026) and WCAG 2.2 AA | Accessible self-service terminal |
We align with these standards; certification is issued by accredited bodies, not by ITKIT.
ITKIT · iCheck · Prototype screens, synthetic data
What it includes
Connects to
What iCheck works with
Airline departure control systems (DCS)
Airport baggage handling system
Card payment terminal (excess baggage)
iBoard (bag tags for offload)
Airport operations
ITKIT · iCheck · Prototype screens, synthetic data
What it includes
Safeguards
What iCheck will never do
Not an airline DCS or a baggage system.
A bag is never shown as accepted before the baggage system confirms it.
Excess-baggage rates are set by each airline; amounts shown are illustrative and Demo Air is fictional.
ITKIT · iCheck · Prototype screens, synthetic data
Delivery
How delivery works
Start small, prove it, then scale and hand over
6–10 weeks
Assess
Map what already exists and decide, system by system: reuse, integrate, modernise or build.
4–6 months
Pilot
iCheck at one authority, with real users and a measured outcome, on national infrastructure.
12–24 months
Scale
Roll out by region and service, sharing identity, integration and audit.
Agreed per contract
Operate and transfer
We run it with your team, train them, then hand over operations, code escrow and keys.
Durations are typical ranges, fixed per contract
ITKIT · iCheck · Prototype screens, synthetic data
Delivery
Next step
Book a walkthrough of the iCheck prototype with synthetic flights.
Accessible, bilingual, shared. iCheck is a working name, and Demo Air is fictional. Ask us for a walkthrough.
1 · Demo
A guided session on the iCheck prototype
2 · Assess
6–10 weeks to map what exists and fix the pilot scope
3 · Pilot
4–6 months with real users and a measured result
ITKIT · [contact name, email and phone]
Thank you