Latest update: The five sample tablets have arrived. A road test in real cars is not possible for now, so all tablets will run at head office as soon as the power adapters now being purchased arrive. Engineering review found the internal tablet test evidence incomplete, so the 24-hour stability test is being repeated on the final version (internal device stability 95% → 70%, results due 5 Oct). Overall development holds at 97%. The Android and CMS developer contracts end on 11 Oct and 1 Nov; a formal handover with a signed handover document per developer and knowledge transfer to the internal team is under way. The campaign PDF report is now live, and the tablet player was released to production.
Executive Summary
Overall Progress
Development scope · EPIC-00–07
97%
Core functional platform is ready (97%). Hardware validation and operational fleet deployment are excluded, pending tablet delivery and partner readiness.
- Core product (100%): Ad playlist, video playback, remote device control, interactive ads, and entertainment features are fully built. The flexible campaign content form was completed on 15 Sep: the advertising team can now configure campaigns for any screen layout, with the system enforcing which slots are mandatory and which media types each slot accepts.
- Testing & QA readiness (100%): Every application runs automated checks before each release build, and internal acceptance testing is complete — all 86 scenarios passed.
- Production deployment (done): The backend went live on 15 Sep and received a second update on 28 Sep that makes the campaign PDF report available in the live environment. The tablet player application was released to production on 25 Sep.
- Internal device stability (70%, was 95%): A formal engineering review on 28 Sep found that the earlier 24-hour test did not prove what it claimed — it ran on an older version, the tablet was not kept on power, and some results were not documented. The test is being repeated on the final version; results are due on 5 Oct and are a condition of the Android handover.
- Team handover: The Android developer’s contract ends 11 Oct (handover signed 9 Oct) and the CMS developer’s on 1 Nov (handover signed 30 Oct). Knowledge is being transferred to the internal team. Each developer signs a handover document; per contract they fix, without extra cost, bugs found before their contract ends for 30 days afterwards. Key condition: all app-signing keys and cloud accounts must be handed to AMG so the company can keep updating the tablets independently.
- Attention point: The Android handover has only eight working days left and three conditions still open: the repeated stability test, a production release of the tablet tools application, and the transfer of signing keys and cloud accounts. The CMS handover has no blockers.
- External dependencies: The five sample tablets arrived; power adapters are being purchased before they can all run. Testing in real cars is not possible for now, so validation moves to head office. Rollout in actual taxis still waits for the taxi partner agreement.
Timeline — Gantt by Epic (Apr–Oct 2026)
Complete
In progress
Planned
Blocked / external dependency
Today (30 Sep)
Swipe horizontally to see the full timeline.
Next management checkpoint: Repeated tablet stability test results (5 Oct), Android handover signed (9 Oct) with all signing keys and cloud accounts transferred to AMG, tablets running at head office once adapters arrive, and the CMS handover (30 Oct).
Go-live to real taxis: pending the taxi-provider partnership decision. Internal development and office-vehicle validation continue independently.