Specify the languages required for each parking-system interface and confirm support for the proposed software version. An operator dashboard, a driver-facing kiosk and a printed report may have different language requirements.
List every interface people will use
Identify the language required by operators, maintenance staff and visitors. Include software menus, alerts, reports and any car-finder interface in the requirements list. AKE’s guidance portfolio includes car-finder kiosks as a separate product category, so the visitor interface should not be overlooked.
Verify the proposed release
Ask for a demonstration or representative screenshots of the specific configuration being proposed. Check terminology, character display and the fields that users need to enter or search. Treat language support as something to verify for the selected system, rather than assume from an older software release.
Include language checks in acceptance
Use realistic tasks in the chosen languages during the acceptance review. For example, ask an operator to find a parking zone and a visitor to follow the car-finding workflow. Record any required corrections before final handover.
Questions and answers
Does an old FAQ confirm all current software languages?
No. Confirm the supported languages for the proposed software version and each required interface.
Should car-finder language be checked separately?
Yes. Driver-facing kiosk or mobile instructions should be included in the language requirements and acceptance checks.
