Who lands
Turnaround coordinator, TOC lead, OCC / network ops supervisor, airline IT asked to “do AI” without sending ops data to a public model.
Airlines
Private AI for the turnaround coordinator.
Movement data, delay codes, and station remarks do not belong in a public model. Little AI Pilot sits on the tools TOC already runs — live tracking, delay prediction, remarks from timestamps. Ground operations is the same product from the station side.
Who this page is for
The ops desk that already owns the clock
Who buys
Airline ops leadership + IT/infrastructure. Compliance is in the room because movement and delay data is sensitive even when it is not passenger PII.
What we do
The same three services, on the airline’s wall
Not a public chatbot. Not a new ops system of record.
On-premise & private AI
Open-weight models on servers, private cloud, or air-gap the airline already controls. Chat, search, and inference without sending movement or remarks to a public API.
- Model selection and serving (vLLM, Ollama, or your stack)
- Private retrieval over ops manuals and approved internal sources
- Access control, audit logs, encryption in transit and at rest
- Air-gapped or default-deny outbound when policy requires it
Custom models
Adapt the base model to IATA delay codes, fleet types, station abbreviations, and the house remarks style.
- Fine-tuning (LoRA / QLoRA) on your corpus
- RAG with evaluation on real coordinator prompts
- Domain language and Bahasa Malaysia where the desk uses it
- Quantisation on the hardware you have
LLM automation workflows
Classify, draft, route, write back.
- Timestamp-to-remarks (Little AI Pilot)
- Delay flags with a reason, not a sidebar chat
- Write-back to Workvivo, WhatsApp, or the sheet — where you approve it
- Guardrails: what the model may do, and what stays human
First workflows
One named product. One next desk.
Named work
Little AI Pilot
Live tracking, delay prediction, and remarks from timestamps into Workvivo, WhatsApp, or the sheet. Read the panel below.
Example scope
OCC disruption copilot
Fleet remarks grounded in the airline’s delay codes and manuals, write-back to the existing ops sheet.
The OCC card is a first workflow we would scope. It is not a case study.
Data & security
Why on-prem on this desk
Restatement of the homepage security promises for airline ops data. Not a certification list.
Where it runs
On-prem, private cloud, or air-gapped. We do not require a public model API. Hybrid only when the constraint is real but not absolute.
How we handle data
Encrypted in transit and at rest. Access scoped by role. We do not train a third-party model on your corpus, and we do not pool client data. Movement and remarks stay on infrastructure you control.
How we integrate
Read the ops tracking tool, sheet, and Workvivo first. Write-back only where you approve it. We do not replace TOC or OCC.
Who it belongs to
Weights, prompts, evaluations, and logs from your deployment stay yours. A mutual NDA is ready before any deeper scoping call.
Named work
Little AI Pilot, for the turnaround coordinator
Turnaround Operations Control
The clock that desk still does not have
Some airline groups stood up Turnaround Operations Control so one room can own the 30–35 minute ground clock for the whole fleet. The desk still stitches an ops tracking tool, a Sheet, and Workvivo. Little AI Pilot sits on top of those tools: live tracking, delay prediction, and operational remarks written from timestamps — not from memory.
What it watches
On-chocks through boarding: bags, fuel, IFC, cleaning, lav/water, engineering. Ranked by risk. The reason, not just the flag.
Where it lands
Workvivo, WhatsApp, and the sheet the shift already uses. We do not ask the desk to adopt a new chat app.
Who it is for
The turnaround coordinator first (TOC). Then group engineering / MRO. Ground operations is the station door — see Ground operations. Adjacent to OCC; not a replacement for them.
TOC conversations continue. If you run that desk, write to us and say so. It is not the public headline of the company site.
Built in Malaysia · data residency as a design constraint · English and Bahasa. Why Malaysia
Get in touch
If you run that desk, write to us
Turnaround coordinator, TOC, OCC, or airline IT — if the clock cannot leave the building, say so.
[email protected]Public contact for projects, partnerships, research, and investor conversations.