App:Travel assistance service administration - Revision history

Stefanseiler at 12:25, 22 June 2025

2025-06-22T12:25:05Z

← Older revision		Revision as of 12:25, 22 June 2025
Line 119:		Line 119:
	== Related articles ==		== Related articles ==

	* [[Special Assistance Request Management Suite ~~(SARA~~)]]		* [[SARA.Core (Special Assistance Request Management Suite)]]
	[[Category:Apps]]		[[Category:Apps]]

Stefanseiler at 16:12, 9 March 2025

2025-03-09T16:12:58Z

← Older revision		Revision as of 16:12, 9 March 2025
Line 119:		Line 119:
	== Related articles ==		== Related articles ==

	* [[~~Travel~~ Assistance ~~Service~~ Management Suite]]		* [[Special Assistance Request Management Suite (SARA)]]
	[[Category:Apps]]		[[Category:Apps]]

Stefanseiler: /* Task flow & automation */

2024-12-04T09:46:19Z

Task flow & automation

← Older revision		Revision as of 09:46, 4 December 2024
Line 68:		Line 68:
	* '''OnSegmentServiceClaim'''		* '''OnSegmentServiceClaim'''
	* '''OnSegmentServiceTimeToDelivery''' - Requires the user to enter a Time To Delivery (TTD) meaning how many hours to a departure or arrival event the task shall be created (embarcation or disembarcation event)		* '''OnSegmentServiceTimeToDelivery''' - Requires the user to enter a Time To Delivery (TTD) meaning how many hours to a departure or arrival event the task shall be created (embarcation or disembarcation event)
	* '''~~OnSegmentServiceConfirmation~~'''		* '''OnSegmentServiceFinalApproval'''
			* '''OnSegmentServicePartialApproval'''
			* '''OnSegmentServiceRejection'''
			* '''OnSegmentServicePartialRejection'''
	* '''OnServiceCancellation'''		* '''OnServiceCancellation'''

Stefanseiler: /* Segment limited availability */

2024-12-04T08:51:55Z

Segment limited availability

← Older revision		Revision as of 08:51, 4 December 2024
Line 30:		Line 30:
	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:		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. The user can pick from a list of travel devices, which support this service.		* '''vessel type''' - Only available if the vessel type supports it. The user can pick from a list of travel devices, which support this service.
	* '''segment''' - Only available if the segment supports it. The user can pick from a list of segments, which support this service.		* '''segment''' - Only available if the segment supports it. The user can pick from a list of segments, which support this service.
	Please note, that both limitations can be active.		Please note, that both limitations can be active.

Stefanseiler: /* Service type */

2024-11-27T10:20:25Z

Service type

← Older revision		Revision as of 10:20, 27 November 2024
Line 7:		Line 7:
	== Service type ==		== Service type ==

	* '''~~Medical~~ Service''' '''Category''' - This service requires medical approval before confirming the service		* '''Travel Service''' '''Category''' - This service requires medical approval before confirming the service
	* '''Icon''' - The icon used to signal the request on the backend process of OC		* '''Icon''' - The icon used to signal the request on the backend process of OC
	* '''Color Tag''' - The signal color of the service request in the backend process of OC		* '''Color Tag''' - The signal color of the service request in the backend process of OC

Stefanseiler: /* Service type */

2024-11-27T10:20:07Z

Service type

← Older revision		Revision as of 10:20, 27 November 2024
Line 7:		Line 7:
	== Service type ==		== Service type ==

	* '''Medical Service''' - This service requires medical approval before confirming the service		* '''Medical Service''' '''Category''' - This service requires medical approval before confirming the service
	* '''Color Tag''' - The signal color of the service request in the backend		* '''Icon''' - The icon used to signal the request on the backend process of OC
			* '''Color Tag''' - The signal color of the service request in the backend process of OC

	== Service availability definition ==		== Service availability definition ==

Stefanseiler: /* Service type */

2024-11-27T10:19:25Z

Service type

← Older revision		Revision as of 10:19, 27 November 2024
Line 8:		Line 8:

	* '''Medical Service''' - This service requires medical approval before confirming the service		* '''Medical Service''' - This service requires medical approval before confirming the service
			* '''Color Tag''' - The signal color of the service request in the backend

	== Service availability definition ==		== Service availability definition ==

