Back to work
Amtrak Technologies · Transportation
Amtrak: Schedule Change Automation (SCA)
Reducing dependency on ARROW with a system-wide cancellation tool
- Target user groups
- 4
- Step request flow: Create to Complete
- 5
- Breakpoints: mobile, tablet, desktop
- 3
Goal
Amtrak staff use ARROW, a database tool that holds train schedules, time changes, and cancellations. I designed a schedule change tool that automates those updates, so staff rely less on ARROW and cancellations reach every system at once.
Activities
- Understanding user behavior: research with key stakeholders on their needs and expectations.
- Defining user dependencies: the systems and handoffs that shape how each group works.
- Building interactions: complete workflows for mobile, tablet, and desktop breakpoints.
- Conceptual wireframing: Designing high-level wireframes and translating them into interactive prototypes.
What the tool does
- Interactive dashboard which supports single, partial, and full train cancellations.
- Re-accommodation of customers.
- Advanced search functionality.
- Integrating CRUD operations.
- One flow from request submission to customers contacted.
Target users
- Amtrak Contact Center Supervisors
- Consolidated National Operations Center (CNOC) scheduling desk
- ARROW maintainer desk
- Thruway Service Agents
Stakeholder interview session
What we heard from the users
| Persona | Operations | Pain points |
|---|---|---|
| Amtrak Contact Center Supervisors Amtrak customers contact them whenever they want to cancel an itinerary | First point of contact for customers requesting cancellations or schedule changes. | Often delayed sending cancellation or change requests to scheduling operators; customers can’t track or raise requests themselves; most service requests are sent manually with no automation; supervisors retrieve invoices via email to send to customers. |
| CNOC operators Contact center supervisors connect with them whenever a customer sends a schedule change request | Receive hundreds of schedule change requests spread across multiple regions of the U.S. | Manually enter schedule changes into their database after receiving them from supervisors; no 24/7 support to revert last-minute changes; unable to track maintenance delays. |
| ARROW maintainer Works with the ARROW database, updates train times and schedules | Maintains and updates the core scheduling database. | Very steep learning curve for ARROW; disconnect between the maintainer and contact center supervisor, with no direct way to track customer requests; wants to message CNOC operators directly for faster communication. |
| Thruway Service Agents Third-party agents providing connections such as buses, trams, and ferries | Coordinate connecting service for Amtrak customers. | Delays and response times are a big pain; often the last to be notified of a maintenance update on the tracks. |
Conceptual wireframes
The 5-step request flow: Create, Impact, Process, Contact, Complete.
Open to senior and staff roles
Seen work you'd want on your team?
Book a 30-minute intro call, or email me. I reply within a day.