App:Travel assistance service administration
The travel service administration is split into two parts:
- Global travel service map - this holds a list of all known travel services known to b-op. It is centrally maintained and acts as standardization between all carriers. This is required to provide global compatibility and to deliver the option for collaboration.
- Service customization - Each carrier digital, e.g. Lufthansa / LH, may define, where, how and by whome services are delivered and customize services picked from the global travel service map.
This article is about this service process customizations, which is done in this app.
Service availability definition
By picking from a list of global travel service definitions, it becomes generally available to the carrier. Once this is done the customization part starts:
- generally available - The service is available to all ports/segments or
- limited available - in this case the carrier wants to define availability per port or per offered segment.
Port limited availability
If limited availability is selected and point of delivery is set to "per port", the carrier has to define how service availability to the PAX can be determined. In this case PAX availability settings can be:
- embarcation - Only availbale, if embarcation ports support this service
- disembarcation - Only available, if disembarcation ports support this service
- embarcation and disembarcation - Only available, if the embarcation ports and disembarcation points of a trip support this service
- all - Only available if each port of the itinerary support the service
Within the delivery partner administration app, the list of supported services at supported ports and the available service providers can be defined.
Segment limited availability
If limited availability is selected and point of delivery is set to "offered segment", the carrier has to define how service availability to the PAX can be determined. In this case PAX availability settings can be:
- travel device - Only available if the travel device supports it. If so, the travel device administration will allow the admin per each travel device to define if the service is available or not.
- segment - Only available if the segment supports it. If so, the offered segments administation, will allow the admin per offered segment to define if the travel service is available or not.
- travel device and segment - Only available if the travel device and segment support it. In this case in both administrations, the admin will be offered to define availability.
Examples for service availability definition
- Service "Wheelchair". The point of service delivery is "port", as the wheelchair service is delivered at airports. The service availability is set to "generally available", as the carrier knows that each port has to be able to deliver this service due to IATA regulations.
- Service "STRETCHER". The point of service delivery is "travel device" and availability is "travel device and segment". As STRETCHER requires mounting/dismantlich, the service stations "LH Technics Frankfurt" and "LH Technics Munich" are selected both for mounting and dismantling.
Service mounting/dismantling task automation
If the service requires work at the travel device, the service stations which are able to do the mounting/dismantling work per travel device for this service have to be defined. So the admin user can pick from the available service stations and define, if they support mounting or dismantling action or both, which is equired for rotation planning! For each service station supporting mounting and dismantling, the admin can define one or multiple mounting/dismantling rules. Each mounting/dismantling rule holds these information:
- time distance - how many hours to a mouting/dismantlich the task shall be created
- task template to use - the task template to use for the creation of the task
Examples:
- Service "STRETCHER", 24 hours before mounting, task template "Mounting task to service station"
- Service "STRETCHER", 6 hours before mounting, task template "Mounting task check to MOC"
Carrier side - Communication task automation
If the service requires port notifications, port notification rules can be defined. Each rule has three atributes, by which the system knows when and for which ports to create tasks
- EventTrigger - OnSegmentServiceClaim, OnSegmentServiceTimeToDelivery, OnSegmentServiceConfirmation, OnServiceCancellation
- Time To Delivey (TTD) - how many hours to a departure or arrival event the task shall be created (embarcation or disembarcation event)
- port application (multi-select is possible) - for which ports of the itinerary this task shall be created (only if service is supported there)
- embarcation ports - this task will be created for each embarcation port
- disembarcation ports - this task will be created for each disembarcation port
- transfer-from ports - will be applied to each transfer port of the itinerary. (handover from operator of earlier segment)
- transfer-to ports - will be applied to each transfer port of the itinerary. (handover to operator of next segment)
- ports limitation (optional) - This list of ports to which this task shall be created. If not specified, all ports defined through port-application are triggering this event
- Task template to use - the task template to use for creation of this task.
Examples:
- Service "AMBULANCE", 3 hours before arrival for "disembarcation ports", ports limitation "LHR", template: "UK Border patrol prenotification info"
- Service "STRETCHER", 3 hours before arrival for "disembarcation ports", no ports limitation, "Outstation pickup task"