Stefanseiler at 10:16, 26 November 2024

2024-11-26T10:16:19Z

← Older revision		Revision as of 10:16, 26 November 2024
Line 4:		Line 4:
	* '''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 [[Dev:Travel services - Global travel service map\|global travel service map]].		* '''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 [[Dev:Travel services - Global travel service map\|global travel service map]].
	This article is about this service process customizations, which is done in this app.		This article is about this service process customizations, which is done in this app.

			== Service type ==

			* '''Medical Service''' - This service requires medical approval before confirming the service

	== Service availability definition ==		== Service availability definition ==

Stefanseiler: /* Examples */

2024-11-26T07:59:53Z

Examples

← Older revision		Revision as of 07:59, 26 November 2024
Line 80:		Line 80:
	When the event target ''passenger'' or ''OC internal'' is selected, this defines how often this event will be triggered:		When the event target ''passenger'' or ''OC internal'' is selected, this defines how often this event will be triggered:

	* once per itinerary		* '''once per itinerary''' - this option is not available, if the event target is service delivery partner
	* per [[Dev:Travel Segment Service Items\|service segment item]]		* '''per port in itinerary'''
			* '''per embarcation port in itinerary'''
			* '''per disembarcation port in itinerary'''
			* '''per [[Dev:Travel Segment Service Items\|service segment item]]'''

	For service deliery partner the application is always per [[Dev:Travel Segment Service Items\|service segment item]].		For service deliery partner the application is always per [[Dev:Travel Segment Service Items\|service segment item]].
Line 94:		Line 97:
	* Rule name "AMBULANCE prenotification"		* Rule name "AMBULANCE prenotification"
	** OnSegmentServiceTimeToDelivery''':''' 3 hours		** OnSegmentServiceTimeToDelivery''':''' 3 hours
	** Used Task template: "Ambulance required task"		** Used Task template: "Ambulance required task" (Deadline 1h)
	** Event Target: service delivery partner		** Event Target: service delivery partner
	** Applicability/multiplication: per [[Dev:Travel Segment Service Items\|service segment item]]		** Applicability/multiplication: per [[Dev:Travel Segment Service Items\|service segment item]]
Line 100:		Line 103:
	* Service "UK Border Patrol prenotification"		* Service "UK Border Patrol prenotification"
	** OnSegmentServiceTimeToDelivery''':''' 3 hours		** OnSegmentServiceTimeToDelivery''':''' 3 hours
	** Used Task template: "~~Ambulance required~~ notice"		** Used Task template: "UK Border patrol notice"
	*** ~~ports limitation "LHR", template~~: ~~"UK Border patrol prenotification info"~~		** Event Target: service delivery partner
	* ~~Service "STRETCHER", 3 hours before arrival for "disembarcation ports", no ports~~ limitation, "~~Outstation pickup task~~"		** Applicability/multiplication: per disembarcation port in itinerary
			** Event multiplication restrictions: Port limitation "LHR"

	== Related articles ==		== Related articles ==

Stefanseiler: /* Examples */

2024-11-26T07:53:19Z

Examples

← Older revision		Revision as of 07:53, 26 November 2024
Line 92:		Line 92:

	=== Examples ===		=== Examples ===
	* Service "~~AMBULANCE~~", 3 hours ~~before arrival for~~ "~~disembarcation ports~~", ports limitation "LHR", template: "UK Border patrol prenotification info"		* Rule name "AMBULANCE prenotification"
			** OnSegmentServiceTimeToDelivery''':''' 3 hours
			** Used Task template: "Ambulance required task"
			** Event Target: service delivery partner
			** Applicability/multiplication: per [[Dev:Travel Segment Service Items\|service segment item]]
			** Event multiplication restrictions: none
			* Service "UK Border Patrol prenotification"
			** OnSegmentServiceTimeToDelivery''':''' 3 hours
			** Used Task template: "Ambulance required notice"
			*** ports limitation "LHR", template: "UK Border patrol prenotification info"
	* Service "STRETCHER", 3 hours before arrival for "disembarcation ports", no ports limitation, "Outstation pickup task"		* Service "STRETCHER", 3 hours before arrival for "disembarcation ports", no ports limitation, "Outstation pickup task"