The cancellation strands the operating crew too. Unlike the passengers, this is what the engine was built for: the roster goes in as pairings and duty periods and RouteSpring derives the hotel bookings itself. Nothing in this layer plans them. Live
pairing_number, crew_email,
leg_sequence and activity_code are required. Rows are grouped into
pairings and duty periods; a row carrying a layover_station is what makes the
engine book a hotel.
No roster submitted yet.