From negligence
to compliance.
Malaysia Airports appointed KAS in February 2026 to enforce ground-service-equipment rules at KL International Airport, in line with CAAM requirements. The rules already existed — what was missing was any way to see who was breaking them. MAVEIS, our in-house platform, was built to answer that question. Then it changed the answer.
The rules existed.
The evidence didn't.
Ground service equipment is the fleet that turns an aircraft around — tugs, dollies, belt loaders, ground power units. At KLIA, equipment belonging to twenty-three operators shares one apron. A unit left broken or parked outside its staging area is an obstruction and a source of debris beside a live aircraft. There was no registry of units and no evidence trail, so a breach carried no cost — and nobody could say how bad the problem was. MAVEIS was built to answer that question, then change the answer.
Negligence → Compliance
- Equipment everywhere, and no registry saying whose it is
- A breach left no record behind, so it carried no consequence
- Safety instructions went to a chat group, with no way to show who read them
- Units are registered, and a scan opens the history
- Breaches are photographed and timestamped, so they can be charged
- Instructions are delivered and acknowledged under a named staff ID
Once a breach started costing money, operators stopped. Fewer notices is what the contract is for.
Obstruction → Flow
- Broken units park up and stay, sometimes for months
- Nobody can say whose it is, so nobody chases it
- The crew that needs the stand is the one who finds it blocked
- A defect is reported where it stands, with photo and location
- The unit is flagged unserviceable and held until inspection clears it
- One hour on the clock, identical for every operator
A broken unit gets an owner and a deadline as soon as it is recorded. The apron stays open and aircraft turn on time.
Hearsay → Evidence
- Condition judged by eye and written as loose free text
- Decisions made over the phone and never written against the record
- No way to show who was told what, or when they were told
- Every record numbered in sequence, so a missing one is visible
- Photo, place, time and named officer on all of it
- The same rule and the same clock, applied by the system
A record made at the equipment, not back at a desk — it still stands up months later, to the client or a regulator.
Measure first. Then enforce.
Contract awarded
Malaysia Airports appoints KAS to enforce GSE rules at KLIA, per CAAM requirements.
MAVEIS rolled out
Officers begin recording equipment and breaches in the field.
The problem, measured
Deliberately run without charging: 710 breaches recorded in nine weeks. The scale is measured, not guessed.
Enforcement goes live
Each breach goes on record with a cost attached. Word gets round within days.
The count collapses
59 violations in July become 4 in the first thirteen days of August.
Production go-live
Operators register their own fleets into the live registry.
Word got round
in days.
Through the measurement months the system recorded but nobody was charged — breaches climbed to 165 in a single week. Enforcement went live in July, and the line fell away: 59 violations in July, 4 in the first thirteen days of August. The findings line holds, because equipment keeps wearing out — the work moves from penalising breaches to clearing hazards before they become one.
Built to keep growing.
- Enforcement in production today — the whole flow from sighting to evidenced, charged record
- QR asset identity on 3,653 registered units, durable enough for a tropical apron
- Groundlink companion app in prototype — from 115 portal accounts to the whole ground workforce
- Inspection module with 3D condition capture, and AVP licensing, in development
Want this discipline
in your operation?
Talk to the team that built it →Figures from the MAVEIS system extract of 13 August 2026. Chart shows the approximate weekly shape.