Systems

Platform information and proposed QAF engineering. Component imagery is illustrative; final configuration and regional performance require validation.

Clear for the guest. Useful for the operator.

The screen the guest sees

The platform's two screens stay where they are; the software on them is ours. Arabic first, English beside it, right-to-left throughout, the Hijri date beside the Gregorian, and prayer times for the city of service from the Umm al-Qura calendar. No advertising, no app store, nothing that asks the guest for anything.

The proposed Emerald cabin in bone and mocha with plain controls and satin-brass edging

A laptop on a depot desk showing a map with a scatter of small dots, a QAF through the window

The fleet controller

The proposed fleet interface brings charge, temperature, location, door state and fault information into one operator view. The operator sets speed limits by zone, schedules pre-cooling, and can receive early fault indications. Open protocols, so it sits inside an existing back office.

Safety

The intent is to preserve the platform’s safety systems, including stability control, anti-lock brakes, airbags and pedestrian alerts. Their integration must be assessed on the final vehicle. On top of them: a geofenced speed limit, a walking-pace mode for a plaza, a reversing camera on every model, and, on the five-door, the platform's driver-assistance package where the operator wants it.

A small camera lens set into the brass-framed rear panel

Charging and energy

CCS2, the depot unit, and vehicle-to-load are described under Battery and Ownership.

Updates

Software is updated at the depot, over the fleet's own network, with the operator's approval — never in service, never without a record against the build number.

Made for the guest.

The small things a QAF does for the person in the rear seat.

The Guest