Kapta · 15/09/2026
Start with a clearly bounded admission workflow and observable acceptance criteria. The pilot should demonstrate the connection between ticket, decision and access, including cases that require staff intervention during actual operations.
Who should take part in preparation?
Bring together operations, the FareHarbor administrator, the access supplier and the local ticketing owner. If the scope includes invoicing or reporting, involve those system owners too. Assign an owner to each decision and confirm the necessary technical access before scheduling the test.
Which scenarios should the pilot cover?
Include a valid ticket, incorrect date, cancellation, rescheduling, repeated use and partial group arrival. Add a network outage and manual assistance. For each scenario, write down the expected outcome and the record that proves it. Cover the accessible route planned for the installation.
How should tickets sold before the change be handled?
List outstanding valid tickets and confirm whether the new workflow recognises them. Check previously sent emails, multi-use passes and amended bookings. Define an operational alternative if an older ticket is not recognised, with owners and criteria for stopping the pilot.
How should the decision to proceed be made?
Compare outcomes against agreed criteria: correct decisions, response time under tested conditions, failure recovery and staff support readiness. Identify what remained outside the test. Ask Kapta for a proposal specifying covered equipment, dependencies, deliverables and conditions for expanding the installation.
